JP7764734B2 - Management system, device, management method and program - Google Patents

Description

This disclosure relates to technology for managing terminal devices.

Patent Document 1 describes a management system in which a management device manages image forming devices via a server.

Japanese Patent Application Laid-Open No. 2019-148957

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 terminal devices via a server in order to send and receive various data between the management device and terminal devices.

The purpose of this disclosure is to improve the efficiency of data transmission in management systems.

One aspect of the present disclosure is a management system including a management device, a device, and a storage device configured to be able to communicate with the management device and the device.
The management device is configured to execute a task execution instruction process that uploads, to the storage device, a task execution instruction that includes task content information indicating the content of a first task and task presence/absence information indicating whether or not a second task is to be executed successively after the first task has been executed.

The device is configured to execute a continuity determination process, a first period setting process, and a second period setting process.
The continuity determination process determines whether or not a second task exists based on task presence/absence information when a task execution instruction corresponding to a first task is obtained from a storage device.

The first period setting process sets the search period for searching for a task execution instruction to the first search period when the continuity determination process determines that the second task does not exist.
The second period setting process sets the search period to a second search period that is shorter than the first search period when the continuity determination process determines that the second task exists.

The management system of the present disclosure, configured in this manner, can prevent a situation in which, when an instruction to execute a second task has not been uploaded to the storage device at the time execution of a first task is completed and the instruction to execute the second task is subsequently uploaded to the storage device, the instruction to execute the second task is not transmitted to the device for a long period of time, even though the instruction has already been uploaded to the storage device, thereby making data transmission more efficient.

Another aspect of the present disclosure is a management device in a management system in which the management device and devices are configured to be able to communicate with a storage device, and the control unit of the management device is configured to execute task execution instruction processing.

The management device of the present disclosure is a device included in the management system of the present disclosure, and can obtain the same effects as the management system of the present disclosure.
Yet another aspect of the present disclosure is a device of a management system in which a management apparatus and a device are configured to be able to communicate with a storage device, and a control unit of the device is configured to execute a continuity determination process, a first period setting process, and a second period setting process.

The device of the present disclosure is an apparatus included in the management system of the present disclosure, and can obtain the same effects as the management system of the present disclosure.
Yet another aspect of the present disclosure is a management method executed in a management system in which a management device and a device are configured to be able to communicate with a storage device, and includes a task execution instruction step, a continuity judgment step, a first period setting step, and a second period setting step.

The management method of the present disclosure is a method executed by the management system of the present disclosure, and by executing this method, it is possible to obtain the same effects as the management system of the present disclosure.
Yet another aspect of the present disclosure is a program configured to cause a control unit included in a management device of a management system configured so that the management device and a device can communicate with a storage device to execute a task execution instruction process.

The program of the present disclosure is a program executed by the management system of the present disclosure, and by executing the program, it is possible to obtain the same effects as the management system of the present disclosure.
Yet another aspect of the present disclosure is a program configured to cause a control unit provided in a device of a management system in which the management device and the device are configured to be able to communicate with a storage device to execute a continuity determination process, a first period setting process, and a second period setting process.

The program disclosed herein is a program executed by the management system disclosed herein, and by executing this program, the same effects as those of the management system disclosed herein can be obtained.

FIG. 2 is a block diagram showing the configuration of a management system. FIG. 2 is a block diagram showing the configurations of a master, a client, and a first-type terminal device. FIG. 2 is a block diagram showing the configuration of a second type terminal device and a cloud server. FIG. 10 is an explanatory diagram illustrating an example of a management sequence by the management system. FIG. 10 is an explanatory diagram illustrating an example of a schedule task table. FIG. 10 is an explanatory diagram illustrating an example of an instant task table. 10 is a flowchart showing a task registration process. FIG. 10 is a diagram illustrating the configuration of an instant task entity of a continuous task. 10 is a flowchart showing a task execution process. FIG. 10 is a sequence diagram showing the first half of the operation related to the execution of successive tasks. FIG. 10 is a sequence diagram showing the latter half of the operation related to the execution of successive tasks.

Hereinafter, embodiments of the present disclosure will be described with reference to the drawings.
(1) Overall Configuration 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.

As shown in FIG. 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.

Client 3 is configured to be able to communicate with terminal device 4 installed at a second location via a local area network. Client 3 is further configured to be able to communicate with cloud server 6 via a wide area network. Terminal device 5 installed at a third location is configured to be able to communicate with cloud server 6 via a wide area network.

The local area network may include, for example, at least one of a wireless LAN and a wired LAN. The wide area network may include, for example, the Internet. A local area network may be constructed 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.

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

A first-type terminal device 4 installed at the second location is managed by the master 2 via the client 3 and cloud server 6. A second-type terminal device 5 installed at the third location is managed by the master 2 via the cloud server 6, not via the client 3.

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 for 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 located away from the first location.

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

(2) Device Configuration As shown in Fig. 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.

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 can be understood to be implemented by processing executed by the CPU 21 in accordance with the computer program.

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

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

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.

The storage unit 35 stores a sub-management program 35a. The sub-management program 35a is a computer program that causes the CPU 41 to implement functions related to the management functions of the master 2 that should be implemented by the client 3. The processing mainly performed by the control unit 31 described below can be understood to be implemented by processing executed by the CPU 41 in accordance with the computer program.

The communication unit 32 is connected to the 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, an LCD display, and is configured to display various screens for the user operating the client 3. The input unit 34 has one or more input devices for inputting operation signals from the user operating the client 3. The control unit 31 operates in accordance with the operation signals input through the input unit 34.

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.

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

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

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

The printing unit 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 colorant 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 cloud server 6 using a method described below. The reading unit 56 is configured to read a reading target such as a printed material under the control of the control unit 51.

As shown in FIG. 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.

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

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

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 that local area network. The display unit 73 includes, for example, an LCD display. The input unit 74 has one or more input devices for inputting operation signals from the user.

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 colorant 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 using a method described below. The reading unit 76 is configured to read a reading target such as a printed material under the control of the control unit 71.

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 102.
The CPU 101 as a processor executes processes in accordance with a computer program stored in the memory 102. The processes executed by the CPU 101 include processes for causing the cloud server 6 to function as cloud storage. The processes mainly performed by the control unit 91 described below may be understood to be realized by the processes executed by the CPU 101 in accordance with the computer program.

The above cloud storage includes table storage and object storage. By executing the above processing by the control unit 91, the first storage 93 functions as table storage, and the second storage 94 functions as object storage.

The exemplary first storage 93 functions as a NoSQL data store and is configured to store tables made up of a collection of schema-less entities. Each entity in a table is made up of a set of properties.

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

Microsoft's Azure is a well-known cloud service that provides the table storage and object storage described above. Cloud server 6 can operate in a similar manner to such a cloud service. Azure is a registered trademark.

(3) Outline of Sequence Next, an outline of the operation sequence relating to management will be explained.
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.

As shown in FIG. 4, Master 2 first performs a process to set a cloud profile in S01. Master 2 sets the cloud profile in accordance with setting operations performed by the primary administrator via the input unit 14, for example.

Setting a cloud profile includes setting cloud parameters. The cloud parameters include initial setting parameters. As described below, 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 on the cloud server 6. This polling operation periodically checks for the presence or absence of instant tasks, described below. The information update operation is an operation specified by a schedule task, described below.

The initial setting parameters include, for example, the period of the polling operation (hereinafter referred to as the polling period) and the period of the information update operation (hereinafter referred to as the information update period). Two types of polling periods are set for the client 3 and the second-type terminal device 5: a first search period and a second search period, which will be described later. Multiple types of information update periods are set depending on the type of information to be updated.

The cloud parameters may further include a schedule task template. The schedule task template specifies the processing content of the schedule task to be executed by each terminal device 4, 5. The information update period corresponds to the execution period of one or more processes in the schedule task.

The schedule task template and 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 that is different from the first storage area.

Configuring a cloud profile also includes configuring a shared access signature (SAS) for using cloud services. SAS stands for Shared Access Signature.

The SAS is configured separately for each of the first storage 93 and the second storage 94 (i.e., the table storage and the object storage). When configuring the cloud profile on Master 2, the primary administrator configures the SAS configured for each of the first storage 93 and the second storage 94 as part of the cloud profile so that Master 2 can access the first storage 93 and the second storage 94.

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

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

As shown in S04, Master 2 exports at least a portion of the cloud profile from Master 2 as a client profile (i.e., data to be read by 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 Master 2 is provided to Client 3. The client profile may be provided to Client 3 by any method. For example, the client profile may be sent from Master 2 to Client 3 by email or other method.

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 by the master 2. In other words, 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.

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 configures the client 3 to be able 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 issuing task execution instructions from the master 2 to the first-type terminal device 4 and transmitting log information and status information from the first-type terminal device 4 to the master 2, and is a function that relays information between the master 2 and the first-type terminal device 4.

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.

The control unit 71 of the type 2 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 references the cloud parameters written by the master 2. The cloud connector obtains these cloud parameters and sets them in its own device.

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. 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.

Once the type 2 terminal device 5 (i.e., the cloud connector) has completed the initial configuration (i.e., the processes of S07 and S08), including the configuration of the cloud parameters and SAS, it periodically executes the schedule task according to the set information update cycle, as shown in S09.

Once the initial settings (i.e., the processes of S05 and S06) including the setting of the above cloud parameters and SAS are completed, the client 3 executes a schedule task that periodically updates the information stored in the first storage 93 of the cloud server 6 according to the set information update cycle, as shown in S10.

A scheduling task using a cloud connector begins 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 specified information that indicates the type 2 terminal device 5 in which the cloud connector is implemented.

The schedule task by the client 3 begins by registering the device information of the type 1 terminal device 4 whose corresponding device information is not registered in the first storage 93, if any of the type 1 terminal devices 4 to be managed are present. The device information of the type 1 terminal device 4 is predetermined information that identifies the type 1 terminal device 4 in question.

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. Each 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.

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.

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.

If the entity is related to "log", the property "PartitionKey" stores the string "log" 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.

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

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 status information for the terminal device corresponding to the device ID stored in the property "DeviceId" in the property "NotifyParameter." When the corresponding terminal device is 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.

If the entity is related to "registration," the property "PartitionKey" stores "registration," a string indicating "registration." Entities related to "registration" store device information for 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.

The property "DeviceId" stores the device ID of the device that updated the entity.
The property "NotifyParameter" stores a character string written in JSON format to indicate the instruction content of the schedule task.

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 notations "x.x.x.x.x..." and "y.y.y.y.y..." shown in task instruction T1 in Figure 5 are illustrative abstract representations of object identifiers. MIB stands for Management Information Base.

The instruction on the second line of task instruction T1 is "x. x. x. x. ...": "%MIB(x.x.x.x. ...)%". The "x.x.x.x. ..." above is the MIB object ID.

The instruction on the third line of task instruction T1 is "y. y. y. y. ...": "%MIB(y.y.y.y....)%". The "y.y.y.y..." above is the MIB object ID.

If the above "x.x.x.x...." is written as Oid1, the instruction on the second line is "Oid1: %MIB(Oid1)%". "%MIB(Oid1)%" is an instruction to obtain the value corresponding to Oid1, which is the object ID, and overwrite "%MIB(Oid1)%" with the obtained value. Therefore, if the value corresponding to Oid1 is "XXXXXX", then in the registered data, "Oid1: %MIB(Oid1)%" will be rewritten to "Oid1: XXXXXX".

Similarly, the instruction on the third line is "Oid2": "%MIB(Oid2)%" when the object ID "y.y.y.y..." is written as Oid2.
The descriptions "xxxxxx...." and "yyyyyy...." shown in the task result T2 in FIG. 5 are illustrative abstract representations of the update results.

For each of the "Log" and "Registration" entities, the string in the "NotifyParameter" property is rewritten in the same way as for the "Status" entity.

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.

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 that entity stores the string "client", which indicates that it is a client 3. When an entity is updated by a cloud connector, the property "Source" of that entity stores the string "device", which indicates that it is a type 2 terminal device 5.

The entity of the cloud connector of a second-type terminal device 5 is updated by the cloud connector. The entity of a first-type terminal device 4 is updated by a client 3 connected to the same local area network as the first-type terminal device 4. In other words, 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 for the client 3 that manages and relays the first-type terminal device 4 may be written as part of the device information in the registration entity of the first-type terminal device 4.

The client 3 communicates with each type 1 terminal device 4 that is a management relay target within the same local area network, and obtains the information necessary to update device information from each type 1 terminal device 4. Based on the obtained information, the client 3 can update the registration entity of the corresponding type 1 terminal device 4.

The client 3 also periodically communicates with each type 1 terminal device 4 that is the target of management relay via the local area network to obtain corresponding log information and status information. Based on the obtained log information and status information, the client 3 can update the log entities and status entities of the corresponding type 1 terminal device 4.

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.

The master 2 also functions as a client 3. In other words, the master 2 can be understood to function as a client 3 with respect to the first-type terminal device 4 at the first base. Specifically, three entities related to "log," "status," and "registration" are generated in the schedule task table in the first storage 93 of the cloud server 6, corresponding to each of the first-type terminal devices 4 at the first base (hereinafter referred to as master-subordinate terminal devices). Like the client 3, the master 2 can obtain 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.

Furthermore, as shown in S11 of FIG. 4, the master 2 periodically accesses the first storage 93 of the cloud server 6 and references the log entities, status entities, and registration entities of each of the terminal devices 4 and 5. Based on these references, the master 2 can execute processing to store the log information, status information, and device information of each of the terminal devices 4 and 5 in the storage unit 15.

Furthermore, the master 2 can display a list of the registered terminal devices 4 and 5 on the screen of the display unit 13, as well as log information and status information for the terminal devices 4 and 5, in accordance with operation signals output from the input unit 14 by user operation. In this way, the management system 1 is configured to enable remote monitoring of the status of terminal devices 4 and 5 used at multiple locations from a single location where the master 2 is installed.

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

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

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", "SequentialTaskId", and "NextSequentialTaskId".

The property "PartitionKey" stores "instanttask", which is a character string indicating that it is an instant task.
The property "RowKey" stores a transaction ID for identifying each instant task.

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 character string written in JSON format to indicate the instruction content of the instant task.

The property "Progress" stores a character string indicating the progress of the instruction.
The property "SequentialTaskId" stores a sequential task ID. The sequential task ID indicates that the task is the first task in the sequential tasks, and specifies the task in the sequential tasks that are the second or later tasks.

The property "NextSequentialTaskId" stores the next sequential task ID. The next sequential task ID specifies the task to be executed next in a series of tasks.

If 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, the property "NotifyParameter" describes information indicating the storage destination of the file (e.g., a URL). For example, if the instant task is a firmware update for the terminal devices 4 and 5, the master 2 stores the update file required for the firmware update in the second storage 94. In this case, the property "NotifyParameter" may describe, for example, the storage destination URL of the firmware update file.

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 instant tasks that target itself. In other words, the cloud connector determines whether a new entity for an instant task that should be executed by itself has been registered in the instant task table.

When a new entity is registered, the cloud connector notifies Master 2 that it has received an instant task request by rewriting the string for the "Progress" property in the corresponding instant task entity from "request" to "processing."

As shown in S18, the master 2 that has registered the instant task entity checks the status of the instant task corresponding to that 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 the set polling interval. Through this periodic reference, the master 2 can confirm that the instant task request has been received based on the updated value of the progress status property.

When executing an instant task, the cloud connector of the second-type terminal device 5 references the "NotifyParameter" property in the instant task entity. If the 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., URL) described in the "NotifyParameter" property, as shown in S16.

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 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.

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 instant tasks that target the management relay target. That is, the client 3 determines whether a new entity for the instant task to be executed by the type 1 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 type 1 terminal devices 4 that are the management relay target and that are set as instant task execution targets in the instant task table (that is, one or more type 1 terminal devices 4 that correspond to the device ID stored in the property "DeviceId") will be referred to as an instant task execution target.

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 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. Then, based on the identified processing content, the client 3 retrieves data files necessary for executing the instant task from the second storage 94 as necessary, as shown in S20.

Then, 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 results of the instant task from the instant task execution targets.

When the execution of instant tasks for all instant task execution targets is completed, the client 3 updates the instant task entity for the corresponding instant task execution target, as shown in S22. Specifically, the client 3 rewrites the string for 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.

To check the status, as shown in S23, Master 2 references the instant task entity in the instant task table in the first storage 93 and finds that the string for the property "Progress" has been rewritten to "done." This confirms that the instant task has been completed, and writes the processing result to the memory unit 15.

The master 2 can also 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, it 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., a firmware update file) provided for the instant task from the second storage 94 as shown in S26.

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 a single 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.

(4) Processing Related to Continuous Tasks Next, a description will be given of the procedure of task registration processing executed by the control unit 11 of the master 2. The task registration processing is processing that is repeatedly executed while the master 2 is in operation.

When the task registration process is executed, the CPU 21 of the control unit 11 first determines in S110 whether there is a task for which an execution request has been issued but which has not been registered on the cloud server 6 (hereinafter referred to as an execution waiting task), as shown in FIG. 7.

If there are no tasks waiting for execution, the CPU 21 ends the task registration process. On the other hand, if there are tasks waiting for execution, the CPU 21 acquires, at S120, the task for which an execution request was issued earliest from among the tasks waiting for execution.

Then, in S130, the CPU 21 generates an instant task entity that requests the execution of the task acquired in S120.
Here, a specific example of instant task entity generation in the case where there are four tasks waiting to be executed as shown in FIG. 8 will be described.

Of the four tasks waiting for execution shown in Figure 8, the task for which an execution request was issued first is the first task in the series of consecutive tasks for the terminal device whose device ID is set to "PrinterA," as shown by task TS1.

Of the four tasks waiting for execution, the task for which an execution request was issued second earliest is the second task in the continuous task list for the terminal device whose device ID is set to "PrinterA," as shown by task TS2.

Of the four tasks waiting for execution, the task for which an execution request was issued third earliest is the first task in the series of consecutive tasks for the terminal device whose device ID is set to "PrinterB," as shown by task TS3.

Of the four tasks waiting for execution, the task for which an execution request was issued last is the second task in the series of consecutive tasks for the terminal device whose device ID is set to "PrinterB," as shown by task TS4.

In the instant task entity for task TS1, the transaction ID is set to "001", the device ID is set to "PrinterA", the consecutive task ID is set to "0", and the next consecutive task ID is set to "1".

In the instant task entity for task TS2, the transaction ID is set to "002", the device ID is set to "PrinterA", the consecutive task ID is set to "1", and the next consecutive task ID is set to "NULL".

In the instant task entity for task TS3, the transaction ID is set to "003", the device ID is set to "PrinterB", the consecutive task ID is set to "0", and the next consecutive task ID is set to "2".

In the instant task entity for task TS4, the transaction ID is set to "004", the device ID is set to "PrinterB", the consecutive task ID is set to "2", and the next consecutive task ID is set to "NULL".

Note that the client 3 can independently search for the instant task entity of a terminal device whose device ID is set to "PrinterA" and the instant task entity of a terminal device whose device ID is set to "PrinterB." This allows the client 3 to prevent a situation in which a terminal device (e.g., "PrinterA") is waiting to acquire the next task, preventing the execution of a task on another terminal device (e.g., "PrinterB").

When the processing of S130 is completed, the CPU 21 registers the instant task entity generated in S130 in the first storage 93 in S140, as shown in FIG. 7, and terminates the task registration processing.

Next, we will explain the procedure for the task execution process executed by the control unit 31 of the client 3 and the control unit 71 of the second-type terminal device 5. The task execution process is a process that is repeatedly executed while the client 3 and the second-type terminal device 5 are operating.

When the task execution process is executed, the CPU 41 of the control unit 31 and the CPU 81 of the control unit 71 first determine in S310 whether the search timing has arrived, as shown in FIG. 9. The search timing is the timing when the polling period set for each of the client 3 and the second-type terminal device 5 has elapsed.

If the search timing has not arrived, the CPU 41, 81 terminates the task execution process. On the other hand, if the search timing has arrived, the CPU 41, 81 performs a search for instant tasks in S320.

Specifically, the CPU 41 accesses the first storage 93 of the cloud server 6 to search for an instant task entity that is the target of a request from a first type terminal device 4 connected to the client 3 via a local area network. If the requested instant task entity exists, the CPU 41 then obtains the earliest registered instant task entity from among the instant task entities that have not yet been obtained.

The CPU 81 also accesses the first storage 93 of the cloud server 6 to search for instant task entities that are the target of a request from the second-type terminal device 5. If the requested instant task entity exists, the CPU 81 then obtains the earliest registered instant task entity from among the unobtained instant task entities.

When the processing of S320 is completed, the CPU 41, 81 determines in S330 whether or not an instant task entity was acquired in S320. If an instant task entity was acquired, the CPU 41, 81 executes the task requested in the acquired instant task entity in S340.

Next, at S350, the CPU 41, 81 determines whether the next task to be executed (hereinafter referred to as the next task) has been specified by referencing the property "NextSequentialTaskId" of the acquired instant task entity. Specifically, the CPU 41, 81 determines that the next task has been specified if a number is stored in the property "NextSequentialTaskId." On the other hand, the CPU 41, 81 determines that the next task has not been specified if a number is not stored in the property "NextSequentialTaskId."

If the next task is specified, the CPU 41, 81 sets the polling period to the second search period set in advance in S360, and ends the task execution process.
If an instant task entity has not been acquired in S330, the CPU 41, 81 proceeds to S370.

If the next task is not specified in S350, the CPU 41, 81 proceeds to S370.
Then, in S370, the CPU 41, 81 determines whether the polling period is set to the second search period. If the polling period is not set to the second search period, the CPU 41, 81 ends the task execution process.

On the other hand, if the polling period is set to the second search period, the CPU 41, 81 determines in S380 whether the time during which the next task could not be acquired (hereinafter referred to as the task unacquired time) has exceeded the preset switching time.

Here, if the task unacquired time does not exceed the switching time, the CPU 41, 81 terminates the task execution process. On the other hand, if the task unacquired time exceeds the switching time, the CPU 41, 81 sets the polling period to the first search period, which is set to be longer than the second search period, in S390, and terminates the task execution process.

When the polling period is set to the first search period, the client 3 and the second-type terminal device 5 search for the first task (i.e., the instant task entity in which "0" is stored in the property "SequentialTaskId").

Furthermore, when the polling period is set to the second search period, the client 3 and the second type terminal device 5 search for an instant task entity whose property "DeviceId" stores the same device ID as the most recently acquired instant task entity, and whose property "SequentialTaskId" stores the same number as the next sequential task ID of the most recently acquired instant task entity.

Next, we will provide an overview of the operational sequence for executing consecutive tasks. In this explanation of the operational sequence for executing consecutive tasks, the client 3 or the second-type terminal device 5 will be referred to as a device.

As shown in FIG. 10, the device determines that the search timing has arrived when the first search cycle has elapsed, as shown in S41. Hereinafter, the search timing that arrives when the first search cycle has elapsed will be referred to as the first search timing.

Then, as shown in S42, the device accesses the first storage 93 of the cloud server 6 and searches for an instant task entity. If the device is a second-type terminal device 5, the second-type terminal device 5 searches for an instant task entity that targets itself. If the device is a client 3, it searches for an instant task entity that targets a management relay target. Hereinafter, the search performed when the first search timing arrives will be referred to as the first search.

Then, as shown in S43, the device cannot acquire the instant task entity of the top task through the first search in S42.
Next, as shown in S44, master 2 registers the instant task entity of the leading task in the first storage 93 of the cloud server 6. Furthermore, as shown in S45, master 2 determines that the confirmation timing has arrived when the polling period set in master 2 has elapsed.

Then, as shown in S46, the master 2 accesses the first storage 93 of the cloud server 6 and checks the result of the leading task.
Then, as shown in S47, master 2 confirms that the leading task has not yet been executed.

The device also determines that the first search timing has arrived, as shown in S48, and executes the first search, as shown in S49. As a result, the device obtains the instant task entity of the top task from the first storage 93 of the cloud server 6, as shown in S50, and executes the top task, as shown in S51.

When the top task is completed, the device notifies the user that execution of the top task has been completed by rewriting the string in the "Progress" property of the instant task entity of the top task registered in the first storage 93 of the cloud server 6, as shown in S52.

Furthermore, when the second search period has elapsed, the device determines that the search timing has arrived, and, as shown in S53, accesses the first storage 93 of the cloud server 6 and searches for the instant task entity of the task to be executed next after the first task (hereinafter referred to as the next task). Hereinafter, the search timing that arrives when the second search period has elapsed is referred to as the second search timing. A search performed when the second search timing arrives is referred to as the second search.

Then, as shown in S54, the device cannot obtain the instant task entity of the next task through the second search in S53.
Next, as shown in S55, the master 2 determines that the confirmation timing has arrived when the polling period set in the master 2 has elapsed.

Then, as shown in S56, the master 2 accesses the first storage 93 of the cloud server 6 and checks the result of the leading task.
Then, as shown in S57, master 2 confirms that execution of the top task has been completed. As a result, as shown in S58, master 2 deletes the instant task entity of the top task from the first storage 93 of the cloud server 6. Furthermore, as shown in S59, master 2 registers the instant task entity of the next task in the first storage 93 of the cloud server 6.

As shown in FIG. 11 , when the second search period has elapsed, the device determines in S60 that the second search timing has arrived. The device then performs a second search in S61. As a result, the device obtains the instant task entity for the next task from the first storage 93 of the cloud server 6 in S62, and executes the next task in S63.

When the next task is completed, the device notifies the user that execution of the next task has been completed by rewriting the string in the "Progress" property of the instant task entity for the next task registered in the first storage 93 of the cloud server 6, as shown in S64.

Furthermore, when the first search period has elapsed, the device determines that the first search timing has arrived, and as shown in S65, accesses the first storage 93 of the cloud server 6 and searches for the instant task entity of the top task.

Then, as shown in S66, the device cannot acquire the instant task entity of the top task through the first search in S65.
Next, as shown in S67, the master 2 determines that the confirmation timing has arrived when the polling period set in the master 2 has elapsed.

Then, as shown in S68, the master 2 accesses the first storage 93 of the cloud server 6 and checks the result of the next task.
Then, as shown in S69, master 2 confirms that the execution of the next task has been completed, and then, as shown in S70, master 2 deletes the instant task entity of the next task from the first storage 93 of the cloud server 6.

Furthermore, as shown in S71, the device determines that the first search timing has arrived when the first search period has elapsed, and as shown in S72, it accesses the first storage 93 of the cloud server 6 and searches for the instant task entity of the top task.

Then, as shown in S73, the device cannot acquire the instant task entity of the top task through the first search in S72.
(5) Effects The management system 1 configured in this manner includes the master 2, the client 3, the second-type terminal device 5 (hereinafter, referred to as device), and the cloud server 6 configured to be able to communicate with the master 2 and the device.

Master 2 is configured to execute a task execution instruction process. The task execution instruction process uploads to cloud server 6 an instant task entity that includes task content information indicating the content of a first task and a next successive task ID indicating whether or not a second task is to be executed immediately after the first task after it has been executed.

The device is configured to execute a continuity determination process, a first period setting process, and a second period setting process.
In the continuity determination process, when an instant task entity corresponding to a first task is acquired from the cloud server 6, it is determined whether or not a second task exists based on the next continuity task ID.

If the continuity determination process determines that the second task does not exist, the first period setting process sets the search period for searching for instant task entities to the first search period.

The second period setting process sets the search period to a second search period that is shorter than the first search period when the continuity determination process determines that the second task exists.
In such a management system 1, in a case where the instant task entity of the second task has not been uploaded to the cloud server 6 at the time when the execution of the first task is completed and the instant task entity of the second task is subsequently uploaded to the cloud server 6, the management system 1 can prevent a situation from occurring in which the instant task entity of the second task has already been uploaded to the cloud server 6 but this instant task entity is not transmitted to the device for a long period of time, thereby making data transmission more efficient.

Note that if the device's memory does not have enough capacity to simultaneously acquire and store the instant task entities of the first task and the second task from the cloud server 6, it is necessary to acquire the first task, execute the first task, and then acquire the second task. This makes it more likely that, as described above, even if the instant task entity of the second task has already been uploaded to the cloud server 6, the instant task entity will not be transmitted to the device for a long period of time. For this reason, improving the efficiency of data transmission by making the first search period and second search period configurable as described above is effective, particularly when the device has a small memory capacity.

Master 2 is also configured to execute a search cycle instruction process. The search cycle instruction process uploads first search cycle information indicating the first search cycle and second search cycle information indicating the second search cycle to the cloud server 6. In such a management system 1, the main administrator can change the first and second search cycles as needed via master 2.

The first period setting process sets the first search period when the continuity determination process determines that the second task does not exist, and further when the period during which the second task could not be acquired exceeds a preset switching time. In such a management system 1, the second search period does not switch to the first search period until the switching time has elapsed. As a result, the management system 1 can prevent frequent switching from the second search period to the first search period, further improving the efficiency of data transmission.

An instant task entity includes a consecutive task ID that indicates whether the task is the first task among multiple tasks to be executed consecutively. This makes it easy for the management system 1 to search for the first task.

In the embodiment described above, the master 2 corresponds to the management device, the cloud server 6 corresponds to the storage device, and the main management program 15a, sub-management program 35a, and communication program 82a correspond to programs.

Furthermore, S110 to S140 correspond to the task execution instruction process and task execution instruction step, S350 corresponds to the continuity determination process and continuity determination step, S380 and S390 correspond to the first period setting process and first period setting step, and S360 corresponds to the second period setting process and second period setting step.

Furthermore, S02 corresponds to the search cycle instruction process, the next consecutive task ID corresponds to task presence/absence information, the consecutive task ID corresponds to the first task information, the second type terminal device 5 corresponds to the image forming device, and the client 3 corresponds to the information processing device.

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.
[Modification 1]
For example, in the above embodiment, the first search period and the second search period are transmitted to the second type terminal device 5 by uploading the cloud parameters to the first storage 93 of the cloud server 6. However, it is also possible to store the second search period information in the instant task entity of the leading task that is executed first among a plurality of tasks to be executed consecutively, and store the first search period information in the instant task entity of the final task that is executed last.

[Modification 2]
In the above embodiment, the first search period and the second search period are set in the initial setting of the master 2. However, the first search period and the second search period may be set in advance. This eliminates the need for the master 2 to upload the first and second search period information to the cloud server 6 and the need for the clients 3 and the second-type terminal devices 5 to acquire the first and second search period information from the cloud server 6, thereby reducing the communication load on the management system 1.

Multiple functions possessed by one component in the above embodiments may be realized by multiple components, or one function possessed by one component may be realized by multiple components. Furthermore, multiple functions possessed by multiple components may be realized by one component, or one function realized by multiple components may be realized by one component. Furthermore, part of the configuration of the above embodiments may be omitted. Furthermore, at least part of the configuration of the above embodiments may be added to or substituted for the configuration of another of the above embodiments.

In addition to the master 2 described above, the present disclosure can also be realized in various forms, such as a system that includes 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.

1...Management system, 2...Master, 3...Client, 5...Type 2 terminal device, 6...Cloud server, 11, 31, 71...Control unit, 15a...Main management program, 35a...Sub-management program, 82a...Communication program

Claims (9)

A management device;
a device;
a storage device configured to be able to communicate with the management device and the device;
The management device
configured to execute a task execution instruction process for uploading to the storage device a task execution instruction including task content information indicating the content of a first task and task presence/absence information indicating the presence or absence of a second task to be executed successively after the first task has been executed,
The device comprises:
a continuity determination process for determining whether the second task exists based on the task presence/absence information when the task execution instruction corresponding to the first task is obtained from the storage device;
a first period setting process for setting a search period for searching for the task execution instruction to a first search period when the continuity determination process determines that the second task does not exist;
and when it is determined by the continuity determination process that the second task exists, executing a second period setting process to set the search period to a second search period that is shorter than the first search period. The management system according to claim 1,
The management device
a management system configured to execute a search cycle instruction process for uploading first search cycle information indicating the first search cycle and second search cycle information indicating the second search cycle to the storage device; 3. The management system according to claim 1 or 2,
A management system in which the first search period and the second search period are preset. The management system according to any one of claims 1 to 3,
The first period setting process is a management system that sets the first search period when the continuity determination process determines that the second task does not exist, and further when the period during which the second task could not be acquired exceeds a predetermined switching time. The management system according to any one of claims 1 to 4,
The task execution instruction includes leading task information indicating whether the task is the leading task among a plurality of tasks to be executed successively. The management system according to any one of claims 1 to 5,
The device comprises:
Is it an image forming device?
A management system is an information processing apparatus communicably connected to the plurality of image forming apparatuses. A management system in which a management apparatus and a device are configured to be able to communicate with a storage device,
The control unit of the device
a continuity determination process for determining whether or not the second task exists based on task presence/absence information when a task execution instruction including task content information indicating the content of a first task and task presence/absence information indicating the presence or absence of a second task to be executed successively after the first task is executed is acquired from the storage device;
a first period setting process for setting a search period for searching for the task execution instruction to a first search period when the continuity determination process determines that the second task does not exist;
and a second period setting process for setting the search period to a second search period that is shorter than the first search period when the continuity determination process determines that the second task exists. A management method executed in a management system in which a management apparatus and a device are configured to be able to communicate with a storage device, comprising:
a task execution instruction step in which the management device uploads to the storage device a task execution instruction including task content information indicating the content of a first task and task presence/absence information indicating the presence or absence of a second task to be executed successively after the first task has been executed;
a continuity determination step of determining whether the second task exists based on the task presence/absence information when the device acquires the task execution instruction corresponding to the first task from the storage device;
a first cycle setting step of setting a search cycle for searching for the task execution instruction to a first search cycle when the device determines in the continuity determining step that the second task does not exist;
a second period setting step of setting the search period to a second search period that is shorter than the first search period when the device determines in the continuity determining step that the second task exists. A control unit provided in a device of a management system configured so that a management device and a device can communicate with a storage device,
a continuity determination process for determining whether or not the second task exists based on task presence/absence information when a task execution instruction including task content information indicating the content of a first task and task presence/absence information indicating the presence or absence of a second task to be executed successively after the first task is executed is acquired from the storage device;
a first period setting process for setting a search period for searching for task execution instructions to a first search period when the continuity determination process determines that the second task does not exist;
and a second period setting process for setting the search period to a second search period that is shorter than the first search period when the continuity determination process determines that the second task exists.