CN103684813A - ENUM-DNS disaster recovery method and system used in IMS network - Google Patents
ENUM-DNS disaster recovery method and system used in IMS network Download PDFInfo
- Publication number
- CN103684813A CN103684813A CN201210321499.7A CN201210321499A CN103684813A CN 103684813 A CN103684813 A CN 103684813A CN 201210321499 A CN201210321499 A CN 201210321499A CN 103684813 A CN103684813 A CN 103684813A
- Authority
- CN
- China
- Prior art keywords
- process module
- overhead
- account
- main
- enum
- 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.)
- Granted
Links
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
- H04L69/40—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass for recovering from a failure of a protocol instance or entity, e.g. service redundancy protocols, protocol state redundancy or protocol service redirection
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L61/00—Network arrangements, protocols or services for addressing or naming
- H04L61/45—Network directories; Name-to-address mapping
- H04L61/4505—Network directories; Name-to-address mapping using standardised directories; using standardised directory access protocols
- H04L61/4511—Network directories; Name-to-address mapping using standardised directories; using standardised directory access protocols using domain name system [DNS]
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L61/00—Network arrangements, protocols or services for addressing or naming
- H04L61/45—Network directories; Name-to-address mapping
- H04L61/4557—Directories for hybrid networks, e.g. including telephone numbers
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
- H04L67/10—Protocols in which an application is distributed across nodes in the network
- H04L67/1095—Replication or mirroring of data, e.g. scheduling or transport for data synchronisation between network nodes
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Computer Security & Cryptography (AREA)
- Hardware Redundancy (AREA)
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
- Data Exchanges In Wide-Area Networks (AREA)
Abstract
本发明公开了一种IMS网络中的ENUM-DNS容灾方法，包括：主开销户进程模块定期将本机数据库中的数据同步到备开销户进程模块；还包括：系统运行过程中，当主开销户进程模块出现故障时，备开销户进程模块执行数据同步操作，之后代替主开销户进程模块进行工作；当主开销户进程模块恢复正常后，备开销户进程模块将本机数据库中的数据同步到主开销户进程模块；主开销户进程模块执行数据同步操作，之后代替备开销户进程模块进行工作。本发明还同时公开了一种IMS网络中的ENUM-DNS容灾系统和服务器，运用该方法、系统和服务器可避免主、备机房中的ENUM-DNS服务器交替运行过程中数据丢失的问题，进而提高业务的可靠性。
The invention discloses an ENUM-DNS disaster recovery method in an IMS network, which includes: the main account opening process module periodically synchronizes the data in the local database to the standby account opening process module; When the account process module fails, the backup account process module performs data synchronization operations, and then replaces the main account process module to work; when the main account process module returns to normal, the backup account process module synchronizes the data in the local database to The main account opening process module; the main account opening process module performs data synchronization operation, and then works instead of the backup account opening process module. The present invention also discloses an ENUM-DNS disaster recovery system and server in an IMS network at the same time. Using the method, system and server can avoid the problem of data loss during the alternate operation of ENUM-DNS servers in the main and backup computer rooms, and further Improve business reliability.
Description
Technical Field
The present invention relates to disaster recovery technology in an IP Multimedia System (IMS) network, and in particular, to a Telephone number mapping working group (ENUM) -Domain Name System (DNS) disaster recovery method and System in an IMS network.
Background
IMS is a new form of multimedia service. Currently, IMS can meet the demand of more innovative and diversified multimedia services for end users. The user in the IMS may be a mobile phone user in a normal case, or may be a soft terminal with a specific number.
The ENUM-DNS server provides a service for querying a correspondence between a telephone number, a domain name, and a host resource for the IMS, and plays a significant role in a telecommunication service. An account opening and canceling process module of the ENUM-DNS server is responsible for processing account opening and canceling messages sent by a telecommunication service support system, the account opening and canceling process module stores the data of opening and canceling in a temporary table of a sybase database, a service foreground module checks the data in the temporary table of the sybase database at regular time and informs a service background module of the ENUM-DNS server to load the data, and the service background module stores the data for a client to inquire. If a disaster tolerance mechanism does not exist, once the account opening and canceling process module fails, the telecommunication service support system cannot issue an account opening and canceling message to the account opening and canceling process module, and immeasurable economic loss can be brought.
In order to solve the above problems, the prior art provides certain solutions, as follows: the method comprises the steps that a main ENUM-DNS server and a standby ENUM-DNS server are arranged, each ENUM-DNS server is provided with a service background module, an account opening and closing process module, a database and a service foreground module, one ENUM-DNS server is arranged in a main machine room, and the other ENUM-DNS server is arranged in a standby machine room. The ENUM-DNS server in the default main computer room carries out service operation with the telecommunication service support system, and when the ENUM-DNS server in the main computer room fails, the ENUM-DNS server in the standby computer room replaces the ENUM-DNS server in the main computer room to work so as to ensure that the service is continuously carried out; and when the ENUM-DNS server in the main computer room returns to normal, the ENUM-DNS server in the main computer room continues to work. However, in the process of the alternate operation of the ENUM-DNS servers in the main machine room and the standby machine room, part of data will be lost, the proceeding of the telecommunication service is influenced to a certain extent, and the reliability is not high.
Disclosure of Invention
In view of the above, the main objective of the present invention is to provide a method and a system for disaster recovery of ENUM-DNS in an IMS network, which can avoid the problem of data loss during the alternate operation of ENUM-DNS servers in the main and standby rooms, thereby improving the reliability of services.
In order to achieve the purpose, the technical scheme of the invention is realized as follows:
a telephone number mapping working group ENUM-domain name system DNS disaster tolerance method in IP multimedia system IMS network, the method includes: the main overhead account process module periodically synchronizes data in a local database to the standby overhead account process module; further comprising:
in the system operation process, when the main overhead account process module fails, the standby overhead account process module executes data synchronization operation and then replaces the main overhead account process module to work;
after the main overhead account process module returns to normal, the standby overhead account process module synchronizes data in the local database to the main overhead account process module; the main overhead account process module executes data synchronization operation and then replaces the standby overhead account process module to work.
In the above scheme, the process of the main accounting process module periodically synchronizing the data in the local database to the standby accounting process module is as follows:
setting a timing backup script on a machine where a sybase database of an ENUM-DNS server of a main computer room is located, wherein the script regularly backs up data in the sybase database to a fixed directory;
a main overhead account process module reads each zone serial number in a domain name table from a sybase database corresponding to the main overhead account process module regularly and writes the zone serial numbers into a fixed directory binary file of a local machine;
the main accounting process module is provided with a File Transfer Protocol (FTP) script and periodically transmits a fixed directory binary file of the ENUM-DNS server of the main computer room to a fixed directory of the standby accounting process module through the FTP.
In the above scheme, the data synchronization operation flow is as follows:
the accounting process module reads a binary file under a self fixed directory and acquires a zone serial number in another accounting process module sybase database;
the overhead account process module queries a zone serial number in a self sybase database;
the accounting process module compares the zone serial number of the accounting process module with the zone serial number of another accounting process module, if the zone serial number of the accounting process module is larger than or equal to the zone serial number of the another accounting process module, the data synchronization operation is ended; otherwise, the overhead account process module leads the backup file in the other overhead account process module sybase database under the fixed directory into the local sybase database;
wherein, the overhead account process module is: a main overhead account process module or a standby overhead account process module.
In the above scheme, the method further comprises:
and the standby overhead account process module determines the failure or recovery of the main overhead account process module through a hypertext transfer protocol (HTTP) heartbeat message between the standby overhead account process module and the main overhead account process module.
In the above scheme, the method for determining that the main overhead account process module fails by the standby overhead account process module is as follows:
the standby account opening and canceling process module sends HTTP heartbeat request information to the main account opening and canceling process module at regular time, if the receiving and monitoring port of the standby account opening and canceling process module is closed and HTTP heartbeat response information of the main account opening and canceling process module is not received for n times continuously, the standby account opening and canceling process module determines that the main account opening and canceling process module breaks down; wherein n is a positive integer.
In the above scheme, the method for determining the failure recovery of the main overhead account process module by the standby overhead account process module is as follows:
and the standby account opening process module sends HTTP heartbeat request messages to the main account opening process module at regular time, and if the standby account opening process module receives HTTP heartbeat response messages returned by the main account opening process module and a receiving monitoring port of the standby account opening process module is in an open state, the standby account opening process module determines that the main account opening process module has recovered from faults.
An ENUM-DNS disaster recovery system in an IMS network, the system comprising: a main overhead account process module and a standby overhead account process module; wherein,
the main overhead account process module is used for periodically synchronizing data in a local database to the standby overhead account process module; after the self fault is recovered, executing data synchronization operation, and then replacing a spare overhead account process module to work;
the backup overhead account process module is used for executing data synchronization operation when the main overhead account process module fails in the system operation process and then replacing the main overhead account process module to work; and after the main overhead account process module is recovered to be normal, synchronizing the data in the local database to the main overhead account process module.
In the above scheme, the backup overhead account process module is further configured to determine a failure or recovery of the main overhead account process module through an HTTP heartbeat message with the main overhead account process module; accordingly, the method can be used for solving the problems that,
and the main overhead account process module is also used for communicating with the standby overhead account process module through HTTP heartbeat messages.
An ENUM-DNS server comprising an overhead process module for periodically synchronizing data in a local database to an overhead process module in another ENUM-DNS server; after self-failure recovery, data synchronization operation is performed, and then work is performed instead of an overhead process module in another ENUM-DNS server.
In the above solution, the ENUM-DNS server is further configured to communicate with an overhead account process module in another ENUM-DNS server through an HTTP heartbeat message.
An ENUM-DNS server comprises an overhead process module, which is used for executing data synchronization operation when an overhead process module in another ENUM-DNS server goes wrong in the running process of a system and then replaces the overhead process module in another ENUM-DNS server to work; and after the overhead account process module in the other ENUM-DNS server is recovered to be normal, synchronizing the data in the local database to the overhead account process module in the other ENUM-DNS server.
In the above solution, the ENUM-DNS server is further configured to determine, through an HTTP heartbeat message with an overhead process module in another ENUM-DNS server, a failure or recovery of an overhead process module in another ENUM-DNS server.
The invention provides a disaster recovery method and a system of an ENUM-DNS in an IMS network.A main invoicing process module periodically synchronizes data in a local database to a standby invoicing process module; in the system operation process, when the main overhead account process module fails, the standby overhead account process module executes data synchronization operation and then replaces the main overhead account process module to work; after the main overhead account process module returns to normal, the standby overhead account process module synchronizes data in the local database to the main overhead account process module; the main overhead account process module executes data synchronization operation and then replaces the standby overhead account process module to work. In the invention, when the main overhead account process module fails or the main overhead account process module recovers from a fault, the standby overhead account process module or the main overhead account process module can perform data synchronization operation to ensure that the overhead account information in the currently running ENUM-DNS server is the latest, so that the problem of data loss in the process of the alternate running of the ENUM-DNS servers in the main machine room and the standby machine room can be avoided, and the reliability of the service is further improved.
In addition, the standby overhead process module determines the fault or recovery of the main overhead process module through the heartbeat message between the standby overhead process module and the main overhead process module, and the occurrence and elimination of the fault of the main overhead process module can be determined in time through the heartbeat mechanism, so that the fault can be eliminated in time, and the smooth operation of the telecommunication service is ensured.
Drawings
Fig. 1 is a schematic flow chart illustrating an implementation of an ENUM-DNS disaster recovery method in an IMS network according to the present invention;
FIG. 2 is a schematic diagram of a flow implementation of a data synchronization operation according to the present invention;
FIG. 3 is a flowchart illustrating a method when a master overhead account process module fails according to an embodiment of the present invention;
FIG. 4 is a flowchart illustrating a method for recovering a failure of a master overhead account process module according to an embodiment of the present invention;
fig. 5 is a schematic structural diagram of an ENUM-DNS disaster recovery system in an IMS network according to the present invention.
Detailed Description
The basic idea of the invention is: the main overhead account process module periodically synchronizes data in a local database to the standby overhead account process module; in the system operation process, when the main overhead account process module fails, the standby overhead account process module executes data synchronization operation and then replaces the main overhead account process module to work; after the main overhead account process module returns to normal, the standby overhead account process module synchronizes data in the local database to the main overhead account process module; the main overhead account process module executes data synchronization operation and then replaces the standby overhead account process module to work.
In the present invention, the main overhead account process module is: an account opening and canceling process module of an ENUM-DNS server in the main computer room; the backup overhead account process module is as follows: and an account opening and canceling process module of the ENUM-DNS server in the standby machine room.
Further, the standby overhead account process module determines the failure or recovery of the main overhead account process module through the heartbeat message between the standby overhead account process module and the main overhead account process module.
The invention is described in further detail below with reference to the figures and the embodiments.
Fig. 1 is a schematic flow chart of an implementation process of an ENUM-DNS disaster recovery method in an IMS network according to the present invention, as shown in fig. 1, including the following steps:
step 101: the main overhead account process module periodically synchronizes data in a local database to the standby overhead account process module;
the method specifically comprises the following steps: a timed backup script may be placed on the machine where the sybase database of the main room ENUM-DNS server resides, periodically, for example: at 1 am each day, data in the sybase database was written using the bcp command, as: 4 main tables in the database are backed up to a fixed directory; in the present invention, the 4 main tables may include: an Id identification table (eds _ identity), a domain name table (zone table), a number formal table (exist _ res), and a parameter table (net _ param _ conf); the master overhead account process module periodically, for example: reading each zone serial number in a domain name table from a sybase database corresponding to each zone serial number at 1 point every morning, and writing the zone serial numbers into a fixed directory binary file of a local machine; the main account opening and closing process module is provided with a File Transfer Protocol (FTP) script, and a fixed directory binary file of an account opening and closing process module of the ENUM-DNS server of the main computer room is periodically transmitted to a fixed directory of the standby account opening and closing process module through the FTP.
Step 102: in the system operation process, when the main overhead account process module fails, the standby overhead account process module executes data synchronization operation and then replaces the main overhead account process module to work;
in the invention, the main and standby account opening and canceling process modules determine who works through a heartbeat mechanism, specifically, the main and standby account opening and canceling process modules ensure that only the main account opening and canceling process module or the standby account opening and canceling process module opens the receiving and monitoring port of an account opening and canceling at the same time through heartbeat messages, and when the account opening and canceling process module at one side finds that the receiving and monitoring port of the account opening and canceling process module at the other side is not monitoring, the receiving and monitoring port of the account opening and canceling process module is automatically opened. When the method is realized, the following method can be adopted:
and timing a backup account canceling process module, such as: and 3 minutes, sending a hypertext transfer protocol (HTTP) heartbeat request message to the main overhead account process module, and sending an HTTP heartbeat response message after the main overhead account process module receives the HTTP heartbeat request message. If the receiving and monitoring port of the standby overhead account process module is closed and continues for n times, n is a positive integer and can be set to 3, and the standby overhead account process module does not receive the HTTP heartbeat response message of the main overhead account process module, the standby overhead account process module determines that the main overhead account process module has a fault, and the standby overhead account process module opens the receiving and monitoring port of the standby overhead account process module. Wherein, whether the receiving listening port is closed or not can be determined by the corresponding identification.
In the invention, the receiving and monitoring port of the main overhead and sales process module defaults to an open state, and when the overhead and sales process module is started, the receiving and monitoring port defaults to a closed state. Besides, the configuration of the receiving and monitoring port of the backup overhead account process module is the same as that of the receiving and monitoring port of the main overhead account process module.
Step 103: after the main overhead account process module returns to normal, the standby overhead account process module synchronizes data in the local database to the main overhead account process module;
the method specifically comprises the following steps: if the receiving monitoring port of the standby overhead account process module is in an open state and a heartbeat response message sent by the main overhead account process module is received, determining that the main overhead account process module is recovered to be normal; and the standby accounting process module exports 4 main tables in a sybase database in the standby computer room ENUM-DNS server to a fixed directory to generate a binary file, and transmits the binary file to the fixed directory of the main accounting process module through the FTP.
Step 104: the main overhead account process module executes data synchronization operation and then replaces the standby overhead account process module to work.
In the present invention, the flow of the data synchronization operation in step 102 and step 104 is shown in fig. 2, and includes the following steps:
step 201: the accounting process module reads a binary file under a self fixed directory and acquires a zone serial number in another accounting process module sybase database;
here, if the reading fails, the current data synchronization operation is ended, i.e., step 205 is performed.
Step 202: the overhead account process module queries a zone serial number in a self sybase database;
here, if the query fails, the current data synchronization operation is ended, i.e., step 205 is performed.
Step 203: comparing the zone serial number of the account opening process module with the zone serial number of another account opening process module, and if the zone serial number of the account opening process module is larger than or equal to the zone serial number of another account opening process module, executing step 205; otherwise, go to step 204;
here, if the zone serial number of the present overhead process module is greater than or equal to the zone serial number of the other overhead process module, it indicates that the overhead message in the present overhead process module is the latest, that is, is newer than the overhead message in the other overhead process module; otherwise, the account opening and canceling message in the account opening and canceling process module needs to be updated.
Step 204: the invoicing process module imports the backup file in another invoicing process module sybase database under the fixed directory into the local sybase database, and then executes the step 205;
here, the backup file may be a backup file of 4 main tables.
Step 205: the data synchronization operation ends.
In the above flow, the accounting process module is: a main overhead account process module or a standby overhead account process module; in step 102, the accounting process module is a standby accounting process module, and in step 104, the accounting process module is a main accounting process module.
The process of the present invention is described in further detail below with reference to specific examples.
Fig. 3 is a schematic flowchart of a method when a master overhead account process module fails according to an embodiment of the present invention, and as shown in fig. 3, the implementation steps of the flow are as follows:
step 301: the standby overhead account process module sends HTTP heartbeat request information to the main overhead account process module;
step 302: if the standby account canceling process module receives that the monitoring port is closed and does not receive the heartbeat response message for 3 times continuously, the main account canceling process module is confirmed to be in fault;
step 303: the backup overhead process module executes data synchronization operation;
step 304: after the data synchronization operation of the process module for preparing the account opening and closing is successful, a notification message of loading the file is sent to a self business foreground module;
step 305: the service foreground module sends a response message of loading files to the backup account opening process module;
step 306: if the service foreground returns a response message of successful loading, the backup cancellation account process module informs the self service background module to load the file;
step 307: and the standby account opening and canceling process module receives the response message of the service background module, if the loading is successful, the standby account opening and canceling process module informs the communication agent process module to open the receiving and monitoring port and informs the service foreground module to start, and the standby account opening and canceling process module starts to receive the account opening and canceling message.
In the above process, if there is a failure condition in steps 304 to 307, the backup cancellation account process module sends an alarm message to the alarm module, and the process ends.
Fig. 4 is a schematic flowchart of a method for recovering a failure of a master overhead account process module according to an embodiment of the present invention, and as shown in fig. 4, the implementation steps of the flow are as follows:
step 401: the standby overhead account process module sends HTTP heartbeat request information to the main overhead account process module;
step 402: the standby overhead account process module receives an HTTP heartbeat response message returned by the main overhead account process module, and if a receiving monitoring port of the standby overhead account process module is in an open state, the standby overhead account process module determines that the main overhead account process module has recovered from the fault;
step 403: the backup accounting process module closes a receiving and monitoring port of the local machine;
step 404: the backup account cancellation process module informs the self business foreground module, namely: the standby service foreground module stops using;
step 405: the standby account opening and closing process module informs the main account opening and closing process module that the service foreground module of the main account opening and closing process module stops using and the receiving monitoring port is closed;
step 406: the backup overhead and sales process module exports 4 main tables in a sybase database of the backup overhead and sales process module to a fixed directory, generates a binary file and transmits the binary file to the fixed directory of the main overhead and sales process module through FTP (file transfer protocol);
step 407: the standby overhead account process module informs the main overhead account process module to import the binary file into the sybase database;
step 408: the main overhead account process module executes data synchronization operation;
step 409: a main account opening and canceling process module sends a request message for acquiring a sequence number of a current number formal table (exist _ res) to a standby account opening and canceling process module;
here, the purpose of the main overhead account process module obtaining the current exit _ res sequence number from the standby overhead account process module is as follows: and ensuring that the data in the main overhead account progress module is up to date.
Step 410: the standby account opening and canceling process module sends a response message for acquiring the current exit _ res serial number to the main account opening and canceling process module;
here, if this step is successful, the response message includes an exist _ res sequence number sent by the back-up account cancellation process module.
Step 411: the main account opening and closing process module informs the self business foreground module, namely: the main business foreground module loads data;
step 412: the main service foreground module sends a data loading response message to the main invoicing process module;
step 413: if the main service foreground module successfully loads data, the main opening and canceling process module informs the service background module of itself, namely: loading data by a main service background module;
step 414: the main service background module sends a data loading response message to the main account opening and canceling process module;
step 415: if the main service background module successfully loads the data, the main overhead account process module informs the communication agent process module to open the receiving and monitoring port, informs the main service foreground module to start and prepare to receive the overhead account information.
Here, if step 410 fails, the main overhead account process module sends an alarm to the alarm module and goes to step 411; if either step 413 or step 414 fails, then the current flow ends.
In order to implement the above method, the present invention further provides an ENUM-DNS disaster recovery system in an IMS network, as shown in fig. 5, the system includes a main accounting-opening process module disposed in an ENUM-DNS server of a main room and a standby accounting-opening process module disposed in an ENUM-DNS server of a standby room; wherein,
the main overhead account process module is used for periodically synchronizing data in a local database to the standby overhead account process module; after the self fault is recovered, executing data synchronization operation, and then replacing a spare overhead account process module to work;
the backup overhead account process module is used for executing data synchronization operation when the main overhead account process module fails in the system operation process and then replacing the main overhead account process module to work; and after the main overhead account process module is recovered to be normal, synchronizing the data in the local database to the main overhead account process module.
The backup overhead account process module is also used for determining the fault or recovery of the main overhead account process module through HTTP heartbeat messages between the backup overhead account process module and the main overhead account process module; accordingly, the method can be used for solving the problems that,
and the main overhead account process module is also used for communicating with the standby overhead account process module through HTTP heartbeat messages.
The invention also provides an ENUM-DNS server, which comprises an overhead process module, a data synchronization module and an overhead process module, wherein the overhead process module is used for periodically synchronizing data in a local database to the overhead process module in another ENUM-DNS server; after self-failure recovery, data synchronization operation is performed, and then work is performed instead of an overhead process module in another ENUM-DNS server.
The ENUM-DNS server is also used for communicating with an overhead account process module in another ENUM-DNS server through HTTP heartbeat messages.
The invention also provides an ENUM-DNS server, which comprises an overhead process module, a data synchronization module and a data synchronization module, wherein the overhead process module is used for executing data synchronization operation when an overhead process module in another ENUM-DNS server fails in the system operation process and then replacing the overhead process module in another ENUM-DNS server to work; and after the overhead account process module in the other ENUM-DNS server is recovered to be normal, synchronizing the data in the local database to the overhead account process module in the other ENUM-DNS server.
The ENUM-DNS server is also used for determining the failure or recovery of the overhead process module in the other ENUM-DNS server through HTTP heartbeat messages with the overhead process module in the other ENUM-DNS server.
The above description is only a preferred embodiment of the present invention, and is not intended to limit the scope of the present invention.
Claims (12)
1. A disaster recovery method for telephone number mapping working group ENUM-domain name system DNS in IP multimedia system IMS network is characterized in that the method comprises: the main overhead account process module periodically synchronizes data in a local database to the standby overhead account process module; further comprising:
in the system operation process, when the main overhead account process module fails, the standby overhead account process module executes data synchronization operation and then replaces the main overhead account process module to work;
after the main overhead account process module returns to normal, the standby overhead account process module synchronizes data in the local database to the main overhead account process module; the main overhead account process module executes data synchronization operation and then replaces the standby overhead account process module to work.
2. The ENUM-DNS disaster recovery method in IMS network as claimed in claim 1, wherein the process of said primary revoke account process module periodically synchronizing data in local database to said back-up revoke account process module is:
setting a timing backup script on a machine where a sybase database of an ENUM-DNS server of a main computer room is located, wherein the script regularly backs up data in the sybase database to a fixed directory;
a main overhead account process module reads each zone serial number in a domain name table from a sybase database corresponding to the main overhead account process module regularly and writes the zone serial numbers into a fixed directory binary file of a local machine;
the main accounting process module is provided with a File Transfer Protocol (FTP) script and periodically transmits a fixed directory binary file of the ENUM-DNS server of the main computer room to a fixed directory of the standby accounting process module through the FTP.
3. The ENUM-DNS disaster recovery method in an IMS network according to claim 1, wherein the flow of the data synchronization operation is:
the accounting process module reads a binary file under a self fixed directory and acquires a zone serial number in another accounting process module sybase database;
the overhead account process module queries a zone serial number in a self sybase database;
the accounting process module compares the zone serial number of the accounting process module with the zone serial number of another accounting process module, if the zone serial number of the accounting process module is larger than or equal to the zone serial number of the another accounting process module, the data synchronization operation is ended; otherwise, the overhead account process module leads the backup file in the other overhead account process module sybase database under the fixed directory into the local sybase database;
wherein, the overhead account process module is: a main overhead account process module or a standby overhead account process module.
4. A method for ENUM-DNS disaster recovery in an IMS network according to claim 1, 2 or 3, characterized in that the method further comprises:
and the standby overhead account process module determines the failure or recovery of the main overhead account process module through a hypertext transfer protocol (HTTP) heartbeat message between the standby overhead account process module and the main overhead account process module.
5. The ENUM-DNS disaster recovery method in an IMS network according to claim 4, wherein the method for determining that the main overhead account process module has a failure by the backup overhead account process module is:
the standby account opening and canceling process module sends HTTP heartbeat request information to the main account opening and canceling process module at regular time, if the receiving and monitoring port of the standby account opening and canceling process module is closed and HTTP heartbeat response information of the main account opening and canceling process module is not received for n times continuously, the standby account opening and canceling process module determines that the main account opening and canceling process module breaks down; wherein n is a positive integer.
6. The ENUM-DNS disaster recovery method in IMS network according to claim 4, wherein the method for determining the failure recovery of the primary cancellation account process module by the backup cancellation account process module is:
and the standby account opening process module sends HTTP heartbeat request messages to the main account opening process module at regular time, and if the standby account opening process module receives HTTP heartbeat response messages returned by the main account opening process module and a receiving monitoring port of the standby account opening process module is in an open state, the standby account opening process module determines that the main account opening process module has recovered from faults.
7. An ENUM-DNS disaster recovery system in an IMS network, the system comprising: a main overhead account process module and a standby overhead account process module; wherein,
the main overhead account process module is used for periodically synchronizing data in a local database to the standby overhead account process module; after the self fault is recovered, executing data synchronization operation, and then replacing a spare overhead account process module to work;
the backup overhead account process module is used for executing data synchronization operation when the main overhead account process module fails in the system operation process and then replacing the main overhead account process module to work; and after the main overhead account process module is recovered to be normal, synchronizing the data in the local database to the main overhead account process module.
8. The ENUM-DNS disaster recovery system in an IMS network as claimed in claim 7, wherein said backlog-offset-account process module is further configured to determine failure or recovery of the main offset-account process module through HTTP heartbeat message with the main offset-account process module; accordingly, the method can be used for solving the problems that,
and the main overhead account process module is also used for communicating with the standby overhead account process module through HTTP heartbeat messages.
9. An ENUM-DNS server comprising an overhead process module for periodically synchronizing data in a local database to an overhead process module in another ENUM-DNS server; after self-failure recovery, data synchronization operation is performed, and then work is performed instead of an overhead process module in another ENUM-DNS server.
10. The ENUM-DNS server of claim 9, wherein the ENUM-DNS server is further configured to communicate with an overhead process module in another ENUM-DNS server via HTTP heartbeat messages.
11. An ENUM-DNS server is characterized by comprising an overhead process module, a data synchronization operation module and a data synchronization module, wherein the overhead process module is used for performing data synchronization operation when an overhead process module in another ENUM-DNS server fails in the system operation process and then replacing the overhead process module in another ENUM-DNS server to work; and after the overhead account process module in the other ENUM-DNS server is recovered to be normal, synchronizing the data in the local database to the overhead account process module in the other ENUM-DNS server.
12. The ENUM-DNS server of claim 11, wherein the ENUM-DNS server is further configured to determine a failure or recovery of an invoicing process module in another ENUM-DNS server via an HTTP heartbeat message with an invoicing process module in another ENUM-DNS server.
Priority Applications (4)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201210321499.7A CN103684813B (en) | 2012-09-03 | 2012-09-03 | ENUM-DNS disaster recovery methods and system in a kind of IMS network |
| PCT/CN2013/081759 WO2014032532A1 (en) | 2012-09-03 | 2013-08-19 | Enum-dns disaster recovery method and system in ims network |
| IN2698DEN2015 IN2015DN02698A (en) | 2012-09-03 | 2013-08-19 | |
| EP13832793.7A EP2887592A4 (en) | 2012-09-03 | 2013-08-19 | Enum-dns disaster recovery method and system in ims network |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201210321499.7A CN103684813B (en) | 2012-09-03 | 2012-09-03 | ENUM-DNS disaster recovery methods and system in a kind of IMS network |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN103684813A true CN103684813A (en) | 2014-03-26 |
| CN103684813B CN103684813B (en) | 2018-05-01 |
Family
ID=50182485
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201210321499.7A Active CN103684813B (en) | 2012-09-03 | 2012-09-03 | ENUM-DNS disaster recovery methods and system in a kind of IMS network |
Country Status (4)
| Country | Link |
|---|---|
| EP (1) | EP2887592A4 (en) |
| CN (1) | CN103684813B (en) |
| IN (1) | IN2015DN02698A (en) |
| WO (1) | WO2014032532A1 (en) |
Cited By (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN110149241A (en) * | 2019-04-09 | 2019-08-20 | 广州市高科通信技术股份有限公司 | A kind of automated testing method and storage medium based on IMS equipment |
| CN111756937A (en) * | 2020-05-07 | 2020-10-09 | 国网山东省电力公司信息通信公司 | A system and method for IMS dispatching and commanding seats in a power supply service center |
| CN111756936A (en) * | 2020-05-06 | 2020-10-09 | 国网山东省电力公司信息通信公司 | Disaster recovery device and method for dispatching command seat based on IMS |
Families Citing this family (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN108536809A (en) * | 2018-03-30 | 2018-09-14 | 四川九阵科技股份有限公司 | A kind of area medical suspension toll collection system and method |
| CN109600430A (en) * | 2018-11-29 | 2019-04-09 | 深圳市网心科技有限公司 | A kind of data managing method, system and electronic equipment and storage medium |
Family Cites Families (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US7680876B1 (en) * | 2006-12-14 | 2010-03-16 | Cisco Technology, Inc. | Highly available domain name system |
| CN101605068A (en) * | 2009-06-15 | 2009-12-16 | 上海及第熊软件科技有限公司 | A kind of method and system of realizing website falsification-proof |
| CN101729290A (en) * | 2009-11-04 | 2010-06-09 | 中兴通讯股份有限公司 | Method and device for realizing business system protection |
| CN102123180A (en) * | 2010-01-08 | 2011-07-13 | 北京中企开源信息技术有限公司 | DNS (Domain Name Server) network structure and domain name resolution method |
| CN101815285B (en) * | 2010-04-12 | 2014-09-10 | 中兴通讯股份有限公司 | Data synchronization method and data synchronization system in internet mobile number application |
-
2012
- 2012-09-03 CN CN201210321499.7A patent/CN103684813B/en active Active
-
2013
- 2013-08-19 EP EP13832793.7A patent/EP2887592A4/en not_active Withdrawn
- 2013-08-19 WO PCT/CN2013/081759 patent/WO2014032532A1/en not_active Ceased
- 2013-08-19 IN IN2698DEN2015 patent/IN2015DN02698A/en unknown
Cited By (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN110149241A (en) * | 2019-04-09 | 2019-08-20 | 广州市高科通信技术股份有限公司 | A kind of automated testing method and storage medium based on IMS equipment |
| CN110149241B (en) * | 2019-04-09 | 2021-08-24 | 广州市高科通信技术股份有限公司 | Automatic testing method based on IMS equipment and storage medium |
| CN111756936A (en) * | 2020-05-06 | 2020-10-09 | 国网山东省电力公司信息通信公司 | Disaster recovery device and method for dispatching command seat based on IMS |
| CN111756936B (en) * | 2020-05-06 | 2021-05-28 | 国网山东省电力公司信息通信公司 | Disaster recovery device and method for dispatching command seat based on IMS |
| CN111756937A (en) * | 2020-05-07 | 2020-10-09 | 国网山东省电力公司信息通信公司 | A system and method for IMS dispatching and commanding seats in a power supply service center |
| CN111756937B (en) * | 2020-05-07 | 2021-05-28 | 国网山东省电力公司信息通信公司 | A system and method for IMS dispatching and commanding seats in a power supply service center |
Also Published As
| Publication number | Publication date |
|---|---|
| CN103684813B (en) | 2018-05-01 |
| IN2015DN02698A (en) | 2015-09-04 |
| WO2014032532A1 (en) | 2014-03-06 |
| EP2887592A1 (en) | 2015-06-24 |
| EP2887592A4 (en) | 2015-08-26 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN107291787B (en) | Active-standby database switching method and device | |
| CN112506702B (en) | Disaster recovery method, device, equipment and storage medium for data center | |
| CN103684813B (en) | ENUM-DNS disaster recovery methods and system in a kind of IMS network | |
| CN110032478B (en) | Method, device and system for real-time synchronization of data of main and standby centers and storage medium | |
| CN102176775A (en) | Intelligent configuration device and method | |
| CN102609479A (en) | Memory database node copying method | |
| US20170318483A1 (en) | Self-recovery method and device after disconnection of base station | |
| CN110502326A (en) | Cloud service scheduling and recovering method based on fault detection and terminal equipment | |
| WO2010028529A1 (en) | A method and device for maintaining a changelog in data synchronization | |
| CN110677282A (en) | Hot backup method of distributed system and distributed system | |
| CN100426751C (en) | Method for ensuring accordant configuration information in cluster system | |
| CN102006179B (en) | Methods and devices for data backup and data backspacing | |
| WO2005046120A1 (en) | A method for data redundancy of hlr | |
| CN100421390C (en) | Client service emergency system and its realizing method | |
| CN111352995A (en) | Server service method, system, device and storage medium based on database Neo4j | |
| CN102437921B (en) | Memory method and network device of configuration information | |
| CN115473766B (en) | Vip implementation method and system based on distributed gateway | |
| CN108009045B (en) | A method and device for handling faults of primary and secondary databases | |
| CN112052127A (en) | Data synchronization method and device for dual-computer hot standby environment | |
| CN109274532B (en) | Method, device and system for issuing policy, centralized control equipment and readable storage medium | |
| CN113114800B (en) | Resource processing method and device | |
| CN101674568B (en) | Integrated service management platform and service subscription method thereof | |
| CN101150545A (en) | A data distribution method under multi-module data configuration of media gateway | |
| CN106453581B (en) | Method for accessing social platform address book based on enterprise ERP system | |
| CN112491633A (en) | Fault recovery method, system and related components of multi-node cluster |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| C10 | Entry into substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |