Equipment management system, equipment management device, equipment management program, and equipment management method
Patent Information
- Application Number
- JP2021134727
- Authority / Receiving Office
- JP · JP
- Patent Type
- Patents
- Current Assignee / Owner
- Filing Date
- 2021-08-20
- Publication Date
- 2025-02-18
- Estimated Expiration
- 2041-08-20
AI Technical Summary
【0012】 本発明によると、端末装置からの印刷データを画像形成装置にプリントサーバーを経由して印刷するための画像形成装置のドライバーを作成することが可能となる。
Smart Images

Figure 0007631145000001 
Figure 0007631145000002 
Figure 0007631145000003
Abstract
Description
[Technical field]
[0001] The present invention relates to a device management system, a device management apparatus, a device management program, and a device management method. [Background technology]
[0002] Patent document 1 describes an equipment management system (image forming system) equipped with an image forming device that remotely accesses a terminal device selected as a terminal device (target terminal) in an installation operation and sends an installation instruction to the terminal device to automatically install a driver.
[0003] Incidentally, in conventional device management systems, print data from a terminal device is temporarily stored in a print server, and when a user issues a print instruction to the image forming device that is to execute the printing, the print data from the print server is printed by the image forming device that is instructed to print. [Prior art documents] [Patent documents]
[0004] [Patent Document 1] JP 2020-43538 A Summary of the Invention [Problem to be solved by the invention]
[0005] However, while the configuration described in Patent Document 1 makes it possible to create a driver for an image forming device for directly printing print data from a terminal device to an image forming device, when printing print data from a terminal device to an image forming device via a print server, since identification information for the print server is not set, it is not possible to create a driver for an image forming device for printing print data from a terminal device to an image forming device via the print server.
[0006] Therefore, an object of the present invention is to provide an equipment management system, an equipment management device, an equipment management program, and an equipment management method that can create a driver for an image forming device to print print data from a terminal device to an image forming device via a print server. [Means for solving the problem]
[0007] In order to solve the above problems, the following device management system and device management device are provided: The first and second aspects Equipment Management Program and A device management method is provided.
[0008] (1) Equipment management system The device management system according to the present invention includes an image forming device, and a device management device that communicates with the image forming device and is connectable to a terminal device, the device management device receives identification information of a print server from the terminal device, the device management device registers a driver of the image forming device associated with the identification information of the print server in a storage unit, the terminal device requests the device management device to download the driver associated with the identification information of the print server, and the device management device accepts download of the driver associated with the identification information of the print server to the terminal device. the device management device determines whether a driver for the image forming device is a model-wide driver that can be commonly used among a plurality of types of the image forming devices; the terminal device accepts an input operation for name information of the print server; the terminal device transmits the name information of the print server to the device management device; the device management device receives the name information of the print server from the terminal device; the device management device associates the model-wide driver with identification information and name information of the print server; and the device management device registers the model-wide driver associated with the identification information and name information of the print server in the storage unit. The present invention is characterized in that:
[0009] (2) Equipment management device The device management device according to the present invention comprises: The present invention comprises an image forming apparatus and a device management device that communicates with the image forming apparatus and is connectable to a terminal device, the device management device receiving identification information of a print server from the terminal device, the device management device registering a driver of the image forming apparatus associated with the identification information of the print server in a storage unit, the terminal device requesting the device management device to download the driver associated with the identification information of the print server, and the device management device accepting the download of the driver associated with the identification information of the print server to the terminal device.An equipment management device in an equipment management system, comprising: an upload reception control unit that accepts uploading of a driver for the image forming device from the terminal device; a reception control unit that receives identification information of the print server from the terminal device; an association control unit that associates the driver for the image forming device uploaded by the upload reception control unit with the identification information of the print server received by the reception control unit; a registration control unit that registers the driver associated with the identification information of the print server by the association control unit in a memory unit; and a download reception control unit that accepts downloading of the driver associated with the identification information of the print server to the terminal device.
[0010] (3 -1 ) The first aspect Equipment Management Program The present invention The first aspect The equipment management program is The present invention comprises an image forming apparatus and a device management device that communicates with the image forming apparatus and is connectable to a terminal device, the device management device receiving identification information of a print server from the terminal device, the device management device registering a driver of the image forming apparatus associated with the identification information of the print server in a storage unit, the terminal device requesting the device management device to download the driver associated with the identification information of the print server, and the device management device accepting the download of the driver associated with the identification information of the print server to the terminal device. The device management program is executed on the terminal device used in the device management system, and causes a computer to execute each step including an upload request control step of requesting the device management device to upload a driver for the image forming device, an input operation acceptance control step of accepting an input operation of identification information of the print server, a transmission control step of sending the identification information of the print server to the device management device, and a download request control step of requesting the device management device to download the driver associated with the identification information of the print server. (3-2) Device management program according to the second aspect A device management program according to a first aspect of the present invention includes an image forming device, and a device management device that communicates with the image forming device and is connectable to a terminal device, wherein the device management device receives identification information of a print server from the terminal device, the device management device registers a driver for the image forming device associated with the identification information of the print server in a storage unit, the terminal device requests the device management device to download the driver associated with the identification information of the print server, the device management device accepts a download of the driver associated with the identification information of the print server to the terminal device, the device management device determines whether the driver for the image forming device is a model-wide driver that can be used in common among a plurality of types of the image forming device, the terminal device accepts an input operation of name information of the print server, and the terminal device registers a driver for the image forming device associated with the identification information of the print server in a storage unit. a terminal device for use in a device management system, the terminal device transmitting name information of the print server to the device management device, the device management device receiving name information of the print server from the terminal device, the device management device associating the model-common driver with the identification information and name information of the print server, and the device management device registering the model-common driver associated with the identification information and name information of the print server in the memory unit; the device management program being executed on the terminal device for use in the device management system, the device management device causing a computer to execute each step including an upload request control step of requesting the device management device to upload a driver for the image forming device, an input operation acceptance control step of accepting an input operation of the identification information and name information of the print server, and a transmission control step of transmitting the identification information and name information of the print server to the device management device.
[0011] (4) Equipment management method In a device management method according to the present invention, a device management device communicates with an image forming device and is connectable to a terminal device, the device management device receives identification information of a print server from the terminal device, the device management device registers a driver of the image forming device associated with the identification information of the print server in a storage unit, the terminal device requests the device management device to download the driver associated with the identification information of the print server, and the device management device accepts download of the driver associated with the identification information of the print server to the terminal device. the device management device determines whether a driver for the image forming device is a model-wide driver that can be commonly used among a plurality of types of the image forming devices; the terminal device accepts an input operation for name information of the print server; the terminal device transmits the name information of the print server to the device management device; the device management device receives the name information of the print server from the terminal device; the device management device associates the model-wide driver with identification information and name information of the print server; and the device management device registers the model-wide driver associated with the identification information and name information of the print server in the storage unit. The present invention is characterized in that: Effect of the Invention
[0012] According to the present invention, it is possible to create a driver for an image forming apparatus for printing print data from a terminal device to an image forming apparatus via a print server. [Brief description of the drawings]
[0013] [Figure 1] 1 is a schematic configuration diagram of an example of a device management system according to an embodiment of the present invention; [Diagram 2] 2 is a schematic configuration diagram illustrating an example of a device management device in the device management system illustrated in FIG. 1. [Figure 3A] 2 is a schematic configuration diagram showing an example of a terminal device of an administrator used in the device management system shown in FIG. 1. [Figure 3B] 2 is a schematic diagram illustrating an example of a terminal device of a general user used in the device management system illustrated in FIG. 1. [Figure 4A] 11 is a flowchart showing the first half of an example of a process flow in the device management system. [Figure 4B] 11 is a flowchart showing the second half of an example of the process flow in the device management system. [Figure 5A] 1 is a front view showing an example of a display screen displayed on a display unit of a terminal device of an administrator in the device management system; [Figure 5B]13 is a front view showing another example of a display screen displayed on the display unit of the terminal device of the administrator in the device management system. FIG. [Figure 5C] 13 is a front view showing yet another example of a display screen displayed on the display unit of the terminal device of the administrator in the device management system. FIG. [Figure 5D] 13 is a front view showing yet another example of a display screen displayed on the display unit of the terminal device of the administrator in the device management system. FIG. [Figure 5E] 13 is a front view showing yet another example of a display screen displayed on the display unit of the terminal device of the administrator in the device management system. FIG. [Figure 5F] 13 is a front view showing yet another example of a display screen displayed on the display unit of the terminal device of the administrator in the device management system. FIG. [Figure 5G] 13 is a front view showing yet another example of a display screen displayed on the display unit of the terminal device of the administrator in the device management system. FIG. [Figure 5H] 13 is a front view showing yet another example of a display screen displayed on the display unit of the terminal device of the administrator in the device management system. FIG. [Figure 5I] 13 is a front view showing yet another example of a display screen displayed on the display unit of the terminal device of the administrator in the device management system. FIG. [Figure 6A] 11 is a plan view showing an example of a first content of an e-mail sent from the equipment management device to the terminal device; FIG. [Figure 6B] 13 is a plan view showing an example of second contents of an e-mail sent from the equipment management device to the terminal device. FIG. [Figure 6C] 13 is a plan view showing an example of a third content of an e-mail sent from the equipment management device to the terminal device. FIG. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS
[0014] Hereinafter, an embodiment of the present invention will be described with reference to the drawings. In the following description, the same components are denoted by the same reference numerals. The names and functions of the components are also the same. Therefore, detailed description thereof will not be repeated.
[0015] Fig. 1 is a schematic configuration diagram of an example of a device management system 300 according to the present embodiment. Fig. 2 is a schematic configuration diagram showing an example of a device management device 100 in the device management system 300 shown in Fig. 1. Figs. 3A and 3B are schematic configuration diagrams showing examples of a terminal device 10(1) of an administrator AD and terminal devices 10(2)-10(m) of general users US-US, respectively, used in the device management system 300 shown in Fig. 1.
[0016] 1, the device management system 300 is composed of a device management device 100 (device management server) and n (n is an integer of 1 or 2 or more) image forming devices 200(1)-(n). A print server PS and m (m is an integer of 2 or more) terminal devices 10(1)-10(m) are connected to the device management system 300.
[0017] The device management device 100 is connected to a network NT2, such as a LAN (Local Area Network) or a WAN (Wide Area Network), via a network NT1 (the Internet). Image forming devices 200(1)-(n), a print server PS, and terminal devices 10(1)-10(m) are connected to the network NT2.
[0018] In this example, the image forming apparatuses 200(1)-(n) are multifunction machines having a printer function and / or printers.
[0019] <Device management device> The device management device 100 communicates with the image forming apparatuses 200(1)-(n) and is connectable to the terminal devices 10(1)-10(m), and includes a control unit 110 and a storage unit 120, as shown in FIG.
[0020] The control unit 110 includes an information processing device such as a CPU. The storage unit 120 includes a non-volatile memory such as a ROM, a volatile memory such as a RAM, and a large-capacity storage device such as an SSD or HDD. The storage unit 120 stores a device management program Pa, a driver database DB, and various types of information.
[0021] In the control unit 110, an equipment management program Pa prestored in the ROM of the storage unit 120 is called up, and when it is loaded onto the RAM of the storage unit 120, various control operations are executed.
[0022] <Terminal device> As shown in FIGS. 3A and 3B, each of the terminal devices 10(1) to 10(m) includes a control unit 11 and a storage unit 12.
[0023] The control unit 11 includes an information processing device such as a CPU. The storage unit 12 includes a non-volatile memory such as a ROM, a volatile memory such as a RAM, and a large-capacity storage device such as an SSD or HDD. The storage unit 12 stores device management programs Pb1, Pb2, and various information. In addition, in the terminal devices 10(1) to 10(m), as described below, a driver DVI associated with device information and print server information is installed, and settings corresponding to the device information and print server information are performed.
[0024] In the control unit 11, device management programs Pb1 and Pb2 stored in advance in the ROM of the storage unit 12 are called up, and when they are loaded onto the RAM of the storage unit 12, various control operations are executed.
[0025] The terminal devices 10(1) to 10(m) each include a reception unit 13 (a keyboard or a touch panel in this example) and a display unit 14 (a display panel in this example). The reception unit 13 is electrically connected to an input system of the control unit 11. The reception unit 13 receives input operations by the user AL. The display unit 14 is electrically connected to an output system of the control unit 11. The display unit 14 displays various information on a display screen based on display data.
[0026] Examples of the terminal devices 10(1) to 10(m) include information processing devices such as personal computers, and mobile terminal devices such as smartphones and tablet terminals.
[0027] (First embodiment) The device management device 100 implements a device management method of the device management system 300. In the device management device 100, as shown in Fig. 2, the control unit 110 functions as a means including a communication control unit Qa1, an upload reception control unit Qa2, a reception control unit Qa3, an association control unit Qa4, a registration control unit Qa5, a download reception control unit Qa6, a transmission control unit Qa7, a device information acquisition control unit Qa8, and a driver determination control unit Qa9. That is, the device management program Pa causes the control unit 110 (computer) to execute each step including a communication control step, an upload reception control step, a reception control step, an association control step, a registration control step, a download reception control step, a transmission control step, a device information acquisition control step, and a driver determination control step.
[0028] The communication control unit Qa1 of the device management apparatus 100 communicates with the image forming apparatuses 200(1)-200(n), the terminal device 10(1) of the administrator AD, and the terminal devices 10(2)-10(m) of the general users US-US via the networks NT1 and NT2. Here, the administrator AD is a user AL who has the authority to manage the terminal devices 10(2)-10(m) of the general users US-US. The administrator AD and the general users US-US are distinguished from each other by the authentication information (user ID and password) used when the terminal devices 10(1)-10(m) log in to the device management apparatus 100. The user AL includes the administrator AD and the general users US-US.
[0029] Moreover, the terminal devices 10(1) to 10(m) implement the device management method of the device management system 300.
[0030] 3A, in the terminal device 10(1) of the administrator AD, the control unit 11 functions as a means including a communication control unit Qb1, an upload request control unit Qb2, an input operation reception control unit Qb3, a transmission control unit Qb4, a download request control unit Qb5, a reception control unit Qb6, a registration determination control unit Qb7, and an alarm control unit Qb8. That is, the device management program Pb1 causes the control unit 11 (computer) to execute each step including a communication control step, an upload request control step, an input operation control step, a transmission control step, a download request control step, a reception control step, a registration determination control step, and an alarm control step.
[0031] In the terminal devices 10(2)-10(m) of the general users US-US, the control unit 11 functions as a means including a communication control unit Qb1, a download request control unit Qb5, and a reception control unit Qb6, as shown in Fig. 3B. That is, the device management program Pb2 causes the control unit 11 to execute steps including a communication control step, a download request control step, and a reception control step.
[0032] -Terminal devices 10(1) to 10(m)- The communication control unit Qb1 of the terminal devices 10(1) to 10(m) communicates with the device management device 100 and the image forming devices 200(1) to 200(n) via the networks NT1 and NT2.
[0033] -Administrator AD's terminal device 10(1)- The storage unit 12 of the terminal device 10(1) of the administrator AD stores in advance the drivers DV{DV(i)} of the image forming devices 200(1) to 200(i) (i is at least one integer from 1 to n).
[0034] The upload request control unit Qb2 of the terminal device 10(1) of the administrator AD requests the device management device 100 to upload a driver DV{DV(j)} (j is any one integer from 1 to i) for the image forming device 200(i).
[0035] -Equipment management device 100- The upload reception control unit Qa2 of the device management apparatus 100 receives an upload from the terminal device 10(1) of the administrator AD of the driver DV{DV(j)} of the image forming apparatus 200(i).
[0036] -Administrator AD's terminal device 10(1)- The input operation reception control unit Qb3 of the terminal device 10(1) of the administrator AD receives, from the reception unit 13, an input operation of print server information SVI including identification information of the print server PS for printing the print data IM (print job) of the image forming device 200(j) on the image forming device 200(j). Here, examples of the identification information of the print server PS include an IP (Internet Protocol) address, a MAC (Media Access Control) address, etc. In this example, the identification information of the print server PS is the IP address.
[0037] The transmission control unit Qb4 of the terminal device 10(1) of the administrator AD transmits to the device management apparatus 100 the print server information SVI including the IP address of the print server PS.
[0038] -Equipment management device 100- The reception control unit Qa3 of the device management apparatus 100 receives the print server information SVI, which includes the IP address of the print server PS, from the terminal device 10(1) of the administrator AD.
[0039] The association control unit Qa4 of the device management apparatus 100 associates the driver DV{DV(j)} of the image forming apparatus 200(i) with the print server information SVI including the IP address of the print server PS.
[0040] The registration control unit Qa5 of the device management apparatus 100 registers the driver DVI associated with the print server information SVI including the IP address of the print server PS in the storage unit 120 (driver database DB).
[0041] -Terminal device 10(k)- The download request control unit Qb5 of the terminal device 10(k) (k is at least one integer from 1 to m) requests the device management device 100 to download the driver DVI associated with the print server information SVI including the IP address of the print server PS.
[0042] -Equipment management device 100- The download reception control unit Qa6 of the device management apparatus 100 receives a request for downloading to the terminal apparatus 10(k) a driver DVI associated with print server information SVI including the IP address of the print server PS.
[0043] The transmission control unit Qa7 of the device management apparatus 100 transmits various types of information in the device management apparatus 100.
[0044] In this embodiment, the device management device 100 receives identification information of the print server PS from the terminal device 10(1) and registers in the memory unit 120 the driver DVI of the image forming device 200(i) associated with the identification information of the print server PS, the terminal device 10(k) requests the device management device 100 to download the driver DVI associated with the identification information of the print server PS, and the device management device 100 accepts the download of the driver DVI associated with the identification information of the print server PS to the terminal device 10(k), so that the user AL can download the driver DVI to the terminal device 10(k) and install (automatically install: silent install) the driver DVI associated with the print server information SVI including the IP address of the print server PS in the terminal device 10(k).
[0045] In this way, according to this embodiment, it is possible to create a driver DVI for the image forming apparatus 200(i) for printing the print data IM from the terminal apparatus 10(k) on the image forming apparatus 200(i) via the print server PS. Therefore, the driver DVI for printing the print data IM on the image forming apparatus 200(i) via the print server PS can be easily installed in the terminal apparatus 10(k).
[0046] In detail, the terminal device 10(1) accepts the input operation of the print server information SVI including the identification information of the print server PS from the accepting unit 13, and can set the identification information of the print server to the driver DV{DV(j)}. That is, the device management device 100 associates the driver DV{DV(j)} of the image forming device 200(i) with the print server information SVI including the identification information (IP address) of the print server PS. Then, the terminal device 10(k) requests the device management device 100 to download the driver DVI associated with the print server information SVI including the IP address of the print server PS, and the device management device 100 accepts the download of the driver DVI associated with the print server information SVI including the IP address of the print server PS to the terminal device 10(k). This allows the user AL to download the driver DVI to the terminal device 10(k) and install (automatically install: silent install) the driver DVI associated with the print server information SVI including the IP address of the print server PS in the terminal device 10(k).
[0047] -Equipment management device 100- The device information acquisition control unit Qa8 of the device management device 100 acquires device information MD including identification information of the image forming device 200(i) from the image forming device 200(i). Here, examples of the identification information of the image forming device 200(1)-200(n) include an IP address and a MAC address. In this example, the identification information of the print server PS is an IP address. Examples of the device information MD include the name information (printer name) of the image forming device 200(1)-200(n), serial number, color mode selection such as automatic color, default settings such as whether to perform double-sided printing or whether to perform stapling, custom settings such as forced black and white printing, and user authority settings.
[0048] The association control unit Qa4 of the device management apparatus 100 associates the driver DV{DV(j)} of the image forming apparatus 200(i) with the device information MD including the IP address of the image forming apparatus 200(i).
[0049] In this way, the driver DVI associated with the device information MD including the IP address of the image forming device 200(i) can be installed (automatically installed: silently installed) in the terminal device 10(k). This makes it possible to create a driver DVI for the image forming device 200(i) for directly printing the print data IM from the terminal device 10(k) on the image forming device 200(i). Therefore, the driver DVI for directly printing the print data IM on the image forming device 200(i) can be easily installed in the terminal device 10(k).
[0050] Furthermore, by associating the driver DV{DV(j)} of the image forming device 200(i) with device information MD including the IP address of the image forming device 200(i), it is possible to obtain the device information MD of the image forming device 200(i) corresponding to the driver DV{DV(j)} of the image forming device 200(i) using the IP address of the image forming device 200(i), and to make various settings for the driver DV{DV(j)} based on the obtained device information MD (for example, selection of a color mode such as automatic color, default settings such as whether to print double-sided or not, whether to staple, custom settings such as forced black and white printing, and setting of user permissions).
[0051] Second embodiment However, when printing is not done via the print server PS, the image forming apparatus 200(i) that prints is specific, and each model of image forming apparatus 200(1) to 200(n) has an individual driver with different settings, making it difficult to assign a unified printer name.
[0052] -Equipment management device 100- In this regard, when the image forming apparatuses 200(1) to 200(n) are multiple types of image forming apparatuses 200, the driver determination control unit Qa9 of the equipment management device 100 determines whether the driver DV{DV(j)} of the image forming apparatus 200 is a common driver DV (universal driver) that can be used in common by multiple types of image forming apparatuses 200.
[0053] In this way, a driver DV (universal driver) common to a plurality of types of image forming apparatuses 200 can be determined, and in this case, a unified printer name can be given.
[0054] -Administrator AD's terminal device 10(1)- The input operation reception control unit Qb3 of the terminal device 10(1) of the administrator AD receives, from the reception unit 13, an input operation of the print server information SVI including the identification information (IP address) and name information (print server name) of the print server PS.
[0055] The transmission control unit Qb4 of the terminal device 10(1) of the administrator AD transmits to the device management apparatus 100 print server information SVI including the IP address and print server name of the print server PS.
[0056] -Equipment management device 100- The reception control unit Qa3 of the device management apparatus 100 receives the print server information SVI, which includes the IP address and the print server name of the print server PS, from the terminal device 10(1).
[0057] The association control unit Qa4 of the device management apparatus 100 associates the driver DV common to all models with the print server information SVI including the IP address and the print server name of the print server PS.
[0058] The registration control unit Qa5 of the device management apparatus 100 registers in the storage unit 120 the driver DVI common to all models that is associated with the print server information SVI including the IP address and print server name of the print server PS.
[0059] -Terminal device 10(k)- The download request control unit Qb5 of the terminal device 10(k) requests the device management device 100 to download the common driver DVI for all models associated with the print server information SVI including the IP address and print server name of the print server PS.
[0060] -Equipment management device 100- The download reception control unit Qa6 of the device management apparatus 100 receives the download of the common driver DVI for each model associated with the print server information SVI including the IP address and print server name of the print server PS to the terminal apparatus 10(k).
[0061] In this way, if the uploaded driver DV{DV(j)} of the image forming device 200 is a driver DV common to all models, a unique print server name can be set, and it is possible to clearly present to the user AL that it is a driver DV common to all models (universal driver) that goes through the print server PS.
[0062] Third embodiment -Administrator AD's terminal device 10(1)- When the download request control unit Qb5 of the terminal device 10(1) of the administrator AD makes a request to the device management device 100 to download the driver DVI associated with the print server information SVI, the transmission control unit Qb4 sends an e-mail ML with download information about the driver DVI to the terminal device 10(k). Here, the destination of the e-mail ML is the terminal device 10(k) to which the driver DVI should be downloaded. The download information may include the IP address and print server name of the print server PS, and the IP address and printer name of the image forming device 200(i) corresponding to the driver DV{DV(j)}.
[0063] The terminal device 10(k) to which the driver DVI is to be downloaded receives the email containing the download information.
[0064] In this way, regardless of the number of types of image forming devices 200 that correspond to the driver DV{DV(j)} (driver DV common to all models), it is possible to collectively guide multiple types of image forming devices 200 in an email ML. This makes it possible to eliminate unnecessary descriptions that may cause confusion.
[0065] The driver DVI may be attached to the e-mail ML as it is, or download information for downloading the driver DVI may be written in the e-mail ML. An example of the download information for downloading the driver DVI is location information {URL (Uniform Resource Locator)} indicating the registration location of the device management device 100 in which the driver DVI is registered.
[0066] Incidentally, if name information that is the same as the name information (print server name) of an already registered print server PS is registered, it will be difficult to distinguish it from the already registered print server PS.
[0067] -Administrator AD's terminal device 10(1)- In this regard, in the terminal device 10(1) of the administrator AD, when the input operation reception control unit Qb3 receives the input operation of the print server name of the print server PS from the reception unit 13, the registration determination control unit Qb7 determines whether or not a print server name identical to the received print server name of the print server PS has already been registered in the memory unit 120 of the equipment management device 100.
[0068] In the terminal device 10(1) of the administrator AD, the warning control unit Qb8 issues a warning when the registration determination control unit Qb7 determines that the device has already been registered. Here, a representative example of the warning is a message displayed on the display unit 14. However, the warning is not limited to this, and may be a voice, an alarm sound, or the like.
[0069] This makes it possible to avoid registering a print server name that is the same as that of an existing print server PS, thereby making it easier to distinguish from already registered print servers PS.
[0070] (Control operation of device management system 300) Next, an example of the control operation of device management system 300 according to this embodiment will be described below with reference to FIGS. 4A and 4B, 5A to 5I, and 6A to 6C.
[0071] Fig. 4A and Fig. 4B are respectively a first half and a second half of a flow chart showing an example of a processing flow in the device management system 300. Fig. 5A to Fig. 5I are front views showing examples of display screens displayed on the display unit 14 of the terminal device 10(1) of the administrator AD in the device management system 300. Fig. 6A to Fig. 6C are respectively plan views showing examples of the first to third description contents of an email ML sent from the device management device 100 to the terminal devices 10(1) to 10(m).
[0072] In the control operation of the device management system 300, the administrator AD logs in to the device management device 100 at the terminal device 10(1) of the administrator AD (S1 in FIG. 4A). At this time, the device management device 100 acquires device information MD including the IP address of the image forming device 200(i) managed by the administrator AD from the image forming device 200(i) (S2 in FIG. 4A), associates the driver DV{DV(j)} of the image forming device 200(i) with the device information MD including the IP address of the image forming device 200(i) (S3 in FIG. 4A), and transmits the data of the device information MD of the image forming device 200(i) to the terminal device 10(1). The terminal device 10(1) displays the device information MD of the image forming device 200(i) in a list on a registered device screen of the display unit 14, as shown in FIG. 5A. Here, the registered device screen displays the device status, model name, IP address, installation location, serial number, and device options.
[0073] Next, when the administrator AD clicks on the pull-down menu of the Settings button BT1 in the upper right of the screen shown in Fig. 5A and selects Printer Driver Management, the device management device 100 sends the data of the Printer Driver File List to the terminal device 10(1), and the terminal device 10(1) pops up a printer driver file list screen on the display unit 14 (see Fig. 5B). In the illustrated example, a driver DV with an identifier of "test" has already been registered.
[0074] Next, the terminal device 10(1) requests the device management device 100 to upload the driver DV{DV(j)} of the image forming device 200(i) (S4 in FIG. 4A). That is, when the administrator AD clicks the "upload" icon IC1 at the top left of the pop-up screen shown in FIG. 5B, the terminal device 10(1) pops up a file upload screen on the display unit 14 as shown in FIG. 5C. Next, when the administrator AD clicks the "select file" button BT2 on the file upload screen, the terminal device 10(1) displays a "file open screen" (not shown) on the display unit 14, and when the administrator AD clicks the driver DV(XXXX_DRIVER) that he or she wants to upload, the driver DV(XXXX_DRIVER) is selected. Then, as shown in Fig. 5D, the terminal device 10(1) displays the selected driver DV(XXXX_DRIVER) on the file upload screen, and the administrator AD inputs the identifier (test1) (name information of the driver DV: driver name) that he / she wants to assign to the selected driver DV(XXXX_DRIVER) in the identifier input field IN1. Next, when the administrator AD clicks the "Upload" button BT3, the terminal device 10(1) transmits the driver DV(XXXX_DRIVER) together with the identifier (test1) to the equipment management device 100.
[0075] The device management apparatus 100 accepts an upload of the driver DV (XXXX_DRIVER) and the identifier (test1) from the terminal device 10(1) (S5 in FIG. 4A).
[0076] Next, the device management device 100 extracts the image forming device 200(i) corresponding to the driver DV(XXXX_DRIVER) and transmits the model list data of the image forming device 200(i) to the terminal device 10(1) (S6 in FIG. 4A), and the terminal device 10(1) pops up a model list (Suported Device List) screen of the image forming device 200(i) corresponding to the driver DV(XXXX_DRIVER) on the display unit 14 (see FIG. 5E) (S7 in FIG. 4A). Here, the model list screen displays the model name, IP address, name, installation location, and serial number.
[0077] A list of models of the image forming apparatuses 200 corresponding to the driver DV is stored in advance in the storage unit 120 of the device management device 100 as a model table corresponding to the driver DV.
[0078] Here, when a plurality of types of models are extracted as the image forming apparatus 200(i) corresponding to the driver DV(XXXX_DRIVER), the driver DV(XXXX_DRIVER) becomes a driver DV common to all models (universal driver).
[0079] Next, on the model list screen shown in FIG. 5E, the administrator AD selects the “check mark” icon CM1 of the model of image forming device 200(i) into which he / she wishes to embed device information MD, and clicks the “Nest” button BT4, whereupon terminal device 10(1) pops up a driver configuration settings screen on display unit 14 (see FIG. 5F) (S8 in FIG. 4A).
[0080] For example, on the driver setting screen shown in Fig. 5F, the administrator AD selects, inputs, and sets the print server information SVI, including whether or not to perform silent installation, selection of emulation if silent installation is performed, whether or not to use print server PS, input of IP address if print server PS is used, input of print server name (Custom Printer Name), and PCT / IP port settings. That is, terminal device 10(1) accepts, from reception unit 13, input operation of print server information SVI including the IP address and print server name of print server PS of image forming device 200(i).
[0081] For example, when the administrator AD clicks the "check mark" icon CM2 to perform a silent installation, clicks the "check mark" icon CM3 to use the print server PS, and enters the IP address (see the λ box in Figure 5G), if the driver DV (XXXX_DRIVER) is a driver DV common to all models, the input field for the print server name (Custom Printer Name) becomes available, and the administrator AD can enter the print server name.
[0082] Here, as shown in FIG. 5H, if the print server name (Custom Printer Name) is duplicated on the driver configuration screen (Driver Configuration Settings) shown in FIG. 5G, a specified message (in this example, the message "This Printer Name is already used.") is displayed.
[0083] On the other hand, if the driver DV (XXXX_DRIVER) is not a common driver DV for all models, the input field for the print server name (Custom Printer Name) is grayed out (see FIG. 5I).
[0084] In addition, the administrator AD selects and operates the settings of the device information MD, including whether or not there are default settings, the color mode setting if the default settings are used, whether or not there is two-sided printing, whether or not there is staples, and the printing policy setting.
[0085] In addition, the administrator AD selects and operates the device information MD, including whether or not to enable custom settings, whether or not to enable forced black and white printing if custom settings are enabled, whether or not to enable change of driver name, and the selection of a suffix if the driver name is changed.
[0086] In addition, as device information MD, the administrator AD selects and inputs whether or not to install user authority (Uer Authority Installation), and if user authority installation is performed, the user name (User Name), domain name (Domain Name), and password (Password).
[0087] Next, when the administrator AD clicks the Save button BT5 at the bottom of the driver setting screen shown in FIGS. 5F to 5I, the terminal device 10(1) transmits the print server information SVI and the device information MD to the device management device 100 (S9 in FIG. 4A).
[0088] The device management device 100 receives the print server information SVI and the device information MD from the terminal device 10(k) (S10 in FIG. 4A), associates the driver DV{DV(j)} with the print server information SVI and the device information MD (S11 in FIG. 4A), and registers the driver DVI associated with the print server information SVI and the device information MD in the driver database DB of the memory unit 120 (S12 in FIG. 4A).
[0089] If the administrator AD wishes to modify the registered driver DVI, the administrator clicks the "Maintenance" icon IC2 on the printer driver file list screen shown in FIG. 5B, and the driver setting screen shown in FIG. 5F is displayed.
[0090] Next, the terminal device 10(1) of the administrator AD sends an email ML with download information regarding the driver DVI to the terminal device 10(k) to which the driver DV should be downloaded (S13 in FIG. 4B).
[0091] In more detail, when the administrator AD clicks on the "Mail" icon IC3 on the printer driver file list screen shown in Fig. 5B, the image forming device 200 model corresponding to the clicked driver DV{DV(j)} is displayed on the display unit 14 of the terminal device 10(1) so as to be selectable, and when the administrator selects the model of the image forming device 200 and inputs the destination of the e-mail ML (the e-mail address of the user AL), the e-mail ML is sent to the terminal device 10(k) from which the driver DV should be downloaded. Here, the terminal device 10(k) from which the driver DV should be downloaded is at least one of the terminal devices of the users AL, including the administrator AD and general users US-US.
[0092] Next, user AL logs in to the device management device 100 at the terminal device 10(k) of user AL (S14 in FIG. 4B). The terminal device 10(k) requests the device management device 100 to download the driver DVI associated with the print server information SVI and the device information MD (S15 in FIG. 4B). The device management device 100 accepts the download of the driver DVI associated with the print server information SVI and the device information MD to the terminal device 10(k) (S16 in FIG. 4B).
[0093] As described above, the user AL can download the driver DVI by email ML, and can also download the driver DVI directly from the device management apparatus 100.
[0094] [Downloading the DVI driver via email ML] The email includes a URL indicating the registration location of the device management device 100 where the driver DV{DV(j)} is registered, and information including the IP address and printer name of the image forming device 200 model selected by the administrator AD.
[0095] Examples of the contents of the email ML include a first content (see FIG. 6A) in the case where print data IM is output to image forming device 200(j) without going through the print server PS, a second content (see FIG. 6B) in the case where driver DV{DV(j)} is a driver DV (universal driver) common to all models and print data IM is output to image forming device 200(j) via the print server PS, and a third content (see FIG. 6C) in the case where driver DV(j) is not a driver DV (universal driver) common to all models and print data IM is output to image forming device 200(j) via the print server PS.
[0096] -First description- For more details, the email ML shown in Figure 6A contains, as the first content, the following sentence in the message field ME1: "Downloadable drivers are available for the following XXXX printers. Click on the download link to install the printer driver. Note: Please save the downloaded file in any folder in the root directory (e.g. "C:\Drivers") and then execute it.", and the URL fields URL1 to URL4 contain the model name, IP address, printer name and URL for each model.
[0097] Here, when any of the URLs in the URL fields URL1 to URL4 for each model listed in the email ML is clicked, a download page for the registration location of the device management device 100 where the driver DV{DV(j)} corresponding to the clicked URL is registered is opened, and a download screen (not shown) is displayed. When the user AL clicks the "download" icon on the download screen, the terminal device 10(k) can download the driver DV{DV(j)} corresponding to the image forming device 200(j) of the model of the clicked URL from the driver database DB in the storage unit 120 in the device management device 100 (S17 in FIG. 4B).
[0098] -Second description- The email ML shown in Figure 6B has the following second content in the message field ME2: "The following print servers have downloadable drivers. Click on the download link to install the printer driver. Note: Please save the downloaded file to any folder in the root directory (e.g., "C:\Drivers") and then execute it." The URL field URL5 lists the IP address, print server name, and URL of the print server PS, and the linked model field LN lists the model name and IP address of each model that can print on the print server PS.
[0099] Here, when the URL in the URL field URL5 of the print server PS written in the email ML is clicked, a download page of the registration location of the device management device 100 where the driver DV{DV(j)} is registered according to the clicked URL is opened, and a download screen (not shown) is displayed. When the user AL clicks the "download" icon on the download screen, the terminal device 10(k) can download the driver DV{DV(j)} corresponding to the print server PS from the driver database DB of the storage unit 120 in the device management device 100 (S17 in FIG. 4B).
[0100] In the box α in FIG. 6B, "XXXX Company" in the example shown in FIG. 6A is changed to "Print Server", indicating that the driver DV is for use via the print server PS.
[0101] Regarding box β in FIG. 6B, if the driver DV is a universal driver (common to all models), the downloaded driver DV is common to all models, so the download URL link can be consolidated into one. (1) If the print server name (Custom Printer Name) is set, the set name will be reflected in the print server name (e.g., PrintServer1). (2) If the print server name (Custom Printer Name) is not set, the print server name will be unified as "Print Server PCL6". If a suffix is set, it will be reflected in the printer name in both cases (1) and (2) (e.g., "PrintServer1_A" or "Print Server PCL6_A").
[0102] For box γ in FIG. 6B, by displaying the associated device information (model name, IP address) on the device management system 300, the driver DV can show the user AL the image forming device 200(i) (MFP) that can print print data (execute a job) via the print server PS.
[0103] If the driver DV you are downloading is a universal driver, the file name of the driver DV is as follows: <Print Server Name>.xxx (Example: PrintServer1.xxx or Print_Server_PCL6.xxx) For example, the file name does not have a suffix.
[0104] -Third description- The email ML shown in Figure 6C contains the following third content in the message field ME3: "Downloadable drivers are available for the following XXXX printers. Click on the download link to install the printer driver. Note: The following device is configured to use the print server (123.456.2.100). Save the downloaded file to any folder in the root directory (e.g. "C:\Drivers") and execute it." The URL fields URL1 to URL4 contain the model name, IP address, printer name and URL for each model.
[0105] Here, when any of the URLs in the URL fields URL1 to URL4 for each model listed in the email ML is clicked, a download page for the registration location of the device management device 100 where the driver DV{DV(j)} corresponding to the clicked URL is registered is opened, and a download screen (not shown) is displayed. When the user AL clicks the "download" icon on the download screen, the terminal device 10(k) can download the driver DV{DV(j)} corresponding to the image forming device 200(j) of the model of the clicked URL from the driver database DB in the storage unit 120 in the device management device 100 (S17 in FIG. 4B).
[0106] Regarding box δ in FIG. 6C, if the driver DV is not a universal driver (common to all models), the downloaded driver DV may have different contents depending on the model. Therefore, the URL links for downloading the driver DV are not consolidated into one, and a note is provided indicating that the driver DV goes through the print server PS.
[0107] If the driver DVD you are downloading is not a universal driver, the file name of the driver DVD is as follows: <Company name>_<Model name>_<Serial number>_<Emulation type>.xxx (Example: XXXX_MX-6170FV_1234578_PCL6.xxx) Examples include:
[0108] [When downloading the DVI driver directly from the device management device 100] When user AL clicks on the “download” icon IC4 on the registered device screen shown in FIG. 5A, the terminal device 10(k) can download the driver DV{DV(j)} corresponding to the image forming device 200(j) of the model indicated by the clicked “download” icon IC4 from the driver database DB in the memory unit 120 in the equipment management device 100 (S17 in FIG. 4B).
[0109] Next, the driver DV downloaded by the user AL is installed (automatically installed) in the terminal device 10(k) of the user AL (S18 in FIG. 4B).
[0110] Then, when the user AL sends print data IM from the terminal device 10(j) to the image forming device 200(j) (S19 in FIG. 4B), the image forming device 200(j) that receives the print data IM prints the print data IM (S20 in FIG. 4B).
[0111] Furthermore, when user AL sends print data IM from terminal device 10(k) to print server PS (S21 in FIG. 4B), the print server PS that receives the print data IM stores the print data IM (S22 in FIG. 4B). When user AL requests print server PS from image forming device 200(j) to print the print data IM to image forming device 200(j) (S23 in FIG. 4B), the print server PS that receives the print request sends the print data IM to image forming device 200(j) (S24 in FIG. 4B), and image forming device 200(j) that receives the print data IM prints the print data IM (S25 in FIG. 4B).
[0112] The present invention is not limited to the above-described embodiment, but can be embodied in various other forms. Therefore, the embodiment is merely illustrative in all respects and should not be interpreted as being restrictive. The scope of the present invention is defined by the claims, and is not limited in any way by the text of the specification. Furthermore, all modifications and changes within the scope of the claims are within the scope of the present invention. [Explanation of symbols]
[0113] 10 Terminal Equipment 11 Control section 12 Storage section 13 Reception 14 Display section 100 Equipment management device 110 Control section 120 Storage section 200 Image forming device 300 Equipment Management System AD administrator AL user DB Driver Database DV Driver DVI Driver IM print data MD device information ML Email NT1 Network NT2 Network PS Print Server Pa Equipment Management Program Pb1 Equipment Management Program Pb2 Equipment Management Program Qa1 Communication control unit Qa2 Upload reception control section Qa3 Reception control section Qa4 Control section Qa5 Registration control section Qa6 Download reception control section Qa7 Transmission control section Qa8 Device information acquisition control section Qa9 Driver Judgment Control Unit Qb1 Communication control unit Qb2 Upload request control section Qb3 Input operation reception control unit Qb4 Transmission control section Qb5 Download request control section Qb6 Reception control section Qb7 Registration judgment control section Qb8 Alarm control unit SVI Print Server Information US General User
Claims
1. An image forming apparatus and a device management device that communicates with the image forming apparatus and is connectable to a terminal device, the device management device receives identification information of the print server from the terminal device; the device management device registers in a storage unit a driver for the image forming device associated with the identification information of the print server; the terminal device requests the device management device to download the driver associated with the identification information of the print server; the device management device accepts a download of the driver associated with the identification information of the print server to the terminal device; the device management device determines whether a driver for the image forming device is a common driver that can be used in common among a plurality of types of the image forming device; The terminal device accepts an input operation of the name information of the print server, The terminal device transmits name information of the print server to the device management device, the device management device receives name information of the print server from the terminal device; the device management device associates the model-specific driver with identification information and name information of the print server; 2. A device management system comprising: a device management apparatus that registers, in the storage unit, the model-specific driver associated with the identification information and name information of the print server.
2. The device management system according to claim 1 , the device management device acquires identification information of the image forming device from the image forming device; 13. A device management system, comprising: a device management device that associates a driver for the image forming device with identification information of the image forming device.
3. 3. The device management system according to claim 1, An equipment management system characterized in that, when the terminal device makes a request to the equipment management device to download a driver common to the model associated with the identification information of the print server, the terminal device sends an email containing download information regarding the driver common to the model.
4. An equipment management device in an equipment management system comprising: an image forming device; and an equipment management device that communicates with the image forming device and is connectable to a terminal device, wherein the equipment management device receives identification information of a print server from the terminal device, the equipment management device registers in a memory unit a driver for the image forming device associated with the identification information of the print server, the terminal device requests the equipment management device to download the driver associated with the identification information of the print server, and the equipment management device accepts downloading of the driver associated with the identification information of the print server to the terminal device, an upload reception control unit that receives an upload of a driver of the image forming apparatus from the terminal device; a reception control unit that receives the identification information of the print server from the terminal device; an association control unit that associates the driver of the image forming apparatus, the upload of which has been accepted by the upload acceptance control unit, with the identification information of the print server, the identification information being received by the reception control unit; a registration control unit that registers the driver associated with the identification information of the print server by the association control unit in a storage unit; a download reception control unit that receives download of the driver associated with the identification information of the print server to the terminal device; A device management device comprising:
5. An equipment management program for an equipment management system executed on the terminal device for use in an equipment management system comprising: an image forming device; and an equipment management device that communicates with the image forming device and is connectable to a terminal device, wherein the equipment management device receives identification information of a print server from the terminal device, the equipment management device registers in a memory a driver for the image forming device associated with the identification information of the print server, the terminal device requests the equipment management device to download the driver associated with the identification information of the print server, and the equipment management device accepts downloading of the driver associated with the identification information of the print server to the terminal device, an upload request control step of requesting the device management device to upload a driver for the image forming device; an input operation reception control step of receiving an input operation of the identification information of the print server; a transmission control step of transmitting identification information of the print server to the device management device; a download request control step of requesting the device management device to download the driver associated with the identification information of the print server.
6. An image forming apparatus comprising: an image forming apparatus; and an equipment management device that communicates with said image forming apparatus and is connectable to a terminal device, wherein said equipment management device receives identification information of a print server from said terminal device, said equipment management device registers in a storage unit a driver of said image forming apparatus associated with the identification information of said print server, said terminal device requests said equipment management device to download said driver associated with the identification information of said print server, said equipment management device accepts download of said driver associated with the identification information of the print server to said terminal device, and said equipment management device determines whether the driver of said image forming apparatus is common to a plurality of types of said image forming apparatus. a terminal device receiving the name information of the print server from the terminal device, the terminal device transmitting the name information of the print server to the device management device, the device management device receiving the name information of the print server from the terminal device, the device management device associating the model-specific driver with identification information and name information of the print server, and the device management device registering the model-specific driver associated with the identification information and name information of the print server in the storage unit, an upload request control step of requesting the device management device to upload a driver for the image forming device; an input operation reception control step of receiving an input operation of the identification information and the name information of the print server; a transmission control step of transmitting identification information and name information of the print server to the device management device; and a device management program for causing a computer to execute each of the steps including the steps of:
7. 7. The device management program according to claim 6, a registration determination control step of determining whether or not name information identical to the received name information of the print server has already been registered in the storage unit of the device management device when the input operation reception control step receives the input operation of the name information of the print server; a warning control step of issuing a warning when it is determined in the registration determination control step that the device has already been registered.
8. a device management device that communicates with the image forming apparatus and is connectable to a terminal device; the device management device receives identification information of the print server from the terminal device; the device management device registers in a storage unit a driver for the image forming device associated with the identification information of the print server; the terminal device requests the device management device to download the driver associated with the identification information of the print server; the device management device accepts a download of the driver associated with the identification information of the print server to the terminal device; the device management device determines whether a driver for the image forming device is a common driver that can be used in common among a plurality of types of the image forming device; The terminal device accepts an input operation of the name information of the print server, The terminal device transmits name information of the print server to the device management device, the device management device receives name information of the print server from the terminal device; the device management device associates the model-specific driver with identification information and name information of the print server; The device management method, wherein the device management device registers, in the storage unit, the model-specific driver associated with the identification information and name information of the print server.
Citation Information
Patent Citations
Image forming apparatus, printer management server, driver delivery system, driver delivery method, information delivery method, delivery program and recording medium
JP2009070202A
Information processing apparatus, information processing method, and program
JP2010250369A
Print management server, printer driver management system, printer driver management program, and information processing device
JP2017068619A
Information processing system, information processing device, information processing method, and program
JP2018018312A
Image forming apparatus and image forming system
JP2020043538A