A robot operation timing planning method and system based on integrity verification
By adopting a robot operation timing planning method based on integrity verification, the problem of insufficient data integrity in industrial robot production line operations is solved, and the accuracy of data and the reliability and security of the scheduling results are achieved, thereby improving scheduling efficiency and anomaly monitoring capabilities.
Patent Information
- Application Number
- CN202611184748.0
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2026-08-06
- Publication Date
- 2026-11-17
AI Technical Summary
In industrial robot production line operations, existing technologies lack a unified means of verifying data integrity, which leads to erroneous data flowing into the programming stage. It is difficult to detect resource contention and time overlap, resulting in low efficiency and easy omissions in adjusting the programming results, and a lack of closed-loop verification mechanism.
A robot operation timing planning method based on integrity verification is adopted. By receiving and verifying workstation coordinate files, process parameter files and planning schemes, a directed acyclic graph is generated, conflict detection and compliance review are carried out, and a closed-loop adjustment mechanism is formed to ensure data accuracy and the executability of the scheduling results.
It implements integrity verification during the data import phase, preventing erroneous data from flowing in and improving the reliability and security of the orchestration results. It enhances the traceability of the total project duration calculation through explicit modeling of directed acyclic graphs, ensures the executability and security of the task sequence, and provides real-time monitoring of the execution status and anomaly tracing.
Smart Images

Figure CN123117599A_ABST
Abstract
Description
Technical Field
[0001] This invention relates to the field of industrial robot operation planning and control technology, specifically to a robot operation timing planning method and system based on integrity verification. Background Technology
[0002] In industrial robot production line operations, the scheduling of processes such as welding, handling, and inspection usually requires simultaneous consideration of the resource constraints, workstation layout, and process parameters of multiple robots. Traditionally, this involves manually arranging the task sequence on tables or drawings, followed by on-site engineers checking for resource conflicts item by item.
[0003] This decentralized orchestration method has several technical drawbacks. First, the workstation coordinate files, process parameters, and planning schemes, as the three basic input data, come from different sources and have different formats. There is a lack of unified data integrity verification methods when importing them into the system. Incorrect coordinate values or incomplete parameter sets may only be exposed during the orchestration stage, leading to repeated rework. Second, the temporal dependencies between work steps are often implicit in process experience, lacking explicit directed dependency modeling. As the number of processes or robots increases, it is difficult for humans to detect resource contention and time overlaps. Third, the adjustment process of the orchestration results lacks a closed-loop verification mechanism. Whether the modified plan eliminates the original conflicts and complies with safety regulations can only be verified manually again, which is inefficient and prone to omissions.
[0004] Therefore, there is a need for a robot operation timing planning technology that can perform integrity verification from the data import stage and form an automatic closed loop between orchestration, conflict detection, and compliance review. Summary of the Invention
[0005] The present invention aims to solve the above-mentioned technical problems and provide a robot operation timing planning method and system based on integrity verification.
[0006] To achieve the above objectives, the present invention provides a robot operation timing planning method based on integrity verification in its first aspect, comprising the following steps: receiving imported workstation coordinate files, process parameter files, and planning schemes; performing data integrity verification on these three types of input data respectively; saving the data that passes integrity verification to the scheme resource library by version, and associating each version with batch identifiers and adjustment records; reading target version data from the scheme resource library, defining sequential dependencies for operation steps, generating task sequences based on dependencies, and completing time window constraint allocation and resource allocation in the same round of processing to obtain the orchestration result; performing conflict detection and compliance review on the orchestration result, locating the detected conflicting steps and related resource information to specific task items, and returning to step S3 for adjustment if conflicts exist; publishing the reviewed and approved task sequences to the execution unit, refreshing the execution status snapshot through polling, and comparing the execution progress with the published sequences to monitor deviations.
[0007] In this method, integrity verification is a prerequisite for data to enter the orchestration process. Workstation identifiers in the workstation coordinate file must be unique, and 3D coordinate values and attitude data must meet format and range requirements. Key-value pairs in the process parameter file must be complete and of matching types. The node topology of the planning scheme must be connected, and dependency references must point to existing nodes. Only data that simultaneously meets these verification conditions is allowed to be imported into the database by version.
[0008] The version saving process incorporates an import confirmation window mechanism. When a node with the same name overwrites another, the system visually lists the import file, the target solution, and the affected scope. The user must confirm before the write operation can proceed. Each version is associated with a batch identifier and adjustment record, distinguishing the solution content under different batches and different adjustment records.
[0009] Task sequence generation is based on directed acyclic graph modeling. The system uses critical path analysis to determine the set of critical steps and floating time that determine the total project duration, and uses this to determine whether there is room for time compression. Resource allocation is visualized through a resource allocation matrix, where rows correspond to work steps, columns correspond to robots, and matrix cells are marked as occupied, idle, or not involved, facilitating intuitive identification of resource occupancy.
[0010] The conflict detection phase covers three types of scenarios: resource usage conflicts, time overlap conflicts, and logical dependency inconsistencies. Each conflict record includes the IDs of the two steps involved in the conflict, conflict resource information, and the time overlap interval, along with a severity level and blocking reason. Compliance review evaluates the current planning scheme item by item based on a predefined list of compliance rules, including time overlap rules, axis interference rules, safety clearance rules, and torque limitation rules. Evaluation results are presented in three levels: pass, fail, or warning. Issues discovered during the review are fed back to the timing orchestration phase for correction, followed by a second review until the task sequence reaches an executable state.
[0011] The execution status monitoring system obtains execution status register data from each robot controller through polling. It writes the current execution step number, task completion percentage, and robot status code into a local snapshot table, and then compares it item by item with the planned baseline in the published sequence to identify slow-moving or stalled work nodes. When a step progresses slowly or its status is abnormal, the cause can be traced by combining the plan and review records.
[0012] In a second aspect of the present invention, a robot operation timing planning system based on integrity verification is provided, comprising: a data import and verification module, a scheme resource management module, a timing arrangement and parameter configuration module, a conflict detection and compliance review module, an execution status monitoring module, and an audit and backtracking center module.
[0013] Compared with the prior art, the present invention has the following beneficial effects: First, integrity verification is implemented during the data import phase to intercept non-compliant data at the source, preventing erroneous data from flowing into the orchestration process and causing repeated rework, thereby improving the data reliability of the entire job planning chain.
[0014] Second, by explicitly modeling the dependencies of work steps using directed acyclic graphs and combining this with critical path analysis, the calculation of the total project duration and the location of bottleneck steps become traceable, avoiding the implicit assumptions in manual experience-based scheduling.
[0015] Third, conflict detection and compliance review form a closed-loop adjustment mechanism. After the orchestration results are automatically detected and problems are found, they are fed back to the orchestration stage for correction. The corrected results are reviewed again until they are approved before they can be released, which ensures the executability and security of the task sequence.
[0016] Fourth, the execution status monitoring quantifies on-site execution deviations into traceable abnormal signals by polling snapshots and comparing them with the planned baseline, providing a data foundation for the early detection of production line anomalies and root cause tracing. Attached Figure Description
[0017] Figure 1This is the first half of the flowchart of the robot operation timing planning method based on integrity verification in the embodiments of the present invention.
[0018] Figure 2 This is the latter half of the flowchart of the robot operation timing planning method based on integrity verification in the embodiments of the present invention.
[0019] Figure 1 The meanings of each marker are as follows: 101 - Receive workstation coordinate file, process parameter file, and planning scheme; 102 - Perform data integrity verification; 103 - Verification passed / failed; 104 - Prompt user to correct data; 105 - Save to the scheme resource library by version; 106 - Read target version data from the scheme resource library; 107 - Define the sequential dependencies of work steps and construct a directed acyclic graph; 108 - Generate task sequence and perform critical path analysis; 109 - Complete time window constraint allocation and resource allocation; 110 - Perform conflict detection and compliance review; 111 - Transfer. Figure 2 .
[0020] Figure 2 The meanings of the markers are as follows: 201 - Conflict or non-compliance exists; 202 - Locate the conflicting steps and resource information; 203 - Return to adjust the orchestration; 204 - Publish the task sequence to the execution unit; 205 - Poll and refresh the execution status snapshot; 206 - Compare with the plan baseline to monitor deviations; 207 - End; 208 - Return. Figure 1 Step 107. Detailed Implementation
[0021] The present invention will be further described in detail below with reference to the accompanying drawings and specific embodiments, but the present invention is not limited thereto.
[0022] like Figure 1 As shown, the robot operation timing planning method based on integrity verification in this embodiment of the invention first executes step 101, receiving the imported workstation coordinate file, process parameter file, and planning scheme. The operator selects the target production line scheme in the project dropdown box of the scheme resource management interface, confirms the current operation object, and imports the above three types of files separately or simultaneously. After receiving the uploaded files, the system does not directly write the data to the business table, but first proceeds to step 102 to perform data integrity verification. (Continue referring to...) Figure 1Step 102 performs integrity checks on the three types of input data. The checks for the workstation coordinate files include: verifying whether each workstation record contains a workstation identifier and workstation name field, whether the X, Y, and Z values of the 3D coordinates are within the pre-configured physical space range, and whether the format of the attitude data conforms to Euler angles or quaternions specifications. The checks for the process parameter files include: verifying whether the parameter key-value pairs are complete and whether the data type of each parameter matches the expected type. The checks for the planning scheme include: verifying whether the node topology of the scheme is connected, whether there are isolated nodes, and whether the predecessor node ID in the dependency references actually exists in the node list.
[0023] Step 103 determines whether the verification passed. If the verification failed, step 104 prompts the user to correct the data and returns to step 101 to re-import.
[0024] If the verification passes, proceed to step 105, where the data that passed the integrity verification is saved to the solution resource library by version. The verified data will then appear in the import confirmation window, displaying the import file name and size, the target solution name and scope of impact, and highlighting whether nodes with the same name will be overwritten. The conflict handling method is clearly explained to the user: in the event of a configuration with the same name, the imported version will be used to replace it. The confirmation item states that the operation is irreversible. After user confirmation, the data is written to the solution resource library by version. Each version's snapshot includes the solution name, included resources, estimated size, and save location, as well as snapshot tags and change descriptions added by the user.
[0025] Next, execute step 106 to read the target version data from the solution resource library. Then, execute step 107 to define the sequential dependencies of the work steps in the topology graph. Node types include roles such as welding, handling, and inspection, and a directed acyclic graph is constructed to represent the dependencies between steps. The configuration information for each node includes: node name, target workstation, executing robot, standard time consumption, earliest start time, latest start time, and time window type. Preconditions can be added in subsequent adjustments.
[0026] Step 108 generates a task sequence based on dependencies. The system calculates the critical path based on the directed acyclic graph. The critical path analysis results are displayed on the left side of the interface, showing the total duration, number of critical steps, and float time, while the steps in the critical sequence are listed sequentially on the right side.
[0027] Step 109 completes time window constraint allocation and resource allocation within the same round of processing. Time window constraint allocation sets the earliest start time, latest start time, standard duration, and time window type for each job step, and adds exclusive mutual exclusion constraints between steps allocated to the same robot. The resource allocation matrix is presented in row-column matrix form, with rows corresponding to each job step and columns corresponding to each robot. Matrix cells are marked as occupied, idle, or unused, and the number of conflicts and the utilization rate of each robot are displayed below. During the scheduling process, the interface continuously displays the progress percentage, number of iterations, estimated remaining time, and fitness trend.
[0028] Step 110 performs conflict detection and compliance review. The conflict detection engine scans the resource usage timeline and identifies three conflict types: resource usage conflicts, time overlap conflicts, and logical dependency inconsistency conflicts. The detection results list displays the conflict ID, involved steps, resource usage, and level. Continue to refer to... Figure 2 Step 201 determines whether there are conflicts or non-compliance. If a conflict exists, step 202 locates the conflicting steps and resource information, then step 203 returns to adjust the orchestration, and finally step 208 returns to the previous step. Figure 1 Step 107 involves readjusting dependencies and task sequences. The system also provides an automatic offset suggestion function, calculating offset suggestions based on timing constraints. The preview results list the offset objects, suggested offset amounts, and constraint bases. Compliance review checks the current planning scheme item by item according to the rule list, which includes timing overlap rules, axis interference rules, safety clearance rules, and torque limit rules. The evaluation results are divided into three levels: pass, fail, and warning.
[0029] If both conflict detection and compliance review pass, proceed to step 204 to publish the approved task sequence to the execution unit. Publish a snapshot version of the current plan in the operation log and distribute the task sequence to the controllers of each robot.
[0030] Step 205: Send a status query request to each robot controller according to the preset polling cycle, read the execution status register data, and write the current execution step number, task completion percentage and robot status code into the local snapshot table.
[0031] Step 206 compares the local snapshot with the planned baseline in the published sequence item by item to identify work nodes that are progressing slowly or have stalled. When a step is progressing slowly or has stalled, the system highlights the deviation information on the monitoring interface. Operators can then trace the cause by combining existing plans and reviewing records.
[0032] Step 207 is complete.
[0033] The Audit and Retrospection Center records all parameter changes, task executions, deployment actions, and result exports. Each audit log entry includes fields for audit entry identifier, operation role, operation type, target entity, and entity identifier. Logs support querying by time window and operation type. In parameter change scenarios, the interface displays the old and new values side-by-side, with an arrow in the middle indicating the direction of change, and the bottom displays the comparison version number and the number of changed fields.
[0034] The above embodiments are only used to illustrate the technical solutions of the present invention and are not intended to limit the scope of protection of the present invention. Any modifications, equivalent substitutions, improvements, etc., made within the spirit and principles of the present invention should be included within the scope of protection of the claims of the present invention.
Claims
1. A robot operation timing planning method based on integrity verification, characterized in that, Includes the following steps: The system receives imported workstation coordinate files, process parameter files, and planning schemes. It verifies the uniqueness of workstation identifiers, the legal range of three-dimensional coordinate values, and the format integrity of attitude data in the workstation coordinate files. It verifies the integrity of parameter key-value pairs and data type matching in the process parameter files. It verifies the connectivity of node topology and the validity of dependency references in the planning scheme. Data that passes integrity verification is saved to the solution resource library by version, and batch identifiers and adjustment records are associated with each version. When saving, prompts are given to handle overwrite conflicts of nodes with the same name, and imported files, target solutions and scope of impact are listed in a visual way for users to review. The target version data is read from the solution resource library, a directed acyclic graph is constructed to express the dependencies between job steps, a task sequence is generated according to the dependencies, the critical path analysis method is used to determine the set of critical steps and floating time in the task sequence, and time window constraint allocation and resource allocation are completed in the same round of processing to obtain the orchestration result. The time window constraint allocation sets the earliest start time, latest start time, standard time and time window type for each job step, and adds exclusive mutual exclusion constraints between steps allocated to the same robot. The orchestration results are subjected to conflict detection and compliance review. Resource usage conflicts, time overlap conflicts, and logical dependency inconsistency conflicts are detected. A severity level and blocking reason are assigned to each conflict record. The detected conflict steps and related resource information are located to specific task items. If a conflict exists, the process returns to step S3 for adjustment. The approved task sequence is published to the execution unit, and the execution status register of each robot controller is read by polling at a preset period. The current execution step number, task completion percentage and robot status code are written into the local snapshot table. The snapshot is compared with the planned baseline in the published sequence item by item to monitor deviations.
2. The robot operation timing planning method based on integrity verification according to claim 1, characterized in that, The data integrity verification performed in step S1 specifically includes: verifying the uniqueness of the workstation identifier, the legal range of the three-dimensional coordinate values, and the format integrity of the attitude data for the workstation coordinate file; verifying the integrity of the parameter key-value pairs and the data type matching for the process parameter file; and verifying the connectivity of the node topology and the validity of the dependency references for the planning scheme.
3. The robot operation timing planning method based on integrity verification according to claim 1, characterized in that, In step S2, when saving data by version, the import confirmation window provides a prompt for handling overwrite conflicts of nodes with the same name, and lists the imported files, target scheme, and scope of impact in a visual manner for user review.
4. The robot operation timing planning method based on integrity verification according to claim 1, characterized in that, The step S3 of generating the task sequence further includes: constructing a directed acyclic graph to express the dependencies between task steps, using critical path analysis to determine the set of critical steps and the floating time in the task sequence, and determining the total duration based on the set of critical steps.
5. The robot operation timing planning method based on integrity verification according to claim 1, characterized in that, When allocating time window constraints in step S3, the earliest start time, latest start time, standard duration, and time window type are set for each job step, and exclusive mutual exclusion constraints are added between steps allocated to the same robot.
6. The robot operation timing planning method based on integrity verification according to claim 1, characterized in that, The specific steps of conflict detection in step S4 include: detecting resource occupation conflicts, time overlap conflicts, and logical dependency inconsistency conflicts; assigning a severity level and blocking reason to each conflict record; and writing the two step IDs involved in the conflict, conflict resource information, and time overlap interval together into the conflict detection record.
7. The robot operation timing planning method based on integrity verification according to claim 1, characterized in that, The compliance review in step S4 further includes: evaluating the current planning scheme item by item according to a predefined list of compliance rules, which includes time overlap rules, axis interference rules, safety distance rules and torque limit rules. The evaluation results are presented in three levels: pass, fail or warning.
8. The robot operation timing planning method based on integrity verification according to claim 1, characterized in that, The polling method for refreshing the execution status snapshot in step S5 further includes: reading the execution status register of each robot controller at a preset period, writing the current execution step number, task completion percentage and robot status code into the local snapshot table, and comparing the snapshot with the planned baseline in the published sequence item by item to identify work nodes that are progressing slowly or have stalled.
9. A robot operation timing planning system based on integrity verification, characterized in that, include: The data import and verification module is used to receive workstation coordinate files, process parameter files, and planning schemes, and to perform data integrity verification. The solution resource management module is used to save verified data by version and manage batch identifiers and adjustment records; The timing orchestration and parameter configuration module is used to define the sequential dependencies of job steps, generate task sequences, and complete time window constraint allocation and resource allocation. The conflict detection and compliance review module is used to detect conflicts and assess compliance in the orchestration results, locate conflicting steps and resource information, and drive the adjustment closed loop. The execution status monitoring module is used to poll and refresh the execution status snapshot and monitor execution deviations by comparing them with the plan baseline. The Audit and Retrospection Center module is used to record parameter changes, task execution, release actions, and result export events, and supports querying by time window and operation type.
10. The robot operation timing planning system based on integrity verification according to claim 9, characterized in that, The conflict detection and compliance review module further includes a resource allocation matrix submodule, which displays the assignment relationship between each operation step and each robot in a row-column matrix format. The matrix units are marked as occupied, idle, or not participating in three states, and the number of resource conflicts and the utilization rate of each robot are calculated simultaneously.
