Multi-channel message unified pushing method based on gateway API authentication

Abstract

The invention provides a multi-channel message unified pushing method based on gateway API authentication, and the method comprises the following steps: S1, carrying out the standardization processing of messages from different service systems, and converting the messages into a unified message format; s2, the standardized message is routed to a corresponding channel queue; s3, according to the characteristics of different channels, performing queue processing on the messages; and S4, calling the API interface of the corresponding channel to send the message. The multi-channel message unified pushing method based on gateway API authentication has the beneficial effects that unified message pushing based on gateway API authentication serves as a message service center which is high in reliability, high in safety, high in expansion and easy to integrate, and a comprehensive management platform for unified message creation, message pushing and message statistics is provided for a user; a message integrated sending function is provided for each system, the trouble that different systems are in butt joint with multiple message channels is saved, and the message sending condition, the message proportion of each channel and the overall sending amount can be checked in real time through the message center.

Description

Technical Field

[0001] The invention belongs to the field of computer technology, and in particular relates to a multi-channel message unified push method based on gateway API authentication. Background Art

[0002] Nowadays, all fields are accelerating their rapid development towards digitalization, mobility and the Internet, and many application systems have been added to meet the needs of information development. The information environment has become large and complex, with numerous business systems. Each application system is relatively isolated, business collaboration is difficult, and each business system is not connected. Each of them has established its own message push channels, which not only duplicates construction, but also affects the efficiency of message transmission and brings challenges to information security.

[0003] The unified messaging platform based on gateway API authentication takes the message body as the center and realizes the unified and comprehensive management of messages, work orders, channels, and logs from the perspective of overall planning. It can provide a one-stop user message push and reach solution for government and enterprise customers. Through the standardized interface specification service of unified messaging, it provides support for the message flow between various business systems, solves the problem of multi-system message dispersion and inability to publish in a unified manner, and provides a one-stop message push service. At the same time, by integrating and coordinating the message sending capabilities of various business systems and conducting unified channel docking management, it reduces duplication of construction, reduces development costs, and ensures that messages are accurately reached through various channels. Summary of the invention

[0004] In view of this, the present invention aims to propose a multi-channel message unified push method based on gateway API authentication to at least solve one problem in the background technology.

[0005] To achieve the above object, the technical solution of the present invention is achieved as follows:

[0006] A multi-channel message unified push method based on gateway API authentication includes the following steps:

[0007] S1. Standardize messages from different business systems and convert them into a unified message format;

[0008] S2, routing the standardized message to the corresponding channel queue;

[0009] S3. Queue the messages according to the characteristics of different channels;

[0010] S4. Call the API interface of the corresponding channel to send a message.

[0011] Furthermore, in step S1, it specifically includes:

[0012] Use natural language processing technology and machine learning algorithms to perform semantic analysis on incoming messages, automatically identify message types and classify them;

[0013] Build an extensible message standardization model, dynamically select corresponding standardization rules according to message type and source system, and convert messages of different formats into a unified internal message format;

[0014] Knowledge graph technology is used to semantically enhance standardized messages.

[0015] Furthermore, the construction of an extensible message standardization model dynamically selects corresponding standardization rules according to the message type and source system to convert messages of different formats into a unified internal message format, including:

[0016] Collect message samples from different source systems and different types and analyze message formats;

[0017] Build an extensible standardization rule base that includes standardization rules for different message formats and source systems;

[0018] Furthermore, the rule base adopts a hierarchical structure, specifically including:

[0019] Top-level rules: general rules for all messages, including character set conversion and special character processing;

[0020] Middle-layer rules: rules for different message formats, including XML parsing rules and JSON parsing rules;

[0021] Underlying rules: rules for a specific source system, including field mapping rules for a certain system;

[0022] Each rule contains the following information:

[0023] Matching conditions, used to determine whether the rule is applicable;

[0024] Conversion operation: an operation that converts a message.

[0025] Further, the condition for determining whether the rule is applicable by using the matching condition includes determining whether the rule is applicable by using the rule matching degree, wherein the rule matching degree is:

[0026] Match(R,M)=w_1*F(R,M)+w_2*S(R,M)+...+w_n*X(R,M);

[0027] in,

[0028] R stands for rule;

[0029] M stands for message;

[0030] w_i represents the weight coefficient;

[0031] F(R,M), S(R,M), and X(R,M) represent the matching degree between rule R and message M on different features;

[0032] According to the rule matching degree, the best matching rule is selected for execution.

[0033] Furthermore, in step S2, it specifically includes:

[0034] Use the constructed user portrait model to analyze user behavior habits, preference settings, and channel usage information, and recommend appropriate communication channels for users;

[0035] Specifically, the following formula is used to calculate the user's recommendation score for each channel:

[0036] Score(u,c)=w_1*P(u,c)+w_2*S(c,m)+...+wn*X(u,c);

[0037] in,

[0038] u represents user;

[0039] c represents channel;

[0040] w_i represents the weight coefficient;

[0041] P(u,c) represents the preference of user u for channel c;

[0042] S(c,m) represents the matching degree between channel c and message m, including the matching degree between message type and channel type;

[0043] X(u,c) represents other factors, including the user's current active status and the availability of the channel;

[0044] According to the recommendation score, select the channel with the highest score for message push;

[0045] Evaluate the recommendation effect, including evaluation indicators and A / B testing. The evaluation indicators include accuracy, recall rate, F1 value, and AUC. In the A / B test, divide the users into two groups, one group uses the recommendation algorithm, and the other group randomly selects channels, and compare the open rate and click rate indicators of the two groups of users.

[0046] Based on the evaluation results, the model and recommendation strategy are optimized.

[0047] Adopt reinforcement learning algorithm to dynamically adjust channel priority according to message sending results to achieve the optimal sending strategy;

[0048] Furthermore, in step S4, it specifically includes:

[0049] Set different message sending rates according to channel characteristics and user needs.

[0050] Furthermore, machine learning algorithms are used to analyze historical message data and predict future message sending trends, such as predicting the delivery rate of different channels and user reactions to different message types.

[0051] Furthermore, the present solution discloses an electronic device, including a processor and a memory that is communicatively connected to the processor and is used to store executable instructions of the processor, wherein the processor is used to execute a multi-channel message unified push method based on gateway API authentication.

[0052] Furthermore, the present solution discloses a server, comprising at least one processor and a memory communicatively connected to the processor, wherein the memory stores instructions executable by the at least one processor, and the instructions are executed by the processor so that the at least one processor executes a multi-channel message unified push method based on gateway API authentication.

[0053] Furthermore, the present solution discloses a computer-readable storage medium storing a computer program. When the computer program is executed by a processor, a multi-channel message unified push method based on gateway API authentication is implemented.

[0054] Compared with the prior art, the multi-channel message unified push method based on gateway API authentication described in the present invention has the following beneficial effects:

[0055] The present invention discloses a method for unified multi-channel message push based on gateway API authentication. The unified message push based on gateway API authentication serves as a highly reliable, highly secure, highly scalable and easily integrated message service center, providing users with a comprehensive management platform for unified message creation, message push and message statistics, providing each system with the function of message integrated sending, eliminating the trouble of different systems connecting multiple message channels, directly hitting the pain points of message sending, and also allowing users to view the message sending status, the message proportion of each channel and the overall sending volume in real time through the message center. BRIEF DESCRIPTION OF THE DRAWINGS

[0056] The accompanying drawings constituting a part of the present invention are used to provide a further understanding of the present invention. The exemplary embodiments of the present invention and their descriptions are used to explain the present invention and do not constitute an improper limitation of the present invention. In the accompanying drawings:

[0057] Figure 1 The figure is a schematic diagram of the overall architecture of the unified message push platform according to an embodiment of the present invention. DETAILED DESCRIPTION

[0058] It should be noted that, in the absence of conflict, the embodiments of the present invention and the features in the embodiments may be combined with each other.

[0059] The present invention will be described in detail below with reference to the accompanying drawings and in conjunction with embodiments.

[0060] This method uses gateway API unified authentication, Redis subscription / publishing mechanism, MongoDB real-time push strategy, Elasticsearch technology, etc. to achieve unified and accurate delivery of user information in multiple scenarios, multiple modes, multiple platforms, and multiple channels.

[0061] Specifically include:

[0062] 1. Microservice architecture: Adopt microservice architecture to achieve the goals of decoupling, maintainability, and scalability, reduce duplicate development, and avoid system bloat.

[0063] 2. Multiple channels support: Supports multiple channels of contact and management, including SMS, email, WeChat, etc., to meet the push needs of different channels

[0064] 3. Real-time push: The Redis subscription / publishing mechanism and the adjustment of MongoDB real-time push strategy can achieve real-time and accuracy of push.

[0065] 4. Data statistics and analysis: Use Elasticsearch to achieve efficient search and filtering of data, support multi-dimensional data statistics and analysis, and provide valuable information and references.

[0066] In the specific implementation process, unified messaging aggregates notification messages from various business systems, provides services such as message templates and message lifecycle management, and forms a unified messaging center. It provides a variety of user message access channels, such as SMS, email, APP notifications, custom service notifications, etc., and can provide users with a comprehensive management platform for unified message creation, message push, and message statistics. It provides a unified message sending interface for applications, shields the sending details of message terminals, and saves complicated docking costs.

[0067] The platform adopts a microservice architecture, which includes four major modules: message push service, unified channel management, unified message management, and unified audit management.

[0068] Message push service

[0069] Message push is the core service of the system. It mainly combines the content configured by message management and channel management, and pushes messages according to the work orders generated in the audit module.

[0070] When an application calls an open API sending interface, the interface will generate an asynchronous work order and obtain the work order serial number. After the work order enters the queue, the message push process determines the message push channel based on the message push method and message push template of the work order. For message channels, such as SMS, email, Webhook push, etc., special processing is performed in accordance with the message push of the channel to ensure that the message push is 100% completed when the network is unobstructed, the configuration is accurate, and the receiving end service is normal.

[0071] In the case of message push failure, the system will automatically enable the message re-dispatch function, and re-dispatch the message that failed to be pushed successfully for no less than three times. If the three re-dispatch operations fail, the failure reason will be recorded and recorded in the push failure work order, and the message sending success rate will be calculated and updated.

[0072] The system also takes into account that when there are hundreds or even thousands of messages that need to be sent, there may be a backlog of messages. At this time, the system will remove messages that are more than 15 minutes old and will not send them. The message will be recorded as timed out and not sent to avoid causing unnecessary impact on customers.

[0073] Unified channel management

[0074] Message channel management is to set channel delivery parameters, including common SMS, email, App, WeChat, DingTalk and other channel parameter configuration management, comprehensively covering various message channel types, meeting the basic push requirements of most business systems, realizing message channel sharing, avoiding unnecessary repeated docking of message channels, thereby reducing R&D resource waste and reducing high maintenance costs.

[0075] The SMS channel configuration parameters include the service provider call address, service provider identification code, service provider platform key, etc. It supports access to common SMS service providers such as Alibaba Cloud SMS Service and Tencent Cloud SMS Service for selection when subscribing to SMS channels.

[0076] The configuration parameters of the mail channel include the mail server host address, port number, security authentication protocol, sending mail account, sending mailbox password, etc. It supports access from mainstream mailbox service providers for selection of message subscription mailbox channels.

[0077] Support access to other third-party push channels, such as DingTalk, Enterprise WeChat, WeChat public accounts, WeChat mini-programs, etc., to meet customized integrated push channels according to actual needs.

[0078] Unified Messaging Management

[0079] Through unified push management, visual message template configuration and multi-channel message push management are performed, and messages are sent from top to bottom according to the best channels that have been subscribed, meeting the performance requirements of high-concurrency message push and high-concurrency query, and solving the current situation of low single-channel message push arrival rate. With the message itself as the main body, from creating message content to multi-channel push configuration, the cost of message creation, sending and management is reduced, and the problem of users' difficulty in getting started is also solved.

[0080] Message templates are composed of template bodies, placeholders, and other common plug-ins. The role of templates is to increase the flexibility of message configuration. Templates are needed for batch push and group push of messages, thereby reducing the input of repeated content. Different types of channels correspond to different message templates, and templates from different service providers may also have certain differences. Users must complete the message template content configuration of the subscribed channel before they can successfully send messages through the channel.

[0081] Based on the existing message channel types in the system, it supports multiple message channel subscriptions for a single message, adapts to a variety of message templates to complete message creation, and completes a high-concurrency and high-efficiency message push mechanism based on the subscribed channels.

[0082] To order messages, you first select a message channel. You can select the same type of message channels, but you can only select one channel service provider for a message channel. The order of the message channels from top to bottom determines the order of message push. If the current message channel has not yet integrated a channel service provider, you can directly complete the service provider integration configuration according to the interface instructions. Secondly, different channel types are adapted to different message templates. Users can customize the template content according to actual needs and complete the message template configuration. Finally, the message content of the subscribed message channel is generated, and the application completes the message sending task through the interface call.

[0083] The created message tasks are managed in a unified message list, which includes the message subject name, subscribed channel, message creation time, message status and operation management. The manager can edit the surviving messages to be sent, delete the timed-out messages, and view and copy the sent messages.

[0084] Unified audit management

[0085] In addition to the daily operation audit of the system itself, the usage analysis conducts statistical analysis on the message push situation from multiple statistical dimensions such as the number of message pushes, the number of message arrivals, and the number of message deaths, and outputs statistical charts and related reports for display.

[0086] The unified messaging center system provides a log function for all operations, including creating messages, modifying messages, deleting messages, etc. It audits all abnormal operations. Administrators can view the system usage at any time to facilitate the maintenance of system security.

[0087] Collect statistics on all messages configured and sent by the unified messaging center system, display relevant indicators such as message sending volume, arrival volume, message mortality rate, etc., analyze the message call status of each channel, and support the generation of statistical reports by filtering according to push channels, message types and other conditions.

[0088] Those of ordinary skill in the art will appreciate that the units and method steps of each example described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, computer software, or a combination of the two. In order to clearly illustrate the interchangeability of hardware and software, the composition and steps of each example have been generally described in terms of function in the above description. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the technical solution. Professional and technical personnel can use different methods to implement the described functions for each specific application, but such implementation should not be considered to be beyond the scope of the present invention.

[0089] In the several embodiments provided in the present application, it should be understood that the disclosed methods and systems can be implemented in other ways. For example, the division of the units described above is only a logical function division, and there may be other division methods in actual implementation, such as multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. The above-mentioned units may or may not be physically separated, and the components displayed as units may or may not be physical units, that is, they may be located in one place, or they may be distributed on multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the embodiments of the present invention.

[0090] Finally, it should be noted that the above embodiments are only used to illustrate the technical solutions of the present invention, rather than to limit it. Although the present invention has been described in detail with reference to the aforementioned embodiments, those skilled in the art should understand that they can still modify the technical solutions described in the aforementioned embodiments, or replace some or all of the technical features therein by equivalents. These modifications or replacements do not make the essence of the corresponding technical solutions deviate from the scope of the technical solutions of the embodiments of the present invention, and they should all be included in the scope of the claims and specification of the present invention.

[0091] The above description is only a preferred embodiment of the present invention and is not intended to limit the present invention. Any modifications, equivalent substitutions, improvements, etc. made within the spirit and principle of the present invention should be included in the protection scope of the present invention.

Claims

1. A multi-channel message unified push method based on gateway API authentication, characterized in that: The following steps are involved: S1. Standardize messages from different business systems and convert them into a unified message format; S2, routing the standardized message to the corresponding channel queue; S3. Queue the messages according to the characteristics of different channels; S4. Call the API interface of the corresponding channel to send a message.

2. According to the method of claim 1, the method is characterized in that: In step S1, it specifically includes: Use natural language processing technology and machine learning algorithms to perform semantic analysis on incoming messages, automatically identify message types and classify them; Build an extensible message standardization model, dynamically select corresponding standardization rules according to message type and source system, and convert messages of different formats into a unified internal message format; Knowledge graph technology is used to semantically enhance standardized messages.

3. According to claim 2, a method for unified multi-channel message push based on gateway API authentication is characterized in that: The extensible message standardization model is constructed to dynamically select corresponding standardization rules according to the message type and source system, and convert messages of different formats into a unified internal message format, including: Collect message samples from different source systems and different types and analyze message formats; Build an extensible standardization rule base that includes standardization rules for different message formats and source systems.

4. According to the method of claim 3, the method is characterized in that: The rule base adopts a hierarchical structure, specifically including: Top-level rules: general rules for all messages, including character set conversion and special character processing; Middle-layer rules: rules for different message formats, including XML parsing rules and JSON parsing rules; Underlying rules: rules for a specific source system, including field mapping rules for a certain system; Each rule contains the following information: Matching conditions, used to determine whether the rule is applicable; Conversion operation, which is used to convert messages.

5. According to the method of claim 4, the method is characterized in that: The conditions for judging whether a rule is applicable by using a matching condition include judging whether a rule is applicable by using a rule matching degree, wherein the rule matching degree is: Match(R,M)=w_1*F(R,M)+w_2*S(R,M)+...+w_n*X(R,M); in, R stands for rule; M stands for message; w_i represents the weight coefficient; F(R,M), S(R,M), and X(R,M) represent the matching degree between rule R and message M on different features; According to the rule matching degree, the best matching rule is selected for execution.

6. A method for unified multi-channel message push based on gateway API authentication according to claim 1, characterized in that: In step S2, it specifically includes: Use the constructed user portrait model to analyze user behavior habits, preference settings, and channel usage information, and recommend appropriate communication channels for users; Using reinforcement learning algorithm, channel priority is dynamically adjusted according to message sending results to achieve the optimal sending strategy.

7. A method for unified multi-channel message push based on gateway API authentication according to claim 1, characterized in that: In step S4, it specifically includes: Set different message sending rates according to channel characteristics and user needs.

8. The method for unified multi-channel message push based on gateway API authentication according to claim 1, characterized in that: Using machine learning algorithms, historical message data is analyzed to predict future message sending trends, including the delivery rates of different channels and user reactions to different message types.

9. An electronic device, comprising a processor and a memory connected to the processor for storing instructions executable by the processor, characterized in that: The processor is used to execute a multi-channel message unified push method based on gateway API authentication as described in any one of claims 1-8 above.

10. A server, characterized in that: It includes at least one processor and a memory communicatively connected to the processor, wherein the memory stores instructions executable by the at least one processor, and the instructions are executed by the processor so that the at least one processor executes a multi-channel message unified push method based on gateway API authentication as described in any one of claims 1-8.

Images