Device and method for determining a usage application

Abstract

A device (130) for determining a usage order (150) for a cleaning robot (100) is described. The device (130) is configured to determine a set of cleaning orders already executed that were carried out by the cleaning robot (100) within a past operating period, wherein the individual cleaning orders each indicate a scope (151, 152) of the cleaning task carried out 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 based on the set of cleaning orders already executed, wherein the usage order (150) indicates a scope (151, 152) of the cleaning task to be carried out by the cleaning robot (100) in the usage order (150).

Description

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

[0002] A cleaning robot can be used in a household to perform one or more different cleaning tasks, in particular vacuuming and / or mopping. For this purpose, a user of the cleaning robot can be enabled to define a usage task for performing a cleaning task via a user interface of the cleaning robot. The usage task can be directed at immediate (ad hoc) execution of the cleaning task (so that the cleaning task is initiated manually). On the other hand, the usage task can be directed at a cleaning task planned for the future (which corresponds to a so-called scheduled task). Defining usage tasks for performing different cleaning tasks can potentially involve a relatively high level of effort for the user.

[0003] This document addresses the technical task of increasing the convenience of a cleaning robot with regard to defining a usage order for performing a cleaning task in an efficient and reliable manner.

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

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

[0006] The device is configured to determine a set (e.g., 10 or more, or 50 or more, or 100 or more) of previously executed cleaning jobs that were performed by the cleaning robot within a previous operating period (e.g., 1 week or more, or 4 weeks or more). The individual cleaning jobs from the set of previously executed cleaning jobs can each have been initiated manually by a user of the cleaning robot (via a user interface of the cleaning robot).

[0007] The individual cleaning jobs specify the scope of the cleaning task performed by the cleaning robot in the respective cleaning job, in particular the spatial scope of the cleaning task and / or the scope of the cleaning task (e.g., vacuuming or mopping). Furthermore, the individual cleaning jobs can specify the time, in particular the day of the week and the time of day, at which the respective cleaning job was performed.

[0008] This makes it possible to determine historical usage data relating to the previous use of the cleaning robot (in the form of a set of cleaning jobs already carried out).

[0009] The device is configured to determine and / or adapt at least one usage order for a future point in time based on the number of cleaning orders already executed. The determined usage order can be a planned usage order that is automatically executed, in particular started, by the cleaning robot at a specific point in time, in particular on a specific day of the week and / or at a specific time of day (without requiring user interaction via a user interface of the cleaning robot).

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

[0011] Thus, a device is described that is designed to determine a suggestion for a (possibly planned) usage task based on historical usage data (relating to the previous use of the cleaning robot and / or the cleaning tasks performed so far). The usage task can define a cleaning task with a specific spatial scope and / or with a specific task scope. This can ensure particularly convenient operation of the cleaning robot.

[0012] The overall area (e.g., the house or apartment) in which the cleaning robot operates can be divided into a plurality of different sub-areas (e.g., rooms). The spatial extent can specify one or more sub-areas from the plurality of different sub-areas.

[0013] The cleaning robot can be configured to operate in several different cleaning modes (e.g., vacuuming or wiping, or a combination of both). Furthermore, the intensity (e.g., suction power and / or water volume) of each cleaning mode can be changed and / or adjusted if necessary. The scope of the task can specify the cleaning mode of the cleaning robot and / or the intensity of the cleaning mode.

[0014] The device can be configured to output a suggestion for executing the determined usage task to a user of the cleaning robot via a user interface of the cleaning robot. The user interface can be provided, for example, on a user device (such as a smartphone) of the user. The user can accept the suggestion in order to operate the cleaning robot in a convenient manner.

[0015] The device can be configured to detect, based on the number of cleaning jobs already performed, that no cleaning job has been performed within the past operating period for a specific sub-area of ​​the overall area in which the cleaning robot is operated and / or for a specific cleaning mode of the multiple different cleaning modes that can be performed by the cleaning robot. Based on this detection, a usage job can be determined (and suggested) that includes the specific sub-area and / or the specific cleaning mode. This can enable particularly convenient operation of the cleaning robot.

[0016] Alternatively or additionally, the device can be configured to identify, on the basis of the number of cleaning jobs already carried out, a specific sub-area of ​​the overall area and / or a specific cleaning mode of the plurality of different cleaning modes of the cleaning robot, for which there is a relatively high number of cleaning jobs (e.g. greater than a number threshold) in the number of cleaning jobs already carried out. Based on this knowledge, a usage job can be determined and / or adapted which has the specific sub-area and / or the specific cleaning mode as its scope. In particular, the device can be configured to identify an already planned usage job which already has the specific cleaning mode but not the specific sub-area as its scope.The scope of the already planned usage order can then be expanded to include the specific sub-area and saved in a modified form. This enables particularly convenient operation of the cleaning robot.

[0017] The device can be configured to determine the upcoming time, in particular the day of the week and the time of day, for the execution of the usage task based on the times, in particular the days of the week and / or the time of day, and the number of cleaning tasks already executed. This enables particularly convenient operation of the cleaning robot.

[0018] As already explained above, the scope of the individual cleaning jobs from the set of cleaning jobs already carried out can each indicate one or more sub-areas of the overall area in which the cleaning robot is operated.

[0019] The device can be configured to subdivide the individual cleaning jobs from the set of previously executed cleaning jobs into one or more data entries for the corresponding one or more sub-areas, so that the scope of the individual data entries only relates to a single sub-area of ​​the overall area. The individual cleaning jobs can thus each be subdivided into one or more components (i.e., data entries), one data entry per sub-area. The usage order for the upcoming point in time can then be determined and / or adjusted in a particularly precise and robust manner based on the data entries.

[0020] As already explained above, the individual cleaning orders and the data entries determined therefrom can each specify a day of the week and a time of day on which and at which the respective cleaning order or the respective data entry was carried out. The device can be configured to assign the determined data entries, depending on the respective day of the week and the respective time of day, to a day segment from a sequence of day segments, wherein the sequence of day segments divides a week into a limited number of day segments (e.g., between 20 and 100).

[0021] For each of the individual day segments in the sequence of day segments, a set of associated data entries can thus be determined. The usage order for the upcoming time can then be determined and / or adjusted in a particularly robust and precise manner based on the set of associated data entries for at least one day segment.

[0022] In particular, the device can be configured to identify a day segment that has a number of associated data entries equal to or greater than a threshold value (e.g., 2 or more, or 3 or more). The usage request for the upcoming time can then be determined and / or adjusted in a particularly precise and robust manner based on the number of associated data entries for the identified day segment.

[0023] The device can be configured to determine the anticipated time, in particular the day of the week and the time of day, for the usage request based on the day of the week and the time of day of the individual data entries of the set of assigned data entries for the identified day segment. For example, the time of day of the usage request can be determined as the average of the times of day of the data entries.

[0024] The device can be configured to detect that a usage order is already scheduled for the identified daytime segment. The scope of the scheduled usage order can then be expanded based on the number of assigned data entries for the identified daytime segment. This enables particularly convenient operation of the cleaning robot.

[0025] The device can be configured to assign the determined data entries, depending on the respective day of the week and the respective time of day, to a first day segment from a sequence of first day segments and to a second day segment from a sequence of second day segments, wherein the second day segments are temporally offset and overlap with the corresponding first day segments. The usage request for the preceding time can then be determined and / or adjusted in a particularly precise and robust manner based on the set of assigned data entries for a specific first day segment and for a specific second day segment that is offset and overlap with the specific first day segment.

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

[0027] According to a further aspect, a method for determining a usage order for a cleaning robot is described. The method comprises determining a set of previously executed cleaning orders that were carried out by the cleaning robot within a past operating period, wherein the individual cleaning orders each indicate the scope of the cleaning task carried out by the cleaning robot in the respective cleaning order. Furthermore, the method comprises determining and / or adapting, based on the set of previously executed cleaning orders, at least one usage order for a future point in time, wherein the usage order indicates the scope of the cleaning task to be carried out by the cleaning robot in the usage order.

[0028] It should be noted that any aspects of the device and / or method described in this document can be combined in a variety of ways and / or in any desired manner. In particular, the features of the patent claims can be combined in a variety of ways and / or in any desired manner.

[0029] The invention will be described in more detail below with reference to exemplary embodiments shown in the accompanying drawings. Figures 1a and 1b an exemplary cleaning robot as an example of a suction and / or sweeping and / or wet cleaning and / or wiping device in different perspective views; Figure 1c exemplary components of a cleaning robot; Figure 1d an example user interface for defining a usage order; Figure 2a an exemplary division of a time period into daily periods; Figure 2ban exemplary analysis of historical cleaning orders; Figure 3 a flowchart of an exemplary method for analyzing historical cleaning orders; Figures 4a and 4b a flowchart of an exemplary procedure for adapting a (already defined) planned usage order; and Figure 5 a flowchart of an exemplary procedure for determining a usage order.

[0030] As stated at the beginning, this document aims to increase the convenience of defining usage tasks for a cleaning robot. In this context, Fig. 1a the top 121 and Fig. 1b the underside 122 of a cleaning robot 100, in particular a vacuum robot.

[0031] During vacuuming operation of the cleaning robot 100, the underside 122 faces the floor to be cleaned or the surface of a cleaning area, such as a room, to be cleaned. The underside 122 of the cleaning robot 100 typically has one or more drive units 101 (with one or more drive wheels), by means of which the cleaning robot 100 can be moved independently in order to clean different areas of the floor. Furthermore, the cleaning robot 100 can have one or more guide and / or support elements 104 (e.g., non-driven wheels) that enable stable movement of the cleaning robot 100 over the floor to be cleaned. In addition, a cleaning robot 100 typically comprises one or more cleaning units 106 (in particular, suction nozzles) that are configured to clean the floor beneath the cleaning robot 100.

[0032] A cleaning unit 106 (in particular a suction nozzle) may include a brush roller 102 configured to rotate about a rotation axis, wherein the rotation axis is typically arranged parallel to the underside 122 of the cleaning robot 100. The brush roller 102 may be used to mechanically remove dust and / or contaminants from the floor to be cleaned, so that the dust and / or contaminants can be sucked into the suction mouth 107 of the cleaning unit 106 with increased reliability.

[0033] On the top side 121 of the cleaning robot 100, a user interface 112 (see Fig. 1c) which enables a user of the cleaning robot 100 to make control inputs. Alternatively or additionally, the cleaning robot 100 can comprise 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 smartphone. In addition, the cleaning robot 100 can comprise a bumper 105 on a side wall 123 (e.g., on a side wall 123 in the front area of ​​the cleaning robot 100), wherein a shock sensor can be arranged on the bumper 105, which is configured to record sensor data indicating whether or not the cleaning robot 100 has hit an obstacle in the direction of movement 120. The triggering of the shock sensor (due to the deflection of the bumper 105) by an obstacle can, for example,cause the cleaning robot 100 to rotate about its vertical or vertical axis, which is perpendicular to the floor, and thereby change the direction of movement 120 in order to avoid the obstacle.

[0034] Furthermore, a cleaning robot 100 typically has one or more environment sensors 110 (see Fig. 1c) that are configured to capture environmental or sensor data relating to the environment of the cleaning robot 100. The one or more environmental sensors 110 can 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 lidar and / or radar sensors, etc. A control unit 130 of the cleaning robot 100 can be configured to determine digital map information relating to the cleaning area to be cleaned based on the environmental data and, if necessary, to store it on a storage unit 111 of the cleaning robot 100. The cleaning robot 100 can use the digital map information to independently orient itself within the cleaning area (e.g., within a room) and / or to determine a route for cleaning the cleaning area.

[0035] Fig. 1cshows a Cartesian coordinate system with a longitudinal axis (i.e., an x-axis), a transverse axis (i.e., a y-axis), and a vertical axis (i.e., a z-axis). The direction of movement 120 of the cleaning robot 100 typically corresponds to the longitudinal axis. The rotation axis of the brush roller 102 typically runs along the transverse axis.

[0036] The user of the cleaning robot 100 can be enabled to specify a usage order for a cleaning task of the cleaning robot 100 at a user interface of the cleaning robot 100. A usage order can alternatively be referred to as a cleaning order (particularly if the order is initiated manually by the user). The user interface can be provided, for example, via a mobile device (such as a smartphone) of the user. Fig. 1dshows an exemplary user interface for defining a usage order or cleaning order 150. The usage orders and / or the cleaning orders 150 can be stored in an external processing 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 performed by the cleaning robot 100 (in particular, the scope of the cleaning task) can be specified. Exemplary aspects and / or dimensions are, a spatial dimension (ie the spatial scope of the task) 151, which defines the spatial area of ​​the cleaning task. In the Fig. 1dIn the example shown, it can be determined, for example, whether the spatial sub-areas A, B, C and / or D are to be cleaned. The individual sub-areas (in particular rooms) can be recognized as differentiated sub-areas (in particular rooms) during a mapping or exploration run of the cleaning robot 100 in an overall area (e.g. in a residential environment) and / or have been determined by the user. A cleaning mode (i.e. the scope of the task) 152, in which it is determined, for example, whether vacuuming or wiping or both should be carried out. Furthermore, the intensity of the fan for the vacuuming operation and / or the amount of wiping water for the wiping operation can be determined, if necessary. A temporal dimension 153, in which, for example, the time is determined at which the cleaning task is to be carried out, in particular started. A periodicity 154 of the usage order, by which it is determined, for example, how often (e.g.on which day of the week) the usage order 150 should be carried out.

[0037] A planned usage task 150 (for the future) can also be referred to as a "Scheduled Task".

[0038] This document describes a method and a corresponding device 130 which make it possible to create suggestions for new planned usage orders 150 or for adapting existing planned usage orders 150 based on the usage history of a cleaning robot 100.

[0039] The cleaning robot 100 can be configured to store each of its usage orders or cleaning orders 150 (both manually initiated usage orders and planned usage orders) by specifying one or more of the following information: Start time (i.e., temporal dimension 153) of the usage order 150; e.g., the day of the week (generally, the periodicity 154) of the usage order 150; rooms included in the usage order 150 (for "Clean-All" orders, all rooms that were reached and cleaned) and / or zones (i.e., spatial dimension 151); cleaning mode set for cleaning (vacuum / wipe, power level, possibly driving strategy, etc.), i.e., scope of the order 152; whether cleaning was aborted prematurely by the user and, if applicable, after which portion of the area; and / or whether cleaning had to be aborted for other reasons, e.g., due to a locked door.

[0040] Based on the documentation of the start times for cleaning certain rooms or zones, the frequency of these usage orders 150 can also be determined.

[0041] A breakdown of the usage orders 150 by individual rooms and the cleaning mode used allows conclusions to be drawn about the cleaning tasks actually desired by the user. It can be advantageous to distinguish the rooms (i.e., sub-areas) actually cleaned by the cleaning robot during a "Clean-All" order (where the entire area is to be cleaned) from those that are theoretically marked on the map but could not be cleaned or were not cleaned. This is due to the usage behavior of some users who start a "Clean-All" program but intentionally block access to certain rooms (e.g., by means of a door) in order to ultimately allow the cleaning robot 100 to work only in the desired one or more rooms.There are also users who carry the cleaning robot 100 into a room, give the "Clean-All" cleaning command and close the room door to let the robot clean only in that room.

[0042] Furthermore, detailing individual areas may be of interest, for example, to document "spot cleaning" programs in which the cleaning robot 100 is to clean a (round or square) area with a specific dimension (e.g., with a specific diameter, edge length, or square meterage) at a specific location. If such cleaning is performed by the user relatively frequently at almost the same location, this cleaning task can also be suggested for recurring cleaning as a usage task 150. Examples of such areas could be: the entrance area at the front door, the area in front of the kitchen unit, or in front of a cat litter box.

[0043] The documentation of usage orders 150 canceled by the user allows conclusions to be drawn as to whether a usage order 150 was incorrectly entered by the user or whether only parts of the defined area were to be cleaned. For example, if the cleaning of three rooms is commissioned but canceled after two, it can be assumed that cleaning the last room was not considered as important. However, if a room was cleaned to more than 75%, for example, before cleaning was canceled, it can be concluded that cleaning of the room was planned and desired. If necessary, every usage order 150 in which the planned area of ​​a room was cleaned to more than 75% can be saved and taken into account. All room-cleaning mode combinations of the usage order 150 can be adopted as entries in the usage history.An exemplary vacuuming and wiping usage order 150 at full power level across the rooms or zones "A", "B" and "C" can thus be carried out via the data entries. A, Vacuuming, 100% power, Thursday, 10:15 AM; B, Vacuuming, 100% power, Thursday, 10:15 AM; C, Vacuuming, 100% power, Thursday, 10:15 AM; A, Mopping, 100% power, Thursday, 10:15 AM; B, Mopping, 100% power, Thursday, 10:15 AM; C, Mopping, 100% power, Thursday, 10:15 AM be broken down.

[0044] An analysis algorithm can evaluate the usage history repeatedly, e.g., once a day or once a week. For this purpose, usage data for a specific past operating period (e.g., 4 or 8 past 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 only provide a suggestion for a usage order 150 when a sufficient amount of usage data is available. Furthermore, usage data from a relatively long time ago can be disregarded or given less weight in the analysis to enable an analysis of the user's current usage behavior. Usage data from a relatively long time ago can therefore be deleted.

[0045] The data entries to be included in the analysis can be sorted by room-cleaning mode combinations (i.e., by data entries). Each individual combination (i.e., each individual data entry) can then be examined separately.

[0046] All data entries belonging to a combination (e.g., "Room B, Vacuuming, 100% Power") can be assigned to individual "day segments." These day segments are time intervals of a 7-day, 24-hour week and each have a length of, for example, 4 hours (or 2 hours or 6 hours). A particularly robust analysis can be achieved by additionally introducing the same number of second day segments, which have the same length but are offset by half a length from the first day segments. Fig. 2a shows exemplary first day sections 201 and exemplary second day sections 202 for a period of approximately 1 ½ days.

[0047] The individual data entries can be assigned (based on the respective day of the week and the respective time of day) to a first day segment 201 and a second day segment 202, into which the respective data entry falls. The number of data entries assigned to a day segment 201, 202 allows conclusions to be drawn about when a user performed the corresponding room-cleaning mode combination relatively frequently or relatively rarely. Thus, a set 205 of data entries can be determined for each of the individual day segments 201, 202.

[0048] The one or more day segments 201, 202 in which at least a certain minimum number of data entries for cleaning tasks were performed can then be examined. For the individual day segments 201, 202, it can thus be checked whether a threshold of data entries has been reached or exceeded. Overlapping day segments 201, 202 that have both reached the threshold can be combined into a common, merged day segment. Data entries assigned to both overlapping day segments 201, 202 are transferred only once to the merged day segment. This procedure prevents inaccurate predictions of usage behavior for data entries close to segment boundaries.

[0049] In the resulting list of (possibly merged) day segments, a data point can be created for each day segment that exceeds the threshold for data entries for executed cleaning tasks. This data point is used as a representative for the day segment in further processing. The data point remains linked to the day segment and the associated data entries, but is assigned a timestamp that corresponds, for example, to the average start times of all data entries assigned to the day segment. This allows a set of data points to be determined that represent when a room-cleaning mode combination was executed relatively frequently within a week (Monday - Sunday).

[0050] Fig. 2b shows a list of (merged) day segments 212 with the respective amount 215 of data entries. Furthermore, Fig. 2b the resulting data points 219.

[0051] Using the generated data points 219 as independent suggestions for usage orders 150 may lead to a temporal collision with other suggestions for other room-cleaning mode combinations or to a temporal collision with already existing usage orders.

[0052] In a subsequent step, all data can be merged, ie all data points of all room-cleaning mode combinations as well as all existing (already planned) usage orders 150. This can in turn be done by assigning the data to day segments 201, 202 (as in connection with Fig. 2aThe temporal length of the daily segments 201, 202 can be maintained, or shorter daily segments 201, 202 can be used. By specifying a minimum temporal length for the individual daily segments 201, 202 (e.g., one hour), it can be ensured that there is a sufficiently large interval between consecutive usage orders 150 (e.g., to be able to charge the electrical energy storage device of the cleaning robot 100).

[0053] An assignment to a first and a second day segment 201, 202 can be made again, and a merge of day segments 201, 202 and the sets 205 of data entries can then be effected. Based on the merged day segments 212 and the merged sets 215, data points 219 for usage orders 150 can then be determined (taking into account already existing planned usage orders 150).

[0054] The described method can be divided into several steps, which can be assigned to two stages. In the first stage, data entries are created and assigned to day segments 201, 202 before the data entries are summarized into data points 219. This reduces the amount of data to be further processed and compared. In the second stage, these data points are themselves assigned to day segments 201, 202 before the actual evaluation finally takes place. The first stage can be performed for each room-cleaning mode combination, and in the second stage, all data can then be combined again to determine combined usage orders 150 (for multiple rooms).

[0055] Fig. 3shows a flowchart of an exemplary method 300 for evaluating the usage history of a cleaning robot 100. In a step 301, data entries can be created based on the usage history (e.g., based on a set of cleaning jobs already performed). A data entry can 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 daily periods 201, 202 (wherein the individual daily periods 201, 202 are Fig. 3referred to as day-part intervals). Furthermore, in a further step 303, overlapping day parts 201, 202, each having a number of data entries that exceeds a certain threshold, can be combined to form merged day parts 212. Based on the set 215 of data entries of a merged day part 212, a data point 219 can be determined (step 304). Steps 301 to 304 can correspond to a first stage of the method 300.

[0056] In a second stage of method 300, the determined data points 219 and the already defined planned usage orders 150 (i.e., scheduled tasks) can be assigned to day segments 201, 202 (step 305). Furthermore, in a further step 306, overlapping day segments 201, 202, each having a certain minimum number of data entries, can be combined.

[0057] Thus, (merged) day segments 212 can be defined, each of which has data points 219 and planned usage orders 150. This information can be used to define new (possibly planned) usage orders 150 and / or to adapt existing planned usage orders 150.

[0058] First, by evaluating the 219 data points per room or zone, it can be determined when the room or zone was last cleaned. If the last cleaning process that included this room or zone was more than, for example, 10 days ago, and if other cleaning tasks were carried out during this period (i.e., the user was not away on a trip), the user can be asked (via one or more user interfaces) whether this room or zone should be cleaned in a specific way (e.g., intensity of dry and / or wet cleaning). Alternatively, the user can be suggested to expand a possibly already existing scheduled task (i.e., a planned usage task) to include the cleaning of this room. On the other hand, if the identified room is never intended to be cleaned, this room may no longer be suggested for cleaning in the future.

[0059] Furthermore, the one or more remaining day segments 212, which contain a set 215 of data entries, can be evaluated individually. For this purpose, a check can be performed for each data point 219 of a manually initiated cleaning job 150 to determine whether there is already an entry for a scheduled task in the same day segment 212 with the same room and cleaning mode settings, or whether the data point 219 can be converted into a scheduled task alone or with one or more other data points 219 from the same or another day segment 212. The following cases, among others, can be considered during this check: 1. For a considered data point 219 of a manually started usage task 150, there is no suitable scheduled task with the same room-cleaning mode combination in the associated day section 212. In the associated and no other day section 212, there is another data point with the same room-cleaning mode combination within a defined maximum time interval (e.g., 2 hours). This considered data point 219 is a candidate for a new scheduled task. The user can be presented with a suggestion for a usage task 150 for this room-cleaning mode combination. The suggested start time can correspond to the mean of the start times of the data entries assigned to the data point (or alternatively, the latest start time) and can, for example, be rounded to quarter hours. The data point 219 can then be removed from the overview. 2.For a considered data point 219 of a manually started usage order 150, there is a matching scheduled task in the associated day section 212 which, with the same cleaning mode combination, covers the room of the usage order 150. Both entries lie within a defined maximum time interval (e.g., 2 hours). This data point 219 is already included in a scheduled task. The data point 219 therefore does not need to be considered further and can be removed from the overview. 3. For a considered data point 219 of a manually started usage order 150, there is a matching scheduled task in the associated day section 212 which covers the same cleaning mode combination, but not the same room. Both entries lie within a defined maximum time interval (e.g., 2 hours). This data point 219 is a candidate to be added to the existing scheduled task.A suggestion can be made to the user to extend the scheduled task to include the room of data point 219. The suggested start time can remain unchanged, if necessary, but can also correspond to an average of the start times (data point 219, scheduled task) (e.g., rounded to quarter hours). Data point 219 can then be removed from the overview. 4. For a considered data point 219 of a manually started usage order 150, there is no suitable scheduled task in the associated day section 212 that includes the same room-cleaning mode combination, but in simultaneous or temporally overlapping day sections 212 of other weekdays. The start times of data point 219 and scheduled task are within a defined maximum time interval (e.g., 2 hours). This data point 219 is a candidate to be added to the existing scheduled task.The user can be given a suggestion to extend the scheduled task (in particular the periodicity and / or frequency of the scheduled task) to include the weekday of data point 219. The suggested start time can remain unchanged if necessary, but can also correspond to an average of the start times (data point 219, scheduled task) (e.g., rounded to quarter hours). Data point 219 can then be removed from the overview. 5. For a considered data point 219 of a manually initiated usage order 150, there is no suitable scheduled task in the associated day section 212 on any weekday that includes the same room-cleaning mode combination, but there are one or more other data points 219 of manually initiated cleaning orders with the same room-cleaning mode combination in simultaneous or temporally overlapping day sections 212 of other weekdays.The start times of the data points 219 are within a defined maximum time interval (e.g. 2h). This data point 219, as well as the one or more similar data points 219 found, are candidates for a new scheduled task. A suggestion for this room-cleaning mode combination on the relevant weekdays 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 data points 219 (or alternatively, the latest start time) and can, for example, be rounded to quarter hours. Data point 219 and the one or more other combined data points 219 can then be removed from the overview.

[0060] Overall, a structured sequence of checks can be performed for each data point 219, resulting in the above-mentioned and / or further case distinctions. The suggestion to create a new scheduled task from a data point 219 of a manually initiated usage task 150 may only be issued if all options for adapting one or more existing, already planned usage tasks 150 have already been checked and evaluated negatively.

[0061] It can be assumed that the one or more cleaning settings for individual rooms are defined with the respective scheduled task and are also adopted from this data and applied by the cleaning robot 100. However, it is also possible for a user to specify room-specific cleaning modes, which are specified in advance by the user in the map of the user interface for each room. Thus, one or more cleaning modes can be associated with each individual room.

[0062] In a scheduled task or in a manually started usage order, it may not be necessary to provide information about the cleaning mode, as this is automatically taken from the map data depending on the room to be cleaned.

[0063] This eliminates the need to compare the cleaning mode for the evaluation of the data entries or data points 219 and the existing usage orders 150. Within the scope of the described procedure, only the start time and room may be evaluated.

[0064] The suggestions for one or more new or modified usage orders 150 are preferably not implemented directly, but can be sent to the user (e.g., to the user's device) via push notification. The user can then accept or reject the suggestions. The suggestions can remain temporarily stored until the user provides feedback, or—if the user does not use the user interface for a relatively long time—until a newer suggestion replaces the previous one. If the user accepts the suggestion(s), corresponding changes to the one or more planned usage orders 150 are automatically implemented.

[0065] In the Figures 4a and 4b An exemplary method 400 for determining a proposal for a planned usage order 150 is described. The method 400 comprises a series of yes / no branches, wherein the yes branches in each case Fig. 4b are shown.

[0066] For a data point 219 for a manually initiated cleaning job in a day segment 212, it can be checked whether a planned usage job 150 with the same settings 152 already exists in the same day segment 212 and for the same room 151 (generally for the same sub-area and / or for the same area) (steps 401, 402). If this is the case, the data point 219 can be deleted (step 413).

[0067] If this is not the case, it can be checked whether a planned usage order 150 with the same settings already exists in the same day segment 212 but for a different room (sub-area and / or area) 151 (step 403). If this is the case, the already planned usage order 150 can be adjusted (i.e., expanded to include the room (sub-area and / or area) 151 of the data point 219) (step 414).

[0068] If this is not the case, it can be checked whether a planned usage order 150 with different settings 152 already exists in the same day segment 212 and for the same room (partial area and / or area) 151 (step 404). If this is the case, the already planned usage order 150 can be adjusted (i.e., expanded to include the settings of data point 219) (step 415).

[0069] If this is not the case, it can be checked whether a planned usage order 150 with the same settings 152 already exists in the same day segment 212 and for the same room (partial area and / or space) 151 but for a different weekday 154 (step 405). If this is the case, the already planned usage order 150 can be adjusted (i.e., extended by the weekday 154 of the data point 219) (step 416).

[0070] If this is not the case, it can be checked whether one or more other data points 219 exist that have the same settings 152 in the same day part 212, but on a different day of the week (step 406). If this is the case, a new planned usage order 150 (for the data points 219) can be created (step 417).

[0071] If this is not the case, it can be checked whether one or more other data points 219 exist for the same room (sub-area and / or area) 151, for the same day part 212, for the same or a different weekly entry, and each with a different setting 152 (step 407). If this is the case, a new planned usage order 150 (for the data points 219) can be created (step 418).

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

[0073] The method 400 can then be repeated for the following data point 219. Thus, the data points 219 for the manually initiated cleaning jobs can be checked one after the other.

[0074] Through the measures described in this document, the cleaning jobs (usage jobs) 150 initiated via the timer function can be automatically adapted to the user's usage preferences, if necessary, without requiring user intervention. For example, the user receives suggestions for usage jobs 150 for frequently manually initiated cleaning tasks, so that the user has to start the cleaning robot 100 less frequently and can rely on the scheduled usage jobs 150.

[0075] Within the framework of the described method, a distinction can be made between individual days of the week, rooms, and / or cleaning modes during the evaluation, so that user preferences can be recognized and taken into account with particular precision. If necessary, the user can be reminded to clean previously missed areas. By combining data entries into data points 219 as described above, the amount of data to be processed can be reduced, allowing even relatively large amounts of data to be evaluated with limited hardware performance.

[0076] Fig. 5shows a flowchart of a (possibly computer-implemented) method 500 for determining a usage order 150 for a cleaning robot 100. The method 500 comprises determining 501 a set of previously executed cleaning orders that were carried out by the cleaning robot 100 within a past operating period. The individual cleaning orders can each indicate the scope 151, 152 of the cleaning task carried out by the cleaning robot 100 in the respective cleaning order.

[0077] The method 500 further includes determining and / or adapting 502, based on the number of cleaning jobs already executed, at least one usage job 150 for a future point in time. The usage job 150 can specify the scope 151, 152 of the cleaning task to be performed by the cleaning robot 100 in the usage job 150.

[0078] The present invention is not limited to the embodiments shown. In particular, it should be noted that the description and figures are intended only to illustrate the principle of the device and / or method described in this document. List of reference symbols

[0079] 100Cleaning robot 101Drive unit 102Brush roller 104Guiding and / or supporting element 105Bumper 106Cleaning unit / suction nozzle 107Suction mouth 110Environment sensor 111Storage unit 112User interface 113Communication interface 120Direction of movement / longitudinal direction 121Top side 122Bottom side 123Side wall 130Control unit / control device 150Usage order 151Spatial scope of order 152Task scope 153Temporary scope of order 154Periodicity 201, 202Day section / time section 205Set of historical usage orders 212Fused day section / time section 215Fused set of historical usage orders 219Data point for a usage order 300Method for analyzing historical Usage orders 301-306Procedural steps 400Procedure for adapting a planned usage order 401-408, 413-419Procedural steps 500Procedure for determining a usage order 501,502Procedural steps

Claims

1. Device (130) for determining a usage order (150) for a cleaning robot (100); wherein the device (130) is configured to - determine a set of cleaning orders already executed that were carried out by the cleaning robot (100) within a past operating period; wherein the individual cleaning orders each indicate a scope (151, 152) of the cleaning task carried out by the cleaning robot (100) in the respective cleaning order; and - determine and / or adapt at least one usage order (150) for a future point in time based on the set of cleaning orders already executed; wherein the usage order (150) indicates a scope (151, 152) of the cleaning task to be carried out by the cleaning robot (100) in the usage order (150).

2. Device (130) according to claim 1, wherein the scope (151, 152) of a cleaning job and / or a usage job (150) comprises - a spatial scope (151) of the cleaning task; wherein the spatial scope (151) in particular indicates one or more sub-areas from an overall area that is divided into a plurality of different sub-areas; and / or - a task scope (152) of the cleaning task; wherein the task scope (152) in particular indicates a cleaning mode, such as vacuuming or wiping or both, of the cleaning robot (100) and / or an intensity of the cleaning mode.

3. Device (130) according to one of the preceding claims, wherein - the individual cleaning jobs from the set of already executed cleaning jobs were each started manually by a user of the cleaning robot (100); and - the determined usage job (150) is a planned usage job (150) that is automatically executed, in particular started, by the cleaning robot (100) at a specific time, in particular on a specific day of the week and / or at a specific time of day.

4. Device (130) according to one of the preceding claims, wherein the device (130) is configured - based on the number of cleaning jobs already carried out, to recognize that - for a specific sub-area of ​​an overall area in which the cleaning robot (100) is operated; and / or - for a specific cleaning mode of several different cleaning modes that can be carried out by the cleaning robot (100), no cleaning job has been carried out within the past operating period; and - based thereon, to determine a usage job (150) which has the specific sub-area and / or the specific cleaning mode as its scope (151, 152).

5. Device (130) according to one of the preceding claims, wherein the device (130) is configured to - based on the set of cleaning jobs already carried out - identify a specific sub-area of ​​an overall area; and / or - identify a specific cleaning mode from a plurality of different cleaning modes of the cleaning robot (100), for which there is a relatively high number of cleaning jobs in the set of cleaning jobs already carried out; and - based thereon, determine and / or adapt a usage job (150) which has the specific sub-area and / or the specific cleaning mode as its scope (151, 152).

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

7. Device (130) according to one of the preceding claims, wherein - the individual cleaning jobs each specify a time, in particular a day of the week and a time of day, at which the respective cleaning job was executed; and - the device (130) is configured to determine the upcoming time, in particular a day of the week and a time of day, for the execution of the usage job (150) based on the times of the set of cleaning jobs already executed.

8. Device (130) according to one of the preceding claims, wherein - the scope (151, 152) of the individual cleaning jobs from the set of already executed cleaning jobs each indicates one or more sub-areas of an overall area in which the cleaning robot (100) is operated; and - the device (130) is configured to - divide the individual cleaning jobs from the set of already executed cleaning jobs into one or more data entries for the corresponding one or more sub-areas, so that the scope (151, 152) of the individual data entries each relates only to a single sub-area of ​​the overall area; and - determine and / or adapt the usage job (150) for the upcoming point in time based on the data entries.

9. Device (130) according to claim 8, wherein - the individual cleaning orders and the data entries determined therefrom each indicate a day of the week and a time of day on which and at which the respective cleaning order orthe respective data entry has been carried out; and - the device (130) is configured to - assign the determined data entries, depending on the respective day of the week and the respective time of day, to a respective day segment (201, 202) from a sequence of day segments (201, 202), wherein the sequence of day segments (201, 202) divides a week into a limited number of day segments (201, 202); - determine a respective set (205) of assigned data entries for the individual day segments (201, 202) of the sequence of day segments (201, 202); and - determine and / or adapt the usage order (150) for the upcoming time based on the set (205) of assigned data entries for at least one day segment (201, 202).

10. The device (130) according to claim 9, wherein the device (130) is configured to - identify a day portion (201, 202) having a number of associated data entries equal to or greater than a number threshold; and - determine and / or adapt the usage order (150) for the upcoming time based on the quantity (205) of associated data entries for the identified day portion (201, 202).

11. Device (130) according to claim 10, wherein the device (130) is configured to determine the preceding time, in particular the day of the week and the time of day, for the usage order (150) on the basis of the day of the week and the times of day of the individual data entries of the set (205) of assigned data entries for the identified part of the day (201, 202).

12. The device (130) according to one of claims 10 to 11, wherein the device (130) is configured to - detect that an already planned usage order (150) exists for the identified day portion (201, 202); and - expand the scope (150) of the already planned usage order (150) based on the set (205) of assigned data entries for the identified day portion (201, 202).

13. The device (130) according to one of claims 9 to 12, wherein the device (130) is configured to - assign the determined data entries, depending on the respective day of the week and the respective time of day, to a first day segment (201) from a sequence of first day segments (201) and to a second day segment (202) from a sequence of second day segments (202), wherein the second day segments (202) are offset in time and overlap with the corresponding first day segments (201); and - determine and / or adapt the usage order (150) for the upcoming time based on the set (205) of assigned data entries for a specific first day segment (201) and for a specific second day segment (202) that is offset and overlaps with the specific first day segment (201).

14. Device (130) according to one of the preceding claims, wherein the device (130) is configured to output a suggestion 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) a set of cleaning orders already executed that were carried out by the cleaning robot (100) within a past operating period; wherein the individual cleaning orders each indicate a scope (151, 152) of the cleaning task carried out by the cleaning robot (100) in the respective cleaning order; and - determining and / or adapting (502), based on the set of cleaning orders already executed, at least one usage order (150) for a future point in time; wherein the usage order (150) indicates a scope (151, 152) of the cleaning task to be carried out by the cleaning robot (100) in the usage order (150).

Images