Simulation task gateway scheduling method and system in industrial environment

Abstract

The invention belongs to the technical field of simulation task scheduling in an industrial environment, and discloses a simulation task gateway scheduling method in the industrial environment. The scheduling method comprises the following specific steps of S1, simulation task maintenance; S2, simulation task container deployment; S3, simulation task container authentication; S4, simulation task container rendering cache; through the simulation task gateway, cluster computing power resources can be managed in a centralized and unified mode, simulation tasks are efficiently completed, computing power resources are utilized more transparently, the computing power cost is effectively saved, the cost of physical machines needed by enterprises for adapting simulation software or systems is reduced, and the compatibility difficulty of different simulation types of tasks is solved. The gateway is highly abstracted as a Kubernetes custom CRD, different simulation tasks can be regarded as free combinations of custom resource type S attributes, and various simulation task deployments can be adapted.

Description

Technical Field

[0001] This invention belongs to the field of simulation task scheduling technology in industrial environments, specifically a simulation task gateway scheduling method and system in an industrial environment. Background Technology

[0002] The industrial simulation task gateway scheduling method is a systematic operational process for efficiently managing the entire lifecycle of industrial simulation tasks, from initiation, allocation, execution to monitoring and adjustment, using specific gateway devices and a series of strategies and algorithms. Its core objective is to achieve optimal allocation of industrial computing power cluster resources, improve the overall operational efficiency and stability of the simulation system, and reduce enterprise costs. Traditional industrial enterprises are deeply mired in a double quagmire of computing power constraints and simulation application challenges. With the acceleration of business expansion and digital transformation, computing resources are becoming increasingly scarce, and limited computing power cannot meet the ever-growing complex computing demands, hindering the pace of enterprise innovation and development. In the simulation field, the problem is even more pronounced. Different types of simulation tasks have extremely poor compatibility; each new task requires the independent development of a corresponding system or software, which undoubtedly increases development costs significantly, consuming a large amount of manpower, resources, and time, and making the development process lengthy and complex. Furthermore, the limitations and problems of physical machines become stumbling blocks to the deployment and use of simulation systems or software. Performance bottlenecks, frequent failures, and high maintenance costs of physical machines seriously affect the stable operation and efficient implementation of simulation tasks. Summary of the Invention

[0003] The purpose of this invention is to provide a simulation task gateway scheduling method and system in an industrial environment to solve the problems mentioned in the background art.

[0004] To achieve the above objectives, the present invention provides the following technical solution: a simulation task gateway scheduling method in an industrial environment, the specific steps of which are as follows: S1: Simulation Task Maintenance The simulation task message is sent through the MQTT middleware. The message content includes system code, task ID, task instruction, simulation type, cluster environment, the pre-task image for initializing the simulation container, the image of the simulation container and additional algorithm model images, the cluster to be deployed, the resources required by different images of the simulation task, the ports exposed by different images of the simulation task, and the mount address required by the simulation task image. The simulation gateway consumes MQTT task messages, parses them into JSON, and stores them in the Redis cluster using system code and task ID. If the command is to create / update, it converts the message into a K8sCRD object and sets the identifier S; if the command is to delete, it first deletes S and then deletes the task information in Redis. S2: Deploy the simulation task container: The simulation gateway is responsible for consuming MQTT simulation task messages. It first parses them into JSON objects, and then stores the task information in the Redis cluster based on the system code and task ID, including commands and status. If the command is to create or update, it is converted into a K8s custom CRD object and assigned an identifier S. If it is a delete command, S is deleted first, and then the corresponding task information in Redis is cleared. S3: Simulation Task Container Authentication: Keyclock is used to implement single sign-on authorization for multiple systems. The proxy for the simulation container is enabled by using the Envoy configuration file in the S-Charts repository. The proxy configuration requires TLS to be enabled and Keyclock to be verified. Users must log in first and then access the simulation screen through Envoy. S4: Simulation task container rendering cache: The simulation task container shader is cached in memory using Memcached, with the system code and simulation task type as the key. When the corresponding system code and simulation task type are started, the shader is quickly loaded from Memcached to complete the simulation task startup. S5: Visualization and control of the simulation task container rendering screen: When deploying tasks, the simulation gateway opens a media port for the simulation container, uses Keyclock to authenticate and authorize the STUN signaling server, develops an S-Sidecar in the same Pod as the simulation container, reads the screen through the media port, and provides visualization and control to the outside world via WebRTC after successful signaling authentication.

[0005] Preferably, in S1, the simulation task maintenance refers to the MQTT middleware adopting a publish-subscribe model to ensure that different systems can reliably publish and receive simulation task messages, and that the transmission of messages uses an encryption mechanism to ensure data security.

[0006] Preferably, in step S2, the configuration YAML files in the S-Charts repository are customized according to different simulation task types and requirements to ensure accurate deployment of various types of simulation task containers.

[0007] Preferably, the authentication of the simulation task container in S3 supports multiple authentication methods in Keyclock's single sign-on authorization, including username and password authentication and OAuth2 authentication, to meet the security authentication needs of different systems.

[0008] Preferably, the simulation task container rendering cache in S4 refers to the caching strategy of Memcached using the Least Recently Used (LRU) algorithm. When memory space is insufficient, the least recently used shader data is automatically evicted to ensure efficient use of the cache.

[0009] Preferably, the visualization and control of the simulation task container rendering screen in S5 refers to the use of secure transmission protocols, including DTLS-SRTP, in WebRTC communication to ensure the security and integrity of the rendering screen data during transmission.

[0010] Preferably, the system includes a simulation task maintenance module, a simulation task container deployment module, a simulation task container authentication module, a simulation task container rendering cache module, and a simulation task container rendering screen visualization and control module. The simulation task maintenance module is used to send and consume simulation task messages through MQTT middleware, and maintain task information in Redis cluster and Kubernetes custom CRD objects; The simulation task container deployment module utilizes Helm to develop an S-Charts repository, uses S-Controller to monitor changes in S resources and uses HelmRelease to process tasks, and uses the Flux component to complete repository update monitoring and HelmRelease deployment to achieve simulation task container deployment. The simulation task container authentication module uses Keyclock to implement single sign-on authorization for users, and enables a proxy and performs access verification through the Envoy configuration file to ensure that users can securely access the simulation container. The simulation task container rendering cache module improves the startup speed of simulation tasks by using Memcached to cache the simulation task container shaders in memory. The simulation task container rendering screen visualization and control module mainly opens the media port of the simulation container, uses Keyclock for signaling server authentication and authorization, and develops S-Sidecar to realize the external visualization and control of the rendering screen through WebRTC.

[0011] Preferably, the simulation task maintenance module further includes a message encryption submodule, which is used to encrypt and decrypt messages transmitted by the MQTT middleware to ensure data transmission security.

[0012] Preferably, the simulation task container rendering screen visualization and control module further includes a secure transmission submodule, which is used to encrypt the rendering screen data during WebRTC communication using a secure transmission protocol to prevent data leakage and tampering.

[0013] The beneficial effects of this invention are as follows: This invention enables centralized and unified management of cluster computing resources through a simulation task gateway, efficiently completing simulation tasks, making computing resource utilization more transparent, effectively saving computing costs, and reducing the cost of physical machines required for enterprises to adapt simulation software or systems. Addressing the compatibility challenges of different simulation task types, the gateway highly abstracts them as custom Kubernetes CRDs. Different simulation tasks can be viewed as free combinations of custom resource type S attributes, adapting to various simulation task deployments, avoiding independent development, and saving on enterprise developer labor costs. Leveraging simulation task container rendering caching and WebRTC visualization and control technology, under normal network conditions, enterprise developers can conduct industrial environment simulation and control work anytime and in any environment using only a browser, greatly improving work efficiency and providing enterprises with a more efficient and economical simulation solution. Attached Figure Description

[0014] Figure 1 This is a schematic diagram of the overall usage process of the simulation system gateway of the present invention; Figure 2 This is a schematic diagram of the MQTT simulation task of the present invention; Figure 3 This is a schematic diagram of the simulation task of the present invention; Figure 4 This is a schematic diagram of the user authentication and signaling server of the present invention; Figure 5 This is a schematic diagram of the overall usage process of the scheduling method of the present invention. Detailed Implementation

[0015] 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 some embodiments of the present invention, and not all embodiments. Based on the embodiments of the present invention, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of the present invention.

[0016] like Figures 1 to 4 As shown in the figure, this embodiment of the invention provides a simulation task gateway scheduling method in an industrial environment. The specific steps of the scheduling method are as follows: S1: Simulation Task Maintenance The simulation task message is sent through the MQTT middleware. The message content includes system code, task ID, task instruction, simulation type, cluster environment, the pre-task image for initializing the simulation container, the image of the simulation container and additional algorithm model images, the cluster to be deployed, the resources required by different images of the simulation task, the ports exposed by different images of the simulation task, and the mount address required by the simulation task image. The simulation gateway consumes MQTT task messages, parses them into JSON, and stores them in the Redis cluster using system code and task ID. If the command is to create / update, it converts the message into a K8sCRD object and sets the identifier S; if the command is to delete, it first deletes S and then deletes the task information in Redis. S2: Deploy the simulation task container: The simulation gateway is responsible for consuming MQTT simulation task messages. It first parses them into JSON objects, and then stores the task information in the Redis cluster based on the system code and task ID, including commands and status. If the command is to create or update, it is converted into a K8s custom CRD object and assigned an identifier S. If it is a delete command, S is deleted first, and then the corresponding task information in Redis is cleared. S3: Simulation Task Container Authentication: Keyclock is used to implement single sign-on authorization for multiple systems. The proxy for the simulation container is enabled by using the Envoy configuration file in the S-Charts repository. The proxy configuration requires TLS to be enabled and Keyclock to be verified. Users must log in first and then access the simulation screen through Envoy. S4: Simulation task container rendering cache: The simulation task container shader is cached in memory using Memcached, with the system code and simulation task type as the key. When the corresponding system code and simulation task type are started, the shader is quickly loaded from Memcached to complete the simulation task startup. S5: Visualization and control of the simulation task container rendering screen: When deploying tasks, the simulation gateway opens a media port for the simulation container, uses Keyclock to authenticate and authorize the STUN signaling server, develops an S-Sidecar in the same Pod as the simulation container, reads the screen through the media port, and provides visualization and control to the outside world via WebRTC after successful signaling authentication.

[0017] In S1, the simulation task maintenance refers to the MQTT middleware adopting a publish-subscribe model to ensure that different systems can reliably publish and receive simulation task messages, and that the transmission of messages uses an encryption mechanism to ensure data security.

[0018] In simulation task maintenance, the MQTT middleware adopts a publish-subscribe model, building an efficient communication bridge between different systems. Each system can flexibly publish and receive simulation task messages, enabling real-time information sharing and collaborative work, thus improving task processing efficiency. Simultaneously, the message transmission encryption mechanism acts like a "security lock" on the data, effectively preventing data leakage and tampering, ensuring the integrity and confidentiality of task information, and providing solid support for the stable and secure operation of simulation tasks in industrial environments.

[0019] In step S2, the configuration YAML files in the S-Charts repository are customized according to different simulation task types and requirements to ensure accurate deployment of various types of simulation task containers.

[0020] The S-Charts repository offers numerous advantages for customizing YAML configuration files to suit different simulation task types and requirements. Firstly, it allows for precise adaptation to the characteristics of various simulation tasks, ensuring that resource allocation and environment configuration during container deployment perfectly match the task, avoiding resource waste or operational anomalies caused by generic configurations. Secondly, it improves deployment accuracy and stability, reduces manual configuration errors, accelerates deployment speed, and enables different types of simulation tasks to run efficiently and reliably in containers.

[0021] Among them, the authentication of the simulation task container in S3 supports multiple authentication methods in Keyclock's single sign-on authorization, including username and password authentication and OAuth2 authentication, to meet the security authentication needs of different systems.

[0022] Keyclock's single sign-on authorization supports multiple authentication methods, including username / password and OAuth2, in simulation task container authentication, offering significant advantages. Different systems have varying security requirements and user habits, allowing for flexible adaptation to different authentication methods. Username / password authentication is simple and direct, suitable for internal systems; OAuth2 authentication facilitates the integration of third-party services, enhancing system openness. This meets diverse scenario needs, improves user experience, and strengthens system security, ensuring secure access to simulation task containers.

[0023] In S4, the simulation task container rendering cache refers to the caching strategy of Memcached using the Least Recently Used (LRU) algorithm. When memory space is insufficient, the least recently used shader data is automatically evicted to ensure efficient use of the cache.

[0024] When memory space is limited, this algorithm can automatically evict the least recently used shader data, preventing the cache from being over-occupied by infrequently used data and ensuring reasonable allocation of memory resources. This greatly improves cache utilization, enabling frequently used shader data to be read quickly, speeding up simulation task startup, improving overall operating efficiency, and providing strong support for the efficient execution of simulation tasks in industrial environments.

[0025] In S5, the visualization and control of the simulation task container rendering screen refers to the use of secure transmission protocols in WebRTC communication, including DTLS-SRTP, to ensure the security and integrity of the rendering screen data during transmission.

[0026] Employing secure transmission protocols such as DTLS-SRTP in WebRTC communication brings numerous benefits to the visualization and control of the simulation task container's rendered screen. It effectively encrypts screen data, preventing theft or tampering during transmission and ensuring data confidentiality and integrity. Simultaneously, it enhances system security, avoiding security risks caused by data leakage. This allows users to confidently remotely view and control the rendered screen, improving the reliability and stability of industrial simulation task operations.

[0027] The system includes a simulation task maintenance module, a simulation task container deployment module, a simulation task container authentication module, a simulation task container rendering cache module, and a simulation task container rendering screen visualization and control module. The simulation task maintenance module is used to send and consume simulation task messages through MQTT middleware, and maintain task information in Redis cluster and Kubernetes custom CRD objects; The simulation task container deployment module utilizes Helm to develop an S-Charts repository, uses S-Controller to monitor changes in S resources and uses HelmRelease to process tasks, and uses the Flux component to complete repository update monitoring and HelmRelease deployment to achieve simulation task container deployment. The simulation task container authentication module uses Keyclock to implement single sign-on authorization for users, and enables a proxy and performs access verification through the Envoy configuration file to ensure that users can securely access the simulation container. The simulation task container rendering cache module improves the startup speed of simulation tasks by using Memcached to cache the simulation task container shaders in memory. The simulation task container rendering screen visualization and control module mainly opens the media port of the simulation container, uses Keyclock for signaling server authentication and authorization, and develops S-Sidecar to realize the external visualization and control of the rendering screen through WebRTC.

[0028] The simulation task maintenance module leverages MQTT middleware for efficient message delivery and consumption, storing task information in a Redis cluster and Kubernetes CRD objects to ensure the reliability and flexibility of task management. The simulation task container deployment module utilizes the Helm development repository, combined with S-Controller and Flux components, to achieve automated and precise container deployment, improving deployment efficiency and accuracy.

[0029] The simulation task container authentication module implements single sign-on authorization through Keyclock, combined with Envoy proxy verification, to ensure secure user access and enhance system security. The rendering cache module utilizes Memcached to cache shaders, accelerating simulation task startup and optimizing user experience. The rendering visualization and control module opens media ports for the simulation container, authenticates the signaling server via Keyclock, and develops S-Sidecar using WebRTC for visualization and control. This enables real-time, stable display and control of the rendering screen, meeting the needs of industrial environments for efficient, secure, and visualized management and operation of simulation tasks.

[0030] The simulation task maintenance module also includes a message encryption submodule, which is used to encrypt and decrypt messages transmitted by the MQTT middleware to ensure data transmission security.

[0031] This module encrypts messages during MQTT middleware transmission, making it difficult for attackers to access the content even if data is intercepted in transit, effectively preventing the leakage of sensitive information. Simultaneously, it accurately decrypts the messages at the receiving end, ensuring data integrity and availability. This establishes a secure channel for the transmission of simulation task-related data, guaranteeing the secure and stable data interaction of the entire industrial simulation system.

[0032] The simulation task container rendering screen visualization and control module also includes a secure transmission submodule, which is used to encrypt the rendering screen data during WebRTC communication using a secure transmission protocol to prevent data leakage and tampering.

[0033] The simulation task container's rendering screen visualization and control module incorporates a secure transmission submodule, offering significant benefits. During WebRTC communication, employing a secure transmission protocol to encrypt the rendered screen data effectively builds a security defense, greatly reducing the risk of data leakage and preventing the outflow of sensitive information. Simultaneously, it prevents malicious data tampering, ensuring the authenticity and integrity of the screen data and providing users with a safe and reliable access experience.

[0034] Example of a simulation task gateway scheduling method in an industrial environment

[0035] Simulation task maintenance: The MQTT middleware distributes simulation task messages containing system code and other information in a publish-subscribe mode with encrypted transmission; the simulation gateway consumes the messages, parses the JSON and stores it in Redis, and converts it into a K8sCRD object or deletes it according to the instructions.

[0036] Deploying simulation task containers: The configuration YAML file for the S-Charts repository is customized according to the task type; the repository is developed using Helm, resources are monitored by S-Controller, and flux components are updated and deployed.

[0037] Simulation task container authentication: Keyclock supports single sign-on authorization through authentication methods such as username and password, OAuth2; it enables and verifies a proxy using the Envoy configuration file, and users access the system through Envoy after logging in.

[0038] Simulation task container rendering cache: Uses Memcached to cache shaders, storing data with system code + simulation task type as the key, and employs the LRU algorithm for fast loading at startup.

[0039] The simulation task container renders a visual and controllable screen: the media port is opened when the simulation gateway is deployed, and the Keyclock authenticates the STUN signaling server; the S-Sidecar is developed to read the screen from the Pod, and WebRTC uses the DTLS-SRTP protocol to provide services to the outside world.

[0040] Example of a simulation task gateway scheduling system based on cloud-native technology stack in an industrial environment

[0041] System composition: Includes modules for simulation task maintenance, deployment of simulation task containers, authentication of simulation task containers, rendering cache, and visualization and control of rendered screens.

[0042] Additional information for each module: The simulation task maintenance module includes a message encryption submodule for encrypting and decrypting messages; the rendering screen visualization and control module includes a secure transmission submodule for WebRTC communication and encrypted data transmission.

[0043] It should be noted that, in this document, relational terms such as "first" and "second" are used only to distinguish one entity or operation from another, and do not necessarily require or imply any such actual relationship or order between these entities or operations. Furthermore, the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such process, method, article, or apparatus.

[0044] Although embodiments of the invention have been shown and described, it will be understood by those skilled in the art that various changes, modifications, substitutions and alterations can be made to these embodiments without departing from the principles and spirit of the invention, the scope of which is defined by the appended claims and their equivalents.

Claims

1. A simulation task gateway scheduling method in an industrial environment, characterized in that: The specific steps of this scheduling method are as follows: S1: Simulation Task Maintenance The simulation task message is sent through the MQTT middleware. The message content includes system code, task ID, task instruction, simulation type, cluster environment, the pre-task image for initializing the simulation container, the image of the simulation container and additional algorithm model images, the cluster to be deployed, the resources required by different images of the simulation task, the ports exposed by different images of the simulation task, and the mount address required by the simulation task image. The simulation gateway consumes MQTT task messages, parses them into JSON, and stores them in the Redis cluster using system code and task ID. If the command is to create / update, it converts the message into a K8sCRD object and sets the identifier S; if the command is to delete, it first deletes S and then deletes the task information in Redis. S2: Deploy the simulation task container: The simulation gateway is responsible for consuming MQTT simulation task messages, first parsing them into JSON objects, and then storing the task information in the Redis cluster based on the system code and task ID, including instructions and status. If the command is to create or update, it is converted into a custom Kubernetes CRD object and assigned the identifier S; if it is to delete, S is deleted first, and then the corresponding task information in Redis is cleared. S3: Simulation Task Container Authentication: Keyclock is used to implement single sign-on authorization for multiple systems. The proxy for the simulation container is enabled by using the Envoy configuration file in the S-Charts repository. The proxy configuration requires TLS to be enabled and Keyclock to be verified. Users must log in first and then access the simulation screen through Envoy. S4: Simulation task container rendering cache: The simulation task container shader is cached in memory using Memcached, with the system code and simulation task type as the key. When the corresponding system code and simulation task type are started, the shader is quickly loaded from Memcached to complete the simulation task startup. S5: Visualization and control of the simulation task container rendering screen: When deploying tasks, the simulation gateway opens a media port for the simulation container, uses Keyclock to authenticate and authorize the STUN signaling server, develops an S-Sidecar in the same Pod as the simulation container, reads the screen through the media port, and provides visualization and control to the outside world via WebRTC after successful signaling authentication.

2. The simulation task gateway scheduling method in an industrial environment according to claim 1, characterized in that: The simulation task maintenance mentioned in S1 refers to the MQTT middleware adopting a publish-subscribe model to ensure that different systems can reliably publish and receive simulation task messages, and that the transmission of messages uses an encryption mechanism to ensure data security.

3. The simulation task gateway scheduling method in an industrial environment according to claim 1, characterized in that: In step S2, the configuration YAML files in the S-Charts repository are customized according to different simulation task types and requirements to ensure accurate deployment of various types of simulation task containers.

4. The simulation task gateway scheduling method in an industrial environment according to claim 1, characterized in that: The S3 simulation task container authentication supports multiple authentication methods in Keyclock's single sign-on authorization, including username and password authentication and OAuth2 authentication, to meet the security authentication needs of different systems.

5. The simulation task gateway scheduling method in an industrial environment according to claim 1, characterized in that: The simulation task container rendering cache in S4 refers to the caching strategy of Memcached, which adopts the Least Recently Used (LRU) algorithm. When memory space is insufficient, the least recently used shader data is automatically evicted to ensure efficient use of the cache.

6. The simulation task gateway scheduling method in an industrial environment according to claim 1, characterized in that: The visualization and control of the simulation task container rendering screen in S5 refers to the use of secure transmission protocols in WebRTC communication, including DTLS-SRTP, to ensure the security and integrity of the rendering screen data during transmission.

7. A simulation task gateway scheduling system based on cloud-native technology stack in an industrial environment, characterized in that: The system includes a simulation task maintenance module, a simulation task container deployment module, a simulation task container authentication module, a simulation task container rendering cache module, and a simulation task container rendering screen visualization and control module. The simulation task maintenance module is used to send and consume simulation task messages through MQTT middleware, and maintain task information in Redis cluster and Kubernetes custom CRD objects; The simulation task container deployment module utilizes Helm to develop an S-Charts repository, uses S-Controller to monitor changes in S resources and uses HelmRelease to process tasks, and uses the Flux component to complete repository update monitoring and HelmRelease deployment to achieve simulation task container deployment. The simulation task container authentication module uses Keyclock to implement single sign-on authorization for users, and enables a proxy and performs access verification through the Envoy configuration file to ensure that users can securely access the simulation container. The simulation task container rendering cache module improves the startup speed of simulation tasks by using Memcached to cache the simulation task container shaders in memory. The simulation task container rendering screen visualization and control module mainly opens the media port of the simulation container, uses Keyclock for signaling server authentication and authorization, and develops S-Sidecar to realize the external visualization and control of the rendering screen through WebRTC.

8. A simulation task gateway scheduling system based on cloud-native technology stack in an industrial environment according to claim 7, characterized in that: The simulation task maintenance module also includes a message encryption submodule, which is used to encrypt and decrypt messages transmitted by the MQTT middleware to ensure data transmission security.

9. A simulation task gateway scheduling system based on cloud-native technology stack in an industrial environment according to claim 7, characterized in that: The simulation task container rendering screen visualization and control module also includes a secure transmission submodule, which is used to encrypt the rendering screen data during WebRTC communication using a secure transmission protocol to prevent data leakage and tampering.

Images