Notification systems, notification methods, and notification programs

Abstract

This disclosure provides a notification system that enables users to share equipment while suppressing competition among users. [Solution] The notification system in this disclosure comprises a plurality of terminal devices and a server device that acquires operating information of devices from devices that terminate operation after completing predetermined operating procedures, wherein the terminal devices and the server device are connected via a network, and when the server device receives a notification setting from a terminal device, it notifies the terminal device that received the notification setting of the operating status of the devices based on the operating information at a predetermined timing.

Description

Technical Field

[0001] The present disclosure relates to a notification system, a notification method, and a notification program.

Background Art

[0002] Patent Document 1 discloses a technology that prepares laundry equipment capable of making a reservation for operation in a coin laundry or the like, eliminates competition between users by making a reservation for operation, and enables the use of the laundry equipment.

Prior Art Documents

Patent Documents

[0003]

Patent Document 1

Summary of the Invention

Problems to be Solved by the Invention

[0004] The present disclosure provides a notification system, a notification method, and a notification program that can suppress competition between users and share equipment.

Means for Solving the Problems

[0005] The notification system in the present disclosure includes a plurality of terminal devices and a server device that acquires operation information of the device from the device that ends the operation when a predetermined operation content is completed, and the terminal device and the server device are connected via a network. The server device notifies the terminal device that has received the notification setting of the operating status of the device based on the operation information at a predetermined timing when receiving the notification setting from the terminal device.

[0006] Furthermore, the notification method in this disclosure involves a server device that connects to multiple terminal devices via a network and acquires operating information of equipment from equipment that terminates operation after completing predetermined operational tasks. When the server device receives a notification setting from the terminal device, it notifies the terminal device that received the notification setting of the operating status of the equipment based on the operating information at a predetermined timing.

[0007] Furthermore, the notification program in this disclosure connects to multiple terminal devices via a network and, upon receiving notification settings from a terminal device, causes a server device that has received notification settings to notify the terminal device that received the notification settings of the operating status of the equipment based on the operating information, at a predetermined timing. The server device obtains operating information of equipment from equipment that terminates operation after completing predetermined operating procedures. [Effects of the Invention]

[0008] The notification system, notification method, and notification program described in this disclosure enable the sharing of equipment while suppressing conflicts among users. [Brief explanation of the drawing]

[0009] [Figure 1] An explanatory diagram illustrating the outline of the notification system according to Embodiment 1. [Figure 2] Diagram illustrating the setting and registration of a room according to Embodiment 1 [Figure 3] An explanatory diagram illustrating notifications to terminal devices in the notification system according to Embodiment 1. [Figure 4] An explanatory diagram illustrating an example of a viewable device according to Embodiment 1. [Figure 5] Block diagram showing an example of the functional configuration of the notification system according to Embodiment 1. [Figure 6] Block diagram showing an example of a computer configuration according to Embodiment 1 [Figure 7] Sequence diagram showing an example of operation of the notification system according to Embodiment 1. [Figure 8] An explanatory diagram illustrating an example of notification settings according to Embodiment 1. [Figure 9] A diagram showing an example of notification to a terminal device according to Embodiment 1. [Figure 10] A diagram showing an example of notification to a terminal device according to Embodiment 1. [Figure 11] A diagram showing an example of notification to a terminal device according to Embodiment 1. [Modes for carrying out the invention]

[0010] (Knowledge and other information that formed the basis of this disclosure) At the time the inventors conceived of this disclosure, there was a technology for equipment such as laundry machines that allowed users to schedule their runs, thereby eliminating competition among users and enabling the sharing of the equipment. The device terminates operation after performing the predetermined operating procedures set before operation. However, in devices such as washing machines, the termination time may vary depending on the operating conditions, even with the same operating settings. Therefore, the inventors discovered that when multiple users in different households use a device whose termination time varies, it is difficult to prevent conflicts simply by scheduling the operation. To solve this problem, the inventors have arrived at the subject matter of this disclosure.

[0011] Therefore, this disclosure provides a notification system, notification method, and notification program that enable users to share equipment while suppressing competition among users, without requiring the provision of equipment for making reservations for driving.

[0012] The embodiments will be described in detail below with reference to the drawings. However, some unnecessarily detailed explanations may be omitted. For example, detailed explanations of already well-known matters or redundant explanations of substantially identical configurations may be omitted. The attached drawings and the following description are provided to enable those skilled in the art to fully understand this disclosure and are not intended to limit the subject matter described in the claims.

[0013] In the description of the present disclosure, alphanumeric characters etc. may be appended to the end of reference numerals to distinguish and describe components having the same or similar functions. Also, in the description of the present embodiment, the alphanumeric characters etc. at the end of reference numerals may be omitted to describe a plurality of components having the same or similar functions without distinction. For example, in FIG. 1, rooms 2a, 2b, 2c are referred to as room 2 when not particularly distinguished. Also, users 6a, 6b,... are referred to as user 6 when not particularly distinguished. Also, terminal devices 7a, 7b... are referred to as terminal device 7 when not particularly distinguished.

[0014] Also, in the description of the present disclosure, explanations may be made using general abbreviations. For example, LAN is an abbreviation for Local Area Network, PC is an abbreviation for Personal Computer, app is an abbreviation for application program, and API is an abbreviation for Application Programming Interface. Also, CPU is an abbreviation for Central Processing Unit, RAM is an abbreviation for Random Access Memory, ROM is an abbreviation for Read Only Memory, HDD is an abbreviation for Hard Disk Drive, and SSD is an abbreviation for Solid State Drive. Also, DVD is an abbreviation for Digital Versatile Disk, and USB is an abbreviation for Universal Serial Bus. Also, IH is an abbreviation for Induction Heating, and SNS is an abbreviation for Social Networking Service.

[0015] (Embodiment 1) [1. Configuration] [1-1. Overview of Notification System] FIG. 1 is an explanatory diagram for explaining the overview of the notification system according to Embodiment 1. As shown in FIG. 1, in the notification system 1, a plurality of laundry processing devices 3, a laundry sharing server 5 that manages these laundry processing devices 3, and terminal devices 7 are connected via a network 8 such as the Internet or a LAN.

[0016] The garment processing device 3 is a device that performs a washing operation including each step related to washing clothes (filling with water, washing, rinsing, spinning, drying, etc.) and washes clothes placed in the washing tub. The garment processing device 3 is an example of a device that performs an operation including predetermined steps. The garment processing device 3 may be a so-called household washing machine or household dryer (hereinafter collectively referred to as household washing machine, etc.). Household washing machines, etc. are generally not intended to be used by multiple users from different households, and therefore often do not have a user authentication function as a main unit function to authenticate the user who will use the washing cycle. Consequently, it is difficult for the main unit of a household washing machine, etc. to restrict use by users other than the reserved user by unlocking the door when the reserved user is authenticated. Furthermore, because the main unit of a household washing machine, etc. does not have a user authentication function, it is not possible to identify the user who performed the washing cycle, making it difficult to set up notifications for a specific user who performed the washing cycle. In this embodiment, the garment processing device 3 is a household washing machine, etc., and the laundry share server 5 is configured to manage the garment processing device 3, which is a household washing machine, etc.

[0017] Each garment processing device 3 is installed in a room 2 accessible to user 6 and is shared by user 6. For example, the garment processing devices 3 are installed in rooms 2a to 2c in the common areas of each floor (odd-numbered or even-numbered floors) of an apartment building, condominium, or house. The apartment building, condominium, or house may be a so-called shared house. In this embodiment, each garment processing device 3 is shared by multiple users from different households.

[0018] Rooms 2a to 2c may be provided in multiple locations on each floor, or they may be distributed across multiple buildings. For example, rooms 2a to 2c may be located in each wing of an apartment building or condominium (e.g., East Wing, West Wing, etc.).

[0019] Each garment processing device 3 has users 6a, who are administrators responsible for the maintenance and management of the garment processing device 3, and users 6b, 6c, 6d, etc., who are general users who only use the garment processing device 3.

[0020] For example, user 6a, acting as an administrator, is the owner of the apartment or condominium where Room 2 is located. Users 6b, 6c, 6d, etc., acting as general users, are residents of the same apartment or condominium where Room 2 is located.

[0021] User 6a, acting as an administrator, connects to the laundry share server 5 via a terminal device 7a such as a smartphone or PC that they own, and manages each garment processing device 3.

[0022] Users 6b, 6c, 6d, etc., acting as general users, connect to the laundry share server 5 via their own smartphones, PCs, or other terminal devices 7b, 7c, 7d, etc., when using each garment processing device 3, and check the operating status of each garment processing device 3. In addition, if users 6b, 6c, 6d, etc., as general users, set up notifications regarding each garment processing device 3 on the laundry share server 5, they will receive those notifications from the laundry share server 5 via their terminal devices 7b, 7c, 7d, etc.

[0023] User 6a, acting as the administrator, pre-configures information about each garment processing device 3 installed in each room 2 on the laundry share server 5 via terminal device 7a. Specifically, information such as identification information (device ID, communication address, etc.), administrator information (administrator's user ID, etc.), affiliated group (group ID indicating the room 2 in which it is installed, etc.), installation location (floor level of the room 2 in which it is installed, the location of the room 2, etc.), and specifications (types of processes that can be executed, and the capabilities of the processes that can be executed) are set on the laundry share server 5 as configuration information for each garment processing device 3.

[0024] Users 6b, 6c, 6d, etc., as general users, register in advance with the laundry share server 5 the group to which they belong, i.e., the clothing processing device 3 they will be using, via terminal devices 7b, 7c, 7d, etc. Specifically, identification information (user ID) and user information (administrator / general user type, gender, age, address, communication address, etc.), along with the group ID indicating room 2, are registered with the laundry share server 5 as user 6's registration information.

[0025] Figure 2 is an explanatory diagram illustrating the setup and registration of Room 2 according to Embodiment 1. As shown on the left side of Figure 2 with respect to the vertical lines in the figure, user 6a, acting as the administrator, pre-configures the information of each garment processing device 3 installed in Rooms 2a, 2b, and 2c in the Laundry Share Server 5 via terminal device 7a. As a result, the Laundry Share Server 5 associates each garment processing device 3 with Rooms 2a, 2b, and 2c, corresponding to the installation status of each garment processing device 3.

[0026] Furthermore, as shown on the right side of Figure 2 with the vertical lines in the diagram as a reference, general users 6b, 6c, 6d… register their user information and other details, along with the rooms 2a, 2b, and 2c they will use, with the laundry share server 5 via terminal devices 7b, 7c, 7d…. For example, user 6b registers rooms 2a and 2b, which are close to their room and convenient, with the laundry share server 5 using terminal device 7b. Similarly, user 6c registers rooms 2b and 2c as rooms they will use using terminal device 7c. User 6d also registers rooms 2a and 2c as rooms they will use using terminal device 7d. By pre-registering in this way, users 6b, 6c, 6d… can receive only notifications regarding the clothing processing device 3 for the rooms they have registered, and avoid receiving unnecessary notifications such as notifications regarding the clothing processing device 3 for unregistered rooms.

[0027] The laundry share server 5 is an example of a server device that acquires operating data indicating the operating status of each garment processing device 3 and manages the operating status of each garment processing device 3. Specifically, the laundry share server 5 acquires operating data from each garment processing device 3 through notifications from each garment processing device 3 or by periodic polling of each garment processing device 3. The laundry share server 5 stores the acquired operating data in association with the identification information (device ID) of each garment processing device 3.

[0028] In response to a viewing request from the terminal device 7, the laundry share server 5 generates a web page displaying the operating status of each garment processing device 3 it manages, based on the operating data of each device, and sends it to the requesting device. As a result, the terminal device 7 can check the operating status of each garment processing device 3 on the web page.

[0029] Furthermore, the laundry share server 5 determines whether a predetermined event (such as operation completion or an abnormality occurring) has occurred in each garment processing device 3 based on the operating data of each garment processing device 3 it manages. If the laundry share server 5 determines that a predetermined event has occurred, it notifies the terminal device 7 of the garment processing device 3 in which the event occurred and the details of the event. Specifically, the laundry share server 5 notifies the terminal device 7 of the user 6 who has registered for notification of the garment processing device 3 in which the event occurred and the details of the event. This notification is sent to the user 6's terminal device 7 via a pre-registered chat room, for example, using the notification message function (notification message API) of the LINE® app.

[0030] Figure 3 is an explanatory diagram illustrating notifications to the terminal device 7 in the notification system 1 according to Embodiment 1. As shown in Figure 3, the laundry share server 5 acquires and manages operating data indicating the operating status of each garment processing device 3.

[0031] User 6, using the terminal device 7, checks notifications from the laundry share server 5 and the operating status of each garment processing device 3 within the registered room 2 via the portal screen 700 of the talk room opened through user registration, etc.

[0032] Specifically, the portal screen 700 displays various announcements and notifications 701a to 701c from the laundry share server 5, such as washing completion / errors in the clothing processing device 3, in chronological order from top to bottom. This allows user 6 to view notifications 701a to 701c from the laundry share server 5 in chronological order.

[0033] Additionally, the portal screen 700 displays operation buttons 702a for checking the operating status and setting notifications for each garment processing device 3, and operation buttons 702b for checking and registering Room 2.

[0034] By operating the operation button 702b on the portal screen 700, the terminal device 7 displays the group screen 720 for confirming and registering the group (registered room 2) associated with user 6. Specifically, the terminal device 7 queries the laundry share server 5 for the group associated with user 6. The laundry share server 5 identifies the room 2 set up in association with user 6's identification information (user ID) and sends it to the terminal device 7. As a result, the terminal device 7 displays the group associated with user 6 in the group list on the group screen 720.

[0035] If there are no groups associated with user 6 (as shown in the example), nothing will be displayed in the group list on the group screen 720. Additionally, a registration button 721 for creating a new group will be displayed on the group screen 720.

[0036] Upon operation of the registration button 721 on the portal screen 700, the terminal device 7 obtains the identification information (group ID) of the group (room 2 to be registered) and displays the scan screen 730 for group registration. On the scan screen 730, the terminal device 7 reads the group identification information from the image captured by the built-in camera and registers the group for use.

[0037] Specifically, terminal device 7 reads the group registration code 731 included in the image captured by the built-in camera and obtains the group identification information (group ID) included in the registration code 731. Then, terminal device 7 notifies the laundry share server 5 of the obtained group identification information. Laundry share server 5 manages the identification information (group ID) notified by terminal device 7 by linking it to the user's identification information (user ID). Laundry share server 5 may issue a registration code 731 that includes the group ID set by user 6a. User 6a may print the issued registration code 731 and post it in the room. This allows user 6a to set up the room according to the actual conditions of the building and common areas, and also supports smooth group registration for user 6.

[0038] By operating the operation button 702a on the portal screen 700, the terminal device 7 requests the laundry share server 5 to display a room screen 710 that allows the user to check the operating status and notification settings of each garment processing device 3 in the registered room 2. Upon receiving this request, the laundry share server 5 checks the registration information of user 6 linked to the talk room and identifies the room 2 in which the user registration is set. Next, based on the operating data of each garment processing device 3 in the identified room 2, the laundry share server 5 generates display data that displays the operating status of each garment processing device 3 in room 2 as a website and sends it to the terminal device 7. This display data displays a room screen 710 on the terminal device 7 that lists the device information 711a to 711c of each garment processing device 3 in the registered room 2. This room screen 710 allows user 6 to easily check the status of each garment processing device 3 in the registered room 2.

[0039] Figure 4 is an explanatory diagram illustrating an example of viewable equipment according to Embodiment 1. As shown in Figure 4, user 6b who has registered to use rooms 2a and 2b can view the status of the equipment (clothing processing device 3) installed in rooms 2a and 2b via the room screen 710. Similarly, user 6c who has registered to use rooms 2b and 2c can view the status of the equipment (clothing processing device 3) installed in rooms 2b and 2c via the room screen 710. If multiple rooms 2 are registered, the user may be prompted to select the room 2 to view before the room screen 710 is displayed.

[0040] Returning to Figure 3, the equipment information 711a to 711b on the room screen 710 includes items such as the operating status of each garment processing device 3, the remaining time until operation is complete, and whether or not notification settings are configured.

[0041] The "Operating Status" section displays the current status of the garment processing device 3 (operating status, presence of abnormalities, availability, etc.). For example, if not in operation, it will show "Available," and if in operation, the current operating stage will be displayed in the "Operating Status" section, such as "Washing," "Rinsing," "Spinning," or "Drying." If an abnormality (error) occurs in the garment processing device 3, "Abnormality Found" will be displayed in the "Operating Status" section, along with the corresponding error number. Furthermore, if the garment processing device 3 is set to unavailable for maintenance or other purposes, it will be displayed in the "Operating Status" section as unavailable, such as "Under Maintenance."

[0042] The "Notification Settings" section indicates whether notifications are sent when a predetermined event (such as completion of operation or an abnormality) occurs in each garment processing device 3. An abnormality may be something that can be addressed by the user, such as forgetting to close the door, uneven distribution of clothes in the washing tub, a clogged drying filter, or a water supply abnormality (forgetting to open the water supply valve). Whether or not to send notifications is set in the laundry share server 5 and linked to the user's identification information (user ID) in each garment processing device 3. For example, if the user's identification information (user ID) is linked, notifications are set to "enabled," and if there is no such link, notifications are set to "disabled." User 6 sets whether or not to send notifications by operating the toggle button in this section.

[0043] The laundry share server 5 manages the garment processing device 3 that has been set to have notification enabled by the operation of this toggle button, by associating it with the user's identification information (user ID). Then, when a predetermined event (such as completion of operation or occurrence of an abnormality) occurs in the garment processing device 3, the laundry share server 5 notifies the terminal device 7 of user 6, to which the user's identification information (user ID) is associated, of the event that occurred.

[0044] Specifically, the laundry share server 5 sends a notification 701 corresponding to the event that occurred via the portal screen 700 of the aforementioned talk room. This notification 701 allows the user 6 to easily check the event that occurred in the garment processing device 3 for which notification settings have been configured.

[0045] [1-1-2. Functional Configuration of the Notification System] Here, the functional configuration of the notification system 1 will be described in detail. Figure 5 is a block diagram showing an example of the functional configuration of the notification system 1 according to Embodiment 1. As shown in Figure 5, the notification system 1 includes a clothing processing device 3, an operation information management server 4, a laundry share server 5, and a terminal device 7.

[0046] The operation information management server 4 periodically polls each garment processing device 3 based on the communication address and other information included in the identification information of each garment processing device 3, and obtains operation data 41 from each garment processing device 3. This operation data 41 is an example of operation information. The operation information management server 4 may also obtain operation data 41 through voluntary notifications from each garment processing device 3. The operation information management server 4 manages the obtained operation data 41 together with the device ID included in the identification information of each garment processing device 3. When there is an update to the operation data 41, or upon request, the operation information management server 4 provides (transmits) the operation data 41 of each garment processing device 3 under its management to the laundry share server 5.

[0047] The laundry share server 5 includes a website processing unit 51, a communication and notification processing unit 52, an equipment and user management unit 53, and a notification setting management unit 54.

[0048] The website processing unit 51 is a processing unit that generates and returns website display data in response to a website viewing request from the terminal device 7.

[0049] Specifically, the website processing unit 51 receives a request from the terminal device 7 to view the room screen 710, which allows users 6 to check the operating status and notification settings of each garment processing device 3 within Room 2 that they have registered to use. Upon receiving this request, the website processing unit 51 checks the user management information 532 based on the user's identification information (user ID) linked to the user's chat room and identifies Room 2, which is registered as a group ID. Next, the website processing unit 51 obtains the operating data 41 of the garment processing device 3 linked to the identified Room 2's group ID from the equipment management information 531. Based on the obtained operating data 41, the website processing unit 51 generates display data to show the operating status of each garment processing device 3 within Room 2 as a website and sends it to the terminal device 7.

[0050] The communication and notification processing unit 52 is a processing unit that handles communication with external devices such as the driving information management server 4 and terminal devices 7 via the network 8, as well as processing various notifications to the terminal devices 7.

[0051] The communication and notification processing unit 52 monitors the operation data 41 of the equipment management information 531 and determines whether a predetermined event has occurred in each garment processing device 3. The events to be notified include completion of operation and occurrence of errors (abnormalities).

[0052] When a predetermined event occurs, the communication and notification processing unit 52 sends a notification corresponding to the event to the terminal device 7 of the user 6 who has set up notifications for the clothing processing unit 3 where the event occurred. Therefore, by setting up notifications for each clothing processing unit 3, the user 6 can confirm that a predetermined event has occurred in the clothing processing unit 3.

[0053] Specifically, the communication and notification processing unit 52 refers to the notification setting management information 541 based on the identification information (device ID) of the clothing processing device 3 where the event occurred, and identifies the user 6 who set the notification. If there is no user 6 who set the notification, the communication and notification processing unit 52 sends a notification to terminal devices 7, such as a monitor device, located in room 2.

[0054] If there is a user 6 who has set up notifications, the communication and notification processing unit 52 sends a notification to the terminal device 7 of the user 6 who has set up notifications, at a predetermined time, corresponding to the event that occurred. More specifically, the communication and notification processing unit 52 sends a notification 701 corresponding to the event that occurred to the terminal device 7 of the user 6's identification information (user ID) via the portal screen 700 of the talk room described above. This allows user 6 to easily know about events that have occurred in the clothing processing device 3 for which notifications have been set.

[0055] Furthermore, the communication and notification processing unit 52 sends notifications in order of user 6, starting with the first user registered in the settings, at different timings, corresponding to events that occur in the clothing processing unit 3. This prevents notification system 1 from having conflicting notifications among multiple users 6.

[0056] For example, the communication and notification processing unit 52 sends a notification to the terminal device 7 of user 6, who is the i-th user in the configuration registration order, regarding an event that occurred in the clothing processing device 3. Then, at a later timing (second timing) than the notification timing (first timing) to user i, the communication and notification processing unit 52 sends a notification to the terminal device 7 of user i+1, who is the (i+1)th user, regarding an event that occurred in the clothing processing device 3.

[0057] Furthermore, the communication and notification processing unit 52 monitors the operation data 41 of the garment processing device 3 where the event occurred, and determines whether or not operation of the garment processing device 3 started within a predetermined time from the first timing. After the communication and notification processing unit 52 sends a notification to the terminal device 7 of the i-th user 6 corresponding to the event that occurred in the garment processing device 3, if operation of the garment processing device 3 does not start within the predetermined time, it sends a notification to the terminal device 7 of the (i+1)th user 6. In this way, the notification system 1 can support the sharing of the garment processing device 3 so that it can be operated efficiently by multiple users 6.

[0058] Furthermore, at the second timing, the communication and notification processing unit 52 sends a notification to the terminal device 7 of the i-th user 6 corresponding to the notification to the (i+1)th user 6. Specifically, the communication and notification processing unit 52 sends a notification to the i-th user 6 indicating that, as a result of notifying the (i+1)th user 6, the priority right to use the clothing processing device 3 has been transferred to the (i+1)th user 6. In this way, the notification system 1 can prevent problems regarding the use of the clothing processing device 3 among multiple users 6.

[0059] Furthermore, if operation of the garment processing device 3 is started within a predetermined time from the first timing, the communication and notification processing unit 52 assumes that the operation was performed by the i-th user 6 based on the notification at the first timing. Therefore, if operation of the garment processing device 3 is started within a predetermined time from the first timing, the communication and notification processing unit 52 notifies the terminal device 7 of the i-th user 6 of the completion of operation of the garment processing device 3 based on the completion of operation of the garment processing device 3. As a result, the notification system 1 can confirm the completion of operation by the i-th user 6 who started operation of the garment processing device 3.

[0060] Furthermore, if operation of the garment processing device 3 is started within a predetermined time from the first timing, the communication and notification processing unit 52 notifies the terminal device 7 of the (i+1)th user 6 that the garment processing device 3 is available based on the completion of operation of the garment processing device 3. This allows the notification system 1 to confirm that the (i+1)th user 6 has finished operating the garment processing device 3 and that the garment processing device 3 is now available.

[0061] The Equipment / User Management Unit 53 is a processing unit that manages equipment management information 531 and user management information 532. Specifically, based on the settings registered by user 6a as an administrator, the Equipment / User Management Unit 53 manages various information (group ID, operation data 41, etc.) related to each garment processing device 3 in the Equipment Management Information 531 by linking it to identification information (equipment ID). In addition, the Equipment / User Management Unit 53 acquires the operation data 41 of each garment processing device 3 from the operation information management server 4 and manages it in the Equipment Management Information 531 by linking it to identification information (equipment ID).

[0062] Furthermore, the equipment / user management unit 53 manages various information about each user 6 (user information, group ID) in the user management information 532, linking it to the user 6's identification information (user ID) based on user registration by user 6. Here, the registered group ID item shows the identification information of the group (room 2) that user 6 has registered to use.

[0063] The notification setting management unit 54 is a processing unit that manages the notification setting management information 541. The notification setting management information 541 manages information for each clothing processing device 3 (registered user (1st), registered user (2nd)...registered user (Nth)) and links it to the identification information (device ID) of the clothing processing device 3.

[0064] Here, in the registered user section of the notification setting management information 541, the identification information (user ID) of the user 6 who set up notifications for the clothing processing device 3 indicated by the device ID is shown in the order of setting registration.

[0065] Terminal device 7 has an application 71 such as the LINE application for notifications and viewing as described above. Terminal device 7 displays screens such as the portal screen 700, room screen 710, group screen 720, and scan screen 730 as described above through processing by this application 71.

[0066] The various functions of the garment processing device 3, operation information management server 4, laundry share server 5, and terminal device 7 described above can be realized through a computer configuration. Here, an example of a computer configuration will be described.

[0067] Figure 6 is a block diagram showing an example of a computer configuration according to Embodiment 1. As shown in Figure 6, the computer 1000 has a CPU 1010, ROM 1020, RAM 1030, storage unit 1040, I / F unit 1050, input unit 1060, and output unit 1070, and each of these units is connected via a bus 1080.

[0068] The CPU 1010 is an example of a processor that oversees and controls the operation of the computer 1000. The ROM 1020 stores boot programs and initial settings. The RAM 1030 functions as the work area for the CPU 1010. The memory unit 1040 is a storage device such as an HDD or SSD, and stores memory units 1040 related to the processing of various functional units. In the case of the laundry share server 5, the memory unit 1040 stores the notification program 1041.

[0069] The I / F unit 1050 is a communication interface that connects various parts within the device (e.g., drive unit, sensors, etc.) and external devices via the network 8. For example, in the computer 1000 within the garment processing device 3, the water supply valve, drain valve, drive motor, supply unit that supplies detergent etc. to the washing tub, and various sensors that measure the temperature and water level inside the washing tub are all connected to the computer 1000 via the I / F unit 1050.

[0070] The input unit 1060 is an input device that accepts various input operations such as keyboards and touch panels. The output unit 1070 is a display device such as an LCD or an audio output device such as a speaker, and outputs information in display and audio formats under the control of the CPU 1010.

[0071] The CPU 1010 of the laundry share server 5 reads the notification program 1041, loads it into the work area of ​​RAM 1030, and executes it sequentially, thereby executing processing related to various functional units such as the website processing unit 51, the communication / notification processing unit 52, the equipment / user management unit 53, and the notification setting management unit 54. In this way, the computer 1000 realizes various functional units such as the website processing unit 51, the communication / notification processing unit 52, the equipment / user management unit 53, and the notification setting management unit 54.

[0072] The notification program 1041 is provided as an installable or executable file recorded on a computer-readable recording medium such as a DVD or other optical recording medium, a USB memory stick, or a semiconductor memory device such as an SSD. Alternatively, the notification program 1041 may be stored on a computer connected to a network such as the Internet and provided or distributed by downloading it via the network. Furthermore, the notification program 1041 may be pre-installed in a ROM 1020 or the like.

[0073] [1-2. Operation] Next, the operation of the notification system 1 will be described. Figure 7 is a sequence diagram showing an example of the operation of the notification system 1 according to Embodiment 1. In the operation example described with reference to Figure 7, it is assumed that all settings by user 6a as an administrator, and user registration and notification settings for the clothing processing device 3 by users 6b and 6c as general users have already been completed. Furthermore, regarding the notification settings for the clothing processing device 3 by users 6b and 6c, the order of settings (registration) is assumed to be user 6b, then 6c. In addition, application 71 in the sequence diagram represents the application for user 6b's terminal device 7b, and the illustration of the application for user 6c's terminal device 7b is omitted.

[0074] As shown in Figure 7, user 6b opens the website (room screen 710) from the terminal device 7b (S1) and requests the status of the garment processing device 3 for room 2, which user 6b has registered, from the laundry share server 5 (S2). In response to this request, the website processing unit 51 of the laundry share server 5 requests the operation information management server 4 for operation data 41 of the garment processing device 3 in order to obtain the status of the garment processing device 3 for room 2, which user 6b has registered (S3). In response to this request, the operation information management server 4 returns the status of the garment processing device 3 (operation data 41) for room 2, which user 6b has registered, to the laundry share server 5 (S4). Then, the communication and notification processing unit 52 of the laundry share server 5 generates display data that shows the operating status of each garment processing device 3 in room 2 based on the acquired operation data 41, and displays it on the website (room screen 710) (S5).

[0075] This section describes the procedure for setting up notifications for the garment processing device 3 on this website (room screen 710), specifically procedure A1. In procedure A1, user 6b selects a washing machine for which they want to set up notifications from the device information 711a to 711c of each garment processing device 3 displayed on the website (room screen 710), and sets the notification for the selected washing machine (S10). Then, the notification setting management unit 54 of the laundry share server 5 sets the notification for the garment processing device 3 selected by user 6b in S10 in the notification setting management information 541 (S11).

[0076] Specifically, the notification setting management unit 54 sets the identification information (user ID) of user 6b in the registered user item linked to the identification information (device ID) of the garment processing device 3 that has been set for notification in the notification setting management information 541. Here, if the registration of up to the ith user has been completed in the registered user item, the notification setting management unit 54 sets the identification information (user ID) of user 6 in the i+1 position.

[0077] Figure 8 is an explanatory diagram illustrating an example of notification settings according to Embodiment 1. As shown in Figure 8, the room screen 710 is provided with notification setting buttons 712a to 712c for setting notifications in the item fields of the device information 711a to 711c of each garment processing device 3 installed in the room 2.

[0078] User 6 switches the notification settings for the clothing processing device 3 corresponding to the device information 711a to 711c by toggling the notification setting buttons 712a to 712c ON / OFF. For example, in the illustrated example, by turning the notification setting button 712a ON, notifications are set for clothing processing device 3 "NO.1" corresponding to device information 711a.

[0079] Furthermore, the room screen 710 may also be provided with a notification setting button 713 for setting up notifications when any of the garment processing devices 3 installed in Room 2 become "available" (not in operation). By turning on this notification setting button 713, User 6 can set up notifications for all garment processing devices 3 in Room 2 at once, so that a notification is sent when any of the garment processing devices 3 become "available" (not in operation).

[0080] Returning to Figure 7, we will now explain A2 in the case where the washing is completed in the garment processing device 3 for which user 6b has set up notifications.

[0081] When the laundry is completed in the garment processing device 3, in A2, the operation information management server 4 updates the operation status in the operation data 41 to completed (S20). Then, the equipment / user management unit 53 of the laundry share server 5 receives notification from the operation information management server 4 of the operation data 41 whose operation status has been updated to completed, along with the equipment ID of the garment processing device 3, and updates the operation data 41 in the equipment management information 531 associated with that equipment ID (S21).

[0082] Next, the communication and notification processing unit 52 of the laundry share server 5 sends a message of completion of operation to the terminal device 7b of user 6b who has set up notifications for the garment processing device 3 where an event (completion of operation) has occurred, based on the operation data 41 in the device management information 531 linked to the device ID (S22). The application 71 on terminal device 7b displays the notification on the portal screen 700 and notifies user 6b.

[0083] Upon receiving notification that the garment processing device 3 has completed its operation, user 6b understands that the garment processing device 3 is now inactive (not running). Therefore, user 6b can start a washing or drying operation using the inactive garment processing device 3.

[0084] The communication and notification processing unit 52 of the laundry share server 5 monitors the operation data 41 of the garment processing device 3. If the garment processing device 3 starts operating within a certain time after the operation completion notification, it is assumed that the user 6b who received the notification started the operation. Therefore, if the garment processing device 3 starts operating within a certain time after the operation completion notification, the communication and notification processing unit 52 of the laundry share server 5 sets up an automatic notification (S24) so ​​that the user 6b who sent the notification is notified of the completion of the operation, etc. Specifically, the communication and notification processing unit 52 uses the registered user (first) item in the notification setting management information 541 as the user ID of user 6b. The certain time between the operation completion notification and the start of operation of the garment processing device 3 may be set in advance by user 6, for example, 5 minutes or 10 minutes.

[0085] The communication and notification processing unit 52 of the laundry share server 5, based on the operation data 41 of the garment processing device 3, determines that the operation of the garment processing device 3 has finished, as per the automatic notification settings described above, and notifies the user 6b's terminal device 7b of the completion of the operation. This allows user 6b to easily confirm the completion of operations such as washing and drying using the now-available garment processing device 3. In this embodiment, the timing at which user 6b receives the notification is the same as the timing at which user 6 receives the notification.

[0086] Next, we will explain A3, which occurs when an abnormality (error) occurs in the garment processing device 3 for which notification settings have been configured. In A3, when an abnormality (error) occurs in the garment processing device 3, the operation information management server 4 updates the operation status in the operation data 41 to an error (S30). Then, the equipment / user management unit 53 of the laundry share server 5 receives notification from the operation information management server 4 of the operation data 41 whose operation status has been updated to an error, along with the equipment ID of the garment processing device 3, and updates the operation data 41 in the equipment management information 531 associated with that equipment ID (S31).

[0087] Next, the communication and notification processing unit 52 of the laundry share server 5 sends an error message for the garment processing device 3 to the terminal device 7b of user 6b who has set up notifications for the garment processing device 3 where an event (error) has occurred, based on the operation data 41 in the device management information 531 linked to the device ID (S32). The application 71 on terminal device 7b displays the error message for the garment processing device 3 on the portal screen 700 and notifies user 6b (S33).

[0088] Next, we will explain case A4, in which users 6b and 6c set up notifications for the garment processing device 3, and when the laundry is completed in the garment processing device 3, notifications are sent in the order they were set (user 6b → user 6c). In case A4, user 6b selects a specific garment processing device 3 via the room screen 710 (website) and sets up notifications for the laundry share server 5 (S40, S41). At this point, the notification setting management unit 54 of the laundry share server 5 registers the notification settings for the garment processing device 3 in the notification setting management information 541 in order of priority (S42).

[0089] For example, if notification settings are made for the same garment processing device 3 in the order of user 6b → user 6c, the notification setting management unit 54 registers user 6b's identification information (user ID) first and user 6c's identification information (user ID) second in the notification setting management information 541 for the identification information (device ID) of the garment processing device 3.

[0090] Next, when the operation of the garment processing device 3 is completed, the operation information management server 4 updates the operation status in the operation data 41 to completed (S43). Then, the equipment / user management unit 53 of the laundry share server 5 receives notification from the operation information management server 4 of the operation data 41 whose operation status has been updated to completed, along with the identification information (equipment ID) of the garment processing device 3, and updates the operation data 41 in the equipment management information 531 linked to that identification information (S44).

[0091] Next, the communication and notification processing unit 52 of the laundry share server 5 identifies users 6b and 6c who have set up notifications for the garment processing device 3 when an event (completion of operation) has occurred, based on the operation data 41 in the device management information 531 linked to the identification information (device ID) of the garment processing device 3. At this point, the communication and notification processing unit 52 of the laundry share server 5 sends an operation completion message to the terminal device 7b of user 6b, who is the first to register (S45). The application 71 on terminal device 7b displays the notification on the portal screen 700 and notifies user 6b (S46).

[0092] User 6b, upon receiving notification that the garment processing device 3 has completed its operation, will understand that the garment processing device 3 is not in operation. However, Case A4 illustrates the situation where user 6b does not start the garment processing device 3 within a certain period of time (S47) and leaves it as is.

[0093] The communication and notification processing unit 52 of the laundry share server 5 monitors the operation data 41 of the garment processing device 3. If the garment processing device 3 is not started within a certain period of time after notification of completion of operation, it is assumed that user 6b, who received the notification, started the operation of the garment processing device 3. In this case, the communication and notification processing unit 52 of the laundry share server 5 notifies the terminal device 7c of the next user (second in the setup order) 6c that the garment processing device 3 has completed operation (S49). The communication and notification processing unit 52 of the laundry share server 5 also notifies user 6b's terminal device 7b that the priority right to use the garment processing device 3 has been transferred to the next user 6c (S48).

[0094] Next, the communication and notification processing unit 52 of the laundry share server 5 monitors the operation data 41 of the garment processing device 3. If the garment processing device 3 starts operating within a certain time after the user 6c is notified of the completion of operation, it is assumed that the user 6c who received the notification has started operating. Therefore, if the garment processing device 3 starts operating within a certain time after the user 6c is notified of the completion of operation, the communication and notification processing unit 52 of the laundry share server 5 sets up automatic notification settings so that the user 6c who sent the notification is notified of the completion of operation, etc. (S50). Specifically, the communication and notification processing unit 52 sets the registered user (1st) item in the notification setting management information 541 to the identification information (user ID) of user 6c.

[0095] Next, we will describe case A5, where user 6b sets up a notification to be sent when any of the garment processing devices 3 in Room 2 become available. In case A5, user 6b has set up a notification setting using registration code 731 (S51) so that a notification is sent when any of the garment processing devices 3 in any of Room 2 become available.

[0096] With this registration code 731 notification setting, the notification setting management unit 54 of the laundry share server 5 sets notification settings in the notification setting management information 541 for all garment processing devices 3 associated with the group ID of Room 2 corresponding to the room screen 710 (S52). The notification setting management unit 54 also sets these notification settings in the order they are set (S53). For example, if there are no notification settings for other users such as user 6c, the identification information (user ID) of user 6b is registered first. If there are notification settings for other users such as user 6c, the identification information (user ID) of user 6b is registered in the subsequent order (for example, if user 6c is the 21st, then user 6b is registered second).

[0097] Note that the setting to notify when a machine becomes available and the setting for individual notifications may be mixed. For example, user 6b may set it up so that a notification is sent when any of the garment processing machines 3 in room 2 become available, and user 6c may set it up so that a notification is sent when any of the garment processing machines 3 in room 2 become available. In this case, for any garment processing machine 3 that user 6c has set up to send a notification, user 6b has also set it up to send a notification, and the order of notifications will be the order in which they were set.

[0098] Next, it is assumed that the operation of one of the garment processing devices 3 that has been set to be available has been completed. When the operation of a garment processing device 3 is completed, the operation information management server 4 updates the operation status in the operation data 41 to completed (S54). Next, the equipment / user management unit 53 of the laundry share server 5 receives notification from the operation information management server 4 of the operation data 41 whose operation status has been updated to completed, along with the identification information (equipment ID) of the garment processing device 3, and updates the operation data 41 in the equipment management information 531 linked to that identification information (S55).

[0099] Next, the communication and notification processing unit 52 of the laundry share server 5 identifies users 6b and 6c who have set up notifications for the garment processing device 3 when an event (completion of operation) has occurred, based on the operation data 41 in the device management information 531 linked to the identification information (device ID) of the garment processing device 3. At this point, the communication and notification processing unit 52 of the laundry share server 5 sends an operation completion message to the terminal device 7b of user 6b, who is the first to register (S56). The application 71 on terminal device 7b displays the notification on the portal screen 700 and notifies user 6b (S57).

[0100] Upon receiving notification that the garment processing device 3 has completed its operation, user 6b understands that the garment processing device 3 is now free. Therefore, user 6b can use the now free garment processing device 3 to start a washing, drying, or other operation.

[0101] The communication and notification processing unit 52 of the laundry share server 5 monitors the operation data 41 of the garment processing device 3. If the garment processing device 3 is started again within a certain time after the operation completion notification, it is assumed that the user 6b who received the notification started the operation. Therefore, if the garment processing device 3 is started again within a certain time after the operation completion notification, the communication and notification processing unit 52 of the laundry share server 5 sets up an automatic notification (S58) so that the user 6b who sent the notification is notified of the completion of the operation, etc. Specifically, the communication and notification processing unit 52 uses the registered user (first) item associated with the device ID of the garment processing device 3 in the notification setting management information 541 as the identification information (user ID) of user 6b.

[0102] If a notification is sent when a machine becomes available, it means that notification settings have also been made for other garment processing machines 3 in Room 2, but notifications are not necessary for those other garment processing machines 3. Therefore, in S58, if operation of a garment processing machine 3 is started within a certain time after the operation completion notification, the communication and notification processing unit 52 deletes the identification information (user ID) of user 6b, which is set as a registered user linked to the identification information (device ID) of garment processing machines 3 other than the one that started operation. As a result, after operation of garment processing machine 3 is started, the laundry share server 5 can prevent unnecessary notifications regarding garment processing machines 3 other than garment processing machine 3 from being sent to user 6b. In addition, it can support the use of garment processing machines 3 by other users, thus contributing to an improved turnover rate.

[0103] Figures 9 to 11 show examples of notifications to the terminal device 7 according to Embodiment 1. In the examples in Figures 9 to 11, it is assumed that user 6 has already set up notifications for the clothing processing device 3 "No. 01". Furthermore, in the example in Figure 10, users 6b and 6c have set up notifications for the clothing processing device 3, and the order of these settings is assumed to be users 6b and then 6c.

[0104] As shown in Figure 9, the portal screen 700 of the terminal device 7 displays various events related to the garment processing device 3 (washing, rinsing, washing complete, etc.) that the user 6 has set to receive notifications for, in chronological order as notifications 701d to 701f. Therefore, by checking notifications 701d to 701f on the portal screen 700, the user 6 can check the events that have occurred in the garment processing device 3 in chronological order. In addition, the user 6 can easily confirm that the garment processing device 3 is available by receiving notification 701f, which indicates that the garment processing device 3 is available. After confirming that the garment processing device 3 is available, the user 6 can use the garment processing device 3 to perform operations such as washing and drying.

[0105] Furthermore, if the garment processing device 3 is operated within a certain period of time after notification 701f indicating that the garment processing device 3 is available, the operating status of the garment processing device 3 is notified to the user 6's terminal device 7 via the automatic notification setting. Specifically, as shown in Figure 10, notification 701g regarding the operating status of the garment processing device 3 is displayed on the portal screen 700.

[0106] For example, if an abnormality occurs in the garment processing device 3, a notification 701h indicating the abnormality will be issued. Also, when the operation of the garment processing device 3 has finished, a notification 701i indicating the end of operation will be issued. This allows the user 6 to easily check the operating status of the garment processing device 3.

[0107] Furthermore, as shown in Figure 11, if, after sending a notification 701f to the portal screen 700a of the terminal device 7a owned by user 6b indicating that the garment processing device 3 is available, the garment processing device 3 is not operated within a certain period of time, a notification 701j is sent to the next user in the setup order, user 6c, indicating that the garment processing device 3 is available. Specifically, the laundry share server 5 sends a notification 701j to the portal screen 700b of the terminal device 7a owned by user 6c, indicating that the garment processing device 3 is available.

[0108] As a result, if user 6b does not start operating the garment processing device 3 within a certain period of time and the garment processing device 3 remains idle, the notification system 1 can prompt the next user 6c to start operating the garment processing device 3. At the same time, the laundry share server 5 sends a notification 701k to user 6b's portal screen 700b indicating that the priority use rights of the garment processing device 3 have been transferred to the next user 6. This notification 701k allows user 6b to recognize that the priority use rights of the garment processing device 3 have been transferred to the next user, thereby preventing problems related to the use of the garment processing device 3.

[0109] [1-3. Effects, etc.] As described above, the notification system 1 comprises multiple terminal devices 7 and a laundry share server 5 that acquires operating data 41 from the garment processing device 3. The terminal devices 7 and the laundry share server 5 are connected via a network 8. When the laundry share server 5 receives a notification setting from a terminal device 7, it notifies the terminal device 7 that received the notification setting of the operating status of the garment processing device 3 based on the operating data 41 at a predetermined timing.

[0110] According to this, the notification system 1 allows users to check the operating status of the garment processing device 3, which is notified at predetermined times, by configuring notification settings on the terminal device 7. Therefore, users 6 can check the operating status of the garment processing device 3 and use it as needed when it is available. In this way, the notification system 1 allows users 6 to share the garment processing device 3 while suppressing conflicts among users 6, even without using a garment processing device 3 that allows operation reservations.

[0111] The laundry share server 5 notifies the terminal device 7 of the first user 6 of the operating status of the garment processing device 3 at a first timing, and at a second timing later than the first timing, it notifies the terminal device 7 of a second user 6, who is different from the first user 6, of the operating status of the garment processing device 3.

[0112] According to this, the notification system 1 notifies the first user 6 of the operating status of the garment processing device 3 at a first timing, and the second user 6 at a second timing, which is later than the first timing. As a result, the notification system 1 can share the garment processing device 3 while further suppressing conflicts between the first and second users 6.

[0113] If the laundry sharing server 5 does not start operation of the garment processing device 3 within a predetermined time from the first timing, the second timing notifies the terminal device 7 of the second user 6 of the operating status of the garment processing device 3.

[0114] According to this, if the garment processing device 3 does not start operating within a predetermined time from the first timing, the notification system 1 notifies the second user 6 of the operating status of the garment processing device 3. Therefore, the notification system 1 can support the sharing of the garment processing device 3 so that it is operated efficiently by the first and second users 6.

[0115] At the second timing, the laundry share server 5 notifies the terminal device 7 of the first user 6 that the right to use the garment processing device 3 has been transferred to the second user 6.

[0116] According to this, the notification system 1 allows the first user 3 to recognize that the right of use has been transferred to the second user 6, thereby preventing problems between the first and second users 6 regarding the use of the clothing processing device 3.

[0117] The laundry share server 5 manages the order in which users 6 have configured their notification settings and notifies users 6's terminal devices 7 of the operating status of the equipment based on this configuration order.

[0118] According to this, notification system 1 sends notifications to user 6 based on the order in which they were set. Therefore, notification system 1 can support the fair sharing of the clothing processing device 3 among user 6.

[0119] If the laundry sharing server 5 starts operation of the garment processing device 3 within a predetermined time from the first timing, it notifies the terminal device 7 of the first user 6 that the operation of the garment processing device 3 has ended based on the completion of the operation of the garment processing device 3.

[0120] According to this, the notification system 1 can confirm the completion of operation by a first user 6 who started operating the garment processing device 3 within a predetermined time from the first timing. Therefore, it is possible to identify a user 6 who is highly likely to have started operating the garment processing device 3 and notify them of the completion of operation.

[0121] If the laundry sharing server 5 starts operation in the garment processing device 3 within a predetermined time from the first timing, it notifies the terminal device 7 of the second user 6 that the garment processing device 3 is available based on the completion of operation in the garment processing device 3.

[0122] According to this, in the notification system 1, if the first user 6 starts operating the garment processing device 3 within a predetermined time from the first timing, the second user 6 can confirm that the operation has finished and the garment processing device 3 is now free. Therefore, it is possible to assist the second user 6 in starting an operation after the first user 6 has finished their laundry operation.

[0123] (Other embodiments) As described above, Embodiment 1 has been presented as an example disclosed in this application. However, the technology in this disclosure is not limited to this and can be applied to embodiments that have been modified, replaced, added, or omitted. Furthermore, it is possible to create new embodiments by combining the components described in Embodiment 1. Therefore, other embodiments are illustrated below.

[0124] For example, in Embodiment 1 described above, a clothing processing device 3 is given as an example of equipment, but the equipment is not limited to the clothing processing device 3. The equipment may be a dishwasher that washes dishes in processes such as washing and rinsing, a cooking appliance (microwave oven, induction cooker) that cooks food in processes such as heating (e.g., high heat, medium heat, low heat) and keeping warm, or a clothing refresher that processes clothes with steam. The present invention is particularly suitable for use in equipment that executes a predetermined sequence, such as a clothing processing device, and terminates operation when the execution of the sequence is completed. The equipment may remain powered ON even after the operation has ended. In addition, in Embodiment 1 described above, a household washing machine is given as an example of the clothing processing device 3, but the clothing processing device 3 is not limited to a household washing machine, and may be a dedicated washing machine or dryer. In addition, in Embodiment 1 described above, a clothing processing device 3 shared by multiple users in different households is given as an example of the clothing processing device 3, but the clothing processing device 3 is not limited to this and may be shared by multiple users in the same household.

[0125] In the above embodiment 1, a configuration was illustrated in which the operation information management server 4, which manages the operation data 41, and the laundry share server 5, which provides notifications based on the operation data 41, are separated. However, the above management and notification may be performed by a single server device. Thus, the configuration of the server device that performs management and notification may be appropriately changed (distributed or integrated) according to the specifications of the server device. Furthermore, communication between the garment processing device 3, the operation information management server 4, the laundry share server 5, and the terminal device 7 via the network 8, etc. in the notification system 1 is not limited to wireless communication such as Wi-Fi (registered trademark), but may also be short-range communication or wired communication.

[0126] Furthermore, while the above-described embodiment 1 illustrates a configuration in which notifications are sent to the terminal device 7 using LINE's notification message function, the notification to the terminal device 7 is not limited to the above configuration. For example, the notification to the terminal device 7 may be sent using a social networking service other than LINE, by email, by a dedicated application, by voice, or by turning a light on or off.

[0127] Furthermore, while the above-described embodiment 1 illustrates a configuration in which notifications are sent to a terminal device 7 owned by user 6, the laundry share server 5 may also send notifications to a terminal device 7 (e.g., a monitoring device) installed in room 2. For example, when a predetermined event occurs in the garment processing device 3, the laundry share server 5 sends a notification to a monitoring device linked to the room 2 in which the garment processing device 3 is installed, indicating the operating status of the garment processing device 3. This allows user 6 to receive notifications regarding the operating status of the garment processing device 3 via a terminal device 7 installed in room 2, even if they do not own a terminal device 7 themselves.

[0128] Furthermore, in the above embodiment 1, the end of operation was given as an example of a predetermined timing. However, the timing of the notification may be before the end of operation, or after a predetermined time has elapsed after the end of operation. For example, the laundry share server 5 may notify that it is about to finish not at the end of operation, but a predetermined time before the end of operation (for example, 5 minutes before). The laundry share server 5 may also notify that a specific process (for example, the drying process) is being performed. A specific process may be, for example, the process immediately before the end of operation.

[0129] Furthermore, in the above embodiment 1, an example of a second timing later than the first timing was disclosed as after a predetermined time has elapsed. However, the second timing only needs to be later than the first timing and is not limited to after a predetermined time has elapsed since the first tying. For example, the laundry share server 5 may ask the first user at the first timing whether it is possible to accommodate them, and the second timing may be when it receives a no answer.

[0130] Furthermore, in Embodiment 1 described above, the order of notification settings was given as an example of how to select the first and second users. However, the method of selecting the first and second users is not limited to the order of notification settings. For example, the laundry share server 5 manages the usage history of each garment processing device 3 (for example, registered users who have set up notifications), and may select the first and second users based on the priority given to that usage history. As an example, the laundry share server 5 may prioritize selecting users with a high usage history (high number of registrations).

[0131] Furthermore, regarding the "after a predetermined time has elapsed" example of a second timing that is later than the first timing, this predetermined time is not necessarily limited to a fixed period. For example, the laundry share server 5 may set the length of the above predetermined time according to the type of equipment (clothing processing device 3) that has been notified (e.g., washing machine, dryer) and user information (age, location, etc.). For example, in the case of a washing machine, a longer time may be set than for a dryer. Also, if the user is older, a longer time may be set than when the user is younger. Also, if the distance between the location of the notified equipment and the user's location is far, a longer time may be set than when the distance is close.

[0132] Furthermore, in the above-described embodiment 1, a configuration was illustrated in which, if operation of the equipment (clothing processing device 3) is started within a predetermined time from the first timing, a notification is given to the first user based on the completion of operation of the equipment. However, the condition that operation of the equipment is started is not limited to within a predetermined time. For example, the laundry share server 5 may, after the first timing, notify the first user asking whether the operation was performed by the first user, and the condition may be that the server receives a response confirming that the operation was performed by the first user.

[0133] Furthermore, notifications to users regarding the operating status of the machine (clothing processing device 3) while it is in operation, and notifications to users who have set up notifications (such as when the machine is finished), may be made simultaneously or with a time delay. For example, the laundry share server 5 may notify users who have operated the machine after the notification of its operating status (completion of operation) and the next user waiting for the machine to become available (completion of operation) at the same time or with a time delay. As an example, the laundry share server 5 may notify the next user of the completion of operation after a predetermined time (e.g., 5 minutes) has elapsed since the notification to the user who operated the machine after the notification of completion of operation. This prevents conflicts between the user who has operated the machine previously and the next user waiting for it to become available.

[0134] Since the embodiments described above are for illustrative purposes of the technology described herein, various modifications, substitutions, additions, omissions, etc., can be made within the claims or their equivalents.

[0135] (Note) Based on the above description of embodiments, the following technologies are disclosed.

[0136] (Technology 1) A notification system comprising a plurality of terminal devices and a server device that acquires operating information of the devices from the devices, wherein the terminal devices and the server device are connected via a network, and the server device, upon receiving a notification setting from a terminal device, notifies the terminal device that received the notification setting of the operating status of the devices based on the operating information at a predetermined timing. According to this, by configuring notification settings on the terminal device, the operating status of the equipment can be checked. Therefore, even if the shared equipment does not allow for operation reservations, users can check the operating status of the equipment and use it as needed. In this way, the notification system allows for equipment sharing while suppressing competition among users, even without using equipment that allows for operation reservations.

[0137] (Technology 2) The notification system according to Technology 1, wherein the server device notifies the terminal device of the first user of the operating status of the equipment at a first timing among a plurality of users who have set up the notification, and notifies the terminal device of the operating status of the equipment of a second user, who is different from the first user, at a second timing later than the first timing. According to this, the operating status of the device is notified to the first user at the first timing, and to the second user at a second timing later than the first timing. Therefore, the notification system can share the device while further reducing conflict between the first and second users.

[0138] (Technology 3) The notification system according to Technology 2, wherein if the server device does not start operation of the equipment within a predetermined time from the first timing, the server device notifies the terminal device of the second user of the operating status of the equipment after the predetermined time has elapsed as the second timing. According to this, if the equipment is not started within a predetermined time from the first timing, the operating status of the equipment is notified to the second user. Therefore, the notification system can support the sharing of equipment so that the equipment is operated efficiently by both the first and second users.

[0139] (Technology 4) The notification system according to Technology 1 or Technology 2, wherein the server device notifies the terminal device of the first user that the right to use the device has been changed at the second timing. According to this, the first user can recognize that the right of use has been transferred to the second user, and the notification system can prevent problems regarding the use of the device between the first and second users.

[0140] (Technical 5) The notification system according to Technical 1 or Technical 2, wherein the server device manages the order in which users have made the notification settings and notifies the terminal devices of the users based on the order in which the settings are made of the equipment. According to this, notifications are sent to users based on the order in which they were set up, so the notification system can help ensure fair sharing of equipment among users.

[0141] (Technical 6) The notification system according to Technical 2, wherein if the server device starts operation of the equipment within a predetermined time from the first timing, the server device notifies the terminal device of the first user of the termination of operation of the equipment based on the termination of operation of the equipment. According to this, the notification system allows the first user who started operating the device within a predetermined time from the first timing to confirm the end of that operation.

[0142] (Technical 7) The notification system according to Technical 2, wherein if the server device starts operation on the device within a predetermined time from the first timing, the server device notifies the terminal device of the second user that the device is available based on the completion of operation on the device. According to this, the notification system allows a second user to confirm that the operation has finished and the equipment is available if the first user starts operating the equipment within a predetermined time from the first timing.

[0143] (Technical 8) A notification method comprising a server device that connects to multiple terminal devices via a network and acquires operating information of the devices from the devices, and when the server device receives a notification setting from the terminal device, it executes a process to notify the terminal device that received the notification setting of the operating status of the devices based on the operating information at a predetermined timing. According to this, it will have the same effect as the notification system described in Technology 1.

[0144] (Technical 9) A notification program that, upon receiving a notification setting from a terminal device, causes a server device that is connected to multiple terminal devices via a network and acquires operational information of the devices from the devices to execute a process to notify the terminal device that received the notification setting of the operating status of the devices based on the operational information at a predetermined timing. According to this, it will have the same effect as the notification system described in Technology 1. [Industrial applicability]

[0145] The notification system, notification method, and notification program described herein can be used to reduce conflicts among users and facilitate the sharing of equipment. [Explanation of Symbols]

[0146] 1. Notification System Rooms 2a-2c 3. Clothing processing device 4. Operation Information Management Server 5. Laundry Share Server (Server Device) 6, 6a~6d Users 7, 7a~7d Terminal devices 8 Networks 41. Driving Data 51 Website Processing Section 52 Communication and Notification Processing Unit 53 Equipment and User Management Department 54 Notification Settings Management Department 71 apps 531 Device management information 532 User Management Information 541 Notification settings management information 700 Portal screen 700a Portal Screen 700b Portal screen 701, 701a~701k notification 702a, 702b operation buttons 710 Room Screen 711a Device information 711b Device information 711c device information 712a~712c Notification settings button 713 When available, set notification button 720 Group Screen 721 Register button 730 Scan screen 731 Registration code 1000 computers 1010 CPU 1020 ROM 1030 RAM 1040 Storage section 1041 Program 1050 I / F section 1060 Input Section 1070 Output section 1080 Bus Cases A1-A5

Claims

1. A notification system comprising a device that terminates operation after completing a predetermined operation, a plurality of terminal devices, and a server device that acquires operation information of the device, wherein the terminal devices and the server device are connected via a network, The aforementioned server device is Upon receiving notification settings from the aforementioned terminal device, the operating status of the equipment based on the aforementioned operating information is notified to the terminal device that received the notification settings at a predetermined timing. Notification system.

2. The server device notifies the terminal device of the first user of the operating status of the equipment at a first timing among the multiple users who have set up the notification, and notifies the terminal device of the second user, who is different from the first user, of the operating status of the equipment at a second timing later than the first timing. The notification system according to claim 1.

3. If the server device does not start operation of the equipment within a predetermined time from the first timing, it notifies the terminal device of the second user of the operating status of the equipment after the predetermined time has elapsed, as a second timing. The notification system according to claim 2.

4. The server device, at the second timing, notifies the terminal device of the first user that the right to use the equipment has been changed for the second user. The notification system according to claim 2.

5. The server device manages the order in which users have made the notification settings and notifies the terminal devices of the users based on that setting order of the operating status of the equipment. The notification system according to claim 2.

6. If the server device starts operation on the equipment within a predetermined time from the first timing, it notifies the terminal device of the first user of the termination of operation on the equipment based on the termination of operation on the equipment. The notification system according to claim 2.

7. If operation of the equipment is started within a predetermined time from the first timing, the server device notifies the terminal device of the second user that the equipment is available based on the completion of operation of the equipment. The notification system according to claim 2.

8. A server device that connects to multiple terminal devices via a network and obtains operating information from devices that terminate operation after completing predetermined operational tasks, Upon receiving notification settings from the aforementioned terminal device, the operating status of the equipment based on the aforementioned operating information is notified to the terminal device that received the notification settings at a predetermined timing. Notification method.

9. A server device that connects to multiple terminal devices via a network and obtains operating information from devices that terminate operation after completing predetermined operational tasks, Upon receiving notification settings from the aforementioned terminal device, the operating status of the equipment based on the aforementioned operating information is notified to the terminal device that received the notification settings at a predetermined timing. Notification program.

Images