Method for configuring short message mass sending service system, and related device, medium and program

Abstract

The embodiment of the application discloses a configuration method of a short message mass sending service system and related products. In the configuration method, after the short message mass sending management end receives a short message filtering strategy configuration completion interface sent by an administrator client, the short message mass sending management end extracts configuration parameter items of N configurable entries configured from the short message filtering strategy configuration completion interface, and imports the configuration parameter items into a short message filtering strategy generation model to obtain a short message filtering strategy rule1, and sends a short message filtering strategy taking effect instruction order2 carrying the short message filtering strategy rule1 to a short message mass sending service end; the short message mass sending service end takes effect on the short message filtering strategy rule1; the short message filtering strategy rule1 is filtered and judged based on the taking effect; in the case that the filtering judgment result is not filtered, the short message mes1 is sent by calling a short message channel in a candidate short message channel resource pool; in the case that the filtering judgment result is filtered, the short message mes1 is abandoned.

Description

Technical Field

[0001] This application relates to the fields of communication and Internet-related technologies, and in particular to configuration methods and related products for SMS bulk messaging service systems. Background Technology

[0002] Currently, SMS is still widely used in many application scenarios. Marketing SMS is a common type of SMS, often characterized by mass sending (batch push). Of course, there are other scenarios where mass SMS is needed, such as epidemic prevention reminders, disaster prevention reminders, and so on.

[0003] Bulk SMS messaging relies on bulk SMS service systems, but current bulk SMS service systems cannot achieve flexible configuration management. For example, SMS filtering policies are fixed by default, which greatly affects the flexibility of the application. Summary of the Invention

[0004] This application provides a configuration method and related products for a bulk SMS service system.

[0005] This application provides a configuration method for a bulk SMS service system. The bulk SMS service system includes: a bulk SMS management terminal, a bulk SMS service terminal, and an application programming interface (API) terminal that are interconnected. The bulk SMS management terminal includes: a runtime environment layer, a data support layer running on top of the runtime environment layer, a service layer running on top of the data support layer, a gateway layer running on top of the service layer, and a front-end display layer. The gateway layer is used for authenticating administrator clients.

[0006] The method includes: after receiving an SMS filtering policy configuration request from an administrator client, the front-end display layer of the SMS bulk sending management terminal sends an SMS filtering policy configuration interface to the administrator client in response to the SMS filtering policy configuration request. The SMS filtering policy configuration interface includes N configurable entries, including configurable entry n1 and configurable entry n2. Configurable entry n1 has n11 candidate configuration parameter items, and any one of the n11 candidate configuration parameter items can be selected as a configuration parameter item for configurable entry n1. Configurable entry n2 has custom configuration parameter items. N and n11 are integers greater than 1.

[0007] After receiving the SMS filtering policy configuration completion interface sent by the administrator client, the front-end presentation layer extracts the configuration parameter items of the N configurable items that have been configured from the SMS filtering policy configuration completion interface. The SMS filtering policy configuration completion interface includes the N configurable items that have been configured. The front-end presentation layer then sends an SMS filtering policy generation instruction order1 to the service layer of the SMS bulk sending management terminal. The SMS filtering policy generation instruction order1 carries the configuration parameter items of the extracted N configurable items.

[0008] The service layer of the bulk SMS management terminal imports the configuration parameters of the N configurable entries carried by the SMS filtering policy generation instruction order1 into the SMS filtering policy generation model to obtain the SMS filtering policy rule1, and passes the SMS filtering policy rule1 to the front-end presentation layer; the front-end presentation layer sends the SMS filtering policy activation instruction order2, which carries the SMS filtering policy rule1, to the bulk SMS service terminal.

[0009] After receiving the SMS filtering policy activation instruction order2 from the SMS bulk sending management terminal, the SMS bulk sending server activates the SMS filtering policy rule1. If it obtains an SMS message mes1 to be sent from the application interface, it performs a filtering decision on the SMS message mes1 based on the activated SMS filtering policy rule1. If the filtering decision result is no filtering, it calls the SMS channel in the candidate SMS channel resource pool to send the SMS message mes1. If the filtering decision result is filtering, it abandons sending the SMS message mes1.

[0010] In some possible implementations, the method includes:

[0011] The front-end display layer of the bulk SMS management terminal receives SMS template configuration requests from the administrator client.

[0012] The front-end presentation layer sends an SMS template configuration interface to the administrator client in response to the SMS template configuration request. The SMS template configuration interface includes M configurable entries, including configurable entry m1 and configurable entry m2. Configurable entry m1 has m11 candidate configuration parameter items, and any one of the m11 candidate configuration parameter items can be selected as a configuration parameter item for configurable entry m1. Configurable entry m2 has custom configuration parameter items. M and m11 are integers greater than 1.

[0013] After receiving the SMS template configuration completion interface sent by the administrator client, the front-end presentation layer extracts the configuration parameter items of the M configurable items that have been configured from the SMS template configuration completion interface, wherein the SMS template configuration completion interface includes the M configurable items that have been configured; the front-end presentation layer sends an SMS template generation command order3 to the service layer of the SMS bulk sending management terminal; the SMS template generation command order3 carries the configuration parameter items of the extracted M configurable items.

[0014] After receiving the SMS template generation instruction order3 from the front-end display layer, the service layer of the SMS bulk sending management terminal imports the configuration parameters of the M configurable items carried by the SMS template generation instruction order3 into the SMS template generation model to obtain the SMS template mode1, and passes the SMS template mode1 to the front-end display layer; the front-end display layer sends the SMS template activation instruction order4, which carries the SMS template mode1, to the application interface terminal.

[0015] The application programming interface (API) activates the SMS template mode1 after receiving the SMS template activation command order4 from the SMS bulk messaging management terminal.

[0016] In some possible implementations, SMS message mes1 includes an SMS identifier idmes1, which is used to identify SMS message mes1.

[0017] Before the bulk SMS service receives the SMS message 'mes1' pushed by the application interface, the method may further include:

[0018] If the application programming interface (API) receives a text message generation request req1 from a user client, where req1 carries text message material mat1, the API imports mat1 into the already activated text message template mode1 to obtain the text message mes1; and sends a text message generation request response res1 carrying mes1 to the user client. If the API receives a bulk text message sending request req2 from the user client, where req2 carries the text message identifier idmes1, the API pushes the text message mes1 to be sent to the bulk text message sending server.

[0019] In some possible implementations, the method may further include:

[0020] The bulk SMS service generates an SMS filtering record P1 when the filtering decision of SMS mes1 is "filtered". The SMS filtering record P1 contains the SMS filtering policy identifier idrule1, the SMS identifier idmes1, and the filtering reason. The SMS filtering policy identifier idrule1 identifies the SMS filtering policy rule1. The bulk SMS service sends an SMS filtering reminder message to the application programming interface (API), which carries the SMS filtering record P1. The API then forwards the SMS filtering reminder message to the user client.

[0021] When the application programming interface (API) receives a filtering appeal request from a user client, the filtering appeal request carries the SMS identifier idmes1 and the reason for the filtering appeal; the API forwards the filtering appeal request to the SMS bulk sending management terminal.

[0022] Upon receiving a filtering appeal request, the front-end presentation layer of the bulk SMS management terminal forwards the filtering appeal request to the administrator client. If it receives a filtering appeal request response from the administrator client, and the filtering appeal request response carries a filtering appeal success identifier, the front-end presentation layer of the bulk SMS management terminal sends a filtering exemption instruction to the bulk SMS server. The filtering exemption instruction carries the SMS identifier idmes1, and the filtering exemption instruction is used to indicate that the SMS mes1 identified by the SMS identifier idmes1 is allowed to be filtered exempted.

[0023] After receiving the filtering exemption instruction, the bulk SMS service calls the SMS channel in the candidate SMS channel resource pool to send the SMS message mes1.

[0024] In some possible implementations, the method further includes: if a filter appeal request response is received from the administrator client in response to the filter appeal request, and the filter appeal request response carries a filter appeal failure identifier, the front-end display layer of the SMS bulk sending management terminal forwards the filter appeal request response to the application interface terminal.

[0025] The application programming interface (API) forwards the filtering appeal request response to the user client. If the API receives a text message generation request (req3) from the user client, where req3 carries text message material mat2 (obtained by modifying text message material mat1), the API imports mat2 into the already activated text message template mode1 to obtain text message mes2. Mes2 contains a text message identifier idmes2, which identifies the text message mes2. The API then sends a text message generation request response (res3) to the user client, where req3 carries the text message mes2. If the API receives a bulk text message sending request (req4) from the user client, where req4 carries the text message identifier idmes2, the API pushes the text message mes2 to be sent to the bulk text message sending server.

[0026] In some possible implementations, the method may further include: the SMS bulk sending server activating a filter counter add1 and an exemption counter add2 simultaneously with the activation of SMS filtering policy rule1; the filter counter add1 is used to accumulate the number of times SMS messages are filtered by SMS filtering policy rule1; the filter counter add1 is used to accumulate the number of times SMS messages are exempted from filtering after being filtered by SMS filtering policy rule1; the count value of filter counter add1 is incremented by 1 when the SMS filtering record P1 is generated; and the count value of exemption counter add2 is incremented by 1 when the filtering exemption instruction is received.

[0027] When the count value of the filter counter add1 exceeds the threshold th1, and the ratio of the count value of the exemption counter add2 to the count value of the filter counter add1 exceeds the threshold th2, the SMS bulk sending server sends an SMS filtering policy optimization request to the SMS bulk sending management server. The SMS filtering policy optimization request carries the SMS filtering policy identifier idrule1 and the SMS filtering record set. The SMS filtering record set contains the SMS filtering record P1. Each SMS filtering record in the SMS filtering record set contains the SMS filtering policy identifier idrule1. The number of SMS filtering records contained in the SMS filtering record set is the current count value of the filter counter add1.

[0028] After receiving the SMS filtering policy optimization request from the SMS bulk sending server, the front-end display layer of the SMS bulk sending management terminal forwards the SMS filtering policy optimization request to the administrator client.

[0029] If the front-end presentation layer of the SMS bulk messaging management terminal receives an SMS filtering policy reconfiguration request from an administrator client, wherein the SMS filtering policy reconfiguration request carries an SMS filtering policy identifier idrule1; the front-end presentation layer sends an SMS filtering policy reconfiguration interface to the administrator client in response to the SMS filtering policy reconfiguration request. The SMS filtering policy reconfiguration interface includes N configurable entries, wherein the N configurable entries include configurable entry n1 and configurable entry n2. Configurable entry n1 has n11 candidate configuration parameter items, and any one of the n11 candidate configuration parameter items can be selected as a configuration parameter item for configurable entry n1. The default configuration parameter item for configurable entry n1 is the configuration parameter item corresponding to configurable entry n1 in SMS filtering policy rule1. Configurable entry n2 has custom configuration parameter items, and the default configuration parameter item for configurable entry n2 is the configuration parameter item corresponding to configurable entry n2 in SMS filtering policy rule1.

[0030] After receiving the SMS filtering policy reconfiguration completion interface sent by the administrator client, the front-end presentation layer extracts the configuration parameter items of the N configurable items that have been configured from the SMS filtering policy reconfiguration completion interface, wherein the SMS filtering policy reconfiguration completion interface includes the N configurable items that have been configured; and sends an SMS filtering policy generation instruction order5 to the service layer of the SMS bulk sending management terminal, wherein the SMS filtering policy generation instruction order5 carries the configuration parameter items of the N configurable items extracted from the SMS filtering policy reconfiguration completion interface.

[0031] The service layer of the bulk SMS management terminal imports the configuration parameters of the N configurable entries carried by the SMS filtering policy generation instruction order5 into the SMS filtering policy generation model to obtain the SMS filtering policy rule2, and passes the SMS filtering policy rule2 to the front-end presentation layer; the front-end presentation layer sends the SMS filtering policy activation instruction order6, carrying the SMS filtering policy rule2, to the bulk SMS service terminal.

[0032] After receiving the SMS filtering policy activation instruction order6 issued by the SMS bulk sending management terminal, the SMS bulk sending server activates the SMS filtering policy rule2 and deactivates the SMS filtering policy rule1.

[0033] A second aspect of this application provides a bulk SMS service system, comprising: a bulk SMS management terminal, a bulk SMS service terminal, and an application programming interface terminal that are interconnected.

[0034] The SMS bulk messaging management terminal includes: a runtime environment layer, a data support layer running on top of the runtime environment layer, a service layer running on top of the data support layer, a gateway layer running on top of the service layer, and a front-end display layer. The gateway layer is used for authenticating administrator clients.

[0035] The front-end display layer of the SMS bulk messaging management terminal is used to send an SMS filtering policy configuration interface to the administrator client in response to the SMS filtering policy configuration request after receiving the request from the administrator client. The SMS filtering policy configuration interface includes N configurable entries, specifically configurable entry n1 and configurable entry n2. Configurable entry n1 has n11 candidate configuration parameters, and any one of these n11 candidate parameters can be selected as a configuration parameter for configurable entry n1. Configurable entry n2 has custom configuration parameters. N and n11 are integers greater than 1.

[0036] The front-end presentation layer is further configured to, after receiving the SMS filtering policy configuration completion interface sent by the administrator client, extract the configuration parameter items of the N configurable items that have been configured from the SMS filtering policy configuration completion interface, wherein the SMS filtering policy configuration completion interface includes the N configurable items that have been configured; and send an SMS filtering policy generation instruction order1 to the service layer of the SMS bulk sending management terminal, wherein the SMS filtering policy generation instruction order1 carries the configuration parameter items of the N configurable items extracted.

[0037] The service layer of the bulk SMS management terminal is used to import the configuration parameters of N configurable items carried by the SMS filtering policy generation instruction order1 into the SMS filtering policy generation model to obtain the SMS filtering policy rule1, and pass the SMS filtering policy rule1 to the front-end display layer; the front-end display layer sends the SMS filtering policy activation instruction order2, which carries the SMS filtering policy rule1, to the bulk SMS service terminal.

[0038] The bulk SMS service is configured to: activate the SMS filtering policy rule1 upon receiving the SMS filtering policy activation instruction order2 from the bulk SMS management terminal; if it obtains an SMS message mes1 to be sent from the application interface terminal, it performs a filtering decision on the SMS message mes1 based on the activated SMS filtering policy rule1; wherein, if the filtering decision result is no filtering, it calls the SMS channel in the candidate SMS channel resource pool to send the SMS message mes1; if the filtering decision result is filtering, it abandons sending the SMS message mes1.

[0039] In some possible implementations, the front-end presentation layer of the bulk SMS management terminal is further configured to: receive an SMS template configuration request from an administrator client; and send an SMS template configuration interface to the administrator client in response to the SMS template configuration request. The SMS template configuration interface includes M configurable entries, wherein the M configurable entries include: configurable entry m1 and configurable entry m2. Configurable entry m1 has m11 candidate configuration parameter items, and any one of the m11 candidate configuration parameter items can be selected as a configuration parameter item for configurable entry m1. Configurable entry m2 has custom configuration parameter items. M and m11 are integers greater than 1.

[0040] The front-end presentation layer is further configured to, after receiving the SMS template configuration completion interface sent by the administrator client, extract the configuration parameter items of the configured M configurable items from the SMS template configuration completion interface, wherein the SMS template configuration completion interface includes the configured M configurable items; and send an SMS template generation instruction order3 to the service layer of the SMS bulk sending management terminal; the SMS template generation instruction order3 carries the extracted configuration parameter items of the M configurable items.

[0041] The service layer of the SMS bulk messaging management terminal is further configured to, upon receiving the SMS template generation instruction order3 from the front-end display layer, import the configuration parameters of the M configurable items carried by the SMS template generation instruction order3 into the SMS template generation model to obtain the SMS template mode1, and pass the SMS template mode1 to the front-end display layer; the front-end display layer sends an SMS template activation instruction order4 carrying the SMS template mode1 to the application interface terminal.

[0042] The application programming interface is also used to activate the SMS template mode1 after receiving the SMS template activation instruction order4 issued by the SMS bulk sending management terminal.

[0043] In some possible implementations,

[0044] The SMS message mes1 contains an SMS identifier idmes1, which is used to identify the SMS message mes1.

[0045] The application programming interface (API) is further configured to, before the bulk SMS service receives the SMS message mes1 to be sent by the API, if it receives an SMS generation request req1 sent by the user client, the SMS generation request req1 carrying SMS material mat1, import the SMS material mat1 into the already activated SMS template mode1 to obtain the SMS message mes1; send an SMS generation request response res1 carrying the SMS message mes1 to the user client; if it receives a bulk SMS sending request req2 sent by the user client, the bulk SMS sending request req2 carrying the SMS identifier idmes1, and push the SMS message mes1 to be sent to the bulk SMS service.

[0046] In some possible implementations,

[0047] The bulk SMS sending server is further configured to generate an SMS filtering record P1 if the filtering decision result of the SMS message mes1 is "filtered". The SMS filtering record P1 contains the SMS identifier idmes1, the filtering reason, and the SMS filtering policy identifier idrule1, where idrule1 identifies the SMS filtering policy rule1. The server also sends an SMS filtering reminder message to the application programming interface (API), the message carrying the SMS filtering record P1.

[0048] The application programming interface is also used to forward the SMS filtering reminder message to the user client; when a filtering appeal request is received from the user client, the filtering appeal request carries the SMS identifier idmes1 and the reason for the filtering appeal; and forward the filtering appeal request to the SMS bulk sending management terminal.

[0049] The front-end display layer of the bulk SMS management terminal is also used to forward the filtering appeal request to the administrator client after receiving the filtering appeal request; if the administrator client receives a filtering appeal request response to the filtering appeal request, and the filtering appeal request response carries a filtering appeal success identifier, the terminal sends a filtering exemption instruction to the bulk SMS server. The filtering exemption instruction carries the SMS identifier idmes1, and the filtering exemption instruction is used to indicate that the SMS mes1 identified by the SMS identifier idmes1 is allowed to be filtered exempted.

[0050] The bulk SMS service is also used to send the SMS message mes1 by calling the SMS channel in the candidate SMS channel resource pool after receiving the filtering exemption instruction.

[0051] In some possible implementations, the front-end display layer of the SMS bulk messaging management terminal is also used to forward the filter appeal request response to the application interface terminal if it receives a filter appeal request response from the administrator client in response to the filter appeal request, and the filter appeal request response carries a filter appeal failure identifier.

[0052] The application programming interface (API) is also used to forward filtering appeal request responses to user clients; if it receives a text message generation request req3 from a user client, the text message generation request req3 carries text message material mat2, which is obtained by modifying text message material mat1, and imports the text message material mat2 into the already effective text message template mode1 to obtain the text message mes2, the text message mes2 contains a text message identifier idmes2, the text message identifier idmes2 is used to identify the text message mes2; a text message generation request response res3 is sent to the user client, the text message generation request response res3 carries the text message mes2; if it receives a mass text message sending request req4 from the user client, the mass text message sending request req4 carries the text message identifier idmes2, and pushes the text message mes2 to be sent to the mass text message sending server.

[0053] In some possible implementations, the bulk SMS server is further configured to: simultaneously activate a filter counter add1 and an exemption counter add2 when the SMS filtering policy rule1 takes effect; the filter counter add1 is used to accumulate the number of times an SMS is filtered by SMS filtering policy rule1; the filter counter add1 is used to accumulate the number of times an SMS is exempted from filtering after being filtered by SMS filtering policy rule1; the count value of filter counter add1 is incremented by 1 when the SMS filtering record P1 is generated; the count value of exemption counter add2 is incremented by 1 when the filter exemption instruction is received; when the count value of filter counter add1 exceeds a threshold th1, and the ratio of the count value of exemption counter add2 to the count value of filter counter add1 exceeds a threshold th2, a bulk SMS server sends an SMS filtering policy optimization request to the bulk SMS management terminal, wherein the SMS filtering policy optimization request carries an SMS filtering policy identifier idrule1 and an SMS filtering record set, the SMS filtering record set contains the SMS filtering record P1, each SMS filtering record in the SMS filtering record set contains the SMS filtering policy identifier idrule1, and the number of SMS filtering records contained in the SMS filtering record set is the current count value of filter counter add1.

[0054] The front-end display layer of the bulk SMS management terminal is also used to forward the SMS filtering strategy optimization request to the administrator client after receiving the SMS filtering strategy optimization request from the bulk SMS server. If a reconfiguration request for SMS filtering policy is received from an administrator client, the request carries an SMS filtering policy identifier idrule1. An SMS filtering policy reconfiguration interface is sent to the administrator client in response to the request. This interface includes N configurable entries, specifically configurable entry n1 and configurable entry n2. Configurable entry n1 has n11 candidate configuration parameters, and any one of these n11 can be selected as a configuration parameter for configurable entry n1. The default configuration parameter for configurable entry n1 is the corresponding configuration parameter in SMS filtering policy rule1. Configurable entry n2 has custom configuration parameters, and its default configuration parameter is the corresponding configuration parameter in SMS filtering policy rule1. After receiving the SMS filtering policy reconfiguration completion interface sent by the administrator client, the configuration parameter items of the N configurable entries that have been configured are extracted from the SMS filtering policy reconfiguration completion interface, wherein the SMS filtering policy reconfiguration completion interface includes the N configurable entries that have been configured; and an SMS filtering policy generation instruction order5 is sent to the service layer of the SMS bulk sending management terminal, wherein the SMS filtering policy generation instruction order5 carries the configuration parameter items of the N configurable entries extracted from the SMS filtering policy reconfiguration completion interface.

[0055] The service layer of the bulk SMS management terminal is also used to import the configuration parameters of the N configurable entries carried by the SMS filtering strategy generation instruction order5 into the SMS filtering strategy generation model to obtain the SMS filtering strategy rule2, and to pass the SMS filtering strategy rule2 to the front-end presentation layer.

[0056] The front-end presentation layer is also used to send an SMS filtering policy activation instruction order6, carrying SMS filtering policy rule2, to the SMS bulk sending server.

[0057] The bulk SMS server is also configured to, upon receiving the SMS filtering policy activation instruction order6 issued by the bulk SMS management terminal, activate the SMS filtering policy rule2 and deactivate the SMS filtering policy rule1.

[0058] A third aspect of this application provides a communication device, including a processor and a memory.

[0059] The processor is used to call the computer program stored in the memory to perform some or all of the operations performed by the SMS bulk sending server, SMS bulk sending management terminal, or application programming interface in the embodiments of the present invention.

[0060] The fourth aspect of this application provides a computer-readable storage medium storing a computer program that, when executed by a computer, can perform some or all of the operations performed by the SMS bulk messaging server, SMS bulk messaging management terminal, or application programming interface in the embodiments of the present invention.

[0061] The fifth aspect of this application provides a computer program, wherein when the computer program is executed by a computer, it can perform some or all of the operations performed by the SMS bulk sending server, SMS bulk sending management terminal, or application programming interface in the embodiments of the present invention.

[0062] As can be seen, the embodiments of this application introduce a flexible and convenient configuration mechanism for the SMS bulk messaging service system with the service layer as its core. This facilitates the flexible configuration and activation of SMS filtering strategies, thereby improving the application flexibility of the SMS bulk messaging service system and expanding its application scope. Attached Figure Description

[0063] Figure 1-A This is a schematic diagram of a bulk SMS service system provided in an embodiment of this application;

[0064] Figure 1-B This is a schematic diagram of a bulk SMS service provided in an embodiment of this application;

[0065] Figure 1-C This is a schematic diagram of an application programming interface provided in an embodiment of this application;

[0066] Figure 1-D This is a schematic diagram of a bulk SMS management terminal provided in an embodiment of this application;

[0067] Figure 2 This is a flowchart illustrating a configuration method for a bulk SMS service system provided in an embodiment of this application;

[0068] Figure 3 This is a schematic diagram illustrating another configuration method for a bulk SMS service system provided in an embodiment of this application;

[0069] Figure 4 This is a schematic diagram illustrating another configuration method for a bulk SMS service system provided in an embodiment of this application;

[0070] Figure 5 This is a schematic diagram of a communication device provided in an embodiment of this application. Detailed Implementation

[0071] To enable those skilled in the art to better understand the present application, the technical solutions in the embodiments of the present application will be clearly described below with reference to the accompanying drawings. Obviously, the described embodiments are only a part of the embodiments of the present application, and not all of them. Based on the embodiments of the present application, all other embodiments obtained by those skilled in the art without creative effort should fall within the scope of protection of the present application.

[0072] The terms "first," "second," and "third," etc., appearing in various parts of this application are used to distinguish different objects and are not intended to describe a specific order. Furthermore, the terms "comprising" and "having," and any variations thereof, are intended to cover non-exclusive inclusion. For example, a process, method, system, product, or apparatus that includes a series of steps or units is not limited to the listed steps or units, but may optionally include steps or units not listed, or may optionally include other steps or units inherent to these processes, methods, products, or apparatuses.

[0073] See Figure 1-A , Figure 1-A This is a schematic diagram illustrating the architecture of a bulk SMS service system provided in an embodiment of this application. The bulk SMS service system includes a bulk SMS server and an application programming interface (API) terminal, and may also include a bulk SMS management terminal. The bulk SMS server, API terminal, and management terminal are interconnected and communicate via a network.

[0074] The bulk SMS server is used to implement bulk SMS sending services. The application programming interface (API) can interact with user clients and is used to generate SMS messages to be sent in bulk based on user needs. The bulk SMS management interface can interact with management clients and can be used for policy configuration and management of the bulk SMS server and API.

[0075] See Figure 1-B The bulk SMS service includes: a runtime environment layer, a data support layer running on top of the runtime environment layer, a service layer running on top of the data support layer, and a data source layer running on top of the service layer. The runtime environment layer provides the software runtime environment. The data support layer provides the system data required for the service layer to run; the data source layer obtains the application data (including SMS messages) that the service layer needs to process.

[0076] See Figure 1-CThe Application Programming Interface (API) can include: a runtime environment layer, a data support layer running on top of the runtime environment layer, a service layer running on top of the data support layer, a gateway layer running on top of the service layer, and an application layer running on top of the gateway layer. The runtime environment layer provides the software runtime environment. The data support layer provides the system data required for the service layer to run. The application layer provides an application interaction interface, allowing interaction with the user client to exchange application data (including SMS messages). The gateway layer filters the passing application data (including SMS messages). The service layer processes application data (including SMS messages) based on the configured processing strategies.

[0077] See Figure 1-D The bulk SMS management terminal includes: a runtime environment layer, a data support layer running on top of the runtime environment layer, a service layer running on top of the data support layer, a gateway layer running on top of the service layer, and a front-end presentation layer. The runtime environment layer provides the software runtime environment. The data support layer provides the system data required for the service layer to run. The gateway layer is used for authentication of administrator clients. The front-end presentation layer provides a management interaction interface for exchanging management data (including various configuration data) with the administrator client. The service layer of the bulk SMS management terminal implements the relevant configuration management functions for the application programming interface and the bulk SMS service.

[0078] The methods in the various method embodiments of this application can be applied to the SMS mass messaging service system exemplified above.

[0079] The following example illustrates the configuration scheme for SMS filtering strategies.

[0080] See Figure 2 , Figure 2 This is a flowchart illustrating a configuration method for a bulk SMS service system according to an embodiment of this application. Figure 2 As shown, a configuration method for a bulk SMS service system provided in one embodiment of this application includes the following:

[0081] 201. The administrator client sends a request to the SMS bulk messaging management terminal to configure SMS filtering policies.

[0082] 202. After receiving the SMS filtering policy configuration request from the administrator client, the front-end display layer of the SMS bulk sending management terminal sends an SMS filtering policy configuration interface to the administrator client in response to the SMS filtering policy configuration request.

[0083] The SMS filtering strategy configuration interface includes N configurable entries, namely configurable entry n1 and configurable entry n2. Configurable entry n1 has n11 candidate configuration parameter items, and any one of the n11 candidate configuration parameter items can be selected as a configuration parameter item for configurable entry n1. Configurable entry n2 has custom configuration parameter items. N and n11 are integers greater than 1.

[0084] It can be understood that configurable entry n1 has n11 candidate configuration parameter items, meaning that the configuration parameter items for configurable entry n1 can only be selected from n11 candidate configuration parameter items, and the administrator client is not allowed to set them freely. Configurable entry n2 has custom configuration parameter items, meaning that the configuration parameter items for configurable entry n2 can be set freely by the administrator client. Some of the N configurable entries can be configurable entries with candidate configuration parameter items, and another part of the N configurable entries can be configurable entries with custom configuration parameter items.

[0085] 203. After receiving the SMS filtering policy configuration interface, the administrator client sends the SMS filtering policy configuration completion interface to the SMS bulk sending management terminal.

[0086] It is understandable that administrators can obtain the SMS filtering policy configuration completion interface by operating the SMS filtering policy configuration interface displayed on the administrator client.

[0087] 204. After receiving the SMS filtering policy configuration completion interface sent by the administrator client, the front-end presentation layer extracts the configuration parameter items of the N configurable items that have been configured from the SMS filtering policy configuration completion interface, which includes the N configurable items that have been configured; and sends an SMS filtering policy generation instruction order1 to the service layer of the SMS bulk sending management terminal, the SMS filtering policy generation instruction order1 carrying the configuration parameter items of the N configurable items extracted.

[0088] 205. After receiving the SMS filtering policy generation instruction order1, the service layer of the SMS bulk sending management terminal imports the configuration parameter items of the N configurable entries carried by the SMS filtering policy generation instruction order1 into the SMS filtering policy generation model to obtain the SMS filtering policy rule1, and then passes the SMS filtering policy rule1 to the front-end presentation layer.

[0089] 206. The front-end presentation layer sends an SMS filtering policy activation instruction order2, carrying the SMS filtering policy rule1, to the SMS bulk sending server.

[0090] 207. After receiving the SMS filtering policy activation instruction order2 from the SMS bulk sending management terminal, the SMS bulk sending server activates the SMS filtering policy rule1. If an SMS message mes1 to be sent is obtained from the application interface, a filtering decision is made on the SMS message mes1 based on the activated SMS filtering policy rule1; if the filtering decision result is no filtering, the SMS channel in the candidate SMS channel resource pool is used to send the SMS message mes1; if the filtering decision result is filtering, the sending of the SMS message mes1 is abandoned.

[0091] In some possible implementations, after the data source layer in the bulk SMS service receives the SMS message 'mes1' pushed by the application programming interface (API), the service layer in the bulk SMS service can select SMS channel 'ch1' from the candidate SMS channel resource pool and attempt to use SMS channel 'ch1' to send SMS message 'mes1'. If sending SMS message 'mes1' via SMS channel 'ch1' fails, the service layer will retry sending SMS message 'mes1' via SMS channel 'ch1'; SMS channel 'ch1' is the highest priority SMS channel currently in the candidate SMS channel resource pool.

[0092] If the SMS-level failure counter count value of count-mes1 exceeds the threshold Th0 and the SMS channel ch1 is still not successfully used to send the SMS message mes1, then SMS channel ch2 is selected from the candidate SMS channel resource pool, and an attempt is made to use SMS channel ch2 to send the SMS message mes1. The SMS channel ch2 is the SMS channel in the candidate SMS channel resource pool whose current priority is second only to SMS channel ch1. The SMS-level failure counter count-mes1 is used to accumulate the number of times the SMS message mes1 has failed to be sent.

[0093] In some possible implementations, the method further includes: when selecting SMS channel ch2 from the candidate SMS channel resource pool, the service layer in the bulk SMS server can clear the count value of the SMS-level failure counter coun-mes1 to zero; when the SMS channel ch2 or the SMS channel ch1 is successfully used to send the SMS mes1 in bulk, the service layer in the bulk SMS server can clear the count value of the SMS-level failure counter coun-mes1 to zero.

[0094] Furthermore, if the SMS-level failure counter coun-mes1 exceeds the threshold Th0 and SMS channel ch2 still fails to successfully send SMS message mes1, then SMS channel ch3 is selected from the candidate SMS channel resource pool, and an attempt is made to send SMS message mes1 using SMS channel ch3, which is the SMS channel in the candidate SMS channel resource pool with the second-highest priority after SMS channel ch2. This process can continue until SMS message mes1 is successfully sent using an SMS channel. Of course, the service layer in the SMS bulk sending server may also give up sending SMS message mes1 after several failed attempts through several SMS channels, and may further notify the application interface of the SMS message mes1 bulk sending failure.

[0095] In some possible implementations, the SMS message may also include a service type tag, for example, SMS message mes1 may also include a service type tag. The service type tag is used to identify the service type, that is, SMS messages of different service types contain different service type tags. At any given time, the SMS bulk messaging server can have only one SMS filtering policy that remains active. This unique, active SMS filtering policy can be used to filter and determine any SMS messages to be sent via the application programming interface (API).

[0096] In addition, the bulk SMS service can also simultaneously activate a library of SMS filtering strategies, which includes multiple SMS filtering policies. These multiple SMS filtering policies in the library correspond to different business type tags (the SMS filtering policies contain business type tags). In this case, after the bulk SMS service receives the SMS message mes1 to be sent (for example, SMS mes1 contains the business type tag label1) pushed by the application interface, it can search the activated SMS filtering policy library for an SMS filtering policy that matches the business type tag label1 (for example, SMS filtering policy rule1 contains the business type tag label1). When an SMS filtering policy rule1 that matches the business type tag label1 is found, the SMS message mes1 can be filtered based on the found activated SMS filtering policy rule1.

[0097] In some possible implementations, if the bulk SMS server does not search the effective SMS filtering policy library for any SMS filtering policy that matches the business type label label1, then the bulk SMS server may select the SMS filtering policy with the highest filtering rate (the highest filtering rate indicates the highest probability that the filtering scale of this SMS filtering policy is the largest) from the SMS filtering policy library (for example, selecting SMS filtering policy rule1), and may make a filtering decision on the SMS mes1 based on the selected effective SMS filtering policy rule1.

[0098] In some other possible implementations, if the bulk SMS service does not search the effective SMS filtering policy library for any SMS filtering policy that matches the service type label label1, the bulk SMS service may also randomly select two SMS filtering policies from the SMS filtering policy library (for example, selecting SMS filtering policies rule1 and rule3). The bulk SMS service may then make a filtering decision on SMS mes1 based on the selected effective SMS filtering policies rule1 and rule3. If the filtering decision result of both SMS filtering policies rule1 and rule3 is "no filtering," the service may use an SMS channel from the candidate SMS channel resource pool to send SMS mes1. If the filtering decision result of SMS filtering policies rule1 or rule3 is "filtering," the service may abandon sending SMS mes1.

[0099] In some other possible implementations, if the bulk SMS service does not search the effective SMS filtering policy library for any SMS filtering policy that matches the service type label label1, then the bulk SMS service can also select SMS filtering policies rule1 and rule3 from the SMS filtering policy library. For example, SMS filtering policy rule1 is the SMS filtering policy with the highest SMS filtering ratio in the SMS filtering policy library, while SMS filtering policy rule3 is an SMS filtering policy with a different rule1 randomly selected from the SMS filtering policy library. The bulk SMS service can then make a filtering decision on SMS mes1 based on the selected effective SMS filtering policies rule1 and rule3. If the filtering decision result of SMS filtering policies rule1 and rule3 is both "no filtering," then the SMS mes1 is sent via a candidate SMS channel resource pool; if the filtering decision result of SMS filtering policies rule1 or rule3 is "filtering," then the bulk sending of SMS mes1 is abandoned.

[0100] It is understandable that if the bulk SMS server does not search for any SMS filtering policy that matches the business type tag label1 in the effective SMS filtering policy library, the special handling mechanisms mentioned above can better balance the relationship between filtering security and bulk sending efficiency.

[0101] Of course, there may be other SMS filtering strategies available for bulk SMS servers, which will not be listed here.

[0102] As can be seen, the embodiments of this application introduce a flexible and convenient configuration mechanism for the SMS bulk messaging service system with the service layer as its core. This facilitates the flexible configuration and activation of SMS filtering strategies, thereby improving the application flexibility of the SMS bulk messaging service system and expanding its application scope.

[0103] The following examples illustrate some SMS template configuration schemes.

[0104] See Figure 3 , Figure 3 This is a flowchart illustrating another configuration method for a bulk SMS service system provided in this application embodiment. Figure 3 As shown, another embodiment of this application provides a configuration method for a bulk SMS service system, which includes the following:

[0105] 301. The administrator client sends an SMS template configuration request to the bulk SMS management terminal.

[0106] 302. The front-end presentation layer of the bulk SMS management terminal receives an SMS template configuration request from the administrator client. The front-end presentation layer sends an SMS template configuration interface to the administrator client in response to the SMS template configuration request. The SMS template configuration interface includes M configurable entries, including configurable entry m1 and configurable entry m2. Configurable entry m1 has m11 candidate configuration parameter items, and any one of the m11 candidate configuration parameter items can be selected individually as a configuration parameter item for configurable entry m1. Configurable entry m2 has custom configuration parameter items. M and m11 are integers greater than 1.

[0107] It can be understood that configurable entry m1 has m11 candidate configuration parameters, meaning that the configuration parameters for configurable entry m1 can only be selected from these m11 candidate parameters, and administrator clients are not allowed to set them freely. Configurable entry m2 has custom configuration parameters, meaning that the configuration parameters for configurable entry m2 can be set freely by administrator clients. Some of the M configurable entries can be configurable entries with candidate configuration parameters, and another part of the M configurable entries can be configurable entries with custom configuration parameters.

[0108] 303. After receiving the SMS template configuration interface, the administrator client sends the SMS template configuration completion interface to the SMS bulk sending management terminal.

[0109] It is understandable that administrators can obtain the SMS template configuration completion interface by operating the SMS template configuration interface displayed on the administrator client.

[0110] 304. After receiving the SMS template configuration completion interface sent by the administrator client, the front-end presentation layer extracts the configuration parameter items of the M configurable items that have been configured from the SMS template configuration completion interface, wherein the SMS template configuration completion interface includes the M configurable items that have been configured; the front-end presentation layer sends an SMS template generation instruction order3 to the service layer of the SMS bulk sending management terminal; the SMS template generation instruction order3 carries the configuration parameter items of the extracted M configurable items.

[0111] 305. After receiving the SMS template generation instruction order3 from the front-end display layer, the service layer of the SMS bulk sending management terminal imports the configuration parameter items of the M configurable items carried by the SMS template generation instruction order3 into the SMS template generation model to obtain the SMS template mode1, and then transmits the SMS template mode1 to the front-end display layer.

[0112] 306. The front-end presentation layer sends an SMS template activation command order4, carrying SMS template mode1, to the application interface.

[0113] 307. The application programming interface (API) activates the SMS template mode1 after receiving the SMS template activation instruction order4 issued by the SMS bulk messaging management terminal.

[0114] In some possible implementations, SMS message mes1 includes an SMS identifier idmes1, which is used to identify SMS message mes1.

[0115] Before the bulk SMS service receives the SMS message 'mes1' pushed by the application interface, the method may further include:

[0116] If the application programming interface (API) receives a text message generation request req1 from a user client, where req1 carries text message material mat1 (which may include text, images, and / or links used to generate the text message), the API imports mat1 into the already activated text message template mode1 to obtain the text message mes1; and sends a text message generation request response res1 carrying mes1 to the user client. If the API receives a bulk text message sending request req2 from the user client, where req2 carries the text message identifier idmes1, the API pushes the text message mes1 to be sent to the bulk text message sending server.

[0117] The following examples illustrate some SMS filtering appeal mechanisms.

[0118] In some possible implementations, the method may further include:

[0119] The bulk SMS service generates an SMS filtering record P1 when the filtering decision of SMS mes1 is "filtered". The SMS filtering record P1 contains the SMS filtering policy identifier idrule1, the SMS identifier idmes1, and the filtering reason. The SMS filtering policy identifier idrule1 identifies the SMS filtering policy rule1. The bulk SMS service sends an SMS filtering reminder message to the application programming interface (API), which carries the SMS filtering record P1. The API then forwards the SMS filtering reminder message to the user client.

[0120] When the application programming interface (API) receives a filtering appeal request from a user client, the filtering appeal request carries the SMS identifier idmes1 and the reason for the filtering appeal; the API forwards the filtering appeal request to the SMS bulk sending management terminal.

[0121] Upon receiving a filtering appeal request, the front-end presentation layer of the bulk SMS management terminal forwards the request to the administrator client. If it receives a filtering appeal response from the administrator client, and this response carries a successful filtering appeal identifier, the front-end presentation layer of the bulk SMS management terminal sends a filtering exemption instruction to the bulk SMS server. This instruction carries the SMS identifier idmes1, and it indicates that SMS mes1, identified by idmes1, is allowed a filtering exemption. In other words, allowing SMS mes1 a filtering exemption means allowing SMS mes1 to not execute the filtering decision.

[0122] After receiving the filtering exemption instruction, the bulk SMS service calls the SMS channel in the candidate SMS channel resource pool to send the SMS message mes1.

[0123] In some possible implementations, the method may further include: if a filter appeal request response is received from the administrator client in response to the filter appeal request, and the filter appeal request response carries a filter appeal failure identifier, the front-end presentation layer of the SMS bulk sending management terminal forwards the filter appeal request response to the application interface terminal.

[0124] The application programming interface (API) forwards the filtering appeal request response to the user client. If the API receives a text message generation request (req3) from the user client, where req3 carries text message material mat2 (obtained by modifying text message material mat1), the API imports mat2 into the already activated text message template mode1 to obtain text message mes2. Mes2 contains a text message identifier idmes2, which identifies the text message mes2. The API then sends a text message generation request response (res3) to the user client, where req3 carries the text message mes2. If the API receives a bulk text message sending request (req4) from the user client, where req4 carries the text message identifier idmes2, the API pushes the text message mes2 to be sent to the bulk text message sending server.

[0125] The following example illustrates the SMS filtering policy reconfiguration mechanism.

[0126] See Figure 4 , Figure 4 This is a flowchart illustrating another configuration method for a bulk SMS service system provided in this application embodiment. Figure 4 As shown, another embodiment of this application provides a configuration method for a bulk SMS service system, which includes the following:

[0127] 401. The bulk SMS server starts a filter counter add1 and an exemption counter add2 simultaneously with the activation of SMS filtering policy rule1. The filter counter add1 accumulates the number of times an SMS message is filtered by SMS filtering policy rule1. The filter counter add1 also accumulates the number of times an SMS message is exempted from filtering after being filtered by SMS filtering policy rule1. When an SMS filtering record P1 is generated (the generation of an SMS filtering record indicates that the SMS filtering decision failed and the SMS will be filtered), the count value of filter counter add1 is incremented by 1. When a filter exemption instruction is received, the count value of exemption counter add2 is incremented by 1.

[0128] 402. When the count value of filter counter add1 exceeds the threshold th1, and the ratio of the count value of exemption counter add2 to the count value of filter counter add1 exceeds the threshold th2, the SMS bulk sending server sends an SMS filtering policy optimization request to the SMS bulk sending management server. The SMS filtering policy optimization request carries the SMS filtering policy identifier idrule1 and the SMS filtering record set. The SMS filtering record set contains the SMS filtering record P1. Each SMS filtering record in the SMS filtering record set contains the SMS filtering policy identifier idrule1. The number of SMS filtering records contained in the SMS filtering record set is the current count value of filter counter add1.

[0129] The threshold th1 can be set to, for example, 10, 20, 50, 100, 125, 500 or other integers greater than 1.

[0130] The threshold th12 can be set to, for example, 20%, 50%, 60%, 70%, 80%, or other numbers greater than 20% and less than 1.

[0131] It can be understood that the higher the ratio (add2 / add1) of the count value of the exemption counter add2 to the count value of the filter counter add1, the higher the success rate of filtering appeals.

[0132] 403. After receiving the SMS filtering strategy optimization request from the SMS bulk sending server, the front-end display layer of the SMS bulk sending management terminal forwards the SMS filtering strategy optimization request to the administrator client.

[0133] 404. After receiving the SMS filtering policy optimization request, the administrator client can send an SMS filtering policy reconfiguration request to the SMS bulk sending management terminal.

[0134] 405. If the front-end display layer of the SMS bulk messaging management terminal receives an SMS filtering policy reconfiguration request from an administrator client, wherein the SMS filtering policy reconfiguration request carries an SMS filtering policy identifier idrule1; the front-end display layer sends an SMS filtering policy reconfiguration interface to the administrator client in response to the SMS filtering policy reconfiguration request, the SMS filtering policy reconfiguration interface includes N configurable entries, wherein the N configurable entries include configurable entry n1 and configurable entry n2, configurable entry n1 has n11 candidate configuration parameter items, any one of the n11 candidate configuration parameter items can be selected as a configuration parameter item of configurable entry n1, wherein the default configuration parameter item of configurable entry n1 is the configuration parameter item corresponding to configurable entry n1 in SMS filtering policy rule1; configurable entry n2 has custom configuration parameter items, the default configuration parameter item of configurable entry n2 is the configuration parameter item corresponding to configurable entry n2 in SMS filtering policy rule1.

[0135] The default configuration parameters can be displayed on the SMS filtering policy reconfiguration interface. Presenting them as default configuration parameters makes it easier for administrators to intuitively understand what the current configuration parameters of the corresponding configurable entries n1 or n2 in SMS filtering policy rule1 are, thus facilitating targeted modifications by administrators.

[0136] 406. After receiving the SMS filtering policy reconfiguration interface, the administrator client sends an SMS filtering policy reconfiguration completion interface to the SMS bulk sending management terminal.

[0137] It is understandable that administrators can obtain the SMS filtering policy reconfiguration completion interface by operating the SMS filtering policy reconfiguration interface displayed on the administrator client.

[0138] 407. After receiving the SMS filtering policy reconfiguration completion interface sent by the administrator client, the front-end presentation layer extracts the configuration parameter items of the N configurable items that have been configured from the SMS filtering policy reconfiguration completion interface, wherein the SMS filtering policy reconfiguration completion interface includes the N configurable items that have been configured; and sends an SMS filtering policy generation instruction order5 to the service layer of the SMS bulk sending management terminal, wherein the SMS filtering policy generation instruction order5 carries the configuration parameter items of the N configurable items extracted from the SMS filtering policy reconfiguration completion interface.

[0139] 408. The service layer of the SMS bulk sending management terminal imports the configuration parameters of the N configurable entries carried by the SMS filtering strategy generation instruction order5 into the SMS filtering strategy generation model to obtain the SMS filtering strategy rule2, and then passes the SMS filtering strategy rule2 to the front-end display layer.

[0140] 409. After receiving the SMS filtering policy rule2 from the service layer of the SMS bulk sending management terminal, the front-end presentation layer can send an SMS filtering policy activation instruction order6 carrying the SMS filtering policy rule2 to the SMS bulk sending server.

[0141] 410. After receiving the SMS filtering policy activation instruction order6 issued by the SMS bulk sending management terminal, the SMS bulk sending server activates the SMS filtering policy rule2 and deactivates the SMS filtering policy rule1.

[0142] It is understandable that invalid SMS filtering policies (such as SMS filtering policy rule1) will no longer be used in SMS filtering decisions.

[0143] For example, if the bulk SMS service receives a bulk SMS message mes3 pushed by the application interface, it performs a filtering decision on the SMS message mes3 based on the effective SMS filtering policy rule2; if the filtering decision result is not to filter, it calls the SMS channel in the candidate SMS channel resource pool to send the SMS message mes3; if the filtering decision result is to filter, it abandons sending the SMS message mes3.

[0144] It is understood that the steps of the methods in the above embodiments can be combined with each other, either partially or entirely. For example, the SMS filtering policy configuration mechanism, the SMS template configuration scheme, and the SMS filtering policy reconfiguration mechanism can all be combined with each other.

[0145] This application also provides a bulk SMS service system, which may include: a bulk SMS management terminal, a bulk SMS service terminal, and an application programming interface terminal that are interconnected.

[0146] The SMS bulk messaging management terminal includes: a runtime environment layer, a data support layer running on top of the runtime environment layer, a service layer running on top of the data support layer, a gateway layer running on top of the service layer, and a front-end display layer. The gateway layer is used for authenticating administrator clients.

[0147] The front-end display layer of the SMS bulk messaging management terminal is used to send an SMS filtering policy configuration interface to the administrator client in response to the SMS filtering policy configuration request after receiving the request from the administrator client. The SMS filtering policy configuration interface includes N configurable entries, specifically configurable entry n1 and configurable entry n2. Configurable entry n1 has n11 candidate configuration parameters, and any one of these n11 candidate parameters can be selected as a configuration parameter for configurable entry n1. Configurable entry n2 has custom configuration parameters. N and n11 are integers greater than 1.

[0148] The front-end presentation layer is further configured to, after receiving the SMS filtering policy configuration completion interface sent by the administrator client, extract the configuration parameter items of the N configurable items that have been configured from the SMS filtering policy configuration completion interface, wherein the SMS filtering policy configuration completion interface includes the N configurable items that have been configured; and send an SMS filtering policy generation instruction order1 to the service layer of the SMS bulk sending management terminal, wherein the SMS filtering policy generation instruction order1 carries the configuration parameter items of the N configurable items extracted.

[0149] The service layer of the bulk SMS management terminal is used to import the configuration parameters of N configurable items carried by the SMS filtering policy generation instruction order1 into the SMS filtering policy generation model to obtain the SMS filtering policy rule1, and pass the SMS filtering policy rule1 to the front-end display layer; the front-end display layer sends the SMS filtering policy activation instruction order2, which carries the SMS filtering policy rule1, to the bulk SMS service terminal.

[0150] The bulk SMS service is configured to: activate the SMS filtering policy rule1 upon receiving the SMS filtering policy activation instruction order2 from the bulk SMS management terminal; if it obtains an SMS message mes1 to be sent from the application interface terminal, it performs a filtering decision on the SMS message mes1 based on the activated SMS filtering policy rule1; wherein, if the filtering decision result is no filtering, it calls the SMS channel in the candidate SMS channel resource pool to send the SMS message mes1; if the filtering decision result is filtering, it abandons sending the SMS message mes1.

[0151] In some possible implementations, the front-end presentation layer of the bulk SMS management terminal is further configured to: receive an SMS template configuration request from an administrator client; and send an SMS template configuration interface to the administrator client in response to the SMS template configuration request. The SMS template configuration interface includes M configurable entries, wherein the M configurable entries include: configurable entry m1 and configurable entry m2. Configurable entry m1 has m11 candidate configuration parameter items, and any one of the m11 candidate configuration parameter items can be selected as a configuration parameter item for configurable entry m1. Configurable entry m2 has custom configuration parameter items. M and m11 are integers greater than 1.

[0152] The front-end presentation layer is further configured to, after receiving the SMS template configuration completion interface sent by the administrator client, extract the configuration parameter items of the configured M configurable items from the SMS template configuration completion interface, wherein the SMS template configuration completion interface includes the configured M configurable items; and send an SMS template generation instruction order3 to the service layer of the SMS bulk sending management terminal; the SMS template generation instruction order3 carries the extracted configuration parameter items of the M configurable items.

[0153] The service layer of the SMS bulk messaging management terminal is further configured to, upon receiving the SMS template generation instruction order3 from the front-end display layer, import the configuration parameters of the M configurable items carried by the SMS template generation instruction order3 into the SMS template generation model to obtain the SMS template mode1, and pass the SMS template mode1 to the front-end display layer; the front-end display layer sends an SMS template activation instruction order4 carrying the SMS template mode1 to the application interface terminal.

[0154] The application programming interface is also used to activate the SMS template mode1 after receiving the SMS template activation instruction order4 issued by the SMS bulk sending management terminal.

[0155] In some possible implementations,

[0156] The SMS message mes1 contains an SMS identifier idmes1, which is used to identify the SMS message mes1.

[0157] The application programming interface (API) is further configured to, before the bulk SMS service receives the SMS message mes1 to be sent by the API, if it receives an SMS generation request req1 sent by the user client, the SMS generation request req1 carrying SMS material mat1, import the SMS material mat1 into the already activated SMS template mode1 to obtain the SMS message mes1; send an SMS generation request response res1 carrying the SMS message mes1 to the user client; if it receives a bulk SMS sending request req2 sent by the user client, the bulk SMS sending request req2 carrying the SMS identifier idmes1, and push the SMS message mes1 to be sent to the bulk SMS service.

[0158] In some possible implementations,

[0159] The bulk SMS service is further configured to generate an SMS filtering record P1 if the filtering decision result of the SMS mes1 is "filtered". The SMS filtering record P1 contains the SMS identifier idmes1, the filtering reason, and the SMS filtering policy identifier idrule1. The SMS filtering policy identifier idrule1 is used to identify the SMS filtering policy rule1. The service also sends an SMS filtering reminder message to the application interface, and the SMS filtering reminder message carries the SMS filtering record P1.

[0160] The application programming interface is also used to forward the SMS filtering reminder message to the user client; when a filtering appeal request is received from the user client, the filtering appeal request carries the SMS identifier idmes1 and the reason for the filtering appeal; and forward the filtering appeal request to the SMS bulk sending management terminal.

[0161] The front-end display layer of the bulk SMS management terminal is also used to forward the filtering appeal request to the administrator client after receiving the filtering appeal request; if a filtering appeal request response is received from the administrator client in response to the filtering appeal request, and the filtering appeal request response carries a filtering appeal success identifier, a filtering exemption instruction is sent to the bulk SMS server, the filtering exemption instruction carries the SMS identifier idmes1, and the filtering exemption instruction is used to indicate that the SMS mes1 identified by the SMS identifier idmes1 is allowed to be filtered exempted.

[0162] The bulk SMS service is also used to send the SMS message mes1 by calling the SMS channel in the candidate SMS channel resource pool after receiving the filtering exemption instruction.

[0163] In some possible implementations, the front-end presentation layer of the SMS bulk messaging management terminal is also used to forward the filter appeal request response to the application interface terminal if it receives a filter appeal request response from the administrator client, which is used to respond to the filter appeal request request and the filter appeal request response carries a filter appeal failure identifier.

[0164] The application programming interface (API) is also used to forward filtering appeal request responses to user clients; if it receives a text message generation request req3 from a user client, the text message generation request req3 carries text message material mat2, which is obtained by modifying text message material mat1, and imports the text message material mat2 into the already effective text message template mode1 to obtain the text message mes2, the text message mes2 contains a text message identifier idmes2, the text message identifier idmes2 is used to identify the text message mes2; a text message generation request response res3 is sent to the user client, the text message generation request response res3 carries the text message mes2; if it receives a mass text message sending request req4 from the user client, the mass text message sending request req4 carries the text message identifier idmes2, and pushes the text message mes2 to be sent to the mass text message sending server.

[0165] In some possible implementations, the bulk SMS server is further configured to: simultaneously activate a filter counter add1 and an exemption counter add2 when the SMS filtering policy rule1 takes effect; the filter counter add1 is used to accumulate the number of times an SMS is filtered by SMS filtering policy rule1; the filter counter add1 is used to accumulate the number of times an SMS is exempted from filtering after being filtered by SMS filtering policy rule1; the count value of filter counter add1 is incremented by 1 when the SMS filtering record P1 is generated; the count value of exemption counter add2 is incremented by 1 when the filter exemption instruction is received; when the count value of filter counter add1 exceeds a threshold th1, and the ratio of the count value of exemption counter add2 to the count value of filter counter add1 exceeds a threshold th2, a bulk SMS server sends an SMS filtering policy optimization request to the bulk SMS management terminal, wherein the SMS filtering policy optimization request carries an SMS filtering policy identifier idrule1 and an SMS filtering record set, the SMS filtering record set contains the SMS filtering record P1, each SMS filtering record in the SMS filtering record set contains the SMS filtering policy identifier idrule1, and the number of SMS filtering records contained in the SMS filtering record set is the current count value of filter counter add1.

[0166] The front-end display layer of the bulk SMS management terminal is also used to forward the SMS filtering strategy optimization request to the administrator client after receiving the SMS filtering strategy optimization request from the bulk SMS server. If a reconfiguration request for SMS filtering policy is received from an administrator client, the request carries an SMS filtering policy identifier idrule1. An SMS filtering policy reconfiguration interface is sent to the administrator client in response to the request. This interface includes N configurable entries, specifically configurable entry n1 and configurable entry n2. Configurable entry n1 has n11 candidate configuration parameters, and any one of these n11 can be selected as a configuration parameter for configurable entry n1. The default configuration parameter for configurable entry n1 is the corresponding configuration parameter in SMS filtering policy rule1. Configurable entry n2 has custom configuration parameters, and its default configuration parameter is the corresponding configuration parameter in SMS filtering policy rule1. After receiving the SMS filtering policy reconfiguration completion interface sent by the administrator client, the configuration parameter items of the N configurable entries that have been configured are extracted from the SMS filtering policy reconfiguration completion interface, wherein the SMS filtering policy reconfiguration completion interface includes the N configurable entries that have been configured; and an SMS filtering policy generation instruction order5 is sent to the service layer of the SMS bulk sending management terminal, wherein the SMS filtering policy generation instruction order5 carries the configuration parameter items of the N configurable entries extracted from the SMS filtering policy reconfiguration completion interface.

[0167] The service layer of the bulk SMS management terminal is also used to import the configuration parameters of the N configurable entries carried by the SMS filtering strategy generation instruction order5 into the SMS filtering strategy generation model to obtain the SMS filtering strategy rule2, and to pass the SMS filtering strategy rule2 to the front-end presentation layer.

[0168] The front-end presentation layer is also used to send an SMS filtering policy activation instruction order6, carrying SMS filtering policy rule2, to the SMS bulk sending server.

[0169] The bulk SMS server is also configured to, upon receiving the SMS filtering policy activation instruction order6 issued by the bulk SMS management terminal, activate the SMS filtering policy rule2 and deactivate the SMS filtering policy rule1.

[0170] The implementation methods of the functions of each entity in the bulk SMS service system can be found in the relevant descriptions in the method embodiments, and will not be repeated here.

[0171] The following are some examples of implementation methods for related communication equipment.

[0172] Please see Figure 5 , Figure 5 This is a schematic diagram of the communication device provided in an embodiment of this application. For example... Figure 5 As shown, a communication device may include: a processor 510 and a memory 520;

[0173] The processor 510 is used to call the program stored in the memory 520 to execute some or all of the operations performed by the SMS bulk sending server, SMS bulk sending management terminal or application programming interface terminal in the method embodiment.

[0174] This application also provides a computer-readable storage medium storing a computer program that, when executed by a computer, can implement some or all of the steps of any of the methods provided in this application.

[0175] This application also provides a computer program that, when executed by a computer, can implement some or all of the steps of any of the methods provided in this application.

[0176] In the above embodiments, the descriptions of each embodiment have different focuses. For parts not described in detail in a certain embodiment, please refer to the relevant descriptions of other embodiments.

[0177] In the several embodiments provided in this application, it should be understood that the disclosed apparatus can be implemented in other ways. For example, the apparatus embodiments described above are merely illustrative; for instance, the division of units is only a logical functional division, and in actual implementation, there may be other division methods. For example, multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed. Furthermore, the coupling or direct coupling or communication connection shown or discussed may be through some interfaces; the indirect coupling or communication connection between devices or units may be electrical or other forms.

[0178] The units described as separate components may or may not be physically separate. The components shown as units may or may not be physical units; that is, they may be located in one place or distributed across multiple network units. Some or all of the units can be selected to achieve the purpose of this embodiment according to actual needs.

[0179] Furthermore, the functional units in the various embodiments of this application can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit. The integrated unit can be implemented in hardware or as a software functional unit.

[0180] If the integrated unit is implemented as a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the prior art, or all or part of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute all or part of the steps of the methods described in the various embodiments of this application. The aforementioned storage medium may include, for example, various media capable of storing program code, such as: USB flash drive, read-only memory (ROM), random access memory (RAM), portable hard drive, magnetic disk, or optical disk.

[0181] In summary, the above embodiments are only used to illustrate the technical solutions of this application, and are not intended to limit it. Although this application has been described in detail with reference to the foregoing embodiments, those skilled in the art should understand that modifications can still be made to the technical solutions described in the foregoing embodiments, or equivalent substitutions can be made to some of the technical features. Such modifications or substitutions do not cause the essence of the corresponding technical solutions to deviate from the scope of the technical solutions of the embodiments of this application.

Claims

1. A configuration method for a bulk SMS service system, characterized in that, The bulk SMS service system includes: a bulk SMS management terminal, a bulk SMS service terminal, and an application programming interface terminal that are interconnected. The method includes: after receiving an SMS filtering policy configuration request from an administrator client, the front-end display layer of the SMS bulk messaging management terminal sends an SMS filtering policy configuration interface to the administrator client in response to the SMS filtering policy configuration request. The SMS filtering policy configuration interface includes N configurable entries, including configurable entry n1 and configurable entry n2. Configurable entry n1 has n11 candidate configuration parameter items, and any one of the n11 candidate configuration parameter items can be selected as a configuration parameter item for configurable entry n1. Configurable entry n2 has custom configuration parameter items. N and n11 are integers greater than 1. After receiving the SMS filtering policy configuration completion interface sent by the administrator client, the front-end presentation layer extracts the configuration parameter items of the N configurable items that have been configured from the SMS filtering policy configuration completion interface. The SMS filtering policy configuration completion interface includes the N configurable items that have been configured. The front-end presentation layer then sends an SMS filtering policy generation instruction order1 to the service layer of the SMS bulk sending management terminal. The SMS filtering policy generation instruction order1 carries the configuration parameter items of the N configurable items that have been extracted. The service layer of the bulk SMS management terminal imports the configuration parameters of the N configurable entries carried by the SMS filtering policy generation instruction order1 into the SMS filtering policy generation model to obtain the SMS filtering policy rule1, and passes the SMS filtering policy rule1 to the front-end display layer; the front-end display layer sends the SMS filtering policy activation instruction order2, which carries the SMS filtering policy rule1, to the bulk SMS service terminal. After receiving the SMS filtering policy activation instruction order2 from the SMS bulk sending management terminal, the SMS bulk sending server activates the SMS filtering policy rule1. If it obtains an SMS message mes1 to be sent from the application interface, it performs a filtering decision on the SMS message mes1 based on the activated SMS filtering policy rule1. If the filtering decision result is no filtering, it calls the SMS channel in the candidate SMS channel resource pool to send the SMS message mes1. If the filtering decision result is filtering, it abandons sending the SMS message mes1.

2. The method according to claim 1, characterized in that, The method includes: the front-end display layer of the SMS bulk messaging management terminal receiving an SMS template configuration request from the administrator client; The front-end presentation layer sends an SMS template configuration interface to the administrator client in response to the SMS template configuration request. The SMS template configuration interface includes M configurable entries, including configurable entry m1 and configurable entry m2. Configurable entry m1 has m11 candidate configuration parameter items, and any one of the m11 candidate configuration parameter items can be selected as a configuration parameter item for configurable entry m1. Configurable entry m2 has custom configuration parameter items. M and m11 are integers greater than 1. After receiving the SMS template configuration completion interface sent by the administrator client, the front-end presentation layer extracts the configuration parameter items of the M configurable items that have been configured from the SMS template configuration completion interface, wherein the SMS template configuration completion interface includes the M configurable items that have been configured; the front-end presentation layer sends an SMS template generation command order3 to the service layer of the SMS bulk sending management terminal; the SMS template generation command order3 carries the configuration parameter items of the extracted M configurable items; After receiving the SMS template generation instruction order3 from the front-end display layer, the service layer of the SMS bulk sending management terminal imports the configuration parameters of the M configurable items carried by the SMS template generation instruction order3 into the SMS template generation model to obtain the SMS template mode1, and passes the SMS template mode1 to the front-end display layer; the front-end display layer sends the SMS template activation instruction order4 carrying the SMS template mode1 to the application interface terminal. The application programming interface (API) activates the SMS template mode1 after receiving the SMS template activation command order4 from the SMS bulk messaging management terminal.

3. The method according to claim 2, characterized in that, The SMS message mes1 includes an SMS identifier idmes1, which is used to identify the SMS message mes1; wherein, before the bulk SMS service receives the SMS message mes1 to be sent from the application interface, the method further includes: If the application interface receives a text message generation request req1 sent by the user client, and the text message generation request req1 carries text message material mat1, the text message material mat1 is imported into the already activated text message template mode1 to obtain the text message mes1; and a text message generation request response res1 carrying the text message mes1 is sent to the user client. If the application programming interface (API) receives a bulk SMS request req2 from the user client, and the bulk SMS request req2 carries the SMS identifier idmes1, the API will push the SMS mes1 to be sent to the bulk SMS server.

4. The method according to claim 3, characterized in that, The method includes: the bulk SMS sending server generating an SMS filtering record P1 when the filtering decision result of the SMS mes1 is filtered, wherein the SMS filtering record P1 records the SMS identifier idmes1, the filtering reason, and the SMS filtering policy identifier idrule1, wherein the SMS filtering policy identifier idrule1 is used to identify the SMS filtering policy rule1; the bulk SMS sending server sending an SMS filtering reminder message to the application programming interface (API), wherein the SMS filtering reminder message carries the SMS filtering record P1, and the API forwarding the SMS filtering reminder message to the user client; When the application programming interface (API) receives a filtering appeal request from a user client, the filtering appeal request carries the SMS identifier idmes1 and the reason for the filtering appeal; the API forwards the filtering appeal request to the SMS bulk sending management terminal. After receiving a filtering appeal request, the front-end presentation layer of the bulk SMS management terminal forwards the filtering appeal request to the administrator client. If it receives a filtering appeal request response from the administrator client, and the filtering appeal request response carries a filtering appeal success identifier, the front-end presentation layer of the bulk SMS management terminal sends a filtering exemption instruction to the bulk SMS server. The filtering exemption instruction carries the SMS identifier idmes1, and the filtering exemption instruction is used to indicate that the SMS mes1 identified by the SMS identifier idmes1 is allowed to be filtered exempted. After receiving the filtering exemption instruction, the bulk SMS service calls the SMS channel in the candidate SMS channel resource pool to send the SMS message mes1.

5. The method according to claim 4, characterized in that, The method further includes: if a filter appeal request response is received from the administrator client in response to the filter appeal request, and the filter appeal request response carries a filter appeal failure identifier, the front-end display layer of the SMS bulk sending management terminal forwards the filter appeal request response to the application interface terminal. The application programming interface (API) forwards the filtering appeal request response to the user client. If the API receives a text message generation request (req3) from the user client, where req3 carries text message material mat2 (obtained by modifying text message material mat1), the API imports mat2 into the already activated text message template mode1 to obtain text message mes2. Mes2 contains a text message identifier idmes2, which identifies the text message mes2. The API then sends a text message generation request response (res3) to the user client, where req3 carries the text message mes2. If the API receives a bulk text message sending request (req4) from the user client, where req4 carries the text message identifier idmes2, the API pushes the text message mes2 to be sent to the bulk text message sending server.

6. The method according to claim 4 or 5, characterized in that, The method further includes: the SMS bulk sending server starts a filter counter add1 and an exemption counter add2 simultaneously with the SMS filtering policy rule1 taking effect, wherein the filter counter add1 is used to accumulate the number of times SMS messages are filtered by SMS filtering policy rule1; the exemption counter add2 is used to accumulate the number of times SMS messages are exempted from filtering after being filtered by SMS filtering policy rule1; the count value of filter counter add1 is incremented by 1 when the SMS filtering record P1 is generated; and the count value of exemption counter add2 is incremented by 1 when the filtering exemption instruction is received. When the count value of the filter counter add1 exceeds the threshold th1, and the ratio of the count value of the exemption counter add2 to the count value of the filter counter add1 exceeds the threshold th2, the SMS bulk sending server sends an SMS filtering policy optimization request to the SMS bulk sending management server. The SMS filtering policy optimization request carries the SMS filtering policy identifier idrule1 and the SMS filtering record set. The SMS filtering record set contains the SMS filtering record P1. Each SMS filtering record in the SMS filtering record set contains the SMS filtering policy identifier idrule1. The number of SMS filtering records contained in the SMS filtering record set is the current count value of the filter counter add1. After receiving the SMS filtering policy optimization request from the SMS bulk sending server, the front-end display layer of the SMS bulk sending management terminal forwards the SMS filtering policy optimization request to the administrator client. If the front-end display layer of the SMS bulk messaging management terminal receives an SMS filtering policy reconfiguration request from an administrator client, wherein the SMS filtering policy reconfiguration request carries an SMS filtering policy identifier idrule1; the front-end display layer sends an SMS filtering policy reconfiguration interface to the administrator client in response to the SMS filtering policy reconfiguration request. The SMS filtering policy reconfiguration interface includes N configurable entries, wherein the N configurable entries include configurable entry n1 and configurable entry n2. Configurable entry n1 has n11 candidate configuration parameter items, and any one of the n11 candidate configuration parameter items can be selected as a configuration parameter item for configurable entry n1. The default configuration parameter item for configurable entry n1 is the configuration parameter item corresponding to configurable entry n1 in SMS filtering policy rule1. Configurable entry n2 has custom configuration parameter items, and the default configuration parameter item for configurable entry n2 is the configuration parameter item corresponding to configurable entry n2 in SMS filtering policy rule1. After receiving the SMS filtering policy reconfiguration completion interface sent by the administrator client, the front-end presentation layer extracts the configuration parameter items of the N configurable items that have been configured from the SMS filtering policy reconfiguration completion interface, wherein the SMS filtering policy reconfiguration completion interface includes the N configurable items that have been configured; and sends an SMS filtering policy generation instruction order5 to the service layer of the SMS bulk sending management terminal, wherein the SMS filtering policy generation instruction order5 carries the configuration parameter items of the N configurable items extracted from the SMS filtering policy reconfiguration completion interface. The service layer of the bulk SMS management terminal imports the configuration parameters of the N configurable items carried by the SMS filtering strategy generation instruction order5 into the SMS filtering strategy generation model to obtain the SMS filtering strategy rule2, and passes the SMS filtering strategy rule2 to the front-end display layer; the front-end display layer sends the SMS filtering strategy activation instruction order6 carrying the SMS filtering strategy rule2 to the bulk SMS service terminal. After receiving the SMS filtering policy activation instruction order6 from the SMS bulk sending management terminal, the SMS bulk sending server activates the SMS filtering policy rule2 and deactivates the SMS filtering policy rule1.

7. A bulk SMS service system, characterized in that, include: The SMS bulk messaging management terminal, SMS bulk messaging server, and application programming interface are interconnected and communicate with each other. The front-end display layer of the SMS bulk messaging management terminal is used to send an SMS filtering policy configuration interface to the administrator client in response to the SMS filtering policy configuration request after receiving the request. The SMS filtering policy configuration interface includes N configurable entries, specifically configurable entry n1 and configurable entry n2. Configurable entry n1 has n11 candidate configuration parameters, and any one of these n11 candidate parameters can be selected as a configuration parameter for configurable entry n1. Configurable entry n2 has custom configuration parameters. N and n11 are integers greater than 1. The front-end presentation layer is further configured to, after receiving the SMS filtering policy configuration completion interface sent by the administrator client, extract the configuration parameter items of the N configurable items that have been configured from the SMS filtering policy configuration completion interface, the SMS filtering policy configuration completion interface including the N configurable items that have been configured; and send an SMS filtering policy generation instruction order1 to the service layer of the SMS bulk sending management terminal, the SMS filtering policy generation instruction order1 carrying the configuration parameter items of the N configurable items extracted. The service layer of the bulk SMS management terminal is used to import the configuration parameters of N configurable items carried by the SMS filtering policy generation instruction order1 into the SMS filtering policy generation model to obtain the SMS filtering policy rule1, and pass the SMS filtering policy rule1 to the front-end display layer; the front-end display layer sends the SMS filtering policy activation instruction order2, which carries the SMS filtering policy rule1, to the bulk SMS service terminal. The bulk SMS service is configured to: activate the SMS filtering policy rule1 upon receiving the SMS filtering policy activation instruction order2 from the bulk SMS management terminal; if it obtains an SMS message mes1 to be sent from the application interface terminal, it performs a filtering decision on the SMS message mes1 based on the activated SMS filtering policy rule1; wherein, if the filtering decision result is no filtering, it calls the SMS channel in the candidate SMS channel resource pool to send the SMS message mes1; if the filtering decision result is filtering, it abandons sending the SMS message mes1.

8. A communication device, characterized in that, include: Processor and memory; The processor is used to invoke the computer program stored in the memory to perform some or all of the operations performed by the SMS bulk messaging server, SMS bulk messaging management terminal, or application programming interface in any one of the methods of claims 1 to 6.

9. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores a computer program that, when executed by a computer, can perform some or all of the operations performed by the SMS bulk messaging server, SMS bulk messaging management terminal, or application programming interface in any one of the methods of claims 1 to 6.

10. A computer program product, characterized in that, When the computer program contained in the computer program product is executed by a computer, it can perform some or all of the operations performed by the SMS bulk sending server, SMS bulk sending management terminal, or application programming interface terminal in any one of the methods of claims 1 to 6.

Images