WO2012075733A1

WO2012075733A1 - Voice type service system and method for realizing disaster tolerance

Info

Publication number: WO2012075733A1
Application number: PCT/CN2011/071190
Authority: WO
Inventors: 刘欣璇; 陈虹桥
Original assignee: 中兴通讯股份有限公司
Priority date: 2010-12-09
Filing date: 2011-02-23
Publication date: 2012-06-14
Also published as: CN102026249B; CN102026249A

Abstract

The present invention discloses a voice type service system, which includes: a management node, a calling node and a backup node; the management node is responsible for service acceptance and is locally positioned; the backup node is remotely positioned for accepting real-time data synchronization from the management node and when the management node is shutdown, the backup node replaces the management node to implement the function; the calling node is responsible for service call processing, is divided into two parts to be positioned, wherein one part is locally positioned, another part is remotely positioned, and each part can implement the function of the calling node independently; when the locally positioned part is shutdown, the remotely positioned part implements the function of the calling node. The present invention accordingly discloses a disaster tolerance method for the voice type service system. Under any execrable disasters, the voice type service system can ensure that the data is not lost and normal operation is resumed in a shorter time by using the solutions of the present invention.

Description

Voice type business system and disaster tolerance realization method

The invention belongs to the field of communication technologies, and relates to a database disaster recovery backup technology, in particular to a method for implementing disaster tolerance of a voice service system and a voice service system using the method. Background technique

As an intelligent service, Coloring Ring Back Tone (CRBT) has developed rapidly in recent years and has stabilized, which has brought huge economic benefits to operators. However, due to the recent disasters around the world, the reliability and stability of business systems have been seriously affected. In severe cases, core business data is lost, and the system cannot recover quickly after the system. This causes huge losses to the operators and adversely affects the user experience.

In addition to the CRBT service, other voice services face the same problem.

The existing disaster recovery backup scheme for the voice service system has the following disadvantages:

1) Existing voice service systems generally use HP/IBM's two-machine system. Once a fault occurs, the two-machine system will automatically switch. If there is a disaster such as an earthquake or a flood, the two-machine system will become unreliable.

2) The existing voice service system backups the core data of the service. Generally, the voice service system performs daily backup of the database. The backup of the data is not real-time. If a disaster occurs, it may be lost for one to two days. Business data. Summary of the invention

The technical problem to be solved by the present invention is: for the defects existing in the prior art, a disaster recovery implementation method for a voice service system, and a voice service system using the method are proposed to implement voice more effectively. Disaster recovery backup of the business system. In order to solve the above problems, the technical solution of the present invention is implemented as follows:

A method for implementing disaster tolerance in a voice service system includes the following steps:

Setting a backup node in a different place, the backup node accepts data synchronization of the management node of the voice service system;

When the local management node fails, the backup node takes over the management node and performs the function of the management node.

Also includes the steps:

The call node of the voice service system is divided into two parts, one part is set locally, and the other part is set in the different place, each part can perform the function of the call node by itself; when the local part is faulty, The portion placed in the off-site performs the function of the call node.

The data synchronization is real-time data synchronization.

Also includes the steps:

The voice type service system is monitored and an alarm is issued when it fails.

A voice-based service system includes a management node, a call node, and a backup node; wherein the management node is placed locally and is used for service acceptance;

The call node is configured to be responsible for service call processing;

The backup node is placed off-site for accepting data synchronization of the management node, and when the management node fails, it performs its function.

The call node is divided into two parts, one part is placed locally, and the other part is placed in the different place, and each part can perform the function of the call node by itself;

When a portion placed locally fails, the portion placed in the remote location is used to perform the function of the calling node.

In any part of the call node, each database stores all voice-type service call related data, and each service control point of the part is associated with each database of the part Even.

The management node and the call node use a separate physical architecture.

The data synchronization is real-time data synchronization.

The method further includes an alarm module, configured to monitor the management node and the call node, and issue an alarm when a fault is detected.

The beneficial effects of the invention are:

The invention adopts a voice-based business system disaster recovery scheme for real-time backup in different places, and divides the call node into two parts, one part is placed locally with the management node, and the other part is placed in a different place together with the backup node, so that even if it is serious The disaster, if the local voice-based business system is completely lost, can still realize the function of the voice-based business system through the backup node and the call node in different places, and realize real-time data backup, so as to have a good disaster tolerance effect.

With the disaster recovery solution of the present invention, the voice service system can resume normal operation in a short period of time under any severe disaster. It improves the quality of service for operators while reducing the economic loss in the event of a disaster. DRAWINGS

1 is a schematic flow chart of the method of the present invention in a specific embodiment;

2 is a network diagram of a system of the present invention according to a specific embodiment;

3 is a basic flowchart of service data synchronization in an embodiment of the present invention;

4 is a basic flowchart of processing a voice file according to an embodiment of the present invention;

FIG. 5 is a basic flowchart of alarm processing in an embodiment of the present invention;

6 is a networking diagram of a disaster recovery scenario 1 according to an embodiment of the present invention;

FIG. 7 is a networking diagram of a disaster recovery scenario 2 according to an embodiment of the present invention;

FIG. 8 is a networking diagram of a disaster recovery scenario 3 according to an embodiment of the present invention. detailed description

The present invention will be further described in detail below in conjunction with the drawings and specific embodiments.

The present invention will be described below by taking the CRBT service as an example.

1 is a schematic flowchart of a method of the present invention in a specific embodiment. As shown in the figure, the method for implementing disaster recovery of a voice service system of the present invention specifically includes the following steps:

1. Set up a backup node in a different place (for example, in another city or region). The backup node accepts real-time data synchronization of the management node of the voice service system. When the local management node is down (that is, when a failure occurs and cannot be continued), the backup node can take over the management node and perform the function of the management node.

2. The call node of the voice service system is divided into two parts, one part is set locally with the management node, and the other part is set in different places together with the backup node, and each part can perform the function of the call node by itself, that is, each part can Responsible for voice service call processing alone. When the local part is dropped, the function of the calling node can be performed by the part placed in the remote place.

In any of the two parts above the call node, each database (DB) stores all of the voice-type service call related data, and each service control point (CP) is connected to each database of the part at the same time.

3. Monitor the voice service system and issue an alarm in time when it fails.

2 is a network diagram of the system of the present invention in a specific embodiment. As shown in the figure, the voice service system of the present invention includes a management node, a call node, and a backup node, and the management node and the backup node are set in different regions or cities, and the call is made. The node is divided into two parts, one part is located in the same place as the management node, and the other part is in the same place as the backup node. Each part can complete the function of the calling node by itself, that is, it is responsible for the call processing of the voice type service. The management node is separated from the call node implementation function, and correspondingly physically separate structures are also used, that is, two independent physical entities are formed. In Figure 2, the MML (Man-Machine Language) interface refers to the human-machine access interface; the RTP is called the Real-time Transport Protocol, which is the real-time transport protocol; The SIP is called the Session Initiation Protocol, which is the session initiation protocol.

The management node is mainly responsible for business acceptance and synchronization of data to each call node. The business acceptance includes ring tone uploading, modification and deletion, user account opening, account cancellation, user ordering, deleting ring tone (group), user addition, modification, deletion setting, and user inquiry. The management node contains devices, including SMP (service management point), SCP (Service Control Point), web (Internet) server, IMP (integrated interface machine), LanSwith (network switch), BOSS IMP (Interface with BOSS system), SMSC IMP (Interface with Short Message Center), CDR (Charging Data Recording).

The management node and the backup node are connected through the network switch, and the service data is synchronized to the backup node in real time, and the service data needs to be synchronized to the database of the call node.

The calling node includes a CP and a DB, and the CP is connected to a SIU (signal interface unit). The DB accepts the synchronization of the management node and is responsible for the call processing of the user. Each DB stores all the CRBT call related data. The SIU uses a polling method to distribute call requests to each CP evenly or in a certain proportion. In the embodiment of the present invention, there are a total of five DBs in the calling node, wherein there are three in the local, and there are two in the offsite (that is, where the backup node is set); there are a total of 11 CPs, among which there are local Six, there are five in different places. Regardless of whether it is local or remote, each CP connects to each DB at the same time, so that any DB in the place fails, and the system automatically forwards the call request to the normal device. In the embodiment of the present invention, the data of the management node and the call node is synchronized with Oracle Advanced Replication technology (the advanced replication technology of ORACLE).

The main system architecture of the backup node is the same as that of the management node. It is equivalent to all the devices in the management node have a set at the backup node, and the external interface is the same. Under normal circumstances, most of the devices in the backup node are inactive, but the service database and voice storage device in the backup node are working.

As shown in the thick line in Figure 3, the business data in the management node is automatically synchronized to Backup node and call node. Offsite backup of business data is implemented using the Data guard technology provided by ORACLE.

For the backup of the voice media file, the uploading module of the voice content uploads the voice file to the management node and the backup node at the same time.

As shown in Figure 4, the real-time synchronization process of voice media files is as follows.

The WEB interface is mainly responsible for receiving user input including ringtone name, ringtone price, singer information, and physical sound files. Then, the ring tone information is notified to the ring tone upload interface by using a PDU ( Protocol Data Unit) message, and the 4 bar physical sound file is placed on an FTP (File Transfer Protocol) server.

The ring tone upload interface receives the request from the WEB interface, and then connects to the service database to perform database operations, and adds ring tone information. After the operation of the database is successful, it will connect to the FTP server to obtain the physical sound, and then FTP to the management node and the backup node's voice storage device to save.

In the embodiment of the present invention, the voice service type system of the present invention further includes an alarm module, which is mainly used for detecting data synchronization from the management node to the backup node and data synchronization of the management node to the call node, and monitoring the database status of each node. If a fault occurs, the alarm can be sent to the intelligent network platform, and the alarm can be sent to the network administrator through the short message interface.

FIG. 5 is a basic flowchart of alarm processing in the present invention. As shown in the figure, the alarm monitoring process is responsible for monitoring the management section, the calling node, and the backup node. If a data synchronization exception occurs, an alarm message is sent to the service management point SMP and the short message interface. Service Management Point The SMP receives alarm messages and provides a user interface for administrators to check for alarm messages. The short message interface receives the alarm message and is connected to the SMSC short message center. The SMSC Short Message Center is responsible for sending SMS notifications to the end user.

There are many options for the recovery plan after the disaster.

1. If the devices in the management node, such as DB, WEB, and IMP interface, are faulty, since the general devices are dual-machine, only local switching to the standby can be performed. 2. If the device in the calling node fails, for example, if a certain DB fails, the service data query will be load-sharing by other DBs.

3. When an abnormality occurs in the management node, such as an earthquake, the device is completely paralyzed. After the system performs an alarm, the system needs to manually switch to make the backup node a new management node. The devices that start all the backup nodes include the WEB server and the IMP interface. The equipment and service platform, at the same time, all business acceptance and data synchronization of the call node are switched to the new management node.

The following gives an example of the best recovery scenario based on different disaster scenarios:

Scenario 1: When the local management node and the call node are all destroyed, the network structure after system recovery is shown in Figure 6. The recovery steps in this case include:

1. Manually switch the backup node to a new management node. The devices that start all backup nodes include the WEB server, the IMP interface device, and the service platform.

2. At the same time, all business acceptance and peripheral interfaces SDP (Service Development Platform), WAPGW (Business Gateway), and BSS (Business Support System) / OCS (Online Charging System) Fee system), all point to the new management platform.

3. The data synchronization of the calling node is switched to the new management node. At the same time, the routing of the core network directly points to the calling node in the remote location.

Scenario 2: When the local management node is down, but the call nodes are all normal, the network structure after the system is restored is as shown in Figure 7. The recovery steps in this case include:

2. At the same time, all business acceptance and peripheral interfaces SDP, WAPGW and OCS all point to the new management platform.

3. The data synchronization of the calling node is switched to the new management node.

Scenario 3: When the local management node is normal, but the call node is all down, the system The restored network structure is shown in Figure 8. The recovery steps in this case include:

Route the core network directly to the call node in the remote location. Other parts do not need to be modified. In summary, with the disaster recovery solution designed by the present invention, the voice service system can resume normal operation in a short time under any severe disaster. While providing the quality of service for operators, it also reduces the economic loss in the event of a disaster. The invention can be widely applied to the CRBT service, and can also be applied to other similar voice service systems.

The specific embodiments of the present invention have been described in detail with reference to the embodiments of the present invention. It should be noted that the foregoing description is only specific embodiments of the present invention, and those skilled in the art may Various changes and modifications of the invention are possible without departing from the spirit and scope of the invention. Therefore, it is intended that the present invention cover the modifications and variations of the invention, and the modifications and variations of the invention are intended to be included within the scope of the invention.

Claims

Claim

A method for implementing a disaster tolerance of a voice service system, comprising the steps of: setting a backup node in a different place, and the backup node accepts data synchronization of a management node of a voice service system;

The method according to claim 1 or 2, further comprising the steps of: dividing the call node of the voice service system into two parts, one part is set locally, and the other part is set in the different place, each part is The function of the calling node can be performed by itself; when a local part is faulty, the function of the calling node is performed by a portion placed in the remote location.

3. The method according to claim 1, wherein the data synchronization is real-time data synchronization.

The method according to claim 1 or 2, further comprising the step of: monitoring the voice service system, and issuing an alarm when it fails.

5. A voice-based service system, comprising: a management node, a call node, and a backup node;

Wherein, the management node is placed locally, and is used to be responsible for business acceptance;

The call node is configured to be responsible for service call processing;

The system according to claim 5, wherein the call node is divided into two parts, one part is placed locally, and the other part is placed in the off-site, and each part can perform the function of the call node independently;

When the local part is faulty, the part placed in the off-site is used to perform the call Call the function of the node.

7. The system according to claim 6, wherein in any part of the call node, each database stores all voice-related service call related data, and each service control point of the part is associated with Each database in this section is connected.

8. The system of claim 5, 6 or 7, wherein the management node and the calling node employ a separate physical architecture.

9. System according to claim 5, 6 or 7, characterized in that said data synchronization is real time data synchronization.

10. The system according to claim 5, 6 or 7, further comprising an alarm module for monitoring the management node and the call node, and issuing a report when a failure is detected