A message interaction system suitable for in-container deployment of a regulation system

Abstract

The application provides a message interaction system suitable for container deployment of a regulation system, comprising: a central message cluster: providing a central message cluster service of one master and multiple backups based on a Raft protocol, a master node responding to a request of a unified message transceiving module and storing messages of each topic; a message channel subscription module: managing a message channel subscribed by a business application and a mapping relationship between the message channel and a message topic of the central message cluster; the unified message transceiving module: according to the mapping relationship of the message channel subscription module, sending a message sent by the business application to a specified topic of the central message cluster, and meanwhile collecting the message of the specified topic from the central cluster and distributing the message to the business application subscribed to the specified channel; and a message read-write management module: persistently storing historical messages into a file.

Description

Technical Field

[0001] This invention belongs to the field of power automation system technology, and in particular relates to a message interaction system suitable for containerized deployment in control systems. Background Technology

[0002] In power grid dispatch automation systems, with the continuous expansion of the power grid and the sustained growth in the number of new energy power plants connected, the traditional front-end data acquisition deployment model based on a fixed number of physical servers can no longer meet the needs of power system development. Containerized deployment of front-end data acquisition, due to its advantages of speed, efficiency, low resource consumption, and convenient data recovery, is gradually being integrated into power grid dispatch automation systems, promoting rapid deployment and convenient management of front-end data acquisition and enabling flexible expansion of the system's acquisition scale. However, since containers are dynamically allocated resources without fixed IP addresses, this poses challenges to message interaction between services within containers and between containers and services on physical servers. Therefore, providing a new message interaction method for control-related services between containers and between containers and physical servers has become crucial for supporting the containerized deployment of services in power grid dispatch automation systems.

[0003] Existing technology patent CN119276847B discloses a message processing method, system, and device applied to a distributed cluster system. The method includes: obtaining a SIP request message sent by a higher-level platform through a higher-level domain, and sending the SIP request message to a lower-level domain; forwarding the SIP request message to a corresponding lower-level device through the lower-level domain, whereby the lower-level device generates a first response message based on the SIP request message; storing key information of the first response message through a caching middleware; querying the key information corresponding to the SIP request message in the caching middleware through the higher-level domain, and assembling the key information to generate a second response message of the SIP request message. This method bypasses the management of SIP session state, enabling SIP message sending without session state and cross-platform SIP service message interaction. Summary of the Invention

[0004] Because containers are dynamically allocated resources without fixed IP addresses, there is no reliable communication between services within containers and between containers and services on physical servers. Furthermore, it is difficult to rely on IP addresses for message passing and historical message retrieval. Therefore, a message exchange system is needed to facilitate message passing between services within containers and between containers and services on physical servers, providing unified management of message exchange and eliminating reliance on IP addresses for message passing.

[0005] To solve the above-mentioned technical problems, the technical solution provided by the present invention is: a message interaction system suitable for containerized deployment in a control system, comprising:

[0006] Central Message Cluster: Provides a one-master-multiple-standby central message cluster service based on the Raft protocol. The master node responds to requests from the unified message sending and receiving module and stores messages for each topic.

[0007] Message Channel Subscription Module: Manages message channels subscribed to by business applications and the mapping relationship between message channels and message topics in the central message cluster;

[0008] Unified message sending and receiving module: Based on the mapping relationship of the message channel subscription module, it sends messages sent by business applications to the specified topics of the central message cluster, and at the same time retrieves messages of the specified topics from the central cluster messages and distributes them to business applications that have subscribed to the specified channels;

[0009] Message read / write management module: Persistently stores historical messages to files.

[0010] Specifically, the central message cluster adopts a multi-node distributed cluster deployment method with one master and multiple backups. Once the primary central message node fails, the entire cluster will automatically elect a new primary message node to take over the entire cluster.

[0011] Specifically, in the central message cluster, message nodes in standby state will periodically send heartbeat messages to the primary message node to inform it of their status. After receiving the heartbeat message, the primary message node will send the data that has not yet been synchronized to the standby message node to the standby message node.

[0012] Specifically, the central message cluster provides a unified external interface for sending and receiving messages. Once any message node in the cluster becomes a master node, it provides a unified interface access method to the outside world.

[0013] Specifically, the message channel subscription module adopts a shared memory management approach to uniformly manage the set of channels subscribed to by business applications, maintain the mapping relationship between channel numbers and business applications, and the mapping relationship between the topics of the central message cluster and the message channels subscribed to by business applications.

[0014] Specifically, when the unified message sending and receiving agent module receives a message sent by a business application, it determines which channel the message should be sent to, and then interacts with the message channel subscription module to determine which topic in the central message cluster the message should be sent to before sending the message.

[0015] Specifically, the unified message sending and receiving agent module accesses the message channel subscription module. The message sending and receiving agent module can query which channels are subscribed to by applications and the topics of the central message cluster corresponding to these channels. After receiving messages from a specific topic in the central message cluster, the message sending and receiving agent module distributes these messages to the various business applications running.

[0016] Specifically, after receiving a message from the producer, the central message node will call the message read / write management module to persistently store the message in a file.

[0017] Specifically, after receiving a message, the message read / write management module sequentially writes the message to the message storage data file and updates the corresponding index file. When a consumer needs to retrieve a message, the message read / write management module retrieves the specified message and returns the retrieved message or message set to the message consumer.

[0018] Specifically, when the message read / write management module performs message retrieval, it will quickly locate the message in the message storage data file by searching for the message number in the corresponding index file.

[0019] The beneficial effects of this invention are: the distributed one-master-multiple-standby central message cluster provided by this invention persistently stores the messages received from business applications in the power control system container and on the physical server into the entire central cluster, ensuring that important messages are not lost; the central message cluster implementation based on the Raft protocol can ensure that if the cluster master node fails, a new standby node will be elected as the new master node through cluster election, ensuring the high availability of the entire cluster.

[0020] The message channel subscription module and message sending and receiving agent module provided by this invention realize message communication between messages within containers and physical servers and the central message cluster, shielding applications running within containers or on physical servers from the conversion work between different message formats. Attached Figure Description

[0021] Figure 1 This is a schematic diagram of the system structure of the present invention.

[0022] Figure 2 This is a schematic diagram of the central message cluster of the present invention. Detailed Implementation

[0023] The present invention will now be described in detail with reference to the accompanying drawings and embodiments.

[0024] Example 1: A message interaction system suitable for containerized deployment in a control system, such as... Figure 1 As shown, it includes:

[0025] Central Message Cluster: Provides a one-master-multiple-standby central message cluster service based on the Raft protocol. The master node responds to requests from the unified message sending and receiving module and stores messages for each topic.

[0026] Message Channel Subscription Module: Manages message channels subscribed to by business applications and the mapping relationship between message channels and message topics in the central message cluster;

[0027] Unified message sending and receiving module: Based on the mapping relationship of the message channel subscription module, it sends messages sent by business applications to the specified topics of the central message cluster, and at the same time retrieves messages of the specified topics from the central cluster messages and distributes them to business applications that have subscribed to the specified channels;

[0028] Message read / write management module: Persistently stores historical messages to files.

[0029] Specifically, in this embodiment, the central message cluster adopts a multi-node distributed cluster deployment method with one master and multiple backups. Once the primary central message node fails, the entire cluster will automatically elect a new primary message node to take over the entire cluster.

[0030] Specifically, in this embodiment, as Figure 2 As shown, message nodes in standby mode in the central message cluster periodically send heartbeat messages to the primary message node to inform it of their status. After receiving the heartbeat message, the primary message node will send the data that has not yet been synchronized to the standby message node to the standby message node.

[0031] Specifically, in this embodiment, the central message cluster provides a unified external interface for sending and receiving messages. After any message node in the cluster becomes a master node, it provides a unified interface access method to the outside world.

[0032] Specifically, in this embodiment, the message channel subscription module adopts a shared memory management approach to uniformly manage the set of channels subscribed by business applications, maintain the mapping relationship between channel numbers and business applications, and the mapping relationship between the topics of the central message cluster and the message channels subscribed by business applications.

[0033] Specifically, in this embodiment, the unified message sending and receiving agent module receives a message sent by a business application, determines which channel the message is sent to, and then interacts with the message channel subscription module to determine which topic in the central message cluster the message will be sent to before sending the message.

[0034] Specifically, in this embodiment, the unified message sending and receiving agent module accesses the message channel subscription module. The message sending and receiving agent module can query which channels are subscribed to by applications and the topics of the central message cluster corresponding to these channels. After receiving messages from a specific topic of the central message cluster, the message sending and receiving agent module distributes these messages to the various business applications running.

[0035] Specifically, in this embodiment, after receiving a message sent by the producer, the central message node will call the message read / write management module to persistently store the message in a file.

[0036] Specifically, in this embodiment, after receiving a message, the message read / write management module sequentially writes the message into the message storage data file and updates the index file corresponding to the data file. When a consumer needs to retrieve a message, the message read / write management module retrieves the specified message and returns the retrieved message or message set to the message consumer.

[0037] Specifically, in this embodiment, when the message read / write management module performs message retrieval, it will quickly locate the position of the message in the message storage data file by searching the message number in the corresponding index file.

[0038] The distributed master-slave central message cluster provided by this invention persistently stores messages received from business applications within the power control system container and on the physical server into the entire central cluster, ensuring that important messages are not lost. The central message cluster implementation based on the Raft protocol ensures that if the cluster master node fails, a new backup node will be elected as the new master node through cluster election, thus guaranteeing the high availability of the entire cluster.

[0039] The message channel subscription module and message sending and receiving agent module provided by this invention realize message communication between messages within containers and physical servers and the central message cluster, shielding applications running within containers or on physical servers from the conversion work between different message formats.

[0040] In this embodiment, the specific steps for message nodes to send and receive messages are as follows:

[0041] Step A: The message node provides message bus service. Message producers send messages to the message bus through the message sending interface, and message consumers receive messages from the message bus through the channel subscription interface and message receiving interface.

[0042] Step B: The message node's message read / write management module provides the functionality to persistently store messages to disk;

[0043] Step C: After the message is written to the disk, it exists in the form of a data file. At the same time, an offset index is generated in the index file according to the rule of a fixed number of messages, so as to improve the speed of retrieving messages from the disk.

[0044] Step D: The client link management module provided by the message node can monitor the link status between producers and consumers;

[0045] Step E: The subscription channel management module provided by the message node enables the message bus service to distribute messages based on the subscription channel status.

[0046] Example 2: This example provides a message interaction system between containers and between containers and physical servers. Containerized deployment is a software delivery and operation method based on container technology. By packaging applications and their dependencies into independent containers, consistent operation across environments can be achieved.

[0047] In power grid dispatch automation systems, with the continuous expansion of the power grid and the sustained growth in the number of new energy power plants connected, the traditional front-end data acquisition deployment model based on a fixed number of physical servers can no longer meet the needs of power system development. Containerized deployment of front-end data acquisition, due to its advantages of speed, efficiency, low resource consumption, and convenient data recovery, is gradually being integrated into power grid dispatch automation systems, promoting rapid deployment and convenient management of front-end data acquisition and enabling flexible expansion of the system's acquisition scale. However, since containers are dynamically allocated resources without fixed IP addresses, this poses challenges to message interaction between services within containers and between containers and services on physical servers. Therefore, providing a new message interaction method for control-related services between containers and between containers and physical servers has become crucial for supporting the containerized deployment of services in power grid dispatch automation systems.

[0048] This embodiment provides a containerized deployment that can support the operation of the control system, improve the flexibility of the expansion of the front-end data acquisition service of the control system, and meet the data acquisition needs of the power system as its scale continues to grow.

[0049] To achieve the above objectives, the present invention is implemented using the following technical solution:

[0050] In a first aspect, the present invention provides a distributed, highly available message storage center, comprising:

[0051] The central message cluster adopts a multi-node distributed deployment with one master and multiple backups. Based on the Raft protocol, the message management center possesses high availability. If the primary central message node fails, the entire cluster automatically elects a new primary message node to take over, ensuring the stability and continuity of the message cluster.

[0052] Furthermore, to ensure data consistency across the entire central message cluster, message nodes in standby mode need to periodically synchronize data with the primary message node. To achieve this, standby message nodes periodically send heartbeat messages to the primary message node to inform it of their status (how much data has been synchronized). Upon receiving the heartbeat message, the primary message node sends the data that has not yet been synchronized to the standby message nodes.

[0053] Furthermore, to ensure functional consistency across the entire central message cluster, a unified external interface is provided for sending and receiving messages. Once any message node in the cluster becomes a master node, it provides a unified interface access method. Clients send and receive messages through this unified interface call method.

[0054] Secondly, the present invention provides a unified message channel subscription module suitable for containerized deployment of control system applications, including:

[0055] The unified message channel subscription module, suitable for containerized deployment, manages the message channel subscription information of business applications within the power control system container and on the physical server. It is responsible for managing the message channel subscription between business applications within the container and on the physical server and the central message cluster running on the physical server, as well as the mapping management between channels and topics. To achieve this, the message channel subscription module uniformly manages the set of channels subscribed to by business applications within the container and on the physical server. For each application within the container and on the physical server that has subscribed to a message channel, the module maintains the mapping relationship between channel numbers and business applications.

[0056] Furthermore, the channel subscription module is also responsible for managing the mapping relationship between the topics of the central message cluster and the message channels subscribed by business applications within the container and on the physical server. This module adopts a shared memory management method, which makes the lookup of mapping relationships highly efficient and supports the message interaction of business applications within the power control system container and on the physical server.

[0057] Thirdly, the present invention provides a unified message sending and receiving agent module suitable for containers and physical servers, including:

[0058] To enable communication between business applications within the power control system container and on the physical server, frequent message sending and receiving is required. The message sending and receiving agent module implements these functions.

[0059] Furthermore, when the message sending and receiving agent receives messages from business applications within the container and on the physical server, it determines which channel the message should be sent to, and then interacts with the message channel subscription module to determine which topic in the central message cluster the message should be sent to before sending the message.

[0060] Furthermore, by accessing the message channel subscription module, the message sending and receiving agent module can query which applications running in containers or on physical servers are subscribed to each channel, as well as the topics of the central message cluster corresponding to these channels. After receiving messages from a specific topic in the central message cluster, the message sending and receiving agent module distributes these messages to the various business applications running in containers or on physical servers.

[0061] Fourthly, the present invention provides a message read / write management module capable of high-speed message persistence and message retrieval, comprising:

[0062] Power control systems often need to trace and query historical messages. To achieve this, after receiving messages sent by producers, the central message node calls the message read and write management module to persistently store the messages in files.

[0063] Furthermore, after receiving a message, the message read / write management module sequentially writes the message into the message storage data file and updates the corresponding index file of the data file. The sequential appending method of writing messages into the file ensures the efficiency of message writing to the file.

[0064] Furthermore, when a consumer needs to retrieve a message, the message read / write management module retrieves the specified message and returns the retrieved message or message set to the message consumer.

[0065] Furthermore, when performing message retrieval, the message read / write management module will quickly locate the message in the message storage data file by searching for the message number in the corresponding index file, thereby achieving fast message retrieval.

[0066] The specific message sending and receiving process is as follows:

[0067] Step A: The application inside the container calls the message sending interface to send the message to the unified message sending and receiving module;

[0068] Step B: The unified message sending and receiving module obtains the message sending channel by parsing the message messages of the application, and then obtains the topic corresponding to the channel through the message channel subscription module;

[0069] Step C: The unified message sending and receiving module sends messages sent by the application in the container to a specific topic in the central message cluster by calling the unified interface provided by the central message cluster;

[0070] Step D: The application within the container calls the message channel subscription module to subscribe to the specified message channel;

[0071] Step E: The unified message sending and receiving module obtains the topic of the central message cluster corresponding to the specified message channel by querying the message channel subscription module;

[0072] Step F: The unified message sending and receiving module receives messages on a specified topic by calling the unified interface provided by the central message cluster;

[0073] Step G: The application inside the container calls the message receiving interface to receive messages from the unified message sending and receiving module.

[0074] Example 3: A message interaction system suitable for containerized deployment in a control system, comprising:

[0075] Central Message Cluster: Provides a one-master-multiple-standby central message cluster service based on the Raft protocol. The master node responds to requests from the unified message sending and receiving module and stores messages for each topic.

[0076] Message Channel Subscription Module: Manages message channels subscribed to by business applications and the mapping relationship between message channels and message topics in the central message cluster;

[0077] Unified message sending and receiving module: Based on the mapping relationship of the message channel subscription module, it sends messages sent by business applications to the specified topics of the central message cluster, and at the same time retrieves messages of the specified topics from the central cluster messages and distributes them to business applications that have subscribed to the specified channels;

[0078] Message read / write management module: Persistently stores historical messages to files.

[0079] Specifically, in this embodiment, the central message cluster adopts a multi-node distributed cluster deployment method with one master and multiple backups. Once the primary central message node fails, the entire cluster will automatically elect a new primary message node to take over the entire cluster.

[0080] Specifically, in this embodiment, the message nodes in the standby state in the central message cluster will periodically send heartbeat messages to the primary message node to inform it of their status. After receiving the heartbeat message, the primary message node will send the data that has not yet been synchronized to the standby message node to the standby message node.

[0081] Specifically, in this embodiment, the central message cluster provides a unified external interface for sending and receiving messages. After any message node in the cluster becomes a master node, it provides a unified interface access method to the outside world.

[0082] Specifically, in this embodiment, the message channel subscription module adopts a shared memory management approach to uniformly manage the set of channels subscribed by business applications, maintain the mapping relationship between channel numbers and business applications, and the mapping relationship between the topics of the central message cluster and the message channels subscribed by business applications.

[0083] Specifically, in this embodiment, the unified message sending and receiving agent module receives a message sent by a business application, determines which channel the message is sent to, and then interacts with the message channel subscription module to determine which topic in the central message cluster the message will be sent to before sending the message.

[0084] Specifically, in this embodiment, the unified message sending and receiving agent module accesses the message channel subscription module. The message sending and receiving agent module can query which channels are subscribed to by applications and the topics of the central message cluster corresponding to these channels. After receiving messages from a specific topic of the central message cluster, the message sending and receiving agent module distributes these messages to the various business applications running.

[0085] Specifically, in this embodiment, after receiving a message sent by the producer, the central message node will call the message read / write management module to persistently store the message in a file.

[0086] Specifically, in this embodiment, after receiving a message, the message read / write management module sequentially writes the message into the message storage data file and updates the index file corresponding to the data file. When a consumer needs to retrieve a message, the message read / write management module retrieves the specified message and returns the retrieved message or message set to the message consumer.

[0087] Specifically, in this embodiment, when the message read / write management module performs message retrieval, it will quickly locate the position of the message in the message storage data file by searching the message number in the corresponding index file.

[0088] The specific implementation process is as follows:

[0089] Step A: The data acquisition program and command issuing program in the front-end container subscribe to the specified message channel by calling the subscription interface. After receiving the request, the message channel subscription module maps the specified message channel and the corresponding front-end data acquisition application and command issuing application and stores them in shared memory.

[0090] Step B: After receiving the front-end channel subscription request, the message channel subscription module not only saves the mapping relationship between the channel and the front-end data acquisition application and the command issuing application, but also obtains the message topic of the central message cluster that the front-end data acquisition application and the command issuing application in the container need to subscribe to by parsing the subscription request.

[0091] Step C: The unified message sending and receiving module continuously polls and reads the shared memory managed by the message channel subscription module. By checking the topic types subscribed to by the pre-instruction issuing application in the container in the shared memory, it calls the external interface of the central message cluster to receive messages of the corresponding topic. Then, by querying the mapping relationship between topics and channels, and channels and pre-instruction issuing applications in the subscribed shared memory, it sends the received control messages to the corresponding instruction issuing application through a separate link.

[0092] Step D: The unified message sending and receiving module continuously polls and reads the shared memory managed by the message channel subscription module. By viewing the mapping relationship between topics and channels in the shared memory, it forwards the message collected by the data collection application to the central message cluster through another separate link.

[0093] Step E: The control program running on the physical node subscribes to the specified message channel by calling the subscription interface. After receiving the request, the message channel subscription module maps the specified data channel and the corresponding control program and stores it in shared memory.

[0094] Step F: After receiving the channel subscription request from the control program, the message channel subscription module not only saves the mapping relationship between the channel and the control program application, but also obtains the message topics of the central message cluster that the control program needs to subscribe to by parsing the subscription request;

[0095] Step G: The unified message sending and receiving module continuously polls and reads the shared memory managed by the message channel subscription module. By checking the topic types subscribed to by the control program in the shared memory, it calls the external interface of the central message cluster to receive messages of the corresponding topics. Then, by querying the mapping relationship between topics and channels, and channels and control programs in the subscribed shared memory, it sends the received messages to the corresponding control programs through separate links.

[0096] Step H: The unified message sending and receiving module continuously polls and reads the shared memory managed by the message channel subscription module. By checking the mapping relationship between topics and channels in the shared memory, it forwards the control messages sent by the control program to the central message cluster through another separate link.

[0097] Although the present invention has been described in detail with reference to the foregoing embodiments, those skilled in the art can still modify the technical solutions described in the foregoing embodiments or make equivalent substitutions for some of the technical features. Any modifications, equivalent substitutions, improvements, etc., made within the spirit and principles of the present invention should be included within the protection scope of the present invention.

Claims

1. A message interaction system suitable for containerized deployment within a control system, characterized in that, The system includes a central message cluster, where the master node responds to requests from the unified message sending and receiving module and stores messages for various topics; a message channel subscription module manages message channels subscribed to by applications, maintaining the mapping between channel numbers and applications, as well as the mapping between message channels and message topics in the central message cluster. Applications within the container call this module to subscribe to a specified message channel; the unified message sending and receiving module, based on the mapping relationship of the message channel subscription module, allows applications within the container to send messages to the unified message sending and receiving module via a message sending interface. The unified message sending and receiving module, through a unified interface provided by the central message cluster, forwards messages sent by applications within the container to the specified topics in the central message cluster, and simultaneously retrieves messages from the central cluster and distributes them to applications that have subscribed to the specified channels. Applications within the container call the message receiving interface to retrieve messages from the unified message sending and receiving module; and a message read / write management module stores historical messages that have been sent and received in files.

2. The message interaction system suitable for containerized deployment in a control system according to claim 1, characterized in that, The central message cluster adopts a multi-node distributed one-master-multiple-standby cluster deployment mode, providing a one-master-multiple-standby central message cluster service based on the Raft protocol. Once a node in the primary central message cluster fails, the entire cluster will automatically elect a new primary message node to take over the entire cluster.

3. The message interaction system suitable for containerized deployment in a control system according to claim 1 or 2, characterized in that, In the central message cluster, message nodes in standby state will periodically send heartbeat messages to the primary message node to inform it of their status. After receiving the heartbeat message, the primary message node will send the data that has not yet been synchronized to the standby message node to the standby message node.

4. The message interaction system suitable for containerized deployment in a control system according to claim 3, characterized in that, The central message cluster provides a unified external interface for sending and receiving messages. Once any message node in the cluster becomes a master node, it provides a unified interface access method to the outside world.

5. The message interaction system suitable for containerized deployment in a control system according to claim 1, characterized in that, The message channel subscription module adopts a shared memory management approach to uniformly manage the set of channels subscribed to by applications, maintain the mapping relationship between channel numbers and applications, and the mapping relationship between topics in the central message cluster and message channels subscribed to by applications.

6. The message interaction system suitable for containerized deployment in a control system according to claim 1, characterized in that, When the unified message sending and receiving module receives a message from the application, it determines which channel the message should be sent to. Then, by interacting with the message channel subscription module, it determines which topic in the central message cluster the message should be sent to before sending the message.

7. The message interaction system suitable for containerized deployment in a control system according to claim 6, characterized in that, The unified message sending and receiving module accesses the message channel subscription module to query the applications that have subscribed to each message channel, as well as the topics of the central message cluster corresponding to these message channels; after receiving messages from a specific topic of the central message cluster, the message sending and receiving module distributes these messages to the applications running.

8. The message interaction system suitable for containerized deployment in a control system according to claim 1, characterized in that, After receiving a message from the producer, the master node of the central message cluster will call the message read / write management module to persistently store the message in a file.

9. The message interaction system suitable for containerized deployment in a control system according to claim 8, characterized in that, After receiving a message, the message read / write management module sequentially writes the message to the message storage data file and updates the corresponding index file. When a consumer needs to retrieve a message, the message read / write management module retrieves the specified message and returns the retrieved message or message set to the message consumer.

10. The message interaction system suitable for containerized deployment in a control system according to claim 9, characterized in that, When performing message retrieval, the message read / write management module will quickly locate the message in the message storage data file by searching for the message number in the corresponding index file.

Images