Management system, management device, and computer program

Abstract

To provide a meaningful technique in a system that manages a plurality of devices via a general-purpose intermediate device.SOLUTION: A first communication device 3, 5 is configured to repeatedly write multiple pieces of status data corresponding to a plurality of devices 4, 5 in a cloud storage 93. A second communication device 2 is configured to switch each of the plurality of devices between a display object and a non-display object. The second communication device is configured to cause a display device to display a device list indicating status of each of one or more devices set as the display object among the plurality of devices. The first communication device repeatedly writes the multiple pieces of status data about the plurality of devices in the cloud storage, regardless of setting of the display object and non-display object. The second communication device repeatedly acquires the status data of each of at least the devices set as the display object from the cloud storage, and updates the device list.SELECTED DRAWING: Figure 1

Description

[Technical field]

[0001] The present disclosure relates to a management system and a management device. [Background technology]

[0002] There are already known techniques for managing information about image forming devices and remotely monitoring the operating status, etc., of the image forming devices. For example, a system is known in which a monitoring device collects information about the image forming devices via a network and displays the collected information on the screen of the monitoring device or on the screen of a client PC connected to the monitoring device (see Patent Document 1). [Prior art documents] [Patent documents]

[0003] [Patent Document 1] JP 2012-48567 A Summary of the Invention [Problem to be solved by the invention]

[0004] However, communication between terminal devices via a wide area network is generally performed via a server device for the security of the local area network to which each terminal device belongs. Similarly, when a management device remotely manages a managed device, it is possible to place a server device between the managed device and the management device. However, the method of constructing a dedicated server device results in high operating costs for the management system.

[0005] On the other hand, when a general-purpose intermediate device is used instead of a dedicated server device, the intermediate device cannot realize the various management functions that can be realized by using a dedicated server device.

[0006] Therefore, according to one aspect of the present disclosure, it is desirable to provide a technique that is useful for managing devices in a system in which a management device manages a plurality of devices via a general-purpose intermediate device. [Means for solving the problem]

[0007] A management system according to an aspect of the present disclosure includes at least one first communication device and a second communication device. The at least one first communication device is configured to repeatedly write a plurality of status data to a cloud storage. Each of the plurality of status data is configured as data describing a status of a corresponding device among a plurality of devices. The second communication device is configured to be able to access the cloud storage.

[0008] The second communication device is configured to set each of the multiple devices as a display target or a hidden target so as to switch between a display target and a hidden target based on a switching instruction input through a user interface, to list one or more devices set as a display target among the multiple devices, and to display on a display device a device list indicating the respective statuses of the one or more devices.

[0009] The at least one first communication device is configured to repeatedly write a plurality of state data for a plurality of devices to the cloud storage, regardless of settings of display targets and non-display targets.

[0010] The second communication device is further configured to repeatedly acquire, from the cloud storage, status data for each of at least one or more devices set as display targets among the multiple devices, and update the device list based on the acquired status data to indicate the latest status of each of the one or more devices.

[0011] This management system uses general-purpose cloud storage and can display on a display device a device list showing the latest status of one or more devices to be displayed, thus providing the administrator with information that is useful for managing multiple devices.

[0012] Furthermore, according to this management system, the display and non-display of each device in the device list can be switched based on instructions via the user interface, and even when a device is switched from hidden to displayed, the second communication device can obtain status data of the device without switching the operation of the corresponding device.

[0013] In this way, by configuring the display / hide of a device and the uploading of status data from the device separately, it is possible to efficiently switch the display / hide of each device along with its status display using general-purpose cloud storage, without the need for complex coordination between the first communication device and the second communication device.

[0014] Therefore, according to one aspect of the present disclosure, it is possible to provide a useful technique for managing devices in a system in which a management device manages multiple devices via general-purpose cloud storage.

[0015] According to an aspect of the present disclosure, a management device for realizing a management system may be provided. The management device according to the aspect of the present disclosure includes a communication unit and a processing unit. The communication unit is configured to be able to access cloud storage that stores a plurality of status data that are repeatedly updated. Each of the plurality of status data is configured as data that describes a status of a corresponding device among a plurality of devices.

[0016] The processing unit is configured to execute processing related to the plurality of devices, such as setting each of the plurality of devices to be a display target or a non-display target, so as to switch between the display target and the non-display target based on a switching instruction input through the user interface.

[0017] The processing unit is further configured to repeatedly acquire, via the communication unit, status data of each of the plurality of devices including the device set to be hidden from the cloud storage.

[0018] The processing unit is further configured to display, on the display device, a device list indicating the status of each of the one or more devices that are set as display targets among the multiple devices based on the repeatedly acquired status data, and to update the device list so as to indicate the latest status of each of the one or more devices.

[0019] According to this management device, in a situation where a plurality of devices are managed via cloud storage, it is possible to provide the administrator with information that is useful for managing the plurality of devices.

[0020] According to an aspect of the present disclosure, a computer program may be provided for causing a computer to realize functions as a management device.

[0021] According to one aspect of the present disclosure, a computer program may be provided for causing a computer of a communication device that can access a cloud storage that stores multiple pieces of status data that are repeatedly updated to set each of multiple devices as a display target or a hidden target so as to switch between a display target and a hidden target based on a switching instruction input through a user interface, repeatedly acquiring status data of each of the multiple devices including the device that is set as a hidden target from the cloud storage, and displaying, on a display device, a device list showing the status of each of the one or more devices that are set as a display target among the multiple devices based on the repeatedly acquired status data, and updating the device list to show the latest status of each of the one or more devices. According to this computer program, the communication device can be used to function as the above-mentioned management device and to build a management system. [Brief description of the drawings]

[0022] [Figure 1] FIG. 1 is a block diagram showing an overall configuration of a management system. [Diagram 2]FIG. 2A is a block diagram showing the configuration of a master, FIG. 2B is a block diagram showing the configuration of a client, and FIG. 2C is a block diagram showing the configuration of a first type terminal device. [Diagram 3] FIG. 3A is a block diagram showing the configuration of a second type terminal device, and FIG. 3B is a block diagram showing the configuration of a cloud server. [Figure 4] FIG. 4 is a schematic sequence diagram relating to the operation of the management system. [Diagram 5] FIG. 5A is a diagram showing the configuration of a schedule task table, and FIG. 5B is a diagram showing the configuration of an instant task table. [Figure 6] FIG. 13 illustrates an exemplary configuration of a device management screen including a device list. [Figure 7] FIG. 11 is a sequence diagram illustrating the operations of a master and a client regarding a schedule task. [Figure 8] FIG. 13 is a functional block diagram showing the functions of the master related to the display of the device management screen. [Figure 9] 11 is a flowchart showing an acquisition and update process repeatedly executed by a control unit of a master. [Figure 10] 1 is a flowchart (part 1) illustrating a display control process executed by a master control unit. [Figure 11] 13 is a flowchart (part 2) illustrating the display control process executed by the control unit of the master. [Figure 12] FIG. 13 is a diagram illustrating an example configuration of the device management screen after some devices have been deleted. [Figure 13] FIG. 13 illustrates an exemplary configuration of a device management screen including a delete device screen. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0023] Exemplary embodiments of the present disclosure will now be described with reference to the drawings. [Overall configuration] A management system 1 according to an exemplary embodiment of the present disclosure is a network system configured to manage terminal devices 4 and 5 located at multiple locations via a cloud server 6 through cooperation between a master 2 and a client 3.

[0024] 1 is configured to be able to communicate with a terminal device 4 installed at a first base via a local area network. The master 2 is further configured to be able to communicate with a cloud server 6 via a wide area network.

[0025] The client 3 is configured to be able to communicate with a terminal device 4 installed at a second base via a local area network. The client 3 is further configured to be able to communicate with a cloud server 6 via a wide area network. The terminal device 5 installed at a third base is configured to be able to communicate with the cloud server 6 via the wide area network.

[0026] The local area network may include, for example, at least one of a wireless LAN and a wired LAN. The wide area network may include, for example, the Internet. A local area network may be constructed in the third base. In this case, the terminal device 5 may be connected to the wide area network via the local area network in the third base.

[0027] The terminal device 4 does not have the ability to use the cloud services provided by the cloud server 6. In other words, each terminal device 4 does not have the function of communicating with the cloud server 6. Hereinafter, this terminal device 4 is particularly referred to as a first type terminal device 4. On the other hand, the terminal device 5 is a terminal device that has the ability to use the cloud services provided by the cloud server 6. In other words, the terminal device 5 has the function of communicating with the cloud server 6. Hereinafter, this terminal device 5 is particularly referred to as a second type terminal device 5.

[0028] The first type terminal device 4 installed at the second base is managed by the master 2 via the client 3 and the cloud server 6. The second type terminal device 5 installed at the third base is managed by the master 2 via the cloud server 6 without via the client 3.

[0029] The terminal devices 4 and 5 managed by the master 2 may be, for example, a group of terminal devices managed by an organization such as a company. In this case, each base may be an activity base of the organization. According to one example, the first base where the master 2 exists may be an office having a management department of the organization. The other second and third bases may be branch offices of the organization that are distant from the first base.

[0030] Examples of the terminal devices 4 and 5 include a printer, a scanner, and a digital multifunction peripheral in which the functions of these are integrated, etc. The master 2 and the client 3 are configured, for example, by installing a dedicated computer program on a personal computer.

[0031] [Device configuration] 2A includes a control unit 11, a communication unit 12, a display unit 13, an input unit 14, and a storage unit 15. The control unit 11 includes a CPU 21 and a memory 22. The CPU 21 as a processor executes processing in accordance with a computer program stored in the storage unit 15. The memory 22 is used as a work memory when the above processing is executed.

[0032] The memory unit 15 includes storage such as a solid state drive (SSD) and a hard disk drive (HDD), and stores various computer programs and data. A main management program 15a is stored in the memory unit 15. The main management program 15a is a computer program for causing the CPU 21 to realize the management functions to be realized by the master 2. It may be understood that the processing mainly performed by the control unit 11 described below is realized by the processing executed by the CPU 21 in accordance with the computer program.

[0033] The communication unit 12 is connected to a local area network of a base where the master 2 exists, and is further connected to a wide area network. The communication unit 12 may be connected to the wide area network via a router (not shown). The display unit 13 is configured to display various screens for a user who operates the master 2. An example of the display unit 13 is a liquid crystal display. Examples of the various screens include a screen for displaying log information and status information of the terminal devices 4 and 5 to be managed, and a screen for remotely operating the terminal devices 4 and 5 according to an operation signal from the user.

[0034] The input unit 14 includes one or more input devices, such as a keyboard and a pointing device, for inputting an operation signal from a user who operates the master 2. The control unit 11 operates in accordance with the operation signal input through the input unit 14.

[0035] 2B includes a control unit 31, a communication unit 32, a display unit 33, an input unit 34, and a storage unit 35. The control unit 31 includes a CPU 41 and a memory 42. The CPU 41 as a processor executes processing in accordance with a computer program stored in the storage unit 35.

[0036] A sub-management program 35a is stored in the storage unit 35. The sub-management program 35a is a computer program for causing the CPU 41 to realize functions related to the management function of the master 2 to be realized by the client 3. It may be understood that the processing mainly performed by the control unit 31 described below is realized by processing executed by the CPU 41 in accordance with the computer program.

[0037] The communication unit 32 is connected to a local area network of a base where the client 3 exists, and is further connected to a wide area network. The communication unit 32 may be connected to the wide area network via a router (not shown). The display unit 33 includes, for example, a liquid crystal display, and is configured to display various screens for a user who operates the client 3. The input unit 34 includes one or more input devices for inputting an operation signal from a user who operates the client 3. The control unit 31 operates according to the operation signal input through the input unit 34.

[0038] 2C includes a control unit 51, a communication unit 52, a display unit 53, and an input unit 54. When the first type terminal device 4 is a digital multifunction peripheral, the first type terminal device 4 may further include a printing unit 55 and a reading unit 56. The first type terminal device 4 may include only one of the printing unit 55 and the reading unit 56.

[0039] The control unit 51 includes a CPU 61 and a memory 62. The memory 62 can include a non-volatile memory such as a flash memory in addition to a RAM, and can store computer programs, setting data, and the like in the non-volatile memory.

[0040] The CPU 61 as a processor generally controls the entire first type terminal device by executing processes according to a computer program stored in the memory 62. It may be understood that the processes mainly performed by the control unit 51 described below are realized by the processes executed by the CPU 61 according to the computer program.

[0041] The communication unit 52 is connected to the local area network of the base where the first type terminal device 4 exists so as to be able to communicate with the master 2 or the client 3 present there. The display unit 53 includes, for example, a liquid crystal display, and is configured to display various screens for a user who operates the first type terminal device 4. The input unit 54 includes one or more input devices, such as a touch panel on a liquid crystal display, for inputting an operation signal from the user.

[0042] The printing unit 55 is configured to be controlled by the control unit 51 and to print an image on a sheet. Examples of the printing unit 55 include an inkjet printer and a laser printer. According to this embodiment, status information such as the remaining amount of coloring material and log information such as the number of printed sheets are provided to the master 2 from the first type terminal device 4 through the client 3 and the cloud server 6 in a manner to be described later. The reading unit 56 is configured to be controlled by the control unit 51 and to read a reading target such as a printed matter.

[0043] 3A includes a control unit 71, a communication unit 72, a display unit 73, and an input unit 74. When the second type terminal device 5 is a digital multifunction peripheral, the second type terminal device 5 may further include a printing unit 75 and a reading unit 76. The second type terminal device 5 may include only one of the printing unit 75 and the reading unit 76.

[0044] The control unit 71 includes a CPU 81 and a memory 82. The memory 82 can include a non-volatile memory such as a flash memory, and can store computer programs, setting data, and the like in the non-volatile memory.

[0045] The CPU 81 as a processor performs overall control of the entire device by executing processing in accordance with a computer program stored in the memory 82. A communication program 82a is stored in the memory 82. The communication program 82a is a program for using a cloud service provided by the cloud server 6. It may be understood that the processing mainly performed by the control unit 71 described below is realized by processing executed by the CPU 81 in accordance with the computer program.

[0046] The communication unit 72 is connected to a wide area network so as to be able to communicate with the cloud server 6. If a local area network is constructed in the third base, the communication unit 72 may be connected to the wide area network via the local area network. The display unit 73 includes, for example, a liquid crystal display. The input unit 74 includes one or more input devices for inputting an operation signal from a user.

[0047] The printing unit 75 is configured to print an image on a sheet under the control of the control unit 71. According to this embodiment, status information such as the remaining amount of coloring material and log information such as the number of printed sheets are provided to the master 2 from the second type terminal device 5 through the cloud server 6 in a manner to be described later. The reading unit 76 is configured to read a reading target such as a printed matter under the control of the control unit 71.

[0048] 3B includes a control unit 91, a communication unit 92, a first storage 93, and a second storage 94. The control unit 91 includes a CPU 101 and a memory 102.

[0049] CPU 101 as a processor executes processing in accordance with a computer program stored in memory 102. The processing executed by CPU 101 includes processing for making cloud server 6 function as cloud storage. It may be understood that the processing mainly performed by control unit 91 described below is realized by processing executed by CPU 101 in accordance with the computer program.

[0050] The cloud storage includes a table storage and an object storage. When the control unit 91 executes the above process, the first storage 93 functions as a table storage, and the second storage 94 functions as an object storage.

[0051] The exemplary first storage 93 functions as a NoSQL data store and is configured to store tables that are made up of a collection of schema-less entities. Each entity in a table is made up of a set of properties, and each property is made up of a key and a value pair.

[0052] The exemplary second storage 94 functions as an object storage that can read and write any text file and binary file as an object from the outside using the HTTP / HTTPS protocol.

[0053] Azure (registered trademark) from Microsoft Corporation is known as a cloud service that provides the above-mentioned table storage and object storage. The cloud server 6 can operate in the same manner as such a cloud service.

[0054] [Sequence Overview] Next, an operation sequence related to management will be outlined with reference to Fig. 4. In the preparation stage, a main management program 15a is installed in the master 2. A process according to the main management program 15a is executed by the control unit 11 of the master 2, and a cloud profile is set (S01).

[0055] As described below, the client 3 and the second type terminal device 5 execute a polling operation for the cloud server 6 and an update operation of information held in the cloud server 6. Setting a cloud profile (S01) includes setting cloud parameters. The cloud parameters include a period for the polling operation (hereinafter referred to as the "polling period") and a period for the information update operation (hereinafter referred to as the "information update period"). Setting a cloud profile (S01) further includes setting a shared access signature (SAS) for using a cloud service.

[0056] The cloud profile is set, for example, according to a setting operation performed by a primary administrator who is a user of the master 2 through the input unit 14. The SAS is set individually for each of the first storage 93 and the second storage 94, i.e., the table storage and the object storage.

[0057] Next, cloud parameters according to the set cloud profile are uploaded from the master 2 to the first storage 93 of the cloud server 6 (S02) and written to the first storage 93 (S03). The cloud parameters including the polling period and the information update period are written to the first storage 93 as table entities.

[0058] Furthermore, at least a portion of the cloud profile is exported from the master 2 as a client profile, i.e., data for reading at the client 3 (S04). The client profile may include, for example, the cloud parameters described above.

[0059] The exported client profile is provided to the client 3. The client profile may be provided to the client 3 by any method. For example, the client profile may be transmitted from the master 2 to the client 3 by email or other methods. Also, for example, the client profile may be provided by the main administrator to a sub-administrator who is a user of the client 3. More specifically, for example, the main administrator may store the client profile in an information processing terminal owned by the main administrator and transmit the client profile to another information processing terminal owned by the sub-administrator, so that the sub-administrator can transfer the client profile from the other information processing terminal to the client 3. The main administrator may transmit the client profile from its own information processing terminal to the client 3. Also, for example, the main administrator may store the client profile in a predetermined storage and provide the storage to the sub-administrator, so that the sub-administrator can transfer the client profile from the storage to the client 3.

[0060] The sub-administrator operates the client 3 to install the sub-management program 35a on the client 3 (S06). At this time, the client profile provided by the master 2 is imported by the sub-administrator's operation, and cloud parameters and SAS according to the client profile are set on the client 3 (S05).

[0061] Through the above installation and settings, the client 3 is configured to be able to use the cloud server 6. As a result, the client 3 is configured to be able to transmit information to the master 2 via the cloud server 6. Specifically, the client 3 is configured to be able to execute relay operations between the master 2 and the first type terminal device 4 via the cloud server 6, such as sending a task execution instruction from the master 2 to the first type terminal device 4 and transmitting log information and status information from the first type terminal device 4 to the master 2.

[0062] Meanwhile, the SAS is registered in the second type terminal device 5 by an input operation by a device administrator who is an administrator of the second type terminal device 5 (S07). The control unit 71 of the second type terminal device 5 in which the SAS is registered executes processing in accordance with the communication program 82a. The control unit 71 executing processing in accordance with the communication program 82a is hereinafter referred to as the "cloud connector." The cloud connector refers to the cloud parameters written by the master 2 in the first storage 93 of the cloud server 6 (S08). The cloud connector acquires the cloud parameters and sets them in its own device (S08).

[0063] Once the initial settings (S05 to S08) of the client 3 and the second type terminal device 5 (cloud connector), including the settings of the above-mentioned cloud parameters and SAS, are completed, the client 3 and the second type terminal device 5 execute a scheduled task to periodically update the information stored in the first storage 93 of the cloud server 6 in accordance with the set information update period.

[0064] The schedule task starts with registering device information in the first storage 93 (S09, S10). The first storage 93 has a schedule task table as one of its tables. As shown in Fig. 5A, the schedule task table is made up of a group of entities including properties of a first key, a second key, a request parameter, a response parameter, a notification source, a progress status, and a device ID.

[0065] The schedule task table has three entities relating to "log," "status," and "registration" for each of the terminal devices 4, 5, and the information in the entities is updated by the client 3 managing the corresponding first type terminal device 4 or the cloud connector of the corresponding second type terminal device 5 (S09, S10).

[0066] The "notification source" property in an entity indicates who updated the entity; when the entity is updated by a client 3 the "notification source" property is updated to the value "client", and when the entity is updated by a cloud connector the "notification source" property is updated to the value "device".

[0067] The entity related to "log" is a log entity having the value "log" of the first key, and describes in the response parameters one piece of log information of the terminal device 4, 5 corresponding to the device ID described as the value of the second key. The device ID is an ID unique to each of the terminal devices 4, 5.

[0068] When the corresponding terminal device is a printer or a digital multifunction peripheral, the log information may include information on the total number of pages printed by the corresponding terminal device. The log information may include, as a print history, information on the user who issued the print command and the number of pages printed for each print job.

[0069] As illustrated in the lower part of FIG. 5A, the response parameters may include, for example, JSON data. For example, the log information may be described in JSON format by associating an object identifier (OID) used in a management information base (MIB) of the corresponding parameter with its value. The description "xxxxx...", "yyyyy..." in the lower part of FIG. 5A corresponds to an abstract representation of an object identifier. The response parameters in the initial state before being updated may exist as request parameters in which an initial value is associated with an object identifier. According to the example in the lower part of FIG. 5A, the initial value "%MIB(yyyyy...)%" associated with the OID "yyyyy..." has been rewritten to the value "4" by the update.

[0070] An entity related to "status" is a status entity having a first key value "status", and describes in a response parameter one of the status information of the terminal devices 4, 5 corresponding to the device ID described as the value of the second key. When the corresponding terminal device is a printer or a digital multifunction peripheral, the status information may include information on the remaining amount of coloring material in the corresponding terminal device and error information such as a paper jam. In the status entity, as in the log entity, the response parameter may be described in JSON format.

[0071] The entity related to "registration" is a registration entity having the value "registration" of the first key, and describes in the response parameters one piece of device information of the terminal device 4, 5 corresponding to the device ID described as the value of the second key. In the response parameters, multiple item values ​​describing the basic configuration of the device are described as the device information.

[0072] In the schedule task table, the entity of the cloud connector of the second type terminal device 5 is updated by the cloud connector (S09). The entity of the first type terminal device 4 is updated by the client 3 connected to the same local area network as the first type terminal device 4 (S10). That is, the client 3 updates the entity for each first type terminal device 4 under the client 3. In the registration entity of the first type terminal device 4, the identification information of the client 3 that controls the first type terminal device 4 is written as a part of the device information.

[0073] Through processing by the control unit 31 in accordance with the sub-management program 35a, the client 3 communicates with each first type terminal device 4 within the local area, obtains information necessary for updating device information from each first type terminal device 4, and updates the registration entity of the corresponding first type terminal device 4 (S10).

[0074] The client 3 periodically communicates with each of the first type terminal devices 4 under its control within a local area to obtain corresponding log information and status information, and can update the log entities and status entities of each of the first type terminal devices 4 in the first storage 93 of the cloud server 6 (S10).

[0075] The cloud connector of the second type terminal device 5 can periodically access the cloud server 6 and update its own log entity and status entity in the first storage 93 so as to update its own log information and status information (S09).

[0076] The master 2 also functions as a client 3. That is, the master 2 may be understood to function as a client 3 with respect to the first type terminal device 4 at the first base. Specifically, the master 2, like the client 3, can update the registration entity, log entity, and status entity of each of the subordinate first type terminal devices 4 in the first storage 93 of the cloud server 6.

[0077] The master 2 can further periodically access the cloud server 6 to refer to the log entities, status entities, and registration entities of each of the terminal devices 4, 5 in the first storage 93, and, based on these references, execute a process of storing the log information, status information, and device information of each of the terminal devices 4, 5 in the memory unit 15 (S11).

[0078] Furthermore, the master 2 can display a list of the registered terminal devices 4, 5 and log information and status information of the terminal devices 4, 5 on the screen of the display unit 13 in accordance with an operation signal from the user via the input unit 14 (S11). In this way, the management system 1 is configured to be able to remotely monitor the status of the terminal devices 4, 5 used at multiple locations from one location where the master 2 is installed.

[0079] In addition, according to the management system 1, instant tasks, which are non-periodic tasks other than scheduled tasks, are executed by the terminal devices 4 and 5 based on a request from the master 2. The master 2 requests the corresponding terminal devices 4 and 5 to execute an instant task by registering an entity of the instant task in the first storage 93 (S13). For example, firmware update in the terminal devices 4 and 5 is realized as one of the instant tasks.

[0080] The master 2 receives an instant task execution request operation from the user of the master 2 in accordance with an operation signal from the user via the input unit 14 (S12), and can register the corresponding entity (S13).

[0081] The first storage 93 includes an instant task table shown in Fig. 5B. Like the schedule task table, the instant task table is composed of a group of entities including properties of a first key, a second key, a request parameter, a response parameter, a notification source, a progress status, and a device ID.

[0082] An entity in the instant task table (hereinafter referred to as an instant task entity) is an entity in which "instant task" is written as the value of the first key. The property of the second key in the instant task entity has a transaction ID as its value. The transaction ID is a unique ID for each instant task that occurs at the same time, and is used to distinguish between the entities of multiple instant tasks that occur at the same time.

[0083] In the device ID property of the instant task entity, the device ID of the terminal device 4, 5 to which the instance task is requested is described as a value. When an instant task is requested to multiple first type terminal devices 4 under the client 3, the device ID of each of the multiple first type terminal devices 4 is described in the device ID property.

[0084] The request parameters in the instant task entity include data describing the content of the process to be executed as an instant task as a value. The content of the process is described as, for example, JSON data.

[0085] When the instant task requested to be executed by the master 2 is a firmware update for the terminal devices 4 and 5, the master 2 stores the firmware update file in the second storage 94 that functions as an object storage (S14). In this case, the URL of the storage destination of the firmware update file is described in the request parameters.

[0086] The cloud connector of the second type terminal device 5 accesses the first storage 93 of the cloud server 6 at the set polling period and determines whether a new entity of an instant task that it should execute is registered in the instant task table (S15).

[0087] If a new entity is registered, the cloud connector communicates receipt of the instant task request to Master 2 by updating the value of the progress property of the corresponding instant task entity in the first storage 93 from “Requested” to “In Progress” (S15).

[0088] The master 2 periodically refers to the instant task entity in the first storage 93 to check the status (S18). By periodically referring to the instant task entity, the master 2 can check that the request for the instant task has been received based on the updated value of the property of the progress status.

[0089] The cloud connector of the second type terminal device 5 refers to the request parameters of the instant task entity when executing the instant task (S15). If the cloud connector determines based on the referred request parameters that a data file required for executing the instant task exists in the second storage 94, it downloads the data file from the second storage 94 based on the storage destination URL described in the request parameters (S16) and executes the instant task.

[0090] When the instant task is completed, the cloud connector of the second type terminal device 5 changes the value of the progress status property from “in progress” to “completed” and updates the corresponding instant task entity in the first storage 93 to write the processing result as a response parameter (S17).

[0091] Like the cloud connector of the second type terminal device 5, the client 3 also accesses the first storage 93 of the cloud server 6 at the set polling period and determines whether or not a new entity of an instant task to be executed by a subordinate first type terminal device 4 is registered in the instant task table (S19). Hereinafter, each of one or more first type terminal devices 4 that are set as an instant task execution target in the instant task table among the subordinate first type terminal devices 4 (i.e., one or more first type terminal devices 4 whose device ID is described in the device ID property) will be referred to as an "instant task execution target."

[0092] If a new entity is registered, the client 3 updates the corresponding instant task entity in the first storage 93 so as to update the value of the progress property from "Requested" to "In Progress" (S19). The client 3 further obtains data files required for executing the instant task from the second storage 94 as necessary by referring to the request parameters (S20).

[0093] After that, the client 3 instructs the instant task execution targets to execute the instant task through the local area network (S21). At this time, the client 3 transfers the data files required for the execution obtained from the second storage 94 to each instant task execution target (S21).

[0094] When the execution of the instant task is completed for all instant task execution targets, the client 3 updates the corresponding instant task entity in the first storage 93 so as to change the value of the progress status property from "in progress" to "completed" and write the processing result as a response parameter (S22). By updating this entity, the client 3 notifies the master 2 of the execution progress and processing result of the instant task for the instant task execution targets via the first storage 93 of the cloud server 6 (S22).

[0095] To check the status, the master 2 refers to the instant task entity in the first storage 93 and finds that the value of the progress status property has been updated to “Completed”, thereby confirming that the instant task has been completed and writing the processing result to the memory unit 15 (S23).

[0096] The master 2 can further display the processing results on the screen of the display unit 13. When the master 2 confirms that the registered instant task has been completed in all of the target terminal devices 4 and 5, in other words, that instant task is no longer necessary (S24), it deletes the instant task entity that is no longer necessary from the first storage 93 (S25), and deletes the data file (e.g., a firmware update file) in the second storage 94 that was used for the instant task (S26).

[0097] In this way, the management system 1 is configured to be able to remotely control terminal devices 4, 5 used at multiple locations from one location where the master 2 is installed, by registering and updating instant task entities in the first storage 93 of the cloud server 6, and further by transferring data files via the second storage 94.

[0098] [Details of the Device Management Screen] Next, a detailed description will be given of the processing operation of the master 2 regarding the configuration and display of the device management screen G0 that is displayed based on information provided by the terminal devices 4 and 5 through a schedule task. In the following, the explanation will be given on the assumption that the terminal devices 4 and 5 are printers or digital multifunction peripherals with a printer function.

[0099] The device management screen G0 includes a first area R1 and a second area R2 as shown in Fig. 6. The first area R1 is mainly used as an area for displaying a device list G1. The device list G1 is a list of multiple terminal devices 4, 5 registered in the management system 1. The devices here correspond to the terminal devices 4, 5, respectively.

[0100] The device management screen G0 may have a group selection screen (not shown), and the device list G1 may display terminal devices 4, 5 that belong to a group selected on the group selection screen from among the multiple terminal devices 4, 5 registered in the management system 1.

[0101] The device list G1 shown in Fig. 6 is displayed in a table structure having row data for each of the terminal devices 4 and 5. Each row data has information on the status, model name, toner / ink amount, and node name of the corresponding terminal device. The status indicates whether the corresponding terminal device is in a state where it can execute a process based on an instruction from an external device such as the master 2. When it is in a state where it can execute a process, "ready" (i.e., READY) is displayed. If an error has occurred in the corresponding terminal device, a character string explaining the error is displayed as the status.

[0102] The model name indicates the product model name of the corresponding terminal device, and the node name indicates the node name of the corresponding terminal device. The toner / ink amount indicates the remaining amount of color material used by the terminal devices 4 and 5 in the printer function. When the terminal devices 4 and 5 have the function as an inkjet printer, the color material is ink, and when they have the function as a laser printer, the color material is toner. In Fig. 6, the remaining amount of color material of each color of CMYK is shown in a bar graph as the toner / ink amount.

[0103] On the other hand, the second area R2 is used as an area for displaying detailed information of one of the terminal devices 4, 5 displayed in the first area R1 selected by a cursor. The second area R2 further includes a graphical user interface for performing operations on one or more terminal devices specified by check boxes in the device list G1. According to Fig. 6, the second area R2 includes an operation object J1 for deleting the specified one or more terminal devices from the device list G1, and an operation object J2 for creating an instant task for requesting execution by the specified one or more terminal devices.

[0104] Furthermore, the device management screen G0 includes an operation object J3 for switching the device list G1 displayed in the first area R1 to a deleted device screen G2 (see FIG. 13). The deleted device screen G2 is a screen that displays the terminal devices 4 and 5 that have been deleted from the device list G1 as hidden targets. Details will be described later.

[0105] The toner / ink amounts displayed for each terminal device to be displayed in the device list G1 are written to the first storage 93 by the client 3 and cloud connector updating, as a scheduled task, the status information of the corresponding terminal device in the first storage 93 of the cloud server 6. The master 2 refers to this status information to collect information on the toner / ink amounts required for displaying the device list G1.

[0106] 7 shows the operation of the master 2 and the client 3 regarding the schedule task as a sequence diagram. As described above, the update period of the status information by the schedule task is set in the client 3 by importing the client profile when the sub-management program 35a is installed.

[0107] The master 2 can accept an operation to change the information update period from the user via the input unit 14, and can update the cloud parameters stored in the first storage 93 of the cloud server 6 to the information update period changed by the above-mentioned change operation. The client 3 can update the setting value of the information update period in its own device by referring to the updated cloud parameters stored in the first storage 93 by a polling operation.

[0108] The client 3 periodically obtains status information, including toner / ink amounts, of each of the first type terminal devices 4 in the local area network from the corresponding first type terminal device 4 in accordance with the information update period set at the time of installation or an information update period changed thereafter.

[0109] Based on the status information thus periodically and repeatedly acquired, the client 3 periodically updates the status entity of the corresponding first type terminal device 4 stored in the first storage 93 of the cloud server 6 at the above-mentioned information update period. That is, the client 3 updates the status information including the toner / ink amount in the status entity of the corresponding first type terminal device 4 to the latest information acquired from the first type terminal device 4.

[0110] In addition, the above-mentioned cloud parameters also include a device search period in the local area network, and the device search period, as well as the information update period for the above-mentioned status information, is set in the client 3. The client 3 searches for a first type terminal device 4 in the local area network at the set device search period, communicates with the first type terminal device 4 found by the search, and periodically acquires status information.

[0111] When a new first type terminal device 4 is found, a registration entity is written from the client 3 to the first storage 93. The master 2 updates the display setting data 11E stored in the memory 22 based on the registration entity written to the first storage 93 so as to set and register the new first type terminal device 4 as a display target in the device list G1.

[0112] The display setting data 11E stores a setting value indicating whether the corresponding terminal device is to be displayed or hidden in the device list G1, in association with the device ID of the corresponding terminal device, for each of the terminal devices 4, 5 registered in the management system 1. The display setting data 11E is saved in the storage unit 15, read out to the memory 22, and used for display control of the device management screen G0.

[0113] Hereinafter, among the terminal devices 4 and 5 registered in the management system 1, each of the terminal devices set as a display target will be referred to as a display target device, and each of the terminal devices set as a non-display target will be referred to as a non-display target device.

[0114] 8 in relation to the display of the device management screen G0 by executing processing according to the main management program 15a. An internal table 11D is created in the memory 22 for storing data necessary for the display control unit 11C to display the device management screen G0 via the display unit 13.

[0115] The information acquiring unit 11A periodically executes the acquisition and update process shown in Fig. 9 at a predetermined reference period (in other words, an acquisition period). In the acquisition and update process, the information acquiring unit 11A acquires table information by referring to the schedule task table in the first storage 93. The table information is a group of entities registered in the schedule task table (S110).

[0116] Thereafter, the information acquiring unit 11A updates the internal table 11D based on the acquired table information (S120). The internal table 11D corresponds to a copy of the schedule task table held by the first storage 93 of the cloud server 6. The information acquiring unit 11A updates the internal table 11D based on the acquired table information so as to hold the same information as the schedule task table held by the first storage 93 of the cloud server 6.

[0117] As a result of this update, the internal table 11D stores the latest log information held by the log entities of each of the terminal devices 4 and 5 registered in the management system 1, which are periodically updated within the first storage 93 by the operation of the client 3 and the cloud connector, the latest status information held by the status entities, and the latest device information held by the registered entities.

[0118] The information acquisition unit 11A further updates the display setting data 11E based on the table information so as to register the new first type terminal device 4 in the display setting data 11E while setting the new first type terminal device 4 as a display target in the device list G1.

[0119] 10 and 11, the display control unit 11C controls the display of the device management screen G0 on the display unit 13. When an instruction to display the device management screen G0 is input via the input unit 14, the display control unit 11C starts the display control process.

[0120] When the display control process is started, the display control unit 11C causes the display unit 13 to display the device management screen G0, and causes the device list G1 to be displayed in the first area R1 of the device management screen G0 (S210). Prior to displaying the device management screen G0, the master 2 causes the information acquisition unit 11A to start repeated execution of an acquisition and update process, and generates an internal table 11D necessary for displaying the device list G1.

[0121] The display control unit 11C refers to the status information of each device to be displayed in the internal table 11D based on the device ID of the group of devices to be displayed indicated in the display setting data 11E, and displays in the first area R1 a device list G1 that lists the terminal devices 4, 5 set as the devices to be displayed, and shows the amount of toner / ink as the status of each terminal device 4, 5.

[0122] Thereafter, the display control unit 11C determines whether a user operation has been performed on the device management screen G0 via the input unit 14 (S220). If it is determined that no operation has been performed (No in S220), the display control unit 11C refers to the internal table 11D, and determines the latest state of each display target device, including the latest toner / ink amount, from the status information of each display target device contained in the internal table 11D (S230), and updates the device management screen G0 including the device list G1 so that the determined latest state of each display target device is shown in the device list G1 (S235).

[0123] If a new terminal device 4, 5 that was not registered in the device list G1 before the update is registered in the display setting data 11E as a display target device, the display control unit 11C updates the device management screen G0 in S235 so as to add and display the new display target device in the device list G1.

[0124] The display control unit 11C repeatedly updates the device management screen G0 having the above configuration at short intervals, thereby displaying the latest state of each display target device in the device list G1.

[0125] In addition, when the display control unit 11C determines that a user operation has been performed on the device management screen G0 via the input unit 14 (Yes in S220), it executes processing in accordance with the user operation (S240-S390).

[0126] Specifically, when an operation is performed to select one display target device from the device list G1 in the first area R1 by operating the cursor (Yes in S240), the display control unit 11C updates the second area R2 so that detailed information of the selected display target device is displayed in the second area R2 (S245). Examples of detailed information of the display target device include an IP address, etc.

[0127] When a deletion operation of a device to be displayed from the device list G1 is performed via the input unit 14 by pressing the operation object J1 shown in Figure 6 in the second area R2 (Yes in S250), the display control unit 11C sets one or more devices to be displayed specified by the user using the check boxes in the first area R1 as devices to be hidden (S260), and updates the device management screen G0 so that these devices to be hidden are deleted from the device list G1 (S265).

[0128] In S260, the display control unit 11C updates the display setting data 11E so as to set the one or more specified display target devices to non-display target devices. Fig. 12 shows an example of the device management screen G0 when some of the display target devices in Fig. 6 are switched to non-display target devices, and some of the terminal devices 4, 5 are deleted from the device list G1.

[0129] When a switching operation to the deleted device screen G2 is performed via the input unit 14 by pressing the operation object J3 shown in FIG. 6 on the device management screen G0 (Yes in S270), the display control unit 11C executes the processing from S300 onward shown in FIG.

[0130] In addition, when an operation to end the display of the device management screen G0 is performed through the input unit 14 (Yes in S280), the display control unit 11C ends the display control process shown in Fig. 10. When another operation is performed (No in S280), the display control unit 11C executes a process corresponding to the operation (S290) and returns to the process of S220.

[0131] Returning to the process of S220, the display control unit 11C repeatedly executes the processes of S230 and S235 until the next operation is performed, and updates the device management screen G0 so that the latest state of each display target device is displayed in the device list G1. When the next operation is performed (Yes in S220), the display control unit 11C executes a process according to the operation.

[0132] When a switching operation to the deleted device screen G2 is performed and the process proceeds to S300, the display control unit 11C determines the latest status of each hidden device, including the latest toner / ink amounts, by referring to the status information of each hidden device indicated in the internal table 11D based on the device IDs of the group of hidden devices indicated in the display setting data 11E.

[0133] The display control unit 11C updates the device management screen G0 so that a deletion device screen G2 is displayed in the first area R1 as a separate screen in place of the device list G1 based on the latest status of the determined hidden devices (S310). The deletion device screen G2 is a screen that lists the hidden devices and shows the latest status of each hidden device.

[0134] The device management screen G0 with the deleted device screen G2 displayed in the first area R1 is shown in Fig. 13. As can be seen from Fig. 13, the deleted device screen G2 is configured to display, for each device to be hidden, information on the status, model name, toner / ink amount, and node name of the corresponding terminal device, similar to the device list G1.

[0135] When the delete device screen G2 is displayed in the first area R1, an operation object J4 for returning the deleted device to the device list G1 is displayed in the second area R2. Also, an operation object J5 for creating an instant task for the deleted device is displayed in the second area R2. Furthermore, detailed information of a device to be hidden that is selected by cursor operation on the delete device screen G2 is displayed in the second area R2. In addition, an operation object J6 for switching the delete device screen G2 displayed in the first area R1 to the device list G1 is displayed in the device management screen G0.

[0136] Even when the deleted device screen G2 is displayed in the first area R1, the display control unit 11C determines whether a user operation has been performed on the device management screen G0 via the input unit 14 (S320).

[0137] When no operation is performed on the device management screen G0 via the input unit 14 (No in S320), the display control unit 11C refers to the status information of each device to be hidden indicated by the internal table 11D, determines the latest status of each device to be hidden including the latest toner / ink amount (S330), and updates the device management screen G0 so that the deleted device screen G2 in the first area R1 indicates the latest status of each device to be hidden (S335). When no operation is performed, the display control unit 11C repeatedly executes the processes of S330 and S335.

[0138] When an operation is performed on the device management screen G0 via the input unit 14 (Yes in S320), the display control unit 11C executes processing according to the operation. Specifically, when an operation for restoring a hidden device to the device list G1 is performed via the input unit 14 by pressing the operation object J4 (Yes in S340), the display control unit 11C changes the setting of one or more hidden devices designated by the user using the check boxes on the deletion device screen G2 in the first area R1 to devices to be displayed (S350).

[0139] In S350, the display control unit 11C updates the display setting data 11E so as to set the one or more designated non-display target devices as display target devices. Furthermore, the display control unit 11C refers to the updated display setting data 11E to identify a group of current display target devices, and refers to the status information of each display target device from the internal table 11D to determine the latest status of each display target device including the toner / ink amount (S370).

[0140] By repeatedly executing the schedule task by the client 3 and the second type terminal device 5, the latest status information of each of the terminal devices 4, 5 is written to the first storage 93 regardless of whether the terminal devices 4, 5 are set as display target devices or non-display target devices, and this is reflected in the internal table 11D.

[0141] Therefore, in S370, the latest status of the display target devices that were set as non-display target devices until just before is determined in the same manner as the other display target devices. Based on the result of this status determination, the display control unit 11C updates the device management screen G0 so that a device list G1 showing the latest status of each display target device is displayed in the first area R1 of the device management screen G0 instead of the deleted device screen G2 (S380). Thereafter, the process returns to S220.

[0142] As a result of the processing in S380, the terminal device 4, 5 that was the target of the restoration operation is redisplayed in the device list G1 so that the row data indicating the latest toner / ink amounts is displayed in the original position before deletion, as shown in Fig. 6. For example, the device list G1 is returned from the state shown in Fig. 12 to the state shown in Fig. 6.

[0143] In addition, when a switching operation to the device list G1 is performed via the input unit 14 by pressing the operation object J6 (Yes in S360), the display control unit 11C proceeds to S370, determines the latest state of each display target device as described above, and further updates the device management screen G0 so that the device list G1 showing the latest state of each display target device is displayed in the first area R1 (S380).Then, the process returns to S220.

[0144] If another operation has been performed (No in S360), the display control unit 11C executes a process corresponding to the operation (S390) and then returns to the process of S320.

[0145] The management system 1 of the present embodiment described above has the following advantages: According to the management system 1 of the present embodiment, status information of each of the terminal devices 4 and 5 as managed devices registered in the management system 1 is provided to the master 2 via a general-purpose cloud storage, not via a dedicated server.

[0146] Status information corresponding to the state data of each of the terminal devices 4 and 5 is periodically and repeatedly written to the first storage 93 by the client 3 and the second type terminal device 5. The master 2 refers to the status information in the first storage 93 and causes the display unit 13 to display a device list G1 including the status information of the terminal devices 4 and 5 set as display targets.

[0147] In other words, the master 2 displays the device management screen G0 on the display unit 13 so that the latest status of each of the one or more terminal devices 4, 5 designated as display targets by the administrator, who is the user of the master 2, among the managed devices, is displayed in the device list G1.

[0148] Therefore, according to this technology, it is possible to construct a system that can remotely monitor managed devices using cloud storage and can provide an administrator with information that is useful for managing the status of the managed devices.

[0149] In particular, according to this embodiment, the control unit 11 of the master 2 sets each of the terminal devices 4, 5 registered in the management system 1 to a device to be displayed or a device to be hidden in accordance with a user's pressing operation of the operation objects J1, J4 via the input unit 14, so as to switch between the device to be displayed and the device to be hidden.

[0150] Each of the client 3 and the second type terminal device 5 (cloud connector) repeatedly and periodically writes the latest status information of the terminal devices 4 and 5 to the first storage 93 by a scheduled task, regardless of whether the master 2 switches between a device to be displayed and a device to be hidden, in other words, regardless of whether each of the terminal devices 4 and 5 registered in the management system 1 is set as a device to be displayed.

[0151] In this manner, in this embodiment, the display / non-display of the terminal devices 4, 5 in the device list G1 is independent of the uploading of status information. Therefore, according to this embodiment, it is possible to switch the display / non-display of each of the terminal devices 4, 5, including the status display, on the master 2 side without requiring complicated cooperation between the master 2 and the client 3 or the second type terminal device 5.

[0152] According to this embodiment, the master 2 repeatedly acquires the status information of all the terminal devices 4, 5, including not only the display target devices but also the non-display target devices, from the first storage 93 and stores it in the internal table 11D. Therefore, when the master 2 switches a non-display target device to a display target device in accordance with an instruction from the user, the master 2 can quickly display the status information of the terminal devices 4, 5 that have been switched to the display target device based on the internal table 11D without accessing the first storage 93. That is, the master 2 can display the status information of the terminal devices 4, 5 in the device list G1 immediately after the terminal devices 4, 5 are switched from non-display target devices to display target devices.

[0153] If the display of the terminal devices 4, 5 that have been switched from hidden devices to displayed devices in the device list G1 is suspended until the internal table 11D is updated by the information acquisition unit 11A through periodic reference to the first storage 93 (see FIG. 8), the user of the master 2 may become dissatisfied. This is because the period of periodic reference is longer than the screen update interval, and the user feels the suspension as a delay in display.

[0154] Even if a method is used in which the status information of a device to be displayed is obtained by accessing the first storage 93 when a device to be hidden is switched to a device to be displayed, it takes some time for this status information to be reflected in the device list G1.

[0155] Therefore, as in this embodiment, regardless of the hidden / display setting, the management system 1 acquires status information of each terminal device 4, 5 in the background and records it in the internal table 11D, making it possible to display a device management screen G0 that is highly responsive to the user.

[0156] The present disclosure is not limited to the above-described exemplary embodiment, and various aspects can be adopted. For example, the configuration of the device management screen G0 is not limited to the illustrated one. In the above-described embodiment, an example in which the toner / ink amount of each terminal device 4, 5 is displayed as the status information has been described, but the displayed status information may include remaining amount information of other consumables, such as remaining amount of sheets.

[0157] In addition, the function of one component in the above embodiments may be distributed among multiple components. The functions of multiple components may be integrated into one component. Part of the configuration of the above embodiments may be omitted. At least part of the configuration of the above embodiments may be added to or substituted for the configuration of another of the above embodiments. All aspects included in the technical idea identified from the wording of the claims are embodiments of the present disclosure. [Explanation of symbols]

[0158] 1... management system, 2... master, 3... client, 4, 5... terminal device, 6... cloud server, 11, 31, 51, 71, 91... control unit, 11A... information acquisition unit, 11C... display control unit, 11D... internal table, 11E... display setting data, 12, 32, 52, 72, 92... communication unit, 13, 33, 53, 73... display unit, 14, 34, 54, 74... input unit, 15, 35... memory unit, 15a... main management program RAM, 21, 41, 61, 81, 101...CPU, 22, 42, 62, 82, 102...memory, 35a...sub-management program, 55, 75...printing unit, 56, 76...reading unit, 82a...communications program, 93...first storage, 94...second storage, G0...device management screen, G1...device list, G2...delete device screen, R1...first area, R2...second area, J1-J6...operation objects.

Claims

1. at least one first communication device configured to repeatedly write to the cloud storage a plurality of state data, each state data describing a state of a corresponding device of the plurality of devices; A second communication device configured to be able to access the cloud storage; Equipped with The second communication device is setting each of the plurality of devices to be a display target or a non-display target based on a switching instruction input through a user interface so as to switch between the display target and the non-display target; displaying, on a display device, a device list that lists one or more devices that are set as the display target among the plurality of devices and further indicates the respective states of the one or more devices; configured to run the at least one first communication device is configured to repeatedly write the plurality of state data for the plurality of devices to the cloud storage regardless of settings of the display target and the non-display target; The second communication device is repeatedly acquiring status data of each of the plurality of devices including the device set to be hidden from the cloud storage, and updating the device list based on the acquired status data so as to indicate a latest status of each of the one or more devices set to be displayed; The management system is configured to, when a specific instruction is input through the user interface, display on the display device a screen separate from the device list that lists the devices that have been set as hidden targets and shows the status of each of the devices that have been set as hidden targets, and to accept, as the switching instruction, an instruction to switch the devices that have been set as hidden targets to the displayed targets through the screen.

2. The management system according to claim 1 , wherein a period during which the second communication device acquires the status data from the cloud storage is longer than an update interval of the device list displayed on the display device.

3. a communication unit that can access a cloud storage that stores a plurality of repeatedly updated status data, each of which describes a status of a corresponding device among a plurality of devices; a processing unit configured to perform processing related to the plurality of devices; Equipped with The processing unit, as the processing related to the plurality of devices, setting each of the plurality of devices to be a display target or a non-display target based on a switching instruction input through a user interface so as to switch between the display target and the non-display target; repeatedly acquiring status data of each of the plurality of devices including the device set as a hidden target from the cloud storage via the communication unit; displaying, on a display device, a device list indicating a status of each of the one or more devices set as the display target among the plurality of devices based on the repeatedly acquired status data, and updating the device list so as to indicate the latest status of each of the one or more devices; when a specific instruction is input through the user interface, displaying on the display device a screen that lists the devices set as hidden targets, separate from the device list, and indicates the status of each of the devices set as hidden targets, and receiving, as the switching instruction, an instruction to switch the devices set as hidden targets to the displayed targets through the screen; A management device configured to execute the above steps.

4. a computer of a communication device having access to a cloud storage storing a plurality of repeatedly updated status data, each of the plurality of devices describing a status of a corresponding device; setting each of the plurality of devices to be a display target or a non-display target based on a switching instruction input through a user interface so as to switch between the display target and the non-display target; repeatedly acquiring status data of each of the plurality of devices including the device set as a hidden target from the cloud storage; displaying, on a display device, a device list indicating a status of each of the one or more devices set as the display target among the plurality of devices based on the repeatedly acquired status data, and updating the device list so as to indicate the latest status of each of the one or more devices; when a specific instruction is input through the user interface, displaying on the display device a screen that lists the devices set as hidden targets, separate from the device list, and indicates the status of each of the devices set as hidden targets, and receiving, as the switching instruction, an instruction to switch the devices set as hidden targets to the displayed targets through the screen; A computer program for executing the above.

Images