Notification System, Notification Method, and Program

Abstract

To reduce user time and effort in setting a notification on the basis of information from a device.SOLUTION: A notification system has reception means for receiving information on a device, notification means for notifying information received by the reception means, detection means for detecting a user's attendance state, and control means for determining whether to notify information by the notification means on the basis of the user's attendance state detected by the detection means.SELECTED DRAWING: Figure 18

Description

Technical Field

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

Background Art

[0002] Conventionally, a monitoring system has been disclosed that can monitor the states of a plurality of devices such as air conditioners, televisions, and refrigerators by using a terminal device such as a smartphone or a tablet terminal (see Patent Document 1).

[0003] In this monitoring system, a notification server acquires the states of a plurality of devices via a network. When the notification server acquires the state of a device, it transmits a notification indicating information such as the operating status and power consumption of the device to the terminal device. The user can remotely grasp the state of the device through the notification screen presented on the terminal device. Further, in this monitoring system, it is possible to set notification conditions such as the time zone and day of the week for which notifications are to be sent for each of the plurality of devices, and the user can switch the on / off of notifications by setting the notification conditions for each device.

Prior Art Documents

Patent Documents

[0004]

Patent Document 1

Summary of the Invention

Problems to be Solved by the Invention

[0005] In the prior art, whether to notify information from a device is not changed according to the user's state. For example, in the case of a user who wants to receive only FAX reception notifications and error notifications from devices installed in the company when at the company, the user switches the notification setting from the devices installed in the company to on when going to work. On the other hand, the user switches the device notification setting to off when returning to the company. These operations have to be performed every time the user goes to and returns from work, which is troublesome.

[0006] The present invention has been made in view of the above problems, When it is determined that the user is at work, instead of notifying the information indicating the status of the device from the device set to notify at the time of leaving work, notify the information from the device set to notify at the time of arrival at work; when it is determined that the user has left work, instead of notifying the information from the device set to notify at the time of arrival at work, notify the information from the device set to notify at the time of leaving work; when it is determined that the user is teleworking, at least notify the information from the device set to notify at the time of leaving work and aims to:

Means for Solving the Problems

[0007] Receiving means for receiving information indicating the state of the device, U - User Determine whether the user is at work, teleworking, or has left work To do Determination Means, When it is determined by the determination means that the user is at work, instead of notifying the information from the device set to notify at the time of leaving work, notify the information from the device set to notify at the time of arrival at work; when it is determined by the determination means that the user has left work, instead of notifying the information from the device set to notify at the time of arrival at work, notify the information from the device set to notify at the time of leaving work; when it is determined by the determination means that the user is teleworking, at least notify the information from the device set to notify at the time of leaving work and is characterized by having means.

Effects of the Invention

[0008] According to the present invention, When it is determined that the user is at work, instead of notifying the information indicating the status of the device from the device set to notify at the time of leaving work, notify the information from the device set to notify at the time of arrival at work; when it is determined that the user has left work, instead of notifying the information from the device set to notify at the time of arrival at work, notify the information from the device set to notify at the time of leaving work; when it is determined that the user is teleworking, at least notify the information from the device set to notify at the time of leaving work it is possible to:

Brief Description of the Drawings

[0009]

Figure 1

Figure 2

Figure 3

Figure 4

Figure 5

Figure 6

Figure 7

Figure 8

Figure 9

Figure 10

Figure 11

Figure 12

Figure 13

Figure 14

Figure 15

Figure 16

Figure 17

Figure 18

Figure 19

Figure 20

Figure 21

Figure 22

Mode for Carrying Out the Invention

[0010] (Example 1) Hereinafter, embodiments of the present invention will be described in detail with reference to the drawings. Note that the following embodiments do not limit the invention according to the claims, and not all combinations of the features described in the embodiments are essential for the solution means of the invention.

[0011] FIG. 1 is a diagram showing an example of the configuration of a notification system according to the present invention. The system configuration of this embodiment is such that a terminal device 200, which is an example of an information processing device, and a plurality of connection devices 500a to 500e are communicably connected to a device management server 400, a chat server 300, and an attendance management server 1900 via a network 100. Note that the network 100 of this embodiment may be the Internet or a LAN (Local Area Network). Also, the network 100 may be wired or wireless. The terminal device 200 is, for example, a mobile terminal such as a smartphone or tablet owned by a user. Alternatively, the terminal device 200 is an electronic device such as a personal computer or a tablet PC. The user performs status monitoring, control instructions for a plurality of connection devices, and attendance management in business via the terminal device 200. The attendance management server 1900 receives the attendance status transmitted from the terminal device 200 and manages the attendance status of the user. The chat server 300 transmits various notifications regarding the status of the connection devices transmitted from the device management server 400 to the terminal device 200. The device management server 400 monitors and controls the operations of a plurality of connection devices connected via the network 100. Also, the device status of each connection device is acquired, and a notification message is transmitted to the chat server 200 in order to notify the user of a notification message including the device status. Note that the chat server 200 and the device management server 400 may be configured by a single server.

[0012] The connected devices are various electrical products installed in offices and homes, such as MFPs (Multi Function Peripherals), lighting, air conditioners, refrigerators, microwave ovens, TVs, etc. These connected devices are communicably connected to the device management server 400 via the network 100. Also, by registering the registered device information including information about the connected devices in the device management server 400, the connected devices can receive control instructions from the device management server 400 and transmit status information. In this embodiment, MFP1 (500a), MFP2 (500b), printer (500c), washing machine (500d), and rice cooker (500e) are connected to the device management server 400 via the network 100. In the following description, when performing equivalent processing on the connected devices 500a to 500e, the connected devices 500a to 500e will be collectively described as the connected device 500.

[0013] Figure 2 is a diagram showing an example of the hardware configuration of the terminal device 200. The operation unit 201 has a touch panel function capable of detecting a user's touch operation. Further, the operation unit 201 displays various screens provided by the OS and the chat application. The user can input a desired operation instruction to the terminal device 200 by inputting a touch operation to the operation unit 201. Note that an operation instruction may be input to the terminal device 200 using a hardware key (not shown). The camera 202 captures an image in response to a user's imaging instruction. The terminal device 200 can exchange data with various peripheral devices via NFC 203 and Bluetooth 204. The communication unit 205 communicates with the chat server 300 connected via the network 100 to receive notifications and exchange messages. Note that the communication unit 205 may perform wired communication using Ethernet (registered trademark) or wireless communication such as Wi-Fi. The CPU 206 reads out the control program stored in the ROM 207 and executes various processes for controlling the operation of the communication terminal 200. The ROM 207 stores the control program. The RAM 208 is used as a temporary storage area such as the main memory and work area of the CPU 206. The storage 209 stores various data such as image data captured by the camera 202, image data downloaded via the communication unit 205, and electronic documents.

[0014] FIG. 3 is a diagram showing an example of the hardware configuration of the chat server 300. The communication unit 301 can transmit and receive data to and from the terminal device 200 and the device management server 400 via the Internet 100. The HDD 302 stores various data such as user information, notification messages, and image data. Further, the HDD 302 stores a chat application 303 for executing a chat service, and can execute message exchanges between users and notifications to specific users. Message transmission and notification can be performed by designating, as a destination, an ID uniquely indicating a user, an identifier uniquely indicating the terminal device 200, or the like. A user can use the chat service by registering user information including a user ID and an identifier of the terminal device 200 in the chat server 300 in advance. Note that the registered user information may be shared with the device management server 400 and the attendance management server 1900. The CPU 304 reads out a control program stored in the ROM 305 and executes various processes for controlling the operation of the chat server 300. The ROM 305 stores the control program. The RAM 306 is used as a temporary storage area such as a main memory and a work area of the CPU 304.

[0015] FIG. 4 is a diagram showing an example of the hardware configuration of the device management server 400. The communication unit 401 can transmit and receive data to and from the connected device 500 and the chat server 300 via the Internet 100. In addition, the communication unit 401 acquires status information indicating the status of the connected device. As the status information, for example, the operating status, setting information, error information, type of event that has occurred, etc. of the connected device 500 are acquired. Note that in order to perform device registration, acquisition of status information of the connected device, etc., it is necessary to register user information including the user ID and the identifier of the terminal device 200 in the device management server 400 in advance, but the registered user information may be shared with the chat server 300. The HDD 402 stores various data such as user information, registered device information of the connected devices registered by the user, group information to which the connected devices belong, notification settings of the connected devices, and status information acquired from the connected devices. The CPU 403 reads out the control program stored in the ROM 404 and executes various processes for controlling the operation of the device management server 400. The ROM 404 stores the control program. The RAM 405 is used as a temporary storage area such as the main memory and work area of the CPU 403.

[0016] FIG. 19 is a diagram showing an example of the hardware configuration of the attendance management server 1900. The communication unit 1901 can transmit and receive data to and from the terminal device 200 via the Internet 100 and accepts changes in attendance information from the connected terminal device 200. The HDD 1902 stores attendance information and various other data. The CPU 1903 reads out the control program stored in the ROM 1904 and executes various processes for controlling the operation of the attendance management server 1900. The ROM 1904 stores the control program and the like. The RAM 1905 is used as a temporary storage area such as the main memory and work area of the CPU 1903.

[0017] FIG. 20 shows a UI screen 2000 for work attendance management using a smartphone as an example. In the UI screen for work attendance management, as work attendance information, changes to an attendance button 2001, a leaving work button 2002, a break button 2003, and a break end button 2004 are accepted. In the work mode 2005, work modes such as telecommuting and working from home can be selected. The work attendance management server 1900 stores the work attendance information received from the terminal device 200 in the HDD 1902. In this embodiment, a smartphone is taken as an example, but it may also be a system that performs work attendance recording by touching a personal computer, a tablet PC, or an IC card.

[0018] FIG. 21 shows an example of a work attendance status update sequence between the terminal device 200 and the work attendance management server 1900. The processing of the terminal device 200 is executed by the CPU 206, and the processing of the work attendance management server 1900 is executed by the CPU 1903. First, when a login to the work attendance management server is executed in S2101, a login result is returned from the work attendance management server 1900 to the terminal device 200 in S2102. If the login is successful, the UI screen 2000 for work attendance management in FIG. 20 is displayed on the operation unit 201 of the terminal device 200. When the user selects any one of the buttons 2001, 2002, 2002, 2003 on the UI screen 2000 for work attendance management, a work status update notification is sent from the terminal device 200 to the work attendance management server 1900 in S2103. In S2104, an update result is returned from the work attendance management server 1900 to the terminal device 200. If the update result is OK, in S2106, the CPU 206 sets a "status update flag" stored in the ROM 207 or the storage 209.

[0019] FIG. 22 shows an example of work information stored in the HDD 1902. The HDD 1902 stores an attendance date and time 2200, an attendance form 2201, a work location (location information) 2202, a leaving work date and time 2203, etc. Note that in order to send and receive work attendance information, it is necessary to register user information including a user ID and an identifier of the terminal device 200 in the work attendance management server 1900, but the registered user information may also be shared with the chat server 300 and the device management server 400.

[0020] FIG. 5 is a diagram showing an example of the hardware configuration of MFP 1 (500a), a printer (500c), and a washing machine (500d) which are connection devices.

[0021] The MFP1(500a) includes a CPU501a, a ROM502a, a RAM503a, a storage 504a, an operation unit 505a, a printing unit 506a, a reading unit 507a, and a communication unit 508a. The CPU501a controls the overall operation of the MFP1(500a). The CPU501a reads out the control program stored in the ROM502a or the storage 504a to the RAM503a and performs various controls such as reading control and printing control. The ROM502a is used as a temporary storage area for expanding various control programs stored in the CPU50l work area, the ROM502a, and the storage 504a. The storage 504a stores image data, print data, various programs, and various setting information. In this embodiment, a flash memory is assumed as the storage 504a, but an auxiliary storage device such as an SSD (Solid State Drive) or an HDD (Hard Disc Drive) may be used. Also, an eMMC (embedded Multi Media Card) may be used. Note that the MFP1(500a) of this embodiment is assumed to have one CPU501a execute each process shown in the sequence described later using one memory (RAM503a), but it is not limited to this. For example, a plurality of CPUs, RAMs, ROMs, and storages can cooperate to execute each process shown in the flowchart described later. Also, some processes may be executed using a hardware circuit such as an ASIC or an FPGA. The operation unit 505a is, for example, a display unit such as a touch panel and hard keys. The operation unit 505a displays information to the user and detects inputs from the user. The printing unit 506a can print the image data (print data) stored in the RAM503a on the recording paper fed from the paper cassette. The reading unit 507a reads the image of the document, and the CPU111 converts the image into image data such as binary data. The image data generated based on the image read by the reading unit 507a is transmitted to an external device or printed on the recording paper. The communication unit 508a connects to the network 100. The communication unit 508a transmits the state information inside the device to the device management server 400.Examples of the status information include the status of jobs such as copying and faxing, notifications of remaining amounts and shortages of toner and printing paper (recording materials), error information such as the location of a failure, and the types of events that have occurred. In addition, the communication unit 508a transmits image data to an external device on the network 100 or receives print data from a terminal device. As a method of transmission and reception via the network 100, transmission and reception using e-mail or file transmission using other protocols (e.g., FTP, SMB, WEBDAV, etc.) can be performed. Furthermore, image data and various setting data can be transmitted and received via the network 100 by access via HTTP communication from the terminal device 200.

[0022] The printer (500c) includes a CPU 501c, a ROM 502c, a RAM 503c, a storage 504c, an operation unit 505c, a printing unit 506c, and a communication unit 507c. The CPU 501c controls the overall operation of the printer (500c). The CPU 501c reads out a control program stored in the ROM 502c or the storage 504c into the RAM 503c and performs various controls such as print control. The ROM 502c stores a control program executable by the CPU 501c. The RAM 503c is a main memory and is used as a temporary storage area for developing various control programs stored in the work area, the ROM 502c, and the storage 504c. The storage 504c stores image data, print data, various programs, and various setting information. In this embodiment, a flash memory is assumed as the storage 504c, but an auxiliary storage device such as an SSD (Solid State Drive) or an HDD (Hard Disc Drive) may be used. Also, an eMMC (embedded Multi Media Card) may be used. Note that the printer (500c) of this embodiment is assumed to have one CPU 501c execute each process shown in the sequence described later using one memory (RAM 503c), but it is not limited to this. For example, a plurality of CPUs, ROMs, RAMs, and storages can cooperate to execute each process shown in the flowchart described later. Also, some processes may be executed using a hardware circuit such as an ASIC or an FPGA. The operation unit 505c is, for example, a display unit such as a touch panel and a hard key. The operation unit 505c displays information to the user and detects an input from the user. The printing unit 506c prints the image data (print data) stored in the RAM 503c on the recording paper fed from the paper feed cassette. The communication unit 507c connects to the network 100. The communication unit 507c transmits the state information inside the device to the device management server 400. The state information includes, for example, the status of the print job, notifications of the remaining amount and shortage of toner, printing paper (recording material), etc., error information such as a failure, and the type of the event that occurred. Also, the communication unit 508a receives print data from a terminal device on the network 100.

[0023] The washing machine (500d) includes a CPU 501d, a ROM 502d, a RAM 503d, an operation unit 504d, a motor control unit 505d, a water level control unit 506d, and a communication unit 507d. The CPU 501d controls the overall operation of the washing machine (500d). The CPU 501d reads out the control program stored in the ROM 502d to the RAM 503d and performs various controls such as motor control and water level control. The ROM 502d stores the control program executable by the CPU 501d. The RAM 503d is the main memory and is used as a work area and a temporary storage area for expanding various control programs stored in the ROM 502d. The operation unit 504d is a display unit such as a touch panel and hard keys, for example. The motor control unit 505d controls the motor rotation speed of the washing tub. The water level control unit 506d controls the water level in the washing tub and controls water supply and drainage. The communication unit 507d is connected to the network 100. The communication unit 507d transmits the status information inside the device to the device management server 400. The status information includes, for example, operation status, error information such as a failure, and the type of the event that has occurred. Also, the communication unit 507d receives a control instruction from an external device on the network 100 or the like.

[0024] FIG. 6 is an example of a screen for registering a connected device displayed on the operation unit 201 of the terminal device 200 with the device management server 400.

[0025] The screen 600a is a screen for displaying the connected devices registered with the device management server 400, and an arbitrary name given by the user to the connected device and the category of the connected device are listed in columns 601 and 602, respectively. The category of the connected device is, for example, a multifunction device, a printer, a rice cooker, a washing machine, and the like. It is assumed that the user has registered user information with the device management server 400 in advance before performing device registration. When the user newly registers a device with the device management server 400, the user selects the device addition button 603 displayed on the screen 600a.

[0026] Screen 600b is a screen that is displayed triggered by the user selecting the device addition button 603, and a list of devices not registered in the device management server 400 is displayed. On screen 600b, for example, the category and product name of the device are displayed. The devices to be listed may be the devices recognized by the terminal device 200 via NFC 203, Bluetooth 204, etc., or the devices belonging to the same network may be displayed. The user selects a device to be registered in the device management server 400 from the devices displayed on screen 600b.

[0027] Screen 600c is a screen that is displayed triggered by the user selecting any one of the devices listed on screen 600b, and the category and product name of the device selected on screen 600b, "Printer (PRINTER-2000B)", are displayed in column 605. Also, a name field 606 for entering a name for the selected device is displayed, and the user enters an arbitrary name in name field 606. After entering the name, when the user selects the registration button 607, the registered device information is sent to the device management server 400 and the registration is completed. The registered device information includes, for example, in addition to the name entered on screen 600c, the category, product name, and MAC (Media Access Control) address of the device. Also, the registered device information includes information such as identification information uniquely assigned to the device, such as the serial number, and user information of the user who performed the registration.

[0028] Figure 7 is an example of a screen for performing group registration of connected devices displayed on the operation unit 201 of the terminal device 200. Group registration means that the user groups one or more of two or more connected devices as one group and registers them in the device management server 400.

[0029] The screen 700a is a screen that displays the group information of connected devices, and the connected devices registered in the device management server 400 are displayed. In this embodiment, the arbitrary names given by the user to the connected devices and the groups to which the connected devices belong are listed in columns 701 and 702 respectively. When the user wants to newly register a group in the device management server 400, the user selects the new group registration button 703 displayed on the screen 700a.

[0030] The screen 700b is a screen that is displayed triggered by the user selecting the new group registration button 703. On the screen 700b, a group name field 704 for entering the name of the newly created group is displayed, and the user can enter any group name. Also, in the connected device field 705, a checkbox 706 for selecting whether to make the connected device belong to the new group is displayed. After checking the connected devices to belong to the new group, when the user selects the registration button 707, the group information is sent to the device management server 400 and the group registration is completed. The group information includes, for example, information such as the group name entered on the screen 700b, the registered device information of the connected devices that were checked, and the user information of the user who created the group. In the example of the screen 700b, it shows that three connected devices, namely "Study Printer", "Home Kitchen Rice Cooker", and "Home Washing Machine", belong to a group with the group name "Home Appliances". In this embodiment, the connected devices are configured to belong to one group, but they may also belong to a plurality of hierarchical groups. For example, "Head Office 1F Floor Multifunction Machine" may belong to two groups, namely the "Head Office Printer" group and the "Head Office 1F Printer" group, which is a subordinate group of the "Head Office Printer" group.

[0031] FIG. 8 is an example of a notification setting screen displayed on the operation unit 201 of the terminal device 200. On the notification setting screen 800a, it is possible to switch the notification setting as to whether or not to display various notifications regarding the state of the connected device 500 generated by the device management server 400 on the terminal device 200. By selecting the attendance management service link 820, the notification setting screen 800b is displayed. The notification setting set on the notification setting screen 800b is transmitted to the device management server 400 and stored.

[0032] On the notification settings screen 800b, the groups registered in the device management server 400 and the connected devices belonging to those groups are displayed. Also, a toggle switch for the attendance management service linkage setting is displayed to switch whether to send notifications linked to the attendance management service to the terminal device 200 for the connected devices belonging to each of the multiple groups. By setting the toggle switch for the attendance management service linkage setting to "OFF", the user can collectively switch so that no notifications linked to the attendance management service are sent to all the connected devices belonging to the group. Similarly, by setting the toggle switch for the attendance management service linkage setting to "ON", the user can collectively switch so that notifications linked to the attendance management service are sent to all the connected devices belonging to the group. For example, on the notification settings screen 800b, the "Headquarters Printer" group 801, which is a group registered in the device management server 400, and the connected devices belonging to that group, the "Headquarters 1F Floor Multifunction Printer" 802 and the "Headquarters 2F Floor Multifunction Printer" 803, are displayed. By setting the attendance management service linkage setting 810 of the "Headquarters Printer" group 801 to "ON", the settings of the connected devices 802 and 803 belonging to the "Headquarters Printer" group 801 can be collectively set to "ON". Furthermore, by setting the attendance management service linkage setting 810 to "ON", the user can select whether to send a notification when the user's work status is either "At Work" or "Off Work". By checking the selection box 811 for "At Work", a notification is sent when the user is in the at-work state. Similarly, the "Home Appliances" group 804 and all the connected devices belonging to the "Home Appliances" group, the "Study Printer" 805, the "Home Kitchen Rice Cooker" 806, and the "Home Washing Machine" 807, are displayed. By setting the attendance management service linkage setting 813 of the "Home Appliances" group 804 to "ON", the settings of the connected devices 805, 806, and 807 belonging to the "Home Appliances" group 804 can be collectively set to "ON". For the connected devices belonging to the "Home Appliances" group 804, by checking the selection box 812 for "Off Work", a notification is sent when the user is in the off-work state. Also, the connected devices that do not belong to any group may be collectively displayed as "None" 808.The attendance management service linkage setting 814 of "Without Group" 808 is set to "OFF", and the setting of "Branch A Printer" 809 which does not belong to a group will also be set to "OFF" in conjunction. Note that it is also possible to switch to a setting different from the attendance management service linkage setting of the group to which the connected device belongs by individually changing the settings of the connected device. For example, even if the attendance management service linkage setting 813 of the "Home Appliances" group 804 is set to "ON", it may be allowed to set only the setting 814 of the study printer 805 to "OFF". Also, "Device Individual Settings" setting means for individual change may be provided on the notification setting screen 800b. Further, when the connected device belongs to a plurality of hierarchically structured groups, by switching the attendance management service linkage setting of the upper group, the attendance management service linkage setting of the lower level and the notification settings of all the connected devices belonging to the lower group may be switched collectively. Also, it may be possible to switch the attendance management service linkage setting of the lower group to a setting different from the attendance management service linkage setting of the upper group. For example, the attendance management service linkage setting of the "Head Office Printer" group which is the upper group is set to "ON". After that, the attendance management service linkage setting of the "Head Office 1F Printer" group which is the lower group thereof may be set to "OFF", and the attendance management service linkage setting of the "Head Office 2F Printer" may be set to "ON". Note that in this case, the settings of the connected devices belonging to the "Head Office 1F Printer" group will all be set to "OFF", and the settings of the connected devices belonging to the "Head Office 2F Printer" group will all be set to "ON". In this embodiment, as the condition of the notification, a form in which either "Arrival at Work" or "Departure from Work" can be selected is adopted, but options such as "During Work" and "Outside of Work" may be available. By doing so, it is also possible to suppress notifications during breaks.

[0033] FIG. 18 is a flowchart of the notification switching setting process of the terminal device. The CPU 206 of the terminal device 200 performs the notification switching process by executing the processes of this flowchart at regular intervals. Each operation (step) of the flowchart is executed by the CPU 206 reading out a control program stored in the ROM 207 or the storage 209 into the RAM 208. Here, the case where the work attendance management service linkage setting 810 is selected will be described as an example, but the processes shown in the flowchart of FIG. 18 are also executed even if the work attendance management service linkage setting 813 or the work attendance management service linkage setting 817 is selected. Also, in addition to the method of executing this flow at regular intervals, the flow may be executed triggered by the change of the work attendance management service linkage setting 810.

[0034] In S1801, the CPU 206 determines whether the setting of the work attendance management service linkage setting 810 has been changed. When the work attendance management service linkage setting 810 is originally OFF and is selected by the user, it is determined that the work attendance management service linkage setting 810 has been changed to ON. If it is determined that the work attendance management service linkage setting 810 has been changed to ON, the CPU 206 proceeds to the process in S1802. On the other hand, if it is determined that the work attendance management service linkage setting 810 has not been changed to ON, the CPU 206 proceeds to the process in S1813. In S1813, it is confirmed that the work attendance status has been updated (the status update flag is 1). If it has been updated, the process proceeds to S1802. In S1802, the CPU 206 stores the variable N in the RAM 207 and sets 1 to the variable N.

[0035] In S1803, the CPU 206 determines whether the setting of the notification for the Nth device in the group of the work attendance management service linkage setting 810 is ON and "Check-in" is set in the selection box. If the determination is YES, in S1804, the CPU 206 determines whether the work attendance status of the user is in the "Check-in" state. If the work attendance status is "Check-in", in S1805, the CPU 206 changes the original notification setting of the Nth device to ON. If the original notification setting of the Nth device is already ON, the setting remains unchanged. In S1804, if the work attendance status of the user is "Check-out", in S1810, the CPU 206 changes the original notification setting of the Nth device to OFF. If the original notification setting of the Nth device is already OFF, the setting remains unchanged.

[0036] In S1806, the CPU 206 determines whether there is still a device in the group. If it is determined that there is still a device in the group, the process proceeds to S1807. In S1807, the CPU 206 stores the variable N in the RAM 207 and sets 1 to the variable N. In S1806, if it is determined that there is no longer a device in the group, the process shown in the flowchart of FIG. 18 ends.

[0037] When the process proceeds from S1803 to S1808, the CPU 206 determines whether the work attendance management service linkage setting 810 is OFF and "Check-out" is set in the selection box. If the determination is YES, in S1809, the CPU 206 determines whether the work attendance status of the user is in the "Check-out" state. If the work attendance status is "Check-out", in S1811, the CPU 206 changes the original notification setting of the Nth device to ON. If the original notification setting of the Nth device is already ON, the setting remains unchanged. In S1809, if the work attendance status of the user is "Check-in", in S1810, the CPU 206 changes the original notification setting of the Nth device to OFF. If the original notification setting of the Nth device is already OFF, the setting remains unchanged.

[0038] When the process proceeds from S1808 to S1812, the CPU 206 changes the work attendance management service linkage setting 810 to OFF and proceeds to S1806.

[0039] Then, the on / off setting of the notification for each connected device set in this flowchart is sent to the device management server 400 and stored.

[0040] FIG. 9 is an example of a notification screen displayed on the operation unit 201 of the terminal device 200. On the notification screen 900, notifications regarding the status of the connected devices transmitted from the chat server 300 are displayed. In the case of the notification screen 900, two notifications 901 and 905 are displayed. The content of the notification includes, for example, as shown in notification 901, the icon 901 and name 902 of the connected device, the notification date and time 903, the message 904 regarding the status of the connected device, and the like. Notification 901 indicates that the terminal device 200 received a notification regarding the status of the connected device named "home washing machine" at "2021 / 10 / 5 10:21". Also, as a message, it notifies the user that the washing of the "home washing machine" ended at 10:21. Similarly, notification 905 indicates that the terminal device 200 received a notification regarding the status of the connected device named "study printer" at "2021 / 10 / 5 11:45". Also, as a message, it notifies the user that the printing of the "study printer" ended normally. The notification screen 900 may be displayed on a chat application that communicates with the chat server 300 installed in advance in the terminal device 200 to provide a chat service. Or, it may be displayed in the status area always displayed on the operation unit 201 or on the lock screen.

[0041] FIG. 10 is a flowchart regarding device registration that starts triggered by selecting the device addition button 603 of the screen 600a displayed on the operation unit 201 of the terminal device 200. Each operation (step) of the flowchart is executed by the CPU 206 reading the control program stored in the ROM 207 or the storage 209 into the RAM 208.

[0042] In S1001, the CPU 206 searches for devices to be registered in the device management server 400 and obtains identification information for uniquely identifying the devices. As for the search method, devices belonging to the same network (LAN) may be obtained by ARP (Address Resolution Protocol) via the communication unit 205. Alternatively, devices may be detected via short-range wireless communication means such as NFC 203 or Bluetooth 204. Also, the MAC address, serial number, etc. of the device are obtained as the identification information.

[0043] In S1002, the CPU 206 determines by querying the device management server 400 whether the identification information of the devices obtained by the search in S1001 has been registered in the device management server 400. As a result of the query, if there is one or more devices not registered in the device management server 400 among the devices obtained by the search in S1001, the process proceeds to S1003. On the other hand, if there are no devices not registered in the device management server 400, the device registration process ends.

[0044] In S1003, the CPU 206 causes the devices determined not to be registered in the device management server 400 in S1002 to be listed and displayed on the screen 600b.

[0045] In S1004, the terminal device 200 accepts the selection of any of the devices displayed on the screen 600b by operating the operation unit 201.

[0046] In S1005, the CPU 206 inputs information necessary as registration device information such as the name for the device selected in S1004 into the screen 600c.

[0047] In S1006, the terminal device 200 accepts the selection of the registration button 607 displayed on the screen 600c via the operation unit 201.

[0048] In S1007, the CPU 206 transmits the registration device information to the device management server 400 via the communication unit 205.

[0049] FIG. 11 is a flowchart regarding group registration that starts triggered by selecting the new group registration button 703 on the screen 700a displayed on the operation unit 201 of the terminal device 200. Each operation (step) of the flowchart is executed by the CPU 206 reading out the control program stored in the ROM 207 or the storage 209 into the RAM 208.

[0050] In S1101, the CPU 206 acquires the registered device information registered in the device management server 400 and displays it in a list on the screen 700b. Note that in S1101, it is assumed that the device management server 400 transmits only the registered device information registered by the user executing this flowchart to the terminal device 200, but the registered device information transmitted by the device management server 400 may be changed according to other conditions.

[0051] In S1102, the terminal device 200 accepts the input of the group name to the group name field 604 displayed on the screen 700b from the user and selects one or more connection devices to be grouped.

[0052] In S1103, the terminal device 200 accepts the selection of the registration button 607 displayed on the screen 700c from the user. In this way, the operation of grouping the connection devices is accepted.

[0053] In S1104, the CPU 206 transmits the group information to the device management server 400 via the communication unit 205.

[0054] FIG. 12 is a flowchart in which the MFP 1 (500a) transmits status information to the device management server 400. Each operation (step) of the flowchart is executed by the CPU 501a reading out the control program stored in the ROM 502a or the storage 504a into the RAM 503a.

[0055] In S1201, the CPU 501a detects an event. Examples of events include completion of jobs such as copying and faxing being executed on the MFP1(500a), the remaining amounts of toner, printing paper, etc. falling below a predetermined threshold, occurrence of a failure, etc. Also included as an event is an instruction to transmit status information from the device management server 400.

[0056] In S1202, the CPU 501a collects the status information to be transmitted to the device management server 400. As status information, the CPU 501a collects the operating status, setting information, error information, event type, etc. of the MFP1(500a), but the information collected may change according to the event. For example, in the case of an event of job completion, the type, date and time of the completed job, and job results may be collected, or in the case of an event of occurrence of a failure, information on the failure location and failure date and time may be collected.

[0057] In S1203, the CPU 501a controls the communication unit 508a and causes the communication unit 508a to transmit the status information collected to the device management server 400.

[0058] FIG. 13 is a flowchart in which the printer(500c) transmits status information to the device management server 400. Each operation (step) of the flowchart is executed by the CPU 501c reading a control program stored in the ROM 502c or the storage 504c into the RAM 503c.

[0059] In S1301, the CPU 501c detects an event. Examples of events include completion of jobs such as printing being executed on the printer(500c), the remaining amounts of toner, printing paper, etc. falling below a predetermined threshold, occurrence of a failure, etc. Also included as an event is an instruction to transmit status information from the device management server 400.

[0060] In S1302, the CPU 501c collects the status information to be transmitted to the device management server 400. As the status information, the CPU 501c collects the operating status, setting information, error information, event type, etc. of the printer (500c), but the information collected may vary according to the event. For example, in the case of an event of job completion, the type, date and time of the completed job, and job results may be collected, or in the case of an event of failure occurrence, the information on the failure location and failure date and time may be collected.

[0061] In S1303, the CPU 501c controls the communication unit 507c to cause the device management server 400 to transmit the collected status information.

[0062] FIG. 14 is a flowchart in which the washing machine (500d) transmits status information to the device management server 400. Each operation (step) of the flowchart is executed by the CPU 501d reading the control program stored in the ROM 502d into the RAM 503d.

[0063] In S1401, the CPU 501d detects an event. Examples of the event include detecting that the washing is completed, that the operation cannot be continued due to inability to supply water or the lid being open, and the occurrence of a failure. Also included as an event is an instruction to transmit status information from the device management server 400.

[0064] In S1402, the CPU 501d collects the status information to be transmitted to the device management server 400. As the status information, the CPU 501d collects the operating status, setting information, error information, event type, etc. of the washing machine (500d), but the information collected may vary according to the event. For example, in the case of an event of washing completion, the completed date and time may be collected, or in the case of an event of failure occurrence, the information on the failure location and failure date and time may be collected.

[0065] In S1403, the CPU 501d controls the communication unit 507d to cause the device management server 400 to transmit the collected status information.

[0066] FIG. 15 is a flowchart for the device management server 400 to post a notice regarding the status information acquired from the connected device 500 to the chat server 300. Each operation (step) in the flowchart is executed by the CPU 403 reading a control program stored in the ROM 404 or the HDD 402 into the RAM 506.

[0067] In S1501, the CPU 403 stores the status information received by the communication unit 401 in the HDD 402.

[0068] In S1502, the CPU 403 analyzes the status information received in S1501 to determine whether the status of the connected device 500 is a status to be notified to the user. The status to be notified is, for example, when the process being executed on the connected device 500 has been completed, or when the connected device 500 has detected a failure and is included in the status information. It is assumed that the notification conditions used for determining whether to notify are stored in advance in the HDD 402 of the device management server 400, but the notification conditions may be configured so that the user can set them for each connected device. For example, when "printing completion of received FAX" is set as the notification condition for the MFP1 (500a), if the CPU 403 determines that the event type indicating that the printing of the received FAX document has been completed is included in the status information, it determines that it is a status to be notified to the user. If the CPU 403 determines as a result of the analysis that it should be notified, it proceeds to S1503. On the other hand, if it determines that it is not a status to be notified, this flowchart ends.

[0069] In S1504, the CPU 403 acquires the notification setting of the connected device 500 determined to be a status to be notified in S1502, and if the setting is "ON", it proceeds to S1505. On the other hand, if the setting is "OFF", this flowchart ends. In S1504, the transition destination is changed in the attendance management service cooperation setting, but branching may also be performed based on the notification setting itself of the connected device determined to be a status to be notified.

[0070] In S1505, the CPU 403 creates a notification message. The notification message is created based on the status information. However, the message may be created using a format predetermined for each event type, or it may be a fixed message set by the user. Further, the notification message may include information such as the name, type, and icon of the connected device.

[0071] In S1506, the CPU 403 searches the user information of the user who registered the connected device 500 determined to be in the state to be notified in S1502 from the registered device information stored in the HDD 402.

[0072] In S1507, the CPU 403 transmits the user ID and the notification message created in S1505 to the chat server 300 so as to notify the user specified in S1506 of the notification message created in S1505.

[0073] FIG. 16 is a flowchart in which the chat server 300 notifies the terminal device 200 of the notification message transmitted from the device management server 300. Each operation (step) of the flowchart is executed by the CPU 304 reading a control program stored in the ROM 305 or the HDD 302 into the RAM 306.

[0074] In S1601, the CPU 304 detects that it has received the notification message transmitted from the device management server 400 and the user ID as the destination via the communication unit 301.

[0075] In S1602, the CPU 304 stores the notification message received in S1601 in the message history of the user who is the destination. Note that the notification message stored in the message history can be retrieved and confirmed by the user.

[0076] In S1603, the CPU 304 notifies the user who is the destination of the notification message received in S1601. In this embodiment, the CPU 304 transmits the notification message and the identifier of the terminal device 200 owned by the user to a distribution server (not shown) that performs push notifications, and notifies the terminal device 200 via the distribution server.

[0077] FIG. 17 is a flowchart showing a terminal device 200 displaying a notification message notified from a chat server 300. Each operation (step) in the flowchart is executed by the CPU 206 reading a control program stored in the ROM 207 or the storage 209 into the RAM 208.

[0078] In S1701, the CPU 206 detects that the communication unit 205 has received the notification message notified from the chat server 300.

[0079] In S1702, the CPU 206 displays the notification message received in S1701 on the notification screen 900.

[0080] In this embodiment, an example has been described in which the device management server 400 determines whether to generate a notification in S1505 at S1504. However, the present invention is not limited to this. For example, S1504 may be omitted, and the creation of the notification message and the posting to the chat server 300 are always performed in S1505 to S1507, and the following control may be performed. The terminal device 200 may switch whether to access the chat server 300 and display the notification message on the notification screen 900 according to the attendance management service cooperation setting or the notification setting of the connected device. In this case, the chat server 300 only adds the message to the history in S1602 without transmitting the notification message to the distribution server. Then, it is determined whether the terminal device 200 displays the notification message at the timing when the terminal device 200 acquires the message history from the chat server 300.

[0081] Also, for example, omitting S1504 and always creating a notification message and posting the notification message to the chat server 300 using S1505 to S1507, the following control may be performed. The device management server 400 may determine whether to send a notification message and the identifier of the terminal device 200 owned by the user to a delivery server (not shown) that performs push notifications based on the notification settings of the connected device for which the status information has been sent. When the notification setting of the connected device is set to be valid, the device management server 400 instructs the chat server 300 to send a notification message and the identifier of the terminal device 200 owned by the user to a delivery server (not shown) that performs push notifications. As a result, the terminal device 200 can perform notifications on the lock screen or the like without receiving a display instruction for the notification from the user. On the other hand, when the notification setting of the connected device is set to be invalid, the device management server 400 instructs the chat server 300 not to send a notification message and the identifier of the terminal device 200 owned by the user to a delivery server (not shown) that performs push notifications. In that case, the terminal device 200 does not need to perform notifications on the lock screen or the like.

[0082] As described above, it becomes possible to register one or more connected devices in a group and collectively change the setting of the notification to the operation unit 201 of the terminal device 200 based on the information from the plurality of devices belonging to the plurality of groups in cooperation with the attendance management service.

[0083] According to the invention described in this embodiment, it is possible to change whether to perform notification of information from a device according to the user's status. For example, consider a user who only wants to receive FAX reception notifications or error notifications from devices installed in the company when they are at the company. In such a case, it is not necessary to repeatedly perform the operation of the user switching the notification setting from the devices installed in the company to on when going to work and switching the notification setting of the devices to off when returning to the company.

[0084] Also, assume a case where, for the purpose of monitoring the people staying at home while away, it is set to receive notifications triggered by detecting the opening and closing of the refrigerator door or the start of washing of the washing machine. In that case, the caregiver no longer needs to repeatedly turn on the notification of information from the device when going out and turn off the notification when returning home.

[0085] That is, for example, when the user returns from the office, the user can change the notification setting based on the information of the connected devices belonging to the head office printer group to OFF in synchronization with the operation of changing the work attendance status to "off work". Also, when returning home, the notification setting based on the information of the connected devices belonging to the home appliance group can be set to ON in synchronization with the change of the work attendance status to "off work". In the above-described embodiment, the state of "off work" is described as an example, but the state of "returning home" may also be used. In that case, a "returning home" selection box may be provided instead of the "off work" selection box 812. And, a returning home button may be provided instead of the off work button 2002. Then, after the returning home button is pressed, based on the information received from the devices set to give notifications when the user is in the state of having returned home in a state where it is detected that the user has returned home, notifications may be given.

[0086] Furthermore, the invention described in this embodiment is more effective when the notification settings of a plurality of devices are to be collectively changed according to the user's state. For example, when wanting to receive only FAX reception notifications and error notifications from a plurality of devices installed in the company when in the company, register those plurality of devices as a group and set it to give notifications when going to work for that group. Thereby, when the user becomes in the work attendance state, it is not necessary to switch on the notification settings of those plurality of devices one by one. Also, for example, when wanting to receive notifications from home appliances after getting off work, there is no need to perform the operation of enabling the notification settings of the study printer 805, the home kitchen rice cooker 815, and the home washing machine 816 respectively. Instead, by setting up the work attendance management service linkage setting 813, the settings of a plurality of connected devices registered in the home appliance group can be changed collectively.

[0087] Note that the chat server 300 may remember whether the connection with the attendance management service of each connected device set on the screen 800b is enabled or disabled, and determine whether to post a message of the connected device. When the notification setting of a certain connected device set on the screen 800b is enabled, the chat server 300 remembers that the notification setting of the connected device is enabled. Then, when there is a notification of the status information of the connected device, the chat server 300 posts a message based on the notification. On the other hand, when the setting of a certain connected device set on the screen 800b is disabled, the chat server 300 remembers that the notification setting of the connected device is disabled. Then, when there is a notification of the status information of the connected device, the chat server 300 does not post a message based on the notification. Here, whether to post a message has been explained, but it may also be determined whether to perform a push notification of the message to the terminal device 200. When the setting of a certain connected device set on the screen 800b is enabled, the chat server 300 remembers that the notification setting of the connected device is enabled. Then, when there is a notification of the status information of the connected device, the chat server 300 sends a notification message and the identifier of the terminal device 200 owned by the user to a distribution server (not shown) that performs push notifications. That is, the chat server 300 enables the message to be automatically displayed on the terminal device 200 even without an instruction from the user to display the message on the lock screen or the home screen. On the other hand, when the setting of a certain connected device set on the screen 800b is disabled, the chat server 300 remembers that the setting of the connected device is disabled. Then, when there is a notification of the status information of the connected device, the chat server 300 does not send a notification message and the identifier of the terminal device 200 owned by the user to a distribution server (not shown) that performs push notifications. That is, the chat server 300 prevents the message from being automatically displayed on the lock screen or the home screen of the terminal device 200. With these methods, it is also possible to easily set whether to post a message or perform a push notification based on the setting of the connected device via the screen 800b by the user.Also, store the notifications that occurred during the period when the notifications of the connected device are disabled, and when the notification switches to ON along with the change in the attendance status, a list of the stored notifications may be displayed.

[0088] In addition, enable the selection of "telework" or "going to the office" in the work mode 2005, and perform the above-described control when the "attendance" button 2001 is selected in the state where "going to the office" is selected. On the other hand, when the "attendance" button 2001 is selected in the state where "telework" is selected, receive notifications based on the information from the connected devices, including both the connected device set to send notifications at the time of attendance and the connected device set to send notifications at the time of leaving work. Thereby, for example, the user can receive notifications from both the connected device installed in the company and the connected device at home while being at home.

[0089] (Other embodiments) The present invention can also be realized by supplying a program that realizes one or more functions of the above-described embodiments to a system or device via a network or a storage medium, and having one or more processors in the computer of the system or device read and execute the program. It can also be realized by a circuit (for example, ASIC) that realizes one or more functions.

Explanation of reference numerals

[0090] 201 Operation unit 206 CPU 209 HDD

Claims

1. Receiving means for receiving information indicating the state of a machine, Determining means for determining whether the user is at work, working from home, or off work, When it is determined by the determining means that the user is at work, the information from the device set to notify at the time of arrival is notified without notifying the information from the device set to notify at the time of departure. When it is determined by the determining means that the user is off work, the information from the device set to notify at the time of departure is notified without notifying the information from the device set to notify at the time of arrival. When it is determined by the determining means that the user is working from home, notification means for notifying at least the information from the device set to notify at the time of departure. A notification system characterized by comprising:

2. Further comprising setting means for setting whether to notify the information when the user is at work, When it is set by the setting means to notify when the user is at work and it is determined by the determining means that the user is at work, the notification means notifies the information. The notification system according to claim 1, characterized in that:

3. The receiving means receives information indicating the state of each of a plurality of grouped devices, The setting means collectively sets, for the plurality of grouped devices, whether to notify the information indicating the state of each of the plurality of devices when the user is at work. The notification system according to claim 2, characterized in that:

4. The notification system according to claim 3, further comprising receiving means for receiving an operation of grouping the plurality of devices from two or more devices.

5. The setting means further sets whether to notify the information when the user is off work, When it is set to notify by the setting means and it is determined by the determining means that the user is off work, the notification means notifies the information. The notification system according to claim 2, characterized in that:

6. The receiving means receives information indicating the state of each of a plurality of grouped devices, The setting means is characterized in that, for the plurality of grouped devices, it collectively sets whether to notify information indicating the state of each of the plurality of devices when the user is off work, according to the notification system described in claim 5.

7. The notification system according to claim 6, further comprising reception means for receiving an operation of grouping the plurality of devices from two or more devices.

8. It further comprises input means for inputting arrival at the office or telecommuting, The determination means determines whether the user is at the office or telecommuting based on the input by the input means, according to the notification system described in any one of claims 1 to 7.

9. It further comprises a mobile terminal, The input means is characterized in that it is possessed by the mobile terminal, according to the notification system described in claim 8.

10. The device is a multifunction device, a printer, or a washing machine, according to the notification system described in claim 1.

11. A receiving step of receiving information indicating the state of the device; A determination step of determining whether the user is at the office, telecommuting, or off work; A notification method characterized by comprising: a notification step of, when it is determined in the determination step that the user is at the office, not notifying the information from the devices set to notify at the time of leaving work but notifying the information from the devices set to notify at the time of arrival at the office; when it is determined in the determination step that the user is off work, not notifying the information from the devices set to notify at the time of arrival at the office but notifying the information from the devices set to notify at the time of leaving work; and when it is determined in the determination step that the user is telecommuting, at least notifying the information from the devices set to notify at the time of leaving work.

12. It further comprises a setting step of setting whether to notify the information when the user is at the office, When it is set in the setting step to notify when the user is at the office and it is determined in the determination step that the user is at the office, in the notification step, the information is notified, according to the notification method described in claim 11.

13. In the receiving step, information indicating the state of each of the plurality of grouped devices is received, In the setting step, for the plurality of grouped devices, information indicating the state of each of the plurality of devices is collectively set as to whether to notify when the user is at work. The notification method according to claim 12, characterized in that.

14. The notification method according to claim 13, further comprising a reception step of receiving an operation of grouping the plurality of devices from two or more devices.

15. In the setting step, it is further set as to whether to notify the information when the user is off work. The notification method according to claim 12, characterized in that, in the setting step, it is set to notify, and when it is determined in the determination step that the user is off work, the information is notified in the notification step.

16. In the reception step, information indicating the state of each of the plurality of grouped devices is received. The notification method according to claim 15, characterized in that, in the setting step, for the plurality of grouped devices, it is collectively set as to whether to notify the information indicating the state of each of the plurality of devices when the user is off work.

17. The notification method according to claim 16, further comprising a reception step of receiving an operation of grouping the plurality of devices from two or more devices.

18. Further comprising an input step of inputting going to work or teleworking, The notification method according to any one of claims 11 to 17, characterized in that, in the determination step, based on the input in the input step, it is determined whether the user is at work or teleworking.

19. The notification method according to any one of claims 11 to 18, characterized in that the device is a multifunction device, a printer, or a washing machine.

20. A reception step of receiving information indicating the state of the device; A determination step of determining whether the user is at work, teleworking, or off work; When it is determined in the determination step that the user is at work, the information from the device set to notify at the time of arrival is notified without notifying the information from the device set to notify at the time of departure. When it is determined in the determination step that the user is off work, the information from the device set to notify at the time of departure is notified without notifying the information from the device set to notify at the time of arrival. When it is determined in the determination step that the user is teleworking, a notification step of at least notifying the information from the device set to notify at the time of departure, and a program for causing a computer to execute the steps.

Images