Robot control method and apparatus, robot, device and medium
By acquiring and matching the robot's target date type and task execution strategy, the problem of inflexible task execution methods by the robot at set times is solved, achieving both flexibility and accuracy in task execution.
Patent Information
- Authority / Receiving Office
- WO · WO
- Patent Type
- Applications
- Current Assignee / Owner
- BEIJING ROBOROCK INNOVATION TECH CO LTD
- Filing Date
- 2025-11-05
- Publication Date
- 2026-05-21
AI Technical Summary
In existing technologies, the timed execution of tasks by robots is not flexible enough and cannot meet the task execution needs of users.
By acquiring the task configuration information of the target task, including the target date type and task execution strategy, the matching relationship between the current date and the target date type is determined, and the robot is controlled to execute the task based on this.
It achieves flexibility and accuracy in robot task execution, and can adjust the task execution strategy according to different date types, thereby better meeting user needs.
Smart Images

Figure CN2025132789_21052026_PF_FP_ABST
Abstract
Description
Robot control methods, devices, robots, equipment, and media
[0001] Cross-references to related applications
[0002] This disclosure claims priority to China National Intellectual Property Administration (CNIPA) application No. 202411613372.1 filed on November 12, 2024, entitled “Control Method, Apparatus, Robot, Equipment, and Medium”, the entire contents of which are incorporated herein by reference. Technical Field
[0003] This application relates to, but is not limited to, the field of robotics, and in particular to a robot control method, device, robot, equipment, and medium. Background Technology
[0004] With the rapid development of technology, robots are being used more and more widely. Among related technologies, robots can perform tasks on a scheduled basis, for example, by starting a task daily or on a specific day of the week. However, this scheduled task execution method is not flexible enough and cannot adequately meet users' task execution needs.
[0005] It should be noted that the information disclosed in the background section above is only used to enhance the understanding of the background of this disclosure, and therefore may include information that does not constitute prior art known to those skilled in the art. Summary of the Invention
[0006] In view of this, embodiments of this application provide at least one robot control method, device, robot, equipment, and medium.
[0007] The technical solution of this application embodiment is implemented as follows:
[0008] This application provides a robot control method, the method comprising:
[0009] In response to the arrival of the robot's target task execution time, the task configuration information of the target task is obtained; the task configuration information includes the target date type corresponding to the target task, and the task execution strategy corresponding to the target date type;
[0010] Determine the matching relationship between the current date and the target date type;
[0011] Based on the matching relationship and the task execution strategy, the robot is controlled to perform the target task.
[0012] This application provides a control device, which includes:
[0013] The first acquisition module is used to acquire the task configuration information of the target task in response to the execution time of the target task arriving at the robot; the task configuration information includes the target date type corresponding to the target task and the task execution strategy corresponding to the target date type;
[0014] The first determining module is used to determine the matching relationship between the current date and the target date type;
[0015] The control module is used to control the robot to perform the target task based on the matching relationship and the task execution strategy.
[0016] This application provides a robot, including the control device provided in the above embodiments.
[0017] This application provides a computer device including a memory and a processor. The memory stores a computer program that can run on the processor. When the processor executes the program, it implements some or all of the steps in the above-described method.
[0018] This application provides a computer-readable storage medium storing a computer program thereon, which, when executed by a processor, implements some or all of the steps in the above-described method.
[0019] This application provides a computer program including computer-readable code. When the computer-readable code is run in a computer device, the processor in the display device executes some or all of the steps in the above-described method.
[0020] This application provides a computer program product, including a computer program or instructions, which, when executed by a processor, implement some or all of the steps in the above-described method. Attached Figure Description
[0021] Figure 1 is a schematic diagram of the implementation process of a robot control method provided in an embodiment of this application;
[0022] Figure 2 is a schematic diagram of the implementation flow of a robot control method provided in an embodiment of this application;
[0023] Figure 3 is a schematic diagram of the implementation flow of a robot control method provided in an embodiment of this application;
[0024] Figure 4 is a schematic diagram of the implementation flow of a robot control method provided in an embodiment of this application;
[0025] Figure 5 is a schematic diagram of the implementation flow of a robot control method provided in an embodiment of this application;
[0026] Figure 6 is a schematic diagram of the composition structure of a control device provided in an embodiment of this application;
[0027] Figure 7 is a schematic diagram of the composition structure of a robot provided in an embodiment of this application;
[0028] Figure 8 is a schematic diagram of the hardware entity of a computer device provided in an embodiment of this application. Detailed Implementation
[0029] To make the objectives, technical solutions, and advantages of this application clearer, the technical solutions of this application are further described in detail below with reference to the accompanying drawings and embodiments. The described embodiments should not be regarded as limitations on this application. All other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of this application.
[0030] In the following description, references to "some embodiments" refer to a subset of all possible embodiments. It is understood that "some embodiments" may be the same or different subsets of all possible embodiments and may be combined with each other without conflict. The terms "first / second / third" are used merely to distinguish similar objects and do not represent a specific ordering of objects. It is understood that "first / second / third" may be interchanged in a specific order or sequence where permitted, so that the embodiments of this application described herein can be implemented in an order other than that illustrated or described herein.
[0031] Unless otherwise defined, all technical and scientific terms used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this application pertains. The terminology used herein is for descriptive purposes only and is not intended to limit the scope of this application.
[0032] This application provides a robot control method. This method can be executed by a processor of a computer device. The computer device can refer to a robot, server, laptop, tablet, desktop computer, smart TV, set-top box, mobile device (e.g., mobile phone, portable video player, personal digital assistant, dedicated messaging device, portable gaming device), or any other device with data processing capabilities. The robot can include, but is not limited to, at least one of home robots and industrial robots. In implementation, the robot's structure can be determined according to actual conditions; for example, the robot can include autonomous mobile robots or robots that cannot move autonomously. This application does not limit this aspect.
[0033] In some implementations, the robot is a mobile robot. For example, a mobile robot may be at least one of the following: cleaning robots (such as sweeping robots, floor scrubbers, mopping robots, and combined washing and mopping robots), guiding robots, and service robots.
[0034] Figure 1 is a schematic flowchart of a robot control method provided in an embodiment of this application. As shown in Figure 1, the method includes the following steps S101 to S103:
[0035] Step S101: In response to the arrival of the execution time of the target task of the robot, obtain the task configuration information of the target task; the task configuration information includes the target date type corresponding to the target task and the task execution strategy corresponding to the target date type.
[0036] Step S102: Determine the matching relationship between the current date and the target date type.
[0037] Step S103: Based on the matching relationship and the task execution strategy, control the robot to execute the target task.
[0038] Here, the target task is any suitable task to be performed by the robot, and this application embodiment does not limit this.
[0039] In some implementations, the target task can be a pre-set timed task, and the execution time of the target task can be preset by the user according to actual needs. For example, when the robot is a cleaning robot, the target task can include, but is not limited to, at least one of timed cleaning tasks, timed self-cleaning tasks, etc. As another example, when the robot is a cooking robot, the target task can include, but is not limited to, at least one of timed cooking tasks, timed keep-warming tasks, etc.
[0040] The target date type can be a specific date type pre-configured for the target task. Each date type can represent a predefined special date category. For example, date types can include, but are not limited to, holidays, weekdays, humid weather, hottest days of summer, pet shedding season, early rise days, exercise days, and diet days.
[0041] The task execution strategy corresponding to the target date type can be a pre-configured strategy for executing tasks on the dates corresponding to that target date type. In implementation, the task execution strategy can be pre-set by the user according to actual needs, and this application embodiment does not limit this. For example, the task execution strategy may include, but is not limited to, executing the task, abandoning the task, executing the task according to the target execution parameters, and delaying the execution of the task.
[0042] The matching relationship between the current date and the target date type indicates whether the current date belongs to the target date type. For example, if the current date matches the target date type, it means that the current date belongs to the target date type; if the current date does not match the target date type, it means that the current date does not belong to the target date type.
[0043] In some implementations, at least one date type and date matching relationship can be pre-defined. By querying this matching relationship, the matching relationship between the current date and the target date type can be determined.
[0044] In some implementations, the matching relationship between the current date and the target date type can be determined based on target matching information corresponding to the target date type. Each date type can correspond to specific matching information. The target matching information is the matching information corresponding to the target date type. The matching information corresponding to a date type can include at least one condition that the date matching that date type satisfies, thereby determining whether a date belongs to that date type based on the matching information. In some implementations, the matching information corresponding to a date type can include at least one of the date range, geographical range, year, etc., corresponding to that date type. For example, whether a date belongs to that date type can be determined by determining whether a date belongs to the date range corresponding to that date type.
[0045] In some implementations, the target task and its configuration information can be pre-configured by the user. For example, a control program (APP) for the robot can be run on a computer device, and the user can configure at least one scheduled task to be executed (including the target task) and the corresponding task configuration information for each scheduled task according to actual needs.
[0046] In some implementations, at least one date type can be pre-configured. When configuring task configuration information for a target task, the user can select a suitable date type from these at least one date type as the target date type and configure a task execution strategy corresponding to that target date type. For example, if the robot is a cleaning robot and the target task is mopping, to reduce the impact of mopping on the user's rest during holidays, the user can select a holiday as the target date type and configure the corresponding task execution strategy as either abandoning or delaying execution. Similarly, if the robot is a cooking robot and the target task is cooking, to reduce food intake on diet days, the user can select a diet day as the target date type and configure the corresponding task execution strategy as either abandoning execution or performing the cooking task with reduced ingredients.
[0047] In some implementations, if the current date matches the target date type, the robot can be controlled to perform the target task according to the task execution strategy. For example, if the target date type is a holiday, and the current date is a holiday, the robot can be controlled to perform the target task according to the task execution strategy.
[0048] In some implementations, even if the current date and the target date type do not match, the robot can be controlled to execute the target task according to the task execution strategy. For example, if the target date type is a weekday, and the current date is not a weekday, the robot can be controlled to execute the target task according to the task execution strategy.
[0049] In some implementations, the task execution strategy may include a first execution strategy and a second execution strategy. If the current date matches the target date type, the robot is controlled to execute the target task according to the first execution strategy; if the current date does not match the target date type, the robot is controlled to execute the target task according to the second execution strategy. For example, if the robot is a cleaning robot, the target task is mopping, and the target date type is a humid, rainy season, the first task execution strategy corresponding to a humid season is to perform the mopping task with a first water consumption, and the second task execution strategy corresponding to a humid season is to perform the mopping task with a second water consumption. Since the first water consumption is less than the second water consumption, if the current date matches a humid season, the robot can be controlled to perform the mopping task with the first water consumption to make the floor drier and save water resources; or, if the current date does not match a humid season, the robot can be controlled to perform the mopping task with the second water consumption to achieve a better cleaning effect. For example, if the robot is a cleaning robot and its target task is vacuuming, and the target date is pet shedding season, the first task execution strategy corresponding to pet shedding season is to perform vacuuming with the first suction power, and the second task execution strategy corresponding to pet shedding season is to perform vacuuming with the second suction power. If the first suction power is greater than the second suction power, then if the current date matches pet shedding season, the robot can be controlled to perform vacuuming with the first suction power to better remove pet hair from the environment; or, if the current date does not match pet shedding season, the robot can be controlled to perform vacuuming with the second suction power to reduce power consumption.
[0050] In some implementations, the control method can be executed by the robot's control device, which can control the robot to perform the target task based on matching relationships and task execution strategies.
[0051] In some implementations, the control method can be executed by a server, which can issue target tasks to the robot based on matching relationships and task execution strategies to control the robot to execute the target tasks. For example, the server can be a cloud server.
[0052] In this embodiment, when the execution time of the robot's target task arrives, firstly, the target date type corresponding to the target task and the task execution strategy corresponding to the target date type are obtained; then, the matching relationship between the current date and the target date type is determined; finally, based on the matching relationship and the task execution strategy, the robot is controlled to execute the target task. In this way, the robot's task execution can be flexibly and accurately controlled according to the target date type and the task execution strategy corresponding to the target date type, thereby better meeting the user's task execution needs for the robot.
[0053] In some embodiments, the above method may further include the following steps S111 and S112:
[0054] Step S111: Obtain date configuration information, which includes at least one date type and matching information corresponding to each date type.
[0055] Here, the date configuration information can be manually configured by the user, obtained from a third-party platform, or pre-stored in the robot's storage device or obtained via the network; this application embodiment does not limit this.
[0056] In some implementations, target matching information corresponding to the target date type can be determined based on the date configuration information; and the matching relationship between the current date and the target date type can be determined based on the target matching information corresponding to the target date type.
[0057] The third-party platforms may include, but are not limited to, at least one of the following: holiday announcement platforms, calendar service platforms, weather platforms, travel planning platforms, and diet planning platforms. For example, if the date type includes "return to spring" weather, matching information for "return to spring" weather can be obtained from a weather platform. This matching information may include the geographical range, year, and / or date range of the most recent "return to spring" weather. Similarly, if the date type includes "exercise day," matching information for exercise days can be obtained from a travel planning platform. This matching information may include the date range where the user plans to exercise. Furthermore, if the date type includes "diet day," matching information for diet days can be obtained from a diet planning platform. This matching information may include the date range where the user plans to diet.
[0058] In some implementations, users can pre-configure at least one date type and matching information corresponding to each date type, and store the at least one date type and matching information corresponding to each date type in a server.
[0059] In some implementations, when the control method is executed by a robot's control device, the control device can obtain date configuration information from a server and / or a third-party platform. In practice, the control device can actively retrieve the date configuration information from the server and / or the third-party platform, or the server and / or the third-party platform can actively push the date configuration information to the control device, so that the control device obtains the date configuration information. This application does not limit this approach.
[0060] In some implementations, the date configuration information can be pre-configured before the robot leaves the factory, or it can be updated with each robot firmware upgrade. For example, for statutory holidays, the matching information corresponding to the statutory holidays (e.g., holidays for the next 10 years) can be directly written into the robot firmware at the factory, or this matching information can be updated with each firmware upgrade.
[0061] Step S112: Based on the date configuration information, determine the target matching information corresponding to the target date type.
[0062] In some implementations, the latest date configuration information can be periodically retrieved, allowing for the determination of target matching information corresponding to the target date type based on this updated information. This ensures the timeliness of date configuration information updates. For example, temporarily adjusted holidays or sudden humid weather caused by typhoons can be promptly updated to the latest target configuration information, making the robot's task execution more flexible.
[0063] For example, it can periodically retrieve the latest date configuration information manually configured by the user. Alternatively, it can periodically retrieve the latest date configuration information from a third-party platform.
[0064] In some implementations, where the control method is executed by a robot's control device, the control device can periodically obtain the latest date configuration information from a server and / or a third-party platform. For example, the robot's control device can obtain the latest date configuration information from a server and / or a third-party platform at 00:00 every day.
[0065] In the above embodiments, by obtaining date configuration information, which includes at least one date type and matching information corresponding to each date type, and determining the target matching information corresponding to the target date type based on the date configuration information, the target matching information corresponding to the target date type can be obtained quickly and accurately, thereby more accurately determining the matching relationship between the current date and the target date type.
[0066] In some embodiments, the target date type has corresponding target matching information, which includes a target date range. Step S102 above may include at least one of steps S121 and S122:
[0067] Step S121: If the current date falls within the target date range, determine that the current date matches the target date type.
[0068] Step S122: If the current date does not fall within the target date range, determine that the current date does not match the target date type.
[0069] Here, the target date range refers to the date range that belongs to this target date type.
[0070] Understandably, if the current date falls within the target date range, it indicates that the current date belongs to the target date type, meaning the current date matches the target date type. If the current date does not fall within the target date range, it indicates that the current date does not belong to the target date type, meaning the current date does not match the target date type.
[0071] In some implementations, the target date range may include at least one date within a set future period that matches the target date type. For example, if the target date type is a public holiday, the target date range may include the dates of at least one public holiday within the next six months. Similarly, if the target date type is a diet day, the target date range may include at least one date within the next month on which the user plans to diet.
[0072] In some implementations, the target date range may include at least one date interval within a predetermined future period that matches the target date type. For example, if the target date type is the "return of spring" weather pattern, the target date range may include date intervals within the next six months that are expected to fall under the "return of spring" weather pattern. Similarly, if the target date type is the "dog days of summer" weather pattern, the target date range may include date intervals within the next three months that fall under the "dog days of summer" weather pattern.
[0073] In some implementations, the target date range may include at least one year and at least one date within each year that matches the target date type. For example, if the target date type is a public holiday, the target date range may include at least one year and at least one public holiday date within each year.
[0074] In some implementations, the target date range may include at least one year and at least one date interval within each year that matches the target date type. For example, if the target date type is spring, the target date range may include at least one year and a date interval within each year that belongs to spring. Similarly, if the target date type is the hottest period of summer (the "dog days"), the target date range may include at least one year and a date interval within each year that belongs to the hottest period of summer.
[0075] In the above embodiments, the target matching information includes a target date range. If the current date falls within the target date range, it is determined that the current date matches the target date type; if the current date does not fall within the target date range, it is determined that the current date does not match the target date type. This allows for quick and accurate determination of whether the current date matches the target date type.
[0076] In some embodiments, the target matching information further includes a target geographical range. Step S121 above may include the following step S131:
[0077] Step S131: If the current date falls within the target date range and the location of the robot falls within the target geographical range, determine that the current date matches the target date type.
[0078] Here, the target geographical area may include, but is not limited to, at least one of the following: region, country, province, or city.
[0079] It is understandable that different regions have different climates, holiday policies, etc., so the corresponding date range for the same date type may differ in different regions, or different date types may apply to different regions. For example, if the target date type is a regional holiday, the target region range can include the region corresponding to region A, and the target date range can include the applicable holiday dates within the target region. That is, the target date range can include at least one holiday date specified in the applicable holiday policy within the region corresponding to region A. Thus, if the robot's location is within the region corresponding to region A, and the current date falls on at least one holiday date specified in the applicable holiday policy within the region corresponding to region A, then the current date is determined to match a regional holiday. Similarly, if the target date type is the heating season, the target region range can include the region with centralized heating within a future set period, and the target date range can include the centralized heating date range within that target region. Thus, if the robot's location is within that target region, and the current date falls within the centralized heating date range within that target region, then the current date is determined to match the heating season.
[0080] In the above embodiments, by including the target geographical range in the target matching information, if the current date belongs to the target date range and the robot's location belongs to the target geographical range, it is determined that the current date matches the target date type. In this way, the geographical range applicable to the target date type and the corresponding date range can be comprehensively considered to determine the matching relationship between the current date and the target date type, thereby making the judgment more accurate and better meeting the user's task execution needs.
[0081] In some embodiments, step S103 may include the following step S141:
[0082] Step S141: If the matching relationship indicates that the current date matches the target date type, control the robot to execute the target task based on the task execution strategy.
[0083] Here, the task execution strategy may include, but is not limited to, at least one of the following: executing the task, abandoning the task, executing the task according to the target execution parameters, and delaying the execution of the task.
[0084] For example, if the robot is a cleaning robot, the target task is mopping, the target date type is a holiday, and the task execution strategy corresponding to the holiday is to abandon or delay execution, then if the current date matches a holiday, the robot can be controlled to abandon or delay the mopping task; or, if the current date does not match a holiday, the robot can be controlled to execute the mopping task.
[0085] For example, if the robot is a cooking robot, the target task is a cooking task, the target date type is a diet day, and the task execution strategy corresponding to the diet day is to abandon the task or perform the cooking task with reduced ingredients, then if the current date matches the diet day, the robot can be controlled to abandon the mopping task or perform the cooking task with reduced ingredients; or, if the current date does not match the diet day, the robot can be controlled to perform the mopping task or perform the cooking task with the normal amount of ingredients.
[0086] In the above embodiments, when the matching relationship indicates that the current date and the target date type match, the robot is controlled to execute the target task based on the task execution strategy. This allows for more flexible control of the robot's task execution, thereby better meeting the user's task execution needs.
[0087] In some embodiments, controlling the robot to perform the target task based on the task execution strategy described in step S141 above includes at least one of the following steps S151 and S152:
[0088] Step S151: If the task execution strategy includes abandoning the task, stop controlling the robot to execute the target task;
[0089] Here, if the current date matches the target date type, and the task execution strategy includes abandoning the task, then the robot is stopped from executing the target task.
[0090] In some implementations, when the control method is executed by the robot's control device, if the task execution strategy includes abandoning the task, the control device can stop controlling the robot to execute the target task.
[0091] In some implementations, where the control method is performed by a server, if the task execution strategy includes abandoning the task, the server can stop issuing the target task to the robot.
[0092] Step S152: If the task execution strategy includes performing a task, control the robot to perform the target task.
[0093] Here, if the current date and the target date type match, and the task execution strategy includes executing a task, then the robot is controlled to execute the target task.
[0094] In some implementations, when the control method is performed by the robot's control device, if the task execution strategy includes performing a task, the control device can control the robot to perform the target task.
[0095] In some implementations, where the control method is performed by a server, if the task execution strategy includes performing a task, the server can issue the target task to the robot so that the robot can perform the target task.
[0096] In some embodiments, step S152 may include the following step S161:
[0097] Step S161: If the task execution strategy includes executing the task according to the target execution parameters, control the robot to execute the target task according to the target execution parameters.
[0098] Here, the target execution parameters can be pre-configured according to actual needs, and this application embodiment does not limit this.
[0099] In some implementations, when the target task includes mopping, the target execution parameters may include, but are not limited to, at least one of the following: target working level, target working mode, target water consumption, etc.
[0100] In some implementations, when the target task includes a vacuuming task or a water suction task, the target execution parameters may include, but are not limited to, at least one of the target operating level, target suction power, etc.
[0101] In some implementations, when the target task includes a cooking task, the target execution parameters may include, but are not limited to, at least one of the target cooking mode, target ingredient quantity, etc.
[0102] In some implementations, when the control method is executed by the robot's control device, if the task execution strategy includes executing the task according to the target execution parameters, the control device can control the robot to execute the target task according to the target execution parameters.
[0103] In some implementations, when the control method is executed by a server, if the task execution strategy includes executing the task according to target execution parameters, the server can issue a target task with the target execution parameters to the robot, so that the robot can execute the target task according to the target execution parameters.
[0104] In the above embodiments, if the current date and the target date type match, and if the task execution strategy includes executing the task according to the target execution parameters, the robot is controlled to execute the target task according to the target execution parameters. This allows for more flexible control of the robot's task execution, thereby better meeting the user's task execution needs.
[0105] The following describes the application of the robot control method provided in the embodiments of this application in a real-world scenario, using a cleaning robot as an example.
[0106] In related technologies, cleaning robots typically only have one way of executing tasks in terms of time: scheduled start-up. For example, a cleaning robot can provide the function of performing a certain task at a set time every day or at a set time on a certain day of the week. However, in reality, this time-dimensional setting is not flexible or user-friendly enough.
[0107] The robot control method of this application embodiment can provide users with a task execution mode that is more in line with actual user experience. For example, a task can be not started on a certain holiday, a task can be started on another holiday, a water suction task can be started during the humid season, and a high-suction sweeping task can be started during pet shedding season. These tasks do not require the user to start them manually on the corresponding special dates. Instead, the user only needs to pre-set the task configuration information and the date configuration information including at least one date type. Subsequently, the system determines when to start the corresponding task based on the set task configuration information and the date configuration information in the cloud.
[0108] In some implementations, users can configure at least one special date type (corresponding to the date type in the aforementioned embodiments) on the server, as well as matching information corresponding to each special date type. The matching information corresponding to the special date type includes the name, date range, year, country or region corresponding to the special date type.
[0109] In some implementations, the special date types in the date configuration information can also come from third-party platforms and be imported into the server via a software development kit (SDK). For example, the region, year, and date range corresponding to the "return to spring" weather pattern can be obtained from a third party to obtain matching information corresponding to this special date type.
[0110] In some implementations, the cleaning robot can periodically retrieve a list of special date types and matching information corresponding to each special date type from the server (corresponding to the date configuration information in the aforementioned embodiments). For example, the cleaning robot can retrieve the latest date configuration information from the server when it restarts at midnight each day.
[0111] In some implementations, when setting up a task, the user can choose to start the task on a date that matches a specific date type.
[0112] In some implementations, the task can be executed in two ways: the cleaning robot executes the task locally on a scheduled basis, or the server periodically sends the task to the cleaning robot to control its execution.
[0113] In some implementations, in a scheme where the cleaning robot performs tasks locally on a timed basis, the cleaning robot detects the time when the target task is about to be executed, and then determines whether the current date belongs to a special date type based on at least one special date type stored locally and the matching information corresponding to each special date type. If it is a special date type, the task is started.
[0114] Figure 2 is a schematic flowchart illustrating the implementation of a robot control method according to an embodiment of this application. This method can be applied to scenarios where a cleaning robot performs tasks locally at regular intervals. As shown in Figure 2, the method includes the following steps S201 to S207:
[0115] Step S201: Configure at least one special date type on the server, as well as the name, date range, year, country, or region corresponding to each special date type;
[0116] In some implementations, the cleaning robot operator or other users may configure at least one special date type and the name, date range, year, country or region corresponding to each special date type on the server.
[0117] In some implementations, at least one special date type and the name, date range, year, country, or region corresponding to each special date type can be obtained from third-party data provided by a third-party platform.
[0118] Step S202: The APP reads the list of currently supported special date types from the server;
[0119] Step S203: The user sets a target task for the cleaning robot through the APP based on a list of special date types;
[0120] After the app obtains the list of special date types, users can use the app to select the target date type corresponding to the target task from the list, thereby completing the setting of the target task and pushing the set target task to the cleaning robot.
[0121] Step S204: The cleaning robot obtains the latest date configuration information from the server;
[0122] This date configuration information includes the latest list of special date types, as well as the name, date range, year, country, or region corresponding to each special date type.
[0123] In some implementations, the cleaning robot can obtain the latest date configuration information from the server upon startup.
[0124] In some implementations, the cleaning robot can retrieve the latest date configuration information from the server at regular intervals each day.
[0125] Step S205: When the execution time of the target task is reached, the cleaning robot determines whether the current date is the target date type;
[0126] If yes, proceed to step S206; if no, proceed to step S207.
[0127] The cleaning robot can determine the date range, year, country, or region corresponding to the target date type from the latest date configuration information based on the target date type corresponding to the target task, and determine whether the current date is the target date type based on the date range, year, country, or region corresponding to the target date type.
[0128] Step S206: The cleaning robot performs the target task;
[0129] In step S207, the cleaning robot abandons the target task.
[0130] In some implementations, in a scheme where a server periodically sends tasks to a cleaning robot to control the robot to perform those tasks, the server can determine whether the current date is a special date type based on the latest configured date information when sending the task. If it is a special date type, the task is sent to the cleaning robot.
[0131] Figure 3 is a schematic flowchart illustrating the implementation of a robot control method according to an embodiment of this application. This method can be applied to scenarios where a server periodically sends tasks to a cleaning robot to control the cleaning robot to perform those tasks. As shown in Figure 3, the method includes the following steps S301 to S306:
[0132] Step S301: Configure at least one special date type on the server, as well as the name, date range, year, country, or region corresponding to each special date type;
[0133] Step S302: The APP reads the list of currently supported special date types from the server;
[0134] Step S303: The user sets the target task for the cleaning robot to the server through the APP based on a list of special date types;
[0135] After the app obtains the list of special date types, users can use the app to select the target date type corresponding to the target task from the list, thereby completing the setting of the target task and pushing the set target task to the server.
[0136] Step S304: Upon reaching the execution time of the target task, the server determines whether the current date is of the target date type;
[0137] If yes, proceed to step S305; if no, proceed to step S306.
[0138] Specifically, the server can determine the date range, year, country, or region corresponding to the target date type from the latest date configuration information based on the target date type corresponding to the target task, and determine whether the current date is the target date type based on the date range, year, country, or region corresponding to the target date type.
[0139] Step S305: Issue the target task to the cleaning robot;
[0140] Step S306: Abandon issuing the target task to the cleaning robot.
[0141] The robot control method provided in the embodiments of this application can achieve functions similar to the following:
[0142] 1) Perform a whole-house sweeping and mopping task at 8:00 AM on every legal workday;
[0143] 2) During the Christmas holiday, perform a single floor-mopping task every day at 10:00 AM;
[0144] 3) At 12:00 every day during pet shedding season, perform a pure sweeping task.
[0145] In some implementations, users can choose to configure the cleaning robot to skip dates that fall under a special date type when performing tasks. In this case, the cleaning robot will abandon the task on dates that fall under a special date type, or the server will abandon issuing the task on dates that fall under a special date type.
[0146] This allows for functionality similar to the following: a sweeping and mopping task to be performed at 10:00 AM every Monday, Wednesday, and Friday, but skipping all public holidays.
[0147] In some implementations, during task configuration, execution parameters for specific date types can also be configured, such as setting the working level, suction power, and / or water consumption as needed. When the cleaning robot performs the task on a date corresponding to a specific date type, it can adjust to the configured execution parameters or adjust the execution parameters as needed. Alternatively, when the server issues the task, it issues the task according to the configured execution parameters.
[0148] In this way, a function similar to the following can be achieved: when the humid weather arrives at 10:00 every day, the mopping task is started. If the cleaning robot determines that the water volume needs to be reduced due to the humid weather, it will use the minimum amount of water that can be supported when performing the mopping task.
[0149] Figure 4 is a schematic flowchart illustrating the implementation of a robot control method according to an embodiment of this application. This method can be applied to scenarios where a cleaning robot performs tasks locally at set times. As shown in Figure 4, the method includes the following steps S401 to S409:
[0150] Step S401: Configure at least one special date type on the server, with each special date type having a corresponding name, date range, year, country, or region;
[0151] For certain special date types, you can also configure the execution parameters of the task on the date corresponding to that special date type.
[0152] Step S402: The APP reads the list of currently supported special date types from the server;
[0153] Step S403: The user sets a target task for the cleaning robot through the APP based on a list of special date types;
[0154] Step S404: The cleaning robot obtains the latest date configuration information from the server;
[0155] Step S405: When the execution time of the target task is reached, the cleaning robot determines whether the current date is the target date type;
[0156] If yes, proceed to step S406; if no, proceed to step S407.
[0157] Step S406: The cleaning robot determines whether the target date type corresponds to the target execution parameters;
[0158] If yes, proceed to step S408; otherwise, proceed to step S409.
[0159] Step S407: The cleaning robot abandons the target task;
[0160] Step S408: The cleaning robot performs the target task according to the target execution parameters;
[0161] Step S409: The cleaning robot performs the target task according to the default execution parameters.
[0162] Figure 5 is a schematic flowchart illustrating the implementation of a robot control method according to an embodiment of this application. This method can be applied to scenarios where a server periodically sends tasks to a cleaning robot to control the cleaning robot to perform those tasks. As shown in Figure 5, the method includes the following steps S501 to S508:
[0163] Step S501: Configure at least one special date type on the server, as well as the name, date range, year, country, or region corresponding to each special date type;
[0164] For certain special date types, you can also configure the execution parameters of the task on the date corresponding to that special date type.
[0165] Step S502: The APP reads the list of currently supported special date types from the server;
[0166] Step S503: The user sets the target task for the cleaning robot to the server through the APP based on a list of special date types;
[0167] Step S504: Upon reaching the execution time of the target task, the server determines whether the current date is of the target date type;
[0168] If yes, proceed to step S505; if no, proceed to step S506.
[0169] Step S505: The server determines whether the target date type corresponds to the target execution parameters;
[0170] If yes, proceed to step S507; otherwise, proceed to step S508.
[0171] Step S506: Abandon issuing the target task to the cleaning robot;
[0172] Step S507: The server sends a target task with target execution parameters to the cleaning robot;
[0173] In step S508, the server sends a target task with default execution parameters to the cleaning robot.
[0174] In some implementations, the server can proactively send the latest date configuration information to the cleaning robot without waiting for the robot to periodically request it. This maximizes the timeliness of the date configuration information updates. For example, during periods of sudden and prolonged thunderstorms causing humid weather, the cleaning robot can automatically start its water-absorbing task to keep the floor dry, without requiring the user to set up mopping every time. Furthermore, the server can proactively send the latest date configuration information to the cleaning robot, allowing it to perform its water-absorbing task more promptly.
[0175] The robot control method provided in this application can reduce the frequency of user-set tasks. For example, a user may only want the cleaning robot to perform cleaning tasks at 10:00 AM on weekdays, allowing the task to be performed when no one is home, thus minimizing disturbance. According to this application, the user does not need to remember to turn off the scheduled task during the National Day holiday, which includes Monday to Friday; the cleaning robot can automatically abandon the cleaning task during the holiday.
[0176] This application provides a control device that can be applied to a robot or a server. Figure 6 is a schematic diagram of the composition of a control device provided in this application. As shown in Figure 6, the control device 600 includes: a first acquisition module 610, a first determination module 620, and a control module 630, wherein:
[0177] The first acquisition module 610 is used to acquire task configuration information of the target task in response to the execution time of the target task of the robot; the task configuration information includes the target date type corresponding to the target task and the task execution strategy corresponding to the target date type;
[0178] The first determining module 620 is used to determine the matching relationship between the current date and the target date type;
[0179] The control module 630 is used to control the robot to perform the target task based on the matching relationship and the task execution strategy.
[0180] In some embodiments, the above apparatus further includes: a second acquisition module, configured to acquire date configuration information, the date configuration information including at least one date type and matching information corresponding to each date type; and a second determination module, configured to determine target matching information corresponding to the target date type based on the date configuration information.
[0181] In some embodiments, the target date type has corresponding target matching information, the target matching information including a target date range; the first determining module is further configured to: determine that the current date matches the target date type if the current date belongs to the target date range; determine that the current date does not match the target date type if the current date does not belong to the target date range.
[0182] In some embodiments, the target matching information further includes a target geographical range; the first determining module is further configured to: determine that the current date matches the target date type if the current date belongs to the target date range and the location of the robot belongs to the target geographical range.
[0183] In some embodiments, the control module is further configured to: control the robot to perform the target task based on the task execution strategy when the matching relationship characterizes that the current date matches the target date type.
[0184] In some embodiments, the control module is further configured to: stop controlling the robot to execute the target task when the task execution strategy includes abandoning the task; and control the robot to execute the target task when the task execution strategy includes executing the task.
[0185] In some embodiments, the control module is further configured to: control the robot to execute the target task according to the target execution parameters when the task execution strategy includes executing the task according to the target execution parameters.
[0186] This application provides a robot, as shown in FIG7, the robot 700 including the control device 600 in the above embodiment.
[0187] The descriptions of the above device and robot embodiments are similar to those of the above method embodiments, and have similar beneficial effects. For technical details not disclosed in the device and robot embodiments of this application, please refer to the descriptions of the method embodiments of this application for understanding.
[0188] It should be noted that, in the embodiments of this application, if the above-described robot control method is implemented as a software functional module and sold or used as an independent product, it can also be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the embodiments of this application, or the part that contributes to the related technology, can be embodied in the form of a software product. This 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 methods described in the various embodiments of this application. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, portable hard drives, read-only memory (ROM), magnetic disks, or optical disks. Thus, the embodiments of this application are not limited to any specific hardware and software combination.
[0189] This application provides a computer device including a memory and a processor. The memory stores a computer program that can run on the processor, and the processor executes the program to implement the steps in the above-described method.
[0190] This application provides a computer-readable storage medium storing a computer program thereon, which, when executed by a processor, implements the steps in the above-described method. The computer-readable storage medium can be transient or non-transient.
[0191] This application provides a computer program product, including a computer program or instructions, which, when executed by a processor, implement some or all of the steps in the above-described method.
[0192] This application provides a computer program product, which includes a non-transitory computer-readable storage medium storing a computer program. When the computer program is read and executed by a computer, it implements some or all of the steps in the above-described method. This computer program product can be implemented specifically through hardware, software, or a combination thereof. In one optional embodiment, the computer program product is specifically embodied as a computer storage medium; in another optional embodiment, the computer program product is specifically embodied as a software product, such as a software development kit (SDK), etc.
[0193] It should be noted that the descriptions of the above-described storage media, computer program products, and device embodiments are similar to the descriptions of the above-described method embodiments, and have similar beneficial effects. For technical details not disclosed in the embodiments of the storage media, computer program products, and devices of this application, please refer to the descriptions of the method embodiments of this application for understanding.
[0194] It should be noted that Figure 8 is a schematic diagram of the hardware entity of a computer device provided in an embodiment of this application. As shown in Figure 8, the hardware entity of the computer device 800 includes: a processor 801, a communication interface 802, and a memory 803, wherein:
[0195] Processor 801 typically controls the overall operation of computer device 800.
[0196] The communication interface 802 enables computer devices to communicate with other terminals or servers over a network.
[0197] The memory 803 is configured to store instructions and applications executable by the processor 801, and can also cache data to be processed or already processed (e.g., image data, audio data, voice communication data, and video communication data) in the processor 801 and various modules in the computer device 800. It can be implemented using flash memory or random access memory (RAM). Data transfer between the processor 801, the communication interface 802, and the memory 803 can be performed via bus 804.
[0198] It should be understood that the phrase "one embodiment" or "an embodiment" throughout the specification means that a specific feature, structure, or characteristic related to the embodiment is included in at least one embodiment of this application. Therefore, "in one embodiment" or "in an embodiment" appearing throughout the specification does not necessarily refer to the same embodiment. Furthermore, these specific features, structures, or characteristics can be combined in any suitable manner in one or more embodiments. It should be understood that in the various embodiments of this application, the sequence numbers of the above-described processes do not imply a sequential 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 this application. The sequence numbers of the above-described embodiments are merely descriptive and do not represent the superiority or inferiority of the embodiments.
[0199] It should be noted that, in this document, the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or apparatus. Unless otherwise specified, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or apparatus that includes that element.
[0200] In the several embodiments provided in this application, it should be understood that the disclosed devices and methods can be implemented in other ways. The device embodiments described above are merely illustrative. For example, the division of units is only a logical functional division, and in actual implementation, there may be other division methods, such as: multiple units or components can be combined, or integrated into another system, or some features can be ignored or not executed. In addition, the coupling, direct coupling, or communication connection between the various components shown or discussed can be through some interfaces, and the indirect coupling or communication connection between devices or units can be electrical, mechanical, or other forms.
[0201] The units described above as separate components may or may not be physically separate. The components shown as units may or may not be physical units. They may be located in one place or distributed across multiple network units. Some or all of the units may be selected to achieve the purpose of this embodiment according to actual needs.
[0202] In addition, each functional unit in the various embodiments of this application can be integrated into one processing unit, or each unit can be a separate unit, or two or more units can be integrated into one unit; the integrated unit can be implemented in hardware or in the form of hardware plus software functional units.
[0203] Those skilled in the art will understand that all or part of the steps of the above method embodiments can be implemented by hardware related to program instructions. The aforementioned program can be stored in a computer-readable storage medium. When the program is executed, it performs the steps of the above method embodiments. The aforementioned storage medium includes various media that can store program code, such as mobile storage devices, read-only memory (ROM), magnetic disks, or optical disks.
[0204] Alternatively, if the integrated units described above are implemented as software functional modules and sold or used as independent products, they can also 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 related technologies, 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 methods described in the various embodiments of this application. The aforementioned storage medium includes various media capable of storing program code, such as mobile storage devices, ROM, magnetic disks, or optical disks.
[0205] In this embodiment, when the execution time of the robot's target task arrives, firstly, the target date type corresponding to the target task and the task execution strategy corresponding to the target date type are obtained; then, the matching relationship between the current date and the target date type is determined; finally, based on the matching relationship and the task execution strategy, the robot is controlled to execute the target task. In this way, the robot's task execution can be flexibly and accurately controlled according to the target date type and the task execution strategy corresponding to the target date type, thereby better meeting the user's task execution needs for the robot.
[0206] The above description is merely an embodiment of this application, but the scope of protection of this application is not limited thereto. Any changes or substitutions that can be easily conceived by those skilled in the art within the scope of the technology disclosed in this application should be included within the scope of protection of this application.
Claims
1. A control method of a robot characterized by, The method includes: In response to the arrival of the execution time of the target task of the robot, the task configuration information of the target task is obtained; the task configuration information includes the target date type corresponding to the target task and the task execution strategy corresponding to the target date type; Determine the matching relationship between the current date and the target date type; Based on the matching relationship and the task execution strategy, the robot is controlled to execute the target task.
2. The method of claim 1, wherein, The method further includes: Obtain date configuration information, which includes at least one date type and matching information corresponding to each date type; Based on the date configuration information, the target matching information corresponding to the target date type is determined.
3. The method of claim 1, wherein, The target date type has corresponding target matching information, which includes a target date range; Determining the matching relationship between the current date and the target date type includes at least one of the following: If the current date falls within the target date range, the current date is determined to match the target date type. If the current date does not fall within the target date range, it is determined that the current date does not match the target date type.
4. The method of claim 3, wherein, The target matching information also includes the target geographical range; The step of determining whether the current date matches the target date type when the current date falls within the target date range includes: If the current date falls within the target date range and the robot's location falls within the target geographical range, then the current date is determined to match the target date type.
5. The method according to any one of claims 1 to 4, characterized in that, The step of controlling the robot to execute the target task based on the matching relationship and the task execution strategy includes: If the matching relationship indicates that the current date matches the target date type, the robot is controlled to execute the target task based on the task execution strategy.
6. The method of claim 5, wherein, Controlling the robot to perform the target task based on the task execution strategy includes at least one of the following: If the task execution strategy includes abandoning the task, stop controlling the robot to execute the target task; When the task execution strategy includes performing a task, the robot is controlled to perform the target task.
7. The method of claim 6, wherein, When the task execution strategy includes executing a task, controlling the robot to execute the target task includes: When the task execution strategy includes executing the task according to the target execution parameters, the robot is controlled to execute the target task according to the target execution parameters.
8. A control device characterized by comprising: The device includes: The first acquisition module is used to acquire the task configuration information of the target task in response to the execution time of the target task arriving at the robot; the task configuration information includes the target date type corresponding to the target task and the task execution strategy corresponding to the target date type; The first determining module is used to determine the matching relationship between the current date and the target date type; The control module is used to control the robot to perform the target task based on the matching relationship and the task execution strategy.
9. A robot, characterized in that Includes the control device as described in claim 8. 10.A computer device, comprising a memory and a processor, and characterized in that, The memory stores a computer program that is loadable into the working memory of a processor, the processor executing the program implementing the method according to any one of claims 1 to 7.
11. A computer readable storage medium having stored thereon a computer program, characterized in that, The computer program is loadable into the working memory of a processor, the processor executing the program implementing the method according to any one of claims 1 to 7.
12. A computer program product comprising computer programs or instructions, characterized in that, The computer program or instructions are loadable into the working memory of a processor, the processor executing the program or instructions implementing the method according to any one of claims 1 to 7.