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

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

The present disclosure relates to technology for managing terminal devices.

Japanese Unexamined Patent Application Publication No. 2002-200001 describes a management system in which a management apparatus manages image forming apparatuses via a server.

JP 2019-148957 A

In a management system in which terminal devices such as image forming apparatuses are managed by a management device, data transmission between the management device and the terminal devices is performed via a server in order to transmit and receive various data between the management device and the terminal devices. efficiency.

An object of the present disclosure is to streamline data transmission in a management system.

One aspect of the present disclosure is a management program used in a management system that manages a plurality of terminal devices, the management program causing a control unit included in the management device to execute a first data acquisition process and a second data acquisition process. is configured to

The management system includes a management device, a sub-management device, a type 1 terminal device, a type 2 terminal device, and a storage device. A type 1 terminal device is a terminal device that is communicably connected to either one of the management device and the sub management device. A type 2 terminal device is a terminal device that is not communicably connected to the management device and the sub-management device. The storage device is configured to be communicable with the management device, the sub-management device and the type 2 terminal device.

The first data acquisition process acquires 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.
In the second data acquisition process, among the secondary connection terminal devices that are the first type terminal devices connected to the secondary management device, the secondary connection related to the model of the secondary connection terminal device that is different from the model corresponding to the main connection model data. Model data and second model data related to a model of a second type terminal device different from the model corresponding to the main connection model data are acquired from the storage device.

The management program of the present disclosure configured in this manner prevents the management device from acquiring model data of the same model as the terminal device connected to the management device from the storage device. Thereby, the management program of the present disclosure can streamline data transmission performed in the management system so that the management device acquires model data.

Another aspect of the present disclosure is a management device used in a management system that manages a plurality of terminal devices, wherein a control unit included in the management device executes a first data acquisition process and a second data acquisition process is configured as

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 for managing a plurality of terminal devices, comprising a first data acquisition step and a second data acquisition step.

The management method of the present disclosure is a method executed by the management program of the present disclosure, and by executing the method, the same effects as those of the management program of the present disclosure can be obtained.
Yet another aspect of the present disclosure is a management system for managing multiple terminal devices, wherein the management device is configured to perform a first data acquisition process and a second data acquisition process. 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 type 2 terminal device uploads the type 2 data to the storage device.

The management system of the present disclosure is a system controlled by the management program of the present disclosure, and can obtain the same effects as the management program of the present disclosure.

It is a block diagram which shows the structure of a management system. It is a block diagram which shows the structure of a master, a client, and a type 1 terminal device. It is a block diagram which shows the structure of a type 2 terminal device and a cloud server. FIG. 4 is an explanatory diagram showing an example of a management sequence by a management system; FIG. 4 is an explanatory diagram showing an example of a schedule task table; FIG. 4 is an explanatory diagram showing an example of an instant task table; FIG. FIG. 11 shows a terminal management window; 6 is a flowchart showing image acquisition processing; FIG. 4 is a diagram showing the configuration of a model image entity; FIG. 11 is a sequence diagram showing an operation related to acquisition of model image data;

Embodiments of the present disclosure will be described below with reference to the drawings.
(1) Overall Configuration The management system 1 of the present embodiment is configured to manage the terminal devices 4 and 5 located at multiple bases through the cloud server 6 in cooperation with the master 2 and the client 3. It is a network system.

As shown in FIG. 1, the master 2 is configured to be able to communicate with the terminal device 4 installed at the first site via the local area network. The master 2 is further configured to be able to communicate with the cloud server 6 via a wide area network.

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

Local area networks may include, for example, wireless LANs and/or wired LANs. A wide area network may include, for example, the Internet. A local area network may be constructed at the third base. 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 cloud services provided by cloud server 6 . In other words, each terminal device 4 does not have the function of communicating with the cloud server 6 . In the following, this terminal device 4 is specifically referred to as a type 1 terminal device 4 . On the other hand, the terminal device 5 is a terminal device capable of using cloud services provided by the cloud server 6 . In other words, the terminal device 5 has a function of communicating with the cloud server 6 . In the following, this terminal device 5 is particularly referred to as a type 2 terminal device 5 .

The type 1 terminal device 4 installed at the second site is managed by the master 2 via the client 3 and the cloud server 6 . The type 2 terminal device 5 installed at the third site is managed by the master 2 via the cloud server 6 without the client 3 .

The terminal devices 4 and 5 managed by the master 2 can be, for example, a group of terminal devices managed by an organization such as a company. In this case, each base can be an activity base of an organization. According to an example, the first site where master 2 resides can be an office with an administrative department of an organization. Other second and third sites may be branch offices of an organization remote from the first site.

Examples of terminal devices 4 and 5 include printers, scanners, and digital multi-function peripherals in which their functions are integrated. The master 2 and client 3 are configured by installing a dedicated computer program in, for example, a personal computer.

(2) Device configuration As shown in FIG. The control unit 11 has a CPU 21 and a memory 22 . CPU 21 as a processor executes processing according to a computer program stored in storage unit 15 . The memory 22 is used as a work memory when executing the above processes.

The storage unit 15 includes storage such as a solid state drive and a hard disk drive, and stores various computer programs and data. The storage unit 15 stores a main management program 15a. The main management program 15a is a computer program for causing the CPU 21 to implement the management functions to be implemented by the master 2 . It may be understood that the processing mainly performed by the control unit 11 described below is realized by the processing executed by the CPU 21 according to a computer program.

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

The input unit 14 includes one or more input devices, such as a keyboard and pointing device, for inputting operation signals from the user operating the master 2 . The control unit 11 operates according to operation signals input through the input unit 14 .

The client 3 includes a control section 31 , a communication section 32 , a display section 33 , an input section 34 and a storage section 35 . The control unit 31 has a CPU 41 and a memory 42 . CPU 41 as a processor executes processing according to a computer program stored in storage unit 35 .

The storage unit 35 stores a secondary management program 35a. The sub-management program 35 a is a computer program for causing the CPU 41 to implement functions related to the management functions of the master 2 to be implemented by the client 3 . It may be understood that the processing mainly performed by the control unit 31 described below is realized by the processing executed by the CPU 41 according to a computer program.

The communication unit 32 is connected to the local area network of the base where the client 3 is present, and further to the wide area network. The communication unit 32 may be connected to a 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 the user who operates the client 3 . The input unit 34 includes one or more input devices for inputting operation signals from the user who operates the client 3 . The control unit 31 operates according to operation signals input through the input unit 34 .

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

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

The CPU 61 as a processor executes processing according to a computer program stored in the memory 62, thereby controlling the overall type 1 terminal device. It may be understood that the processing mainly performed by the control unit 51 described below is realized by the processing executed by the CPU 61 according to a computer program.

The communication unit 52 is connected to the local area network of the site where the type 1 terminal device 4 exists so as to be able to communicate with the master 2 or the client 3 existing there. The display unit 53 includes, for example, a liquid crystal display, and is configured to display various screens for the user who operates the type 1 terminal device 4 . The input unit 54 includes one or more input devices, such as a touch panel on a liquid crystal display, for inputting 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 printing unit 55 include inkjet printers and laser printers. According to this embodiment, status information such as the remaining amount of coloring material and log information such as the number of prints are provided from the first type terminal device 4 to the master 2 via the client 3 and the cloud server 6 by a method described later. . The reading unit 56 is configured to be controlled by the control unit 51 to read an object to be read such as printed matter.

As shown in FIG. 3 , the type 2 terminal device 5 includes a control section 71 , a communication section 72 , a display section 73 and an input section 74 . When the type 2 terminal device 5 is a digital multifunction peripheral, the type 2 terminal device 5 can further include a printing section 75 and a reading section 76 . The type 2 terminal device 5 may have only one of the printing unit 75 and the reading unit 76 .

The control unit 71 has a CPU 81 and a memory 82 . The memory 82 can comprise non-volatile memory such as flash memory, and can store computer programs, setting data, and the like in the non-volatile memory.

A CPU 81 as a processor executes processing in accordance with a computer program stored in a memory 82 to centrally control the entire apparatus. The memory 82 stores a communication program 82a. The communication program 82 a is a program for using cloud services 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 the processing executed by the CPU 81 according to a 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 constructed at the third site, 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.

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 from the second type terminal device 5 to the master 2 through the cloud server 6 by a method described later. The reading unit 76 is configured to be controlled by the control unit 71 to read an object to be read such as printed matter.

The cloud server 6 includes a control section 91 , a communication section 92 , a first storage 93 and a second storage 94 . The control unit 91 has a CPU 101 and a memory 102 .
CPU 101 as a processor executes processing according to a computer program stored in memory 102 . The processing executed by the CPU 101 includes processing for causing the cloud server 6 to function as a cloud storage. It may be understood that the processing mainly performed by the control unit 91 described below is realized by the processing executed by the CPU 101 according to a computer program.

The cloud storage includes table storage and object storage. By the execution of the above process by the control unit 91, the first storage 93 functions as a table storage, and the second storage 94 functions as an object storage.

The exemplary first storage 93 functions as a NoSQL data store and is configured to be able to store tables whose constituent elements are groups of schema-less entities. Each entity in the table consists of a set of properties.

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

Microsoft's Azure is known as a cloud service that provides the table storage and object storage described above. Cloud server 6 may operate similarly to such cloud services. Azure is a registered trademark.

(3) Outline of Sequence Next, an outline of the operation sequence regarding management will be described.
When the main management program 15a is installed in the master 2, the control unit 11 of the master 2 executes processing according to the main management program 15a. That is, master 2 comes to have a management function.

As shown in FIG. 4, the master 2 first performs a process of setting a cloud profile in S01. The master 2 sets the cloud profile according to the setting operation performed by the main administrator through the input unit 14, for example.

Configuring cloud profiles includes setting cloud parameters. Cloud parameters include default parameters. The client 3 and the type 2 terminal device 5 perform a polling operation for the cloud server 6 and an operation for updating information held in the cloud server 6, as will be described later. This polling operation is an operation for periodically confirming the presence or absence of an instant task, which will be described later. The information update operation is an operation defined by a schedule task, which will be described later.

The initial setting parameters include, for example, a polling operation period (hereinafter referred to as a polling period) and an information update operation period (hereinafter referred to as an information update period). A plurality of information update periods are set according to the types of information to be updated.

Cloud parameters may also include scheduled task templates. In the scheduled task template, the processing contents of the scheduled task to be executed by each of the terminal devices 4 and 5 are defined. The above information update cycle corresponds to the execution cycle of one or more processes in the schedule task.

A scheduled task template and a scheduled task table exist separately. That is, in the first storage 93, the scheduled task template is written in the first storage area, and the scheduled task table is written in the second storage area different from the first storage area.

Setting the cloud profile further includes setting a shared access signature (hereinafter referred to as SAS) for using cloud services. SAS is an abbreviation for Shared Access Signature.

SAS is individually set for each of the first storage 93 and the second storage 94 (that is, table storage and object storage). In setting the cloud profile in the master 2, the main administrator configures the SAS set in each of the first storage 93 and the second storage 94 so that the first storage 93 and the second storage 94 can be accessed from the master 2. , as part of the cloud profile.

The same SAS is set when the main management program 15a is installed in the master 2 as well. When the master 2 accesses the cloud server 6 , the SAS set in the master 2 is sent to the cloud server 6 . When the transmitted SAS matches the SAS of the access destination set in the cloud server 6, communication with the access destination (that is, reading and writing of data) becomes possible.

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

Master 2 exports at least part of the cloud profile from master 2 as a client profile (ie, data for reading by client 3), as shown in S04. The client profile may include, for example, at least one of the above initialization parameters, scheduled task template and SAS. A client profile exported by master 2 is provided to client 3 . A client profile may be provided to the client 3 in any manner. For example, the client profile may be sent from the master 2 to the client 3 by e-mail or other method.

The sub-administrator operates the client 3 to install the sub-administration program 35a on the client 3, as shown in S06. At this time, the client profile provided from the master 2 is imported into the client 3 by the operation of the sub-administrator, as shown in S05. That is, various data set in the client profile are appropriately set in the client 3 . 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 scheduled task template may be imported.

By installing the secondary management program 35 a and setting the client profile as described above, the client 3 can use the cloud server 6 . Thereby, the client 3 is configured to be able to communicate with the master 2 via the cloud server 6 . The client 3 is configured to be able to execute the management relay function via the cloud server 6 . The management relay function includes task execution instructions from the master 2 to the type 1 terminal device 4 and transmission of log information and status information from the type 1 terminal device 4 to the master 2. It is a function of relaying information with the device 4 .

Further, as shown in S07, the SAS is registered in the type 2 terminal device 5 by an input operation by the administrator of the type 2 terminal device 5 (hereinafter referred to as the device administrator).
The SAS registration for the type 2 terminal device 5 may be performed via the input unit 74 of the type 2 terminal device 5, for example. Further, for example, the SAS may be registered in the type 2 terminal device 5 from an information processing device different from the type 2 terminal device 5 . Specifically, a predetermined WEB server may be incorporated in the type 2 terminal device 5 . Then, by accessing the WEB server from an information processing device different from the type 2 terminal device 5, entering the SAS through the user interface of the information processing device, and transmitting it to the WEB server, the type 2 terminal device 5 may be able to register the SAS.

The control unit 71 of the type 2 terminal device 5 in which the SAS is registered executes processing according to the communication program 82a. The control unit 71 that executes processing according to the communication program 82a is hereinafter referred to as a cloud connector. The cloud connector accesses the first storage 93 of the cloud server 6 using SAS and refers to the cloud parameters written by the master 2, as shown in S08. The cloud connector acquires this cloud parameter and sets it in its own device.

Note that when the cloud connector accesses the cloud server 6 , the SAS of the access destination is transmitted from the cloud connector to the cloud server 6 . When the transmitted SAS matches the SAS of the access destination set in the cloud server 6, communication with the access destination (that is, reading and writing of data) becomes possible.

The type 2 terminal device 5 (that is, the cloud connector), when the initial setting (that is, the processing of S07 and S08) including the setting of the above cloud parameters and SAS is completed, updates the set information as shown in S09. Execute a scheduled task periodically according to a period.

When the initial settings (that is, the processing of S05 and S06) including the setting of the above cloud parameters and SAS are completed, the client 3 regularly updates the cloud server 6 according to the set information update cycle as shown in S10. executes a scheduled task to update information stored in the first storage 93 of the .

A scheduled task by the cloud connector starts by registering the device information in the first storage 93 when the corresponding device information is not registered in the first storage 93 . The device information corresponding to the cloud connector is predetermined information indicating the type 2 terminal device 5 in which the cloud connector is installed.

If there is a type 1 terminal device 4 whose corresponding device information is not registered in the first storage 93 among the type 1 terminal devices 4 to be managed, the scheduled task by the client 3 is is registered in the first storage 93 with the device information of the type 1 terminal device 4 that is not registered. The device information of the type 1 terminal device 4 is predetermined information indicating the type 1 terminal device 4 .

The first storage 93 has a schedule task table as one of the tables. A schedule task table contains a collection of one or more entities. An entity contains multiple properties. In this embodiment, the multiple properties include, for example, "PartitionKey", "RowKey", "DeviceId", "NotifyParameter", "Progress" and "Source" as shown in FIG.

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

Information in the entity is updated by the client 3 that manages the type 1 terminal device 4 when the corresponding terminal device is the type 1 terminal device 4 . Information in the entity is updated by the cloud connector of the second type terminal device 5 if the corresponding terminal device is the second type terminal device 5 .

If the entity is related to "log", the property "PartitionKey" stores "log", which is a character string indicating "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". A device ID is identification information unique to each of the terminal devices 4 and 5 .

The log information may include information indicating the total number of printed sheets of the corresponding terminal device when the corresponding terminal device is a printer or a digital multi-function peripheral. The log information may include, as a print history, information indicating the user who issued the print command and the number of prints for each print job.

If the entity is related to "status", the property "PartitionKey" stores "status", which is a character string indicating the "status". The entity related to "status" stores the status information of 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 a digital multi-function peripheral, the status information may include remaining color material information and error information such as a paper jam of the corresponding terminal device.

In the case of an entity related to "registration", the property "PartitionKey" stores "registration", which is a character string indicating "registration". The entity related to "registration" stores the device information of the terminal device corresponding to the device ID stored in the property "DeviceId" in the property "NotifyParameter". 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 described in JSON format to indicate the instruction content of the schedule task.

For example, in the property "NotifyParameter" in the entity related to "status", the object identifier (hereinafter referred to as OID) used in the management information base (hereinafter referred to as MIB) of the corresponding parameter is associated with the value, in JSON format Described. “x.x.x.x.x . ·” is an exemplary abstract representation of an object identifier. MIB is an abbreviation for Management Information Base.

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

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

If the above “xxxxx. "%MIB(Oid1)%" is an instruction to acquire a value corresponding to Oid1, which is an object ID, and overwrite "%MIB(Oid1)%" with the acquired value. Therefore, if the value corresponding to Oid1 is "XXXXXXX", in the registered data, ""Oid1": "%MIB (Oid1)%"" is rewritten to ""Oid1": "XXXXXX"".

Similarly, if the object ID "y.y.y.y...." is written as Oid2, the instruction on the third line is ""Oid2":"%MIB(Oid2)%"".
“x.x.x.x.x .・” is an abstract representation of the update result.

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

The property "Progress" contains character strings indicating the progress, for example, the character string "done" indicating that the task has been completed, the character string "request" indicating that the execution of the instruction is requested, and the A character string "processing" indicating that it is inside is stored.

The property "Source" indicates the type of device that updated the entity. When the entity is updated by the client 3, a character string “client” indicating the client 3 is stored in the property “Source” of the entity. When an entity is updated by a cloud connector, a character string “device” indicating that it is the type 2 terminal device 5 is stored in the property “Source” of the entity.

The cloud connector entity of the type 2 terminal device 5 is updated by the cloud connector. The entity of the type 1 terminal device 4 is updated by the client 3 connected to the same local area network as the type 1 terminal device 4 . That is, the client 3 updates the entity for each type 1 terminal device 4 under the control of the client 3 (that is, the type 1 terminal device 4 targeted for management relay). The identification information of the client 3 whose management relay target is the type 1 terminal device 4 may be written in the registration entity of the type 1 terminal device 4 as part of the device information.

The client 3 communicates with each type 1 terminal device 4 targeted for management relay within the same local area network, and acquires information necessary for updating device information from each type 1 terminal device 4 . The client 3 can update the registered entity of the corresponding type 1 terminal device 4 based on the acquired information.

Further, the client 3 periodically communicates with each of the type 1 terminal devices 4 targeted for management relay via the local area network, and acquires corresponding log information and status information. The client 3 can update the log entity and status entity of the corresponding type 1 terminal device 4 based on the acquired log information and status information.

The cloud connector of the type 2 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 the client 3 . That is, it may be understood that the master 2 functions as the client 3 for the type 1 terminal device 4 at the first site. Specifically, in the schedule task table in the first storage 93 of the cloud server 6, "log", "status" corresponding to each type 1 terminal device 4 (hereinafter referred to as master subordinate terminal device) at the first base and three entities for "registration" are created. Like the client 3, the master 2 can acquire various types of information from the master subordinate terminal device and update the registered entity, log entity, and status entity of each corresponding master subordinate terminal device.

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

Further, the master 2 displays the list of the registered terminal devices 4 and 5 on the screen of the display unit 13 according to the operation signal output from the input unit 14 by the user's operation, and displays the log of the terminal devices 4 and 5. Information and status information can be displayed. In this way, the management system 1 is configured to be able to remotely monitor the states of the terminal devices 4 and 5 used at a plurality of locations at one location where the master 2 is installed.

As shown in S12, the master 2 receives an instant task execution request operation from the main administrator in accordance with the operation signal output from the input unit 14 by the operation of the main administrator, and according to this execution request operation, the instant task entity ( Generates data indicating the instant task entity). Instant tasks are non-periodic tasks other than scheduled tasks.

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

The instant task entity is registered in the first storage 93 in the form of an instant task table illustrated in FIG. 6, for example.
The instant task table, like the schedule task table, contains the properties of "PartitionKey", "RowKey", "DeviceId", "NotifyParameter", "Progress" and "Source".

The property "PartitionKey" stores "instanttask", which is a character string indicating 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 type 1 terminal device 4 or the type 2 terminal device 5 that is the destination of the instruction.
The property "NotifyParameter" stores a character string described 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 "Source" is not used and is blank.
If a predetermined file is required for execution of the instant task, the master 2 stores the file in the second storage 94 as shown in S14 of FIG. In this case, the property "NotifyParameter" describes information (for example, URL) indicating the storage destination of the file. For example, if the instant task is to update the firmware in the terminal devices 4 and 5, the master 2 stores an update file required for updating the firmware in the second storage 94. FIG. 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 type 2 terminal device 5 accesses the first storage 93 of the cloud server 6 at the set polling cycle and searches for instant tasks targeted for itself. That is, the cloud connector determines whether a new entity of the instant task to be executed by itself is registered in the instant task table.

When a new entity is registered, the Cloud Connector indicates that an Instant Task request has been received by rewriting the property "Progress" string in the corresponding Instant Task entity from "request" to "processing". Transmit to master 2.

After registering the instant task entity, the master 2 checks the status of the instant task corresponding to the instant task entity, as shown in S18. Specifically, the master 2 periodically refers to the instant task entity in the instant task table registered in the first storage 93 at the set polling cycle. Through a periodic reference, Master 2 can confirm that the Instant Task request has been received based on the updated progress property value.

The cloud connector of the type 2 terminal device 5 refers to the property "NotifyParameter" in the instant task entity when executing the instant task. Then, when the data file necessary for executing the instant task exists in the second storage 94, the cloud connector, based on the storage location information (for example, URL) described in the property "NotifyParameter", as shown in S16 Then, the data file is downloaded from the second storage 94 .

When the instant task ends, the cloud connector of the type 2 terminal device 5 updates the corresponding instant task entity as shown in S17. Specifically, the cloud connector rewrites the property "Progress" character string in the corresponding Instant Task entity from "processing" to "done", thereby notifying the master 2 of the completion of the Instant Task execution. .

As shown in S19, the client 3 accesses the first storage 93 of the cloud server 6 at the set polling cycle, and searches for instant tasks targeted for management relay. That is, the client 3 determines whether or not a new entity of the instant task to be executed by the type 1 terminal device 4 targeted for relaying management of the client 3 is registered in the instant task table. Below, one or more type 1 terminal devices 4 set as instant task execution targets in the instant task table among the type 1 terminal devices 4 to be relayed for management (that is, stored in the property “DeviceId” Each of the one or more type 1 terminal devices 4) corresponding to the device ID is called an instant task execution target.

When a new instant task entity for the instant task execution target is registered, the client 3 rewrites the character string of the property "Progress" in the instant task entity from "request" to "processing" to execute the instant task. It notifies the master 2 that the task request has been received. Further, the client 3 refers to the property "NotifyParameter" in the instant task entity to recognize the processing content to be executed. Then, based on the recognized processing content, the client 3 acquires data files required for execution of the instant task from the second storage 94 as necessary, as shown in S20.

Thereafter, as shown in S21, the client 3 instructs the instant task execution target to execute the instant task through the local area network. At this time, the data file acquired from the second storage 94 is transferred to each instant task execution target. Then, the client 3 acquires the instant task execution result from the instant task execution target.

When the instant task execution is completed for all the instant task execution targets, the client 3 updates the instant task entity of the corresponding instant task execution target, as shown in S22. Specifically, the client 3 rewrites the character string of the property "Progress" in the corresponding Instant Task entity from "processing" to "done", thereby notifying the master 2 of the completion of the Instant Task execution. .

As confirmation of the situation, the master 2 refers to the instant task entity in the instant task table of the first storage 93 as shown in S23, and learns that the character string of the property "Progress" has been rewritten to "done". , confirms that the instant task has been completed, and writes the processing result in the storage unit 15 .

The master 2 can further display the processing result 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 in all corresponding instant task execution targets, as shown in S25, the instant task entity of the instant task that is no longer needed is transferred to the second instant task entity. 1 Delete from the storage 93 . The master 2 also deletes the data file (for example, the firmware update file) provided for the instant task from the second storage 94, as shown in S26.

In this way, the management system 1 registers and updates instant task entities in the first storage 93 of the cloud server 6 and transfers data files via the second storage 94, thereby enabling the terminal devices 4, 5 can be remotely controlled at one site where the master 2 is installed.

(4) Processing Related to Acquisition of Model Image Data The master 2 can display a terminal management window W1 shown in FIG. After the main management program 15a is activated, the terminal management window W1 is displayed when a predetermined input operation for displaying the terminal management window W1 is performed via the keyboard or pointing device.

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 amount of toner/ink, and node name for each of the terminal devices 4 and 5 included in the management system 1 .

The above status, model name, remaining toner/ink level, and node name are obtained by the master 2 acquiring status information, model name information, remaining toner/ink level information, and node name information from the respective terminal devices 4 and 5. , are displayed in the terminal management window W1.

The selected terminal display area R2 displays the model name I1 and model image I2 of the terminal devices 4 and 5 selected in the management terminal display area R1. The hatched portions in the management terminal display area R1 shown in FIG. 7 correspond to the terminal devices 4 and 5 selected.

Next, the procedure of image acquisition processing executed by the control unit 11 of the master 2 will be described. The image acquisition process is a process that is repeatedly executed while the master 2 is operating.
When the image acquisition process is executed, the CPU 21 of the control unit 11 first determines in S110 whether or not the search timing has arrived, as shown in FIG. The search timing is the timing at which the polling period set for the master 2 elapses.

Here, if the search timing has not arrived, the CPU 21 terminates the image acquisition process. On the other hand, when the search timing has arrived, the CPU 21 executes device search in S120. Specifically, the CPU 21 first performs data communication with a type 1 terminal device 4 (hereinafter referred to as a local device) connected to the master 2 via a local area network, thereby performing data communication with a local device provided in the management system 1. and the model name of each local device. Further, the CPU 21 accesses the first storage 93 of the cloud server 6, and refers to the entity related to "registration" for each cloud device, which will be described later. to identify. The cloud device includes a type 1 terminal device 4 and a type 2 terminal device 5 that are connected to the client 3 via a local area network.

Next, in S130, the CPU 21 acquires model image data indicating the model of the local device from each local device specified in S120. However, the CPU 21 does not acquire the model image data from the local device of the same model as the model corresponding to the already acquired model image data in S130. The model image data is data corresponding to the model image I2 in the terminal management window W1.

Further, in S140, the CPU 21 accesses the first storage 93 of the cloud server 6 and refers to the model image entity for each model of the cloud device identified in S120, thereby obtaining the cloud device from the model image entity. acquires the model image data indicating the model of the device, and ends the image acquisition process. However, in S140, the CPU 21 does not acquire the 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.

The model image entity includes properties of "PartitionKey", "RowKey" and "Binary" as shown in FIG.
The property "PartitionKey" stores the character string "deviceimage" indicating the entity of the model image.

A character string indicating the model name is stored in the property “RowKey”.
The property "Binary" stores the model image data of the model specified by the model name stored in "RowKey".

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 operation sequence for obtaining model image data will be schematically described.

As shown in FIG. 10 , after the type 2 terminal device 5 executes a process of enabling access to the cloud server 6 in S41, in S42 the registered entity and the model image entity are transferred to the first storage. Register with 93. However, if a model image entity of the same model as the type 2 terminal device 5 has already been registered, the type 2 terminal device 5 does not register the model image entity.

The client 3 executes a process of enabling access to the cloud server 6 in S43, and then performs a device search in S44. As a result, the client 3 identifies the type 1 terminal device 4 connected to the client 3 via the local area network and the model name of each type 1 terminal device 4 .

Further, in S45, the client 3 acquires the device information and the model image data from each type 1 terminal device 4 specified by the device search, and registers the registered entity of each type 1 terminal device 4 with the model of each model. The image entity is registered in the first storage 93 .

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

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

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

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

Such a main management program 15 a does not allow the master 2 to acquire model image data of the same model as the type 1 terminal device 4 connected to the master 2 from the cloud server 6 . As a result, the main management program 15a can streamline the data transfer performed in the management system 1 for the master 2 to acquire the model image data.

Further, the first data acquisition process does not acquire the main connection model data from the main connection terminal device of the same model as the model corresponding to the already acquired main connection model data. Since such a main management program 15a can prevent redundant acquisition of main connection model data of the same model, the processing load on the master 2 can be reduced.

Also, the client 3 uploads the secondary connection model data only when the secondary connection model data can be obtained from the secondary connection terminal device. As a result, data indicating that the secondary connection model data could not be acquired is not stored in the cloud server 6 , so the management system 1 can suppress reduction in the data storage capacity of the cloud server 6 .

The client 3 also uploads to the cloud server 6 a model image entity in which the first model name information indicating the model name of the secondary connection terminal device and the secondary connection model data are associated with each other. The second type terminal device 5 uploads to the cloud server 6 a model image entity associated with the second model name information indicating the model name of the second type terminal device 5 and the second model data. As a result, the model image data of the same model can be prevented from being redundantly stored in the cloud server 6 , so the management system 1 can suppress reduction in the data storage capacity of the cloud server 6 .

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.

Also, S130 corresponds to the first data acquisition process and the first data acquisition step, and S140 corresponds to the second data acquisition process and the second data acquisition step.
An embodiment of the present disclosure has been described above, but the present disclosure is not limited to the above embodiment, and can be implemented in various modifications.

For example, in the above embodiment, model data is model image data, but model data is not limited to image data, and model data is information common to the same model (for example, model specifications). may be
Further, 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 be stored in the second storage 94 of the cloud server 6.

A plurality of functions possessed by one component in the above embodiment may be implemented by a plurality of components, or a function possessed by one component may be implemented by a plurality of components. Also, a plurality of functions possessed by a plurality of components may be realized by a single component, or a function realized by a plurality of components may be realized by a single component. Also, part of the configuration of the above embodiment may be omitted. Also, at least part of the configuration of the above embodiment may be added or replaced with respect to the configuration of the other above embodiment.

In addition to the master 2 described above, a system having the master 2 as a component, a program for making a computer function as the master 2, a non-transitional physical recording medium such as a semiconductor memory recording this program, a management method, etc. The present disclosure can also be implemented in various forms.

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 (7)

A management program used in a management system for managing a plurality of terminal devices,
The management system is
a management device;
a sub-managing device;
a type 1 terminal device that is the terminal device that is communicably connected to either one of the management device and the sub management device;
a type 2 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 communicate with the management device, the sub management device, and the second type terminal device;
The management program causes a controller provided in the management device to:
a first data acquisition process for acquiring 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;
secondary connection model data related to a model of the secondary connection terminal device that is different from the model corresponding to the main connection model data among the secondary connection terminal devices that are the type 1 terminal devices connected to the secondary management device; and a second data acquisition process of acquiring from the storage device the model corresponding to the main connection model data and the second model data related to the model of the second type terminal device different from the model corresponding to the main connection model data. management program. The management program according to claim 1,
The first data acquisition processing is a management program that does not acquire the main connection model data from the main connection terminal device of the same model as that corresponding to the already acquired main connection model data. A management device used in a management system that manages a plurality of terminal devices,
The management system is
the management device;
a sub-managing device;
a type 1 terminal device that is the terminal device that is communicably connected to either one of the management device and the sub management device;
a type 2 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 communicate with the management device, the sub management device, and the second type terminal device;
The control unit included in the management device includes:
a first data acquisition process for acquiring 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;
secondary connection model data related to a model of the secondary connection terminal device that is different from the model corresponding to the main connection model data among the secondary connection terminal devices that are the type 1 terminal devices connected to the secondary management device; and a second data acquisition process for acquiring from the storage device the model corresponding to the main connection model data and the second model data related to the model of the second type terminal device different from the model corresponding to the main connection model data. management device. A management method used by a management device in a management system for managing a plurality of terminal devices,
The management system is
the management device;
a sub-managing device;
a type 1 terminal device that is the terminal device that is communicably connected to either one of the management device and the sub management device;
a type 2 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 communicate with the management device, the sub management device, and the second type terminal device;
The management method is
a first data acquisition step of acquiring 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;
secondary connection model data related to a model of the secondary connection terminal device that is different from the model corresponding to the main connection model data among the secondary connection terminal devices that are the type 1 terminal devices connected to the secondary management device; and a second data acquisition step of acquiring second model data related to a model of the second type terminal device different from the model corresponding to the main connection model data from the storage device. A management system for managing a plurality of terminal devices,
The management system is
a management device;
a sub-managing device;
a type 1 terminal device that is the terminal device that is communicably connected to either one of the management device and the sub management device;
a type 2 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 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 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;
secondary connection model data related to a model of the secondary connection terminal device that is different from the model corresponding to the main connection model data among the secondary connection terminal devices that are the type 1 terminal devices connected to the secondary management device; a second data acquisition process for acquiring from the storage device the model corresponding to the main connection model data and the second model data related to the model of the second type terminal device different from the model corresponding to the main connection model data;
The secondary management device acquires the secondary connection model data from the secondary connection terminal device and uploads the acquired secondary connection model data to the storage device,
The second type terminal device is a management system for uploading the second type data to the storage device. A management system according to claim 5, wherein
A management system in which the secondary management device uploads the secondary connection model data only when the secondary connection model data can be acquired from the secondary connection terminal device. A management system according to claim 5 or claim 6,
The secondary management device uploads the secondary connection model data to the storage device in association with first model name information indicating the model name of the secondary connection terminal device,
A management system in which the second type terminal device uploads the second type data to the storage device in association with second model name information indicating the model name of the second type terminal device.

Images