Method, device and system for using message middleware in power dispatch automation system
By configuring mapping relationships to convert message identifiers to message middleware configurations, the problem of diverse message middleware requirements in the new generation of power dispatch automation systems is solved, achieving ease of use and cost reduction.
Patent Information
- Application Number
- CN202310526176.X
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- Filing Date
- 2023-05-11
- Publication Date
- 2026-02-10
- Estimated Expiration
- 2043-05-11
AI Technical Summary
In the new generation of power dispatch automation systems, a single message middleware cannot meet the diverse message interaction needs, which requires developers to frequently learn and adjust business functions, increasing development and maintenance costs.
By configuring mapping relationships, message identifiers are converted to message middleware configurations, enabling unified and easy-to-use message sending and receiving, and reducing dependence on business functions.
It improves the ease of use of message middleware, reduces the development and maintenance costs of business functions, and minimizes the impact of message middleware upgrades or changes on business functions.
Smart Images

Figure CN116567055B_ABST
Abstract
Description
Technical Field
[0001] This invention belongs to the field of power dispatch automation, and specifically relates to a method, device and system for using message middleware in a power dispatch automation system. Background Technology
[0002] Message middleware is a supporting software system based on queuing and message passing technologies, providing synchronous or asynchronous, reliable message transmission for application systems in a network environment. It is widely used in power dispatch automation systems. Traditional power dispatch automation systems are built in a siloed manner, with limited information exchange between systems. Furthermore, power dispatch automation systems primarily rely on primary equipment information to achieve power grid monitoring and analysis capabilities, collecting primary equipment information from substations via power telecontrol protocols. Message middleware is mainly used for internal information exchange within the system, and all message exchange scenarios have the same requirements for message middleware. Generally, a single message middleware is used uniformly for message exchange in power dispatch automation systems.
[0003] In recent years, to support the construction of new power systems, a new generation of dispatching technology support systems has been newly designed and developed. These systems have significantly improved in terms of the scope of business information perception and the degree of system collaboration, leading to new message interaction scenarios. These scenarios place new demands on message middleware. The performance, security, and throughput requirements vary across different scenarios, making it impossible to meet the needs of all message interaction scenarios with a single message middleware. Therefore, the message middleware used in the new generation of dispatching technology support systems has evolved from a single type to a diversified approach. Each message middleware has a different usage method. Developers learn how to use the message middleware by studying the accompanying user manuals. However, due to the low frequency of use of message middleware, relearning is required for subsequent use, resulting in high development costs for business functions. Furthermore, since business functions directly use message middleware for message sending and receiving, adjustments to the business function code are necessary when the message middleware is upgraded or changed, leading to high operational risks and costs for business functions. Summary of the Invention
[0004] To address the aforementioned issues, this invention proposes a method, apparatus, and system for using message middleware in a power dispatch automation system. This system enables the use of different message middleware for sending and receiving messages in a unified and easy-to-use manner, thereby improving the usability of message middleware and reducing the development and maintenance costs of business functions.
[0005] To achieve the above-mentioned technical objectives and effects, the present invention is implemented through the following technical solution:
[0006] In a first aspect, the present invention provides a method for using a message middleware in a power dispatch automation system, applied to a sending operation module, comprising:
[0007] Based on the received message identifier and the preset configuration mapping relationship, find out the configuration required for the message middleware to send / receive message content;
[0008] The received message content corresponding to the message identifier, along with the configuration required for the message middleware to send / receive the message content, is sent to the corresponding message middleware. This allows the receiving operation module to receive the message content, the configuration required for the message middleware to send / receive the message content, and additional information related to the message middleware from the message receiving function module of the message middleware. The module then converts the configuration required for the message middleware to send / receive the message content into a message identifier based on the preset configuration mapping relationship.
[0009] Optionally, the preset configuration mapping relationship is the correspondence between message identifiers and the configurations required for the message middleware to send / receive message content.
[0010] Optionally, the message identifier is a message type designed for business purposes.
[0011] Optionally, when the message middleware is the message bus of the power dispatch automation system, the configuration required for the message middleware to send / receive message content includes the message channel number and the message type number.
[0012] Secondly, this invention provides a method for using message middleware in a power dispatch automation system, applied to a receiving operation module.
[0013] include:
[0014] Receive message content from the message receiving module of the message middleware, the configuration required for the message middleware to send / receive message content, and additional information related to the message middleware;
[0015] The configuration required for the message middleware to send / receive message content is converted into message identifiers based on the preset configuration mapping relationship;
[0016] The configuration required for the message middleware to send / receive message content is obtained through the following method:
[0017] The sending operation module uses the received message identifier and the preset configuration mapping relationship to find the configuration required for the message middleware to send / receive message content;
[0018] The sending operation module sends the received message content corresponding to the message identifier, along with the configuration required for the message middleware to send / receive message content, to the corresponding message middleware.
[0019] Optionally, the preset configuration mapping relationship is the correspondence between message identifiers and the configurations required for the message middleware to send / receive message content.
[0020] Optionally, the message identifier is a message type designed for business purposes.
[0021] Optionally, when the message middleware is the message bus of the power dispatch automation system, the configuration required for the message middleware to send / receive message content includes the message channel number and the message type number.
[0022] Thirdly, the present invention provides a message middleware application device in a power dispatch automation system, applied to a sending operation module, comprising:
[0023] The configuration acquisition unit required for the message middleware to send / receive message content converts the received message identifier into the configuration required for the message middleware to send / receive message content based on the received message identifier and the preset configuration mapping relationship.
[0024] The transmission unit is used to send the received message content corresponding to the message identifier, along with the configuration required for the message middleware to send / receive the message content, to the corresponding message middleware. This allows the receiving operation module to receive the message content, the configuration required for the message middleware to send / receive the message content, and additional information related to the message middleware from the message receiving function module of the message middleware. The receiving module then converts the configuration required for the message middleware to send / receive the message content into a message identifier based on the preset configuration mapping relationship.
[0025] Fourthly, the present invention provides a message middleware application device in a power dispatch automation system, applied to a receiving operation module, comprising:
[0026] The data acquisition unit is used to receive message content, configuration required for the message middleware to send / receive message content, and additional information related to the message middleware from the message receiving function module of the message middleware.
[0027] The transmission unit is used to convert the configuration required by the message middleware to send / receive message content into message identifiers based on the preset configuration mapping relationship;
[0028] The configuration required for the message middleware to send / receive message content is obtained through the following method:
[0029] The sending operation module uses the received message identifier and the preset configuration mapping relationship to find the configuration required for the message middleware to send / receive message content corresponding to the message identifier;
[0030] The sending operation module sends the received message content corresponding to the message identifier, along with the configuration required for the message middleware to send / receive message content, to the corresponding message middleware.
[0031] Fifthly, the present invention provides a message middleware usage system in a power dispatch automation system, characterized in that it includes a storage medium and a processor;
[0032] The storage medium is used to store instructions;
[0033] The processor is configured to operate according to the instructions to perform the method according to any one of the first aspects.
[0034] Sixthly, the present invention provides a message middleware usage system in a power dispatch automation system, including a storage medium and a processor;
[0035] The storage medium is used to store instructions;
[0036] The processor is configured to operate according to the instructions to perform the method according to any one of the first aspects.
[0037] In a seventh aspect, the present invention provides a message middleware usage system in a power dispatch automation system, including a sending operation module and a receiving operation module;
[0038] The sending operation module finds the configuration required for the message middleware to send / receive message content corresponding to the message identifier based on the received message identifier and the preset configuration mapping relationship; and sends the received message content corresponding to the message identifier, along with the configuration required for the message middleware to send / receive message content, to the corresponding message middleware.
[0039] The receiving operation module receives message content, configuration required for the message middleware to send / receive message content, and additional information related to the message middleware from the message receiving function module of the message middleware, and converts the configuration required for the message middleware to send / receive message content into a message identifier based on the preset configuration mapping relationship.
[0040] Compared with the prior art, the beneficial effects of the present invention are as follows:
[0041] Based on this invention, developers only need to master the basic concepts of message middleware configuration related to message identifiers. This allows them to send and receive messages using different message middleware in a unified and easy-to-use manner, improving the usability of message middleware and reducing the development cost of business functions. Furthermore, this invention also enables the isolation of business functions from message middleware. Changes and upgrades to message middleware do not require adjustments to the code of business functions, reducing the operational risks and costs of business functions. Attached Figure Description
[0042] To more clearly illustrate the technical solutions in the embodiments of the present invention or the prior art, the drawings used in the embodiments will be briefly described below. Obviously, the drawings described below are only some embodiments of the present invention. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort, wherein:
[0043] Figure 1 This is a flowchart illustrating a method for using message middleware in a power dispatch automation system according to an embodiment of the present invention. Detailed Implementation
[0044] The technical solutions of the embodiments of the present invention will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only a part of the embodiments of the present invention, and not all of them. Based on the embodiments of the present invention, all other embodiments obtained by those of ordinary skill in the art without creative effort are within the scope of protection of the present invention.
[0045] Furthermore, if the embodiments of this invention involve descriptions such as "first" or "second," these descriptions are for descriptive purposes only and should not be construed as indicating or implying their relative importance or implicitly specifying the number of technical features indicated. Therefore, a feature defined with "first" or "second" may explicitly or implicitly include at least one of those features. Additionally, the technical solutions of the various embodiments can be combined with each other, but this must be based on the ability of those skilled in the art to implement them. If the combination of technical solutions is contradictory or impossible to implement, it should be considered that such a combination of technical solutions does not exist and is not within the scope of protection claimed by this invention.
[0046] Example 1
[0047] This invention provides a method for using message middleware in a power dispatch automation system, applied to a sending operation module, such as... Figure 1 As shown, it includes:
[0048] Based on the received message identifier and the preset configuration mapping relationship, find out the configuration required for the message middleware to send / receive message content;
[0049] The received message content corresponding to the message identifier, along with the configuration required for the message middleware to send / receive the message content, is sent to the corresponding message middleware. This allows the receiving operation module to receive the message content, the configuration required for the message middleware to send / receive the message content, and additional information related to the message middleware from the message receiving function module of the message middleware. The module then converts the configuration required for the message middleware to send / receive the message content into a message identifier based on a preset configuration mapping relationship.
[0050] In practical implementation, the message identifier and message content are combined as a sending data unit; the message identifier, message content, and additional information are combined as a receiving data unit. Researchers use the sending operation module to send the sending data unit to complete message sending, and use the receiving operation module to receive the receiving data unit to complete message receiving. In this invention, the sending and receiving operation modules use message middleware to essentially complete message sending and receiving, replacing the prior art's direct use of message middleware for message sending and receiving. The mapping relationship between the message identifier required in this process and the configuration required for message sending and receiving by the message middleware is maintained through configuration.
[0051] Based on the method in this embodiment of the invention, developers can grasp the basic concepts of message middleware usage and maintain the mapping relationship between message identifiers and the configuration required for message middleware to send and receive messages through configuration. Developers can upgrade or replace message middleware by modifying non-business function code.
[0052] In one specific embodiment of the present invention, the preset configuration mapping relationship is the correspondence between message identifiers and the configurations required for message middleware to send and receive messages.
[0053] In one specific embodiment of the present invention, the message identifier is a message type designed for business purposes, such as "synchronization status" or "change telemetry".
[0054] In one specific embodiment of the present invention, when the message middleware is a message bus of a power dispatch automation system, the configuration required for the message middleware to send / receive message content includes a message channel number and a message type number. The configuration required for sending / receiving message content differs for different message middlewares and can be set according to actual needs.
[0055] The implementation process of the method in the embodiments of the present invention will be described in detail below with reference to a specific implementation method.
[0056] When developing in C++, the process of using the message bus of the power dispatch automation system using the method of this invention is as follows.
[0057] Step 1: Develop the MessageBusApi and message_receive_info classes to build a general message sending and receiving model. The send method of the MessageBusApi class is for sending messages, and the receive method is for receiving messages.
[0058] The `address_name` parameter of the `send` method is the message identifier for the message being sent, while the `buff` and `length` parameters are the message content to be sent.
[0059] The result parameter of the receive method is of type message_receive_info. Its get_recv_buff and get_recv_len methods return the message content of the received message, the get_address_name method returns the message identifier of the received message, and the get_additional_str_info and get_additional_int_info methods return additional information related to the message bus.
[0060] Step 2: Develop a subclass of the MessageBusApi class, KD_MessageBus, to correspond to the message bus. The KD_MessageBus class uses the message bus interface to send and receive messages. The configuration required for the KD_MessageBus class to send and receive messages using the message bus is obtained from the XML configuration file.
[0061] Step 3: Develop the MessageBusFactory class. Its create method creates an instance of a subclass of the MessageBusApi class. The type parameter of the create method is the model of the message middleware. When the type parameter is "KD", it creates an instance of the KD_MessageBus class.
[0062] Step 4: In the non-business function code, ① create an instance of the MessageBusFactory class, bus_fac. ② Create an instance of the KD_MessageBus class by calling the create method through bus_fac, and point to this instance through the MessageBusApi class pointer variable bus_api. ③ Pass bus_api to the business function code.
[0063] Step 5: In the business function code, the `receive` method of the `MessageBusApi` class pointer variable `bus_api` is used to receive messages and store them in the `recv_msg` instance of the `message_receive_info` class. The `get_address_name` method is called through `recv_msg` to obtain the message identifier and differentiate messages, thus handling messages such as "model change" differently. The `get_recv_buff` and `get_recv_len` methods are called through `recv_msg` to retrieve the message content. The `send` method is called through `bus_api` to send messages, distinguishing them by message identifiers such as "synchronization status" and sending different messages accordingly. The necessary configuration for message middleware sending and receiving messages is configured in the XML configuration file for message identifiers such as "model change" and "synchronization status".
[0064] Repeat steps 4 and 5 to enable message sending and receiving in other message interaction scenarios using the message bus; refer to steps 2, 3, 4, and 5 to enable message sending and receiving using other message middleware; refer to steps 1, 2, 3, 4, and 5 to enable message sending and receiving in other programming languages using message middleware.
[0065] Example 2
[0066] This invention provides a method for using message middleware in a power dispatch automation system, applied to a receiving operation module, including:
[0067] Receive message content from the message receiving module of the message middleware, the configuration required for the message middleware to send / receive message content, and additional information related to the message middleware;
[0068] The configuration required for the message middleware to send / receive message content is used to obtain the message identifier based on a preset configuration mapping relationship;
[0069] The configuration required for the message middleware to send / receive message content is obtained through the following method:
[0070] The sending operation module uses the received message identifier and the preset configuration mapping relationship to find the configuration required for the message middleware to send / receive message content corresponding to the message identifier;
[0071] The sending operation module sends the received message content corresponding to the message identifier, along with the configuration required for the message middleware to send / receive message content, to the corresponding message middleware.
[0072] In practical implementation, the message identifier and message content are combined as a sending data unit; the message identifier, message content, and additional information are combined as a receiving data unit. Researchers use the sending operation module to send the sending data unit to complete message sending, and use the receiving operation module to receive the receiving data unit to complete message receiving. In this invention, the sending and receiving operation modules use message middleware to essentially complete message sending and receiving, replacing the prior art's direct use of message middleware for message sending and receiving. The mapping relationship between the message identifier required in this process and the configuration required for message sending and receiving by the message middleware is maintained through configuration.
[0073] Based on the method in this embodiment of the invention, developers can grasp the basic concepts of message middleware usage and maintain the mapping relationship between message identifiers and the configuration required for message middleware to send and receive messages through configuration. Developers can upgrade or replace message middleware by modifying non-business function code.
[0074] In one specific embodiment of the present invention, the preset configuration mapping relationship is the correspondence between message identifiers and the configurations required for message middleware to send and receive messages.
[0075] In one specific embodiment of the present invention, the message identifier is a message type designed for business purposes, such as "synchronization status" or "change telemetry".
[0076] In one specific embodiment of the present invention, when the message middleware is the message bus of a power dispatch automation system, the configuration required for the message middleware to send / receive message content includes message channel number and message type number.
[0077] The implementation process of the method in the embodiments of the present invention will be described in detail below with reference to a specific implementation method.
[0078] When developing in C++, the process of using the message bus of the power dispatch automation system using the method of this invention is as follows.
[0079] Step 1: Develop the MessageBusApi and message_receive_info classes to build a general message sending and receiving model. The send method of the MessageBusApi class is for sending messages, and the receive method is for receiving messages.
[0080] The `address_name` parameter of the `send` method is the message identifier for the message being sent, while the `buff` and `length` parameters are the message content to be sent.
[0081] The result parameter of the receive method is of type message_receive_info. Its get_recv_buff and get_recv_len methods return the message content of the received message, the get_address_name method returns the message identifier of the received message, and the get_additional_str_info and get_additional_int_info methods return additional information related to the self-developed message middleware.
[0082] Step 2: Develop a subclass of the MessageBusApi class, KD_MessageBus, to correspond to the message bus. The KD_MessageBus class uses the message bus interface to send and receive messages. The configuration required for the KD_MessageBus class to use the message bus is obtained from the XML configuration file.
[0083] Step 3: Develop the MessageBusFactory class. Its create method creates an instance of a subclass of the MessageBusApi class. The type parameter of the create method is the model of the message middleware. When the type parameter is "KD", it creates an instance of the KD_MessageBus class.
[0084] Step 4: In the non-business function code, ① create an instance of the MessageBusFactory class, bus_fac. ② Create an instance of the KD_MessageBus class by calling the create method through bus_fac, and point to this instance through the MessageBusApi class pointer variable bus_api. ③ Pass bus_api to the business function code.
[0085] Step 5: In the business function code, the `receive` method of the `MessageBusApi` class pointer variable `bus_api` is used to receive messages and store them in the `recv_msg` instance of the `message_receive_info` class. The `get_address_name` method is called through `recv_msg` to obtain the message identifier and differentiate messages, thus handling messages such as "model change" differently. The `get_recv_buff` and `get_recv_len` methods are called through `recv_msg` to retrieve the message content. The `send` method is called through `bus_api` to send messages, distinguishing them by message identifiers such as "synchronization status" and sending different messages accordingly. The necessary configurations for message middleware sending and receiving messages are configured in the XML configuration file for message identifiers such as "model change" and "synchronization status".
[0086] Repeat steps 4 and 5 to enable message sending and receiving in other message interaction scenarios using the message bus; refer to steps 2, 3, 4, and 5 to enable message sending and receiving using other message middleware; refer to steps 1, 2, 3, 4, and 5 to enable message sending and receiving in other programming languages using message middleware.
[0087] Example 3
[0088] Based on the same inventive concept as Embodiment 1, an embodiment of the present invention provides a message middleware application device in a power dispatch automation system, applied to a sending operation module, comprising:
[0089] The configuration acquisition unit required for the message middleware to send / receive message content is used to find the configuration required for the message middleware to send / receive message content based on the received message identifier and the preset configuration mapping relationship.
[0090] The transmission unit is used to send the received message content corresponding to the message identifier, along with the configuration required for the message middleware to send / receive the message content, to the corresponding message middleware. This allows the receiving operation module to receive the message content, the configuration required for the message middleware to send / receive the message content, and additional information related to the message middleware from the message receiving function module of the message middleware. The receiving module then converts the configuration required for the message middleware to send / receive the message content into a message identifier based on the preset configuration mapping relationship.
[0091] The rest are the same as in Example 1.
[0092] Example 4
[0093] Based on the same inventive concept as Embodiment 2, this embodiment of the invention provides a message middleware application device in a power dispatch automation system, characterized in that it is applied to a receiving operation module and includes:
[0094] The data acquisition unit is used to receive message content, configuration required for the message middleware to send / receive message content, and additional information related to the message middleware from the message receiving function module of the message middleware.
[0095] The transmission unit is used to convert the configuration required by the message middleware to send / receive message content into message identifiers based on the preset configuration mapping relationship;
[0096] The configuration required for the message middleware to send / receive message content is obtained through the following method:
[0097] The sending operation module uses the received message identifier and the preset configuration mapping relationship to find the configuration required for the message middleware to send / receive message content corresponding to the message identifier;
[0098] The sending operation module sends the received message content corresponding to the message identifier, along with the configuration required for the message middleware to send / receive message content, to the corresponding message middleware.
[0099] The rest are the same as in Example 2.
[0100] Example 5
[0101] Based on the same inventive concept as Embodiment 1, this embodiment of the invention provides a message middleware usage system in a power dispatch automation system, characterized in that it includes a storage medium and a processor;
[0102] The storage medium is used to store instructions;
[0103] The processor is configured to operate according to the instructions to execute the method according to any one of Embodiment 1.
[0104] Example 6
[0105] Based on the same inventive concept as Embodiment 2, this embodiment of the invention provides a message middleware usage system in a power dispatch automation system, characterized in that it includes a storage medium and a processor;
[0106] The storage medium is used to store instructions;
[0107] The processor is configured to operate according to the instructions to execute the method according to any one of Embodiment 2.
[0108] Example 7
[0109] This invention provides a message middleware usage system in a power dispatch automation system, including a sending operation module and a receiving operation module;
[0110] The sending operation module finds the configuration required for the message middleware to send / receive message content corresponding to the message identifier based on the received message identifier and the preset configuration mapping relationship; and sends the received message content corresponding to the message identifier, along with the configuration required for the message middleware to send / receive message content, to the corresponding message middleware.
[0111] The receiving operation module receives message content, configuration required for the message middleware to send / receive message content, and additional information related to the message middleware from the message receiving function module of the message middleware, and converts the configuration required for the message middleware to send / receive message content into a message identifier based on the preset configuration mapping relationship.
[0112] Those skilled in the art will understand that embodiments of this application can be provided as methods, systems, or computer program products. Therefore, this application can take the form of a completely hardware embodiment, a completely software embodiment, or an embodiment combining software and hardware aspects. Furthermore, this application can take the form of a computer program product embodied on one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) containing computer-usable program code.
[0113] This application is described with reference to flowchart illustrations and / or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of this application. It will be understood that each block of the flowchart illustrations and / or block diagrams, and combinations of blocks in the flowchart illustrations and / or block diagrams, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, special-purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, generate instructions for implementing the flowchart... Figure 1 One or more processes and / or boxes Figure 1 A device that provides the functions specified in one or more boxes.
[0114] These computer program instructions may also be stored in a computer-readable storage medium that can direct a computer or other programmable data processing device to function in a particular manner, such that the instructions stored in the computer-readable storage medium produce an article of manufacture including instruction means, which are implemented in a process Figure 1 One or more processes and / or boxes Figure 1 The function specified in one or more boxes.
[0115] These computer program instructions may also be loaded onto a computer or other programmable data processing equipment to cause a series of operational steps to be performed on the computer or other programmable equipment to produce a computer-implemented process, thereby providing instructions that execute on the computer or other programmable equipment for implementing the process. Figure 1 One or more processes and / or boxes Figure 1 The steps of the function specified in one or more boxes.
[0116] The embodiments of the present invention have been described above with reference to the accompanying drawings. However, the present invention is not limited to the specific embodiments described above. The specific embodiments described above are merely illustrative and not restrictive. Those skilled in the art can make many other forms under the guidance of the present invention without departing from the spirit and scope of the claims. All of these forms are within the protection scope of the present invention.
[0117] The foregoing has shown and described the basic principles, main features, and advantages of the present invention. Those skilled in the art should understand that the present invention is not limited to the above embodiments. The embodiments and descriptions in the specification are merely illustrative of the principles of the invention. Various changes and modifications can be made to the invention without departing from its spirit and scope, and all such changes and modifications fall within the scope of the present invention as claimed. The scope of protection of this invention is defined by the appended claims and their equivalents.
Claims
1. A method for using message middleware in a power dispatch automation system, characterized in that, Applied to the sending operation module, including: Based on the received message identifier and the preset configuration mapping relationship, find out the configuration required for the message middleware to send / receive message content; The received message content corresponding to the message identifier, along with the configuration required for the message middleware to send / receive the message content, is sent to the corresponding message middleware. This allows the receiving operation module to receive the message content, the configuration required for the message middleware to send / receive the message content, and additional information related to the message middleware from the message receiving function module of the message middleware. The module then converts the configuration required for the message middleware to send / receive the message content into a message identifier based on the preset configuration mapping relationship. The preset configuration mapping relationship is the correspondence between message identifiers and the configurations required for the message middleware to send / receive message content; The message identifier is a message type designed for business purposes; When the message middleware is the message bus of the power dispatch automation system, the configuration required for the message middleware to send / receive message content includes the message channel number and the message type number.
2. A method for using message middleware in a power dispatch automation system, characterized in that: Applied to the receiving operation module, include: Receive message content from the message receiving module of the message middleware, the configuration required for the message middleware to send / receive message content, and additional information related to the message middleware; The configuration required for the message middleware to send / receive message content is converted into message identifiers based on a preset configuration mapping relationship; The configuration required for the message middleware to send / receive message content is obtained through the following method: The sending operation module uses the received message identifier and the preset configuration mapping relationship to find the configuration required for the message middleware to send / receive message content; The sending operation module sends the received message content corresponding to the message identifier, along with the configuration required for the message middleware to send / receive message content, to the corresponding message middleware. The preset configuration mapping relationship is the correspondence between message identifiers and the configurations required for the message middleware to send / receive message content; The message identifier is a message type designed for business purposes; When the message middleware is the message bus of the power dispatch automation system, the configuration required for the message middleware to send / receive message content includes the message channel number and the message type number.
3. A message middleware application device in a power dispatch automation system, characterized in that, Applied to the sending operation module, including: The configuration acquisition unit required for the message middleware to send / receive message content converts the received message identifier into the configuration required for the message middleware to send / receive message content based on the received message identifier and the preset configuration mapping relationship. The transmission unit is used to send the received message content corresponding to the message identifier, along with the configuration required for the message middleware to send / receive the message content, to the corresponding message middleware. This allows the receiving operation module to receive the message content, the configuration required for the message middleware to send / receive the message content, and additional information related to the message middleware from the message receiving function module of the message middleware. The receiving module then converts the configuration required for the message middleware to send / receive the message content into a message identifier based on the preset configuration mapping relationship. The preset configuration mapping relationship is the correspondence between message identifiers and the configurations required for the message middleware to send / receive message content; The message identifier is a message type designed for business purposes; When the message middleware is the message bus of the power dispatch automation system, the configuration required for the message middleware to send / receive message content includes the message channel number and the message type number.
4. A message middleware application device in a power dispatch automation system, characterized in that, Applied to the receiving operation module, including: The data acquisition unit is used to receive message content, configuration required for the message middleware to send / receive message content, and additional information related to the message middleware from the message receiving function module of the message middleware. The transmission unit is used to convert the configuration required by the message middleware to send / receive message content into message identifiers based on a preset configuration mapping relationship; The configuration required for the message middleware to send / receive message content is obtained through the following method: The sending operation module uses the received message identifier and the preset configuration mapping relationship to find the configuration required for the message middleware to send / receive message content corresponding to the message identifier; The sending operation module sends the received message content corresponding to the message identifier, along with the configuration required for the message middleware to send / receive message content, to the corresponding message middleware. The preset configuration mapping relationship is the correspondence between message identifiers and the configurations required for the message middleware to send / receive message content; The message identifier is a message type designed for business purposes; When the message middleware is the message bus of the power dispatch automation system, the configuration required for the message middleware to send / receive message content includes the message channel number and the message type number.
5. A message middleware system used in a power dispatch automation system, characterized in that, Including storage media and processor; The storage medium is used to store instructions; The processor is configured to operate according to the instructions to execute the method according to claim 1.
6. A message middleware system used in a power dispatch automation system, characterized in that, Including storage media and processor; The storage medium is used to store instructions; The processor is configured to operate according to the instructions to execute the method according to claim 2.
7. A message middleware system used in a power dispatch automation system, characterized in that, It includes a sending operation module and a receiving operation module; The sending operation module finds the configuration required for the message middleware to send / receive message content corresponding to the message identifier based on the received message identifier and the preset configuration mapping relationship; and sends the received message content corresponding to the message identifier, along with the configuration required for the message middleware to send / receive message content, to the corresponding message middleware. The receiving operation module receives message content, configuration required for the message middleware to send / receive message content, and additional information related to the message middleware from the message receiving function module of the message middleware, and converts the configuration required for the message middleware to send / receive message content into a message identifier based on the preset configuration mapping relationship; The preset configuration mapping relationship is the correspondence between message identifiers and the configurations required for the message middleware to send / receive message content; The message identifier is a message type designed for business purposes; When the message middleware is the message bus of the power dispatch automation system, the configuration required for the message middleware to send / receive message content includes the message channel number and the message type number.
Citation Information
Patent Citations
Method for supporting poly-morphism function of message bus
CN102427419A