Message push charging method and terminal

Abstract

The application discloses a message pushing charging method and a terminal, acquires a message channel queue arranged in sequence composed of message channels selected by a user; acquires a sending rule configuration selected by the user; acquires a charging standard according to the message channel queue and the sending rule configuration; generates a pushing link according to the message channel queue, and sends a message to be pushed according to the sending rule configuration after acquiring a charging token; receives a message pushing result, and performs charging settlement according to the message pushing result and the charging standard; the application can generate corresponding charging standards according to the message channels and the sending rule configuration selected by the user, and generate corresponding pushing links according to the message channel queue, and then sends the message after acquiring the charging token, so that the personalized customization with high freedom in the multi-channel sending process is realized, and the user can select the message channels and the sending rule according to the own demand.

Description

Technical Field

[0001] This invention relates to the field of push messaging, and more particularly to a push messaging billing method and terminal. Background Technology

[0002] In many business scenarios, it's necessary to send notifications to users, such as reminding them of purchases, sending holiday greetings, or indicating coupon usage. Currently, to ensure message delivery rates, merchants typically use multi-channel push notifications, delivering messages through different apps and SMS. However, managing multiple channels is complex, and merchants manually sending messages through multiple channels individually is time-consuming, inefficient, and difficult to manage. Summary of the Invention

[0003] The technical problem to be solved by the present invention is to provide a message push billing method and terminal to realize unified management and billing of message push across multiple channels.

[0004] To solve the above-mentioned technical problems, the present invention adopts the following technical solution:

[0005] A message push billing method includes the following steps:

[0006] Obtain the message channel queue arranged in order of the message channels selected by the user;

[0007] Retrieve the user-selected sending rule configuration;

[0008] The billing standard is obtained based on the message channel queue and sending rule configuration.

[0009] A push link is generated based on the message channel queue, and after obtaining the billing token, the message to be pushed is sent according to the sending rules.

[0010] Receive message push results and perform billing and settlement based on the message push results and the billing standards.

[0011] To solve the above-mentioned technical problems, another technical solution adopted by the present invention is as follows:

[0012] A message push billing terminal includes a memory, a processor, and a computer program stored in the memory and executable on the processor. When the processor executes the computer program, it performs the following steps:

[0013] Obtain the message channel queue arranged in order of the message channels selected by the user;

[0014] Retrieve the user-selected sending rule configuration;

[0015] The billing standard is obtained based on the message channel queue and sending rule configuration.

[0016] A push link is generated based on the message channel queue, and after obtaining the billing token, the message to be pushed is sent according to the sending rules.

[0017] Receive message push results and perform billing and settlement based on the message push results and the billing standards.

[0018] The beneficial effects of this invention are as follows: it can generate corresponding billing standards based on the message channels and sending rules selected by the user, and generate corresponding push links based on the message channel queues. Sending is only performed after receiving the billing token, thus realizing a high degree of personalization in the process of sending messages through multiple channels. Users can select message channels and sending rules according to their own needs. At the same time, the operation of pushing only after receiving the billing token and performing billing and settlement after the push is completed can avoid the problem of users not paying after the message is pushed. Furthermore, it eliminates the need to perform push operations on different message channels separately, and can be directly sent to multiple message channels after one configuration, which is more convenient. Attached Figure Description

[0019] Figure 1 This is a flowchart illustrating the steps of a message push billing method according to an embodiment of the present invention;

[0020] Figure 2 This is a schematic diagram of the structure of a message push billing terminal according to an embodiment of the present invention;

[0021] Figure 3 This is a schematic diagram of the use case system flow according to an embodiment of the present invention;

[0022] Figure 4 This is a schematic diagram of the intermediate layer push chain construction according to an embodiment of the present invention;

[0023] Figure 5 This is a schematic diagram of the push path queue elements in the intermediate layer push chain of this invention.

[0024] Label Explanation:

[0025] 1. A message push billing terminal; 2. Processor; 3. Memory. Detailed Implementation

[0026] To explain in detail the technical content, objectives, and effects of the present invention, the following description is provided in conjunction with the embodiments and accompanying drawings.

[0027] Please refer to Figure 1 A message push billing method includes the following steps:

[0028] Obtain the message channel queue arranged in order of the message channels selected by the user;

[0029] Retrieve the user-selected sending rule configuration;

[0030] The billing standard is obtained based on the message channel queue and sending rule configuration.

[0031] A push link is generated based on the message channel queue, and after obtaining the billing token, the message to be pushed is sent according to the sending rules.

[0032] Receive message push results and perform billing and settlement based on the message push results and the billing standards.

[0033] As can be seen from the above description, the beneficial effects of the present invention are as follows: it can generate corresponding billing standards according to the message channels and sending rules selected by the user, and generate corresponding push links according to the message channel queue. Sending is only performed after receiving the billing token, thus realizing highly flexible personalized customization in the process of sending messages through multiple channels. Users can select message channels and sending rules according to their own needs. At the same time, the operation of pushing only after receiving the billing token and performing billing and settlement after the push is completed can avoid the problem of users not paying after the message push is completed. Furthermore, there is no need to perform push operations separately on different message channels. It can be configured once and sent directly to multiple message channels, which is more convenient.

[0034] Furthermore, the step of configuring and obtaining the billing standard based on the message channel queue and sending rules includes:

[0035] Obtain the channel billing standard corresponding to each message channel in the message channel queue;

[0036] The billing standard is obtained by combining the channel billing standards according to the sending rules.

[0037] As described above, each message channel has a different push method and varying levels of integration difficulty. Furthermore, some third-party message channels, such as SMS push channels, require fixed fees. Therefore, each message channel should be configured with a corresponding channel billing standard, which can be directly displayed to users as a reference for choosing a push channel. Transparent billing increases user trust. Additionally, different combinations of channel billing standards can be configured based on the user's chosen sending rules, allowing users to visually compare costs under different sending rule configurations, thus improving configuration flexibility.

[0038] Furthermore, obtaining the billing token includes:

[0039] Determine whether a payment success message corresponding to the billing standard has been received. If so, obtain the billing token based on the payment success message.

[0040] As described above, a billing token can only be obtained after a user successfully pays the fee, thus preventing the user from defaulting on payments after the message is pushed through the messaging channel. After a user successfully pays the fee, a corresponding billing token is set as an indicator of successful payment. The message push process is only executed when this token is present, ensuring that the user has completed the payment during the message push process.

[0041] Furthermore, the sending rule configuration includes selective sending and sending all;

[0042] The step of configuring and combining the channel billing standards according to the sending rules to obtain the billing standard includes:

[0043] If the user selects the sending rule configuration as one-choice sending, then the highest one among the channel billing standards is taken as the billing standard;

[0044] If the user selects the sending rule configuration as sending all, then the billing standard for all channels will be added together to obtain the billing standard.

[0045] As described above, users can choose to send messages to one of the message channels in the message channel list or to every single message channel in the list, depending on their budget and scenario. If they choose to send to one channel, once a message is successfully sent to one of the channels, the system will not attempt to send messages through other channels. If they choose to send to all channels, messages will be sent to every single message channel in the list. When sending to one channel, the system selects the channel with the highest billing standard and charges accordingly. When sending to all channels, the system first charges each message channel in the selected list, and then settles the billing after receiving the push notification. This ensures that even with the highest possible cost, the system will collect the full amount without overcharging. Furthermore, the billing process can be displayed to ensure transparency.

[0046] Furthermore, the receipt of the message push result, and the billing settlement based on the message push result and the billing standard, include:

[0047] Receive message push results, wherein the message push results include the sending results corresponding to each message channel that has sent a message in the message channel queue, and the sending results include either sending success or sending failure;

[0048] Obtain the channel billing standard corresponding to the failed message channel as the refund standard, and process the refund according to the refund standard to complete the billing settlement.

[0049] As described above, since message sending can only begin after obtaining the corresponding billing token through advance payment, billing and settlement are performed based on the sending results of different message channels after message sending is completed, ensuring the accuracy of the final billing.

[0050] Please refer to Figure 2 A message push billing terminal includes a memory, a processor, and a computer program stored in the memory and executable on the processor. When the processor executes the computer program, it performs the following steps:

[0051] Obtain the message channel queue arranged in order of the message channels selected by the user;

[0052] Retrieve the user-selected sending rule configuration;

[0053] The billing standard is obtained based on the message channel queue and sending rule configuration.

[0054] A push link is generated based on the message channel queue, and after obtaining the billing token, the message to be pushed is sent according to the sending rules.

[0055] Receive message push results and perform billing and settlement based on the message push results and the billing standards.

[0056] The beneficial effects of this invention are as follows: it can generate corresponding billing standards based on the message channels and sending rules selected by the user, and generate corresponding push links based on the message channel queues. Sending is only performed after receiving the billing token, thus realizing a high degree of personalization in the process of sending messages through multiple channels. Users can select message channels and sending rules according to their own needs. At the same time, the operation of pushing only after receiving the billing token and performing billing and settlement after the push is completed can avoid the problem of users not paying after the message is pushed. Furthermore, it eliminates the need to perform push operations on different message channels separately, and can be directly sent to multiple message channels after one configuration, which is more convenient.

[0057] Furthermore, the step of configuring and obtaining the billing standard based on the message channel queue and sending rules includes:

[0058] Obtain the channel billing standard corresponding to each message channel in the message channel queue;

[0059] The billing standard is obtained by combining the channel billing standards according to the sending rules.

[0060] As described above, each message channel has a different push method and varying levels of integration difficulty. Furthermore, some third-party message channels, such as SMS push channels, require fixed fees. Therefore, each message channel should be configured with a corresponding channel billing standard, which can be directly displayed to users as a reference for choosing a push channel. Transparent billing increases user trust. Additionally, different combinations of channel billing standards can be configured based on the user's chosen sending rules, allowing users to visually compare costs under different sending rule configurations, thus improving configuration flexibility.

[0061] Furthermore, obtaining the billing token includes:

[0062] Determine whether a payment success message corresponding to the billing standard has been received. If so, obtain the billing token based on the payment success message.

[0063] As described above, a billing token can only be obtained after a user successfully pays the fee, thus preventing the user from defaulting on payments after the message is pushed through the messaging channel. After a user successfully pays the fee, a corresponding billing token is set as an indicator of successful payment. The message push process is only executed when this token is present, ensuring that the user has completed the payment during the message push process.

[0064] Furthermore, the sending rule configuration includes selective sending and sending all;

[0065] The step of configuring and combining the channel billing standards according to the sending rules to obtain the billing standard includes:

[0066] If the user selects the sending rule configuration as one-choice sending, then the highest one among the channel billing standards is taken as the billing standard;

[0067] If the user selects the sending rule configuration as sending all, then the billing standard for all channels will be added together to obtain the billing standard.

[0068] As described above, users can choose to send messages to one of the message channels in the message channel list or to every single message channel in the list, depending on their budget and scenario. If they choose to send to one channel, once a message is successfully sent to one of the channels, the system will not attempt to send messages through other channels. If they choose to send to all channels, messages will be sent to every single message channel in the list. When sending to one channel, the system selects the channel with the highest billing standard and charges accordingly. When sending to all channels, the system first charges each message channel in the selected list, and then settles the billing after receiving the push notification. This ensures that even with the highest possible cost, the system will collect the full amount without overcharging. Furthermore, the billing process can be displayed to ensure transparency.

[0069] Furthermore, the receipt of the message push result, and the billing settlement based on the message push result and the billing standard, include:

[0070] Receive message push results, wherein the message push results include the sending results corresponding to each message channel that has sent a message in the message channel queue, and the sending results include either sending success or sending failure;

[0071] Obtain the channel billing standard corresponding to the failed message channel as the refund standard, and process the refund according to the refund standard to complete the billing settlement.

[0072] As described above, since message sending can only begin after obtaining the corresponding billing token through advance payment, billing and settlement are performed based on the sending results of different message channels after message sending is completed, ensuring the accuracy of the final billing.

[0073] The message push billing method and terminal of the present invention can be applied to scenarios that require multi-channel message push, and is especially suitable for scenarios that require charging for multi-channel message push. The following is a description through specific embodiments.

[0074] Please refer to Figure 1 Embodiment 1 of the present invention is as follows:

[0075] A message push billing method includes the following steps:

[0076] S1. Obtain the message channel queue arranged in order of the message channels selected by the user;

[0077] S2. Obtain the user-selected sending rule configuration, which includes sending one option or sending all.

[0078] Selective sending means sequential single-channel reception, that is, messages are sent to message channels one by one according to the order in the message channel queue. If a message is successfully sent, no further messages will be sent. Sending all means simultaneous multi-channel reception, that is, messages are sent simultaneously through message channels in the message channel queue. Message channels include WeChat Mini Programs, WeChat Official Accounts, SMS, WeChat Work, etc. Users can confirm whether to add message channels to the message channel queue by setting the on / off status, and can sort the selected message channels by dragging and dropping.

[0079] It also allows for template configuration of messages to be pushed, such as order success reminders, consumption report notifications, and departure reviews. Templates can be pre-configured for users to edit. For different push channels, default push templates can be obtained, and the push message style can be modified based on the default push templates. This allows for an intuitive experience of the push effect of different message channels, helping merchants choose message push channels.

[0080] In one alternative implementation, the pre-configured selectable message channels and templates can be stored in a database, such as MongoDB, for easy expansion later; different databases can also be selected for storage according to different data types, for example, databases with diverse structures can be stored in the non-relational database MongoDB, while data with strong transaction requirements can be stored in MySQL for easy control.

[0081] S3. Obtain the billing standard according to the message channel queue and sending rules configuration, including:

[0082] S31. Obtain the channel billing standard corresponding to each message channel in the message channel queue;

[0083] S32. To obtain a billing standard by combining the channel billing standards according to the sending rule configuration, including: if the sending rule selected by the user is configured to send one option, then the highest one among the channel billing standards is obtained as the billing standard; if the sending rule selected by the user is configured to send all, then all the channel billing standards are added together one by one to obtain the billing standard.

[0084] S4. Generate a push link based on the message channel queue, and after obtaining the billing token, send the message to be pushed according to the sending rules.

[0085] The process of obtaining the billing token includes: determining whether a payment success message corresponding to the billing standard has been received; if so, obtaining the billing token based on the payment success message.

[0086] S5. Receive message push results, and perform billing and settlement based on the message push results and the billing standard, including:

[0087] S51. Receive message push results, wherein the message push results include the sending results corresponding to each message channel that has sent messages in the message channel queue, and the sending results include either sending success or sending failure.

[0088] S52. Obtain the channel billing standard corresponding to the target message channel based on the sending result as the refund standard, and perform a refund according to the refund standard to complete the billing settlement. Specifically, if the sending rule is configured to send one message at a time, obtain the channel billing standard corresponding to the target message channel with a successful sending result as the refund standard. If the refund standard is less than the payment amount in the payment success information, refund the difference between the payment amount and the refund standard. If the sending rule is configured to send all messages, obtain the channel billing standard corresponding to the target message channel with a failed sending result as the refund standard, and perform a refund according to the sum of all the refund standards.

[0089] Embodiment two of the present invention applies the above-described message push billing method to a real-world scenario:

[0090] Please refer to Figures 3-5 The middleware code implementation defines an abstract class `PushChain` that implements the interfaces `CreatedChain`, `ReadyChain`, and `PushedChain`. These three interfaces declare `applyTokens()`, `pushMsg()`, and `confirmResult()`, respectively. The entire lifecycle of `PushChain` is as follows:

[0091] A1. Create a custom PushChainBuilder constructor from the custom PushChainBuilderFactory. This constructor declares the build() method and returns CreatedChain. Inside the PushChainBuilderImpl implementation class, read the push strategy configured by the merchant (i.e., the sending rule configuration in step S2) and generate either a SeqAnySuccessChain for sequential single-channel push or an AllPushChain for push across all channels (the message channels selected by the user have already been obtained in step S1). Since both types of push chains inherit from PushChain, and PushChain implements the CreatedChain interface, the final returned value can be a ready push chain of different push strategy types. The push chain contains a key attribute called pushChannels, which is taken from the channel queue opened by the merchant configuration (i.e., the message channel queue in step S1). The queue elements are specific push classes transformed from the configuration, such as SMS SmsPusher, WeChat Official Account WechatPubPusher, WeChat Mini Program WechatMiniProgramPusher, and Enterprise WeChat WeComPusher. The relevant push classes are derived from the Pusher class and each overrides its internal abstract method channelPush() to implement message push.

[0092] A2. Before pushing, CreatedChain uses its custom applyTokens() method to request tokens and perform corresponding pre-deduction processing from the billing layer. Upon success, it returns ReadyChain (equivalent to step S3), indicating that the push chain has entered the next step, preparations are complete, and the push can officially begin. SeqAnySuccessChain and AllPushChain, due to differences in the requested tokens, each rewrite the applyTokens() method to achieve different pre-deduction methods.

[0093] A3. After becoming ReadyChain, the push channels in the pushChannels queue are retrieved using pushMsg(). Based on the different push strategy methods pushMsg() overridden by SeqAnySuccessChain and AllPushChain, push is attempted sequentially for a single channel. If successful, proceed to the next step; otherwise, try other channels, or push to all channels. The specific push for each channel is handled by the channelPush() method overridden by the push classes retrieved from the queue, as mentioned at the end of step A1. This allows for pushing various channels using different set strategies. The push results are recorded in the context property of the push chain. After completing the operation, PushedChain is returned, indicating that the push has ended and the system has entered the push-completed state.

[0094] A4. PushedChain uses the confirm() method to notify the billing layer of the push results, in order to confirm the pre-deduction or roll back the pre-deduction for a failed push. Similarly, if SeqAnySuccessChain and AllPushChain have special handling in this step, such as recording the push results in the required format, then the confirm() method of the parent class PushChain should be overridden; otherwise, the parent class's method should be used directly to notify the billing layer of the results (equivalent to step S5).

[0095] In the construction and execution of the push chain, if you want a free full-channel sending chain for certain merchants (excluding SMS), the backend can further override the token application and deduction (applyToken()) and push result notification to the billing layer for confirmation or deduction rollback (confirm()) in the class derived from AllPushChain to perform differentiated processing. The specific logic of the message push channel (pushMsg()) is the same as AllPushChain and does not need to be overridden; that is, subsequent personalized extensions are also relatively convenient.

[0096] In one optional implementation, the messages to be pushed are sent to a middleware layer. This middleware layer uses a message queue middleware, such as Kafka, to smooth out peak and off-peak message processing, preventing server resource congestion and downtime during peak message volumes. Specifically, Kafka's multi-partition + multi-threaded listeners and consumer batch data retrieval with a built-in thread pool enhance the middleware system's message processing capabilities. A caching middleware (Redis in this case) optimizes the performance of retrieving duplicate data. When the middleware processes each message (i.e., during step A1), it retrieves essential information for each message channel from the user registration information, such as phone number or OpenID, and places it in the context of the message chain. After step A4, this information can be used to associate and record user information and push data. After the push is completed, the billing, sending results, and billing settlement process can be displayed, providing clear billing details. Furthermore, it can analyze the push preferences of various merchants, such as message channel preferences and template preferences, and calculate the reach rate of each message channel.

[0097] Please refer to Figure 2 Embodiment 3 of the present invention is as follows:

[0098] A message push billing terminal 1 includes a processor 2, a memory 3, and a computer program stored in the memory 3 and executable on the processor 2. When the processor 2 executes the computer program, it implements the steps in Embodiment 1 or Embodiment 2 described above.

[0099] In summary, this invention provides a message push billing method and terminal that achieves higher message reach through complementary multi-channel messaging. Specifically, it diversifies push formats and enriches push content by providing optional sending rule configurations and flexible, configurable message channels. The three-step process of applying for a billing token, pushing a message, and confirming the result ensures more accurate billing. Furthermore, after payment, the required push messages are sent, and billing is settled based on the sending results, resulting in more reliable data, richer push formats, more diverse content, and flexible, scalable configuration. Compared to SMS, other channels are cheaper, helping users increase profits through low-cost or near-zero-cost push channels.

[0100] The above description is merely an embodiment of the present invention and does not limit the patent scope of the present invention. Any equivalent modifications made based on the content of the present invention specification and drawings, or direct or indirect applications in related technical fields, are similarly included within the patent protection scope of the present invention.

Claims

1. A message push billing method, characterized in that, Including the following steps: Obtain the message channel queue arranged in order of the message channels selected by the user; Retrieve the user-selected sending rule configuration; The process of obtaining a billing standard based on the message channel queue and sending rule configuration includes: obtaining the channel billing standard corresponding to each message channel in the message channel queue; and combining the channel billing standards according to the sending rule configuration to obtain a billing standard. A push link is generated based on the message channel queue, and after obtaining the billing token, the message to be pushed is sent according to the sending rules. Receiving message push results and performing billing settlement based on the message push results and the billing standard includes: receiving message push results, wherein the message push results include the sending results corresponding to each message channel that has sent messages in the message channel queue; obtaining the channel billing standard corresponding to the target message channel based on the sending results as the refund standard; performing a refund based on the refund standard; and completing the billing settlement. If the user selects the sending rule configuration as "select one to send", the channel billing standard corresponding to the target message channel with a successful sending result is obtained as the refund standard. If the refund standard is less than the payment amount, the difference between the payment amount and the refund standard is refunded. If the user selects the sending rule configuration as sending all messages, the channel billing standard corresponding to the target message channel whose sending result is a failure is obtained as the refund standard, and the refund is made according to the sum of all the said refund standards.

2. The message push billing method according to claim 1, characterized in that, The process of obtaining the billing token includes: Determine whether a payment success message corresponding to the billing standard has been received. If so, obtain the billing token based on the payment success message.

3. The message push billing method according to claim 1, characterized in that, The sending rule configuration includes selective sending and sending all; The step of configuring and combining the channel billing standards according to the sending rules to obtain the billing standard includes: If the user selects the sending rule configuration as one-choice sending, then the highest one among the channel billing standards is taken as the billing standard; If the user selects the sending rule configuration as sending all, then the billing standard for all channels will be added together to obtain the billing standard.

4. A message push billing terminal, comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, characterized in that, When the processor executes the computer program, it performs the following steps: Obtain the message channel queue arranged in order of the message channels selected by the user; Retrieve the user-selected sending rule configuration; The process of obtaining a billing standard based on the message channel queue and sending rule configuration includes: obtaining the channel billing standard corresponding to each message channel in the message channel queue; and combining the channel billing standards according to the sending rule configuration to obtain a billing standard. A push link is generated based on the message channel queue, and after obtaining the billing token, the message to be pushed is sent according to the sending rules. Receiving message push results and performing billing settlement based on the message push results and the billing standard includes: receiving message push results, wherein the message push results include the sending results corresponding to each message channel that has sent messages in the message channel queue; obtaining the channel billing standard corresponding to the target message channel based on the sending results as the refund standard; performing a refund based on the refund standard; and completing the billing settlement. If the user selects the sending rule configuration as "select one to send", the channel billing standard corresponding to the target message channel with a successful sending result is obtained as the refund standard. If the refund standard is less than the payment amount, the difference between the payment amount and the refund standard is refunded. If the user selects the sending rule configuration as sending all messages, the channel billing standard corresponding to the target message channel whose sending result is a failure is obtained as the refund standard, and the refund is made according to the sum of all the said refund standards.

5. A message push billing terminal according to claim 4, characterized in that, The process of obtaining the billing token includes: Determine whether a payment success message corresponding to the billing standard has been received. If so, obtain the billing token based on the payment success message.

6. A message push billing terminal according to claim 4, characterized in that, The sending rule configuration includes selective sending and sending all; The step of configuring and combining the channel billing standards according to the sending rules to obtain the billing standard includes: If the user selects the sending rule configuration as one-choice sending, then the highest one among the channel billing standards is taken as the billing standard; If the user selects the sending rule configuration as sending all, then the billing standard for all channels will be added together to obtain the billing standard.

Images