Automatic control conflict processing method based on new energy industry

Abstract

The invention discloses an automatic control conflict processing method based on a new energy industry, and relates to the technical field of automatic control, and the method comprises the steps: abstracting a power equipment control operation into an independent control process instance, constructing a control process state machine, and achieving the life cycle management of the process instance; configuring a unique equipment lock for each power equipment, defining a control flow priority judgment strategy, arbitrating a plurality of control flow instances applying for the same equipment lock, and ensuring that only one control flow instance can obtain the equipment lock at the same moment to enter an execution stage; based on the execution stage, when it is detected that the control process instance cannot continue due to the fact that the equipment lock is occupied in equipment lock management, the control process instance is set to be in a conflict state according to a priority strategy, a suspension, interruption or rollback strategy is automatically adopted, and after conflict conditions are relieved, the suspended control process instance is automatically tried to be recovered. According to the invention, intelligentization, controllability and security of the operation process of the power equipment are realized.

Description

Technical Field

[0001] This invention relates to the field of automatic control technology, specifically to a method for handling automatic control conflicts in the new energy industry. Background Technology

[0002] With the rapid development of the new energy industry, new energy power plants and power grids have gradually shifted from manual operation to automation and intelligence. Power plant monitoring systems have also begun to widely adopt automated operation functions such as automatic control in operation and management. Operation commands have also begun to come from multiple control sources, including: automatic control logic, protection actions, dispatching commands, and manual operation commands, etc. However, in this multi-source collaborative environment, the same equipment is often operated simultaneously by processes from multiple different sources, leading to a series of problems such as conflicts between different source processes, inconsistent operation command states, lack of priority processing mechanisms for multiple operation commands, and difficulty in equipment state rollback and recovery. These problems seriously affect the stable operation of the power system. Therefore, realizing an automatic control and conflict handling method for power equipment based on process state machine and control lock mechanism has become a key issue that needs to be considered. Summary of the Invention

[0003] To address the aforementioned technical problems, this technical solution provides a method for handling automatic control conflicts in the new energy industry, thus resolving the aforementioned issues.

[0004] To achieve the above objectives, the technical solution adopted by the present invention is as follows: Methods for handling automatic control conflicts in the new energy industry include: S1. Abstract the control operations of power equipment into independent control process instances, construct a control process state machine, and realize lifecycle management of process instances; S2. Configure a unique device lock for each power device, define a control flow priority determination strategy, arbitrate multiple control flow instances that apply for the same device lock, and ensure that only one control flow instance can obtain the device lock and enter the execution phase at the same time. S3. Based on the execution phase, when it is detected in the device lock management that a control flow instance cannot continue due to the device lock being occupied, it is set to a conflict state according to the priority policy, and a suspension, interruption or rollback strategy is automatically adopted. After the conflict condition is resolved, the suspended control flow instance is automatically attempted to be restored.

[0005] Preferably, step S1 specifically includes: Based on the SCADA monitoring and data acquisition system, when the system detects that the target power equipment control operation is triggered, an independent control process instance is immediately created for the control operation, and the target equipment, control command and origin information of the control process instance are accurately recorded. After creating an independent control flow instance, the initial state is automatically set to requested. This initial state indicates that the control flow has been formally initiated and is waiting to request the control lock of the target device. Based on the control flow being in the requested state, the system checks whether the device lock of the target device is free. If the device lock is free, the process instance successfully acquires the lock and the state transitions to locked. This state indicates that the control flow has obtained exclusive operation qualification on the target device and is ready to enter the execution phase. Once the control flow is locked, the control flow instance begins to actually issue control commands to the target device, including start, speed adjustment, and stop. Once the commands are issued, the control flow status is immediately updated to "in execution".

[0006] Preferably, step S1 further includes: Once the control flow is in the execution state, the system confirms that the device has correctly received and executed the instruction, and that the device has reached the state required by the instruction. The control flow state then changes to the holding state, which indicates that the control operation has taken effect and the target device is in a stable state isolated by the control flow. If the control process is in a held state, it will automatically end when it reaches its preset endpoint. The control process instance will terminate normally, and the control process state will change to released, releasing the device lock it holds, making the target device available for control by other processes.

[0007] Preferably, step S1 further includes: Based on the SCADA monitoring and data acquisition system, if the control process fails to execute, is interrupted by a higher priority process, or is actively canceled by the operator, the process status will be forcibly changed to rolled back. Once in this state, the system will immediately start the rollback procedure to try to restore the target device status to the initial state before the execution of the control process and release the device lock. Integrate the six control flow states: requested, locked, executing, holding, released, and rolled back, and establish a control flow state machine; For each independent control process instance, an independent audit log is created, recording each state change in real time and in detail to the audit log, providing operators with log records to trace the entire lifecycle of the control process.

[0008] Preferably, step S2 specifically includes: Based on the control flow being in the requested state, a device lock application for the target device is initiated to the system's lock manager. The lock manager checks the current state of the device lock to determine whether it is idle or occupied. If the device lock is determined to be in an idle state, the lock manager immediately assigns the device lock to the currently requesting control flow, records the binding relationship between the lock and the flow instance, and changes the state of the flow instance from requested to locked.

[0009] Preferably, step S2 further includes: If the device lock is determined to be in an occupied state, the lock manager immediately initiates the priority determination strategy for arbitration; The priority determination strategy includes: the safety protection process is the highest priority, used for emergency shutdown and protection actions, and cannot be interrupted; the manual operation process is the medium priority, responding to real-time operator instructions; and the automatic control process is the lowest priority, triggered by preset conditions. If the current control flow has a higher priority than the current lock holder, the lock manager immediately sends an interrupt signal to the lower priority flow that currently holds the lock, forcing it to enter the interrupt handling flow. If the priority of the current control flow is lower than or equal to that of the current lock holder, the lock manager will put the application process into a conflict state, suspend it in the waiting queue of the target device, or directly reject the application and return a rejection feedback to the initiator.

[0010] Preferably, step S2 further includes: Based on the control flow being in a released or rolled-back state, the system actively releases the device lock it holds. After receiving the release signal, the lock manager releases the binding relationship between the lock and the control flow and immediately checks the waiting queue of the target device. If the waiting queue is not empty, the lock manager selects the control flow instance with the highest priority in the queue, assigns it a device lock, and changes its state from suspended to locked. If the waiting queue is empty, the device lock remains idle and waits for the next request, ensuring that only one control flow instance can acquire the device lock and enter the execution phase at any given time.

[0011] Preferably, step S3 specifically includes: Based on the fact that the control flow is in a locked state, the SCADA monitoring and data acquisition system is used to continuously detect the lock status and waiting queue of all devices. When a high-priority control flow is detected requesting a device lock that is being held by a low-priority control flow, the lock manager immediately sets the low-priority control flow to a conflict state. Based on setting low-priority control flows to a conflict state, the conflict handling strategy of the control flow is adaptively adjusted.

[0012] Preferably, step S3 further includes: For control flows that cannot immediately acquire a lock due to low priority, the system suspends them and places them in the target device waiting queue. If a high-priority control flow needs to interrupt a low-priority control flow, the lock manager immediately sends an interrupt signal to the low-priority control flow. The interrupted control flow immediately stops any current execution action, and the system forcibly switches it to a rolled-back state, starts the rollback procedure to restore the target device state, and releases the device lock. If two control flows of the same priority compete for the same device lock, they will be executed according to the order in which they are issued, and the control flow that arrives later will be suspended and placed in a waiting queue.

[0013] Preferably, step S3 further includes: Based on control flow conflict resolution, the system automatically resumes suspended control flows. If the device lock is successfully restored, the system restores it from the suspended state to the locked state and continues to execute the next control flow. If the device lock restoration fails, the control flow directly enters the rolled-back state to prevent repeated execution.

[0014] Compared with the prior art, the beneficial effects of the present invention are as follows: This invention proposes an automatic control conflict resolution scheme for the new energy industry. By combining process state machines, control lock mechanisms, priority arbitration, and automatic rollback strategies, it effectively solves the problems of conflicts caused by processes from different sources, inconsistent equipment states, and frequent manual intervention in existing SCADA monitoring and data acquisition systems. This achieves intelligent, controllable, and safe operation of power equipment processes, and has strong engineering application and promotion value. Attached Figure Description

[0015] Figure 1 This is a flowchart of a method for handling automatic control conflicts in the new energy industry. Detailed Implementation

[0016] The following description is intended to disclose the invention and enable those skilled in the art to implement it. The preferred embodiments described below are merely examples, and other obvious variations will occur to those skilled in the art.

[0017] Reference Figure 1 As shown, the method for handling automatic control conflicts in the new energy industry includes: S1. Abstract the power equipment control operation into an independent control process instance, construct a control process state machine, and realize lifecycle management of the process instance; the state machine includes six states: requested, locked, executing, holding, released, and rolled back. Step S1 specifically includes: Based on the SCADA monitoring and data acquisition system, when the system detects that the target power equipment control operation is triggered, an independent control process instance is immediately created for the control operation, and the target equipment, control command and origin information of the control process instance are accurately recorded. After creating an independent control flow instance, the initial state is automatically set to requested. This initial state indicates that the control flow has been formally initiated and is waiting to request the control lock of the target device. Based on the control flow being in the requested state, the system checks whether the device lock of the target device is free. If the device lock is free, the process instance successfully acquires the lock and the state transitions to locked. This state indicates that the control flow has obtained exclusive operation qualification on the target device and is ready to enter the execution phase. Once the control flow is locked, the control flow instance begins to actually issue control commands to the target device, including start, speed adjustment, and stop. Once the commands are issued, the control flow status is immediately updated to "in execution".

[0018] Step S1 also includes: Once the control flow is in the execution state, the system confirms that the device has correctly received and executed the instruction, and that the device has reached the state required by the instruction. The control flow state then changes to the holding state, which indicates that the control operation has taken effect and the target device is in a stable state isolated by the control flow. If the control process is in a held state, it will automatically end when it reaches its preset endpoint. The control process instance will terminate normally, and the control process state will change to released, releasing the device lock it holds, making the target device available for control by other processes.

[0019] Step S1 also includes: Based on the SCADA monitoring and data acquisition system, if the control process fails to execute, is interrupted by a higher priority process, or is actively canceled by the operator, the process status will be forcibly changed to rolled back. Once in this state, the system will immediately start the rollback procedure to try to restore the target device status to the initial state before the execution of the control process and release the device lock. Integrate the six control flow states: requested, locked, executing, holding, released, and rolled back, and establish a control flow state machine; For each independent control process instance, an independent audit log is created, recording each state change in real time and in detail to the audit log, providing operators with log records to trace the entire lifecycle of the control process.

[0020] When using it, please refer to the steps outlined above: In current power system control and operation management, linear or finite state machine models are commonly used. These models suffer from drawbacks such as coarse state division, imperfect anomaly handling mechanisms, and insufficient granularity in equipment lock management. This leads to difficulties in recovering from control flow interruptions, frequent conflicts between multiple concurrent processes, and weak operation backtracking capabilities. This step establishes a complete control flow lifecycle management mechanism by constructing a refined state machine that includes six states: requested, locked, executing, holding, released, and rolled back. It avoids control conflicts through exclusive equipment lock management, ensures equipment isolation in stable states through the holding state, enhances system fault tolerance through the rolled-back state and automatic rollback procedures, and provides traceable closed-loop operation management for operators by combining full-process audit logs.

[0021] S2. Configure a unique device lock for each power device, define a control flow priority determination strategy, arbitrate multiple control flow instances that apply for the same device lock, and ensure that only one control flow instance can obtain the device lock and enter the execution phase at the same time. Step S2 specifically includes: Based on the control flow being in the requested state, a device lock application for the target device is initiated to the system's lock manager. The lock manager checks the current state of the device lock to determine whether it is idle or occupied. If the device lock is determined to be in an idle state, the lock manager immediately assigns the device lock to the currently requesting control flow, records the binding relationship between the lock and the flow instance, and changes the state of the flow instance from requested to locked.

[0022] Step S2 also includes: If the device lock is determined to be in an occupied state, the lock manager immediately initiates the priority determination strategy for arbitration; The priority determination strategy includes: the safety protection process is the highest priority, used for emergency shutdown and protection actions, and cannot be interrupted; the manual operation process is the medium priority, responding to real-time operator instructions; and the automatic control process is the lowest priority, triggered by preset conditions. If the current control flow has a higher priority than the current lock holder, the lock manager immediately sends an interrupt signal to the lower priority flow that currently holds the lock, forcing it to enter the interrupt handling flow. If the priority of the current control flow is lower than or equal to that of the current lock holder, the lock manager will put the application process into a conflict state, suspend it in the waiting queue of the target device, or directly reject the application and return a rejection feedback to the initiator.

[0023] Step S2 also includes: Based on the control flow being in a released or rolled-back state, the system actively releases the device lock it holds. After receiving the release signal, the lock manager releases the binding relationship between the lock and the control flow and immediately checks the waiting queue of the target device. If the waiting queue is not empty, the lock manager selects the control flow instance with the highest priority in the queue, assigns it a device lock, and changes its state from suspended to locked. If the waiting queue is empty, the device lock remains idle and waits for the next request, ensuring that only one control flow instance can acquire the device lock and enter the execution phase at any given time.

[0024] When using it, please refer to the steps outlined above: In current power equipment control systems, there is a common problem of imperfect conflict handling mechanisms when multiple processes access devices concurrently. This includes a lack of dynamic priority arbitration strategies and rigid interruption mechanisms, often leading to delayed emergency protection responses or low-priority processes blocking system resources. This step addresses this by constructing a three-level priority-based device lock management strategy. This strategy enables mandatory interruption priority for safety protection processes, real-time response guarantees for manual operations, and queue scheduling for automatic control processes. This effectively improves system security and resource scheduling efficiency, ensuring that critical operations always have the highest execution authority.

[0025] S3. Based on the execution phase, when it is detected in the device lock management that a control flow instance cannot continue due to the device lock being occupied, it is set to a conflict state according to the priority policy, and a suspension, interruption or rollback strategy is automatically adopted. After the conflict condition is resolved, the suspended control flow instance is automatically attempted to be restored. Step S3 specifically includes: Based on the fact that the control flow is in a locked state, the SCADA monitoring and data acquisition system is used to continuously detect the lock status and waiting queue of all devices. When a high-priority control flow is detected requesting a device lock that is being held by a low-priority control flow, the lock manager immediately sets the low-priority control flow to a conflict state. Based on setting low-priority control flows to a conflict state, the conflict handling strategy of the control flow is adaptively adjusted.

[0026] Step S3 also includes: For control flows that cannot immediately acquire a lock due to low priority, the system suspends them and places them in the target device waiting queue. If a high-priority control flow needs to interrupt a low-priority control flow, the lock manager immediately sends an interrupt signal to the low-priority control flow. The interrupted control flow immediately stops any current execution action, and the system forcibly switches it to a rolled-back state, starts the rollback procedure to restore the target device state, and releases the device lock. If two control flows of the same priority compete for the same device lock, they will be executed according to the order in which they are issued, and the control flow that arrives later will be suspended and placed in a waiting queue.

[0027] Step S3 also includes: Based on control flow conflict resolution, the system automatically resumes suspended control flows. If the device lock is successfully restored, the system restores it from the suspended state to the locked state and continues to execute the next control flow. If the device lock restoration fails, the control flow directly enters the rolled-back state to prevent repeated execution.

[0028] When using it, please refer to the steps outlined above: In existing technologies, equipment lock management often relies on static priority scheduling or simple first-come-first-served strategies, lacking the ability to adaptively handle dynamic conflicts in the control flow. This often leads to prolonged blocking of low-priority processes, low system resource utilization, and the inability to quickly release equipment locks when high-priority tasks intervene, easily causing deadlocks or state inconsistencies. This step introduces a conflict detection and adaptive handling mechanism based on real-time monitoring, achieving intelligent scheduling and rapid rollback of high and low priority processes, improving system response efficiency and resource utilization. At the same time, through automatic recovery and state consistency assurance, it effectively avoids process duplication and equipment state conflicts, enhancing the reliability and flexibility of control processes in complex industrial environments.

[0029] Based on the above, the specific implementation method is as follows: Initially, wind turbine #1 is in operation, without a tag or lock-on procedure. When the wind speed parameter is detected to be greater than 25 by the SCADA monitoring and data acquisition system, procedure A is automatically triggered. The automatic control type is the lowest priority. The system immediately creates an independent control procedure instance, records the target device as #1_FAN, and sets the initial state to requested. After successfully applying for a device lock, the process instance transitions to the locked state and then enters the execution state, starting to issue speed adjustment commands to the fan. At this time, the system generates an independent audit log to fully record the state transition time and control parameters. During the execution of process A, the operator initiates process B at 10:01:30. The manual control type is medium priority. The lock manager detects that the device lock has been occupied and immediately starts the priority arbitration strategy. According to the three-level priority determination rule, process B has a higher priority than process A. The system immediately sends an interrupt signal to process A. The interrupted process A stops execution and is forcibly converted to a rolled-back state. The rollback program is automatically started to restore the fan to the running state before process A was executed and release the equipment lock. After process B successfully obtains the equipment lock, its state is converted to locked and it is ready to execute the shutdown control command. After process B acquires the equipment lock, the system changes its status from locked to executing, successfully issues a shutdown command to put the fan into a stopped state, and after the SCADA monitoring and data acquisition system confirms that the equipment has reached stability, the status of process B changes to holding, and finally changes to released when the preset endpoint is reached, automatically releasing the equipment lock and ending the process instance. At this time, the equipment status is updated to stopped running and the tagging status is changed to tagged, and the lock holding process is recorded as process B. Throughout the process, the system achieves full lifecycle management through six state transitions of the state machine, resolves concurrent conflicts by relying on priority arbitration, and constructs a traceable operation loop through audit logs.

[0030] The foregoing has shown and described the basic principles, main features, and advantages of the present invention. Those skilled in the art should understand that the present invention is not limited to the above embodiments. The embodiments and descriptions in the specification are merely principles of the invention. Various changes and modifications can be made to the invention without departing from its spirit and scope, and all such changes and modifications fall within the scope of the claimed invention. The scope of protection claimed by the appended claims and their equivalents is defined.

Claims

1. A method for handling automatic control conflicts in the new energy industry, characterized in that, include: S1. Abstract the control operations of power equipment into independent control process instances, construct a control process state machine, and realize lifecycle management of process instances; S2. Configure a unique device lock for each power device, define a control flow priority determination strategy, arbitrate multiple control flow instances that apply for the same device lock, and ensure that only one control flow instance can obtain the device lock and enter the execution phase at the same time. S3. Based on the execution phase, when it is detected in the device lock management that a control flow instance cannot continue due to the device lock being occupied, it is set to a conflict state according to the priority policy, and a suspension, interruption or rollback strategy is automatically adopted. After the conflict condition is resolved, the suspended control flow instance is automatically attempted to be restored.

2. The method for handling automatic control conflicts in the new energy industry according to claim 1, characterized in that, Step S1 specifically includes: Based on the SCADA monitoring and data acquisition system, when the system detects that the target power equipment control operation is triggered, an independent control process instance is immediately created for the control operation, and the target equipment, control command and origin information of the control process instance are accurately recorded. After creating an independent control flow instance, the initial state is automatically set to requested. This initial state indicates that the control flow has been formally initiated and is waiting to request the control lock of the target device. Based on the control flow being in the requested state, the system checks whether the device lock of the target device is free. If the device lock is free, the process instance successfully acquires the lock and the state transitions to locked. This state indicates that the control flow has obtained exclusive operation qualification on the target device and is ready to enter the execution phase. Once the control flow is locked, the control flow instance begins to actually issue control commands to the target device, including start, speed adjustment, and stop. Once the commands are issued, the control flow status is immediately updated to "in execution".

3. The method for handling automatic control conflicts in the new energy industry according to claim 2, characterized in that, Step S1 also includes: Once the control flow is in the execution state, the system confirms that the device has correctly received and executed the instruction, and that the device has reached the state required by the instruction. The control flow state then changes to the holding state, which indicates that the control operation has taken effect and the target device is in a stable state isolated by the control flow. If the control process is in a held state, it will automatically end when it reaches its preset endpoint. The control process instance will terminate normally, and the control process state will change to released, releasing the device lock it holds, making the target device available for control by other processes.

4. The method for handling automatic control conflicts in the new energy industry according to claim 3, characterized in that, Step S1 also includes: Based on the SCADA monitoring and data acquisition system, if the control process fails to execute, is interrupted by a higher priority process, or is actively canceled by the operator, the process status will be forcibly changed to rolled back. Once in this state, the system will immediately start the rollback procedure to try to restore the target device status to the initial state before the execution of the control process and release the device lock. Integrate the six control flow states: requested, locked, executing, holding, released, and rolled back, and establish a control flow state machine; For each independent control process instance, an independent audit log is created, recording each state change in real time and in detail to the audit log, providing operators with log records to trace the entire lifecycle of the control process.

5. The method for handling automatic control conflicts in the new energy industry according to claim 1, characterized in that, Step S2 specifically includes: Based on the control flow being in the requested state, a device lock application for the target device is initiated to the system's lock manager. The lock manager checks the current state of the device lock to determine whether it is idle or occupied. If the device lock is determined to be in an idle state, the lock manager immediately assigns the device lock to the currently requesting control flow, records the binding relationship between the lock and the flow instance, and changes the state of the flow instance from requested to locked.

6. The method for handling automatic control conflicts in the new energy industry according to claim 5, characterized in that, Step S2 also includes: If the device lock is determined to be in an occupied state, the lock manager immediately initiates the priority determination strategy for arbitration; The priority determination strategy includes: the safety protection process is the highest priority, used for emergency shutdown and protection actions, and cannot be interrupted; the manual operation process is the medium priority, responding to real-time operator instructions; and the automatic control process is the lowest priority, triggered by preset conditions. If the current control flow has a higher priority than the current lock holder, the lock manager immediately sends an interrupt signal to the lower priority flow that currently holds the lock, forcing it to enter the interrupt handling flow. If the priority of the current control flow is lower than or equal to that of the current lock holder, the lock manager will put the application process into a conflict state, suspend it in the waiting queue of the target device, or directly reject the application and return a rejection feedback to the initiator.

7. The method for handling automatic control conflicts in the new energy industry according to claim 6, characterized in that, Step S2 also includes: Based on the control flow being in a released or rolled-back state, the system actively releases the device lock it holds. After receiving the release signal, the lock manager releases the binding relationship between the lock and the control flow and immediately checks the waiting queue of the target device. If the waiting queue is not empty, the lock manager selects the control flow instance with the highest priority in the queue, assigns it a device lock, and changes its state from suspended to locked. If the waiting queue is empty, the device lock remains idle and waits for the next request, ensuring that only one control flow instance can acquire the device lock and enter the execution phase at any given time.

8. The method for handling automatic control conflicts in the new energy industry according to claim 7, characterized in that, Step S3 specifically includes: Based on the fact that the control flow is in a locked state, the SCADA monitoring and data acquisition system is used to continuously detect the lock status and waiting queue of all devices. When a high-priority control flow is detected requesting a device lock that is being held by a low-priority control flow, the lock manager immediately sets the low-priority control flow to a conflict state. Based on setting low-priority control flows to a conflict state, the conflict handling strategy of the control flow is adaptively adjusted.

9. The method for handling automatic control conflicts in the new energy industry according to claim 8, characterized in that, Step S3 also includes: For control flows that cannot immediately acquire a lock due to low priority, the system suspends them and places them in the target device waiting queue. If a high-priority control flow needs to interrupt a low-priority control flow, the lock manager immediately sends an interrupt signal to the low-priority control flow. The interrupted control flow immediately stops any current execution action, and the system forcibly switches it to a rolled-back state, starts the rollback procedure to restore the target device state, and releases the device lock. If two control flows of the same priority compete for the same device lock, they will be executed according to the order in which they are issued, and the control flow that arrives later will be suspended and placed in a waiting queue.

10. The method for handling automatic control conflicts in the new energy industry according to claim 9, characterized in that, Step S3 also includes: Based on control flow conflict resolution, the system automatically resumes suspended control flows. If the device lock is successfully restored, the system restores it from the suspended state to the locked state and continues to execute the next control flow. If the device lock restoration fails, the control flow directly enters the rolled-back state to prevent repeated execution.

Images