A method, device and system for testing a trusted DCS controller in batches based on a message queue

Abstract

The application discloses a kind of based on message queue batch test trusted DCS controller method, device and system.Belongs to trusted DCS controller technical field.This method is based on RabbitMQ service, writes a message consumer program of RabbitMQ server on trusted DCS controller, writes a message producer program of RabbitMQ server on client;Message consumer program is operated on each trusted DCS controller to receive and handle received message, and the message of test instruction is issued using the message producer program of client.By this method, it can effectively set trusted function for multiple devices in batches, and also test trusted management platform can simultaneously support receiving the trusted alarm function generated by multiple trusted DCS controllers, to avoid the problem that when multiple devices simultaneously appear trusted alarm in production environment, trusted management platform appears unpredictable error or causes trusted management platform to collapse.

Description

TECHNICAL FIELD

[0001] The application belongs to the technical field of DCS controller, and particularly relates to a method, device and system for batch testing of trusted DCS controller based on a message queue. BACKGROUND

[0002] In the field of industrial automation, as a core control device, the safety and trustworthiness of a distributed control system (DCS) are crucial for ensuring the stability and safety of the production process. With the increasing network security threats, the security protection requirements for DCS controllers are also increasing. Therefore, a trusted DCS controller integrating functions such as trusted boot, static trust verification, dynamic trust verification, trusted whitelist, process protection, and application access control has emerged. These functions together form a comprehensive security protection system, effectively improving the trustworthiness and security of the DCS system.

[0003] However, in existing technical practices, although the trusted DCS controller and its management platform achieve efficient management and security protection of a single device in terms of function, they have obvious limitations when facing the management needs of multiple DCS controllers and host computers in large-scale production environments. Specifically, the current trusted management platform usually only supports the configuration and deletion of trusted function policies for a single DCS controller, and cannot realize batch operations on multiple devices. This limitation not only increases the workload of test engineers and reduces work efficiency, but also limits the flexibility and scalability of the system in large-scale deployment scenarios.

[0004] In addition, there are also challenges in the testing of trusted alarm functions. Since the existing trusted management platform lacks the ability to simultaneously receive alarm information from multiple trusted DCS controllers, it cannot effectively verify the processing capacity and efficiency of the platform in concurrent scenarios. This not only affects the comprehensive evaluation of the platform performance, but also restricts the further improvement of the overall security protection level of the DCS system. SUMMARY

[0005] The purpose of the present application is to overcome the shortcomings of the prior art and provide a method, device and system for batch testing of trusted DCS controller based on a message queue, to solve the problem that in the prior art, when dealing with the trusted management tasks of multiple DCS controllers and host computers, there is a lack of efficient trusted management platform that can batch configure and delete trusted policies and simultaneously receive alarm information from multiple devices, to meet the actual needs in large-scale production environments.

[0006] To achieve the above purpose, the present application adopts the following technical solutions:

[0007] A method for batch testing of trusted DCS controller based on a message queue, comprising the following steps:

[0008] S1, create a queue and a switch for connection; the queue is used for storing and forwarding messages, and the switch is used for distributing messages to trusted DCS controllers;

[0009] S2, judge whether the connection request of a client meets a set condition, and if so, establish a connection with the client; judge whether the connection request of a trusted DCS controller meets a set condition, and if so, establish a connection with the trusted DCS controller; a message producer program is arranged in the client, and a message consumer program is arranged in the trusted DCS controller;

[0010] S3, the queue receives a test instruction message of a client, and the switch sends the test instruction message to multiple trusted DCS controllers; the test instruction message is in the form of a queue; after receiving the test instruction message, the trusted DCS controller processes the test instruction message through an API, and reports the result of the test instruction message to a trusted management platform;

[0011] S4, each DCS trusted controller subscribes to and receives the test instruction message, executes the test instruction message through an execl method, and assigns a timestamp and an IP of the DCS trusted controller to the test result through the execl method to generate a string;

[0012] S5, each DCS trusted controller sends the string generated in S4 to the client.

[0013] Further improvements of the application are as follows:

[0014] Preferably, in S2, the set conditions include whether a connection username is correct, whether a password is correct, whether a message queue name is correct, and whether a vhost used is correct.

[0015] Preferably, in S3, the test instruction message includes configuring a trusted start, deleting a trusted start, static trusted verification, dynamic trusted verification, a trusted white list, process protection, application program access control, deleting a protected file or program, renaming a protected file or program, modifying a protected file or program, reading a protected file or program, and executing a protected file or program.

[0016] Preferably, in S5, the client receives and displays the execution result and execution time of each trusted DCS controller.

[0017] Preferably, in S4, the result of executing the test instruction message is also displayed on the trusted management platform.

[0018] An apparatus for batch testing trusted DCS controllers based on a message queue, comprising:

[0019] A creation module is used to create a queue and a switch; the queue is used to store and forward messages, and the switch is used to distribute messages to a trusted DCS controller;

[0020] a judgment module, configured to judge whether a connection request from a trusted DCS controller satisfies a first set condition, and if so, establish a connection with the trusted DCS controller; and to judge whether a connection request from a client satisfies a second set condition, and if so, establish a connection with the client; the client is provided with a message producer program, and the trusted DCS controller is provided with a message consumer program;

[0021] The forwarding module is used to control the queue to receive the test instruction message from the client. The switch sends the test instruction message to multiple trusted DCS controllers. The test instruction message is in the form of a queue. After receiving the test instruction message, the trusted DCS controller processes the test instruction message through the API and reports the result of the test instruction message to the trusted management platform.

[0022] An execution module is used to control each DCS trusted controller to subscribe to and receive test instruction messages, execute the test instruction messages through the execl method, assign a timestamp and the IP address of the DCS trusted controller to the test results through the execl method, and generate a string;

[0023] The execution result forwarding module is used to control each DCS trusted controller to send the character string generated by the execution module to the client.

[0024] Preferably, it also includes:

[0025] A first connection module, configured to send a connection request to the judgment module;

[0026] The message producer module is used to select multiple trusted DCS controllers and send test instructions to the multiple trusted DCS controllers.

[0027] Preferably, it also includes:

[0028] A second connection module, configured to send a connection request to the judgment module;

[0029] The message consumer module is used to process the test instruction message through the API and report the result of the test instruction message to the trusted management platform.

[0030] A message queue-based batch testing system for trusted DCS controllers, comprising:

[0031] RabbitMQ server, which is the device for batch testing trusted DCS controllers based on message queues;

[0032] The client is an operating system that is used to issue connection requests and test command messages to the RabbitMQ server;

[0033] Multiple trusted DCS controllers are used to receive test instructions from switches and process test instruction messages through APIs;

[0034] The trusted management platform is used to receive and process trusted policy change log messages or trusted alarm messages, and display trusted policy change log messages or trusted alarm messages.

[0035] Preferably, the client is a Windows operating system or a Linux operating system.

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

[0037] The present invention proposes a method for batch testing trusted DCS controllers based on message queues. A RabbitMQ server message consumer program is written on the trusted DCS controller, and a RabbitMQ server message producer program is written on the client. The message consumer program is run on each domestically produced trusted DCS controller to receive and process received messages, and the client's message producer program is used to publish test instruction messages. This method can effectively improve the efficiency of policies for batch setting trusted functions for multiple devices. It can also test the trusted management platform's ability to simultaneously support receiving trusted alarms generated by multiple trusted DCS controllers, thereby avoiding unpredictable errors or crashes in the trusted management platform when trusted alarms are generated by multiple devices simultaneously in a production environment. This can significantly improve the accuracy of the trusted management platform when sending messages to multiple devices simultaneously. BRIEF DESCRIPTION OF THE DRAWINGS

[0038] Figure 1 This is a flow chart of a method for batch testing trusted DCS controllers based on a message queue according to the present invention;

[0039] Figure 2 This is a diagram of the RabbitMQ server structure of the present invention;

[0040] Figure 3 This is a client structure diagram of the present invention;

[0041] Figure 4 This is a structural diagram of a trusted DCS controller of the present invention;

[0042] Figure 5 This is a structural diagram of the trusted management platform of the present invention;

[0043] Figure 6 This is a system diagram of the present invention for batch testing trusted DCS controllers based on message queues. DETAILED DESCRIPTION

[0044] Hereinafter, the terms "first," "second," "third," and "fourth" are used for descriptive purposes only and should not be construed as indicating or implying relative importance or implicitly specifying the quantity of the technical features indicated. Thus, a feature identified as "first," "second," "third," or "fourth" may explicitly or implicitly include one or more of such features.

[0045] The co-shooting method provided in the embodiments of the present application can be applied to client devices such as mobile phones, tablet computers, wearable devices, vehicle-mounted devices, augmented reality (AR) / virtual reality (VR) devices, laptop computers, ultra-mobile personal computers (UMPCs), netbooks, and personal digital assistants (PDAs). The embodiments of the present application do not impose any restrictions on the specific types of client devices.

[0046] It should be noted that the terms "first," "second," and the like in the description and drawings of the present invention are used to distinguish similar objects and are not necessarily used to describe a specific order or precedence. It should be understood that the terms used in this manner are interchangeable where appropriate, so that the embodiments of the present invention described herein can be implemented in an order other than those illustrated or described herein. In addition, the terms "including" and "having," as well as any variations thereof, are intended to cover non-exclusive inclusions. For example, a process, method, system, product, or apparatus comprising a series of steps or units is not necessarily limited to those steps or units explicitly listed, but may include other steps or units that are not explicitly listed or that are inherent to these processes, methods, products, or apparatus.

[0047] The trusted DCS controller integrates trusted startup, static trusted verification, dynamic trusted verification, trusted whitelist, process protection, and application access control. It also supports commands for applying trusted startup, static trusted verification, dynamic trusted verification, trusted whitelist, process protection, and application access control to set and delete policies for these functions; obtain the trusted status of the DCS controller, and conduct trusted function audits. Users can quickly configure relevant trusted policies for the DCS controller through corresponding commands.

[0048] Because DCS controllers and trusted management platforms provide these multiple functions, production environments often have multiple DCS controllers and DCS host computers. The trusted management platform only supports configuring and deleting trusted function policies for a specific DCS controller, and cannot batch-configure trusted function policies for multiple devices at the same time. In this case, test engineers need to use the trusted function-related commands on the trusted management platform or through a serial line to configure and delete the corresponding trusted function policies for each DCS controller, thus affecting the progress of testing. At the same time, it is also impossible to have multiple trusted DCS controllers generate alarm information at the same time, resulting in an inability to test the trusted management platform's ability to simultaneously support receiving trusted alarms generated by multiple trusted DCS controllers.

[0049] To solve the above problems, see Figure 1 The first aspect of the present invention discloses a method for batch testing a trusted DCS controller based on a message queue, the method comprising the following steps:

[0050] S1, determine whether the client's connection request meets the set condition 1, if so, establish a connection with the client; determine whether the trusted DCS controller's connection request meets the set condition 2, if so, establish a connection with the trusted DCS controller;

[0051] The above setting conditions include whether the connection username and password are correct, whether the message queue name is correct, whether the vhost used is correct, etc.

[0052] In some implementations of the present invention, before determining a connection request, a queue and an exchange need to be established. The queue is used to store and forward messages. The exchange is used to distribute messages to different queues based on routing keys and binding rules.

[0053] In the above process, if it is determined that the client's connection request does not meet the requirements, the failure reason is output and displayed to the client for subsequent processing; if the connection request of the trusted DCS controller does not meet the set conditions, the failure reason is sent to the trusted DCS controller.

[0054] In the above process, the client can be Windows / Linux operating system.

[0055] It should be noted that the above-mentioned trusted DCS controllers include multiple trusted DCS controllers, and each trusted DCS controller needs to send a connection request to facilitate subsequent reception of test instructions.

[0056] S2, receiving the test instruction from the client. The client, as the test instruction producer, sends a test instruction message to multiple trusted DCS controllers. The test instruction message is in the form of a queue. After receiving the test instruction message, the trusted DCS controller processes the test instruction message through the API and reports the result of the test instruction message to the trusted management platform.

[0057] Specifically, the test instruction messages include: (1) configuring and deleting policies for trusted startup, static trusted verification, dynamic trusted verification, trusted whitelist, process protection, application access control, and other functions; (2) deleting, renaming, modifying, reading, and executing protected files or programs.

[0058] S3, each DCS trusted controller subscribes to and receives the test instruction message, executes the test instruction message through the execl method, assigns a timestamp and the IP of the DCS trusted controller to the test result through the execl method, and generates a character string.

[0059] Specifically, the execl method is used to execute the test instruction, and the output content when the test instruction is executed is obtained, and the execution timestamp, the output content and the IP of the DCS trusted controller are spliced ​​into a string.

[0060] S4, each DCS trusted controller sends the character string generated in S3 to the test instruction producer, so that the test instruction producer knows the result of each DCS trusted controller processing the test instruction.

[0061] Specifically, a RabbitMQ message consumer is used to send the character string generated in S3 to a RabbitMQ server, and the RabbitMQ server delivers the message to a test instruction producer so that the user can view the processing result of the test instruction of each DCS trusted controller.

[0062] In some embodiments of the present invention, in this process, each DCS trusted controller subscribes to and receives a test instruction message, executes the test instruction message through an execl method, assigns a timestamp and the IP address of the DCS trusted controller to the test result through the execl method, and generates a string. The method for processing the RabbitMQ message queue in execl is to import the message data in the RabbitMQ message queue into execl and process it in execl.

[0063] In some implementation schemes of the present invention, after receiving the test instruction message, the trusted DCS controller processes the test instruction message through an API and returns the processing result to the client for display on the client.

[0064] In some implementation schemes of the present invention, after receiving the test instruction message, the trusted DCS controller processes the test instruction message through an API, and the test result is displayed on the trusted management platform UI.

[0065] The second aspect of the present invention discloses a device for batch testing trusted DCS controllers based on a message queue. The device includes modules arranged at multiple ends, specifically including a judgment module and a forwarding module arranged at a RabbitMQ server:

[0066] A judgment module is used to judge whether the connection request of the trusted DCS controller meets the set condition 1, and if so, establish a connection with the trusted DCS controller; judge whether the connection request of the client meets the set condition 2, and if so, establish a connection with the client;

[0067] The forwarding module receives the test instruction from the client and sends the test instruction message to multiple trusted DCS controllers. The test instruction message is in the form of a queue. After receiving the test instruction message, the trusted DCS controller processes the test instruction message through the API and reports the result of the test instruction message to the trusted management platform.

[0068] Preferably, the forwarding module includes a queue module and a switch module:

[0069] The queue module (Queue) is a container for storing and forwarding messages. It has a first-in-first-out (FIFO) feature and can store messages persistently.

[0070] Exchange module: The core component that implements message routing and distributes messages to different queues based on routing keys and binding rules.

[0071] In some embodiments of the present invention, the device further includes a first connection module and a message producer module provided on the client.

[0072] The first connection module is used to send a connection request to the judgment module in the RabbitMQ server to request to establish a connection.

[0073] The message producer module is used to select multiple trusted DCS controllers to which test instruction messages need to be sent in batches, and send test instructions to the multiple trusted DCS controllers.

[0074] Preferably, the client is further provided with a first display module for receiving and displaying the reason for the connection failure; it is also capable of receiving and displaying the information carried by the character string returned by the second sending module, that is, it is capable of supporting the reception of execution result messages sent from message consumers on each trusted DCS controller and displaying this result message.

[0075] The first receiving module is used for receiving the IP, port, virtual_host, exchange, message queue name requiring to send a message, MQ exchange type when sending the message and message body of the RabbitMQ server input by a user.

[0076] In some embodiments of the application, the second connection module and the message consumer module are further arranged in each trusted DCS controller.

[0077] The second connection module is used for sending a connection request to the judgment module by the trusted DCS controller.

[0078] The message consumer module is used for obtaining and processing the message from the queue of the RabbitMQ as a receiver of the message, processing the test instruction message through an API and reporting the result of the test instruction message to the trusted management platform.

[0079] (1) the received message is executed by using an execl method;

[0080] (2) the output content when the execl method is executed is obtained;

[0081] (3) a timestamp and a local IP are added to the output content of the execl method to generate a string with time and running result. The string is used for finally showing to the user, and the string contains the time, result and host IP information of the executed command, so that the user can know which device executes the result when viewing the interface.

[0082] As preferred, the application further comprises:

[0083] The second receiving module is used for subscribing to the message queue and exchange of the RabbitMQ service and receiving the test instruction message sent by the test exchange.

[0084] The second sending module is used for transmitting the generated string to the first display module through amqp_basic_publish to display the information brought by the string in the client, and the string contains the time, result and host IP information of the executed command; and is further used for transmitting the trusted log and policy change information of the trusted function generated in the process of processing the test instruction by the message consumer module to the trusted management platform.

[0085] It should be understood that amqp_basic_publish is a function used in RabbitMQ for publishing a message to a message queue.

[0086] In some embodiments of the application, the device further comprises a processing module and a display module arranged in the trusted management platform.

[0087] a processing module configured to receive and process the trusted policy change log message or the trusted alarm message;

[0088] a display module configured to display the trusted policy change log message or the trusted alarm message on a UI.

[0089] A third aspect of the present application discloses a system for batch testing trusted DCS controllers based on a message queue, comprising:

[0090] Referring to Figure 2 a RabbitMQ server comprising a queue and an exchange, the queue being configured to store and forward messages, and the exchange being configured to receive messages and send the messages to a plurality of trusted DCS controller systems.

[0091] Referring to Figure 3 a client configured to assist a user to publish a connection request and a test instruction to the RabbitMQ server.

[0092] Referring to Figure 4 a plurality of trusted DCS controllers configured to receive the test instruction message from the exchange and process the test instruction message through an API.

[0093] Referring to Figure 5 a trusted management platform configured to receive and process the trusted policy change log message or the trusted alarm message, and display the trusted policy change log message or the trusted alarm message on a UI, comprising a processing module and a display module.

[0094] It should be understood that the above:

[0095] RabbitMQ is an open-source message broker software, which complies with the AMQP protocol, is used to implement the Advanced Message Queuing Protocol (AMQP), and can perform asynchronous communication between different application programs to provide stable and reliable message transmission services. The RabbitMQ server is provided with a judgment module and a forwarding module, wherein the forwarding module comprises a queue module and an exchange module.

[0096] The client can be a Windows / Linux system, which is configured to assist a user to publish a connection request and a test instruction to the RabbitMQ server, and comprises a first connection module, a message producer module, a first display module and a first receiving module.

[0097] A trusted DCS controller, a distributed control system (DCS), is a control device that integrates multiple technologies, including computer, control, communication, and graphic display, into the production process. Each trusted DCS controller in the present invention includes a second connection module, a message consumer module, a second sending module, and a second receiving module.

[0098] See also Figure 6 A specific embodiment of the present invention discloses a method for batch testing trusted DCS controllers based on a message queue, comprising the following steps:

[0099] 1) Run the RabbitMQ service and use the RabbitMQ management interface or command-line tool to create a queue and an exchange and bind them together.

[0100] 2) Start the message consumer program on each trusted DCS controller and successfully connect it to the RabbitMQ service. The message consumer program includes the following functions:

[0101] a) Subscribe to the message queue and switch of the RabbitMQ service;

[0102] b) Receive messages from the message queue;

[0103] c) Execute the received message using the execl method;

[0104] d) Get the output content when the execl method is executed;

[0105] e) Add a timestamp and the local IP address to the result returned by the execl method, generating a string containing the time and result. This string is ultimately displayed to the user and includes the command execution time, result, and host IP information, making it easier for users to identify which device executed the result when viewing the interface.

[0106] f) Use the amqp_basic_publish method to return the string generated in e) to the message producer program.

[0107] 3) Run the message producer program on the Windows / Linux operating system and send a request to connect to the RabbitMQ service. When the connection is successful, send the corresponding test instruction message. The message producer program includes the following functions:

[0108] a) Provides a GUI interface that allows users to enter the RabbitMQ server's IP, port, virtual_host, switch, the name of the message queue to which the message is to be sent, the MQ switch type when the message is sent, and the message body;

[0109] b) can support receiving the execution result message sent from the message consumer on each trusted DCS controller, and presenting the result message.

[0110] 4) the message consumer program on each trusted DCS controller successfully bound to the queue of the RabbitMQ service receives the test instruction message sent in step 3);

[0111] 5) each trusted DCS controller processes the test instruction message by calling the relevant API of the trusted function or the relevant API of the operating system through the execl function.

[0112] 6) when the processed test instruction message is the policy of the trusted function, the trusted function generates a log message of the policy change, and sends (reports) the log message to the trusted management platform;

[0113] 7) when the processed test instruction message is the test of the trusted function, the trusted function generates a trusted alarm information of the security protection, and sends (reports) the trusted alarm information to the trusted management platform;

[0114] 8) the trusted management platform receives and processes the trusted policy change log message or the trusted alarm message, and displays the processing result on the UI (interactive interface) of the trusted management platform. At this time, the test item of the management platform concurrent trusted alarm can be realized;

[0115] 9) each trusted DCS controller sends the received instruction processing result message to the RabbitMQ service, and the RabbitMQ service delivers the message to the message producer program for the user to view the processing result of the message sent in step 5).

[0116] The above only describes the preferred embodiments of the present application, and is not used to limit the present application. Any modification, equivalent replacement, improvement, etc. made within the spirit and principle of the present application shall be included in the protection scope of the present application.

Claims

1. A method for batch testing trusted DCS controllers based on message queues, characterized in that: The following steps are involved: S1, creating a connected queue and switch; the queue is used to store and forward messages, and the switch is used to distribute messages to the trusted DCS controller; S2, determining whether the connection request of the client satisfies the set conditions, and if so, establishing a connection with the client; determining whether the connection request of the trusted DCS controller satisfies the set conditions, and if so, establishing a connection with the trusted DCS controller; the client is provided with a message producer program, and the trusted DCS controller is provided with a message consumer program; S3: The queue receives the test command message from the client, and the switch sends the test command message in the form of a queue to multiple trusted DCS controllers. After receiving the test command message, the trusted DCS controller processes the test command message through the API and reports the result of the test command message to the trusted management platform. S4, each DCS trusted controller subscribes to and receives the test instruction message, executes the test instruction message through the execl method, assigns a timestamp and the IP address of the DCS trusted controller to the test result through the execl method, and generates a string; S5, each DCS trusted controller sends the string generated in S4 to the client.

2. The method for batch testing trusted DCS controllers based on message queues according to claim 1, characterized in that: In S2, the setting conditions include whether the connection user name is correct, whether the password is correct, whether the message queue name is correct, and whether the vhost used is correct.

3. The method for batch testing trusted DCS controllers based on message queues according to claim 1, characterized in that: In S3, the test instruction message includes configuring trusted startup, deleting trusted startup, static trusted verification, dynamic trusted verification, trusted whitelist, process protection, application access control, deleting protected files or programs, renaming protected files or programs, modifying protected files or programs, reading protected files or programs, and executing protected files or programs.

4. The method for batch testing trusted DCS controllers based on message queues according to claim 1, characterized in that: In S5, the client receives and displays the execution result and execution time of each trusted DCS controller.

5. The method for batch testing trusted DCS controllers based on message queues according to claim 1, characterized in that: In S4, the result of executing the test instruction message is also displayed on the trusted management platform.

6. A device for batch testing trusted DCS controllers based on message queues, characterized in that: include: Create modules for creating queues and switches; The queue is used to store and forward messages, and the switch is used to distribute messages to the trusted DCS controller; a judgment module, configured to judge whether a connection request from a trusted DCS controller satisfies a first set condition, and if so, establish a connection with the trusted DCS controller; and to judge whether a connection request from a client satisfies a second set condition, and if so, establish a connection with the client; the client is provided with a message producer program, and the trusted DCS controller is provided with a message consumer program; The forwarding module is used to control the queue to receive the test instruction message from the client. The switch sends the test instruction message to multiple trusted DCS controllers. The test instruction message is in the form of a queue. After receiving the test instruction message, the trusted DCS controller processes the test instruction message through the API and reports the result of the test instruction message to the trusted management platform. An execution module is used to control each DCS trusted controller to subscribe to and receive test instruction messages, execute the test instruction messages through the execl method, assign a timestamp and the IP address of the DCS trusted controller to the test results through the execl method, and generate a string; The execution result forwarding module is used to control each DCS trusted controller to send the character string generated by the execution module to the client.

7. The device for batch testing trusted DCS controllers based on message queues according to claim 6, characterized in that: Also includes: A first connection module, configured to send a connection request to the judgment module; The message producer module is used to select multiple trusted DCS controllers and send test instructions to the multiple trusted DCS controllers.

8. The device for batch testing trusted DCS controllers based on message queues according to claim 6, characterized in that: Also includes: A second connection module, configured to send a connection request to the judgment module; The message consumer module is used to process the test instruction message through the API and report the result of the test instruction message to the trusted management platform.

9. A message queue-based batch testing trusted DCS controller system, characterized in that: include: RabbitMQ server, which is the device for batch testing trusted DCS controllers based on message queues as described in claim 7; The client is an operating system that is used to issue connection requests and test command messages to the RabbitMQ server; Multiple trusted DCS controllers are used to receive test instructions from switches and process test instruction messages through APIs; The trusted management platform is used to receive and process trusted policy change log messages or trusted alarm messages, and display trusted policy change log messages or trusted alarm messages.

10. The message queue-based batch testing trusted DCS controller system according to claim 9, characterized in that: The client is a Windows operating system or a Linux operating system.

Images