WO2017152765A1

WO2017152765A1 - Automatic fusing-based message sending method, device and system

Info

Publication number: WO2017152765A1
Application number: PCT/CN2017/074622
Authority: WO
Inventors: 胡晶晶
Original assignee: 阿里巴巴集团控股有限公司; 胡晶晶
Priority date: 2016-03-10
Filing date: 2017-02-23
Publication date: 2017-09-14
Also published as: TWI678086B; TW201733312A; CN107181664B; CN107181664A

Abstract

The present application relates to the technical field of communications, and in particular, to an automatic fusing-based message sending method, device and system. The method comprises: receiving a message sending request and obtaining features in the message sending request; performing a blacklist check according to the features; and sending a corresponding message after the message passes the blacklist check, and generating a log about the current message sending according to the features. By asynchronously analyzing a log and adding feature data that exceeds a threshold value to a blacklist, logic control on messages sent to a user can be implemented, such that the messages do not disturb the user; moreover, the sent message processing speed of a message processing system is improved.

Description

Automatic melting message sending method, device and system

Technical field

The present application relates to the field of communications technologies, and in particular, to a method, an apparatus, and a system for automatically transmitting a message.

Background technique

With the development of Internet technology, users will generate a lot of messages after trading on the electronic trading platform. The electronic trading platform sends the message to the user, for example, the mail notifies the transaction result, and the short message informs whether the payment is successful, but if it is short through some channel Sending a large number of messages to the user during the time is likely to cause blocking of the notification channel of the user. For example, the notification channel is a mailbox, and the user's mailbox receives a large amount of messages in a short time, which may cause the mailbox capacity to overflow or the important mail of the user to be drowned in a large number of notifications. In the message, this will affect the user's normal use of the mailbox.

In the prior art, the number of such messages is generally counted by counting every time a message is sent, and the sending of the message is cancelled if the number of transmissions exceeds the threshold. However, due to the large number of target users of the message, the notification channels used by the user are various. The system needs to perform the counting operation in the database every time the message is sent, so that the data write concurrency is large, which affects the system to send messages. Processing efficiency.

Summary of the invention

In order to solve the problem that the message processing system sends messages in the prior art is not efficient, and if a certain type of message is sent to cause harassment to the user, an automatic fuse message sending method, device and system can improve the sending. The efficiency of the message and the harassment of users by similar messages.

An embodiment of the present application provides an automatic fuse message sending method, including

Receiving a request to send a message, and obtaining a feature in the request for sending the message;

Performing a blacklist check according to the feature;

After the blacklist is verified, a corresponding message is sent, and a log of the current sent message is generated according to the feature.

The embodiment of the present application further provides an automatic fuse message sending method, including

Synchronize the log of the message processing system;

Accumulating the number of identical feature messages according to the log;

Determine whether the quantity exceeds the quantity threshold, and if it exceeds, add the feature to the blacklist.

The embodiment of the present application further provides an automatic fuse message processing apparatus, including

a receiving unit, configured to receive a request for sending a message, and obtain a feature in the request for sending the message;

a verification unit, configured to perform blacklist verification according to the feature;

The processing unit is configured to: after the blacklist is verified, send a corresponding message, and generate a log of the current sending message according to the feature.

The embodiment of the present application further provides an automatic fuse breaking accounting device, including

a synchronization unit for synchronizing logs of the message processing system;

a calculating unit, configured to accumulate the number of messages having the same feature according to the log;

The processing unit is configured to determine whether the quantity exceeds a quantity threshold, and if yes, add the feature to the blacklist.

The embodiment of the present application further provides an automatic fuse message processing system, including a message processing device and a billing device.

The message processing apparatus is configured to receive a request for sending a message, and obtain a feature in the request for sending the message, perform blacklist verification according to the feature, and send a corresponding message after being verified by the blacklist, and according to the The feature generates a log of the current sent message;

The accounting device is configured to synchronize the logs of the message processing system, and according to the number of the same feature messages accumulated in the log, determine whether the quantity exceeds a quantity threshold, and if yes, add the feature to the blacklist.

It can be seen that the technical solution provided by the embodiment of the present application can implement logical control on a message sent to a user, and if the sent message is in a blacklist, the message is not sent, thereby avoiding message harassment to the user; The processing speed at which the message processing system sends messages.

Of course, any product or method that implements this application does not necessarily need to achieve the above. All the advantages described.

DRAWINGS

In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the drawings to be used in the embodiments or the prior art description will be briefly described below. Obviously, the drawings in the following description are only It is a few embodiments described in the present application, and other drawings can be obtained from those skilled in the art without any inventive labor.

1 is an overall flowchart of a method for transmitting a message in the prior art;

2 is a flowchart of a method for sending an automatic fuse message according to an embodiment of the present application;

FIG. 3 is a flowchart of a method for sending an automatic fuse message according to an embodiment of the present application;

4 is a schematic structural diagram of an automatic fuse message processing apparatus according to an embodiment of the present application;

FIG. 5 is a schematic structural diagram of an automatic fuse billing apparatus according to an embodiment of the present application; FIG.

FIG. 6 is a schematic structural diagram of an automatic fuse message processing system according to an embodiment of the present application;

FIG. 7 is a specific flowchart of an automatic fuse message processing system in processing a message according to an embodiment of the present application;

FIG. 8 is a specific flowchart of an automatic fuse message processing system in processing a message according to an embodiment of the present application.

detailed description

The embodiment of the present application provides a method, an apparatus, and a system for automatically transmitting a message.

The technical solutions in the embodiments of the present application are clearly and completely described in the following, in which the technical solutions in the embodiments of the present application are clearly and completely described. The embodiments are only a part of the embodiments of the present application, and not all of them. All other embodiments obtained by a person of ordinary skill in the art based on the embodiments of the present application without departing from the inventive scope shall fall within the scope of the application.

As shown in FIG. 1 , it is an overall flowchart of a message sending method in the prior art. In the prior art, the steps of counting the number of statistical messages and determining whether to send or not are all processed in the message processing system, thereby causing the efficiency of message sending. Low problem.

The foregoing prior art specifically includes the service system initiating a message request to the message processing system, and performing a pre-check and a blacklist check on the sending message request in the message processing system, wherein the blacklist check refers to determining Whether the message (channel + service information) sent this time belongs to the blacklist. If the blacklist indicates that the service information sent through the channel has exceeded the threshold, it has already affected the user. After passing the blacklist check, it is necessary to determine whether the message to be sent and the previous send record have an impact on the user, that is, the query for the number of sent messages and the number of schools described in the figure. If the verification of the number of sent messages mentioned above is passed, the calling gateway sends the current message; finally, the current sending message is recorded in the accounting system, that is, 1 is added to the sending message record in the accounting system.

FIG. 2 is a flowchart of a method for sending an automatic fuse message according to an embodiment of the present application, where the workflow in the message processing system is described, and the message processing in the present application is compared with the prior art. The system does not perform the steps of querying, verifying, accounting, etc. of the sent message, but merely determining whether to send the message by verifying the blacklist, simplifying the message sending process, and completing the control by the accounting system to operate the blacklist. The purpose of sending a message is to reduce the interruption of the same type of message to the user, and avoid the problem that the user's notification channel is blocked by sending a large number of messages to the user through the same notification channel.

Specifically, the method includes the following steps: Step 201: Receive a message request, and obtain a feature in the message request.

Step 202: Perform blacklist verification according to the feature.

Step 203: After the blacklist is verified, the corresponding message is sent, and a log of the current sent message is generated according to the feature.

As an embodiment of the present application, the sending a message request includes at least:

Channels and business information for sending messages;

Or, the target user and business information of the message.

The channel for sending the message includes the mobile phone number, email address, and client of the target user. Etc., wherein the mobile phone number is used to send a short message to the user, and the email address is used to send a mail to the user, and the client is used to send a notification message to the client of the user, for example, to send a payment success message to the Alipay client of the user smart terminal.

The service information includes a service type, and may also include information such as a service message content, where the service message content is, for example, “Your XXXX order payment is successful”, “Your XXX order is successfully transferred”, and the service type may be, for example, a payment. Successful (or failed) messages, successful (or failed) messages, notification messages for goods have been shipped, etc. These business information can be determined by channel, for example, when the channel is a mobile number, the business information may be Only simple text information is included. When the channel is an email address, the business information may include multimedia content such as text and images.

As an embodiment of the present application, when the request for sending a message includes the target user and the service information, the method for obtaining the request for sending the message further includes: analyzing the channel for sending the message according to the target user information.

Wherein, when the request for sending a message does not include a channel, then the target user needs to be included. Since a user may have multiple channels of communication, it may include a mobile phone number, an email address, a client terminal, etc., and which channel is used to send the message. The selection can be judged according to various conditions. For example, if most of the user's login operation is performed on the client on the mobile phone, the notification message can be selected to be sent by the client, and if the user browses the product, the operation is through the computer. If you are done, you can choose SMS or email to send a message. Just specify which user (target user) to send the message to.

As an embodiment of the present application, performing blacklist verification according to the feature further includes determining whether the feature exists in the blacklist, and if not, transmitting the message.

The feature includes at least a channel and a service type, and may also include time information of the sent message.

As an embodiment of the present application, the log includes at least a channel and a service type for sending a message.

The log may further include time information for sending a message, and the log may be stored locally in the message processing device.

The foregoing channel may be in the form of an alphabetic string or a numeric string, or may also be a string composed of a mixture of letters and numbers, the business information may be a code of a business type, and the code of the business type may identify a service type. Convert to specific text information when sent to the user.

The method of the embodiment of the present application can implement logical control on a message sent to a user. If the sent message is in a blacklist, the message is not sent, thereby avoiding message harassment to the user; and the message processing system is improved. The processing speed of sending messages.

FIG. 3 is a flowchart of a method for sending an automatic fuse message according to an embodiment of the present application. The workflow of the accounting system is mainly described in the figure. The method is to separate the processing log from the message processing system. For the purpose of improving the efficiency of message transmission, the method in the accounting system is combined with the method of the embodiment shown in FIG. 2 to complete the control message transmission, so as to avoid sending too much information of the same service type to the user through the same channel.

Specifically, the method includes the step 301 of synchronizing the log of the message processing system.

Step 302: Accumulate the number of identical feature messages according to the log.

Step 303: Determine whether the quantity exceeds a quantity threshold, and if yes, add the feature to the blacklist.

As an embodiment of the present application, the feature includes at least a channel for transmitting a message and a type of service.

As an embodiment of the present application, the feature further includes time information of the sent message.

As an embodiment of the present application, determining whether the quantity exceeds a predetermined threshold further includes determining whether the quantity exceeds a quantity threshold within a certain time, and if yes, adding the feature to a blacklist.

If the number of the same service message sent to the user through the same channel exceeds a certain threshold within a certain period of time, the situation is considered to be interference to the user, for example, sending the message to the user by using the short message of the mobile phone within 1 minute. If the number of successful payment messages exceeds 10, it is considered that this situation is a disturbance to the user. If more than 10 messages are sent to the user through the short message of the mobile phone within one hour, the situation is considered not to be the case. Belong to the user Interference.

As an embodiment of the present application, the method further includes: determining time information of the feature in the blacklist, and if the interval between the time information and the current time exceeds a time threshold, deleting the feature from the blacklist .

The blacklist is updated at a time. When a certain type of service information sent through a certain channel does not appear for a certain period of time, it indicates that the type of service information sent through the channel does not interfere with the user. This information should be allowed to continue to be sent, rather than always blocking the transmission of such information.

Through the method of the foregoing embodiment, the log of the sent message can be recorded in an asynchronous manner, and the log is analyzed and the blacklist is updated in a billing system independent of the message processing system, so that only the message processing system sends the message. It is necessary to judge the blacklist, which improves the processing efficiency of the message processing system to send messages.

FIG. 4 is a schematic structural diagram of an automatic fuse message processing apparatus according to an embodiment of the present application. The apparatus may be configured by using a logic circuit or a special chip (for example, an FPGA), or implemented by an existing high performance computer, wherein Some of the functional units may be implemented by one hardware device alone, or several functional units may be implemented by one or more hardware devices, including:

The receiving unit 401 is configured to receive a request for sending a message, and obtain a feature in the request for sending the message.

The verification unit 402 is configured to perform blacklist verification according to the feature.

The processing unit 403 is configured to: after the blacklist is verified, send a corresponding message, and generate a log of the current sent message according to the feature.

Channels and business information for sending messages;

Or, the target user and business information of the message.

As an embodiment of the present application, the receiving unit is further configured to analyze, according to the target user information, a channel for sending a message.

As an embodiment of the present application, the checking unit is further configured to determine whether the feature exists in the blacklist, and if not, send the message.

FIG. 5 is a schematic structural diagram of an automatic fuse billing apparatus according to an embodiment of the present application. The apparatus may be formed by using a logic circuit or a special chip (for example, an FPGA), or implemented by an existing high performance computer, wherein Some of the functional units may be implemented by one hardware device alone, or several functional units may be implemented by one or more hardware devices, including:

The synchronization unit 501 is configured to synchronize the logs of the message processing system.

The calculating unit 502 is configured to accumulate the number of the same feature message according to the log.

The processing unit 503 is configured to determine whether the quantity exceeds a quantity threshold, and if yes, add the feature to the blacklist.

As an embodiment of the present application, the processing unit is further configured to determine whether the quantity exceeds a quantity threshold within a certain time, and if yes, add the feature to a blacklist.

As an embodiment of the present application, the method further includes an updating unit 504, determining time information of features in the blacklist, and if the interval between the time information and the current time exceeds a time threshold, the feature is from the black Remove from the list.

FIG. 6 is a schematic structural diagram of an automatic fuse message processing system according to an embodiment of the present application, and the message processing apparatus and the accounting apparatus in the embodiment shown in FIG. 4 and FIG. 5 are included in the figure, wherein:

The message processing device 601 is configured to receive a request for sending a message, and obtain a feature in the request for sending the message, perform blacklist verification according to the feature, and send a corresponding message after verifying by using the blacklist, and according to the The feature generates a log of the message sent this time;

The accounting device 602 is configured to synchronize the logs of the message processing system, and according to the number of the same feature messages accumulated in the log, determine whether the quantity exceeds a quantity threshold, and if yes, add the feature to the blacklist.

The system in this embodiment may be provided with each functional unit or an additional functional unit in the foregoing apparatus, and details are not described herein again.

FIG. 7 is a specific flowchart of an automatic fuse message processing system in processing a message according to an embodiment of the present application. The message processing device and the accounting device in the figure may be implemented by one or several computers, or It is formed by a dedicated chip, and the included logs, blacklists, etc. can be implemented by a database, and can be located at any position, for example, the log is in the same computer as the message processing device, or is located in a different computer.

Specifically, in the figure, step 701 is included, and the service system sends a message request to the message processing apparatus.

In this step, the service system may be, for example, a payment transaction system, or a transfer system, or a collection system. In the embodiment, the payment transaction system is taken as an example, and at least the sending message request sent by the payment transaction system is The user information and the service type are included, where the service type indicates which type of service the message to be sent belongs to, such as a payment completion message, a payment failure message, a transfer completion message, a transfer failure message, and the like, and may also include a service message content, such as a user. ID+payment completion message + a certain payment completion message, or includes a transmission channel + service type + service message content, such as a mobile phone number and a payment completion message, a payment completion message.

The sending the message request may specifically include sending user information (channel) + service type coding + some parameters required for assembling the message content. The message processing device obtains the message template corresponding to the service type code according to the service type code, and replaces the parameter content that is input by the user with some replaceable variable in the template, and assembles the message content that is finally sent to the user.

Step 702: The message processing apparatus performs pre-checking on the sending message request.

In this step, it is mainly verified whether the format of the request for sending a message meets the requirements, for example, whether the format of the user ID is correct, whether the format of a payment completion message is correct, whether the service type of the message to be sent exists, and the like.

Step 703: Obtain a feature in the sending message request.

In this step, if the message request is a user ID and a payment completion message (service type), the user ID needs to be extracted from the request, and the appropriate transmission channel is matched according to the user ID, for example, saved in the user information. The channels for sending messages are mobile phone number and email address respectively. According to the user's preference or the channel according to the historical message, one of them is selected as the channel for sending the message. In this example, the mobile phone number is selected as the channel for sending the message. At least the channel (mobile number) and payment completion message of the message are included in the feature.

If the message sending channel includes the message sending channel and the service type, the feature in the sending message request is directly obtained, and the feature includes at least a channel (mobile phone number) and a payment completion message.

Step 704, performing blacklist verification on the feature.

The blacklist in this step includes multiple features, and compares the received feature in the sent message request with multiple features in the blacklist. If the same is true, the blacklist check fails. Otherwise, the blacklist is black. If the verification fails, the payment completion message is not sent. In this embodiment, the blacklist verification is performed, and the payment completion message can be completed.

Step 705: The message processing device invokes a communication device such as a gateway to send a payment completion message in a specified channel, and generates a log of the current transmission message.

In this step, the communication device such as the gateway and the message processing device may be integrated, or may be separate devices, which are not limited herein.

The log for generating the current message includes at least the channel and service type of the current sending message, where the service type is, for example, a payment success message, a transfer success message, a transfer failure message, a seller already shipped message, and the like, in other embodiments. The log may also include the time for sending the message (for later determining whether to enter the blacklist according to the time), the content of the service message, and the like.

The log can be stored in a message processing device.

So far, the message processing flow in the message processing apparatus ends.

Step 706, the accounting device synchronizes the logs in the message processing device.

In this step, the accounting device periodically reads the log of the message processing device and performs the accounting process locally. The accounting process here refers to the subsequent analysis, calculation, and the like.

Step 707, calculating the number of logs having the same characteristics.

In this step, the accounting device accumulates the logs of the same channel type and the service type according to the plurality of logs recorded, as shown in the following Table 1 as a synchronized log table, in which the channels for each message are separately recorded. And business type.

Table 1

In the table, the first log and the third log have the same channel and service type, and the fourth log has the same channel as the first one, but the business type is different, and the data of other rows in the table is not Show) There are 100 records of the payment success message sent by the mobile phone number short message.

In step 708, it is determined whether the calculated quantity is greater than the quantity threshold.

In this step, if the calculated quantity is greater than the quantity threshold, then step 709 is entered, otherwise the flow of accounting is ended.

In this example, the preset number of thresholds is 99. According to the foregoing calculation of 100, it indicates that the payment success message has been sent by the mobile phone number short message, which may already constitute interference to the user.

In step 709, the feature is recorded in the blacklist.

The above feature is a mobile phone number and a payment success message, and the feature is added to the blacklist. The blacklist can be stored in a message processing device or a billing device.

FIG. 8 is a specific flowchart of a message processing system of an automatic fuse according to an embodiment of the present application. Steps 801 to 805 of the embodiment are basically the same as steps 701 to 705 of the embodiment shown in FIG. The same is true, in the step 805, when the message processing device generates the log of the current message, the log includes the time information of the sent message in addition to the channel and the service type.

Step 806, the accounting device synchronizes the logs in the message processing device.

Step 807, calculating the number of logs having the same characteristics in a time range.

In this step, the number of logs having the same feature is calculated according to the time information of the message sent in the log and the preset time range. For example, the time range is 1 hour, and the number of logs having the same feature in one hour is calculated as 100.

In step 808, it is determined whether the calculated quantity is greater than the quantity threshold.

In this step, if the calculated quantity exceeds the quantity threshold, the process proceeds to step 809, otherwise the flow of the accounting is ended.

Similar to the embodiment of FIG. 7, the number threshold is 99, and the number of logs having the same feature in one hour calculated in step 807 is 100, and the judgment result exceeds the number threshold, and the process proceeds to step 809.

In step 809, the feature is recorded in the blacklist.

In this step, when the billing device records the feature, the time information for creating the feature is also recorded. In the step of performing the blacklist check by the message processing device, the message processing device filters out the expired feature according to the creation time information, or passes the The following step 810 performs an update of the blacklist. In this example, the blacklist is located in the message processing device.

In step 810, the accounting device calculates the length of time in which the feature exists in the blacklist. If the time threshold is exceeded, the feature is deleted from the blacklist.

Specifically, the difference between the current time and the time information of the feature in the blacklist is calculated by a predetermined period. If the time threshold is exceeded, the feature is deleted from the blacklist, otherwise the feature in the blacklist is retained. That is to say, if a certain service information is not sent to the user through a certain channel for a certain period of time, the service information sent by the channel does not constitute a harassment to the user, and the service information transmission in this manner can be resumed.

By updating the blacklist, you can control the behavior of sending service messages to users to avoid interference with users.

By separating the process of message processing and blacklist update, the efficiency of sending service messages by the system can be greatly improved, and the control of these service messages does not cause harassment to users.

Improvements to a technology can clearly distinguish between hardware improvements (eg, improvements to circuit structures such as diodes, transistors, switches, etc.) or software improvements (for process flow improvements). However, as technology advances, many of today's method flow improvements can be seen as direct improvements in hardware circuit architecture. Designers almost always get the corresponding hardware circuit structure by programming the improved method flow into the hardware circuit. Therefore, it cannot be said that the improvement of a method flow cannot be implemented by hardware entity modules. For example, a Programmable Logic Device (PLD) (such as a Field Programmable Gate Array (FPGA)) is an integrated circuit whose logic function is determined by the user programming the device. The designer is self-programming to "integrate" a digital system onto a single PLD without requiring the chip manufacturer to design and fabricate a dedicated integrated circuit chip 2 . Moreover, today, instead of manually making integrated circuit chips, this programming is mostly implemented using "logic compiler" software, which is similar to the software compiler used in programming development, but before compiling The original code has to be written in a specific programming language. This is called the Hardware Description Language (HDL). HDL is not the only one, but there are many kinds, such as ABEL (Advanced Boolean Expression Language). AHDL (Altera Hardware Description Language), Confluence, CUPL (Cornell University Programming Language), HDCal, JHDL (Java Hardware Description Language), Lava, Lola, MyHDL, PALASM, RHDL (Ruby Hardware Description Language), etc., are currently the most commonly used VHDL (Very-High-Speed Integrated Circuit Hardware Description Language) and Verilog2. It should also be apparent to those skilled in the art that the hardware flow for implementing the logic method flow can be easily obtained by simply programming the method flow into the integrated circuit with a few hardware description languages.

The controller can be implemented in any suitable manner, for example, the controller can take the form of, for example, a microprocessor or processor and a computer readable medium storing computer readable program code (eg, software or firmware) executable by the (micro)processor. In the form of logic gates, switches, application specific integrated circuits (ASICs), programmable logic controllers, and embedded microcontrollers, examples of controllers include, but are not limited to, the following microcontrollers: ARC 625D, Atmel AT91SAM, The Microchip PIC18F26K20 and the Silicone Labs C8051F320, the memory controller can also be implemented as part of the memory's control logic.

Those skilled in the art will also appreciate that in addition to implementing the controller in purely computer readable program code, the controller can be logically programmed by means of logic gates, switches, ASICs, programmable logic controllers, and embedding. The form of a microcontroller or the like to achieve the same function. Such a controller can therefore be considered a hardware component, and the means for implementing various functions included therein can also be considered as a structure within the hardware component. Or even a device for implementing various functions can be considered as a software module that can be both a method of implementation and a structure within a hardware component.

The system, device, module or unit illustrated in the above embodiments may be implemented by a computer chip or an entity, or by a product having a certain function.

For the convenience of description, the above devices are described separately by function into various units. Of course, the functions of each unit may be implemented in the same software or software and/or hardware when implementing the present application.

It will be apparent to those skilled in the art from the above description of the embodiments that the present application can be implemented by means of software plus a necessary general hardware platform. Based on such understanding, the technical solution of the present application may be embodied in the form of a software product in essence or in the form of a software product, which may be stored in a storage medium such as a ROM/RAM or a disk. , an optical disk, etc., includes instructions for causing a computer device (which may be a personal computer, server, or network device, etc.) to perform the methods described in various embodiments of the present application or portions of the embodiments.

The various embodiments in the specification are described in a progressive manner, and the same or similar parts between the various embodiments may be referred to each other, and each embodiment focuses on the differences from the other embodiments. In particular, for the system embodiment, since it is basically similar to the method embodiment, the description is relatively simple, and the relevant parts can be referred to the description of the method embodiment.

This application can be used in a variety of general purpose or special purpose computer system environments or configurations. For example: personal computers, server computers, handheld or portable devices, tablet devices, multiprocessor systems, microprocessor based systems, set-top boxes, programmable consumer electronics devices, network PCs, small computers, mainframe computers, including A distributed computing environment of any of the above systems or devices, and the like.

This application can be described in the general context of computer-executable instructions executed by a computer Said, for example, a program module. Generally, program modules include routines, programs, objects, components, data structures, and the like that perform particular tasks or implement particular abstract data types. The present application can also be practiced in distributed computing environments where tasks are performed by remote processing devices that are connected through a communication network. In a distributed computing environment, program modules can be located in both local and remote computer storage media including storage devices.

While the present invention has been described by the embodiments of the present invention, it will be understood by those skilled in the art

Claims

An automatic fuse message sending method, characterized in that

Receiving a request to send a message, and obtaining a feature in the request for sending the message;

Performing a blacklist check according to the feature;

After the blacklist is verified, a corresponding message is sent, and a log of the current sent message is generated according to the feature.
The method of claim 1, wherein the request to send a message comprises at least:

The channel and business information for sending the message; or the target user and business information for sending the message.
The method according to claim 2, wherein when the request for sending the message includes the target user and the service information, the feature in the request for sending the message further comprises: analyzing according to the target user information The channel through which the message was sent.
The method according to claim 1, wherein performing blacklist checking according to the feature further comprises determining whether the feature exists in the blacklist, and if not, transmitting the message.
The method of claim 1 wherein the log includes at least a channel and a type of service for transmitting the message.
An automatic fuse message sending method, characterized in that

Synchronize the log of the message processing system;

Accumulating the number of identical feature messages according to the log;

Determine whether the quantity exceeds the quantity threshold, and if it exceeds, add the feature to the blacklist.
The method of claim 6 wherein said characteristics include at least a channel and a type of service for transmitting the message.
The method according to claim 7, wherein the feature further includes time information of the transmitted message.
The method according to claim 8, wherein determining whether the quantity exceeds a predetermined threshold further comprises determining whether the quantity exceeds a quantity threshold within a certain time, and if the quantity is exceeded, the characteristic is add to blacklist.
The method according to claim 8, further comprising determining time information of the feature in the blacklist, and if the interval between the time information and the current time exceeds a time threshold, the feature is from the Removed from the blacklist.
An automatic fuse message processing apparatus, characterized in that

a receiving unit, configured to receive a request for sending a message, and obtain a feature in the request for sending the message;

a verification unit, configured to perform blacklist verification according to the feature;

The processing unit is configured to: after the blacklist is verified, send a corresponding message, and generate a log of the current sending message according to the feature.
The apparatus according to claim 11, wherein the request for sending a message comprises at least:

The channel and business information for sending the message; or the target user and business information for sending the message.
The apparatus according to claim 12, wherein the receiving unit is further configured to analyze, according to the target user information, a channel for sending a message.
The apparatus according to claim 12, wherein the checking unit is further configured to determine whether the feature exists in the blacklist, and if not, send the message.
An automatic fuse billing device characterized by comprising

a synchronization unit for synchronizing logs of the message processing system;

a calculating unit, configured to accumulate the number of messages having the same feature according to the log;

The processing unit is configured to determine whether the quantity exceeds a quantity threshold, and if yes, add the feature to the blacklist.
The apparatus of claim 15 wherein said characteristics include at least a channel and a type of service for transmitting the message.
The apparatus according to claim 16, wherein said feature further includes time information of the transmitted message.
The apparatus according to claim 17, wherein the processing unit is further configured to determine whether the quantity exceeds a quantity threshold within a certain time, and if the quantity exceeds, add the feature to a blacklist.
The device according to claim 17, further comprising an updating unit, determining time information of features in the blacklist, and if the interval between the time information and the current time exceeds a time threshold, the feature is Remove from the blacklist.
An automatic fuse message processing system, characterized by comprising a message processing device and a billing device,

The message processing apparatus is configured to receive a request for sending a message, and obtain a feature in the request for sending the message, perform blacklist verification according to the feature, and send a corresponding message after being verified by the blacklist, and according to the The feature generates a log of the current sent message;

The accounting device is configured to synchronize the logs of the message processing system, and according to the number of the same feature messages accumulated in the log, determine whether the quantity exceeds a quantity threshold, and if yes, add the feature to the blacklist.