Management program, management device, management method, and management system

Abstract

To improve the efficiency of data transmission.SOLUTION: A main management program makes a control unit included in a master 2 execute first and second data acquisition processing. The first data acquisition processing acquires model image data (hereinafter, main connection model data) indicating a model of a main connection terminal device from a first-type terminal device 4 (hereinafter, the main connection terminal device) connected to the master 2. The second data acquisition processing acquires auxiliary connection model data and second model data from a cloud server 6. The auxiliary connection model data indicates a model of an auxiliary connection terminal device that is different from a model corresponding to the main connection model data, from among the first-type terminal devices 4 (hereinafter, the auxiliary connection terminal devices) connected to a client 3. The second model data indicates a model of a second-type terminal device 5 that is different from the model corresponding to the main connection model data.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 describes a management system in which a management device manages image forming devices via a server. [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 a management system in which a management device manages terminal devices such as image forming devices, it is desirable to streamline data transmission between the management device and the terminal devices via a server in order to send and receive various data between the management device and the terminal devices.

[0005] The present disclosure aims to improve the efficiency of data transmission in a management system. [Means for solving the problem]

[0006] One aspect of the present disclosure is a management program used in a management system that manages multiple terminal devices, configured to cause a control unit provided in the management device to execute a first data acquisition process and a second data acquisition process.

[0007] The management system comprises a management device, a sub-management device, a first type terminal device, a second type terminal device, and a storage device. The first type terminal device is a terminal device that is communicatively connected to either the management device or the sub-management device. The second type terminal device is a terminal device that is not communicatively connected to the management device or the sub-management device. The storage device is configured to be communicable with the management device, the sub-management device, and the second type terminal device.

[0008] The first data acquisition process acquires main connection model data related to the model of a main connection terminal device from a main connection terminal device that is a first type terminal device connected to the management device. The second data acquisition process acquires from the storage device sub-connection model data relating to a model of a sub-connection terminal device that is a first type terminal device connected to the sub-management device and that is different from the model corresponding to the main connection model data, and second model data relating to a model of a second type terminal device that is different from the model corresponding to the main connection model data.

[0009] The management program of the present disclosure configured in this manner prevents the management device from obtaining model data of the same model as the terminal device connected to the management device from the storage device, thereby improving the efficiency of data transmission performed in the management system in order for the management device to obtain model data.

[0010] Another aspect of the present disclosure is a management device used in a management system that manages multiple terminal devices, wherein a control unit provided in the management device is configured to execute a first data acquisition process and a second data acquisition process.

[0011] The management device of the present disclosure is a device controlled by the management program of the present disclosure, and can obtain the same effects as the management program of the present disclosure. Yet another aspect of the present disclosure is a management method used by a management device in a management system that manages a plurality of terminal devices, the method including a first data acquisition step and a second data acquisition step.

[0012] The management method of the present disclosure is a method executed by the management program of the present disclosure, and by executing this method, it is possible to obtain the same effects as the management program of the present disclosure. Another aspect of the present disclosure is a management system for managing a plurality of terminal devices, wherein the management device is configured to execute a first data acquisition process and a second data acquisition process. The sub-management device acquires sub-connection model data from a sub-connection terminal device and uploads the acquired sub-connection model data to a storage device. The second-type terminal device uploads the second model data to the storage device.

[0013] The management system of the present disclosure is a system controlled by the management program of the present disclosure, and can achieve the same effects as the management program of the present disclosure. [Brief explanation of the drawings]

[0014] [Figure 1] FIG. 2 is a block diagram showing the configuration of a management system. [Figure 2] FIG. 2 is a block diagram showing the configurations of a master, a client, and a first-type terminal device. [Figure 3] FIG. 2 is a block diagram showing the configuration of a second type terminal device and 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. 10 is an explanatory diagram illustrating an example of an instant task table. [Figure 7] FIG. 10 is a diagram illustrating a terminal management window. [Figure 8] 10 is a flowchart showing an image acquisition process. [Figure 9] FIG. 10 is a diagram showing the configuration of a model image entity. [Figure 10] FIG. 10 is a sequence diagram showing an operation related to acquisition of model image data. DETAILED DESCRIPTION OF THE INVENTION

[0015] Hereinafter, embodiments of the present disclosure will be described with reference to the drawings. (1) Overall structure The management system 1 of this embodiment is a network system configured to manage terminal devices 4 and 5 located at multiple locations via a cloud server 6 through cooperation between a master 2 and a client 3 .

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

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

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

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

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

[0021] The terminal devices 4 and 5 managed by the master 2 may be, for example, a group of terminal devices managed by an organization such as a company. In this case, each location may be an activity base of the organization. For example, the first location where the master 2 is located may be an office that houses the organization's management department. The other second and third locations may be branch offices of the organization that are distant from the first location.

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

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

[0024] The memory unit 15 includes storage devices such as a solid state drive and a hard disk drive, and stores various computer programs and data. The memory unit 15 stores a main management program 15a. The main management program 15a is a computer program that causes the CPU 21 to implement the management functions that should be implemented by the master 2. The processing mainly performed by the control unit 11 described below may be understood to be implemented by processing that the CPU 21 executes in accordance with the computer program.

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

[0026] 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 who operates the master 2. The control unit 11 operates in accordance with the operation signals input through the input unit 14.

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

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

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

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

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

[0032] The CPU 61 as a processor performs overall control of the entire first-type terminal device by executing processes in accordance with a computer program stored in the memory 62. The processes mainly performed by the control unit 51 described below may be understood to be realized by the processes executed by the CPU 61 in accordance with the computer program.

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

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

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

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

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

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

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

[0040] The cloud server 6 includes a control unit 91, a communication unit 92, a first storage 93, and a second storage 94. The control unit 91 includes a CPU 101 and a memory . CPU 101 as a processor executes processes in accordance with computer programs stored in memory 102. The processes executed by CPU 101 include processes for causing cloud server 6 to function as cloud storage. The processes mainly performed by control unit 91 described below may be understood to be realized by processes executed by CPU 101 in accordance with the computer programs.

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

[0042] The exemplary first storage 93 functions as a NoSQL data store and is configured to store tables each consisting of a set of schema-less entities, each of which is configured with a set of properties.

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

[0044] Microsoft Azure is a well-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. Azure is a registered trademark.

[0045] (3) Sequence overview Next, the operation sequence relating to management will be outlined. When the main management program 15a is installed in the master 2, processing in accordance with the main management program 15a is executed by the control unit 11 of the master 2. In other words, the master 2 comes to have a management function.

[0046] 4, the master 2 first performs a process of setting a cloud profile in S01. The master 2 sets the cloud profile in accordance with a setting operation performed by the main administrator via the input unit 14, for example.

[0047] Setting a cloud profile includes setting cloud parameters. The cloud parameters include initial setting parameters. As will be described later, the client 3 and the second-type terminal device 5 perform a polling operation on the cloud server 6 and an update operation of information held in the cloud server 6. This polling operation is an operation to periodically check the presence or absence of an instant task, which will be described later. The information update operation is an operation specified by a schedule task, which will be described later.

[0048] The initial setting parameters include, for example, a polling operation cycle (hereinafter referred to as a polling cycle) and an information update operation cycle (hereinafter referred to as an information update cycle). A plurality of information update cycles are set according to the type of information to be updated.

[0049] The cloud parameters may further include a schedule task template, which defines the process content of the schedule task to be executed by each of the terminal devices 4 and 5. The information update period corresponds to the execution period of one or more processes in the schedule task.

[0050] The schedule task template and the schedule task table exist separately. That is, in the first storage 93, the schedule task template is written to a first storage area, and the schedule task table is written to a second storage area different from the first storage area.

[0051] The setting of the cloud profile further includes setting a shared access signature (hereinafter referred to as SAS) for using the cloud service. SAS is an abbreviation for Shared Access Signature.

[0052] The SAS is set individually for each of the first storage 93 and the second storage 94 (i.e., the table storage and the object storage). When setting up a cloud profile on the master 2, the main administrator sets up the SAS set up for each of the first storage 93 and the second storage 94 as part of the cloud profile so that the first storage 93 and the second storage 94 can be accessed from the master 2.

[0053] The same SAS is also set when the main management program 15a is installed in the master 2. When the master 2 accesses the cloud server 6, the SAS set in the master 2 is sent to the cloud server 6. Then, if the sent SAS matches the SAS of the access destination set in the cloud server 6, communication with the access destination (i.e., reading and writing of data) becomes possible.

[0054] As shown in S02, in accordance with the operation of the primary administrator, the master 2 uploads cloud parameters according to the set cloud profile to the first storage 93 of the cloud server 6. As a result, as shown in S03, the uploaded cloud parameters are written to the first storage 93.

[0055] As shown in S04, the master 2 exports at least a portion of the cloud profile from the master 2 as a client profile (i.e., data to be read by the client 3). The client profile may include, for example, at least one of the above-mentioned initial setting parameters, schedule task template, and SAS. The client profile exported by the master 2 is provided to the client 3. The client profile may be provided to the client 3 by any method. For example, the client profile may be sent from the master 2 to the client 3 by email or other method.

[0056] As shown in S06, the sub-administrator operates the client 3 to install the sub-management program 35a on the client 3. At this time, as shown in S05, the sub-administrator operates the client 3 to import the client profile provided from the master 2. That is, various data set in the client profile is set in the client 3 as appropriate. For example, the SAS, polling period, information update period, etc. set in the client profile are imported and set in the client 3. The above-mentioned schedule task template may also be imported.

[0057] By installing the sub-management program 35a and setting the client profile as described above, the client 3 becomes able to use the cloud server 6. This allows the client 3 to communicate information with the master 2 via the cloud server 6. The client 3 is also configured to be able to execute a management relay function via the cloud server 6. The management relay function includes a task execution instruction from the master 2 to the first type terminal device 4, and the transmission of log information and status information from the first type terminal device 4 to the master 2, and is a function that relays information between the master 2 and the first type terminal device 4.

[0058] Furthermore, as shown in S07, the SAS is registered in the second type terminal device 5 by an input operation by the administrator of the second type terminal device 5 (hereinafter referred to as the device administrator). The registration of the SAS to the second type terminal device 5 may be performed, for example, via the input unit 74 of the second type terminal device 5. Alternatively, for example, the SAS may be registered to the second type terminal device 5 from an information processing device other than the second type terminal device 5. Specifically, a predetermined web server may be built into the second type terminal device 5. The SAS may be registered to the second type terminal device 5 by accessing the web server from an information processing device other than the second type terminal device 5, inputting the SAS via a user interface in the information processing device, and transmitting it to the web server.

[0059] The control unit 71 of the second type terminal device 5 in which the SAS is registered executes processing in accordance with the communication program 82a. The control unit 71 that executes processing in accordance with the communication program 82a is hereinafter referred to as the cloud connector. As shown in S08, the cloud connector uses the SAS to access the first storage 93 of the cloud server 6 and refers to the cloud parameters written by the master 2. The cloud connector acquires the cloud parameters and sets them in its own device.

[0060] When the cloud connector accesses the cloud server 6, the SAS of the access destination is sent from the cloud connector to the cloud server 6. Then, if the sent SAS matches the SAS of the access destination set in the cloud server 6, communication with the access destination (i.e., reading and writing of data) becomes possible.

[0061] When the second type terminal device 5 (i.e., the cloud connector) completes the initial settings (i.e., the processing of S07 and S08) including the setting of the above cloud parameters and SAS, it periodically executes the scheduled task according to the set information update period, as shown in S09.

[0062] When the client 3 completes the initial settings (i.e., processing of S05 and S06) including the setting of the above cloud parameters and SAS, it executes a scheduled task to periodically update the information stored in the first storage 93 of the cloud server 6 according to the set information update period, as shown in S10.

[0063] A schedule task using a cloud connector starts by first registering the device information in the first storage 93 if the corresponding device information is not registered in the first storage 93. The device information corresponding to a cloud connector is predetermined information indicating the second-type terminal device 5 in which the cloud connector is implemented.

[0064] If there is a type 1 terminal device 4 among the type 1 terminal devices 4 to be managed whose corresponding device information is not registered in the first storage 93, the schedule task by the client 3 starts by registering the device information of the type 1 terminal device 4 whose device information is not registered in the first storage 93. The device information of the type 1 terminal device 4 is predetermined information that indicates the type 1 terminal device 4.

[0065] The first storage 93 includes a schedule task table as one of its tables. The schedule task table includes a group of one or more entities. An entity includes multiple properties. In this embodiment, the multiple properties include, for example, "PartitionKey", "RowKey", "DeviceId", "NotifyParameter", "Progress", and "Source", as shown in FIG. 5.

[0066] The schedule task table has three entities related to "log," "status," and "registration" for each of the terminal devices 4 and 5. In other words, in this embodiment, there is an individual schedule task table (hereinafter referred to as "individual table") for each of the managed terminal devices 4 and 5, and the schedule task table can be considered to be a collection of these individual tables. Each individual table has three entities related to "log," "status," and "registration" for the corresponding terminal device 4 and 5.

[0067] If the corresponding terminal device is a first-type terminal device 4, the information in the entity is updated by the client 3 that manages the first-type terminal device 4. If the corresponding terminal device is a second-type terminal device 5, the information in the entity is updated by the cloud connector of the second-type terminal device 5.

[0068] If the entity is related to "log", the property "PartitionKey" stores "log", which is a string indicating that it is a "log". The entity related to "log" stores the log information of the terminal device corresponding to the device ID stored in the property "DeviceId" in the property "NotifyParameter". The device ID is identification information unique to each of the terminal devices 4 and 5.

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

[0070] If the entity is related to "status," the property "PartitionKey" stores "status," a string indicating that it is a "status." An entity related to "status" stores, in the property "NotifyParameter," status information for the terminal device corresponding to the device ID stored in the property "DeviceId." When the corresponding terminal device is a printer or a digital multifunction peripheral, the status information may include information on the remaining amount of coloring material in the corresponding terminal device and error information such as paper jams.

[0071] If the entity is related to "registration", the property "PartitionKey" stores "registration", which is a string indicating "registration". The entity related to "registration" stores device information of the terminal device corresponding to the device ID stored in the property "DeviceId" in the property "NotifyParameter". The device information includes multiple items that describe the basic configuration of the device.

[0072] The property "DeviceId" stores the device ID of the device that updated the entity. The property "NotifyParameter" stores a string written in JSON format to indicate the instructions for the scheduled task.

[0073] For example, the property "NotifyParameter" in an entity related to "status" is written in JSON format, associating the object identifier (OID) used in the management information base (MIB) of the corresponding parameter with its value. The descriptions "xxxxx..." and "yyyyy..." shown in task instruction T1 in Figure 5 are illustrative abstract representations of object identifiers. MIB stands for Management Information Base.

[0074] The instruction on the second line of task instruction T1 is ""xxxx···": "%MIB(xxxx···)%"". The above "xxxx···" is the object ID of the MIB.

[0075] The instruction on the third line of the task instruction T1 is ""yyyy···": "%MIB(yyyy···)%"". The above "yyyy···" is the object ID of the MIB.

[0076] If the above "xxxx..." is written as Oid1, the instruction on the second line is ""Oid1": "%MIB(Oid1)%"". And "%MIB(Oid1)%" is an instruction to get the value corresponding to Oid1, which is the object ID, and overwrite the obtained value with "%MIB(Oid1)%". Therefore, if the value corresponding to Oid1 is "XXXXXXX", in the registered data, ""Oid1": "%MIB(Oid1)%"" will be rewritten to ""Oid1": "XXXXXXX"".

[0077] Similarly, the instruction on the third line is ""Oid2": "%MIB(Oid2)%"" when the object ID "yyyy..." is written as Oid2. The descriptions "xxxxx..." and "yyyyy..." shown in the task result T2 in Figure 5 are illustrative abstract representations of the update results.

[0078] In each of the entities related to "log" and "registration", the character string in the property "NotifyParameter" is rewritten in the same way as in the entity related to "status".

[0079] The property "Progress" stores a string indicating the progress, such as the string "done" indicating that the task has been completed, the string "request" indicating that an instruction is being requested to be executed, or the string "processing" indicating that the task is currently being executed.

[0080] The property "Source" indicates the type of device that updated the entity. When an entity is updated by a client 3, the property "Source" of the entity stores the string "client", which indicates that the entity is a client 3. When an entity is updated by a cloud connector, the property "Source" of the entity stores the string "device", which indicates that the entity is a second-type terminal device 5.

[0081] The entity of the cloud connector of the second type terminal device 5 is updated by the cloud connector. The entity of the first type terminal device 4 is updated by the client 3 connected to the same local area network as the first type terminal device 4. That is, the client 3 updates the entity for each first type terminal device 4 under the client 3 (i.e., the first type terminal device 4 that is the management relay target). Identification information of the client 3 that has the first type terminal device 4 as the management relay target may be written as part of the device information in the registration entity of the first type terminal device 4.

[0082] The client 3 communicates with each of the first-type terminal devices 4 that are management relay targets within the same local area network, and acquires information necessary for updating device information from each of the first-type terminal devices 4. Based on the acquired information, the client 3 can update the registration entity of the corresponding first-type terminal device 4.

[0083] The client 3 further periodically communicates with each of the first-type terminal devices 4 that are management relay targets via the local area network to acquire corresponding log information and status information. Based on the acquired log information and status information, the client 3 can update the log entities and status entities of the corresponding first-type terminal devices 4.

[0084] The cloud connector of the second type terminal device 5 can periodically access the cloud server 6 and update its own log entity and status entity based on its own log information and status information.

[0085] The master 2 also functions as a client 3. That is, it can be understood that the master 2 functions as a client 3 with respect to the first type terminal device 4 at the first location. Specifically, three entities related to "log," "status," and "registration" corresponding to each of the first type terminal devices 4 at the first location (hereinafter referred to as master subordinate terminal devices) are generated in the schedule task table in the first storage 93 of the cloud server 6. The master 2, like the client 3, can acquire various information from the master subordinate terminal devices and update the registration entity, log entity, and status entity of each corresponding master subordinate terminal device.

[0086] 4, the master 2 further periodically accesses the first storage 93 of the cloud server 6 and refers to the log entities, status entities, and registration entities of the terminal devices 4 and 5. Based on these references, the master 2 can execute a process of storing the log information, status information, and device information of each of the terminal devices 4 and 5 in the storage unit 15.

[0087] Furthermore, the master 2 can display a list of the registered terminal devices 4 and 5 on the screen of the display unit 13, and can also display log information and status information of the terminal devices 4 and 5, in accordance with an operation signal output from the input unit 14 by a user operation. In this way, the management system 1 is configured so that the statuses of the terminal devices 4 and 5 used at multiple locations can be remotely monitored from one location where the master 2 is installed.

[0088] As shown in S12, the master 2 receives an instant task execution request operation from the main manager in accordance with an operation signal output from the input unit 14 by the main manager's operation, and generates data indicating an instant task entity (hereinafter referred to as instant task entity) in accordance with this execution request operation. An instant task is a non-periodic task other than a scheduled task.

[0089] Furthermore, the master 2 can register the corresponding instant task entity in the first storage 93 by transmitting the created data to the cloud server 6 as shown in S13.

[0090] The instant task entities are registered in the first storage 93 in the form of an instant task table, for example, as shown in FIG. The instant task table, like the scheduled task table, includes the properties "PartitionKey", "RowKey", "DeviceId", "NotifyParameter", "Progress" and "Source".

[0091] The property "PartitionKey" stores the string "instanttask" which indicates that it is an instant task. The property "RowKey" stores a transaction ID for identifying each instant task.

[0092] The property "DeviceId" stores a device ID for identifying the first type terminal device 4 or the second type terminal device 5 that is the destination of the instruction. The property "NotifyParameter" stores a string written in JSON format to indicate the instructions of the instant task.

[0093] The property "Progress" stores a character string indicating the progress of the instruction. The property "Source" is not used and is left blank. When a specific file is required to execute an instant task, the master 2 stores the file in the second storage 94, as shown in S14 of FIG. 4. In this case, information indicating the storage destination of the file (e.g., a URL) is described in the property "NotifyParameter." For example, when the instant task is a firmware update for the terminal devices 4 and 5, the master 2 stores an update file required for the firmware update in the second storage 94. In this case, for example, the URL of the storage destination of the firmware update file may be described in the property "NotifyParameter."

[0094] As shown in S15, the cloud connector of the second type terminal device 5 accesses the first storage 93 of the cloud server 6 at the set polling period and searches for an instant task that targets itself. That is, the cloud connector determines whether or not a new entity of an instant task that should be executed by itself is registered in the instant task table.

[0095] When a new entity is registered, the cloud connector notifies Master 2 that it has received the instant task request by rewriting the string of the property “Progress” in the corresponding instant task entity from “request” to “processing”.

[0096] As shown in S18, the master 2 that has registered the instant task entity checks the status of the instant task corresponding to the instant task entity. Specifically, the master 2 periodically references the instant task entity in the instant task table registered in the first storage 93 at a set polling cycle. By periodically referencing the instant task entity, the master 2 can confirm that the instant task request has been received based on the updated value of the progress status property.

[0097] When executing an instant task, the cloud connector of the second type terminal device 5 refers to the property "NotifyParameter" in the instant task entity. If a data file required to execute the instant task exists in the second storage 94, the cloud connector downloads the data file from the second storage 94 based on the storage destination information (e.g., a URL) described in the property "NotifyParameter," as shown in S16.

[0098] When the instant task is completed, the cloud connector of the second type terminal device 5 updates the corresponding instant task entity as shown in S17. Specifically, the cloud connector rewrites the character string of the property "Progress" in the corresponding instant task entity from "processing" to "done," thereby notifying the master 2 that the execution of the instant task has been completed.

[0099] As shown in S19, the client 3 accesses the first storage 93 of the cloud server 6 at the set polling period and searches for an instant task that targets the management relay target. That is, the client 3 determines whether or not a new entity of the instant task to be executed by the first type terminal device 4 that is the management relay target of the client 3 has been registered in the instant task table. Hereinafter, each of one or more first type terminal devices 4 that are set as the execution target of the instant task in the instant task table among the first type terminal devices 4 that are the management relay target (that is, one or more first type terminal devices 4 that correspond to the device ID stored in the property "DeviceId") will be referred to as an instant task execution target.

[0100] When a new instant task entity for the instant task execution target is registered, the client 3 notifies the master 2 that it has received the instant task request by rewriting the character string of the property "Progress" in the corresponding instant task entity from "request" to "processing." The client 3 then references the property "NotifyParameter" in the instant task entity to identify the processing content to be executed. Based on the identified processing content, the client 3 then obtains data files required for executing the instant task from the second storage 94 as necessary, as shown in S20.

[0101] Thereafter, as shown in S21, the client 3 instructs the instant task execution targets to execute the instant task via the local area network. At this time, the data file obtained from the second storage 94 is transferred to each instant task execution target. The client 3 then obtains the execution result of the instant task from the instant task execution targets.

[0102] When the execution of the instant task for all instant task execution targets is completed, the client 3 updates the instant task entity of the corresponding instant task execution target as shown in S22. Specifically, the client 3 notifies the master 2 that the execution of the instant task is completed by rewriting the character string of the property "Progress" in the corresponding instant task entity from "processing" to "done."

[0103] To check the status, as shown in S23, the master 2 refers to the instant task entity in the instant task table of the first storage 93, and finds that the character string of the property “Progress” has been rewritten to “done.” This confirms that the instant task has been completed, and the master 2 writes the processing result to the memory unit 15.

[0104] The master 2 can further display the processing results on the screen of the display unit 13. As shown in S24, when the master 2 confirms that the registered instant task has been completed for all corresponding instant task execution targets, the master 2 deletes the instant task entity of the instant task that is no longer needed from the first storage 93 as shown in S25. The master 2 also deletes the data file (e.g., firmware update file) provided for the instant task from the second storage 94 as shown in S26.

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

[0106] (4) Processing related to obtaining model image data The master 2 can display the terminal management window W1 shown in Fig. 7 on the display screen of the display unit 13. After the main management program 15a is started, a predetermined input operation for displaying the terminal management window W1 is performed via the keyboard or pointing device, and the terminal management window W1 is then displayed.

[0107] As shown in FIG. 7, the terminal management window W1 includes a management terminal display area R1 and a selected terminal display area R2. The management terminal display area R1 displays at least the status, model name, remaining toner / ink amount, and node name for each of the terminal devices 4 and 5 included in the management system 1.

[0108] The above status, model name, remaining toner / ink amount, and node name are displayed in the terminal management window W1 by the master 2 acquiring status information, model name information, remaining toner / ink amount information, and node name information from each terminal device 4, 5.

[0109] The selected terminal display area R2 displays the model name I1 and model image I2 of the terminal device 4, 5 selected in the control terminal display area R1. The hatched portion in the control terminal display area R1 shown in FIG. 7 corresponds to the selected terminal device 4, 5.

[0110] Next, a description will be given of the procedure of the image acquisition process executed by the control unit 11 of the master 2. The image acquisition process is a process that is repeatedly executed while the master 2 is in operation. When the image acquisition process is executed, the CPU 21 of the control unit 11 first determines whether or not a search timing has arrived in S110, as shown in Fig. 8. The search timing is the timing when the polling period set for the master 2 has elapsed.

[0111] Here, if the search timing has not arrived, the CPU 21 ends the image acquisition process. On the other hand, if the search timing has arrived, the CPU 21 executes a device search in S120. Specifically, the CPU 21 first performs data communication with the first type terminal devices 4 (hereinafter referred to as local devices) connected to the master 2 via a local area network, thereby identifying the local devices included in the management system 1 and the model names of each local device. Furthermore, the CPU 21 accesses the first storage 93 of the cloud server 6 and identifies the cloud devices included in the management system 1 and the model names of each cloud device by referring to entities related to "registration" for each cloud device (described later). The cloud devices include the first type terminal devices 4 and the second type terminal devices 5 connected to the client 3 via a local area network.

[0112] Next, at S130, the CPU 21 acquires model image data indicating the model of the local device from each local device identified at S120. However, the CPU 21 does not acquire model image data from a local device of the same model as the model corresponding to the model image data already acquired at S130. Note that the model image data is data corresponding to the model image I2 in the terminal management window W1.

[0113] Furthermore, in S140, the CPU 21 accesses the first storage 93 of the cloud server 6 and acquires model image data indicating the model of the cloud device from the model image entity by referring to the model image entity for each of the cloud device models identified in S120, and ends the image acquisition process. However, in S140, the CPU 21 does not acquire model image data from the model image entity of the same model as the model corresponding to the model image data already acquired in S130.

[0114] As shown in FIG. 9, the model image entity includes the properties "PartitionKey", "RowKey", and "Binary". The property "PartitionKey" stores "deviceimage", which is a character string indicating that the entity is a model image.

[0115] The property "RowKey" stores a character string indicating the model name. The property "Binary" stores model image data of the model identified by the model name stored in "RowKey."

[0116] The model image entity is registered in the first storage 93 of the cloud server 6 by the client 3 and the second type terminal device 5 . Next, an operational sequence for acquiring model image data will be briefly described.

[0117] 10, the second type terminal device 5 executes a process of enabling access to the cloud server 6 in S41, and then in S42 registers the registration entity and the model image entity in the first storage 93. However, if a model image entity of the same model as the second type terminal device 5 has already been registered, the second type terminal device 5 does not register the model image entity.

[0118] In S43, the client 3 executes a process to enable access to the cloud server 6, and then in S44, performs a device search. As a result, the client 3 identifies the first type terminal devices 4 connected to the client 3 via the local area network and the model names of each first type terminal device 4.

[0119] In addition, in S45, the client 3 acquires device information and model image data from each first-type terminal device 4 identified by the device search, and registers the registration entity of each first-type terminal device 4 and the model image entity of each model in the first storage 93.

[0120] Then, in S46, the master 2 executes a device search for the first storage 93 of the cloud server 6, and in S47 and S48, acquires device information and model image data from the first storage 93.

[0121] (5) Effects The main management program 15a configured in this manner is configured to cause the control unit 11 included in the master 2 to execute a first data acquisition process and a second data acquisition process.

[0122] The first data acquisition process acquires, from a first type terminal device 4 (hereinafter referred to as a main connection terminal device) connected to the master 2, model image data (hereinafter referred to as main connection model data) indicating the model of the main connection terminal device.

[0123] The second data acquisition process acquires sub-connection model data and second model data from the cloud server 6. The sub-connection model data is model image data indicating a model of a sub-connection terminal device different from the model corresponding to the main connection model data, among the first type terminal devices 4 (hereinafter referred to as sub-connection terminal devices) connected to the client 3. The second model data is model image data indicating a model of a second type terminal device 5 different from the model corresponding to the main connection model data.

[0124] Such a main management program 15a does not allow the master 2 to obtain, from the cloud server 6, model image data of the same model as that of the first-type terminal device 4 connected to the master 2. This enables the main management program 15a to improve the efficiency of data transmission performed in the management system 1 in order for the master 2 to obtain model image data.

[0125] Furthermore, the first data acquisition process does not acquire main connection model data from a main connection terminal device of the same model as the model corresponding to the main connection model data that has already been acquired. Such a main management program 15a can prevent duplicate acquisition of main connection model data of the same model, thereby reducing the processing load on the master 2.

[0126] Furthermore, the client 3 uploads the sub-connection model data only when it has been able to acquire the sub-connection model data from the sub-connection terminal device. This prevents data indicating that the sub-connection model data could not be acquired from being stored in the cloud server 6, allowing the management system 1 to prevent a decrease in the data storage capacity of the cloud server 6.

[0127] Furthermore, the client 3 uploads a model image entity in which first model name information indicating the model name of the sub-connection terminal device and sub-connection model data are associated with each other to the cloud server 6. The second type terminal device 5 uploads a model image entity in which second model name information indicating the model name of the second type terminal device 5 and second model data are associated with each other to the cloud server 6. This prevents model image data of the same model from being stored in duplicate in the cloud server 6, and therefore the management system 1 can prevent a reduction in data storage capacity in the cloud server 6.

[0128] In the embodiment described above, the master 2 corresponds to a management device, the client 3 corresponds to a sub-management device, the cloud server 6 corresponds to a storage device, and the main management program 15a corresponds to a management program.

[0129] Moreover, S130 corresponds to a first data acquisition process and a first data acquisition step, and S140 corresponds to a second data acquisition process and a second data acquisition step. Although one embodiment of the present disclosure has been described above, the present disclosure is not limited to the above embodiment and can be implemented in various modifications.

[0130] For example, in the above embodiment, the model data is model image data, but the model data is not limited to image data, and may be information common to the same model (for example, model specifications). Furthermore, in the above embodiment, the model image data is stored in the first storage 93 of the cloud server 6, but the model image data may also be stored in the second storage 94 of the cloud server 6.

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

[0132] In addition to the master 2 described above, the present disclosure can also be realized in various forms, such as a system including the master 2 as a component, a program for causing a computer to function as the master 2, a non-transient physical recording medium such as a semiconductor memory on which this program is recorded, and a management method. [Explanation of symbols]

[0133] 1... management system, 2... master, 3... client, 4... first type terminal device, 5... second type terminal device, 6... cloud server, 11... control unit, 15a... main management program

Claims

1. A management program used in a management system that manages a plurality of terminal devices, The management system includes: A management device; a sub-management device; a first type terminal device that is the terminal device connected to either the management device or the sub-management device so as to be able to communicate with the management device; a second type terminal device that is the terminal device that is not communicably connected to the management device and the sub-management device; a storage device configured to be able to communicate with the management device, the sub-management device, and the second-type terminal device; The management program is configured to cause a control unit of the management device to: a first data acquisition process for acquiring main connection model name information indicating the model name of the main connection terminal device and main connection model data related to the model of the main connection terminal device from the main connection terminal device that is the first type terminal device connected to the management device; a second data acquisition process for acquiring sub-connection model name information indicating the model name of a sub-connection terminal device that is the first type terminal device connected to the sub-management device and second model name information indicating the model name of the second type terminal device, and acquiring from the storage device sub-connection model data related to a model of the sub-connection terminal device that is different from the model indicated by the main connection model name information acquired in the first data acquisition process, among the sub-connection terminal devices, and second model data related to a model of the second type terminal device that is different from the model indicated by the main connection model name information acquired in the first data acquisition process; The management program that is configured to run

2. 2. The management program according to claim 1, The first data acquisition process is a management program that does not acquire the main connection model data from the main connection terminal device of the same model as the model corresponding to the main connection model data that has already been acquired.

3. A management device used in a management system that manages a plurality of terminal devices, The management system includes: the management device; a sub-management device; a first type terminal device that is the terminal device connected to either the management device or the sub-management device so as to be able to communicate with the management device; a second type terminal device that is the terminal device that is not communicably connected to the management device and the sub-management device; a storage device configured to be able to communicate with the management device, the sub-management device, and the second-type terminal device; The control unit included in the management device a first data acquisition process for acquiring main connection model name information indicating the model name of the main connection terminal device and main connection model data related to the model of the main connection terminal device from the main connection terminal device that is the first type terminal device connected to the management device; a second data acquisition process for acquiring sub-connection model name information indicating the model name of a sub-connection terminal device that is the first type terminal device connected to the sub-management device and second model name information indicating the model name of the second type terminal device, and acquiring from the storage device sub-connection model data related to a model of the sub-connection terminal device that is different from the model indicated by the main connection model name information acquired in the first data acquisition process, among the sub-connection terminal devices, and second model data related to a model of the second type terminal device that is different from the model indicated by the main connection model name information acquired in the first data acquisition process; a management device configured to execute the

4. A management method used in a management device in a management system that manages a plurality of terminal devices, comprising: The management system includes: the management device; a sub-management device; a first type terminal device that is the terminal device connected to either the management device or the sub-management device so as to be able to communicate with the management device; a second type terminal device that is the terminal device that is not communicably connected to the management device and the sub-management device; a storage device configured to be able to communicate with the management device, the sub-management device, and the second-type terminal device; The management method includes: a first data acquisition step of acquiring main connection model name information indicating the model name of the main connection terminal device and main connection model data related to the model of the main connection terminal device from the main connection terminal device which is the first type terminal device connected to the management device; a second data acquisition step of acquiring sub-connection model name information indicating the model name of a sub-connection terminal device that is the first type terminal device connected to the sub-management device and second model name information indicating the model name of the second type terminal device, and acquiring from the storage device sub-connection model data related to a model of the sub-connection terminal device that is different from the model indicated by the main connection model name information acquired in the first data acquisition step, and second model data related to a model of the second type terminal device that is different from the model indicated by the main connection model name information acquired in the first data acquisition step; A management method comprising:

5. A management system for managing a plurality of terminal devices, The management system includes: A management device; a sub-management device; a first type terminal device that is the terminal device connected to either the management device or the sub-management device so as to be able to communicate with the management device; a second type terminal device that is the terminal device that is not communicably connected to the management device and the sub-management device; a storage device configured to be able to communicate with the management device, the sub-management device, and the second-type terminal device; The management device a first data acquisition process for acquiring main connection model name information indicating the model name of the main connection terminal device and main connection model data related to the model of the main connection terminal device from the main connection terminal device that is the first type terminal device connected to the management device; a second data acquisition process for acquiring sub-connection model name information indicating the model name of a sub-connection terminal device that is the first type terminal device connected to the sub-management device and second model name information indicating the model name of the second type terminal device, and acquiring from the storage device sub-connection model data related to a model of the sub-connection terminal device that is different from the model indicated by the main connection model name information acquired in the first data acquisition process, among the sub-connection terminal devices, and second model data related to a model of the second type terminal device that is different from the model indicated by the main connection model name information acquired in the first data acquisition process; configured to run the sub-management device acquires the sub-connection model data from the sub-connection terminal device and uploads the acquired sub-connection model data to the storage device; The second type terminal device is a management system that uploads the second model data to the storage device.

6. 6. The management system according to claim 5, A management system in which the sub-management device uploads the sub-connection model data only when the sub-management device is able to acquire the sub-connection model data from the sub-connection terminal device.

7. 7. The management system according to claim 5 or 6, the sub-management device uploads the sub-connection model data to the storage device in association with first model name information indicating the model name of the sub-connection terminal device; The management system uploads the second model data to the storage device in association with second model name information indicating the model name of the second type terminal device.

Images