WO2017121284A1 - Service processing method and device - Google Patents

Abstract

This disclosure involves a service processing method and device. The method comprises: when receiving a short message sending request, respectively generating a weight interval corresponding to various short message SPs according to the weights of a plurality of short message SPs used for providing a short message sending service corresponding to the short message sending request, the ratios of the weights to a weight sum corresponding to the ratios of volumes of the short message sending service borne by the SPs; generating a random number in a union set of the weight intervals corresponding to the various SPs, and if the random number is in the weight interval of a short message SP, then determining the short message SP as a target SP; and allocating a short message sending service corresponding to the short message sending request to the target SP. This disclosure enables the change of short message SPs to be more flexible.

Description

Business processing method and device

The present application claims the priority of the Chinese Patent Application Serial No. No. No. No. No. No. No. No.

Technical field

The present disclosure relates to network technologies, and in particular, to a service processing method and apparatus.

Background technique

The short message service provider (SMS) is a service provider that provides profitability for short message mobile phone value-added services under the platform of the telecom operator. It is responsible for developing and providing SMS services suitable for users according to the needs of users. In the related art, the service configuration and the short message SP are strongly associated, that is, the short message sending configuration of a certain service is fixedly processed by an SP. The drawback of this method is that the fixed allocation of services to an SP is not conducive to the change of the SMS SP, and the manual recovery is also required when the abnormal recovery occurs, and the service allocation is not flexible.

Summary of the invention

To overcome the problems in the related art, the present disclosure provides a service processing method and apparatus to implement flexible change of a short message SP.

According to a first aspect of the embodiments of the present disclosure, a service processing method is provided, including:

When receiving the short message sending request, the weight interval corresponding to each short message SP is generated according to the weight of the plurality of short message SPs for providing the short message sending service corresponding to the short message sending request, and the weights correspond to the proportion of the total weight sum The proportion of the traffic volume of the short message sending service undertaken by the SP;

Generating a random number in a union range of weight ranges corresponding to the respective short message SPs, and if the random number is located in a weight interval of a short message SP, determining that the short message SP is a target SP;

And distributing the short message sending service corresponding to the short message sending request to the target SP.

According to a second aspect of the embodiments of the present disclosure, a service processing apparatus is provided, including:

The interval generating module is configured to generate a weight interval corresponding to each short message SP according to a weight of multiple short message SPs for providing a short message sending service corresponding to the short message sending request, when the short message sending request is received, where the weight is occupied The ratio of the total weight sum corresponds to the proportion of the traffic volume of the short message sending service undertaken by the SP;

a random determination module, configured to generate a random number in a union range of weight ranges corresponding to the respective short message SPs, and if the random number is located in a weight interval of a short message SP, determine that the short message SP is a target SP;

The service allocation module is configured to allocate the short message sending service corresponding to the short message sending request to the target SP.

The technical solution provided by the embodiment of the present disclosure may include the following beneficial effects: by setting the weight of the SP, and assigning a service to each SP according to the weight, so that the change of the service allocation between the SPs can be realized by the change of the weight, thereby making the short message SP changes are more flexible.

The above general description and the following detailed description are intended to be illustrative and not restrictive.

DRAWINGS

The accompanying drawings, which are incorporated in the specification of FIG

FIG. 1 is an application system for business processing according to an exemplary embodiment;

FIG. 2 is a flowchart of a service processing method according to an exemplary embodiment;

FIG. 3 is a flowchart of another service processing method according to an exemplary embodiment;

FIG. 4 is a structural diagram of a service processing apparatus according to an exemplary embodiment;

FIG. 5 is a structural diagram of another service processing apparatus according to an exemplary embodiment;

FIG. 6 is a structural diagram of still another service processing apparatus according to an exemplary embodiment.

detailed description

Exemplary embodiments will be described in detail herein, examples of which are illustrated in the accompanying drawings. The following description refers to the same or similar elements in the different figures unless otherwise indicated. The embodiments described in the following exemplary embodiments do not represent all embodiments consistent with the present invention. Instead, they are merely examples of devices and methods consistent with aspects of the invention as detailed in the appended claims.

FIG. 1 illustrates an application system of the service processing method of the present application. As shown in FIG. 1 , the server 11 can receive a short message sending request. For example, a certain business organization needs to send a group short message to send the business organization to a specific group of people. Fixed SMS message. The server 11 may, according to the short message sending request, instruct any SMS SP in the SMS SP cluster 12 to process the service. For example, the short message sending service corresponding to the short message sending request may be allocated to the short message SP13, and the short message SP13 sets the service organization. SMS messages are sent to specific people.

In this example, if the server 11 receives a large number of short message sending requests, the services corresponding to the requests may be allocated to the SPs in the short message SP cluster 12, and the multiple SPs jointly bear the short message sending service. For example, if the server 11 receives 100 pieces of short message sending service and needs to be processed, then 20 of them can be assigned to the short message. The SP13 processes, and 10 of them are allocated to the short message SP14 for processing, and the remaining services are allocated to the short message SP15 for processing. That is, the server 11 is equivalent to a distributed device, and can distribute the request service flow sent by the short message to the plurality of short message SPs.

In an example, the server 11 may perform the offloading of the short message sending service according to the policy configured on the background system 16, and the policy may be the weight of each SP in the short message SP cluster 12, and the weight accounts for the total weight and the proportion corresponding to the SP. The proportion of business volume undertaken by the SMS sending service. For example, suppose there are four SMS SP devices in the SMS SP cluster 12, and the weights of the four devices can be configured by the background system 16 as [SP15: SP13: SP14: SP17] = [10: 20: 10: 30], respectively. The weight ratio can be known, when the server 11 allocates the short message sending service, 1/7 of the traffic is allocated to the SP15, the 2/7 traffic is allocated to the SP13, and the 1/7 traffic is allocated to the SP14, and 3 The traffic of /7 is allocated to SP17, that is, the proportion of services between each short message SP is limited by the weight ratio. In addition, the configured SP weight can be a positive integer.

For one of the short message sending services, the server 11 can send the short message sending service to a certain short message SP according to the flow of the service processing method shown in FIG. 2 . as shown in picture 2:

In step 201, when receiving the short message transmission request, the weight interval corresponding to each short message SP is generated according to the weights of the plurality of short message SPs for providing the short message transmission service corresponding to the short message transmission request.

For example, when receiving the short message transmission request, the server 11 may generate a weight interval corresponding to each short message SP according to the weight of each short message SP. When generating the weight interval, the minimum value is 1, and the maximum value can be set to the sum of the individual weights (ie, the total weight sum) plus 1, and the range of each interval is [the maximum value of the previous interval, the maximum value of the previous interval + current weight value).

Still taking the above weight configuration [SP15:SP13:SP14:SP17]=[10:20:10:30] as an example, the following weight interval can be generated:

Weight range corresponding to SP15: [1, 11);

Weight range corresponding to SP13: [11, 31);

Weight range corresponding to SP14: [31, 41);

Weight range corresponding to SP17: [41, 71);

In another example, the weights of the individual short message SPs may also be sorted, for example, [SP15:SP14:SP13:SP17]=[10:10:20:30], and then the respective weights are generated according to the above method. Interval, including:

Weight range corresponding to SP15: [1, 11);

SP14 corresponding weight interval: [11, 21);

Weight range corresponding to SP13: [21, 41);

Weight range corresponding to SP17: [41, 71);

In step 202, a random number is generated in the union of the weight intervals corresponding to the respective short message SPs. If the random number is located in the weight interval of the short message SP, the short message SP is determined to be the target SP.

For example, within a union range of weight intervals corresponding to each short message SP, that is, [1, 71), a random number is generated in the range, and the random number is compared with each weight interval to determine which weight the random number is located. Interval. For example, assuming that a random number 52 is generated, the weight interval [41, 71] corresponding to the 52 is obtained.

In this example, if the random number falls within a certain weight interval, it can be indicated that the short message SP corresponding to the weight interval is selected, and the SP can be referred to as a target SP. In addition, the probability that the random number falls within a certain weight interval is basically the same as the proportion of the weight interval in the weight interval union [1, 71). For example, the weight interval [41, 71) corresponding to SP17 is the most. Long, then the probability that the random number falls into the interval is relatively large. Therefore, by configuring the weight and the random matching manner, the server can allocate the traffic according to the configured weight ratio when the server divides the flow.

In step 203, the short message sending service corresponding to the short message sending request is allocated to the target SP.

For example, the target SP may send a corresponding short message sending service according to the request of the short message sending request, for example, the short message content set by the business organization may be sent to a specific group.

In the service processing method of the present example, after configuring the weights of the SPs, the background system 16 may store the weights corresponding to the SPs in the database, and may send the weights of the SPs to the server 11 and be cached locally by the server 11. Therefore, the server 11 can generate a weighting interval as soon as possible after receiving the short message sending request, and select the target SP by using a random matching method. In addition, if the weight of each SP does not change, the server 11 may also store the weight after the first generation of the weight interval, and then select the target SP according to the weight interval when the next time the short message transmission request is received, further improving the determination of the target SP. speed.

By configuring weights for multiple SMS SPs, you can flexibly change the service of an SP. For example, if you want to reduce the amount of traffic allocated to an SP, reduce its weight, or if you want to stop assigning to an SP. If the SMS is sent to the service, set its weight to zero. The server can implement the automatic splitting of the short message sending service according to the weight, as long as the weights of the SPs for the short message sending service are set according to the actual service requirements or the service capabilities of the SP. The background system can also update the weight of each SP. The updated SP weight can be called new configuration data, and the new configuration data can be sent to the server by the background system, and the server caches the new configuration data locally.

Applying the service processing method of this example, you can quickly remove the faulty SP when the SMS SP is abnormal. For example, if the SMS sending service is no longer cooperated with a short message SP, or the SMS sending success rate of a short message SP is compared. Low, you can use the business processing method of this example to eliminate the corresponding SP. Figure 3 illustrates the business process A flow chart of the method may include:

In step 301, a monitoring clear command is obtained, where the command carries the SP identifier to be culled.

For example, the server may obtain a monitoring clear command, which is mainly used to notify which SMS SPs will be rejected, and no longer receive SMS sending services. For example, the monitoring clear command may be determined by the monitoring platform by monitoring the sending success rate and duration of each short message SP. For example, the monitoring platform may set an RP culling condition including: the sending success rate is lower than the preset success rate. The threshold is 85% and the duration is greater than or equal to the time threshold of 3 minutes (the values of the success rate threshold and the time threshold can be adjusted). If the monitoring platform monitors that the spoofing condition is met when the SP sends the short message, it is determined that the SP can be culled, the monitoring clear command is sent to the server, and the SP identifier of the short message SP to be culled can be carried in the command. The monitoring platform may be a monitoring platform set outside the server, or may be a monitoring platform set on the server.

In step 302, according to the monitoring and clearing command, the weight of the short message SP corresponding to the SP identifier is removed, and the configuration data status of the short message SP in the background system is modified to be unavailable, so that the short message SP is no longer assumed. SMS delivery service.

For example, after obtaining the monitoring and clearing command, the server may remove the SP configuration information cached by the server, including the weight of the SMS SP corresponding to the SP identifier, and also change the configuration data status of the SP in the background system to be unavailable. In this way, when the server receives the short message sending request and calculates the target SP to be allocated, the SP that has already removed the weight will not have the corresponding weight interval, and will not be assigned the short message sending service.

In addition, the server obtains the monitoring and clearing command, and the monitoring platform may also notify the person in charge of the rejected SMS SP according to the command, so that the person in charge knows that the SP has been culled and no longer processes the short message sending service.

The service processing method of the example can monitor the SMS sending log of the SP, and automatically notify the server when the short message sending success rate of the short message SP is low, and the server removes the weight of the corresponding SP, thereby quickly removing the abnormal SP and reducing the service. risk.

In another example, the configuration data status of the SP can also be changed by the administrator in the background system. For example, if a short message SP in the current stage fails and is not suitable for processing the short message sending service, the configuration data status of the SP in the database of the background system may be set to be unavailable; or, when no longer cooperate with a short message SP, It is also possible to remove the configuration data of the SP from the background system. . After the configuration data status of the SP is changed, the background system may send a data status notification to the server. For example, the server may be notified to configure the SMS SP whose data status is unavailable. The server will notify the data status that if the status of an SP is unavailable, the configuration data of the SP cached by the local server, including the weight corresponding to the SP, may be removed, so that the short message SP will no longer bear the short message sending service.

The application also provides a service processing device, which can execute the above-mentioned service processing method, as shown in FIG. 4 As shown, the apparatus can include an interval generation module 41, a random determination module 42, and a service distribution module 43.

The interval generating module 41 is configured to generate, according to the weights of the plurality of short message SPs for providing the short message sending service corresponding to the short message sending request, a weight interval corresponding to each short message SP, where the weight is generated. The ratio of the sum of the total weights corresponds to the proportion of the traffic volume of the short message sending service undertaken by the SP;

The random determination module 42 is configured to generate a random number in a union range of weight ranges corresponding to the respective short message SPs, and if the random number is located in a weight interval of a short message SP, determine that the short message SP is a target SP. ;

The service allocation module 43 is configured to allocate the short message sending service corresponding to the short message sending request to the target SP.

Referring to FIG. 5, the apparatus may further include: a monitoring receiving module 44 and a data culling module 45.

The monitoring receiving module 44 is configured to acquire a monitoring clear command, where the monitoring clear command carries an SP identifier to be culled;

The data culling module 45 is configured to: according to the monitoring and clearing command, cull the weight of the short message SP corresponding to the SP identifier, and modify the configuration data status of the short message SP in the background system to be unavailable, so that the short message SP is not Responsible for SMS delivery business.

In an example, the monitoring receiving module 44 is configured to separately monitor the sending success rate and duration of the plurality of short message SPs; if the sending success rate of the short message SP is lower than a preset success rate threshold, and the duration reaches The time threshold determines that the short message SP is culled.

In an example, referring to FIG. 6, the apparatus may further include: a status receiving module 46 and a data processing module 47, wherein

The status receiving module 46 is configured to receive a data status notification sent by the background system, where the data status notification is used to indicate that the configuration data status is unavailable.

The data processing module 47 is configured to: according to the data status notification, remove the weight of the short message SP, so that the short message SP does not process the short message sending service.

In an example, the device may further include: a data storage module 48, configured to receive new configuration data sent by the background system, where the new configuration data includes respective weights of the plurality of short message SPs; and cache the new configuration data On the local server.

The service processing device of the example may be disposed in a server, and the server may allocate the short message sending service corresponding to the received short message sending request to an SP, and implement a flexible change of the short message sending service by changing the weight of the SP. The split ratio between the various SPs.

Those skilled in the art will readily appreciate other aspects of the present invention after considering the specification and practicing the invention disclosed herein. implementation plan. The present application is intended to cover any variations, uses, or adaptations of the present invention, which are in accordance with the general principles of the present invention and include common general knowledge or conventional technical means in the art that are not disclosed in the present disclosure. . The specification and examples are to be considered as illustrative only,

It is to be understood that the invention is not limited to the details of the details of The scope of the invention is limited only by the appended claims.

Claims (10)

A service processing method, comprising: When receiving the short message sending request, the weight interval corresponding to each short message SP is generated according to the weight of the plurality of short message SPs for providing the short message sending service corresponding to the short message sending request, and the weights correspond to the proportion of the total weight sum The proportion of the traffic volume of the short message sending service undertaken by the SP; Generating a random number in a union range of weight ranges corresponding to the respective short message SPs, and if the random number is located in a weight interval of a short message SP, determining that the short message SP is a target SP; And distributing the short message sending service corresponding to the short message sending request to the target SP. The method of claim 1 further comprising: Obtaining a monitoring clear command, where the monitoring clear command carries an SP identifier to be culled; And according to the monitoring and clearing command, the weight of the short message SP corresponding to the SP identifier is removed, and the configuration data status of the short message SP in the background system is modified to be unavailable, so that the short message SP no longer bears the short message sending service. The method of claim 2, wherein the obtaining a monitoring clear command comprises: Monitoring, respectively, a sending success rate and a duration of the plurality of short message SPs; If the sending success rate of a short message SP is lower than a preset success rate threshold and the duration reaches a time threshold, it is determined that the short message SP is rejected. The method of claim 1 further comprising: Receiving a data status notification sent by the background system, where the data status notification is used to indicate that the configuration data status is unavailable; And according to the data status notification, the weight of the short message SP is removed, so that the short message SP does not process the short message sending service. The method of claim 1 further comprising: Receiving new configuration data sent by the background system, where the new configuration data includes respective weights of the plurality of short message SPs; The new configuration data is cached on the local server. A service processing device, comprising: The interval generating module is configured to generate a weight interval corresponding to each short message SP according to a weight of multiple short message SPs for providing a short message sending service corresponding to the short message sending request, when the short message sending request is received, where the weight is occupied The ratio of the total weight sum corresponds to the proportion of the traffic volume of the short message sending service undertaken by the SP; a random determination module, configured to generate one in a union range of weight ranges corresponding to the respective short message SPs a random number, if the random number is located in a weight interval of a short message SP, determining that the short message SP is a target SP; The service allocation module is configured to allocate the short message sending service corresponding to the short message sending request to the target SP. The device according to claim 6, further comprising: a monitoring and receiving module, configured to acquire a monitoring and clearing command, where the monitoring and clearing command carries an SP identifier to be culled; a data culling module, configured to remove the weight of the short message SP corresponding to the SP identifier according to the monitoring and clearing command, and modify the configuration data status of the short message SP in the background system to be unavailable, so that the short message SP is no longer Bear the SMS sending service. The device of claim 7 wherein: The monitoring receiving module is configured to separately monitor a sending success rate and a duration of the plurality of short message SPs; if a sending success rate of a short message SP is lower than a preset success rate threshold, and the duration reaches a time threshold, then It is determined that the short message SP is rejected. The device according to claim 6, further comprising: a status receiving module, configured to receive a data status notification sent by the background system, where the data status notification is used to indicate that the configuration data status is unavailable to the SMS SP; The data processing module is configured to: according to the data status notification, remove the weight of the short message SP, so that the short message SP does not process the short message sending service. The device according to claim 6, further comprising: a data storage module, configured to receive new configuration data sent by the background system, where the new configuration data includes respective weights of the plurality of short message SPs; and cache the new configuration data in a local server.

Images