Apparatus and method for determining use orders

Abstract

An apparatus (130) for determining a usage order (150) for a cleaning robot (100) is described. The device (130) is configured to determine a total number of cleaning orders that have been executed by the cleaning robot (100) during a past operating period, each cleaning order specifying a range (151, 152) of cleaning tasks that have been executed by the cleaning robot (100) in the respective cleaning order. The device (130) is further configured to determine and / or adapt at least one usage order (150) for a future point in time on the basis of the total number of cleaning orders that have been executed, wherein the usage order (150) specifies a range (151, 152) of cleaning tasks to be executed by the cleaning robot (100) in the usage order (150).

Description

Technical Field

[0001] The present invention relates to a cleaning robot. In particular, the present invention relates to a device and a corresponding method for increasing the comfort of using a cleaning robot. Background Art

[0002] A cleaning robot can be used in a household to perform one or more different cleaning tasks, in particular suction and / or wiping. For this purpose, the user of the cleaning robot can be enabled to define usage orders for performing cleaning tasks via a user interface of the cleaning robot. The usage orders can be for the immediate (temporary) execution of cleaning tasks (so that a cleaning task is manually initiated). On the other hand, the usage orders can be for cleaning tasks planned for the future (this corresponds to so-called planned tasks). The provision of usage orders for performing different cleaning tasks may, if necessary, be associated with relatively high costs for the user. Summary of the invention

[0003] The present document relates to the technical task of increasing the comfort of a cleaning robot with respect to a usage order prescribed for performing cleaning tasks in an efficient and reliable manner.

[0004] This object is achieved by the subject matter of the respective independent patent claim. Advantageous embodiments are defined in particular in the dependent patent claims, described in the following description or illustrated in the attached drawings.

[0005] According to one aspect, a device for determining a usage order for a cleaning robot, in particular for a suction and / or sweeping and / or wiping robot, is described. The device may be part of the cleaning robot. Alternatively or additionally, the device may be at least partially or completely part of an external computing unit (e.g. a backend server).

[0006] The device is set up to determine a total number of cleaning orders that have been executed (e.g., 10 or more, or 50 or more, or 100 or more), which have been executed by the cleaning robot within a past operating period (e.g., 1 week or more, or 4 weeks or more). Individual cleaning orders from the total number of cleaning orders that have been executed can be manually started by a user of the cleaning robot (via a user interface of the cleaning robot).

[0007] Each cleaning order specifies the scope of the cleaning task performed by the cleaning robot in the corresponding cleaning order, in particular the spatial scope of the cleaning task and / or the task scope of the cleaning task (e.g., suction or wiping). In addition, each cleaning order can specify the time point, in particular, the working day and the daytime, when the corresponding cleaning order is performed.

[0008] It is thus possible to determine historical usage data regarding previous uses of the cleaning robot (in the form of a total amount of cleaning orders that have been executed).

[0009] The device is set up to determine and / or adapt at least one usage order for a future point in time based on the total amount of cleaning orders that have already been executed. The determined usage order can be a planned usage order that is automatically executed, in particular started (without user interaction via a user interface of the cleaning robot) by the cleaning robot at a specific point in time, in particular on specific working days and / or at specific daytime hours.

[0010] The usage order specifies the scope of the cleaning task to be performed by the cleaning robot in the usage order, in particular the spatial scope of the cleaning task and / or the task scope of the cleaning task.

[0011] Thus, a device is described which is designed to determine suggestions for (if necessary planned) usage orders based on historical usage data (on previous usage of the cleaning robot and / or on cleaning tasks performed so far). The usage order can define cleaning tasks with a specific spatial scope and / or with a specific task scope. This can lead to a particularly comfortable operation of the cleaning robot.

[0012] The entire area (eg, a house or an apartment) in which the cleaning robot operates may be subdivided into a plurality of different sub-areas (eg, rooms). The spatial range may describe one or more sub-areas from the plurality of different sub-areas.

[0013] The cleaning robot can be configured to operate in a plurality of different cleaning modes (e.g., suction or wiping or a combination of the two). In addition, the intensity of the respective cleaning mode (e.g., suction intensity and / or water volume) can be changed and / or adjusted if necessary. The task scope can specify the cleaning mode of the cleaning robot and / or the intensity of the cleaning mode.

[0014] The device can be set up to output a suggestion for executing the determined use order to the user of the cleaning robot via the user interface of the cleaning robot. The user interface can be provided, for example, at the user device of the user (such as a smart phone). The user can accept the suggestion to operate the cleaning robot in a comfortable manner.

[0015] The device can be set up to recognize, based on the total amount of cleaning orders that have been executed: for a specific sub-area of ​​the entire area in which the cleaning robot operates and / or for a specific cleaning mode among a plurality of different cleaning modes that can be executed by the cleaning robot, no cleaning orders have been issued in the past operating period. Based on this recognition, a use order can be determined (and suggested) which has a specific sub-area and / or a specific cleaning mode as a scope. Thus, a particularly comfortable operation of the cleaning robot can be achieved.

[0016] Alternatively or in addition, the device can be set up to identify a specific sub-area of ​​the entire area and / or a specific cleaning mode among a plurality of different cleaning modes of the cleaning robot based on the total amount of cleaning orders that have been executed, for which there is a relatively high number of cleaning orders (e.g., greater than a quantity threshold) in the total amount of cleaning orders that have been executed. Based on this understanding, a use order can be determined and / or adapted, the use order having a specific sub-area and / or a specific cleaning mode as a range. The device can be set up in particular to identify an already planned use order, the use order having a specific cleaning mode as a range but not a specific sub-area. Then, a specific sub-area can be expanded to the range of the already planned use order and stored in a changed form. Thereby, a particularly comfortable operation of the cleaning robot can be achieved.

[0017] The device can be set up to determine a future time, in particular a weekday and a daytime, for executing a use order based on the time of the total amount of cleaning orders that have already been executed, in particular a weekday and / or a daytime. This allows a particularly comfortable operation of the cleaning robot.

[0018] As already explained further above, the scope of an individual cleaning order from the total amount of cleaning orders that have been executed can respectively describe one or more sub-areas of the entire area in which the cleaning robot operates.

[0019] The device can be configured to subdivide each cleaning order from the total amount of cleaning orders that have been executed into one or more data entries for the corresponding one or more sub-areas, so that the scope of each data entry only relates to a unique sub-area of ​​the entire area. Thus, each cleaning order can be subdivided into one or more components (i.e. data entries), one data entry for each sub-area. Based on the data entries, the usage order for a future point in time can then be determined and / or adapted in a particularly precise and robust manner.

[0020] As already explained further above, the individual cleaning orders and the data entries determined therefrom can respectively indicate the working day and the time of day at which the respective cleaning order or the respective data entry was executed. The device can be configured to respectively assign the determined data entries to a day time slot from a sequence of day time slots according to the respective working day and the respective time of day, wherein the sequence of day time slots subdivides a week into a finite number of day time slots, for example between 20 and 100.

[0021] Thus, the total amount of allocated data entries can be determined for each daily period in the sequence of daily periods. The usage order for future time points can then be determined and / or adapted in a particularly robust and precise manner based on the total amount of allocated data entries for at least one daily period.

[0022] The device can be configured in particular to identify a daily period with a number of allocated data entries that is equal to or greater than a quantity threshold value, for example 2 or more, or 3 or more. A usage order for a future point in time can then be determined and / or adapted in a particularly precise and robust manner based on the total amount of allocated data entries for the identified daily period.

[0023] The device can be configured to determine a future point in time, in particular a weekday and a daytime, for a use order based on the weekday and the daytime of each data entry in the total amount of data entries allocated for the identified day period. For example, the daytime of a use order can be determined as an average of the daytime of the data entries.

[0024] The device can be set up to detect the presence of a planned usage order for the identified day period. The scope of the planned usage order can then be expanded based on the total amount of the assigned data entries for the identified day period. This can achieve a particularly comfortable operation of the cleaning robot.

[0025] The device can be configured to allocate the determined data entries to a first daily time period from a sequence of first daily time periods and to a second daily time period from a sequence of second daily time periods, respectively, according to the respective weekdays and the respective daytime hours, wherein the second daily time period is offset in time and overlaps with the corresponding first daily time period. The usage order for a future point in time can then be determined and / or adapted in a particularly precise and robust manner based on the total amount of the allocated data entries for a specific first daily time period and a specific second daily time period, which is offset in time and overlaps with the specific first daily time period.

[0026] According to a further aspect, a cleaning robot, in particular a suction and / or sweeping and / or wiping robot, is described, which comprises the device described in this document.

[0027] According to another aspect, a method for determining a use order for a cleaning robot is described. The method comprises determining a total amount of cleaning orders that have been executed, which have been executed by the cleaning robot in a past operating period, wherein each cleaning order respectively specifies a range of cleaning tasks to be performed by the cleaning robot in the respective cleaning order. Furthermore, the method comprises determining and / or adapting at least one use order for a future point in time based on the total amount of cleaning orders that have been executed, wherein the use order specifies a range of cleaning tasks to be performed by the cleaning robot in the use order.

[0028] It should be noted that any aspects of the apparatus described in this document and / or the method described in this document can be combined with each other in various and / or arbitrary ways. In particular, the features of the patent claims can be combined with each other in various and / or arbitrary ways. BRIEF DESCRIPTION OF THE DRAWINGS

[0029] Furthermore, the present invention will be described in more detail based on the embodiments shown in the attached drawings.

[0030] Figure 1a and 1b An exemplary cleaning robot is shown in different perspective views as an example of a suction and / or sweeping and / or wet cleaning and / or wiping device;

[0031] Figure 1c illustrates exemplary components of a cleaning robot;

[0032] Figure 1d showing an exemplary user interface for specifying a usage order;

[0033] Figure 2a An exemplary division of time periods into day periods is shown;

[0034] Figure 2b An exemplary analysis of historical cleaning orders is shown;

[0035] Figure 3 A flow chart illustrating an exemplary method for analyzing historical cleaning orders;

[0036] Figure 4a and 4b a flow chart showing an exemplary method for adapting a (already defined) planned usage order; and

[0037] Figure 5 A flow chart illustrating an exemplary method for determining a usage order. DETAILED DESCRIPTION

[0038] As explained at the outset, this document is concerned with increasing the convenience of ordering a cleaning robot for use. Figure 1aThe top side 121 of the cleaning robot 100, in particular a suction robot, is shown and Figure 1b The underside 122 is shown.

[0039] In the suction operation of the cleaning robot 100, the lower side 122 faces the floor to be cleaned or the surface to be cleaned of the cleaning area, such as the room. The lower side 122 of the cleaning robot 100 typically has one or more drive units 101 (with one or more drive wheels), and the cleaning robot 100 can be moved independently by the drive unit 101 to clean different areas of the floor. In addition, the cleaning robot 100 can have one or more guide and / or support elements 104 (for example non-drive wheels), which enable the cleaning robot 100 to move stably on the floor to be cleaned. In addition, the cleaning robot 100 typically includes one or more cleaning units 106 (especially suction nozzles), which are set up for cleaning the floor below the cleaning robot 100.

[0040] The cleaning unit 106, in particular the suction nozzle, can have a brush roller 102, which is configured to rotate about an axis of rotation, wherein the axis of rotation is typically arranged parallel to the underside 122 of the cleaning robot 100. The brush roller 102 can be used to mechanically detach dust and / or dirt on the floor to be cleaned from the floor, so that the dust and / or dirt can be sucked into the suction opening 107 of the cleaning unit 106 with increased reliability.

[0041] User interface 112 (see Figure 1c ) can be arranged at the upper side 121 of the cleaning robot 100, the user interface enabling a user of the cleaning robot 100 to operate a control input. Alternatively or in addition, the cleaning robot 100 may include a communication interface 113 (e.g. for a wireless communication connection, such as WLAN), via which the cleaning robot 100 can communicate with an external user interface on an electronic user device, such as a smart phone. In addition, the cleaning robot 100 may include a buffer 105 at a side wall 123 (e.g. at a side wall 123 in the front area of ​​the cleaning robot 100), wherein an impact sensor can be arranged at the buffer 105, the impact sensor being set up for detecting sensor data, the sensor data indicating whether the cleaning robot 100 hits an obstacle in the direction of movement 120. For example, the triggering of the impact sensor by an obstacle (due to the deflection of the buffer 105) can cause the cleaning robot 100 to rotate around its vertical axis or vertical axis perpendicular to the floor, and thereby change the direction of movement 120 in order to avoid the obstacle.

[0042] In addition, the cleaning robot 100 typically has one or more environmental sensors 110 (see Figure 1c), the environmental sensor 110 is configured to detect environmental data or sensor data about the environment of the cleaning robot 100. One or more environmental sensors 110 may include: one or more image cameras, one or more ultrasonic sensors, one or more tactile and / or optical distance sensors, one or more acoustic sensors, one or more temperature sensors, one or more laser radars and / or radar sensors, etc. The control unit 130 of the cleaning robot 100 may be configured to determine digital map information about the cleaning area to be cleaned based on the environmental data and store it in the storage unit 111 of the cleaning robot 100 if necessary. The cleaning robot 100 can use the digital map information for independent orientation within the cleaning area (e.g., within a room) and / or for specifying a driving route for cleaning the cleaning area.

[0043] Figure 1c A Cartesian coordinate system is shown with a longitudinal axis (ie with an x-axis), a transverse axis (ie with a y-axis) and a vertical axis (ie with a z-axis). The direction of movement 120 of the cleaning robot 100 typically corresponds to the longitudinal axis. The axis of rotation of the brush roll 102 typically extends along the transverse axis.

[0044] The user of the cleaning robot 100 may be enabled to specify a usage order for cleaning tasks of the cleaning robot 100 at a user interface of the cleaning robot 100. The usage order may alternatively be referred to as a cleaning order (especially if the order is manually initiated by the user). The user interface may be provided, for example, via a mobile user device of the user (e.g., via a smartphone). Figure 1d An exemplary user interface for specifying a usage order or cleaning order 150 is shown. The usage order and / or cleaning order 150 can be stored in an external computing unit (e.g. in a database of a backend server) (in order to reduce the required storage space on the cleaning robot 100). Data communication can take place via the communication interface 113 of the cleaning robot 100. Within the scope of the usage order 150, different aspects and / or dimensions of the cleaning task to be completed by the cleaning robot 100 (in particular the scope of the cleaning task) can be specified. Exemplary aspects and / or dimensions are

[0045] The spatial dimension (i.e., spatial order range) 151, in which the spatial area of ​​the cleaning task is specified. Figure 1d In the example shown in , it can be specified whether to clean the spatial sub-areas A, B, C and / or D. The individual sub-areas (especially rooms) can be identified as sub-areas (especially rooms) that are distinguished from each other when the cleaning robot 100 is mapping or exploring the entire area (for example, in a living environment) and / or have been specified by the user.

[0046] Cleaning mode (ie task scope) 152, in which, for example, it is specified whether suction or wiping or both should be performed. In addition, the intensity of the blower for the suction operation and / or the amount of wiping water for the wiping operation can be specified if necessary.

[0047] A time dimension 153 , in which, for example, a time is specified at which a cleaning task is to be performed, in particular started.

[0048] The periodicity 154 of the use order, by which it is specified, for example, how often (for example on which working days) the use order 150 is to be executed in each case.

[0049] A planned (for the future) usage order 150 may also be referred to as a “planned task”.

[0050] This document describes a method and a corresponding device 130 which enable the creation of proposals for new planned usage orders 150 or for adapting existing planned usage orders 150 based on the usage history of the cleaning robot 100 .

[0051] The cleaning robot 100 can be designed to store each of its usage orders or cleaning orders 150 (both manually initiated usage orders and planned usage orders) with the specification of one or more of the following information:

[0052] The start time of the use order 150 (i.e., time dimension 153);

[0053] For example, use the working day of order 150 (usually periodic 154);

[0054] Using the rooms (in the case of a "clean all" order, all rooms that have been reached and cleaned) and / or zones (i.e., spatial dimensions 151) contained in the order 150;

[0055] The cleaning mode set for cleaning (suction / wiping, power level, driving strategy, etc.), i.e., the order range 152;

[0056] whether the cleaning was terminated prematurely by the user and, if necessary, after which proportion of the surface area; and / or

[0057] · Whether cleaning had to be interrupted for other reasons, such as due to a closed door.

[0058] Based on the record of start times for cleaning specific rooms or zones, the frequency of these usage orders 150 may also be determined.

[0059] The distribution of the use order 150 to the individual rooms and the cleaning mode used therein allow the inference of the cleaning tasks actually desired by the user. It can be advantageous here to distinguish the rooms (i.e. sub-areas) that are actually cleaned by the cleaning robot during the "clean all" order (where the entire area should be cleaned) from those rooms that are theoretically recorded on the map but cannot be cleaned or are not cleaned. This is related to the use behavior of some users, who start the "clean all" program but deliberately block the way to some rooms (for example, with the help of doors) so that the cleaning robot 100 is ultimately only working in the desired room or rooms. Similarly, there are users who carry the cleaning robot 100 into a room, issue a "clean all" cleaning command there and close the door of the room so that the robot is only cleaning in the room.

[0060] Furthermore, a detailed description of the individual surfaces may be of interest, for example in order to be able to record a "spot cleaning" program, in which the cleaning robot 100 should clean an area with specific dimensions (e.g. with a specific diameter or with a specific side length or a specific number of square meters) at a specific location. If such cleaning is performed relatively frequently by the user in almost the same place, this cleaning task can also be suggested for repeated cleaning as a usage order 150. Examples of such surfaces may be: the entrance area of ​​a front door, the area in front of a row of kitchen appliances or the area in front of a cat toilet.

[0061] The record of usage orders 150 aborted by the user makes it possible to infer whether a usage order 150 has been incorrectly specified by the user or whether only a portion of the defined area should be cleaned. If, for example, the cleaning of three rooms is commissioned but is aborted after two rooms, it can be assumed that the cleaning in the last room has been considered less important. However, if, before the cleaning was aborted, a room had been cleaned by more than, for example, 75%, it can be inferred that the cleaning of this room was planned and desired. If necessary, each usage order 150 in which the planned area of ​​the room has been cleaned by more than 75% can be stored and taken into account. In this case, all room-cleaning mode combinations of usage orders 150 can be adopted as entries in the usage history. Thus, an exemplary suction and wiping usage order 150 at full power level in the rooms or zones "A", "B" and "C" can be assigned by the following data entry:

[0062] A, suction, 100% power, Thursday, 10:15;

[0063] B, suction, 100% power, Thursday, 10:15;

[0064] C, suction, 100% power, Thursday, 10:15;

[0065] A, wipe, 100% battery, Thursday, 10:15;

[0066] B, wipe, 100% battery, Thursday, 10:15;

[0067] C, wipe, 100% battery, Thursday, 10:15.

[0068] The analysis algorithm can evaluate the usage history repeatedly, for example once a day or once a week. To this end, the usage data for a specific operating period in the past (for example the past 4 or 8 weeks) can be evaluated to enable a robust and statistically relevant evaluation. The (control) device 130 of the cleaning robot 100 can be configured to provide suggestions for the use order 150 only when a sufficient amount of usage data is available. In addition, relatively old usage data in the past can be ignored or not considered so heavily during the analysis to enable the analysis of the user's current usage behavior. Therefore, relatively old usage data in the past can be deleted.

[0069] The data items to be included in the analysis can be sorted according to the room-cleaning mode combinations (ie according to the data items). Each individual combination (ie each individual data item) can then be viewed individually.

[0070] All data entries belonging to a combination (e.g. "Room B, suction, 100% power") can be assigned to individual "day periods". These day periods are time intervals of 24 hours, 7 days a week, and each have a length of, for example, 4 hours (or 2 hours or 6 hours). A particularly robust evaluation can be achieved by additionally introducing a second identical day period, which has the same length but is offset by half the length compared to the first day period. Figure 2a Shows approximately 1 1 / 2 An exemplary first day period 201 and an exemplary second day period 202 of a time period of a day.

[0071] The respective data entries can be respectively assigned (based on the respective weekday and the respective daytime) to the first daily period 201 and the second daily period 202 into which the respective data entry falls. The number of data entries assigned to one daily period 201, 202 allows to infer when the user performs the corresponding room-cleaning mode combination relatively frequently or relatively sparsely. Therefore, the total amount 205 of data entries can be determined for each daily period 201, 202 respectively.

[0072] Next, one or more daily periods 201, 202 can be considered, in which at least a certain minimum number of data entries are executed for the cleaning task. For each daily period 201, 202, it can therefore be checked whether a threshold value for the data entry is reached or exceeded. Overlapping daily periods 201, 202 that both have reached the threshold value can be combined into a common, fused daily period. The data entries assigned to the two overlapping daily periods 201, 202 are only taken over once into the fused daily period in this case. This action prevents inaccurate predictions of usage behavior in the case of data entries close to period boundaries.

[0073] In the resulting list of (possibly fused) day periods, a data point can be created for each day period for which a threshold of data entries of cleaning tasks performed is exceeded, which data point represents that this day period is used in further processing. The data point remains associated with the day period and the data entry assigned thereto, but a timestamp is obtained, which corresponds, for example, to the average of the start times of all data entries assigned to the day period. Thus, a total amount of data points can be determined, which represents when a room-cleaning mode combination was performed relatively frequently during a week (Monday to Sunday).

[0074] Figure 2b A list of (fused) daily time periods 212 with corresponding total amounts 215 of data entries is shown. In addition, Figure 2b Data points 219 derived therefrom are shown.

[0075] The use of the generated data points 219 as an independent proposal for a usage order 150 may possibly lead to time conflicts with other proposals for other room-cleaning mode combinations or to time conflicts with already existing usage orders.

[0076] In a subsequent step, all data can be aggregated, i.e. all data points for all room-cleaning mode combinations and all existing (already planned) usage orders 150. This can in turn be done by assigning the data to day time periods 201, 202 (e.g. in combination with Figure 2a The time length of the daily periods 201, 202 can be retained or shorter daily periods 201, 202 can be used. By stipulating a minimum time length (e.g. one hour) for each daily period 201, 202, it can be ensured that there are sufficiently large intervals between the usage orders 150 that are consecutive in time (e.g., in order to be able to charge the electrical energy storage device of the cleaning robot 100).

[0077] The first and second daily periods 201, 202 can be reassigned, respectively, and the daily periods 201, 202 and the total quantity 205 of the data entries can then be merged. Based on the merged daily period 212 and the merged total quantity 215, a data point 219 can then be determined for the usage order 150 (taking into account the already existing planned usage order 150).

[0078] The method described can be subdivided into a plurality of steps, which can be assigned to two phases. In the first phase, data entries are created and assigned to daily periods 201, 202 before they are combined into data points 219. This reduces the amount of data to be further processed and compared with one another. In the second phase, these data points themselves are again assigned to daily periods 201, 202 before the actual evaluation is finally performed. The first phase can be performed for each room-cleaning mode combination, and in the second phase all data can then be gathered again in order to determine the combined usage order 150 (for multiple rooms).

[0079] Figure 3 A flow chart of an exemplary method 300 for evaluating the usage history of a cleaning robot 100 is shown. In step 301, data entries can be created based on the usage history (e.g., based on the total amount of cleaning orders that have been executed). The data entries can here each correspond to a combination of a room and a cleaning mode. In a further step 302, the individual data entries can be assigned to different day time periods 201, 202 (where Figure 3 In addition, in another step 303, overlapping daily time periods 201, 202 can be combined into a fused daily time period 212, wherein the overlapping daily time periods 201, 202 each have a number of data entries exceeding a certain threshold. Based on the total amount 215 of the data entries of the fused daily time period 212, data points 219 can be determined respectively (step 304). Steps 301 to 304 can correspond to the first stage of the method 300.

[0080] In the second phase of the method 300, the determined data points 219 and the already defined planned usage orders 150 (i.e., planned tasks) can be assigned to the daily time periods 201, 202 (step 305). In addition, in a further step 306, overlapping daily time periods 201, 202 can be combined, each of which has a certain minimum number of data entries.

[0081] Thus, (fused) daily periods 212 can be defined, each with a data point 219 and a planned usage order 150. This information can be used to define new (if necessary planned) usage orders 150 and / or to adapt already existing planned usage orders 150.

[0082] Firstly, it can be determined for each room or zone based on the evaluation of data point 219 when the room or zone was last cleaned. If the last cleaning process involving the room or zone has passed longer than, for example, 10 days, and other cleaning orders have also been executed in this time period (i.e. the user has not gone out), the user can be asked (via one or more user interfaces) whether the room or zone should be cleaned in a specific way (e.g. the intensity of dry cleaning and / or wet cleaning). Alternatively, the user can be advised to expand a possibly existing planned task (i.e. the planned usage order) by cleaning the room. On the other hand, if the identified room should never be cleaned, the room may no longer be recommended for cleaning in the future if necessary.

[0083] Furthermore, one or more remaining daily periods 212 with a certain amount 215 of data entries can be evaluated individually. To this end, a check can be made for each data point 219 of a manually initiated cleaning order 150: whether an entry for a scheduled task with the same settings for the room and the cleaning mode already exists in the same daily period 212, or whether this data point 219 can be converted into a scheduled task individually or together with one or more other data points 219 from the same or different daily periods 212. In this check, the following situations can be taken into account in particular:

[0084] 1. For the considered data point 219 of the manually initiated use order 150, there is no suitable scheduled task with the same room-cleaning mode combination in the associated daily time period 212. There is another data point with the same room-cleaning mode combination within a defined maximum time interval (e.g. 2 hours) in the associated daily time period and not in any other daily time period 212.

[0085] The considered data point 219 is a candidate for a new planned task. A suggestion for a usage order 150 for this room-cleaning mode combination can be presented to the user. The suggested start time can correspond to the average of the start times of the data entries assigned to the data point (or alternatively the latest start time) and can be rounded to a quarter of an hour, for example. The data point 219 can eventually be removed from the overview.

[0086] 2. For the considered data point 219 of a manually initiated use order 150, there is a suitable scheduled task in the associated daily period 212, which includes the room of the use order 150 with the same cleaning mode combination. Both entries are within a defined maximum time interval (eg 2 hours).

[0087] This data point 219 is already included in the planned task. Therefore, the data point 219 does not need to be considered further and can be removed from the overview.

[0088] 3. For the considered data point 219 of the manually initiated use order 150, there is a suitable scheduled task in the associated daily period 212, which includes the same cleaning mode combination, but does not include the same room. Both entries are within the defined maximum time interval (eg 2 hours).

[0089] This data point 219 is a candidate to be added to an existing scheduled task. A suggestion of a room for extending the data point 219 to the scheduled task may be presented to the user. If necessary, the suggested start time may remain unchanged, but may also correspond to the average of the start times (data point 219, scheduled task) (e.g. rounded to a quarter of an hour). The data point 219 may eventually be removed from the overview.

[0090] 4. For the considered data point 219 of the manually initiated use order 150, there is no suitable scheduled task with the same room-cleaning mode combination in the corresponding daily period 212, but there is one in a simultaneous or temporally overlapping daily period 212 on another working day. The start time of the data point 219 and the scheduled task lies within a defined maximum time interval (e.g. 2 hours).

[0091] This data point 219 is a candidate to be added to an existing scheduled task. A suggestion of a weekday for extending the data point 219 to the scheduled task (in particular the periodicity and / or frequency of the scheduled task) can be presented to the user. If necessary, the suggested start time can remain unchanged, but can also correspond to the average value of the start times (data point 219, scheduled task) (e.g. rounded to the quarter hour). The data point 219 can eventually be removed from the overview.

[0092] 5. For the considered data point 219 of a manually initiated use order 150, there is no suitable scheduled task including the same room-cleaning mode combination on any working day in the corresponding daily period 212, but there are one or more other data points 219 of manually initiated cleaning orders with the same room-cleaning mode combination in the same or temporally overlapping daily periods 212 on other working days. The start time of the data point 219 is within the defined maximum time interval (e.g., 2 hours).

[0093] This data point 219 and one or more similar data points 219 found are candidates for new planned tasks. A suggestion for this room-cleaning mode combination can be presented to the user on the weekday in question. The suggested start time can correspond to the average of the start times of the data entries assigned to the data point 219 (or alternatively the latest start time) and can be rounded to a quarter of an hour, for example. The data point 219 and one or more other combined data points 219 can eventually be removed from the overview.

[0094] In general, a structured sequence of checks can be performed for each data point 219, which checks reveal the above-mentioned and / or other case differences. If necessary, a proposal to create a new planning task from a data point 219 of a manually initiated use order 150 can be output only when all possibilities for adapting one or more existing, planned use orders 150 have been checked and evaluated negatively.

[0095] It can be assumed that one or more cleaning settings for each room are defined with a corresponding planning task and are also received from the data and applied by the cleaning robot 100. However, it is also possible that the user can predefine room-specific cleaning modes, which are specified by the user in advance for each room in a map of the user interface. Thus, one or more cleaning modes can be associated with each room.

[0096] In a planned task or in a manually initiated use order, it is then necessary not to make any specifications regarding the cleaning mode, since these are automatically received from the map data depending on the room to be cleaned.

[0097] It is therefore not necessary to compare the cleaning patterns for the evaluation of the data entries or data points 219 and the existing use orders 150. Within the scope of the described method, only the start time and the room are then evaluated if necessary.

[0098] The suggestion for one or more new or adapted usage orders 150 is preferably not implemented directly, but can be sent to the user (i.e., to the user's user device, for example) for example by means of a push message. The user can then accept or reject the suggestion. The suggestion can remain in intermediate storage until the user responds or - if the user does not use the user interface for a relatively long time - until a new suggestion replaces the previous one. If the user accepts the suggestion or the suggestions, the corresponding changes are automatically implemented in one or more planned usage orders 150.

[0099] exist Figure 4a and 4b An exemplary method 400 for determining a recommendation for a planned usage order 150 is described in . The method 400 includes a series of yes / no branches, wherein Figure 4b The branches are shown in FIG.

[0100] For a data point 219 for a manually initiated cleaning order in a daily period 212, it can be checked whether a planned use order 150 with the same settings 152 already exists in the same daily period 212 and for the same room 151 (usually for the same sub-area and / or for the same surface) (steps 401, 402). If this is the case, the data point 219 can be deleted (step 413).

[0101] If this is not the case, a check can be made as to whether a planned usage order 150 with the same settings already exists in the same day period 212, but for a different room (sub-area and / or surface) 151 (step 403). If this is the case, the already planned usage order 150 (i.e. the room (sub-area and / or surface) 151 with the extended data point 219) can be adapted (step 414).

[0102] If this is not the case, it can be checked whether there is already a planned use order 150 with different settings 152 in the same day period 212 and for the same room (subarea and / or surface) 151 (step 404). If this is the case, the already planned use order 150 can be adapted (i.e. the settings of the data point 219 are extended) (step 415).

[0103] If this is not the case, a check can be made as to whether there is already a planned usage order 150 with the same settings 152 in the same day period 212 and for the same room (subarea and / or surface) 151 but for a different weekday 154 (step 405). If this is the case, the already planned usage order 150 (i.e. the weekday 154 extended by the data point 219) can be adapted (step 416).

[0104] If this is not the case, it can be checked whether there are one or more other data points 219 with the same settings 152 in the same day period 212 but on different working days (step 406). If this is the case, a new planned usage order 150 can be created (for the data point 219) (step 417).

[0105] If this is not the case, it can be checked whether one or more further data points 219 exist for the same room (subarea and / or area) 151, for the same day period 212, for the same or different weekdays and in each case with different settings 152 (step 407). If this is the case, a new planned use order 150 can be created (for the data point 219) (step 418).

[0106] If this is not the case, a proposal for a planned usage order 150 can be created for the data point 219 under consideration (step 408 ).

[0107] The method 400 may then be repeatedly executed for subsequent data points 219. Thus, the data points 219 may be checked gradually for manually initiated cleaning orders.

[0108] By means of the measures described in this document, the cleaning orders (usage orders) 150 started by the timer function can be automatically adapted to the user's usage preferences, without user intervention if necessary. For example, the user receives suggestions for usage orders 150 for cleaning tasks that are frequently started manually, so that the user does not have to start the cleaning robot 100 himself less frequently and can rely on the planned usage orders 150.

[0109] In the context of the described method, individual working days, rooms and / or cleaning modes can be differentiated during the evaluation, so that the preferences of the user can be recognized and taken into account in a particularly precise manner. If necessary, the user can be reminded to clean previously omitted areas. By combining the data entries into data points 219 in the described manner, the amount of data to be processed can be reduced, so that even relatively large amounts of data can be evaluated with limited hardware performance.

[0110] Figure 5 A flow chart of a (possibly computer-implemented) method 500 for determining use orders 150 for a cleaning robot 100 is shown. The method 500 comprises determining 501 the total amount of cleaning orders that have been executed by the cleaning robot 100 in the past operating period. In this case, the individual cleaning orders can each specify the scope 151, 152 of the cleaning tasks to be executed by the cleaning robot 100 in the respective cleaning order.

[0111] The method 500 further comprises determining and / or adapting 502 at least one usage order 150 for a future point in time based on the total amount of cleaning orders already executed. In this case, the usage order 150 can specify the scope 151 , 152 of the cleaning tasks to be executed by the cleaning robot 100 in the usage order 150 .

[0112] The invention is not limited to the embodiments shown. In particular, it should be noted that the description and the drawings are only intended to illustrate the principles of the device described in this document and / or the method described in this document.

[0113] Reference numerals list

[0114] 100 cleaning robots

[0115] 101 driver unit

[0116] 102 brush roller

[0117] 104 Guiding and / or supporting elements

[0118] 105 Buffer

[0119] 106 cleaning unit / nozzle

[0120] 107 suction port

[0121] 110 Environmental Sensors

[0122] 111 storage unit

[0123] 112 User Interface

[0124] 113 Communication interface

[0125] 120 movement direction / vertical

[0126] 121 upper side

[0127] 122 lower side

[0128] 123 side wall

[0129] 130 Control unit / control device

[0130] 150 Use Order

[0131] 151 Space Order Range

[0132] 152 Mission Scope

[0133] 153 Time Order Range

[0134] 154 Periodicity

[0135] 201, 202 Daily time period / time segment

[0136] 205 Total amount of historical usage orders

[0137] 212 Fusion of daily time periods / time segments

[0138] 215 The total amount of historical orders used

[0139] 219 Data points using orders

[0140] 300 Methods for analyzing historical usage orders

[0141] 301-306 Method Steps

[0142] 400 Method for adapting the planned usage order

[0143] 401-408, 413-419 Methods and Steps

[0144] 500 is used to determine the method of using the order

[0145] 501, 502 Method Steps

Claims

1. A device (130) for determining a usage order (150) for a cleaning robot (100); wherein the device (130) is configured to: - determining the total amount of cleaning orders that have been executed, which have been executed by the cleaning robot (100) in the past operating period; wherein each cleaning order respectively specifies the scope (151, 152) of the cleaning tasks performed by the cleaning robot (100) in the corresponding cleaning order; and - Determining and / or adapting at least one usage order (150) for a future point in time based on the total amount of cleaning orders already executed; wherein the usage order (150) describes the scope (151, 152) of the cleaning tasks to be performed by the cleaning robot (100) in the usage order (150).

2. The device (130) according to claim 1, wherein the scope (151, 152) of the cleaning order and / or the usage order (150) comprises, - a spatial extent (151) of the cleaning task; wherein the spatial extent (151) in particular describes one or more sub-areas from an overall area subdivided into a plurality of different sub-areas; and / or - a task scope (152) of the cleaning task; wherein the task scope (152) in particular specifies a cleaning mode of the cleaning robot (100), such as suction or wiping or both, and / or the intensity of the cleaning mode.

3. The device (130) according to any one of the preceding claims, wherein - individual cleaning orders from the total amount of cleaning orders already executed are respectively manually initiated by a user of the cleaning robot (100); and The determined usage order (150) is a planned usage order (150) which is automatically executed, in particular started, by the cleaning robot (100) at a specific point in time, in particular on a specific working day and / or at a specific daytime.

4. The device (130) according to any one of the preceding claims, wherein the device (130) is configured to: - Based on the total volume of cleaning orders that have been executed - for a specific sub-area of ​​the entire area in which the cleaning robot (100) is operated; and / or -- for a specific cleaning mode among a plurality of different cleaning modes that can be performed by the cleaning robot (100), Has not resulted in a cleaning order during the past operating period; and Based on this, a usage order (150) is determined with a specific sub-area and / or a specific cleaning mode as scope (151, 152).

5. The device (130) according to any one of the preceding claims, wherein the device (130) is configured to: - Based on the total quantity of cleaning orders that have been executed - a specific sub-region of the entire region; and / or --a specific cleaning mode among a plurality of different cleaning modes of the cleaning robot (100), for which there is a relatively high number of cleaning orders in the total amount of cleaning orders that have been executed; and Based on this, a usage order (150) is determined and / or adapted with specific sub-areas and / or specific cleaning modes as scope (151, 152).

6. The device (130) according to claim 5, wherein the device (130) is configured to - identifying an already planned use order (150) which already has a specific cleaning mode as a range (151, 152), but not a specific sub-area; and - Extending the scope (151, 152) of an already planned usage order (150) by a specific sub-area.

7. The device (130) according to any one of the preceding claims, wherein - each cleaning order specifies the time at which the corresponding cleaning order has been carried out, in particular the weekdays and daytime hours; and The device (130) is designed to determine a future time, in particular a weekday and a daytime, for executing a usage order (150) based on the time of the total amount of cleaning orders that have already been executed.

8. The device (130) according to any one of the preceding claims, wherein - the range (151, 152) of each cleaning order from the total amount of cleaning orders already executed respectively describes one or more sub-areas of the entire area in which the cleaning robot (100) is operated; and - the device (130) is configured to: - subdividing each cleaning order from the total amount of cleaning orders that have been executed into one or more data entries for the corresponding one or more sub-areas, respectively, so that the range (151, 152) of each data entry only relates to a unique sub-area of ​​the entire area; and - Determining and / or adapting a usage order for a future point in time based on the data entry (150).

9. The device (130) according to claim 8, wherein - each cleaning order and the data entry determined therefrom respectively indicate the weekday and the time of day on which the respective cleaning order or the respective data entry has been carried out; and - the device (130) is configured to: - assigning the determined data entries to a daytime period (201, 202) from a sequence of daytime periods (201, 202) according to the respective weekday and the respective daytime time, wherein the sequence of daytime periods (201, 202) divides a week into a finite number of daytime periods (201, 202); - determining the total amount (205) of the allocated data entries for each day period (201, 202) of the sequence of day periods (201, 202); and - determining and / or adapting a usage order (150) for a future point in time based on the total amount (205) of allocated data entries for at least one daily period (201, 202).

10. The device (130) according to claim 9, wherein the device (130) is configured to - identifying a daily period (201, 202) having a number of allocated data entries equal to or greater than a number threshold; and - determining and / or adapting a usage order (150) for a future point in time based on the total amount (205) of allocated data entries for the identified day period (201, 202).

11. A device (130) according to claim 10, wherein the device (130) is configured to determine a future time point, in particular a weekday and a daytime time, for a usage order (150) based on the weekday and daytime times of the individual data entries in the total amount (205) of the allocated data entries for the identified day time period (201, 202).

12. The device (130) according to any one of claims 10 to 11, wherein the device (130) is configured to: - detecting the presence of already planned usage orders (150) for the identified day period (201, 202); and - expanding the scope (150) of the already planned usage order (150) based on the total amount (205) of the allocated data entries for the identified day period (201, 202).

13. The device (130) according to any one of claims 9 to 12, wherein the device (130) is configured to: - assigning the determined data entries to a first daily period (201) in a sequence from the first daily periods (201) and to a second daily period (202) in a sequence from the second daily periods (202) according to the respective weekdays and the respective daytime times, respectively, wherein the second daily period (202) is offset in time and overlaps with the corresponding first daily period (201); and - Determining and / or adapting a usage order (150) for a future point in time based on the total amount (205) of allocated data entries for a specific first daily period (201) and a specific second daily period (202), wherein the specific second daily period (202) is offset from and overlaps with the specific first daily period (201).

14. The device (130) according to any of the preceding claims, wherein the device (130) is configured to output a recommendation for executing the determined usage order (150) to a user of the cleaning robot (100) via a user interface of the cleaning robot (100).

15. A method (500) for determining a usage order (150) for a cleaning robot (100); wherein the method (500) comprises: - determining (501) the total amount of cleaning orders that have been executed, which have been executed by the cleaning robot (100) in the past operating period; wherein each cleaning order respectively specifies the scope (151, 152) of the cleaning tasks executed by the cleaning robot (100) in the corresponding cleaning order; and - Based on the total amount of cleaning orders already executed, determining and / or adapting (502) at least one usage order (150) for a future point in time; wherein the usage order (150) describes the scope (151, 152) of the cleaning tasks to be performed by the cleaning robot (100) in the usage order (150).

Images