A method and system for scheduling work tasks in an automated three-dimensional warehouse
Through the task scheduling model of centralized release and decentralized claim, the problems of low equipment execution efficiency and limited intelligent development in automated three-dimensional warehouses are solved, and the equipment independently selects tasks and improves the intelligent and operation efficiency of the warehouse.
Patent Information
- Application Number
- CN202210675735.9
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- Filing Date
- 2022-06-15
- Publication Date
- 2024-11-26
- Estimated Expiration
- 2042-06-15
AI Technical Summary
The task scheduling of existing automated three-dimensional warehouses relies on central computers, resulting in low equipment execution efficiency and limited intelligent development, and equipment cannot independently select tasks.
Adopt a task scheduling model of centralized release and decentralized claim. The central computer receives user orders and publishes operation tasks. The equipment independently claims and performs tasks according to its own status, reduces the load of the central computer and enhances equipment autonomy.
It improves the operating efficiency and intelligence level of the warehouse, reduces the load and data monitoring of the central computer, and strengthens the participation of equipment in task scheduling.
Smart Images

Figure CN115115194B_ABST
Abstract
Description
Technical Field
[0001] The present invention belongs to the field of task management of automated stereoscopic warehouses, and more specifically, relates to a method and system for scheduling operation tasks of automated stereoscopic warehouses. Background Art
[0002] Automated high-bay warehouses are widely in demand in China. In 2018, more than 5,000 automated high-bay warehouses were built in China, mainly in the manufacturing, clothing, medicine, food and tobacco industries. With the development of the market, the scale of the high-bay warehouse market has maintained an annual growth rate of more than 10% in recent years.
[0003] The task scheduling of warehouse equipment is the core of the management of the automated warehouse. It is mainly responsible for decision-making, coordination and allocation of work tasks of various equipment in the warehouse, ensuring the continuous turnover and sequential handover of goods in and out of the warehouse between different equipment, and maintaining parallel working status between each equipment, so that the operation of the entire warehouse can continue to run uninterruptedly. World-renowned automated warehouse task scheduling products include warehouse management systems developed by companies such as SAP of Germany and Oracle of the United States, which can manage complex warehouse distribution processes and supply chain logistics, and optimize multi-channel task fulfillment in real time. Domestic companies have also developed automated three-dimensional task scheduling software, such as Shenyang Siasun Robot Automation Co., Ltd., Shenyang AVIC Antai Technology Co., Ltd., Jiangsu Six Dimensions Intelligent Logistics Equipment Co., Ltd., Shanghai Guanmei Technology Co., Ltd., etc.
[0004] However, the current task scheduling of the automated warehouse system is mainly handled by the central computer, which adopts a centralized management method, that is, the central computer formulates the work tasks of each device according to the user's in and out orders, and then assigns the tasks to each warehouse device to complete. The coordination between the devices is controlled by the central computer, and the devices cannot independently select their own tasks or arrange their own work processes. This method can ensure that the warehouse equipment operates collaboratively under unified command and dispatch, and has the advantages of easy management, high reliability and good stability. However, the centralized management method also has certain disadvantages: first, all task management is the responsibility of the central computer. When the central computer is overloaded or fails, it will affect the operating efficiency of each device; second, in order to coordinate the parallel work of warehouse equipment, the central computer needs to centrally collect the status data of all devices in the warehouse. When data collection is delayed or wrong, it will affect the timeliness and accuracy of the central computer's coordination and dispatch; third, each device completely obeys the command of the central computer, and has no right to make independent decisions, so it is impossible to optimize the task execution process autonomously according to the actual situation of the warehouse, which hinders the development of automated warehouses to a higher level of intelligence.
[0005] Although there are many existing patents on automated warehouses, they are mainly focused on the innovation of hardware equipment structure, cargo transfer process, cargo space allocation management, and warehouse information management. They do not involve the allocation and management method of inbound and outbound tasks among various devices, especially without considering that as the intelligence level of equipment continues to increase, the equipment should also become one of the decision makers for task allocation. For example, patent document CN201510640281.1 proposes a method for optimizing the scheduling of tasks in a warehouse through task conflict detection; patent document CN202111466840.3 proposes a method for evenly sending tasks to various devices for execution based on the execution status of warehouse equipment and the full load of tasks; patent document CN202110628930.1 proposes a task allocation method mainly for stackers, with the aim of minimizing the time it takes for stackers to complete tasks; patent document CN201811154356.5 proposes a system for real-time control and image display of logistics processes by an operating platform based on real-time operation data and task instructions issued by the WMS / ERP system.
[0006] There are also many existing patents on task scheduling, but they are mainly concentrated in the field of task scheduling of computer programs, especially the use of distributed mode by computers to allocate and manage program tasks, and do not involve the scheduling of tasks for entering and exiting warehouses. Although some patents have proposed more general task scheduling methods, such as patent documents CN202111317594.5 and CN202111177573.8, the task allocation mode is still that the central computer sends tasks to the equipment, rather than each device autonomously selecting tasks according to its own status, and there are no products that can be used for automated warehouses.
[0007] In summary, existing technologies and products mainly adopt a centralized management mode for the task scheduling of automated stereoscopic warehouses, that is, the central computer decomposes the in-and-out tasks into subtasks that can be executed by different devices in the warehouse, and then uniformly allocates them to various devices and schedules the devices to execute them in sequence, resulting in excessive reliance on the central computer when each device is working. When the central computer is unable to fully understand the working status of the equipment due to excessive load, poor network, algorithm errors, etc., it will affect the effect of task allocation, reduce the execution efficiency of the equipment, and further affect the warehouse's in-and-out capacity. In addition, the equipment itself does not have the right to independently choose tasks, which also hinders the further development of the intelligent stereoscopic warehouse. Summary of the invention
[0008] In view of the defects of the prior art, the purpose of the present invention is to provide a method and system for scheduling work tasks in an automated warehouse, aiming to solve the problem that the task scheduling in the existing automated warehouse is too dependent on the central control computer, and the equipment itself has no right of autonomous selection, resulting in poor task allocation effect and low equipment execution efficiency.
[0009] To achieve the above-mentioned purpose, in a first aspect, the present invention provides a method for scheduling job tasks in an automated warehouse, comprising the following steps:
[0010] Receive the inbound and outbound orders issued by the user, and establish an inbound and outbound operation task list according to the inbound and outbound orders; the operation task list includes multiple operation tasks, and the information of each operation task includes: task identification, task content, predicted completion time point, release time, release number, inbound and outbound order number, execution equipment type, execution equipment identification, task status, previous task identification and next task identification; the task content is a list of various movement locations and execution operation types passed by the equipment when executing the task, the previous task identification is the identification of the previous operation task that must be completed before executing the operation task in the inbound and outbound order to which the operation task belongs, and the next task identification is the identification of the next operation task that should be started after executing the operation task in the inbound and outbound order to which the operation task belongs;
[0011] Extracting the work tasks from the work task list in sequence and publishing them on the device network, so that the devices in the warehouse can determine whether to claim the corresponding tasks based on the work task information and the device's own conditions; each work task can be claimed by multiple warehouse devices, and finally the best warehouse device is selected as the successfully claimed device;
[0012] When a certain operation task cannot be released and an error is reported, if only less than one-third of the operation tasks in the inbound and outbound order to which the operation task belongs are claimed, it is considered that the inbound and outbound order cannot be completed, all the operation tasks contained in the inbound and outbound order are cleared, and a claim failure message is sent to the device that has claimed the task; if one-third to two-thirds of the operation tasks in the inbound and outbound order to which the operation task belongs are claimed, it is considered that the inbound and outbound order may be completed, all the operation tasks contained in the order are cleared, a claim failure message is sent to the device that has claimed the tasks in the order, and then the inbound and outbound order is re-issued. If the task release of the order reports an error again after the inbound and outbound order is re-issued, it is considered that the order cannot be completed; if more than two-thirds of the operation tasks in the inbound and outbound order to which the operation task belongs are claimed, it is considered that the inbound and outbound order should be completed, and the operation task is re-issued. If the operation task still reports an error after being re-issued twice, it is considered that the order cannot be completed, all the tasks contained in the order are cleared, and a claim failure message is sent to the device that has claimed the tasks in the order;
[0013] When all the work tasks in the inbound and outbound orders are claimed, a claim success mark is sent to the warehouse equipment that claims the work tasks to instruct each device to execute the claimed work tasks.
[0014] In an optional example, the job tasks are sequentially extracted from the job task list and published on the device network, specifically:
[0015] Regularly search the job task list to extract job tasks suitable for release; the job tasks suitable for release are: the task status of the current job task is unclaimed, and the task status of the previous job task is claimed;
[0016] Determine the number of times the job task to be released is published. If the number is less than the warning threshold, the job task is published on the device network; if the number is greater than or equal to the warning threshold but less than the error threshold, an alarm is first triggered so that the warehouse manager knows that there is an abnormality in the claiming of the task, and then the job task is published on the device network; if the number is greater than or equal to the error threshold, the job task is not published and an error is reported; when publishing the job task on the device network, the publishing time and the number of publications are updated; the warning threshold is related to the number of devices in the stereoscopic warehouse that can claim and execute the job task, and the error threshold is set to twice the warning threshold.
[0017] In an optional example, the equipment in the warehouse determines whether to accept the corresponding task based on the information of the operation task and the equipment's own situation, specifically:
[0018] S31, the equipment in the warehouse receives the job task published in the network, and determines whether it can execute the job task. If it cannot be executed, the job task is discarded and the process goes to step S33; if it can be executed, the process goes to step S32;
[0019] S32, the device predicts the time point at which the job task is completed, and writes the job task into a task list; the task information in the task list includes: task identifier, task content, task status, predicted time point for completing the task, time when the claim message is sent, number of times the claim message is sent, identifier of the device that executed the previous task, and identifier of the device that executed the next task; the task status is set to unclaimed;
[0020] S33, the task status of the task in the equipment periodic inspection task list is unclaimed;
[0021] S34, calculating the interval between the sending time of the claim message of the task status as unclaimed task and the current time, if the time interval is less than the sending time threshold, go to step S37; if the time interval is greater than or equal to the sending time threshold, go to step S35;
[0022] S35, determine the number of times the claim message of the operation task is sent, if the number of times is greater than the claim threshold, delete the operation task from the task list, and go to step S37; if the number of times is not greater than the claim threshold, go to step S36; the claim threshold is related to the number of devices in the stereoscopic warehouse that can claim and execute the operation task;
[0023] S36, sending a claim message for the job task, updating the time and number of times the claim message is sent; the claim message includes: device ID, task ID, predicted task completion time, and the number of tasks that have been claimed but not completed by the device;
[0024] S37, determine whether the device is turned off. If the device is not turned off, go to step S33. If the device is turned off, the device will no longer claim and execute the task.
[0025] In an optional example, a device in a warehouse receives a job task published in a network and determines whether it can execute the job task, specifically:
[0026] Warehouse equipment determines whether it can execute the published task based on the task content, the number of tasks that have been claimed but not completed, its own fault conditions, and the remaining power;
[0027] If one of the following conditions is met, the equipment is considered unable to perform the task: the equipment cannot reach the starting, middle or end location specified in the task content; the equipment cannot complete the operation type specified in the task; the number of tasks that the equipment has claimed but not completed is more than twice the number of the same type of equipment in the warehouse; the equipment switches to manual control mode and cannot be automatically controlled by the central computer.
[0028] In an optional example, when all the work tasks are claimed, a claim success flag is sent to the warehouse device that claims the work task to instruct each device to execute the claimed work task, specifically:
[0029] Regularly check the claim messages of received job tasks;
[0030] Analyze the task claim message to determine the device that successfully claims the task; select the best warehouse device from the task claim messages of multiple devices that claim the task, as the warehouse device that successfully claims the task, and write the device ID into the execution device ID of the task list; if one or more of the following conditions are met, it is considered to be the best warehouse device: the warehouse device with the closest predicted completion time of the task; the first warehouse device to claim the task; the warehouse device with the least number of claimed but uncompleted tasks;
[0031] Feedback a claim failure message to other warehouse devices that failed to claim the operation task;
[0032] Determine whether the inbound and outbound order to which the operation task belongs can be fully executed; if it cannot be fully executed, continue to regularly check the received claim messages; if it can be fully executed, extract the claim devices of all the operation tasks included in the inbound and outbound order, and feedback the claim success message to each device; the claim success message includes: task ID, device ID, previous task execution device ID and next task execution device ID.
[0033] In an optional example, it is determined whether the inbound and outbound order to which the operation task belongs can be fully executed, specifically:
[0034] Retrieve the job task information in the job task list. If the next job task of the job task is marked as None, it means that the job task is the last task in the inbound and outbound order. When the task is claimed, all the job tasks in the inbound and outbound order have been claimed, indicating that the inbound and outbound order can be fully executed. Otherwise, it is considered that the inbound and outbound order cannot be fully executed.
[0035] In an optional example, the following steps are also included: the warehouse equipment executes the operation task and publishes the task execution result on the equipment network, specifically:
[0036] S51, the device receives a task claim message and determines the status of the claim message;
[0037] S52, if the claim is successful, modify the task status in the task list to "claimed", and then go to step S54;
[0038] S53, if the claim fails, delete the task from the task list and go to step S58;
[0039] S54, the device periodically checks whether the task can be started. If not, go to step S58; if it can be started, go to step S55; the condition for starting the task is: the device has received the completion message sent by the previous task execution device of the task, and the task is the first task in the task list with the status of claimed;
[0040] S55, the device executes the task, changes the task status in the task list to start, and sends a start execution message to the central computer;
[0041] S56: The device completes the task and deletes the task from the task list;
[0042] S57, the device sends a message of completion of execution to the central computer, and at the same time sends a message of completion of execution to the next task execution device of the task;
[0043] S58, determine whether the device is turned off, if not, go to step S51.
[0044] In a second aspect, the present invention provides a job task scheduling system for an automated high-bay warehouse, comprising:
[0045] An order receiving unit is used to receive an inbound and outbound order issued by a user, and to establish an inbound and outbound operation task list according to the inbound and outbound order; the operation task list includes multiple operation tasks, and the information of each operation task includes: task identification, task content, predicted completion time point, release time, release number, inbound and outbound order number, execution device type, execution device identification, task status, previous task identification and next task identification; the task content is a list of various movement locations and execution operation types passed by the equipment when executing the task, the previous task identification is the identification of the previous operation task that must be completed before executing the operation task in the inbound and outbound order to which the operation task belongs, and the next task identification is the identification of the next operation task that should be started after executing the operation task in the inbound and outbound order to which the operation task belongs;
[0046] The task publishing unit is used to sequentially extract the operation tasks from the operation task list and publish them on the device network, so that the devices in the warehouse can determine whether to claim the corresponding tasks according to the information of the operation tasks and the device's own conditions; each operation task can be claimed by multiple warehouse devices, and the best warehouse device is finally selected as the successfully claimed device;
[0047] An error processing unit is used for, when a certain operation task cannot be released and an error is reported, if only less than one-third of the operation tasks in the inbound and outbound order to which the operation task belongs are claimed, it is considered that the inbound and outbound order cannot be completed, all the operation tasks contained in the inbound and outbound order are cleared, and a claim failure message is sent to the device that has claimed the task; if one-third to two-thirds of the operation tasks in the inbound and outbound order to which the operation task belongs are claimed, it is considered that the inbound and outbound order may be completed, all the operation tasks contained in the order are cleared, a claim failure message is sent to the device that has claimed the tasks in the order, and then the inbound and outbound order is re-issued. If the task release of the order reports an error again after the inbound and outbound order is re-issued, it is considered that the order cannot be completed; if more than two-thirds of the operation tasks in the inbound and outbound order to which the operation task belongs are claimed, it is considered that the inbound and outbound order should be completed, and the operation task is re-issued. If the operation task still reports an error after being re-issued twice, it is considered that the order cannot be completed, all the tasks contained in the order are cleared, and a claim failure message is sent to the device that has claimed the tasks in the order;
[0048] The task execution unit is used to send a claim success mark to the warehouse equipment that claims the work task after all the work tasks in the inbound and outbound orders have been claimed, so as to instruct each device to execute the claimed work task; at the same time, it receives the execution results of the claimed tasks fed back by each device. When it is detected that all the tasks in the inbound and outbound orders have been claimed and executed by the equipment, the order is considered to have been executed.
[0049] In an optional example, the task publishing unit periodically retrieves a job task list to extract job tasks suitable for publishing; the job tasks suitable for publishing are: the task status of the current job task is unclaimed, and the task status of the previous job task is claimed; and the number of publications of the job task to be published is determined. If the number is less than a warning threshold, the job task is published on the device network; if the number is greater than or equal to the warning threshold but less than an error threshold, an alarm is first issued so that the warehouse manager knows that there is an abnormality in the claim of the task, and then the job task is published on the device network; if the number is greater than or equal to the error threshold, the job task is not published and an error is reported; when publishing the job task on the device network, the publishing time and number of publications are updated; the warning threshold is related to the number of devices in the stereoscopic warehouse that can claim and execute the job task, and the error threshold is set to twice the warning threshold.
[0050] In an optional example, the system further includes:
[0051] The task claim judgment unit is used to determine whether to claim the corresponding task based on the information of the job task and the device's own situation, specifically: S31, the equipment in the warehouse receives the job task published in the network, and determines whether it can execute the job task. If it cannot be executed, the job task is discarded and the process goes to step S33; if it can be executed, the process goes to step S32; S32, the device predicts the time point when the job task is completed, and writes the job task into the task list; the task information in the task list includes: task identification, task content, task status, predicted time point for completing the task, time when the claim message is sent, number of times the claim message is sent, the previous task execution device identification and the next task execution device identification; the task status is set to unclaimed; S33, the device regularly checks the tasks in the task list whose task status is unclaimed; S34, calculates the claim message sent for the tasks whose task status is unclaimed The interval between the previous time and the current time, if the time interval is less than the sending time threshold, go to step S37; if the time interval is greater than or equal to the sending time threshold, go to step S35; S35, determine the number of times the claim message of the job task is sent, if the number of times it is sent is greater than the claim threshold, delete the job task from the task list, and go to step S37; if the number of times it is sent is not greater than the claim threshold, go to step S36; the claim threshold is related to the number of devices in the stereoscopic warehouse that can claim and execute the job task; S36, send the claim message of the job task, update the time and number of times the claim message is sent; the claim message includes: device identification, task identification, predicted task completion time point, and the number of tasks that the device has claimed but not completed; S37, determine whether the device is turned off, if the device is not turned off, go to step S33, if the device is turned off, the device will no longer claim and execute tasks.
[0052] In general, the above technical solution conceived by the present invention has the following beneficial effects compared with the prior art:
[0053] The present invention provides a method and system for scheduling job tasks in an automated stereoscopic warehouse. The system adopts a task scheduling mode of centralized release and decentralized claiming, and distributes the in-and-out warehouse operations managed by a central computer to different warehouse devices for execution. The central computer receives the in-and-out warehouse orders of users, formulates the job tasks that the warehouse devices need to perform to complete the order, and formulates the order in which different devices perform the tasks, and then publishes the job tasks to each warehouse device through the Internet; the warehouse device receives the job tasks from the Internet, and according to its own status and task requirements, it independently and flexibly claims the job tasks in accordance with the principle of optimal work efficiency, and executes the successfully claimed tasks; the central computer monitors the claiming and execution of the job tasks, and manages the completion of the in-and-out warehouse orders. The present invention realizes the integration of the advantages of centralized task management and independent operation of equipment in an automated stereoscopic warehouse, which can reduce the load of the central computer and the amount of data of the industrial Internet monitoring equipment status, while strengthening the participation of the equipment in the task scheduling decision-making process and improving the intelligence and autonomy of the storage equipment. BRIEF DESCRIPTION OF THE DRAWINGS
[0054] Figure 1 It is a flow chart of a method for scheduling job tasks in an automated warehouse provided by an embodiment of the present invention;
[0055] Figure 2 A flowchart of a job task scheduling system for an automated high-bay warehouse according to an embodiment of the present invention;
[0056] Figure 3 Figure 2 Sub-flow chart of step S2 in FIG.
[0057] Figure 4 Figure 2 Sub-flow chart of step S3;
[0058] Figure 5 Figure 2 Sub-flow chart of step S4;
[0059] Figure 6 Figure 2 Sub-flow chart of step S5;
[0060] Figure 7 It is an architecture diagram of a job task scheduling system for an automated stereoscopic warehouse provided by an embodiment of the present invention. DETAILED DESCRIPTION
[0061] In order to make the purpose, technical solution and advantages of the present invention more clearly understood, the present invention is further described in detail below in conjunction with the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are only used to explain the present invention and are not used to limit the present invention.
[0062] The present invention proposes an automated stereoscopic warehouse task scheduling system, which combines the centralized management of the central computer and the independent operation of the warehouse equipment by adopting a method in which a central computer centrally issues work tasks according to the requirements of inbound and outbound orders, and the warehouse equipment claims and executes the work tasks according to its own status, thereby reducing the operating load of the central computer, improving the automation and intelligent management capabilities of the equipment, and effectively improving the operating efficiency and intelligence of the warehouse.
[0063] The technical problem to be solved by the present invention is to provide a task scheduling system for an automated high-bay warehouse, which can take into account the advantages of centralized management by a central computer and independent operation of warehouse equipment. The central computer uniformly plans and publishes in-and-out warehouse tasks, and the warehouse equipment independently and flexibly selects suitable tasks to be executed based on its own capabilities and current working status, and feeds back the execution results to the central computer.
[0064] The invention discloses an operation task scheduling system for an automated stereoscopic warehouse, wherein the automated stereoscopic warehouse comprises a central computer and warehouse equipment, wherein the warehouse equipment is a mobile machine with automation capability, such as a stacker, a depalletizing and stacking robot, a sorting robot, a conveyor belt, AGVA, RGV, etc.
[0065] Figure 1 is a flow chart of a method for scheduling job tasks in an automated warehouse provided by an embodiment of the present invention; Figure 1 As shown, the following steps are included:
[0066] S101, receiving an inbound and outbound order issued by a user, and establishing an inbound and outbound operation task list according to the inbound and outbound order; the operation task list includes multiple operation tasks, and the information of each operation task includes: task identification, task content, predicted completion time point, release time, release number, inbound and outbound order number, execution device type, execution device identification, task status, previous task identification and next task identification; the task content is a list of various movement locations and execution operation types passed by the equipment when executing the task, the previous task identification is the identification of the previous operation task that must be completed before executing the operation task in the inbound and outbound order to which the operation task belongs, and the next task identification is the identification of the next operation task that should be started after executing the operation task in the inbound and outbound order to which the operation task belongs;
[0067] S102, sequentially extracting the work tasks from the work task list and publishing them on the device network, so that the devices in the warehouse can determine whether to claim the corresponding tasks based on the work task information and the device's own conditions; each work task can be claimed by multiple warehouse devices, and the best warehouse device is finally selected as the successfully claimed device;
[0068] S103, when a certain operation task cannot be released and an error is reported, if only less than one-third of the operation tasks in the inbound and outbound order to which the operation task belongs are claimed, it is considered that the inbound and outbound order cannot be completed, all the operation tasks contained in the inbound and outbound order are cleared, and a claim failure message is sent to the device that has claimed the task; if one-third to two-thirds of the operation tasks in the inbound and outbound order to which the operation task belongs are claimed, it is considered that the inbound and outbound order may be completed, all the operation tasks contained in the order are cleared, a claim failure message is sent to the device that has claimed the tasks in the order, and then the inbound and outbound order is re-issued. If the task release of the order reports an error again after the inbound and outbound order is re-issued, it is considered that the order cannot be completed; if more than two-thirds of the operation tasks in the inbound and outbound order to which the operation task belongs are claimed, it is considered that the inbound and outbound order should be completed, and the operation task is re-issued. If the operation task still reports an error after being re-issued twice, it is considered that the order cannot be completed, all the tasks contained in the order are cleared, and a claim failure message is sent to the device that has claimed the tasks in the order;
[0069] S104, when all the work tasks in the inbound and outbound orders are claimed, a claim success mark is sent to the warehouse equipment that claims the work tasks to instruct each device to execute the claimed work tasks.
[0070] like Figure 2 As shown, an embodiment of the present invention provides a scheduling system for an automated three-dimensional warehouse, and the scheduling system includes the following steps:
[0071] S1. The central computer receives the inbound and outbound orders and creates an inbound and outbound task list;
[0072] Specifically, a warehouse entry and exit order can generate multiple work tasks. Each work task belongs to only one warehouse entry and exit order and can only be executed by a certain type of warehouse equipment. The information of the work task includes: task ID, task content, predicted completion time, release time, release number, warehouse entry and exit order number, execution equipment type, execution equipment ID, task status, previous task ID, and next task ID. Task status includes: unclaimed, claimed, started, and completed. The previous task ID is the ID of the previous task that must be completed before the execution of this task begins in the warehouse entry and exit order to which this work task belongs. The next task ID is the ID of the next task that should be started after the execution of this task is completed in the warehouse entry and exit order to which this work task belongs. Through the previous task ID and the next task ID, the execution order of multiple work tasks in a certain warehouse entry and exit order can be strictly specified.
[0073] Optionally, the task content is a list of equipment movement locations and equipment operation types, including: equipment starting location, equipment starting operation type, equipment intermediate location 1, equipment intermediate operation type 1, ..., equipment intermediate location n, equipment intermediate operation type n, equipment ending location, equipment ending operation type.
[0074] S2, the central computer extracts the job tasks from the job task list and publishes them on the network;
[0075] Specifically, Figure 3 As shown, step S2 includes the following sub-steps:
[0076] S21, the central computer regularly searches the job task list and extracts the job tasks suitable for release;
[0077] Specifically, the job tasks suitable for release are: the task status of the current task is unclaimed, and the task status of the previous task is claimed. The purpose of setting the task release rule is to ensure that the claiming of tasks can be carried out in sequence, that is, if the previous task is not claimed, the next task cannot be claimed, so that the execution of tasks must strictly follow the warehouse process.
[0078] S22, calculate the interval between the release time of the job task and the current time. If the time interval is less than the sending time threshold, go to step S26.
[0079] S23. Determine the number of times the job task is published. If the number is less than the warning threshold, go to step S25. If the number is greater than the warning threshold but less than the error threshold, alarm the system and then go to step S25. If the number is greater than the error threshold, go to step S24.
[0080] Specifically, the warning threshold of a task is related to the number of devices in the high-bay warehouse that can claim and execute the task. Optionally, the warning threshold can be set as follows:
[0081] in The round-up symbol.
[0082] For example, there is a task for an AGV to pick up goods from a storage point. If there are 2 AGVs in the warehouse, the number of devices that can claim and execute the AGV task is 2, and the warning threshold of this task is set to 8; if there are 6 AGVs in the warehouse, the number of devices that can claim and execute the AGV task is 6, and the warning threshold of this task is set to 5.
[0083] Optionally, the error threshold is set to twice the warning threshold.
[0084] S24, stop publishing the task and report an error to the system, then go to step S26.
[0085] Specifically, the system should handle the error manually. If it is not handled manually, the system will first read the inbound and outbound order to which the task belongs from the job task list, and then select the following three methods to automatically handle the job task:
[0086] (1) If less than one-third of the tasks in the order are claimed, the order is considered uncompleted, all tasks included in the order are cleared from the job task list, and a claim failure message is sent to the device that claimed the tasks in the order.
[0087] (2) If one-third to two-thirds of the tasks in the order are claimed, the order is considered to be completed, all tasks included in the order are cleared from the job task list, and a claim failure message is sent to the device that claimed the tasks in the order, and then the inbound and outbound order is re-issued to the central computer. If the task release of the order is reported as an error again after the inbound and outbound order is re-issued, the order is considered to be uncompleted, all tasks of the order are cleared, and a claim failure message is sent to the device that claimed the tasks in the order.
[0088] (3) If more than two-thirds of the tasks in the order have been claimed, the task is considered completed, the release time and release times of the task are reset to zero, and the task is re-released. If the task is still reported as an error after being re-released twice, the order is considered uncompleted, all tasks in the order are cleared, and a claim failure message is sent to the device that claimed the task in the order.
[0089] S25. Publish the task on the device network and update the task publishing time and frequency.
[0090] Optionally, the job task publishing process is: read the task identifier, task content and execution device type from the task list, read the network addresses of all devices of this type from the device network address table according to the execution device type, combine the task identifier, task content and network address into a UDP message, and send it to all warehouse devices of this type.
[0091] S26, the central computer determines whether to shut down, if not, then go to step S21. If yes, then the computer shuts down and ends the task scheduling.
[0092] S3. Warehouse equipment receives the work tasks issued by the central computer and claims the tasks that can be executed at the moment.
[0093] Specifically, Figure 4 As shown, step S3 includes the following sub-steps:
[0094] S31, the warehouse equipment receives the operation task, determines whether it can execute the task, and if not, abandons the task, and then goes to step S33;
[0095] Specifically, the warehouse equipment determines whether it can execute the task issued by the central computer based on the task content, the number of tasks that have been claimed but not completed, its own fault conditions, remaining power, etc. The judgment rules are:
[0096] (1) The equipment cannot reach the starting, middle or end location specified in the task content;
[0097] (2) The device cannot complete the specified type of operation;
[0098] (3) The number of tasks that have been claimed but not completed by the equipment is more than twice the number of the same type of equipment in the warehouse;
[0099] (4) The equipment switches to manual control mode and cannot be automatically controlled by the central computer.
[0100] S32, the warehouse equipment predicts the time point for completing the task and writes the task into the task list;
[0101] Specifically, the task information in the task list includes: task ID, task content, task status, predicted task completion time, claim message sending time, claim message sending times, previous task execution device ID, next task execution device ID. The task status is set to unclaimed;
[0102] S33, tasks in the warehouse equipment regular inspection task list with unclaimed status;
[0103] S34, calculate the interval between the time when the claim message of the task is sent and the current time. If the time interval is less than the sending time threshold, go to step S37;
[0104] S35. Determine the number of times the claim message of the task is sent. If the number of times is greater than the claim threshold, delete the task from the task list, and then go to step S37.
[0105] Specifically, the claim threshold of a task is related to the number of devices in the high-bay warehouse that can execute the task. Optionally, the claim threshold can be set as follows:
[0106] in The round-up symbol.
[0107] S36. Send a claim message for the task to the central computer, and update the time and number of times the claim message is sent.
[0108] Specifically, the claim message includes the device ID, the task ID, the predicted task completion time, and the number of tasks that the device has claimed but not completed.
[0109] S37, the warehouse equipment determines whether to shut down, if not, go to step S33.
[0110] S4. The central computer starts the task according to the task claim result;
[0111] Specifically, Figure 5 As shown, step S4 includes the following sub-steps:
[0112] S41, the central computer regularly checks the received task claim message;
[0113] Specifically, the central computer does not analyze every claim message immediately after receiving it, but waits for a period of time and analyzes after accumulating a certain number of claim messages. The purpose is to ensure that when the same task is claimed by multiple devices, the claim messages sent by all devices can be fully collected, and then analyzed and compared uniformly to select the best claiming device.
[0114] S42, the central computer analyzes the task claiming message and determines the device that successfully claims the task;
[0115] Specifically, the central computer selects the best warehouse device from among the multiple devices claiming the task as the warehouse device that successfully claims the task based on the task claiming messages, and writes the device ID into the execution device ID of the task list. The confirmation of the claiming device can be judged by one or more of the following conditions:
[0116] (1) Predict the warehouse equipment closest to the time when the task will be completed;
[0117] (2) The first warehouse equipment to claim the task;
[0118] (3) Warehouse equipment with the least number of claimed but uncompleted tasks;
[0119] S43, the central computer feeds back a claim failure message to other warehouse devices that failed to claim the task;
[0120] S44, the central computer analyzes whether the inbound and outbound orders to which the task belongs can be fully executed. If not, go to step S46;
[0121] Specifically, the central computer retrieves the job task information from the job task list. If the next task of the job task is marked as none, it means that the task is the last task in the inbound and outbound order. When the task is claimed, all the job tasks in the inbound and outbound order have been claimed, indicating that the inbound and outbound order can be fully executed.
[0122] S45. The central computer extracts the claiming devices of all tasks included in the warehousing order, and feeds back a claiming success message to each device; the claiming success message includes: task ID, device ID, device ID for executing the previous task, and device ID for executing the next task.
[0123] S46, the central computer determines whether to shut down, if not, then go to step S41. If yes, then the computer shuts down and ends the task scheduling.
[0124] S5. Warehouse equipment executes the task and publishes the task execution results to the central computer and other equipment;
[0125] Specifically, Figure 6 As shown, step S5 includes the following sub-steps:
[0126] S51. The warehouse equipment receives the task claim message fed back by the central computer and determines the status of the claim message.
[0127] S52: If the claim is successful, the task status in the task list is changed to claimed, and then go to step S54.
[0128] S53: If the claim fails, delete the task from the task list and go to step S58.
[0129] S54, regularly check whether the task can be started, if not, go to step S58,
[0130] Specifically, the condition for starting the execution of a task is that the device has received a completion message sent by the device that executed the previous task of the task, and the task is the first task in the task list with a status of claimed.
[0131] S55: The device executes the task, changes the task status in the task list to start, and sends a start execution message to the central computer.
[0132] S56: The device completes the task and deletes the task from the task list.
[0133] S57, the device sends a message of completion of execution to the central computer, and at the same time sends a message of completion of execution to the next task execution device of the task.
[0134] S58: The device determines whether to shut down. If not, go to step S51.
[0135] S6. The central computer receives the task completion execution message from the device and determines the completion status of the inbound and outbound orders;
[0136] Specifically, the central computer receives the task execution completion message from each device and changes the task status in the task list to completed. If the next task of a task is marked as None and the status of the task is Completed, it means that the inbound and outbound orders to which the task belongs have been completed. The inbound and outbound orders are archived and all tasks of the inbound and outbound orders are deleted from the job task list.
[0137] S7. The central computer regularly checks the completion status of each claimed task in the task list.
[0138] Specifically, if a task exceeds the predicted completion time point and no completion execution message is received from the device, it is considered that there is a problem with the execution of the task and an alarm is sent to the system.
[0139] S8, the central computer determines whether to shut down, if not, go to step S1. If yes, the computer shuts down and ends the task scheduling.
[0140] Figure 7 : is a diagram of the system architecture of the automated warehouse operation task scheduling provided by the embodiment of the present invention, such as Figure 7 As shown, including:
[0141] The order receiving unit 710 is used to receive the inbound and outbound orders issued by the user, and to establish an inbound and outbound operation task list according to the inbound and outbound orders; the operation task list includes multiple operation tasks, and the information of each operation task includes: task identification, task content, predicted completion time point, release time, release number, inbound and outbound order number, execution device type, execution device identification, task status, previous task identification and next task identification; the task content is a list of various movement locations and execution operation types passed by the equipment when executing the task, the previous task identification is the identification of the previous operation task that must be completed before executing the operation task in the inbound and outbound order to which the operation task belongs, and the next task identification is the identification of the next operation task that should be started after executing the operation task in the inbound and outbound order to which the operation task belongs;
[0142] The task publishing unit 720 is used to sequentially extract the operation tasks from the operation task list and publish them on the device network, so that the devices in the warehouse can determine whether to claim the corresponding tasks according to the information of the operation tasks and the device's own conditions; each operation task can be claimed by multiple warehouse devices, and the best warehouse device is finally selected as the successfully claimed device;
[0143] The error processing unit 730 is used for, when a certain operation task cannot be released and an error is reported, if only less than one-third of the operation tasks in the inbound and outbound order to which the operation task belongs are claimed, it is considered that the inbound and outbound order cannot be completed, all the operation tasks contained in the inbound and outbound order are cleared, and a claim failure message is sent to the device that has claimed the task; if one-third to two-thirds of the operation tasks in the inbound and outbound order to which the operation task belongs are claimed, it is considered that the inbound and outbound order may be completed, all the operation tasks contained in the order are cleared, a claim failure message is sent to the device that has claimed the tasks in the order, and then the inbound and outbound order is re-issued. If the task release of the order reports an error again after the inbound and outbound order is re-issued, it is considered that the order cannot be completed; if more than two-thirds of the operation tasks in the inbound and outbound order to which the operation task belongs are claimed, it is considered that the inbound and outbound order should be completed, and the operation task is re-issued. If the operation task still reports an error after being re-issued twice, it is considered that the order cannot be completed, all the tasks contained in the order are cleared, and a claim failure message is sent to the device that has claimed the tasks in the order;
[0144] The task execution unit 740 is used to send a claim success mark to the warehouse equipment that claims the work task after all the work tasks in the inbound and outbound order have been claimed, so as to instruct each device to execute the claimed work task; at the same time, it receives the execution results of the claimed tasks fed back by each device. When it is detected that all the tasks in the inbound and outbound order have been claimed and executed by the device, the order is considered to have been executed.
[0145] The task claim judgment unit 750 is used to determine whether to claim the corresponding task based on the information of the job task and the device's own situation, specifically: S31, the equipment in the warehouse receives the job task published in the network, and determines whether it can execute the job task. If it cannot be executed, the job task is discarded and the step is transferred to step S33; if it can be executed, it enters step S32; S32, the device predicts the time point when the job task is completed, and writes the job task into the task list; the task information in the task list includes: task identification, task content, task status, predicted time point for completing the task, claim message sending time, claim message sending number of times, previous task execution device identification and next task execution device identification; the task status is set to unclaimed; S33, the device regularly checks the task list for tasks with unclaimed task status; S34, calculates the claim message sending of tasks with unclaimed task status The interval between the sending time and the current time, if the time interval is less than the sending time threshold, go to step S37; if the time interval is greater than or equal to the sending time threshold, go to step S35; S35, determine the number of times the claim message of the job task is sent, if the number of times it is sent is greater than the claim threshold, delete the job task from the task list, and go to step S37; if the number of times it is sent is not greater than the claim threshold, go to step S36; the claim threshold is related to the number of devices in the stereoscopic warehouse that can claim and execute the job task; S36, send the claim message of the job task, update the time and number of times the claim message is sent; the claim message includes: device identification, task identification, predicted task completion time point, and the number of tasks that the device has claimed but not completed; S37, determine whether the device is turned off, if the device is not turned off, go to step S33, if the device is turned off, the device will no longer claim and execute tasks.
[0146] Understandably, Figure 7 The detailed functional implementation of each unit in the method can be found in the introduction of the aforementioned method embodiment, which will not be repeated here.
[0147] It will be easily understood by those skilled in the art that the above description is only a preferred embodiment of the present invention and is not intended to limit the present invention. Any modifications, equivalent substitutions and improvements made within the spirit and principles of the present invention should be included in the protection scope of the present invention.
Claims
1. A method for scheduling job tasks in an automated warehouse, characterized in that: The steps include: Receive the inbound and outbound orders issued by the user, and establish an inbound and outbound operation task list according to the inbound and outbound orders; the operation task list includes multiple operation tasks, and the information of each operation task includes: task identification, task content, predicted completion time point, release time, release number, inbound and outbound order number, execution equipment type, execution equipment identification, task status, previous task identification and next task identification; the task content is a list of various movement locations and execution operation types passed by the equipment when executing the task, the previous task identification is the identification of the previous operation task that must be completed before executing the operation task in the inbound and outbound order to which the operation task belongs, and the next task identification is the identification of the next operation task that should be started after executing the operation task in the inbound and outbound order to which the operation task belongs; The job tasks are sequentially extracted from the job task list and published on the device network so that the devices in the warehouse can determine whether to claim the corresponding tasks based on the information of the job tasks and the device's own conditions; each job task can be claimed by multiple warehouse devices, and the best warehouse device is finally selected as the successfully claimed device; the devices in the warehouse determine whether to claim the corresponding tasks based on the information of the job tasks and the device's own conditions, specifically: S31, the device in the warehouse receives the job tasks published on the network, and determines whether it can execute the job tasks. If it cannot be executed, the job tasks are discarded and the process goes to step S33; if it can be executed, the process goes to step S32; S32, the device predicts the time point when the job task is completed, and writes the job task into the task list; the task information in the task list includes: task identification, task content, task status, predicted time point when the task is completed, claim message sending time, claim message sending number of times, previous task execution device identification and next task execution device identification; the task status is set to unclaimed; S 33. The device periodically checks the tasks in the task list whose task status is unclaimed; S34. Calculate the interval between the sending time of the claim message of the task status unclaimed and the current time. If the time interval is less than the sending time threshold, go to step S37; if the time interval is greater than or equal to the sending time threshold, go to step S35; S35. Determine the number of times the claim message of the task is sent. If the number of times is greater than the claim threshold, delete the task from the task list and go to step S37; if the number of times is not greater than the claim threshold, go to step S36; the claim threshold is related to the number of devices in the stereoscopic warehouse that can claim and execute the task; S36. Send the claim message of the task and update the sending time and number of the claim message; the claim message includes: device identification, task identification, predicted task completion time point, and the number of tasks that the device has claimed but not completed; S37. Determine whether the device is turned off. If the device is not turned off, go to step S33. If the device is turned off, the device will no longer claim and execute tasks; When a certain operation task cannot be released and an error is reported, if only less than one-third of the operation tasks in the inbound and outbound order to which the operation task belongs are claimed, it is considered that the inbound and outbound order cannot be completed, all the operation tasks contained in the inbound and outbound order are cleared, and a claim failure message is sent to the device that has claimed the task; if one-third to two-thirds of the operation tasks in the inbound and outbound order to which the operation task belongs are claimed, it is considered that the inbound and outbound order may be completed, all the operation tasks contained in the order are cleared, a claim failure message is sent to the device that has claimed the tasks in the order, and then the inbound and outbound order is re-issued. If the task release of the order reports an error again after the inbound and outbound order is re-issued, it is considered that the order cannot be completed; if more than two-thirds of the operation tasks in the inbound and outbound order to which the operation task belongs are claimed, it is considered that the inbound and outbound order should be completed, and the operation task is re-issued. If the operation task still reports an error after being re-issued twice, it is considered that the order cannot be completed, all the tasks contained in the order are cleared, and a claim failure message is sent to the device that has claimed the tasks in the order; When all the work tasks in the inbound and outbound orders are claimed, a claim success mark is sent to the warehouse equipment that claims the work tasks to instruct each device to execute the claimed work tasks.
2. The method according to claim 1, characterized in that The job tasks are sequentially extracted from the job task list and published on the device network, specifically: Regularly search the job task list to extract job tasks suitable for release; the job tasks suitable for release are: the task status of the current job task is unclaimed, and the task status of the previous job task is claimed; Determine the number of times the job task to be published is published, and if the number is less than the warning threshold, publish the job task on the device network; If the number is greater than or equal to the warning threshold but less than the error threshold, an alarm is first triggered to let the warehouse manager know that there is an abnormality in claiming the task, and then the task is published on the device network; If the number is greater than or equal to the error threshold, the job task will not be published and an error will be reported; when publishing the job task on the device network, the publishing time and number of publications will be updated; the warning threshold is related to the number of devices in the stereoscopic warehouse that can claim and execute the job task, and the error threshold is set to twice the warning threshold.
3. The method according to claim 1, characterized in that The equipment in the warehouse receives the job tasks published on the network and determines whether it can perform the job tasks, specifically: Warehouse equipment determines whether it can execute the published task based on the task content, the number of tasks that have been claimed but not completed, its own fault conditions, and the remaining power; If one of the following conditions is met, the equipment is considered unable to perform the task: the equipment cannot reach the starting, middle or end location specified in the task content; the equipment cannot complete the operation type specified in the task; the number of tasks that the equipment has claimed but not completed is more than twice the number of the same type of equipment in the warehouse; the equipment switches to manual control mode and cannot be automatically controlled by the central computer.
4. The method according to claim 1, characterized in that: When all the tasks are claimed, a claim success flag is sent to the warehouse device that claimed the task to instruct each device to execute the claimed task. Specifically: Regularly check the claim messages of received job tasks; Analyze the task claim message to determine the device that successfully claims the task; select the best warehouse device from the task claim messages of multiple devices that claim the task, as the warehouse device that successfully claims the task, and write the device ID into the execution device ID of the task list; if one or more of the following conditions are met, it is considered to be the best warehouse device: the warehouse device with the closest predicted completion time of the task; the first warehouse device to claim the task; the warehouse device with the least number of claimed but uncompleted tasks; Feedback a claim failure message to other warehouse devices that failed to claim the operation task; Determine whether the inbound and outbound orders to which the task belongs can be fully executed; If it cannot be fully executed, continue to check the received claim messages regularly; If it can be fully executed, the claiming devices of all the work tasks included in the inbound and outbound order are extracted, and a claim success message is fed back to each device; the claim success message includes: task ID, device ID, previous task execution device ID and next task execution device ID.
5. The method according to claim 4, characterized in that Determine whether the inbound and outbound orders to which the task belongs can be fully executed, specifically: Retrieve the job task information in the job task list. If the next job task of the job task is marked as None, it means that the job task is the last task in the inbound and outbound order. When the task is claimed, all the job tasks in the inbound and outbound order have been claimed, indicating that the inbound and outbound order can be fully executed. Otherwise, it is considered that the inbound and outbound order cannot be fully executed.
6. The method according to claim 5, characterized in that The following steps are also included: the warehouse equipment executes the task and publishes the task execution result on the equipment network, specifically: S51, the device receives a task claim message and determines the status of the claim message; S52, if the claim is successful, modify the task status in the task list to "claimed", and then go to step S54; S53, if the claim fails, delete the task from the task list and go to step S58; S54, the device periodically checks whether the task can be started. If not, go to step S58; if it can be started, go to step S55; the condition for starting the task is: the device has received the completion message sent by the previous task execution device of the task, and the task is the first task in the task list with the status of claimed; S55, the device executes the task, changes the task status in the task list to start, and sends a start execution message to the central computer; S56: The device completes the task and deletes the task from the task list; S57, the device sends a message of completion of execution to the central computer, and at the same time sends a message of completion of execution to the next task execution device of the task; S58, determine whether the device is turned off, if not, go to step S51.
7. An automated warehouse task scheduling system, characterized in that: include: An order receiving unit is used to receive the inbound and outbound orders issued by the user, and to establish an inbound and outbound operation task list according to the inbound and outbound orders; The job task list includes multiple job tasks, and the information of each job task includes: task identification, task content, predicted completion time point, release time, release number, corresponding inbound and outbound order number, execution equipment type, execution equipment identification, task status, previous task identification, and next task identification; the task content is a list of various movement locations and execution operation types that the equipment passes through when executing the task, the previous task identification is the identification of the previous job task that must be completed before executing the job task in the inbound and outbound order to which the job task belongs, and the next task identification is the identification of the next job task that should be started after executing the job task in the inbound and outbound order to which the job task belongs; The task publishing unit is used to sequentially extract the job tasks from the job task list and publish them on the device network, so that the devices in the warehouse can determine whether to claim the corresponding tasks based on the information of the job tasks and the device's own conditions; each job task can be claimed by multiple warehouse devices, and the best warehouse device is finally selected as the successfully claimed device; the task claim judgment unit is used to determine whether to claim the corresponding task based on the information of the job task and the device's own conditions, and specifically includes the following steps: S31, the device in the warehouse receives the job task published in the network, and determines whether it can execute the job task. If it cannot be executed, the job task is discarded and the process goes to step S33; if it can be executed, the process goes to step S32; S32, the device predicts the time point when the job task is completed, and writes the job task into the task list; the task information in the task list includes: task identifier, task content, task status, predicted time point when the task is completed, claim message sending time, claim message sending number of times, previous task execution device identifier and next task execution device identifier; the task The status is set to unclaimed; S33, the device periodically checks the tasks in the task list with unclaimed status; S34, calculates the interval between the sending time of the claim message of the task status unclaimed and the current time, if the time interval is less than the sending time threshold, go to step S37; if the time interval is greater than or equal to the sending time threshold, go to step S35; S35, determine the number of times the claim message of the job task is sent, if the number of times is greater than the claim threshold, delete the job task from the task list, go to step S37; if the number of times is not greater than the claim threshold, go to step S36; the claim threshold is related to the number of devices in the stereoscopic warehouse that can claim and execute the job task; S36, send the claim message of the job task, update the sending time and number of the claim message; the claim message includes: device identification, task identification, predicted task completion time point, and the number of tasks that the device has claimed but not completed; S37, determine whether the device is turned off, if the device is not turned off, go to step S33, if the device is turned off, the device will no longer claim and execute tasks; An error processing unit is used for, when a certain operation task cannot be released and an error is reported, if only less than one-third of the operation tasks in the inbound and outbound order to which the operation task belongs are claimed, it is considered that the inbound and outbound order cannot be completed, all the operation tasks contained in the inbound and outbound order are cleared, and a claim failure message is sent to the device that has claimed the task; if one-third to two-thirds of the operation tasks in the inbound and outbound order to which the operation task belongs are claimed, it is considered that the inbound and outbound order may be completed, all the operation tasks contained in the order are cleared, a claim failure message is sent to the device that has claimed the tasks in the order, and then the inbound and outbound order is re-issued. If the task release of the order reports an error again after the inbound and outbound order is re-issued, it is considered that the order cannot be completed; if more than two-thirds of the operation tasks in the inbound and outbound order to which the operation task belongs are claimed, it is considered that the inbound and outbound order should be completed, and the operation task is re-issued. If the operation task still reports an error after being re-issued twice, it is considered that the order cannot be completed, all the tasks contained in the order are cleared, and a claim failure message is sent to the device that has claimed the tasks in the order; The task execution unit is used to send a claim success mark to the warehouse equipment that claims the work task after all the work tasks in the inbound and outbound orders have been claimed, so as to instruct each device to execute the claimed work task; at the same time, it receives the execution results of the claimed tasks fed back by each device. When it is detected that all the tasks in the inbound and outbound orders have been claimed and executed by the equipment, the order is considered to have been executed.
8. The system according to claim 7, characterized in that The task publishing unit periodically searches the job task list to extract job tasks suitable for publishing; the job tasks suitable for publishing are: the task status of the current job task is unclaimed, and the task status of the previous job task is claimed; and determines the number of times the job task to be published is published, and if the number is less than a warning threshold, publishes the job task on the device network; If the number is greater than or equal to the warning threshold but less than the error threshold, an alarm is first triggered to let the warehouse manager know that there is an abnormality in claiming the task, and then the task is published on the device network; If the number is greater than or equal to the error threshold, the job task will not be published and an error will be reported; when publishing the job task on the device network, the publishing time and number of publications will be updated; the warning threshold is related to the number of devices in the stereoscopic warehouse that can claim and execute the job task, and the error threshold is set to twice the warning threshold.
