JP7732337B2 - Management system, management program, and management method - Google Patents

Description

This disclosure relates to technology for managing terminal devices.

Patent Document 1 discloses a system in which a server device acquires configuration information for an image forming device from a management device and provides the acquired configuration information to the image forming device. With this system, the image forming device can acquire the configuration information sent from the server device and configure the image forming device using the acquired information.

Japanese Patent Application Laid-Open No. 2019-148957

In a system configured as described above in which a management device uses a server device to manage terminal devices such as image forming devices, there may be a need to temporarily or permanently remove a specific terminal device from the management target.

There are various possible specific methods for removing a specific terminal device from the management list. For example, the administrator may manually remove the terminal device from the management list on the management device. Another possible method is for the management device to remove the terminal device from the management list in response to a specified process being performed on the terminal device indicating removal from the management list.

Regardless of the method used to remove a terminal device from the management list, it is desirable for the administrator to be able to properly understand on the management device that the terminal device has been removed from the management list. For example, it would be convenient to be able to understand not only the fact that the terminal device has been removed from the management list, but also the cause of the removal (for example, whether the removal was caused by an operation on the management device or the terminal device side).

Therefore, one aspect of the present disclosure aims to enable an administrator to properly understand on the management device that a specific terminal device has been removed from the management target in a system in which a first communications device manages terminal devices via an intermediate device such as a server device.

In one aspect of the present disclosure, a management system includes a first communication device and a second communication device. The first communication device and the second communication device each have access to cloud storage. The second communication device is communicatively connected to at least one first terminal device, or is provided in the second terminal device.

The cloud storage records management target information. The management target information includes information related to each of at least one management target terminal. The management target information is information related to the corresponding management target terminal. The at least one management target terminal is one or more of the at least one first terminal device and the at least one second terminal device. The management target information is recorded by a second communication device to which the management target terminal is connected or provided.

The first communication device executes a display process, a first reception process, a first deletion process, and a second deletion process.
The display process includes displaying a first terminal list, in which the at least one managed terminal is listed.

The first reception process includes receiving a first deletion request, the first deletion request requesting that any one of the at least one managed terminal be deleted from a first terminal list.
The first deletion process includes, in response to the first deletion request being accepted by the first acceptance process, identifying in a first manner that the first deletion request has been made to a first terminal to be deleted in the first terminal list. The first terminal to be deleted is a terminal to be managed that is the target of the first deletion request.

The second deletion process includes, in response to recognizing based on the contents recorded in the cloud storage that a second deletion request has been made by the second communication device, identifying the second deletion request to a second terminal to be deleted in the first terminal list in a second manner. The second deletion request requests that one of the at least one managed terminal be deleted from the management targets. The second terminal to be deleted is the managed terminal that is the target of the second deletion request.

The second communication device executes a second reception process and a deletion response process. The second reception process includes receiving a second deletion request. The deletion response process includes, in response to the second deletion request being received by the second reception process, reflecting in the cloud storage that the second deletion request has been made.

With this management system, when a managed terminal is deleted from the first terminal list, the administrator can appropriately grasp the deletion on the first communication device. Specifically, the administrator can easily distinguish whether the deleted managed terminal was deleted by a first deletion request on the first communication device or a second deletion request on the second communication device, based on whether the deleted managed terminal is identified in the first manner or the second manner (i.e., whether it is identified as a first deleted terminal or a second deleted terminal).

The first communication device may be configured to obtain management target information from cloud storage and/or write task-related data to cloud storage. The task-related data indicates a task to be executed by a managed terminal. The second communication device may be configured to obtain management target information from a managed terminal connected to or provided with the second communication device and write it to cloud storage, and/or execute a task based on the task-related data written to cloud storage.

In another aspect of the present disclosure, a first communication device or a second communication device constituting the above-mentioned management system may be provided. In yet another aspect of the present disclosure, a management program that is a computer program for causing a computer to function as the first communication device, and a computer program for causing a computer to function as the second communication device may be provided. In yet another aspect of the present disclosure, a management method for managing managed terminals from the first communication device via cloud storage and the second communication device, used in the above-mentioned management system, may be provided, in particular a method for managing managed terminals by referencing cloud storage in the first communication device.

1 is a configuration diagram of a management system according to an embodiment; FIG. 2A is a block diagram of a master, FIG. 2B is a block diagram of a client, and FIG. 2C is a block diagram of a first type terminal device. FIG. 3A is a block diagram of a second-type terminal device, and FIG. 3B is a block diagram of a cloud server. FIG. 10 is an explanatory diagram illustrating a part of an example of a management sequence by the management system. FIG. 10 is an explanatory diagram showing the remainder of the example of the management sequence by the management system. FIG. 10 is an explanatory diagram illustrating an example of a schedule task table. FIG. 10 is an explanatory diagram illustrating an example of a device management screen. FIG. 10 is an explanatory diagram showing another example of the device management screen. FIG. 10 is an explanatory diagram illustrating an example of a client setting screen. FIG. 10 is an explanatory diagram showing an example of a first deletion list screen.

Hereinafter, exemplary embodiments of the present disclosure will be described with reference to the drawings.
1. Embodiment
[Overall configuration]
The management system 1 according to an exemplary embodiment of the present disclosure is a network system configured to manage terminal devices 3 and 4 located at multiple locations via a cloud server 6 through cooperation between a master 10 and a client 20.

The master 10 illustrated in FIG. 1 is configured to be able to communicate with one or more terminal devices 3 installed at a first location via a local area network. The master 10 is further configured to be able to communicate with a cloud server 6 via a wide area network.

The client 20 is configured to be able to communicate with one or more terminal devices 3 installed at a second location via a local area network. The client 20 is further configured to be able to communicate with the cloud server 6 via a wide area network. The terminal device 4 installed at a third location is configured to be able to communicate with the cloud server 6 via a wide area network.

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 established at the third location. In this case, the terminal device 4 may be connected to the wide area network via the local area network within the third location.

Terminal device 3 does not have the ability to use the cloud services provided by cloud server 6. In other words, each terminal device 3 does not have the function of communicating with cloud server 6. Below, this terminal device 3 will be referred to specifically as a first-type terminal device 3. On the other hand, terminal device 4 is a terminal device that has the ability to use the cloud services provided by cloud server 6. In other words, terminal device 4 has the function of communicating with cloud server 6. Below, this terminal device 4 will be referred to specifically as a second-type terminal device 4.

The first-type terminal device 3 installed at the second base is managed by the master 10 via the client 20 and cloud server 6. The second-type terminal device 4 installed at the third base is managed by the master 10 via the cloud server 6, not via the client 20.

The terminal devices 3 and 4 managed by the master 10 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 for the organization. For example, the first base where the master 10 is located may be an office that houses the organization's management department. The other second and third bases may be branch offices of the organization that are distant from the first base.

Examples of terminal devices 3 and 4 include printers, scanners, and digital multifunction peripherals that combine these functions. The master 10 and client 20 are configured, for example, by installing a dedicated computer program on a personal computer.

[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 11a and a memory 11b. The CPU 11a as a processor executes processing in accordance with a computer program stored in the storage unit 15. The memory 11b is used as a work memory when executing the processing.

The memory unit 15 includes storage devices such as a solid state drive (SSD) and a hard disk drive (HDD), and stores various computer programs and data. The memory unit 15 stores a main management program 17. The main management program 17 is a computer program that causes the CPU 11a to implement the management functions that should be implemented by the master 10. The processing mainly performed by the control unit 11 described below can be understood to be implemented by processing executed by the CPU 11a in accordance with the computer program.

The communication unit 12 is connected to the local area network of the base where the master 10 is located, and is also connected to a wide area network. The communication unit 12 may also be connected to the wide area network via a router (not shown).

The display unit 13 is configured to display various screens for the user operating the master 10. An example of the display unit 13 is an LCD display. Examples of the various screens include the device management screen 70 (see Figures 7 and 8), the first deletion list screen (see Figure 10), and the second deletion list screen (not shown), which will be described later. The device management screen 70 is a so-called portal screen for the management function realized by the master 10. The primary administrator, who is the user of the master 10, can basically manage the managed terminal devices 3 and 4 by performing various input operations and viewing various information starting from the device management screen 70. The device management screen 70 can display, for example, log information and status information for the managed terminal devices 3 and 4.

The input unit 14 includes one or more input devices, such as a keyboard and a pointing device, for inputting operation signals from a user operating the master 10. Specifically, the input unit 14 may include, for example, a mouse. Furthermore, for example, the input unit 14 may include a touch panel. The touch panel may be positioned so as to overlap the entire area or almost the entire area of the display unit 13 where an image is displayed. The control unit 11 operates in accordance with the operation signals input through the input unit 14.

The client 20 shown in FIG. 2B includes a control unit 21, a communication unit 22, a display unit 23, an input unit 24, and a storage unit 25. The control unit 21 includes a CPU 21a and a memory 21b. The CPU 21a, as a processor, executes processing in accordance with a computer program stored in the storage unit 25.

The storage unit 25 stores a sub-management program 27. The sub-management program 27 is a computer program that causes the CPU 21a to implement functions related to the management functions of the master 10 that should be implemented by the client 20. The processing mainly performed by the control unit 21 described below can be understood to be implemented by processing executed by the CPU 21a in accordance with the computer program.

The communication unit 22 is connected to the local area network of the base where the client 20 is located, and is further connected to a wide area network. The communication unit 22 may be connected to the wide area network via a router (not shown). The display unit 23 includes, for example, an LCD display, and is configured to display various screens for the user operating the client 20. Screens displayed on the display unit 23 include, for example, the client setting screen 110 (see Figure 9), which will be described later. The input unit 24 includes one or more input devices for inputting operation signals from the user operating the client 20. The control unit 21 operates in accordance with the operation signals input through the input unit 24.

The first type terminal device 3 shown in FIG. 2C includes a control unit 31, a communication unit 32, a display unit 33, and an input unit 34. When the first type terminal device 3 is, for example, a digital multifunction peripheral, the first type terminal device 3 may further include a printing unit 35 and a reading unit 36. The first type terminal device 3 may also include only one of the printing unit 35 and the reading unit 36.

The control unit 31 includes a CPU 31a and memory 31b. In addition to RAM, memory 31b can also include non-volatile memory such as flash memory, and computer programs, setting data, etc. can be stored in the non-volatile memory.

The CPU 31a as a processor performs overall control of the entire Type 1 terminal device by executing processes in accordance with the computer program stored in the memory 31b. The processes mainly performed by the control unit 31 described below can be understood to be realized by the processes executed by the CPU 31a in accordance with the computer program.

The communication unit 32 is connected to the local area network of the base where the type 1 terminal device 3 is located so as to be able to communicate with the master 10 or client 20 located there. The display unit 33 includes, for example, an LCD display, and is configured to display various screens for the user operating the type 1 terminal device 3. The input unit 34 includes one or more input devices, such as a touch panel on an LCD display, for inputting operation signals from the user.

The printing unit 35 is configured to print an image on a sheet under the control of the control unit 31. Examples of the printing unit 35 include an inkjet printer and a laser printer. According to this embodiment, status information such as the remaining amount of colorant and log information such as the number of printed sheets are written from the first type terminal device 3 to the cloud server 6 via the client 20 using a method described below, and are then provided to the master 10. The reading unit 36 is configured to read an image of a target object on a printed material under the control of the control unit 31.

The second type terminal device 4 shown in FIG. 3A includes a control unit 41, a communication unit 42, a display unit 43, and an input unit 44. When the second type terminal device 4 is, for example, a digital multifunction peripheral, the second type terminal device 4 may further include a printing unit 45 and a reading unit 46. The second type terminal device 4 may also include only one of the printing unit 45 and the reading unit 46.

The control unit 41 includes a CPU 41a and memory 41b. The memory 41b may include non-volatile memory such as flash memory, and computer programs, setting data, etc. may be stored in the non-volatile memory.

The CPU 41a as a processor performs overall control of the entire device by executing processing in accordance with a computer program stored in memory 41b. A communication program 47 is stored in memory 41b. The communication program 47 is a program for using cloud services provided by the cloud server 6. The processing performed by the control unit 41 described below can be understood to be realized by processing performed by the CPU 41a in accordance with the computer program.

The communication unit 42 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 established at the third location, the communication unit 42 may be connected to the wide area network via that local area network. The display unit 43 includes, for example, an LCD display. The input unit 44 has one or more input devices for inputting operation signals from the user.

The printing unit 45 is configured to print an image on a sheet under the control of the control unit 41. According to this embodiment, status information such as the remaining amount of colorant and log information such as the number of printed sheets are written from the second-type terminal device 4 to the cloud server 6 using a method described below, and are then provided to the master 10. The reading unit 46 is configured to read an image of a target object on a printed material under the control of the control unit 41.

The cloud server 6 shown in FIG. 3B includes a control unit 61, a communication unit 62, a first storage 63, and a second storage 64. The control unit 61 includes a CPU 61a and a memory 61b.

The CPU 61a as a processor executes processes in accordance with the computer programs stored in the memory 61b. The processes executed by the CPU 61a include processes for causing the cloud server 6 to function as cloud storage. The processes mainly performed by the control unit 61 described below can be understood to be realized by the processes executed by the CPU 61a in accordance with the computer programs.

The above cloud storage includes table storage and object storage. By executing the above processing by the control unit 61, the first storage 63 functions as table storage, and the second storage 64 functions as object storage.

The exemplary first storage 63 functions as a NoSQL data store and is configured to store tables each consisting of a set of schema-less entities. Each entity in a table consists of a set of properties, and each property consists of a key-value (i.e., value) pair.

The exemplary second storage 64 functions as an object storage that can externally read and write any text and binary files as objects using the HTTP/HTTPS protocol.

Microsoft's Azure (registered trademark) is a well-known cloud service that provides the table storage and object storage described above. Cloud server 6 can operate in the same way as such a cloud service.

The cloud server 6 functions passively with respect to the master 10, clients 20, and second-type terminal devices 4. In other words, the cloud server 6 does not actively perform decision-making processes or issue commands, requests, or notifications to the master 10, clients 20, and second-type terminal devices 4. The master 10, clients 20, and second-type terminal devices 4 each write necessary data to the cloud server 6 as needed. Furthermore, the master 10, clients 20, and second-type terminal devices 4 each access the cloud server 6 as needed and read data stored in the cloud server 6.

Data written to the cloud server 6 by the master 10 may include, for example, data indicating various requests, notifications, etc. (hereinafter abbreviated as "notifications, etc.") targeted at one or more of the first-type terminal devices 3 and second-type terminal devices 4. More specifically, data indicating notifications, etc. is written to, for example, the first storage 63.

The master 10 also writes the aforementioned text files or binary files, etc., to the second storage 64 as necessary. Specifically, for example, when the master 10 writes data indicating a task that instructs updating firmware in one or more specific first-type terminal devices 3 and/or second-type terminal devices 4 to the first storage 63, the master 10 writes software (e.g., an update program) required to execute the task (i.e., to update the firmware) to the second storage 64.

Data read from the cloud server 6 by the client 20 may include, for example, data indicating the above-mentioned notifications, etc., targeted at a type 1 terminal device 3 under the control of the client 20. "Under the control of the client 20" means, in other words, that the device exists within a local area network that includes the client 20 and is capable of communicating with the client 20. In this embodiment, for example, at the second base, a type 1 terminal device 3 connected to the client 20 via a local area network is a type 1 terminal device 3 under the control of the client 20. Furthermore, the client 20 may read files written to the second storage 64 as necessary.

Data read from the cloud server 6 by the second-type terminal device 4 may include, for example, data indicating the above-mentioned notifications, etc., targeted at the second-type terminal device 4. Furthermore, the second-type terminal device 4 may read files written to the second storage 64 as necessary.

Data written to the cloud server 6 by the client 20 may include, for example, status information and log information for the type 1 terminal device 3 under the control of the client 20. As will be described later, a table corresponding to each type 1 terminal device 3 (for example, the schedule task table described later) is generated in the first storage 63 for each type 1 terminal device 3 under the control of the client 20. This table includes, for example, three entities related to "log," "status," and "registration," as will be described later with reference to FIG. 6. Log information is written to the "log" entity, and status information is written to the "status" entity. Various data, described later, is written to the "registration" entity by the master 10.

Furthermore, if the data written by the master 10 includes data instructing a task (e.g., the firmware update described above) targeted at a type 1 terminal device 3 subordinate to the client 20, the client 20 writes data indicating the execution results of that task to the first storage 63 of the cloud server 6. This data is also written to a table (e.g., the instant task table described below) provided individually for each type 1 terminal device 3 for writing the execution results of the task.

Data written to the cloud server 6 by a second-type terminal device 4 may include, for example, status information and log information for the second-type terminal device 4. That is, in the first storage 63, a table corresponding to the second-type terminal device 4 is generated for the second-type terminal device 4, just as with the first-type terminal device 3 described above. Furthermore, if the data written by the master 10 includes data instructing a task targeted at the second-type terminal device 4, the second-type terminal device 4 writes data indicating the execution results of that task to the first storage 63 of the cloud server 6. Specifically, just as with the first-type terminal device 3 described above, the data is written to a table designed to write the execution results of the task for the second-type terminal device 4.

The data read by the master 10 from the cloud server 6 includes, for example, the various data written in the above-mentioned tables.
In other words, the master 10 does not directly communicate with the clients 20 or the second-type terminal devices 4. The master 10 writes data to the cloud server 6 or reads data from the cloud server 6 as needed, thereby indirectly sending various notifications to the clients 20 and the second-type terminal devices 4 and acquiring various information from the clients 20 and the second-type terminal devices 4. The clients 20 and the second-type terminal devices 4 also write data to the cloud server 6 or read data from the cloud server 6 as needed, thereby indirectly acquiring various notifications from the master 10 and transmitting various information related to the terminal devices to the master.
[Sequence Overview]
Next, various examples of management-related operations in the management system 1 will be explained using Fig. 4. First, an example of a preparatory stage for constructing the management system 1 will be explained. Note that an example of the operation in this preparatory stage is not shown in Fig. 4.

In the preparation stage, the main management program 17 is installed in the master 10. As a result, processing in accordance with the main management program 17 is executed in the master 10. In the following explanation, "the master 10" basically means "the control unit 11 executing the main management program 17."

A cloud profile is set in the master 10. Setting the cloud profile includes setting cloud parameters. As described below, the client 20 and the second-type terminal device 4 perform polling operations on the cloud server 6 and update operations for information held in the cloud server 6. The cloud parameters include the period for the polling operation (hereinafter referred to as the "polling period") and the period for the information update operation (hereinafter referred to as the "information update period"). Setting the cloud profile further includes setting a shared access signature (SAS) for using the cloud service.

The cloud profile is configured, for example, by the primary administrator through the input unit 14. The SAS is configured separately for each of the first storage 63 and second storage 64, i.e., the table storage and the object storage.

Then, some or all of the configured cloud profile, including the configured cloud parameters, is uploaded from the master 10 to the first storage 63 and written to the first storage 63. Specifically, the cloud parameters are written to the first storage 63 as table entities.

The master 10 further exports at least a portion of the cloud profile as a client profile, i.e., data to be read by the client 20. The client profile may include, for example, the cloud parameters described above.

The exported client profile is provided to the client 20. The client profile may be provided to the client 20 in any manner. For example, the client profile may be provided from the master 10 to the client 20 using email or an easily portable storage medium.

The sub-administrator, who is the user of the client 20, can operate the client 20 to install the sub-management program 27 on the client 20. At this time, the sub-administrator's operation imports the client profile provided from the master 10. As a result, cloud parameters and SAS according to the client profile are set on the client 20. In the following explanation, "the client 20" basically means "the control unit 21 executing the sub-management program 27."

After the above installation and configuration, the client 20 becomes able to use the cloud server 6. That is, the client 20 is configured to be able to communicate with the master 10 via the cloud server 6. Specifically, the client 20 is configured to be able to perform relay operations between the master 10 and the first-type terminal device 3 via the cloud server 6, such as issuing task execution instructions from the master 10 to the first-type terminal device 3 and transmitting log information and status information from the first-type terminal device 3 to the master 10.

On the other hand, an SAS is registered in a type 2 terminal device 4 through input operations by the device administrator, who is the administrator of the type 2 terminal device 4. The control unit 41 of the type 2 terminal device 4 in which the SAS is registered executes processing in accordance with the communication program 47. The control unit 41 executing processing in accordance with the communication program 47 will be referred to as the "cloud connector" hereinafter. The cloud connector references the cloud parameters written by the master 10 in the first storage 63 of the cloud server 6. The cloud connector obtains these cloud parameters and sets them in its own device.

In this way, the initial settings of the client 20 and the second-type terminal device 4 (cloud connector), including the setting of cloud parameters and SAS, are completed. The operational sequence of the management system 1 after the initial settings are completed is outlined below with reference to Figure 4.

Once the above-described initial settings are complete, the client 20 and the cloud connector execute a schedule task periodically in accordance with the set information update period (S01, S02).
The schedule task by the cloud connector includes registering the type 2 terminal device 4 equipped with the cloud connector in the first storage 63 (i.e., setting a schedule task table). For example, when the corresponding type 2 terminal device 4 is not registered in the first storage 63 (for example, when a corresponding schedule task table does not exist), the cloud connector sets a table corresponding to the type 2 terminal device 4 in the first storage 63.

The scheduling task by the client 20 includes registering subordinate type 1 terminal devices 3 in the first storage 63. The client 20, for example, searches for subordinate type 1 terminal devices 3. If a type 1 terminal device 3 that is not registered in the first storage 63 is found, the client 20 registers the type 1 terminal device 3 in the first storage 63 (i.e., sets up a corresponding table). The client 20 itself also registers the type 1 terminal device 3 that has been found and registered in the first storage 63 as a client-registered device.

The schedule task also includes periodically updating various pieces of information stored in each table in the first storage 63 in accordance with a set information update period.
As illustrated in FIG. 6, the schedule task table is made up of a group of entities each including a plurality of properties such as a first key, a second key, a request parameter, a response parameter, a notification source, a status, and a device ID.

As mentioned above, the schedule task table has three entities for each of terminal devices 3 and 4: "Log," "Status," and "Registration." Information within each entity is updated by the client 20 that manages the corresponding terminal device if it is a type 1 terminal device 3, or by the cloud connector of the corresponding terminal device if it is a type 2 terminal device 4 (S01, S02).

The "Notification Source" property within an entity indicates who updated the entity; when the entity is updated by a client 20, 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".

The entity related to "log" is a log entity with the first key value "log", and the log information of the terminal device corresponding to the device ID entered as the second key value is described in the response parameters. The device ID is an ID unique to each of terminal devices 3 and 4.

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

As illustrated in the lower part of Figure 6, response parameters can include, for example, JSON data. For example, log information can be written in JSON format by associating the object identifier (OID) used in the management information base (MIB) of the corresponding parameter with its value. The descriptions "x.x.x.x.x ..." and "y.y.y.y.y ..." in the lower part of Figure 6 indicate exemplary abstract representations of object identifiers.

Response parameters in their initial state before being updated can exist as request parameters with an initial value associated with the object identifier. In the example at the bottom of Figure 6, the initial value "%MIB(y.y.y.y.y)%" associated with OID "y.y.y.y.y..." has been rewritten to the value "4" due to the update.

An entity related to "status" is a status entity with the first key value "status", and status information for one of the terminal devices 3 and 4 corresponding to the device ID entered as the value of the second key is described in the response parameters. When the corresponding terminal device is, for example, a printer or digital multifunction peripheral, the status information may include information on the remaining amount of coloring material in the corresponding terminal device, as well as error information such as paper jams. As with log entities, the response parameters for status entities may be written in JSON format.

The entity related to "registration" is a registration entity with the first key value "registration", and the response parameters describe device information for one of the terminal devices 3 and 4 corresponding to the device ID described as the second key value. The response parameters describe multiple item values describing the basic configuration of the device as device information.

In the schedule task table, the schedule task table entity for the second-type terminal device 4 is updated by the corresponding cloud connector (S01). The schedule task table entity for the first-type terminal device 3 is updated by the client 20 that manages the first-type terminal device 3 (S02). Identification information for the client 20 that manages the first-type terminal device 3 is written as part of the device information into the registration entity for the first-type terminal device 3.

However, the "management status" property of the registered entity is updated by Master 10. That is, a display flag is written to the "management status" property by Master 10.

In the default state immediately after a terminal device is registered (i.e., immediately after a registration entity for the terminal device is set), the display flag is set to on, for example. Setting the display flag to on means that the terminal device is displayed in the master device list DL (see FIG. 7 ) of the device management screen 70, which will be described later, in the master 10. In other words, the display flag indicates whether the corresponding terminal device is listed in the master device list DL in the master 10. Note that the display flag may be set to off in the default state. In this case, the master 10 may set the display flag to on in response to recognizing that the display flag is set to off through processing such as S04, which will be described later.

In the schedule task, the client 20 communicates with each subordinate type 1 terminal device 3 within the local area to obtain log information and status information. The client 20 then updates (e.g., overwrites) the corresponding log entities and status entities in the first storage 63 based on the obtained log information and status information (S02).

In the schedule task, the cloud connector acquires log information and status information for the corresponding type-2 terminal device 4. Then, based on the acquired log information and status information, the cloud connector updates (e.g., overwrites) the corresponding log entity and status entity in the first storage 63 (S01).

Although not shown in the figure, instant tasks, which are non-periodic tasks other than scheduled tasks, can be executed by terminal devices 3 and 4 based on a request from the master 10. The master 10 can cause the target terminal device to execute the instant task by registering the contents of the instant task and the target terminal device in a specified entity (the instant task table mentioned above) in the first storage 63.

Next, we will explain the periodic update process (S03 to S08) that is executed, for example, periodically by the master 10. Note that the periodic update process may be executed in response to a predetermined trigger, such as an execution instruction operation by an administrator. One of the purposes of the periodic update process is to update the device management screen 70, an example of which is shown in FIG. 7.

Before proceeding with the explanation of S03 and beyond, the device management screen 70 of this embodiment will be explained with reference to Figures 7 to 10. Note that the following explanation of the device management screen 70 assumes that the terminal devices 3 and 4 are digital multifunction peripherals with printer functionality.

As shown in FIG. 7, the device management screen 70 includes a first region R1, a second region R2, and a third region R3. Furthermore, multiple tabs are displayed in regions of the device management screen 70 that are different from the first to third regions R1 to R3. In this embodiment, for example, a first tab 71, a second tab 72, and a third tab 73 are displayed. Any one of the first to third tabs 71 to 73 is alternatively selected via the input unit 14. A screen corresponding to the selected tab is displayed in the first region R1. FIG. 7 shows an example in which the second tab 72 is selected and a screen corresponding to the second tab 72 is displayed. Specifically, when the second tab 72 is selected, a master device list DL is displayed in the first region R1.

The master device list DL is a list of terminal devices registered as managed devices in the master 10. More specifically, the master device list DL is a list of managed terminals (hereinafter referred to as "managed terminals") that are registered as managed devices and are set to be displayed in the master device list DL (i.e., are to be displayed).

The device management screen 70 may also have a group selection screen (not shown), and the master device list DL may display terminal devices that belong to a group selected on the group selection screen from among the multiple registered terminal devices 3 and 4.

The master device list DL shown in Figure 7 is displayed in a table structure with row data for each managed terminal to be displayed. Each row data contains information such as the status, model name, toner/ink amount, and node name of the corresponding managed terminal. The status indicates whether the corresponding managed terminal is in a state where it can execute processing based on an external instruction from the master 10 or the like. When it is in a state where it can execute processing, the status of the corresponding managed terminal, such as "Ready" or "Toner empty," is displayed. On the other hand, when it is not in a state where it can execute processing based on an external instruction, information indicating that it is not in a state where it can execute processing, such as "Connection error," is displayed as the status.

The model name indicates the product model name of the corresponding managed terminal. The node name indicates the node name of the corresponding managed terminal. The toner/ink amount indicates the remaining amount of colorant used in the printer function of the corresponding managed terminal. If the corresponding managed terminal functions as an inkjet printer, the colorant is ink. If the corresponding managed terminal functions as a laser printer, the colorant is toner. In Figure 6, the remaining amount of colorant for each color of CMYK is shown as a bar graph as toner/ink amount.

The second area R2 displays detailed information about one of the managed terminals displayed in the first area R1, selected via the input unit 14. The second area R2 also includes a graphical user interface for performing specific operations on one or more managed terminals designated, for example, by check boxes in the master device list DL. In this embodiment, as shown in FIG. 7, the second area R2 displays a delete operation object J1 and a task creation object J2. The delete operation object J1 is operated via the input unit 14 to delete one or more managed terminals designated, for example, by check boxes from the master device list DL. The task creation object J2 is operated via the input unit 14 to create an instant task targeting one or more designated terminal devices.

When the delete operation object J1 is operated via the input unit 14, one or more managed terminals designated by the primary administrator using check boxes in the master device list DL are set to be hidden and deleted from the master device list DL. For example, as shown in FIG. 7, when the check boxes for two managed terminals whose node names end with "6" and "7" are selected and the delete operation object J1 is operated, these two managed terminals are set to be hidden. Then, as shown in FIG. 8, these two managed terminals are deleted from the master device list DL. Managed terminals deleted from the master device list DL are placed in a first deletion list DDL1 (see FIG. 10).

However, even if a managed terminal is deleted from the master device list DL by such a deletion operation on the master 10, the managed terminal is still effectively treated as a managed terminal. That is, a table corresponding to the deleted managed terminal is maintained in the first storage 63. Then, in the first storage 63, deletion target information indicating that the terminal has been deleted on the master 10 is recorded in association with the corresponding table. Specifically, in this embodiment, the value of the "management status" entity in the "registration" entity of the managed terminal that has been made invisible, i.e., the display flag, is set to off.

Due to various factors, a situation may arise in which a certain managed device has its display flag set to off in the first storage 63, but is not set as a hidden device in the master 10 and is displayed in the master device list DL. However, even if such a situation occurs, the master 10 will acquire information that the display flag is set to off through a periodic update process, and the managed device will be set as a hidden device.

The third area R3 displays objects indicating various items related to management functions. In this embodiment, the objects displayed in the third area R3 include a first deletion list object 76 and a second deletion list object 77. These first and second deletion list objects 76, 77 are operated via the input unit 14 to display terminal devices that have been deleted from the master device list DL.

In this embodiment, there are two cases in which a managed device that has been displayed in the master device list DL can be deleted from the master device list DL. The first case is a case in which deletion is initiated by the operation of the deletion operation object J1 on the device management screen 70 of the master 10, as described above. The second case is a case in which deletion is initiated by a device deletion process performed by the client 20 or the cloud connector.

The second case will be explained in more detail. As mentioned above, in the client 20, the subordinate type 1 terminal devices 3 are registered as client-registered devices. For example, a user of the client 20, such as a sub-administrator, can delete any one or more client-registered devices from their status as managed terminals (i.e., remove them from management) by performing a specified individual deletion operation via the input unit 24 of the client 20. When an individual deletion operation is performed, the registration of the corresponding terminal device is cancelled in the client 20. Furthermore, the client 20 deletes the registration information of the corresponding terminal device in the first storage 63 (i.e., the table for the terminal device, etc.). In other words, when an individual deletion operation is performed on the client 20 side, unlike when the deletion operation object J1 is operated on the master 10, the registration information of the corresponding terminal device in the first storage 63 is deleted.

The client 20 can also display a client settings screen 110, as shown in FIG. 9. The sub-administrator can configure various settings for the client 20 through the client settings screen 110. The various settings that can be configured through the client settings screen 110 include enabling or disabling the cloud connection function. That is, the sub-administrator can enable or disable the function for connecting from the client 20 to the cloud server 6. In this embodiment, for example, the client settings screen 110 displays a checkbox 111 for enabling or disabling the cloud connection function. When the checkbox 111 is checked by the sub-administrator, the cloud connection function is enabled. Various functions performed by the client 20, such as the schedule tasks described above, within the overall management function are realized by enabling the cloud connection function on the client 20. On the other hand, when the cloud connection function is disabled, for example, by unchecking the checkbox 111, the client 20 deletes the registration information of the subordinate terminal devices from the first storage 63. Then, various management-related processes using communication with the cloud server 6, such as schedule tasks, are stopped.

The cloud connector's cloud connection function can also be enabled or disabled by a specific operation via the input unit 44 of the type 2 terminal device 4 on which the cloud connector is installed. When the cloud connection function is enabled, the cloud connector performs various functions, such as the schedule tasks described above. On the other hand, when the cloud connection function is disabled, the cloud connector deletes the registration information for the type 2 terminal device 4 on which the cloud connector is installed from the first storage 63. Then, various management-related processes, such as schedule tasks, that use communication with the cloud server 6 are stopped.

In this way, when a managed device is removed from management by the client 20 or cloud connector, the registration information for that managed device is deleted from the first storage 63.

The master 10 becomes aware of the deletion of registration information for managed devices from the first storage 63 through its periodic update process. When the master 10 becomes aware that registration information for any of the managed terminals listed in the master device list DL has been deleted from the first storage 63, it deletes the managed terminal from the master device list DL and places it in a second deletion list (not shown). The second deletion list has, for example, the same or a similar format as the first deletion list DDL1.

The primary administrator can selectively display the first deletion list DDL1 and the second deletion list on the display unit 13 of the master 10. For example, the master 10 may display the first deletion list screen 80 illustrated in FIG. 10 on the display unit 13 in response to the first deletion list object 76 on the device management screen 70 being operated via the input unit 14. The first deletion list screen 80 displays the first deletion list DDL1. The first deletion list screen 80 also displays a restore operation object J3. The primary administrator can specify a terminal device in the first deletion list DDL1, for example, using a checkbox, and operate the restore operation object J3 to re-list the specified terminal device in the master device list DL. In this case, the terminal device is deleted from the first deletion list DDL1. Furthermore, the corresponding display flag in the first storage 63 is set to ON.

Similarly, the master 10 may display a second deletion list screen (not shown) on the display unit 13 in response to the second deletion list object 77 on the device management screen 70 being operated via the input unit 14. The second deletion list screen displays the second deletion list. The second deletion list screen may have a form similar to the first deletion list screen 80 of FIG. 10, for example. In other words, terminal devices listed in the second deletion list may also be able to be listed again in the master device list DL by operating the restore operation object J3.

The first deletion list DDL1 and the second deletion list may be displayed in response to operations different from those described above. For example, an image for selecting an operation may be popped up in response to an operation of the first deletion list object 76 via the input unit 14. Then, the first deletion list DDL1 may be displayed in response to an object included in that image for displaying the first deletion list DDL1 being selected. Alternatively, for example, an object other than the first deletion list object 76 may be displayed on the screen, and the first deletion list DDL1 may be displayed in response to an operation of that object. The same applies to specific operations for displaying the second deletion list.

Returning to Figure 4, the periodic update process by the master 10 will now be described. When the time to execute the periodic update process arrives, the master 10 requests device data from the first storage 63 (S03) and acquires the device data from the first storage 63 (S04). Specifically, device data here refers to the data in the tables of each managed terminal. In other words, in S04, data for each "log," "status," and "registration" entity is acquired for each managed terminal.

After acquiring the device data, the master 10 checks the display flag of each managed device. Based on the acquired device data, the master 10 then checks the registration status in the first storage 63 (S06). In other words, it identifies the managed devices currently registered in the first storage 63 (i.e., for which a table containing a "Registration" entity is registered).

The master 10 then updates the master device list DL based on the acquired device data (S07). Specifically, if the master device list DL lists a managed terminal whose display flag is set to off based on the result of the display flag confirmation process in S05, the master 10 deletes the managed terminal from the master device list DL and places it in the first deletion list DDL1. Furthermore, if the master device list DL lists a terminal device that is not registered in the first storage 63 (i.e., a terminal device that has been deleted from management by the client 20 or cloud connector) based on the result of the registration status confirmation in S06, the master 10 deletes the managed terminal from the master device list DL and places it in the second deletion list. Then, if the device management screen 70 is currently displayed on the display unit 13, the master device list DL updated in S07 is displayed on the device management screen 70 (S08).

Next, the device deletion process by the master 10 (corresponding to the first case described above) will be described. The device deletion process by the master 10 is executed in response to the operation of the deletion operation object J1 on the device management screen 70. When the deletion operation object J1 is operated, the master 10 accepts the operation (S11). Upon accepting the operation of the deletion operation object J1, the master 10 sets the display flag of one or more management terminal devices (hereinafter referred to as "devices to be deleted") designated by check boxes or the like among the managed terminals listed in the master device list DL to off (S12). That is, the master 10 accesses the first storage 63 and sets the display flag of the "registration" entity of the device to be deleted to off.

Furthermore, the master 10 moves the device to be deleted from the master device list DL to the first deletion list DDL1 (S13). Then, if the device management screen 70 is currently displayed on the display unit 13, the master device list DL updated in S13 is displayed on the device management screen 70 (S14).

Next, the device deletion process by the client 20 (corresponding to the second case described above) will be described with reference to FIG. 5. When a registration deletion operation is performed by a sub-administrator or the like, the client 20 accepts the registration deletion operation (S21). Registration deletion operations include the individual deletion operation described above and the operation of disabling the cloud connection function via the client settings screen 110 described above (see FIG. 9).

When a registration deletion operation is received, the client 20 deletes the registration information of the managed terminal specified by the registration deletion operation from the first storage 63 (S22). For example, if an individual deletion operation is performed, the registration information is deleted individually for each specified managed terminal. If the cloud connection function is disabled, the registration information of the managed terminals under the client 20 is deleted all at once. As a result, if a regular update process is performed on the master 10 after S22 is executed, the managed terminals deleted in S22 will be deleted from the master device list DL and placed in the second deletion list.

Next, we will explain the device deletion process by the cloud connector (corresponding to the second case described above). When a sub-administrator or other user disables the cloud connection function on a type 2 terminal device equipped with a cloud connector, the cloud connector accepts this operation (S31). The cloud connector then deletes the registration information for the type 2 terminal device 4 equipped with the cloud connector from the first storage 63 (S32). As a result, if a periodic update process is performed on the master 10 after S32 is executed, the managed terminal deleted in S32 will be deleted from the master device list DL and placed on the second deletion list.

Next, the deletion list display process performed by the master 10 will be described. When a deletion list display operation is performed on the device management screen 70 by the primary administrator or the like, the master 10 accepts the deletion list display operation (S41). The deletion list display operation is an operation requesting the display of the first deletion list DDL1 or the second deletion list, and in this embodiment corresponds to an operation on the first deletion list object 76 or the second deletion list object 77.

When the master 10 receives a deletion list display operation, it displays a deletion list screen on the display unit 13, including either the first deletion list DDL1 or the second deletion list, whichever is specified by the deletion list display operation (S42). For example, if the deletion list operation is an operation on the first deletion list object 76, it displays the first deletion list screen 80, including the first deletion list DDL1.

Next, the device redisplay process performed by the master 10 will be described. When the first deletion list screen (FIG. 10) or the second deletion list screen is displayed on the display unit 13 of the master 10 and a redisplay operation is performed by the primary administrator or the like via the input unit 14, the master accepts the redisplay operation (S51). The redisplay operation is an operation that requests that a deleted managed device be displayed again in the master device list DL. Specifically, the redisplay operation corresponds to operating the restore operation object J3 described above via the input unit 13.

Upon receiving the redisplay operation, the master 10 sets the display flag of the managed device to be redisplayed in the first storage 63 to ON (S52). Furthermore, the master 10 moves the device to be redisplayed, which is located on the first deletion list screen or the second deletion list screen, to the master device list DL (S53). Then, if the device management screen 70 is currently displayed on the display unit 13, the master device list DL updated in S53 is displayed on the device management screen 70 (S54).

[Effects of the embodiment]
According to the present embodiment described above, when a managed terminal is deleted from the master device list DL, the main administrator can appropriately grasp the deletion in the master 10. Specifically, based on whether the deleted managed terminal is placed in the first deletion list or the second deletion list, the main administrator can easily identify whether the deletion was due to an operation on the master 10 side or an operation on either the client 20 or the cloud connector.

More specifically, the main administrator can display the first deletion list and the second deletion list on the master 10. Then, based on the terminal devices listed in the displayed first deletion list and second deletion list, the reasons for deletion of the deleted managed terminals can be easily identified.

Furthermore, when a managed device registration deletion operation is performed on the client 20 or cloud connector, the table of the corresponding terminal device is deleted from the first storage 63. Therefore, when a managed terminal is deleted from the management targets by the client 20 or cloud connector, the master 10 can easily know of the deletion by appropriately referencing the first storage 63.

In this embodiment, the master 10 corresponds to an example of a first communication device in this disclosure. The client 20 corresponds to an example of a second communication device in this disclosure. The cloud server 6 corresponds to an example of a cloud storage in this disclosure. The first-type terminal device 3 corresponds to an example of a first terminal device in this disclosure. The second-type terminal device 4 corresponds to an example of a second terminal device in this disclosure. At least a portion of each schedule task table for each terminal device in the first storage 63 corresponds to an example of managed object information in this disclosure. The master device list DL corresponds to an example of a first terminal list in this disclosure. Operating the deletion operation object J1 corresponds to an example of a first deletion request in this disclosure. The operations accepted in S21 and S31 correspond to an example of a second deletion request in this disclosure. An instant task corresponds to an example of a task in this disclosure. A display flag set to off corresponds to an example of information to be deleted in this disclosure.

The processing of S04 corresponds to an example of an acquisition processing in the present disclosure. The processing of S07 corresponds to an example of a second deletion processing in the present disclosure. The processing of S08, S14, and S44 correspond to an example of a display processing in the present disclosure. The processing of S11 corresponds to an example of a first reception processing in the present disclosure. The processing of S12 and S13 correspond to an example of a first deletion processing in the present disclosure. The processing of S12 also corresponds to an example of a deletion recording processing in the present disclosure. The processing of S21 and S31 correspond to an example of a second reception processing in the present disclosure. The processing of S22 and S32 correspond to an example of a deletion response processing in the present disclosure. The processing of S42 corresponds to an example of a first deletion list display processing and a second deletion list display processing in the present disclosure. The main management program 17 corresponds to an example of a management program in the present disclosure.

2. Other Embodiments
Although the embodiments of the present disclosure have been described above, the present disclosure is not limited to the above-described embodiments and can be implemented in various modified forms.

For example, in the above embodiment, as an example of the first aspect of the present disclosure, a managed device deleted from the master device list DL in the master 10 is placed in a first deletion list. Furthermore, as an example of the second aspect of the present disclosure, a managed device deleted in the client 20 or cloud connector (hereinafter abbreviated as "cloud side") is placed in a second deletion list. However, the first and second aspects of the present disclosure are not limited to the above-mentioned examples. That is, when a managed device is deleted from the master device list DL in the master 10, the managed device may be identified in any manner that allows the main administrator to recognize that the managed device was deleted by an operation on the master 10. Furthermore, when a managed device is deleted on the cloud side, the managed device may be identified in any manner that allows the main administrator to recognize that the managed device was deleted by an operation on the cloud side.

For example, in the master device list DL of the device management screen 70, deleted managed devices may be displayed in a different manner from other undeleted managed devices and in a different manner depending on whether they were deleted on the master 10 or the cloud side. Specifically, managed devices deleted on the master 10 may be displayed in a grayed-out manner, and managed devices deleted on the cloud side may be displayed in a different manner (for example, with a gray background color superimposed). Also, for example, in the master device list DL, managed devices deleted on the master 10 and managed devices deleted on the cloud side may be displayed with different images added to them.

For example, instead of the first deletion list object 76 and the second deletion list object 77, a single deletion object may be displayed on the device management screen 70. When this object is operated, a deletion list screen similar to the first deletion list screen 80 shown in FIG. 10 may be displayed. On this deletion list screen, managed devices deleted on the master 10 and managed devices deleted on the cloud side may be displayed together in different formats.

Furthermore, the method for deleting a managed terminal from the master device list DL in the master 10 is not limited to operating the deletion operation object J1. Furthermore, the method for deleting a managed terminal from management in the client 20 or cloud connector is not limited to the various operations described above, including operations via the client setting screen 110.

Furthermore, when an operation to remove a managed terminal from management is performed on the client 20 or cloud connector, the table for the corresponding managed terminal in the first storage 63 may be processed in any manner. For example, the entire relevant table may be deleted, or a specific portion of the relevant table may be deleted. In this case, the master 10 may determine whether the managed terminal has been deleted by the client 20 or cloud connector depending on whether the specific portion has been deleted.

The first storage 63 is not limited to a NoSQL data store, but may be an SQL database such as a relational database.
At least one of the first and second bases may be provided with a second-type terminal device 4. A third base may be provided with a network system similar to that of the second base, i.e., a client 20 and a first-type terminal device 3. In the management system 1, there may be multiple network systems similar to that of the second base.

Multiple functions possessed by one component in the above embodiments may be realized by multiple components, or one function possessed by one component may be realized by multiple components. Furthermore, multiple functions possessed by multiple components may be realized by one component, or one function realized by multiple components may be realized by one component. Furthermore, part of the configuration of the above embodiments may be omitted. Furthermore, 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.

1: Management system, 3, 4: Terminal devices, 6: Cloud server, 10: Master, 20: Client, 63: First storage, 70: Device management screen, 80: First deletion list screen, 110: Client settings screen, DL: Master device list, DDL1: First deletion list.

Claims (13)

a first communication device configured to be able to access cloud storage;
a second communication device that is communicatively connected to each of at least one first terminal device or that is provided in a second terminal device and that is configured to be able to access the cloud storage;
Equipped with
The cloud storage stores management target information including information related to each of at least one management target terminal, the at least one management target terminal being one or more of the at least one first terminal device and the second terminal device, and the management target information is stored by the second communication device to which the management target terminal is connected or provided;
the first communication device,
a display process for displaying a first terminal list in which the at least one managed terminal is listed;
a first reception process for receiving a first deletion request for requesting that any one of the at least one managed terminal be deleted from the first terminal list;
a first deletion process that, in response to the first deletion request being accepted by the first acceptance process, specifies in a first manner that the first deletion request has been made to a first terminal to be deleted, which is the managed terminal that is the request target of the first deletion request, in the first terminal list;
a second deletion process that, in response to recognizing, based on the recorded content of the cloud storage, that a second deletion request has been made by the second communication device, requesting that one of the at least one managed terminal be deleted from the managed terminals, specifies, in a second manner, that the second deletion request has been made to a second deleted terminal in the first terminal list, which is the managed terminal that is the request target of the second deletion request;
is configured to run
the second communication device,
a second reception process for receiving the second deletion request;
a deletion response process that reflects the fact that the second deletion request has been made in the cloud storage in response to the second deletion request being accepted by the second acceptance process;
A management system that is configured to run The management system according to claim 1,
the first communication device is configured to acquire the management target information from the cloud storage and/or write task-related data to the cloud storage, the task-related data indicating a task to be executed by the management target terminal;
the second communication device is configured to acquire the management target information from the management target terminal connected to or provided on the second communication device and write the information to the cloud storage, and/or execute the task based on the task-related data written in the cloud storage.
Management system. 3. The management system according to claim 1 or 2,
the first communication device has a first deletion list configured to list the first terminal to be deleted,
The first aspect of the first deletion process includes placing the first terminal to be deleted in the first deletion list.
Management system. 4. The management system according to claim 3,
The first aspect of the first deletion process further includes deleting the first terminal to be deleted from the first terminal list.
Management system. 5. The management system according to claim 3 or claim 4,
The first communication device is further configured to execute a first deletion list display process for displaying the first deletion list.
Management system. The management system according to any one of claims 1 to 5,
the first communication device has a second deletion list configured to list the second terminal to be deleted;
The second aspect of the second deletion process includes placing the second terminal to be deleted in the second deletion list.
Management system. 7. The management system according to claim 6,
The second aspect of the second deletion process further includes deleting the second terminal to be deleted from the first terminal list.
Management system. The management system according to claim 6 or 7,
The first communication device is further configured to execute a second deletion list display process for displaying the second deletion list.
Management system. The management system according to any one of claims 1 to 8,
the deletion handling process includes deleting part or all of information corresponding to the second terminal to be deleted from the management target information of the cloud storage;
Management system. The management system according to claim 9,
the first communication device is further configured to execute an acquisition process for acquiring the management target information from the cloud storage;
In the second deletion process, the first communication device treats, among the managed terminals included in the first terminal list, the managed terminal for which the deletion response process has been performed in the managed terminal information acquired by the acquisition process as the second terminal to be deleted.
Management system. The management system according to claim 10,
the first communication device is further configured to execute a deletion recording process, in response to the first deletion request being accepted by the first acceptance process, to record, in the cloud storage, deletion target information indicating that the first deletion request has been made, in association with information corresponding to the first deleted terminal that is the request target of the first deletion request in the management target information;
the acquisition process includes acquiring the information to be deleted from the cloud storage;
The first communication device is configured to, in response to the acquisition of the deletion target information by the acquisition process, execute the first deletion process on the first deletion target terminal when the first deletion target terminal associated with the deletion target information exists in the first terminal list.
Management system. A management program executable by a computer included in a first communication device in a system including a first communication device and a second communication device, each of which is configured to be able to access a cloud storage, the management program comprising:
the second communication device is communicatively connected to each of at least one first terminal device or is provided in the second terminal device;
The cloud storage records management target information including information related to each of at least one management target terminal, the at least one management target terminal being one or more of the at least one first terminal device and the second terminal device, and the management target information is recorded by the second communication device to which the corresponding management target terminal is connected or provided;
The management program is installed on the computer.
a display process for displaying a first terminal list in which the at least one managed terminal is listed;
a first reception process for receiving a first deletion request for requesting that any one of the at least one managed terminal be deleted from the first terminal list;
a first deletion process that, in response to the first deletion request being accepted by the first acceptance process, specifies in a first manner that the first deletion request has been made to a first terminal to be deleted, which is the managed terminal that is the request target of the first deletion request, in the first terminal list;
a second deletion process that, in response to recognizing, based on the recorded content of the cloud storage, that a second deletion request has been made by the second communication device, requesting that one of the at least one managed terminal be deleted from the managed terminals, specifies, in a second manner, that the second deletion request has been made to a second deleted terminal in the first terminal list, which is the managed terminal that is the request target of the second deletion request;
A management program that runs the A management method for managing at least one managed terminal by a first communication device that can access a cloud storage via the cloud storage and a second communication device that can access the cloud storage, the method comprising:
the second communication device is communicatively connected to each of at least one first terminal device or is provided in a second terminal device, and the at least one managed terminal is one or more of the at least one first terminal device and the second terminal device;
the cloud storage stores management target information including information related to each of the at least one management target terminals, the management target information being recorded by the second communication device to which the management target terminals are connected or provided;
The management method includes:
displaying, on the first communication device, a first terminal list in which the at least one managed terminal is listed;
receiving a first deletion request to request that any of the at least one managed terminal be deleted from the first terminal list;
In response to the first deletion request being accepted, specifying in a first manner that the first deletion request has been made to the managed terminal that is a request target of the first deletion request in the first terminal list;
In response to recognizing, in the second communication device, based on the recorded content of the cloud storage, that a second deletion request has been made to request that any one of the at least one managed terminal be deleted from a managed object, specifying in a second manner that the second deletion request has been made to the managed terminal in the first terminal list that is the request target of the second deletion request;
A management method comprising: