Vacuum cleaner management program and vacuum cleaner management system

Abstract

The purpose of the present invention is to realize various functions and services using information processing technology for home appliances, especially vacuum cleaners, while suppressing increases in configurational complexity and price.　The present invention is a vacuum cleaner management system that is for use by a user of a stick-type vacuum cleaner 2 not equipped with a communication function and includes a user terminal 1 attached to a terminal holder 20 in the stick-type vacuum cleaner 2 and a vacuum cleaner management device 3. The vacuum cleaner management system also includes: a vacuum cleaner identification unit 32 that determines whether the user terminal 1 can be used on the basis of identification information for the stick-type vacuum cleaner 2; an operation status detection unit 33 that detects the operation status of the stick-type vacuum cleaner 2 when it is determined by the vacuum cleaner identification unit 32 that the stick-type vacuum cleaner 2 can be used; and an output unit 18 that outputs the operation status.

Description

Vacuum cleaner management program and vacuum cleaner management system

[0001] The present invention relates to so-called home appliances, particularly vacuum cleaners, and information processing technology for managing the same.

[0002] 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 connect to networks such as the Internet and provide various functions and services, such as operational control. 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 having a sensor that measures the rotation speed 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 motor rotation speed and motor current obtained from multiple vacuum cleaners and transmits information about the vacuum cleaner to the mobile information terminal" (abstract).

[0003] Japanese Patent Publication No. 2022-162696

[0004] Currently, many home appliances are in use that do not have communication functions. In other words, many home appliances that are not IoT appliances are also in use. These appliances cannot enjoy some of the functions and services that are available in IoT appliances. In addition, IoT appliances require functions such as communication functions, which may lead to a more complex structure and higher prices.

[0005] Therefore, an object of the present invention is to provide various functions and services using information processing technology for home appliances, particularly vacuum cleaners, while preventing the configuration from becoming more complicated and the price from increasing.

[0006] The configuration of the present invention to solve the above problem is a vacuum cleaner management program that functions as a vacuum cleaner identification unit that is used by a user of a vacuum cleaner that does not have communication functions and that determines whether a user terminal, which is a computer attached to the 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 if the vacuum cleaner identification unit determines that the user terminal is usable, and an output unit that outputs the operation status.

[0007] 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 that 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 the identification information of the vacuum cleaner, an operation status detection unit that detects the operation status of the vacuum cleaner if the vacuum cleaner identification unit determines that the vacuum cleaner is usable, and an output unit that outputs the operation status.

[0008] 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 make up the system.

[0009] According to the present invention, it is possible to provide various functions and services using information processing technology to home appliances, particularly vacuum cleaners, while preventing the configuration from becoming complicated and the price from increasing.

[0010] 14 is a perspective view showing a state in which a stick vacuum cleaner according to one embodiment of the present invention is stored in a stick state on a charging stand. FIG. 15 is a diagram showing a state in which a user terminal 1 is installed on a stick vacuum cleaner 2 according to one embodiment of the present invention. FIG. 16 is a functional block diagram of a user terminal 1 according to Example 1. FIG. 17 is a hardware configuration diagram of a user terminal 1 according to Example 1. FIG. 18 is a diagram showing user management information 191 used in Example 1. FIG. 19 is a diagram showing vacuum cleaner management information 192 used in Example 1. FIG. 19 is a flowchart showing a cleaning area presentation processing flow according to Example 1. FIG. 20 is a diagram showing a display screen of AR information according to Example 1. FIG. 21 is a system configuration diagram of a vacuum cleaner management system according to Example 2. FIG. 22 is a hardware configuration diagram of a vacuum cleaner management device 3 according to Example 2. FIG. 23 is a diagram showing user management information 351 used in Example 2. FIG. 24 is a diagram showing vacuum cleaner management information 352 used in Example 2. FIG. 25 is a flowchart (part 1) showing a cleaning area presentation processing flow according to Example 2. FIG. 26 is a flowchart (part 2) showing a cleaning area presentation processing flow according to Example 2. FIG. 27 is a diagram schematically showing a side view when a terminal holder 20 is attached to a stick vacuum cleaner 2 according to Example 3. FIG. 28 is an enlarged view of FIG. 14 showing a state in which the terminal holder 20 is attached according to Example 3. 10 is a diagram showing a first example of the attachment unit 200 in Example 3. FIG. 11 is a diagram showing a second example of the attachment unit 200 in Example 3. FIG. 12 is a functional block diagram of a user terminal 1 in Example 4. FIG. 13 is a hardware configuration diagram of a user terminal 1 in Example 4. FIG. 14 is a diagram showing layout information 193 used in Example 4. FIG. 15 is a diagram showing tracking information 194 used in Example 4. FIG. 16 is a flowchart showing a presentation process flow of map information in Example 4. FIG. 17 is a diagram showing a first example of map information 195 used in Example 4. FIG. 18 is a diagram showing a second example of map information 195 used in Example 4. FIG. 19 is a system configuration diagram of a vacuum cleaner management system in Example 5. FIG. 19 is a hardware configuration diagram of a vacuum cleaner management device 3 in Example 5. FIG. 19 is a diagram showing layout information 353 used in Example 5. FIG. 19 is a diagram showing tracking information 354 used in Example 5. FIG. 19 is a flowchart (part 1) showing a presentation process flow of map information in Example 5. FIG. 19 is a flowchart (part 2) showing a presentation process flow of map information in Example 5.

[0011] An embodiment of the present invention will be described below. In this embodiment, a vacuum cleaner will be described as an example of a home appliance. In particular, a stick vacuum cleaner will be described 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.

[0012] 1 is a perspective view showing a stick vacuum cleaner 2 according to this embodiment stored in a charging stand 26 in a stick state. The stick vacuum cleaner 2 comprises 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.

[0013] 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 integrated unit. 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 example.

[0014] The stick vacuum cleaner 2 can be changed into various states for cleaning, such as a handheld state or a stick state. The charging base 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. The charging base 26 can charge the stick vacuum cleaner 2.

[0015] A sign 25 such as an AR marker or nameplate is provided on the cleaner head 24, which faces the cleaning surface such as the floor. Identification information for identifying the stick vacuum cleaner 2 is recorded on this sign 25. 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. This process will be described below.

[0016] Fig. 2 is a diagram showing the state in which a user terminal 1 is installed on a stick vacuum cleaner 2 in this embodiment. In this embodiment, as shown in Fig. 2, the user terminal 1 is held in a terminal holder 20 connected to the vacuum cleaner main body 21. In this case, 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 25. It is desirable 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.

[0017] 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 cleaning area presentation process will be described in detail. Furthermore, in Example 3, the structure of the terminal holder 20 will be described in detail. Furthermore, in Examples 4 and 5, examples of creating map information will be described. Note that it is possible to combine at least two of each example.

[0018] Example 1 is an example in which the cleaning area presentation process is executed solely by the user terminal 1. Fig. 3 is a functional block diagram of the user terminal 1 in Example 1. The user terminal 1 includes a communication unit 11, an imaging 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 storage unit 19.

[0019] The communication unit 11 has a function of communicating via a router or a network and a function of short-range 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.

[0020] Furthermore, the vacuum cleaner identification unit 14 identifies the stick vacuum cleaner 2 using the image captured by the imaging unit 12. In Examples 1 and 2, the image of the label unit 25 captured by the imaging unit 12 is used to identify the identification information recorded on the label unit 25, and identification is performed using this. Note that the label unit 25 can be an AR (Augmented Reality) marker, a two-dimensional code, or a nameplate. Here, the identification information is recorded on the nameplate in a visible format.

[0021] 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, and the identification information is read by this.

[0022] Furthermore, the operation status detection unit 15 detects the operation status of the stick vacuum cleaner 2, such as the identification of the cleaning area, using the image of the floor surface captured by the image capture unit 12. The AR information creation unit 16 then 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 information to be provided to related parties, including users. Therefore, the information to be provided is not limited to AR information, but may be a captured image (including a still image or a video), an animation indicating the cleaning area, or text indicating the cleaning area.

[0023] 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.

[0024] 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 Example 1. 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.

[0025] First, the camera 101 is an example of the imaging unit 12 and has an imaging function. The microphone 102 is an example of the sound collection unit 13 and has an audio 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 user operations and displays various information such as AR information. The touch panel 103 may be configured as an input device and an output device.

[0026] The processing device 104 can be realized by a processor such as a CPU (Central Processing Unit), and executes calculations in accordance with a cleaner management program 107 stored in a storage device 106, which will be described later.

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

[0028] 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, operation status detection unit 15, and 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 (described later) or other storage media.

[0029] 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 function of 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 hard disk drive (HDD), solid state drive (SSD), memory card, etc.

[0030] 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 Example 1. The user management information 191 is information about the user of the user terminal 1. Therefore, as shown in FIG. 5, the user management information 191 has the following fields: user, address, contact information, and owned vacuum cleaner. Here, the user is information that identifies the user, such as the user's name and membership number. The address indicates the address of the user. The contact information indicates the user's contact information, which can be a telephone number or email address. The owned vacuum cleaner is information that identifies the home appliance used by the user, i.e., 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.

[0031] 6 is a diagram showing vacuum cleaner management information 192 used in Example 1. 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 items: vacuum cleaner, vacuum cleaner ID, related party, date and time, AR information, and cleaning history (cleaned area).

[0032] Here, the vacuum cleaner indicates the type of the managed object, that is, the vacuum cleaner that is the target of the cleaning area presentation process. In Example 1, the 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.

[0033] The vacuum cleaner ID is identification information that identifies the vacuum cleaner in question. This vacuum cleaner ID is information equivalent to the identification information recorded in the label 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 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 enables the determination of step S9 in the processing flow (Figure 7) described below. This distinction can be made by adding a user field or by comparing the user management information 191 with the vacuum cleaner management information 192.

[0034] 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 AR information created by the AR information creation unit 16. The cleaning history (cleaned area) indicates the area cleaned by the corresponding stick vacuum cleaner 2 based on the AR information. Therefore, the cleaning history (cleaned area) has items of coordinates and room. Here, the coordinates are coordinates that indicate the area cleaned by the stick vacuum cleaner 2, i.e., 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.

[0035] Next, a description will be given of the cleaning area presentation process in Example 1. Fig. 7 is a flowchart showing the cleaning area presentation process flow in Example 1. The following describes the configuration of the user terminal 1 using the configuration shown in Fig. 3 .

[0036] First, in step S1, the input unit 17 accepts input from the user and activates a 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 cleaner head 24) of the stick vacuum cleaner 2, enabling the user terminal 1 to capture images in this direction.

[0037] In step S2, the photographing unit 12 starts photographing. This photographing 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 pickup unit 13. Alternatively, the sound pickup unit 13 may pick up sounds generated when the stick vacuum cleaner 2 is in operation, and the photographing unit 12 may start photographing based on the sounds.

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

[0039] 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 included in the captured image, and based on this, identifies identification information for identifying the stick vacuum cleaner 2. In this case, the identification information identifies the type, such as the model, of the stick vacuum cleaner 2.

[0040] In step S4, the cleaner identification unit 14 determines whether the user terminal 1 held in the terminal holder 20 is usable, i.e., whether the cleaning area presentation process in this flowchart is possible. To this end, 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 the cleaner ID is recorded, i.e., if the cleaner is usable, the process proceeds to step S5. If the cleaner ID is not recorded and the cleaner is unusable, the process ends. At this time, it is desirable for the output unit 18 to display a message indicating that the cleaner is unusable. Thus, in step S4, the identification process is performed using the identification information. Note that if the user terminal 1 is installed in the terminal holder 20, the indicator 25 can be accurately photographed. Therefore, step S4 also serves as a means for the cleaner identification unit 14 to determine whether the user terminal 1 is correctly attached to the terminal holder 20.

[0041] Furthermore, in step S5, the vacuum cleaner identification unit 14 identifies the related person corresponding to the vacuum cleaner ID identified in step S4 from the vacuum cleaner management information 192. Furthermore, in step S6, the vacuum cleaner identification unit 14 accepts a selection of a recipient of AR information, which will be described later, via the input unit 17 and the sound collection unit 13. For this purpose, the vacuum cleaner identification unit 14 displays the related person identified in step S5 via the output unit 18. Note that the related person may be output as an audio via an audio output unit such as a speaker.

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

[0043] In step S8, the AR information creation unit 16 creates AR information by superimposing the operating status detected by the operating status detection unit 15 on an image of the cleaning area, which is the floor surface captured by the capture unit 12. The created AR information will now be described using its display screen. FIG. 8 is a diagram showing the display screen of the AR information in Example 1. In FIG. 8, the AR information is displayed on the output unit 18 of the user terminal 1. A trajectory 182 of the vacuum cleaner head 24 is superimposed on the captured image (floor surface 181). The shading of the trajectory 182 indicates the frequency of movement. In other words, the darker the area, the more cleaning has been performed. Also, in FIG. 8, the cleaning record (cleaned area) 183, i.e., the date and time, cleaning time, and coordinates, is displayed as the operating status. Here, the date and time indicates the current date and time of cleaning. The cleaning time is the time since the stick vacuum cleaner 2 started cleaning. Furthermore, the coordinates and location indicating the location are identified according to a position detection unit, such as a gyro, of the user terminal 1 and are also displayed.

[0044] 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 explaining the processing flow.

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

[0046] Furthermore, 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 record (cleaned area) 183 and the 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 user can also share the cleaning record with the user using the stick vacuum cleaner 2. Note that this sharing may be realized in real time, or may be achieved with a time lag or by sharing only the results. Details of these will be described later in Example 2. Furthermore, in step S11, the AR information creation unit 16 displays the display screen shown in FIG. 8 on the output unit 18.

[0047] Furthermore, in step S12, the AR information creation unit 16 determines whether cleaning with the stick vacuum cleaner 2 has finished. At this time, the completion can be determined by an operation from the user on the input unit 17 or a voice instruction 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 in operation and picked up by the sound collection unit 13 has stopped. As a result, if cleaning has finished, the process proceeds to step S13. Furthermore, if cleaning is continuing, the creation of AR information in step S8 continues. Therefore, the image capture by the image capture unit 12 and the detection of the operating status by the operating status detection unit 15 also continue.

[0048] Then, in step S13, the AR information creation unit 16 records the created AR information and the cleaning record (cleaned area) indicating the operating status, thereby updating the vacuum cleaner management information 192. Furthermore, it is desirable that the AR information creation unit 16 stop the notification in step S10 and the display in step S11.

[0049] This concludes the description of Example 1. According to Example 1, it is possible to provide a cleaning area presentation process even for a vacuum cleaner without a communication function, and as a result, users 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 users. 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 the process transitions from step S8 to step S10.

[0050] In the first embodiment, the cleaning area presentation process is performed by the user terminal 1 alone, but in the second embodiment, 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 the second embodiment. In Fig. 9, the vacuum cleaner management system has a user terminal 1 held by the terminal holder 20 of the 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 to the network 5 directly.

[0051] 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.

[0052] Furthermore, the user terminal 1 and the vacuum cleaner management device 3 are connected to the user terminals 1-a and 1-b used by the relevant parties described in Example 1 via a router 4 and a network 5. In FIG. 9, the user terminal 1-a is located in the same home as the user terminal 1, and is connected to the user terminal 1 and the vacuum cleaner management device 3 via a router 4. The user terminal 1-b is located in a different location (outside the home) 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 terminals 1-a and 1-b may have the same functions as the user terminal 1, or may be configured such that the vacuum cleaner identification unit 14 to the AR information creation unit 16 are omitted.

[0053] Next, a description will be given of the vacuum cleaner management device 3, which is a characteristic configuration of Example 2. 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, a description will be given of the configuration of the vacuum cleaner management device 3.

[0054] 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 storage unit 35. First, the communication unit 31 connects to each user terminal via the network 5.

[0055] Furthermore, the vacuum cleaner identification unit 32, the operation status detection unit 33, and the AR information creation unit 34 perform the same processes as the vacuum cleaner identification unit 14, the operation status detection unit 15, and the AR information creation unit 16 of Example 1. Furthermore, the storage unit 35 stores user management information 351 and vacuum cleaner management information 352. Each of these pieces of information will be described later.

[0056] Next, a hardware configuration will be described as an implementation example of the vacuum cleaner management device 3. 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.

[0057] First, the processing device 301 can be realized by a processor such as a CPU, and executes calculations in accordance with a vacuum cleaner management program 305 stored in a secondary storage device 304 (described later). 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.

[0058] 9. The memory 303 and the secondary storage device 304 store the vacuum cleaner management program 305 and information used for processing by the processing device 301, which are stored in the secondary storage device 304. The secondary storage device 304 can be implemented 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 implemented as various storage media such as an external hard disk drive (HDD), solid state drive (SSD), or memory card, or may be implemented as a device separate from the vacuum cleaner management device 3, such as a file server.

[0059] Here, 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, each for one of its functions. Note that 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 the home appliance management program. Furthermore, the vacuum cleaner management program 305 may be realized as one function of an integrated management application that manages multiple home appliances.

[0060] 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 processing of the vacuum cleaner identification unit 32, operation status detection unit 33, and AR information creation unit 34 in accordance with the vacuum cleaner management program 305.

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

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

[0063] 12 is a diagram showing vacuum cleaner management information 352 used in Example 2. Like the vacuum cleaner management information 352, the vacuum cleaner management information 352 is information for managing home appliances used by a user, such as a stick vacuum cleaner 2. Therefore, like the vacuum cleaner management information 192, the vacuum cleaner management information 352 has the following fields: vacuum cleaner, vacuum cleaner ID, person involved, date and time, AR information, and cleaning history (cleaned area).

[0064] However, the vacuum cleaner management information 352 is intended for multiple users, such as members. Therefore, the vacuum cleaner management information 352 will contain records for each vacuum cleaner of the target user. As in the first embodiment, it is desirable to distinguish users from other related parties. Furthermore, 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. Furthermore, 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.

[0065] Next, a cleaning area presentation process in Example 2 will be described. Figures 13A and 13B are flowcharts showing a 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.

[0066] First, in steps S1 and S2, the same processing as in Example 1 is executed by the user terminal 1. Then, 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 to this, in step S15, the communication unit 31 of the vacuum cleaner management device 3 accepts the image.

[0067] Then, in step S16, the vacuum cleaner identification unit 32 uses the received image to recognize the identification information recorded in the label unit 25. This process is performed in the same manner as step S3 in Example 1. Also, in step S17, the vacuum 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. That is, the same process as step S4 in Example 1 is performed. However, in step S17, the vacuum cleaner management information 352 is used instead of the vacuum cleaner management information 192. As a result, if it is recorded, that is, if it is usable, the process proceeds to step S20. Also, if it is not recorded and therefore not usable, the process proceeds to step S18.

[0068] In step S18, the vacuum cleaner identification unit 32 notifies the user terminal 1 that the vacuum cleaner is unusable via the communication unit 31. Then, in step S19, the communication unit 11 of the user terminal 1 receives the notification of step S18 and displays information that the vacuum cleaner is unusable on the output unit 18. As a result, this flowchart ends.

[0069] 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 realized by processing similar to that in step S5, but it is desirable to exclude the user from the related parties.

[0070] Furthermore, in step S21, the vacuum cleaner identification unit 32 notifies the user terminal 1 of the related parties identified in step S20 via the communication unit 31. 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, i.e., 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.

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

[0072] 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 image capture 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.

[0073] Furthermore, 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. That is, 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 user terminals of the recipients, including the user terminal 1, using the communication unit 31. This recipient is the user terminal of the recipient accepted in step S25 or the user terminal 1 of the user. For example, the AR information is notified to the user terminal 1-a and the user terminal 1-b in FIG. 9.

[0074] 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 on user terminals of recipients other than the user terminal 1. Note that the 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 content will be explained later after the explanation of this flowchart. In addition, the display on terminals other than the user terminal 1 is terminated by an operation by the relevant user.

[0075] Furthermore, in step S30, the user terminal 1 determines whether cleaning with the stick vacuum cleaner 2 has finished. This is performed in the same manner as step S12 in the first embodiment, but may be performed by any of the vacuum cleaner identification unit 14, the operating status detection unit 15, or the AR information creation unit 16, or may be performed by another configuration. As a result, if cleaning has finished, the process proceeds to step S31. Furthermore, 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.

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

[0077] In step S32, the communication unit 31 of the vacuum cleaner management device 3 receives the end notification, and in response, the AR information creation unit 34 ends 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 record (cleaned area) indicating the operating status.

[0078] Furthermore, in step S34, the AR information creation unit 34 uses the communication unit 31 to send a completion notification to other user terminals of the provision destination other than the user terminal 1. As a result, the display processing on the other user terminals ends. This concludes the explanation of this flowchart, but notification and display (another aspect) of the AR information to user terminals of the provision destination other than the user terminal 1 will be explained.

[0079] 9 are assumed to be the destinations. 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.

[0080] First, the user terminal 1-a inside the home is notified and displayed as AR information is created, just like the user terminal 1. This is called real-time processing. Furthermore, when cleaning is completed, the user terminal 1-b outside the home is notified and displayed with information indicating the results.

[0081] This concludes the description of the second embodiment, but according to the second embodiment, even for a vacuum cleaner without a communication function, the process of presenting the cleaning area can be realized in cooperation with the server-like vacuum cleaner management device 3. This allows appropriate resources to be used, and efficient processing can be realized.

[0082] Next, a third embodiment relating to the structure of the terminal holder 20 will be described. Fig. 14 is a diagram schematically illustrating a side view of the stick vacuum cleaner 2 in the third embodiment when the terminal holder 20 is attached thereto. As also 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 connector 211 for connecting to the extension tube 23. The stick vacuum cleaner 2 in 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.

[0083] Here, the terminal holder 20 is detachably installed on the vacuum cleaner main body 21, more preferably on the connection part 211. For example, the terminal holder 20 is configured in a ring-like or tubular 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 a part other than the extension tube 23 or the connection part 211. Furthermore, when the extension tube 23 of the stick vacuum cleaner 2 is removed and a replacement nozzle (tube) is provided, the terminal holder 20 may be connected to the nozzle. The replacement nozzle is a nozzle that is shorter than the extension tube 23 and includes a brush nozzle and a tapered nozzle. Furthermore, it is desirable for the replacement nozzle to have a cableless structure that omits a cable that controls the vacuum cleaner head 24.

[0084] 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 at an angle of 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, which will be described later. This allows the imaging part 12 of the user terminal 1 to capture images of the cleaner head 24 and the floor surface to be cleaned.

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

[0086] First, the holding unit 20-1 securely holds the user terminal 1 by clamping it, for example. The base 20-3 and the attachment unit 200 are connected, and the terminal holder 20 is fixedly attached to the stick vacuum cleaner 2. The arm unit 20-2 then connects the holding unit 20-1 to the base 20-3. In the third embodiment, the base 20-3 or the terminal holder 20 and the attachment 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 of 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 attachment unit 200 added to these. This allows the terminal holder 20 to be shared with 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.

[0087] Next, an example of the structure of the mounting portion 200 according to the third embodiment will be described with reference to Fig. 16 and Fig. 17. Fig. 16 is a diagram showing a first example of the mounting portion 200 according to the third embodiment. Here, Fig. 16 is a view seen from the direction A-A shown in Fig. 14. The same applies to Fig. 17.

[0088] 16, the lower part of the terminal holder 20 is connected to the mounting part 200. The 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, the lower mounting part 200-2a and the lower mounting part 200-2b move in the direction of the arrows (left and right), and together with the upper mounting part 200-1, they 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.

[0089] Then, the lower mounting portion 200-2a and the lower mounting portion 200-2b are fixedly connected with screws or nails, and a force is generated in the left direction in the figure. This causes the mounting portion 200 to tighten the connection portion 211. As a result, the terminal holder 20 connected to the mounting portion 200 is fixed to the connection portion 211.

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

[0091] Here, upper mounting portion 200-1 is connected to lower mounting portion 200-2a and lower mounting portion 200-2b via springs that generate force in the tightening direction. In this way, mounting portion 200 tightens connecting portion 211. As a result, terminal holder 20 connected to mounting portion 200 is fixed to connecting portion 211.

[0092] With the configuration of the third embodiment described above, the user terminal 1 can 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 functions, including information processing related to cleaning.

[0093] 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 independently. 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, and therefore their description will be omitted.

[0094] Fig. 18 is a functional block diagram of the user terminal 1 in Example 4. In Fig. 18, compared to Fig. 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. Since the other configurations are the same as those in Example 1, the following description will focus on the differences.

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

[0096] The coordinate detection unit 1002 may 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 result from the operation status detection unit 15. The layout information 193, tracking information 194, and map information 195 will be described later.

[0097] 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.

[0098] 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.

[0099] Next, the layout information 193, tracking information 194, and map information 195 will be described. FIG. 20 is a diagram showing the layout information 193 used in Example 4. The layout information 193 is information indicating the layout of a usage location, such as a house or an office, where the stick vacuum cleaner 2 is used. Therefore, the layout information 193 has items for a user and a layout corresponding to the usage location. The user indicates the user of the stick vacuum cleaner 2 at the usage location, such as the resident. Note that the user item can be omitted. The layout indicates the layout of sections, such as the floor plan of the usage location. In the example of FIG. 20, the coordinates of each section (room) are shown, but the format is not limited thereto. Note that the above items are merely examples and are not limited thereto, and some of them can be omitted.

[0100] FIG. 21 is a diagram showing tracking information 194 used in Example 4. The tracking information 194 is information indicating the movement history of the stick vacuum cleaner 2. Therefore, the 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.

[0101] The map information 195 is information that indicates the state of cleaning and is created based on the layout information 193, the 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 explanation of the processing flow.

[0102] 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. The configuration of the user terminal 1 will be described below using the configuration shown in Fig. 18. This process flow has some parts in common with Example 1, so the following description will focus on the differences.

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

[0104] In step S101, the operating status detection unit 15 determines whether layout information 193 is stored in the storage unit 19. The determination may be made not only based on whether layout information 193 exists, but also based on whether layout information 193 including the position detected by the coordinate detection unit 1002 exists. In this case, the layout information 193 includes the coordinates of the location of use. As a result, if layout information 193 exists, the process proceeds to step S7. If layout information 193 does not exist, the process proceeds to step S102.

[0105] In step S102, the operating status detection unit 15 creates the corresponding layout information 193 in accordance with the user's operation on the input unit 17, and stores the layout information 193 in the storage unit 19. Then, in step S7, the operating status detection unit 15 detects the operating status of the stick vacuum cleaner 2, as in the first embodiment.

[0106] In step S103, the operation status detection unit 15 updates the coordinates and date and time in 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 cleaner head 24 is floating above the floor surface. If the cleaner head 24 is floating, it becomes difficult to suck up dust on the floor, and it can be assumed that cleaning is not being performed. For this reason, in the fourth embodiment, map information is created only when the cleaner head 24 is not floating.

[0107] As a result, if the cleaner head 24 is floating (floating), the process proceeds to step S105. If 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 technology. This step may be omitted, and step S106 may be executed instead. Floating refers to the cleaner head 24 being separated from the floor surface by a distance equal to or greater than a predetermined value.

[0108] In step S105, the operation status detection unit 15 stops the detection in step S7 and 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.

[0109] In step S106, the map information creation unit 1001 creates map information 195 using the layout information 193, the 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. 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.

[0110] 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 content are shown in FIGS. 23A and 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 in with a color corresponding to the cleaning record (trajectory). In FIG. 23A, the living / dining room (LD) is the most cleaned room, so it is filled in with black. The kitchen (K) and master bedroom (MBR) are the next most cleaned rooms after the living / dining room, so they are filled in with the next darkest color. Furthermore, the children's rooms (BR) at both ends are cleaned less than the kitchen and master bedroom, so they are displayed even lighter. The hallway (HALL), etc., is not cleaned, so it is not filled in. Here, this map information 195 is created by combining the above-mentioned coordinates and cleaning results (trajectories) with layout information 193, which is information that is not filled in (does not include trajectories).

[0111] FIG. 23B is a diagram illustrating a second example of map information 195 used in the fourth embodiment. The map information 195 in FIG. 23B is created by combining the functions of the AR information creation unit 16 in the first embodiment. For this purpose, the map information 195 in FIG. 23B displays each unit block with a color superimposed on image data corresponding to the cleaning history. This unit block is recorded as layout information 193. Using the functions of the AR information creation unit 16, the map information 195 is updated when the user changes the orientation of the user terminal 1 (photographing unit 12). This allows the user to more intuitively grasp the cleaning history. Note that such a display may be realized without using the AR information creation unit 16. In other words, the cleaning history 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 alternately or in parallel. Furthermore, the map information 195 may not only be displayed by filling in each unit section or room, but may also be displayed as line information showing the trajectory of the stick vacuum cleaner 2 .

[0112] Furthermore, in step S107, the same display as in the first embodiment may be performed, or this display may be performed by batch processing after the cleaning is completed (step S12 or later) using the map information 195 stored in the storage unit 19. Furthermore, notification may be given as needed each time (so-called real-time processing).

[0113] Similarly to the first embodiment, the completion determination is made in step S12, and if cleaning is continuing, the process proceeds to step S103. If cleaning has been completed, the process proceeds to step S108.

[0114] 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 completes the process of the fourth embodiment. In the fourth embodiment, the map information 195 is created and displayed, allowing the user to intuitively grasp the cleaning status. Furthermore, the fourth embodiment can be combined with any of the first to third embodiments. Furthermore, the cleaning record (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.

[0115] 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. Therefore, a description thereof will be omitted below. However, at least one of the configurations and information for executing functions common to the user terminal 1 and the vacuum cleaner management device 3 can be omitted.

[0116] Fig. 24 is a system configuration diagram of a vacuum cleaner management system in Example 5. In Fig. 24, compared to Fig. 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 storage unit 19. Since other configurations are the same as those in Example 2, the following description will mainly focus on the differences.

[0117] 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 be determined using the movement history (coordinates) of the stick vacuum cleaner 2. The area to be cleaned can be determined using 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.

[0118] 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. Since other configurations are the same as those in Example 2, the differences will be described below.

[0119] The map information creation module 309 is a function of the vacuum cleaner management program 305 and 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 may be implemented as a function of an integrated management application that also manages other home appliances. Note that, in Example 5 as well, the user terminal 1 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 result of the operation status detection module 307.

[0120] Next, the layout information 353, tracking information 354, and map information 355 will be described. Fig. 26 is a diagram showing the layout information 353 used in Example 5. The layout information 353 has the same items as the layout information 193 in Example 4. However, the layout information 353 includes not only information about the stick vacuum cleaner 2, but also layout information (records) for other places of use. This is because the vacuum cleaner management device 3 manages multiple users.

[0121] FIG. 27 is a diagram showing tracking information 354 used in Example 5. The tracking information 354 has the same items as the tracking information 194 in Example 4. However, the 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 because the vacuum cleaner management device 3 manages multiple users. Note that map information 355 is the same information as the map information 195 in Example 4, and is shown in FIGS. 23A and 23B. Like the layout information 353 and tracking information 354, the map information 355 is information about multiple vacuum cleaners.

[0122] Next, a process for presenting map information in Example 5 will be described. Figures 28A and 28B are flowcharts showing a process flow for presenting map information in Example 5. The following description will be given using the configuration shown in Figure 18 as the configuration of the user terminal 1 and the configuration shown in Figure 19 as the configuration of the vacuum cleaner management device 3. This process flow has some parts in common with Example 2, so the following description will focus on the differences.

[0123] 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.

[0124] In step S35, the operating status detection unit 33 determines whether layout information 353 including the position detected by the coordinate detection unit 1002 is stored in the storage unit 35. For this reason, 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.

[0125] Furthermore, in step S36, the operating status detection unit 33 creates the corresponding layout information 353 in cooperation with the user terminal 1, that is, in accordance with the user's operation on the input unit 17 of the user terminal 1, and stores the layout information 353 in the storage unit 35. Then, in step S26, the operating status detection unit 33 detects the operating status of the stick vacuum cleaner 2, as in the second embodiment.

[0126] 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 cleaner head 24 is floating above the floor surface. This is executed in the same manner as step S104 in Example 4. In other words, in Example 5 as well, map information is created only when the cleaner head 24 is not floating.

[0127] As a result, if the cleaner head 24 is floating (floating), the process proceeds to step S39. If the cleaner head 24 is not floating (not floating), the process proceeds to step S40. Whether the cleaner head 24 is floating can be determined using image processing technology, as in the fourth embodiment. This step may be omitted, and step S40 may be executed instead.

[0128] In step S39, the operation status detection unit 33 stops step S26 and coordinate detection. In the fifth embodiment, 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 continue, and the operation status detection unit 15 may invalidate this result. Then, the determination in step S38 is repeated.

[0129] Furthermore, in step S40, the map information creation unit 36 ​​creates map information 355 using the layout information 353, the 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. Furthermore, 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.

[0130] In step S106, the map information creation unit 1001 creates map information 195 using the layout information 193, the 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. 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.

[0131] In step S41, the map information creation unit 36 ​​notifies the user terminal 1 of the created map information 355 using the communication unit 31. 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 the fourth embodiment.

[0132] Also, 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 completion notification from the user terminal 1. Then, in step S43, the map information creation unit 36 ​​of the vacuum cleaner management device 3 finishes creating the map information 355. Then, in step S44, the map information creation unit 36 ​​stores the map information 355 created in step S40 in the storage unit 35, thereby executing the update process. This concludes the processing of the fifth embodiment.

[0133] In Example 5, by creating and displaying map information 355 in cooperation with a server-like vacuum cleaner management device 3, resources can be effectively utilized to display a cleaning status that the user can intuitively grasp. Furthermore, Example 5 can be combined with any of Examples 1 to 5. In particular, notification of map information (step S41) may be performed on user terminals of related parties other than the user. AR information may also be notified to the core user terminal. Furthermore, notification of map information may be performed by batch processing using map information 355 stored in the storage unit 35 after cleaning is completed (step S31 or later), or may be notified as needed (so-called real-time processing). Furthermore, the cleaning history (cleaned areas) in the vacuum cleaner management information 352 may be used as the map information 355. In this case, the map information 355 can be omitted.

[0134] 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...Signal 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

1. A vacuum cleaner management program which causes a user terminal, which is a computer used by a user of a vacuum cleaner without communication capabilities and attached to a terminal holder of the vacuum cleaner, to function as: a vacuum cleaner identification unit which determines whether the user terminal is usable based on identification information of the vacuum cleaner; an operation status detection unit which detects the operation status of the vacuum cleaner when the vacuum cleaner identification unit determines that the user terminal is usable; and an output unit which outputs the operation status.

2. A vacuum cleaner management program as described in claim 1, further comprising: the user terminal having an image capturing unit that captures an image of at least a part of the vacuum cleaner; and the vacuum cleaner identification unit that identifies the vacuum cleaner based on the image captured by the image capturing unit.

3. A vacuum cleaner management program as described in claim 2, wherein the photographing unit photographs a sign unit attached to the vacuum cleaner and having identification information for identifying the vacuum cleaner recorded thereon, and the vacuum cleaner identification unit identifies the vacuum cleaner using the identification information recorded on the photographed sign unit.

4. A vacuum cleaner management program according to claim 3, wherein the marker unit is an AR marker provided on a cleaner head of the vacuum cleaner.

5. A vacuum cleaner management program according to claim 2, wherein the photographing section photographs a vacuum cleaner head of the vacuum cleaner, and the vacuum cleaner identification section identifies the vacuum cleaner using the shape of the photographed vacuum cleaner head.

6. A vacuum cleaner management program according to claim 5, wherein the vacuum cleaner head is used as an AR marker.

7. A vacuum cleaner management program as described in claim 2, further comprising: causing the user terminal to function as an AR information creation unit that creates an AR image according to the operation status detected by the operation status detection unit; the photographing unit photographs the area being cleaned by the vacuum cleaner; the operation status detection unit identifies a trajectory moved by a cleaner head of the vacuum cleaner; and the AR information creation unit superimposes the trajectory on an image of the cleaning area to create the AR image.

8. A vacuum cleaner management system that is used by a user of a vacuum cleaner that does not have a communication function and that 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 vacuum cleaner is usable, and an output unit that outputs the operation status.

9. A vacuum cleaner management system as described in claim 8, further comprising: the user terminal having an image capturing unit that captures an image of at least a portion of the vacuum cleaner; and the vacuum cleaner identification unit that identifies the vacuum cleaner based on the image captured by the image capturing unit.

10. A vacuum cleaner management system as described in claim 9, wherein the photographing unit photographs a sign unit attached to the vacuum cleaner and recording identification information for identifying the vacuum cleaner, and the vacuum cleaner identification unit identifies the vacuum cleaner using the identification information recorded on the photographed sign unit.

11. A vacuum cleaner management system according to claim 10, wherein the marker unit is an AR marker provided on a cleaner head of the vacuum cleaner.

12. A vacuum cleaner management system according to claim 9, wherein the photographing unit photographs a vacuum cleaner head of the vacuum cleaner, and the vacuum cleaner identification unit identifies the vacuum cleaner using the photographed shape of the vacuum cleaner head.

13. The vacuum cleaner management system according to claim 12, wherein the vacuum cleaner head is used as an AR marker.

14. A vacuum cleaner management system as described in claim 9, further comprising an AR information creation unit that creates an AR image according to the operation status detected by the operation status detection unit, wherein the photographing unit photographs the area cleaned by the vacuum cleaner, the operation status detection unit identifies a trajectory of movement of a cleaner head of the vacuum cleaner, and the AR information creation unit superimposes the trajectory on an image of the cleaning area to create the AR image.

Images