High-availability industrial message design system and implementation method

Abstract

The present invention provides a high-availability industrial message design system and implementation method, which relates to the field of computer software technology. The method includes: a telegram management module, a message management module, a basic middle platform-shared service module, and a message center console. The present invention can quickly configure message routing consumption in combination with business scenarios, and the message can be routed and consumed from the source end of the message middleware according to the configuration information, avoiding the channel occupancy limitation caused by the client establishing a connection, greatly improving the high stability of the message; the message embedding point provided can effectively connect the entire life cycle of the message from production to consumption, can effectively track the ins and outs of the message, provide convenience for the connection of business scenarios, and ensure the high stability of the message.

Description

Technical Field

[0001] The present invention relates to the field of computer software technology, and in particular to a design and implementation method of a complete message production and consumption system based on Erlang language development and expansion, and in particular to a high-availability industrial message design system and implementation method. Background Art

[0002] China Baowu Ecological Technology Platform is based on the pilot requirements of state-owned capital investment companies. Baowu Group headquarters is transformed into a capital operation headquarters that combines value creation and control functions. In the digital economy era, enterprises should actively carry out digital transformation, build new capabilities, and promote business innovation and development. The realization of the modernization of corporate governance systems and capabilities is inseparable from the construction of business innovation capabilities. Technology component innovation is an important guarantee for the realization of corporate digital transformation.

[0003] The essence of the basic middle platform is to integrate relevant technical components, provide relevant basic technical architecture guarantees, avoid repeated development of the same functions, achieve one-time development and multiple reuse, simplify things, reduce development costs, empower front-end and middle-end businesses, and provide flexible and efficient basic services.

[0004] When users need to connect messages across systems, traditional message services cannot meet the needs of business systems with increasingly large business volumes. At this time, a new plug-in-based message design model is needed to decouple service calls between business systems through a configurable message delivery model, thereby enhancing the reusability and maintainability of components.

[0005] Comparing the current domestic message component products, we found that these products have the following limitations:

[0006] 1. Traditional messaging is always at the application layer, and performance bottlenecks will occur under the same server configuration;

[0007] 2. Messages flow through multiple systems, resulting in low efficiency;

[0008] 3. Message distribution lacks flexibility, and coding is required every time to implement message subscription;

[0009] 4. The messages will not be kept on record and will be destroyed once consumed, making them impossible to trace.

[0010] The invention patent with publication number CN113138860A discloses a message queue management method and device, including: dynamically obtaining the number of messages contained in each message queue, and calculating the message queue entry index and message queue exit index of each message queue in real time; calculating the message processing time of each message queue according to the message queue entry index and message queue exit index of each message queue; judging whether each message queue needs to perform capacity adjustment according to the message processing time of each message queue and a preset time processing threshold, and performing capacity adjustment processing on the message queues for which the judgment result is yes.

[0011] The above invention patent only provides the relevant basic application solutions for message management. Although it standardizes the management and capacity expansion calculation of message components to a certain extent, it fails to solve the performance bottleneck that message production and consumption performance will be greatly reduced when a large number of messages are queued. In addition, there are many message transfers, and message capacity calculation will also occupy related machine resources and be difficult to track after problems occur. This research bypasses the requirements of high availability of messages, irreparable loss of messages, and maximization of resource utilization of single node / cluster message production or consumption under the same configuration. It cannot meet the solution of core problems, and therefore does not really solve the pain points related to message management.

[0012] In view of the above defects, it is necessary to provide a method to solve how to sink the relevant business functions to the message component level based on the Erlang language, realize the flow of messages across systems, make it have the characteristics of high availability, high performance and high stability, meet the needs of users to track and locate every link of the message flow, and make up for the deficiency of the loose integration of traditional message middleware with the business perspective. Summary of the invention

[0013] In view of the defects in the prior art, the present invention provides a high-availability industrial message design system and implementation method.

[0014] According to a high-availability industrial message design system and implementation method provided by the present invention, the scheme is as follows:

[0015] In a first aspect, a high-availability industrial message design system is provided, the system comprising: a telegram management module, a message management module, a basic middle platform-shared service module, and a message center console;

[0016] Telegram management module: Maintains and manages configuration information related to asynchronous messages of telegrams, and provides a visual management function interface related to the reception, consumption and monitoring of telegrams;

[0017] Message management module: maintains and manages configuration information related to common messages, and provides a visual management function interface related to the reception, consumption and monitoring of common messages;

[0018] Basic middle platform - shared service module: register and maintain relevant basic information of services, provide shared services to the outside world, and provide favorable support for the interconnection and interoperability between systems and service operation and maintenance;

[0019] Message center console: provides a visual management interface for monitoring message middleware and provides convenient management tools for operation and maintenance personnel;

[0020] Among them, the message management module is associated with the basic middle platform-shared service module, and the message management module and the basic middle platform-shared service module are in a one-to-one relationship or a many-to-many relationship;

[0021] There is also an association relationship between the message management module and the basic middle platform-shared service module. The message management module and the basic middle platform-shared service module have a one-to-one relationship or a one-to-many relationship;

[0022] The telegram management module and the message management module communicate with the message middleware, and all communication information can be visually monitored through the message center console module.

[0023] Preferably, the electronic message management module includes:

[0024] One-stop registration of telegrams: register asynchronous messages of telegram type for classification management and maintenance;

[0025] Basic information management of telegrams: perform related operations management and maintenance including modification, deletion, and query of registered telegrams, and automatically allocate queue channels for newly created telegrams;

[0026] Telegram structure management: Describe the business message body for telegram messages and configure relevant structure information for use in parsing string messages;

[0027] Telegram registration progress tracking: Track the progress of one-stop registration messages, and proceed to the next registration operation for intermediate messages;

[0028] Telegram queue service management: configure consumers for telegrams. The consumer service follows the REST standard specification. Once there is a message in the queue, it will actively consume and distribute the message.

[0029] Message sending history: trace the message sending history of the message sent to the message center. If the message fails to be sent, resend it according to business needs.

[0030] Message consumption history: The message consumption history of the messages sent to the message center is traced. If the message consumption fails, it is re-consumed according to business needs.

[0031] Preferably, the message management module includes:

[0032] One-stop message registration: One-stop registration for common messages to specify relevant routing key information and queue names;

[0033] Queue configuration management: perform related operations including modification, deletion and query of registered queue information;

[0034] Queue service management: When you need to specify a consumer for a queued message, you need to configure the relevant consumer on the corresponding queue first. The consumer service follows the REST standard specification. Once there is a message in the queue, it will actively consume and distribute the message.

[0035] Message production history: trace the production history of common messages sent to the message center. If it is found that the production of common messages fails, re-production is performed according to business needs.

[0036] Message consumption history: Tracing the message consumption history of common messages sent to the message center. If it is found that the common message consumption fails, re-consumption is performed according to business needs.

[0037] Preferably, the basic middle platform-shared service module includes:

[0038] Production message service: When the business connects to asynchronous messages, it needs to store the messages in the message queue through this service interface, and then the plug-in end monitors and consumes them autonomously;

[0039] SMS service: When the business performs verification code verification or information reminder, the information is pushed according to the SMS service;

[0040] Sending email service: When the business performs verification code verification or information reminder, the information is pushed according to the sending email service;

[0041] Mobile message push service: When the business performs verification code verification or information reminder, information is pushed according to the mobile message push service;

[0042] In-site message service: When the business requires in-site notifications, announcements, or to-do reminders, information is pushed based on the in-site message service.

[0043] Preferably, the message center console includes:

[0044] Message server console: performs global monitoring of the message management middleware RabbitMQ, mainly including server node activity information, memory usage, and channel connection status.

[0045] Queue consumption status monitoring: monitor the status of messages in the message queue to determine whether the message is in the queue or being consumed;

[0046] Queue configuration information monitoring: audit and verify message routing configuration information;

[0047] Queue information monitoring: monitor whether the queue is in working state.

[0048] In a second aspect, a high-availability industrial message design and implementation method is provided, the method comprising:

[0049] Step S1: Complete the registration message service in service management through the basic middle platform;

[0050] Step S2: Register the message information in the message management through the basic middle platform and message management;

[0051] Step S3: Complete the configuration of the message structure in the message management through the basic middle platform and message management;

[0052] Step S4: Configure the message queue information in the message management through the basic middle platform and message management;

[0053] Step S5: Configure the message service information in the message management through the basic middle platform and message management;

[0054] Step S6: Check the resume in the message management through the basic middle platform and message management;

[0055] Step S7: Complete message registration in ordinary messages through the basic middle platform and message management;

[0056] Step S8: Perform queue service management in common messages through the basic middle platform and message management;

[0057] Step S9: View the message history in ordinary messages through the basic middle platform and message management.

[0058] Preferably, the operation entry for registering the message service in step S1 includes: entering the shared service management page, clicking the Add button, entering the message service ID, the application to which the service belongs, the service category, the service method name, the service English name, whether the service is authorized, the service category, and the service description, and clicking the Save button to complete the registration of the message service information.

[0059] Preferably, the operation entry for registering the telegram information in step S2 includes: entering the telegram management page, selecting the telegram information page, clicking the Add button, entering the telegram number information, telegram name, telegram category, and the application to which the telegram belongs, and clicking the Save button to complete the addition.

[0060] Preferably, the operation entry for configuring the message structure in step S3 includes: entering the message structure management page, registering and configuring the message structure information as needed, or performing related import, modification or deletion operations on an existing structure.

[0061] Preferably, the operation entry for configuring the message queue information in step S4 includes: entering the message queue information management page, adding a queue, selecting the queue information page, clicking the Add button, entering information, and clicking the Save button to complete the addition;

[0062] The operation entry for configuring the message service information in step S5 includes: entering the message service information management page, selecting the message service information page, clicking the Add button, selecting the corresponding message and service information, and clicking the Save button to complete the configuration;

[0063] The operation entry for viewing the history in step S6 includes: entering the message history viewing page, the user clicks the view history button on the send history / receive message history page, jumps to the history details page, and checks the problems encountered in the service call;

[0064] The operation entry of the message registration in step S7 includes: entering the one-stop message registration page, where the user performs related operations including message information registration, modification and deletion;

[0065] The operation entry of the queue service management in step S8 includes: entering the queue service management page, and the user performs binding or unbinding operation on the queue service management page for the association relationship between the message queue and the consumer service;

[0066] The operation entry for viewing the message history in step S9 includes: entering the message history viewing page, the user clicks the view history button on the message production history / consumption history page, jumps to the history details page, and checks the problems encountered in the service call.

[0067] Compared with the prior art, the present invention has the following beneficial effects:

[0068] 1. The present invention simplifies the use threshold of message middleware and facilitates user operation;

[0069] 2. The present invention provides a configuration management function for message-related configuration that fits the business perspective, making configuration easier;

[0070] 3. The present invention develops plug-in extensions for the bottom layer, avoids the connection resource occupation at the middleware level, and improves the message processing rate of the message middleware;

[0071] 4. The present invention manages the entire life cycle of a message, ensuring that each message has a destination;

[0072] 5. The visualized link tracking management of the present invention makes every link of message transfer transparent and visible. BRIEF DESCRIPTION OF THE DRAWINGS

[0073] Other features, objects and advantages of the present invention will become more apparent from the detailed description of non-limiting embodiments made with reference to the following drawings:

[0074] Figure 1 Design a diagram for the overall functionality of the message center;

[0075] Figure 2 This is a structural diagram of the sinking message center;

[0076] Figure 3 It is a sinking message control method;

[0077] Figure 4 Produce and consume message flow for the message center. DETAILED DESCRIPTION

[0078] The present invention is described in detail below in conjunction with specific embodiments. The following embodiments will help those skilled in the art to further understand the present invention, but are not intended to limit the present invention in any form. It should be noted that, for those of ordinary skill in the art, several changes and improvements can also be made without departing from the concept of the present invention. These all belong to the protection scope of the present invention.

[0079] The embodiment of the present invention provides a high-availability industrial message design system to solve the problems of message communication between applications in the ecological technology platform and improve the related business processing performance. The overall functional structure diagram is shown in Figure 1 As shown; To realize message production, consumption, queue monitoring and log record tracking, refer to Figure 2 As shown; for relevant control methods, refer to Figure 3 As shown, the relevant technical design process flow process reference Figure 4 The system includes: a telegram management module, a message management module, a basic middle platform-shared service module, and a message center console.

[0080] Among them, the telegram management module is associated with the basic middle platform-shared service module, and the telegram and shared service can be either a one-to-one relationship or a many-to-many relationship; the message management module is also associated with the basic middle platform-shared service module, and ordinary messages and shared services can be either a one-to-one relationship or a one-to-many relationship; the telegram management module and the message management module communicate with the message middleware at the bottom layer, and all communication information can be visualized and monitored through the message center console module.

[0081] Specifically, each module is described as follows:

[0082] Telegram management module: used to maintain and manage configuration information related to asynchronous messages (telegrams support multiple types of messages entering the same queue), and provides a visual management function interface related to the reception, consumption and monitoring of messages, so as to achieve the effect of full life cycle management of messages. The functions provided by this module are as follows:

[0083] One-stop registration of telegrams: mainly for registering asynchronous messages of telegram type, for classification management and maintenance;

[0084] Basic information management of telegrams: related operations management and maintenance including modification, deletion and query can be performed on registered telegrams, and queue channels will be automatically allocated for newly created telegrams;

[0085] Telegram structure management: business message body description can be performed for telegram messages, and relevant structure information can be configured for use in string message parsing;

[0086] Telegram registration progress tracking: Track the progress of one-stop registration messages, and proceed to the next registration operation for intermediate messages;

[0087] Telegram queue service management: Consumers can be configured for telegrams. The consumer service follows the REST standard. Once there is a message in the queue, it will actively consume and distribute the message.

[0088] Message sending history: You can trace the message sending history of the message sent to the message center. If the message fails to be sent, you can resend it according to business needs.

[0089] Message consumption history: You can trace the message consumption history of the messages sent to the message center. If the message consumption fails, you can re-consume it according to business needs.

[0090] Message management module: used to maintain and manage configuration information related to common messages (common messages are usually a type of message in a queue), and provides a visual management function interface related to the reception, consumption and monitoring of common messages, so as to achieve the effect of full life cycle management of common messages. The main functions provided by this module are as follows:

[0091] One-stop message registration: One-stop registration for common messages to specify relevant routing key information, queue names, etc.

[0092] Queue configuration management: You can modify, delete, and query the registered queue information;

[0093] Queue service management: When you need to specify a consumer for a queued message, you need to configure the relevant consumer on the corresponding queue first. The consumer service generally follows the REST standard specification. Once there is a message in the queue, it will actively consume and distribute the message.

[0094] Message production history: You can trace the production history of common messages sent to the message center. If you find that the production of a common message fails, you can re-produce it according to business needs.

[0095] Message consumption history: You can trace the message consumption history of common messages sent to the message center. If you find that common message consumption fails, you can re-consume it according to business needs.

[0096] Basic middle platform - shared service module: used to register and maintain relevant basic information of the service, and provide shared services to the outside world, such as SMS service, verification code service, email service, mobile message push service, etc., to provide favorable support for the interconnection between systems and service operation and maintenance.

[0097] The basic platform packages some microservices into shared services for the message center to configure and use. It provides the following basic services:

[0098] Production message service: When the business connects to asynchronous messages, it needs to store the messages in the message queue through this service interface, and then the plug-in end monitors and consumes them autonomously;

[0099] SMS service: When the business performs verification code verification or information reminder, the information is pushed according to the SMS service;

[0100] Sending email service: When the business performs verification code verification or information reminder, the information is pushed according to the sending email service;

[0101] Mobile message push service: When the business performs verification code verification or information reminder, information is pushed according to the mobile message push service;

[0102] In-site message service: When the business requires in-site notifications, announcements, or to-do reminders, information is pushed based on the in-site message service.

[0103] Message Center Console: Provides a visual management interface for monitoring the message middleware, mainly including the health monitoring of the RabbitMQ server cluster nodes, the monitoring of message channel-related communications, the monitoring of queue congestion, etc., providing convenient management tools for operation and maintenance personnel.

[0104] Specifically, the message center console includes:

[0105] Message server console: performs global monitoring on the message management middleware RabbitMQ, mainly including server node activity information, memory usage, and channel connection status.

[0106] Queue consumption status monitoring: Monitor the status of messages in the message queue to indicate whether the message is in the queue or being consumed.

[0107] Queue configuration information monitoring: Audit and verify message routing configuration information.

[0108] Queue information monitoring: You can monitor whether the queue is in working status.

[0109] The present invention also provides a high-availability industrial message design and implementation method, the method comprising:

[0110] Step S1: Register the message service; the menu path in this step: Basic Middle Platform → Service Management.

[0111] Follow the above operation entry: enter the shared service management page, click the "Add" button, enter the message service ID, service application, service category, service method name, service English name, whether the service is authorized, service category, service description, etc., and click the "Save" button to complete the registration of the message service information.

[0112] The message service standard specification adopts: S+"_"+first-level module name+"_"+second-level module name (optional)+"_"+2-digit serial number (if 2 digits are not enough, it can be expanded to 4 digits).

[0113] Step S2: Register the telegram information; through the menu path: Basic Middle Platform → Message Management → Telegram Management.

[0114] Follow the above operation entry: enter the telegram management page, select the "Telegram Information" page, click the "Add" button, enter the telegram number information, telegram name, telegram category, and the application to which the telegram belongs, and click the "Save" button to complete the addition.

[0115] Step S3: Message structure configuration; through the menu path: Basic Middle Platform → Message Management → Message Management.

[0116] Follow the above operation entry: Enter the message structure management page and register and configure the message structure information as needed. You can also import, modify, and delete existing structures.

[0117] Step S4: Configure the message queue information; through the menu path: Basic Middle Station → Message Management → Message Management.

[0118] Follow the above operation entry: Enter the message queue information management page, first add a queue, select the "Queue Information" page, click the "Add" button, enter the information, and click the "Save" button to complete the addition. You can unbind an existing message queue.

[0119] Queue naming rule: Q_first-level module_second-level module_serial number.

[0120] Is it a strong sequentiality: (No by default) Whether consumers in the queue consume in a strong sequential manner.

[0121] Step S5: Configure the telegram service information; through the menu path: Basic Middle Platform → Message Management → Telegram Management.

[0122] Follow the above operation entry: enter the message service information management page, select the "Message Service Information" page (you can also directly click the "Message Service" button in the message information operation bar), click the "Add" button, select the corresponding message and service information, and click the "Save" button to complete the configuration. You can unbind the existing message service.

[0123] Step S6: View the resume; through the menu path: Basic Middle Platform → Message Management → Telegram Management.

[0124] Follow the above operation entry: enter the message history viewing page, the user can click the "View History" button on the Send History / Receive Message History page to jump to the "History Details" page to troubleshoot problems encountered in the service call.

[0125] Step S7: Message registration; through the menu path: Basic Middle Platform → Message Management → Normal Message.

[0126] Follow the above operation entry: enter the one-stop message registration page, where users can register, modify, delete, and other operations on message information.

[0127] Step S8: Queue service management; through the menu path: Basic Middle Platform → Message Management → Normal Message.

[0128] Follow the above operation entry: Enter the queue service management page, where users can bind and unbind the relationship between the message queue and the consumer service.

[0129] Step S9: View message history; through the menu path: Basic Middle Platform → Message Management → Normal Message.

[0130] Follow the above operation entry: Enter the message history viewing page. Users can click the "View History" button on the message production history / consumption history page to jump to the "History Details" page to troubleshoot problems encountered in service calls.

[0131] Next, the present invention will be described in more detail.

[0132] Baowu Eco-Technology Platform: ePlat;

[0133] Scenario:

[0134] Baowu Ecological Technology Platform integrates nine components. One of them is the basic middle platform, which builds a message center for developer users. The message center provides a complete solution for business operations that do not require timely response to request results. The message center provides developers with queue information, queue service information, message production history, message consumption history and other functions. Through the message management page, queues can be added, queue services can be bound, and related history information of ordinary message production and consumption history can be viewed, so that the complete life cycle of ordinary messages can be managed from beginning to end.

[0135] 1) The user finds [One-stop message registration] in the basic middle platform-message center, clicks to enter, defines the message and registers relevant basic information, such as the application, routing rules, queue code, etc.

[0136] 2) Configure the consumer service for the queue where the message is registered to specify which consumer will consume and process the message once there is one in the current queue.

[0137] 3) With the help of the service market, the default format for parameter filling is table format. Users can refer to the production message service document to fill in parameter values, or directly call the service according to the default parameter values ​​provided. The service has parameter routing rules routingKey, message body messageBody, and application English name projectEname, all of which are required parameters.

[0138] 4) Click the "Test" button to execute the message production operation.

[0139] 5) Check the returned results in table format. The message is sent successfully, which is the return instruction after the message center receives the message. The returned results can be switched to JSON format.

[0140] 6) Users can view the message record information just produced on the message production history viewing page, and can view the complete message link information by viewing the details.

[0141] 7) Users can view the record information of the message just produced being consumed on the message consumption history viewing page, and can view the complete message link information by viewing the details.

[0142] The present invention has the following technical features:

[0143] Distributed: It integrates with RabbitMQ in plug-in mode and can be easily expanded horizontally.

[0144] High message reliability: The design provided by the present invention can ensure the management and monitoring of the entire life cycle of the message, so that all business messages passing through the message center can be traced back to their source, and failed messages can be resent or re-received.

[0145] High message stability: The design provided by the present invention connects the underlying message channel based on the Erlang language at the RabbitMQ middleware level, and does not need to establish a long link with the consumer end, thereby enhancing the stability of message forwarding.

[0146] Improve performance: The design scheme provided by the present invention expands and develops the function of forwarding and consuming relevant business messages based on the Erlang language at the RabbitMQ middleware level. The message is directly processed by the relevant business logic from the queue source end and directly connected to the business consumer end, omitting the transfer link, ensuring that the node or cluster resource utilization is maximized under the same configuration.

[0147] Message tracking: The design provided by the present invention realizes the full life cycle point log collection of business messages through ELK technology. It can track the entire life cycle process of messages from entry to exit through relevant point information, and push early warnings for abnormal points.

[0148] A high-availability industrial message design system and implementation method provided by the embodiment of the present invention can quickly configure message routing and consumption in combination with business scenarios, and the messages can be routed and consumed from the source end of the message middleware according to the configuration information, avoiding the channel occupancy limitation caused by establishing a connection by the client, and greatly improving the high stability of the message; the provided message embedding point can effectively connect the entire life cycle of the message from production to consumption, and can effectively track the ins and outs of the message, which provides convenience for the connection of business scenarios and ensures the high stability of the message.

[0149] Those skilled in the art know that, in addition to implementing the system and its various devices, modules, and units provided by the present invention in a purely computer-readable program code, the system and its various devices, modules, and units provided by the present invention can be completely implemented in the form of logic gates, switches, application-specific integrated circuits, programmable logic controllers, and embedded microcontrollers by logically programming the method steps to implement the same functions. Therefore, the system and its various devices, modules, and units provided by the present invention can be considered as a hardware component, and the devices, modules, and units included therein for implementing various functions can also be considered as structures within the hardware component; the devices, modules, and units for implementing various functions can also be considered as both software modules for implementing the method and structures within the hardware component.

[0150] The above describes the specific embodiments of the present invention. It should be understood that the present invention is not limited to the above specific embodiments, and those skilled in the art can make various changes or modifications within the scope of the claims, which does not affect the essence of the present invention. In the absence of conflict, the embodiments of the present application and the features in the embodiments can be combined with each other arbitrarily.

Claims

1. A high-availability industrial message design system, characterized in that: include: Telegram management module, message management module, basic middle platform-shared service module, and message center console; Telegram management module: Maintains and manages configuration information related to asynchronous messages of telegram type, and provides a visual management function interface related to the reception, consumption and monitoring of telegrams; among them, asynchronous messages of telegram type refer to the support of multiple types of telegrams into the same queue; Message management module: Maintains and manages configuration information related to common messages, and provides a visual management function interface related to the reception, consumption and monitoring of common messages; common messages refer to a type of message entering a queue; Basic middle platform - shared service module: register and maintain relevant basic information of services, provide shared services to the outside world, and provide favorable support for the interconnection and interoperability between systems and service operation and maintenance; Message center console: provides a visual management interface for monitoring message middleware and provides convenient management tools for operation and maintenance personnel; Among them, the message management module is associated with the basic middle platform-shared service module, and the message management module and the basic middle platform-shared service module are in a one-to-one relationship or a many-to-many relationship; There is also an association relationship between the message management module and the basic middle platform-shared service module. The message management module and the basic middle platform-shared service module have a one-to-one relationship or a one-to-many relationship; The telegram management module and the message management module communicate with the message middleware, and all communication information can be visually monitored through the message center console module; The message management module includes: One-stop registration of telegrams: register asynchronous messages of telegram type for classification management and maintenance; Basic information management of telegrams: perform related operations management and maintenance including modification, deletion, and query of registered telegrams, and automatically allocate queue channels for newly created telegrams; Telegram structure management: Describe the business message body for telegram messages and configure relevant structure information for use in parsing string telegrams; Telegram registration progress tracking: Track the progress of one-stop registration messages, and proceed to the next registration operation for intermediate messages; Telegram queue service management: configure consumers for telegrams. Consumer services follow the REST standard. Once there is a message in the queue, it will actively consume and distribute the message. Message sending history: trace the message sending history of the message sent to the message center. If the message fails to be sent, resend it according to business needs. Message consumption history: Tracing the message consumption history of messages sent to the message center. If the message consumption fails, re-consumption is performed according to business needs. The message management module includes: One-stop message registration: One-stop registration for common messages to specify relevant routing key information and queue names; Queue configuration management: perform related operations including modification, deletion and query of registered queue information; Queue service management: When you need to specify a consumer for a queued message, you need to configure the relevant consumer on the corresponding queue first. The consumer service follows the REST standard specification. Once there is a message in the queue, it will actively consume and distribute the message. Message production history: trace the production history of common messages sent to the message center. If it is found that the production of common messages fails, re-production is performed according to business needs. Message consumption history: Tracing the message consumption history of common messages sent to the message center. If it is found that the common message consumption fails, re-consumption is performed according to business needs.

2. The high-availability industrial message design system according to claim 1, characterized in that: The basic middle platform-shared service module includes: Production message service: When the business connects to asynchronous messages, it needs to store the messages in the message queue through this service interface, and then the plug-in end monitors and consumes them autonomously; SMS service: When the business performs verification code verification or information reminder, the information is pushed according to the SMS service; Sending email service: When the business performs verification code verification or information reminder, the information is pushed according to the sending email service; Mobile message push service: When the business performs verification code verification or information reminder, information is pushed according to the mobile message push service; In-site message service: When the business requires in-site notifications, announcements, or to-do reminders, information is pushed based on the in-site message service.

3. The high-availability industrial message design system according to claim 1, characterized in that: The message center console includes: Message server console: performs global monitoring on the message management middleware RabbitMQ, mainly including server node activity information, memory usage, and channel connection status; Queue consumption status monitoring: monitor the status of messages in the message queue to determine whether the message is in the queue or being consumed; Queue configuration information monitoring: audit and verify message routing configuration information; Queue information monitoring: monitor whether the queue is in working state.

4. A high-availability industrial message design and implementation method, characterized in that: A high-availability industrial message design system based on any one of claims 1 to 3, comprising: Step S1: Complete the registration message service in service management through the basic middle platform; Step S2: Register the message information in the message management through the basic middle platform and message management; Step S3: Complete the configuration of the message structure in the message management through the basic middle platform and message management; Step S4: Configure the message queue information in the message management through the basic middle platform and message management; Step S5: Configure the message service information in the message management through the basic middle platform and message management; Step S6: Check the history in the message management through the basic middle platform and message management; Step S7: Complete message registration in ordinary messages through the basic middle platform and message management; Step S8: Perform queue service management in common messages through the basic middle platform and message management; Step S9: View the message history in ordinary messages through the basic middle platform and message management.

5. The high-availability industrial message design and implementation method according to claim 4 is characterized in that: The operation entry for registering the message service in step S1 includes: entering the shared service management page, clicking the Add button, entering the message service ID, the application to which the service belongs, the service category, the service method name, the service English name, whether the service is authorized, the service classification, and the service description, and clicking the Save button to complete the registration of the message service information.

6. The high-availability industrial message design and implementation method according to claim 4, characterized in that: The operation entry for registering the telegram information in step S2 includes: entering the telegram management page, selecting the telegram information page, clicking the Add button, entering the telegram number information, telegram name, telegram category, and the application to which the telegram belongs, and clicking the Save button to complete the addition.

7. The high-availability industrial message design and implementation method according to claim 4 is characterized in that: The operation entry for configuring the message structure in step S3 includes: entering the message structure management page, registering and configuring the message structure information as needed, or performing related import, modification or deletion operations on the existing structure.

8. The high-availability industrial message design and implementation method according to claim 4, characterized in that: The operation entry for configuring the message queue information in step S4 includes: entering the message queue information management page, adding a queue, selecting the queue information page, clicking the Add button, entering information, and clicking the Save button to complete the addition; The operation entry for configuring the message service information in step S5 includes: entering the message service information management page, selecting the message service information page, clicking the Add button, selecting the corresponding message and service information, and clicking the Save button to complete the configuration; The operation entry for viewing the history in step S6 includes: entering the message history viewing page, the user clicks the view history button on the send history / receive message history page, jumps to the history details page, and checks the problems encountered in the service call; The operation entry of the message registration in step S7 includes: entering the one-stop message registration page, where the user performs related operations including message information registration, modification and deletion; The operation entry of the queue service management in step S8 includes: entering the queue service management page, and the user performs binding or unbinding operation on the queue service management page for the association relationship between the message queue and the consumer service; The operation entry for viewing the message history in step S9 includes: entering the message history viewing page, the user clicks the view history button on the message production history / consumption history page, jumps to the history details page, and checks the problems encountered in the service call.

Images