Robot scheduling platform, robot, medium, task deployment method and system

Abstract

The present application relates to the field of robot technology, and discloses a robot scheduling platform, a robot, a medium, a task deployment method and a system for improving the efficiency of task deployment. The robot scheduling platform is arranged to: establish a binding relationship between the robot and the map information of the robot's current use map; obtain a task adding request, the task adding request includes the task deployment information corresponding to the robot, and the task deployment information includes the target work task and the map information of the work map corresponding to the target work task; according to the binding relationship and the map information of the work map, determine whether the work map is consistent with the robot's current use map; when the work map is consistent with the robot's current use map, save the task deployment information corresponding to the robot, so as to deploy the work task for the robot through the task deployment information.

Description

Technical Field

[0001] The present application relates to the field of robotics technology, and in particular to a robot scheduling platform, a robot, a medium, a task deployment method and a system. Background Art

[0002] Currently, robots are used in many application scenarios, and robots perform corresponding work tasks according to settings. The inventors realize that in the current solution, the work tasks of the robots are manually switched and set on the robots by users. However, robots sometimes have to perform different work tasks according to different time periods. Therefore, currently, the clerks are required to switch the work task mode of the machine according to the time period, which is very time-consuming and labor-intensive, and reduces efficiency. Summary of the invention

[0003] The embodiments of the present application provide a robot scheduling platform, a robot, a medium, a task deployment method and a system to solve the technical problem of low efficiency of task deployment in traditional solutions.

[0004] A robot scheduling platform comprises a memory and a processor, wherein the memory stores a program code, and the processor is used to call the program code, and when the program code is executed, the robot scheduling platform is arranged as follows:

[0005] Establishing a binding relationship between the robot and map information of a map currently used by the robot;

[0006] Obtaining a task adding request, wherein the task adding request includes task deployment information corresponding to the robot, and the task deployment information includes a target work task and map information of a work map corresponding to the target work task;

[0007] According to the binding relationship and the map information of the working map, it is determined whether the working map is consistent with the current usage map of the robot. Figure 1 To;

[0008] When the work map is consistent with the robot's current location Figure 1 If the robot is configured to be a task-oriented robot, the task deployment information corresponding to the robot is saved, so as to deploy work tasks for the robot through the task deployment information.

[0009] In one embodiment, the robot scheduling platform is further arranged as follows:

[0010] When the working map is inconsistent with the current use map of the robot, a first prompt message is issued, where the first prompt message is used to indicate that the working map is inconsistent with the current use map of the robot.

[0011] In one embodiment, the robot scheduling platform is further arranged as follows:

[0012] receiving a task pull request for the robot;

[0013] In response to the task pull request, determine whether task deployment information corresponding to the robot is saved;

[0014] When the task deployment information corresponding to the robot is saved, the task deployment information of the robot is fed back to the robot.

[0015] In one embodiment, the robot scheduling platform is further arranged as follows:

[0016] When a binding request for binding a target store to the robot is received, it is determined whether all the work maps corresponding to the robot's deployed work tasks are consistent with the robot's current use map. Figure 1 To;

[0017] When all the work maps corresponding to the deployed work tasks are consistent with the current use location of the robot Figure 1 To display all the deployed work tasks of the robot.

[0018] In one embodiment, the robot scheduling platform is further arranged as follows:

[0019] When there is a work map among all the work maps corresponding to the deployed work tasks that is inconsistent with the current map used by the robot, the task state of the deployed work tasks corresponding to the inconsistent work map is set to a map abnormal state;

[0020] Display all the deployed work tasks of the robot and the corresponding task status.

[0021] In one embodiment, all deployed work tasks of the robot include deactivated tasks; and the robot scheduling platform is further arranged as follows:

[0022] When receiving an activation request for the disabled task, determining whether the work map corresponding to the disabled task is consistent with the current use map of the robot Figure 1 To;

[0023] When the working map corresponding to the disabled task is inconsistent with the current usage map of the robot, a second prompt message is issued, and the task status of the disabled task is set to a map abnormality state. The second prompt message is used to indicate that the current usage map of the robot has been adjusted.

[0024] In one embodiment, the robot scheduling platform is further arranged as follows:

[0025] When the work map corresponding to the deactivated task is consistent with the current use map of the robot Figure 1 If so, the task status corresponding to the disabled task is set to the enabled status.

[0026] A robot, a memory and a processor, wherein the memory stores a program code, and the processor is used to call the program code, and when the program code is executed, the robot is arranged to:

[0027] Acquire task deployment information corresponding to the robot from a robot scheduling platform, wherein the task deployment information includes a target work task; wherein the task deployment information is information deployed by the robot scheduling platform described in any of the above items;

[0028] Deploy the robot's work tasks according to the target work tasks.

[0029] In one embodiment, after the robot deploys the work tasks of the robot according to the target work tasks, the robot is further arranged to:

[0030] Determine the work task to be executed according to the target work task and the task deployment status before the robot receives the task deployment information;

[0031] Execute the work task to be executed.

[0032] In one embodiment, when the robot determines the work task to be performed based on the target work task and the task deployment status before the robot receives the task deployment information, the robot is arranged as follows:

[0033] Determine whether the robot has a deployed work task before receiving the task deployment information;

[0034] When there are deployed work tasks, the target work tasks and the deployed work tasks are used as work tasks to be selected;

[0035] When there is no deployed work task, the target work task is used as the work task to be selected;

[0036] The work task to be executed is determined according to the execution period of the work task to be selected.

[0037] In one embodiment, after the robot determines that a work task is to be performed, the robot is further arranged to:

[0038] Determine whether the work map corresponding to the executed work task is consistent with the current use map of the robot Figure 1 To;

[0039] When all are consistent, all the executed work tasks are displayed;

[0040] When there is an inconsistency, only the Figure 1 The work tasks being performed are as follows.

[0041] A task deployment method, the task deployment method comprising:

[0042] Establishing a binding relationship between the robot and the current usage map of the robot;

[0043] Obtaining a task adding request, wherein the task adding request includes task deployment information corresponding to the robot, and the task deployment information includes a target work task and map information of a work map corresponding to the target work task;

[0044] According to the binding relationship and the map information of the working map, it is determined whether the working map is consistent with the current usage map of the robot. Figure 1 To;

[0045] When the work map is the current use map of the robot, the task deployment information corresponding to the robot is saved to deploy work tasks for the robot through the task deployment information.

[0046] A task deployment method, the task deployment method comprising:

[0047] Acquire task deployment information corresponding to the robot from a robot scheduling platform, wherein the task deployment information includes a target work task; wherein the task deployment information is information deployed by the robot scheduling platform described in any of the above items;

[0048] Deploy the robot's work tasks according to the target work tasks.

[0049] A robot task automatic deployment system comprises the robot scheduling platform as described in any one of the foregoing items, and the robot as described in any one of the foregoing items.

[0050] A computer-readable storage medium stores a computer program, wherein the computer program, when executed by a processor, implements the steps implemented by the robot scheduling platform as described in any of the above items, or implements the steps implemented by the robot as described in any of the above items.

[0051] In one of the solutions provided above, by pre-establishing a binding relationship between each robot and the map information of the corresponding usage map, the robot scheduling platform is used to automatically deploy the work tasks that each robot can perform, so as to realize the automatic deployment of the robot's work tasks. After deployment, the robot scheduling platform can send the task to the robot or the robot actively obtains the task information corresponding to the robot saved on the robot scheduling platform. Compared with the traditional solution that can only be deployed and set on each machine, and people are required to adjust the mode according to the time period, the implementation of this application allows the robot to set the automated task directly on the robot scheduling platform so as to automatically execute the task later, which is more efficient, and the robot scheduling platform can manage and deploy each robot accordingly, which is convenient for the overall management of the tasks of each robot and more intelligent. BRIEF DESCRIPTION OF THE DRAWINGS

[0052] In order to more clearly illustrate the technical solutions of the embodiments of the present application, the drawings required for use in the description of the embodiments of the present application will be briefly introduced below. Obviously, the drawings described below are only some embodiments of the present application. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying any creative labor.

[0053] Figure 1 This is a schematic diagram of a system architecture of a robot task automatic deployment system in one embodiment of the present application;

[0054] Figure 2 This is a schematic diagram of a structure of a robot scheduling platform in one embodiment of the present application;

[0055] Figure 3 is a structural schematic diagram of a robot in one embodiment of the present application;

[0056] Figure 4 This is a flow chart of a task deployment method implemented by a robot scheduling platform in one embodiment of the present application;

[0057] Figure 5 This is another flowchart of the task deployment method implemented by the robot scheduling platform side in one embodiment of the present application;

[0058] Figure 6 This is another flowchart of the task deployment method implemented by the robot scheduling platform side in one embodiment of the present application;

[0059] Figure 7 This is another flowchart of the task deployment method implemented by the robot scheduling platform side in one embodiment of the present application;

[0060] Figure 8 This is a flowchart of a task deployment method implemented by a robot in an embodiment of the present application;

[0061] Fig. 9 This is another flowchart of a task deployment method implemented by a robot in one embodiment of the present application;

[0062] Fig.10 This is a schematic diagram of a structure of a robot task automation device in one embodiment of the present application;

[0063] Fig.11 It is another structural schematic diagram of the robot task automation device in one embodiment of the present application. DETAILED DESCRIPTION

[0064] The following will be combined with the drawings in the embodiments of the present application to clearly and completely describe the technical solutions in the embodiments of the present application. Obviously, the described embodiments are part of the embodiments of the present application, not all of the embodiments. Based on the embodiments in the present application, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of this application.

[0065] The present application provides a task deployment method, a robot task automatic deployment system, a robot scheduling platform, a robot and related storage media. To facilitate understanding of the present application, the present application will describe each of the above topics one by one. The robot task automatic deployment system is the basic system framework for implementing the present application. It is advisable to first introduce the robot task automatic deployment system provided in the embodiment of the present application.

[0066] like Figure 1 As shown, Figure 1 A system schematic diagram of the robot task automatic deployment system provided for the present application includes robots and a robot scheduling platform. Exemplarily, the robots include robot R1, robot R2, ..., robot RM, wherein robots R1-RM may be robots of different stores and / or the same store; the robots may communicate with the robot scheduling platform via a network.

[0067] The above-mentioned robot scheduling platform can be but is not limited to various terminal devices such as personal computers, laptops, smart phones, tablet computers, etc. In another implementation scenario, the robot scheduling platform can also refer to a cloud platform, which can be controlled by the terminal device to achieve interaction with the robot, without specific limitation.

[0068] The robot depends on the application scenario of the robot task automatic deployment system, and can be a variety of store robots. For example, the robot can be a robot for restaurants, a robot for hotels, a robot for sales stores, a robot for offices, or other robots used to perform work tasks outside stores. In some embodiments, the robot can also be a robot used to perform work tasks outdoors, which is not limited in this application and is not illustrated one by one.

[0069] Based on Figure 1 The robot task automatic deployment system shown in the present application first describes its corresponding functions or implementation steps from the robot scheduling platform side and the robot side respectively.

[0070] First, the robot scheduling platform provided in the embodiment of the present application is described in detail. Figure 2 As shown, Figure 2 A schematic diagram of the structure of the robot scheduling platform provided in the present application includes a memory, a transceiver and a processor, wherein the memory stores program code, the transceiver is used to receive or send information / instructions, and the processor is used to provide computing and control capabilities. The memory may include a non-volatile storage medium and an internal memory. The non-volatile storage medium may store an operating system and a computer program. The internal memory provides an environment for the operation of the operating system and the computer program in the non-volatile storage medium. The processor is used to call the program code, and when the program code is executed, the robot scheduling platform is arranged as follows:

[0071] (1) establishing a binding relationship between the robot and map information of a map currently used by the robot;

[0072] (2) obtaining a task adding request, wherein the task adding request includes task deployment information corresponding to the robot, and the task deployment information includes a target work task and map information of a work map corresponding to the target work task;

[0073] (3) judging whether the working map is consistent with the current location of the robot according to the binding relationship and the map information of the working map; Figure 1 To;

[0074] (4) When the work map is consistent with the current location of the robot Figure 1 If the robot is configured to be a task-oriented robot, the task deployment information corresponding to the robot is saved, so as to deploy work tasks for the robot through the task deployment information.

[0075] For the above process (1), the robot scheduling platform obtains the map information of the robot and the current usage map of the robot to establish a binding relationship. Among them, the robot can have one or more different working maps built in. However, in a certain period of time, the robot has its current corresponding usage map, that is, the current usage map. For example, for robot R1, the robot R1 may have N kinds of working maps built in, but currently, based on the usage scenario of the robot R1, the current usage map of the robot R1 is the working map. Figure 1 In the embodiment of the present application, the robot's work tasks depend on the map in the robot body. To facilitate the automated deployment of each robot's work tasks, the robot scheduling platform obtains the correspondence between each robot and the robot's current usage map through the transceiver, and then establishes a binding relationship.

[0076] In some embodiments, the robot scheduling platform may proactively obtain the correspondence between the robot's current map and establish a binding relationship from each robot according to a certain acquisition strategy; in other embodiments, a reporting trigger condition may be set for each robot. When the reporting trigger condition is met, each robot automatically reports the correspondence between the robot and the current map to the robot scheduling platform, so that the robot scheduling platform can establish a binding relationship between the robot and the current map. In some application scenarios, the trigger condition refers to when the robot changes the map, that is, when the robot changes the map, the robot scheduling platform can establish a binding relationship between the robot and the map based on the latest correspondence.

[0077] In one embodiment, when establishing a binding relationship, it can be established based on the robot's identifier and the map information of the currently used map. Exemplarily, the robot's identifier can be the robot's name, number or other identifier, etc., and the map information includes a map identifier, which can also be the map's name, number or other identifier, etc. The binding relationship is established by establishing a corresponding relationship between the map identifier and the robot's identifier, and the specifics are not limited.

[0078] It should be noted that the map information of the robot's work map can also include information such as map points and map modes, where the map points are the location points when the robot performs tasks, and the map mode refers to whether the work map is an outdoor map or an indoor map, or the mode information of the map in certain scenarios.

[0079] For the above (2) process, after the robot scheduling platform establishes a binding relationship between the robot and the current usage map of the robot, the robot scheduling platform can deploy the robot's work tasks. For the robot scheduling platform, taking one of the example scenarios as an example, the robot scheduling platform can render a robot work task deployment screen through the platform display interface. The administrator can deploy work tasks for the robot through the robot work task deployment screen to trigger the generation of corresponding task addition requests. The robot scheduling platform can obtain the task addition request, and the task addition request includes the task deployment information corresponding to the robot, and the task deployment information includes the target work task and the map information of the work map corresponding to the target work task.

[0080] It should be noted that, in order to facilitate a clear description of the embodiments of the present application, the work tasks deployed for the robot are referred to as target work tasks in the present application. Among them, there is a corresponding work map and corresponding map information for each deployed target work task. In some implementation scenarios, each target work task may be a work task corresponding to a different time period, for example, target work task 1 corresponds to time period 1, target work task 2 corresponds to time period 2, ..., target work task N corresponds to time period N. In other implementation scenarios, the above-mentioned different target work tasks may correspond to the same or different work maps.

[0081] For example, taking a practical application scenario as an example, during peak hours, robot R1 should go to the store entrance of store 1 to solicit customers (corresponding to the work location Figure 1 ), during off-peak hours, robot R1 should go to other locations in store 1 for cruising or return (also corresponding to the work location Figure 1 ), the so-called peak hours and off-peak hours can be estimated based on experience and specific application scenarios, which will not be described in detail here. Therefore, when adding work tasks for the deployment of robot R1, the administrator can use the robot work task deployment screen to set target work task 1: robot R1 goes to the store entrance of store 1 to attract customers during the peak period; and / or set target work task 2: robot R1 goes to store 1 to cruise or return orders during the off-peak period. After setting the work tasks and submitting the tasks, the above task addition request is triggered.

[0082] It should be noted that when deploying the robot's work tasks, you can select a robot under the store to deploy the work tasks, thereby triggering the above-mentioned task addition request. The robot can be set to perform a certain work task in a certain time period, and even task information such as task duration can be included, without specific limitation.

[0083] For the above (3) process, after the robot scheduling platform receives the above task adding request, the robot scheduling platform will respond to the task adding request to deploy the robot's work task. Specifically, the robot scheduling platform will first determine whether the work map of the added target work task is the current use map of the robot based on the binding relationship. It should be noted that the current use map of the robot refers to the map currently used by the robot.

[0084] For example, the work map for the target work task added to robot R1 is the work area Figure 1 , and the current map used by robot R1 is the work area Figure 1 , because robot R1 and the work area Figure 1 , a binding relationship has been established before. At this time, the work location of the added target work task can be determined based on the binding relationship. Figure 1 The map currently used by the robot R1 (workplace Figure 1 ) is consistent, that is, the work location of the target work task Figure 1 is the current usage map of robot R1; on the contrary, for example, the work area of ​​the target work task Figure 2 , then the work location of the target work task is Figure 2 This is not the current map used by the robot R1 (workplace Figure 1 ), indicating that the maps are inconsistent.

[0085] For the above process (4), when the work map corresponding to the target work task is the current use map of the robot, such as the example in the above (3), it means that the added target work task is correct and the robot R1 can execute the target work task, then the task deployment information is saved.

[0086] Through the robot scheduling platform provided by this embodiment, by pre-establishing the binding relationship between each robot and the corresponding usage map, the robot scheduling platform is used to automatically deploy the work tasks that each robot can perform, so as to realize the automatic deployment of the robot's work tasks. After deployment, the robot scheduling platform can send the task to the robot or the robot can actively obtain the task information corresponding to the robot saved on the robot scheduling platform. Compared with the traditional solution that can only be deployed and set on each machine, and people are required to adjust the mode according to the time period, the implementation of the embodiment of the present application allows the robot to set the automated task directly on the robot scheduling platform so as to automatically perform the task later, which is more efficient, and the robot scheduling platform corresponds to each robot, which is convenient for the overall management of the tasks of each robot, and more intelligent.

[0087] It is also worth mentioning that through the established binding relationship, the robot can also be automatically deployed with executable work tasks, further improving deployment efficiency and effectiveness.

[0088] In one embodiment, the robot scheduling platform is further arranged as follows:

[0089] (5) When the working map is inconsistent with the current usage map of the robot, a first prompt message is issued, wherein the first prompt message is used to indicate that the working map is inconsistent with the current usage map of the robot.

[0090] For example, in the task adding request, the work map of the target work task deployed for robot R1 is the work location Figure 2 , then the work location corresponding to the target work task Figure 2 This is not the current map used by the robot R1 (workplace Figure 1 ), the target task cannot be assigned to robot R1 at this time, and the robot scheduling platform will issue a first prompt message to indicate the work location of the deployed target task. Figure 2 Inconsistent with the current map used by robot R1.

[0091] Among them, in an example scenario, the first prompt information in text form can be rendered through the platform interface of the robot scheduling platform, and / or prompt information in voice form can be issued. For example, it directly indicates that the current usage map of the robot R1 has been adjusted, thereby prompting the need to add a work task corresponding to the current usage map of the robot R1.

[0092] Through this embodiment, it is possible to effectively avoid deploying erroneous or mismatched work tasks for robots, improve the efficiency of work task deployment, and reduce unnecessary interactions between the robot scheduling platform and robots due to map errors, thereby reducing traffic consumption.

[0093] In some embodiments, the robot scheduling platform is further arranged to:

[0094] (6) receiving a task pull request from the robot;

[0095] (7) responding to the task pull request and determining whether task deployment information corresponding to the robot is saved;

[0096] (8) When the task deployment information corresponding to the robot is saved, the task deployment information of the robot is fed back to the robot.

[0097] For the above process (6), the robot scheduling platform can receive task pull requests from any robot. In some implementation scenarios, the robots of each store can send task pull requests to the robot scheduling platform at preset time nodes to obtain the target work tasks deployed by the robot scheduling platform.

[0098] For the above (7)-(8) processes, after receiving the task pull request, the robot scheduling platform will respond to the task pull request to determine whether the task deployment information corresponding to the robot is saved. If the task deployment information corresponding to the robot is saved, it means that there is already a task deployment for the robot, so the task deployment information of the robot's work task can be fed back to the robot.

[0099] For example, the robot R1 under store 1 can send a task request to the robot scheduling platform. After receiving the task pull request of robot R1, the robot scheduling platform will determine whether to save the corresponding task deployment information of the robot R1. As mentioned in the previous example, suppose that when adding work tasks to the deployment of robot R1, the target work task 1 (customer solicitation task) is set: during peak hours, robot R1 goes to the store entrance of store 1 to solicit customers, and the task deployment information is saved. When the task pull request of the robot R1 is received, the above-mentioned customer solicitation task of the robot R1 can be found and fed back to the robot R1, and the robot R1 can perform the customer solicitation task later.

[0100] It should be noted that in the above embodiment, the robot regularly requests the robot scheduling platform to deploy the work task according to the preset time node. In other embodiments, the robot scheduling platform can actively send task deployment information to the robot, which is not limited in this application.

[0101] Through the above embodiments, the robot scheduling platform automatically or passively deploys appropriate work tasks for each robot, effectively eliminating the tedious operation of manually switching the robot's work tasks and making it more intelligent.

[0102] In one embodiment, when the robot side pulls the task list from the robot scheduling platform, since the time zones are different, the robot scheduling platform will also return the current time zone based on the area of ​​the store to which the robot belongs so that the machine can distinguish it, and bring the task list so that the robot side can match the current tasks to be performed according to the map mode, time, and current time zone to perform the work.

[0103] In one embodiment, the robot scheduling platform is further arranged as follows:

[0104] (9) Displaying the available stores in a preset display mode;

[0105] (10) receiving a store selection request, wherein the store selection request is used to select a target store from the selectable stores;

[0106] (11) When a binding request for binding the target store to the robot is received, it is determined whether all the work maps corresponding to the work tasks deployed by the robot are consistent with the current use map of the robot. Figure 1 To;

[0107] (12) When all the work maps corresponding to the deployed work tasks are consistent with the current use location of the robot Figure 1 To display all the deployed work tasks of the robot.

[0108] For the above (9)-(10) processes, when it is necessary to deploy work tasks for robots in each store through the robot scheduling platform, the platform administrator can trigger the robot work task deployment process through the robot scheduling platform. When the robot scheduling platform triggers the work task deployment process, as an example scenario, the optional stores will first be displayed in a preset display mode.

[0109] Exemplarily, the stores under the robot scheduling platform include store 1, store 2, ..., store N. The store list can be displayed in the display interface of the robot scheduling platform in the form of a list, and the store list includes the above N stores. The platform administrator can select the required store (target store) from the store list to trigger the store selection request. For the robot scheduling platform, the robot scheduling platform can receive the store selection request, and the store selection request is used to select the target store from the optional stores, and the target store is one of the above N stores.

[0110] For the process (11)-(12), after selecting the target store from the store list, the platform administrator can deploy the target work task to the robot under the target store to trigger the task binding request. The platform administrator can select one or more robots to bind to the target store. In some implementation scenarios, when no robot is selected to bind to the target store, the robot's work task will not be displayed at this time.

[0111] For example, taking robot R1 as an example, when robot R1 is selected to bind a work store, that is, when a binding request for binding the target store with robot R1 is received, it will first determine whether the previously deployed work tasks of robot R1 are consistent with the current use location of the robot. Figure 1 When all the work maps corresponding to the deployed work tasks are consistent with the current use area of ​​the robot Figure 1 To display all the deployed work tasks of the robot.

[0112] It should be noted that in order to distinguish the target work tasks in the task adding request when adding work tasks to the robot through the task adding request, this application refers to the work tasks that have been deployed on the robot as deployed work tasks. For example, the deployed work tasks of robot R1 include work tasks 2, 3, and 4, among which the work maps corresponding to work tasks 2-4 are work maps. Figure 1 ; Robot R1 currently uses the map as the work area Figure 1 Obviously, the work locations corresponding to work tasks 2-4 are Figure 1 The current work area of ​​robot R1 Figure 1 are all consistent, therefore, all task information currently deployed by the robot R1 will be rendered and displayed, that is, the above-mentioned work tasks 2-4 will be displayed.

[0113] It should be noted that in some embodiments, the robot scheduling platform may also select the target store independently according to the strategy, without specific limitation.

[0114] In some embodiments, the robot scheduling platform is further arranged to:

[0115] (13) When there is a work map among all the work maps corresponding to the deployed work tasks that is inconsistent with the map currently used by the robot, the task status of the deployed work tasks corresponding to the inconsistent work map is set to a map abnormality state, and the corresponding task status of all the deployed work tasks of the robot is displayed.

[0116] For the above process (13), for example, the deployed tasks of robot R1 include task 2, task 3, and task 4, where the work maps corresponding to task 2 and task 3 are work maps. Figure 2 ; The work map corresponding to work task 4 is the work site Figure 1 , while robot R1 currently uses the map as the work area Figure 1 Obviously, the work locations corresponding to work tasks 2 and 3 are Figure 2 The current work area of ​​robot R1 Figure 1 There is inconsistency, therefore, the task status of work task 2 and work task 3 will be set to the map abnormal status, and then the task information and task status of all work tasks deployed by the robot will be displayed, that is, work tasks 2-4 will be displayed. Different from the aforementioned embodiment, the task status of work task 2 and work task 3 is displayed as the map abnormal status.

[0117] It can be seen from this embodiment that when deploying work tasks for robots, the robot scheduling platform can have a process of querying and screening each store and the robots in each store. Then, before deploying work tasks to the selected robot, it can also check all currently deployed task information of the bound robot and the task status of the work tasks, so that the task status and map situation of the currently deployed robot can be clearly known, so as to deploy appropriate work tasks for the robot, avoid repeated or inappropriate work task deployment, and make additional contributions to the intelligence of the robot's automated deployment of work tasks.

[0118] It should be noted that the working status of the robot's deployed work task is indicative information that reflects the specific situation of the deployed work task, which may include whether the work map corresponding to the deployed work task is abnormal (abnormal if the map does not match, otherwise normal), whether the deployed work task is enabled or disabled, etc.

[0119] In one embodiment, all the deployed work tasks currently deployed by the robot include deactivated tasks; and the robot scheduling platform is further arranged as follows:

[0120] (14) When receiving an activation request for the disabled task, determining whether the work map corresponding to the disabled task is consistent with the current use map of the robot. Figure 1 To;

[0121] (15) When the working map corresponding to the disabled task is inconsistent with the current use map of the robot, a second prompt message is issued, and the task status of the disabled task is set to a map abnormality status. The second prompt message is used to indicate that the current use map of the robot has been adjusted.

[0122] In one embodiment, the robot scheduling platform is further arranged as follows:

[0123] (16) When the working map corresponding to the disabled task is consistent with the current use map of the robot, the task state corresponding to the disabled task is set to the enabled state.

[0124] For the above (14)-(16) processes, when all the currently deployed work tasks of the robot include deactivated tasks, the deactivated tasks of the robot can also be started when adding deployed work tasks to the robot or in any other scenario. For the robot scheduling platform, a request to enable the deactivated tasks can be received, and when a request to enable the deactivated tasks is received, it will continue to determine whether the work map corresponding to the deactivated tasks is consistent with the current work map of the robot. Figure 1When the working map corresponding to the disabled task is inconsistent with the current use map of the robot, a second prompt message is issued, and the task state of the disabled task is set to a map abnormal state.

[0125] For example, assuming that the work map corresponding to the currently disabled task is the work map Figure 5 , and the current usage map of the robot is the work area Figure 1 , it can be seen that, if it is inconsistent, the task status of the deactivated task will be set to map abnormality, and a second prompt message will be issued. In this way, by re-verifying whether the map of the deactivated task is consistent, it is possible to avoid starting incompatible work tasks and improve deployment effectiveness. In addition, the task status of the deactivated task will be set to map abnormality to avoid repeated deployment of work tasks with map abnormalities. Assuming that the work map corresponding to the current deactivated task is the work map Figure 1 , then they are consistent, and if they are consistent, then the robot responds to the enable request to enable the disabled task and sets the task state to the enabled state. That is, the robot can execute the work task in the enabled state.

[0126] It should be noted that, as an example scenario, the second prompt information in text form can be rendered through the platform interface of the robot scheduling platform, and / or the second prompt information in voice form can be issued, without specific limitation.

[0127] The above-mentioned embodiment describes the robot scheduling platform provided by the embodiment of the present application from the perspective of the platform side of the robot scheduling platform. Next, the robot side provided by the embodiment of the present application is described in detail.

[0128] In one embodiment, if Figure 3 As shown, a robot is provided, comprising a memory, a transceiver and a processor, wherein the memory stores a program code, the transceiver is used to receive or send information / instructions, and the processor is used to call the program code, and when the program code is executed, the robot is arranged as follows:

[0129] (101) acquiring task deployment information corresponding to the robot from a robot scheduling platform, wherein the task deployment information includes a target work task; wherein the task deployment information is information deployed by the robot scheduling platform;

[0130] (102) Deploy the robot's work tasks according to the target work tasks.

[0131] The above (101)-(102) processes are functions or steps implemented by the robot side. For the robot, it can obtain the task deployment information corresponding to the robot from the robot scheduling platform through the transceiver, wherein the task deployment information is the task deployment information automatically deployed by the robot scheduling platform, and the task deployment information includes the target work task. The process of setting the task deployment information by the robot scheduling platform can be found in the above platform side embodiment, which is not repeated here. Then, after the robot obtains the target work task, it can deploy its own robot's work task.

[0132] In some embodiments, the robot can periodically report the correspondence between itself and the currently used map to the robot scheduling platform, so that the robot scheduling platform establishes a binding relationship between the robots based on the robot's report. For details, please refer to the above description, which will not be repeated here.

[0133] After the binding relationship is established, the robot scheduling platform can deploy the target work task for the robot and save it. For the robot, in some embodiments, the robot can actively or passively receive the task deployment information corresponding to the robot saved by the robot scheduling platform, so as to obtain the corresponding target work task and deploy it to the robot. Compared with the traditional solution, there is no need for manual deployment of work tasks to the robot. When there are many robots in the store, it can effectively improve the efficiency of task deployment, reduce unnecessary operations, and improve the efficiency of robot task management.

[0134] In some embodiments, after the robot deploys the work tasks of the robot according to the target work tasks, the robot is further arranged to:

[0135] (103) determining the work task to be executed according to the target work task and the task deployment status of the robot before receiving the task deployment information;

[0136] (104) executing the work task to be executed;

[0137] For the above (103)-(104), after the robot deploys the target work task, the robot can automatically match and execute the corresponding work task based on the deployed work task. First, the robot determines the work task to be executed based on the target work task and the task deployment status before the robot receives the task deployment information.

[0138] Specifically, the robot determines the work task to be executed according to the target work task and the task deployment status before the robot receives the task deployment information, and is arranged as follows: determining whether there is a deployed work task before the robot receives the task deployment information; if there is a deployed work task, the target work task and the deployed work task are used as the work tasks to be selected; if there is no deployed work task, the target work task is directly used as the work task to be selected. Then, the work task to be executed is matched according to the execution period of the work task to be selected.

[0139] For example, for robot R1, its deployed work task is work task 1, and the target work task deployed again by the robot scheduling platform is work task 2, then work task 1 and work task 2 will be selected as the work tasks to be selected. If the robot does not have a deployed work task, work task 1 will be directly selected as the work task to be selected.

[0140] Taking work task 1 and work task 2 as the work tasks to be selected as an example, if work task 1 needs to be executed in the current period, work task 1 will be selected as the work task to be executed.

[0141] After determining the work tasks to be selected, it should be noted that the work tasks to be executed may include one or more. Therefore, when there are multiple work tasks, the work tasks to be executed can be displayed in some way. For example, it can be displayed in the form of a task list, which is not limited to the specifics. After displaying the work tasks to be executed, it should be noted that by displaying the work tasks to be executed, the robot can let the store manager clearly know all the currently deployed work tasks, so that the store manager can understand the task status of the robot.

[0142] In one embodiment, after the robot determines that a work task is to be performed, the robot is further arranged to:

[0143] (105) Determine whether the work map corresponding to the work task being executed is consistent with the current use map of the robot. Figure 1 To;

[0144] (106) When all are consistent, all the executed work tasks are displayed;

[0145] (107) When there is an inconsistency, only the Figure 1 The work tasks being performed are as follows.

[0146] For the above (106)-(108), when the robot displays the work task to be performed, it will recheck the work map corresponding to the work task to be performed, and determine whether the work map corresponding to the work task to be performed is consistent with the current use map of the robot. Figure 1If all are consistent, all the executed tasks will be displayed. If there is any inconsistency, only the local Figure 1 This way, repeated verification can be performed to ensure that Figure 1 In practical applications, there are some scenarios, such as after the robot scheduling platform deploys the target task, the robot's current map may be adjusted. When the robot does not have time to obtain the latest task deployment information from the robot scheduling platform and needs to execute the task, the robot can re-check all currently deployed tasks to effectively avoid the execution of tasks that do not match the map, which affects the success rate of task execution.

[0147] It should be noted that the above-mentioned embodiments describe the system side, the robot scheduling platform side and the robot side. Based on the above-mentioned end sides, the embodiments of the present application also provide a corresponding task deployment method, which is also described separately from the robot scheduling platform and the robot side below.

[0148] In one embodiment, the robot scheduling platform is first described. Figure 4 As shown, a task deployment method is provided, which is applied in Figure 1 The robot scheduling platform in is used as an example to illustrate, including the following steps:

[0149] S10: establishing a binding relationship between the robot and the current usage map of the robot;

[0150] S20: Acquire a task adding request, wherein the task adding request includes task deployment information corresponding to the robot, and the task deployment information includes a target work task and map information of a work map corresponding to the target work task;

[0151] S30: judging whether the working map is consistent with the current use area of ​​the robot according to the binding relationship and the map information of the working map; Figure 1 To;

[0152] S40: When the working map is consistent with the current location of the robot Figure 1 If the robot is configured to be a task-oriented robot, the task deployment information corresponding to the robot is saved, so as to deploy work tasks for the robot through the task deployment information.

[0153] In one embodiment, continue as Figure 4 As shown, after step S30, that is, after judging whether the working map is the current map used by the robot according to the binding relationship and the map information of the working map, the task deployment method further includes the following steps:

[0154] S50: When the working map is inconsistent with the current use map of the robot, a first prompt message is issued, where the first prompt message is used to indicate that the working map is inconsistent with the current use map of the robot.

[0155] In one embodiment, if Figure 5 As shown, the task deployment method also includes the following steps:

[0156] S60: receiving a task pull request from the robot;

[0157] S70: Responding to the task pull request, determining whether task deployment information corresponding to the robot is saved;

[0158] S80: When the task deployment information corresponding to the robot is saved, the task deployment information of the robot is fed back to the robot.

[0159] In one embodiment, if Figure 6 As shown, the task deployment method also includes the following steps:

[0160] S90: Display the available stores according to the preset display mode;

[0161] S100: receiving a store selection request, where the store selection request is used to select a target store from the optional stores;

[0162] S110: When a binding request for binding the target store and the robot is received, it is determined whether all work maps corresponding to the deployed work tasks of the robot are consistent with the current use map of the robot. Figure 1 To;

[0163] S120: When all the work maps corresponding to the deployed work tasks are consistent with the current use location of the robot Figure 1 To display all the deployed work tasks of the robot.

[0164] In one embodiment, the above steps S90 - S100 may be omitted.

[0165] In one embodiment, after step S110, it is determined whether all the work maps corresponding to the deployed work tasks of the robot are consistent with the current use map of the robot. Figure 1 After that, the task deployment method further includes the following steps:

[0166] S130: When there is a work map among all the work maps corresponding to the deployed work tasks that is inconsistent with the current map used by the robot, the task status of the deployed work tasks corresponding to the inconsistent work map is set to a map abnormality state, and then all the deployed work tasks of the robot and the corresponding task status are displayed.

[0167] In one embodiment, if Figure 7 As shown, all the deployed work tasks currently deployed by the robot include deactivated tasks; the task deployment method also includes the following steps:

[0168] S140: receiving an activation request for the disabled task;

[0169] S150: When receiving an activation request for the disabled task, determining whether the work map corresponding to the disabled task is consistent with the current use map of the robot. Figure 1 To;

[0170] S160: When the working map corresponding to the disabled task is inconsistent with the current use map of the robot, a second prompt message is issued, and the task status of the disabled task is set to a map abnormality status, and the second prompt message is used to indicate that the current use map of the robot has been adjusted.

[0171] S170: When the work map corresponding to the deactivated task is consistent with the current use map of the robot Figure 1 If so, the task status corresponding to the disabled task is set to the enabled status.

[0172] It should be noted that for more steps on the robot scheduling platform side in the task deployment method, please refer to the corresponding description of the aforementioned embodiment, and the description and explanation will not be repeated here.

[0173] Through the task deployment method provided by this embodiment, by pre-establishing the binding relationship between each robot and the corresponding usage map, the robot scheduling platform is used to automatically deploy the work tasks that each robot can perform, so as to realize the automatic deployment of the robot's work tasks. After deployment, the robot scheduling platform can send the task to the robot or the robot can actively obtain the task information corresponding to the robot saved on the robot scheduling platform. Compared with the traditional solution, the implementation of the embodiment of the present application allows the robot to set the automated task directly on the robot scheduling platform so as to automatically perform the task later, which is more efficient. In addition, the robot scheduling platform corresponds to each robot, which is convenient for the overall management of the tasks of each robot and more intelligent.

[0174] In one embodiment, the description is made from the robot side, such as Figure 8 As shown, a task deployment method is provided, which is applied in Figure 1 The robot in the example is used to illustrate the following steps:

[0175] S101: Acquire task deployment information corresponding to the robot from a robot scheduling platform, wherein the task deployment information includes a target work task; wherein the task deployment information is information deployed by the robot scheduling platform to implement the above-mentioned corresponding embodiment;

[0176] S102: Deploy the robot's work tasks according to the target work tasks.

[0177] In one embodiment, after step S102, that is, after the robot deploys the work task of the robot according to the target work task, the task deployment method further includes the following steps:

[0178] S103: determining the work task to be executed according to the target work task and the task deployment status of the robot before receiving the task deployment information;

[0179] S104: Execute the work task to be executed.

[0180] In one embodiment, in step S103, determining the work task to be executed according to the target work task and the task deployment status before the robot receives the task deployment information specifically includes the following steps:

[0181] S1031: When there is a deployed work task, the target work task and the deployed work task are used as work tasks to be selected;

[0182] S1032: When there is a deployed work task, the target work task is used as a work task to be selected;

[0183] S1033: Determine the work task to be executed according to the execution period of the work task to be selected.

[0184] In one embodiment, after step S103, that is, determining the work task to be executed, the following steps are further included:

[0185] S105: Determine whether the work map corresponding to the executed work task is consistent with the current use map of the robot. Figure 1 To;

[0186] S106: When all are consistent, all the executed work tasks are displayed;

[0187] S107: When there is inconsistency, only the location Figure 1 The work tasks being performed are as follows.

[0188] It should be noted that, for more steps on the robot side in the task deployment method, please refer to the corresponding description of the aforementioned embodiment, and the description and explanation will not be repeated here.

[0189] It should be understood that the size of the serial numbers of the steps in the above embodiments does not mean the order of execution. The execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of the present application.

[0190] In one embodiment, a task deployment device is provided, which corresponds one-to-one to the robot scheduling platform side in the task deployment method in the above embodiment. Fig.10 As shown, the task deployment device includes a creation module 101, an acquisition module 102, a judgment module 103 and a storage module 104. The functional modules are described in detail as follows:

[0191] An establishing module 101 is used to establish a binding relationship between the robot and the map information of the map currently used by the robot;

[0192] An acquisition module 102 is used to acquire a task adding request, wherein the task adding request includes task deployment information corresponding to the robot, and the task deployment information includes a target work task and map information of a work map corresponding to the target work task;

[0193] A judgment module 103, configured to judge whether the working map is consistent with a current use map of the robot according to the binding relationship and the map information of the working map;

[0194] The saving module 104 is used to store the working map and the current location of the robot. Figure 1 If the robot is configured to be a task-oriented robot, the task deployment information corresponding to the robot is saved, so as to deploy work tasks for the robot through the task deployment information.

[0195] In one embodiment, the task deployment device further includes a display module, wherein:

[0196] The display module is used to issue a first prompt message when the working map is inconsistent with the current use map of the robot, and the first prompt message is used to indicate that the working map is inconsistent with the current use map of the robot.

[0197] In one embodiment, the task deployment device further includes a receiving module, a determining module and a sending module, wherein:

[0198] A receiving module, used for receiving a task pull request of the robot;

[0199] A determination module, used to respond to the task pull request and determine whether the task deployment information corresponding to the robot is saved;

[0200] The sending module is used to feed back the task deployment information corresponding to the robot to the robot when the task deployment information corresponding to the robot is saved.

[0201] In one embodiment, for the task deployment device, wherein:

[0202] The display module is also used to display the selectable stores according to a preset display mode;

[0203] The receiving module is further used to receive a store selection request, wherein the store selection request is used to select a target store from the optional stores;

[0204] The judgment module is further configured to, when receiving a binding request for binding the target store with the robot, determine whether all work maps corresponding to the deployed work tasks of the robot are consistent with the current use map of the robot. Figure 1 To;

[0205] The display module is also used to display all the work maps corresponding to the deployed work tasks in the current use area of ​​the robot. Figure 1 To display all the deployed work tasks of the robot.

[0206] In one embodiment, the task deployment device further includes a setting module, wherein:

[0207] A setting module is used for setting the task status of the deployed work task corresponding to the inconsistent work map to a map abnormal state when there is a work map inconsistent with the current use map of the robot among all the work maps corresponding to the deployed work task;

[0208] The display module is used to display all the deployed work tasks of the robot.

[0209] In one embodiment, for the task deployment device, wherein:

[0210] The receiving module is further used to receive an activation request for the disabled task;

[0211] The judgment module is further configured to, when receiving an activation request for the disabled task, determine whether the work map corresponding to the disabled task is consistent with the current use map of the robot. Figure 1 To;

[0212] The display module is further configured to issue a second prompt message when the working map corresponding to the disabled task is inconsistent with the current use map of the robot;

[0213] The setting module is also used to set the task status of the disabled task to a map abnormal state when the working map corresponding to the disabled task is inconsistent with the current use map of the robot, and the second prompt information is used to indicate that the current use map of the robot has been adjusted.

[0214] The setting module is also used to set the task state corresponding to the disabled task to the enabled state when the working map corresponding to the disabled task is consistent with the current use map of the robot.

[0215] For the specific definition of the task deployment device, please refer to the definition of the robot scheduling platform above, which will not be repeated here. Each module in the above-mentioned task deployment device can be implemented in whole or in part by software, hardware and a combination thereof. The above-mentioned modules can be embedded in or independent of the processor in the computer device in the form of hardware, or can be stored in the memory of the computer device in the form of software, so that the processor can call and execute the operations corresponding to the above modules.

[0216] In one embodiment, a task deployment device is provided, which corresponds one-to-one to the robot side in the task deployment method in the above embodiment. Fig.11 As shown, the task deployment device includes an acquisition module 202 and a deployment module 202. Each functional module is described in detail as follows:

[0217] The acquisition module 201 is used to acquire the task deployment information corresponding to the robot from the robot scheduling platform, wherein the task deployment information includes the target work task; wherein the task deployment information is the information deployed by the robot scheduling platform to implement the above-mentioned corresponding embodiment;

[0218] The deployment module 202 is used to deploy the work tasks of the robot according to the target work tasks.

[0219] In one embodiment, the task deployment device further includes a determination module and an execution module, wherein:

[0220] A determination module, used to determine the work task to be executed according to the target work task and the task deployment status before the robot receives the task deployment information;

[0221] An execution module is used to execute the work task to be executed.

[0222] In one embodiment, the determination module is specifically used for:

[0223] When there is the deployed work task, the target work task and the deployed work task are used as the work tasks to be selected;

[0224] When there is the deployed work task, the target work task is used as the work task to be selected;

[0225] The work task to be executed is determined according to the execution period of the work task to be selected.

[0226] In one embodiment, the task deployment device further includes a display module, which is specifically used to:

[0227] Determine whether the work map corresponding to the executed work task is consistent with the current use map of the robot Figure 1 To;

[0228] When all are consistent, all the executed work tasks are displayed;

[0229] When there is an inconsistency, only the Figure 1 The work tasks being performed are as follows.

[0230] For the specific definition of the task deployment device, please refer to the definition of robot adjustment above, which will not be repeated here. Each module in the above task deployment device can be implemented in whole or in part by software, hardware and their combination. The above modules can be embedded in or independent of the processor in the computer device in hardware form, or stored in the memory of the computer device in software form, so that the processor can call and execute the operations corresponding to the above modules.

[0231] In one embodiment, a computer readable storage medium is provided, on which a computer program is stored, and when the computer program is executed by a processor, the following steps are implemented:

[0232] Establishing a binding relationship between the robot and map information of a map currently used by the robot;

[0233] Obtaining a task adding request, wherein the task adding request includes task deployment information corresponding to the robot, and the task deployment information includes a target work task and map information of a work map corresponding to the target work task;

[0234] According to the binding relationship and the map information of the working map, it is determined whether the working map is related to the current location of the robot. Figure 1 To;

[0235] When the work map is consistent with the robot's current location Figure 1 If the robot is configured to be a task-oriented robot, the task deployment information corresponding to the robot is saved, so as to deploy work tasks for the robot through the task deployment information.

[0236] Among them, more steps or functions implemented when the computer program is executed by the processor can correspond to the steps or functions implemented by the robot scheduling platform in the aforementioned embodiment, and will not be repeated here.

[0237] In one embodiment, a computer readable storage medium is provided, on which a computer program is stored, and when the computer program is executed by a processor, the following steps are implemented:

[0238] Acquire task deployment information corresponding to the robot from a robot scheduling platform, wherein the task deployment information includes a target work task; wherein the task deployment information is information deployed by the robot scheduling platform of the aforementioned embodiment;

[0239] Deploy the robot's work tasks according to the target work tasks.

[0240] Among them, more steps or functions implemented when the computer program is executed by the processor can correspond to the steps or functions implemented by the robot in the aforementioned embodiment, and will not be repeated here.

[0241] Those skilled in the art can understand that all or part of the processes in the above-mentioned embodiment methods can be completed by instructing the relevant hardware through a computer program, and the computer program can be stored in a non-volatile computer-readable storage medium. When the computer program is executed, it can include the processes of the embodiments of the above-mentioned methods. Among them, any reference to memory, storage, database or other media used in the embodiments provided in this application can include non-volatile and / or volatile memory. Non-volatile memory can include read-only memory (ROM), programmable ROM (PROM), electrically programmable ROM (EPROM), electrically erasable programmable ROM (EEPROM) or flash memory. Volatile memory can include random access memory (RAM) or external cache memory. As an illustration and not limitation, RAM is available in many forms, such as static RAM (SRAM), dynamic RAM (DRAM), synchronous DRAM (SDRAM), double data rate SDRAM (DDRSDRAM), enhanced SDRAM (ESDRAM), synchronous link (Synchlink) DRAM (SLDRAM), memory bus (Rambus) direct RAM (RDRAM), direct memory bus dynamic RAM (DRDRAM), and memory bus dynamic RAM (RDRAM).

[0242] Those skilled in the art can clearly understand that for the convenience and simplicity of description, only the division of the above-mentioned functional units and modules is used as an example. In actual applications, the above-mentioned functions can be distributed and completed by different functional units and modules as needed, that is, the internal structure of the device can be divided into different functional units or modules to complete all or part of the functions described above.

[0243] The embodiments described above are only used to illustrate the technical solutions of the present application, rather than to limit them. Although the present application has been described in detail with reference to the aforementioned embodiments, a person skilled in the art should understand that the technical solutions described in the aforementioned embodiments may still be modified, or some of the technical features may be replaced by equivalents. Such modifications or replacements do not deviate the essence of the corresponding technical solutions from the spirit and scope of the technical solutions of the embodiments of the present application, and should all be included in the protection scope of the present application.

Claims

1. A robot dispatching platform, It is characterized in that The robot scheduling platform comprises a memory and a processor, wherein the memory stores a program code, and the processor is used to call the program code, and when the program code is executed, the robot scheduling platform is arranged as follows: Establishing a binding relationship between the robot and map information of a map currently used by the robot; Obtaining a task adding request, wherein the task adding request includes task deployment information corresponding to the robot, and the task deployment information includes a target work task and map information of a work map corresponding to the target work task; Determining whether the working map is consistent with a current usage map of the robot according to the binding relationship and the map information of the working map; When the work map is consistent with the current use map of the robot, the task deployment information corresponding to the robot is saved, so as to deploy work tasks for the robot through the task deployment information; When a binding request for binding a target store with the robot is received, determining whether all work maps corresponding to the work tasks deployed by the robot are consistent with the current use map of the robot; When there is a work map among all the work maps corresponding to the deployed work tasks that is inconsistent with the current map used by the robot, the task state of the deployed work task corresponding to the inconsistent work map is set to a map abnormal state; Display all the deployed work tasks of the robot and the corresponding task status.

2. The robot scheduling platform according to claim 1, It is characterized in that The robot scheduling platform is also arranged as follows: When the working map is inconsistent with the current use map of the robot, a first prompt message is issued, where the first prompt message is used to indicate that the working map is inconsistent with the current use map of the robot.

3. The robot scheduling platform according to claim 1, It is characterized in that The robot scheduling platform is also arranged as follows: receiving a task pull request for the robot; In response to the task pull request, determine whether task deployment information corresponding to the robot is saved; When the task deployment information corresponding to the robot is saved, the task deployment information corresponding to the robot is fed back to the robot.

4. The robot scheduling platform according to claim 1, It is characterized in that The robot scheduling platform is also arranged as follows: When all the work maps corresponding to the deployed work tasks are consistent with the current usage map of the robot, all the deployed work tasks of the robot are displayed.

5. The robot scheduling platform according to any one of claims 1 to 4, It is characterized in that All deployed work tasks of the robot include deactivated tasks; and the robot scheduling platform is further arranged as follows: When receiving an activation request for the disabled task, determining whether the work map corresponding to the disabled task is consistent with the current use map of the robot; When the working map corresponding to the disabled task is inconsistent with the current usage map of the robot, a second prompt message is issued, and the task status of the disabled task is set to a map abnormality state. The second prompt message is used to indicate that the current usage map of the robot has been adjusted.

6. The robot scheduling platform as claimed in claim 5, It is characterized in that The robot scheduling platform is also arranged as follows: When the working map corresponding to the disabled task is consistent with the current usage map of the robot, the task state corresponding to the disabled task is set to an enabled state.

7. A robot, It is characterized in that The robot comprises a memory and a processor, wherein the memory stores a program code, and the processor is used to call the program code, and when the program code is executed, the robot is arranged to: Acquire task deployment information corresponding to the robot from a robot scheduling platform, wherein the task deployment information includes a target work task; wherein the task deployment information is information deployed by the robot scheduling platform according to any one of claims 1 to 6; Deploy the robot's work tasks according to the target work tasks.

8. The robot according to claim 7, It is characterized in that After the robot deploys the work tasks of the robot according to the target work tasks, the robot is further arranged as follows: Determine the work task to be executed according to the target work task and the task deployment status before the robot receives the task deployment information; Execute the work task to be executed.

9. The robot according to claim 8, It is characterized in that When the robot determines the work task to be performed according to the target work task and the task deployment status before the robot receives the task deployment information, the robot is arranged as follows: Determine whether the robot has a deployed work task before receiving the task deployment information; When there is the deployed work task, the target work task and the deployed work task are used as the work tasks to be selected; When there is no deployed work task, the target work task is used as the work task to be selected; The work task to be executed is determined according to the execution period of the work task to be selected.

10. The robot according to claim 8, It is characterized in that After the robot determines to perform the work task, the robot is further arranged to: Determining whether the work map corresponding to the executed work task is consistent with the current use map of the robot; When all are consistent, all the executed work tasks are displayed; When there is an inconsistency, only the executed work tasks that are consistent with the map are displayed.

11. A task deployment method, It is characterized in that The task deployment method comprises: Establishing a binding relationship between the robot and the map currently used by the robot; Obtaining a task adding request, wherein the task adding request includes task deployment information corresponding to the robot, and the task deployment information includes a target work task and map information of a work map corresponding to the target work task; Determining whether the working map is consistent with a current usage map of the robot according to the binding relationship and the map information of the working map; When the work map is consistent with the current use map of the robot, the task deployment information corresponding to the robot is saved, so as to deploy work tasks for the robot through the task deployment information; When a binding request for binding a target store with the robot is received, determining whether all work maps corresponding to the work tasks deployed by the robot are consistent with the current use map of the robot; When there is a work map among all the work maps corresponding to the deployed work tasks that is inconsistent with the current map used by the robot, the task state of the deployed work task corresponding to the inconsistent work map is set to a map abnormal state; Display all the deployed work tasks of the robot and the corresponding task status.

12. A task deployment method, It is characterized in that The task deployment method comprises: Acquire task deployment information corresponding to the robot from a robot scheduling platform, wherein the task deployment information includes a target work task; wherein the task deployment information is information deployed by the robot scheduling platform according to any one of claims 1 to 6; Deploy the robot's work tasks according to the target work tasks.

13. A robot task automatic deployment system, It is characterized in that It comprises a robot scheduling platform as described in any one of claims 1-6, and a robot as described in any one of claims 7-10.

14. A computer-readable storage medium storing a computer program. It is characterized in that When the computer program is executed by a processor, it implements the steps implemented by the robot scheduling platform as described in any one of claims 1 to 6, or implements the steps implemented by the robot as described in any one of claims 7 to 10.

Images