Management system and management program

Abstract

To efficiently manage a terminal device while suppressing operation cost of a system as a whole.SOLUTION: A first communication device is operated in a main management mode on the basis of a fact that the first communication device has main management information. The first communication device in the main management mode acquires terminal information written on a cloud storage, and displays it on a first screen. A second communication device is operated in a sub-management mode on the basis of a fact that the second communication device has sub-management information. The second communication device in the sub-management mode executes write processing and display processing. The write processing includes acquiring terminal information from a terminal device and writing onto the cloud storage. The display processing displays the terminal information acquired from the terminal device, on a second screen which is partly different from the first screen.SELECTED DRAWING: Figure 1

Description

[Technical Field]

[0001] The present disclosure relates to a technique for managing a terminal device. [Background technology]

[0002] Patent Document 1 discloses a system in which a management device manages an image forming device via a server device. In this system, the server device acquires predetermined information from the image forming device and transmits the information to the management device. [Prior art documents] [Patent documents]

[0003] [Patent Document 1] Japanese Patent Application Publication No. 2019-148957 Summary of the Invention [Problem to be solved by the invention]

[0004] In the above system, the server device operates actively. That is, the server device independently performs various determination processes, such as the acquisition and transmission of the predetermined information, and notifies the management device or the image forming device of the processing results. This increases the cost of operating the server device.

[0005] In order to efficiently manage one or more image forming devices, it is possible to provide a communication device having a relay function between one or more image forming devices and a server, and to provide information about each image forming device from the communication device to the server. In this case, it is desirable to construct both the management device and the communication device easily and at low cost.

[0006] Therefore, in one aspect of the present disclosure, in a system in which a management device manages one or more terminal devices connected to a communication device via an intermediate device such as a server, an object is to enable efficient management of terminal devices while reducing the operating costs of the entire system. [Means for solving the problem]

[0007] According to an aspect of the present disclosure, there is provided a management system including a first communication device and a second communication device, the first communication device and the second communication device being capable of accessing cloud storage, and the second communication device being communicatively connected to at least one terminal device.

[0008] The first communication device has first setting information used for operation of the first communication device. The first setting information includes main management information indicating a main management mode. The first communication device executes a first read process, a first setting process, a first acquisition process, and a first display process.

[0009] The first read process is a process of reading first setting information. The first setting process is a process of setting the first communication device to a main management mode in response to main management information being included in the first setting information read by the first read process. The first acquisition process is a process of acquiring terminal information written to cloud storage for each of the at least one terminal device when the first communication device is set to the main management mode by the first setting process. The terminal information is information related to the corresponding terminal device. The terminal information is written to cloud storage by the second communication device. The first display process is a process of displaying a first screen. The first screen includes the terminal information acquired by the first acquisition process.

[0010] The second communication device has second setting information used for operation of the second communication device. The second setting information includes sub-management information indicating a sub-management mode. The second communication device executes a second read process, a second setting process, a second acquisition process, a write process, and a second display process.

[0011] The second read process is a process of reading second setting information. The second setting process is a process of setting the second communication device to a sub-management mode in response to the sub-management information being included in the second setting information read by the second read process. The second acquisition process is a process of acquiring terminal information from each of the at least one terminal device when the sub-management mode is set by the second setting process. The write process is a process of writing each piece of terminal information acquired by the second acquisition process to cloud storage. The second display process is a process of displaying a second screen. The second screen includes each piece of terminal information acquired by the second acquisition process. The second screen further partially matches the first screen and partially differs from the first screen.

[0012] The terminal information may include any information related to the terminal device, such as information indicating the terminal device (e.g., unique information), information indicating the state or operating state of the terminal device, etc.

[0013] In such a management system, the cloud storage functions passively with respect to the first communication device and the second communication device. That is, the second communication device writes terminal information to the cloud storage. The cloud storage does not voluntarily transmit the written terminal information to the first communication device. The written terminal information is acquired (i.e., read) by the first communication device. This reduces the operational costs of the cloud storage.

[0014] Furthermore, primary management information or secondary management information is provided to each of the first and second communication devices so that they can be set to a desired mode. The first communication device is set to the primary management mode in response to the provision of the primary management information, and the second communication device is set to the secondary management mode in response to the provision of the secondary management information. A screen including terminal information is displayed in each of the primary management mode and the secondary management mode. However, the screens in the primary management mode and the secondary management mode are partially identical but partially different. For example, information common to both the primary management mode and the secondary management mode may be displayed in the same manner. On the other hand, for example, information specific to the primary management mode may be displayed only on the screen in the primary management mode, and information specific to the secondary management mode may be displayed only on the screen in the secondary management mode.

[0015] Therefore, by providing each of the first and second communication devices with the primary management information or secondary management information corresponding to the mode to be set, the first and second communication devices can be operated in the desired mode easily and at low cost, thereby making it possible to efficiently manage terminal devices while reducing the operating costs of the entire management system.

[0016] The second setting information may include function restriction information indicating function restrictions in the secondary management mode. The secondary management mode may have a first mode in which execution of functions corresponding to the secondary management mode is not restricted, and a second mode in which execution of functions corresponding to the secondary management mode is restricted. The second setting process in the second communication device may set the second communication device to the second mode if the second setting information read by the second reading process includes secondary management information and function restriction information. This configuration makes it possible to easily restrict the functions of the second communication device. Therefore, it is possible to prevent a decrease in the reliability of the management system due to unintended operations on the second communication device, such as unintended changes to various settings in the second communication device.

[0017] The first communication device may include a first computer having first setting information, and the second communication device may include a second computer having second setting information. The first computer and the second computer each include a common program and are configured to execute the program. The common program is configured to cause the target computer, either the first computer or the second computer, on which the program is executed to perform different processes depending on whether the target computer has the first setting information or the second setting information. More specifically, the program causes the first computer to perform a first read process, a first setting process, a first acquisition process, and a first display process in response to the first computer having the first setting information. Meanwhile, the program causes the second computer to perform a second read process, a second setting process, a second acquisition process, a writing process, and a second display process in response to the second computer having the second setting information. In a management system configured in this manner, the common program allows the computer to selectively operate as either the first communication device or the second communication device. Therefore, the management system can be operated more efficiently and at lower cost.

[0018] Another aspect of the present disclosure is a management program executable by a computer included in each of a first communication device and a second communication device in a system including a first communication device and a second communication device, each configured to be able to access cloud storage.

[0019] This management program causes the computer to execute a read process and a mode setting process. The read process is a process for reading mode setting information. The mode setting information includes main management information indicating the main management mode or sub-management information indicating the sub-management mode.

[0020] The mode setting process sets the computer to the primary management mode if the mode setting information read by the read process includes primary management information, and sets the computer to the secondary management mode if the mode setting information read by the read process includes secondary management information.

[0021] Furthermore, when the mode is set to the primary management mode by the mode setting process, the management program further causes the computer to execute an acquisition process and a first display process. The acquisition process is a process of acquiring collected information written to cloud storage. The collected information is collected by another computer set to the secondary management mode and written to the cloud storage by the other computer. The first display process is a process of displaying a first screen. The first screen includes the collected information acquired by the acquisition process.

[0022] Furthermore, when the secondary management mode is set by the mode setting process, the management program further causes the computer to execute a write process and a second display process. The write process is a process of collecting the collected information and writing it to the cloud storage. The second display process is a process of displaying a second screen including the collected information collected in the write process. The second screen partially matches the first screen and partially differs from the first screen.

[0023] According to this management program, the first communication device and the second communication device can be set to either the primary management mode or the secondary management mode. That is, by having the management program load either mode setting information including primary management information or mode setting information including secondary management information, the computer executing the management program can be set to either the primary management mode or the secondary management mode as desired. Therefore, there is no need to prepare separate management programs corresponding to the primary management mode and the secondary management mode, and a system including the first and second communication devices set to the primary management mode and the secondary management mode, respectively, can be easily constructed using a common management program.

[0024] In yet another aspect of the present disclosure, a first communication device or a second communication device constituting the management system may be provided. In yet another aspect of the present disclosure, 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 method used in the management system, a method used in the first communication device in the system, and a method used in the second communication device in the system may be provided. [Brief explanation of the drawings]

[0025] [Figure 1] 1 is a configuration diagram of a management system according to an embodiment; [Figure 2] 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. [Figure 3] FIG. 3A is a block diagram of a second-type terminal device, and FIG. 3B is a block diagram of a cloud server. [Figure 4] FIG. 10 is an explanatory diagram illustrating an example of a management sequence by the management system. [Figure 5] FIG. 10 is an explanatory diagram illustrating an example of a schedule task table. [Figure 6] FIG. 6A is an explanatory diagram showing an example of a master initial file, and FIG. 6B is an explanatory diagram showing an example of a client initial file. [Figure 7] FIG. 10 is an explanatory diagram showing a master management screen. [Figure 8] FIG. 10 is an explanatory diagram showing a password setting screen. [Figure 9] FIG. 10 is an explanatory diagram showing a password change screen. [Figure 10] FIG. 10 is an explanatory diagram showing a client management screen in client normal mode. [Figure 11] FIG. 10 is an explanatory diagram showing a client management screen in a client lock mode. [Figure 12] 10 is a flowchart of a mode setting process. [Figure 13] 10 is a flowchart of a client initial file generation process. [Figure 14] 10 is a flowchart of a password change request process executed by the master when changing a lock password, and a password update process executed by the client. DETAILED DESCRIPTION OF THE INVENTION

[0026] Hereinafter, exemplary embodiments of the present disclosure will be described with reference to the drawings. [1. Embodiment] (1-1) Overall structure 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.

[0027] 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.

[0028] 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 the wide area network.

[0029] 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 a 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.

[0030] The terminal device 3 does not have the ability to use the cloud services provided by the cloud server 6. In other words, each terminal device 3 does not have the function of communicating with the cloud server 6. Hereinafter, this terminal device 3 will be particularly referred to as a first-type terminal device 3. On the other hand, the terminal device 4 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 4 has the function of communicating with the cloud server 6. Hereinafter, this terminal device 4 will be particularly referred to as a second-type terminal device 4.

[0031] The first type terminal device 3 installed at the second base is managed by the master 10 via the client 20 and the 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 without via the client 20.

[0032] 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 of the organization. For example, the first base where the master 10 is located may be an office that houses the 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.

[0033] Examples of the terminal devices 3 and 4 include a printer, a scanner, and a digital multifunction peripheral that integrates the functions of these devices. The master 10 and the client 20 are configured, for example, by installing a dedicated computer program on a personal computer.

[0034] (1-2) Equipment 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 the above processing is executed.

[0035] The storage unit 15 includes storage such as a solid state drive (SSD) and a hard disk drive (HDD), and stores various computer programs and data. The storage unit 15 stores a management program 17.

[0036] The management program 17 is a computer program for causing the CPU 11a to realize the management functions (main management functions) that should be realized by the master 10. The processing mainly performed by the control unit 11 described below may be understood to be realized by the processing executed by the CPU 11a in accordance with the computer program.

[0037] In this embodiment, the management program 17 is not a program dedicated to the master 10. The management program 17 is a computer program that can cause a computer to function as either the master 10 or the client 20. The management program 17 causes a computer to function as either the master 10 or the client 20 depending on the contents of an initial file that the management program 17 reads when the management program 17 is executed.

[0038] In this embodiment, as will be described later, a master initial file 18, which is an initial file for causing the computer in the master 10 (i.e., the control unit 11) to realize the main management function, is generated in the storage unit 15 of the master 10. The management program 17 of the master 10 realizes the main management function by referring to this master initial file 18 at startup. In the following description, the term "main management program" refers to the management program 17 that realizes the main management function in accordance with the master initial file 18.

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

[0040] The display unit 13 is configured to display various screens for a user who operates the master 10. An example of the display unit 13 is a liquid crystal display. An example of the various screens is a master management screen 70 (see FIG. 7), which will be described later. The master management screen 70 is a so-called portal screen in the management function realized by the master 10. Basically, the main administrator, who is the user of the master 10, can manage the terminal devices 3 and 4 to be managed by performing various input operations and viewing various information starting from the master management screen 70. The master management screen 70 can display, for example, the operating state, log information, and status information of each of the terminal devices 3 and 4 to be managed.

[0041] 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. Alternatively, the input unit 14 may include, for example, a touch panel. The touch panel may be disposed so as to overlap the entire or almost 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.

[0042] 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. It may be understood that the processing mainly performed by the control unit 21 described below is realized by processing executed by the CPU 21a in accordance with the computer program.

[0043] The memory unit 25 stores a management program 17, similar to the master 10. In the client 20, as will be described later, a client initial file 28 is generated, which is an initial file for causing the computer in the client 20 (i.e., the control unit 21) to realize the functions (sub-management functions) that should be realized by the client 20. The management program 17 of the client 20 realizes the sub-management functions by referencing this client initial file 28 at startup. In the following description, the term "sub-management program" refers to the management program 17 that realizes the sub-management functions in accordance with the client initial file 28.

[0044] That is, both the master 10 and the client 20 have a common management program 17. In the master 10, the master initial file 18 is referenced as the initial file to be referenced by the management program 17, thereby realizing the main management function of the master 10. That is, the master 10 is set to a master mode that realizes the main management function based on the master initial file 18. On the other hand, in the client 20, the client initial file 28 is referenced as the initial file to be referenced by the management program 17, thereby realizing the secondary management function of the client 20. That is, the client 20 is set to a client mode that realizes the secondary management function based on the client initial file 28.

[0045] In this embodiment, the client mode is further classified into two types: client normal mode and client lock mode. Specifically, the client 20 is set to one of these two modes. Specifically, when the sub-management program is started, it determines whether or not there is function restriction information in the client initial file 28. In this embodiment, the function restriction information corresponds to, for example, a lock password. If no function restriction information is included, the client normal mode is set. On the other hand, if function restriction information is included, the client lock mode is set. In the client normal mode, the execution of various functions provided in the client mode is not restricted. On the other hand, in the client lock mode, some of the various functions provided in the client mode are restricted and cannot be executed.

[0046] The communication unit 22 is connected to a local area network of the base where the client 20 exists, and further connected to a wide area network. The communication unit 22 may be connected to the wide area network via a router (not shown).

[0047] The display unit 23 includes, for example, a liquid crystal display, and is configured to display various screens for a user who operates the client 20. Examples of the various screens on the client 20 include client management screens 90 and 100 (see FIGS. 10 and 11), which will be described later. The client management screen 90 shown in FIG. 10 is displayed in client normal mode. The client management screen 100 shown in FIG. 11 is displayed in client lock mode.

[0048] The client management screens 90 and 100 are so-called portal screens in the sub-management function realized by the client 20. A sub-manager, who is a user of the client 20, can basically manage the subordinate terminal devices 3 by performing various input operations and viewing various information starting from the client management screens 90 and 100. The client management screens 90 and 100 may display, for example, the operating state, log information, and status information of each subordinate terminal device 3. The client management screens 90 and 100 are partially identical and partially different from the master management screen 70. Note that the functions executable via the client management screen 100 in client lock mode are more limited than the functions executable via the client management screen 90 in client normal mode.

[0049] The input unit 24 includes one or more input devices for inputting operation signals from a user who operates the client 20. The control unit 21 operates in accordance with the operation signals input through the input unit 24.

[0050] 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 include only one of the printing unit 35 and the reading unit 36.

[0051] The control unit 31 includes a CPU 31a and a memory 31b. The memory 31b may include a RAM as well as a nonvolatile memory such as a flash memory, and may store computer programs, setting data, and the like in the nonvolatile memory.

[0052] The CPU 31a as a processor performs overall control of the entire first-class terminal device by executing processes according to the computer programs stored in the memory 31b. The processes mainly performed by the control unit 31 described below may be understood to be realized by the processes executed by the CPU 31a according to the computer programs.

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

[0054] 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 coloring material 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 in a manner described below, and are then provided to the master 10. The reading unit 36 ​​is configured to read an image of a reading target on a printed matter or the like under the control of the control unit 31.

[0055] 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 include only one of the printing unit 45 and the reading unit 46.

[0056] The control unit 41 includes a CPU 41a and a memory 41b. The memory 41b may include a nonvolatile memory such as a flash memory, and may store computer programs, setting data, and the like.

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

[0058] 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 the local area network. The display unit 43 includes, for example, a liquid crystal display. The input unit 44 includes one or more input devices for inputting operation signals from the user.

[0059] 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 coloring material and log information such as the number of printed sheets are written from the second type terminal device 4 to the cloud server 6 in a manner described later, and are then provided to the master 10. The reading unit 46 is configured to read an image of a reading target on a printed matter or the like under the control of the control unit 41.

[0060] 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.

[0061] 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 may be understood to be realized by the processes executed by the CPU 61a in accordance with the computer programs.

[0062] The cloud storage includes a table storage and an object storage. When the control unit 61 executes the above process, the first storage 63 functions as a table storage, and the second storage 64 functions as an object storage.

[0063] 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 is configured with a set of properties, and each property is configured with a key-value (i.e., value) pair.

[0064] The exemplary second storage 64 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.

[0065] Microsoft's Azure (registered trademark) is a known 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.

[0066] The cloud server 6 functions passively with respect to the master 10, the client 20, and the second-type terminal device 4. That is, the cloud server 6 does not actively perform decision processing or the like itself, but does not issue commands, requests, notifications, etc. to the master 10, the client 20, and the second-type terminal device 4. The master 10, the client 20, and the second-type terminal device 4 each write necessary data to the cloud server 6 themselves as needed. Also, the master 10, the client 20, and the second-type terminal device 4 each access the cloud server 6 themselves as needed and read data stored in the cloud server 6.

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

[0068] Furthermore, the master 10 writes the above-mentioned text file or binary file, etc., to the second storage 64 as necessary. Specifically, for example, when the master 10 writes data indicating a task instructing firmware update 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., firmware update) to the second storage 64.

[0069] The data read from the cloud server 6 by the client 20 may include, for example, data indicating the above-mentioned notifications and the like, targeted at a first-type terminal device 3 under the control of the client 20. "Under the control of the client 20" means, in a broad sense, that the device exists within a local area network including the client 20 and is communicatively connected to the client 20, and in a narrow sense, that the device is communicatively connected to the client 20 and is registered as a management target in the client 20 (and thus in the master 10). In this embodiment, for example, at the second base, a first-type terminal device 3 connected to the client 20 through a local area network is a first-type terminal device 3 under the control of the client 20. Furthermore, the client 20 may read files written in the second storage 64 as necessary.

[0070] The data read from the cloud server 6 by the second type terminal device 4 may include, for example, data indicating the above-mentioned notifications and the like, which is targeted at the second type terminal device 4. Furthermore, the second type terminal device 4 may read files written in the second storage 64 as necessary.

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

[0072] Furthermore, if the data written by the master 10 includes data instructing a task (for example, the above-mentioned firmware update) targeted at a first type terminal device 3 under the control of the client 20, the client 20 writes data indicating the execution result of the task to the first storage 63 of the cloud server 6. This data is also written to a table (for example, an instant task table described later) provided individually for each first type terminal device 3 for writing the execution result of the task.

[0073] The data written to the cloud server 6 by the second type terminal device 4 may include, for example, status information and log information of the second type terminal device 4. That is, in the first storage 63, similar to the above-mentioned first type terminal device 3, a table corresponding to the second type terminal device 4 (for example, the schedule task table exemplified in FIG. 5) is also generated for the second type terminal device 4. The status information of the second type terminal device 4 is written to a "status" entity and / or a "registration" entity in the corresponding schedule task table.

[0074] 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 result of the task to the first storage 63 of the cloud server 6. Specifically, similar to the case of the first type terminal device 3 described above, the data is written to a table (for example, an instant task table) that is provided to write the execution result of the task of the second type terminal device 4.

[0075] 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 10.

[0076] (1-3) Sequence overview Next, various examples of management-related operations in the management system 1 will be explained in brief with reference to Fig. 4. First, an example of a preparatory stage for constructing the management system 1 will be explained. Note that an example of operations in this preparatory stage is not shown in Fig. 4.

[0077] In the preparation stage, an installer installs the management program 17 in the master 10. After starting up, the installer may refer to an initial file and perform various settings according to the initial file.

[0078] In this embodiment, there are, for example, the two types of initial files mentioned above. Specifically, there is a master initial file 18 for realizing the main management function (i.e., operating as the master 10), and a client initial file 28 for realizing the secondary management function (i.e., operating as the client 20). An example of the master initial file 18 is shown in Fig. 6A. An example of the client initial file 28 is shown in Fig. 6B.

[0079] The master initial file 18 may be generated anywhere and in any way. For example, the master initial file 18 may be generated by a text editor or the like in accordance with an input operation by the main administrator to the input unit 14 of the master 10. In this embodiment, the client initial file 28 is generated automatically or by user operation based on the main management program, as will be described later.

[0080] In the master initial file 18 illustrated in FIG. 6A, symbol A1 indicates operation mode information. The operation mode information specifies whether to operate in master mode or client mode. In other words, the operation mode information specifies whether to execute the main management function (i.e., function as master 10) or the secondary management function (i.e., function as client 20). The operation mode information illustrated in FIG. 6A indicates the master mode. Note that the operation mode information indicated by symbol B1 in FIG. 6B is also set in the client initial file 28. The operation mode information illustrated in FIG. 6B indicates the client mode. Symbol A2 indicates the cycle for periodically obtaining the execution results of instant tasks, which will be described later, by polling.

[0081] When the management program 17 is installed in the master 10, the control unit 11 of the master 10 executes processing in accordance with the management program 17 and the master initial file 18 (i.e., processing in accordance with the main management program). In other words, the master 10 has a main management function. Thereafter, the control unit 11 of the master 10 executes the management program 17 every time it is started up. In this case, the management program 17 references the master initial file 18 and realizes the main management function in accordance with the operation mode information A1 that indicates the master mode. In other words, it behaves as the main management program and causes the control unit 11 to operate in master mode.

[0082] Processing according to the main management program includes setting a cloud profile. The cloud profile setting is performed, for example, by the main administrator through a setting operation via the input unit 14. The cloud profile setting includes setting cloud parameters. As will be described later, the client 20 and the second-type terminal device 4 perform a polling operation on the cloud server 6 and an update operation of information held in the cloud server 6, including a schedule task, which will be described later. The cloud parameters include the period of the polling operation and the execution period of the schedule task (hereinafter referred to as the "information update period"). The cloud profile setting further includes setting a shared access signature (SAS) for using the cloud service.

[0083] The cloud profile is set, for example, in accordance with a setting operation performed by the main administrator via the input unit 14. The SAS is set individually for each of the first storage 63 and the second storage 64, that is, for each of the table storage and the object storage.

[0084] Subsequently, 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 entities of a table.

[0085] The master 10 also generates and exports a client profile including at least a portion of the cloud profile, i.e., the aforementioned client initial file 28. In this embodiment, as an example, the client initial file 28 is generated in response to an input operation by the main administrator requesting the generation of the client initial file 28.

[0086] In the client initial file 28 illustrated in FIG. 6B, symbol B2 indicates function restriction information, i.e., password information, for operating the client 20 in client lock mode. The password information B2 indicates a lock password. Symbol B3 indicates an SAS for accessing the second storage 64, and symbol B4 indicates an SAS for accessing the first storage 63. Symbols B5 to B7 each indicate an information update period for a schedule task. In this embodiment, as an example, multiple types of schedule tasks are executed according to the type of information to be acquired. The information update period is set individually for each schedule task. Symbol B8 indicates the execution period of a process for periodically checking the presence or absence of an instant task by polling.

[0087] The exported client initial file 28 is provided to the client 20. The client initial file 28 may be provided to the client 20 by any method. For example, the client initial file 28 may be provided from the master 10 to the client 20 by email or an easily portable storage medium.

[0088] The sub-administrator can install the management program 17 on the client 20 by starting the above-mentioned installer on the client 20. At this time, the client initial file 28 provided by the master 10 is imported, for example, by the sub-administrator's operation. As a result, processing in accordance with the management program 17 and the client initial file 28 (i.e., processing in accordance with the sub-management program) is executed by the control unit 21 of the client 20. In other words, the client 20 comes to have a sub-management function.

[0089] Thereafter, the control unit 21 of the client 20 executes the management program 17 each time it is started. At that time, the management program 17 references the client initial file 28 and realizes the secondary management function according to the operating mode information B1 indicating the client mode. In other words, it behaves as a secondary management program and causes the control unit 21 to operate in the client mode. At this time, the control unit 21 further determines whether or not the client initial file 28 contains function restriction information (password information B2 in this embodiment). If the function restriction information is not contained, the control unit 21 operates in the client normal mode, and if the function restriction information is contained, the control unit 21 operates in the client lock mode.

[0090] After the above installation and settings, the client 20 becomes able to use the cloud server 6. That is, the client 20 is configured to be able to communicate information with the master 10 via the cloud server 6. Specifically, the client 20 is configured to be able to execute 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.

[0091] Meanwhile, an SAS is registered in the second type terminal device 4 by an input operation by a device administrator who is an administrator of the second type terminal device 4. The control unit 41 of the second type 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 is hereinafter referred to as the "cloud connector." 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 acquires these cloud parameters and sets them in its own device.

[0092] In this way, the initial settings of the client 20 and the second type terminal device 4 (cloud connector), including the settings of the cloud parameters and SAS, are completed. Once the above-described initial settings are complete, the client 20 and the cloud connector perform an initial registration process. Specifically, the client 20 searches for a type 1 terminal device 3 that is communicably connected to the client 20. The searched type 1 terminal device 3 is then registered as a client-registered device in the client 20 itself, and also in the cloud server 6. Specifically, a schedule task table is generated individually for each type 1 terminal device 3 in the first storage 63. The initial registration information is then written to the schedule task table. Thereafter, the client 20 and the cloud connector write various information, including information acquired by the schedule task, to the schedule task table every time they execute a schedule task.

[0093] As illustrated in FIG. 5, 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.

[0094] As described above, the schedule task table has three entities related to "log," "status," and "registration" for each of the terminal devices 3 and 4. The information in each entity is updated by the client 20 that manages the corresponding terminal device if the corresponding terminal device is a first-type terminal device 3, or by the cloud connector in the corresponding terminal device if the corresponding terminal device is a second-type terminal device 4.

[0095] The "Notification Source" property in an entity indicates who updated the entity; when an entity is updated by a client 20, the "Notification Source" property is updated to the value "Client", and when an entity is updated by a cloud connector, the "Notification Source" property is updated to the value "Device".

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

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

[0098] As illustrated in the lower part of Figure 5, the response parameters may include, for example, JSON data. For example, log information may 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 "xxxxx ..." and "yyyyy ..." in the lower part of Figure 5 indicate exemplary abstract representations of object identifiers.

[0099] The initial state of the response parameter before being updated can exist as a request parameter with an initial value associated with the object identifier. In the example at the bottom of Figure 5, the initial value "%MIB(yyyyy ...)%" associated with the OID "yyyyy ..." has been rewritten to the value "4" by the update.

[0100] An entity related to "status" is a status entity having a first key value of "status", and status information for one of the terminal devices corresponding to the device ID described 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 and error information such as paper jams. As with the log entity, the response parameters for the status entity may be described in JSON format.

[0101] In this embodiment, the status information is written to the "status" entity in the schedule task table of the second type terminal device 4, and the status information is written to the "registration" entity in the schedule task table of the first type terminal device 3. However, the entities to which the status information is written are not limited to this.

[0102] The entity related to "registration" is a registration entity having the value "registration" of the first key, and device information of one of the terminal devices 3, 4 corresponding to the device ID entered as the value of the second key is described in the response parameter. In the response parameter, multiple item values ​​that explain the basic configuration of the device are described as device information. Also, as described above, in the schedule task table of the first type terminal device 3, status information is also written in the "registration" entity. Note that status information may also be written in the "registration" entity in the schedule task table of the second type terminal device 4.

[0103] The entities in the schedule task table of the second type terminal device 4 are updated by the corresponding cloud connector. The entities in the schedule task table of the first type terminal device 3 are updated by the client 20 that manages the first type terminal device 3. Identification information of the client 20 that manages the first type terminal device 3 is written as part of the device information in the "registration" entity of the first type terminal device 3. The schedule task table may include data written by the master 10.

[0104] After completing the above initial registration process, the client 20 and the cloud connector each periodically execute a schedule task according to the set information update cycle. Note that the above initial registration process may be included in the schedule task.

[0105] Specifically, a schedule task includes multiple tasks with different execution periods. Specifically, it includes at least a first task that periodically acquires status information at an information update period and writes it to a schedule task table, and a second task that periodically acquires log information and writes it to a schedule task table. In this embodiment, the first task will be specifically described, and descriptions of tasks other than the first task will be omitted. That is, in this embodiment, a "schedule task" basically means the first task.

[0106] First, a schedule task performed by the client 20 will be specifically described with reference to FIG. 4. When the time to execute the schedule task arrives, the client 20 executes a device search process (S01). The device search process includes a first process of searching for subordinate first-type terminal devices 3 and a second process of acquiring status information from each of the subordinate first-type terminal devices 3. The first process is basically the same as the initial registration process described above. Specifically, the client 20 searches again for first-type terminal devices 3 that are communicably connected to the client 20. Then, if the searched first-type terminal devices 3 include a first-type terminal device 3 that has not yet been registered in the cloud server 6, the first-type terminal device 3 is registered in the client 20 itself and in the first storage 63, as in the initial registration process.

[0107] When the device search process is completed, the client 20 updates the terminal registration information in the first storage 63 (S02). The terminal registration information is information related to each of the first type terminal devices 3 subordinate to the client 20, and in this embodiment, includes, for example, at least status information. If a new, unregistered first type terminal device 3 is found by the device search process, the terminal registration information also includes information necessary for registering the new first type terminal device 3. In this case, a new schedule task table is generated for the new first type terminal device 3, and status information and the like are written to the new schedule task table.

[0108] When the device search process is completed, the client 20 further registers the information acquired in the device search process in the client 20 itself, and displays a client management screen including the registered information on the display unit 23 (S03). Specifically, when the client 20 is set to the client normal mode, a client management screen 90 shown in Fig. 10 is displayed on the display unit 23. On the other hand, when the client 20 is set to the client lock mode, a client management screen 100 shown in Fig. 11 is displayed on the display unit 23. The client management screen 100 shown in Fig. 11 restricts input operations by the sub-administrator.

[0109] Next, a schedule task performed by the cloud connector will be described. When the time to execute the schedule task arrives, the cloud connector updates the terminal registration information in the first storage 63 (S11). The terminal registration information in this case is information related to the second type terminal device 4 in which the cloud connector is implemented, and in this embodiment, for example, includes at least current status information of the second type terminal device 4.

[0110] The client 20 and the cloud connector each execute the schedule task as described above repeatedly and periodically at an information update interval. Although not shown in the figure, the terminal devices 3 and 4 may execute the aforementioned instant tasks, which are non-periodic tasks other than scheduled tasks, 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 predetermined entity (the aforementioned instant task table) in the first storage 63. The aforementioned task instructing firmware update is an example of an instant task.

[0111] Next, a description will be given of the periodic update process (S21 to S23) that is periodically executed, for example, at regular intervals by the master 10. The periodic update process may be executed in response to a predetermined trigger, such as an execution instruction operation by an administrator.

[0112] When the time to execute the periodic update process arrives, the master 10 acquires update data from the first storage 63 (S21). The update data specifically includes registration information for each of the managed terminal devices 3 and 4. The registration information specifically includes data for each entity of "log," "status," and "registration" in the table (see FIG. 5).

[0113] The master 10, having acquired the update data, updates the internally registered data (S22). Specifically, the internally registered data is updated based on the update data acquired in S21. The internally registered data includes the registration information of each of the terminal devices 3 and 4 to be managed, which is stored in the master 10 itself, and other various data required for management.

[0114] Next, the master 10 updates the master management screen 70 (S23). That is, the internally registered data updated in S22 is reflected on the master management screen 70. For example, the log information and status information displayed on the master management screen 70 are updated to the content updated in S150.

[0115] (1-4) Explanation of the Master Management Screen The master management screen 70 of this embodiment will be described with reference to Fig. 7. The following description of the master management screen 70 is based on the premise that the terminal devices 3 and 4 are digital multifunction peripherals having a printer function.

[0116] 7, the master management screen 70 includes a first region R1, a second region R2, and a third region R3. In addition, in the master management screen 70, a plurality of tabs are displayed in regions different from the first to third regions R1 to R3. In this embodiment, for example, a first tab 71, a second tab 72, a third tab 73, and a fourth tab 74 are displayed. Any one of the first to fourth tabs 71 to 74 is alternatively selected via the input unit 14.

[0117] A screen corresponding to the selected tab is displayed in the first area 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, the master device list MDL is displayed in the first area R1.

[0118] The master device list MDL is a list of terminal devices registered as management targets in the master 10 (hereinafter referred to as "master management target terminals"). In addition, the master management screen 70 may have a group selection screen (not shown), and the master device list MDL may display terminal devices that belong to the group selected on the group selection screen from among the multiple registered terminal devices 3 and 4.

[0119] The master device list MDL shown in Fig. 7 is displayed in a table structure having row data for each master management target terminal to be displayed. Each row data has information such as the status, model name, toner / ink amount, and node name of the corresponding master management target terminal. The status indicates whether the corresponding master management target terminal is in a state where it can execute a process based on an external instruction from the master 10 or the like. When it is in a state where it can execute a process, 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 a process based on an external instruction, information indicating that it is in a state where it cannot execute a process, such as "Connection error," is displayed as the status.

[0120] The model name indicates the product model name of the corresponding master management target terminal. The node name indicates the node name of the corresponding master management target terminal. The toner / ink amount indicates the remaining amount of color material used in the printer function of the corresponding master management target terminal. If the corresponding master management target terminal has the function of an inkjet printer, the color material is ink. If the corresponding master management target terminal has the function of a laser printer, the color material is toner. In FIG. 7, the remaining amount of color material for each color of CMYK is shown as a bar graph as toner / ink amount. The toner / ink amount is part of the status information and is obtained from the terminal device via the cloud server 6. When the master 10 obtains the status information of each terminal device from the cloud server 6, it updates the image indicating the toner / ink amount (the bar graph described above) on the master management screen 70 based on the information indicating the toner / ink amount included in the status information.

[0121] When the third tab 73 is selected, a list of clients 20 managed by the master 10 is displayed in the first area R1. In this embodiment, for the sake of simplicity, one client 20 is illustrated as an example, but the management system 1 may have multiple clients 20. In this case, the master 10 can manage terminal devices under the control of each of the multiple clients 20 via the multiple clients 20.

[0122] The second area R2 displays detailed information about one of the master management target terminals displayed in the first area R1, selected via the input unit 14. The second area R2 further includes a graphical user interface for performing predetermined operations on one or more master management target terminals designated by, for example, check boxes in the master device list MDL. In this embodiment, for example, as illustrated in Fig. 7, the second area R2 displays at least a first object J1, a second object J2, and a third object J3.

[0123] For example, the second object J2 is operated via the input unit 14 to delete one or more master management target terminals designated by check boxes or the like from the master device list MDL. When the second object J2 is operated via the input unit 14, one or more master management target terminals designated by the main administrator using check boxes in the master device list MDL are set to be hidden and deleted from the master device list MDL.

[0124] The third area R3 displays objects indicating various items related to the management function. In this embodiment, the object displayed in the third area R3 is a cloud profile object 76. The cloud profile object 76 is operated via the input unit 14 to check or change various settings related mainly to the connection to the cloud server 6.

[0125] The cloud profile object 76 is also operated to receive a request to generate the client initial file 28. Specifically, when a specific generation request operation to request generation of the client initial file 28 is performed on the cloud profile object 76 via the input unit 14, a password setting screen 80 shown in Fig. 8 is displayed. The password setting screen 80 includes a password input field 81 and an input confirmation button 82.

[0126] If the primary administrator wants to set a lock password for the client 20, i.e., if the primary administrator wants the client 20 to operate in client lock mode by default, the primary administrator can set the lock password via the password setting screen 80. Specifically, when a lock password is entered in the password input field 81 and the input confirmation button 82 is operated, a client initial file 28 is generated that includes password information B2 indicating the entered lock password. On the other hand, if the input confirmation button 82 is operated without entering a lock password in the password input field 81, a client initial file 28 that does not include password information B2 is generated. The client initial file 28 generated in this manner is exported as described above. The generated client initial file 28 is also held in the master 10.

[0127] Returning to FIG. 7, the explanation of the master management screen 70 will continue. The master management screen 70 further displays a function setting button 75. The function setting button 75 is an interface that serves as the starting point for setting various functions in the master 10. When the function setting button 75 is operated, a function setting screen (not shown) is displayed. The main administrator can make various settings through the function setting screen.

[0128] The master management screen 70 also accepts a specific change request operation for changing the lock password. When the change request operation is performed via the input unit 14, a password change screen 86 shown in Fig. 9 is displayed on the display unit 13. In this embodiment, the change request operation includes selecting the third tab 73 to display a list of clients in the first area R1, selecting a client from the list of clients whose lock password is to be changed, and performing a predetermined operation to confirm the change request after the selection operation.

[0129] The password change screen 86 includes a change information input interface 87 and an input confirmation button 88. If the primary administrator wishes to change the lock password, he or she can change the lock password via the password change screen 86. Specifically, predetermined information required for password change is input into the change information input interface 87. In this embodiment, for example, the current password and a new password after the change must be input. When the required information is input into the change information input interface 87 and the input confirmation button 88 is operated, the lock password change process is performed. Specifically, as described below, an instant task requesting a lock password change is generated and written to the cloud server 6. As a result, as described below, this instant task is executed by the client 20, and the lock password is changed on the client 20. Note that, as will be described in detail later with reference to FIG. 14, the execution result of the instant task is acquired by the master 10 via the cloud server 6. Then, the master 10 performs processing according to the execution result.

[0130] (1-5) Explanation of the client management screen Next, the client management screens 90, 100 of this embodiment will be described with reference to FIGS. 10 and 11. First, the client management screen 90 when set to client normal mode will be described with reference to FIG. 10. The client management screen 90 has the same configuration as the master management screen 70. That is, like the master management screen 70, it has a first area R1, a second area R2, and a third area R3. Also, like the master management screen 70, a first tab 71, a second tab 72, and a fourth tab 74 are displayed. Also, like the master management screen 70, the second area R2 displays detailed information and first to third objects J1 to J3, etc. In these respects, the client management screen 90 is common to the master management screen 70.

[0131] On the other hand, the client management screen 90 also differs from the master management screen 70. Specifically, a client device list CDL is displayed in the first area R1 on the client management screen 90. The client device list CDL is a list of client registered devices.

[0132] Furthermore, the cloud profile object 76 (see FIG. 7) is not displayed in the third area R1 on the client management screen 90. Furthermore, the third tab 73 (see FIG. 7) corresponding to the client list is not displayed on the client management screen 90.

[0133] Next, the client management screen 100 when the client lock mode is set will be described with reference to Fig. 11. The client management screen 100 has basically the same configuration as the client management screen 90 in the client normal mode.

[0134] However, some of the functions that can be executed in client normal mode are restricted. Specifically, some input operations that could be accepted in client normal mode are invalidated and cannot be accepted. Note that "restriction" here also includes the complete inability to execute the relevant functions.

[0135] More specifically, in this embodiment, for example, input operations on the first to third objects J1 to J3 displayed in the third area R3 are disabled. Therefore, functions that start from input operations on the first to third objects J1 to J3 cannot be executed. Furthermore, for example, input operations on the fourth tab 74 are also disabled. Therefore, a task list cannot be displayed in the first area R1.

[0136] 11, in the client lock mode, various objects corresponding to restricted functions are displayed in gray on the client management screen 100. Therefore, the sub-administrator can easily recognize that the client lock mode is set and the functions that are disabled.

[0137] In the client lock mode, the function restrictions can be released by performing an unlock operation. In other words, the client lock mode can be changed to the client normal mode. The unlock operation includes at least inputting the lock password.

[0138] More specifically, in this embodiment, an interface for releasing the function restrictions is displayed on the function setting screen that is displayed by operating the function setting button 75 in the client lock mode. When this interface is operated, a password entry screen (not shown) is displayed on the display unit 13. When a valid lock password is entered on this password entry screen, the function restrictions are released and the operation mode switches to the client normal mode. As a result, a client management screen 90 corresponding to the client normal mode is displayed on the display unit 13. Note that it may be possible to switch from the client normal mode to the client lock mode.

[0139] (1-6) Mode setting process The mode setting process executed by the control unit 11 of the master 10 and the control unit 21 of the client 20 will be described with reference to Fig. 12. The mode setting process is included in the management program 17. When the control unit 11 and the control unit 21 are started, they each read and execute the management program 17. When processing based on the management program 17 is started, the mode setting process shown in Fig. 12 is executed.

[0140] First, a case where the control unit 11 of the master 10 executes the mode setting process will be described. When the control unit 11 of the master 10 starts this mode setting process, the specified operation mode is confirmed in S110. Specifically, the operation mode information set in the initial file of the master 10 is confirmed. In this embodiment, the master initial file 18 is set as the initial file in the master 10. Therefore, in S110, the operation mode information A1 in the master initial file 18 is referenced. As shown in FIG. 6A, the master initial file 18 contains the operation mode information A1 indicating the master mode. Therefore, the control unit 11 recognizes that it should operate in the master mode and proceeds to S120.

[0141] In S120, the control unit 11 sets the operating mode to master mode and executes master mode management processing. The master mode management processing refers to all processing corresponding to the main management function. The master mode management processing includes displaying the master management screen 70, various processing starting from the master management screen 70, the periodic update processing shown in FIG. 4, and the processing for generating the instant tasks described above.

[0142] After starting the master mode management process, if a predetermined termination condition is met, the control unit 11 terminates the mode setting process. The termination condition includes, for example, an operation to instruct the end of the execution of the management program 17, turning off the power of the control unit 11, etc.

[0143] Next, a case where the control unit 21 of the client 20 executes the mode setting process will be described. The initial file held by the client 20 is the client initial file 28 shown in FIG. 6B. Therefore, when the control unit 21 of the client 20 starts the mode setting process, the client initial file 28 is referenced in S110. The client initial file 28 contains operation mode information B1 indicating the client mode, as shown in FIG. 6B. Therefore, the control unit 21 recognizes that it should operate in the client mode, and proceeds to S130.

[0144] In S130, the control unit 21 determines whether or not there is an instruction to restrict functionality, i.e., whether or not to operate in client lock mode. Specifically, it determines whether or not password information B2 is included in the client initial file 28. If password information B2 is not included, the control unit 21 recognizes that it should operate in client normal mode and proceeds to S140.

[0145] In S140, the control unit 21 sets the operating mode to client normal mode and executes client normal mode management processing. The client normal mode management processing refers to all processing corresponding to the sub-management function with no functional limitations. The client normal mode management processing includes displaying the client management screen 90 corresponding to the client normal mode and various processing starting from the client management screen 90.

[0146] After the client normal mode management process starts, if a predetermined termination condition is met, the control unit 21 terminates the client normal mode setting process. On the other hand, if the client initial file 28 contains the password information B2, the control unit 21 recognizes in S130 that the client should operate in the client lock mode, and proceeds to S150.

[0147] In S150, the control unit 21 sets the operating mode to the client lock mode and starts the client lock mode management process. The client lock mode management process refers to all the processes corresponding to the sub-management function, excluding the restricted functions. The client lock mode management process includes displaying the client management screen 100 corresponding to the client lock mode and various processes starting from the client management screen 100.

[0148] After starting the client lock mode management process, the control unit 21 repeatedly executes the process of S160. In S160, the control unit 21 determines whether or not an unlock operation has been accepted. If an unlock operation has not been accepted, the control unit 21 continues the client lock mode management process. If an unlock operation has been accepted, the control unit 21 proceeds to S140 and switches the operation mode to the client normal mode.

[0149] (1-7) Client initial file generation process Next, the client initial file generation process executed by the control unit 11 of the master 10 will be described with reference to Fig. 13. This process is a process for generating the client initial file 28. This process is executed in response to an input operation requesting the generation of the client initial file 28.

[0150] When the control unit 11 starts the client initial file generation process, in S210 it receives a request to generate a client initial file made by the main administrator or the like. In S220, the control unit 11 accepts the input of a lock password. Specifically, the control unit 11 accepts the input of a lock password by causing the display unit 13 to display a password setting screen 80 shown in FIG.

[0151] In S230, the control unit 11 generates the client initial file 28. If a lock password was set in S220, the control unit 11 generates the client initial file 28 that includes password information B2. If a lock password was not set in S220, the control unit 11 generates the client initial file 28 that does not include password information B2.

[0152] In S240, the control unit 11 exports the client initial file 28 generated in S230. (1-8) Change password Next, the process executed when the master 10 changes the lock password set in the client 20 will be described with reference to FIG.

[0153] When the change request operation is performed by the main administrator or the like, the control unit 11 of the master 10 accepts various operations for the change in S310. Specifically, the control unit 11 displays the password change screen 86 shown in FIG. 9 and accepts input operations on the password change screen 86.

[0154] When the necessary information is entered on the password change screen 86 and the input confirmation button 88 is operated, the control unit 11 makes a request to change the lock password in S320. Specifically, in this embodiment, an instant task requesting a change of the lock password is generated and written to the cloud server 6. As a result, an instant task table corresponding to the instant task is generated in the first storage 63 of the cloud server 6. Information indicating the client 20 that is the target of the request, the new lock password, etc. are written in this instant task table.

[0155] On the other hand, as described above, the control unit 21 of the client 20 checks the presence or absence of an instant task for itself by periodic polling. Therefore, the control unit 21 also checks the presence or absence of an instant task at the first polling timing (S410) after the master 10 generates an instant task for changing the lock password.

[0156] At this time, the control unit 21 recognizes that the instant task for itself exists in the first storage 63, and acquires information about the instant task (S420). That is, the control unit 21 acquires the instant task that requests a change of the lock password.

[0157] Then, in S430, the control unit 21 executes the acquired instant task. Specifically, the lock password indicated in the password information B2 in the client initial file 28 is updated to the newly acquired lock password.

[0158] It is possible that, for some reason, the lock password is not updated correctly in the client 20. For example, the lock password may not be changed due to an error occurring in the client 20. Also, for example, a communication error between the client 20 and the cloud server 6 may prevent the client 20 from successfully acquiring the instant task, which may result in the lock password not being updated.

[0159] After executing the instant task, the control unit 21 of the client 20 writes the execution result of the instant task (that is, the result of the lock password change process) to the first storage 63 in S440.

[0160] The control unit 11 of the master 10 reads the execution result of the instant task from the first storage 63 at a predetermined timing (S330) after writing the instant task in S320. Then, in S340, the control unit 11 performs processing based on the execution result of the read instant task. Specifically, the control unit 11 determines whether the client 20 has succeeded in changing the lock password. If the control unit 11 determines that the client 20 has succeeded in changing the lock password, it updates the lock password held in the master 10 to the new lock password after the change. On the other hand, if the control unit 11 determines that the client 20 has failed to change the lock password, the control unit 11 does not update the lock password held in the master 10.

[0161] (1-9) Effects of the embodiment According to the embodiment described above, a common management program 17 is executed in each of the master 10 and the client 20. When the management program 17 is executed, it references an initial file and sets the operation mode specified in the initial file. Furthermore, the management screens used for management are partially identical and partially different for each operation mode. Therefore, the management system 1 can be managed efficiently and at low cost using the common management program 17.

[0162] Furthermore, the client initial file 28 for operating the client 20 in the client mode is generated in the master 10 based on the cloud profile generated in the master 10. Therefore, the client initial file 28 can be generated efficiently.

[0163] In addition, in this embodiment, it is possible to restrict the functions of the client 20. Specifically, a client normal mode and a client lock mode are provided as client modes, and when the client lock mode is set, some functions are restricted. This makes it possible to prevent unintended operations by the client 20. Moreover, setting the client lock mode can be easily achieved by setting password information B2 in the client initial file 28.

[0164] In this embodiment, the master 10 corresponds to an example of a first communication device in the present disclosure. The client 20 corresponds to an example of a second communication device in the present disclosure. The first-type terminal device 3 corresponds to an example of at least one terminal device in the present disclosure. The cloud server 6 corresponds to an example of cloud storage in the present disclosure. The master initial file 18 (FIG. 6A) corresponds to an example of first setting information in the present disclosure. In the master initial file 18, operation mode information A1 indicating the master mode corresponds to an example of primary management information in the present disclosure. The client initial file 28 (FIG. 6B) corresponds to an example of second setting information in the present disclosure. In the client initial file 28, operation mode information B1 indicating the client mode corresponds to an example of secondary management information in the present disclosure, and password information B2 corresponds to an example of function restriction information in the present disclosure. The master management screen 70 corresponds to an example of a first screen in the present disclosure. The client management screen 90 corresponds to an example of a second screen in the present disclosure. The master mode corresponds to an example of the primary management mode in the present disclosure. The client mode corresponds to an example of the secondary management mode in the present disclosure. More specifically, the client normal mode corresponds to an example of the first mode in the present disclosure, and the client lock mode corresponds to an example of the second mode in the present disclosure. Each password input to the change information input interface 87 in Figure 9 corresponds to an example of password change information in the present disclosure.

[0165] The processing of S01 corresponds to an example of a second acquisition processing in the present disclosure. The processing of S02 corresponds to an example of a write processing in the present disclosure. The processing of S03 corresponds to an example of a second display processing in the present disclosure. The processing of S21 corresponds to an example of a first acquisition processing in the present disclosure. The processing of S23 corresponds to an example of a first display processing in the present disclosure. The processing of S110 corresponds to an example of a first read processing and a second read processing in the present disclosure. The processing of S120 corresponds to an example of a first setting processing, a first acquisition processing, and a first display processing in the present disclosure. The processing of S140 and S150 correspond to an example of a second setting processing, a second acquisition processing, a write processing, and a second display processing in the present disclosure. The client initial file generation processing of FIG. 13 corresponds to an example of a generation processing in the present disclosure. The processing of S160 corresponds to an example of a release acceptance processing in the present disclosure. The transition from S160 to S140 corresponds to an example of a restriction release processing in the present disclosure. The processing of S310 corresponds to an example of a change acceptance processing in the present disclosure. The processing of S320 corresponds to an example of a change information output processing in the present disclosure. The process of S420 corresponds to an example of a change information acquisition process in the present disclosure. The process of S430 corresponds to an example of a password change process in the present disclosure.

[0166] 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.

[0167] For example, the master management screen 70 and the client management screen 90 described above are merely examples, and these screens 70 and 90 may be configured in any manner. Furthermore, the parts of the client management screen 90 that are common to and different from the master management screen 70 may be set in any manner and in any way.

[0168] The functions to be restricted in the client lock mode may be determined in any way in the client 20. Functions different from the functions based on input operations originating from the client management screen 90 may be restricted.

[0169] It is not essential that various objects corresponding to restricted functions be displayed in gray on the client management screen 100 that is displayed in the client lock mode. They do not have to be displayed in gray, or they may be displayed in a manner different from graying out.

[0170] Changing the lock password is not limited to using instant tasks. The first storage 63 is not limited to a NoSQL data store, but may be an SQL database such as a relational database.

[0171] At least one of the first and second bases may be provided with a second type terminal device 4. At the third base, a network system similar to that at the second base, i.e., a client 20 and a first type terminal device 3, may be provided. In the management system 1, there may be multiple network systems similar to that at the second base.

[0172] In the above embodiments, multiple functions of one component may be realized by multiple components, or one function of one component may be realized by multiple components. Furthermore, multiple functions of 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. [Explanation of symbols]

[0173] 1...management system, 3, 4...terminal device, 6...cloud server, 10...master, 17...management program, 18...master initial file, 20...client, 28...client initial file, 63...first storage, 64...second storage, 70...master management screen, 80...password setting screen, 86...password change screen, 90, 100...client management screen.

Claims

1. a first communication device configured to be able to access cloud storage; a second communication device that is communicatively connected to at least one terminal device and that is configured to be able to access the cloud storage; Equipped with the first communication device has first setting information used for operation of the first communication device, the first setting information including primary management information indicating a primary management mode; the first communication device, a first reading process for reading the first setting information; a first setting process for setting the first communication device to the master management mode in response to the first setting information read by the first reading process including the master management information; a first acquisition process for acquiring terminal information, which is information related to the at least one terminal device and which is written to the cloud storage by the second communication device when the primary management mode is set by the first setting process; a first display process for displaying a first screen including the terminal information acquired by the first acquisition process; is configured to run the second communication device has second setting information used for operation of the second communication device, the second setting information including secondary management information indicating a secondary management mode; the second communication device, a second reading process for reading the second setting information; a second setting process for setting the second communication device to the secondary management mode in response to the secondary management information being included in the second setting information read by the second reading process; a second acquisition process of acquiring the terminal information from each of the at least one terminal device when the secondary management mode is set by the second setting process; a write process of writing the terminal information acquired by the second acquisition process to the cloud storage; a second display process for displaying a second screen including the terminal information acquired by the second acquisition process, the second screen being partially identical to the first screen and partially different from the first screen; A management system that is configured to run

2. The management system according to claim 1, the first communication device set to the primary management mode is further configured to execute a generation process for generating the second setting information; the second reading process in the second communication device reads the second setting information generated by the generation process; Management system.

3. 3. The management system according to claim 1 or 2, the second setting information includes function restriction information indicating a restriction of a function in the secondary management mode, the sub-management mode has a first mode in which execution of a function corresponding to the sub-management mode is not restricted, and a second mode in which execution of a function corresponding to the sub-management mode is restricted, the second setting process in the second communication device sets the second communication device to the second mode when the second setting information read by the second reading process includes the secondary management information and the function restriction information. Management system.

4. 4. The management system according to claim 3, the functions restricted in the second mode include functions executed in response to an input operation on the second screen by a user of the second communication device. Management system.

5. 5. The management system according to claim 3 or claim 4, The second communication device set to the second mode a cancellation reception process for receiving a cancellation operation which is an input operation for requesting cancellation of the second mode; a restriction release process for switching the second communication device to the first mode when the release operation is accepted by the release acceptance process; configured to run Management system.

6. 6. The management system according to claim 5, the function restriction information includes a password; the unlocking operation includes an operation of inputting the password. Management system.

7. 7. The management system according to claim 6, the first communication device set to the primary management mode, a change acceptance process for accepting an input operation of password change information, which is information including the new password after the change, for requesting a change of the password; a change information output process for writing the password change information accepted by the change acceptance process to the cloud storage; is configured to run the second communication device set to the secondary management mode, a change information acquisition process for acquiring, from the cloud storage, the password change information written to the cloud storage by the change information output process; a password change process for changing the password included in the function restriction information to the new password based on the password change information acquired by the change information acquisition process; configured to run Management system.

8. A system comprising a first communication device and a second communication device, each configured to be able to access cloud storage, wherein the first communication device comprises a first computer and the second communication device comprises a second computer, the system comprising a management program executable by the first computer and the second computer, The management program is executed on the first computer or the second computer, a read process for reading mode setting information including main management information indicating a main management mode or sub-management information indicating a sub-management mode; a mode setting process for setting the target computer to the main management mode if the mode setting information read by the read process includes the main management information, and for setting the target computer to the secondary management mode if the mode setting information read by the read process includes the secondary management information; an acquisition process for acquiring collected information from the cloud storage when the mode is set to the primary management mode by the mode setting process, the collected information being information collected from at least one terminal device by a secondary management mode computer and written to the cloud storage, the secondary management mode computer being one of the first computer and the second computer that is different from the execution target computer and is set to the secondary management mode; a first display process for displaying a first screen including the collected information acquired by the acquisition process; a write process of collecting the collected information from the at least one terminal device and writing the collected information to the cloud storage when the secondary management mode is set by the mode setting process; a second display process for displaying a second screen including the collected information collected in the writing process, the second screen being partially identical to the first screen and partially different from the first screen; A management program that runs the

9. In a system including a first communication device and a second communication device, each of which is configured to be able to access cloud storage, a management program executable by a computer included in the first communication device, The management program is installed on the computer. a read process for reading setting information used for operation of the first communication device, the setting information including main management information indicating a main management mode; a setting process for setting the computer to the main management mode in response to the main management information being included in the setting information read by the reading process; an acquisition process for acquiring, when the primary management mode is set by the setting process, terminal information, which is information related to at least one terminal device communicatively connected to the second communication device and which is written to the cloud storage by the second communication device set to the secondary management mode; a display process for displaying a screen including the terminal information acquired by the acquisition process, the screen being partially identical to and partially different from a screen including the terminal information displayed on the second communication device; A management program that runs the

10. In a system including a first communication device and a second communication device, each of which is configured to be able to access cloud storage, a management program executable by a computer included in the second communication device, The management program is installed on the computer. a read process for reading setting information used for operation of the second communication device, the setting information including secondary management information indicating a secondary management mode; a setting process for setting the computer to the secondary management mode in response to the secondary management information being included in the setting information read by the reading process; an acquisition process for acquiring terminal information, which is information related to at least one terminal device communicatively connected to the second communication device, from each of the at least one terminal device when the secondary management mode is set by the setting process; a write process of writing the terminal information acquired by the acquisition process to the cloud storage; a display process for displaying a screen including the terminal information acquired by the acquisition process, the screen being partially identical to and partially different from a screen including the terminal information acquired by the first communication device from the cloud storage, the screen being displayed on the first communication device; A management program that runs the

Images