WO2006058464A1

WO2006058464A1 - Short message center cluster system and control method thereof

Info

Publication number: WO2006058464A1
Application number: PCT/CN2004/001406
Authority: WO
Inventors: Zhigui Yuan; Shengmei Luo; Shizhong Chen
Original assignee: Zte Corporation
Priority date: 2004-12-02
Filing date: 2004-12-02
Publication date: 2006-06-08
Also published as: CN100571418C; CN101023683A

Abstract

A short message center cluster system, which includes a cluster scheduling center and at least two short message centers; said cluster scheduling center is used for cluster deployment and service scheduling; said short message center includes cluster node server which is the communication connection point of the short message center cluster as well as the access module and service process module; the cluster node server is coupled to other module of the short message center, and is coupled to the cluster scheduling center. The present invention provides a cluster technique among multiple short message centers, wherein all the short message centers form a organic whole by establishing certain negotiatory mechanism among the multiple short message centers, therefore enabling the short message center within the cluster system to backup each other, and enabling the short message to be processed in branch stream within the cluster. In addition , the present invention also provides all the short message centers within the cluster system with disaster tolerance function, which improves the reliability of short message service.

Description

Short message center cluster system and control method thereof

The present invention relates to a short message center in the field of communications, and more particularly to a cluster system in a short message and a control method therefor. Background technique

As the most important value-added service in the telecom industry, short messages are becoming more and more important. Short message centers or similar products are set up in existing CDMA networks, GSM networks and fixed telephone networks. While providing convenient services for the majority of users and bringing lucrative profits to operators, the requirements of all parties for the short message center are becoming more and more strict. The security and robustness of the system have been aligned with the main equipment such as switches. The basic requirement is to ensure the normal operation of the short message center under any circumstances.

At present, the number of short message centers running on existing communication networks has reached several thousand. These short message centers are basically independent of each other. Even if there is a correlation between the two short message centers, they are only a simple combination relationship, which can only play a certain degree of load sharing and disaster recovery backup. Can not meet the current requirements for the security and robustness of the short message center.

In the field of computer server, clustering technology between multiple servers has become very popular. This clustering technology greatly improves the availability of the entire system, such as HACMP (High Avai laby l ity Cluster Mul ti-Processing) on IBM minicomputers. Technology and Microsoft's MSGS (Microsoft Clus ter Service) technology.

Therefore, if a short message center is regarded as a network element of the telecommunication network, then the computer server clustering technology is used to combine a plurality of such network elements into one organic whole, so that the network elements can be Backing up each other and sharing services with each other is very meaningful for improving the reliability of the short message service of the telecommunication network. Summary of the invention

The present invention has been made in view of the above technical problems in the prior art, and an object thereof is to provide a short message center cluster system and a control method thereof, and a plurality of short message centers are formed to form one Machine complex to improve the reliability of short message services.

According to an aspect of the present invention, a short message center cluster system is provided, comprising: a cluster scheduling center for performing cluster configuration and service scheduling;

At least two short message centers, each of which includes an access node and a service processing module, and a cluster node server, wherein the short message center is used to form a clustered communication connection, and the short message is The other modules of the center are connected to the cluster dispatch center.

According to another aspect of the present invention, a method for controlling a short message center cluster system is provided, including: setting a short message receiving and sending route of each short message center is the same; monitoring a short message center working condition; if a short message center If an abnormal situation occurs, the short message is allocated to other short message center processing in the cluster system according to the scheduling of the cluster scheduling center.

Preferably, before the step of monitoring the working condition, the method further includes: configuring the service data of each short message center in the cluster scheduling center, including the user number segment, the traffic indicating busy condition, the traffic distribution policy, and the disaster recovery policy.

Preferably, if the abnormal situation is that the traffic load of the short message center reaches the load upper limit, the step of allocating the short message to other short message center processing in the cluster system according to the scheduling of the cluster scheduling center further comprises: the short message to be overflowed Submitted to the cluster dispatch center; the cluster dispatch center allocates the received short message to the corresponding short message center according to the busy state of the short message center and the offload policy.

Preferably, if the abnormal situation is that the traffic load of the short message center reaches the load upper limit, the step of allocating the short message to other short message center processing in the cluster system according to the scheduling of the cluster scheduling center further comprises: the short message to be overflowed The cluster node server submitted to the short message center; the cluster dispatch center determines the short message center that receives the short messages according to the busy state and the offload policy of the short message center; the cluster node server sends the short message to the corresponding short message Central cluster node server.

Preferably, if the abnormal situation is that the non-access module of the short message center fails, the step of allocating the short message to other short message center processing in the cluster system according to the scheduling of the cluster scheduling center further comprises: directly sending the short message Submitted to the cluster dispatch center; the cluster dispatch center assigns short messages to the corresponding short message center according to the disaster recovery policy. Preferably, if the abnormal situation is that the non-access module of the short message center fails, the step of allocating the short message to other short message center processing in the cluster system according to the scheduling of the cluster scheduling center further comprises: The message is submitted to the cluster node server of the short message center; the cluster dispatch center determines the short message center that receives the short messages according to the disaster tolerance policy; the cluster node server sends the short message to the cluster node server of the corresponding short message center .

Preferably, if the abnormal situation is a system-level fault in the short message center, the step of allocating the short message to other short message center processing in the cluster system according to the scheduling of the cluster scheduling center further comprises: sending from the external network to the short All short messages in the message center are submitted to the corresponding short message center according to the disaster recovery strategy.

Preferably, if the system-level fault is that a certain type of access module of the short message center fails, the step of allocating the short message to other short message center processing in the cluster system according to the scheduling of the cluster scheduling center further includes: All the short messages of the short message center are sent to the other short message centers according to the disaster recovery policy. The short messages of the short message center are sent to the network corresponding to other types of access modules. Normal processing is performed. If the terminating call of the short message is the network corresponding to the faulty access module, the short message is processed and sent to the other normal short message center for terminal call processing through the cluster scheduling center.

As can be seen from the above, the present invention provides a clustering technology between a plurality of short message centers. By establishing a certain negotiation mechanism between a plurality of short message centers, an organic whole is formed, so that short message centers in the cluster system can mutually ^ , short messages can be offloaded within the cluster; each short message center in the cluster system achieves multi-directional shunting, on the one hand to protect the short message center can withstand the impact of large traffic, on the other hand, fully utilize the network resources . In addition, the present invention also enables the short message centers in the cluster system to have a multi-directional disaster recovery function, thereby improving the reliability of the short message service. DRAWINGS

1 is a schematic structural diagram of a short message center cluster system according to an embodiment of the present invention;

2 is a control method of a short message center cluster system according to an embodiment of the present invention. Flow chart

3 is a schematic flowchart of a normal operation of a short message center in the embodiment shown in FIG. 2. FIG. 4 is a schematic diagram of a service flow when a short message center in the embodiment shown in FIG. 2 is overloaded; FIG. 5 is a schematic diagram of the embodiment shown in FIG. Schematic diagram of the business process when the non-access module of the short-message center fails;

6 is a schematic diagram of a service flow when a signaling access module of a short message center fails in the embodiment shown in FIG. 2;

FIG. 7 is a schematic diagram of the service flow when the ESME access module of the short message center fails in the embodiment shown in FIG. 2. detailed description

The technical solution of the present invention will be further described in detail below with reference to the accompanying drawings and embodiments. BRIEF DESCRIPTION OF THE DRAWINGS Figure 1 is a block diagram showing the structure of a short message center cluster system including a cluster dispatch center 101 and N short message centers in accordance with one embodiment of the present invention. The cluster dispatch center 101 is used to provide cluster configuration and service scheduling management functions for the entire system, and each short message center includes a cluster node server 102 in addition to the access module and the business processing module. The cluster node server 102 in each short message center is a communication connection point of the short message center to form a cluster, and is connected to the cluster scheduling center 101, and is respectively connected with other modules in the short message center. The cluster node server 102 communicates with the cluster dispatch center 101 and other modules of the short message center via TCP/IP. As can be seen from the above, the cluster scheduling center 101 is the control part of the entire cluster system, and the cluster node server 102 implements the cluster networking of the short message center.

The access module of the short message center is connected to the external network. The external network includes the telecommunication network and an external short message entity (ESME) network. Accordingly, the access modules in the short message center can be divided into signaling interfaces. Incoming modules and ESME access modules.

In addition, the cluster system may further include a console 103, which is connected to the cluster dispatch center 101 via TCP/IP, and is configured to provide a necessary human-machine management interface to configure the cluster system and issue operation instructions to the cluster dispatch center 101.

The cluster node server 102 should periodically report the short message center to the cluster scheduling center 101. The busy condition, so that the cluster dispatch center 101 can reasonably divide the business.

In the cluster scheduling center 101, the traffic conditions of the short message center, the traffic distribution policy, and the disaster recovery policy can be set in advance. The traffic indication busy condition is an upper limit occupied by the system key resources (such as CPU and memory) that informs the cluster scheduling center 101 that the short message center is busy. After the busy state, the cluster scheduling center 101 no longer allocates short messages to other short message centers. Short message center, avoid overloading the short message center. The splitting policy refers to the proportion of short messages that are overflowed to other short message centers when a traffic load reaches the upper limit of the load in a short message center, for example, in a short message center consisting of four, A, B, C, and D. In the cluster system, the short message traffic overflowed by the A short message center is divided into three short message centers of B, C, and D according to 1:2:3. The disaster recovery policy refers to the proportion of short messages sent by the short message center to other short message centers when the short message center fails. For example, in the above example, when the A short message center fails, it belongs to A short. The short message traffic of the message center is allocated to three short message centers of B, C, and D according to 1:2:3.

Further, in order to reduce the performance requirements of the cluster scheduling center 101, the cluster node servers 102 of all the short message centers may be directly connected to each other, so that the shunt short message and the disaster recovery short message may be directly connected to the cluster of the original short message center. The point server 102 sends to the cluster node server 102 of the corresponding short message center without going through the cluster dispatch center 101. At this point, the cluster scheduling center 101 is only responsible for scheduling the cluster system without passing short messages.

As can be seen from the above description, with this embodiment, a certain negotiation mechanism can be established between multiple short message centers, so that short message centers in the cluster system can mutually short messages can be offloaded in the cluster.

Figure 2 illustrates a control method for a short message center cluster system in accordance with one embodiment of the present invention. As shown in FIG. 2, in step 201, the short message receiving and sending routes of each short message center are set to be the same. In each cluster node short message center, for the short message of the external network, set the short message incoming (that is, the telecommunication network or ESME submits the short message process to the short message center) and the outgoing (that is, the short message center delivers the short message to the telecommunication network or ESME) The routing of the message process is the same, for example, the user route of all the number segments of the set system points to the short message center. To facilitate the management of the short message center, you can also assign a cluster node ID to each short message center.

In the cluster scheduling center, in order to achieve effective scheduling management, for each short message center The service data is included, including the user number segment, the traffic indication busy condition, the traffic distribution policy, and the disaster recovery policy. In step 205, the cluster scheduling center monitors the working status of the short message center, and takes corresponding measures according to the current situation of the short message center to ensure the normal implementation of the service.

When the short message center works normally, its business process is shown in Figure 3. For convenience of description, in the present embodiment, the short message cluster system is composed of two short message centers A and B clusters. At this time, the short message processing of the short message center is only related to the access module and the service processing module. Take the short message center A as an example. The specific processing flow is as follows:

The short message from the telecommunication network is submitted to the signaling access module A 204 via the interface 2 A, and the signaling access module A 204 submits the short message to the service processing module A 203 via the interface 2B. If the short message is sent to the telecommunications network subscriber, the service processing module A 203 delivers the short message to the signalling access module A 204 via the interface 2B, and the signaling access module A 204 sends the short message to the telecommunications network via the interface 2A. If the short message is sent to the ESME user, the service processing module A 203 posts the short message to the ESME access module A 205 via the interface 2C, and then the ESME access module A 205 posts the short message to the ESME network via the interface 2D.

Similarly, the short message from the ESME network is submitted to the ESME access module A 205 via the interface 2D, and the ESME access module A 205 submits the short message to the service processing module A 203 via the interface 2C. If the short message is sent to the telecommunications network user, the service processing module A 203 delivers the short message to the signaling access module A 204 via the interface 2B, and the signaling access module A 204 delivers the short message to the telecommunication network via the interface 2A. If the short message is sent to the ESME user, the service processing module A 203 posts the short message to the ESME access module A 205 via the interface 2C, and then the ESME access module A 205 posts the short message to the ESME network via the interface 2D.

In step 210, if an abnormal situation occurs in the short message center, the short message is allocated to other short message center processing in the cluster system according to the scheduling of the cluster scheduling center.

In the cluster system, the service processing module of each short message center periodically reports the load situation and the fault condition to the access module and the cluster node server of the short message center. The abnormal situation occurs in the short message center, including the following: The service load of the short message center reaches the upper limit of the load; the non-access module of the short message center fails; the system level fault occurs in the short message center. When the above abnormal situation occurs, the cluster scheduling center processes the short message according to the corresponding policy. Figure 4 to Figure 7 shows the flow chart of short message processing in the above several abnormal situations, the following - for explanation. For ease of illustration, the embodiment still employs a short message clustering system consisting of two short message centers A and B.

When the access module learns that the load of the service processing module is higher than the predetermined load limit, the associated short message center starts the offload processing. The short message center submits the overflowed short message to the cluster scheduling center; the cluster scheduling center allocates the overflowed short message to the corresponding short message center according to the busy condition and the offloading policy of each short message center. When the load of the business processing module is 1⁄4^ at the predetermined load limit, the shunt is stopped. The cluster node server of the short message center periodically reports the load status of the short message center to the cluster dispatch center, and the cluster dispatch center implements the traffic split policy reference. Preferably, the busy state of the short message center is timed by the cluster node server of the short message center to the cluster scheduling center.

4 is a schematic diagram of the short message splitting in the above case, and the specific process is as follows: The short message from the telecommunication network is submitted to the signaling access module A 204 through the interface 2A, and the signaling access module A 204 determines the service processing module A. If the load of 203 has reached the predetermined load limit, the signaling access module A 204 sends the overflowed short message directly to the cluster node server A 102 through the interface 2E. The cluster node server A 102 sends the overflowed short message to the cluster dispatch center 101 through the interface 2H, and then the cluster dispatch center 101 sends the overflowed short message to the cluster node server of the short message center B through the interface 21 according to the offload policy. B 202. The cluster node server B 202 sends a short message to the service processing module B 207 via the interface 2K. If the overflowed short message is sent to the telecommunication network user, the service processing module B 207 terminates the short message to the signaling access module B 209 through the interface 2P, and then the signaling access module B 209 terminates to the telecommunication network through the interface 2R. Call short message. If the overflowed short message is sent to the ESME user, the service processing module B 207 terminates the short message to the ESME access module B 208 through the interface 2N, and then the ESME access module B 208 terminates the short message to the ESME network through the interface 2Q. .

Similarly, the short message from the ESME network is submitted to the ESME access module A 205 through the interface 2D, and the ESME access module A 205 determines that the load of the service processing module A 203 has reached the predetermined load upper limit, and the ESME access module A 204 will overflow. The short message is sent directly to the cluster node server A 102 through the interface 2 G. Cluster Node Server A 102 passes the overflowed short message through the interface 2H is sent to the cluster dispatch center 101, and the cluster dispatch center 101 sends the overflowed short message to the cluster node server B 202 of the short message center B through the interface 21 according to the offload policy. The cluster node server B 202 sends a short message to the service processing module B 207 via the interface 21. If the overflowed short message is sent to the telecommunication network user, the service processing module B 207 terminates the short message to the signaling access module B 209 through the interface 2P, and then the signaling access module B 209 terminates the call to the telecommunication network through the interface 2R. short message. If the overflowed short message is sent to the ESME user, the service processing module B 207 terminates the short message to the ESME access module B 208 through the interface 2N, and then the ESME access module B 208 terminates the short message to the ESME network through the interface 2Q. .

According to the above description, when the load of the short message center exceeds the upper limit, the shunting process can relieve the pressure of the overloaded short message center in time, and can timely process the overflow short message, thereby avoiding the backlog or loss of the short message.

When a non-access module in one or more short message centers in the cluster system fails, the short message center receives the short message of the external network, bypasses the fault module, and directly submits the short message to the cluster dispatch center. , assigned by the cluster dispatch center to other short message center processing. Figure 5 shows the service flow diagram when the non-access module fails. The details are as follows:

The short message from the telecommunication network is submitted to the signaling access module A 204 through the interface 2A. When the signaling access module A 204 finds that the service processing module A 203 is faulty, all the short message is directly sent to the cluster node through the interface 2E. Point server A 102. The cluster node server A 102 then sends the short message to the cluster dispatch center 101 via interface 2H. The cluster dispatch center 101 sends the short message to the cluster node server B 202 of the short message center B through the interface 21 according to the disaster recovery policy, and the cluster node server B 202 sends the short message to the service processing module B 207 through the interface 2K. If the short message is sent to the telecommunication network user, the service processing module B 207 terminates the short message to the signaling access module B 209 through the interface 2P, and then the signaling access module B 209 terminates the short message to the telecommunication network through the interface 2R. Message. If the short message is sent to the ESME user, the service processing module B 207 terminates the short message to the ESME access module B 208 through the interface 2N, and then the ESME access module B 208 terminates the short message to the ESME network through the interface 2Q.

The short message from the ESME network is submitted to the ESME access module A 205 through the interface 2D, and the ESME access module A 205 finds that the service processing module A 203 is faulty, and all the short message is sent. It is directly sent to the cluster node server A 102 through the interface 2G. The cluster node server A 102 then sends the short message to the cluster dispatch center 101 via the interface 2H. The cluster dispatch center 101 sends the short message to the cluster node server B 202 of the short message center B through the interface 21 according to the disaster tolerance policy, and the cluster node server B 202 sends the short message to the service processing module B 207 through the interface 2K. If the short message is sent to the telecommunication network user, the service processing module B 207 terminates the short message to the signaling access module B 209 through the interface 2P, and then the signaling access module B 209 terminates the short message to the telecommunication network through the interface 2R. Message. If the short message is sent to the ESME user, the service processing module B 207 terminates the short message to the ESME access module B 208 through the interface 2N, and then the ESME access module B 208 terminates the short message to the ESME network through the interface 2Q.

According to the above description, when the non-access module of the short message center fails, the above processing can be used to ensure the smooth implementation of the short message service.

When a system-level fault occurs in one or more short message centers in the cluster system, all short messages sent to the short message center are submitted to other normal short message centers according to the disaster recovery policy. This operation can be performed through the external network. Routing implementation. The so-called system-level fault refers to the failure of a certain type of access module or all access modules in the short message center.

Figure 6 is a schematic diagram of the service flow when the signaling access module in the short message center fails. The details are as follows:

If the signaling access module A 204 of the short message center A fails, the signaling transfer point of the telecommunication network determines that the route of the short message center A is unreachable, enables the alternate route, and connects the telecommunication network to the short message center. The short message is directly sent to the signaling access module B 209 of the short message center B through the interface 2R. The signaling access module B 209 sends the short message call to the service processing module B 207 through the interface 2P. If the short message is sent to the telecommunication network user, the service processing module B 207 sends the signaling access module B through the interface 2P. 209 delivers the short message, and the signaling access module B 209 delivers the short message to the telecommunication network through the interface 2R. If the short message is sent to the ESME user, the service processing module B 209 delivers the short message to the ESME access module B 208 via the interface 2N, and then the ESME access module B 208 posts the short message to the ESME network via the interface 2Q.

For the short message from the ESME network, it is submitted to the ESME access module A 205 of the short message center A through the interface 2D, and the ESME access module A 205 submits it to the service processing mode through the interface 2C. Block A 203. If the short message is sent to the telecommunication network user, and the service processing module A 203 determines that the signaling access module A 204 is faulty, the short message to the telecommunication network submitted by the ESME access module A 205 is directly sent to the interface 2F. Cluster Node Server A 102. The cluster node server A 102 sends these short messages to the cluster dispatch center 101 through the interface 2H, and the cluster dispatch center 101 sends the short message through the interface 21 to the cluster node server B 202 of the short message center B according to the disaster tolerance policy. The cluster node server B 202 terminates the call directly to the signaling access module B 209 through the interface 2M, and the signaling access module B 209 terminates the call to the telecommunication network through the interface 2R. If the short message is sent to the ESME user, the service processing module A 203 posts the short message to the ESME access module A 205 via the interface 2C, and then the ESME access module A 205 posts the short message to the ESME network via the interface 2D.

Figure 7 shows the service flow of the ESME access module A 205 in the short message center A when it fails. The details are as follows:

If the ESME access module A 205 of the short message center A fails, the ESME determines that the route of the short message center A is unreachable, enables the alternate route, and sends all the short messages of the ESME network to the short message center directly through the interface 2Q. ESME Access Module B 208 of Short Message Center B. The ESME access module B 208 sends the short message call to the service processing module B 207 through the interface 2N. If the short message is sent to the telecommunication network user, the service processing module B 207 passes the interface 2P to the signaling access module. B 209 delivers the short message, and signaling access module B 209 delivers the short message to the telecommunications network via interface 2R. If the short message is sent to the ESME user, the service processing module B 209 delivers the short message to the ESME access module B 208 via the interface 2N, and then the ESME access module B 208 posts the short message to the ESME network via the interface 2Q.

For the short message from the telecommunication network, the signaling access module A 204 is submitted to the short message center A through the interface 2A, and the signaling access module A 204 submits it to the service processing module A 203 via the interface 2B. If the short message is sent to the telecommunications network user, the service processing module A 203 delivers the short message to the signaling access module A 204 via the interface 2B, and then the short message is sent by the signaling access module A 204 to the telecommunication network via the interface 2A. . If the short message is sent to the ESME user, the service processing module A 203 determines that the ESME access module A 205 is faulty, and then sends the short message to the ESME network submitted by the signaling access module A 204 to the group directly through the interface 2F. Assembly Point server A 102. The cluster node server A 102 sends these short messages to the cluster dispatch center 101 through the interface 2H, and the cluster dispatch center 101 sends the short message to the cluster node server B 202 of the short message center B through the interface 21 according to the disaster tolerance policy. The cluster node server B 202 terminates the call directly to the ESME access module B 208 through the interface 2J, and the ESME access module B 208 terminates the call to the ESME network through the interface 2Q.

If all the access modules of the short message center A are faulty, all the short messages sent to the short message center are submitted to the corresponding access module of the short message center B through the backup route, and then processed. The processing flow is the processing flow of the short message in the short message center B, and will not be described here.

The above description shows that when a certain type of access module (such as a signaling access module, an ESME access module) or all access modules of a short message center fails, the above process can be used to send short messages to other shorts. The message center guarantees the realization of the short message service.

If the cluster node servers of each short message center in the cluster system are directly connected to each other, each offload short message or disaster tolerant short message can be directly sent by the cluster node server to the cluster node server without going through the cluster dispatch center.

Although the short message center cluster system and the control method thereof of the present invention have been described in detail through the exemplary embodiments, the above embodiments are not exhaustive, and those skilled in the art can implement the spirit and scope of the present invention. Various changes and modifications. Therefore, the invention is not to be construed as being limited by the scope of the appended claims.

Claims

Claim

A short message center cluster system, comprising:

A cluster dispatch center for cluster configuration and service scheduling;

2. The short message center cluster system according to claim 1, wherein the collected dispatch center and the set point server are connected by using a TCP/IP protocol; and the cluster node server and the short message center are Other modules are connected by TCP/IP protocol.

3. The short message center cluster system according to claim 1 or 2, wherein the cluster node servers are directly connected to each other.

4. The short message center cluster system according to claim 1, further comprising a console connected to the cluster dispatch center via a TCP/IP for providing a necessary management interface to perform the cluster system Configure and issue operational instructions to the cluster dispatch center.

A control method for a short message center cluster system, comprising: setting a short message receiving and sending the same route for each short message center; monitoring a working condition of the short message center; if an abnormal situation occurs in the short message center Then, according to the scheduling of the cluster scheduling center, the short message is allocated to other short message center processing in the cluster system.

The control method according to claim 5, wherein the step of setting the short message receiving and transmitting route is the same as directing the user route of all the number segments of the cluster system to the short message center.

The control method according to claim 5, further comprising: configuring the service data of each short message center in the cluster scheduling center, including the user number segment and the traffic indicating busy condition, before performing the monitoring working condition step , traffic distribution policies, and disaster recovery strategies.

8. The control method according to claim 5, wherein the monitoring The working condition of the short message center is completed by periodically reporting the load situation and the fault condition to the access module and the cluster node server of the short message center through the service processing module of each short message center.

9. The control method according to claim 5, further comprising: first assigning a cluster node ID to each short message center.

The control method according to any one of claims 5 to 9, characterized in that, if the abnormal condition is that the traffic load of the short message center reaches the load upper limit, the short message is allocated to the cluster according to the scheduling of the cluster scheduling center. The steps of the other short message center processing in the system further include: submitting the overflowed short message to the cluster scheduling center; the cluster scheduling center assigns the received short message to the corresponding short message according to the busy state of the short message center and the offloading policy. center.

The control method according to any one of claims 5 to 9, characterized in that, if the abnormal situation is that the traffic load of the short message center reaches the load upper limit, the short message is allocated to the cluster according to the scheduling of the cluster scheduling center. The steps of the other short message center processing in the system further include: submitting the overflowed short message to the cluster node server of the short message center; the cluster scheduling center determines, according to the busy state of the short message center and the offloading policy, the short of receiving the short message Message Center; The above cluster node server sends a short message to the cluster node server of the corresponding short message center.

The control method according to claim 10 or 11, wherein the busy condition of the short message center is reported to the cluster scheduling center by the cluster node server of the short message center.

The control method according to any one of claims 5 to 9, wherein if the abnormal condition is that the non-access module of the short message center fails, the short message is allocated according to the scheduling of the cluster scheduling center. The steps of the other short message center processing in the cluster system further include: submitting the short message directly to the cluster scheduling center; the cluster scheduling center allocates the short message to the corresponding short message center according to the disaster tolerance policy.

The control method according to any one of claims 5 to 9, wherein if the abnormal condition is that the non-access module of the short message center fails, the short message is allocated according to the scheduling of the cluster scheduling center. Steps for processing other short message centers in the cluster system The steps include: submitting a short message to a cluster node server of the short message center; the cluster scheduling center determines a short message center that receives the short messages according to the disaster tolerance policy; the cluster node server sends the short message to the corresponding short message center Cluster node server.

The control method according to any one of claims 5 to 9, characterized in that, if the abnormal situation is a system level fault in the short message center, the short message is allocated to the cluster system according to the scheduling of the cluster scheduling center. The processing of the other short message center further includes: all the short messages sent from the external network to the short message center are all submitted to the corresponding short message center according to the disaster recovery strategy.

The control method according to claim 15, wherein the short message sent by the external network to the fault short message center is submitted to the corresponding short message center through the backup route of the external network.

The control method according to claim 15, wherein the system level fault refers to a failure of a certain type of access module or all access modules in the short message center.

The control method according to claim 17, wherein if the system level fault is that a certain type of access module of the short message center fails, the short message is allocated according to the scheduling of the cluster scheduling center. The processing of the other short message center in the cluster system further includes: sending the short message of the short message center of the network corresponding to the access module to the other normal short message center according to the disaster recovery policy; The short message of the short message center is sent to the network corresponding to the module for normal processing. If the terminating call of the short message is the network corresponding to the faulty access module, the short message is processed and sent to the other normal short through the cluster scheduling center. The message center performs terminal call processing.

The control method according to claim 18, wherein the short message sent from the short message center of the short message center is sent to the corresponding short message through the backup route of the network Short message center.