Control of robotic vacuum cleaner based on dust distribution data
By receiving dust distribution data, the robot vacuum cleaner optimizes the cleaning path and operating parameters, solving the problem of inefficiency in the existing technology, and achieving a more efficient and accurate dust cleaning effect.
Patent Information
- Application Number
- CN202380027669.7
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Priority Date
- 2022-03-17
- Filing Date
- 2023-03-02
- Publication Date
- 2024-11-08
AI Technical Summary
During cleaning operations, automatic robot vacuum cleaners may consume power in unwanted places due to the inability to accurately identify the distribution of dust in buildings, resulting in inefficiency and poor cleaning results.
By receiving and analyzing dust distribution data, the robot vacuum cleaner can plan cleaning paths and operating parameters such as suction, brush bar rotation speed and cleaning speed to optimize the cleaning process and ensure deeper cleaning in areas with the most dusty areas.
It improves cleaning efficiency and power utilization, ensures that the dust distribution data of building floors is effectively utilized, and achieves more accurate and efficient cleaning operations.
Smart Images

Figure CN118922114A_ABST
Abstract
Description
Technical Field
[0001] The present invention relates to a computer implementation of controlling a robotic vacuum cleaner based on received dust distribution data, which may be in the form of a dust distribution map. A corresponding system is also provided. Background Art
[0002] In ordinary homes and other buildings, dust particles are so small that they are difficult, if not impossible, to detect with the naked eye. As a result, when performing cleaning operations such as vacuuming, the user essentially has to perform the task "blindly." A similar problem occurs with automatic robotic vacuum cleaners. Without knowing where in a building the dustiest locations are typically located, a robotic vacuum cleaner may unnecessarily consume power in locations within the building where little dust is collected. It would therefore be desirable to generate and ultimately use data indicating the spatial distribution of dust particles on a building floor. And to be able to use such data in order to inform and ultimately control the cleaning operations of a robotic vacuum cleaner. Summary of the invention
[0003] At a high level, the present invention relates to a robotic vacuum cleaner planning cleaning operations based on dust distribution data, which indicates the spatial distribution of dust particles on a building floor. In some cases, the dust distribution data can be in the form of dust particle size distribution data, which not only provides information about the spatial distribution of dust particles, but also provides information about the size distribution of dust particles on the building floor. Therefore, the present invention is able to automatically plan cleaning operations based on the amount and location of dust particles in a user's home or other places, thereby improving and fine-tuning the cleaning process. Specifically, a first aspect of the present invention provides a computer-implemented method for controlling the operation of a robotic vacuum cleaner, the computer-implemented method comprising: receiving dust distribution data indicating the spatial distribution of dust particles on a building floor; and based on the received dust distribution data, planning a cleaning operation of the building floor performed by the robotic vacuum cleaner.
[0004] Before elaborating on more optional features of the invention, some features of the robotic vacuum cleaner in question are first considered in more detail.
[0005] The robot vacuum cleaner is configured to perform a cleaning operation in which it passes through a building floor, performing some cleaning action, such as vacuuming, dusting, wiping, etc. The cleaning operation is planned, and the plan can be retrieved from, for example, a memory of the robot vacuum cleaner. In a preferred case, the cleaning action is vacuuming, in which dust particles on the floor are entrained in an airflow, which causes the dust particles to be removed from the floor by suction and deposited in a container forming part of the robot vacuum cleaner. In some cases, the container can be removed from the robot vacuum cleaner. During this process, the dust particles move along the airflow path. In terms of its nature as a robot vacuum cleaner, it is understood that the robot vacuum cleaner includes some device for generating a vacuum or negative pressure, thereby generating a suction force, which causes air to flow from the outside of the robot vacuum cleaner into the airflow path. The device for generating a vacuum or negative pressure can be referred to as a vacuum generating component, and can include a motor. The speed of the motor (e.g., revolutions per minute) is preferably proportional to or related to the suction force. The higher the motor speed, the stronger the suction force. The speed of the motor can be controlled by controlling the power supply to the motor, wherein the more power supplied to the motor, the faster the speed, and vice versa. The motor may have a plurality of predetermined power levels, each corresponding to a predetermined motor speed. Preferably, there are three predetermined power levels corresponding to three different motor speeds.
[0006] At any given time, the robotic vacuum cleaner may be configured to remove dust particles from a cleaning area of the floor. Specifically, the cleaning area of the floor from which dust particles are removed at a given time may be an area of the floor below a cleaning area defining assembly of the robotic vacuum cleaner. Obviously, the cleaning area defining assembly is preferably located at the base of the robotic vacuum cleaner (here, the term "base" is used to refer to the side or surface of the robotic vacuum cleaner that faces or contacts the floor during the cleaning operation). The cleaning area defining assembly preferably includes a housing having an open base, wherein at least the outer wall of the housing defines the edge of the cleaning area.
[0007] The housing preferably comprises an outer shell having a lower edge, the lower edge being arranged to face the floor in use. Preferably, when the robot vacuum cleaner is placed on the floor and the base faces the floor, the lower edge is arranged to be spaced from the floor. The spacing ensures that air can enter the housing from the outside. In some cases, the housing may contain a brush. In use, when the robot vacuum cleaner moves on the floor, the brush can be configured to disturb or agitate the dust located on the floor (specifically, in the cleaning area of the floor), thereby causing the dust to be entrained in the moving air and enter the airflow path. In a preferred case, the brush can be configured to rotate in use, improving the degree to which the dust particles are disturbed, thereby ensuring that more dust particles can be entrained in the airflow and thus can be sucked up. Such a housing may be referred to as a brush bar. The lower edge of the brush bar housing may define a generally rectangular cleaning area of the floor, from which dust is removed at any given time. This may be referred to as a "brush bar area" in this article. The rotation of the brush may be controlled by a motor. The speed of the motor may be controlled by controlling the power supply to the motor, wherein the greater the power provided to the motor, the faster the speed, and vice versa. The motor may have a plurality of predetermined power levels, each corresponding to a predetermined motor speed. Preferably, there are three predetermined power levels corresponding to three different motor speeds.
[0008] The computer-implemented method according to the first aspect of the present invention requires that the cleaning operation be planned based on dust distribution data. In the context of the present application, the terms "dust distribution data" and "dust particle size distribution data" can be used interchangeably. In some cases, the dust distribution data can be in the form of a dust distribution map, which is a visual representation of the dust distribution data. Specifically, the dust distribution map can be a visual representation of the spatial distribution of the total mass or total number of dust particles on all particle sizes. Alternatively, the dust distribution map can be a visual representation of the spatial distribution of the total mass or total number of dust particles in a given particle size class (or in each of a plurality of particle size classes). The dust distribution map can be in the form of a heat map, in which different colors are used to indicate different values. The dust distribution map can provide a visual representation of the total mass or total number of dust particles per unit area, rather than showing the absolute total number or absolute total mass of dust particles (on all particle size classes, or within each particle size class).
[0009] The cleaning operation can be defined by a planned cleaning route, i.e., the path that the robot vacuum cleaner should pass through the floor of a room or the entire floor of a building, for example. The memory of the robot vacuum cleaner can store a map of the building floor (or more precisely, data representing the map of the building floor). The building floor can be divided into a plurality of regions, each region representing a room in a part of the building. The building floor can also be divided into a plurality of grid cells. Here, a "grid cell" can be generated simply by overlaying a grid onto the map of the building floor. In some cases, the grid can be a simple square grid, each grid cell being the same. Alternatively, the grid can be irregular. Planning the cleaning operation can include determining which regions and / or grid cells should be passed through, and in what order. More specifically, planning the cleaning operation can include generating data specifying which regions and / or grid cells are to be passed through and / or in what order. To this end, each grid cell and / or region can have an associated identifier. Throughout this application, for simplicity, the term "position" can be used to describe a grid cell or region. An area can include one or more grid cells. Planning the cleaning operation may include determining an order in which the robotic vacuum cleaner visits locations, the order of the locations being determined based on the received dust distribution data. In some cases, it may be preferred to prioritize locations containing the most dust. Thus, planning the cleaning operation may include sorting the locations in order of dust amount, and generating instructions that, when executed by a processor of the robotic vacuum cleaner, cause the robotic vacuum cleaner to visit the locations in order of decreasing dust amount. In this context, "dust amount" may refer to the total mass or total number of dust particles at a given location, optionally per unit area.
[0010] The cleaning operation may also be defined by one or more operating parameters. In the context of the present application, the term "operating parameter" refers to a value or description that defines how (or to what extent) the robot vacuum cleaner performs a given action. This will be elaborated later when an example of operating parameters is described in detail. In this case, planning the cleaning operation may include generating (or otherwise determining) one or more operating parameters, which are generated based on the received dust distribution data. Different operating parameters can be generated for different locations of the floor. Therefore, generating one or more operating parameters may include, for each of a plurality of locations of the building floor, generating corresponding values of one or more operating parameters. In these cases, the operating parameter values for each of the plurality of locations of the floor may be generated based on the dust distribution data associated with the corresponding location. For example, this may include generating data including an indication of one or more operating parameters for each of a plurality of location identifiers, each location identifier corresponding to a corresponding location of the building floor. For example, based on the total mass or total number of dust particles (optionally, per unit area), generating data may include generating one or more operating parameters for each grid cell or each area. Typically, the operating parameters will be selected so that the areas that typically contain the most dust experience a greater degree of cleaning. This will become clearer when discussing specific operating parameters.
[0011] A first example of an operating parameter that can be controlled based on dust distribution data is suction. Specifically, in a preferred case, based on the received dust distribution data, the suction selected at a location with a relatively high dust amount is higher than that at a location with a relatively low dust amount. Here, "dust amount" should be interpreted as described above. Based on the dust amount at a given location, generating an operating parameter may include selecting a power level to be provided to the motor when the robot vacuum cleaner is in that location. According to the previous disclosure, this may include selecting from a continuous range of power values, or from a predetermined (discrete) set of power values. For the sake of completeness, it is noted that a higher power is preferably selected in an area with a relatively high dust amount, while a lower power is preferably selected in an area with a relatively low dust amount. This ensures that the dustiest areas are cleaned with the greatest suction.
[0012] A second operating parameter that can be controlled based on the dust distribution data is the rotational speed of the brush within the housing. Specifically, in a preferred case, based on the received dust distribution data, the rotational speed of the brush bar is selected to be higher at a location where the dust amount is relatively high than at a location where the dust amount is relatively low. Based on the dust amount at a given location, generating an operating parameter may include selecting a power level to be provided to the motor when the robotic vacuum cleaner is in that location. According to the previous disclosure, this may include selecting from a continuous range of power values, or from a predetermined (discrete) set of power values. For the sake of completeness, it is noted that a higher power is preferably selected in areas where the dust amount is relatively high, while a lower power is preferably selected in areas where the dust amount is relatively low. This ensures that the brush bar cleans the dustiest areas when it rotates at maximum speed.
[0013] The third operating parameter that can be controlled based on the dust distribution data is the cleaning speed. In the context of the present invention, the term "cleaning speed" refers to the speed at which the robot vacuum cleaner moves through a given position. If the cleaning speed is higher, the robot vacuum cleaner will spend less time in each cleaning area (as defined above), so the cleaning area will be cleaned less thoroughly. If the cleaning speed is lower, the robot vacuum cleaner will spend more time in each cleaning area, so the cleaning area will be cleaned more thoroughly. Therefore, in a preferred case, according to the received dust distribution data, a lower cleaning speed is selected at a position where the dust amount is relatively high than at a position where the dust amount is relatively low. Alternatively, but very equivalently, the operating parameter can be the amount of time that the robot vacuum cleaner spends at a given position, such as the amount of time that the robot vacuum cleaner spends in each cleaning area. Therefore, in a preferred case, according to the received dust distribution data, the amount of time spent at a position where the dust amount is relatively high is selected to be higher than the amount of time spent at a position where the dust amount is relatively low.
[0014] Planning a cleaning operation may include generating a cleaning plan. The cleaning plan may include instructions that, when executed by a processor of the robotic vacuum cleaner, cause the robotic vacuum cleaner to perform the cleaning operation defined by the cleaning plan. The cleaning plan may include an ordered list of locations within a building floor (the ordering defines the order in which the robotic vacuum cleaner traverses the locations), and for each location, one or more operating parameters to be used at the location. More specifically, planning a cleaning operation may include generating data representing a cleaning plan as described above. In some cases, a computer-implemented method may include receiving a request for a cleaning plan, in response to which a step of generating a cleaning plan or planning a cleaning operation occurs. In some cases, the request may include various parameters that limit the plan. For example, the request may include the total length of time for the cleaning operation. Alternatively, the request may include instructions to clean only those areas with the highest amount of dust.
[0015] The above disclosure relates to the planning of a single cleaning operation. However, the computer-implemented method of the first aspect of the present invention can go further than this and include an automatic scheduling capability based on dust distribution data. Specifically, the computer-implemented method can include planning multiple cleaning operations based on the received dust distribution data. In this case, a further operating parameter can be the frequency at which the robot vacuum cleaner cleans a given location. The frequency can be defined according to the number of cleaning times within a given time period. Alternatively or in addition, the frequency can be defined according to the proportion of cleaning operations at which the robot vacuum cleaner cleans a given location. According to the received dust distribution map, the frequency is preferably selected to be higher in areas with relatively high dust volume than in areas with relatively low dust volume. For example, some areas that are generally considered to have only a small amount of dust may only be cleaned in every other cleaning operation, or once every two weeks, rather than once a week. In some cases, there may be multiple defined cleaning plans or planned cleaning operations, and planning multiple cleaning operations may include determining which predetermined planned cleaning operation should occur at which time. Each of the multiple defined cleaning plans is preferably based on dust distribution data, and each may have a related planning ID. Therefore, planning a cleaning operation may include assigning a planning ID to each of multiple, such as days or other cleaning periods. For example, a user may specify that they want to have a cleaning session every day, in which case a planning ID may be assigned to each day.
[0016] In the above, the focus has been on generating operating parameters based on the total amount of dust, that is, the total mass or total number of dust particles in a given location. However, it should be understood that the generation of operating parameters or the determination of cleaning paths can be based not only on the total amount of dust, but also on the amount of dust in each particle size class. The operating parameters can also be selected based on the floor type. For example, using a slower brush bar rotation speed can better pick up larger dust particles to ensure that the airflow can entrain the moving dust particles (otherwise the dust particles may have too much kinetic energy to be entrained in the airflow). In contrast, smaller particles usually require more agitation to be lifted from the floor because it is usually embedded deeper and represents a smaller target that the bristles of the brush can reach. Therefore, in areas with many smaller dust particles, higher brush bar rotation speeds are preferred. On hard floors, the higher the brush bar rotation speed, the better; on carpets, each time the bristles of the brush bar contact the carpet fibers, it is sometimes necessary to give the carpet fibers more time to relax, so a lower brush bar rotation speed may be preferred.
[0017] The table below shows examples of relative values of suction power, brush bar rotation speed and cleaning speed which may be preferred for specific floor types and predominant dust particle sizes.
[0018] Floor Type Particle size Optimum suction power Optimum brush bar rotation speed Robot speed carpet Small high Low / Medium normal Hard Floors Small high high Low carpet big medium Low Low Hard Floors big high Low normal
[0019] Here, the terms should be considered relative rather than absolute. The topics shown in columns 3 to 5 should also be considered independent of each other, i.e. for carpets with small dust particles, the optimum suction power may be high, but this need not be combined with a low / medium relative brush bar rotation speed or a normal robot speed. In other words, the table can be split into three separate, independent tables: one including columns 1, 2, 3; one including columns 1, 2, 4; and one including columns 1, 2, 5.
[0020] The first aspect of the invention relates to a computer-implemented method. However, it will be appreciated that a system performing such a computer-implemented method also provides the same advantages. Therefore, a second aspect of the invention provides a robotic vacuum cleaner system comprising a processor configured to perform the computer-implemented method of the first aspect of the invention. The optional features set out in conjunction with the first aspect of the invention are obviously also applicable to the computer-implemented method performed by the system of the second aspect of the invention and are not repeated here for the sake of brevity.
[0021] The first and second aspects of the present invention relate to a computer-implemented method by which a cleaning operation or part thereof is automatically planned based on received dust distribution data. In a third aspect of the present invention, a dust distribution map can be used to allow a user to plan a cleaning operation himself. This represents another way in which the control of a cleaning operation can be based on dust distribution data, this time in the form of a dust distribution map. Specifically, the third aspect of the present invention provides a computer-implemented method for controlling a robotic vacuum cleaner using a client device, the computer-implemented method comprising: receiving a dust distribution map indicating the distribution of dust particles on a building floor by a client device; displaying the dust distribution map on a display component of the client device; receiving a user input corresponding to a selected position of the dust distribution map, the selected position being a position to be cleaned by the robotic vacuum cleaner; generating instructions based on the received user input, when executed by a processor of the robotic vacuum cleaner, the instructions are configured to cause the robotic vacuum cleaner to clean a position of the building floor corresponding to the selected position of the dust distribution map. In some cases, receiving the user input includes receiving the user input via a touch screen of the client device. A fourth aspect of the present invention provides a system configured to perform the computer-implemented method of the third aspect of the present invention. The optional features set forth in relation to the first to third aspects of the present invention also apply equally to the fourth aspect of the present invention, unless clearly incompatible or the context clearly dictates otherwise.
[0022] A fifth aspect of the invention provides a computer-implemented method for monitoring dust distribution on a building floor, the computer-implemented method comprising: receiving dust distribution data indicating the distribution of dust particles on a building floor; comparing the dust distribution data with expected dust distribution data based on stored dust distribution data to determine the deviation between the amount of dust in one or more regions of the received dust distribution data and the corresponding regions in the stored dust distribution data; and generating an alarm if the deviation exceeds a predetermined threshold in one or more regions. The optional features associated with the first to third aspects of the invention may also apply to the fourth aspect of the invention, unless clearly incompatible, or the context clearly indicates otherwise.
[0023] Other aspects of the invention relate to the generation of dust distribution data and dust distribution maps, which are used by the foregoing aspects of the invention to inform and control the cleaning operation of a robotic vacuum cleaner.
[0024] Once the dust distribution map is generated, it can then be used to inform control decisions, more specifically, automatically plan subsequent cleaning operations. It should be noted that the features of the following aspects of the invention can be combined with the features of any of the previous aspects of the invention. For example, the present invention can be considered to cover a method of generating dust distribution data and then using the data to inform control decisions.
[0025] More specifically, another aspect of the present invention provides a system for generating dust particle size distribution data indicating the distribution of dust particles on a building floor, the system comprising: a robot vacuum cleaner, comprising: an airflow path having a piezoelectric sensor located therein, the piezoelectric sensor being configured to generate a plurality of electrical signals in response to a corresponding plurality of vibrations, each vibration being caused by dust particles striking a detection area of the airflow path; and a position determination module configured to determine position information of the robot vacuum cleaner within the building; and a data processing system, wherein: the data processing system is configured to generate dust particle size distribution data indicating the distribution of dust particle sizes on the building floor based on the plurality of electrical signals.
[0026] The robot vacuum cleaner can be configured to perform a cleaning operation in which it passes through a building floor, performing some cleaning action, such as vacuuming, dusting, wiping, etc. Preferably, the cleaning operation is pre-planned and can be retrieved from, for example, a memory of the robot vacuum cleaner. In a preferred case, the cleaning action is vacuuming, in which dust particles on the floor are entrained in an airflow, which causes the dust particles to be removed from the floor by suction and deposited in a container forming part of the robot vacuum cleaner. In some cases, the container can be removed from the robot vacuum cleaner. During this process, the dust particles move along the airflow path. In terms of its nature as a robot vacuum cleaner, it is understood that the robot vacuum cleaner includes some means for generating a vacuum or negative pressure, thereby generating a suction force, which causes air to flow from the outside of the robot vacuum cleaner into the airflow path. The means for generating a vacuum or negative pressure can be referred to as a vacuum generating component and can include a motor. The speed of the motor (e.g., revolutions per minute) is preferably proportional to or related to the suction force. The higher the motor speed, the stronger the suction force. The speed of the motor can be controlled by controlling the power supply to the motor, wherein the more power supplied to the motor, the faster the speed, and vice versa. The motor may have a plurality of predetermined power levels, each corresponding to a predetermined motor speed. Preferably, there are three predetermined power levels corresponding to three different motor speeds.
[0027] At any given time, the robotic vacuum cleaner may be configured to remove dust particles from a cleaning area of the floor. Specifically, the cleaning area of the floor from which dust particles are removed at a given time may be an area of the floor below a cleaning area defining assembly of the robotic vacuum cleaner. Obviously, the cleaning area defining assembly is preferably located at the base of the robotic vacuum cleaner (here, the term "base" is used to refer to the side or surface of the robotic vacuum cleaner that faces or contacts the floor during the cleaning operation). The cleaning area defining assembly preferably includes a housing having an open base, wherein at least the outer wall of the housing defines the edge of the cleaning area.
[0028] The housing preferably comprises an outer shell having a lower edge, the lower edge being arranged to face the floor in use. Preferably, when the robot vacuum cleaner is placed on the floor and the base faces the floor, the lower edge is arranged to be spaced from the floor. The spacing ensures that air can enter the housing from the outside. In some cases, the housing may contain a brush. In use, when the robot vacuum cleaner moves on the floor, the brush can be configured to disturb or agitate the dust located on the floor (specifically, in the cleaning area of the floor), thereby causing the dust to be entrained in the moving air and enter the airflow path. In a preferred case, the brush can be configured to rotate in use, improving the degree to which the dust particles are disturbed, thereby ensuring that more dust particles can be entrained in the airflow and thus can be sucked up. Such a housing may be referred to as a brush bar. The lower edge of the brush bar housing may define a generally rectangular cleaning area of the floor, from which dust is removed at any given time. This may be referred to as a "brush bar area" in this article. The rotation of the brush may be controlled by a motor. The speed of the motor may be controlled by controlling the power supply to the motor, wherein the greater the power provided to the motor, the faster the speed, and vice versa. The motor may have a plurality of predetermined power levels, each corresponding to a predetermined motor speed. Preferably, there are three predetermined power levels corresponding to three different motor speeds.
[0029] Here, "airflow path" refers to the route of moving air from the outside to the container, such as below the gap defined by the floor and the lower edge of the outer wall of the housing / shell, and then entering the container through the robot vacuum cleaner. The airflow path preferably includes an air duct located between the housing and the container and in fluid communication with it. In a preferred case, the piezoelectric sensor is located in the air duct. As previously mentioned, the piezoelectric sensor is configured to generate an electrical signal when dust particles hit the detection area of the airflow path. Here, "detection area" refers to any area located close enough to the piezoelectric sensor so that dust particles hitting the piezoelectric sensor can generate an electrical signal. For example, the detection area can be the area of the piezoelectric sensor itself. Alternatively, the detection area can include some or all of the inner surfaces of the air duct. It should be understood that no matter how the exact geometry of the detection area is, as long as the detection area remains constant throughout the cleaning operation or multiple cleaning operations, the piezoelectric sensor can obtain meaningful data.
[0030] The piezoelectric sensor preferably comprises a piezoelectric crystal. Those skilled in the art will appreciate that piezoelectric crystals have the property of accumulating charge in the material in response to an applied mechanical stress. This means that a voltage can be generated in response to an impact that causes vibrations in the piezoelectric crystal. Therefore, the electrical signal can be in the form of a voltage signal, although equivalently, a current signal or a power signal can also be used. The electrical signal preferably includes a graph of the electrical characteristic over time (or includes data representing the graph, for example by sampling the voltage across the piezoelectric signal at multiple time points). Preferably, a high sampling rate is used, at least 1000 measurements per second, more preferably at least 5000 measurements per second. More preferably, the sampling rate is at least 10,000 measurements per second, and even more preferably, about 15,000 measurements per second.
[0031] The data processing system can be configured to generate dust particle size distribution data indicating the distribution of dust particle sizes at different locations in a building. Here, "dust particle size distribution on the floor of a building" can be understood to refer to the distribution of particle sizes and locations. In other words, the dust particle size distribution data includes information about the distribution of dust particle sizes at different locations or partitions of the floor. More specifically, the "dust particle size distribution" of a given partition of a floor can refer to the number of dust particles or the total mass of dust particles in each of a plurality of predetermined size classes within the partition of the floor. The partitions may correspond to a plurality of cleaning areas defined by a cleaning area defining component, i.e., the partitions may each have an area corresponding to the area of the cleaning area defined by the cleaning area defining component of the robot vacuum cleaner. In these cases, it is particularly preferred that the cleaning areas are rectangular because this means that they can be paved on the floor. The nature of the dust particle size distribution data will be discussed in more detail later in this application with reference to the way it is generated.
[0032] The particle size classes may include one or more of the following: ultrafine dust particles, fine dust particles, medium dust particles, and coarse dust particles. The following table illustrates the upper and lower ranges of particle sizes within each class.
[0033] grade Lower limit (μm) Upper limit (μm) Ultrafine 5 to 15 45 to 135 thin 45 to 135 90 to 270 medium 90 to 270 250 to 750 thick 250 to 750 1000 to 3000
[0034] Of course, in each case, the lower limit must be lower than the upper limit. In preferred cases, the following upper and lower limits can be used.
[0035] grade Lower limit (μm) Upper limit (μm) Ultrafine 10 90 thin 90 180 medium 180 500 thick 500 2000
[0036] Here, the term "dust particle size" is defined according to industry standards. Specifically, dolomite particles are used to define "particle size". The particles are assumed to be spherical in nature with an average density of 2.7 g / cm 3According to this definition, the term "particle size" refers to the diameter of such particles. This is in accordance with the industrial standard IEC-60312 relating to household vacuum cleaners.
[0037] The method by which the data processing system generates dust particle size distribution data will now be discussed.
[0038] First, the determination of dust particle size is discussed. The data processing system may include a dust particle size determination module, which is configured to determine the size and / or mass of the dust particle based at least on the electrical signal of the piezoelectric sensor for each particle that hits the detection area. Specifically, for each particle that hits the detection area, the dust particle size determination module may be configured to determine the size information of the dust particle. Here, "size information" may refer to the particle size itself, or may more broadly refer to the particle size class to which the dust particle belongs. For example, the dust particle size determination module may be configured to determine the size of the particle, and then determine the particle size class based on the size of the particle. Alternatively, the particle size determination module may simply determine the particle size class immediately. Either is equally valid.
[0039] For each particle, the particle size determination module can be configured to determine size information by applying a particle size determination algorithm to the electrical signal generated by the piezoelectric sensor about the particle. As discussed, the output of the particle size determination algorithm can be the particle size itself, and the particle size determination module is then configured to determine the particle size class based on the particle size. Alternatively, the output of the particle size determination algorithm can be the particle size class itself. As discussed, either is equally valid. In some cases, the particle size determination algorithm can be configured to derive the particle momentum from the electrical signal and derive the particle mass based on knowledge of the airflow velocity. The particle size can then be determined by assuming that the particle is spherical and has a predetermined density (e.g., 2.7 g / cm 3 ) to estimate the volume of the particle. In these cases, the particle size can be taken as the diameter of a hypothetical spherical dust particle.
[0040] The core of generating a dust distribution map is to obtain data related to the spatial distribution of dust particles within a building. The system of the first aspect of the present invention includes a position determination module, which is configured to determine the position information of the robotic vacuum cleaner within the building. Here, "position information" refers to data identifying the position of the robotic vacuum cleaner in the building. However, there are various ways to configure the position determination module to determine the position information and associate it with a given particle.
[0041] In one approach, when the robotic vacuum cleaner is located in a particular cleaning zone (as defined above), the position determination module may be configured to identify the cleaning zone that the robotic vacuum cleaner is located in. It may do so, for example, based on identifying which stage of a planned cleaning operation the robotic vacuum cleaner is currently in, or it may detect the position, for example, using image data obtained by a camera.
[0042] During the cleaning operation, the robot vacuum cleaner can be configured to clean each cleaning area. Then, when the robot vacuum cleaner is in a first position, where dust from the first cleaning area is removed, the position determination module is configured to determine the position of the robot vacuum cleaner (e.g., record the position of the first cleaning area), and the particle size determination module is configured to determine the size information of each dust particle that hits the detection area of the piezoelectric sensor. In these cases, after all dust has been removed from the floor in the first cleaning area, or after a predetermined amount of time, the data processor can be configured to determine the total number of dust particles in each particle size class based on the size information that has been determined. To this end, the data processing system can include a particle counter. Therefore, the dust particle size distribution data generated for the first cleaning area or the first position can include the total number of dust particles in each particle class associated with the first cleaning area or its position, preferably stored in the memory of the robot vacuum cleaner. The robot vacuum cleaner can then be configured to move to a second cleaning area, and the process can be repeated so that the dust particle size distribution data for the second cleaning area includes the total number of dust particles in each particle class associated with the second cleaning area or its position, preferably stored in the memory of the robot vacuum cleaner. This process may be repeated for each of the broadly defined plurality of cleaning regions such that the dust particle size distribution data for each of the plurality of cleaning regions includes the number of particles in each particle size class for that region.
[0043] The robot vacuum cleaner may be configured to clean one cleaning area at a time, i.e. it may travel to a first cleaning area, stop, and then travel to a second cleaning area. Alternatively, and preferably, the robot vacuum cleaner may be configured to continuously pass through the floor.
[0044] In the cases discussed in the previous paragraph, the focus is on the total number of particles in each particle size class for each cleaning area. However, in alternative cases, the total mass of dust particles is of interest instead. In these cases, when the robotic vacuum cleaner is in a first position, where dust from the first cleaning area is removed, the position determination module is configured to determine the position of the robotic vacuum cleaner (e.g., record the position of the first cleaning area), the particle size determination module is configured to determine the size information of each dust particle that strikes the detection area of the piezoelectric sensor, and the particle mass determination module may be configured to determine the mass of each particle that strikes the detection area of the piezoelectric sensor. In these cases, after all dust has been removed from the floor in the first cleaning area, or after a predetermined amount of time, the data processor may be configured to calculate the total mass of dust particles in each particle size class based on the mass information that has been determined by the particle mass determination module. Therefore, the dust particle size distribution data generated for the first cleaning area may include the total mass of dust particles in each particle class associated with the first cleaning area or its position, preferably stored in the memory of the robotic vacuum cleaner. The robotic vacuum cleaner may then be configured to move to a second cleaning area, and the process may be repeated so that the dust particle size distribution data for the second cleaning area includes the total mass of dust particles in each particle class associated with the second cleaning area or its location, preferably stored in a memory of the robotic vacuum cleaner. The process may be repeated for each of a broad plurality of cleaning areas, so that the dust particle size distribution data for each of the plurality of cleaning areas includes the total number of particles in each particle size class for that area.
[0045] In some cases, in addition to the total mass of dust particles or the total number of dust particles within each particle size class, it may be desirable to obtain the total number of particles or the total mass of dust particles across all particle size classes. To this end, the data processing system may further include an addition module configured to calculate the total mass or total number of particles across all particle size classes within a given cleaning area. This data may then be stored in a memory of the system.
[0046] In the scenario given above, the cleaning area of the plurality of cleaning areas is predetermined, which means that there is a fixed particle size level in the dust particle size distribution data.
[0047] In relevant cases, the building floor can be divided into partitions that are smaller than the brush bar area and therefore smaller than the cleaning area. In these cases, during the cleaning operation, the position determination module can be configured to determine which partitions are located within or below the cleaning area defining component of the robot vacuum cleaner at a given time, such as when the robot vacuum cleaner is located in the first position. In other words, the position determination module is configured to determine which partitions are within the cleaning area at this time. This can be done based on the position information of the robot vacuum cleaner. At a given time, when the robot vacuum cleaner moves (continuously) on the floor, the particle size determination module is configured to determine the size information of each dust particle that impacts the detection area of the piezoelectric sensor. Each partition of the floor can be associated with a plurality of intervals, each of which corresponds to one of a plurality of particle size levels. Then, for each particle that impacts the detection area of the piezoelectric sensor, and for each partition of the floor in the cleaning area when the dust particle impacts the detection area (i.e., when the dust particle is detected), the particle counter can be configured to increase the value associated with the interval corresponding to the determined particle size level. In this way, as the robot vacuum cleaner moves across the floor, each time a dust particle is detected, the value of each interval increases while a zone of the floor is within the cleaning area of the robot vacuum cleaner. Note that this process applies regardless of whether the robot vacuum cleaner is moving continuously or incrementally.
[0048] In a related case, as an alternative or in addition to the above process, at a given time, when the robot vacuum cleaner moves on the floor, the particle size determination module is configured to determine the size information of each dust particle that hits the detection area of the piezoelectric sensor, and the dust particle mass determination module is configured to determine the mass of each dust particle that hits the detection area of the piezoelectric sensor. Each partition of the floor can be associated with a plurality of intervals, each interval corresponding to one of a plurality of particle size classes. Then, for each particle that hits the detection area of the piezoelectric sensor, and for each partition of the floor that is in the cleaning area when the dust particle hits the detection area (i.e., when the dust particle is detected), the cumulative mass determination module can be configured to increase the cumulative dust particle mass value associated with the interval corresponding to the determined particle size class. In this way, when the robot vacuum cleaner moves on the floor, each time a dust particle is detected, the cumulative dust particle mass value of each interval increases while the partition of the floor is in the cleaning area of the robot vacuum cleaner. It should be noted that this process is applicable regardless of whether the robot vacuum cleaner is moving continuously or incrementally.
[0049] In the examples given above, the term "interval" does not refer to a physical interval, but rather to an area where a value (in this case, a particle count or cumulative mass of dust particles) is stored. For example, this may correspond to a portion of the memory of a robotic vacuum cleaner or elsewhere on the system.
[0050] In other cases, dust particle size distribution data may be generated in a different manner to allow for more flexible particle sizing. In summary, as each dust particle is detected by the piezoelectric sensor, rather than having predetermined cleaning zones and determining the total mass or number of dust particles within each of those zones, its particle size class and optionally the particle mass is recorded, along with the position of the robot vacuum cleaner when the particle was detected. Then, after a cleaning operation (or at any suitable point in time), dust particle size distribution data may be generated by first defining a plurality of cleaning zones, and then by determining the total mass or number of dust particles in each particle size class for each defined cleaning zone.
[0051] More specifically, to generate dust particle size distribution data, for each dust particle detected by the piezoelectric sensor, the data processing system can be configured to determine the size information of the dust particle (in the same manner as previously outlined) and, optionally, the mass of the dust particle, and the position determination module can be configured to determine the position of the robot vacuum cleaner when the dust particle is detected. This data can then be stored, for example, on a memory of the robot vacuum cleaner. The data processing system can also be configured to generate or otherwise define a plurality of cleaning areas or area partitions, and determine the total number of dust particles in each particle size class, or the total mass of dust particles in each particle size class, for each defined cleaning area or area partition. As previously described, the addition module of the data processing system can then be configured to calculate the total number of dust particles or the total mass of dust particles over all particle size classes.
[0052] Throughout this application, "dust particle size distribution data" may refer to the total mass or total number of dust particles distributed into different particle size classes for each cleaning area or area partition, or the total mass or total number of dust particles at different particle size classes for each cleaning area or area partition.
[0053] Before discussing the generation of the dust distribution map in more detail, consider in more detail the physical components of the system, and the location where each step performed by the system occurs. The data processing system can be located on the robot vacuum cleaner, so all the features discussed above can occur on the robot vacuum cleaner without the need for an external server or the like. However, in a preferred case, in order to avoid the need to store a large amount of data in the memory of the robot vacuum cleaner, the system can further include a cloud computing server, or communicate with it (e.g., via a network). In this case, the data processing system can be a distributed data processing system, including a first data processor located on the robot vacuum cleaner and a second data processor located on the cloud computing server. The first data processor can include a particle size determination module and a particle mass determination module, and optionally includes a location determination module. The addition module can be located on the first data processor or the second data processor. The cloud computing server can include a memory configured to store dust particle size distribution data.
[0054] In those embodiments where the dust particle size distribution data is generated on a first processor on the robotic vacuum cleaner, but is further processed on a second data processor (e.g. on a cloud computing server) or the dust particle size distribution data is stored on a memory of a cloud computing server, it is first necessary to move the dust particle size distribution data from the robotic vacuum cleaner to the cloud computing server. Therefore, the robotic vacuum cleaner preferably comprises a memory (preferably a temporary memory in the form of a buffer memory or a cache), and the first data processor is configured to, after generating the dust particle size distribution data, send the generated dust particle size distribution data to the memory for (temporary) storage. Alternatively, the robotic vacuum cleaner may comprise a temporary memory and a permanent memory, and the robotic vacuum cleaner may be configured to send the data stored in the temporary memory to the permanent memory.
[0055] The moment at which the contents of the memory of the robot vacuum cleaner are transferred to the memory of the cloud computing server can be determined in a number of ways:
[0056] - The building floor may be divided into a plurality of zones, each zone corresponding to, for example, a room in the building. According to the cleaning plan, the robotic vacuum cleaner may be configured to clean the zones in sequence. In some cases, the first data processor may be configured to send data stored in the memory of the robotic vacuum cleaner to the cloud computing server after the robotic vacuum cleaner has cleaned each zone.
[0057] - Similarly, the building floor may be divided into a plurality of fixed-size grids. For example, each grid may be 1.5 m x 1.5 m, but the grid is not required to be a square grid. According to the cleaning plan, the robotic vacuum cleaner may be configured to clean the grids successively. In some cases, the first data processor may be configured to send data stored in the memory of the robotic vacuum cleaner to the cloud computing server after cleaning each grid.
[0058] - Similar to the two above cases, the robotic vacuum cleaner may be configured to send data stored in the memory of the robotic vacuum cleaner to the cloud computing server after each cleaning area (defined previously) has been cleaned.
[0059] - In some cases, the robotic vacuum cleaner may be configured to send data stored in the memory of the robotic vacuum cleaner to the cloud computing server only after the entire cleaning operation is completed, for example when all areas and / or all grids have been cleaned according to the cleaning plan.
[0060] In some cases, the robotic vacuum cleaner may be configured to send data stored in the memory of the robotic vacuum cleaner to the cloud computing server at predetermined time intervals. The time intervals are preferably fixed.
[0061] - In some cases, the first data processor of the robotic vacuum cleaner may be configured to continuously send data to the cloud computing server as the data is generated.
[0062] In some cases, the frequency with which the dust particle size distribution data is transmitted to the cloud computing server may be selected by a user, such as via an application on a client device.
[0063] It has now been explained how dust particle size distribution data is generated by a data processing system. As previously described, aspects of the first aspect of the present invention are particularly effective for generating dust particle size distribution data for generating a dust distribution map. Therefore, now consider the steps of generating a dust distribution map. At a high level, the data processing system can be configured to generate instructions based on the dust particle size distribution data, which, when executed by a processor of a client device, cause a display component of the client device to display a dust distribution map that visually represents the dust particle size distribution data.
[0064] The data processing system may be configured to receive a request for a dust distribution map and generate instructions in response to receiving the request for the dust distribution map. Specifically, in some cases, a first data processor on the robotic vacuum cleaner may be configured to receive the request for the dust distribution map. Or alternatively, a second data processor on the cloud computing server may be configured to receive the request for the dust distribution map.
[0065] In embodiments where the dust particle size distribution data is stored on the robotic vacuum cleaner, the first data processor is preferably configured to receive a request for a dust distribution, and accordingly, the first data processor is preferably configured to generate instructions in response to the request. In other embodiments where the dust particle size distribution data is stored externally (i.e., on a cloud computing server), if the robotic vacuum cleaner is configured to receive a request for a dust distribution map, it is preferably also configured to transmit the request to a second data processor on the cloud computing server. The request may then be received by the second data processor, and the second data processor may be configured to generate instructions in response to the request. Alternatively or in addition, the second data processor at the cloud computing server may be configured to receive a request for a dust distribution map, and to generate instructions in response to the request.
[0066] After having generated the instructions, the data processing module is preferably configured to transmit the instructions to the client device, whereupon the processor of the client device is preferably configured to execute the instructions.As a result of executing the instructions, the display component of the client device is preferably configured to display a dust distribution map representing the dust particle size distribution data.
[0067] Now discuss the dust distribution map that can be generated and displayed on the display component of the client device. The dust distribution map is a visual representation of the dust particle size distribution data. The dust distribution map can be a visual representation of the spatial distribution of the total mass or total number of dust particles on all particle sizes. Alternatively, the dust distribution map can be a visual representation of the spatial distribution of the total mass or total number of dust particles in a given particle size class (or in each of a plurality of particle size classes). The dust distribution map can be in the form of a heat map, where different colors are used to indicate different values. The dust distribution map can provide a visual representation of the total mass or total number of dust particles per unit area, rather than displaying the absolute total number or absolute total mass of dust particles (on all particle size classes, or within each particle size class). The calculation or determination of the total mass or total number of dust particles per unit area can be performed during the generation of dust particle size distribution data (e.g., performed by a data processing system, then performed by a first data processor or a second data processor). Alternatively, the determination or calculation of the total mass or total number of dust particles per unit area can be performed during instruction generation (e.g., performed by a data processing system, a first data processor, or a second data processor).
[0068] Aspects of the invention described so far focus on a system for generating dust particle size distribution data. A corresponding aspect of the invention provides a method for generating dust particle size distribution data indicating the distribution of dust particles on a building floor, the method comprising: generating a plurality of electrical signals by a piezoelectric sensor in response to a corresponding plurality of vibrations during a cleaning operation of a robot vacuum cleaner, each vibration being caused by dust particles striking a detection area of an airflow path of the robot vacuum cleaner; determining position information indicating the position of the robot vacuum cleaner within a building; and generating dust particle size distribution data indicating the distribution of dust particle sizes on a building floor based on the plurality of electrical signals and the determined position information. It is easy to understand that the method according to this aspect of the invention achieves the same technical effect as the system aspect.
[0069] Optional features of the system aspects of the present invention are also applicable to the method aspects of the present invention, unless clearly incompatible, or the context clearly indicates otherwise. Various optional features are explicitly listed below, but it should be noted that the features listed above still apply.
[0070] The method may also include performing a cleaning operation by the robotic vacuum cleaner, wherein it passes through the building floor, performing some cleaning action, such as vacuuming, dusting, wiping, etc. Preferably, the cleaning operation is pre-planned, and the method may include retrieving the cleaning plan from, for example, a memory of the robotic vacuum cleaner. In a preferred case, the cleaning action is vacuuming, wherein dust particles on the floor are entrained in an airflow, which causes the dust particles to be removed from the floor by suction and deposited in a container forming part of the robotic vacuum cleaner. In some cases, the container can be removed from the robotic vacuum cleaner. During this process, the dust particles move along the airflow path. In terms of its nature as a robotic vacuum cleaner, it is understood that the robotic vacuum cleaner includes some means for generating a vacuum or negative pressure, thereby generating a suction force, which causes air to flow from the outside of the robotic vacuum cleaner into the airflow path.
[0071] Performing a cleaning operation may include removing dust particles from a cleaning area of the floor at any given time. Specifically, the cleaning area of the floor from which dust particles are removed at a given time may be an area of the floor below a cleaning area defining assembly of the robotic vacuum cleaner, as previously described in detail with reference to the first aspect of the invention.
[0072] The steps for generating dust particle size distribution data are now discussed in more detail.
[0073] First, the determination of the dust particle size is discussed. For each particle that strikes the detection area, the method may include the step of determining size information for the particle, wherein "size information" has the same meaning as previously used in this application. For example, the method may include determining the size of the particle and then determining the particle size class based on the determined size. Alternatively, the method may include immediately determining the particle size class. Either method is equally valid.
[0074] Determining the size information of the dust particle may include applying a particle size determination algorithm to the electrical signal generated for the particle. As discussed, the output of the particle size determination algorithm may be the particle size itself, and the particle size determination module is then configured to determine the particle size class based on the particle size. Alternatively, the output of the particle size determination algorithm may be the particle size class itself. As discussed, either method is equally valid.
[0075] The method of the second aspect of the invention comprises determining the position of the robotic vacuum cleaner within the building. However, there are various ways in which this can be achieved and the position information can be associated with a given particle.
[0076] In one method, when the robot vacuum cleaner is located in a particular cleaning area (as defined above), determining position information indicative of the position of the robot vacuum cleaner may include identifying the cleaning area in which the robot vacuum cleaner is located, for example based on identifying which stage of a planned cleaning operation the robot vacuum cleaner is currently in. Alternatively, the method may include detecting the position, for example using image data obtained by a camera. During the cleaning operation, the method may include cleaning one cleaning area at a time by the robot vacuum cleaner (i.e. moving to the cleaning area, vacuuming, and then continuing to move). In these cases, when the robot vacuum cleaner is in a first position, where dust from the first cleaning area is removed, the method may include determining the position of the robot vacuum cleaner (e.g. recording the position of the first cleaning area), and determining size information for each dust particle that impacts the detection area of the piezoelectric sensor. In these cases, after all dust has been removed from the floor in the first cleaning area, or after a predetermined amount of time, the method may further include determining the total number of dust particles in each particle size class based on the size information. The dust particle size distribution data generated for the first cleaning area may therefore include the total number of dust particles in each particle class associated with the first cleaning area or its position, preferably stored in a memory of the robot vacuum cleaner. The method may include moving the robotic vacuum cleaner to a second cleaning area and repeating the process so that the dust particle size distribution data for the second cleaning area includes the total number of dust particles in each particle class associated with the second cleaning area or its location, preferably stored in a memory of the robotic vacuum cleaner. The method may include repeating these steps for each of a broad plurality of cleaning areas so that the dust particle size distribution data for each of the plurality of cleaning areas includes the number of particles in each particle size class for that area.
[0077] In the case discussed in the previous paragraph, the focus is on the total number of particles in each particle size class for each cleaning area. However, in alternative cases, the total mass of dust particles is of interest instead. In these cases, when the robot vacuum cleaner is in a first position, where dust from the first cleaning area is removed, the method may include determining the position of the robot vacuum cleaner (e.g., recording the position of the first cleaning area), and determining the size information of each dust particle that strikes the detection area of the piezoelectric sensor, and determining the mass of each particle that strikes the detection area of the piezoelectric sensor. In these cases, after all dust has been removed from the floor in the first cleaning area, or after a predetermined amount of time, the method may include calculating the total mass of dust particles in each particle size class based on the mass information that has been determined by the particle mass determination module. Therefore, the dust particle size distribution data generated for the first cleaning area may include the total mass of dust particles in each particle class associated with the first cleaning area or its position, preferably stored in the memory of the robot vacuum cleaner. The method may also include moving the robot vacuum cleaner to a second cleaning area and repeating the process so that the dust particle size distribution data for the second cleaning area includes the total mass of dust particles in each particle class associated with the second cleaning area or its position, preferably stored in the memory of the robot vacuum cleaner. The method may further include repeating these steps for each of the broad plurality of cleaning regions such that the dust particle size distribution data for each of the plurality of cleaning regions includes the total number of particles in each particle size class for that region.
[0078] In some cases, in addition to the total mass of dust particles or the total number of dust particles within each particle size class, it may be desirable to obtain the total number of particles or the total mass of dust particles for all particle size classes. To this end, the method may further include calculating the total mass or total number of particles on all particle size classes within a given cleaning area. The method may further include storing in a memory of the system.
[0079] In the scenario given above, the cleaning areas among the multiple cleaning areas are predetermined, which means that there are fixed particle size levels in the dust particle size distribution data. In other cases, the dust particle size distribution data can be generated in a different way to achieve more flexible particle sizes. In summary, when the piezoelectric sensor detects each dust particle, instead of having predetermined cleaning areas and determining the total mass or number of dust particles in each of these areas, its particle size class and optionally the particle mass are recorded, as well as the position of the robot vacuum cleaner when the particle was detected. Then, after the cleaning operation (or at any suitable point in time), the dust particle size distribution data can be generated by first defining multiple cleaning areas and then by determining the total mass or number of dust particles in each particle size class for each defined cleaning area.
[0080] More specifically, to generate dust particle size distribution data, for each dust particle detected by the piezoelectric sensor, the method may include determining size information of the dust particle (in the same manner as previously outlined) and optionally the mass of the dust particle, and determining the position of the robotic vacuum cleaner when the dust particle was detected. The method may then include storing the information on, for example, a memory of the robotic vacuum cleaner. The method may also include generating or otherwise defining a plurality of cleaning areas or area partitions, and determining the total number of dust particles in each particle size class or the total mass of dust particles in each particle size class for each defined cleaning area or area partition. As previously described, the method may further include calculating the total number of dust particles or the total mass of dust particles for all particle size classes.
[0081] A first data processor located on board the robotic vacuum cleaner and a second data processor located on a cloud computing server have been described. It should be appreciated that the same optional features apply here wherever the various method steps occur.
[0082] In those embodiments where the dust particle size distribution data is generated on a first processor on the robotic vacuum cleaner, but is further processed on a second data processor (e.g. on a cloud computing server) or the dust particle size distribution data is stored on a memory of a cloud computing server, it is first necessary to move the dust particle size distribution data from the robotic vacuum cleaner to the cloud computing server. Therefore, the robotic vacuum cleaner preferably comprises a memory (preferably a temporary memory in the form of a buffer memory or cache), and the method further comprises sending, by the first data processor, the generated dust particle size distribution data to the memory for (temporary) storage after it has been generated. Alternatively, the robotic vacuum cleaner may comprise a temporary memory and a permanent memory, and the method may further comprise sending, by the robotic vacuum cleaner, the data stored in the temporary memory to the permanent memory.
[0083] The moment at which the contents of the memory of the robot vacuum cleaner are transferred to the memory of the cloud computing server can be determined in a number of ways:
[0084] - The building floor may be divided into a plurality of zones, each zone corresponding to, for example, a room in the building. According to the cleaning plan, the robotic vacuum cleaner may be configured to clean the zones successively. In some cases, the first data processor may be configured to send data stored in the memory of the robotic vacuum cleaner to the cloud computing server after the robotic vacuum cleaner has cleaned each zone.
[0085] - Similarly, the building floor may be divided into a plurality of fixed-size grids. For example, each grid may be 1.5 m x 1.5 m, but the grid is not required to be a square grid. According to the cleaning plan, the robotic vacuum cleaner may be configured to clean the grids successively. In some cases, the first data processor may be configured to send data stored in the memory of the robotic vacuum cleaner to the cloud computing server after each grid has been cleaned.
[0086] - Similar to the two above cases, the robotic vacuum cleaner may be configured to send data stored in the memory of the robotic vacuum cleaner to the cloud computing server after each cleaning area (defined previously) has been cleaned.
[0087] - In some cases, the robotic vacuum cleaner may be configured to send data stored in the memory of the robotic vacuum cleaner to the cloud computing server only after the entire cleaning operation is completed, for example when all areas and / or all grids have been cleaned according to the cleaning plan.
[0088] In some cases, the robotic vacuum cleaner may be configured to send data stored in the memory of the robotic vacuum cleaner to the cloud computing server at predetermined time intervals. The time intervals are preferably fixed.
[0089] - In some cases, the first data processor of the robotic vacuum cleaner may be configured to continuously send data to the cloud computing server as the data is generated.
[0090] In some cases, the frequency with which the dust particle size distribution data is transmitted to the cloud computing server may be selected by a user, such as via an application on a client device.
[0091] Now having explained how the data processing system generates dust particle size distribution data in the context of the second aspect of the invention. Now consider the step of generating a dust distribution map. At a high level, the method may further comprise generating instructions based on the dust particle size distribution data, which, when executed by a processor of a client device, cause a display component of the client device to display a dust distribution map visually representing the dust particle size distribution data.
[0092] To implement the process, the method may further include receiving a request for a dust distribution map, and generating instructions in response to receiving the request for the dust distribution map. Specifically, the first data processor may receive the request for the dust distribution map. Alternatively, the second data processor may receive the request for the dust distribution map.
[0093] In embodiments where the dust particle size distribution data is stored on the robotic vacuum cleaner, the method may include receiving a request for a dust distribution map by a first data processor, and correspondingly, generating instructions by the first data processor in response to the request. In other embodiments where the dust particle size distribution data is stored externally (i.e., on a cloud computing server), if the method includes receiving a request for a dust distribution map by the robotic vacuum cleaner, it preferably also includes transmitting the request by the first data processor to a second data processor on the cloud computing server. The request may then be received by the second data processor, and the second data processor may generate instructions in response to the request. Alternatively or in addition, the second data processor at the cloud computing server may receive a request for a dust distribution map and generate instructions in response to the request.
[0094] After the instructions have been generated, the method may further include transmitting the instructions to the client device, whereby a processor of the client device may execute the instructions. As a result of executing the instructions, a display component of the client device may display a dust distribution map representing the dust particle size distribution data.
[0095] With regard to the nature of the dust distribution map, the optional features set out above also apply to the second aspect of the invention.
[0096] Similar to the aforementioned aspect of the invention, another aspect of the invention may provide a method for generating dust particle size distribution data indicating the distribution of dust particles on a building floor, the method comprising: receiving a plurality of electrical signals generated in response to a corresponding plurality of vibrations from a piezoelectric sensor, each vibration caused by dust particles striking a detection area of an airflow path of a robotic vacuum cleaner; receiving position information indicating the position of the robotic vacuum cleaner within a building; and generating dust particle size distribution data indicating the distribution of dust particle sizes on a building floor based on the plurality of electrical signals and the determined position information. The method of the third aspect of the invention may be a computer-implemented method. It should be understood that the optional features set forth above with reference to the aforementioned aspects of the invention are equally applicable here, unless clearly incompatible or the context clearly dictates otherwise.
[0097] The present invention includes any combination of the described aspects and preferred features unless such a combination is expressly impermissible or explicitly avoided. BRIEF DESCRIPTION OF THE DRAWINGS
[0098] Embodiments of the present invention will now be described with reference to the accompanying drawings, in which:
[0099] - Figure 1A is a high-level system diagram that includes client devices, a robotic vacuum cleaner, and a cloud computing server.
[0100] - Figure 1B and 1CA robotic vacuum cleaner is shown, highlighting the location of the piezoelectric sensor.
[0101] - Figure 2 is a schematic diagram showing components of a client device.
[0102] - Figure 3 is a schematic diagram showing components of a robotic vacuum cleaner.
[0103] - Figure 4A is a schematic diagram illustrating components of a dust distribution data generation module of a processor of a robot vacuum cleaner.
[0104] - Figure 4B is a schematic diagram showing components of a control module of a processor of a robotic vacuum cleaner.
[0105] - Figure 5 is a schematic diagram showing components of a cloud computing server.
[0106] - Figure 6 is a flow chart illustrating at a high level the steps performed by the system of the present invention.
[0107] - Fig. 7A , 7B 8A and 8B are flowcharts showing the generation of dust distribution data.
[0108] - Figure 8C An example of a dust distribution map that can be generated using dust particle distribution data is shown.
[0109] - Fig.9A and 9B is a schematic diagram illustrating the movement of a robotic vacuum cleaner during a cleaning operation.
[0110] - Fig.10 is a flow chart showing the steps involved in transmitting dust distribution data to a cloud computing server.
[0111] - Fig.11 is a flow chart showing the steps that occur when a cloud computing server receives dust distribution data.
[0112] - Fig.12 is a flow chart showing the steps involved in a control operation based on dust distribution data.
[0113] - Fig.13 is a diagram showing the layout of zones in a building floor.
[0114] - Fig.14 is a table illustrating a set of operating parameters that a robotic vacuum cleaner may use.
[0115] - Fig.15is a flow chart showing the steps involved in the alarm generation process based on dust distribution data. DETAILED DESCRIPTION
[0116] Various aspects and embodiments of the present invention will now be discussed with reference to the accompanying drawings. Other aspects and embodiments will be apparent to those skilled in the art. All documents mentioned herein are incorporated herein by reference.
[0117] Figure 1A is a high-level schematic diagram of a system 1 that can be used to perform, for example, the method of the first aspect of the present invention. System 1 includes three components: a client device 10, a robotic vacuum cleaner 20, and a cloud computing server 30. These components are interconnected, as shown by the lines connecting them. Specifically, the client device 10, the robotic vacuum cleaner 20, and the cloud computing server 30 can be connected to each other via one or more networks (not shown), preferably a wireless network, such as a Wi-Fi network or a cellular network. In some cases, all three components can be connected by the same network, while in other cases, each pair of components can be connected by a separate corresponding network. In other cases, two pairs of components can be connected via a first network, and a third pair of components can be connected via a second network. Figure 1A and 1B An example of a robotic vacuum cleaner 20 is shown, which may be used in embodiments of the present invention and will be discussed in greater detail later.
[0118] Now refer to Figures 1B to 5 The components constituting the client device 10, the robot vacuum cleaner 20, and the cloud computing server 30 are described respectively, and then reference is made to Figures 6 to 13 Methods that can be performed by the corresponding components are described in detail.
[0119] Figure 2 An example of a client device 10 that can be used in accordance with the methods of the present invention is shown. The client device 10 is preferably a handheld device, such as a smartphone or tablet computer, on which applications configured to perform various aspects of the present invention are stored. The client device 10 includes a robotic vacuum cleaner interface module 102 for interfacing with the robotic vacuum cleaner 102. The client device 10 also includes a display component 104, an input receiving component 106 (e.g., a touch screen, which can be integrated with the display component 104), a processor 108, and a memory 110. The client device 112 also includes a cloud computing server interface module 112 for interfacing with the cloud computing server 30. The functions of these components will be described in more detail later in this application with reference to various methods that can be performed in accordance with the present invention.
[0120] Figure 3is a schematic diagram of a robot vacuum cleaner 20 that can be used in the method according to the present invention. The robot vacuum cleaner 20 includes a piezoelectric sensor 201 having a detection area 203. The purpose of the piezoelectric sensor 201 is to generate an electrical signal indicating the size and / or mass of the dust particles when the dust particles are incident on its detection area 203. Specifically, the piezoelectric sensor 201 is configured to generate an electrical signal based on the vibrations (and the pressure changes generated thereby) caused by the dust particles hitting the detection area 203. In some embodiments, the piezoelectric sensor 201 can be sensitive enough to generate an electrical signal based on the vibrations caused by the particles hitting the surface anywhere in the airflow path of the robot vacuum cleaner 20. Figure 1B and 1C A non-limiting example of a robotic vacuum cleaner 20 is shown, which may be used in embodiments of the present invention. In particular, these figures illustrate the location of an airflow path 22 within the robotic vacuum cleaner 20. The front of the robotic vacuum cleaner 20 includes a brush bar 24 that includes rollers 26. The base of the brush bar 24 defines an approximately rectangular area, referred to herein as brush bar area A. At a given time, when the robotic vacuum cleaner 20 is in a particular position, all dust particles located in the brush bar area A are entrained in the airflow and pass through the airflow path 22 (which is preferably in the form of an air duct, but it should be recognized that other arrangements are also possible). The piezoelectric sensor 201 is located on or in the top surface 28 of the airflow path 22, preferably with the detection area 203 exposed to the airflow path 22. As discussed, in some cases, the piezoelectric sensor 201 (e.g., RS PRO, SMD diaphragm external, piezoelectric buzzer, up to 30Vac 1 ) may generate a signal based only on vibrations caused by dust particles hitting the detection area 203, but in other cases, the electrical signal may be generated based on vibrations caused by dust particles hitting any inner surface 29 of the airflow path 22. In some cases, the electrical signal may be generated based on all or substantially all dust particles passing through the airflow path 22, but in other cases, the piezoelectric sensor 201 may generate an electrical signal only for a sample of dust particles passing through the airflow path 22. As long as the sampling ratio is constant or substantially constant, the present invention remains effective.
[0121] Back to Figure 3 The robot vacuum cleaner 20 further comprises a client device interface module 202 for interfacing with the client device 1. The robot vacuum cleaner 20 further comprises a processor 204, which comprises a dust distribution data generation module 210, the purpose of which is to generate dust distribution data based on input from the piezoelectric sensor 201. Figure 4AThe dust distribution data generation module 210 is shown in more detail in FIG. It includes a piezoelectric sensor interface module 2102 for interfacing with the piezoelectric sensor 201 (i.e., for receiving the electrical signal generated by the piezoelectric sensor 201, as described above). The dust distribution data generation module 210 also includes a particle size determination module 2014, a particle mass determination module 2106 (although it may not be present in some embodiments that do not measure particle mass), a particle counter 2108 (although it may not be present in some embodiments that do not count the number of particles), and a position determination module 2109. The functions of these modules will be described in detail later in this application.
[0122] Back again Figure 3 , the processor 204 also includes a control module 212, the purpose of which is to plan cleaning operations based on the dust distribution map or dust distribution data. Figure 4B More details of the control module 212 are shown, which includes an operating parameter generation module 2122, a cleaning route planning module 2124, and an alarm generation module 2126. The functions of these modules will be described in detail later in this application.
[0123] Back again Figure 3 , the robot vacuum cleaner 20 also includes a memory 206, which includes a buffer 2014, a dust particle mass determination algorithm 216 (although this may not be present in embodiments where particle mass calculation is not required), a dust particle size determination algorithm 218, a floor plan 220, and a cleaning plan 222. Finally, the robot vacuum cleaner 20 includes a cloud computing server interface module 208 for interfacing with the cloud computing server 30.
[0124] Figure 5 is a schematic diagram of a cloud computing server 30, which is preferably located remote from the robot vacuum cleaner 20 and the client device 10. The cloud computing server 30 includes a robot vacuum cleaner interface module 302 for interfacing with the robot vacuum cleaner 20. The cloud computing server 30 also includes a processor 304, which includes an addition module 310 and an instruction generation module 312. The cloud computing server 30 also includes a memory 306, which includes a buffer 314 and dust particle distribution data 316. Finally, the cloud computing server 30 includes a client device interface module 308 for interfacing with the client device 10.
[0125] Methods that may be performed according to some aspects of the present invention are now described in detail. Figure 62 is a flow chart showing the high-level steps performed by the dust distribution data generation module 210 of the processor 204 of the robotic vacuum cleaner 20. Steps S600 and S602 occur during a cleaning operation of the robotic vacuum cleaner 20, i.e., when the robotic vacuum cleaner 200 is vacuuming the floor of a house or other building according to some cleaning plan 222 stored in its memory 208. In step S600, raw particle data is received from the piezoelectric sensor 201 (specifically, via the piezoelectric sensor interface module 2102), and in step S602, position information is received from the position determination module 2109 of the dust distribution data generation module 210. Figure 6 In the embodiment, step S600 is shown as being performed before step S602, but these steps may occur in any order, or may occur simultaneously. Thereafter, at step S604, dust particle size distribution data is generated. In this context, dust particle size distribution data refers to data indicating the total number and / or mass of dust particles in each of a plurality of particle size classes within a given area. Now referring to Fig. 7A , 7B , 8A and 8B describe methods by which this operation may be performed.
[0126] Fig. 7A Involves a process in which the position of each particle detected is recorded individually. Fig. 7A The steps shown. In a first step S700, a dust particle causes a vibration, which is converted into an electrical signal by the piezoelectric sensor 201. Then, in step S702, the particle size determination module 2104 of the dust distribution data generation module 210 applies the dust particle size determination algorithm 218 to the electrical signal to determine which particle size class the dust particle in question falls into. Then, in step S704, the position where the robot vacuum cleaner 20 picks up the dust particle is obtained from the position determination module 2109 of the dust distribution data generation module 210. Then, finally, in step S706, the particle size class and corresponding position of the particle are recorded and stored in the buffer 214 of the memory 208 of the robot vacuum cleaner 20. As discussed, this process is performed for each dust particle detected by the piezoelectric sensor 201. The resulting final dust distribution data effectively includes a list of particles (e.g., each particle can be assigned a particle ID), together with their positions detected by the piezoelectric sensor 201, together with their particle size class. Figure 7B An almost identical process is shown, except that at step S702', the particle mass determination algorithm 216 is also applied to the electrical signal by the particle mass determination module 2106, so that the mass of the particle and the size class of the particle can be determined. Then, at step S708', the dust particle mass is also stored together with the position and particle size class.
[0127] Fig. 8A Involves the process of particle counting / mass determination for each brush strip area A. Fig.9A and 9B explains this in a little more detail. Fig.9A An example of a cleaning path that the robot vacuum cleaner 20 may take is shown, illustrated by a spiral line. In the example shown, a (x, y) Cartesian coordinate system is used to define points on the floor based on some predetermined origin. Fig. 9B As shown, as the robotic vacuum cleaner 20 advances along its path, it cleans the floor area corresponding to the brush bar area A, moving in increments of the same length as the longitudinal length of the brush bar (i.e., the length measured in the direction of movement of the robotic vacuum cleaner 20) or moving continuously. Fig. 8A , the process shown is performed when the robot vacuum cleaner 20 is located in each brush bar area A. In a first step (not shown), the position of the brush bar area A is determined and recorded. Then, when a particle is incident on the detection area 203 of the piezoelectric sensor 201, for example, an electrical signal is generated at step S800. Then, at step S802, the particle size determination module 2016 applies the dust particle size determination algorithm 218 to the electrical signal to determine the particle size class to which the dust particle belongs. At step S804, the particle size class is recorded, for example, in the buffer 214 of the memory 208. When the robot vacuum cleaner 20 is located in a given brush bar area A, steps S800 and S804 are performed for each particle detected. At step S806, based on all recorded data, the particle counter 2108 determines the number of particles in each particle size class of the given brush bar area. These counts can then be recorded in the buffer 214 of the memory 208 of the robot vacuum cleaner 20. The robot vacuum cleaner 20 can then move to the next brush bar area and repeat the process until the cleaning path has been completed. By recording only the total number of dust particles in each particle level for a given brush bar area, the amount of data that needs to be stored in the buffer 214 of the memory 208 is significantly reduced, although it is not as large as using Fig. 7A The resulting dust distribution map will have lower particle sizes than the dust distribution data generated by the method described above.
[0128] Figure 8B The process is largely the same, except that at step S802', the particle mass determination algorithm 216 is also applied to the electrical signal by the particle mass determination module 2106, so that the mass of the particles as well as the size class of the particles can be determined. Then, at step S808', for example, the total dust particle mass in each particle size class is determined by the particle mass determination module 2106, rather than just the number of particles.
[0129] At this point, the dust distribution data has been generated and stored in the buffer 214 of the memory 206 of the robotic vacuum cleaner 20. In some cases (not shown), this data may be transmitted to the permanent memory of the robotic vacuum cleaner, but in a preferred embodiment, the dust distribution data 316 is stored in (or associated with) the memory 306 of the cloud computing server 30. Fig.10 10. The process by which dust distribution data 316 may be stored on the memory 306 of the cloud computing server 30 is shown. In a first step S1000, it is determined, for example by the processor 204 of the robotic vacuum cleaner 20, that dust distribution data should be transmitted from the buffer 214 of the memory 306 of the robotic vacuum cleaner 20 to the cloud computing server 30. Scenarios in which the dust distribution data may be determined to be ready for transmission include when the robotic vacuum cleaner 20 has completed a full cleaning operation, when the robotic vacuum cleaner 20 has completed cleaning a predetermined area of a floor of a house or building at predetermined time intervals, or when, for example, a request for dust distribution data (e.g., in the form of a dust distribution map) is received from a client device 10. When it is determined in step S1000 that data should be transmitted, in step S1002, the processor 204 (e.g., a specific compression module, Figure 2 The generated dust distribution data stored in the buffer 214 of the memory 206 of the robot vacuum cleaner 20 can then be compressed. By compressing the data, there is less data to be transmitted to the cloud computing server 30 via one or more networks (not shown, but discussed in detail above). Fig.10 In step S1004, the dust distribution data is transmitted to the cloud computing server 30 via the cloud computing server interface module 208 of the robot vacuum cleaner 20. Fig.11 , Fig.11 The steps subsequently performed by the cloud computing server 30 are listed. At step S1100, dust distribution data is received at the cloud computing server 30 via its robot vacuum cleaner interface module 302. Then, at step S1102, the compressed dust distribution data is decompressed by, for example, a decompression module (not shown) of the processor 304 of the cloud computing server 30, and may be temporarily stored in, for example, a buffer 316 of the memory 306 of the cloud computing server 30. At this point, it should be recalled that the dust distribution data generated by the dust distribution data generation module 201 of the processor 204 of the robot vacuum cleaner 20 includes information that is divided into various particle size classes. For example, if the dust distribution data has been used Fig. 7A The dust distribution data may include multiple records, each including a particle size class and a location of a particle. Similarly, if a Fig. 8AIn the case of the method, for each brush bar area, the dust distribution data may include the total number of particles in each particle size class. In either case, there is no information on the total particle mass or total number of particles across all particle size classes. Fig.11 In step S1104, the adding module 310 of the processor 304 of the cloud computing server 30 calculates the total mass of dust particles or the total number of particles by adding together the values in each particle size class, for example for a given brush strip area or other partition of the floor that has been cleaned. After the adding module 310 performs the calculation, the resulting dust distribution data 316 is stored in the memory 316 of the cloud computing server 30.
[0130] Figures 6 to 11 The process can be performed one or more times during a single cleaning operation. After the cleaning operation is completed, the memory 306 of the cloud computing server 30 (or the memory 206 in the case where it is retained on the robotic vacuum cleaner) will store comprehensive dust distribution data 316, which represents the amount of dust in multiple particle size classes in each of multiple partitions of the building floor (in terms of dust particle mass or dust particle quantity), as well as data representing the total amount of dust in each of these partitions of the area. One of the main motivations of the present invention is to generate a dust distribution map based on the generated dust distribution data, which can then be displayed on the display component 104 of the client device 10.
[0131] To initiate the process, in response to user input received at the input receiving component 106 of the client device 10, the client device 10 may transmit a request for a dust distribution map to the cloud computing server 30 via the cloud computing server interface module 112 of the input device 10. The request may be sent to the cloud computing server 30 via an application on the client device 10. The request is then received at the cloud computing server 30 via the client device interface module 308. At this point, Figure 6 Step S606: Based on the dust particle distribution data 316 stored on the memory 306, the instruction generation module 312 of the processor 304 of the cloud computing server 30 generates instructions, which, when executed by the processor 108 of the client device 10, are configured to cause the display component 104 of the client device 10 to display the dust particle distribution map. Other details about the map features are given elsewhere in this application. In step S608, the generated instructions are transmitted to the client device 10, whereupon they are received via the cloud computing server interface module 112 and can be executed by the processor 108.
[0132] Figure 8C An example of a dust distribution map that can be generated based on dust distribution data generated according to, for example, the first aspect of the present invention is shown. In the dust distribution map, brighter areas are areas that contain more dust.
[0133] The remaining figures relate to the process of controlling the robotic vacuum cleaner 20 based on the generated dust distribution data. To initiate a cleaning operation, a user of the client device 10 may send a request to the robotic vacuum cleaner 20 through an application stored thereon. The request may be transmitted via the robotic vacuum cleaner interface module 102 of the client device 10 and the client device interface module 202 of the robotic vacuum cleaner 30. In response, the control module 212 of the processor 204 of the robotic vacuum cleaner 20 may generate a cleaning plan to be executed by the robotic vacuum cleaner. Fig.12 As shown, in order for the control module 212 to generate a cleaning plan, or plan a cleaning operation, the control module 212 of the processor 204 of the robot vacuum cleaner 20 can receive generated dust distribution data, such as data from the cloud computing server 30. Specifically, in response to a request for a cleaning operation, the robot vacuum cleaner 20 can transmit a request for generated dust distribution data 316 from the memory 306 of the cloud computing server 30 through the cloud computing server interface module 208. The request can be received at the cloud computing server 30 via the robot vacuum cleaner interface module 302. In response, the cloud computing server 30 can transmit the dust distribution data 316 from its memory to the robot vacuum cleaner 20 via the robot vacuum cleaner interface module 302. The control module 212 of the processor 204 of the robot vacuum cleaner 20 can then receive the dust distribution data 316 via the cloud computing server interface module 208. This is shown as Fig.12 Then, at step S1202, the control module 212 plans a cleaning operation based on the received dust distribution data 316. The planned cleaning operation 222 can then be stored in the memory 206 of the robot vacuum cleaner 20. More specifically, the cleaning route planning module 2124 of the control module 212 can determine the cleaning route, for example, by determining the order of various locations that the robot vacuum cleaner 20 should visit during the cleaning operation. Then, the operating parameter generation module 2122 can determine one or more suitable operating parameters to be used for each location. These two components can work together accordingly to form a cleaning plan.
[0134] In alternative embodiments, these steps may occur at different locations. For example, the planning operation may occur at a control module (not shown) of the cloud computing server 30 and then be transmitted to the robotic vacuum cleaner 20 for storage in the memory 206. This approach has the advantage of outsourcing potentially computationally demanding planning to a cloud computing server, thereby reducing the processing requirements of the processor 204 of the robotic vacuum cleaner 20.
[0135] As discussed elsewhere in this application, there are many operating parameters that can be changed during cleaning, including suction and the rotation speed of the brush bar. In addition, the cleaning plan 222 can also specify the order of various locations to be visited during cleaning. Fig.13 A schematic diagram of a room is shown containing predetermined areas 1 to 16. Of course, in reality, the clean area may be more complex than this, but this is for illustration purposes only. Fig.14 An example of a cleaning plan is shown which specifies that the robot vacuum cleaner 20 should first move along the left hand side of the room, passing through the zones with position IDs 1, 5, 9 and 13. For each zone, the plan specifies the motor power and brush bar speed. It should be understood that other operating parameters may also be defined in the plan. It should be emphasized that Fig.14 The layout shown in is a schematic representation, and the data may be stored in various forms. Fig.14 In the example above, the data is presented in a table for ease of understanding. It should be noted that the cleaning plan may also include other parameters, and Fig.14 The examples shown in should not be considered limiting.
[0136] Fig.15 An example of an alarm generation process is shown, in which trends in dust distribution data can be monitored, and an alarm can be generated in the event of an unexpected deviation being detected. Specifically, in a first step S1300, an alarm generation module 2126 of a control module 212 of a processor 204 of a robot vacuum cleaner 20 can receive recently generated dust distribution data. Alternatively, this step can be performed on a processor 108 of a client device 10 or a processor 304 of a cloud computing server 30. Then, in step S1302, a deviation between the received dust distribution data and an expected dust distribution can be determined by the same component as performing step S1300 or by another component. In step S1304, it is determined whether the deviation exceeds a predetermined deviation threshold, and if so, in step S1306, an alarm is generated. If not, the process ends.
[0137] The features disclosed in the preceding description, or in the following claims, or in the accompanying drawings, expressed in their specific form or as means for performing the disclosed functions, or as methods or processes for obtaining the disclosed results, may, where appropriate, be used alone or in any combination of these features to implement the invention in its different forms.
[0138] Although the present invention has been described in conjunction with the above exemplary embodiments, many equivalent modifications and variations will be apparent to those skilled in the art when this disclosure is given. Therefore, the above exemplary embodiments of the present invention are considered to be illustrative rather than restrictive. Various changes may be made to the described embodiments without departing from the spirit and scope of the present invention.
[0139] For the avoidance of any doubt, any theoretical explanations provided herein are intended to enhance the reader's understanding. The inventors do not wish to be bound by any of these theoretical explanations.
[0140] Any section headings used herein are for organizational purposes only and are not to be construed as limiting the subject matter described.
[0141] Throughout the specification, including the following claims, unless the context requires otherwise, the words "comprises" and "comprising" and variations will be understood to imply the inclusion of stated integers or steps or groups of integers or steps but not the exclusion of any other integers or steps or groups of integers or steps.
[0142] It must be noted that, as used in the specification and the appended claims, the singular forms "a", "an", and "the" include plural referents unless the context clearly dictates otherwise. Ranges may be expressed herein as from "about" one particular value, and / or to "about" another particular value. When such a range is expressed, another embodiment includes from the one particular value and / or to the other particular value. Similarly, when a value is expressed as an approximation by using the antecedent "about," it will be understood that the particular value forms another embodiment. The term "about" in relation to a numerical value is optional and means, for example, + / - 10%.
Claims
1. A computer-implemented method of controlling the operation of a robotic vacuum cleaner, the computer-implemented method comprising: receiving dust distribution data indicating a spatial distribution of dust particles on a floor of a building; and Based on the received dust distribution data, cleaning operations of the building floor to be performed by the robotic vacuum cleaner are planned.
2. The computer-implemented method of claim 1 , wherein: The building floor is divided into a plurality of zones or grid cells, and planning the cleaning operation includes generating data specifying which zones or grid cells the robotic vacuum cleaner is to traverse based on the received dust distribution data.
3. The computer-implemented method of claim 2, wherein: Planning a cleaning operation includes determining an order in which the robotic vacuum cleaner traverses zones or grid cells, the order of zones or grid cells being determined based on the received dust distribution data.
4. The computer-implemented method of claim 3, wherein: Planning the cleaning operation includes arranging the locations in order of dust amount and generating instructions that, when executed by a processor of the robotic vacuum cleaner, cause it to visit the locations in order of decreasing dust amount.
5. The computer-implemented method according to any one of claims 1 to 4, wherein: Planning a cleaning operation includes generating one or more operating parameters, the one or more operating parameters being generated based on the dust distribution data.
6. The computer-implemented method of claim 5, wherein: Generating one or more operating parameters includes: For each of a plurality of locations, zones, or grid cells on a building floor, generating a corresponding value of one or more operating parameters; and Values of operating parameters for each of a plurality of locations, zones, or grid cells on the building floor are generated based on dust distribution data associated with the respective locations.
7. A computer-implemented method according to claim 5 or 6, wherein: The one or more parameters include suction; and Based on the received dust distribution data, the suction intensity in a location, area or grid cell with a relatively high dust amount is selected to be higher than the suction intensity in a location, area or grid cell with a relatively low dust amount.
8. A computer-implemented method according to any one of claims 5 to 7, wherein: The one or more parameters include a rotation rate of a brush within a housing of the robotic vacuum cleaner.
9. A computer-implemented method according to any one of claims 5 to 8, wherein: The one or more parameters include a cleaning speed; and Based on the received dust distribution data, the cleaning speed in locations, areas or grid cells with relatively high dust amounts is selected to be lower than the cleaning speed in locations, areas or grid cells with relatively low dust amounts.
10. A computer-implemented method according to any one of claims 5 to 9, wherein: Planning a cleaning operation includes generating a cleaning plan comprising instructions that, when executed by a processor of the robotic vacuum cleaner, cause the robotic vacuum cleaner to perform a cleaning operation defined by the cleaning plan, the cleaning plan comprising an ordered list of locations, areas, or grid cells within a building floor, and for each location, area, or grid cell, one or more operating parameters to be used at that location, area, or grid cell.
11. A computer-implemented method according to any one of claims 5 to 10, wherein: The method includes planning a plurality of cleaning operations based on the received dust distribution data; The one or more operating parameters include a respective frequency at which the robotic vacuum cleaner cleans each location, each area, or each grid cell; and The frequency of locations, areas or grid cells having a relatively high dust amount is selected to be higher than the frequency of locations, areas or grid cells having a relatively low dust amount.
12. A robotic vacuum cleaner system comprising a processor configured to perform the computer-implemented method of any one of claims 1 to 11.
13. A computer-implemented method of controlling a robotic vacuum cleaner using a client device, the computer-implemented method comprising: receiving, by a client device, a dust distribution map indicating a distribution of dust particles on a floor of a building; displaying the dust distribution map on a display component of the client device; receiving a user input of a selected location corresponding to the dust map, the selected location being a location to be cleaned by the robotic vacuum cleaner; Instructions are generated based on the received user input, which, when executed by a processor of the robotic vacuum cleaner, are configured to cause the robotic vacuum cleaner to clean a location of the building floor corresponding to a selected location of the dust map.
14. The computer-implemented method of claim 13, wherein: Receiving user input includes receiving user input via a touch screen of the client device.
15. A computer implemented method for monitoring dust distribution on a building floor, the computer implemented method comprising: receiving dust distribution data indicating a distribution of dust particles on a floor of a building; comparing the dust distribution data to expected dust distribution data based on the stored dust distribution data to determine deviations between dust amounts in one or more regions of the received dust distribution data and corresponding regions in the stored dust distribution data; and If the deviation exceeds a predetermined threshold in one or more areas, an alert is generated.
