JP2025062382A - Vacuum cleaner management program and vacuum cleaner management system - Google Patents

Abstract

To grasp cleaning performance while suppressing complication of a configuration and increase in price.SOLUTION: A cleaner management system having a user terminal 1 used by a user of a stick type cleaner 2 with no communication function, which is attached to the terminal holder 20 of the stick type cleaner 2, and a cleaner management device 3 includes: a cleaner identification part 32 for determining whether the user terminal 1 is usable on the basis of identification information on the stick type cleaner 2; an operation status detection part 33 for detecting the operation status of the stick type cleaner 2 when the user terminal is determined to be usable by the cleaner identification part; a map information creation part 36 for creating map information 355 showing the state of cleaning using layout information 353 showing a region to be cleaned by the stick type cleaner 2, tracking information 354 showing the moving history of the stick type cleaner 2, and the operation status; and an output part for outputting the map information.SELECTED DRAWING: Figure 24

Description

The present invention relates to so-called home appliances, particularly vacuum cleaners, and information processing technology for managing them.

Currently, household appliances such as vacuum cleaners are used for housework. So-called IoT (Internet of Things) appliances have been proposed for these appliances. IoT appliances are connected to networks such as the Internet and provide various functions and services such as control of operation. For example, Patent Document 1 describes "a more convenient vacuum cleaner and vacuum cleaner management system by enabling operations that involve the performance of the vacuum cleaner." More specifically, it describes "a vacuum cleaner management system in which a mobile information terminal, a vacuum cleaner, and a center device are connected via the Internet, the vacuum cleaner is equipped with a sensor that measures the number of rotations and motor current of a motor controlled by a power converter, and a communication means for transmitting the sensor output to the Internet, and the center device inputs the number of rotations and motor current of the motor obtained from multiple vacuum cleaners and transmits information about the vacuum cleaner to the mobile information terminal" (abstract).

JP 2022-162696 A

Currently, many home appliances are in use that do not have communication functions. In other words, many home appliances other than IoT home appliances are in use. With such home appliances, there are some functions and services that are possible with IOT home appliances that cannot be enjoyed. In addition, IoT home appliances require functions such as communication functions, which may lead to more complex structures and higher prices. In particular, it is difficult to grasp the cleaning status, such as how much cleaning has been done. In particular, with manual vacuum cleaners, the cleaning status relies solely on the user's senses and memory, which lacks accuracy.

The present invention aims to make it possible to grasp cleaning performance while preventing the configuration from becoming too complicated and the price from increasing.

The present invention, which aims to solve the above problem, comprises a vacuum cleaner identification unit that is used by a user of a vacuum cleaner that does not have a communication function and that determines whether a user terminal, which is a computer attached to a terminal holder of the vacuum cleaner, is usable based on the identification information of the vacuum cleaner, an operation status detection unit that detects the operation status of the vacuum cleaner when the vacuum cleaner identification unit determines that the user terminal is usable, a map information creation unit that creates map information showing the cleaning status using layout information that indicates the area to be cleaned by the vacuum cleaner, tracking information that indicates the movement history of the vacuum cleaner, and the operation status, and a vacuum cleaner management program that functions as an output unit that outputs the map information.

The present invention also includes a vacuum cleaner management system that is used by a user of a vacuum cleaner that does not have a communication function and has a user terminal attached to a terminal holder of the vacuum cleaner and a vacuum cleaner management device, the vacuum cleaner management system having a vacuum cleaner identification unit that determines whether the user terminal is usable based on identification information of the vacuum cleaner, an operation status detection unit that detects the operation status of the vacuum cleaner when the vacuum cleaner identification unit determines that the user terminal is usable, a map information creation unit that creates map information showing the cleaning status using layout information that indicates the area to be cleaned by the vacuum cleaner, tracking information that indicates the movement history of the vacuum cleaner, and the operation status, and an output unit that outputs the map information.

Furthermore, the present invention also includes a vacuum cleaner management method using the above-mentioned vacuum cleaner management program, vacuum cleaner management system, and each of the devices and subsystems that constitute the system.

The present invention makes it possible to provide various functions and services using information processing technology for home appliances, particularly vacuum cleaners, while preventing the configuration from becoming too complicated and the price from rising.

1 is a perspective view showing a state in which a stick vacuum cleaner according to an embodiment of the present invention is stored in a charging stand in a stick state. FIG. 1 is a diagram showing a state in which a user terminal 1 is installed on a stick vacuum cleaner 2 in one embodiment of the present invention. FIG. 2 is a functional block diagram of a user terminal 1 according to the first embodiment. FIG. 2 is a hardware configuration diagram of a user terminal 1 according to the first embodiment. FIG. 11 is a diagram showing user management information 191 used in the first embodiment. FIG. 11 is a diagram showing cleaner management information 192 used in the first embodiment. 10 is a flowchart showing a cleaning area presentation process flow in the first embodiment. FIG. 13 is a diagram showing a display screen of AR information in the first embodiment. FIG. 11 is a system configuration diagram of a vacuum cleaner management system in a second embodiment. FIG. 11 is a hardware configuration diagram of a cleaner management device 3 in a second embodiment. FIG. 11 is a diagram showing user management information 351 used in the second embodiment. FIG. 11 is a diagram showing cleaner management information 352 used in the second embodiment. 13 is a flowchart (part 1) showing a cleaning area presentation process flow in the second embodiment. 13 is a flowchart (part 2) showing the cleaning area presentation process flow in the second embodiment. 13 is a diagram showing a side view of a stick vacuum cleaner 2 with a terminal holder 20 attached thereto in a third embodiment. FIG. 14 showing a state in which the terminal holder 20 in the third embodiment is attached. FIG. 13A to 13C are diagrams illustrating a first example of a mounting portion 200 according to a third embodiment. 13A and 13B are diagrams illustrating a second example of the mounting portion 200 in the third embodiment. FIG. 13 is a functional block diagram of a user terminal 1 according to a fourth embodiment. FIG. 13 is a hardware configuration diagram of a user terminal 1 in a fourth embodiment. FIG. 19 is a diagram showing layout information 193 used in the fourth embodiment. FIG. 19 is a diagram showing tracking information 194 used in the fourth embodiment. 13 is a flowchart showing a process flow for presenting map information in the fourth embodiment. FIG. 13 is a diagram showing a first example of map information 195 used in the fourth embodiment. FIG. 13 is a diagram showing a second example of the map information 195 used in the fourth embodiment. FIG. 13 is a system configuration diagram of a vacuum cleaner management system in a fifth embodiment. FIG. 13 is a hardware configuration diagram of a cleaner management device 3 in a fifth embodiment. FIG. 13 is a diagram showing layout information 353 used in the fifth embodiment. FIG. 13 is a diagram showing tracking information 354 used in the fifth embodiment. 19 is a flowchart (part 1) showing a process flow for presenting map information in the fifth embodiment. 23 is a flowchart (part 2) showing the map information presentation process flow in the fifth embodiment.

One embodiment of the present invention will be described below. In this embodiment, a vacuum cleaner will be used as an example of a home appliance. In particular, a stick vacuum cleaner will be used as an example of a manual vacuum cleaner operated by a user. Furthermore, the stick vacuum cleaner of this embodiment does not have a communication function with other devices such as a smartphone or a router. A configuration for realizing a management function related to such a stick vacuum cleaner will be described below.

Figure 1 is a perspective view showing a stick vacuum cleaner 2 according to this embodiment in a stick state stored in a charging stand 26. Here, the stick vacuum cleaner 2 is configured to include a vacuum cleaner body 21, a handle 22, an extension tube 23, and a vacuum cleaner head 24. The vacuum cleaner body 21 and the vacuum cleaner head 24 are connected via the extension tube 23.

The vacuum cleaner body 21 is provided with a handle 22 that is held by the user. A terminal holder 20 is provided below the handle 22 on the vacuum cleaner body 21. This terminal holder 20 holds a user terminal 1 such as a smartphone, and may be configured to be separable from the vacuum cleaner body 21, or may be configured as an integral part. In this embodiment, at least a part of the vacuum cleaner management function is executed by the user terminal 1 held in the terminal holder 20. This function (processing flow) will be described in each embodiment.

The stick vacuum cleaner 2 can be changed into various states for cleaning, such as a handheld state or a stick state. The charging stand 26 in which the stick vacuum cleaner 2 is stored stores the stick vacuum cleaner 2 in a stick state, and is configured with a base member 29, three stand members 28, and a holder member 27. This charging stand 26 can charge the stick vacuum cleaner 2.

The cleaner head 24, which faces the cleaning surface such as the floor, is provided with a sign section 25 such as an AR marker or a nameplate. Identification information for identifying the stick vacuum cleaner 2 is recorded on this sign section 25. Note that the identification information may be information for identifying the individual stick vacuum cleaner 2, or information for identifying the type, such as the model. An image is then captured by the user terminal 1 held in the terminal holder 20, and the identification information is read. The process is described below.

Figure 2 is a diagram showing the user terminal 1 installed on the stick vacuum cleaner 2 in this embodiment. In this embodiment, as shown in Figure 2, the user terminal 1 is held in a terminal holder 20 connected to the vacuum cleaner body 21. At this time, the user terminal 1 is held in the terminal holder 20 so that it faces the vacuum cleaner head 24 and the camera can capture an image of the sign section 25. It is preferable that the orientation of the terminal holder 20 is variable and that the direction in which the user terminal 1 faces can also be changed accordingly. Furthermore, the camera of the user terminal 1 captures an image of the floor surface to be cleaned by the stick vacuum cleaner 2.

In this embodiment, the vacuum cleaner management function is executed on the condition that an identification process is performed using the identification information of the sign unit 25 photographed by the user terminal 1. Here, in this embodiment, as the vacuum cleaner management function, a process of presenting the cleaning area cleaned by the stick vacuum cleaner 2 is executed. In the following Examples 1 and 2, which are specific examples of this embodiment, the details of this cleaning area presentation process are explained. Furthermore, in Example 3, the structure of the terminal holder 20 is explained in detail. Furthermore, in Examples 4 and 5, examples of creating map information are explained. Note that it is possible to combine at least two of each example.

Example 1 is an example in which the cleaning area presentation process is executed by the user terminal 1 alone. FIG. 3 is a functional block diagram of the user terminal 1 in Example 1. The user terminal 1 has a communication unit 11, an image capture unit 12, a sound collection unit 13, a vacuum cleaner identification unit 14, an operation status detection unit 15, an AR information creation unit 16, an input unit 17, an output unit 18, and a memory unit 19.

First, the communication unit 11 has a function of communicating via a router or a network and a function of short-distance wireless communication. The photographing unit 12 is realized by a camera or the like and acquires surrounding images. The sound collection unit 13 is realized by a microphone or the like and acquires surrounding sounds.

The vacuum cleaner identification unit 14 also uses the image captured by the image capture unit 12 to identify the stick vacuum cleaner 2. In Examples 1 and 2, the image of the sign unit 25 captured by the image capture unit 12 is used to identify the identification information recorded in the sign unit 25, and this is used to perform identification. Note that an AR (Augmented Reality) marker, a two-dimensional code, or a nameplate can be used as the sign unit 25. Here, the identification information is recorded on the nameplate in a visible format.

Alternatively, the label unit 25 may be omitted, and the stick vacuum cleaner 2 may be identified using the shape of the vacuum cleaner head 24 photographed by the photographing unit 12. When the shape of the vacuum cleaner head 24 is used, the vacuum cleaner identification unit 14 will identify the type of stick vacuum cleaner 2. Furthermore, an RFID (Radio Frequency Identification) tag on which identification information is recorded may be used as the label unit 25. In this case, an RFID reader is provided in the user terminal 1, which reads the identification information.

The operation status detection unit 15 detects the operation status of the stick vacuum cleaner 2, such as identifying the cleaning area, using the image of the floor surface captured by the image capture unit 12. The AR information creation unit 16 creates AR information using the image of the floor surface captured by the image capture unit 12 and the cleaning area identified by the operation status detection unit 15. Here, the AR information is information created using augmented reality technology. The AR information indicates the cleaning area, and is an example of provided information provided to related parties including the user. For this reason, the provided information is not limited to AR information, but may be a captured image (including still images and videos), an animation indicating the cleaning area, or the cleaning area may be indicated in text.

The input unit 17 also accepts various operations from the user. The output unit 18 also outputs AR information and the like. The input unit 17 and the output unit 18 may be integrated into one unit, such as a touch panel. The storage unit 19 also stores user management information 191 and vacuum cleaner management information 192. These pieces of information will be explained after the implementation example of the user terminal 1.

Next, an implementation example of the user terminal 1 will be described. The user terminal 1 can be realized by various computers such as a smartphone, tablet, mobile phone, or PC. FIG. 4 is a hardware configuration diagram of the user terminal 1 in the first embodiment. In FIG. 4, the user terminal 1 has a camera 101, a microphone 102, a touch panel 103, a processing device 104, a communication device 105, and a storage device 106, which are connected to each other via a communication path.

First, the camera 101 is an example of the implementation of the imaging unit 12, and has an imaging function. The microphone 102 is an example of the implementation of the sound collection unit 13, and has a sound collection function. The touch panel 103 is configured to serve both as the input unit 17 and the output unit 18 in FIG. 3, and accepts operations from the user and displays various information such as AR information. Note that the touch panel 103 may be configured as a separate input device and an output device.

The processing device 104 can be realized by a processor such as a CPU (Central Processing Unit), and performs calculations according to a vacuum cleaner management program 107 stored in the storage device 106, which will be described later.

The vacuum cleaner management program 107 is composed of a vacuum cleaner identification module 108, an operation status detection module 109, and an AR information creation module 110 for each of its functions. Each of these modules may be realized as an individual program or a partial combination. In particular, the AR information creation module 110 may be realized as a program with an augmented reality function separate from home appliance management. Furthermore, the vacuum cleaner management program 107 may be realized as one function of an integrated management application that manages multiple home appliances.

Here, the configuration shown in FIG. 3, which executes the same functions as each module, is as follows.
Vacuum cleaner identification module 108: Vacuum cleaner identification unit 14
Operation status detection module 109: Operation status detection unit 15
AR information creation module 110: AR information creation unit 16
Therefore, the processing device 104 executes the processes of the vacuum cleaner identification unit 14, the operation status detection unit 15, and the AR information creation unit 16 in accordance with the vacuum cleaner management program 107. The vacuum cleaner management program 107 can be stored in the storage device 106 (to be described later) or other storage media.

The communication device 105 corresponds to the communication unit 11 in FIG. 3 and has a function of communicating via a router or a network and a short-range wireless communication. The storage device 106 corresponds to the storage unit 19 in FIG. 3 and stores the above-mentioned vacuum cleaner management program 107, user management information 191, and vacuum cleaner management information 192. Therefore, the storage device 106 may be realized by a main storage device such as a memory and a secondary storage device (storage medium) that is a so-called storage. The secondary storage device may be realized by an external HDD (Hard Disk Drive), SSD (Solid State Drive), memory card, etc.

Here, the user management information 191 and the vacuum cleaner management information 192 will be described. FIG. 5 is a diagram showing the user management information 191 used in the first embodiment. The user management information 191 is information about the user of the user terminal 1. For this reason, as shown in FIG. 5, the user management information 191 has the following items: user, address, contact information, and owned vacuum cleaner. Here, the user is information that identifies the user, such as the name and membership number of the user. The address indicates the address of the user. The contact information indicates the contact information of the user, and can be a telephone number or an email address. The owned vacuum cleaner is information that identifies the home appliance used by the user, that is, the vacuum cleaner. Here, the user management information 191 can be used to manage and authenticate users in the vacuum cleaner management program 107. Note that the user management information 191 may be omitted.

FIG. 6 is a diagram showing the vacuum cleaner management information 192 used in the first embodiment. The vacuum cleaner management information 192 is information for managing the stick vacuum cleaner 2, which is a home appliance used by the user. Therefore, as shown in FIG. 6, the vacuum cleaner management information 192 has the following fields: vacuum cleaner, vacuum cleaner ID, related party, date and time, AR information, and cleaning history (cleaned area).

Here, the vacuum cleaner indicates the type of vacuum cleaner that is the object of management, i.e., the target of the cleaning area presentation process. In the first embodiment, a stick vacuum cleaner 2 is recorded. Note that, if there are multiple targets of the cleaning area presentation process, there will be multiple records in the vacuum cleaner management information 192.

The cleaner ID is identification information for identifying the relevant cleaner. This cleaner ID is information equivalent to the identification information recorded in the marker unit 25. The related parties indicate the related parties at the end of the cleaning area. Typical examples of related parties include the user of the user terminal 1 (A in the figure), as well as their family members and cohabitants. If a commercial vacuum cleaner is used as the target vacuum cleaner, the user's colleagues, managers, customers, etc. can be registered. However, these related parties are merely examples, and any person can be registered by the user's operation, etc. Furthermore, it is desirable to distinguish the user from other related parties. This distinction makes it possible to make a judgment in step S9 in the processing flow (Figure 7) described later. This distinction may be made by providing a user item, or by comparing the user management information 191 with the vacuum cleaner management information 192.

The date and time indicates the date and time when cleaning was performed or the date and time when the AR information was created. The AR information indicates a log of the AR information created by the AR information creation unit 16. The cleaning history (cleaned area) indicates the area that has been cleaned with the corresponding stick vacuum cleaner 2 based on the AR information. Therefore, the cleaning history (cleaned area) has the items of coordinates and room. Here, the coordinates are coordinates that indicate the area cleaned by the stick vacuum cleaner 2, that is, the trajectory of movement. Furthermore, the room indicates a room that has been cleaned (or has not been cleaned) according to the coordinates. Note that the cleaning history (cleaned area) can be omitted.

Next, the cleaning area presentation process in Example 1 will be described. FIG. 7 is a flowchart showing the cleaning area presentation process flow in Example 1. Below, the configuration of the user terminal 1 will be described using the configuration shown in FIG. 3.

First, in step S1, the input unit 17 accepts input from the user and activates the configuration for the presentation process. For example, the vacuum cleaner management program 107 in FIG. 4 is activated. At this time, the user places the user terminal 1 in the terminal holder 20. As a result, the terminal holder 20 holds the user terminal 1, and the user terminal 1 faces downward (toward the vacuum cleaner head 24) of the stick vacuum cleaner 2, making it possible to capture images in this direction.

In step S2, the image capturing unit 12 starts capturing images. This capturing is started in response to an instruction from the user, which can be started by an operation on the input unit 17 or a voice instruction picked up by the sound collection unit 13. The sound collection unit 13 may also collect sounds generated when the stick vacuum cleaner 2 is in operation, and the image capturing unit 12 may start capturing images based on the collected sounds.

In addition, in step S3, the vacuum cleaner identification unit 14 uses the captured image to recognize the identification information recorded on the sign unit 25. Here, if a nameplate is used as the sign unit 25, character recognition technology is used to recognize the identification information written in a visible form. If an AR marker or two-dimensional code is used, well-known technology is used to identify the identification information.

In the first embodiment, it is also possible not to use the label unit 25. In this case, in step S3, the cleaner identification unit 14 identifies the shape of the cleaner head 24 contained in the captured image, and identifies identification information for identifying the stick vacuum cleaner 2 based on the shape. In this case, the identification information identifies the type of the stick vacuum cleaner 2, such as the model number.

In addition, in step S4, the cleaner identification unit 14 determines whether the user terminal 1 held in the terminal holder 20 is usable, that is, whether the cleaning area presentation process in this flowchart is possible. For this purpose, the cleaner identification unit 14 determines whether the cleaner ID corresponding to the recognized identification information is recorded in the cleaner management information 192. As a result, if it is recorded, that is, if it is usable, the process proceeds to step S5. If it is not recorded and it is not usable, the process ends. At this time, it is desirable for the output unit 18 to display that it is not usable. Thus, in step S4, an identification process using the identification information is performed. Note that if the user terminal 1 is installed in the terminal holder 20, the indicator unit 25 can be accurately photographed. For this reason, step S4 also has the significance of the cleaner identification unit 14 determining that the user terminal 1 is correctly attached to the terminal holder 20.

In addition, in step S5, the vacuum cleaner identification unit 14 identifies related parties corresponding to the vacuum cleaner ID identified in step S4 from the vacuum cleaner management information 192. In addition, in step S6, the vacuum cleaner identification unit 14 accepts a selection of the recipient of the AR information (described below) via the input unit 17 and the sound collection unit 13. For this purpose, the vacuum cleaner identification unit 14 displays the related parties identified in step S5 via the output unit 18. Note that the related parties may be output as audio via an audio output unit such as a speaker.

In addition, in step S7, the operation status detection unit 15 detects the operation status of the stick vacuum cleaner 2, such as identifying the cleaning area, using the image of the floor surface captured by the image capture unit 12. More specifically, it identifies the trajectory of the movement of the vacuum cleaner head 24.

In step S8, the AR information creation unit 16 creates AR information by superimposing the operation status detected by the operation status detection unit 15 on the image showing the cleaning area, which is the floor surface photographed by the photographing unit 12. Here, the created AR information will be described using its display screen. FIG. 8 is a diagram showing the display screen of the AR information in the first embodiment. In FIG. 8, the AR information is displayed on the output unit 18 of the user terminal 1. Then, the trajectory 182 of the vacuum cleaner head 24 is superimposed on the photographed image (floor surface 181). Here, the shading of the trajectory 182 indicates the frequency of movement. In other words, the darker the area, the more cleaning has been done. Also, in FIG. 8, the cleaning performance (cleaned area) 183, that is, the date and time, cleaning time, and coordinates are displayed as the operation status. Here, the date and time indicates the current date and time when cleaning is being performed. The cleaning time is the time since the stick vacuum cleaner 2 started cleaning. Furthermore, the coordinates and the location indicating the location are specified according to a position detection unit such as a gyro of the user terminal 1, and these are also displayed.

Furthermore, in FIG. 8, the user identification information 184 indicates the user (A) of the user terminal 1. Note that the cleaning history (cleaned area) 183 and the user identification information 184 may be omitted. In particular, the user identification information 184 may not be displayed on the user terminal 1 of the user (A), but may be displayed on another user terminal. This concludes the explanation of the AR information, and we will return to FIG. 7 to continue the explanation of the processing flow.

In step S9, the AR information creation unit 16 determines whether the recipients accepted in step S6 are only the user or include non-users. If the recipients include non-users, the process proceeds to step S10. If the recipients are only the user, the process proceeds to step S11.

In addition, in step S10, the AR information creation unit 16 notifies the user terminal of the other user of the created AR information using the communication unit 11. At this time, it is desirable that the cleaning history (cleaned area) 183 and user identification information 184 described in FIG. 8 are also notified. As a result, the display screen shown in FIG. 8 is displayed on the user terminal of the other user. Therefore, the other users can share the cleaning history with the stick vacuum cleaner 2 with the user. This sharing may be realized in real time, or may be shared with a time lag or only the results. The details of these will be described later in Example 2. In addition, in step S11, the AR information creation unit 16 displays the display screen shown in FIG. 8 on the output unit 18.

In step S12, the AR information creation unit 16 determines whether cleaning with the stick vacuum cleaner 2 has finished. At this time, the end can be determined by an operation from the user on the input unit 17 or a voice instruction to be picked up by the sound collection unit 13. Furthermore, the AR information creation unit 16 may also determine that the sound of the stick vacuum cleaner 2 being operated and picked up by the sound collection unit 13 has stopped. As a result, if cleaning has finished, the process transitions to step S13. In addition, if cleaning is continuing, the creation of AR information in step S8 continues. Therefore, the image capture unit 12 continues to capture images, and the operation status detection unit 15 continues to detect the operation status.

Then, in step S13, the AR information creation unit 16 updates the vacuum cleaner management information 192 by recording the created AR information and the cleaning record (cleaned area) indicating the operation status. Furthermore, it is preferable that the AR information creation unit 16 stop the notification in step S10 and the display in step S11.

This concludes the explanation of Example 1. According to Example 1, it is possible to provide a cleaning area presentation process even for a vacuum cleaner that does not have a communication function, and as a result, the user and other related parties can understand the cleaning status. However, in Example 1, the cleaning area may be presented to a limited number of people, such as the user. In this case, steps S6, S9, and S10 are omitted. Furthermore, the cleaning area may be presented to fixed related parties. In this case, step S9 is omitted, and a transition is made from step S8 to step S10.

In Example 1, the cleaning area presentation process is performed by the user terminal 1 alone, but in Example 2, it is linked to a vacuum cleaner management device 3 realized by a server or the like. FIG. 9 is a system configuration diagram of the vacuum cleaner management system in Example 2. In FIG. 9, the vacuum cleaner management system has a user terminal 1 held by the terminal holder 20 of a stick vacuum cleaner 2, and a vacuum cleaner management device 3, which are connected via a network 5. In this case, the user terminal 1 may be connected to the network 5 via a router 4, or may be connected via another device, or may be connected directly to the network 5.

In addition, in the second embodiment, among the functions of the user terminal 1 described in the first embodiment, the functions and configurations executed by the vacuum cleaner management device 3 can be omitted. For example, at least one of the vacuum cleaner identification unit 14, the operation status detection unit 15, and the AR information creation unit 16 can be omitted.

The user terminal 1 and the vacuum cleaner management device 3 are connected to the user terminal 1-a and the user terminal 1-b used by the relevant parties described in Example 1 via the router 4 and the network 5. In FIG. 9, the user terminal 1-a is located in the same house as the user terminal 1, and is connected to the user terminal 1 and the vacuum cleaner management device 3 via the router 4. The user terminal 1-b is located in a different place (outside the house) from the user terminal 1, and is directly connected to the network 5. The user terminal 1 and the stick vacuum cleaner 2 are the same as those in Example 1. The user terminal 1-a and the user terminal 1-b may have the same functions as the user terminal 1, or may be configured to omit the vacuum cleaner identification unit 14 to the AR information creation unit 16.

Next, the vacuum cleaner management device 3, which is a characteristic configuration of the second embodiment, will be described. The vacuum cleaner management device 3 is used by manufacturers and distributors of stick vacuum cleaners 2, and these distributors manage users as members. Next, the configuration of the vacuum cleaner management device 3 will be described.

First, the functional blocks of the vacuum cleaner management device 3 will be described with reference to FIG. 9. The vacuum cleaner management device 3 has a communication unit 31, a vacuum cleaner identification unit 32, an operation status detection unit 33, an AR information creation unit 34, and a memory unit 35. First, the communication unit 31 connects to each user terminal via the network 5.

The cleaner identification unit 32, the operation status detection unit 33, and the AR information creation unit 34 execute the same processes as the cleaner identification unit 14, the operation status detection unit 15, and the AR information creation unit 16 of the first embodiment. The memory unit 35 stores user management information 351 and cleaner management information 352. Each of these pieces of information will be described later.

Next, a hardware configuration of one implementation example of the vacuum cleaner management device 3 will be described. The vacuum cleaner management device 3 can be realized by a computer such as a server or a cloud system. FIG. 10 is a hardware configuration diagram of the vacuum cleaner management device 3 in Example 2. In FIG. 10, the vacuum cleaner management device 3 has a processing device 301, a communication device 302, a memory 303, and a secondary storage device 304, which are connected to each other via a communication path.

First, the processing device 301 can be realized by a processor such as a CPU, and executes calculations according to a vacuum cleaner management program 305 stored in a secondary storage device 304 described below. The communication device 302 corresponds to the communication unit 31 in FIG. 9, connects to the network 5, and communicates with other devices such as the user terminal 1.

The memory 303 and the secondary storage device 304 correspond to the storage unit 35 in FIG. 9. The memory 303 expands the vacuum cleaner management program 305 stored in the secondary storage device 304 and information used for processing by the processing device 301. The secondary storage device 304 can be realized as a so-called storage device. The secondary storage device 304 stores the vacuum cleaner management program 305, user management information 351, and vacuum cleaner management information 352. The secondary storage device 304 may be realized as various storage media such as an external HDD (Hard Disk Drive), SSD (Solid State Drive), or memory card, or may be realized as a device separate from the vacuum cleaner management device 3, such as a file server.

The vacuum cleaner management program 305 is composed of a vacuum cleaner identification module 306, an operating status detection module 307, and an AR information creation module 308 for each of its functions. Each of these modules may be realized as an individual program or a partial combination. In particular, the AR information creation module 308 may be realized as a program with an augmented reality function separate from home appliance management. Furthermore, the vacuum cleaner management program 305 may be realized as one function of an integrated management application that manages multiple home appliances.

Here, the configuration shown in FIG. 9, which executes the same functions as each module, is as follows.
Vacuum cleaner identification module 306: Vacuum cleaner identification unit 32
Operation status detection module 307: operation status detection unit 33
AR information creation module 308: AR information creation unit 34
Therefore, the processing device 301 executes the processes of the cleaner identification unit 32 , the operating status detection unit 33 , and the AR information creation unit 34 in accordance with the cleaner management program 305 .

Here, the vacuum cleaner management program 305 executes the same processing as the vacuum cleaner management program 107 of the user terminal 1. The vacuum cleaner management program 305 can be stored in the secondary storage device 304 or other storage media.

Next, user management information 351 and vacuum cleaner management information 352 will be described. Figure 11 is a diagram showing user management information 351 used in Example 2. Like user management information 191, user management information 351 is information about the user of user terminal 1. Therefore, like user management information 191, user management information 351 has the fields for user, address, contact information, and owned vacuum cleaner. However, user management information 351 targets multiple users, such as members. Therefore, user management information 351 will contain records for each target user.

FIG. 12 is a diagram showing the vacuum cleaner management information 352 used in the second embodiment. Like the vacuum cleaner management information 352, the vacuum cleaner management information 352 is information for managing a home appliance used by a user, for example, a stick vacuum cleaner 2. For this reason, like the vacuum cleaner management information 192, the vacuum cleaner management information 352 has the following fields: vacuum cleaner, vacuum cleaner ID, related party, date and time, AR information, and cleaning history (cleaned area).

However, the vacuum cleaner management information 352 targets multiple users, such as members. Therefore, the vacuum cleaner management information 352 will contain records for each vacuum cleaner of the target user. As with the first embodiment, it is desirable to distinguish users from other related parties. By using the related party field, it becomes possible to identify the related party in step S20 of the processing flow (FIG. 13A) described below. This distinction may be made by providing a user field, or by comparing the user management information 351 with the vacuum cleaner management information 352.

Next, the cleaning area presentation process in Example 2 will be described. Figures 13A and 13B are flowcharts showing the cleaning area presentation process flow in Example 2. Below, the configuration of the user terminal 1 will be described using the configuration shown in Figure 3, and the configuration of the vacuum cleaner management device 3 will be described using the configuration shown in Figure 9.

First, in steps S1 and S2, the user terminal 1 executes the same processing as in Example 1. In addition, in step S14, the communication unit 11 of the user terminal 1 notifies the vacuum cleaner management device 3 of the image captured in step S2. In response, in step S15, the communication unit 31 of the vacuum cleaner management device 3 accepts the image.

Then, in step S16, the cleaner identification unit 32 uses the received image to recognize the identification information recorded in the sign unit 25. This process is executed in the same manner as step S3 in the first embodiment. In addition, in step S17, the cleaner identification unit 32 determines whether the user terminal 1 held by the terminal holder 20 is usable, that is, whether the cleaning area presentation process in this flowchart is possible. In other words, the same process as step S4 in the first embodiment is executed. However, in step S17, the cleaner management information 352 is used instead of the cleaner management information 192. As a result, if it is recorded, that is, if it is usable, the process transitions to step S20. If it is not recorded and therefore cannot be used, the process transitions to step S18.

In addition, in step S18, the vacuum cleaner identification unit 32 notifies the user terminal 1 via the communication unit 31 that the vacuum cleaner cannot be used. Then, in step S19, the communication unit 11 of the user terminal 1 accepts the notification of step S18 and displays information that the vacuum cleaner cannot be used on the output unit 18. As a result, this flowchart ends.

In addition, in step S20, the cleaner identification unit 32 identifies the related parties corresponding to the cleaner ID identified in step S16 from the cleaner management information 352. This step can be achieved by processing similar to that of step S5, but it is preferable to exclude the user from the related parties.

In addition, in step S21, the vacuum cleaner identification unit 32 notifies the user terminal 1 via the communication unit 31 of the related parties identified in step S20. Then, in step S22, the communication unit 11 of the user terminal 1 accepts the related parties, and the output unit 18 displays them. At this time, the output unit 18 displays a message prompting the user to select the related parties to whom the information will be provided. Then, in step S23, the input unit 17 and the sound collection unit 13 accept the user's selection of the displayed related parties, that is, the selection of the recipient. As a result, in step S24, the communication unit 11 notifies the vacuum cleaner management device 3 of the selected notification destination.

Note that steps S20 to S24 may be executed as follows. The vacuum cleaner identification unit 32 identifies related parties, including the user, in step S20, and notifies related parties, including the user, via the communication unit 31 in step S21. In this case, in step S22, the user is displayed as a required user and cannot be removed from the selection.

Then, in step S25, the vacuum cleaner management device 3 accepts the destination notified in step S24. Next, moving to FIG. 13B, in step S26, the operation status detection unit 33 detects the operation status of the stick vacuum cleaner 2, such as identifying the cleaning area, using the image of the floor surface captured by the imaging unit 12. In other words, the same process as in step S7 is executed. Note that this step may be executed by the operation status detection unit 15 of the user terminal 1, which notifies the vacuum cleaner management device 3 of the operation status via the communication unit 11.

In addition, in step S27, the AR information creation unit 34 creates AR information by superimposing the operation status detected by the operation status detection unit 33 or the operation status detection unit 15 on the image captured by the imaging unit 12. In other words, the same process as in step S8 is executed. Then, in step S28, the AR information creation unit 34 notifies the created AR information to the destination user terminals, including the user terminal 1, using the communication unit 31. This destination is the destination user terminal accepted in step S25 and the user terminal 1 of the user. For example, the AR information is notified to the user terminal 1-a and user terminal 1-b in FIG. 9.

In step S29, the AR information notified by the communication unit 11 of the user terminal 1 is accepted and displayed on the output unit 18. This process is the same as in Example 1, and is also executed in user terminals of recipients other than the user terminal 1. Note that notification and display of the AR information to user terminals of recipients other than the user terminal 1 may be performed in a manner different from that of the user terminal 1. This will be described later after the explanation of this flowchart. Display on terminals other than the user terminal 1 is terminated by an operation of the relevant user.

In addition, in step S30, the user terminal 1 determines whether cleaning with the stick vacuum cleaner 2 has finished. This is performed in the same way as step S12 in the first embodiment, but may be performed by the vacuum cleaner identification unit 14, the operation status detection unit 15, or the AR information creation unit 16, or may be performed by other configurations. As a result, if cleaning has finished, the process transitions to step S31. In addition, if cleaning is continuing, the process of displaying AR information continues. In this case, the user terminal 1 also continues the processes of steps S2 and S14.

In addition, in step S31, the communication unit 11 sends an end notification to the vacuum cleaner management device 3 indicating that cleaning has ended. Then, the display process in the output unit 18 ends. At this time, the processes in steps S2 and S14 also end.

In addition, in step S32, the communication unit 31 of the vacuum cleaner management device 3 receives a termination notification, and in response, the AR information creation unit 34 terminates the creation of the AR information. Then, in step S33, the AR information creation unit 34 updates the vacuum cleaner management information 352 by recording the created AR information and the cleaning history (cleaned areas) indicating the operating status.

Furthermore, in step S34, the AR information creation unit 34 uses the communication unit 31 to notify the end notification to other user terminals of the provision destination other than the user terminal 1. As a result, the display process on the other user terminals ends. This concludes the explanation of this flowchart, but we will now explain the notification and display (alternative aspects) of the AR information to user terminals of the provision destination other than the user terminal 1.

Here, the destinations are user terminal 1-a and user terminal 1-b in Figure 9. As described above, user terminal 1-a is located in the same home as user terminal 1, and is connected to user terminal 1 and vacuum cleaner management device 3 via router 4. User terminal 1-b is located in a different location (outside the home) from user terminal 1, and is directly connected to network 5.

First, the user terminal 1-a inside the home is notified and displayed appropriately each time AR information is created, just like the user terminal 1. So-called real-time processing is executed. In addition, when cleaning is completed, information indicating the results is notified and displayed to the user terminal 1-b outside the home.

This concludes the explanation of the second embodiment. According to the second embodiment, even for a vacuum cleaner that does not have a communication function, the process of presenting the cleaning area is realized in cooperation with the vacuum cleaner management device 3 such as a server. This allows appropriate resources to be utilized, and efficient processing can be realized.

Next, a third embodiment of the structure of the terminal holder 20 will be described. FIG. 14 is a schematic side view of the stick vacuum cleaner 2 of the third embodiment when the terminal holder 20 is attached to the stick vacuum cleaner 2. As described in FIG. 1, the stick vacuum cleaner 2 has a vacuum cleaner body 21 and a vacuum cleaner head 24, which are connected via an extension tube 23. The vacuum cleaner body 21 is provided with a handle 22 that is held by the user. The lower part of the vacuum cleaner body 21 has a tubular or annular connection part 211 for connecting to the extension tube 23. The stick vacuum cleaner 2 of the third embodiment has a communication function and other information processing functions, and may be linked to a user terminal 1, a vacuum cleaner management device 3, etc.

Here, the terminal holder 20 is installed so as to be detachable to the vacuum cleaner body 21, more preferably to the connection part 211. For example, the terminal holder 20 is configured in a ring or tube shape, and is fixed via an adapter or the like that wraps around the connection part 211. The terminal holder 20 may be attached to something other than the extension tube 23 or the connection part 211. Furthermore, when the extension tube 23 of the stick type vacuum cleaner 2 is removed and a separate nozzle (tube) is provided for replacement, the terminal holder 20 may be connected to the nozzle. The separate nozzle is a nozzle that is shorter than the extension tube 23, and includes a brush nozzle and a tapered nozzle. It is also preferable that the separate nozzle has a cableless structure in which a cable for controlling the vacuum cleaner head 24 is omitted.

Next, FIG. 15 is an enlarged view of FIG. 14 showing the state in which the terminal holder 20 in Example 3 is attached. In FIG. 15, the terminal holder 20 is fixed to the connection part 211 via the attachment part 200. At this time, it is desirable to position the holding part 20-1 of the terminal holder 20 so that it is approximately 100° from the direction of the connection part 211 and the extension tube 23. However, this angle can be fine-tuned by moving the holding part 20-1 or the arm part 20-2 described below. This allows the image capture part 12 of the user terminal 1 to capture an image of the vacuum cleaner head 24 and the floor surface to be cleaned.

Here, the terminal holder 20 has at least a holding part 20-1, an arm part 20-2, and a base 20-3, and is attached to the stick vacuum cleaner 2. This attachment is preferably performed via the attachment part 200 of the terminal holder 20.

First, the holding unit 20-1 holds the user terminal 1 in a fixed manner, for example by clamping it. The base 20-3 and the mounting unit 200 are connected, and the terminal holder 20 is fixedly attached to the stick vacuum cleaner 2. The arm unit 20-2 connects the holding unit 20-1 and the base 20-3. In the third embodiment, the base 20-3 or the terminal holder 20 and the mounting unit 200 are configured separately. However, these may be configured as an integrated unit, or may be configured as an integrated unit or separable unit. In other words, the terminal holder 20 in the third embodiment may be configured with the holding unit 20-1, the arm unit 20-2, and the base 20-3, or may be configured with the mounting unit 200 added to these. This allows the terminal holder 20 to be shared by multiple vacuum cleaners, particularly vacuum cleaners with different specifications such as size. As described above, in the third embodiment, the terminal holder 20 having the holding unit 20-1 is detachably attached to the vacuum cleaner body of the stick vacuum cleaner 2.

Next, an example of the structure of the mounting portion 200 in Example 3 will be described with reference to Figs. 16 and 17. Fig. 16 is a diagram showing a first example of the mounting portion 200 in Example 3. Here, Fig. 16 is a view seen from the A-A direction shown in Fig. 14. The same is true for Fig. 17.

In FIG. 16, the bottom of the terminal holder 20 is connected to the mounting part 200. This mounting part 200 has an upper mounting part 200-1, a lower mounting part 200-2a, and a lower mounting part 200-2b, and its cross section is configured to be annular. Here, by moving in the direction of the arrow (left and right), the lower mounting part 200-2a and the lower mounting part 200-2b together with the upper mounting part 200-1 sandwich the connection part 211. For this reason, the upper mounting part 200-1 and the lower mounting part 200-2a and the lower mounting part 200-2b are movably connected by pins.

The lower mounting part 200-2a and the lower mounting part 200-2b are then fixedly connected with screws or nails, generating a force in the left direction in the figure. This causes the mounting part 200 to tighten the connection part 211. As a result, the terminal holder 20 connected to the mounting part 200 is fixed to the connection part 211.

Next, FIG. 17 is a diagram showing a second example of the mounting part 200 in the third embodiment. In FIG. 17 as well, the mounting part 200 is connected to the lower part of the terminal holder 20. This mounting part 200 has an upper mounting part 200-1, a lower mounting part 200-2a, and a lower mounting part 200-2b, and its cross section is configured to be annular. Here, by moving in the direction of the arrow (left and right), the lower mounting part 200-2a and the lower mounting part 200-2b come to sandwich the connection part 211 together with the upper mounting part 200-1.

Here, the upper mounting part 200-1 is connected to the lower mounting part 200-2a and the lower mounting part 200-2b via a spring that generates a force in the tightening direction. In this way, the mounting part 200 tightens the connection part 211. As a result, the terminal holder 20 connected to the mounting part 200 is fixed to the connection part 211.

The configuration of Example 3 described above allows the user terminal 1 to be fixedly held in the terminal holder 20. As a result, the user of the stick vacuum cleaner 2 can use the user terminal 1 and benefit from various information processing, including information processing related to cleaning.

Examples 4 and 5 are examples in which map information showing cleaning results is created and displayed (presentation process). Of these, in Example 4, the user terminal 1 creates the map information by itself. Note that the stick vacuum cleaner 2 and terminal holder 20 in Examples 4 and 5 are the same as those in Examples 1 to 3, so their description will be omitted.

Figure 18 is a functional block diagram of the user terminal 1 in Example 4. In Figure 18, compared to Figure 3, a map information creation unit 1001 and a coordinate detection unit 1002 are added, and the AR information creation unit 16 is omitted. However, the AR information creation unit 16 may also be provided in Example 4. In addition, layout information 193, tracking information 194, and map information 195 are stored in the storage unit 19. The other configuration is the same as in Example 1, so the following description will focus on the differences.

First, the map information creation unit 1001 creates map information showing a cleaned map using the cleaned area and the area to be cleaned. The cleaned area can use the movement history (coordinates) of the stick vacuum cleaner 2. The area to be cleaned can use layout information showing the layout of a house or office.

The coordinate detection unit 1002 can use a so-called gyro, GPS sensor, or beacon receiver to detect the position of the stick vacuum cleaner 2. The coordinate detection unit 1002 may be omitted, and the position of the stick vacuum cleaner 2 may be identified using the detection results from the operation status detection unit 15. The layout information 193, tracking information 194, and map information 195 will be described later.

Next, an implementation example of the user terminal 1 in Example 4 will be described. FIG. 19 is a hardware configuration diagram of the user terminal 1 in Example 4. In FIG. 19, compared to FIG. 4, a map information creation module 111 and a GPS sensor 112 are added, and the AR information creation module 110 is omitted. However, the AR information creation module 110 may also be provided in Example 4. In addition, layout information 193, tracking information 194, and map information 195 are stored in the storage device 106. Since the other configurations are the same as those in Example 1, the differences will be described below.

The map information creation module 111 is a function of the vacuum cleaner management program 107, and is an example of an implementation of the map information creation unit 1001. However, this may be implemented as a program separate from the vacuum cleaner management program 107, or may be implemented as a function of an integrated management application that also manages other home appliances. The GPS sensor 112 is an example of an implementation of the coordinate detection unit 1002 in FIG. 18, and can detect a position using latitude and longitude, which are an example of coordinates. Note that the GPS sensor 112 may be omitted, and the position of the stick vacuum cleaner 2 may be identified using the detection result from the operation status detection module 109.

Next, the layout information 193, the tracking information 194, and the map information 195 will be described. FIG. 20 is a diagram showing the layout information 193 used in the fourth embodiment. The layout information 193 is information showing the layout of the place of use where the stick vacuum cleaner 2 is used, such as a house or an office. For this reason, the layout information 193 has items of user and layout corresponding to the place of use. The user indicates the user of the stick vacuum cleaner 2 at the place of use, for example, the resident. Note that the user item can be omitted. The layout indicates the arrangement of sections, such as the floor plan of the corresponding place of use. In the example of FIG. 20, the coordinates of each section (room) are shown, but the format is not limited. Note that the above items are merely examples, are not limited to these, and some of them can be omitted.

Figure 21 is a diagram showing tracking information 194 used in Example 4. Tracking information 194 is information indicating the movement history of a stick vacuum cleaner 2. Therefore, tracking information 194 has the items of date and time and coordinates for the corresponding stick vacuum cleaner 2. The date and time indicates the date and time of the movement, i.e., the date and time when cleaning was performed with the stick vacuum cleaner 2. The coordinates indicate the movement history when the corresponding vacuum cleaner was operating (cleaning). The above items are merely examples and are not limited to these, and some of them may be omitted.

The map information 195 is information that shows the state of cleaning and is created based on the layout information 193, tracking information 194, and the operating status (trajectory) of the stick vacuum cleaner 2 detected by the operating status detection unit 15. The map information 195 will be explained together with the processing flow.

Next, the map information presentation process in Example 4 will be described. FIG. 22 is a flowchart showing the map information presentation process flow in Example 4. Below, the configuration of the user terminal 1 will be described using the configuration shown in FIG. 18. Also, since this process flow has some parts in common with Example 1, the following description will focus on the differences.

First, steps S1 to S4 are the same as in the first embodiment. Then, if it is determined in step S4 that it is usable, the process proceeds to step S101. If it is not usable, the process ends. Also, when the process is started in step S1, the coordinate detection unit 1002 starts detecting the coordinates of the stick vacuum cleaner 2.

In addition, in step S101, the operation status detection unit 15 determines whether layout information 193 is stored in the memory unit 19. The determination may be made not only based on the presence or absence of layout information 193, but also based on whether layout information 193 is present that includes the position detected by the coordinate detection unit 1002. In this case, the layout information 193 includes the coordinates of the location of use. As a result, if layout information 193 is present, the process transitions to step S7. If layout information 193 is not present, the process transitions to step S102.

In addition, in step S102, the operation status detection unit 15 creates the corresponding layout information 193 according to the user's operation on the input unit 17, and stores it in the memory unit 19. Then, in step S7, the operation status detection unit 15 detects the operation status of the stick vacuum cleaner 2, as in the first embodiment.

In step S103, the operation status detection unit 15 updates the coordinates and date and time of the tracking information 194 based on the coordinates detected by the coordinate detection unit 1002. In step S104, the operation status detection unit 15 uses the captured image to determine whether the vacuum cleaner head 24 is floating above the floor surface. If the vacuum cleaner head 24 is floating, it becomes difficult to suck up dust on the floor surface, and it can be considered that cleaning is not being performed. For this reason, in Example 4, map information is created only when the vacuum cleaner head 24 is not floating.

If the result is that the cleaner head 24 is floating (floating), the process proceeds to step S105. If the result is that the cleaner head 24 is not floating (not floating), the process proceeds to step S106. Whether the cleaner head 24 is floating can be determined using well-known image processing techniques. This step may be omitted, and processing may be performed to execute step S106. Floating refers to the cleaner head 24 being separated from the floor surface by a predetermined distance or more.

In step S105, the operation status detection unit 15 stops the detection in step S7 or step S103. Then, the determination in step S104 is repeated. Note that in this step, the detection itself may be continued and the operation status detection unit 15 may invalidate the result.
This is done for this purpose.

In addition, in step S106, the map information creation unit 1001 creates map information 195 using the layout information 193, tracking information 194, and the operating status (trajectory) detected in step S7. More specifically, the map information 195 is created by superimposing the tracking information 194, which indicates the cleaning results, and the operating status (trajectory) detected in step S7 on the layout information 193. In addition, the coordinates detected in step S103 are used as the tracking information 194. As a result, the map information 195 shows the state of cleaning of the area to be cleaned, such as a house.

Next, in step S107, the map information creation unit 1001 displays the created map information on the output unit 18. Here, the map information 195 and its display contents are shown in FIG. 23A and FIG. 23B. FIG. 23A is a diagram showing a first example of the map information 195 used in Example 4. In FIG. 23A, each floor plan is filled with a color according to the cleaning record (track). In FIG. 23A, the living/dining room (LD) is filled with black because it has been cleaned the most. In addition, the kitchen (K) and the master bedroom (MBR) are filled with the next darkest color because they have been cleaned the second most after the living/dining room. Furthermore, the children's rooms (BR) at both ends are cleaned less than the kitchen and master bedroom, so they are displayed even lighter. And the hallway (HALL) and the like are not filled in because they have not been cleaned. Here, this map information 195 is created by combining the above-mentioned coordinates and cleaning history (trajectory) with layout information 193, which is information that is not filled in (does not include a trajectory).

Also, FIG. 23B is a diagram showing a second example of map information 195 used in Example 4. Map information 195 in FIG. 23B is created by combining the functions of AR information creation unit 16 in Example 1. For this purpose, first, in map information 195 in FIG. 23B, a color corresponding to the cleaning record is superimposed on image data for each unit section and displayed. This unit section is recorded as layout information 193. Then, using the functions of AR information creation unit 16, the map information 195 is updated in accordance with the change when the user changes the orientation of the user terminal 1 (photographing unit 12). For this reason, the user can more intuitively grasp the cleaning record. Note that such a display may be realized without using AR information creation unit 16. In other words, the cleaning record may be superimposed on image data showing the state of the room. Furthermore, map information 195 including both FIG. 23A and FIG. 23B may be created and displayed. In this case, both may be displayed while switching between them, or may be displayed in parallel. Furthermore, the map information 195 may be displayed not only by filling in each unit section or room, but also as line information showing the trajectory of the stick vacuum cleaner 2.

Furthermore, in step S107, a display similar to that in Example 1 may be performed, or this display may be performed by batch processing using the map information 195 stored in the memory unit 19 after cleaning is completed (step S12 or later). Furthermore, notifications may be given each time as appropriate (so-called real-time processing).

As in the first embodiment, the end determination is performed in step S12, and if cleaning is continuing, the process transitions to step S103. If cleaning has ended, the process transitions to step S108.

Then, in step S108, the map information creation unit 1001 executes the update process by storing the map information 195 created in step S106 in the storage unit 19. This ends the process of Example 4. In Example 4, the map information 195 is created and displayed, allowing the user to intuitively understand the cleaning status. Example 4 can be combined with any of Examples 1 to 3. Furthermore, the cleaning history (cleaned area) of the cleaner management information 192 may be used as the map information 195. In this case, the map information 195 can be omitted.

Example 5 is an example in which map information showing the cleaning results of Example 4 is created and displayed (presentation process) in cooperation with a vacuum cleaner management device 3 that is realized by a server or the like. Note that the stick vacuum cleaner 2 and terminal holder 20 in Example 5 are the same as those in Examples 1 to 4. The user terminal 1 is also the same as that in Example 4. For this reason, the description thereof will be omitted below. However, at least one of the configurations and information for executing the functions common to the user terminal 1 and the vacuum cleaner management device 3 can be omitted.

Figure 24 is a system configuration diagram of a vacuum cleaner management system in Example 5. In Figure 24, compared to Figure 9, a map information creation unit 36 is added, and the AR information creation unit 34 is omitted. However, the AR information creation unit 34 may also be provided in Example 5. In addition, layout information 353, tracking information 354, and map information 355 are stored in the memory unit 19. The other configuration is the same as in Example 2, so the following description will focus on the differences.

First, the map information creation unit 36, like the map information creation unit 1001 in Example 4, creates map information showing a cleaned map using the cleaned area and the area to be cleaned. The cleaned area can use the movement history (coordinates) of the stick vacuum cleaner 2. The area to be cleaned can use layout information showing the layout of a house or office. The layout information 353, tracking information 354, and map information 355 will be described later.

Next, a hardware configuration as an implementation example of the vacuum cleaner management device 3 will be described. The vacuum cleaner management device 3 can be realized by a computer such as a server or a cloud system. FIG. 25 is a hardware configuration diagram of the vacuum cleaner management device 3 in Example 5. In FIG. 25, compared to FIG. 10, a map information creation module 309 is added, and the AR information creation module 308 is omitted. However, the AR information creation module 308 may also be provided in Example 5. In addition, layout information 353, tracking information 354, and map information 355 are stored in the storage device 106. The other configuration is the same as in Example 2, so the differences will be described below.

The map information creation module 309 is a function of the vacuum cleaner management program 305 and is an example of an implementation of the map information creation unit 36. However, this may be implemented as a program separate from the vacuum cleaner management program 305, or as a function of an integrated management application that also manages other home appliances. Note that in Example 5, the user terminal 1 also has a GPS sensor 112, which is an example of an implementation of the coordinate detection unit 1002. However, the GPS sensor 112 may be omitted, and the position of the stick vacuum cleaner 2 may be identified using the detection results of the operation status detection module 307.

Next, layout information 353, tracking information 354, and map information 355 will be described. FIG. 26 is a diagram showing layout information 353 used in Example 5. Layout information 353 has the same items as layout information 193 in Example 4. However, layout information 353 includes not only information about the stick vacuum cleaner 2, but also layout information (records) for other locations of use. This is to allow the vacuum cleaner management device 3 to manage multiple users.

Figure 27 is a diagram showing tracking information 354 used in Example 5. Tracking information 354 has the same items as tracking information 194 in Example 4. However, tracking information 354 includes not only information about the stick vacuum cleaner 2, but also tracking information (records) about other vacuum cleaners used by the user. This is to allow the vacuum cleaner management device 3 to manage multiple users. Map information 355 is the same information as map information 195 in Example 4, and is shown in Figures 23A and 23B. Similarly to layout information 353 and tracking information 354, map information 355 is information about multiple vacuum cleaners.

Next, the map information presentation process in Example 5 will be described. Figures 28A and 28B are flowcharts showing the map information presentation process flow in Example 5. Below, the configuration shown in Figure 18 is used as the configuration of the user terminal 1, and the configuration shown in Figure 19 is used as the configuration of the vacuum cleaner management device 3. This process flow also has some parts in common with Example 2, so the following description will focus on the differences.

First, steps S1 to S19 are the same as in Example 2. However, when activation is performed in step S1, the coordinate detection unit 1002 starts detecting the coordinates of the stick vacuum cleaner 2. Then, in step S14, the detected coordinates are also notified. Also, if it is determined in step S17 that the device is usable, the process proceeds to step S35.

In addition, in step S35, the operation status detection unit 33 determines whether layout information 353 including the position detected by the coordinate detection unit 1002 is stored in the memory unit 35. Therefore, the layout information 353 includes the coordinates of the location of use. As a result, if layout information 353 is present, the process proceeds to step S26. If layout information 353 is not present, the process proceeds to step S36.

In addition, in step S36, the operation status detection unit 33 cooperates with the user terminal 1, that is, creates the corresponding layout information 353 in accordance with the user's operation on the input unit 17 of the user terminal 1, and stores it in the storage unit 35. Then, in step S26, the operation status detection unit 33 detects the operation status of the stick vacuum cleaner 2, as in Example 2.

In step S37, the operation status detection unit 33 updates the coordinates and date and time in the corresponding record in the tracking information 354 using the coordinates notified in step S14. In step S38, the operation status detection unit 33 uses the notified image to determine whether the vacuum cleaner head 24 is floating above the floor surface. This is performed in the same way as in step S104 in Example 4. In other words, in Example 5 as well, map information is created only when the vacuum cleaner head 24 is not floating.

If the result is that the head is floating (floating), the process proceeds to step S39. If the head is not floating (not floating), the process proceeds to step S40. Note that whether the cleaner head 24 is floating can be determined using image processing technology, as in the fourth embodiment. Note that this step may be omitted, and the process may be such that step S40 is executed.

In addition, in step S39, the operation status detection unit 33 stops step S26 and coordinate detection. In Example 5, in order to stop coordinate detection, the operation status detection unit 33 notifies the user terminal 1 of a stop command using the communication unit 31. Note that in this step, the detection itself may be continued, and the operation status detection unit 15 may invalidate this result. Then, the judgment in step S38 is repeated.

In addition, in step S40, the map information creation unit 36 creates map information 355 using the layout information 353, tracking information 354, and the operating status (trajectory) detected in step S26. More specifically, the map information 355 is created by superimposing the tracking information 354, which indicates the cleaning results, and the operating status (trajectory) detected in step S26 on the layout information 353. In addition, the coordinates detected in step S37 are used as the tracking information 354. As a result, the map information 195 shows the state of cleaning of the area to be cleaned, such as a house.

In addition, in step S41, the map information creation unit 36 uses the communication unit 31 to notify the user terminal 1 of the created map information 355. Then, in step S42, the output unit 18 of the user terminal 1 displays the map information 355. Here, the display content in this step is the same as in Example 4.

Furthermore, similarly to the second embodiment, steps S30 and S31 are executed. Therefore, the communication unit 31 of the vacuum cleaner management device 3 receives a termination notification from the user terminal 1. Then, in step S43, the map information creation unit 36 of the vacuum cleaner management device 3 terminates the creation of the map information 355. Then, in step S44, the map information creation unit 36 executes the update process by storing the map information 355 created in step S40 in the memory unit 35. This concludes the processing of the fifth embodiment.

In the fifth embodiment, the map information 355 is created and displayed in cooperation with the cleaner management device 3 such as a server, making effective use of resources, and the cleaning status can be displayed so that the user can intuitively grasp it. In addition, the fifth embodiment can be combined with any of the first to fifth embodiments. In particular, the notification of the map information (step S41) may be performed on the user terminals of related parties other than the user. In addition, the AR information may also be notified to the core user terminal. Furthermore, the notification of the map information may be performed by batch processing using the map information 355 stored in the storage unit 35 after the cleaning is completed (step S31 or later), or may be notified appropriately each time (so-called real-time processing). Furthermore, the cleaning record (cleaned area) of the cleaner management information 352 may be used as the map information 355. In this case, the map information 355 can be omitted.

1...user terminal, 11...communication unit, 12...photographing unit, 13...sound collection unit, 14...vacuum cleaner identification unit, 15...operation status detection unit, 16...AR information creation unit, 17...input unit, 18...output unit, 19...storage unit, 191...user management information, 192...vacuum cleaner management information, 193...layout information, 194...tracking information, 195...map information, 1001...map information creation unit, 1002...coordinate detection unit, 2...stick type vacuum cleaner, 20...terminal holder, 20-1...holding unit, 20-2...arm unit, 20-3...base, 21...vacuum cleaner main body, 2 2...Handle, 23...Extension tube, 24...Vacuum cleaner head, 25...Lamp unit, 26...Charging stand, 27...Holder member, 28...Stand member, 29...Base member, 200...Mounting unit, 211...Connection unit, 3...Vacuum cleaner management device, 31...Communication unit, 32...Vacuum cleaner identification unit, 33...Operation status detection unit, 34...AR information creation unit, 35...Storage unit, 36...Map information creation unit, 351...User management information, 352...Vacuum cleaner management information, 353...Layout information, 354...Tracking information, 355...Map information, 4...Router, 5...Network 5

Claims (10)

A user terminal is a computer that is used by a user of a vacuum cleaner that does not have a communication function and is attached to a terminal holder of the vacuum cleaner.
a cleaner identification unit that determines whether the user terminal is available for use based on the identification information of the cleaner;
an operating status detection unit that detects an operating status of the vacuum cleaner when the vacuum cleaner identification unit determines that the vacuum cleaner is usable;
a map information creation unit that creates map information showing a cleaning status by using layout information showing an area to be cleaned by the vacuum cleaner, tracking information showing a movement history of the vacuum cleaner, and the operating status;
a vacuum cleaner management program that functions as an output unit that outputs the map information; 2. The vacuum cleaner management program according to claim 1,
Furthermore, the user terminal has an image capturing unit that captures an image of at least a part of the vacuum cleaner,
The vacuum cleaner identification unit is a vacuum cleaner management program that identifies the vacuum cleaner based on the image captured by the imaging unit. 2. The vacuum cleaner management program according to claim 1,
the operating status detection unit determines whether a cleaner head of the vacuum cleaner is floating based on whether the cleaner head is spaced apart from a floor surface by a predetermined distance or more;
The map information creating section creates the map information when the cleaner head is not lifted. 4. The vacuum cleaner management program according to claim 3,
The operation status detection unit stops detecting the operation status when the cleaner head is lifted. 2. The vacuum cleaner management program according to claim 1,
Further, a cleaner identification unit is provided for determining whether the user terminal is available for use based on the identification information of the cleaner,
The operating status detection unit detects the operating status of the vacuum cleaner when the vacuum cleaner identification unit determines that the vacuum cleaner is usable. A vacuum cleaner management system is provided for a user of a vacuum cleaner having no communication function, the vacuum cleaner management system having a user terminal attached to a terminal holder of the vacuum cleaner and a vacuum cleaner management device,
a cleaner identification unit that determines whether the user terminal is available for use based on the identification information of the cleaner;
an operating status detection unit that detects an operating status of the vacuum cleaner when the vacuum cleaner identification unit determines that the vacuum cleaner is usable;
a map information creation unit that creates map information showing a cleaning status by using layout information showing an area to be cleaned by the vacuum cleaner, tracking information showing a movement history of the vacuum cleaner, and the operating status;
A vacuum cleaner management system having an output unit that outputs the map information. The cleaner management system according to claim 6,
Furthermore, the user terminal has an image capturing unit that captures an image of at least a part of the vacuum cleaner,
The vacuum cleaner identification unit is a vacuum cleaner management system that identifies the vacuum cleaner based on an image captured by the imaging unit. The cleaner management system according to claim 6,
the operating status detection unit determines whether a cleaner head of the vacuum cleaner is floating based on whether the cleaner head is spaced apart from a floor surface by a predetermined distance or more;
The map information creation unit creates the map information when the cleaner head is not surfaced. The cleaner management system according to claim 8,
The operation status detection unit stops detecting the operation status when the cleaner head is lifted. The cleaner management system according to claim 6,
Further, a cleaner identification unit is provided for determining whether the user terminal is available for use based on the identification information of the cleaner,
The operating status detection unit detects the operating status of the vacuum cleaner when the vacuum cleaner identification unit determines that the vacuum cleaner is usable.

Images