Exception handling method and device, equipment, storage medium and program product

Abstract

The embodiment of the invention relates to an exception handling method and device, equipment, a storage medium and a program product. The method comprises the following steps: acquiring operation exception information associated with a logistics task of a target object, wherein the operation exception information comprises the type of the logistics task and an indication of an exception state; determining a pick-up state of the target object based on the indication of the abnormal state, wherein the pick-up state at least indicates whether the target object is correctly picked up to a mobile device for bearing the target object; and executing processing for the abnormal state at least based on the task type and the pickup state. Therefore, when the equipment fails or the logistics task is abnormal, the problem can be automatically identified and timely processed, so that the intelligent level and the operation efficiency of the whole logistics system are improved.

Description

Technical Field

[0001] Example embodiments of the present disclosure generally relate to the field of computer technology, and more particularly, to methods, apparatuses, electronic devices, computer-readable storage media, and computer program products for exception handling. Background Art

[0002] With the development of intelligent warehousing and automated logistics technologies, more and more warehousing management systems and automated devices are widely used in various logistics scenarios. These systems require efficient task scheduling and management mechanisms to ensure the smooth execution of various logistics tasks such as outbound and inbound operations, and to improve the overall operational efficiency of the warehouse.

[0003] In related technologies, due to the complexity of the warehousing environment, problems such as equipment anomalies, task conflicts, and inventory status anomalies may affect the normal execution of logistics tasks, resulting in abnormal interruptions of logistics tasks. Therefore, how to handle exceptions in logistics tasks and efficiently manage the execution of tasks is an issue worthy of attention. Summary of the Invention

[0004] In a first aspect of the present disclosure, a method for exception handling is provided. The method includes: obtaining operation exception information associated with a logistics task of a target object, the operation exception information including the type of the logistics task and an indication of an exception status; determining a pick-up status of the target object based on the indication of the exception status, the pick-up status at least indicating whether the target object has been correctly picked up onto a movable device for carrying the target object; and performing processing for the exception status based at least on the task type and the pick-up status.

[0005] In a second aspect of the present disclosure, an apparatus for exception handling is provided. The apparatus includes: an obtaining module configured to obtain operation exception information associated with a logistics task of a target object, the operation exception information including the type of the logistics task and an indication of an exception status; a status determination module configured to determine a pick-up status of the target object based on the indication of the exception status, the pick-up status at least indicating whether the target object has been correctly picked up onto a movable device for carrying the target object; and an execution module configured to perform processing for the exception status based at least on the task type and the pick-up status.

[0006] In a third aspect of the present disclosure, an electronic device is provided. The device includes at least one processing unit; and at least one memory coupled to the at least one processing unit and storing instructions for execution by the at least one processing unit. The instructions, when executed by the at least one processing unit, cause the electronic device to perform the method of the first aspect.

[0007] In a fourth aspect of the present disclosure, a computer-readable storage medium is provided. A computer program is stored on the medium, and when the computer program is executed by a processor, the method of the first aspect is implemented.

[0008] In a fifth aspect of the present disclosure, a computer program product is provided. The product includes a computer program, and when the computer program is executed by a processor, the method according to the first aspect of the present disclosure is implemented.

[0009] It should be understood that the content described in this part is not intended to define the key features or important features of the embodiments of the present disclosure, nor is it used to limit the scope of the present disclosure. Other features of the present disclosure will become easily understood through the following description. BRIEF DESCRIPTION OF THE DRAWINGS

[0010] In the following, in combination with the drawings and with reference to the following detailed description, the above and other features, advantages and aspects of the various implementations of the present disclosure will become more apparent. In the drawings, the same or similar reference numerals denote the same or similar elements, where:

[0011] Figure 1 A schematic diagram showing an example environment in which the embodiments of the present disclosure can be implemented;

[0012] Figure 2 A flowchart showing an example process of exception handling according to some embodiments of the present disclosure;

[0013] Figure 3A A schematic diagram showing a scenario of executing a logistics task according to some embodiments of the present disclosure;

[0014] Figure 3B A schematic diagram showing a process of exception handling for an outbound task according to some embodiments of the present disclosure;

[0015] Figure 3C A schematic diagram showing a process of exception handling for a return-to-warehouse task according to some embodiments of the present disclosure;

[0016] Figure 3D A schematic diagram showing a process of exception handling for an operation task according to some embodiments of the present disclosure;

[0017] Figure 4 A schematic structural block diagram showing a device for exception handling according to certain embodiments of the present disclosure; and

[0018] Figure 5 A block diagram showing a computing device in which one or more embodiments of the present disclosure can be implemented. DETAILED DESCRIPTION OF THE EMBODIMENTS

[0019] Embodiments of the present disclosure will be described in more detail below with reference to the accompanying drawings. Although some embodiments of the present disclosure are shown in the drawings, it should be understood that the present disclosure can be implemented in various forms and should not be construed as limited to the embodiments set forth herein. On the contrary, these embodiments are provided to more thoroughly and completely understand the present disclosure. It should be understood that the drawings and embodiments of the present disclosure are only for exemplary purposes and are not used to limit the protection scope of the present disclosure.

[0020] In the description of the embodiments of the present disclosure, the term "including" and its similar terms should be understood as open inclusion, that is, "including but not limited to". The term "based on" should be understood as "at least partially based on". The term "an embodiment" or "the embodiment" should be understood as "at least one embodiment". The term "some embodiments" should be understood as "at least some embodiments". There may also be other explicit and implicit definitions hereinafter.

[0021] It should be noted that in the technical solution of the present disclosure, the acquisition, storage, and application of the user's personal information involved all comply with the provisions of relevant laws and regulations and do not violate public order and good customs.

[0022] It can be understood that before using the technical solutions disclosed in the embodiments of the present disclosure, the types, usage scopes, usage scenarios, etc. of the personal information involved in the present disclosure should be informed to the user and the user's authorization should be obtained in an appropriate manner according to relevant laws and regulations.

[0023] For example, when receiving the user's active request, a prompt message is sent to the user to clearly prompt the user that the operation requested by the user will require obtaining and using the user's personal information, so that the user can autonomously choose whether to provide personal information to software or hardware such as an electronic device, an application program, a server, or a storage medium that performs the operation of the technical solution of the present disclosure according to the prompt message.

[0024] As an optional but non-limiting implementation manner, the manner of sending a prompt message to the user in response to receiving the user's active request may be, for example, in the form of a pop-up window, and the prompt message may be presented in text in the pop-up window. In addition, the pop-up window may also carry a selection control for the user to choose "agree" or "disagree" to provide personal information to the electronic device.

[0025] It can be understood that the above process of notifying and obtaining the user's authorization is only illustrative and does not limit the embodiments of the present disclosure. Other methods that meet relevant laws and regulations can also be applied to the embodiments of the present disclosure.

[0026] As used herein, the term "model" can learn the corresponding association between inputs and outputs from training data, so that after training, for a given input, the corresponding output can be generated. The generation of the model can be based on machine learning techniques. Deep learning is a machine learning algorithm that processes inputs and provides corresponding outputs by using multiple layers of processing units. A neural network model is an example of a model based on deep learning. In this document, "model" can also be referred to as "machine learning model", "learning model", "machine learning network" or "learning network", and these terms are used interchangeably herein.

[0027] A "neural network" is a machine learning network based on deep learning. A neural network can process inputs and provide corresponding outputs, and it generally includes an input layer and an output layer, as well as one or more hidden layers between the input layer and the output layer. Neural networks used in deep learning applications usually include many hidden layers, thus increasing the depth of the network. The layers of the neural network are connected in sequence, so that the output of the previous layer is provided as the input of the next layer, where the input layer receives the input of the neural network, and the output of the output layer is the final output of the neural network. Each layer of the neural network includes one or more nodes (also called processing nodes or neurons), and each node processes the input from the previous layer.

[0028] As briefly mentioned above, in modern logistics and warehousing management, automated warehousing and logistics systems have become an important means to improve logistics efficiency and optimize inventory management. With the development of e-commerce, supply chain optimization, and intelligent manufacturing, the operational requirements of warehouses are increasing day by day, and enterprises are increasingly relying on automated equipment to complete tasks such as goods storage, sorting, and handling. Compared with traditional logistics models, automated systems can improve storage and retrieval efficiency, reduce labor costs, and reduce the risk of errors caused by human operations. However, during the execution of logistics tasks, some logistics tasks may not be executed normally due to equipment failures, scheduling conflicts, or other abnormalities, thus affecting the overall logistics efficiency.

[0029] In the current logistics and warehousing system, when a device fails, the usual operation process is for on-site personnel to take the device offline and tow it to the maintenance area for inspection. After the device is repaired, it is put back online to resume the previously interrupted tasks. However, if the device is carrying target objects to be processed when the failure occurs, then the logistics tasks of these target objects will be delayed. Due to the uncertainty of the repair time, these delayed tasks cannot be processed in a timely manner and can only wait until the device is repaired and returns to the normal operating state before continuing to execute. And if the target objects carried on the device in the abnormal state are the only copies of a certain inventory, then this abnormality can affect subsequent outbound orders.

[0030] In addition, a faulty device not only interrupts the task it is performing but also occupies storage resources such as corresponding cache bits and slots. These occupied resources cannot be used by other tasks, resulting in a waste of resources. At the same time, since the interrupted tasks of the faulty device cannot be completed in a timely manner, it also affects the normal operation of other tasks, thereby reducing the efficiency of the entire logistics and warehousing system.

[0031] Therefore, in order to address issues such as insufficient efficiency faced by related technologies in exception handling, a more efficient solution for exception handling is needed.

[0032] In an embodiment of the present disclosure, a solution for exception handling is provided. According to an embodiment of the present disclosure, operation exception information associated with a logistics task of a target object is obtained, and the operation exception information includes the type of the logistics task and an indication of the exception status; the picking status of the target object is determined based on the indication of the exception status, and the picking status at least indicates whether the target object has been correctly picked up onto a movable device for carrying the target object; and a process for the exception status is executed based at least on the task type and the picking status.

[0033] Thus, by obtaining operation exception information associated with a logistics task of a target object and accurately identifying various exception statuses in the logistics process, various exception handling measures can be flexibly taken to effectively respond to various exceptions and reduce the impact on logistics tasks. In addition, by automatically closing the loop of data after an exception is determined, the occupied storage resources are released in a timely manner, optimizing resource utilization, and providing strong support for the stable operation and efficient management of the logistics and warehousing system.

[0034] Figure 1 FIG. shows a schematic diagram of an exemplary environment 100 in which embodiments of the present disclosure can be implemented. As Figure 1 shown, the exemplary environment 100 may include an electronic device 110. An application 120 that can run on the electronic device 110. The application 120 can be any suitable type of application related to logistics tasks, and examples thereof may include, but are not limited to: a logistics management platform, a Warehouse Management System (WMS), and other suitable types of applications. Embodiments of the present disclosure are not limited in this regard. The user 140 can interact with the application 120 via the electronic device 110 and / or its attached devices.

[0035] In the exemplary environment 100, if the application 120 is in an active state, the electronic device 110 can present an interface 150 of the application 120. Via the corresponding interface 150, the application 120 can provide various user interfaces related to logistics tasks to the user 140.

[0036] In some embodiments, the electronic device 110 communicates with the server 130 to implement the supply of services for the application 120. The electronic device 110 can be any type of mobile terminal, fixed terminal or portable terminal, including mobile phones, desktop computers, laptop computers, notebook computers, netbook computers, tablet computers, media computers, multimedia tablets, palmtop computers, portable game terminals, VR / AR devices, Personal Communication System (PCS) devices, personal navigation devices, Personal Digital Assistant (PDA), audio / video players, digital cameras / video cameras, positioning devices, television receivers, radio broadcast receivers, e-book devices, game devices, or any combination of the foregoing, including accessories and peripherals of these devices or any combination thereof. In some embodiments, the electronic device 110 can also support any type of user interface (such as a "wearable" circuit, etc.).

[0037] The server 130 can be an independent physical server, or a server cluster or distributed system composed of multiple physical servers, or a cloud server that provides basic cloud computing services such as cloud services, cloud databases, cloud computing, cloud functions, cloud storage, network services, cloud communications, middleware services, domain name services, security services, content delivery networks, and big data and artificial intelligence platforms. The server 130 can include, for example, a computing system / server, such as a mainframe, an edge computing node, a computing device in a cloud environment, and so on. The server 130 can provide back-end services for the application 120 that supports content presentation in the electronic device 110.

[0038] It should be understood that the structures and functions of the various elements in the environment 100 are described only for exemplary purposes, without implying any limitation on the scope of the present disclosure.

[0039] Figure 2 A schematic diagram of an example process 200 for exception handling according to some embodiments of the present disclosure is shown. The process 200 can be implemented in the environment 100. For example, the process 200 can be implemented at the electronic device 110. Hereinafter, for the convenience of discussion, reference will be made to Figure 1 to describe the process 200.

[0040] In block 210, the electronic device 110 obtains operation exception information associated with the logistics task of the target object. The target object refers to the specific items (such as goods, cargo, etc.) involved in the logistics task or the containers (such as cargo boxes, pallets, etc.) used to carry the items. In the logistics task, operations such as access, handling, and inventory taking need to be performed on these target objects.

[0041] In some embodiments, the electronic device 110 may monitor the execution of the logistics task in real time. If an abnormality occurs (such as equipment failure, picking the wrong target object, missing target object, etc.), the electronic device 110 may obtain and record relevant operation abnormality information.

[0042] In some embodiments, the operation abnormality information includes the type of the logistics task. The task type includes one of the following: a task of moving a target object from a target location to a storage location, a task of sending the target object back from the storage location to the target location, and a task of operating on the target object at the target location. Alternatively or additionally, the operation abnormality information further includes an abnormality status indication (such as equipment failure, failure to successfully pick up goods, unavailable storage resources, etc.).

[0043] In some embodiments, the status of the target object is an important basis for logistics management and task execution. Different statuses reflect the position of the target object in the logistics task, the task execution situation, and the abnormality handling status. For example, the status of the target object may include statuses such as abnormality, in the process of outbound, in the process of returning to the warehouse, and shelved. The abnormality status means that the target object is locked due to some abnormal situation and cannot continue to execute the current task. The in the process of outbound status means that the target object is in the process of executing the task of moving the target object from the target location to the storage location. The in the process of returning to the warehouse status means that the target object is in the process of executing the task of sending the target object back from the storage location to the target location. The shelved status means that the target object has been stored in the target location and is in a long-term storage state.

[0044] In block 220, the electronic device 110 determines the picking status of the target object based on the indication of the abnormality status. The picking status at least indicates whether the target object has been correctly picked up onto the movable device for carrying the target object.

[0045] The picking status at least indicates whether the target object (such as goods, containers, etc.) has been correctly taken out and placed on the movable device for handling. The picking status may include the status of being correctly picked up, indicating that the target object has been successfully picked up by the movable device and is in the carrying device (such as a basket) of the device. Alternatively or additionally, the picking status may further include not being correctly picked up, indicating that the target object has not been picked up or an error occurred during the picking process.

[0046] In block 230, the electronic device 110 performs processing for the abnormality status based at least on the task type and the picking status.

[0047] As an example, Figure 3A shows a schematic diagram of a scenario 300 for executing a logistics task according to some embodiments of the present disclosure. Referring to Figure 3A, in scenario 300, it includes a movable device, a business personnel, a target object, and storage resources. The movable device (such as an automated storage and retrieval device, a transport robot, etc.) is responsible for transporting the target object (such as a container or goods) within scenario 300. These devices can move automatically or semi-automatically between different areas of scenario 300 to perform various types of logistics tasks.

[0048] Continuing to refer to Figure 3A , the storage resources include multiple different areas, which mainly include a target location and a storage location. The target location (such as warehouse storage location 301) is the final storage location of the target object. For example, the target location can be a high-level storage location in the warehouse for long-term storage of the target object. The storage location (such as warehouse staging location 302) is a temporary storage area for the target object during the handling process. The storage location may be located on the lower level or the ground level of the warehouse for temporarily storing the target object to be processed.

[0049] In some embodiments, the electronic device 110 can record the status of the target location and the storage location respectively, which is used to describe the usage of the storage resources in the logistics task, ensure the correct management of inventory, allocation of storage space during task execution, and enable efficient adjustment in case of task anomalies.

[0050] Exemplarily, the status of the target location and the storage location can be divided into four states: pre-occupied, occupied, pre-released, and idle. The pre-occupied state indicates that a certain storage resource is about to be used, but the target object has not been placed yet. The occupied state indicates that the target object has been placed in this storage resource, and this storage resource is in use and cannot be reallocated to other tasks. The pre-released state indicates that a certain storage resource is about to be emptied, the target object is still in this location, but a new task has been assigned and is about to use this storage resource. The idle state indicates that this storage resource is not occupied and can be allocated to new tasks.

[0051] In some embodiments, the status of the target location can change according to different tasks. For example, in the task of moving the target object from the target location to the storage location, the status of the target location may change from occupied to pre-released. The status of the storage location can also change according to different tasks. For example, in the task of moving the target object from the target location to the storage location, the status of the storage location may change from idle to pre-occupied.

[0052] In some embodiments, the task type includes one of the following: the task of moving the target object from the target location to the storage location, which can also be understood as an outbound task, that is, taking out the target object from the formal storage area and temporarily storing or transporting it to a new location for subsequent operations.

[0053] As an example, Figure 3B shows a schematic diagram of the exception handling process of the outbound task 310 according to some embodiments of the present disclosure.

[0054] Reference Figure 3B Figure 3B , the type of task 310 is a task of moving a target object from a target location to a storage location (such as an outbound task). The electronic device 110 determines that an exception occurs when executing task 310. If it is determined based on the indication of the exception status that the device is in an abnormal state and the picking status indicates that the target object has not been picked up, the electronic device 110 may execute block 311 and attempt to replace the movable device that executes task 310.

[0055] In some embodiments, the electronic device 110 determines whether there is another movable device at the target location. If it is determined that there is another movable device, the logistics task is assigned to the other movable device.

[0056] As an example, the electronic device 110 determines that an exception occurs when executing an outbound task. The exception is that the current movable device (such as an automated storage and retrieval device) fails and cannot execute the picking task, and the picking status indicates that the target object has not been picked up yet. In this case, the electronic device 110 may check whether there is any other available movable device at the target location (for example, the current lane corresponding to the warehouse storage location). If there is an available device, the electronic device 110 may cancel the task of the original faulty device and transfer the logistics task to the new device, and the new device completes the outbound task.

[0057] In some embodiments, if the electronic device 110 determines that there is no other movable device, the logistics task of the original faulty device may be cancelled. Then, the electronic device 110 may update the target location to an occupied state, indicating that the target object is still stored in the original storage location. The electronic device 110 may update the storage location to an idle state, indicating that the target object has not been moved to the temporary storage location.

[0058] As an example, if there is no other available device in the current lane corresponding to the warehouse storage location and the electronic device 110 cannot replace the device, it is necessary to cancel the abnormal task and adjust the inventory status. Specifically, the electronic device 110 updates the status of the target object from being in the process of outbound handling to being shelved. The target object is no longer in the process of outbound handling but has returned to the warehouse storage location and is in a long-term storage state. The electronic device 110 may also change the status of the target location from pre-released to occupied, indicating that the target object is still on the storage location. And if the target object has been assigned a corresponding storage location (temporary storage location), the electronic device 110 may restore the status of the storage location from pre-occupied to idle.

[0059] In addition, in the outbound task, the electronic device 110 may pre-occupy storage resources (i.e., lock the inventory) to ensure that it will not be occupied by other tasks. Due to the interruption of the task, the electronic device 110 needs to release this part of the pre-occupied inventory and reduce the amount of inventory pre-occupation (Inventory pre-occupation quantity = Original inventory pre-occupation quantity - Task pre-occupation quantity).

[0060] In some embodiments, after canceling the logistics task of the original movable device, in order to avoid affecting the normal outbound of the target object and further affecting the order status, the electronic device 110 may determine whether there is another target location storing the target object. If the electronic device 110 determines that the target object is stored at the other target location, it may generate a logistics task to move the target object out of the other target location.

[0061] As an example, after canceling the logistics task of the original movable device, the electronic device 110 may attempt to reposition the task and search for other available target objects (such as target goods). For example, the electronic device 110 searches whether the target goods required for the task are included in other aisles. If there are other available target goods, the electronic device 110 may select the most suitable target goods and the target location storing the goods according to a preset positioning algorithm, and generate a new outbound task. If there is only one such target good in the inventory, the electronic device 110 may wait for the device to be repaired and reposition, and generate a corresponding outbound task.

[0062] In the embodiments of the present disclosure, by updating the status of the storage resources in a timely manner after canceling the logistics task of the original movable device and maintaining the accuracy of the inventory data, the utilization rate of the storage resources can be improved, ensuring that other tasks can be executed smoothly. In addition, by generating a repositioning task, that is, by attempting to find similar inventories at other locations or re-planning the execution of the task, the order fulfillment ability can be improved, and task delays or backlogs caused by exceptions can be reduced.

[0063] Return reference Figure 3B , if it is determined based on the indication of the abnormal state that the device is in an abnormal state and the pick-up state indicates that the target object has been picked up, the electronic device 110 may execute block 312, and the electronic device 110 simulates that the target object has arrived.

[0064] When the electronic device 110 detects that the device is in an abnormal state, but the target object (such as a container, goods, etc.) has been picked up, at this time, the electronic device 110 may simulate the arrival state of the target object in order to maintain the continuity of the logistics process. The core of this strategy is to complete the subsequent logistics tasks through manual intervention to avoid the target object being lost or staying on the faulty device due to device abnormalities. The main processing logic is as follows:

[0065] In some embodiments, the electronic device 110 generates an artificial logistics task to move the target object from the movable device to the storage location. In response to determining that the target object has been moved to the storage location, the storage location is updated to an occupied state.

[0066] As an example, if the electronic device 110 determines that there is a device anomaly and the target object has been picked up from the target location (warehouse location) and brought into the device but not placed in the storage location (temporary storage location), due to the device failure, the electronic device 110 generates an artificial logistics task instructing the operator to place the physical box at the temporary storage location designated by the task. Then, the electronic device 110 marks this task as having reached the temporary storage location to simulate the normal logistics process and updates the status of the temporary storage location to the occupied status to ensure that the storage information in the system remains synchronized.

[0067] As another example, if the electronic device 110 determines that there is a device anomaly and the target object has been placed from the target location (warehouse location) into the storage location (temporary storage location), the electronic device 110 can check the status of this logistics task in the application 120 (such as in the system console). If the status of the task in the console is unfinished, the electronic device 110 simulates that the target object has arrived, updates the task to the completed status, and updates the status of the storage location to the occupied status. If the status of the task in the console is completed, since the subsequent operations have been completed, the electronic device 110 does not require additional processing.

[0068] Return reference Figure 3B , if it is determined that the pick-up status indicates that there is no target object at the target location, the electronic device 110 can execute block 313 to generate an artificial wiring task. Specifically, the electronic device 110 updates the target location and the storage location to the idle status and the target object to the abnormal status. When the electronic device 110 detects that there is no target object at the target location (i.e., the situation of an empty box anomaly), it is necessary to promptly adjust the storage status and reallocate tasks to avoid inventory management chaos, thereby ensuring the correctness of subsequent operations. The main processing logic includes: since the target object is not found, the electronic device 110 needs to update the status of the target location and the storage location, avoid occupying invalid storage space, and set the unfound container to the abnormal locked status to prevent subsequent tasks from scheduling this container.

[0069] As an example, when the movable device attempts to pick up the target object from the target location and finds that the target location is empty, resulting in a task anomaly, the electronic device 110 updates the status of the target location (original storage location) and the storage location (target temporary storage location) to the idle status, allowing other target objects to be stored at this location. The status of the target object (such as the target container) is updated to the abnormal status and locked to prevent it from being continuously called by other tasks. In addition, the electronic device 110 can also revoke the inventory preoccupation (subtract the preoccupation quantity corresponding to this abnormal logistics task from the quantity of the storage resources originally preoccupied in the system) to adjust the inventory data and avoid affecting the execution of other normal tasks due to incorrect inventory calculations.

[0070] In some embodiments, if it is determined that the pick-up status indicates that a target object is stored at another target location, the electronic device 110 may generate a logistics task to move the target object from the other target location to the storage location.

[0071] Similarly, the electronic device 110 may also search for other inventories of the same target object according to a predetermined positioning algorithm and generate a new material task. If there is no other inventory, the electronic device 110 will backlog the task and wait to re-execute the outbound task after finding the target object. After finding the target object, a return-to-warehouse task needs to be executed, that is, arranging equipment or personnel to put the container back to the appropriate storage location to ensure accurate inventory data. For example, the electronic device 110 generates a manual line-placement task, that is, instructing the operator to manually place the found container on the conveyor line (line-placement), and the conveyor system or the movable device will send it back to the target location to complete the return-to-warehouse operation.

[0072] Return reference Figure 3B , if it is determined that the pick-up status indicates that the first object picked up by the movable device is not the target object, the electronic device 110 may execute block 313 to generate a manual line-placement task. If it is found that the object picked up by the movable device is not the target object, the storage information needs to be adjusted to correct the association relationship between the mis-picked object and the storage location. Specifically, the electronic device 110 associates the first object with the target location. Then, the electronic device 110 updates the original location corresponding to the first object before the association to the idle state.

[0073] As an example, the logistics task indicates that the target object to be taken out is C_b, and its corresponding target location is L_0. However, the object actually taken out by the movable device is the first object C_a, indicating that C_a was mis-stored at L_0, and the target object C_b is not at L_0. At this time, the electronic device 110 can update the storage information to ensure that it matches the actual situation and re-arrange the logistics task of the target object C_b.

[0074] The specific processing steps are as follows. If the electronic device 110 determines that the first object C_a is in the shelved state, it means that it was mis-placed at the target location L_0, and there is an error in the storage location L_1 recorded for the C_a object in the storage information. In this case, the electronic device 110 unbinds the association between C_a and L_1 and updates L_1 to "idle" for subsequent storage of other objects. Then, the electronic device 110 updates the relationship between C_a and L_0 to make the system record consistent with the actual storage situation and ensure that no errors occur during subsequent queries and task processing. If the status of C_a is an abnormal state or in the process of returning to the warehouse, it means that the status of C_a recorded in the storage information is the state of not being moved to the target location, and it needs to be updated to the shelved state, and the first object C_a is associated with the target location L_0.

[0075] Further, after correcting the association relationship between the first object and the storage location, the electronic device 110 cancels the logistics task of the target object C_b and releases the storage resources corresponding to C_b for subsequent task scheduling. Alternatively or additionally, in order not to affect normal outbound, the electronic device 110 determines whether another target location stores the target object. If it is determined that another target location stores the target object, the electronic device 110 generates a logistics task to move the target object from the other target location to the storage location.

[0076] Similarly to the foregoing, the electronic device 110 can search for other inventories of the same target object according to a predetermined positioning algorithm and generate a new material task. If there is no other inventory, the electronic device 110 backlogs the task and waits to re-execute the outbound task after finding the target object. After finding the target object, a return-to-warehouse task needs to be executed, that is, arranging equipment or labor to put the container back to the appropriate storage location to ensure accurate inventory data. For example, the electronic device 110 generates a manual line-placement task, that is, instructing the operator to manually place the found container on the conveyor line (line-placement), and the conveyor system or the movable device sends it back to the target location to complete the return-to-warehouse operation.

[0077] In some embodiments, the task type includes one of the following: a task of sending the target object from the storage location back to the target location, which can also be understood as a return-to-warehouse task, that is, sending the target object from the temporary storage area or other temporary storage locations back to the formal storage area for subsequent access or inventory management.

[0078] As an example, Figure 3C shows a schematic diagram of the exception handling process of the return-to-warehouse task 320 according to some embodiments of the present disclosure.

[0079] Refer to Figure 3C , the type of the task 320 is a task of sending the target object from the storage location back to the target location (such as a return-to-warehouse task). The electronic device 110 determines that an exception occurs when executing the task 320. If it is determined based on the indication of the exception status that the device is in an abnormal state and the pick-up status indicates that the target object has not been picked up, the electronic device 110 can execute block 321 and attempt to replace the movable device executing the task 320.

[0080] In some embodiments, the electronic device 110 determines whether there is another movable device at the target location. If it is determined that there is another movable device, the logistics task is assigned to the other movable device.

[0081] As an example, the electronic device 110 determines that an exception occurs when performing the task of returning to the warehouse. The exception is that the current movable device (such as an automated storage and retrieval device) fails and cannot perform the picking task, and the picking status indicates that the target object has not been picked up yet. In this case, the electronic device 110 can check whether there is any other available movable device at the target location (for example, the current aisle corresponding to the warehouse storage location). If there is an available device, the electronic device 110 can cancel the task of the original faulty device and transfer the logistics task to the new device, and the new device completes the task of returning to the warehouse.

[0082] In some embodiments, if the electronic device 110 determines that there is no other movable device, it can cancel the logistics task of the original faulty device. Then, the electronic device 110 updates the storage location to the occupied state and the target location to the idle state.

[0083] As an example, the electronic device 110 determines that the movable device (such as an automated storage and retrieval device) responsible for performing the original logistics task fails and there is no standby device available to take over the task. The electronic device 110 can cancel the current task to avoid task suspension from affecting subsequent operations. Since the task of returning to the warehouse has been cancelled, the target location (warehouse storage location) originally planned to store is no longer needed to be reserved and the storage location (temporary storage location) about to be released is revoked and released. The electronic device 110 updates the status of the target location to idle, which can be used for other tasks, and updates the status of the storage location to occupied to avoid misallocation. The electronic device 110 can update the status of the target object to shelved, indicating that the target object is still available. Even if it is not officially placed back in the target location, it can be used for the relocation task and outbound of the same type of object.

[0084] Furthermore, when the faulty device resumes operation after being repaired, if the target object is still at the temporary storage location and is idle, the electronic device 110 generates a new task of returning to the warehouse to ensure its final return to the place. If the target object has been used for other logistics tasks (such as outbound), there is no need to perform the task of returning to the warehouse.

[0085] Return reference Figure 3C , if it is determined based on the indication of the abnormal state that the device is in an abnormal state and the picking status indicates that the target object has been picked up and has not been moved to the storage location, the electronic device 110 can execute block 322 to generate an artificial logistics task of moving the target object from the movable device to the storage location, thereby instructing the operator to manually place the target object into the storage location. If it is determined that there is no storage location in the idle state, the electronic device 110 can generate an artificial logistics task of sending the target object from the movable device back to the target location, instructing the operator to send the target object back to the target location (or throwing the target object onto the conveyor line, and after the conveyor line detects the target object, the target object is sent back to the target location through the movable device), ensuring the correctness of the storage information and avoiding affecting subsequent operations due to task backlog.

[0086] If it is determined that the target object has been moved to the storage location, the electronic device 110 may execute block 323 to simulate that the target object has arrived, that is, it can be determined that the device handling task has been completed. Specifically, the electronic device 110 may update the storage location to an occupied state and the target location to an idle state, making it available for other tasks.

[0087] In the embodiments of the present disclosure, since the purpose of the return task is to send the target object (such as a container) from the staging location back to the target location (storage location). When the return task is suspended due to a device failure, it may cause the target object to be in the state of being in the return process, resulting in the system being unable to correctly locate the position of the target object, thus affecting the execution of other tasks (such as tasks that need to pick up the same type of target object from another location). By preferentially placing the target object with an abnormal return task into the storage location (staging location) as much as possible, the target object can still be used for order picking without affecting the execution of other logistics tasks.

[0088] Refer to Figure 3C , if it is determined that a second object different from the target object is stored at the target location, the electronic device 110 may execute block 324 to generate a manual logistics task.

[0089] In some cases, another object (such as the second object) may have been wrongly stored at the target location, resulting in the abnormal execution of the return task. To ensure the accuracy of the storage information, the electronic device 110 may associate the second object actually stored at the target location with the target location, and update the original location corresponding to the second object before the association to an idle state, making it available again. In addition, since the target location is already occupied and the logistics task of the current target object cannot be completed, the electronic device 110 cancels the original logistics task to prevent the task from being suspended for a long time.

[0090] In some embodiments, if it is determined that there is another target location in an idle state, the electronic device 110 may generate a logistics task for the task of sending the target object to another target location.

[0091] As an example, when the electronic device 110 determines that when executing task 320 of planning to store the target object C_b at the target location L_0, a second object C_a has already been stored at the target location L_0. This indicates that C_a has been wrongly stored at L_0, resulting in an abnormal logistics task for the target object C_b. The electronic device 110 may first adjust the association relationship between the second object C_a and the target location recorded in the storage information.

[0092] The specific processing steps are as follows. If the electronic device 110 determines that the second object C_a is in the shelved state, it means that it has been misplaced to the target location L_0, and there is an error in the storage location L_1 of the C_a object recorded in the storage information. In this case, the electronic device 110 unbinds the association between C_a and L_1, updates L_1 to "idle" for subsequent storage of other objects. Then, the electronic device 110 updates the relationship between C_a and L_0 to make the system record consistent with the actual storage situation, ensuring that errors do not occur during subsequent queries and task processing. If the status of C_a is an abnormal state or in the process of returning to the warehouse, it means that the status of C_a recorded in the storage information is the state of not being moved to the target location, and it needs to be updated to the shelved state, and the second object C_a is associated with the target location L_0.

[0093] Further, after correcting the association relationship between the second object and the storage location, the electronic device 110 cancels the logistics task of the target object C_b and releases the storage resources corresponding to C_b for subsequent task scheduling. Alternatively or additionally, the electronic device 110 can re-plan the logistics task of C_b. If there is an available temporary storage location, the electronic device 110 generates an artificial logistics task, prompting the operator to temporarily store the target object C_b in this location and wait for the subsequent equipment to resume and re-arrange the task of returning to the warehouse. If there is no available temporary storage location, the electronic device 110 generates an artificial logistics task, indicating that it is manually placed on the line, puts C_b on the conveyor line, and schedules a movable device to send it back to the appropriate target location.

[0094] In some embodiments, the task type includes one of the following: a task of operating a target object at a target location, that is, performing operations related to logistics management at the target location, such as an inventory task (checking the recorded storage information and the actual storage situation), a merchandising task (adjusting the storage method of the target object, optimizing the warehouse layout), etc.

[0095] As an example, Figure 3D shows a schematic diagram of the abnormal processing process of the operation task 330 according to some embodiments of the present disclosure.

[0096] Refer to Figure 3D , the type of task 330 is a task of operating a target object at a target location (such as an operation task). The electronic device 110 determines that an abnormality occurs when executing task 330. If it is determined based on the indication of the abnormal state that the device is in an abnormal state and the pick-up state indicates that the target object has not been picked up, the electronic device 110 can execute block 331 and attempt to replace the movable device executing task 330.

[0097] In some embodiments, the electronic device 110 determines whether there is another movable device at the target location. If it is determined that there is another movable device, the logistics task is assigned to the other movable device.

[0098] As an example, the electronic device 110 determines that an abnormality occurs when performing an inventory / stocking task. The abnormal situation is that the current movable device (such as an automated storage and retrieval device) fails and cannot perform the picking task, and the picking status indicates that the target object has not been picked up. In this case, the electronic device 110 can check whether there is any other available movable device at the target location (for example, the current aisle corresponding to the warehouse storage location). If there is an available device, the electronic device 110 can cancel the task of the original faulty device and transfer the logistics task to the new device, and the new device completes the logistics task.

[0099] In some embodiments, if the electronic device 110 determines that there is no other movable device, it can cancel the logistics task of the original faulty device. Then, the electronic device 110 can update the target location to the occupied state, indicating that the target object is still stored in the original storage location. The electronic device 110 can update the storage location to the idle state, indicating that the target object has not been moved to the staging location. For example, if there is no other available device in the current aisle, resulting in the abnormality of task 330 and unable to continue execution, the electronic device 110 updates the corresponding storage information and suspends task 330, waiting to resume execution after the device is repaired.

[0100] Reference Figure 3D , if it is determined that the movable device is in an abnormal state and the picking status indicates that the target object has been picked up, the electronic device 110 can execute block 332 to simulate that the target object has arrived.

[0101] When the electronic device 110 detects that the device is in an abnormal state, but the target object (such as a container, goods, etc.) has been picked up, at this time, the electronic device 110 can simulate the arrival state of the target object in order to maintain the continuity of the logistics process. The core of this strategy is to complete the subsequent logistics tasks through manual intervention to avoid the target object being lost or staying on the faulty device due to equipment abnormalities. The main processing logic is as follows:

[0102] In some embodiments, the electronic device 110 generates an artificial logistics task to move the target object from the movable device to the storage location. In response to determining that the target object has been moved to the storage location, the storage location is updated to the occupied state.

[0103] As an example, if the electronic device 110 determines that the device is abnormal and the target object has been picked up from the target location (warehouse storage location) to the device but has not been placed in the storage location (staging location), due to the device failure, the electronic device 110 generates an artificial logistics task instructing the operator to place the physical box at the staging location specified by the task. Then, the electronic device 110 marks this task as having arrived at the staging location to simulate the normal logistics process and updates the status of the staging location to the occupied state to ensure that the storage information in the system remains synchronized.

[0104] As another example, if the electronic device 110 determines that the device is abnormal and the target object has been moved from the target location (warehousing location) to the storage location (temporary storage location), the electronic device 110 may check the status of the logistics task in the application 120 (such as in the system console). If the status of the task in the console is incomplete, the electronic device 110 simulates that the target object has arrived, updates the task to a completed status, and updates the status of the storage location to an occupied status. If the status of the task in the console is completed, since the subsequent operations have been completed, the electronic device 110 does not need to perform additional processing.

[0105] Return reference Figure 3D , if it is determined that the picking status indicates that there is no target object at the target location, the electronic device 110 may execute block 333 to generate a manual wiring task. Specifically, the electronic device 110 updates the target location and the storage location to an idle status and the target object to an abnormal status, and cancels the original logistics task.

[0106] As an example, when the movable device attempts to pick up the target object from the target location and finds that the target location is empty, resulting in a task exception, the electronic device 110 updates the statuses of the target location (original storage location) and the storage location (target temporary storage location) to an idle status, allowing other target objects to be stored at this location. The status of the target object (such as the target container) is updated to an abnormal status and locked to prevent it from being continuously called by other tasks. In addition, the electronic device 110 can also revoke the inventory preoccupation (subtract the preoccupation quantity corresponding to the abnormal logistics task from the quantity of the storage resources originally preoccupied in the system) to adjust the inventory data and avoid affecting the execution of other normal tasks due to inventory calculation errors.

[0107] Reference Figure 3D , if during the execution of task 330, it is determined that the picking status indicates that the third object picked up by the movable device is not the target object, the electronic device 110 may execute block 313 to generate a manual wiring task. If it is found that the object picked up by the movable device is not the target object, the storage information needs to be adjusted to correct the association relationship between the mispicked object and the storage location. Specifically, the electronic device 110 associates the third object with the target location and determines the original location corresponding to the third object before the association as an idle status.

[0108] In some embodiments, after the electronic device 110 determines that the third object picked up by the movable device is not the target object, it may perform a processing procedure similar to the aforementioned outbound task 310. For example, the electronic device 110 cancels the original logistics task and generates a logistics task to move the target object to another target location.

[0109] In an embodiment of the present disclosure, by being able to automatically identify errors and update stored information, it is possible to avoid affecting subsequent tasks due to data errors, effectively reducing the cascading effects caused by inventory confusion. In addition, through manual logistics tasks, operators can manually adjust the storage location or perform a return-to-storage operation under guidance to ensure that the inventory status returns to normal as soon as possible, thereby enhancing the continuity and overall efficiency of logistics operations.

[0110] Figure 4 FIG. 4 shows a block diagram of an apparatus 400 for exception handling according to some embodiments of the present disclosure. The apparatus 400 may be implemented as or included in an electronic device 110.

[0111] The apparatus 400 includes an acquisition module 410 configured to acquire operation exception information associated with a logistics task of a target object, the operation exception information including the type of the logistics task and an indication of an exception status; a status determination module 420 configured to determine a pick-up status of the target object based on the indication of the exception status, the pick-up status at least indicating whether the target object has been correctly picked up onto a movable device for carrying the target object; and an execution module 430 configured to perform processing for the exception status based at least on the task type and the pick-up status.

[0112] In some embodiments, the task type includes one of the following: a task of moving a target object from a target location to a storage location, a task of sending the target object back from the storage location to the target location, and a task of operating the target object at the target location.

[0113] In some embodiments, the logistics task is a task of moving a target object from a target location to a storage location, and the execution module 430 is further configured to: in response to determining that the movable device is in an abnormal state and the pick-up status indicates that the target object has not been picked up, determine whether there is another movable device at the target location; and in response to determining that there is another movable device, allocate the logistics task to the other movable device.

[0114] In some embodiments, the execution module 430 is further configured to: in response to determining that there is no other movable device, cancel the logistics task; update the target location to an occupied state and the storage location to an idle state; and in response to determining that another target location stores the target object, generate a logistics task of moving the target object out of the other target location.

[0115] In some embodiments, the logistics task is a task of moving a target object from a target location to a storage location, and the execution module 430 is further configured to: in response to determining that the movable device is in an abnormal state and the pick-up status indicates that the target object has been picked up, generate a manual logistics task of moving the target object from the movable device to the storage location; and in response to determining that the target object has been moved to the storage location, update the storage location to an occupied state.

[0116] In some embodiments, the logistics task is a task of moving a target object from a target location to a storage location, and the execution module 430 is further configured to: in response to determining that the picking state indicates that the target object does not exist at the target location, update the target location and the storage location to an idle state and the target object to an abnormal state; and in response to determining that another target location stores the target object, generate a logistics task of moving the target object from the other target location to the storage location.

[0117] In some embodiments, the logistics task is a task of moving a target object from a target location to a storage location, and the execution module 430 is further configured to: in response to determining that the picking state indicates that the first object picked up by the movable device is not the target object, associate the first object with the target location; and update the original location corresponding to the first object before association to an idle state.

[0118] In some embodiments, the execution module 430 is further configured to: cancel the logistics task; and in response to determining that another target location stores the target object, generate a logistics task of moving the target object from the other target location to the storage location.

[0119] In some embodiments, the task type is a task of sending the target object back from the storage location to the target location, and the execution module 430 is further configured to: in response to determining that the movable device is in an abnormal state and the picking state indicates that the target object has not been picked up, determine whether there is another movable device at the target location; and in response to determining that there is another movable device, assign the logistics task to the other movable device.

[0120] In some embodiments, the execution module 430 is further configured to: in response to determining that there is no other movable device, cancel the logistics task; update the storage location to an occupied state and the target location to an idle state.

[0121] In some embodiments, the task type is a task of sending the target object back from the storage location to the target location, and the execution module 430 is further configured to: in response to determining that the movable device is in an abnormal state and the picking state indicates that the target object has been picked up, generate an artificial logistics task of moving the target object from the movable device to the storage location; in response to determining that the target object has been moved to the storage location, update the storage location to an occupied state and the target location to an idle state; and in response to determining that there is no storage location in an idle state, generate an artificial logistics task of sending the target object back from the movable device to the target location.

[0122] In some embodiments, the task type is a task of returning a target object from a storage location to a target location, and the execution module 430 is further configured to: in response to determining that the target location already stores a second object different from the target object, associate the second object with the target location; and update the original location corresponding to the second object before the association to an idle state.

[0123] In some embodiments, the execution module 430 is further configured to: cancel a logistics task; and in response to determining that there is another target location in an idle state, generate a logistics task for returning the target object to the another target location.

[0124] In some embodiments, the task type is a task of operating a target object at a target location, and the execution module 430 is further configured to: in response to determining that the movable device is in an abnormal state and the picking state indicates that the target object has not been picked up, determine whether there is another movable device at the target location; in response to determining that there is another movable device, allocate the logistics task to the another movable device; and in response to determining that there is no another movable device, cancel the logistics task.

[0125] In some embodiments, the task type is a task of operating a target object at a target location, and the execution module 430 is further configured to: in response to determining that the movable device is in an abnormal state and the picking state indicates that the target object has been picked up, generate a manual logistics task for moving the target object from the movable device to a storage location; and in response to determining that the target object has been moved to the storage location, update the storage location to an occupied state.

[0126] In some embodiments, the task type is a task of operating a target object at a target location, and the execution module 430 is further configured to: in response to determining that the picking state indicates that there is no target object at the target location, update the target location and the storage location to an idle state and the target object to an abnormal state; and cancel the logistics task.

[0127] In some embodiments, the task type is a task of operating a target object at a target location, and the execution module 430 is further configured to: in response to determining that the picking state indicates that a third object picked up by the movable device is not the target object, associate the third object with the target location; and determine the original location corresponding to the third object before the association to be in an idle state.

[0128] In some embodiments, the execution module 430 is further configured to: cancel a logistics task; and generate a logistics task for moving the target object to another target location.

[0129] The modules included in apparatus 400 can be implemented in various ways, including software, hardware, firmware, or any combination thereof. In some embodiments, one or more units can be implemented using software and / or firmware, such as machine-executable instructions stored on a storage medium. In addition to or as an alternative to the machine-executable instructions, some or all of the units in apparatus 400 can be implemented at least in part by one or more hardware logic components. By way of example and not limitation, exemplary types of hardware logic components that can be used include field-programmable gate arrays (FPGAs), application-specific integrated circuits (ASICs), application-specific standard products (ASSPs), systems-on-a-chip (SOCs), complex programmable logic devices (CPLDs), and the like.

[0130] Figure 5 FIG. shows a block diagram of an electronic device 500 in which one or more embodiments of the present disclosure can be implemented. It should be understood that Figure 5 the illustrated electronic device 500 is merely exemplary and should not constitute any limitation on the functions and scope of the embodiments described herein.

[0131] As Figure 5 shown, the electronic device 500 is in the form of a general-purpose electronic device. The components of the electronic device 500 can include, but are not limited to, one or more processors or processing units 510, a memory 520, a storage device 530, one or more communication units 540, one or more input devices 550, and one or more output devices 560. The processing unit 510 can be an actual or virtual processor and is capable of performing various processes according to programs stored in the memory 520. In a multi-processor system, multiple processing units execute computer-executable instructions in parallel to improve the parallel processing ability of the electronic device 500.

[0132] The electronic device 500 generally includes multiple computer storage media. Such media can be any available media accessible to the electronic device 500, including but not limited to volatile and non-volatile media, removable and non-removable media. The memory 520 can be a volatile memory (such as registers, caches, random access memory (RAM)), a non-volatile memory (such as read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), flash memory), or some combination thereof. The storage device 530 can be a removable or non-removable medium and can include a machine-readable medium, such as a flash drive, a magnetic disk, or any other medium that can be used to store information and / or data and can be accessed within the electronic device 500.

[0133] The electronic device 500 can further include additional removable / non-removable, volatile / non-volatile storage media. Although not shown in Figure 5As shown, a disk drive for reading from and writing to a removable, non-volatile disk (such as a "floppy disk") and an optical disk drive for reading from and writing to a removable, non-volatile optical disk can be provided. In these cases, each drive can be connected to a bus (not shown) by one or more data medium interfaces. Memory 520 may include a computer program product 525 having one or more program modules configured to perform the various methods or actions of the various embodiments of the present disclosure.

[0134] Communication unit 540 enables communication with other electronic devices via a communication medium. Additionally, the functions of the components of electronic device 500 can be implemented in a single computing cluster or multiple computer machines capable of communicating via a communication connection. Thus, electronic device 500 can operate in a networked environment using a logical connection to one or more other servers, network personal computers (PCs), or another network node.

[0135] Input device 550 can be one or more input devices such as a mouse, keyboard, trackball, etc. Output device 560 can be one or more output devices such as a display, speaker, printer, etc. Electronic device 500 can also communicate with one or more external devices (not shown) as needed via communication unit 540, external devices such as storage devices, display devices, etc., communicate with one or more devices that enable a user to interact with electronic device 500, or communicate with any device that enables electronic device 500 to communicate with one or more other electronic devices (e.g., network card, modem, etc.). Such communication can be performed via an input / output (I / O) interface (not shown).

[0136] According to an exemplary implementation of the present disclosure, a computer-readable storage medium is provided, on which one or more computer instructions are stored, and the one or more computer instructions are executed by a processor to implement the method described above. According to an exemplary implementation of the present disclosure, a computer program product is also provided, the computer program product being tangibly stored on a non-transitory computer-readable medium and including computer-executable instructions, and the computer-executable instructions are executed by a processor to implement the method described above.

[0137] Aspects of the present disclosure are described herein with reference to the flowcharts and / or block diagrams of methods, apparatuses (systems), and computer program products according to the present disclosure. It should be understood that each block of the flowcharts and / or block diagrams, and the combinations of blocks in the flowcharts and / or block diagrams, can be implemented by computer-readable program instructions.

[0138] These computer-readable program instructions can be provided to a processing unit of a general-purpose computer, a special-purpose computer, or other programmable data processing apparatus to produce a machine such that the instructions, when executed by the processing unit of the computer or other programmable data processing apparatus, result in an apparatus that implements the functions / acts specified in one or more boxes of the flowchart and / or block diagram. These computer-readable program instructions may also be stored in a computer-readable storage medium that causes a computer, a programmable data processing apparatus, and / or other devices to function in a particular manner, such that the computer-readable medium storing the instructions comprises a manufacture including instructions that implement various aspects of the functions / acts specified in one or more boxes of the flowchart and / or block diagram.

[0139] The computer-readable program instructions may also be loaded onto a computer, other programmable data processing apparatus, or other device, such that a series of operational steps are performed on the computer, other programmable data processing apparatus, or other device to produce a computer-implemented process, whereby the instructions executed on the computer, other programmable data processing apparatus, or other device implement the functions / acts specified in one or more boxes of the flowchart and / or block diagram.

[0140] The flowcharts and block diagrams in the figures illustrate the architecture, functionality, and operation of possible implementations of systems, methods, and computer program products according to various implementations of the present disclosure. In this regard, each box in the flowchart or block diagram may represent a module, a segment of code, or a portion of an instruction, and the module, segment of code, or portion of an instruction includes one or more executable instructions for implementing the specified logical function. In some alternative implementations, the functions noted in the boxes may occur out of the order noted in the figures. For example, two consecutive boxes may in fact be executed substantially in parallel, or they may sometimes be executed in the reverse order, depending upon the functionality involved. It should also be noted that each box of the block diagrams and / or flowcharts, and combinations of boxes in the block diagrams and / or flowcharts, can be implemented by special-purpose hardware-based systems that perform the specified functions or acts, or by combinations of special-purpose hardware and computer instructions.

[0141] The implementations of the present disclosure have been described above. The description is exemplary, not exhaustive, and is not limited to the disclosed implementations. Many modifications and variations will be apparent to those of ordinary skill in the art without departing from the scope and spirit of the described implementations. The choice of terms used herein is intended to best explain the principles of the implementations, the practical application, or improvements made to the technology in the marketplace, or to enable other ordinary skill in the art to understand the implementations disclosed herein.

Claims

1. An exception handling method, comprising: Acquire operation abnormality information associated with a logistics task of a target object, the operation abnormality information including a type of the logistics task and an indication of the abnormal state; Determining a pickup state of the target object based on the indication of the abnormal state, the pickup state at least indicating whether the target object has been correctly picked up on a movable device for carrying the target object; as well as Based at least on the task type and the pickup status, a process for the abnormal state is performed.

2. The method according to claim 1, wherein the task type comprises one of the following: a task of moving the target object from a target location to a storage location, Return the target object from the storage location to the target location task, A task of manipulating the target object at the target location.

3. The method according to claim 2, wherein the logistics task is a task of moving the target object from the target location to the storage location, and wherein executing the processing for the abnormal state comprises: In response to determining that the movable device is in an abnormal state and the pickup state indicates that the target object has not been picked up, determining whether there is another movable device at the target location; as well as In response to determining that the other movable device exists, the logistics task is assigned to the other movable device.

4. The method according to claim 3, further comprising: In response to determining that the other movable device does not exist, canceling the logistics task; updating the target location to an occupied state and the storage location to an idle state; as well as In response to determining that another target location stores the target object, a logistics task is generated to move the target object from the another target location.

5. The method according to claim 2, wherein the logistics task is a task of moving the target object from the target location to the storage location, and wherein executing the processing for the abnormal state comprises: In response to determining that the movable device is in an abnormal state and the pickup state indicates that the target object has been picked up, generating a manual logistics task to move the target object from the movable device to the storage location; as well as In response to determining that the target object has been moved to the storage location, the storage location is updated to an occupied state.

6. The method according to claim 2, wherein the logistics task is a task of moving the target object from the target location to the storage location, and wherein executing the process for the abnormal state comprises: In response to determining that the pickup status indicates that the target object does not exist at the target location, updating the target location and the storage location to an idle state and the target object to an abnormal state; as well as In response to determining that another target location stores the target object, a logistics task is generated to move the target object from the another target location to the storage location.

7. The method according to claim 2, wherein the logistics task is a task of moving the target object from the target location to the storage location, and wherein executing the process for the abnormal state comprises: In response to determining that the pickup status indicates that a first object picked up by the movable device is not the target object, associating the first object with the target location; as well as An original position corresponding to the first object before the association is performed is updated to an idle state.

8. The method according to claim 7, further comprising: cancelling the logistics task; as well as In response to determining that another target location stores the target object, a logistics task is generated to move the target object from the another target location to the storage location.

9. The method according to claim 2, wherein the task type is a task of returning the target object from the storage location to the target location, and wherein executing the process for the abnormal state further comprises: In response to determining that the movable device is in an abnormal state and the pickup state indicates that the target object has not been picked up, determining whether there is another movable device at the target location; In response to determining that the other movable device exists, the logistics task is assigned to the other movable device.

10. The method according to claim 9, further comprising: In response to determining that the other movable device does not exist, canceling the logistics task; The storage location is updated to be occupied and the target location is updated to be idle.

11. The method according to claim 2, wherein the task type is a task of returning the target object from the storage location to the target location, and wherein executing the process for the abnormal state further comprises: In response to determining that the movable device is in an abnormal state and the pickup state indicates that the target object has been picked up, generating a manual logistics task to move the target object from the movable device to the storage location; In response to determining that the target object has been moved to the storage location, updating the storage location to an occupied state and the target location to an idle state; as well as In response to determining that there is no idle storage location, a manual logistics task is generated to return the target object from the movable device to the target location.

12. The method according to claim 2, wherein the task type is a task of returning the target object from the storage location to the target location, and wherein executing the process for the abnormal state further comprises: In response to determining that the target location has stored a second object different from the target object, associating the second object with the target location; as well as An original position corresponding to the second object before the association is performed is updated to an idle state.

13. The method according to claim 12, further comprising: cancelling the logistics task; as well as In response to determining that there is another target location in an idle state, a logistics task of returning the target object to the another target location is generated.

14. The method according to claim 2, wherein the task type is a task of operating the target object at the target location, and wherein performing a process for the abnormal state further comprises: In response to determining that the movable device is in an abnormal state and the pickup state indicates that the target object has not been picked up, determining whether there is another movable device at the target location; In response to determining that the other movable device exists, allocating the logistics task to the other movable device; as well as In response to determining that the other movable device does not exist, the logistics task is canceled.

15. The method according to claim 2, wherein the task type is a task of operating the target object at the target location, and wherein performing a process for the abnormal state further comprises: In response to determining that the movable device is in an abnormal state and the pickup state indicates that the target object has been picked up, generating a manual logistics task to move the target object from the movable device to the storage location; as well as In response to determining that the target object has been moved to the storage location, the storage location is updated to an occupied state.

16. The method according to claim 2, wherein the task type is a task of operating the target object at the target location, and wherein performing a process for the abnormal state further comprises: In response to determining that the pickup status indicates that the target object does not exist at the target location, updating the target location and the storage location to an idle state and the target object to an abnormal state; as well as Cancel the logistics task.

17. The method according to claim 2, wherein the task type is a task of operating the target object at the target location, and wherein executing a processing method for the abnormal state further comprises: In response to determining that the pickup status indicates that the third object picked up by the movable device is not the target object, associating the third object with the target location; as well as An original position corresponding to the third object before the association is performed is determined as an idle state.

18. The method according to claim 17, further comprising: cancelling the logistics task; as well as A logistics task is generated to move the target object to another target location.

19. A device for exception handling, comprising: an acquisition module configured to acquire operation abnormality information associated with a logistics task of a target object, the operation abnormality information including a type of the logistics task and an indication of the abnormal state; a state determination module, configured to determine a pickup state of the target object based on the indication of the abnormal state, the pickup state at least indicating whether the target object has been correctly picked up on a movable device for carrying the target object; as well as The execution module is configured to execute processing for the abnormal state based on at least the task type and the pickup state.

20. An electronic device, comprising: at least one processing unit; as well as At least one memory, the at least one memory being coupled to the at least one processing unit and storing instructions for execution by the at least one processing unit, the instructions causing the electronic device to perform the method according to any one of claims 1 to 18 when executed by the at least one processing unit.

21. A computer-readable storage medium having a computer program stored thereon, wherein the computer program can be executed by a processor to implement the method according to any one of claims 1 to 18.

22. A computer program product tangibly stored in a computer storage medium and comprising computer executable instructions which, when executed by a device, cause the device to perform the method according to any one of claims 1 to 18.

Images