Storage medium, information processing system, setting method, and information processing apparatus

Abstract

The present application provides a storage medium, an information processing system, a setting method, and an information processing apparatus. User effort in setting a notification based on information from a plurality of devices is reduced. The setting method includes: registering a plurality of devices; registering devices in the plurality of devices in groups; and changing settings of a notification to a display of an information processing apparatus based on information from a plurality of devices in one group all at once without changing settings of a notification to the display of the information processing apparatus based on information from devices not in the one group.

Description

Technical Field

[0001] This invention relates to storage media, systems, setup methods, and information processing devices. Background Technology

[0002] A monitoring system is disclosed in the prior art that can monitor the status of multiple devices such as air conditioners, televisions and refrigerators by using a terminal such as a smartphone or tablet (see International Publication WO2020 / 017051).

[0003] In this monitoring system, a notification server obtains the status of multiple devices via a network. When the notification server obtains the device status, it sends notifications about the device's operational status and power consumption to the terminal. Users can remotely check the device status using the notification screen displayed on the terminal. The monitoring system allows setting notification conditions, such as notification time slots and days of the week, for each of the multiple devices. This enables users to enable or disable notifications by setting notification conditions for individual devices.

[0004] To enable or disable notifications, existing technologies require changing the notification settings of each device across multiple devices. Summary of the Invention

[0005] The present invention provides a computer-readable storage medium storing a program for causing a computer of an information processing device to perform a control method. The control method includes: registering a plurality of devices; registering devices among the plurality of devices in a group; and simultaneously changing the settings of the notifications to the display of the information processing device based on information from multiple devices in one group, without changing the settings of the notifications to the display of the information processing device based on information from devices not in the same group.

[0006] Further features of the invention will become apparent from the following description of exemplary embodiments with reference to the accompanying drawings. Attached Figure Description

[0007] Figure 1 This is a diagram showing the system configuration.

[0008] Figure 2 This is a block diagram showing the hardware configuration of the terminal.

[0009] Figure 3 This is a block diagram showing the hardware configuration of the chat server.

[0010] Figure 4 This is a block diagram showing the hardware configuration of the device management server.

[0011] Figure 5This is a block diagram illustrating an example of the hardware configuration of multiple connected devices.

[0012] Figures 6A to 6C This is a diagram showing the device registration screen of the terminal.

[0013] Figure 7A and Figure 7B This is a diagram showing the device group registration screen of the terminal.

[0014] Figure 8 This is a diagram showing the terminal's notification switching settings screen.

[0015] Figure 9 This is an image showing the notification screen on the terminal.

[0016] Figure 10 This is a flowchart of the terminal device registration process.

[0017] Figure 11 This is a flowchart of the terminal device group registration process.

[0018] Figure 12 This is a flowchart of MFP's notification processing.

[0019] Figure 13 This is a flowchart of the printer notification processing.

[0020] Figure 14 This is a flowchart of the washing machine's notification processing.

[0021] Figure 15 This is a flowchart of the notification processing of the device management server.

[0022] Figure 16 This is a flowchart of the chat server's notification processing.

[0023] Figure 17 This is a flowchart of the terminal's notification display process.

[0024] Figure 18 This is a flowchart of the terminal's notification switching settings processing. Detailed Implementation

[0025] Embodiments of the present invention will now be described in detail with reference to the accompanying drawings. It should be understood that the following embodiments do not limit the invention according to the claims, and not all combinations of features described in the embodiments are absolutely necessary for the solution of the present invention.

[0026] Figure 1This diagram illustrates an example of the system configuration of the present invention. The system configuration of this embodiment enables a terminal 200, as an example of an information processing device, to communicatively connect to a device management server 400 and a chat server 300 via a network 100, along with multiple connected devices 500a to 500e. The network 100 in this embodiment can be the Internet or a local area network (LAN). The network 100 can be wired or wireless. The terminal 200 is an electronic device owned by a user, such as a personal computer (PC), smartphone, or tablet PC. The user monitors the status of the multiple connected devices via the terminal 200 and issues commands for control. The chat server 300 sends various notifications related to the status of the connected devices sent from the device management server 400 to the terminal 200. The device management server 400 monitors and controls the operation of the multiple connected devices via the network 100. The device management server 400 also obtains the status of the connected devices and sends notification messages containing the device status to the chat server 300 to notify the user of the status. The chat server 300 and the device management server 400 can be configured as a single server.

[0027] Examples of connected devices include various electrical products installed in offices or homes, such as multifunction peripherals (MFPs), lights, air conditioners, refrigerators, electric ovens, and televisions. These connected devices are communicatively connected to the device management server 400 via network 100. Connected devices can receive control commands from and send status information to the device management server 400 by registering registration unit information, which includes information related to the connected device, with the device management server 400. In this embodiment, MFP 1 (500a), MFP 2 (500b), printer (500c), washing machine (500d), and rice cooker (500e) are connected to the device management server 400 via network 100. In the following description, when connected devices 500a to 500e are processed together, they are collectively referred to as connected device 500.

[0028] Figure 2This diagram illustrates an example of the hardware configuration of terminal 200. The operation unit 201 has a touch panel capable of detecting user touch operations and displays various screens provided by the operating system (OS) and chat applications. The user can input desired operator commands to terminal 200 by inputting touch operations to the operation unit 201. Operator commands can be input to terminal 200 using hardware keys (not shown). Camera 202 captures images according to the user's camera commands. Terminal 200 can send and receive data to and from various peripheral devices via Near Field Communication (NFC) 203 or Bluetooth 204. Communication unit 205 communicates with chat server 300 connected via network 100 to receive notifications and exchange messages. Communication unit 205 can be used... Wired communication such as Ethernet or wireless communication such as Wi-Fi. The Central Processing Unit (CPU) 206 reads the control program stored in the Read-Only Memory (ROM) 207 and executes various processes for controlling the operation of the terminal 200. The ROM 207 stores the control program. The Random Access Memory (RAM) 208 serves as a temporary storage area for the CPU 206's main memory and working memory.

[0029] Storage device 209 stores various types of data, such as photos and electronic documents.

[0030] Figure 3 This diagram illustrates an example of the hardware configuration of the chat server 300. The communication unit 301 can send and receive data from the terminal 200 and the device management server 400 via the network 100. The hard disk drive (HDD) 302 stores various data such as user information, notification messages, and image data. The HDD 302 also stores a chat application 303 for performing the chat service and can perform message exchange between users and send notifications to specific users. Messages and notifications can be sent by specifying a unique ID that identifies the user or an identifier that uniquely identifies the terminal 200 as an address. Users can use the chat service by pre-registering user information, including the user ID and the identifier of the terminal 200, with the chat server 300. Registered user information can be shared with the device management server 400. The CPU 304 reads the 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. RAM 306 serves as a temporary storage area for the main memory and working memory of the CPU 304.

[0031] Figure 4This diagram illustrates an example of the hardware configuration of the device management server 400. The communication unit 401 can send and receive data from the connected device 500 and chat server 300 via network 100. The communication unit 401 obtains status information indicating the status of the connected device 500. Examples of status information include the operating status of the connected device 500, setting information, error messages, and the types of events that have occurred. To register a device or obtain status information related to the connected device 500, user information, including a user ID and an identifier for the terminal 200, needs to be pre-registered with the device management server 400. The registered user information can be shared with the chat server 300. The HDD 402 stores various data such as user information, registration unit information related to the connected device 500 registered by the user, connected device group information, connected device notification settings, and status information obtained from the connected device 500. The CPU 403 reads the control program stored in the ROM 404 and executes various processes for controlling the operation of the device management server 400. ROM 404 stores the control program. RAM 405 is used as a temporary storage area for main memory and working memory such as CPU 403.

[0032] Figure 5 This is a diagram illustrating an example of the hardware configuration of the connected devices, MFP 1 (500a), printer (500c), and washing machine (500d).

[0033] The MFP 1 (500a) includes a CPU 501a, a ROM 502a, a RAM 503a, a storage device 504a, an operation unit 505a, a printing unit 506a, a reading unit 507a, and a communication unit 508a. The CPU 501a controls the operation of the entire MFP 1 (500a). The CPU 501a reads the control program stored in the ROM 502a or the storage device 504a into the RAM 503a to perform various control operations such as read control and print control. The ROM 502a stores the control program that can be executed by the CPU 501a. The RAM 503a is the main memory and also serves as a temporary storage area for decompressing the various control programs stored in the working area, the ROM 502a, and the storage device 504a. The storage device 504a stores image data, print data, various programs, and various setting information items. In this embodiment, the storage device 504a is a flash memory. Other examples include auxiliary storage devices such as solid-state drives (SSDs) and hard disk drives (HDDs). Another example is an embedded multimedia card (eMMC). The MFP 1 (500a) of this embodiment performs a series of processes, described later, performed by a CPU 501a using a memory (RAM 503a). However, this is merely illustrative. For example, multiple components (CPU, RAM, ROM, and storage devices) may cooperate to perform the flowchart described later. Hardware circuitry such as application-specific integrated circuits (ASICs) or field-programmable gate arrays (FPGAs) may be used to perform a portion of the processing. Examples of operation units 505a include displays such as touch panels and hard keys. Operation units 505a display information to the user and detect input from the user. Printing units 506a can print image data (print data) stored in RAM 503a onto recording paper fed from the paper tray. Reading units 507a read images from a document. The CPU 501a converts the images into image data such as binary data. Image data generated from the image read by reading unit 507a is sent to an external device or printed on recording paper. Communication unit 508a is connected to network 100. Communication unit 508a transmits device-related status information to device management server 400. Examples of status information include job status (such as copying and faxing), notifications of toner and paper (recording material) levels, error messages (such as fault location), and the type of event that occurred. Communication unit 508a sends image data to an external device on network 100 or receives print data from terminal 200.Examples or methods of sending and receiving via network 100 include sending and receiving via email and sending files using other protocols such as File Transfer Protocol (FTP), Server Message Blocks (SMB), and Web-based Distributed Authoring and Versioning (WEBDAV). Another example is sending and receiving image data and various settings data from terminal 200 via network 100 through Hypertext Transfer Protocol (HTTP) communication.

[0034] The printer (500c) includes a CPU 501c, a ROM 502c, a RAM 503c, a storage device 504c, an operation unit 505c, a printing unit 506c, and a communication unit 507c. The CPU 501c controls the operation of the entire printer (500c). The CPU 501c reads the control program stored in the ROM 502c or the storage device 504c into the RAM 503c to perform various control operations such as print control. The ROM 502c stores the control program that can be executed by the CPU 501c. The RAM 503c is the main memory and also serves as a temporary storage area for decompressing the various control programs stored in the working area, the ROM 502c, and the storage device 504c. The storage device 504c stores image data, print data, various programs, and various setting information items. In this embodiment, the storage device 504c is a flash memory. Other examples include auxiliary storage devices such as SSDs and HDDs. Another example is eMMC. The printer (500c) of this embodiment executes a series of processes, described later, performed by a CPU (501c) using a memory (RAM (503c)). However, this is merely illustrative. For example, multiple components (CPU, RAM, ROM, and storage devices) may cooperate to execute the flowchart described later. Hardware circuitry such as an ASIC or FPGA may be used to execute a portion of the processing. Examples of the operation unit 505c include a display such as a touch panel and hard keys. The operation unit 505c displays information to the user and detects input from the user. The printing unit 506c can print image data (print data) stored in RAM 503c onto recording paper fed from the paper tray. The communication unit 507c is connected to the network 100. The communication unit 507c transmits device-related status information to the device management server 400. Examples of status information include the status of the print job, notifications of insufficient or insufficient toner and printing paper (recording material), error messages (such as malfunctions), and the type of event that has occurred. The communication unit 507c also receives print data from the terminal 200 on the network 100.

[0035] 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 operation of the entire washing machine (500d). The CPU 501d reads the control program stored in the ROM 502d into the RAM 503d to perform various control operations such as motor control and water level control. The ROM 502d stores the control program that can be executed by the CPU 501d. The RAM 503d is the main memory and also serves as a temporary storage area for decompressing the various control programs stored in the working area and the ROM 502d. Examples of the operation unit 504d include a display such as a touch panel and hard keys. The motor control unit 505d controls the rotational speed of the motor in the washing tub. The water level control unit 506d controls the water level in the washing tub and controls water inlet and outlet. The communication unit 507d is connected to a network 100. Communication unit 507d is connected to network 100. Communication unit 507d transmits device-related status information to device management server 400. Examples of status information include operating status, error messages (such as faults), and the type of event that has occurred. Communication unit 507d also receives control commands from external devices on network 100.

[0036] Figures 6A to 6C This shows an example of a screen displayed on the operation unit 201 of terminal 200 for registering the connected device with the device management server 400.

[0037] Screen 600a displays connected devices registered with the device management server 400, where any given name given by the user to the connected device and the category of the connected device are listed in columns 601 and 602, respectively. Examples of connected device categories include multifunction devices, printers, rice cookers, and washing machines. Users pre-register their user information with the device management server 400 before registering the device. When registering an additional device with the device management server 400, the user selects the Add Device button 603 displayed on screen 600a.

[0038] Screen 600b is displayed when the user selects the Add Device button 603. Screen 600b lists devices that have not been registered with the Device Management Server 400. Screen 600b displays the device category and product name. The listed devices can be devices identified via NFC 203 or Bluetooth 204 provided in terminal 200, or devices on the same network. The user selects the desired device to register with the Device Management Server 400 from the devices displayed on screen 600.

[0039] Screen 600c is the screen displayed when the user selects any device from the devices listed on screen 600b. In screen 600c, the category and product name of the device selected on screen 600b, "Printer (PRINTER-2000B)," is displayed in field 605.

[0040] Screen 600c also displays the name field 606 of the selected device. The user enters any name in the name field 606. By entering a name and selecting the registration button 607, the registration unit information is sent to the device management server 400, and registration is completed. In addition to the name entered on screen 600c, examples of registration unit information include the device category, product name, and media access control (MAC) address. The registration unit information also includes unique identification information assigned to the device (such as a serial number) and information related to the registered user.

[0041] Figure 7A and Figure 7B This is an example diagram showing a screen displayed on the operation unit 201 of terminal 200 for group registration of connected devices. Group registration means that a user registers one or more connected devices together as a group on the device management server 400.

[0042] Screen 700a displays information about connected device groups, showing the connected devices registered with the device management server 400. In this embodiment, screen 700a displays a list of arbitrary names given by the user to the connected devices and a list of groups to which the connected devices belong, in columns 701 and 702, respectively. To register a new group with the device management server 400, the user selects the new group registration button 703 displayed on screen 700a.

[0043] Screen 700b is displayed when the user selects the New Group Registration button 703. Screen 700b displays a group name field 704 for entering the name of the newly created group, where the user can enter any group name. The connected devices field 705 displays the connected devices and checkboxes 706 for selecting whether to include the connected devices in the new group. By having the user select the connected devices to be included in the new group and then select the Registration button 707, the group information is sent to the device management server 400, and the group registration is completed. Examples of group information include the group name entered on screen 700b, registration unit information related to the selected connected devices, and information related to the user who created the group. In the example of screen 700b, three connected devices, "Study Room Printer," "Home Kitchen Rice Cooker," and "Home Washing Machine," are included in a group called "Home Appliances." In this embodiment, the connected devices belong to one group. Alternatively, the connected devices may be included in multiple hierarchical groups. For example, “Headquarters 1F Multifunction Unit” can be included in two groups: “Headquarters Printer” and “Headquarters 1F Printer”, where “Headquarters 1F Printer” is a subgroup of “Headquarters Printer”.

[0044] Figure 8 This diagram illustrates an example of a notification settings screen displayed on the operation unit 201 of terminal 200. The notification settings screen 800 allows switching between various notification settings related to whether or not to display on terminal 200 the status notifications generated by device management server 400 regarding the connected device 500. The notification settings configured on the notification settings screen 800 are sent to device management server 400 for storage.

[0045] The notification settings screen 800 displays the groups registered with the device management server 400 and the connected devices belonging to those groups. The notification settings screen 800 also displays a toggle switch for group notification switching settings, which relates to whether or not notifications containing status information about all connected devices belonging to the group are displayed on the terminal 200. Users can switch the group notification settings by "turning off" the toggle switch to prevent the display of notifications related to all connected devices in the group. Similarly, users can switch the group notification settings by "turning on" the toggle switch to display notifications related to all connected devices in the group. For example, the notification settings screen 800 displays "Headquarters Printer" group 801, which is a group registered with the device management server 400, and "Headquarters 1F Multifunction Device" 802 and "Headquarters 2F Multifunction Device" 803 belonging to that group. Users can disable the notification settings 811 and 812 for devices 802 and 803 connected to the "Headquarters Printer" group 801 by using the group notification switching setting 810 to disable the "Headquarters Printer" group 801. Similarly, the notification settings screen 800 displays the "Home Appliances" group 804 and all connected devices belonging to the "Home Appliances" group 804 ("Study Printer" 805, "Home Kitchen Rice Cooker" 806, and "Home Washing Machine" 807). Users can enable the notification settings 814, 815, and 816 for devices 805, 806, and 807 connected to the "Home Appliances" group 804 by using the group notification switching setting 813 to enable the "Home Appliances" group 804. As shown in the notification settings screen 800, connected devices not belonging to any group can be collectively displayed as "Ungrouped" 808.

[0046] The group notification switching setting 817 for "Ungrouped" 808 is "Off," and the notification setting 818 for "Branch A Printer," which does not belong to any group, is also "Off." Alternatively, notification settings different from the group notification switching settings of the group to which the connected device belongs can be changed individually. For example, even when the group notification switching setting 813 for "Home Appliances" group 804 is "On," the notification setting 814 for the study room printer 805 can be "Off." If the connected devices belong to multiple hierarchical groups, the subgroup notification switching settings and the notification settings of all connected devices belonging to the subgroup can be switched simultaneously by switching the group notification switching setting of the higher-level group. The subgroup's group notification switching setting can be switched to a different notification setting than the higher-level group's. For example, if the group notification switching setting of the higher-level group ("Headquarters Printer" group) is "On," and in this state, the group notification switching setting of the subgroup ("Headquarters 1F Printer" group) can be "Off," and the group notification switching setting of "Headquarters 2F Printer" can be "On." In this case, both notification settings for devices connected to the "Headquarters 1F Printers" group are "turned off," and both notification settings for devices connected to the "Headquarters 2F Printers" group are "turned on."

[0047] Figure 18 It is what is displayed on the operation unit 201 of the selected terminal 200. Figure 8 The flowchart illustrates the notification switching process that begins when group notification switching setting 810 is selected on screen 800. Each operation (step) in the flowchart is executed by the CPU 206, which reads the control program stored in ROM 207 or storage device 209 into RAM 208. Here is an example of selecting group notification switching setting 810. The same process is also executed when group notification switching setting 813 or group notification switching setting 817 is selected. Figure 18 The process is shown in the flowchart.

[0048] In S1801, CPU 206 determines whether Group Notification Switching Setting 810 has been changed to "ON". When the user selects Group Notification Switching Setting 810 when it is "OFF", CPU 206 determines that Group Notification Switching Setting 810 has changed to ON. If CPU 206 determines that Group Notification Switching Setting 810 has changed to ON, CPU 206 proceeds to S1802. If CPU 206 determines that Group Notification Switching Setting 810 has not changed to ON, CPU 206 proceeds to S1810.

[0049] In S1802, CPU 206 stores variable N in RAM 208 and sets variable N to 1.

[0050] In S1803, CPU 206 changes the notification setting of the Nth device in the group of group notification switching setting 810 to ON. If the original notification setting of the Nth device is OFF, CPU 206 changes the setting to ON. If the original notification setting of the Nth device is ON, CPU 206 retains the setting.

[0051] In S1804, CPU 206 determines whether there are other devices in the group.

[0052] If CPU 206 determines that there are other devices in the group, CPU 206 proceeds to S1805. If CPU 206 determines that there are no other devices in the group, CPU 206 terminates. Figure 18 The process is shown in the flowchart.

[0053] If the process proceeds from S1801 to S1810, CPU 206 determines whether Group Notification Switching Setting 810 has been changed to OFF. If the user selects Group Notification Switching Setting 810 when it is ON, CPU 206 determines that Group Notification Switching Setting 810 has been changed to OFF. If CPU 206 determines that Group Notification Switching Setting 810 has been changed to OFF, CPU 206 proceeds to S1806. Conversely, if CPU 206 determines that Group Notification Switching Setting 810 has not been changed to OFF, CPU 206 proceeds to S1801.

[0054] In S1806, CPU 206 stores variable N in RAM 208 and sets variable N to 1.

[0055] In S1807, CPU 206 changes the notification setting of the Nth device in the group of group notification switching setting 810 to OFF. If the original notification of the Nth device was set to ON, CPU 206 changes that setting to OFF. If the original notification of the Nth device was set to OFF, CPU 206 retains that setting.

[0056] In S1808, CPU 206 determines whether there are other devices in the group.

[0057] If CPU 206 determines that there are other devices in the group, then CPU 206 proceeds to S1809. If CPU 206 determines that there are no other devices in the group, then CPU 206 terminates. Figure 18 The process is shown in the flowchart.

[0058] The ON / OFF notification settings of each connected device set on screen 800 are sent to device management server 400 for storage.

[0059] Figure 9 This is an example diagram showing a notification screen displayed on the operation unit 201 of terminal 200. Notification screen 900 displays a notification about the status of the connected device sent from chat server 300. Notification screen 900 displays two notifications, 901 and 905. As shown in notification 901, each notification includes an icon and name 902 of the connected device, a notification date 903, and a message 904 related to the status of the connected device. Notification 901 indicates that terminal 200 received a notification at "2021 / 10 / 5 10:21" regarding the status of a connected device named "Household Washing Machine". The user is notified that the washing using the "Household Washing Machine" ended at 10:21 as a message. Similarly, notification 905 indicates that terminal 200 received a notification at "2021 / 10 / 5 11:45" regarding the status of a connected device named "Study Room Printer". The user is notified that printing with the "Study Room Printer" was successfully completed as a message. The notification screen 900 can be displayed on a chat application installed on the terminal 200 and communicating with the chat server 300 to provide chat services. Alternatively, the notification screen 900 can be displayed on the status area or lock screen normally displayed on the operation unit 201.

[0060] Figure 10 This is a flowchart of the device registration process that begins when the Add Device button 603 is selected on the screen 600a displayed on the operation unit 201 of the terminal 200. Each operation (step) in the flowchart is executed by the CPU 206, which reads the control program stored in the ROM 207 or the storage device 209 into the RAM 208.

[0061] In S1001, CPU 206 searches for devices to register with device management server 400 and obtains identification information to uniquely identify the device. For the search method, devices on the same network (LAN) can be detected via communication unit 205 according to Address Resolution Protocol (ARP). Alternatively, devices can be detected via near-field communication (such as NFC 203 or Bluetooth 204). Examples of identification information include the media access control (MAC) address or serial number of each device.

[0062] In S1002, CPU 206 queries device management server 400 to determine whether identification information related to the devices found in the search in S1001 has been registered with device management server 400. If the query result indicates that the devices found in S1001 include one or more devices that have not been registered with device management server 400, the process proceeds to S1003. Conversely, if no devices have not been registered with device management server 400, the device registration process ends.

[0063] In S1003, CPU 206 displays a list of devices that were determined in S1002 not to have registered with the device management server 400 on screen 600b.

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

[0065] In S1005, the CPU 206 inputs information such as the name of the device selected in S1004 as registration unit information on the screen 600c.

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

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

[0068] Figure 11 This is a flowchart of group registration that begins when the new group registration button 703 is selected on the screen 700a displayed on the operation unit 201 of terminal 200. Each operation (step) in the flowchart is executed by the CPU 206, which reads the control program stored in ROM 207 or storage device 209 into RAM 208.

[0069] In S1101, CPU 206 obtains the registration unit information registered with device management server 400 and displays a list of registered devices on screen 700b. In S1101, device management server 400 only sends the registration unit information of users registering for the current flowchart to terminal 200. The registration unit information to be sent by device management server 400 can be changed according to other conditions.

[0070] In S1102, terminal 200 receives input from the user for the group name in group name field 604 on screen 700b, and selects one or more connected devices to be grouped.

[0071] In S1103, terminal 200 receives from the user the selection of the registration button 607 displayed on screen 700c.

[0072] In S1104, CPU 206 sends group information to device management server 400 via communication unit 205.

[0073] Figure 12This is a flowchart illustrating the process by which MFP 1 (500a) sends status information to the device management server 400. Each operation (step) in the flowchart is executed by the CPU 501a, which reads the control program stored in ROM 502a or storage device 504a into RAM 503a.

[0074] In S1201, CPU 501a detects events. Examples of events include: the completion of a copy, fax, or other job performed by MFP 1 (500a); the fact that the remaining toner or printing paper has fallen below a predetermined threshold; and the occurrence of a fault. Instructions to send status information from the device management server 400 are also included in the events.

[0075] In S1202, CPU 501a collects status information to be sent to device management server 400. The status information collected by CPU 501a includes the operating status, setting information, error information, and event type of MFP 1 (500a). The information to be collected can be changed according to the event. For example, in the case of a job completion event, the type and date of the completed job and the result of the job can be collected; and in the case of a fault event, information related to the fault location and fault date can be collected.

[0076] In S1203, CPU 501a controls communication unit 508a, causing communication unit 508a to send the collected status information to device management server 400.

[0077] Figure 13 This is a flowchart illustrating the process by which the printer (500c) sends status information to the device management server 400. Each operation (step) in the flowchart is executed by the CPU 501c, which reads the control program stored in ROM 502c or storage device 504c into RAM 503c.

[0078] In S1301, CPU 501c detects events. Examples of events include: the completion of a printing or other job performed by the printer (500c); the fact that the remaining toner or printing paper has fallen below a predetermined threshold; and the occurrence of a fault. Instructions to send status information from the device management server 400 are also included in the events.

[0079] In S1302, CPU 501c collects status information to be sent to device management server 400. The status information collected by CPU 501c includes the printer's (500c) operating status, setting information, error information, and event type. The information to be collected can be changed according to the event. For example, in the case of a job completion event, the type and date of the completed job and the job result can be collected; and in the case of a fault event, information related to the fault location and fault date can be collected.

[0080] In S1303, CPU 501c controls communication unit 507c, causing communication unit 507c to send the collected status information to device management server 400.

[0081] Figure 14 This is a flowchart illustrating the process by which the washing machine (500d) sends status information to the device management server 400. Each operation (step) in the flowchart is executed by the CPU 501d, which reads the control program stored in ROM 502d into RAM 503d.

[0082] In S1401, CPU 501d detects events. Examples of events include: washing completed; the detection that the operation could not continue due to lack of water supply or an open lid; and the occurrence of a fault. Instructions for sending status information from the device management server 400 are also included in the events.

[0083] In S1402, CPU 501d collects status information to be sent to device management server 400. The status information collected by CPU 501d includes the operating status of the washing machine (500d), setting information, error information, and event types. The information to be collected can be changed based on the event. For example, in the case of a washing completion event, the washing completion date can be collected, and in the case of a fault event, information related to the fault location and fault date can be collected.

[0084] In S1403, CPU 501d controls communication unit 507d, causing communication unit 507d to send the collected status information to device management server 400.

[0085] Figure 15 This is a flowchart illustrating the process by which the device management server 400 sends status information obtained from the connected device 500 to the chat server 300. Each operation (step) in the flowchart is executed by the CPU 403, which reads the control program stored in ROM 404 or HDD 402 into RAM 405.

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

[0087] In S1502, CPU 403 analyzes the status information received in S1501 to determine whether to report the status of the connected device 500 to the user. Examples of statuses to be reported include the completion of a process performed by the connected device 500 and the detection of a fault in the connected device 500. The notification conditions used to determine whether to issue a notification are pre-stored in the HDD 402 of the device management server 400. Alternatively, the notification conditions can be set by the user for each connected device. For example, assuming that the notification conditions for MFP 1 (500a) include "the printing of the received fax document is complete," when CPU 403 determines that the status information includes an event type indicating that the printing of the received fax document is complete, CPU 403 determines that the status should be reported to the user. If CPU 403 determines that the status should be reported as a result of the analysis, the process proceeds to S1503. Otherwise, the flowchart ends.

[0088] In S1503, CPU 403 obtains the notification setting of the connected device 500 that was determined to be reported in S1502. If it is set to "ON", the process proceeds to S1504. If it is set to "OFF", the flowchart ends. Although the group notification switching setting in S1503 determines where the process branches, the notification setting of the connected device determined to be reported can be used for branching.

[0089] In S1504, CPU 403 creates a notification message. The notification message is created based on status information. The message can be created using a format defined for each event type, or a user-defined fixed message can be used. The notification message may include the name and type of the connected device, its icon, and other information.

[0090] In S1505, CPU 403 searches the registration unit information stored in HDD 402 for user information related to the user of the connected device 500 that was determined to be reported in S1502.

[0091] In S1506, CPU 403 sends the user ID and the notification message created in S1504 to chat server 300, so that the notification message is sent to the user specified in S1505.

[0092] Figure 16 This is a flowchart illustrating the process by which the chat server 300 notifies the terminal 200 of a notification message sent from the device management server 400. Each operation (step) in the flowchart is executed by the CPU 304, which reads the control program stored in ROM 305 or HDD 302 into RAM 306.

[0093] In S1601, the CPU 304 detects the receipt of a notification message and its destination (i.e., user ID) sent from the device management server 400 via the communication unit 301.

[0094] In S1602, CPU 304 stores the notification message received in S1601 in the destination user's message history. The notification message stored in the message history can be traced by the user.

[0095] In S1603, CPU 304 notifies the destination user of the notification message received in S1601. In this embodiment, the notification is provided to terminal 200 via the distribution server by sending the notification message and the identifier of the user's terminal 200 to the distribution server (not shown) that performs the push notification.

[0096] Figure 17 This is a flowchart of the process by which terminal 200 displays notification messages sent from chat server 300. Each operation (step) in the flowchart is executed by CPU 206, which reads the control program stored in ROM 207 or storage device 209 into RAM 208.

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

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

[0099] This embodiment illustrates an example where the device management server 400 determines at S1503 whether to generate a notification message at S1504. However, the present invention is not limited to the above example. For example, the device management server 400 may omit step S1503 and must perform the creation and publication of the notification message to the chat server 300 from steps S1504 to S1506, and may operate as follows: The terminal 200 may access the chat server 300 to determine whether to display the notification message on the notification screen 900 based on group notification switching settings or connected device notification settings. In this case, the chat server 300 does not send the notification message to the distribution server and only adds the message to the history at S1602. The terminal 200 determines whether to display the notification message at a timed interval when the chat server 300 obtains the message history.

[0100] Alternatively, the device management server 400 can omit step S1503 and must still create and publish the notification message to the chat server 300 from steps S1504 to S1506, and can operate as follows: The device management server 400 can determine whether to send the notification message and the user's terminal 200 identifier to the distribution server (not shown) that performs push notifications based on the notification settings of the connected device that sent the status information. If the connected device notification settings are enabled, the device management server 400 instructs the chat server 300 to send the notification message and the user's terminal 200 identifier to the distribution server (not shown). This allows the terminal 200 to display the notification message on the lock screen, etc., even without a notification display instruction from the user. If the connected device notification settings are disabled, the device management server 400 instructs the chat server 300 not to send the notification message and the user's terminal 200 identifier to the distribution server (not shown). In this case, the terminal 200 does not need to display the notification message on the lock screen, etc.

[0101] Therefore, one or more connected devices can be registered as a group, and the notification settings for the operation unit 201 of the terminal 200 based on information from multiple devices belonging to multiple groups can be changed simultaneously for each group. This eliminates the need to enable individual notification settings for the study printer 805, the kitchen rice cooker 806, and the washing machine 807 when the user wishes to receive notifications from home appliances. Alternatively, by selecting the group notification switching setting 813, the settings for multiple connected devices registered as home appliance groups can be changed simultaneously.

[0102] Therefore, when leaving the office, the user can use group notification switching setting 810 to turn off notification settings based on information related to connected devices in the headquarters printer group. When returning home, the user can use group notification switching setting 813 to turn on notification settings based on information related to connected devices in the home appliance group.

[0103] The enabling / disabling of notification settings for each connected device set on screen 800 can be stored in chat server 300, and chat server 300 can determine whether to publish a message for the connected device. If the notification settings for a specific connected device set on screen 800 are enabled, chat server 300 stores the enabled notification settings for the connected device. When a notification of status information related to the connected device is given, chat server 300 publishes a message based on that notification. Conversely, if the notification settings for a specific connected device set on screen 800 are disabled, chat server 300 stores the disabled notification settings for the connected device. When a notification of status information related to the connected device is given, chat server 300 does not publish a message based on that notification. This is an example of whether to publish. Alternatively, push notifications can be made to terminal 200. If the notification settings for a specific connected device set on screen 800 are enabled, chat server 300 stores the enabled notification settings for the connected device. When a notification of status information for the connected device is given, chat server 300 sends the notification message and the identifier of the user's terminal 200 to a distribution server (not shown) that made the push notification. In other words, even if the user does not give a message display command, the chat server 300 automatically displays the message on the lock screen or home screen of the terminal 200. Conversely, if the notification settings for a specific connected device set on the screen 800 are disabled, the chat server 300 stores the disabled notification settings for the connected device. When a notification of the status information of the connected device is given, the chat server 300 does not send the notification message and the identifier of the user's terminal 200 to the distribution server (not shown) that performs push notifications. In other words, the chat server 300 prevents the lock screen or home screen of the terminal 200 from automatically displaying the message. This facilitates setting whether to publish a message or perform a push notification based on the notification settings of the connected device configured by the user via the screen 800.

[0104] Other embodiments

[0105] The embodiments of the present invention can also be implemented by providing software (programs) that perform the functions of the above embodiments to a system or device via a network or various storage media, and the computer or central processing unit (CPU) or microprocessor unit (MPU) of the system or device reads out and executes the program.

[0106] While the invention has been described with reference to exemplary embodiments, it should be understood that the invention is not limited to the disclosed exemplary embodiments. The scope of the appended claims should be given the broadest interpretation to cover all such modifications and equivalent structures and functions.

Claims

1. A computer-readable storage medium storing a program for causing a computer of an information processing device to perform a control method, the control method comprising: Register multiple devices; Among them, two or more of the multiple devices are also associated with the first group of the multiple groups, and Among these, other devices in the multiple devices are not registered in association with any of the multiple groups; and Change notification settings at the user interface to enable notifications for one or more of multiple devices, and send notifications to the information processing device, where each notification is based on information about the status or conditions of the corresponding device. The user interface is configured such that devices associated with the first group can enable device notifications even when other devices in the first group have not enabled their notifications, and the user interface is also configured such that notification settings for each of the two or more devices associated with the first group can be changed based on a single user input. Send a notification to the information processing device about one or more of a plurality of devices that have enabled notification settings.

2. The computer-readable storage medium according to claim 1, wherein, Without changing the settings of the notifications to the display of the information processing device based on information from devices in other groups, the settings of the notifications to the display based on information from multiple devices in one group are changed simultaneously.

3. The computer-readable storage medium according to claim 1, wherein, The settings of individual notifications for multiple devices in a group can be changed separately from the settings of notifications for the display based on information from multiple devices in the group.

4. The computer-readable storage medium according to claim 1, wherein, It can also change the notification settings for devices that are not registered in any group.

5. The computer-readable storage medium according to claim 4, wherein, It can change the settings of individual notifications for multiple devices that are not registered in any group.

6. The computer-readable storage medium according to claim 1, wherein the control method further comprises: Create an additional group.

7. The computer-readable storage medium according to any one of claims 1 to 6, wherein, Information from the plurality of devices includes information based on events generated in the plurality of devices.

8. The computer-readable storage medium according to any one of claims 1 to 6, wherein, The plurality of devices includes a multifunctional device capable of printing.

9. The computer-readable storage medium according to claim 8, wherein, The information includes information indicating that the recording material in the multifunctional device is insufficient.

10. The computer-readable storage medium according to any one of claims 1 to 6, wherein, The information processing equipment includes a smartphone.

11. An information processing system, comprising: Device management server, used to obtain device information from multiple devices; A chat server is used to send notifications to information processing devices based on information obtained from the device management server. Registration components are used to register individual devices in groups; The configuration component is used to configure whether to enable notifications based on information from multiple devices in a group registered by the registration component. A determination component is used to determine whether the notification has been set to be enabled by the setting component; A generation component is used to generate a notification based on the device information when it is determined that the notification is set to be enabled; as well as A sending component is used to send the notification generated by the generating component to the information processing device. Among them, two or more of the multiple devices are also associated with the first group of the multiple groups, and Among these, other devices in the multiple devices are not registered in association with any of the multiple groups; and Change notification settings at the user interface to enable notifications for one or more of multiple devices, and send notifications to the information processing device, where each notification is based on information about the status or conditions of the corresponding device. The user interface is configured such that devices associated with the first group can enable device notifications even when other devices in the first group have not enabled their notifications, and the user interface is also configured such that notification settings for each of the two or more devices associated with the first group can be changed based on a single user input. Send a notification to the information processing device about one or more of a plurality of devices that have enabled notification settings.

12. A setting method, comprising: Register multiple devices; Among them, two or more of the multiple devices are also associated with the first group of the multiple groups, and Among these, other devices in the multiple devices are not registered in association with any of the multiple groups; and Change notification settings at the user interface to enable notifications for one or more of multiple devices, and send notifications to the information processing device, where each notification is based on information about the status or conditions of the corresponding device. The user interface is configured such that devices associated with the first group can enable device notifications even when other devices in the first group have not enabled their notifications, and the user interface is also configured such that notification settings for each of the two or more devices associated with the first group can be changed based on a single user input. Send a notification to the information processing device about one or more of a plurality of devices that have enabled notification settings.

13. An information processing device, comprising: The first registration component is used to register multiple devices; Among them, two or more of the multiple devices are also associated with the first group of the multiple groups, and Among these, other devices in the multiple devices are not registered in association with any of the multiple groups; and Change notification settings at the user interface to enable notifications for one or more of multiple devices, and send notifications to the information processing device, where each notification is based on information about the status or conditions of the corresponding device. The user interface is configured such that devices associated with the first group can enable device notifications even when other devices in the first group have not enabled their notifications, and the user interface is also configured such that notification settings for each of the two or more devices associated with the first group can be changed based on a single user input. Send a notification to the information processing device about one or more of a plurality of devices that have enabled notification settings.

Images