Method, device and system for batch testing of trusted DCS controllers based on message queue

Abstract

The invention discloses a method, device and system for batch testing of trusted DCS controllers based on message queues. The method belongs to the technical field of trusted DCS controllers. According to the method, based on RabbitMQ service, a message consumer program of a RabbitMQ server is written on a trusted DCS controller, and a message producer program of the RabbitMQ server is written on a client; and running a message consumer program on each trusted DCS controller to receive and process the received message, and issuing the message of the test instruction by using the message producer program of the client. Through the method, the credible functions can be effectively set for multiple devices in batches, and meanwhile, the function that the credible management platform supports receiving of credible alarms generated by multiple credible DCS controllers at the same time can be tested, so that the credible alarms generated by multiple devices in the production environment can be prevented from being damaged when the credible alarms occur at the same time. And the trusted management platform has an unpredictable error or causes the crash of the trusted management platform.

Description

Technical Field

[0001] The invention belongs to the technical field of DCS controllers, and specifically relates to a method, a device and a system for batch testing of credible DCS controllers based on a message queue. Background Art

[0002] In the field of industrial automation, the security and reliability of distributed control systems (DCS) as core control devices are crucial to ensuring the stability and security of production processes. With the continuous increase of network security threats, the security protection requirements for DCS controllers are also increasing. Therefore, trusted DCS controllers that integrate trusted startup, static trusted verification, dynamic trusted verification, trusted whitelist, process protection, application access control and other functions have emerged. These functions together constitute a comprehensive security protection system, which effectively improves the credibility and security of DCS systems.

[0003] However, in existing technical practices, although the trusted DCS controller and its management platform have achieved efficient management and security protection for a single device, they have shown obvious limitations when faced with the management needs of multiple DCS controllers and host computers in a large-scale production environment. Specifically, the current trusted management platform usually only supports the configuration and deletion of trusted function policies for a single DCS controller, and cannot implement 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 testing the trusted alarm function. Since the existing trusted management platform lacks the ability to simultaneously receive alarm information from multiple trusted DCS controllers, it is impossible to effectively verify the platform's ability and efficiency in processing alarm information in concurrent scenarios. This not only affects the overall evaluation of the platform's performance, but also restricts the further improvement of the overall security protection level of the DCS system. Summary of the invention

[0005] The purpose of the present invention is to overcome the shortcomings of the above-mentioned prior art and provide a method, device and system for batch testing of trusted DCS controllers based on message queues to solve the problem that when processing trusted management tasks of multiple DCS controllers and host computers in the prior art, there is a lack of an efficient trusted management platform that is difficult to batch configure, delete trusted policies and simultaneously receive alarm information of multiple devices, so as to meet the actual needs in a large-scale production environment.

[0006] In order to achieve the above object, the present invention adopts the following technical solutions: A method for batch testing a trusted DCS controller based on a message queue comprises the following steps: 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 a trusted DCS controller; S2, judging whether the connection request of the client satisfies the set conditions, and if so, establishing a connection with the client; judging 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 instruction message from the client, and the switch sends the test instruction message to multiple trusted DCS controllers, and 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; 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 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 by S4 to the client.

[0007] A further improvement of the present invention is: Preferably, in S2, the setting conditions include whether the connection username is correct, whether the password is correct, whether the message queue name is correct, and whether the vhost used is correct.

[0008] Preferably, 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.

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

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

[0011] A device for batch testing a trusted DCS controller based on a message queue, comprising: 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; 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; 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 of the client, and the switch sends the test instruction message to multiple trusted DCS controllers, and 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 a test instruction message, execute the test instruction message through an execl method, assign a timestamp and the IP of the DCS trusted controller to the test result through the execl method, and generate a character 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.

[0012] Preferably, it also includes: A first connection module, used for sending a connection request to the determination module; The message producer module is used to select multiple trusted DCS controllers and send test instructions to the multiple trusted DCS controllers.

[0013] Preferably, it also includes: A second connection module, used for sending a connection request to the determination 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.

[0014] A message queue-based batch testing trusted DCS controller system, comprising: RabbitMQ server, which is the device for batch testing trusted DCS controllers based on message queues mentioned above; The client is an operating system 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.

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

[0016] Compared with the prior art, the present invention has the following beneficial effects: The present invention proposes a method for batch testing of trusted DCS controllers based on message queues, which includes writing a message consumer program of a RabbitMQ server on the trusted DCS controller and writing a message producer program of the RabbitMQ server on the client; running the message consumer program on each domestic trusted DCS controller to receive and process the received messages, and using the message producer program of the client to publish the message of the test instruction. Through this method, the working efficiency of the strategy of batch setting trusted functions for multiple devices can be effectively improved, and at the same time, the trusted management platform can be tested for supporting the trusted alarm function generated by multiple trusted DCS controllers at the same time, so as to avoid the problem that the trusted management platform has unpredictable errors or crashes when multiple devices have trusted alarms at the same time in the production environment, and the accuracy of the trusted management platform when multiple devices send messages at the same time can be significantly improved. BRIEF DESCRIPTION OF THE DRAWINGS

[0017] Figure 1 This is a flow chart of a method for batch testing of trusted DCS controllers based on message queues of the present invention; Figure 2 The RabbitMQ server structure diagram of the present invention; Figure 3 It is a client structure diagram of the present invention; Figure 4 It is a structural diagram of a trusted DCS controller of the present invention; Figure 5 This is a structural diagram of the trusted management platform of the present invention; Figure 6 This is a system diagram of the present invention for batch testing of trusted DCS controllers based on message queues. DETAILED DESCRIPTION

[0018] In the following, the terms "first", "second", "third", and "fourth" are used for descriptive purposes only and should not be understood as indicating or implying relative importance or implicitly indicating the number of the indicated technical features. Therefore, a feature defined as "first", "second", "third", and "fourth" may explicitly or implicitly include one or more of the features.

[0019] The co-production method provided in the embodiment 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 (UMPC), netbooks, personal digital assistants (PDA), etc. The embodiment of the present application does not impose any restrictions on the specific type of the client device.

[0020] It should be noted that the terms "first", "second", etc. in the specification and drawings of the present invention are used to distinguish similar objects, and are not necessarily used to describe a specific order or sequence. It should be understood that the data used in this way can be interchanged 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" and any variations thereof are intended to cover non-exclusive inclusions, for example, a process, method, system, product or device that includes a series of steps or units is not necessarily limited to those steps or units that are clearly listed, but may include other steps or units that are not clearly listed or inherent to these processes, methods, products or devices.

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

[0022] Since the DCS controller and the trusted management platform provide the above functions, there are often multiple DCS controllers and DCS host computers in the production environment. The trusted management platform only supports the configuration and deletion of trusted function policies for a certain DCS controller, and cannot batch set trusted function policies for multiple devices at the same time. At this time, the test engineer needs to use the trusted function related commands on the trusted management platform or through the serial line to configure and delete the corresponding trusted function policies for the DCS controllers one by one, thus affecting the progress of the test work. At the same time, it is also impossible to make multiple trusted DCS controllers generate alarm information at the same time, resulting in the inability to test the trusted management platform's support for receiving trusted alarms generated by multiple trusted DCS controllers at the same time.

[0023] To solve the above problems, see Figure 1The 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: S1, determine whether the connection request of the client satisfies the set condition 1, if so, establish a connection with the client; determine whether the connection request of the trusted DCS controller satisfies the set condition 2, if so, establish a connection with the trusted DCS controller; 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.

[0024] In some implementation schemes of the present invention, before determining the 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 according to routing keys and binding rules.

[0025] 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.

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

[0027] 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.

[0028] S2, receiving the test instruction from the client. The client, as a 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.

[0029] 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.

[0030] 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.

[0031] 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 concatenated into a string.

[0032] 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.

[0033] Specifically, a RabbitMQ message consumer is used to send the 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.

[0034] In some implementation schemes of the present invention, in this process, each of the DCS trusted controllers subscribes to and receives a test instruction message, executes the test instruction message through an execl method, assigns a timestamp and the IP of the DCS trusted controller to the test result through an 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.

[0035] 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.

[0036] 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.

[0037] The second aspect of the present invention discloses a device for batch testing a trusted DCS controller based on a message queue, the device comprising modules arranged at multiple ends, specifically comprising a judgment module and a forwarding module arranged at a RabbitMQ server: 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; The forwarding module receives the test instruction from the client and sends the test instruction message to multiple trusted DCS controllers, wherein 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.

[0038] Preferably, the forwarding module includes a queue module and a switch module: The queue module (Queue) is a container for storing and forwarding messages. It has the characteristics of first-in-first-out (FIFO) and can store messages persistently.

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

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

[0041] 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.

[0042] 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.

[0043] Preferably, a first display module is also provided in the client for receiving and displaying the reason for connection failure; it can also receive and display the information carried by the character string returned by the second sending module, that is, it can support receiving execution result messages sent from message consumers on each trusted DCS controller and displaying the result messages.

[0044] The first receiving module is used to receive the IP, port, virtual_host, switch, message queue name to send the message, MQ switch Type when sending the message, and message body input by the user.

[0045] In some embodiments of the present invention, a second connection module and a message consumer module are also provided in each trusted DCS controller; A second connection module, the second connection module is used to send a connection request to the judgment module at the trusted DCS controller; The message consumer module, as the receiver of the message, obtains and processes the message from the RabbitMQ queue; it 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. Specifically, the process of this module processing the message is as follows: (1) Use the execl method to execute the received message; (2) Get the output content when the execl method is executed; (3) Add timestamp and local IP address to the output of the execl method to generate a string with time and running results. This string is used to display to the user. The string contains the time, result and host IP information of the command execution, so that the user can know which device executed the result when viewing the interface.

[0046] As a preferred embodiment, it also includes: The second receiving module subscribes to the message queue and switch of the RabbtiMQ service, and receives the test instruction message sent by the test switch.

[0047] The second sending module is used to pass the above-generated string to the first display module through amqp_basic_publish, and display the information brought by the string in the client, wherein the string includes the time, result and host IP information of the execution command; it is also used to pass the trusted log and trusted function policy change information generated in the process of the message consumer module processing the test instruction to the trusted management platform.

[0048] It should be understood that amqp_basic_publish is a function used in RabbitMQ to publish messages to the message queue.

[0049] In some embodiments of the present invention, the device further includes a processing module and a display module disposed in the trusted management platform.

[0050] A processing module, used for receiving and processing trusted policy change log messages or trusted alarm messages; The display module displays the trusted policy change log message or the trusted alarm message on the UI.

[0051] A third aspect of the present invention discloses a system for batch testing a trusted DCS controller based on a message queue, the system comprising: See also Figure 2 , the RabbitMQ server includes a queue and a switch, the queue is used to store and forward messages; the switch is used to receive messages and send the messages to multiple trusted DCS controller systems.

[0052] See also Figure 3 ,The client is the operating system used to issue connection requests and test instructions to the RabbitMQ server; See also Figure 4 , multiple trusted DCS controllers are used to receive test instructions sent by switches and process test instruction messages through APIs; See also Figure 5The trusted management platform is used to receive and process trusted policy change log messages or trusted alarm messages, and display the trusted policy change log messages or trusted alarm messages on the UI. It includes a processing module and a display module.

[0053] It should be understood that the above: RabbitMQ is an open source message broker software that follows the AMQP protocol and is used to implement the Advanced Message Queuing Protocol (AMQP). It can perform asynchronous communication between different applications and provides stable and reliable message transmission services. The RabbitMQ server is equipped with a judgment module and a forwarding module, among which the forwarding module includes a queue module and a switch module.

[0054] The client can be a Windows / Linux system, used to assist users in issuing connection requests and test instructions to the RabbitMQ server; it includes a first connection module, a message producer module, a first display module and a first receiving module.

[0055] Trusted DCS controller, DCS (Distributed Control System) controller is a control device that integrates multiple technologies such as computer technology, control technology, communication technology and graphic display technology into the production process. Each trusted DCS controller of the present invention includes a second connection module, a message consumer module, a second sending module and a second receiving module.

[0056] See also Figure 6 A specific embodiment of the present invention discloses a method for batch testing a trusted DCS controller based on a message queue, comprising the following steps: 1) Run the RabbitMQ service, use the RabbitMQ management interface or command line tool, create a queue and a switch, and bind them together; 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: a) Subscribe to the message queue and switch of the RabbitMQ service; b) Receive messages from the message queue; c) Execute the received message using the execl method; d) Get the output content when the execl method is executed; e) Add timestamp and local IP address to the result returned by the execl method to generate a string with time and running result. This string is used to be displayed to the user in the end. The string contains the time, result and host IP information of the command execution, so that the user can know which device executed the result when viewing the interface.

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

[0058] 3) Run the message producer program on the Windows / Linux operating system, send a request to connect to the RabbitMQ service, and when the connection is successful, send the corresponding test instruction message. The functions of the message producer program are as follows: a) Provide 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 needs to be sent, the MQ switch type when the message is sent, and the message body; b) It can support receiving execution result messages sent by message consumers on each trusted DCS controller and display the result messages.

[0059] 4) The message consumer program on each trusted DCS controller that is successfully bound to the queue of the RabbitMQ service receives the test instruction message sent in step 3); 5) Each trusted DCS controller calls the relevant API of the trusted function or the relevant API of the operating system through the execl function to process the test instruction message.

[0060] 6) When the test instruction message processed by each trusted DCS controller is the policy of the trusted function, the trusted function will generate a log message of the policy change and send (report) the log message to the trusted management platform; 7) When the test instruction message processed by each trusted DCS controller is a test of a trusted function, the trusted function will generate a trusted alarm message for security protection, and send (report) the trusted alarm message to the trusted management platform; 8) The trusted management platform will simultaneously receive and process the above-mentioned trusted policy change log messages or trusted alarm messages, and display the processing results on the trusted management platform UI (interactive interface). At this time, the test items of concurrently generating trusted alarms for the management platform can be implemented; 9) Each trusted DCS controller sends the received command processing result message to the RabbitMQ service, and the RabbitMQ service delivers this message to the message producer program so that the user can view the processing result of the message sent in step 5).

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

Claims

1. A method for batch testing a trusted DCS controller based on a message queue, 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 a trusted DCS controller; S2, judging whether the connection request of the client satisfies the set conditions, and if so, establishing a connection with the client; judging 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 instruction message from the client, and the switch sends the test instruction message to multiple trusted DCS controllers, and 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; 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 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 by S4 to the client.

2. A 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 is characterized in that: In S3, the test instruction message includes configuring trusted boot, deleting trusted boot, 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 is 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 is 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 a trusted DCS controller; 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; 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 of the client, and the switch sends the test instruction message to multiple trusted DCS controllers, and 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 a test instruction message, execute the test instruction message through an execl method, assign a timestamp and the IP of the DCS trusted controller to the test result through the execl method, and generate a character 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 is characterized in that: Also includes: A first connection module, used for sending a connection request to the determination 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 is characterized in that: Also includes: A second connection module, used for sending a connection request to the determination 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 trusted DCS controller system based on message queue batch testing, 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 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. A 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