Methods for generating and closing-loop processing system-level handling tasks in material control systems
By establishing context records for vehicles, generating system-level tasks, and introducing alternative destination strategies, the problems of delayed abnormal response and weak fault tolerance in material control systems are solved, thereby improving the intelligence and stability of the system.
Patent Information
- Application Number
- CN202611423350.8
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2026-09-14
- Publication Date
- 2026-11-17
Smart Images

Figure CN123113759A_ABST
Abstract
Description
Technical Field
[0001] This invention relates to the field of material control, and more particularly to a method for generating and closing-loop processing system-level handling tasks in a material control system. Background Technology
[0002] In the fields of modern intelligent manufacturing and automated warehousing and logistics, material control systems or handling control systems play a crucial scheduling role. With the advancement of Industry 4.0, the level of automation in factory logistics is constantly improving, and automated guided vehicles, rail-guided vehicles, overhead cranes, and other vehicles are widely used for material transfer in wafer manufacturing, panel production, and smart warehouses.
[0003] In these high-precision, high-continuity production environments, the efficiency and stability of material flow directly determine overall production capacity. However, in actual operation, due to factors such as equipment failure, path congestion, communication delays, or manual intervention, vehicles are prone to abnormal stoppages, path blockages, or identity conflicts. To maintain the long-term stable operation of the system, an efficient and intelligent system-level task management mechanism is essential. This mechanism must be able to automatically identify anomalies, generate transfer or rejection tasks, and ensure traceability and closed-loop control of the entire lifecycle of tasks from creation to completion.
[0004] Existing systems often rely on manual monitoring or simple timeout alarm mechanisms. When vehicles malfunction or become stuck, manual intervention is usually required. The lack of automated mechanisms for generating system-level tasks such as malfunctioning vehicle removal and idle vehicle relocation leads to malfunctioning vehicles occupying critical channel resources for extended periods, severely impacting overall logistics efficiency.
[0005] In complex factory maps, route planning failures are a common problem. Existing technologies typically resort to simple retries or simply dropping the task with an error message when encountering a dead end, lacking differentiated alternative destination strategies for different task types. This prevents vehicles from flexibly relocating to backup sites when encountering localized congestion or equipment malfunctions, reducing system flexibility.
[0006] When faced with multiple concurrent system-level task requests, existing technologies often lack a dynamic evaluation system based on a preset set of rules. They cannot intelligently determine the task type based on event details and the vehicle's current state, nor can they dynamically adjust the insertion position in the execution queue based on the task type and creation time, resulting in critical tasks being blocked by non-urgent tasks.
[0007] Therefore, we propose a method for generating and closing-loop processing system-level handling tasks in material control systems to solve the above problems. Summary of the Invention
[0008] This invention provides a method for generating and closing-loop processing system-level handling tasks in a material control system, which addresses the problems of delayed abnormal response, lack of closed-loop management, and weak fault tolerance in existing systems.
[0009] The first aspect of this invention provides a method for generating and closing-loop processing system-level handling tasks in a material control system. The method includes: detecting a trigger event occurring on a target object and establishing a context record for the target object; evaluating the target object based on the context record and obtaining an evaluation result; when the evaluation result indicates that a task needs to be created, constructing a target task and associating the target task with the context record; executing the target task and synchronizing the execution status of the target task to the context record during execution; when an execution exception occurs during the execution of the target task, determining a backup strategy based on the context record, updating the execution parameters of the target task based on the backup strategy, and recording the update information in the context record; and when the target task reaches its final state, performing closed-loop processing on the target task based on the context record.
[0010] Optionally, in a first implementation of the first aspect of the present invention, the target object includes a vehicle, and the triggering event includes an abnormal event or a lingering event; The context record includes event details, task type flags, and state transition history.
[0011] Optionally, in a second implementation of the first aspect of the present invention, the step of performing rule evaluation on the target object based on the context record to obtain an evaluation result; and constructing the target task when the evaluation result indicates that a task needs to be created, includes: Obtain the context record and the current state information of the target object; Select a matching target rule from the preset rule set, and perform condition judgment based on the current state information; When the judgment result of the condition is passed, the task construction instruction corresponding to the target rule is obtained, the target task is constructed according to the task construction instruction, and the task type tag is written when constructing the target task.
[0012] Optionally, in a third implementation of the first aspect of the present invention, the step of selecting a matching target rule from a preset rule set and performing condition judgment in conjunction with the current state information includes: Candidate rules that are associated with the context record and the condition content are selected from the preset rule set to generate a candidate rule set; The candidate rule set is sorted according to a preset priority order to obtain a sorted rule sequence; The rules are matched and judged one by one from the sorted sequence of rules in descending order of priority; When the matching result is satisfactory, the matching judgment of subsequent candidate rules is stopped, the candidate rule that satisfies the matching result is taken as the target rule, and a rule hit record is generated; the rule hit record is used to generate the task construction instruction.
[0013] Optionally, in a fourth implementation of the first aspect of the present invention, the execution of the target task, including synchronizing the execution status of the target task to the context record during execution, includes: The target task is sent to the execution queue, the task identifier of the target task is obtained, and the execution order of the target task in the execution queue is determined. The execution order and the task identifier are synchronized to the context record, and the status of the context record is updated to a queuing status; When the target task begins execution, the execution start time is recorded. During the execution of the target task, the state changes of the target task are monitored, and the changed execution state and the corresponding state change time are written into the context record in sequence.
[0014] Optionally, in a fifth implementation of the first aspect of the present invention, the execution exception includes path planning failure, the execution parameters include the destination, and the backup strategy includes a backup destination strategy. When an execution exception occurs during the execution of the target task, a backup strategy is determined based on the context record, and the execution parameters of the target task are updated based on the backup strategy, including: When the path planning fails, obtain the reason for the failure and determine whether the reason for the failure is an untransferable type. When the failure reason does not belong to the untransferable type, the corresponding backup destination strategy is determined from the preset strategy set according to the task type tag in the context record; Obtain a set of available destinations, filter the available destinations according to the backup destination strategy, and select candidate destinations that meet preset conditions as backup destinations; After updating the destination of the target task to the backup destination, route planning is performed again.
[0015] Optionally, in a sixth implementation of the first aspect of the present invention, the final state includes normal completion, abnormal completion, task cancellation, and transfer failure; The closed-loop processing of the target task based on the context record includes: Release the resources occupied by the target task, and record the resource release result in the context record; Based on the final state and the context record, determine the corresponding reporting method, and send the execution result of the target task and the final state to the upper layer system according to the reporting method; When the final state is the abnormal completion or the transfer failure, determine whether the target task belongs to the cyclic test associated task, and if it belongs to the cyclic test associated task, stop the test process corresponding to the cyclic test associated task. The context record containing the resource release result and the execution result is archived.
[0016] Optionally, in the seventh implementation of the first aspect of the present invention, an identifier update process for the target object is further included: Obtain the renaming status information of the target object; When the renaming status information is pending renaming and the target identifier corresponding to the target object is not occupied, a renaming execution instruction is generated; The rename execution instruction is sent to the device where the target object is located, so that the device where the target object is located performs an update operation on the identification information of the target object; Obtain the update result of the update operation and write the update result into the context record.
[0017] Beneficial effects: A context record containing event details, type tags, and state transition history was established for each candidate vehicle, enabling the system to not only issue commands but also perceive its state. During execution, all state synchronization, path updates, and even final state archiving rely on this context thread, solving the pain points of black-box task execution and difficulty in backtracking anomalies in traditional systems, and improving the maintainability and debugging efficiency of the system. Candidate vehicles are matched against predefined rule sets, and system-level tasks are dynamically constructed based on the matching rules. In particular, a unique identifier is assigned to each task type and applied throughout the entire process of task creation, distribution, fault tolerance, and closed-loop management. This enables the system to adopt differentiated handling strategies for different types of anomalies, avoiding the drawbacks of a one-size-fits-all approach and enhancing the system's intelligence level. A backup destination query and update logic based on system task type was introduced at the task execution layer. When route planning fails, the system no longer directly reports an error or retryes indefinitely, but intelligently switches to a backup site and replans based on the type tag, reducing the risk of global stagnation caused by local congestion or equipment failure and significantly improving the robustness of the system. By incorporating the renaming operation into the system-level management scope, strictly verifying the conflict between active task occupancy and target identifier before execution, and synchronously updating the context record after the operation, the barrier between physical vehicle identity and logical task data is broken down, ensuring strong data consistency of the system in high-concurrency scenarios. The system clearly defines various final state types, such as normal completion, abnormal completion, cancellation, and transfer failure, and performs a series of actions accordingly, including resource release, result reporting, cessation of related tests, and historical archiving. This effectively prevents zombie tasks from illegally occupying transportation equipment and port resources for extended periods, ensuring the long-term stability and resource utilization of the system. Attached Figure Description
[0018] Figure 1 This is a schematic diagram of an embodiment of the method for generating and closing-loop processing system-level handling tasks in the material control system of the present invention. Detailed Implementation
[0019] This invention provides a method for generating and closing-loop processing system-level handling tasks in a material control system, addressing the problems of delayed abnormal response, lack of closed-loop management, and weak fault tolerance in existing systems. The terms "first," "second," "third," "fourth," etc. (if present) in the specification, claims, and accompanying drawings are used to distinguish similar objects and are not necessarily used to describe a specific order or sequence. It should be understood that such data can be interchanged where appropriate so that the embodiments described herein can be implemented in a sequence other than that illustrated or described herein. Furthermore, the terms "comprising" or "having" and any variations thereof are intended to cover a non-exclusive inclusion; for example, a process, method, system, product, or apparatus that comprises a series of steps or units is not necessarily limited to those steps or units explicitly listed, but may include other steps or units not explicitly listed or inherent to such processes, methods, products, or apparatus.
[0020] For ease of understanding, the specific process of the embodiments of the present invention is described below. Please refer to [link / reference]. Figure 1 An embodiment of the method for generating and closing-loop processing system-level handling tasks in the material control system of the present invention includes: 101. Define a system task type set, which includes abnormal vehicle exclusion, idle vehicle transfer, vehicle return, inventory scan, and task transfer. When an abnormal event or a vehicle is detected to be stuck, the vehicle involved is identified as a candidate vehicle, and a context record is established for each candidate vehicle. The context record includes event details, a system task type flag determined based on the event details, and a state transition history, thus obtaining the initial context record.
[0021] It is understood that the executing entity of this invention can be a device for generating and closing-loop processing system-level handling tasks in a material control system, or it can be a terminal or a server; the specific implementation is not limited here. This embodiment of the invention will be described using a server as an example.
[0022] Specifically, a predefined set of system task types is defined, including abnormal vehicle exclusion, idle vehicle transfer, vehicle return, inventory scan, and task transfer. A unique type tag is assigned to each system task type, and a corresponding backup destination strategy is set for each system task type. The status of vehicles in the system is monitored. When the identification information of a vehicle meets the preset abnormal rules, an abnormal event is determined to have occurred. When the dwell time of a vehicle on a non-storage device exceeds a preset threshold, a dwell event is determined to have occurred. Vehicles experiencing abnormal or delayed events are identified as candidate vehicles, and the corresponding event details are recorded to obtain a candidate vehicle set. For each candidate vehicle in the candidate vehicle set, a context record is established, in which the event details, the system task type marker determined based on the event details, and the initial state are written into the context record, and the initial state and the time of event occurrence are recorded as state transition history to obtain the initial context record.
[0023] 102. Based on the initial context record, perform rule evaluation on the candidate vehicle according to the preset rule set. When the evaluation result indicates that a system-level task needs to be created, construct the system-level task according to the system task type tag, record the task identifier of the system-level task in the context record, and obtain the context record carrying the task identifier and system task type tag. At the same time, make the system-level task carry the system task type tag.
[0024] Specifically, the system obtains the initial context record and the current status information of the candidate vehicles, selects the rule that matches the event details from the preset rule set, and performs condition judgments on the candidate vehicles in order of rule priority. When the rule ranked first in the rule priority order passes the judgment, the judgment of subsequent rules is stopped, and the task construction instruction is determined according to the rule that passes the judgment, so as to obtain the evaluation result carrying the task construction instruction. Based on the evaluation results of the task construction instructions, obtain the task construction method corresponding to the system task type tag, construct the system-level task according to the task construction method, and write the system task type tag into the attribute field of the system-level task during construction to obtain the system-level task carrying the system task type tag; write the system-level task carrying the system task type tag into the task storage area to obtain the task identifier, append the task identifier to the initial context record, update the state transition history, record the current state as the scheduled state, and obtain the context record carrying the task identifier and system task type tag.
[0025] Furthermore, the event details and current status information of candidate vehicles are obtained from the initial context record. Rules whose condition content is related to the event details are filtered from the preset rule set to generate a candidate rule set. The candidate rule set is sorted according to the preset priority order to obtain a sorted rule sequence. Rules are obtained one by one from the sorted rule sequence in order of priority from high to low. The condition content of the current rule is matched with the current status information of the candidate vehicle and the initial context record. When the matching result is satisfied, the matching of subsequent rules is stopped, and the rule identifier and the condition content that satisfies the condition are recorded to generate a rule hit record carrying the rule identifier and condition content. Based on the rule hit record, the rule action corresponding to the rule identifier is obtained, the rule action is converted into a task construction instruction, and the rule hit record is used as the basis for generating the task construction instruction to obtain an evaluation result carrying the task construction instruction and the rule hit record. The evaluation result carrying the task construction instruction and the rule hit record is used to determine the task construction method corresponding to the system task type tag.
[0026] 103. Deploy system-level tasks for execution. During execution, synchronize the execution status of the system-level tasks to the context record carrying the task identifier and system task type flag to obtain the context record carrying the execution status.
[0027] Specifically, system-level tasks carrying system task type tags are sent to the execution queue. The execution queue arranges the execution order between system-level tasks and existing tasks according to a preset order, and synchronizes the execution order information and the task identifier of the system-level task to the context record. At the same time, the status of the context record is updated to the queuing status, resulting in a context record carrying queuing status information and execution order. When a system-level task begins execution, the state of the context record is updated to the execution state, and the execution start time is recorded, resulting in a context record carrying the execution start time and a system task type flag. During the execution of the system-level task, the state changes of the system-level task are monitored, and the changed state and the corresponding state change time are written into the context record in sequence, updating the state transition history, resulting in a context record carrying the execution state. The context record carrying the execution state includes the execution order, the execution start time, and all state change records.
[0028] Furthermore, obtain the context record carrying the task identifier and system task type tag, extract the system task type tag from the context record, obtain the task priority value corresponding to the system-level task from the preset priority mapping table according to the system task type tag, and use the creation time of the system-level task as the time reference point to generate the sorting basis, and obtain the sorting basis information carrying the task priority value and time reference point. The sorting criteria information, carrying task priority values and time reference points, is compared one by one with the sorting criteria information of existing tasks in the execution queue. Based on the comparison results, the insertion position of the system-level task in the execution queue is determined, and the insertion operation is performed at the insertion position to generate an execution queue with completed insertion. Based on the sequence number of the insertion position in the execution queue, a position identifier is generated. The position identifier, the task identifier of the system-level task, and the sorting criteria information are synchronized to the context record. At the same time, the status of the context record is updated to the queuing status, generating a context record carrying the queuing status, position identifier, and sorting criteria information. The context record carrying the queuing status, position identifier, and sorting criteria information is used to determine the execution priority order when the system-level task starts to execute.
[0029] 104. When a system-level task fails to plan its path during execution, the system task type flag is retrieved from the context record carrying the execution status. The backup destination is determined according to the backup destination policy corresponding to the system task type flag. The destination of the system-level task is updated to the backup destination, and the path planning is re-performed. The path update information is then appended to the context record to obtain the context record carrying the path update information.
[0030] Specifically, during the execution of a system-level task, when path planning fails, the reason for failure is obtained, and it is determined whether the reason for failure belongs to a preset non-transferable type. If the reason for failure does not belong to a non-transferable type, the reason for failure and the time of failure are written into the context record, and the state transition history is updated to obtain a context record carrying the reason for failure. The system task type flag is obtained from the context record carrying the reason for failure. Based on the system task type flag, the corresponding backup destination strategy is determined from the preset backup destination strategy set. The available destination list is queried according to the backup destination strategy. A destination that meets the preset conditions is selected from the available destination list as a backup destination. The backup destination and its selection basis are recorded to obtain a context record carrying backup destination information. The destination of the system-level task is updated to the backup destination. The route planning is re-executed according to the updated destination to obtain the re-planning result. When the re-planning result indicates that the route planning is successful, the backup destination, the selection basis, and the re-planning result are written to the context record, the state transition history is updated, and a context record carrying the route update information is obtained. When the re-planning result indicates that the route planning fails, the system-level task is marked as a transfer failure, and the transfer failure record is appended to the context record to obtain a context record carrying the transfer failure record.
[0031] Furthermore, the system task type tag is extracted from the context record carrying the failure reason record, and the backup destination strategy corresponding to the system task type tag is searched in the preset backup destination strategy set to obtain the matching backup destination strategy; the matching backup destination strategy contains destination type constraints and destination selection rules; according to the destination type constraints, destinations that meet the destination type constraints are filtered in the currently available destination set to generate a candidate destination set. Query the real-time status information of each candidate destination in the candidate destination set. Based on the destination selection rules and the real-time status information of each candidate destination, determine one candidate destination as a backup destination from the candidate destination set and generate a selection basis record. The selection basis record contains the selected backup destination and the reason for selection. Write the backup destination and the selection basis record into a context record that carries a failure reason record, update the state transition history, and obtain a context record carrying backup destination information. The context record carrying backup destination information is used to perform destination update and re-route planning.
[0032] 105. When a system-level task reaches its final state, closed-loop processing is performed based on the context record carrying path update information. Closed-loop processing includes releasing the resources occupied by the system-level task, reporting the execution result of the system-level task to the upper-level system, and archiving the context record.
[0033] Specifically, when a system-level task reaches its final state, a context record carrying path update information is obtained to determine the final state type of the system-level task. The final state type includes normal completion, abnormal completion, task cancellation, and transfer failure. Based on the final state type, the sequence of actions that the system-level task needs to execute in the closed-loop processing phase is determined, and a closed-loop processing instruction carrying the final state type and action sequence is obtained. The resource release operation is executed according to the closed-loop processing instructions, releasing the transportation equipment resources and port resources occupied by the system-level task, and recording the resource release result and release completion time in the context record to obtain a context record carrying the resource release record; according to the final state type and the system task type mark in the context record, the corresponding reporting method is determined from the preset reporting method set, and the execution result and final state type of the system-level task are sent to the upper-layer system according to the reporting method, and the reporting result and reporting time are recorded in the context record to obtain a context record carrying the reporting record; When the final state type is abnormal completion or transfer failure, the system-level task is determined to be a cyclic test associated task based on the system task type flag in the context record. If it is a cyclic test associated task, the cyclic test process associated with the system-level task is stopped, and the stop result is recorded in the context record to obtain a context record carrying the associated stop record. The information in the context record carrying the resource release record, the context record carrying the reporting record, and the context record carrying the associated stop record are summarized to generate final state archive information. The final state archive information is written into the context record, and the context record is transferred to the historical storage area to complete the closed-loop archiving process.
[0034] 106. During system operation, the renaming status information of each vehicle is obtained. When a vehicle's renaming status is detected as pending renaming, it is checked whether the vehicle is occupied by an active task. Unoccupied vehicles awaiting renaming are identified as candidate renaming vehicles, and a candidate renaming vehicle set is generated. For each candidate renaming vehicle in the candidate renaming vehicle set, it is checked whether the target identifier corresponding to the candidate renaming vehicle is occupied by other active tasks. When the target identifier is not occupied, the renaming capability information of the device where the candidate renaming vehicle is located is obtained. A renaming execution instruction is generated based on the vehicle's renaming status and renaming capability information, and a confirmation result carrying the renaming execution instruction is obtained. The renaming execution instruction is sent to the device where the candidate renaming vehicle is located, so that the device performs an update operation on the identifier information of the candidate renaming vehicle according to the renaming execution instruction, and obtains a vehicle with an updated identifier. Obtain the update result of the updated identifier of the vehicle. When the candidate vehicle to be renamed has a corresponding context record, write the update result and the renaming completion time into the context record corresponding to the candidate vehicle to update the state transition history. When the candidate vehicle to be renamed does not have a corresponding context record, create a new context record for the candidate vehicle to be renamed, and write the update result and the renaming completion time into the new context record to obtain a context record carrying the renaming completion record. The context record carrying the renaming completion record is used as the basis for rule evaluation in subsequent polling cycles.
[0035] Further, the current identifier information and target identifier information of each candidate renaming vehicle in the candidate renaming vehicle set are obtained. The format of the current identifier information is verified, including whether the identifier length, identifier character composition, and identifier prefix conform to preset rules, and an identifier format verification result is generated. The identifier format verification result is used to determine whether the candidate renaming vehicle has the basic conditions to perform the renaming operation. When the identifier format verification result is passed, it is checked whether the device where the candidate renaming vehicle is located is online and whether it has the identifier writing capability. At the same time, it is checked whether the target identifier of the candidate renaming vehicle is occupied by other active tasks, and a device capability confirmation result and a target identifier occupancy check result are generated. The device capability confirmation result, the target identifier occupancy check result, and the identifier format verification result together constitute the renaming pre-confirmation information. Based on the target identifier occupancy check result in the renaming pre-confirmation information and the equipment capability confirmation result, a renaming execution instruction is generated. The renaming execution instruction contains the current identifier, target identifier, and identifier update method of the candidate renaming vehicle, resulting in a renaming execution instruction carrying the current identifier information, target identifier information, and identifier update method. The renaming execution instruction carrying the current identifier information, target identifier information, and identifier update method is used by the equipment where the candidate renaming vehicle is located to perform the identifier update operation. The renaming execution instruction carrying the current identifier information, target identifier information, and identifier update method is sent to the equipment where the candidate renaming vehicle is located, so that the equipment updates the current identifier of the candidate renaming vehicle to the target identifier according to the identifier update method, generating a vehicle with updated identifier. The vehicle with updated identifier is used to obtain the update result later.
[0036] The present invention also provides a device for generating and closing-loop processing system-level handling tasks in a material control system. The device includes a memory and a processor. The memory stores computer-readable instructions. When the computer-readable instructions are executed by the processor, the processor performs the steps of the method for generating and closing-loop processing system-level handling tasks in the material control system described in the above embodiments.
[0037] The present invention also provides a computer-readable storage medium, which can be a non-volatile computer-readable storage medium or a volatile computer-readable storage medium, wherein the computer-readable storage medium stores instructions that, when the instructions are executed on a computer, cause the computer to perform the steps of the method for generating and closing-loop processing system-level handling tasks in the material control system.
[0038] Those skilled in the art will clearly understand that, for the sake of convenience and brevity, the specific working processes of the systems, devices, and units described above can be referred to the corresponding processes in the foregoing method embodiments, and will not be repeated here.
[0039] If the integrated unit is implemented as a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present invention, in essence, or the part that contributes to the prior art, or all or part of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute all or part of the steps of the methods described in the various embodiments of the present invention. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, portable hard drives, read-only memory (ROM), random access memory (RAM), magnetic disks, or optical disks.
[0040] The above-described embodiments are only used to illustrate the technical solutions of the present invention, and are not intended to limit it. Although the present invention has been described in detail with reference to the foregoing embodiments, those skilled in the art should understand that modifications can still be made to the technical solutions described in the foregoing embodiments, or equivalent substitutions can be made to some of the technical features. Such modifications or substitutions do not cause the essence of the corresponding technical solutions to deviate from the spirit and scope of the technical solutions of the embodiments of the present invention.
Claims
1. A method for generation and closed loop processing of system level handling tasks in a material control system, characterized in that, include: A triggering event is detected in the target object, and a context record is established for the target object; Based on the context record, the target object is evaluated according to rules to obtain an evaluation result; when the evaluation result indicates that a task needs to be created, the target task is constructed and associated with the context record; Execute the target task, and during the execution process, synchronize the execution status of the target task to the context record; When an execution exception occurs during the execution of the target task, a backup strategy is determined based on the context record, the execution parameters of the target task are updated based on the backup strategy, and the update information is recorded in the context record. When the target task reaches its final state, closed-loop processing is performed on the target task based on the context record.
2. The method of claim 1, wherein the system-level handling task is generated and closed-loop processed in the material control system. The target object includes a vehicle, and the triggering event includes an abnormal event or a lingering event; The context record includes event details, task type flags, and state transition history.
3. The method of claim 2, wherein the system-level handling task is generated and closed-loop processed in the material control system, and the method further comprises: receiving a system-level handling task from a system-level handling task generator; and determining whether the system-level handling task is to be executed by the system-level handling task executor. The process involves evaluating the target object based on the context record to obtain an evaluation result; when the evaluation result indicates that a task needs to be created, constructing the target task includes: Obtain the context record and the current state information of the target object; Select a matching target rule from the preset rule set, and perform condition judgment based on the current state information; When the judgment result of the condition is passed, the task construction instruction corresponding to the target rule is obtained, the target task is constructed according to the task construction instruction, and the task type tag is written when constructing the target task.
4. The method for generating and closing-loop processing system-level handling tasks in a material control system according to claim 3, characterized in that, The step of selecting a matching target rule from a preset rule set and performing condition judgment in conjunction with the current state information includes: Candidate rules that are associated with the context record and the condition content are selected from the preset rule set to generate a candidate rule set; The candidate rule set is sorted according to a preset priority order to obtain a sorted rule sequence; The rules are matched and judged one by one from the sorted sequence of rules in descending order of priority; When the matching result is satisfactory, the matching judgment of subsequent candidate rules is stopped, the candidate rule that satisfies the matching result is taken as the target rule, and a rule hit record is generated; the rule hit record is used to generate the task construction instruction.
5. The method for generating and closing-loop processing system-level handling tasks in a material control system according to claim 1, characterized in that, The execution of the target task, including synchronizing the execution status of the target task to the context record during execution, includes: The target task is sent to the execution queue, the task identifier of the target task is obtained, and the execution order of the target task in the execution queue is determined. The execution order and the task identifier are synchronized to the context record, and the status of the context record is updated to a queuing status; When the target task begins execution, the execution start time is recorded. During the execution of the target task, the state changes of the target task are monitored, and the changed execution state and the corresponding state change time are written into the context record in sequence.
6. The method for generating and closing-loop processing system-level handling tasks in a material control system according to claim 2, characterized in that, The execution exception includes path planning failure; the execution parameters include the destination; and the backup strategy includes an alternative destination strategy. When an execution exception occurs during the execution of the target task, a backup strategy is determined based on the context record, and the execution parameters of the target task are updated based on the backup strategy, including: When the path planning fails, obtain the reason for the failure and determine whether the reason for the failure is an untransferable type. When the failure reason does not belong to the untransferable type, the corresponding backup destination strategy is determined from the preset strategy set according to the task type tag in the context record; Obtain a set of available destinations, filter the available destinations according to the backup destination strategy, and select candidate destinations that meet preset conditions as backup destinations; After updating the destination of the target task to the backup destination, route planning is performed again.
7. The method for generating and closing-loop processing system-level handling tasks in a material control system according to claim 1, characterized in that, The final state includes normal completion, abnormal completion, task cancellation, and transfer failure; The closed-loop processing of the target task based on the context record includes: Release the resources occupied by the target task, and record the resource release result in the context record; Based on the final state and the context record, determine the corresponding reporting method, and send the execution result of the target task and the final state to the upper layer system according to the reporting method; When the final state is the abnormal completion or the transfer failure, determine whether the target task belongs to the cyclic test associated task, and if it belongs to the cyclic test associated task, stop the test process corresponding to the cyclic test associated task. The context record containing the resource release result and the execution result is archived.
8. The method for generating and closing-loop processing system-level handling tasks in a material control system according to claim 1, characterized in that, It also includes an identifier update process for the target object: Obtain the renaming status information of the target object; When the renaming status information is pending renaming and the target identifier corresponding to the target object is not occupied, a renaming execution instruction is generated; The rename execution instruction is sent to the device where the target object is located, so that the device where the target object is located performs an update operation on the identification information of the target object; Obtain the update result of the update operation and write the update result into the context record.
