Industrial automation control method and system based on wireless remote processing

Abstract

The present application provides an industrial automation control method and system based on wireless remote processing. First, the control event stream of a predetermined wireless remote task is selected as the core event stream, and the assigned resource nodes involved in the relevant industrial automation control data are anchored based on this core event stream. Then, the required resource control actions are performed on these resource nodes to ensure the smooth execution of the task. After completing the predetermined task, the control right is passed to the control event stream of the next candidate wireless remote task, and the resource control actions of the subsequent tasks are executed in sequence. When the control event stream of a task obtains an execution confirmation instruction and completes its resource control action, the authority transfer will be stopped and the corresponding resource node will be unlocked, allowing the next task to start execution. As a result, effective task management and resource allocation are achieved in the case of multi-task competition for resources, the efficiency and stability of industrial automation task execution are improved, and the conflicts and delays caused by resource preemption are reduced.

Description

Technical Field

[0001] The present application relates to the field of industrial control technology, and in particular to an industrial automation control method and system based on wireless remote processing. Background Art

[0002] As the degree of industrial automation continues to increase, cloud computing platforms are increasingly being used to handle complex industrial control tasks. These tasks often require real-time monitoring and control of equipment and may be initiated by users in different geographical locations. However, existing resource management and task scheduling mechanisms are usually unable to effectively handle the situation where multiple wireless remote tasks request the same resource node at the same time, resulting in a disordered task execution order, resource conflicts, and increased response time.

[0003] Especially in scenarios where emergency tasks conflict with routine maintenance tasks, there is a lack of a mechanism to quickly determine priority and adjust task execution. In addition, the release of resource nodes after task execution often lacks effective supervision, which may lead to resource waste or failure to provide resources for other tasks in a timely manner.

[0004] Therefore, there is an urgent need for a new method to manage resource nodes on the cloud computing platform more intelligently and efficiently to ensure that each wireless remote task can obtain the necessary resources at the right time, thereby improving the overall service quality and the response speed of industrial automation control. Summary of the invention

[0005] In view of this, the purpose of the present application is to provide an industrial automation control method and system based on wireless remote processing.

[0006] According to a first aspect of the present application, there is provided an industrial automation control method based on wireless remote processing, the method comprising:

[0007] Taking the control event stream of the predetermined wireless remote task as the core event stream, anchoring the assigned resource node involved in the industrial automation control data in the predetermined wireless remote task according to the core event stream, and performing a resource control action for the assigned resource node in the predetermined wireless remote task on the industrial automation control data;

[0008] When the resource control action for the assigned resource node is finished, sequentially passing authority to the control event flow of the next candidate wireless remote task after the predetermined wireless remote task, and performing the resource control action for the assigned resource node in the corresponding candidate wireless remote task;

[0009] After the core event flow obtains the confirmation instruction of the scheduled wireless remote task, it verifies whether the control event flow currently obtaining the authority has completed the resource control action for the assigned resource node in the corresponding candidate wireless remote task. When the control event flow currently obtaining the authority completes the corresponding resource control action, the authority transfer is stopped and the assigned resource node is unlocked according to the core event flow. The next candidate wireless remote task of the candidate wireless remote task corresponding to the control event flow currently obtaining the authority is used as the scheduled wireless remote task, and the step of using the control event flow of the scheduled wireless remote task as the core event flow is returned until each candidate wireless remote task completes the resource control action for the assigned resource node in the corresponding candidate wireless remote task.

[0010] In a possible implementation of the first aspect, the method further includes:

[0011] Determine industrial automation control data based on control data cycles respectively associated with each resource node in the resource manager;

[0012] After obtaining the session instruction generated by the wireless remote device, generating a control event stream for the session instruction, and acquiring the target wireless remote task generated by the wireless remote device according to the generated control event stream;

[0013] When the target wireless remote task includes a resource control action for a designated resource node involved in the industrial automation control data, loading the target wireless remote task into a task background corresponding to the designated resource node;

[0014] The wireless remote task at the first position in the task background is used as the predetermined wireless remote task.

[0015] In a possible implementation manner of the first aspect, the target wireless remote task includes: a task triggering action, at least one resource control action, and an external conversation action;

[0016] The step of acquiring the target wireless remote task generated by the wireless remote device according to the generated control event flow includes:

[0017] Obtaining the task triggering action, the at least one resource control action, and the external conversation action respectively according to the generated control event flow, and processing the obtained actions;

[0018] When the target wireless remote task includes a resource control action for the assigned resource node involved in the industrial automation control data, loading the target wireless remote task into the task background corresponding to the assigned resource node includes:

[0019] When processing the currently obtained resource control action according to the generated control event flow, determining whether the currently obtained resource control action is a resource control action for the assigned resource node;

[0020] When the currently obtained resource control action is not a resource control action for the assigned resource node, processing the currently obtained resource control action according to the generated control event flow;

[0021] When the currently obtained resource control action is a resource control action for the assigned resource node, the target wireless remote task is loaded into the task background corresponding to the assigned resource node according to the generated control event flow.

[0022] In a possible implementation of the first aspect, the method further includes:

[0023] After the generated control event flow obtains the authority transfer signal sent by the control event flow of the previous candidate wireless remote task in the task background, the resource control action for the assigned resource node in the target wireless remote task is performed;

[0024] After the generated control event flow completes the corresponding resource control action, sending an authority transfer signal to the control event flow of the next candidate wireless remote task in the task background, and sending a resource control completion signal to the wireless remote device to instruct the wireless remote device to continue to generate candidate resource control actions located after the target resource control action, wherein the target resource control action is the resource control action for the assigned resource node in the target wireless remote task;

[0025] The candidate resource control actions generated by the wireless remote device are processed according to the generated control event flow.

[0026] In a possible implementation manner of the first aspect, the sequentially transferring authority to the control event flow of the next candidate wireless remote task after the predetermined wireless remote task, and performing a resource control action for the assigned resource node in the corresponding candidate wireless remote task, includes:

[0027] According to the core event flow, the authority is transferred to the first control event flow of the next first candidate wireless remote task after the predetermined wireless remote task, and a resource control action for the assigned resource node in the first candidate wireless remote task is performed;

[0028] When the resource control action of the first control event flow for the assigned resource node ends, the resource control action for the assigned resource node in the second candidate wireless remote task is performed according to the second control event flow that transfers the authority to the next second candidate wireless remote task after the first candidate wireless remote task. When the resource control action of the second control event flow for the assigned resource node ends, the authority transfer process continues to be executed until the authority transfer process is suspended.

[0029] In a possible implementation manner of the first aspect, the control event flow of the next candidate wireless remote task after the predetermined wireless remote task performs a resource control action for the assigned resource node in the corresponding candidate wireless remote task, including:

[0030] reading the current control data at the assigned resource node according to the control event flow of the next candidate wireless remote task after the scheduled wireless remote task;

[0031] A resource control action for the assigned resource node in the corresponding candidate wireless remote task is performed according to the current control data.

[0032] In a possible implementation of the first aspect, the method further includes:

[0033] After each control event flow obtains a confirmation instruction corresponding to the candidate wireless remote task, the confirmation instruction is triggered according to each control event flow;

[0034] Determine the sequence IDs of the candidate wireless remote tasks respectively associated with each control event flow based on the sequence of resource control actions performed by each control event flow on the assigned resource node;

[0035] Determine the confirmation order of the candidate wireless remote tasks respectively associated with each control event flow that triggers the confirmation instruction according to the order ID;

[0036] According to the confirmation order, confirmation processing is performed on the candidate wireless remote tasks respectively associated with each control event flow that triggers the confirmation instruction.

[0037] In a possible implementation of the first aspect, the method further includes:

[0038] After obtaining the wireless remote task restoration request, suspending the permission transfer process or suspending the unlocking of the assigned resource node, and extracting the wireless remote task to be restored represented in the wireless remote task restoration request;

[0039] Searching in the resource manager for candidate resource nodes on which resource control actions have been performed by the control event flow of the wireless remote task to be restored;

[0040] When each candidate resource node includes the assigned resource node, based on the wireless remote task list to be restored pre-acquired for the assigned resource node, performing a restoration operation on the control data at the assigned resource node;

[0041] When the restore operation is finished, resuming the permission transfer process or resuming unlocking the assigned resource node;

[0042] The step of obtaining the wireless remote task list to be restored includes:

[0043] Generating a basic wireless remote task list corresponding to the assigned resource node;

[0044] When the control event flow of the first target wireless remote task is passed the authority to perform the resource control action for the assigned resource node in the first target wireless remote task, or when the control event flow of the first target wireless remote task anchors the assigned resource node, the first target wireless remote task is loaded into the basic wireless remote task list;

[0045] When the confirmation of the first target wireless remote task is completed, or when the first target wireless remote task has been restored, removing the first target wireless remote task from the basic wireless remote task list;

[0046] The basic wireless remote task list corresponding to the assigned resource node when the wireless remote task restoration request is obtained is used as the wireless remote task list to be restored corresponding to the assigned resource node.

[0047] In a possible implementation of the first aspect, the method further includes:

[0048] When the execution of the second target wireless remote task is occupied by the third target wireless remote task, determining whether the second target wireless remote task and the third target wireless remote task both include a resource control action for the assigned resource node;

[0049] When both are included, feeding back abnormal occupancy information to the wireless remote device of the second target wireless remote task;

[0050] The industrial automation control data is resource control script data of a target industrial control module;

[0051] The method of anchoring the assigned resource node involved in the industrial automation control data in the predetermined wireless remote task according to the core event flow, and performing a resource control action on the industrial automation control data for the assigned resource node in the predetermined wireless remote task, includes:

[0052] The assigned resource node involved in the resource control script data in the predetermined wireless remote task is anchored according to the core event flow, and the resource control action for the assigned resource node in the predetermined wireless remote task is performed on the resource control script data.

[0053] According to the second aspect of the present application, a scheduling system is provided, which includes a machine-readable storage medium and a processor, wherein the machine-readable storage medium stores machine-executable instructions, and when the processor executes the machine-executable instructions, the scheduling system implements the aforementioned industrial automation control method based on wireless remote processing.

[0054] According to a third aspect of the present application, a computer-readable storage medium is provided, wherein the computer-readable storage medium stores computer-executable instructions, and when the computer-executable instructions are executed, the aforementioned industrial automation control method based on wireless remote processing is implemented.

[0055] According to any one of the above aspects, the technical effect of the present application is:

[0056] First, the control event flow of the scheduled wireless remote task is selected as the core event flow, and the assigned resource nodes involved in the relevant industrial automation control data are anchored based on this core event flow. Then, the required resource control actions are performed on these resource nodes to ensure the smooth execution of the task. After completing the scheduled task, the control right will be passed to the control event flow of the next candidate wireless remote task, and the resource control actions of the subsequent tasks will be executed in sequence. When the control event flow of a task obtains the execution confirmation instruction and completes its resource control action, the authority transfer will be stopped and the corresponding resource node will be unlocked, allowing the next task to start execution. In this way, effective task management and resource allocation are achieved in the case of multi-task competition for resources, the efficiency and stability of industrial automation task execution are improved, and the conflicts and delays caused by resource preemption are reduced. BRIEF DESCRIPTION OF THE DRAWINGS

[0057] In order to more clearly illustrate the technical solutions of the embodiments of the present application, the drawings required for use in the embodiments will be briefly introduced below. It should be understood that the following drawings only show certain embodiments of the present application and therefore should not be regarded as limiting the scope. For ordinary technicians in this field, other related drawings can be obtained based on these drawings without creative work.

[0058] Figure 1 A flow chart of an industrial automation control method based on wireless remote processing provided in an embodiment of the present application;

[0059] Figure 2A schematic diagram of the component structure of a scheduling system for implementing the above-mentioned industrial automation control method based on wireless remote processing provided in an embodiment of the present application is shown. DETAILED DESCRIPTION

[0060] To make the purpose, technical scheme and advantages of the embodiment of the present application clearer, the technical scheme in the embodiment of the present application will be clearly and completely described below according to the drawings in the embodiment of the present application. It should be understood that the drawings in the present application only serve the purpose of explanation and description, and are not used to limit the scope of protection of the present application. In addition, it should be understood that the schematic drawings are not drawn in real proportion. The flowchart used in this application shows the operations implemented according to some embodiments of the embodiment of the present application. It should be understood that the operations of the flowchart can be implemented out of order, and the steps without logical context can be reversed in order or implemented simultaneously. In addition, those skilled in the art can add at least one other operation to the flowchart under the guidance of the content of the present application, or destroy at least one operation from the flowchart.

[0061] In addition, the described embodiments are only a part of the embodiments of the present application, rather than all the embodiments. The components of the embodiments of the present application described and shown in the drawings here can be arranged and designed in various configurations. Therefore, the following detailed description of the embodiments of the present application provided in the drawings is not intended to limit the scope of the application claimed for protection, but merely represents the selected embodiments of the present application. According to the embodiments of the present application, all other embodiments obtained by those skilled in the art without making creative work correspond to the scope of protection of the present application.

[0062] Figure 1 The flowchart of the industrial automation control method and system based on wireless remote processing provided by the embodiment of the present application is shown. It should be understood that in other embodiments, the order of some steps of the industrial automation control method based on wireless remote processing of this embodiment can be shared with each other according to actual needs, or some steps can be omitted or maintained. The detailed steps of the industrial automation control method based on wireless remote processing include:

[0063] Step S110, taking the control event flow of the scheduled wireless remote task as the core event flow, anchoring the assigned resource node involved in the industrial automation control data in the scheduled wireless remote task based on the core event flow, and performing resource control actions on the industrial automation control data for the assigned resource node in the scheduled wireless remote task.

[0064] For example, user A submits a request to the scheduling system to deploy a new web application. This request creates a core event stream that contains the configuration information of the required service. The resource nodes here correspond to the virtual resources (such as virtual machines) in the cloud scheduling system. After receiving this request, the scheduling system starts to perform the following operations:

[0065] Anchor resources: The scheduling system selects appropriate virtual machine resources based on the configuration information in the core event stream and provides CPU, memory, storage and other resources for user A's Web application.

[0066] Execute control actions: The scheduling system generates the configuration files required for the Web application, starts an instance of the Web server, and deploys user A's application code to the selected virtual machine.

[0067] Step S120, when the resource control action for the assigned resource node is completed, the authority is sequentially transferred to the control event flow of the next candidate wireless remote task after the predetermined wireless remote task, and the resource control action for the assigned resource node in the corresponding candidate wireless remote task is performed.

[0068] For example, user B then submits a request to the scheduling system, hoping to deploy a database service. User B's request becomes a candidate wireless remote task. When user A's web application is successfully started and running, the scheduling system transfers the processing right to user B's task.

[0069] Anchor resources: The scheduling system now selects another set of virtual resources that are suitable for running the database service.

[0070] Execute control actions: Similarly, the scheduling system generates database configuration, starts the database instance, and performs necessary initialization operations.

[0071] Step S130, after the core event flow obtains the confirmation instruction of the scheduled wireless remote task, verifies whether the control event flow currently obtaining the authority has completed the resource control action for the assigned resource node in the corresponding candidate wireless remote task, and when the control event flow currently obtaining the authority completes the corresponding resource control action, stops the authority transfer and unlocks the assigned resource node according to the core event flow, takes the next candidate wireless remote task of the candidate wireless remote task corresponding to the control event flow currently obtaining the authority as the scheduled wireless remote task, and returns to the step of taking the control event flow of the scheduled wireless remote task as the core event flow, until each candidate wireless remote task completes the resource control action for the assigned resource node in the corresponding candidate wireless remote task.

[0072] For example, before starting to deploy the database service of user B, the scheduling system will check whether the web application of user A is running stably. After confirming that the web application of user A is running normally, the scheduling system will complete the control action.

[0073] Unlock resources: The resource nodes used by user A's web application are unlocked, indicating that no configuration changes are required, making these resources available for use by other tasks.

[0074] Processing the next task: The scheduling system now treats user C's message queue service deployment request as the next scheduled wireless remote task and repeats the above steps to allocate resources and start the service. Once the service is stable, control is transferred to the subsequent task again.

[0075] In this way, the scheduling system on the scheduling system can efficiently manage resources and ensure that various services are responded to and deployed in the order of user requests. Each task is executed only after its predecessor task is successfully completed and resources are unlocked, which ensures the optimal utilization of resources and the orderliness of service deployment.

[0076] Based on the above steps, first, the control event flow of the scheduled wireless remote task is selected as the core event flow, and the assigned resource nodes involved in the relevant industrial automation control data are anchored according to this core event flow. Then, the required resource control actions are performed on these resource nodes to ensure the smooth execution of the task. After completing the scheduled task, the control right will be passed to the control event flow of the next candidate wireless remote task, and the resource control actions of the subsequent tasks will be executed in sequence. When the control event flow of a task obtains the execution confirmation instruction and completes its resource control action, the authority transfer will be stopped and the corresponding resource node will be unlocked, allowing the next task to start execution. In this way, effective task management and resource allocation are achieved in the case of multi-task competition for resources, the efficiency and stability of industrial automation task execution are improved, and the conflicts and delays caused by resource preemption are reduced.

[0077] In a possible implementation, the method further includes:

[0078] Step A110, determining industrial automation control data based on control data cycles respectively associated with each resource node in the resource manager.

[0079] For example, in the scheduling system, the resource manager is responsible for tracking different types of virtual resources (such as virtual machines, containers, etc.) and their performance status. Each virtual resource has a control data cycle, which is determined by the system administrator or the automatic optimization policy to ensure the effective utilization of resources and the timeliness of task response. For example, for database services, the control data cycle may include parameters such as database backup frequency and transaction processing capacity; while for Web application services, the focus may be on indicators such as page loading speed and number of user connections.

[0080] Step A120, after obtaining the session instruction generated by the wireless remote device, generate a control event stream for the session instruction, and obtain the target wireless remote task generated by the wireless remote device according to the generated control event stream.

[0081] For example, user A submits a new service deployment request through the scheduling system interface, such as deploying a web application for an online store. After the request is received, a series of control event flows can be generated, which include all the steps required from initializing virtual resources, configuring network security rules to finally deploying the application.

[0082] Step A130, when the target wireless remote task includes a resource control action for a designated resource node involved in industrial automation control data, the target wireless remote task is loaded into a task background corresponding to the designated resource node.

[0083] Step A140: taking the wireless remote task at the first position in the task background as the predetermined wireless remote task.

[0084] The scheduling system can identify the task that needs to be executed, that is, the Web application deployment task of user A, and add this task to the task background of the corresponding virtual resource (such as the selected virtual machine or container). The task background is like a to-do list, ensuring that each task can be executed in a predetermined order.

[0085] If there are already other tasks in the task background, then user A's task will be placed in the queue for execution. If it is the first task, it will become a scheduled wireless remote task, which means it will be the next task to be executed. The scheduling system will monitor the status of the currently executing tasks and start user A's web application deployment task immediately once it is completed.

[0086] Through the above steps, the scheduling system can ensure that the services requested by users are deployed and managed in the correct order and priority. This process also ensures the efficient allocation and use of resources and meets the service needs of different users.

[0087] In a possible implementation manner, the target wireless remote task includes: a task triggering action, at least one resource control action, and an external conversation action.

[0088] Step A120 may include: obtaining the task triggering action, the at least one resource control action, and the external conversation action respectively according to the generated control event flow, and processing the obtained actions.

[0089] Step A130 may include:

[0090] Step A131 : when processing the currently obtained resource control action according to the generated control event flow, determining whether the currently obtained resource control action is a resource control action for the assigned resource node.

[0091] Step A132: When the currently obtained resource control action is not a resource control action for the assigned resource node, the currently obtained resource control action is processed according to the generated control event flow.

[0092] Step A133: when the currently obtained resource control action is a resource control action for the assigned resource node, the target wireless remote task is loaded into the task background corresponding to the assigned resource node according to the generated control event flow.

[0093] For example, user A submits a service deployment request through the management interface of the scheduling system. This request triggers the task trigger action and creates a series of subsequent resource control actions to implement service deployment, and also includes an external session action to communicate with user A.

[0094] Task triggering action: User A clicks the "Deploy" button on the interface to start the Web application deployment process.

[0095] Resource control actions: The cloud scheduling system starts preparing virtual machines, configuring networks, allocating storage space and other resources to meet the needs of Web application operation.

[0096] External session actions: The scheduling system updates user A with status information about the deployment progress, or requests more configuration information from user A when necessary.

[0097] The scheduling system executes tasks step by step from task triggering actions to various resource control actions according to the generated control event flow. For example:

[0098] When it is determined that the virtual machine resources are ready (one of the resource control actions), the scheduling system will send this status update to user A (external session action).

[0099] If the Web application deployment involves specific database support and the database service is already running on a specific virtual machine, the virtual machine of the database service is the assigned resource node.

[0100] Determine the target of the resource control action: When processing a resource control action, the scheduling system determines whether the action is targeted at the virtual machine resource node of the database service.

[0101] Action processing of non-assigned resource nodes: If the action is not related to the database service, such as just allocating an IP address for a Web application, the scheduling system directly executes the action.

[0102] Action processing for assigned resource nodes: If the action does involve database services, such as requiring a database upgrade or configuration change, the scheduling system will load this action into the task backend of the database service virtual machine. This allows it to be safely executed in a predetermined order without interfering with currently running services.

[0103] In this way, the scheduling system can handle multiple service deployment requests from wireless remote devices in an orderly manner. It ensures that all necessary resource control actions are properly executed and communicated with users when appropriate. At the same time, by loading specific actions to the task background of the corresponding resource node, the scheduling system is able to maintain service stability and effectively manage resource usage.

[0104] In a possible implementation, the method further includes:

[0105] Step B110, after the generated control event flow obtains the authority transfer signal sent by the control event flow of the previous candidate wireless remote task in the task background, the resource control action for the assigned resource node in the target wireless remote task is performed.

[0106] Step B120, after the generated control event flow completes the corresponding resource control action, sends an authority transfer signal to the control event flow of the next candidate wireless remote task in the task background, and sends a resource control completion signal to the wireless remote device to instruct the wireless remote device to continue generating candidate resource control actions after the target resource control action, and the target resource control action is the resource control action for the assigned resource node in the target wireless remote task.

[0107] Step B130: Process the candidate resource control actions generated by the wireless remote device according to the generated control event flow.

[0108] For example, the target wireless remote task is managed by controlling the event flow. The following is an example of a specific scenario described based on the technical content:

[0109] On the scheduling system, user A's Web application deployment task (target wireless remote task) is waiting to be executed. This task is in the task background queue. The previous candidate wireless remote tasks, such as user Z's data analysis task, have completed their resource control actions.

[0110] When user Z's task is completed, it will send a permission transfer signal to the task background, indicating that its resource control action has been completed. At this time, the control event flow of user A's Web application deployment task receives this signal and starts to perform the required resource control actions on the assigned resource nodes (such as the configured virtual machine or database server).

[0111] User A's Web application deployment task is successfully completed after performing necessary resource control actions, such as setting virtual machine parameters and deploying application code. The scheduling system will then update the task background and send a permission transfer signal to the control event flow of the next candidate wireless remote task, indicating that it is now its turn to start execution.

[0112] At the same time, a resource control completion signal may be sent to user A's wireless remote device to notify user A that their Web application has been deployed, or if necessary, other subsequent service requests may be submitted, such as requests to expand application functionality or increase database storage space.

[0113] Assume that after receiving the resource control completion signal, user A wants to add additional security performance monitoring services to his Web application. User A generates a new service request through a wireless remote device, which becomes a new candidate resource control action.

[0114] The scheduling system will receive and process this new request, and determine how to integrate this service into the current web application deployment based on the control event flow. This may involve configuring additional monitoring tools, updating security policies, or deploying additional virtual machines to support this new functionality.

[0115] Through these steps, it can be ensured that service deployment is executed in order, and the completion of each task can be correctly delivered and notified to relevant users and system components. Such a mechanism allows efficient handling of complex environments with multiple users and multiple tasks while ensuring service quality and user satisfaction.

[0116] In a possible implementation, step S120 may include:

[0117] Step S121 , performing a resource control action for the assigned resource node in the first candidate wireless remote task according to the first control event flow of the next first candidate wireless remote task after the predetermined wireless remote task by transferring authority to the first control event flow of the next first candidate wireless remote task.

[0118] Step S122, when the resource control action for the assigned resource node in the first control event flow ends, the resource control action for the assigned resource node in the second candidate wireless remote task is performed according to the second control event flow that transfers the authority to the next second candidate wireless remote task after the first candidate wireless remote task, and when the resource control action for the assigned resource node in the second control event flow ends, the authority transfer process continues to be executed until the authority transfer process is suspended.

[0119] For example, in this scheduling system and service deployment scenario, permission transfer means that the scheduling system executes different wireless remote tasks in sequence and transfers the resource control rights to the next candidate task after completion. The following are examples of specific scenarios for each technical step:

[0120] Assume that user A's web application has been successfully deployed and is running, and the virtual resource nodes it uses now need maintenance (such as patching, hardware upgrades, etc.). At this time, the scheduling system will pass the authority to the next scheduled task, that is, the first candidate wireless remote task, based on the core event flow.

[0121] The first candidate wireless remote task may be a database service update requested by user B, which requires temporarily stopping the database service, applying the update, and then restarting the service. The start of this task means that the corresponding resource node is locked in order to perform the required resource control actions.

[0122] Once the database service update of user B is completed, the scheduling system will end the task according to the first control event flow and pass the authority to the next candidate task, that is, the second candidate wireless remote task.

[0123] The second candidate wireless remote task: This may be a data analysis task of user C, which requires the expansion of storage space to accommodate more data sets. The scheduling system performs resource control actions according to the second control event flow, such as adding storage volumes or configuring new database tables.

[0124] As each task is completed, the scheduling system will continue to pass permissions to subsequent tasks until there are no more candidate tasks or the maintenance window ends. For example, user D wants to deploy a new message queue service, then after user C's data analysis task is completed, the scheduling system will pass permissions to user D's message queue deployment task.

[0125] Each subsequent task has its own control event stream, and the scheduling system manages resources based on these event streams to ensure that each service can get appropriate resource support and run smoothly.

[0126] In this way, the scheduling system can ensure that all resource control actions are processed in an orderly manner, while ensuring high availability of services and optimal utilization of resources. This also allows the system to flexibly allocate resources between tasks and respond to the needs of different users.

[0127] In a possible implementation, step S120 may further include:

[0128] Step S123: reading the current control data at the assigned resource node according to the control event flow of the next candidate wireless remote task after the scheduled wireless remote task.

[0129] Step S124 , performing a resource control action for the assigned resource node in the corresponding candidate wireless remote task according to the current control data.

[0130] For example, in the scenario of scheduling system and service deployment, each wireless remote task is managed through its control event flow. The scheduled wireless remote task is the task currently being executed, and the next candidate wireless remote task is the task waiting to be executed in the queue. The following is an example of how to correspond to these technical steps:

[0131] Assume that user B wants to update their deployed CRM system. This update operation is queued as a candidate wireless remote task after the Web application deployment task of user A. When user A's task is completed, user B's CRM system update task becomes a scheduled wireless remote task.

[0132] Before preparing to start the task of user B, the scheduling system of the cloud scheduling system will read the current control data on the virtual machine where the CRM system is located (i.e., the assigned resource node) according to the control event flow of the task, such as the current configuration parameters, operating status, resource usage, etc.

[0133] Based on the current control data read from the CRM system virtual machine, the scheduling system can determine which resource control actions are needed to complete the update request of user B. This may include steps such as downloading a new software package, stopping the service, applying the update, and restarting the service.

[0134] The scheduling system will execute these resource control actions in the order and manner defined by the control event flow. If the update involves structural changes or parameter adjustments to the database, the scheduling system will also ensure that these changes do not affect other services that depend on the same database.

[0135] These steps ensure that the scheduling system can safely and effectively deploy and update services based on the actual resource status and user requests. By carefully managing and controlling event flows and control data, the scheduling system improves its ability to respond to service changes while reducing the risk of service interruptions caused by improper resource control.

[0136] In a possible implementation, the method further includes:

[0137] Step C110 , after each control event flow obtains a confirmation instruction corresponding to the candidate wireless remote task, triggering the confirmation instruction according to each control event flow.

[0138] Step C120 : determining the sequence IDs of the candidate wireless remote tasks respectively associated with each control event flow based on the sequence of resource control actions performed by each control event flow on the assigned resource node.

[0139] Step C130 : determining the confirmation order of the candidate wireless remote tasks respectively associated with each control event flow that triggers the confirmation instruction according to the order ID.

[0140] Step C140 , performing confirmation processing on the candidate wireless remote tasks respectively associated with each control event flow that triggers the confirmation instruction according to the confirmation order.

[0141] For example, executing tasks involves complex event flow management and resource control. The following are examples of specific scenarios for each step described in the technical content:

[0142] Assume user A requests to update their web application to the latest version. When they submit this request through the scheduling system's interface or API, a control event flow is created and associated with this task. In order to start the update process, a final confirmation from user A must first be obtained. User A receives a message asking them to confirm to start the update. Once the user clicks the confirmation button, the corresponding confirmation instruction is triggered.

[0143] There are multiple task requests on the cloud scheduling system at the same time, for example, user B wants to expand storage space, and user C wants to add a new database instance. Each task has its corresponding control event flow. The scheduling system of the cloud scheduling system determines the best order to execute these tasks based on factors such as resource availability and priority, and assigns a sequence ID to each task.

[0144] Based on the previously determined order ID, the scheduling system will decide which task will be confirmed first. For example, if user B's storage expansion request is given a higher priority due to urgency, then even if user A's update request arrives first, user B's confirmation instruction may be processed first.

[0145] Exemplarily, the scheduling system confirms each task one by one according to the confirmation order. This means that the system will verify the readiness of each task, including whether all necessary information has been provided, whether resources are ready, etc. Only when the task is confirmed, the corresponding resource control action will be triggered.

[0146] For example, once user B's storage expansion request is confirmed, the related resource control actions (such as allocating additional disk space) will start immediately. Subsequently, user A's web application update task will also be confirmed after its confirmation instruction is triggered, and will start execution when the conditions are met.

[0147] Through such a process, we ensure that all tasks are properly confirmed and executed in a reasonable order, thereby maximizing resource utilization efficiency and improving user satisfaction.

[0148] In a possible implementation, the method further includes:

[0149] Step D110, after obtaining the wireless remote task restoration request, suspending the authority transfer process or suspending the unlocking of the assigned resource node, and extracting the wireless remote task to be restored represented in the wireless remote task restoration request.

[0150] Step D120: Search the resource manager for candidate resource nodes on which resource control actions have been performed by the control event flow of the wireless remote task to be restored.

[0151] Step D130: when each candidate resource node includes the assigned resource node, based on the wireless remote task list to be restored that is pre-acquired for the assigned resource node, restore the control data at the assigned resource node.

[0152] Step D140, when the restoration operation is finished, resuming the permission transfer process or resuming the unlocking of the assigned resource node.

[0153] For example, combined with the previous examples, these steps describe how to handle restore requests in service deployment and resource control. The following is an example of a specific scenario for each technical step:

[0154] Suppose user A discovers a problem after updating their web application and needs to restore the application to the previous version. User A submits a restore request. When the cloud scheduling system receives this request, the scheduling system will suspend the ongoing permission transfer process and temporarily relock the application resource node (such as a virtual machine) of user A if it has been unlocked in order to perform the restore operation.

[0155] The resource manager searches for all resource nodes that have been subjected to resource control actions by the Web application control event flow of user A, including major application servers, databases, storage, etc., to determine which resource nodes need to participate in the restoration process.

[0156] Once all resource nodes that need to be rolled back are found, the scheduling system will start the restore operation according to the list of wireless remote tasks to be restored. For example, if the update operation involves changing the database schema, the restore operation may include restoring the database schema to the state before the update.

[0157] After completing all necessary restore operations, the scheduling system will resume the permission transfer process again, allowing other waiting tasks to continue executing. At the same time, if resource nodes were locked during the restore process, they will also be unlocked, making these resources available for other tasks to use.

[0158] Through the above steps, the scheduling system can effectively handle restoration requests, ensuring that the service can be quickly restored to the expected state while ensuring the stability of the system and the availability of resources. This flexibility is critical for the operation and maintenance team because it allows them to respond to problems quickly and minimize potential service interruption time.

[0159] The step of obtaining the wireless remote task list to be restored includes:

[0160] Step D101, generating a basic wireless remote task list corresponding to the assigned resource node.

[0161] Step D102, when the control event flow of the first target wireless remote task is passed the authority to perform the resource control action on the assigned resource node in the first target wireless remote task, or when the control event flow of the first target wireless remote task anchors the assigned resource node, the first target wireless remote task is loaded into the basic wireless remote task list.

[0162] Step D103: when the confirmation of the first target wireless remote task is completed, or when the first target wireless remote task has been restored, remove the first target wireless remote task from the basic wireless remote task list.

[0163] Step D104, obtaining the basic wireless remote task list corresponding to the assigned resource node when the wireless remote task restoration request is made, as the wireless remote task list to be restored corresponding to the assigned resource node.

[0164] For example, in the scenario of scheduling system and service deployment, the wireless remote task list is used to record all the tasks that have been executed or to be executed on a specific resource node. The following is an example of the specific scenario of each step in the technical content based on this scenario:

[0165] Consider a data center that is using a scheduling system to manage its server clusters (assign resource nodes). The data center maintains a basic task list that lists all routine maintenance tasks, software update tasks, and configuration change tasks related to these servers.

[0166] User A requests to upgrade the operating system of a server, and this task becomes the "first target wireless remote task". When the scheduling system grants permission to this task and starts to perform related resource control actions, such as installing a new operating system version, or when this task needs to anchor a resource node to ensure exclusive access, the scheduling system will add this task to the basic task list.

[0167] After the OS upgrade is complete and passes the final check, the "First Target Wireless Remote Task" is confirmed complete and removed from the basic task list. If for some reason you need to undo the upgrade (i.e. perform a restore operation), this task will also be removed from the list after the restore process is complete.

[0168] For example, suppose that a compatibility issue is found after the operating system is upgraded, and user A submits a restore request. When receiving this request, the scheduling system will use the basic task list corresponding to the current server as the task list to be restored. This list records in detail all changes that may need to be rolled back, including the operating system upgrade task, to ensure that the previous state can be restored quickly and accurately.

[0169] The above steps ensure that the historical tasks of resource nodes can be effectively tracked so that when problems occur, a quick response can be made and necessary restoration operations can be performed to maintain service continuity and stability.

[0170] In a possible implementation, the method further includes:

[0171] Step E110, when the execution of the second target wireless remote task is occupied by the third target wireless remote task, determining whether the second target wireless remote task and the third target wireless remote task both include a resource control action for the assigned resource node.

[0172] Step E120, when both are included, abnormal occupancy information is fed back to the wireless remote device of the second target wireless remote task. The industrial automation control data is resource control script data of the target industrial control module.

[0173] Step S110 may include: anchoring the assigned resource node involved in the resource control script data in the scheduled wireless remote task according to the core event flow, and performing a resource control action on the assigned resource node in the scheduled wireless remote task on the resource control script data.

[0174] For example, in a data center management scenario, user A plans to perform a second-target wireless remote task (task B), such as updating the firmware of a storage system. At the same time, user B initiates a third-target wireless remote task (task C), such as urgently repairing data corruption on another storage device. Assume that both tasks need to use the same storage server (assigned resource node). You can check whether both task B and task C attempt to control resources on this server.

[0175] If both Task B and Task C involve controlling the same server, but Task C is prioritized due to its urgency, the cloud platform will send an abnormal occupancy notification to the administrator responsible for Task B. This notification may tell the administrator through the management interface or email that their firmware update task cannot be executed because the server is currently processing a more urgent task.

[0176] After the emergency repair task C is completed, it is time for task B to perform the firmware update. According to the rules of the core event flow, the storage server will be anchored to ensure that the firmware update process is not interrupted by other tasks. Then, the resource control script data in task B is executed to download, install, and apply the firmware until the update is fully completed.

[0177] Such a mechanism ensures that even in a multi-user environment, resource conflicts can be effectively managed and the order of task execution can be resolved according to established priorities, ultimately ensuring the stable operation of the data center and the reliability of services.

[0178] Figure 2 The schematic diagram shows a scheduling system 100 that can be used to implement various embodiments described in the present application.

[0179] For one embodiment, Figure 2 A scheduling system 100 is shown having at least one processor 102, a control module (chip set) 104 coupled to at least one of the (at least one) processors 102, a memory 106 coupled to the control module 104, a non-volatile memory (NVM) / storage device 108 coupled to the control module 104, at least one input / output device 110 coupled to the control module 104, and a network interface 112 coupled to the control module 104.

[0180] The processor 102 may include at least one single-core or multi-core processor, and the processor 102 may include any combination of general-purpose processors or special-purpose processors (such as graphics processors, application processors, baseband processors, etc.). In an alternative implementation, the scheduling system 100 can be used as a server device such as a gateway described in the embodiments of the present application.

[0181] Figure 2 The schematic diagram shows a scheduling system 100 that can be used to implement various embodiments described in the present application.

[0182] For one embodiment, Figure 2 A scheduling system 100 is shown having at least one processor 102, a control module (chip set) 104 coupled to at least one of the (at least one) processors 102, a memory 106 coupled to the control module 104, a non-volatile memory (NVM) / storage device 108 coupled to the control module 104, at least one input / output device 110 coupled to the control module 104, and a network interface 112 coupled to the control module 104.

[0183] The processor 102 may include at least one single-core or multi-core processor, and the processor 102 may include any combination of general-purpose processors or special-purpose processors (such as graphics processors, application processors, baseband processors, etc.). In an alternative implementation, the scheduling system 100 can be used as a server device such as a gateway described in the embodiments of the present application.

[0184] In an alternative embodiment, the scheduling system 100 may include at least one computer-readable medium (e.g., memory 106 or NVM / storage device 108) having instructions 114 and at least one processor 102 that is configured to execute the instructions 114 to implement a module to perform the actions described in the present disclosure in conjunction with the at least one computer-readable medium.

[0185] For one embodiment, the control module 104 may include any suitable interface controller to provide any suitable interface to at least one of the processor(s) 102 and / or any suitable device or component in communication with the control module 104 .

[0186] The control module 104 may include a memory controller module to provide an interface to the memory 106. The memory controller module may be a hardware module, a software module, and / or a firmware module.

[0187] The memory 106 may be used, for example, to load and store data and / or instructions 114 for the scheduling system 100. For one embodiment, the memory 106 may include any suitable volatile memory, such as a suitable DRAM. In an alternative embodiment, the memory 106 may include a double data rate type four synchronous dynamic random access memory (DDR4 SDRAM).

[0188] For one embodiment, the control module 104 may include at least one input / output controller to provide an interface to the NVM / storage device 108 and the (at least one) input / output device 110 .

[0189] For example, NVM / storage device 108 may be used to store data and / or instructions 114. NVM / storage device 108 may include any suitable non-volatile memory (e.g., flash memory) and / or may include any suitable (at least one) non-volatile storage device (e.g., at least one hard disk drive (HDD), at least one compact disk (CD) drive, and / or at least one digital versatile disk (DVD) drive).

[0190] NVM / storage device 108 may include storage resources that are physically part of the device on which scheduling system 100 is installed, or it may be accessible to the device without being part of the device. For example, NVM / storage device 108 may be accessed via (at least one) input / output device 110 over a network.

[0191] The (at least one) input / output device 110 may provide an interface for the dispatch system 100 to communicate with any other appropriate device, and the input / output device 110 may include a communication component, a phonetic component, an online monitoring component, etc. The network interface 112 may provide an interface for the dispatch system 100 to communicate according to at least one network, and the dispatch system 100 may wirelessly communicate with at least one component of a wireless network according to any standard and / or protocol of at least one wireless network standard and / or protocol, for example, access a wireless network according to a communication standard, or a combination thereof for wireless communication.

[0192] For one embodiment, at least one of the (at least one) processors 102 may be loaded together with the logic of at least one controller (e.g., a memory controller module) of the control module 104. For one embodiment, at least one of the (at least one) processors 102 may be loaded together with the logic of at least one controller of the control module 104 to form a system-level load. For one embodiment, at least one of the (at least one) processors 102 may be integrated on the same die with the logic of at least one controller of the control module 104. For one embodiment, at least one of the (at least one) processors 102 may be integrated on the same die with the logic of at least one controller of the control module 104 to form a system on chip (SoC).

[0193] In various embodiments, the dispatch system 100 may be, but is not limited to, a terminal device such as a server, a desktop computing device, or a mobile computing device (e.g., a laptop computing device, a handheld computing device, a tablet computer, a netbook, etc.). In various embodiments, the dispatch system 100 may have more or fewer components and / or different architectures. For example, in an alternative embodiment, the dispatch system 100 includes at least one camera, a keyboard, a liquid crystal display (LCD) screen (including a touch screen display), a non-volatile memory port, multiple antennas, a graphics chip, an application-specific integrated circuit (ASIC), and a speaker.

[0194] The embodiments of the present application are introduced in detail above. Specific examples are used in this article to illustrate the principles and implementation methods of the present application. The description of the above embodiments is only used to help understand the method and core idea of ​​the present application. At the same time, for general technical personnel in this field, according to the idea of ​​the present application, there will be changes in the specific implementation method and application scope. In summary, the content of this specification should not be understood as a limitation on the present application.

Claims

1. An industrial automation control method based on wireless remote processing, characterized in that: The method comprises: Taking the control event stream of the predetermined wireless remote task as the core event stream, anchoring the assigned resource node involved in the industrial automation control data in the predetermined wireless remote task according to the core event stream, and performing a resource control action for the assigned resource node in the predetermined wireless remote task on the industrial automation control data; When the resource control action for the assigned resource node is finished, sequentially passing authority to the control event flow of the next candidate wireless remote task after the predetermined wireless remote task, and performing the resource control action for the assigned resource node in the corresponding candidate wireless remote task; After the core event flow obtains the confirmation instruction of the scheduled wireless remote task, it verifies whether the control event flow currently obtaining the authority has completed the resource control action for the assigned resource node in the corresponding candidate wireless remote task. When the control event flow currently obtaining the authority completes the corresponding resource control action, the authority transfer is stopped and the assigned resource node is unlocked according to the core event flow. The next candidate wireless remote task of the candidate wireless remote task corresponding to the control event flow currently obtaining the authority is used as the scheduled wireless remote task, and the step of using the control event flow of the scheduled wireless remote task as the core event flow is returned until each candidate wireless remote task completes the resource control action for the assigned resource node in the corresponding candidate wireless remote task.

2. The industrial automation control method based on wireless remote processing according to claim 1 is characterized in that: The method further comprises: Determine industrial automation control data based on control data cycles respectively associated with each resource node in the resource manager; After obtaining the session instruction generated by the wireless remote device, generating a control event stream for the session instruction, and acquiring the target wireless remote task generated by the wireless remote device according to the generated control event stream; When the target wireless remote task includes a resource control action for a designated resource node involved in the industrial automation control data, loading the target wireless remote task into a task background corresponding to the designated resource node; The wireless remote task at the first position in the task background is used as the predetermined wireless remote task.

3. The industrial automation control method based on wireless remote processing according to claim 2 is characterized in that: The target wireless remote task includes: a task triggering action, at least one resource control action and an external conversation action; The step of acquiring the target wireless remote task generated by the wireless remote device according to the generated control event flow includes: Obtaining the task triggering action, the at least one resource control action, and the external conversation action respectively according to the generated control event flow, and processing the obtained actions; When the target wireless remote task includes a resource control action for the assigned resource node involved in the industrial automation control data, loading the target wireless remote task into the task background corresponding to the assigned resource node includes: When processing the currently obtained resource control action according to the generated control event flow, determining whether the currently obtained resource control action is a resource control action for the assigned resource node; When the currently obtained resource control action is not a resource control action for the assigned resource node, processing the currently obtained resource control action according to the generated control event flow; When the currently obtained resource control action is a resource control action for the assigned resource node, the target wireless remote task is loaded into the task background corresponding to the assigned resource node according to the generated control event flow.

4. The industrial automation control method based on wireless remote processing according to claim 3 is characterized in that: The method further comprises: After the generated control event flow obtains the authority transfer signal sent by the control event flow of the previous candidate wireless remote task in the task background, the resource control action for the assigned resource node in the target wireless remote task is performed; After the generated control event flow completes the corresponding resource control action, sending an authority transfer signal to the control event flow of the next candidate wireless remote task in the task background, and sending a resource control completion signal to the wireless remote device to instruct the wireless remote device to continue to generate candidate resource control actions located after the target resource control action, wherein the target resource control action is the resource control action for the assigned resource node in the target wireless remote task; The candidate resource control actions generated by the wireless remote device are processed according to the generated control event flow.

5. The industrial automation control method based on wireless remote processing according to claim 1, characterized in that: The sequentially transferring authority to the control event flow of the next candidate wireless remote task after the predetermined wireless remote task, and performing a resource control action for the assigned resource node in the corresponding candidate wireless remote task, comprises: According to the core event flow, the authority is transferred to the first control event flow of the next first candidate wireless remote task after the predetermined wireless remote task, and a resource control action for the assigned resource node in the first candidate wireless remote task is performed; When the resource control action of the first control event flow for the assigned resource node ends, the resource control action for the assigned resource node in the second candidate wireless remote task is performed according to the second control event flow that transfers the authority to the next second candidate wireless remote task after the first candidate wireless remote task. When the resource control action of the second control event flow for the assigned resource node ends, the authority transfer process continues to be executed until the authority transfer process is suspended.

6. The industrial automation control method based on wireless remote processing according to claim 1, characterized in that: The control event flow of the next candidate wireless remote task after the predetermined wireless remote task performs a resource control action for the assigned resource node in the corresponding candidate wireless remote task, including: reading the current control data at the assigned resource node according to the control event flow of the next candidate wireless remote task after the scheduled wireless remote task; A resource control action for the assigned resource node in the corresponding candidate wireless remote task is performed according to the current control data.

7. The industrial automation control method based on wireless remote processing according to claim 1, characterized in that: The method further comprises: After each control event flow obtains a confirmation instruction corresponding to the candidate wireless remote task, the confirmation instruction is triggered according to each control event flow; Determine the sequence IDs of the candidate wireless remote tasks respectively associated with each control event flow based on the sequence of resource control actions performed by each control event flow on the assigned resource node; Determine the confirmation order of the candidate wireless remote tasks respectively associated with each control event flow that triggers the confirmation instruction according to the order ID; According to the confirmation order, confirmation processing is performed on the candidate wireless remote tasks respectively associated with each control event flow that triggers the confirmation instruction.

8. The industrial automation control method based on wireless remote processing according to claim 1, characterized in that: The method further comprises: After obtaining the wireless remote task restoration request, suspending the permission transfer process or suspending the unlocking of the assigned resource node, and extracting the wireless remote task to be restored represented in the wireless remote task restoration request; Searching in the resource manager for candidate resource nodes on which resource control actions have been performed by the control event flow of the wireless remote task to be restored; When each candidate resource node includes the assigned resource node, based on the wireless remote task list to be restored pre-acquired for the assigned resource node, performing a restoration operation on the control data at the assigned resource node; When the restore operation is finished, resuming the permission transfer process or resuming unlocking the assigned resource node; The step of obtaining the wireless remote task list to be restored includes: Generating a basic wireless remote task list corresponding to the assigned resource node; When the control event flow of the first target wireless remote task is passed the authority to perform the resource control action for the assigned resource node in the first target wireless remote task, or when the control event flow of the first target wireless remote task anchors the assigned resource node, the first target wireless remote task is loaded into the basic wireless remote task list; When the confirmation of the first target wireless remote task is completed, or when the first target wireless remote task has been restored, removing the first target wireless remote task from the basic wireless remote task list; The basic wireless remote task list corresponding to the assigned resource node when the wireless remote task restoration request is obtained is used as the wireless remote task list to be restored corresponding to the assigned resource node.

9. The industrial automation control method based on wireless remote processing according to claim 1, characterized in that: The method further comprises: When the execution of the second target wireless remote task is occupied by the third target wireless remote task, determining whether the second target wireless remote task and the third target wireless remote task both include a resource control action for the assigned resource node; When both are included, feeding back abnormal occupancy information to the wireless remote device of the second target wireless remote task; The industrial automation control data is resource control script data of a target industrial control module; The method of anchoring the assigned resource node involved in the industrial automation control data in the predetermined wireless remote task according to the core event flow, and performing a resource control action on the industrial automation control data for the assigned resource node in the predetermined wireless remote task, includes: The assigned resource node involved in the resource control script data in the predetermined wireless remote task is anchored according to the core event flow, and the resource control action for the assigned resource node in the predetermined wireless remote task is performed on the resource control script data.

10. A scheduling system, characterized in that: It comprises a processor and a computer-readable storage medium, wherein the computer-readable storage medium stores machine-executable instructions, and when the machine-executable instructions are executed by the processor, the industrial automation control method based on wireless remote processing described in any one of claims 1 to 9 is implemented.

Images