Task orchestration methods, robot control methods, and robot control systems

Abstract

This application provides a task scheduling method, a robot control method, and a robot control system. Tasks are scheduled within a control interface that displays task tracks, and each robot is controlled to execute tasks based on these tracks. The visual task tracks provide a clear view of the task execution sequence and its correspondence with the robots, allowing operators to quickly predict spatiotemporal conflicts during task execution. This also prevents resource imbalances caused by mismatches between robot functionalities and tasks, ensuring efficient collaboration among the robots.

Description

Technical Field

[0001] This application relates to the field of robotics technology, specifically to a task scheduling method, a robot control method, and a robot control system. Background Technology

[0002] With the continuous development of the robotics industry and the need for business integration, multi-robot collaborative operations have shown significant advantages over single-robot operations in many scenarios such as industrial production, logistics warehousing, intelligent security, and stage performances. For example, they can greatly improve work efficiency and enhance the reliability and flexibility of the system. Therefore, they have received widespread attention and in-depth research.

[0003] Currently, when assigning tasks to multiple robots that need to work together, tasks are usually assigned to each robot in sequence according to the order of tasks or simple priority rules. During the execution process, resource conflicts or misaligned collaborative actions are likely to occur, resulting in low collaborative efficiency. Summary of the Invention

[0004] In view of this, embodiments of this application provide a task scheduling method, a robot control method, and a robot control system, which can improve the collaborative efficiency of multiple robots working together.

[0005] In a first aspect, embodiments of this application provide a task orchestration method applied to an electronic device. The task orchestration method includes: displaying a control interface, the control interface including a first area, the first area including multiple independent task tracks corresponding to robots, the task tracks being used to allow the robots corresponding to the task tracks to execute tasks corresponding to task components in the task tracks in a time sequence; receiving a task addition instruction, the task addition instruction including the robot corresponding to the task to be added, the task execution time corresponding to the task to be added, and the task execution duration corresponding to the task to be added; generating a task component of the task to be added in the task track of the robot corresponding to the task to be added based on the task execution time and the task execution duration, the position of the task component being used to represent the task execution time, and the length of the task component being used to represent the task execution duration.

[0006] Secondly, embodiments of this application provide a robot control method applied to an electronic device, the electronic device being configured to execute the task orchestration method of the first aspect. The robot control method includes: in response to an execution instruction, sending an operation instruction to the robot corresponding to each task track according to each task track in the control interface, so that the robot receiving the operation instruction executes the task corresponding to the operation instruction.

[0007] Thirdly, embodiments of this application provide a task orchestration device applied to an electronic device. The task orchestration device includes: a display module for displaying a control interface, the control interface including a first area containing multiple independent task tracks corresponding to robots, the task tracks being used to allow the robots corresponding to the task tracks to execute tasks corresponding to task components in the task tracks in a time sequence; a receiving module for receiving a task addition instruction, the task addition instruction including the robot corresponding to the task to be added, the task execution time corresponding to the task to be added, and the task execution duration corresponding to the task to be added; and a generation module for generating a task component of the task to be added in the task track of the robot corresponding to the task to be added, based on the task execution time and the task execution duration, the position of the task component representing the task execution time, and the length of the task component representing the task execution duration.

[0008] Fourthly, embodiments of this application provide a robot control device applied to an electronic device. The robot control device includes an execution module, configured to respond to an execution command and send operation commands to the robots corresponding to each task track according to each task track in the control interface, so that the robots receiving the operation commands execute the tasks corresponding to the operation commands.

[0009] Fifthly, embodiments of this application provide a robot control system, including: an electronic device configured to: in response to an execution command, send operation commands to robots corresponding to each task track according to each task track in a control interface, wherein the control interface includes a first area, the first area containing multiple independent task tracks corresponding to each robot, the task tracks being used to allow the robots corresponding to the task tracks to execute tasks corresponding to task components in the task tracks in a time sequence; and a robot configured to: receive the operation commands sent by the electronic device, and execute the tasks corresponding to the operation commands according to the operation commands.

[0010] In a sixth aspect, embodiments of this application provide an electronic device, including: a processor; and a memory for storing processor-executable instructions, wherein the processor is used to execute the task orchestration method of the first aspect or the robot control method of the second aspect described above.

[0011] In a seventh aspect, embodiments of this application provide a computer-readable storage medium storing a computer program for performing the task orchestration method of the first aspect or the robot control method of the second aspect described above.

[0012] Eighthly, embodiments of this application provide a computer program product, which includes a computer program. When the computer program is executed by the processor of a computer device, it enables the computer device to perform the task scheduling method of the first aspect or the robot control method of the second aspect.

[0013] Ninthly, embodiments of this application provide a chip, including: a processor; and a memory for storing processor-executable instructions, wherein the processor is used to execute the task orchestration method of the first aspect or the robot control method of the second aspect described above.

[0014] This application provides a task orchestration method, a robot control method, and a robot control system. By displaying a control interface that includes independent task tracks corresponding to multiple target robots, task components for the target tasks of the target robots corresponding to each task track are set on each track, and these task components represent the task execution time. Upon responding to execution commands, multiple target robots are controlled based on the multiple task tracks.

[0015] This application presents the relationship between task timing and robot correspondence through a visual task track, enabling staff to quickly predict spatiotemporal conflicts during task execution. It also avoids resource imbalance caused by mismatch between robot functional characteristics and tasks, thus ensuring the collaborative efficiency of each target robot. Attached Figure Description

[0016] Figure 1 The diagram shown is a schematic representation of the system architecture of a robot control system provided in an exemplary embodiment of this application.

[0017] Figure 2 The diagram shown is a flowchart illustrating a task orchestration method provided in an exemplary embodiment of this application.

[0018] Figure 3A The diagram shown is a schematic representation of the control interface provided in an exemplary embodiment of this application.

[0019] Figure 3B The diagram shown is a schematic representation of the control interface provided in an exemplary embodiment of this application.

[0020] Figure 3C The diagram shown is a schematic representation of the control interface provided in an exemplary embodiment of this application.

[0021] Figure 3D This is a schematic diagram of the structure of a task-adding interface provided in an exemplary embodiment of this application.

[0022] Figure 3E This is a schematic diagram of the structure of a control interface provided for an exemplary embodiment of this application.

[0023] Figure 3F This is a schematic diagram of the structure of a control interface provided for an exemplary embodiment of this application.

[0024] Figure 3GThis is a schematic diagram of the structure of a control interface provided for an exemplary embodiment of this application.

[0025] Figure 3H A schematic diagram of the structure of the second region provided for an exemplary embodiment of this application.

[0026] Figure 3I This is a schematic diagram of the structure of a control interface provided for an exemplary embodiment of this application.

[0027] Figure 4 The diagram shown is a flowchart illustrating a robot control method provided in another exemplary embodiment of this application.

[0028] Figure 5 The diagram shown is a flowchart illustrating a robot control method provided in an exemplary embodiment of this application.

[0029] Figure 6A This is a schematic diagram of the structure of a control interface provided for an exemplary embodiment of this application.

[0030] Figure 6B This is a schematic diagram of the structure of a control interface provided for an exemplary embodiment of this application.

[0031] Figure 7 The diagram shown is a structural schematic of a task orchestration apparatus provided in an exemplary embodiment of this application.

[0032] Figure 8 The diagram shown is a schematic representation of the structure of a robot control device provided in an exemplary embodiment of this application.

[0033] Figure 9 The diagram shown is a block diagram of an electronic device for performing a robot control method according to an exemplary embodiment of this application. Detailed Implementation

[0034] The technical solutions of the embodiments of this application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of this application, and not all embodiments. Based on the embodiments of this application, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of this application.

[0035] Application Overview

[0036] With the continuous development of computer technology, the application of multi-robot collaborative operations is becoming more and more widespread. For example, industrial robots collaborate to achieve intelligent management of production lines, self-moving equipment clusters work together to achieve automatic sorting of goods, and agricultural robots collaborate to achieve precision farmland operations, etc.

[0037] Currently, when assigning tasks to multiple robots that need to work collaboratively, a robot list and a task list are typically created first. The task list is created based on the order and priority of the tasks, while the robot list includes all robots used to perform the collaborative tasks. Then, the tasks from the task list are assigned to the idle robots in the robot list.

[0038] However, this task assignment method has limitations. Firstly, simply assigning tasks based on robot idle status fails to fully consider the functional characteristics and execution advantages of each robot. For example, a heavy-duty robot with high load capacity might be assigned a light assembly task, while a robot with high-precision operation capabilities might be assigned a handling task, leading to resource imbalance and reduced overall work efficiency. Secondly, when task progress is displayed in a list format, workers need to mentally perform an abstract conversion between task time sequence and spatial coordinates. In this case, workers cannot fully predict whether spatiotemporal conflicts will occur between robots, resulting in a higher probability of resource conflicts or misaligned collaborative actions, posing safety hazards. Furthermore, when unexpected tasks are inserted, it is often necessary to rebuild the task list and then assign tasks based on the rebuilt list, which is time-consuming.

[0039] In summary, current methods for controlling robots in scenarios involving multi-robot collaborative operations suffer from low collaborative control efficiency.

[0040] This application provides a task orchestration method and a robot control method. Tasks are orchestrated in a control interface with task tracks, and each robot is controlled to execute tasks according to the orchestrated task tracks. The visual task tracks intuitively present the correspondence between task execution sequence and robot performance, allowing operators to quickly predict spatiotemporal conflicts during task execution. This also avoids resource imbalances caused by mismatches between robot functionalities and tasks, ensuring the collaborative efficiency of all robots.

[0041] Exemplary System

[0042] Figure 1 The diagram shown is a schematic representation of the system architecture of a robot control system provided in an exemplary embodiment of this application. Figure 1As shown, the robot control system 100 may include multiple robots 110 and an electronic device 120 including a control interface. The robots 110 may be different types of automated equipment such as humanoid robots, hand-type robots, industrial robotic arms, AGVs (Automated Guided Vehicles), and inspection robots. The electronic device 120, including the control interface, can communicate with the multiple robots 110 via wired or wireless means. For example, the electronic device 120 can transmit operating commands to the robots 110 wirelessly. Wireless communication methods may include Bluetooth communication, Long Range Radio (LoRa) communication, or other wireless communication methods.

[0043] The electronic device 120 provides a control interface for users to adjust various modules or buttons. The control interface includes multiple parallel timeline tracks, which are task tracks. Each task track corresponds to a unique robot, and time scales (e.g., hours / minutes / seconds) are evenly distributed on the tracks. The task components that the robot needs to perform are marked with icons at the corresponding time points.

[0044] Users can add task components corresponding to tasks in the control interface. Then, the electronic device 120 can generate task addition instructions based on the user's operation in the interface, and generate task components for the task to be added in the task track of the robot corresponding to the task to be added based on the robot, the task execution time, and the task execution duration contained in the task addition instructions.

[0045] Users can schedule tasks in the control interface and click the "Execute" button after the task scheduling is completed. The electronic device 120 then sends operation commands to each robot according to the task tracks in the first area. Upon receiving the operation commands, the robot 110 executes the tasks based on the task information contained within the operation commands.

[0046] It should be understood that the above application scenario examples are only shown to facilitate understanding of the spirit and principles of this application, and the embodiments of this application are not limited thereto. Rather, the embodiments of this application can be applied to any applicable scenario.

[0047] Exemplary methods

[0048] Figure 2 The diagram shown is a flowchart illustrating a task orchestration method provided in an exemplary embodiment of this application. Figure 2 The method can be derived from Figure 1 The electronic device 120 in the middle performs the operation. For example... Figure 2 As shown, the task orchestration method may include the following:

[0049] 210: Display control interface. The control interface includes a first area, which contains multiple independent task tracks corresponding to each robot. The task tracks are used to allow the robots corresponding to the task tracks to execute the tasks corresponding to the task components in the task tracks in a time sequence.

[0050] The control interface can be either a touch-based or mouse-based interface. It can be displayed to the user when it receives a display command from another electronic device, or when it detects the user's login or specific actions performed on that electronic device.

[0051] In one example, the first area is a visual workspace in the control interface used for multi-robot task orchestration. Its horizontal dimension can be used to map the physical timeline, and its vertical dimension can be used to distinguish each robot.

[0052] In one example, the first region is arranged horizontally or vertically to construct an independent task track for each robot.

[0053] In one example, for each task track, which is based on a timeline and extends from the start time to the end time, it forms a visual path for the robot's task execution.

[0054] In one example, for each task track, there are task components set in the task track. The task track is used to allow the robot corresponding to the task track to execute the tasks corresponding to the task components in the task track in chronological order along the direction of the task track.

[0055] In one example, the robot corresponding to the task track contained in the first area can be a robot used to perform collaborative tasks. The robot used to perform collaborative tasks can be any robot that can interact with the electronic device, or it can be a robot selected by the user from the robots that can interact with the electronic device.

[0056] 220: Receive task addition instruction. The task addition instruction includes the robot corresponding to the task to be added, the task execution time, and the task execution duration.

[0057] 230: Based on the task execution time and task execution duration, generate the task component of the task to be added in the task track of the robot corresponding to the task to be added. The position of the task component is used to represent the task execution time, and the length of the task component is used to represent the task execution duration.

[0058] In one example, the task-adding instruction could be generated by a module within the electronic device or initiated by another electronic device.

[0059] In one example, the task add instruction is used to add a task component corresponding to the task to be added to the task track. The task add instruction contains information that represents the robot corresponding to the task to be added, the task execution time corresponding to the task to be added, and the task execution duration corresponding to the task to be added.

[0060] In one example, the electronic device can determine the task track on which the task component corresponding to the task to be added needs to be added based on the robot corresponding to the task to be added, and generate the graphic block corresponding to the task to be added in the task track on which the task component corresponding to the task to be added needs to be added based on the task execution duration and the task execution time of the task to be added.

[0061] In one example, if there are multiple robots corresponding to the task to be added, the electronic device can determine that there are multiple task tracks for which the task component corresponding to the task to be added needs to be added, and generate the task component corresponding to the task to be added in each determined task track.

[0062] In one example, task components can be displayed in various forms such as graphic blocks or dots; that is, task components in the form of graphic blocks or dots can be set in the task track.

[0063] In one example, for each task component in the first region, the position of the task component can be used to characterize the task execution time of the task corresponding to the task component, and the length of the task component can be used to characterize the task execution duration of the task corresponding to the task component.

[0064] In one example, the position of the task component can be the center of the corresponding graphic block, or the left edge of the projection of the corresponding graphic block onto the task track. Correspondingly, the length of the task component can be the distance between the left and right edges of the projection of the corresponding graphic block onto the task track.

[0065] This application provides a task orchestration method. By displaying a control interface showing independent task tracks corresponding to multiple robots, it receives a task addition command containing the robot corresponding to the task to be added, the task execution duration, and the task execution time. Based on the task execution duration and time, it generates a task component for the task to be added within the robot's task track in the task correspondence table. The position of the task component represents the task execution time, and the length of the task component represents the task execution duration. This task orchestration method, through a visual and highly interactive task track design, achieves intuitive planning and efficient scheduling of multi-robot tasks, significantly improving the convenience and accuracy of task orchestration and further ensuring collaborative efficiency.

[0066] In addition, when tasks need to be dynamically inserted, this task orchestration method does not require rebuilding the entire task list. The task sequence can be quickly updated by adding task instructions, which greatly reduces the time spent on task orchestration.

[0067] According to one embodiment of this application, the task orchestration method further includes: in response to a user's selection operation on a task component in a first area, determining a specified component and a specified task corresponding to the specified component, and, based on the user's editing operation on the specified component, changing at least one of the length and position of the specified component to update the specified task.

[0068] In one example, the electronic device can monitor operations such as mouse clicks and touch clicks in the control interface. When the user clicks on a task component in the first area, the electronic device can determine that the user has performed a selection operation. If the task component clicked by the user is the task component selected by the user, the electronic device can use the task component selected by the user as the designated component and the task corresponding to the designated component as the designated task.

[0069] In one example, after a user selects a task component, they can edit it. The electronic device can then monitor the user's actions on the task component. If an editing operation is detected, the device can modify at least one of the task component's length and position based on the editing operation, thereby updating at least one of the task's execution time and execution duration.

[0070] In one example, when the control interface is a touch-based interface, the user's touch click on the task component can be a selection operation; when the control interface is a mouse-based interface, the user's mouse click on the task component can be a selection operation.

[0071] In one example, when the control interface is a mouse-based interactive interface, the action of moving the mouse over a task component can also be used as a selection action. The specific type of selection action can be set as needed, and this manual does not limit it.

[0072] In this embodiment, the control interface allows users to flexibly select and edit task components, greatly improving the autonomy and convenience of task scheduling. Users can quickly adjust the task schedule according to actual needs without re-entering task information, reducing operational steps. Simultaneously, the edited task components are displayed in real-time on the task track to provide real-time operational feedback, enabling users to intuitively perceive the task modification process, reducing the probability of operational errors, and ensuring the efficiency and accuracy of task scheduling.

[0073] According to one embodiment of this application, the structure of the control interface can be as follows: Figure 3A As shown, Figure 3A This is a schematic diagram of the control interface provided in an exemplary embodiment of this application. As can be seen, the first area of ​​the control interface includes multiple task tracks corresponding to different robots. For each task track, there are task components for the task that the robot corresponding to that track needs to perform. The number of task components in a task track can be one or more.

[0074] A timeline is set below the first area. For each task component, the projection position of the left edge of the task component on the timeline corresponds to the task execution time, and the projection position of the right edge corresponds to the task termination time. The length of the task component is the task execution time of the task corresponding to the task component.

[0075] In one example, the shape of the task component can be an ellipse, rectangle, rounded rectangle, or a very narrow rectangle (i.e., a line segment). The specific shape of the task component can be set as needed, and this specification does not impose any restrictions on it.

[0076] In one example, regardless of the shape of the task component, the projection position of its leftmost edge on the time axis can represent the task execution time of the task corresponding to the task component, the projection position of the right edge can represent the task termination time of the task corresponding to the task component, and the length of the task component (i.e., the distance between the projection positions of the left and right edges) can represent the task execution duration of the task corresponding to the task component.

[0077] In one example, for each task track in the first region, the task track can be a long strip of area defined by two parallel lines (e.g., Figure 3A As shown in the image), it can also be a separate line (such as...). Figure 3A (Any of the black solid lines shown that are parallel to the time axis).

[0078] In one example, when the task track is a single line, the bottom edge of the task component within that track can be aligned with the track itself. Alternatively, task components can be symmetrically distributed along the task track's central axis. For instance, the focus (or center) of an elliptical task component might be located within that task track.

[0079] In one example, the tasks performed by each robot can be of the same type or different types. Even when performing the same type of task, the length of the task component corresponding to the same type of task may not be the same in the task tracks of different robots. In other words, the task execution time may not be the same.

[0080] by Figure 3ATaking robots 1 and 3 as examples, although both robots need to perform tasks of type 1, the tasks they need to perform are different in terms of both the task execution time and the task execution duration.

[0081] certainly, Figure 1 The example shown here only uses task type as the display item for task components. In practical applications, each task component can be assigned a unique task identifier, which can then be displayed as the task component's display item. The specific data types and content included in the display items on the task components can be set as needed, and this manual does not impose any restrictions on this.

[0082] According to one embodiment of this application, the editing operation includes at least one of drag-and-drop, zoom, and delete operations. The task arrangement method further includes: if the editing operation is a drag-and-drop operation, determining the drag direction and drag distance based on the user's drag operation on the specified component, and adjusting the position of the specified component based on the drag direction and drag distance; if the editing operation is a zoom operation, adjusting the length of the specified component based on the user's zoom operation on the specified component; if the editing operation is a delete operation, deleting the specified component from the task track where the specified component is located based on the user's delete operation on the specified component.

[0083] In one example, if the user's editing operation is a drag-and-drop operation, the electronic device can calculate the horizontal distance the user-selected task component (i.e., the specified component) moves along the task track while the user is dragging, and change the position of the specified component in the interface based on the horizontal distance and direction of movement. Thus, the changed position is the position of the task component after the user has completed the drag-and-drop operation.

[0084] In one example, as the user performs a drag operation, the electronic device can convert the movement distance into a time value according to the time axis scale, and update the task information of the specified task in real time based on the movement direction and time value. This task information may include the task execution time.

[0085] In one example, after the user performs a drag-and-drop operation, the electronic device can redetermine the task information of the specified task based on the task component after the position has changed. The task information may include at least one of the task execution time and task execution duration.

[0086] In one example, the user's drag-and-drop operation on a task component is as follows: Move the mouse pointer to the task component corresponding to the task, click the left mouse button (or click and hold the task component on the touchscreen of an electronic device). The task component will then slightly highlight or its border will change color, indicating that it has entered draggable mode. While keeping the mouse button pressed (or your finger on the screen), move the mouse horizontally (or slide your finger across the screen), and the task component will follow. Once the task component reaches the desired position, release the mouse button (or lift your finger from the screen), and the task execution time will be updated to the time at the corresponding position, and the task component will be fixed in the new position.

[0087] In one example, the slight highlighting or border color change of the task component to indicate that the task component has entered a draggable state is merely illustrative. The specific representation when a task component enters a draggable state can be set as needed, and this specification does not impose any limitations on it. Figure 3B As shown.

[0088] Figure 3B This is a schematic diagram of the control interface provided in an exemplary embodiment of this application. The diagram illustrates the example of a user dragging and dropping a task component corresponding to task 1, where task 1 is the specified task, and the task component corresponding to task 1 is the specified component. Figure 3B In the upper operation interface, the solid rectangle marked with Task 1 is the original position of the specified component, and the dashed rectangle marked with Task 1 can be the specified component whose position changes with the user's drag operation.

[0089] When a user performs a drag-and-drop operation, the control interface can retain the original position of the specified component and generate a dashed rectangle in real time for dynamic preview based on the user's drag-and-drop operation. The position of the dashed rectangle is updated as the user drags and drops, intuitively presenting the expected time schedule after the task adjustment.

[0090] exist Figure 3B The lower part of the interface shows the rectangle marked "Task 1" as the final position of the specified component after the user completes the drag-and-drop operation.

[0091] Of course, when the user performs a drag-and-drop operation, the control interface can directly display the expected time schedule after the task adjustment through solid-line rectangles whose positions are updated with the movement of the mouse or finger. That is, the control interface only contains solid-line rectangles labeled "Task 1," and the position of these rectangles changes with the user's drag-and-drop operation. After the user finishes dragging, the rectangles are fixed in their new positions. The specific screen displayed on the control interface when the user performs a drag-and-drop operation can be configured as needed; this manual does not impose any restrictions on this.

[0092] In one example, when the user performs a drag-and-drop operation, that is, when the task component is dragged, the control interface can also display a prompt message in real time near the task component, such as "The task execution time will be adjusted to: 15:30:00".

[0093] In one example, if the editing operation performed by the user is a zoom operation, the electronic device can adjust the length of the specified component according to the user's zoom operation on the specified component when the user performs the zoom operation.

[0094] In one example, the user's zooming action on a task component can be manifested as follows: moving the mouse pointer to the task component corresponding to the task, clicking the left mouse button (or clicking and holding the task component on the touch screen of an electronic device), at which point the task component will be slightly highlighted or its border will change color, indicating that it has entered the selected state. Keeping the mouse button pressed down (or keeping the finger on the screen), moving the mouse wheel (or pinching with two fingers) will change the length of the task component accordingly.

[0095] In one example, the scaling operation can change only the length of the task component and the position of its right edge, without changing the position of its left edge.

[0096] In one example, once the length of the task component is adjusted to the desired length, releasing the mouse button (or lifting the finger off the screen) will update the task execution duration to the corresponding duration, and the task length will also be fixed at the updated length.

[0097] In one example, if the user performs a delete operation, the electronic device can remove the corresponding execution component (i.e., the task component corresponding to the specified task) from the task track after the user performs the operation, and at the same time delete the relevant record of the execution task from its own stored data.

[0098] In one example, a user can delete a task component by right-clicking the task component (or long-pressing the task component on an electronic device). This will bring up an operation menu, where the user can select the "Delete Task" option to complete the deletion operation.

[0099] In this embodiment, the control interface provides diverse editing operations such as dragging, zooming, and deleting, offering users precise and efficient task adjustment methods. Through an intuitive graphical interface, users can quickly optimize task scheduling and manage tasks without complex command inputs or menu operations, thus improving the flexibility and reliability of task scheduling for multi-robot collaborative operations.

[0100] According to one embodiment of this application, the task orchestration method further includes: when the scaling operation is a first drag operation on the left edge of a specified component, adjusting the position of the left edge according to the first drag operation to adjust the position and length of the specified component; when the scaling operation is a second drag operation on the right edge of a specified component, adjusting the position of the right edge according to the second drag operation to adjust the length of the specified component.

[0101] In one example, the user can also zoom in and out of a task component by dragging it along its left and right edges.

[0102] In one example, users can zoom in and out of a task component by hovering the mouse pointer over its left or right edge. When the pointer changes to a double-headed arrow, clicking and holding the left mouse button while dragging (or, on a touchscreen device, long-pressing and sliding along the edge of the task component). Dragging the right edge to the left shortens the task component, reducing its execution time; dragging to the right lengthens it. Releasing the mouse (or finger) updates the task execution time. Figure 3C As shown.

[0103] Figure 3C This is a schematic diagram of the control interface provided for an exemplary embodiment of this application. The diagram illustrates the example of a user performing a zoom operation on a task component corresponding to task 1, where task 1 is the specified task. Figure 3C In the upper part of the interface, the solid rectangle marked with Task 1 represents the specified component before the scaling operation was performed.

[0104] The image shows an example of a user dragging the right edge of a specified component to perform a zoom operation. When the user performs the zoom operation, the control interface generates a dashed border in real time to provide a dynamic preview based on the zoom operation performed by the user. The position of the dashed rectangle is updated as the mouse or finger moves to present the expected time schedule after the task adjustment.

[0105] exist Figure 3C In the lower part of the interface, after the zoom operation is completed, the specified component is finally displayed as a solid-line rectangle. Of course, when the user performs a zoom operation, the control interface can directly display the expected time schedule after the task adjustment by updating the position of the solid-line border as the mouse or finger moves. The screen displayed on the control interface when the user performs a zoom operation can be set as needed; this manual does not impose any restrictions on this.

[0106] In one example, when the user performs a zoom operation, the control interface can also dynamically display the adjusted duration value near the task component, such as "Task execution time adjusted to: 25 minutes".

[0107] In one example, users can also drag the left edge of a task component to perform a scaling operation, similar to the operation for the right edge. Furthermore, dragging the left edge to the left increases the length of the task component, extending the task execution time and advancing the execution time; dragging to the right shortens the task component, shortening the task execution time and delaying the execution time. In other words, if a user drags the right edge of a task component to perform a scaling operation, only the length of the task component needs to be adjusted based on the scaling direction and distance to update the task execution time. If the user drags the left edge of a task component to perform a scaling operation, not only the task execution time needs to be updated, but the task execution time also needs to be updated based on the position of the left edge after the drag.

[0108] In this embodiment, users can precisely adjust the position and length of components by dragging their edges, meeting the needs of fine-grained editing. Compared to overall scaling, this allows for more detailed layout adjustments.

[0109] According to one embodiment of this application, the task orchestration method further includes: responding to a user's task addition operation, displaying a task addition interface, and determining the robot corresponding to the task to be added, the task execution duration corresponding to the task to be added, and the task execution time corresponding to the task to be added based on the user's editing operation on the task addition interface, so as to generate a task addition instruction.

[0110] In one example, the control interface may have a task addition button, and the task addition operation can be a click operation performed by the user on the task addition button in the control interface.

[0111] In one example, users can also trigger the task addition action by using keyboard shortcuts, allowing the electronic device to detect the user's task addition action.

[0112] In one example, when an electronic device detects a user adding a task, it can display a task addition interface. This interface provides clear input fields and options, such as a robot dropdown selection box, an execution duration input box, and an execution time input box. Figure 3D As shown.

[0113] Figure 3D This is a schematic diagram of a task addition interface provided in an exemplary embodiment of this application. This interface pops up when the electronic device detects a user's task addition operation. The task addition interface includes four categories: task type, robot, execution duration, and execution time, allowing the user to edit the task information of the task to be added.

[0114] Regarding task type, users can select the task type to add from a variety of task types via a drop-down menu. Figure 3D The task type is "Task 1".

[0115] For the robots, each robot is presented in a list format. Figure 3D The available options are Robot 1, Robot 2, and Robot 3. Robot 2 and Robot 3 are grayed out and are the robots selected by the user. In other words, among the robots, Robot 2 and Robot 3 are the robots used to perform the task to be added, or Robot 2 and Robot 3 are the robots corresponding to the task to be added.

[0116] Users can set the execution time by editing the input box to the right of the execution time. Figure 3D The value displayed is "10s", which means that the task to be added will take 10 seconds to execute.

[0117] For the execution time, users can edit the input box to the right of the execution time to set the time when the task starts execution. Figure 3D The message "After 5 seconds" indicates that the task to be added will begin execution in 5 seconds.

[0118] In one example, the task addition interface can be displayed in one of the following forms: a floating pop-up, a sidebar, or a details panel.

[0119] In one example, Figure 3D The categories included in the task addition interface are for illustrative purposes only. The specific structure of the task addition interface and the specific categories included in the task addition interface can be set as needed.

[0120] In one example, the electronic device can determine the target robot, execution duration, and execution time of the task to be added based on the user's editing operations on the task addition interface. Then, based on the determined target robot, execution duration, and execution time, a task addition instruction is generated.

[0121] In one example, the task addition instruction may also include information that characterizes the task type to be added.

[0122] In one example, the electronic device can also store the target robot corresponding to the task to be added, the task execution duration corresponding to the task to be added, and the task execution time of the task to be added. When the task addition conditions are met, a task addition instruction is generated.

[0123] In one example, the task condition could be reaching a preset time.

[0124] In one example, after determining the robot corresponding to the task to be added, the task execution duration, and the task execution time, the electronic device can also verify the data determined above to avoid resource conflicts, such as when the task to be added partially overlaps with existing tasks in the task track.

[0125] In this embodiment, users can quickly complete task creation and arrangement through intuitive interface operation. The electronic device can automatically generate task components and accurately add them to the task track, ensuring the visual presentation and standardized management of new task information, making task arrangement more efficient and orderly.

[0126] According to one embodiment of this application, the task orchestration method further includes: in response to a user's selection operation of a task component in a first area, determining a specified component and a specified task corresponding to the specified component; and displaying the task information of the specified task in a floating window in the area surrounding the specified component, wherein the task information includes at least one of task type, task execution time, and task execution duration.

[0127] When a user selects a task component, the electronic device can directly identify the selected component as the designated component and set the corresponding task as the designated task. The task information for that designated task is then displayed to the user.

[0128] In one example, the task information for a specified task can be displayed in the area surrounding a specified component. This area can be a certain range of blank space around the outer edge of the specified component. It is typically located above, below, to the left, or to the right of the specified component, maintaining a distance of 5-20 pixels from the edge of the specified component, and avoiding other interface elements as much as possible to ensure that the floating window is not obstructed and that the content is clearly visible.

[0129] In one example, the floating window is a visual container that is independent of the regular layout of the page. It uses various means such as slight shadows and changing the background color of the floating window to visually distinguish it from the main interface, so as to centrally display specific information (task information in this application).

[0130] In one example, the electronic device can obtain the coordinate position of a specified component in the control interface, determine the surrounding area of ​​the specified component based on the position of the specified component, and display the task information of the specified task in the surrounding area of ​​the specified component in the form of a floating window.

[0131] In one example, the task information includes at least one of the following: task type, task execution time, and task execution duration.

[0132] In this embodiment, there is no need to search through a complex task list. The task information of the corresponding task can be obtained directly by selecting the task component, which reduces the operation steps and allows users to intuitively understand the task information. This significantly improves the efficiency of information acquisition, especially in multi-robot collaborative scenarios.

[0133] According to one embodiment of this application, the control interface further includes a second area, which includes robot components corresponding to multiple robots, and the robot components are used to display the robot names. Figure 3E As shown.

[0134] Figure 3E This is a schematic diagram of the structure of a control interface provided for an exemplary embodiment of this application. In the diagram, the control interface includes a first area and a second area. The second area contains multiple robot components corresponding to different robots, and each robot component displays its name. The first area contains task tracks corresponding to a single robot.

[0135] In one example, the robot component can also be used to display at least one of robot type and robot state, such as Figure 3F As shown.

[0136] Figure 3F This is a schematic diagram of the control interface provided for an exemplary embodiment of this application. The diagram illustrates an example where the robot component is also used to display the robot's status, which may include at least one of battery level, location, and network connectivity. The diagram also uses the example of the robot status including these three types of data. Figure 3E similar, Figure 3F The control interface shown includes a first area and a second area. The second area contains multiple robot components corresponding to each robot. These robot components are used to display the robot's name and status. The first area contains task tracks that correspond one-to-one with each robot.

[0137] In one example, the order of the robots in the second region can be the same as the order of the corresponding task tracks of the robots in the first region (e.g., ...). Figure 3F As shown), it can also be in the reverse order (such as...). Figure 3F The task tracks in the first area are arranged from top to bottom in the order of Robot 3, Robot 2, and Robot 1.

[0138] In one example, there is no correlation between the order of the robots in the second region and the order of the corresponding task tracks of the robots in the first region.

[0139] In this embodiment, displaying robot components in the second area helps users accurately match tasks with execution robots during task scheduling and monitoring, improving the accuracy and efficiency of operations. At the same time, it optimizes the interface design of the control interface, making the interface layout more reasonable and the information display more orderly.

[0140] According to one embodiment of this application, in the control interface, the color of the robot component corresponding to the same robot and the color of the task component in the task track are the same color, while the colors of the robot components corresponding to different robots are different colors.

[0141] In the control interface, the robot components and task tracks of different robots can be distinguished by color, such as... Figure 3G As shown.

[0142] Figure 3G The schematic diagram of the control interface provided for an exemplary embodiment shows that, for the same robot, the color of the robot component located in the second area is the same as the color of the task component located in the task track in the first area. However, for different robots, the colors of the robot components are different, and the colors of the task components in the task track are also different.

[0143] In other words, different colors can be used to distinguish different robots in the control interface.

[0144] In this embodiment of the application, by unifying the colors of the same robot components and task tracks and distinguishing different robot colors, efficient visual recognition is achieved, operational confusion is reduced, and interface clarity and task management convenience are improved.

[0145] According to one embodiment of this application, the task orchestration method further includes: in response to a user's selection operation of robot components in two regions, determining multiple target robots from multiple robots for performing cooperative operations, and generating a task track corresponding to each target robot in a first region, wherein the first region contains task tracks corresponding one-to-one with the multiple target robots.

[0146] In one example, the second area contains robot components corresponding to multiple robots.

[0147] In one example, for each robot component in the second area, the robot component can be designed as an interactive card-style button, with the card labeled with at least one of the robot's name, type, and status information.

[0148] In one example, for each robot component in the second region, a selection box may be provided on the robot component for selecting that robot component.

[0149] In one example, the control interface is as follows: Figure 3H As shown, Figure 3H This is a schematic diagram of the structure of a second region provided for an exemplary embodiment of this application. The left side of the figure shows the second region where the robot component is designed as an interactive card-style button, and the right side shows the second region where the robot component is designed to contain a selection box for selecting the robot component.

[0150] In one example, users can select a robot by clicking on the card-style buttons or checkboxes in the second area using a mouse or their finger. The robot selected by the user is the target robot, which is used to perform the collaborative operation.

[0151] exist Figure 3H In the second area on the left, the grayed-out robot component corresponds to the target robot selected by the user. In the second area on the right, the grayed-out robot component with a selection box corresponds to the target robot.

[0152] In one example, after the target robot is identified, the electronic device generates a corresponding task track for each selected robot (the target robot) in the first area of ​​the control interface. For instance, it draws a horizontal bar representing the task arrangement for robot 2, upon which task components can be added later. Figure 3I As shown.

[0153] Figure 3I This is a schematic diagram of a control interface provided for an exemplary embodiment of this application. The control interface includes a first area and a second area. The robot components in the second area are illustrated using interactive cards as an example. As can be seen, the user selects robot components 2 and 3 from the robot components corresponding to robots 1, 2, and 3 respectively. That is, based on the user's robot selection operation, robots 2 and 3 can be identified as target robots. Therefore, after the robots are identified, the electronic device can generate a task track corresponding to each target robot in the first area of ​​the control interface.

[0154] Figure 3I The first area contains the task tracks corresponding to Robot 2 and Robot 3 respectively. The task track corresponding to Robot 2 is the task track for which no task component has been added yet, while the task track corresponding to Robot 3 is the task track for which the task component corresponding to the task to be performed by Robot 3 has been added.

[0155] In one example, the task tracks in the first region contain only task tracks that correspond one-to-one with multiple target robots.

[0156] In this embodiment, the user can autonomously select robots and dynamically generate task tracks, significantly improving the system's flexibility and personalization. Users can flexibly select robots to participate in collaborative operations based on actual operational needs, without being limited to pre-set fixed combinations, thus enabling diverse task arrangements. Simultaneously, the intuitive and visual task track generation method makes the correspondence between tasks and robots clearer, facilitating task allocation and management, effectively improving the planning efficiency of multi-robot collaborative operations, and reducing operational complexity and the probability of errors.

[0157] According to one embodiment of this application, the task orchestration method further includes: receiving a robot addition instruction, the robot addition instruction including the robot name corresponding to the robot to be added, and generating a robot component of the robot to be added in a second area based on the robot name.

[0158] In one example, the electronic device can receive a robot addition instruction, which may include information representing the robot name to be added. Then, based on the robot name value in the robot addition instruction, the electronic device can generate the robot component for the robot to be added in a second area.

[0159] In one example, the electronic device can generate robot addition instructions based on the user's robot addition operation.

[0160] In one example, the robot's additional instructions could be sent by other electronic devices to the electronic device performing the task orchestration method.

[0161] In one example, the control interface may include a robot addition button, and the task addition operation can be performed by the user clicking the robot addition button on the control interface.

[0162] In one example, users can also trigger the robot addition action by using keyboard shortcuts, allowing the electronic device to detect the user's robot addition action.

[0163] In one example, when the electronic device detects a user's robot addition action, a robot addition interface can pop up. This interface provides a concise and clear input area, guiding the user to enter the name of the robot to be added. It also allows setting input format prompts (such as allowing only combinations of letters, numbers, and underscores, with a length not exceeding 10 characters) to help the user enter the correct information.

[0164] In one example, the robot adding interface may also include a button to select the robot type. Therefore, the robot adding command may also include information representing the robot type. The electronic device can then generate the corresponding robot component for the robot to be added in the second area based on the robot type and robot name.

[0165] In one example, after a user enters a robot name on the robot addition interface, the electronic device can validate the entered name. Validation rules may include: whether the name conforms to a preset format, whether it is a duplicate of an existing robot name, and whether it contains illegal characters. If the entered name does not meet the requirements, the electronic device can provide error information to the user through an on-screen prompt, requesting re-entry; if the entry meets the requirements, the system records and saves the name and creates a basic information entry for the robot in the background database, preparing for subsequent task allocation and management.

[0166] In this embodiment, robots can be easily added to the control interface, greatly enhancing its scalability and adaptability. Whether adding equipment due to business expansion or replacing a faulty robot, users can complete the addition through simple operations without complex reconfiguration.

[0167] Figure 4 The diagram shown is a flowchart illustrating a task orchestration method provided in another exemplary embodiment of this application. Figure 4 The example is Figure 2 Examples of the embodiments are provided below; to avoid repetition, the similarities can be referred to the descriptions in the above embodiments, and will not be repeated here. For example... Figure 4 As shown, the task orchestration method may include the following:

[0168] 410: Display control interface, which includes a first area and a second area, wherein the second area contains robot components of multiple robots.

[0169] 420: In response to the user's robot selection operation, determine each target robot from multiple robots, and generate the corresponding task track for each target robot in the first area.

[0170] 430: In response to the user's task addition operation, display the task addition interface and generate task addition instructions based on the user's editing operation in the task addition interface.

[0171] 440: Based on the task addition instruction, generate the task component corresponding to the task to be added in the task track of the target robot corresponding to the task to be added.

[0172] 450: In response to the user's selection of a task component in the first area, the specified task is determined and the task information of the specified task is displayed to the user.

[0173] 460: Based on the user's editing operation on the task component corresponding to the specified task, update at least one of the task execution time and task execution duration of the specified task.

[0174] In this embodiment, the specific structure of the first and second regions of the control interface, the contents of the robot components in the first region, how to determine the target robot from multiple robots, how to set the track of the target robot in the second region, and the interaction logic corresponding to the buttons set in the first and second regions can all be found in the description of steps 210-230 above, and will not be repeated here.

[0175] In this embodiment, the control interface allows users to flexibly select and edit task components, greatly improving the autonomy and convenience of task scheduling. Users can quickly adjust the task schedule according to actual needs without re-entering task information, reducing operational steps. Simultaneously, the edited task components are displayed in real-time on the task track to provide real-time operational feedback, enabling users to intuitively perceive the task modification process, reducing the probability of operational errors, and ensuring the efficiency and accuracy of task scheduling.

[0176] This embodiment also provides a robot control method, such as Figure 5 As shown, Figure 5 The method can be executed by an electronic device, which is the same electronic device as the one used in the aforementioned task orchestration method. Specifically, the robot control method may include the following:

[0177] 510: In response to the execution command, according to each task track in the control interface, send operation commands to the robots corresponding to each task track, so that the robots that receive the operation commands can execute the tasks corresponding to the operation commands.

[0178] In one example, the electronic device may pre-store execution conditions. When the execution conditions are met, the electronic device can generate an execution instruction. These execution conditions could include reaching a certain time, the number of tasks on the first interface reaching a preset threshold, etc.

[0179] In one example, the electronic device can extract information about the task trajectory of each robot, obtaining information such as the task type, task description, and task execution time for each task that the robot needs to perform—that is, obtaining the task information for each task. Then, based on the task information for each task that the robot needs to perform, operation instructions are generated and sent to the robot.

[0180] In one example, after receiving an operation command, the robot can execute each task sequentially according to the task information in the operation command and in chronological order.

[0181] In one example, for a robot, the operation instruction sent to the robot by the electronic device can include task information for all tasks the robot needs to perform, or it can only include task information for the task the robot currently needs to perform. That is, the electronic device can directly generate an operation instruction based on the task information for all tasks the robot needs to perform. Alternatively, for each task the robot needs to perform, an operation instruction containing only the task information for that specific task can be sent to the robot.

[0182] In this embodiment, the specific structure of the control interface and the structure of the task components included in the task track can be found in the description of steps 210-220 above, and will not be repeated here.

[0183] In this embodiment, upon receiving the execution command, operation instructions are sent to the robots corresponding to each task track according to the task tracks in the control interface. This allows the robots receiving the operation instructions to execute tasks sequentially according to time. This robot control method can accurately allocate tasks based on task tracks, ensuring orderly execution by the robots, thereby achieving efficient resource utilization and system load balancing, further guaranteeing the efficiency of multi-robot collaboration.

[0184] According to one embodiment of this application, the robot control method further includes: during the process of controlling the robot to perform a task, displaying a time marker of the current moment in a first area of ​​the control interface, the time marker passing through each task track in the first area, and displaying each task component in each task track in a display manner with different degrees of prominence, wherein the prominence of task components that have overlapping parts with the time marker is higher than the prominence of task components that do not have overlapping parts with the time marker.

[0185] In one example, after receiving an execution instruction, the electronic device can obtain the current time in real time through the system clock or other time acquisition mechanisms.

[0186] In one example, the electronic device can display the acquired current time as a time marker in the task track area of ​​the first region. For example, it could be a vertical line running through all task tracks, visually indicating the current position.

[0187] In one example, the electronic device can determine whether there is an overlap between the task component and the time marker for each task component. If there is, the salience of the task component is adjusted so that the salience of the task component is higher than that of task components that do not overlap with the time marker.

[0188] In one example, an electronic device can increase the prominence of a task component by increasing its border width, adjusting its color, or other means.

[0189] In one example, task components that do not overlap with the time markers can retain their original display style. For example... Figure 6A As shown.

[0190] Figure 6A This is a schematic diagram of the control interface provided in an exemplary embodiment of this application. The diagram includes the task tracks corresponding to robots 1, 2, and 3, respectively. The current time marker is a vertical line that runs through all task tracks. Based on the judgment result of whether there is an overlap between the task components and the time marker, it can be determined that there is an overlap between the task components and the time markers corresponding to task 4 and task 5.

[0191] Therefore, the electronic device can adjust the salience of the task components corresponding to task 4 and task 5 so that the salience of the task components corresponding to task 4 and task 5 is higher than the salience of other task components.

[0192] In one example, as the current time marker moves, the task components that overlap with the time marker also change, for example, from task 4 and task 5 to task 6.

[0193] In this embodiment of the application, by displaying real-time moving time markers on the control interface and displaying task components that overlap with the time markers with varying degrees of differentiation, the task progress can be made intuitively visible, thereby enabling clear acquisition of information such as the robot's status.

[0194] According to one embodiment of this application, the robot control method further includes: expanding the width of the task component so that the width of the task component is greater than that of other task components in the task track where the task component is located.

[0195] In one example, an electronic device can adjust the prominence of a task component by expanding its width.

[0196] In one example, when there is overlap between a task component and a time marker, the electronics can expand the width of the task component to n times the average width of other task components in the task track on which the task component resides. Here, n is greater than 1.

[0197] In one example, for task components that overlap with time markers at the same time and are located on different task tracks, the distance between task components will approach as their width expands.

[0198] In one example, the control interface can have different display layers, with the uppermost display layer having higher prominence than the lowermost. Therefore, the electronic device can also change the prominence of a task component by adjusting its display layer. For example, when there is overlap between a task component and a time marker, the task component can be moved from its current display layer to a higher priority display layer.

[0199] In this embodiment, by dynamically expanding the width of the task component that overlaps with the time marker, a sharp visual contrast is formed between the task component that overlaps with the time marker and other task components, thereby achieving the purpose of highlighting key tasks and intuitively presenting task progress.

[0200] According to one embodiment of this application, the control interface includes a robot component, which is used to display the robot status. The robot control method further includes: for each robot in each task track, determining the task being executed by the robot based on the current time and the task component in the task track corresponding to the robot; determining the robot status of the robot based on the task being executed by the robot; and updating the robot component of the robot based on the determined robot status.

[0201] In one example, the robot's status may include at least one of the following: battery level, location, network status, currently performing task, and whether it is idle. Battery level refers to the robot's remaining battery power, location status indicates whether the robot's positioning is accurate or successful, and network status indicates whether the robot has successfully connected to a network or the specific type of network the robot is connected to (e.g., wired, wireless, etc.).

[0202] In one example, the electronic device continuously monitors the current moment and scans the task components (i.e., each task) on the task track of each robot in the first region. Based on the scan results, it determines the task the robot is currently performing, and based on the task being performed, it determines the robot state, and then updates the robot components accordingly. Figure 6B As shown.

[0203] Figure 6BThis is a schematic diagram of the control interface structure shown in an exemplary embodiment of this application. Taking the current time as an example (indicated by the dashed line in the first region), the electronic device can determine the task being executed by each robot based on the current time and the multiple tasks corresponding to that robot (i.e., the tasks corresponding to all task components in the task track corresponding to that robot). In the diagram, for robot 1, the electronic device can determine whether the execution time periods of task 1 and task 2 include the current time; for robot 2, the electronic device can determine whether the execution time periods of task 1, task 2, and task 3 include the current time; and for robot 3, the electronic device can determine whether the execution time periods of task 1 and task 2 include the current time.

[0204] Then, the electronic equipment can determine the task being performed by each robot based on the judgment result. For example, robot 1 is performing task 1, robot 2 currently has no task in progress and its execution status is idle, and robot 3 is performing task 3.

[0205] Finally, electronic devices can determine the robot's state based on the task the robot is performing.

[0206] In one example, the robot state could include the task the robot is performing.

[0207] In one example, the robot state includes the task the robot is currently executing, the length of the task's execution period, and the next task. Taking robot 1 as an example, the state of robot 1 could include "Task 1 (8s) → Task 2 (4s)", which means that robot 1 is in a busy state, currently executing task 1, and will subsequently execute task 2, with the estimated execution time marked for each.

[0208] In one example, after determining the robot's state, the electronic device can update the robot components in the control interface based on the robot's state. That is, it updates the content in the robot components that represents the robot's state.

[0209] In one example, the task the robot is performing can be displayed in various ways, such as highlighting. Figure 6B In the second area, robot 1 performs task 1, and robot 3 performs task 2.

[0210] In one example, a user can select a robot by checking the checkboxes near the robot icons in the second area.

[0211] In this embodiment, users can intuitively and clearly understand through the second area whether each robot is currently performing a task, what task it is performing, and the subsequent task arrangements, making the entire task execution process transparent and facilitating the monitoring of the overall work progress.

[0212] It should be understood that the execution order of the above steps can be adjusted according to actual needs.

[0213] Exemplary device

[0214] This application embodiment also provides a robot control system, including: an electronic device and a robot. The electronic device is used to: respond to execution instructions and send operation instructions to the robots corresponding to each task track according to each task track in the control interface. The control interface includes a first area containing multiple independent task tracks corresponding to each robot. The task tracks are used to allow the robots corresponding to the task tracks to execute tasks corresponding to task components in the task tracks in a time sequence. The robot is used to: receive the operation instructions sent by the electronic device and execute the tasks corresponding to the operation instructions.

[0215] The specific functions and effects of the robot control system provided in this application embodiment can be referred to the description of the above method embodiment. To avoid repetition, they will not be repeated here.

[0216] Figure 7 The diagram shown is a structural schematic of a task orchestration device provided in an exemplary embodiment of this application. This robot control device can be applied to electronic devices. Figure 7 As shown, the task orchestration device 700 includes: a first display module 710, a receiving module 720, and a generating module 730.

[0217] The first display module 710 is used to display the control interface. The control interface includes a first area, which contains multiple independent task tracks corresponding to each robot. The task tracks are used to allow the robots corresponding to the task tracks to execute the tasks corresponding to the task components in the task tracks in a time sequence.

[0218] The receiving module 720 is used to receive task addition instructions, which include the robot corresponding to the task to be added, the task execution time, and the task execution duration.

[0219] The generation module 730 is used to generate a task component of the task to be added in the task track of the robot corresponding to the task to be added, based on the task execution time and the task execution duration. The position of the task component is used to represent the task execution time, and the length of the task component is used to represent the task execution duration.

[0220] Optionally, the task orchestration device 700 further includes an editing module 740, configured to: in response to a user's selection operation on a task component in the first area, determine a specified component and a specified task corresponding to the specified component; and, based on the user's editing operation on the specified component, change at least one of the length and position of the specified component to update the specified task.

[0221] Optionally, the editing operation includes at least one of drag-and-drop, zoom, and delete operations; the editing module 740 is configured to: if the editing operation is a drag-and-drop operation, determine the drag direction and drag distance based on the user's drag operation on the specified component, and adjust the position of the specified component based on the drag direction and drag distance; if the editing operation is a zoom operation, adjust the length of the specified component based on the user's zoom operation on the specified component; if the editing operation is a delete operation, delete the specified component from the task track where the specified component is located based on the user's delete operation on the specified component.

[0222] Optionally, the specified component includes a left edge and a right edge, where the left edge represents the task execution time of the specified task and the right edge represents the task termination time of the specified task; the editing module 740 is configured to: when the scaling operation is a first drag operation on the left edge of the specified component, adjust the position of the left edge according to the first drag operation to adjust the position and length of the specified component; when the scaling operation is a second drag operation on the right edge of the specified component, adjust the position of the right edge according to the second drag operation to adjust the length of the specified component.

[0223] Optionally, the task orchestration device 700 also includes a display module 750.

[0224] Optionally, the display module 750 is used to: display the task addition interface in response to the user's task addition operation; and determine the robot corresponding to the task to be added, the task execution duration corresponding to the task to be added, and the task execution time corresponding to the task to be added based on the user's editing operation on the task addition interface, so as to generate a task addition instruction.

[0225] Optionally, the display module 750 is used to: in response to the user's selection operation of the task component in the first area, determine the specified component and the specified task corresponding to the specified component; and display the task information of the specified task in the form of a floating window in the area surrounding the specified component. The task information includes at least one of the following: task type, task execution time, and task execution duration.

[0226] Optionally, the control interface includes a second area, which includes robot components corresponding to multiple robots, and the robot components are used to display the robot names.

[0227] Optionally, in the control interface, the color of the robot component corresponding to the same robot and the color of the task component in the task track are the same color, while the colors of the robot components corresponding to different robots are different colors.

[0228] Optionally, the generation module 730 is configured to: in response to a user's selection operation of robot components in a second region, determine multiple target robots from multiple robots for performing cooperative operations; and generate a task track corresponding to each target robot in a first region, wherein the first region contains task tracks that correspond one-to-one with the multiple target robots.

[0229] Optionally, the generation module 730 is configured to: receive a robot addition instruction, the robot addition instruction including the robot name corresponding to the robot to be added; and generate the robot component of the robot to be added in the second area according to the robot name.

[0230] It should be understood that the operation and functions of the first display module 710, receiving module 720, generating module 730, editing module 740, and display module 750 in the above embodiments can be referred to the above description. Figure 2 The description of the task orchestration method provided in the embodiments will not be repeated here to avoid repetition.

[0231] Figure 8 The diagram shown is a schematic representation of a robot control device provided in an exemplary embodiment of this application. This robot control device can be applied to electronic devices. Figure 8 As shown, the robot control device 800 includes an execution module 810.

[0232] The execution module 810 is used to respond to the execution command and send operation commands to the robots corresponding to each task track according to each task track in the control interface, so that the robots that receive the operation commands can execute the tasks corresponding to the operation commands.

[0233] Optionally, the robot control device also includes a second display module 820.

[0234] Optionally, the second display module 820 is used to: display a time marker of the current moment in a first area of ​​the control interface during the process of controlling the robot to perform a task, with the time marker running through each task track in the first area; and display each task component in each task track in a display manner with different degrees of prominence, wherein the prominence of task components that have overlapping parts with the time marker is higher than that of task components that do not have overlapping parts with the time marker.

[0235] Optionally, the second display module 820 is used to: expand the width of the task component so that the width of the task component is greater than that of other task components in the task track where the task component is located.

[0236] Optionally, the second display module 820 is used to: for each robot in each task track, determine the task that the robot is performing based on the current time and the task components in the task track corresponding to the robot;

[0237] Based on the task the robot is performing, determine the robot's state, and update the robot's components accordingly.

[0238] It should be understood that the operation and function of the execution module 810 and the second display module 820 in the above embodiments can be referred to the above. Figure 5 The description of the robot control method provided in the embodiments will not be repeated here to avoid repetition.

[0239] Figure 9 The diagram shown is a block diagram of an electronic device 120 for performing a task orchestration method or a robot control method according to an exemplary embodiment of this application. Specifically, the electronic device 120 may be a server, a robot, a controller, a server that interacts with the robot or controller, or other devices.

[0240] Reference Figure 9 The electronic device 120 includes a processing component 121, which further includes one or more processors, and memory resources represented by memory 122 for storing instructions executable by the processing component 121, such as application programs. The application programs stored in memory 122 may include one or more modules, each corresponding to a set of instructions. Furthermore, the processing component 121 is configured to execute instructions to perform the aforementioned task orchestration method or robot control method.

[0241] Electronic device 120 may also include a power supply component configured to perform power management of electronic device 122, a wired or wireless network interface configured to connect electronic device 120 to a network, and an input / output (I / O) interface. Electronic device 120 can be operated based on an operating system stored in memory 122, such as Windows Server. TM MacOSX TM Unix TM Linux TM FreeBSD TM Or similar.

[0242] A non-transitory computer-readable storage medium, when the instructions in the storage medium are executed by the processor of the aforementioned electronic device 120, enables the electronic device 120 to perform a task orchestration method or a robot control method.

[0243] A computer program product includes a computer program that, when executed by a processor of a computer device, enables the computer device to perform the task orchestration method or robot control method provided in any of the above embodiments.

[0244] All of the above-mentioned optional technical solutions can be combined in any way to form optional embodiments of this application, and will not be described in detail here.

[0245] Those skilled in the art will recognize that the units and algorithm steps of the various examples described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are implemented in hardware or software depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this application.

[0246] Those skilled in the art will understand that, for the sake of convenience and brevity, the specific working processes of the systems, devices, and units described above can be referred to the corresponding processes in the foregoing method embodiments, and will not be repeated here.

[0247] In the several embodiments provided in this application, it should be understood that the disclosed systems, apparatuses, and methods can be implemented in other ways. For example, the apparatus embodiments described above are merely illustrative; for instance, the division of units is only a logical functional division, and in actual implementation, there may be other division methods. For example, multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed. Furthermore, the coupling or direct coupling or communication connection shown or discussed may be through some interfaces; the indirect coupling or communication connection between apparatuses or units may be electrical, mechanical, or other forms.

[0248] The units described as separate components may or may not be physically separate. The components shown as units may or may not be physical units; that is, they may be located in one place or distributed across multiple network units. Some or all of the units can be selected to achieve the purpose of this embodiment according to actual needs.

[0249] In addition, the functional units in the various embodiments of this application can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit.

[0250] If the aforementioned functions are implemented as software functional units and sold or used as independent products, they can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the prior art, or a portion of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute all or part of the steps of the methods described in the various embodiments of this application. The aforementioned storage medium includes various media capable of storing program verification codes, such as USB flash drives, portable hard drives, read-only memory (ROM), random access memory (RAM), magnetic disks, or optical disks.

[0251] It should be noted that in the description of this application, the terms "first," "second," "third," etc., are used for descriptive purposes only and should not be construed as indicating or implying relative importance. Furthermore, in the description of this application, unless otherwise stated, "a plurality of" means two or more.

[0252] It should be noted that the user information (including but not limited to user device information, user personal information, etc.) and data (including but not limited to data used for analysis, data stored, data displayed, etc.) involved in this application are all information and data authorized by the user or fully authorized by all parties. Furthermore, the collection, use and processing of the relevant data must comply with the relevant laws, regulations and standards of the relevant countries and regions, and corresponding operation entry points are provided for users to choose to authorize or refuse.

[0253] The above description is merely a preferred embodiment of this application and is not intended to limit this application. Any modifications or equivalent substitutions made within the spirit and principles of this application should be included within the protection scope of this application.

Claims

1. A task orchestration method, characterized in that, The task orchestration method, applied to electronic devices, includes: The control interface includes a first area containing multiple independent task tracks corresponding to multiple robots. The task tracks are used to allow the robots corresponding to the task tracks to execute the tasks corresponding to the task components in the task tracks in a time sequence. The multiple robots are multiple target robots used to perform collaborative operations. The control interface also includes a second area containing robot components, which are used to display the robot names. In response to the user's selection operation of robot components in the second area, a plurality of target robots for performing cooperative operations are determined from the plurality of robots; For each of the plurality of target robots, a task track corresponding to the target robot is generated in the first region, wherein the first region contains task tracks that correspond one-to-one with the plurality of target robots; Receive a task addition instruction, wherein the task addition instruction includes the robot corresponding to the task to be added, the task execution time corresponding to the task to be added, and the task execution duration corresponding to the task to be added; Based on the task execution time and the task execution duration, a task component for the task to be added is generated in the task track of the robot corresponding to the task to be added. The position of the task component is used to represent the task execution time, and the length of the task component is used to represent the task execution duration.

2. The task orchestration method according to claim 1, characterized in that, The task orchestration method also includes: In response to the user's selection operation of the task component in the first area, the specified component and the specified task corresponding to the specified component are determined; Based on the user's editing operation on the specified component, at least one of the length and position of the specified component is changed to update the specified task.

3. The task orchestration method according to claim 2, characterized in that, The editing operation includes at least one of drag-and-drop, zoom-and-delete, and delete operations; The step of changing at least one of the length and position of the specified component based on the user's editing operation on the specified component includes: If the editing operation is a drag operation, the drag direction and drag distance are determined according to the user's drag operation on the specified component, and the position of the specified component is adjusted according to the drag direction and the drag distance; If the editing operation is the scaling operation, adjust the length of the specified component according to the user's scaling operation on the specified component; If the edit operation is the delete operation, the specified component is deleted from the task track where the specified component is located, based on the user's delete operation on the specified component.

4. The task orchestration method according to claim 3, characterized in that, The specified component includes a left edge and a right edge, the left edge being used to characterize the task execution time of the specified task, and the right edge being used to characterize the task termination time of the specified task; The step of adjusting the length of the specified component based on the user's scaling operation on the specified component includes: When the scaling operation is a first drag operation on the left edge of the specified component, the position of the left edge is adjusted according to the first drag operation to adjust the position and length of the specified component; When the scaling operation is a second drag operation on the right edge of the specified component, the position of the right edge is adjusted according to the second drag operation to adjust the length of the specified component.

5. The task orchestration method according to claim 1, characterized in that, The task orchestration method also includes: In response to the user's task addition action, the task addition interface is displayed; Based on the user's editing operations on the task addition interface, the robot corresponding to the task to be added, the task execution duration, and the task execution time are determined to generate a task addition instruction.

6. The task orchestration method according to claim 1, characterized in that, The task orchestration method also includes: In response to the user's selection operation of the task component in the first area, the specified component and the specified task corresponding to the specified component are determined; In the area surrounding the designated component, task information of the designated task is displayed in a floating window. The task information includes at least one of the following: task type, task execution time, and task execution duration.

7. The task orchestration method according to claim 1, characterized in that, In the control interface, the color of the robot component corresponding to the same robot and the color of the task component in the task track are the same color, while the colors of the robot components corresponding to different robots are different.

8. The task orchestration method according to claim 1, characterized in that, The task orchestration method also includes: Receive a robot add instruction, wherein the robot add instruction includes the robot name corresponding to the robot to be added; Based on the robot name, the robot component of the robot to be added is generated in the second area.

9. A robot control method, characterized in that, Applied to an electronic device configured to perform the task orchestration method of any one of claims 1 to 8, the robot control method includes: In response to the execution command, the robot sends an operation command to the robot corresponding to each task track according to each task track in the control interface, so that the robot that receives the operation command can execute the task corresponding to the operation command.

10. The robot control method according to claim 9, characterized in that, The robot control method further includes: During the process of controlling the robot to perform tasks, a time marker of the current moment is displayed in the first area of ​​the control interface, and the time marker runs through each task track in the first area; Each task component in each task track is displayed in a way that varies in salience, wherein the salience of a task component that overlaps with the time marker is higher than that of a task component that does not overlap with the time marker.

11. The robot control method according to claim 10, characterized in that, The components of each task in each task track are displayed in a way that varies in degree of prominence, including: Expand the width of the task component so that its width is greater than that of other task components in the task track where it is located.

12. The robot control method according to claim 10, characterized in that, The control interface includes a robot component, which is used to display the robot's status; the robot control method further includes: For each robot corresponding to each task track, the task being performed by the robot is determined based on the current time and the task components in the task track corresponding to the robot. Based on the task the robot is performing, determine the robot state of the robot, and update the robot components of the robot based on the determined robot state.

13. An electronic device, characterized in that, The electronic device includes: a processor; and a memory for storing processor-executable instructions, wherein the processor is used to execute the task orchestration method of any one of claims 1 to 8 or the robot control method of any one of claims 9 to 12.

14. A robot control system, characterized in that, include: The electronic device of claim 13 is configured to: in response to an execution instruction, send an operation instruction to the robot corresponding to each task track according to each task track in the control interface, wherein the control interface includes a first area, the first area includes multiple independent task tracks corresponding to each robot, and the task track is used to allow the robot corresponding to the task track to execute the task corresponding to the task component in the task track in a time sequence. The robot is used to: receive the operation instructions sent by the electronic device, and execute the task corresponding to the operation instructions according to the operation instructions.

15. A computer program product, characterized in that, The computer program product includes a computer program that, when executed by the processor of a computer device, enables the computer device to perform the task scheduling method of any one of claims 1 to 8 or the robot control method of any one of claims 9 to 12.

Images