JP2011060143A - Program introduction support device, program introduction support method, and program introduction program - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To reduce a working burden in introduction work of programs into a plurality of image forming devices. <P>SOLUTION: This program introduction support device includes a determination means for transmitting a prescribed request to the image forming device, to be addressed to a plurality of ports, and for determining the port used for communication with the image forming device, in response to the port number of the port replying a response to the prescribed request, and an installation control means for transmitting an installation request of the program in the image forming device, to the port determined by the determination means. <P>COPYRIGHT: (C)2011,JPO&INPIT

Description

  The present invention relates to a program introduction support apparatus, a program introduction support method, and a program introduction program, and more particularly to a program introduction support apparatus, a program introduction support method, and a program introduction program that support introduction of a program into an image forming apparatus.

  In recent years, there are some image forming apparatuses that are mainly called multifunction peripherals or multi-function peripherals, which are capable of developing new applications and installing developed applications after shipment. If a license for using such an application can be provided in accordance with the user's usage form separately from the application entity, it is not only convenient for the user, but also an expansion of business opportunities for the side selling the application. Can be expected.

  However, in a user environment using a large number of image forming apparatuses, there is a problem that it is very complicated to introduce a license for each image forming apparatus. In view of this, Japanese Patent Application Laid-Open No. H10-228561 discloses a technique for collectively introducing application licenses to a plurality of image forming apparatuses using a device management apparatus.

  However, when the software architecture of the application platform of the image forming apparatus is fundamentally revised in response to a change in the hardware configuration of the image forming apparatus or according to a demand from the market, an application platform having a new configuration is developed. There is. In this case, the application and license management method in the new application platform may be different from the conventional one. Specifically, the application package format, license file format, and the like may be different.

  When a new type of image forming apparatus equipped with a new application platform is introduced to the market, all of the conventional types of image forming apparatuses already installed in the office are new at a certain point in time. It is extremely rare to be replaced with a model image forming apparatus. Therefore, an environment in which a conventional model and a new model are usually mixed in an office occurs.

  If these types of image forming apparatuses can respond to requests from the same device management apparatus (provided that a program capable of processing such requests is installed), an environment in which multiple models are mixed In this case, the administrator can enjoy the same convenience as in Patent Document 1. However, in reality, due to the software architecture of each model, the port number (TCP port number) that can be used for communication with the device management apparatus may be different for each model. Alternatively, some old models may not be able to respond to requests from the device management apparatus (a program that can process such requests cannot be installed).

  Then, the administrator confirms the image forming apparatus that can respond to the request from the device management apparatus in the system environment (office or the like), or confirms which port number each image forming apparatus corresponds to. Complicated work is required. In particular, in an environment where it is necessary to manage hundreds or thousands of image forming apparatuses, the work load becomes enormous.

  The present invention has been made in view of the above points, and is a program introduction support apparatus, a program introduction support method, and a program introduction program capable of reducing the work burden of program introduction work for a plurality of image forming apparatuses. The purpose is to provide.

  Accordingly, in order to solve the above-described problem, the present invention transmits a predetermined request to an image forming apparatus to a plurality of ports and responds to the port number of the port that has returned a response to the predetermined request. Determination means for determining a port to be used for communication with the image forming apparatus, and installation control means for transmitting a program installation request to the image forming apparatus to the port determined by the determination means.

  In such a program introduction support apparatus, it is possible to reduce the work burden of the program introduction work for a plurality of image forming apparatuses.

  According to the present invention, it is possible to reduce the work burden of introducing a program to a plurality of image forming apparatuses.

It is a figure which shows the system configuration example of the apparatus management system in embodiment of this invention. It is a figure which shows the hardware structural example of the apparatus management apparatus in embodiment of this invention. It is a figure which shows the function structural example of the apparatus management system in embodiment of this invention. It is a figure for demonstrating the 1st process sequence of the registration process of a management object apparatus. It is a figure which shows the structural example of the management object apparatus list memory | storage part. It is a figure which shows the example of a display of a process result screen. It is a figure for demonstrating the 2nd process sequence of the registration process of a management object apparatus. It is a sequence diagram for demonstrating the process sequence of installation and activation of an application. It is a figure which shows the structural example of a product key. It is a figure which shows the structural example of a license management table. It is a figure which shows the structural example of a license file.

  Hereinafter, embodiments of the present invention will be described with reference to the drawings. FIG. 1 is a diagram showing a system configuration example of a device management system according to an embodiment of the present invention. In the device management system 1 in FIG. 1, a user environment E1 is a system environment of a user (customer) of the image forming apparatus 20 (image forming apparatuses 20A, 20B, 20C, or 20D). For example, the user environment E1 corresponds to a company or office of the user of the image forming apparatus 20. In the user environment E1, the image forming apparatus 20 and the device management apparatus 10 are connected via a network 30 (whether wired or wireless), such as a LAN (Local Area Network). The image forming apparatus 20 is a multifunction machine that realizes a plurality of functions such as printing, scanning, copying, and fax transmission / reception in a single casing. However, each image forming apparatus 20 may be a printer or a scanner that realizes a single function. The image forming apparatus 20 can enhance functions as needed by adding or updating an application program (hereinafter, simply referred to as “application”).

  The device management apparatus 10 is a computer such as a PC (Personal Computer) that collectively acquires and installs an application operating in the image forming apparatus 20 in the user environment E1 and a license (use authority) of the application, and introduces a program. It is an example of a support device. Note that there may be a plurality of user environments E1 depending on the number of users (the number of users per company or office).

  On the other hand, the manufacturer environment E <b> 2 is a system environment on the seller side of an application added to the image forming apparatus 20. For example, the manufacturer environment E <b> 2 is operated by the manufacturer of the image forming apparatus 20. The manufacturer environment E2 includes a license management server 50, a package management server 60, and the like.

  The license management server 50 is a computer that manages a license of an application purchased by a user. The package management server 60 is a computer that manages application entities (package files).

  The user environment E1 and the manufacturer environment E2 are connected via a network 70 such as the Internet.

  In FIG. 1, the alphabet (“A”, “B”, “C”, or “D”) at the end of the code of the image forming apparatus 20 can respond to a difference in model or a request from the device management apparatus 10. Indicates whether or not there is. Basically, a difference in alphabet means a difference in model. However, the image forming apparatus 20B and the image forming apparatus 20C are the same model. Hereinafter, the model to which the image forming apparatus 20A belongs is referred to as “model A”. The model to which the image forming apparatuses 20B and 20C belong is referred to as “model B”. A model to which the image forming apparatus 20D belongs is referred to as a model “D”.

  In addition, the request from the device management apparatus 10 refers to a predetermined request (application installation request, activation request, etc.) using HTTP (HyperText Transfer Protocol) in the present embodiment.

  The image forming apparatuses 20 </ b> A and 20 </ b> B can respond to a request from the device management apparatus 10. However, due to the difference in model, the port number (TCP (Transmission Control Protocol) port) for receiving a request from the device management apparatus 10 is different. The image forming apparatus 20A can receive a request from the device management apparatus 10 through the port having the port number “W” and the port having the port number “X”. The image forming apparatus 20B can receive a request from the device management apparatus 10 through the port having the port number “Y” and the port having the port number “Z”. W, X, Y, and Z are actually numerical values indicating port numbers, and the values are different from each other. In the present embodiment, for the sake of convenience, a numerical value indicating a port number is written in alphabets.

  The image forming apparatuses 20 </ b> C and 20 </ b> D cannot respond to the request from the device management apparatus 10. However, with respect to the image forming apparatus 20C, HTTP communication by the port Z (the port having the port number “Z”. The same applies to the port notation in the following) or the port Y is possible. By installing a program module for processing the request, it is possible to respond to the request. That is, the difference between the image forming apparatus 20B and the image forming apparatus 20C is whether or not the program module is installed. Therefore, when the program module is installed in the image forming apparatus 20C, the image forming apparatus 20 is classified as the image forming apparatus 20B. On the other hand, the image forming apparatus 20D cannot install the program module because of the software architecture. Therefore, the request from the device management apparatus 10 cannot be handled.

  In FIG. 1, only one image forming apparatus 20A, 20B, 20C, and 20D is shown, but a plurality of each may be arranged. In addition, all of the image forming apparatuses 20A, 20B, 20C, and 20D may not be arranged. For example, only the image forming apparatus 20A and the image forming apparatus 20B may be arranged.

  FIG. 2 is a diagram illustrating a hardware configuration example of the device management apparatus according to the embodiment of the present invention. The device management apparatus 10 of FIG. 2 includes a drive device 100, an auxiliary storage device 102, a memory device 103, a CPU 104, an interface device 105, a display device 106, and an input device that are connected to each other via a bus B. 107.

  A program for realizing processing in the device management apparatus 10 is provided by a recording medium 101 such as a CD-ROM. When the recording medium 101 on which the program is recorded is set in the drive device 100, the program is installed from the recording medium 101 to the auxiliary storage device 102 via the drive device 100. However, the program need not be installed from the recording medium 101 and may be downloaded from another computer via a network. The auxiliary storage device 102 stores the installed program and also stores necessary files and data.

  The memory device 103 reads the program from the auxiliary storage device 102 and stores it when there is an instruction to start the program. The CPU 104 realizes functions related to the device management apparatus 10 in accordance with a program stored in the memory device 103. The interface device 105 is used as an interface for connecting to a network. The display device 106 displays a GUI (Graphical User Interface) or the like by a program. The input device 107 includes a keyboard and a mouse, and is used for inputting various operation instructions.

  FIG. 3 is a diagram illustrating a functional configuration example of the device management system according to the embodiment of the present invention.

  In FIG. 1, the image forming apparatus 20 includes a request processing unit 21, a license check unit 22, and the like. In response to a request from the device management apparatus 10, the request processing unit 21 transmits device information, installs an application, introduces a license file 90, uninstalls an application, deletes the license file 90, and the like. That is, the request processing unit 21 corresponds to a program module that enables the image forming apparatus 20 to respond to a request from the device management apparatus 10. Accordingly, the image forming apparatus 20 in FIG. 2 is the image forming apparatus 20A or 20B. The request processing unit 21 of the image forming apparatus 20A and the request processing unit of the image forming apparatus 20B have different port numbers for use as described above.

  The license file 90 is a file in which data certifying a license for an application (data for permitting use of the application) is recorded. That is, the application in the present embodiment cannot be used in the image forming apparatus 20 simply by obtaining the entity. The application becomes available when the license file 90 is introduced into the image forming apparatus 20.

  The license check unit 22 determines whether or not to use the application based on the license file 90 when the application is used.

  The license management server 50 includes a license management unit 51, a license management table 52, and the like. The license management unit 51 manages licenses using the license management table 52 such as issuance of licenses related to applications. The license management table 52 is a table in which the license status of the application is recorded, and is stored in the storage device of the license management server 50.

  The package management server 60 includes a package management unit 61, a package storage unit 62A, a package storage unit 62B, and the like.

  The package management unit 61 manages applications recorded in the package storage unit 62A and the package storage unit 62B. For example, in response to receiving an application download request, the package management unit 61 acquires the application from the package storage unit 62A or the package storage unit 62B, and returns it to the request source. The package storage unit 62A is a storage area for storing the application for the image forming apparatus 20A in association with the identifier (product ID) in the storage device of the package management server 60. The package storage unit 62B is a storage area for storing an application for the image forming apparatus 20B in association with its identifier (product ID) in the storage device of the package management server 60. Here, the application for the image forming apparatus 20 </ b> A and the application for the image forming apparatus 20 </ b> B are distinguished and managed because the application platforms in the two image forming apparatuses 20 are not compatible. Therefore, even for applications that provide the same service (function), the implementation content (execution code content) differs between the image forming apparatus 20A and the image forming apparatus 20B.

  The device management apparatus 10 includes a UI control unit 111, a model determination unit 112, a management target device list storage unit 113, a package information acquisition unit 114, a device information acquisition unit 115, an installation destination reception unit 116, a package acquisition unit 117, and a license acquisition unit. 118, an installation control unit 119, and the like. Each of these units is realized by processing that the program installed in the device management apparatus 10 causes the CPU 104 of the device management apparatus 10 to execute.

  The UI control unit 111 starts processing according to an instruction from the user. The model determination unit 112 determines the model of each image forming apparatus 20 and whether each image forming apparatus 20 can respond to the request of the device management apparatus 10, and the image that can respond to the request of the apparatus management apparatus 10. The identification information (IP address or host name, etc.) of the forming apparatus 20 is recorded in the management target device list storage unit 113. The management target device list storage unit 113 is a storage area for storing a list of image forming apparatuses 20 to be managed by the device management apparatus 10 in the auxiliary storage device 102. The package information acquisition unit 114 acquires information related to the installation target application from the license management server 50. The device information acquisition unit 115 acquires device information from the image forming apparatus 20A or 20B that is the installation destination or the license introduction destination. The installation destination accepting unit 116 accepts designation of the image forming apparatus 20A or 20B as an application installation destination from the user. The package acquisition unit 117 downloads (acquires) the application to be installed from the package management server 60. The license acquisition unit 118 acquires the license file 90 related to the application to be installed from the license management server 50. The installation control unit 119 transmits the application or license file 90 to the image forming apparatus 20 that is the installation destination or the license introduction destination.

  Hereinafter, a processing procedure of the device management system 1 will be described. As pre-processing for operating the device management system 1, registration processing of the image forming apparatus 20 (device) to be managed by the device management apparatus 10 is executed.

  FIG. 4 is a diagram for explaining a first processing procedure of registration processing of a management target device. The process in FIG. 5 is a process related to one image forming apparatus 20. Therefore, the processing in FIG. 6 is executed for each image forming apparatus 20 connected to the network 30. A list of IP addresses of the image forming apparatuses 20 connected to the network 30 may be automatically acquired by the model determination unit 112 using a device search technique, or recorded in advance in the auxiliary storage device 102 by the user. May be.

  In step S <b> 101, the model determination unit 112 acquires the value of the network device type of the image forming apparatus 20 to be processed (hereinafter referred to as “target device”) by SNMP (Simple Network Management Protocol). The network device type is the name of an object in which a value that can identify the model is recorded in the MIB (Management Information Base) of the image forming apparatus 20.

  If the acquired value is not included in the range of values indicating the model A (No in S102), the model determination unit 112 sends an HTTP device information acquisition request to the port Y (hereinafter simply referred to as “device information acquisition request”). Is transmitted (S103). The device information acquisition request conforms to the interface of the request processing unit 21 included in the image forming apparatus 20A or 20B. The same applies to the device information acquisition request executed below. Further, the content of the device information may be the same as the information acquired by the device information acquisition unit 115 in the later description.

  When the device information is not returned from the target device in response to the device information acquisition request (No in S104), the model determination unit 112 transmits a device information acquisition request to the port Z (S105). When the device information is returned in response to the device information acquisition request (Yes in S106) or the device information is returned in response to the device information acquisition request addressed to port Y (Yes in S104), the model determination unit 112 Determines that the target device is the image forming apparatus 20B. Therefore, the model determination unit 112, for example, the IP address of the target device, the port number (Y or Z) for which the device information has been successfully acquired, and the identifier indicating the model B (hereinafter, the identifier indicating the model is referred to as “model ID”). .) Is recorded in the management target device list storage unit 113 (S107).

  FIG. 5 is a diagram illustrating a configuration example of the management target device list storage unit. As shown in the figure, the management target device list storage unit 113 is configured to record an IP address, a port number, a model ID, and the like for each image forming apparatus 10 to be managed by the device management apparatus 10. ing.

  When device information is not returned in response to device information acquisition requests addressed to ports Y and Z (No in S106), the model determination unit 112 branches the process depending on whether an HTTP response is returned (S108). . That is, even if the request processing unit is not mounted on the target device, if port Y or port Z is opened in the target device, a response at the HTTP level is returned. Therefore, in step S108, it is determined whether the port Y or the port Z is opened in the target device.

  When an HTTP response is returned (Yes in S108), the model determination unit 112 acquires model information from the target device using SNMP (S109). When the acquired model information indicates the model B (Yes in S110), the target device is the image forming apparatus 20C. Therefore, the model determination unit 112 records the IP address of the target device in association with the information indicating that the model B is incompatible with the device management apparatus 10 in the memory device 103 (S111).

  If the acquired model information does not indicate the model B (No in S110), or if an HTTP response is not returned (No in S108), the model determination unit 112 determines the IP address of the target device and the target device. Is recorded in the memory device 103 in association with information indicating that it is not a management target (S131).

  On the other hand, when the value of the network device type is within the range of the value indicating the model A (Yes in S102), the model determination unit 112 transmits a model information acquisition request to the port W (S121). When the device information is not returned from the target device in response to the device information acquisition request (No in S122), the model determination unit 112 transmits the device information acquisition request to the port X (S123). When the device information is returned in response to the device information acquisition request (Yes in S124), or the device information is returned in response to the device information acquisition request addressed to the port W (Yes in S122), the model determination unit 112 Determines that the target device is the image forming apparatus 20A. Therefore, the model determination unit 112 associates the IP address of the target device with, for example, the port number (W or X) for which the device information has been successfully acquired and the model ID of the model A, and records them in the management target device list storage unit 113. (S125).

  When the device information is not returned in response to the device information acquisition request addressed to the port W and X (No in S124), the model determination unit 112 indicates the IP address of the target device and the target device is not managed. The information is associated and recorded in the memory device 103 (S131).

  When the processing of FIG. 4 is completed for all the image forming apparatuses 20, the model determination unit 112 causes the display device 106 to display a screen (processing result screen) including the processing result.

  FIG. 6 is a diagram illustrating a display example of the processing result screen. In the figure, the processing result screen displays an IP address and a processing result for each image forming apparatus 20 to be processed. In the memory device 103, regarding the IP address associated with the information indicating that it is not a management target, “Non-target” is displayed. In the memory device 103, “available” is displayed for the IP address associated with the information indicating that the image forming apparatus 20C is associated. “Available” indicates that it can be managed by installing the request processing unit. For the IP address recorded in the management target device list storage unit 113, “registration success” is displayed.

  In the present embodiment, “registration success” is displayed for the image forming apparatuses 20A and 20B. For the image forming apparatus 20C, “Available” is displayed. In the image forming apparatus 20D, “not applicable” is displayed.

  Next, the alternative process of FIG. 4 will be described. That is, the process of FIG. 4 may be replaced by the process of FIG.

  FIG. 7 is a diagram for explaining a second processing procedure of the registration processing of the management target device.

  The model determination unit 112 transmits a model information acquisition request to the port W (S201). When the device information is not returned from the target device in response to the device information acquisition request (No in S202), the model determination unit 112 transmits a device information acquisition request to the port X (S203). When device information is returned in response to the device information acquisition request (Yes in S204), or when device information is returned in response to a device information acquisition request addressed to port W (Yes in S202), the model determination unit 112 Determines that the target device is the image forming apparatus 20A. Therefore, the model determination unit 112 associates the IP address of the target device with, for example, the port number (W or X) for which the device information has been successfully acquired and the model ID of the model A, and records them in the management target device list storage unit 113. (S205).

  When the device information is not returned in response to the device information acquisition request addressed to the port W and X (No in S204), the model determination unit 112 transmits a device information acquisition request addressed to the port Y (S206). When the device information is not returned from the target device in response to the device information acquisition request (No in S207), the model determination unit 112 transmits a device information acquisition request to the port Z (S208). When the device information is returned in response to the device information acquisition request (Yes in S207) or the device information is returned in response to the device information acquisition request addressed to port Y (Yes in S209), the model determination unit 112 Determines that the target device is the image forming apparatus 20B. Therefore, the model determination unit 112 associates the IP address of the target device with, for example, the port number (Y or Z) for which device information has been successfully acquired and the model ID of the model B, and records them in the management target device list storage unit 113. (S210).

  When device information is not returned in response to device information acquisition requests addressed to ports Y and Z (No in S209), the model determination unit 112 branches the process depending on whether an HTTP response is returned (S211). .

  When an HTTP response is returned (Yes in S211), the model determination unit 112 acquires model information from the target device using SNMP (S212). When the acquired model information indicates the model B (Yes in S213), the target device is the image forming apparatus 20C. Therefore, the model determination unit 112 records the IP address of the target device in association with the information indicating that the model B is incompatible with the device management apparatus 10 in the memory device 103 (S214).

  When the acquired model information does not indicate the model B (No in S213), or when the HTTP response is not returned (No in S211), the model determination unit 112 determines the IP address of the target device and the target device. Is recorded in the memory device 103 in association with information indicating that it is not a management target (S215).

  When the processing in FIG. 7 is completed for all the image forming apparatuses 20, the model determination unit 112 displays the processing result screen 510 on the display device 106.

  The process of FIG. 7 differs from FIG. 4 in that the value of the network device type is not first acquired by SNMP. For example, when many models B are installed in the user environment E1, the performance shown in FIG. 4 can be improved. In the case of FIG. 7, it can be determined that the target device is not model A only after at least two device information acquisition requests are made, whereas in FIG. 4, the target device is model A based on the value of the network device type. This is because it is possible to determine that it is not.

  On the other hand, when many models A are installed in the user environment E1, the performance shown in FIG. 7 can be improved. This is because when the target device is model A, the process of acquiring the value of the network device type is executed more in the case of FIG.

  Therefore, which of FIG. 4 and FIG. 7 is executed may be selectable according to the situation of the user environment E1. For example, the model determination unit 112 displays a screen for selecting which of the method of FIG. 4 and the method of FIG. 7 to use before executing the process, and depending on the selection content on the screen, FIG. You may make it perform FIG. Alternatively, information indicating which method is used may be recorded in the setting file, and FIG. 4 or FIG. 7 may be executed based on the information.

  In FIG. 4, in step S <b> 102, it is determined whether the target device is model A based on the value of the network device type. Therefore, when a new value belonging to the model A is defined as the value of the network device type (when the image forming apparatus 20A having a new value is introduced to the market), the model A is based on the new value. The implementation of the model determination unit 112 needs to be changed so that it is determined that there is. In the user environment E1, the model determination unit 112 needs to be updated.

  However, the model determination unit 112 is not always appropriately updated in the user environment E1. Then, in FIG. 4, there may be a case where the model of the image forming apparatus 20 </ b> A having a new network device type value cannot be determined appropriately. Specifically, the image forming apparatus 20A having a new network device type value may be determined not to be model A in step S102, and finally determined to be out of management.

  Therefore, in FIG. 4, when it is determined in step S <b> 102 that the target device is not the model A, step S <b> 121 and subsequent steps may be executed when it is determined that the target device is not managed. Then, even if it is determined that the image forming apparatus 20A having the new network device type value is not the model A based on the network device type value, the determination based on the port number (processing after S121) ) Can be determined to be model A.

  When the image forming apparatus 20C and the image forming apparatus 20D cannot exist, S108 to S111 in FIG. 4 and S211 to S214 in FIG. 7 do not have to be executed.

  Next, a processing procedure for executing application installation and activation on the management target image forming apparatus 20 will be described. FIG. 8 is a sequence diagram for explaining an application installation and activation processing procedure. In the figure, it is assumed that the user of the image forming apparatus 20 has purchased an application and has already obtained the product key of the application.

  The product key is an identifier that is uniquely issued (or assigned) every time an application is purchased, and is used as information for identifying a license (usage authority) for the application and is a valid purchaser of the application. It is used as information to prove

  Note that the form of purchasing an application is not limited to a predetermined one. You may purchase by the transaction in a shop front, and you may purchase by electronic transaction (for example, using a web site). In the former case, the product key will generally be affixed to a CD-ROM or SD card on which the application is recorded. In the latter case, the product key may be displayed on the Web page when the purchase is confirmed on the Web site where the application is purchased, or the product key may be notified by e-mail. In FIG. 8, it is assumed that the user performs installation and activation (acquisition of a license) related to the purchased application on each image forming apparatus 20 using the device management apparatus 10.

  Upon receiving an application installation start instruction input via the initial screen displayed on the display device 106, the UI control unit 111 of the device management apparatus 10 causes the display device 106 to display a product key input screen (S301). . When the product key of the application to be installed (hereinafter referred to as “current application”) is input by the user via the product key input screen (S302), the package information acquisition unit 114 specifies the input product key. Then, a request for obtaining package information related to the product key is transmitted to the license management server 50 (S303).

  FIG. 9 is a diagram illustrating a configuration example of a product key. As shown in the figure, the product key is data including a unique ID, a product ID, and the like.

  The unique ID is a unique ID that is generated when the product key is generated. That is, the uniqueness of the product key is ensured by the unique ID. The product ID is the product ID of the purchased application. The product ID is uniquely assigned for each application. The product ID and product key are clearly distinguished. That is, the product ID distinguishes between different applications as products, whereas the product key distinguishes the act of purchasing an application. Therefore, a different product key is issued for each purchase for an application related to the same product ID.

  In response to receiving the package information acquisition request, the license management unit 51 of the license management server 50 determines the validity of the product key specified in the acquisition request with reference to the license management table 52.

  FIG. 10 is a diagram illustrating a configuration example of the license management table. In the figure, the license management table 52 has items such as a management number, a product key, a product ID, a machine number, a status, a license validity period, a license validity period, and a license issuance date for each license issued for the application.

  Among these items, the management number, product key, product ID, status, and license validity period are recorded in the license management table 52 when the application is purchased.

  On the other hand, the machine number, the license expiration date, and the license issuance date are recorded according to the issuance of the license (that is, issuance of the license file 90). Also, the status value is updated in response to the issuance of the license.

  The management number is an identifier (number) that is uniquely assigned to each record as a record is generated for the license management table 52. The product key and product ID are as described above. The license validity period indicates a period during which the license is valid.

  When the license file 90 is issued, the machine number of the image forming apparatus 20 designated as a device that uses the application is registered in the machine number. The machine number is identification information (device identifier) for uniquely identifying each image forming apparatus 20. The status is information indicating a license state. In the present embodiment, the license has states of “no license”, “checkout”, and “checkin”. “No license” is a state in which a license has not been issued. Checkout is a state where a license is being used. Check-in is a state in which the license is returned (can be used). The license expiration date is the expiration date of the license (license file 90) calculated based on the license expiration date when the license file 90 is issued. The license issue date is the issue date of the license (license file 90) registered when the license file 90 is issued.

  Using the license management table 52 as described above, for example, the license management unit 51 has a record including the received product key registered in the license management table 52, and the status of the record including the product key is “check”. If the license expiration date of the record including the product key does not exceed the current time (including the case where the license expiration value is not registered), the product key is determined to be valid. In other cases, it is determined that the product key is invalid.

  When it is determined that the product key is invalid, the license management unit 51 returns error information indicating that the product key is invalid to the package information acquisition unit 114. In this case, the package information acquisition unit 114 displays the error information on the display device 106 and stops the installation work.

  When it is determined that the product key is valid, the license management unit 51 returns the information (package information) recorded in the record related to the received product key to the package information acquisition unit 114 (S304). Therefore, the package information includes at least the product ID associated with the product key (that is, the product ID of the current application).

  When the package information is received by the package information acquisition unit 114, the UI control unit 111 of the device management apparatus 10 displays a screen (confirmation screen) including the received package information on the display device 106, and the contents of the current application and The content of the license is confirmed by the user (S305).

  When the user inputs an instruction to continue the installation work (for example, when an OK button is pressed on the confirmation screen), the installation destination receiving unit 116 displays a device selection screen including a list of the image forming apparatuses 20 on the display device 106. And the user selects the image forming apparatus 20 to install the current application (S306). On the device selection screen, a list of image forming apparatuses 20 recorded in the management target device list storage unit 113 is displayed, and one or more image forming apparatuses 20 can be selected from the list.

  Subsequently, the device information acquisition unit 115 transmits a device information acquisition request to each image forming apparatus 20 selected on the device selection screen (S307). At this time, the device information acquisition unit 115 transmits a device information acquisition request for each image forming apparatus 20 based on the IP address and port number recorded in the management target device list storage unit 113. Therefore, the device information acquisition request is transmitted to a port corresponding to the model.

  Upon receiving the device information acquisition request, the request processing unit 21 of each image forming apparatus 20 returns information including the machine number of the image forming apparatus 20 to the device information acquiring unit 115 as device information (S308). Note that the device information may include list information of applications installed in the image forming apparatus.

  The subsequent step S309 is a loop process executed for each image forming apparatus 20 for which device information has been acquired (selected on the device selection screen). The image forming apparatus 20 to be processed in the loop processing is hereinafter referred to as “current device”.

  Subsequently, the package acquisition unit 117 designates the product ID of the current application and the model ID of the current device, and transmits a download request to the package management server 60 (S309-1). The package management unit 61 of the package management server 60 acquires the application corresponding to the specified product ID from the package storage unit 62 corresponding to the model ID, and returns the acquired application to the package acquisition unit 117 (S309-). 2). That is, when the model ID indicates model A, the package management unit 61 acquires an application from the package storage unit 62A. When the model ID indicates the model B, the package management unit 61 acquires an application from the package storage unit 62B.

  If there are a plurality of current applications, the download (S309-1, S309-2) is repeated a plurality of times. The case where there are a plurality of current packages is a case where a plurality of product keys are input in step S301.

Subsequently, the license acquisition unit 118 designates the product key input in step S301, the product ID of the current application, and the machine number of the current device, and transmits a license use request to the license management server 50 ( S309-3)
The license management unit 51 of the license management server 50 updates the license management table 52 and generates a license file 90. In the license management server 50, a record related to the product ID specified in the license use request (hereinafter referred to as “target record”) is an update target. Specifically, the received machine number is recorded for the target record, and the status of the target record is set to “checkout”. In addition, a value indicating the time when the valid period of the target record is added to the current time (current date) is recorded in the valid period of the target record. The current date is recorded on the license issuance date of the target record. By updating the target record, it is possible to prevent a license file from being issued for the same product key beyond the licensable range.

  The license file 90 is generated so as to have a configuration as shown in FIG. 11, for example.

  FIG. 11 is a diagram illustrating a configuration example of a license file. In the figure, the license file 90 includes a product ID, a machine number, and an expiration date. The product ID is a product ID of an application to which a license is granted (permitted to be used) by the license file. The machine number is the machine number of the image forming apparatus 20 that is permitted to use the application related to the product ID by the license file. The expiration date is the expiration date of the license file, that is, the expiration date of the license granted by the license file 90.

  In the product ID of the license file, the product ID related to the product key included in the license use request (product ID of the target record) is recorded. The machine number included in the license issuance request is recorded in the machine number of the license file. The expiration date recorded in the target record is recorded in the expiration date of the license file.

  The license management unit 51 returns the generated license file 50 to the license acquisition unit 118 (S309-4).

  Subsequently, the installation control unit 119 transmits the application (current application) acquired in step S309-2 and the license file 90 acquired in step S309-4 to the current device, and installs and activates the application. The activation is requested from the current device (S309-5). The request is transmitted as a device information acquisition request based on the IP address and port number recorded in the management target device list storage unit 113. Therefore, the request is transmitted to a port corresponding to the model of the current device.

  The request processing unit 21 of the current device installs the application and records the license file 90 in a predetermined storage area.

  In the image forming apparatus 20, the license file 90 is used for a license check by the license check unit 22 that is executed when the installed application is activated. In other words, the license check unit 22 indicates that the license file 90 corresponding to the application to be activated exists, and the machine number of the license file 90 matches the machine number of the image forming apparatus 20 that the application is about to be activated. If it is satisfied that the license file 90 has not expired, activation of the application is permitted. In other cases, activation of the application is not permitted.

  As described above, the device management apparatus 10 according to the present embodiment automatically determines the port number corresponding to the image forming apparatus 20 and the model of the image forming apparatus 20. Further, communication with the image forming apparatus 20 is performed based on the automatically determined port number. Further, an application corresponding to the model of the image forming apparatus 20 that is the installation destination is acquired based on the automatically determined model, and the image forming apparatus 20 is installed with the application.

  Therefore, the user does not need to confirm the port number corresponding to each image forming apparatus 20 or the model of each image forming apparatus 20 or to be aware of the operation according to the model difference. As a result, the work burden of introducing the application to the plurality of image forming apparatuses 20 is reduced.

  As mentioned above, although the Example of this invention was explained in full detail, this invention is not limited to such specific embodiment, In the range of the summary of this invention described in the claim, various deformation | transformation・ Change is possible.

DESCRIPTION OF SYMBOLS 1 Device management system 10 Device management apparatus 20A, 20B, 20C, 20D Image forming apparatus 21 Request processing part 22 License check part 50 License management server 51 License management part 52 License management table 60 Package management server 61 Package management part 62A Package storage part 62B Package storage unit 100 Drive device 101 Recording medium 102 Auxiliary storage device 103 Memory device 104 CPU
105 interface device 106 display device 107 input device 111 UI control unit 112 model determination unit 113 managed device list storage unit 114 package information acquisition unit 115 device information acquisition unit 116 installation destination reception unit 117 package acquisition unit 118 license acquisition unit 119 installation control Part

JP 2008-243180 A

Claims (9)

A determining unit that transmits a predetermined request to the image forming apparatus to a plurality of ports and determines a port to be used for communication with the image forming apparatus according to a port number of a port that has returned a response to the predetermined request. When,
A program introduction support apparatus comprising: an installation control unit that transmits a program installation request to the image forming apparatus to the port determined by the determination unit. The predetermined request is an acquisition request for predetermined information;
The program introduction support apparatus according to claim 1, wherein the determination unit determines a port to be used for communication with the image forming apparatus according to a port number of the port to which the predetermined information is returned. The determination unit determines a model of the image forming apparatus based on a port number of a port which has returned a response to the predetermined request;
Having a program acquisition means for acquiring a program corresponding to the model determined by the determination means;
3. The program introduction support apparatus according to claim 1, wherein the installation control unit transmits the program acquired by the program acquisition unit to the image forming apparatus in response to the installation request. A program introduction support method executed by a computer,
Determination procedure for transmitting a predetermined request to an image forming apparatus to a plurality of ports and determining a port to be used for communication with the image forming apparatus according to a port number of a port which has returned a response to the predetermined request When,
A program introduction support method comprising: an installation control procedure for transmitting a program installation request to the image forming apparatus to the port determined in the determination procedure. The predetermined request is an acquisition request for predetermined information;
5. The program introduction support method according to claim 4, wherein the determination procedure determines a port to be used for communication with the image forming apparatus in accordance with a port number of the port to which the predetermined information is returned. The determination procedure determines a model of the image forming apparatus based on a port number of a port that has returned a response to the predetermined request,
A program acquisition procedure for acquiring a program corresponding to the model determined in the determination procedure;
6. The program introduction support method according to claim 4, wherein the installation control procedure transmits the program acquired in the program acquisition procedure to the image forming apparatus in response to the installation request. On the computer,
Determination procedure for transmitting a predetermined request to an image forming apparatus to a plurality of ports and determining a port to be used for communication with the image forming apparatus according to a port number of a port which has returned a response to the predetermined request When,
A program introduction support program for executing an installation control procedure for transmitting a program installation request to the image forming apparatus to the port determined in the determination procedure. The predetermined request is an acquisition request for predetermined information;
8. The program introduction support program according to claim 7, wherein the determination procedure determines a port to be used for communication with the image forming apparatus according to a port number of the port to which the predetermined information is returned. The determination procedure determines a model of the image forming apparatus based on a port number of a port that has returned a response to the predetermined request,
A program acquisition procedure for acquiring a program corresponding to the model determined in the determination procedure;
The program installation support program according to claim 7 or 8, wherein the installation control procedure transmits the program acquired in the program acquisition procedure to the image forming apparatus in response to the installation request.

Images