Task processing method and device, electronic equipment and storage medium

Abstract

The embodiment of the invention provides a task processing method and device, electronic equipment and a storage medium, the method is applied to a robot and comprises the steps that at least one display control and an exception reporting control are displayed on a display screen of the robot, and the display control is used for displaying task associated information of a to-be-processed task; in response to a trigger operation on the exception reporting control, displaying an exception task selection page, so as to determine a target exception task based on the trigger operation in the exception task selection page, the exception task selection page comprising at least one display control; in response to a trigger operation of uploading the target abnormal task, sending task associated information and abnormal information of the target abnormal task to the target terminal; wherein the exception information comprises description information of exception of the target exception task. According to the technical scheme provided by the embodiment of the invention, the abnormal condition is responded in time, the processing progress of the to-be-processed task is quickly promoted, and the effect of improving the task processing efficiency is realized.

Description

Technical Field

[0001] Embodiments of the present disclosure relate to robot technology, and in particular, to a task processing method, apparatus, electronic device, and storage medium. Background Art

[0002] With the rapid popularization of Internet technology and the continuous progress of artificial intelligence, robots have become the focus of attention in various industries.

[0003] In related technologies, robots are often used to process various different tasks to be processed. However, related technologies have at least the following technical problems: Due to the differences in different tasks to be processed, abnormal situations may occur during the execution of the tasks to be processed, resulting in the interruption of the processing process of the tasks to be processed, being unable to respond to abnormal situations in a timely manner, and affecting the processing progress and efficiency of the robot for the tasks to be processed. Summary of the Invention

[0004] The present disclosure provides a task processing method, apparatus, electronic device, and storage medium to achieve the purpose of improving task processing efficiency.

[0005] In a first aspect, an embodiment of the present disclosure provides a task processing method applied to a robot. The method includes:

[0006] Displaying at least one display control and an exception reporting control on the display screen of the robot, where the display control is used to display task-related information of the task to be processed;

[0007] In response to a trigger operation on the exception reporting control, displaying an exception task selection page to determine a target exception task based on a trigger operation on the exception task selection page, where the exception task selection page includes the at least one display control;

[0008] In response to a trigger operation for uploading the target exception task, sending the task-related information and exception information of the target exception task to a target terminal;

[0009] where the exception information includes descriptive information indicating that the target exception task has an exception.

[0010] In a second aspect, an embodiment of the present disclosure further provides a task processing apparatus disposed in a robot. The apparatus includes:

[0011] A control display module, configured to display at least one display control and an exception reporting control on the display screen of the robot, where the display control is used to display task-related information of the task to be processed;

[0012] a target abnormal task determination module, configured to, in response to a trigger operation on the abnormality reporting control, display an abnormal task selection page to determine a target abnormal task based on the trigger operation on the abnormal task selection page, wherein the abnormal task selection page includes the at least one display control;

[0013] An information sending module, configured to send task association information and abnormality information of the target abnormal task to a target terminal in response to a triggering operation of uploading the target abnormal task;

[0014] The abnormal information includes description information of the abnormality of the target abnormal task.

[0015] In a third aspect, an embodiment of the present disclosure further provides an electronic device, the electronic device comprising:

[0016] at least one processor; and

[0017] a memory communicatively connected to the at least one processor; wherein,

[0018] The memory stores a computer program that can be executed by the at least one processor, and the computer program is executed by the at least one processor so that the at least one processor can perform the task processing method described in any one of the embodiments of the present disclosure.

[0019] In a fourth aspect, an embodiment of the present disclosure further provides a computer-readable storage medium, wherein the computer-readable storage medium stores computer instructions, and the computer instructions are used to enable a processor to implement any task processing method described in the embodiments of the present disclosure when executed.

[0020] In an embodiment of the present disclosure, at least one display control and an exception reporting control are displayed on a display screen of a robot, wherein the display control is used to display task association information of a pending task. When an abnormal situation occurs during the execution of a pending task through the exception reporting control, an abnormal task selection page can be displayed in response to a triggering operation on the exception reporting control. The pending task that the robot needs to execute is displayed through the abnormal task selection page, and based on the triggering operation in the abnormal task selection page, the target abnormal task is determined, wherein the abnormal task selection page includes at least one display control; in response to a triggering operation of uploading the target abnormal task, the task association information and the abnormal information of the target abnormal task are sent to a target terminal, thereby reporting the task association information and the abnormal information to the target terminal through the robot, responding to the abnormal situation in a timely manner, and quickly advancing the processing progress of the pending task, thereby achieving the effect of improving task processing efficiency. BRIEF DESCRIPTION OF THE DRAWINGS

[0021] In combination with the accompanying drawings and with reference to the following specific embodiments, the above and other features, advantages, and aspects of the various embodiments of the present disclosure will become more apparent. Throughout the drawings, the same or similar reference numerals denote the same or similar elements. It should be understood that the drawings are schematic, and the original components and elements are not necessarily drawn to scale.

[0022] Figure 1 It is a schematic flowchart of a task processing method provided by an embodiment of the present disclosure;

[0023] Figure 2 It is a schematic diagram of an abnormal task selection page provided by an embodiment of the present disclosure;

[0024] Figure 3 It is a schematic flowchart of a task processing method provided by an embodiment of the present disclosure;

[0025] Figure 4 It is a schematic diagram of a task display page provided by an embodiment of the present disclosure;

[0026] Figure 5 It is a schematic diagram of a display interface for abnormal reasons to be selected provided by an embodiment of the present disclosure

[0027] Figure 6 It is a schematic flowchart of a distribution task processing method provided by an embodiment of the present disclosure;

[0028] Figure 7 It is a schematic structural diagram of a task processing device provided by an embodiment of the present disclosure;

[0029] Figure 8 It is a schematic structural diagram of an electronic device provided by an embodiment of the present disclosure. Specific Embodiments

[0030] The 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. Instead, 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.

[0031] It should be understood that the various steps recorded in the method embodiments of the present disclosure can be executed in a different order and / or in parallel. In addition, the method embodiments may include additional steps and / or omit the steps shown. The scope of the present disclosure is not limited in this regard.

[0032] As used herein, the term "including" and its variations are open-ended, i.e., "including but not limited to." The term "based on" means "based, at least in part, on." The term "one embodiment" means "at least one embodiment," the term "another embodiment" means "at least one additional embodiment," and the term "some embodiments" means "at least some embodiments." Other terms are defined in the following description.

[0033] It should be noted that the concepts of "first" and "second" mentioned in this disclosure are only used to distinguish different devices, modules or units, and are not used to limit the order or interdependence of the functions performed by these devices, modules or units.

[0034] It should be noted that the modifications of "one" and "multiple" mentioned in the present disclosure are illustrative rather than restrictive, and those skilled in the art should understand that unless otherwise clearly indicated in the context, they should be understood as "one or more".

[0035] The names of the messages or information exchanged between multiple devices in the embodiments of the present disclosure are only used for illustrative purposes and are not used to limit the scope of these messages or information.

[0036] It is understandable that before using the technical solutions disclosed in the various embodiments of this disclosure, the type, scope of use, usage scenarios, etc. of the personal information involved in this disclosure should be informed to the user and the user's authorization should be obtained in an appropriate manner in accordance with relevant laws and regulations.

[0037] For example, in response to a user's active request, a prompt message is sent to the user to clearly inform the user that the operation requested will require the acquisition and use of the user's personal information. This allows the user to independently choose whether to provide personal information to the electronic device, application, server, storage medium, or other software or hardware that performs the operations of the disclosed technical solution based on the prompt message.

[0038] As an optional but non-limiting implementation, in response to receiving a user's active request, the prompt information may be sent to the user in the form of a pop-up window, in which the prompt information may be presented in text form. Furthermore, the pop-up window may also contain a selection control for the user to select "agree" or "disagree" to provide personal information to the electronic device.

[0039] It is understandable that the above notification and user authorization process are merely illustrative and do not limit the implementation of the present disclosure. Other methods that comply with relevant laws and regulations may also be applied to the implementation of the present disclosure.

[0040] Before introducing the technical solution, an exemplary description of the application scenario can be given first. This technical solution can be applied to the scenario where a robot processes a to-be-processed task with an abnormal situation when executing a to-be-processed task of delivering an object to be delivered. Exemplarily, this technical solution can be applied to scenarios such as station delivery scenarios and food delivery scenarios; the robot delivers the object to be delivered between different buildings, floors or rooms. For example, in a station delivery scenario, the station can be used as the goods placement end, and the object to be delivered is stored in the robot through the goods placement end, thereby generating a to-be-processed task for delivering the object to be delivered, and the robot executes this to-be-processed task to deliver the object to be delivered to the pick-up end. Or, this technical solution can be applied to an item storage scenario where the robot stores items on behalf of others; for example, in an item storage scenario, obtaining the item to be stored and storing the item to be stored can be used as the to-be-processed task, and the robot executes this to-be-processed task. Through this technical solution, when an abnormal situation occurs during the execution of the to-be-processed task, the robot sends the task association information and abnormal information of the target abnormal task to the target terminal, responds to the abnormal situation in a timely manner, quickly promotes the processing progress of the to-be-processed task, and improves the task processing efficiency of the to-be-processed task.

[0041] Figure 1 FIG. is a schematic flowchart of a task processing method provided by an embodiment of the present disclosure. The embodiment of the present disclosure is applicable to the situation where a robot reports a target abnormal task that appears to a target terminal when an abnormal situation occurs in a to-be-processed task. This method can be executed by a task processing device, and this device can be implemented in the form of software and / or hardware. Optionally, it is implemented by an electronic device, and this electronic device can be a mobile terminal, a PC terminal or a server, etc.

[0042] As Figure 1 shown, the method is applied to a robot and includes:

[0043] S110. Display at least one display control and an abnormal reporting control on the display screen of the robot, where the display control is used to display the task association information of the to-be-processed task.

[0044] It should be noted that the robot disclosed in this solution is used to execute the to-be-processed task. For example, in a station delivery scenario, the to-be-processed task is a delivery task of delivering the object to be delivered. In order to better display the processing situation of the to-be-processed task, a display screen can be configured on the robot, and the task information of the to-be-processed task is visually displayed through the display screen. Further, in order to improve the convenience of executing the to-be-processed task, the display screen can be a touch display screen.

[0045] In this embodiment, at least one display control is displayed on the display screen; the display control is used to display task-related information for pending tasks. The task-related information includes a task identifier and the user identifier of at least one user associated with the pending task. This task-related information distinguishes different pending tasks. Optionally, each pending task is associated with at least one user. For example, if the pending task is a delivery task, the pending task is associated with at least one pickup user; if the pending task is an item deposit task, the pending task is associated with at least one item depositing user and an item retrieving user.

[0046] In practice, the number of display controls correlates to the number of pending tasks for the robot. For example, pending tasks include express delivery and food delivery. Each display control corresponds to a pending task, with each display control displaying task-related information for a single pending task. Alternatively, a single display control may be included on the display screen to display task-related information for all pending tasks executed by the robot.

[0047] In this embodiment, an exception reporting control is displayed on the robot's display screen. The exception reporting control is used to obtain exception information about pending tasks with exceptions, such as the task identifier of the abnormal pending task, the cause of the exception, and other information. In a specific implementation, an exception reporting control can be set for each display control. When an exception occurs in the pending task corresponding to the display control, the abnormal pending task is reported through the exception reporting control corresponding to the display control. Alternatively, an exception reporting control can be displayed on the display screen. When an exception occurs in any pending task, the exception reporting control can be triggered to report the exception.

[0048] For a clear and detailed description of the display controls on the display screen, see Figure 2 . Figure 2 Taking the post delivery scenario as an example, the display controls on the robot's display screen are shown. In the post delivery scenario, the robot has at least one slot to place pending tasks. Figure 2 There are four slots in the display, three of which correspond to pending tasks and one is idle. Each pending task is displayed through a display control. The display control corresponding to the pending task displays the slot identifier, task association information, and exception reporting control. Figure 2As shown, the compartment identifier can be expressed as "××1", "××2", "××3", and the task association information can be expressed as "××××1", "××××2", "××××3". The display screen also includes a "Click to Select Abnormal Information" control as an abnormal reporting control. By triggering the corresponding drop-down control of "Click to Select Abnormal Information", abnormal information is generated. For the to-be-processed tasks with determined abnormal causes, the abnormal information can be directly displayed on the display control, such as "Quantity Missing". The display screen may also include a "Submit" control for abnormal reporting.

[0049] S120. In response to the triggering operation on the abnormal reporting control, display an abnormal task selection page to determine a target abnormal task based on the triggering operation on the abnormal task selection page.

[0050] In this embodiment, the abnormal reporting control can be at least one type of button, edit box, selection control, and drop-down control; correspondingly, according to the different types of the abnormal reporting control, the triggering operation on the abnormal reporting control can be a click operation, an input operation, a selection operation, etc. In practical applications, in response to the triggering operation on the abnormal reporting control, an abnormal task selection page is displayed, and the task association information of at least one to-be-processed task received by the robot is displayed through the abnormal task selection page.

[0051] In a specific implementation, the triggering operation on the abnormal task selection page can be the triggering operation on any control in the abnormal selection page; the target abnormal task is determined through the triggering operation on the abnormal task selection page. It should be noted that the target abnormal task is a task that the robot cannot continue to process, for example, a task that does not support the robot to process, or a task with incorrect task association information.

[0052] In practical applications, the abnormal task selection page contains at least one control, and the target abnormal task is determined by responding to the triggering operation on the control. Exemplarily, the abnormal task selection page contains an abnormal task input box, and the target abnormal task can be determined by inputting the task association information of the to-be-processed task with an abnormality in the abnormal task input box; or, the abnormal task selection page contains at least one display control, and the display control is used to display the task association information of the to-be-processed task. The target abnormal task can be determined from the to-be-processed tasks based on the triggering operation on the display control.

[0053] In this embodiment, the abnormal task selection page includes at least one display control and the task association information displayed on the display control; the display control on the abnormal task selection page also includes an abnormal cause selection sub-control, and at least one to-be-selected abnormal cause and an abnormal cause editing control are displayed after the abnormal cause selection sub-control is triggered.

[0054] For easy viewing, at least one display control located on the abnormal task selection page has the same layout as at least one display control displayed on the display screen. Optionally, in the abnormal task selection page, a display control can be correspondingly set for each to-be-processed task assigned to the robot to comprehensively display the task-related information of the to-be-processed task. By displaying the display control on the abnormal task selection page, the task-related information of the to-be-processed task can be clearly and intuitively displayed, facilitating the user to accurately and quickly select the target abnormal task.

[0055] In this embodiment, the abnormal cause selection sub-control is used to obtain the abnormal information of the target abnormal task; the abnormal information includes the description information of the existence of the abnormal situation of the target abnormal task, such as the description of the abnormal cause, the description of the abnormal severity level, and the description of the abnormal type of the target abnormal task, etc. Exemplarily, in the scenario of station delivery, the description information of the abnormal cause may include item loss, item quantity shortage, imperfect item information, and item overweight, etc. The description information of the abnormal severity level may include minor abnormality, medium abnormality, and severe abnormality, etc.; the description information of the abnormal type may include the abnormality of the to-be-processed object, the abnormality of the task-related information, etc.

[0056] Optionally, in the abnormal task selection page, there are at least one abnormal cause selection sub-control. For example, each display control corresponds to an abnormal cause selection sub-control; or, the abnormal task selection page only contains one abnormal cause selection sub-control to obtain the abnormal information of the target abnormal task after determining the target abnormal task.

[0057] It should be noted that after the abnormal cause selection sub-control is triggered, at least one to-be-selected abnormal cause and an abnormal cause editing control are displayed. Specifically, the to-be-selected abnormal cause can be selected, and the abnormal information of the target abnormal task is determined based on the selected to-be-selected abnormal cause. The abnormal cause editing control is used to input and edit text, and the abnormal information is determined based on the edited text in the abnormal cause editing control.

[0058] In this embodiment, the task-related information of the to-be-processed task can be clearly and intuitively displayed, facilitating the user to accurately and quickly select the target abnormal task. Moreover, an abnormal cause selection sub-control is set in the abnormal task selection page, so as to obtain the abnormal information of the target abnormal task based on the abnormal cause selection sub-control, improving the convenience in the process of processing the target abnormal task.

[0059] In practical applications, the implementation method for determining the target abnormal task based on the trigger operation in the abnormal task selection page is: determining the target abnormal task based on the trigger operation on the display control in the abnormal task selection page. When it is detected that a display control in the abnormal task selection page is triggered, the to-be-processed task corresponding to the task-related information displayed by the display control can be determined as the target abnormal task.

[0060] Further, after determining the target abnormal task, the triggering operation of the sub-control can be selected based on the abnormal cause to obtain the abnormal information corresponding to the target abnormal task. Specifically, the method for obtaining the abnormal information corresponding to the target abnormal task can be: in response to the triggering operation of the abnormal cause selection sub-control, at least one to-be-selected abnormal cause and an abnormal cause editing control are displayed. The abnormal information is determined based on the triggering operation of the to-be-selected abnormal cause and / or the edited text in the abnormal cause editing control.

[0061] In a specific implementation, the implementation method for determining the target abnormal task based on the triggering operation on the abnormal task selection page can also be: in response to the triggering operation of the abnormal cause selection sub-control, at least one to-be-selected abnormal cause and an abnormal cause editing control are displayed, so as to determine the abnormal information based on the triggering operation of the to-be-selected abnormal cause and / or the edited text in the abnormal cause editing control; and, the to-be-processed task corresponding to the triggered abnormal cause selection sub-control is used as the target abnormal task.

[0062] Optionally, the abnormal cause selection sub-control corresponds to the to-be-processed task. When the abnormal cause selection sub-control is triggered, the corresponding to-be-processed task can be determined, and the to-be-processed task corresponding to the triggered abnormal cause selection sub-control is determined as the target abnormal task. Specifically, on the abnormal task selection page, the number of triggered abnormal cause selection sub-controls can be multiple to quickly determine multiple target abnormal tasks.

[0063] In addition, the abnormal information corresponding to the target abnormal task can be determined through the triggering operation of the abnormal cause selection sub-control. Specifically, in response to the triggering operation of the abnormal cause selection sub-control, at least one to-be-selected abnormal cause can be displayed, and the selected to-be-selected abnormal cause is determined as the abnormal information.

[0064] It should be noted that for each abnormal cause selection sub-control, the same to-be-selected abnormal cause can be preset for display; or different to-be-selected abnormal causes can be set according to the differences in the to-be-processed tasks corresponding to the abnormal cause selection sub-controls, so as to adaptively provide to-be-selected abnormal causes that match the to-be-processed tasks according to the differences in the processing tasks.

[0065] Further, after the abnormal cause selection sub-control is triggered, an abnormal cause editing control can be displayed. After the abnormal cause editing control is triggered, the edited text in the abnormal cause editing control can be obtained, and the information corresponding to the edited text is determined as the abnormal information.

[0066] In this embodiment, based on the triggering operation for the to-be-selected exception reason and / or the edited text in the exception reason editing control, the exception information is determined, thereby improving the diversity of the ways to obtain the exception information; the convenience of determining the exception information is improved by pre-providing the to-be-selected exception reasons; and, when the to-be-selected exception reasons cannot accurately reflect the exception information, an exception reason editing control is also provided, which is beneficial to obtaining the exception information flexibly and accurately.

[0067] S130. In response to the triggering operation for uploading the target exception task, send the task association information and the exception information of the target exception task to the target terminal.

[0068] Among them, the exception information includes the description information indicating that there is an exception in the target exception task.

[0069] In a specific implementation, the uploading of the target exception task can be triggered by means of voice commands, gesture commands, etc. Alternatively, an exception submission control can also be provided on the exception task selection page. When the exception submission control is clicked, the uploading of the target exception task is triggered.

[0070] In order to process the target exception task in a timely manner, in response to the triggering operation for uploading the target exception task, the determined task association information and exception information of the target exception task can be sent to the target terminal to complete the uploading operation of the target exception task. Among them, the target terminal can be a terminal for processing exception tasks; for example, it can be an operation and maintenance terminal for maintaining the work of the robot.

[0071] The technical solution of the embodiment of the present disclosure displays at least one display control and an exception reporting control on the display screen of the robot. Among them, the display control is used to display the task association information of the to-be-processed task. Through the exception reporting control, when an exception occurs during the execution of the to-be-processed task, in response to the triggering operation for the exception reporting control, an exception task selection page can be displayed. The to-be-processed tasks that the robot needs to execute are displayed through the exception task selection page, and based on the triggering operation on the exception task selection page, the target exception task is determined. Among them, the exception task selection page includes at least one display control; in response to the triggering operation for uploading the target exception task, the task association information and the exception information of the target exception task are sent to the target terminal, so that the task association information and the exception information are reported to the target terminal through the robot, responding to the exception situation in a timely manner, quickly promoting the processing progress of the to-be-processed task, and achieving the effect of improving the task processing efficiency.

[0072] Figure 3This is a flowchart of a task processing method provided by an embodiment of the present disclosure. Based on the aforementioned embodiment, after determining abnormal information, feedback information can be received from the target terminal. If the target abnormal task is a stranded task, the target abnormal task is marked and recorded. The explanations of terms that are identical or corresponding to the aforementioned embodiments are not repeated here.

[0073] like Figure 3 As shown, the method includes:

[0074] S210: Display at least one display control and an exception reporting control on a display screen of the robot, wherein the display control is used to display task-related information of the task to be processed.

[0075] Optionally, the abnormal task selection page includes at least one display control and task association information displayed on the display control; the display control of the abnormal task selection page also includes an abnormal cause selection sub-control, and after the abnormal cause selection sub-control is triggered, at least one abnormal cause to be selected and an abnormal cause editing control are displayed.

[0076] S220 . In response to a trigger operation on the exception reporting control, display an abnormal task selection page to determine a target abnormal task based on the trigger operation on the abnormal task selection page.

[0077] In this embodiment, the method for determining the target abnormal task also includes: in response to a trigger operation on a display control on an abnormal task selection page, displaying a task display page, the task display page is used to present at least one pending subtask associated with the task to be reported, and the task to be reported is the pending task corresponding to the triggered display control; in response to a trigger operation on at least one pending subtask presented on the task display page, determining the target abnormal task.

[0078] It should be noted that each pending task may include at least one pending subtask; accordingly, each task-related information may include at least one subtask-related information. For example, if the pending task is a delivery task, there may be multiple delivery objects corresponding to the pending task, and each delivery object may correspond to a pending subtask. The subtask-related information may be the object identifier of the delivery object.

[0079] In a specific implementation, when a display control is triggered on the abnormal task selection page, a task display interface corresponding to the display control may be displayed. It should be noted that the task display interface may correspond to at least one display control, and it can also be understood that at least one pending subtask corresponding to the display control may be presented in the task display interface. Exemplarily, in the case where the task display interface corresponds one-to-one with the display control, if display control 1 corresponds to task 1 to be reported, then after display control 1 is triggered, task display interface 1 is displayed, and task display interface 1 displays at least one pending subtask associated with task 1 to be reported.

[0080] Furthermore, if it is detected that at least one to-be-processed subtask presented on the task display page is triggered, each triggered to-be-processed subtask may be determined as a target abnormal task.

[0081] Figure 4 A schematic diagram of a task display page provided by an embodiment of the present disclosure, such as Figure 4 As shown in the figure, the task display page displays the identifiers of the pending subtasks associated with the task to be reported "××1". The task display page also displays a selection box for each pending subtask, which is used to select the target abnormal task from the pending subtasks. Figure 4 As shown in the figure, the pending subtasks "××101", "××103", and "××105" are selected, which means that the pending subtasks "××101", "××103", and "××105" are target abnormal tasks. Perform page change operation to display all pending subtasks.

[0082] This embodiment clearly and completely displays information of pending subtasks to the user by displaying a task display page, and quickly identifies target abnormal tasks based on triggering an operation on at least one pending subtask.

[0083] In practical applications, the method further includes: displaying at least one abnormality reason to be selected, so as to determine abnormality information of the target abnormal task based on a triggering operation on the at least one abnormality reason to be selected.

[0084] Specifically, the target abnormal task may include at least one task to be processed and / or subtask to be processed. For the case where the target abnormal task is at least one subtask to be processed, at least one selectable abnormal cause may be displayed on the task display page or on the display screen of the robot. If the number of target abnormal tasks is one, the selectable abnormal cause of the target abnormal task can be directly displayed. If the number of target abnormal tasks is multiple, at least one selectable abnormal cause can be displayed for each target abnormal task respectively. In a specific implementation, after detecting that the corresponding selectable abnormal cause is triggered, abnormal information can be generated for the corresponding target abnormal task based on the correspondence between the selectable abnormal cause and the target abnormal task.

[0085] A schematic diagram of the display interface of the selectable abnormal cause is as Figure 5 shown, and each selectable abnormal cause corresponds to a selection box, so as to determine the abnormal information by performing a selection operation on the selection box. As Figure 5 shown, the selectable abnormal causes may include "less goods / no goods", "goods damaged", "unable to open the box", and "wrong goods". It is possible to select only one selection box, or multiple selection boxes can be selected simultaneously.

[0086] In this embodiment, after the operation of triggering at least one subtask to be processed, the reason why the subtask to be processed is an abnormal task is intuitively and clearly displayed for the user by showing the selectable abnormal cause, which is convenient for the user to make a selection.

[0087] S230. In response to the triggering operation of uploading the target abnormal task, send the task association information and abnormal information of the target abnormal task to the target terminal.

[0088] In order to enable the user to clearly and intuitively view the abnormal information of the target abnormal task, the method further includes: determining the display control corresponding to the target abnormal task on the display screen, and displaying the abnormal information at the preset display position of the display control.

[0089] It should be noted that the display control is used to display the task association information of at least one task to be processed, that is, corresponding to at least one task to be processed. After determining the target abnormal task, the display control corresponding to the target abnormal task information on the display screen can be determined, and the abnormal information of the target abnormal task is displayed at the preset display position of the display control. Among them, the preset display position can be the blank position in the display control.

[0090] In practical applications, when displaying the abnormal information, the abnormal information can be displayed in a text display mode or in a picture mode. Specifically, the display mode of the abnormal information can be determined based on the size of the display range of the preset display position.

[0091] In this embodiment, by displaying the exception information at the preset display position of the display control, the task association information and the exception information of the target exception task are simultaneously displayed in the display control, facilitating the user to intuitively and clearly view the information of the target exception task.

[0092] S240. Receive the feedback information of the target terminal to determine whether the target exception task is a stranded task based on the feedback information; if the target exception task is a stranded task, mark the target exception task and record the target exception task.

[0093] Among them, the feedback information is used to reflect the task attributes of the target exception task, and the task attributes include stranded tasks and non-stranded tasks. For example, in the scenario of station delivery, if the pick-up end fails to normally obtain the object to be delivered after the object to be delivered is delivered to the destination, the task of delivering the object to be delivered is a stranded task.

[0094] In a specific implementation, the target terminal pre-stores the task attributes of the tasks to be processed assigned to the robot. After the target terminal receives the task association information and the exception information of the target exception task, it can determine the task attributes of the target exception task based on the task association information of the target exception task, generate feedback information based on the task attributes, and send the feedback information to the robot. The robot parses the feedback information. If it is determined that the target exception task is a stranded task, it means that the target exception task requires user cooperation for processing. Mark and record the target exception task to wait for the user to process the target exception task. Exemplarily, in the scenario of station delivery, if the target exception task is a stranded task, mark and record the stranded task, and clear the record of the stranded task when it is detected that the object to be delivered corresponding to the stranded task is taken away.

[0095] Furthermore, if it is determined that the target exception task is a non-stranded task, the task association information and the exception information of the target exception task can be sent to the task scheduling system so that the task scheduling system can reassign and process the target exception task, thereby improving the task processing efficiency.

[0096] This embodiment classifies the target exception tasks into stranded tasks and non-stranded tasks, and provides different processing methods respectively, so as to accurately and effectively process the target exception tasks in a timely manner according to the task attributes of the target exception tasks, and improve the task processing efficiency.

[0097] In the above, the embodiments corresponding to the task processing method have been described in detail. In order to make those skilled in the art further clear the technical solution of this method, the following specifically describes it in combination with the scenario of station delivery.

[0098] In actual applications, the robot includes at least one grid for placing pending tasks, each of which includes at least one pending subtask, corresponding to an object to be delivered; the robot also includes a display screen, which includes at least one display control, which is used to display task association information of the pending task placed in the grid, wherein the task association information includes a task identifier and a user identifier of at least one user associated with the pending task.

[0099] Each slot on the robot corresponds to a pending task, and each pending task corresponds to at least one object to be delivered. The objects to be delivered include items to be delivered, such as documents, food, and clothing. In other words, each slot can be used to store at least one object to be delivered. The display screen on the robot can be a touchscreen display, and the display controls on the display screen correspond to the pending tasks.

[0100] In this embodiment, by setting up a grid on the robot, the storage of the objects to be delivered is achieved, and by completing the task processing process, the delivery of the objects to be delivered is achieved.

[0101] In the post delivery scenario of this embodiment, the task processing process is as follows: Figure 6 As shown. Specifically, after the robot initiates an exception report, it can detect whether the exception is an exception generated at the delivery end. If not, the target abnormal task can be outbounded and the reason for the exception can be recorded. If so, the goods corresponding to the target abnormal task can be determined, and whether the reason for the exception is oversize, overweight or lost goods. If it is one of them, the target abnormal task will be determined as a task that does not support robot delivery and marked to avoid the user selecting robot delivery again when placing an order for the second time. If it is not one of the reasons, it can be determined whether the target abnormal task is a task that requires self-pickup. If it is required, the target abnormal task will be marked as abnormally ended. If self-pickup is not required, it is determined whether the target abnormal task is a stranded task. If so, the target abnormal task will be returned and marked as abnormally ended. If it is not a stranded task, the task association information of the target abnormal task can be sent to the task scheduling system to reallocate the target abnormal task.

[0102] In this embodiment, the method also includes: determining the pending tasks to which the target abnormal task belongs based on the server, and determining whether to pull a new task based on the target carrying information and current carrying information of the grid corresponding to the pending task; if a new task is pulled, generating a task pulling instruction and sending it to the task scheduling system, so that the task scheduling system pulls the new task based on the task pulling instruction, and sends the new task to the robot, so that the robot's grid carries the new task.

[0103] The server can be the target terminal or another terminal that has established a communication connection with the target terminal. The server obtains task association information and exception information for the target abnormal task. It should be noted that the target abnormal task can be at least one pending task or at least one pending subtask.

[0104] In a specific implementation, the server can determine the task association information of the target abnormal task and use the pending tasks that match the task association information of the target abnormal task as the pending tasks to which the target abnormal task belongs. For example, if the task association information of the target abnormal task is "××1", the pending tasks with the task association information "××1" are determined to be the pending tasks to which the target abnormal task belongs.

[0105] To improve robot efficiency, when a target exception task occurs, the robot can determine whether the slot corresponding to the pending task to which the target exception task belongs can handle new tasks, thereby improving slot utilization. Specifically, the robot can obtain the target load information and current load information for the slot corresponding to the target exception task. The target load information reflects at least one of the maximum number, maximum weight, and maximum volume of objects that the slot can handle. The current load information reflects at least one of the actual number, weight, and volume of objects currently being handled by the slot.

[0106] In a specific implementation, if the target load information and the current load information meet preset conditions, the new task is determined to be accepted; if the preset conditions are not met, the new task is determined not to be accepted. Specifically, the preset conditions may include at least one of the following conditions: the actual number of items accepted by the slot is less than the maximum number that can be accepted; the actual weight accepted by the slot is less than the maximum weight that can be accepted; or the actual volume accepted by the slot is less than the maximum volume that can be accepted.

[0107] If a new task is requested, the system determines the task information for the new task based on the current and target task information. A task request instruction is generated based on the task information and sent to the task scheduling system. The task information includes at least one of the number, volume, and weight of the new task. Upon receiving the task request instruction, the task scheduling system identifies a pending task that matches the task information as the new task and issues it to the robot, ensuring that the robot's slot is equipped to handle the new task.

[0108] If no new task is pulled, a grid closing message is generated and sent to the robot to perform the grid closing operation.

[0109] Furthermore, after determining the target abnormal task as a task that does not support robot delivery, it is also possible to determine whether an empty opening is generated in the robot. The specific process is as follows: Figure 6As shown in the figure. If a space port is generated, it is determined whether to cancel the pending task to which the target abnormal task belongs, that is, to determine whether the number of target abnormal tasks is equal to the total number of tasks corresponding to the pending task to which the target abnormal task belongs. If they are equal, the pending task to which the target abnormal task belongs is cancelled, the target abnormal task is marked as abnormally ended, the reason for the abnormality is recorded, and a new order is pulled again. If it is less than the total number of tasks, or if no space port is generated, the target abnormal task can be converted into a normal task, and it is determined whether the normal task needs to be pulled again. If so, the task association information of the normal task is sent to the task scheduling system for redrawing; if not, the normal task can be sent to the server, and the server is informed of the reason why the task cannot be dispatched and other information.

[0110] In this embodiment, after the target abnormal task is determined, new tasks can be pulled for the space port based on the information of the space port, thereby improving the utilization rate of the space port and the working efficiency of the robot.

[0111] Figure 7 It is a schematic structural diagram of a task processing device provided by an embodiment of the present disclosure, as Figure 7 shown, the device includes: a control display module 710, a target abnormal task determination module 720, and an information sending module 730.

[0112] The control display module 710 is configured to display at least one display control and an abnormal report control on the display screen of the robot, wherein the display control is used to display the task association information of the pending task;

[0113] The target abnormal task determination module 720 is configured to, in response to a trigger operation on the abnormal report control, display an abnormal task selection page, and determine a target abnormal task based on a trigger operation on the abnormal task selection page, wherein the abnormal task selection page includes at least one display control;

[0114] The information sending module 730 is configured to, in response to a trigger operation of uploading the target abnormal task, send the task association information and abnormal information of the target abnormal task to the target terminal;

[0115] Among them, the abnormal information includes the description information that the target abnormal task has an abnormality.

[0116] Based on the above optional technical solutions, optionally, the abnormal task selection page includes at least one display control and the task association information displayed on the display control;

[0117] The display control of the abnormal task selection page further includes an abnormal reason selection sub-control, and at least one selectable abnormal reason and an abnormal reason editing control are displayed after the abnormal reason selection sub-control is triggered.

[0118] Based on the above optional technical solutions, optionally, the target abnormal task determination module 720 includes:

[0119] an exception information determination submodule, configured to, in response to a triggering operation on an exception cause selection subcontrol, display at least one exception cause to be selected and an exception cause edit control, so as to determine exception information based on the triggering operation on the exception cause to be selected and / or the edit text in the exception cause edit control; and

[0120] The first target abnormal task determination submodule is configured to select the to-be-processed task corresponding to the triggered abnormal cause selection subcontrol as the target abnormal task.

[0121] On the basis of the above optional technical solutions, optionally, the following further aspects are included:

[0122] A task display page display submodule is configured to display a task display page in response to a triggering operation on a display control on an abnormal task selection page, wherein the task display page is configured to present at least one pending subtask associated with the task to be reported, where the task to be reported is the pending task corresponding to the triggered display control;

[0123] The second target abnormal task determining submodule is configured to determine a target abnormal task in response to triggering an operation on at least one to-be-processed subtask presented on the task display page.

[0124] On the basis of the above optional technical solutions, optionally, the following further aspects are included:

[0125] The cause triggering submodule is used to display at least one abnormal cause to be selected, so as to determine abnormal information of the target abnormal task based on a triggering operation on the at least one abnormal cause to be selected.

[0126] On the basis of the above optional technical solutions, optionally, the following further aspects are included:

[0127] The abnormal information display module is used to determine the display control corresponding to the target abnormal task on the display screen and display the abnormal information at the preset display position of the display control.

[0128] Based on the above-mentioned optional technical solutions, optionally, the robot includes at least one grid for placing tasks to be processed, the tasks to be processed include at least one sub-task to be processed, and the sub-task to be processed corresponds to the object to be delivered; the robot also includes a display screen, the display screen includes at least one display control, the display control is used to display task association information of the task to be processed placed in the grid, the task association information includes a task identifier and a user identifier of at least one user associated with the task to be processed.

[0129] On the basis of the above optional technical solutions, optionally, the following further aspects are included:

[0130] A feedback information receiving module, configured to receive feedback information from a target terminal after sending task association information and exception information of a target exception task to the target terminal, so as to determine whether the target exception task is a stranded task based on the feedback information;

[0131] An exception recording module, configured to mark the target exception task and record the target exception task if the target exception task is a stranded task.

[0132] Optionally, based on the above optional technical solutions, it further includes:

[0133] A to-be-processed task determination module, configured to determine a to-be-processed task to which the target exception task belongs based on the server, and determine whether to pull a new task according to the target bearing information and the current bearing information of the grid corresponding to the to-be-processed task;

[0134] A task distribution module, configured to generate a task pulling instruction and send it to the task scheduling system if a new task is pulled, so that the task scheduling system pulls a new task based on the task pulling instruction and distributes the new task to the robot, so that the grid of the robot bears the new task.

[0135] In the technical solution provided by the embodiments of the present disclosure, at least one display control and an exception reporting control are displayed on the display screen of the robot. The display control is used to display the task association information of the to-be-processed task. Through the exception reporting control, when an exception occurs during the execution of the to-be-processed task, an exception task selection page can be displayed in response to a trigger operation on the exception reporting control. The to-be-processed tasks that the robot needs to execute are displayed through the exception task selection page, and a target exception task is determined based on a trigger operation on the exception task selection page. The exception task selection page includes at least one display control; in response to a trigger operation for uploading the target exception task, the task association information and exception information of the target exception task are sent to the target terminal, so that the task association information and exception information are reported to the target terminal through the robot, responding to the exception situation in a timely manner, quickly promoting the processing progress of the to-be-processed task, and achieving the effect of improving the task processing efficiency.

[0136] The task processing device provided by the embodiments of the present disclosure can execute the task processing method provided by any embodiment of the present disclosure, and has corresponding functional modules and beneficial effects for executing the method.

[0137] It should be noted that the various units and modules included in the above device are only divided according to functional logic, but are not limited to the above division, as long as the corresponding functions can be realized; in addition, the specific names of the functional units are only for the convenience of mutual distinction and do not limit the protection scope of the embodiments of the present disclosure.

[0138] Figure 8 This is a schematic diagram of the structure of an electronic device provided by an embodiment of the present disclosure. Figure 8 , which shows an electronic device (eg Figure 8 The terminal device in the embodiments of the present disclosure may include, but is not limited to, mobile terminals such as mobile phones, laptop computers, digital broadcast receivers, PDAs (personal digital assistants), PADs (tablet computers), PMPs (portable multimedia players), in-vehicle terminals (such as in-vehicle navigation terminals), and fixed terminals such as digital TVs and desktop computers. Figure 8 The electronic device shown is only an example and should not limit the functions and scope of use of the embodiments of the present disclosure.

[0139] like Figure 8 As shown, the electronic device 800 may include a processing device (e.g., a central processing unit, a graphics processing unit, etc.) 801, which can perform various appropriate actions and processes according to a program stored in a read-only memory (ROM) 802 or a program loaded from a storage device 808 into a random access memory (RAM) 803. Various programs and data required for the operation of the electronic device 800 are also stored in the RAM 803. The processing device 801, the ROM 802, and the RAM 803 are connected to each other via a bus 804. An edit / output (I / O) interface 805 is also connected to the bus 804.

[0140] Typically, the following devices may be connected to the I / O interface 805: an input device 806 including, for example, a touch screen, a touchpad, a keyboard, a mouse, a camera, a microphone, an accelerometer, a gyroscope, etc.; an output device 807 including, for example, a liquid crystal display (LCD), a speaker, a vibrator, etc.; a storage device 808 including, for example, a magnetic tape, a hard disk, etc.; and a communication device 809. The communication device 809 may allow the electronic device 800 to communicate with other devices wirelessly or by wire to exchange data. Although Figure 8 The electronic device 800 is shown with various devices, but it should be understood that it is not required to implement or possess all of the devices shown. More or fewer devices may be implemented or possessed instead.

[0141] In particular, according to an embodiment of the present disclosure, the process described above with reference to the flowchart can be implemented as a computer software program. For example, an embodiment of the present disclosure includes a computer program product, which includes a computer program carried on a non-transitory computer-readable medium, and the computer program includes a program code for executing the method shown in the flowchart. In such an embodiment, the computer program can be downloaded and installed from the network through the communication device 809, or installed from the storage device 808, or installed from the ROM 802. When the computer program is executed by the processing device 801, the above-mentioned functions defined in the method of the embodiment of the present disclosure are performed.

[0142] The names of the messages or information exchanged between multiple devices in the embodiments of the present disclosure are only used for illustrative purposes and are not used to limit the scope of these messages or information.

[0143] The electronic device provided by the embodiment of the present disclosure and the task processing method provided by the above embodiment have the same concept. For technical details not fully described in this embodiment, please refer to the above embodiment, and this embodiment has the same beneficial effects as the above embodiment.

[0144] An embodiment of the present disclosure provides a computer storage medium on which a computer program is stored. When the program is executed by a processor, the task processing method provided by the above embodiment is implemented.

[0145] It should be noted that the computer-readable medium disclosed above may be a computer-readable signal medium or a computer-readable storage medium or any combination of the above two. The computer-readable storage medium may be, for example, but not limited to, an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, device or device, or any combination of the above. More specific examples of computer-readable storage media may include, but are not limited to: an electrical connection with one or more wires, a portable computer disk, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the above. In the present disclosure, a computer-readable storage medium may be any tangible medium containing or storing a program that may be used by or in combination with an instruction execution system, device or device. In the present disclosure, a computer-readable signal medium may include a data signal propagated in a baseband or as part of a carrier wave, in which a computer-readable program code is carried. This propagated data signal may take a variety of forms, including but not limited to an electromagnetic signal, an optical signal, or any suitable combination of the above. The computer readable signal medium may also be any computer readable medium other than a computer readable storage medium, which may send, propagate or transmit a program for use by or in conjunction with an instruction execution system, apparatus or device. The program code contained on the computer readable medium may be transmitted using any suitable medium, including but not limited to: wires, optical cables, RF (radio frequency), etc., or any suitable combination of the above.

[0146] In some embodiments, the client and server can communicate using any currently known or future developed network protocol, such as HTTP (HyperText Transfer Protocol), and can be interconnected with any form or medium of digital data communication (e.g., a communication network). Examples of communication networks include a local area network ("LAN"), a wide area network ("WAN"), an internet (e.g., the Internet), and a peer-to-peer network (e.g., an ad hoc peer-to-peer network), as well as any currently known or future developed network.

[0147] The computer-readable medium may be included in the electronic device, or may exist independently without being incorporated into the electronic device.

[0148] The computer-readable medium carries one or more programs. When the one or more programs are executed by the electronic device, the electronic device:

[0149] The above computer-readable medium carries one or more programs, which, when executed by the electronic device, cause the electronic device to: display at least one display control and an exception reporting control on the display screen of the robot, where the display control is used to display task-related information of a task to be processed; in response to a trigger operation on the exception reporting control, display an exception task selection page to determine a target exception task based on a trigger operation in the exception task selection page, where the exception task selection page includes at least one display control; in response to a trigger operation for uploading the target exception task, send the task-related information and exception information of the target exception task to a target terminal; where the exception information includes a description information indicating that the target exception task has an exception.

[0150] Computer program code for performing the operations of the present disclosure may be written in one or more programming languages or combinations thereof. The programming languages include, but are not limited to, object-oriented programming languages such as Java, Smalltalk, C++, and also include conventional procedural programming languages such as the "C" language or similar programming languages. The program code may execute entirely on the user's computer, partly on the user's computer, as a stand-alone software package, partly on the user's computer and partly on a remote computer, or entirely on the remote computer or server. In the case of a remote computer, the remote computer may be connected to the user's computer through any type of network, including a local area network (LAN) or a wide area network (WAN), or may be connected to an external computer (e.g., through the Internet using an Internet service provider).

[0151] The flowcharts and block diagrams in the accompanying drawings illustrate the possible architectures, functions, and operations of systems, methods, and computer program products according to various embodiments of the present disclosure. In this regard, each block in the flowchart or block diagram may represent a module, a program segment, or a part of code that contains one or more executable instructions for implementing a specified logical function. It should also be noted that, in some alternative implementations, the functions marked in the blocks may occur in a different order than marked in the accompanying drawings. For example, two consecutive blocks shown may actually be executed substantially in parallel, and they may sometimes be executed in the reverse order, depending on the functions involved. It should also be noted that each block in the block diagram and / or flowchart, and combinations of blocks in the block diagram and / or flowchart, may be implemented by a dedicated hardware-based system for performing the specified functions or operations, or may be implemented by a combination of dedicated hardware and computer instructions.

[0152] The units involved in the embodiments of the present disclosure can be implemented in software or in hardware. Among them, the name of a unit does not constitute a limitation on the unit itself in some cases. For example, the first acquisition unit can also be described as "the unit for acquiring at least two Internet protocol addresses".

[0153] The functions described above in this article can be performed, at least in part, by one or more hardware logic components. For example, without 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 so on.

[0154] In the context of the present disclosure, a machine-readable medium can be a tangible medium that can contain or store a program for use by or in connection with an instruction execution system, apparatus, or device. A machine-readable medium can be a machine-readable signal medium or a machine-readable storage medium. A machine-readable medium can include, but is not limited to, electronic, magnetic, optical, electromagnetic, infrared, or semiconductor systems, apparatus, or devices, or any suitable combination of the foregoing. More specific examples of a machine-readable storage medium would include an electrical connection based on one or more wires, a portable computer diskette, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or Flash memory), an optical fiber, a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing.

[0155] The above description is only for the preferred embodiments of the present disclosure and the description of the applied technical principles. Those skilled in the art should understand that the scope of disclosure involved in the present disclosure is not limited to the technical solutions formed by the specific combination of the above technical features, and should also cover other technical solutions formed by any combination of the above technical features or their equivalent features without departing from the above disclosure concept. For example, the technical solutions formed by mutually replacing the above features with the (but not limited to) technical features having similar functions disclosed in the present disclosure.

[0156] In addition, although the operations are depicted in a particular order, this should not be construed as requiring that the operations be performed in the particular order shown or in sequential order. In certain circumstances, multitasking and parallel processing may be advantageous. Similarly, although several specific implementation details are included in the foregoing discussion, these should not be construed as limitations on the scope of the present disclosure. Certain features that are described in the context of separate embodiments may also be implemented in combination in a single embodiment. Conversely, various features that are described in the context of a single embodiment may also be implemented separately or in any suitable subcombination in multiple embodiments.

[0157] Although the subject matter has been described in language specific to structural features and / or methodological acts, it is to be understood that the subject matter defined in the appended claims is not necessarily limited to the specific features or acts described above. Rather, the specific features and acts described above are merely example forms of implementing the claims.

Claims

1. A task processing method, characterized in that, Applied to a robot, the method includes: Display at least one display control and an exception reporting control on the display screen of the robot, where the display control is used to display task-related information of a task to be processed; In response to a trigger operation on the exception reporting control, display an exception task selection page, and based on a trigger operation on the exception task selection page, determine a target exception task, where the exception task selection page includes the at least one display control; In response to a trigger operation to upload the target exception task, send the task-related information and exception information of the target exception task to a target terminal; Wherein, the exception information includes a description information indicating that the target exception task has an exception.

2. The method according to claim 1, wherein The exception task selection page includes the at least one display control and the task-related information displayed on the display control; The display control on the exception task selection page further includes an exception cause selection sub-control, and after the exception cause selection sub-control is triggered, at least one selectable exception cause and an exception cause editing control are displayed.

3. The method according to claim 2, wherein The determining the target exception task based on a trigger operation on the exception task selection page includes: In response to a trigger operation on the exception cause selection sub-control, display at least one selectable exception cause and an exception cause editing control, and based on a trigger operation on the selectable exception cause and / or the edited text in the exception cause editing control, determine the exception information; and, Take the to-be-processed task corresponding to the triggered exception cause selection sub-control as the target exception task.

4. The method according to claim 2, characterized in that, The method further includes: In response to a trigger operation on the display control on the exception task selection page, display a task display page, and the task display page is used to present at least one to-be-processed subtask associated with the task to be reported, and the task to be reported is the to-be-processed task corresponding to the triggered display control; In response to a trigger operation on at least one to-be-processed subtask presented on the task display page, determine the target exception task.

5. The method according to claim 4, wherein It further includes: Display at least one selectable exception cause, and based on a trigger operation on the at least one selectable exception cause, determine the exception information of the target exception task.

6. The method according to claim 1, wherein It further includes: Determine the display control corresponding to the target exception task on the display screen, and display the exception information at a preset display position of the display control.

7. The method according to any one of claims 1 to 6, characterized in that, The robot includes at least one compartment, and the compartment is used to place the to-be-processed task, and the to-be-processed task includes at least one to-be-processed subtask, and the to-be-processed subtask corresponds to a to-be-delivered object; The robot further includes a display screen, and the display screen includes at least one display control, and the display control is used to display the task-related information of the to-be-processed task placed in the compartment, and the task-related information includes a task identifier and a user identifier of at least one user associated with the to-be-processed task.

8. The method according to claim 1, wherein After sending the task-related information and exception information of the target exception task to the target terminal, the method further includes: Receive the feedback information of the target terminal to determine whether the target abnormal task is a stranded task based on the feedback information; If the target abnormal task is a stranded task, mark the target abnormal task and record the target abnormal task.

9. The method according to claim 1, wherein The method further includes: Determine the to-be-processed task to which the target abnormal task belongs based on the server, and determine whether to pull a new task according to the target bearing information and the current bearing information of the grid corresponding to the to-be-processed task; If a new task is pulled, generate a task pulling instruction and send it to the task scheduling system, so that the task scheduling system pulls a new task based on the task pulling instruction and distributes the new task to the robot, so that the grid of the robot bears the new task.

10. A task processing device, characterized in that, Set in the robot, the device includes: A control display module, configured to display at least one display control and an exception reporting control on the display screen of the robot, where the display control is used to display task association information of the to-be-processed task; A target abnormal task determination module, configured to display an abnormal task selection page in response to a trigger operation on the exception reporting control, and determine a target abnormal task based on a trigger operation on the abnormal task selection page, where the abnormal task selection page includes the at least one display control; An information sending module, configured to send the task association information and the exception information of the target abnormal task to the target terminal in response to a trigger operation of uploading the target abnormal task; Wherein, the exception information includes a description information indicating that the target abnormal task has an exception.

11. An electronic device, characterized in that, The electronic device includes: One or more processors; A storage device for storing one or more programs, When the one or more programs are executed by the one or more processors, the one or more processors implement the task processing method according to any one of claims 1-9.

12. A storage medium containing computer-executable instructions, where the computer-executable instructions are used to execute the task processing method according to any one of claims 1-9 when executed by a computer processor.

Images