Cross-platform multi-channel message sending system and configuration method

Abstract

The invention discloses a cross-platform multi-channel message sending system and a configuration method. The multi-channel message sending system comprises a scheduling module used for generating sending configuration information of a message according to received target user information and message content; the management module is connected with the scheduling module and is used for providing a unified message sending interface for the scheduling module and dynamically calling a corresponding message channel based on the sending configuration information; the unified message sending interface supports multi-channel type message sending; the docking module is connected with the management module and used for docking the message channels and the corresponding sending interfaces, the docking module comprises a plurality of message sender instances, each message sender instance corresponds to one message channel, and the message sender instances are used for sending the message content through the corresponding sending interfaces. In this way, the flexibility and the processing efficiency of the message sending system can be improved.

Description

Technical Field

[0001] This application relates to the field of information management, and in particular, to a cross-platform multi-channel message sending system and a configuration method thereof. Background Art

[0002] Existing message sending systems usually only support one or a few message channels, resulting in users having to switch between multiple platforms, with low efficiency. Moreover, different message channels adopt different communication protocols and interfaces, which increases the technical complexity and development cost of cross-platform integration. Traditional message sending systems lack intelligent scheduling capabilities and cannot dynamically adjust the sending strategy according to the user's active state and message priority. With the development of communication technology, users' requirements for the real-time, accurate, and personalized nature of message sending are increasing day by day, and traditional message sending systems can no longer meet the flexibility and efficiency requirements of current message sending services. Summary of the Invention

[0003] This application mainly provides a cross-platform multi-channel message sending system and a configuration method thereof to solve the problem of insufficient flexibility and processing efficiency of the message sending system.

[0004] To solve the above technical problems, a technical solution adopted by this application is: to provide a cross-platform multi-channel message sending system, including: a scheduling module, configured to generate sending configuration information of a message according to the received target user information and message content; a management module, connected to the scheduling module, configured to provide a unified message sending interface to the scheduling module and dynamically call a corresponding message channel based on the sending configuration information; the unified message sending interface supports message sending of multiple channel types; a docking module, connected to the management module, configured to dock each of the message channels and the corresponding sending interfaces, the docking module includes a plurality of message sender instances, each of the message sender instances corresponds to a message channel, and the message sender instance is configured to send the message content through the corresponding sending interface.

[0005] In some embodiments, the scheduling module is further configured to analyze the user behavior and obtain the message priority according to the received target user information and the message content, and then generate the sending configuration information according to the analysis result of the user behavior and the message priority.

[0006] In some embodiments, the scheduling module includes a user behavior analysis module and a decision optimization module; the user behavior analysis module is configured to analyze the received target user information and the message content, generate a user active state and a message priority corresponding to the message, so as to determine a message sending time and a message channel; the decision optimization module is configured to generate the sending configuration information according to the message sending time and the message channel, where the sending configuration information includes channel selection, sending time, multi-channel collaboration strategy, and retransmission strategy, and send the sending configuration information to the management module through the unified message sending interface.

[0007] In some embodiments, the management module includes a policy orchestration module, a target orchestration module, and a reporting and statistics module; the policy orchestration module is configured to define and parse the sending configuration information, and select a qualified message channel according to the parsing result for message sending; the target orchestration module is configured to manage the objects of message sending; the reporting and statistics module is configured to report the message sending results of each message channel.

[0008] In some embodiments, the policy orchestration module is further configured to define the policy syntax of the sending configuration information, determine the failure retransmission and parallel sending configuration information of message sending; the policy orchestration module is also configured to parse the sending scheme of the sending configuration information, determine the message channel corresponding to the message channel, and call the sender instance corresponding to the message channel to send the message to the docking module.

[0009] In some embodiments, the target orchestration module is further configured to select and restrict the message sending channel according to the message content; the target orchestration module is also configured to disassemble a group into multiple independent objects when the object of message sending is a group.

[0010] In some embodiments, the reporting and statistics module is further configured to configure information in a unified structure format, integrate the sending results of multiple message channels, aggregate the sending results into an array, and report the array at a preset reporting frequency; the reporting and statistics module is also configured to match the corresponding reporting method according to the reported target type.

[0011] In some embodiments, the docking module is further configured to generate a corresponding sender according to the type of each message channel, where the sender is used to implement the sending method of the communication protocol corresponding to the message channel; the docking module is also configured to dock the message channel and the unified message sending interface through the sender instance of the sender, and send the message according to the communication protocol corresponding to the sending configuration information; the docking module is also configured to send the result of message sending to the reporting and statistics module.

[0012] To solve the above technical problems, the present application also provides a configuration method for a cross-platform multi-channel message sending system for configuring the multi-channel message sending system as described above, including: creating a docking module, and creating a sender directory in the project of the docking module, the sender directory including a plurality of sender instances; setting a unique identifier in each of the sender instances; each of the sender instances corresponding to a message channel, the sender instance being used to execute the sending method of the corresponding sending interface, the message channel being used to connect to the corresponding information platform; setting a unified message sending interface in the docking module; the unified message sending interface including a sending method, each of the sender instances matching the unified message sending interface; creating a management module, constructing a sender manager directory in the management module, and setting a sender manager object in the sender manager directory; the sender manager object including a hash map table for storing the mapping relationship between the message channel and the corresponding transmitter object identifier in a key-value manner; encapsulating the unified message sending interface to a superior module in the management module; creating a scheduling module, creating a task orchestrator directory in the scheduling module, and setting a task orchestrator scheduler object in the task orchestrator directory; setting the core method scheduling decision process of the task orchestrator scheduler object; wherein, the receiving end of the scheduling decision process is a scheduling information structure, and the output of the scheduling decision process is a scheduling result structure.

[0013] In some embodiments, the scheduling information structure includes the mobile phone number's place of origin and the target population label; the scheduling result structure includes the message channel key value selected by the sending configuration information.

[0014] The beneficial effects of this application are as follows: Different from the prior art, this application discloses a multi-channel message sending system and a configuration method. The multi-channel message sending system includes a scheduling module for generating message sending configuration information according to the received target user information and message content; a management module connected to the scheduling module for providing a unified message sending interface to the scheduling module and dynamically invoking corresponding message channels based on the sending configuration information; the unified message sending interface supports the sending of messages of multiple channel types; a docking module connected to the management module for docking each message channel and the corresponding sending interface. The docking module includes multiple message sender instances, each message sender instance corresponding to a message channel, and the message sender instance is used to send the message content through the corresponding sending interface. The system is split into multi-level modules, with different modules providing different functions and working together to achieve the decoupling of the system, thereby improving the flexibility, scalability, and stability of the system. At the same time, according to the structural hierarchy of the system for interaction, using a unified message sending interface to shield the downstream channel protocol upwards and integrating cross-platform multi-channel and multi-protocol message channels downwards, enabling the system to reduce the integration cost of different platform channels under different protocols. BRIEF DESCRIPTION OF THE DRAWINGS

[0015] In order to more clearly illustrate the technical solutions in the embodiments of the present application or the prior art, the following will briefly introduce the drawings required for use in the description of the embodiments or the prior art. Obviously, the following drawings are only some embodiments of the present application. For those of ordinary skill in the art, without creative efforts, other drawings can also be obtained based on these drawings, where:

[0016] Figure 1 is a schematic structural diagram of an embodiment of a cross-platform multi-channel message sending system provided by the present application;

[0017] Figure 2 is as Figure 1 shown in the schematic structural diagram of an embodiment of the system scheduling module;

[0018] Figure 3 is as Figure 1 shown in the schematic structural diagram of an embodiment of the system management module;

[0019] Figure 4 is a schematic flowchart of an embodiment of the configuration method of the multi-channel message sending system provided by the present application. DETAILED DESCRIPTION OF THE EMBODIMENTS

[0020] Next, the technical solutions in the embodiments of the present application will be clearly and completely described in conjunction with the accompanying drawings in the embodiments of the present application. Obviously, the described embodiments are only a part of the embodiments of the present application, rather than all the embodiments. Based on the embodiments in the present application, all other embodiments obtained by those of ordinary skill in the art without creative efforts shall fall within the protection scope of the present application.

[0021] The terms "first", "second", and "third" in the embodiments of the present application are only used for descriptive purposes, and cannot be construed as indicating or implying relative importance or implicitly specifying the quantity of the indicated technical features. Thus, the features defined with "first", "second", and "third" may explicitly or implicitly include at least one of such features. In the description of the present application, the meaning of "a plurality" is at least two, such as two, three, etc., unless otherwise specifically and clearly defined. In addition, the terms "comprising" and "having" and any variations thereof are intended to cover non-exclusive inclusion. For example, a process, method, system, product, or device that includes a series of steps or units is not limited to the listed steps or units, but optionally further includes steps or units not listed, or optionally further includes other steps or units inherent to these processes, methods, products, or devices.

[0022] Referring to

[0023] Referring to Figure 1 , Figure 1 is a schematic structural diagram of an embodiment of a cross-platform multi-channel message sending system provided by the present application. The multi-channel message sending system includes:

[0024] A scheduling module 10, configured to generate sending configuration information of a message according to the received target user information and message content.

[0025] The scheduling module 10 is the top-level input-output model of the system, used to implement intelligent scheduling functions. It receives information such as the target population and region as the input of the scheduling module 10, and then the scheduling module 10 outputs configuration information such as channel selection and sending timing. The scheduling module 10 selects the sending path and sending time of the message through an intelligent algorithm, and comprehensively considers channel load, message type, and user behavior data to ensure that the message is delivered efficiently and accurately.

[0026] The management module 20 is connected to the scheduling module 10, and is used to provide a unified message sending interface to the scheduling module 10 and dynamically call the corresponding message channels based on the sending configuration information. The unified message sending interface supports the sending of messages of multiple channel types.

[0027] The management module 20 is the core of the system middle layer, responsible for converting the configuration information output by the scheduling module 10 into specific message sending instructions, dynamically calling the underlying docking module 30, and realizing cross-platform and cross-channel message sending.

[0028] The management module 20 provides a unified and abstract message sending interface for the upper-layer scheduling module 10, shields the underlying channel differences, and ensures the accurate execution of instructions. At the same time, the management module 20 intelligently selects the optimal message channel according to the sending configuration information and the requirements of the upper layer, dynamically adjusts the configuration information, ensures the efficient delivery of messages, and realizes the unified sending of messages across multiple platforms, multiple channels, and multiple protocols.

[0029] The docking module 30 is connected to the management module 20 and is used to dock each message channel and the corresponding sending interface. The docking module 30 includes multiple message sender instances, and each message sender instance corresponds to a message channel. The message sender instance is used to send the message content through the corresponding sending interface.

[0030] The docking module 30 is the execution unit at the bottom layer of the system and is responsible for directly docking with the message channels of each third-party platform. Each message sender instance issues the message content through the sending interface of a specific channel according to the instructions of the management module 20. In this way, the docking module 30 realizes the transparent processing of different platform protocols, ensures that messages can be seamlessly transmitted between different channels, and thus improves the compatibility of the system and the delivery efficiency of messages.

[0031] By splitting the system into multi-level modules, different modules provide different functions and work together to achieve the decoupling of the system, thereby improving the flexibility, scalability, and stability of the system; at the same time, interacting according to the structural level of the system, using a unified message sending interface to shield the downstream channel protocol upwards and integrating cross-platform, multi-channel, and multi-protocol message channels downwards, enabling the system to reduce the integration cost of different platform channels under different protocols.

[0032] Furthermore, the scheduling module 10 is further used to analyze the user behavior and obtain the message priority according to the received target user information and message content, and then generate the sending configuration information according to the analysis result of the user behavior and the message priority.

[0033] The scheduling module 10 accurately predicts the user active state through big data analysis and machine learning algorithms, and dynamically generates the optimal sending configuration information in combination with the message priority.

[0034] Refer to Figure 2 , the scheduling module 10 includes a user behavior analysis module 11 and a decision optimization module 12.

[0035] The user behavior analysis module 11 is used to analyze the received target user information and message content, generate the user active status and the message priority corresponding to the message, so as to determine the message sending time and the message channel.

[0036] The user behavior analysis module 11 accurately predicts the user active status by collecting data such as online duration, active time period, message interaction situation, etc., and using big data and machine learning algorithms.

[0037] The decision optimization module 12 is used to generate sending configuration information according to the message sending time and the message channel. The sending configuration information includes channel selection, sending time, multi-channel collaboration strategy and reissuing strategy, and is sent to the management module 20 through a unified message sending interface.

[0038] The decision optimization module 12 comprehensively considers factors such as channel load, message type, target population characteristics, etc., and outputs the optimal sending configuration information to ensure that the message is delivered efficiently and accurately.

[0039] Specifically, the channel selection includes multiple channels such as whatsapp, sms, voice, etc. The sending time is the specific time point of message sending, which can be dynamically adjusted according to the user active status. The multi-channel collaboration strategy includes whether to use multi-channel parallel distribution. The reissuing strategy is whether to use failed reissuing when the sending fails.

[0040] For example, an e-commerce platform plans to push a time-limited 3-hour mobile phone exclusive discount message to "users who have browsed mobile phones recently but have not placed an order". It is necessary to generate an optimal sending strategy through the scheduling module 10. The input information includes target user information: User A: Has browsed the details page of a certain brand of mobile phone multiple times in the past 3 days. The historical order shows a preference for receiving App push and SMS, and the active period is 20:00-22:00. User B: Searched for the mobile phone keyword for the first time yesterday, and the historical email opening rate is 80%, but often ignores SMS. And the message content: "The XX mobile phone you are concerned about has dropped 500 yuan directly, only before 21:00 today! Click to claim the discount", and includes business tags: high timeliness (expires in 3 hours), and the conversion target is to place an order immediately.

[0041] The scheduling module 10 conducts user behavior analysis according to the above input information. User A has a strong purchase intention (frequent browsing without placing an order). The historical response rate to App push is 40%, the SMS response rate is 15%, and the activity after 8 pm increases by 300%. User B has a preliminary interest (only single search), the email opening rate is 80%, but the click-through rate is only 5%, and the email interaction during the lunch break on weekdays is frequent.

[0042] Based on the above analysis results, message priority is determined. The priority of the message content is the highest because this message is a high-value promotion with a time limit of 3 hours, which directly affects the daily GMV target. The generated sending configuration parameters include:

[0043] The channel selection order for User A is as follows: 1. App push, 2. SMS; The sending time is 20:05, the starting point of User A's active period; The multi-channel collaboration strategy is strong timeliness collaboration. After the App push, if not clicked within 30 minutes, an SMS will be immediately appended. The SMS content emphasizes urgency: "There are still 2.5 hours left! Your exclusive discount for User A is about to expire"; The reissuance strategy is that if there is still no conversion at 21:00 (1 hour before the deadline), a floating window message + SMS will be pushed through the App for the third time.

[0044] The channel selection order for User A is as follows: 1. Email, 2. App push; The sending time is 12:15, the golden lunch break period of User A; The multi-channel collaboration strategy is cross-platform guidance. An "click to jump to App" button is embedded in the email. When the email is not opened after 2 hours, an App push will be triggered; The reissuance strategy is that if neither the email nor the App is opened 1 hour before the deadline (20:00), a template message of the WeChat service number will be triggered.

[0045] In terms of the differentiation of channel selection, User A gives priority to the high-reach App push, matching its historical behavior preferences. User B selects the email with a high open rate as the main channel to avoid the inefficiency of the SMS channel. In terms of strengthening time sensitivity, a reissuance checkpoint is set 1 hour before the end of the user's active time window (evening for User A / noon for User B) to activate procrastinating users. In terms of the multi-channel superposition effect, the remaining time is dynamically displayed in the SMS content of User A to create a sense of urgency, and a deep link is embedded in the email of User B to shorten the conversion path. In terms of the cost control mechanism, the secondary SMS of User A is only sent to unresponsive people to avoid excessive harassment, and User B finally uses the WeChat template message (zero cost) instead of paid SMS reissuance.

[0046] Refer to Figure 3 , the management module 20 includes a policy orchestration module 21, a target orchestration module 22, and a reporting and statistics module 23.

[0047] The policy orchestration module 21 is used to define and parse the sending configuration information, and select a qualified message channel for message sending according to the parsing result.

[0048] The policy orchestration module 21 further parses and defines the overview instructions issued by the scheduling module 10, and selects one or more qualified message channels from the message channels for message sending according to the parsing result.

[0049] Further, the policy orchestration module 21 is further configured to define the policy syntax for sending configuration information and determine the retransmission configuration information for failed message sending and the parallel sending configuration information.

[0050] The policy orchestration module 21 defines the syntax rules for sending configuration information, and defines the parallel sending rules and retransmission rules for message sending.

[0051] For example, whatsapp|sms^voice means to send through WhatsApp first, and if it fails, retransmit in parallel using both the sms and voice channels. Here, "|" represents retransmission, and "^" represents parallel sending.

[0052] The policy orchestration module 21 is also used to parse the sending configuration information and dynamically adjust the called message channels according to the sending results of the message channels.

[0053] The policy orchestration module 21 is also used to orchestrate the message plan and implement the actual message channel call by combining the message sending results fed back by the downstream module and the timer.

[0054] The target orchestration module 22 is used to manage the objects of message sending.

[0055] The target orchestration module 22 selects or restricts the types of message channels to be called according to the message content or the type of the message object. Also, it manages the objects of message sending to improve the efficiency of message sending.

[0056] Further, the target orchestration module 22 is further configured to select and restrict the message sending channels according to the message content.

[0057] For example, if what needs to be sent is a mobile phone number, the channels will be selected and restricted according to the number, and channels that do not support the number such as the Email channel will be filtered out.

[0058] The target orchestration module 22 is also used to disassemble a group into multiple independent sending objects when the object of message sending is a group.

[0059] For example, parse whether the recipient number is a "user set" defined by the system, such as a group, then disassemble the recipient number into a set of actual recipient numbers and then organize them.

[0060] The reporting and statistics module 23 is used to report the message sending results of each message channel.

[0061] The reporting and statistics module 23 obtains the actual message sending results of each message channel fed back by the lower-level module and organizes the multiple sending results using a unified protocol.

[0062] Further, the reporting and statistics module 23 is further configured to integrate the sending results of multiple message channels in a unified structural format, aggregate the sending results into an array, and report the array at a preset reporting frequency.

[0063] Sort out the results of several different channels through a unified protocol structure, and report these results through the protocol required externally, so as to ensure that each message can be tracked and recorded.

[0064] Integrate the sending results of several different channels through a unified structural format definition. For example, define a structure body, add a chan_message_id field to record the message id of the downstream channel, and use error_code and error_message to define whether the sending is successful and the reason for failure, etc.

[0065] The reporting and statistics module 23 is also configured to match the corresponding reporting method according to the reported target type.

[0066] Aggregate these sent record data and results to form a large JSON array, and report it at a certain frequency in a form that matches the receiver.

[0067] Specifically, if the receiver is an internal system, decouple the sending through the MQ method; if the receiver is an external system, send it through the http method.

[0068] The docking module 30 is further configured to generate corresponding senders according to the types of each message channel, and the senders are used to implement the sending methods of the communication protocols corresponding to the message channels.

[0069] The docking module 30 generates senders according to the channel types. For example, it generates an SMTP sender for the Email channel, a CMPP sender for the domestic SMS channel, an SMPP sender for the international SMS channel, and an HTTPS sender for the WhatsApp channel. Each sender implements a unified message sending interface to ensure that the messages are sent correctly according to the protocol.

[0070] The docking module 30 is also configured to dock the message channel and the unified message sending interface through the sender instance of the sender, and send messages according to the communication protocol corresponding to the sending configuration information.

[0071] The docking module 30 realizes the seamless docking of the message channel and the unified interface through the sender instance, ensuring that each channel, such as SMTP, CMPP, SMPP, HTTPS, etc., sends messages correctly according to the configuration.

[0072] The docking module 30 is also configured to send the result of message sending to the reporting and statistics module 23.

[0073] The docking module 30 feeds back the result of message sending to the upper-layer statistical reporting module, ensures that the status of each message is accurately recorded by the system, dynamically manages the message channels, and thus realizes the tracking and management of the entire life cycle of the messages.

[0074] See Figure 4 , this application also provides a configuration method for a multi-channel message sending system, which is used to configure the multi-channel message sending system as described above, and includes the following steps:

[0075] 01: Create the docking module 30, and create a sender directory (senders directory) in the project of the docking module 30. The sender directory includes multiple sender instances.

[0076] 02: Set a unique identifier in each sender instance. Each sender instance (sender object) corresponds to a message channel. The sender instance is used to execute the sending method of the corresponding sending interface., and the message channel is used to connect to the corresponding information platform.

[0077] 03: Set a unified message sending interface in the docking module 30. The unified message sending interface includes a sending method, and each sender instance matches the unified message sending interface.

[0078] Define a unified message distribution interface that includes a sending method, so that each sender instance implements this interface, thereby realizing the integration of cross-platform channels.

[0079] Create a sender directory in the project of the docking module 30, which contains several sender instances and is independently defined. Different sender objects are implemented according to different channels, such as docking for message distribution using protocols such as http / https, smtp, and smpp.

[0080] 04: Create the management module 20, build a send manager (sendermanager) directory in the management module 20, and set a send manager object in the send manager directory. The send manager object includes a hash map, and the hash map is used to store the mapping relationship between the message channel and the corresponding transmitter object identifier in a key-value manner.

[0081] Among them, the key value (Key) is the identifier (name) of each sending channel, and the corresponding identifier of each sender instance is unique.

[0082] Implement corresponding policy orchestration and target orchestration methods, etc. Through the request data coming from the upstream, clarify the channel to be distributed, and then find the corresponding sender instance through the hash map (HashMap), and use the sending method to specifically distribute the message to the corresponding channel.

[0083] 05: In the management module 20, a unified message sending interface is encapsulated to the upper-level module.

[0084] A unified message delivery interface is encapsulated upward, and the definition of corresponding configuration information is provided to achieve the hiding of specific delivery details from the upper level, to unify the delivery of messages, and to support capabilities such as configuration information.

[0085] 06: Create a scheduling module 10, create a task scheduler directory in the scheduling module 10, and set a task scheduler scheduler object in the task scheduler directory.

[0086] 07: Set the core method of the task scheduler scheduler object to schedule the decision process. Among them, the scheduling decision process receives a scheduling information structure, and the output of the scheduling decision process is a scheduling result structure.

[0087] Furthermore, the scheduling information structure includes the location of the mobile phone number and the target population label.

[0088] The scheduling result structure includes the message channel key value selected by sending configuration information.

[0089] By configuring the multi-channel message sending system through the above method, seamless integration and intelligent scheduling of multi-platform channels are achieved, the real-time and accuracy of message sending are improved, the personalized needs of users are met, and the communication efficiency is optimized.

[0090] Different from the prior art, this application breaks down the message sending process into three modules that work together, with different modules providing different capabilities, thus achieving decoupling of hierarchical functions and improving the flexibility and scalability of the system. The docking module 30 is located at the bottom of the system, hiding the different protocols of information channels of different platforms upwards, and docking with specific information channels and sending interfaces downwards, with a unified and abstract message sending capability; the management module 20 coordinates in the middle, provides a unified interface and selects channels on demand; the intelligent scheduling module 10 makes top-level decisions, outputs the optimal sending configuration based on input information such as the location of the mobile phone number, target population labels, etc., to ensure efficient and accurate delivery of messages. The system is deconstructed into the above three parts, and the interactive content is carried out according to its structural hierarchy, so that the message channel integration across multiple platforms, channels and protocols can be realized, with an abstract unified message sending interface, and has the ability to freely make corresponding decisions and schedules according to upstream or external information.

[0091] The above descriptions are merely embodiments of the present application and are not intended to limit the patent scope of the present application. Any equivalent structure or equivalent process transformation made using the contents of the present application specification and drawings, or directly or indirectly applied in other related technical fields, are also included in the patent protection scope of the present application.

Claims

1. A cross-platform multi-channel message sending system, characterized in that, Including: A scheduling module, configured to generate sending configuration information for a message according to received target user information and message content; A management module, connected to the scheduling module, configured to provide a unified message sending interface to the scheduling module and dynamically call a corresponding message channel based on the sending configuration information; the unified message sending interface supports message sending of multiple channel types; A docking module, connected to the management module, configured to dock each of the message channels and corresponding sending interfaces, the docking module includes a plurality of message sender instances, each message sender instance corresponds to a message channel, and the message sender instance is configured to send the message content through the corresponding sending interface.

2. The multi-channel message sending system according to claim 1, wherein The scheduling module is further configured to analyze user behavior and obtain message priority according to the received target user information and the message content, and then generate sending configuration information according to the analysis result of user behavior and the message priority.

3. The multi-channel message sending system according to claim 2, characterized in that The scheduling module includes a user behavior analysis module and a decision optimization module; The user behavior analysis module is configured to analyze the received target user information and the message content, generate user active status and message priority corresponding to the message, so as to determine message sending time and message channel; The decision optimization module is configured to generate the sending configuration information according to the message sending time and the message channel, the sending configuration information includes channel selection, sending time, multi-channel cooperation strategy and reissuing strategy, and is sent to the management module through the unified message sending interface.

4. The multi-channel message sending system according to claim 1, wherein The management module includes a policy orchestration module, a target orchestration module and a reporting and statistics module; The policy orchestration module is configured to define and parse the sending configuration information, and select a qualified message channel for message sending according to the parsing result; The target orchestration module is configured to manage the objects of message sending; The reporting and statistics module is configured to report the message sending results of each message channel.

5. The multi-channel message sending system according to claim 4, wherein The policy orchestration module is further configured to define the policy syntax of the sending configuration information and determine the failure reissuing and parallel sending configuration information of message sending; The policy orchestration module is further configured to parse the sending configuration information and dynamically adjust the called message channel according to the sending result of the message channel.

6. The multi-channel message sending system according to claim 4, wherein, The target orchestration module is further configured to select and limit the message sending channel according to the message content; The target orchestration module is further configured to disassemble a group into multiple independent sending objects when the object of message sending is a group.

7. The multi-channel message sending system according to claim 4, characterized in that, The reporting and statistics module is further configured to integrate the sending results of multiple message channels in a unified structure format, aggregate the sending results into an array, and report the array at a preset reporting frequency; The reporting and statistics module is further configured to match a corresponding reporting method according to the reported target type.

8. The multi-channel message sending system according to claim 7, wherein The docking module is further configured to generate a corresponding sender according to the type of each message channel, and the sender is configured to implement the sending method of the communication protocol corresponding to the message channel. The docking module is also used to dock the message channel with the unified message sending interface through a transmitter instance of the transmitter, and send the message according to the communication protocol corresponding to the sending configuration information; The docking module is also used to send the result of message sending to the reporting statistics module.

9. A configuration method for a cross-platform multi-channel message sending system, which is used to configure the multi-channel message sending system according to any one of claims 1-8, characterized in that, include: Creating a docking module, and creating a transmitter directory in a project of the docking module, wherein the transmitter directory includes a plurality of transmitter instances; A unique identifier is set in each of the transmitter instances; each of the transmitter instances corresponds to a message channel, the transmitter instance is used to execute the sending method of the corresponding sending interface, and the message channel is used to connect to the corresponding information platform; A unified message sending interface is set in the docking module; the unified message sending interface includes a sending method, and each of the sender instances matches the unified message sending interface; Creating a management module, constructing a sending manager directory in the management module, and setting a sending manager object in the sending manager directory; the sending manager object includes a hash mapping table, and the hash mapping table is used to store a mapping relationship between a message channel and a corresponding transmitter object identifier in a key-value manner; Encapsulating the unified message sending interface to the superior module in the management module; Creating a scheduling module, creating a task scheduler directory in the scheduling module, and setting a task scheduler scheduler object in the task scheduler directory; The core method scheduling decision process of the task scheduler scheduler object is set; wherein the scheduling decision process receives a scheduling information structure, and the output of the scheduling decision process is a scheduling result structure.

10. The configuration method according to claim 9, characterized in that, The dispatch information structure includes the location of the mobile phone number and the target population label; The scheduling result structure includes a message channel key value selected by sending configuration information.

Images