JP5768921B2 - License source determination device, license source determination method, license source determination system, and license source determination program - Google Patents

Description

  The present invention relates to a license source determination device, a license source determination method, a license source determination system, and a license source determination program.

  In recent years, there are some image forming apparatuses that are mainly called multifunction peripherals or multifunction peripherals, in which applications can be installed 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. 2004-228561 discloses a technique for collectively introducing application licenses for a plurality of image forming apparatuses.

  In Patent Document 1, it is assumed that there is one license issuer or a common license issuer. On the other hand, the inventor of the present application is considering the construction of a flexible system in which the license issuer is allowed to differ depending on the application. If the license issuer is allowed to differ depending on the application, for example, it becomes easy to change the license issuer from a certain model of the image forming apparatus.

  However, there is a high possibility that the procedure for obtaining a license differs depending on the license issuer. For example, there is a high possibility that communication protocols are different or parameters necessary for obtaining a license are different.

  Then, a client program corresponding to the license issuer is required. This means that the user who acquires the application license needs to use different client programs depending on the license issuer. Such an operation is very burdensome for the user and may adversely affect the promotion of the application.

  The present invention has been made in view of the above points, and even when there are a plurality of license issuers, the license source determination can appropriately suppress an increase in the workload of the license introduction work. An object is to provide a device, a license source determination method, a license source determination system, and a license source determination program.

  Therefore, in order to solve the above-described problem, the license determination device issues an issue for identifying the license data issuer for each license identification information for identifying the license data used by the electronic device for determining whether or not to start the program. Issuer information storage means storing correspondence information with issuer information including original identification information, and the issuer information corresponding to the license identification information specified in the acquisition request in response to the issuer information acquisition request Is obtained using the issuer information storage means, and issuer information providing means for returning the issuer information is provided.

  In such a license determination apparatus, even if there are a plurality of license issuers, it is possible to appropriately suppress an increase in the workload of the license introduction work.

  According to the present invention, even when there are a plurality of license issuers, it is possible to appropriately suppress an increase in the workload of the license introduction work.

It is a figure which shows the system configuration example of the license introduction assistance system in 1st embodiment. 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 license introduction assistance system in 1st embodiment. It is a sequence diagram for demonstrating an example of the process sequence of the license introduction process in 1st embodiment. It is a figure which shows the structural example of an issuer information storage part. It is a figure which shows the structural example of a selection information storage part. It is a figure which shows the system configuration example of the license introduction assistance system in 2nd embodiment. It is a figure which shows the function structural example of the license introduction assistance system in 2nd embodiment. It is a sequence diagram for demonstrating an example of the process sequence of the license introduction process in 2nd embodiment. It is a figure which shows the structural example of a dependence relationship management table. It is a figure which shows the structural example of a license file. It is a figure which shows the structural example of a license management table. It is a figure which shows the structural example of an installation information management table. It is a flowchart for demonstrating the process sequence of the license file generation process by a license management part.

  Hereinafter, embodiments of the present invention will be described with reference to the drawings. FIG. 1 is a diagram illustrating a system configuration example of a license introduction support system according to the first embodiment. In the license introduction support system 1 in FIG. 1, the user environment E <b> 1 is the system environment of the user of the image forming apparatus 20. 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, one or more image forming apparatuses 20, the device management apparatus 10, and the like are connected via a network 30 (regardless of wired or wireless) such as a LAN (Local Area Network). The image forming apparatus 20 is a multifunction device that realizes a plurality of functions such as printing, scanning, copying, and fax transmission / reception in a single housing, and is an example of an electronic device. The image forming apparatus 20 can enhance functions as needed by adding or updating program components (hereinafter simply referred to as “components”).

  The device management apparatus 10 is a computer such as a PC (Personal Computer) that collectively acquires and installs components operating in the image forming apparatus 20 in the user environment E1 and licenses (usage authority) of the components. In the present embodiment, the device management apparatus 10 is an example of a license introduction support apparatus. 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).

  The device management apparatus 10 is connected to the license management servers 50A, 50B, and 50C, and the license source determination apparatus 80 via a network 70 such as a LAN (Local Area Network) or the Internet.

  The license management servers 50A, 50B, and 50C (hereinafter referred to as “license management server 50” when not distinguished from each other) are computers that function as issuers of licenses for components purchased by the user. In the figure, an example in which three license management servers 50 are arranged is shown, but there may be two, or four or more. The plurality of license management servers 50 are not arranged for load distribution. That is, each license management server 50 corresponds to a different license management method. The license management method is a concept that prescribes a processing procedure related to license issuance or the like, or a format of data indicating a license (license file hereinafter). The license management system also defines the data format of the license identifier necessary for issuing a license.

  The license identifier is data that is distributed to a user by purchasing a component license and identifies the purchased license. The license identifier is issued every time a license is purchased. Therefore, even if the license contents match and the licenses are for the same component, the values of the license identifiers are different. Each license management server 50 manages the contents of the license, the use status of the license (whether it has been issued), etc. in association with the license identifier. As a result, the use of components exceeding the scope of the purchased license is appropriately restricted. Hereinafter, the license identifier is referred to as a “product key” for convenience. It should be noted that the distribution of the product key in accordance with the purchase of the license and the management of the license contents and the license usage state associated with the product key are related to the license issuer (license management server 50). It is a common matter. However, the product key format may differ depending on the license management server 50.

  Each license management server 50 may be operated by the same operating entity or may be operated by different operating entities.

  In response to a license issuer inquiry transmitted from the device management apparatus 10, the license source determination device 80 issues a license issuer corresponding to the product key specified in the inquiry (ie, the license management server 50). It is a computer which determines which is.

  FIG. 2 is a diagram illustrating a hardware configuration example of the device management apparatus according to the embodiment of the present invention. In FIG. 1, a device management apparatus 10 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 connected to each other via a bus B. Device 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.

  Each license management server 50 and license source determination device 80 may have the same hardware configuration as that in FIG. However, each license management server 50 and the license source determination device 80 do not necessarily include the display device 106 and the input device 107.

  FIG. 3 is a diagram illustrating a functional configuration example of the license introduction support system according to the first embodiment. In FIG. 1, the device management apparatus 10 includes a common processing unit 11, a license introduction processing unit 12A, a license introduction processing unit 12B, and a license introduction processing unit 12C (hereinafter referred to as “license introduction processing unit 12” unless they are distinguished from each other). .) Etc. These units are realized by processing executed by the CPU 104 by a program installed in the device management apparatus 10.

  The common processing unit 11 executes commonly required processing regardless of the license issuer. In the figure, the common processing unit 11 includes a request reception unit 111, a device information acquisition unit 112, an issuer information acquisition unit 113, a selection unit 114, a selection information storage unit 115, and the like.

  The request receiving unit 111 receives a request for introducing a license to the image forming apparatus 20. In the license introduction request, the product key and the destination image forming apparatus 20 are designated. The device information acquisition unit 112 acquires device information from the image forming apparatus 20. The device information includes model information indicating the model of the image forming apparatus 20, information regarding components installed in the image forming apparatus 20, and the like. The issuer information acquisition unit 113 acquires information on the issuer of the license corresponding to the product key input by the user (hereinafter referred to as “issuer information”) from the license source determination device 80. The selection unit 114 selects the license introduction processing unit 12 corresponding to the issuer information, and instructs the selected license introduction processing unit 12 to execute the process. The selection information storage unit 115 stores information for the selection unit 114 to determine the license introduction processing unit 12 corresponding to the issuer information, for example, using the auxiliary storage device 102. More specifically, the selection information storage unit 115 stores correspondence information between the issuer information and the license introduction processing unit 12.

  Each license introduction processing unit 12 executes a license acquisition process from the license management server 50 corresponding to the license introduction processing unit 12 in response to an instruction from the selection unit 114. In addition, the license introduction processing unit 12 executes a license introduction process for the image forming apparatus 20 designated as the license introduction destination.

  In the present embodiment, each license introduction processing unit 12 corresponds to the license management server 50 having the same alphabet (A, B, or C) at the end of the code. The reason why the license introduction processing unit 12 exists for each license management server 50 is that the processing procedure for obtaining the license, the communication protocol, and the like may be different for each license management server 50. Further, depending on which license management server 50 has issued the license, the processing procedure and communication protocol for introducing the license into the image forming apparatus 20 may be different. In the present embodiment, a file storing data (license data) in which a license is embodied is referred to as a license file.

  The license source determination device 80 includes an issuer information providing unit 81, an issuer information storage unit 82, and the like. In response to the issuer information acquisition request transmitted from the issuer information acquisition unit 113, the issuer information providing unit 81 returns the issuer information related to the product key specified in the acquisition request. The issuer information storage unit 82 stores correspondence information between product keys and issuer information.

  Each image forming apparatus 20 may have a different license management method depending on the model. Accordingly, each image forming apparatus 20 accepts introduction of a license file from the device management apparatus 10 in accordance with a processing procedure or communication protocol corresponding to the license management method that the image forming apparatus 20 supports. In addition, each image forming apparatus 20 determines whether or not to activate a component that is activated on its own device, based on the license file, according to a processing procedure according to the license management method that it corresponds to.

  The processing procedure of the license introduction support system 1 according to the first embodiment will be described below. FIG. 4 is a sequence diagram for explaining an example of the processing procedure of the license introduction processing in the first embodiment. In the figure, it is assumed that the user of the image forming apparatus 20 has purchased a component license and has already obtained a product key related to the license. However, it is assumed that the license file relating to the license is not yet introduced into the image forming apparatus 20.

  The request reception unit 111 of the device management apparatus 10 receives an input of a license introduction start instruction from the user via the initial screen displayed on the display device 106 (S101). Subsequently, the request reception unit 111 displays a device selection screen including a list of the image forming apparatuses 20 on the display apparatus 106, and allows the user to select the image forming apparatus 20 as a license file introduction destination (S102). A plurality of image forming apparatuses 20 can be selected on the device selection screen. In the device selection screen, the image forming apparatus 20 whose IP address, host name, and the like are stored in advance in the auxiliary storage device 102 is displayed. Alternatively, the request reception unit 111 automatically searches the image forming apparatus 20 connected to the network 30 by issuing a broadcast or the like on the network 30, and the host name or the like of the searched image forming apparatus 20 is obtained. You may display on an apparatus selection screen.

  Subsequently, the device information acquisition unit 112 transmits a device information acquisition request to each image forming apparatus 20 selected on the device selection screen (S103). Receiving the device information acquisition request, each image forming apparatus 20 returns the device information including the list information of components installed in the image forming apparatus 20 and the machine number and model information of the image forming apparatus 20 (S104). The machine number is identification information for identifying the machine body of each image forming apparatus 20. The machine number may be unique for each machine of the image forming apparatus 20. The component list information is, for example, a list of component identifiers (hereinafter referred to as “component ID”).

  Subsequently, the request reception unit 111 displays a product key input screen on the display device 106, and receives an input of a product key from the user via the product product key input screen (S105).

  Subsequently, the issuer information acquisition unit 113 designates the input product key and the model information included in the device information acquired in step S104, and issues an issuer information acquisition request to the license source determination device. (S106). That is, for the license file related to the product key, an appropriate license issuer (that is, the license file acquisition destination) when the image forming apparatus 20 related to the model indicated by the model information is the installation destination is the license source. The determination device 80 is inquired.

  Subsequently, the issuer information providing unit 81 of the license source determination device 80 searches the issuer information storage unit 82 for issuer information corresponding to the product key and the model information (S107).

  FIG. 5 is a diagram illustrating a configuration example of the issuer information storage unit. In the figure, an issuer information storage unit 82 stores issuer information (such as an issuer product key and an issuer URL) for each combination of an input product key and model information.

  The input product key and model information are the product key and model information that are collated with the product key and model information specified in the issuer information acquisition request. The reason why the model information is included in the information for specifying the issuer information is that it is assumed that the license issuer differs depending on the model for the same product key. Therefore, model information may be removed in a system environment in which such a case cannot occur.

  The issuer product key is a product key managed by the issuer of the license corresponding to the combination of the input product key and the model information. For example, the product key numbering system may be different for each license management server 50. In addition, even for the same component, the license issuer may differ depending on the model of the image forming apparatus 20 that is the installation destination (use destination) of the license of the component. On the other hand, there is a case where a license relating to a product key that has already been issued in the market is not used in any type of image forming apparatus 20 (ie, a license has not been issued). That is, the process of FIG. 4 may not be executed for the product key.

  In such a situation, when the license management server 50 that has already been issued in the market and cannot interpret the product key input by the user (not managed) is the license issuer, the license management server 50 The license for the product key cannot be issued. This means that the user cannot use the license based on the purchased license key. Therefore, an issuer product key corresponding to the license issuer is stored in association with a product key (input product key) that may already be issued in the market.

  Regarding the license management server 50 that can understand a product key that has already been issued to the market, the same value as the input product key is registered as the product key for the issuer. For example, the records in the first row, the fourth row, and the seventh row in FIG. 5 are examples.

  The issuer URL is a URL (Uniform Resource Locator) of the license management server 50 that is the license issuer. The issuer URL is an example of issuer identification information in the present embodiment. The issuer identification information is not necessarily a URL. Any information may be used as long as the license management server 50 can be identified according to the communication protocol used by the license management server 50 as a license issuer.

  In step S107, the issuer information storage unit 82 is searched for a record including the input product key and model information that matches the product key and model information specified in the issuer information acquisition request.

  Subsequently, the issuer information providing unit 81 acquires the issuer product key and the issuer URL of the retrieved record from the issuer information storage unit 82 (S108). Subsequently, the issuer information providing unit 81 returns the issuer information including the issuer product key and the issuer URL to the device management apparatus 10 (S109).

  Subsequently, the selection unit 114 selects the license introduction processing unit 12 to delegate the license introduction processing based on the received issuer URL and the selection information storage unit 115 (S110).

  FIG. 6 is a diagram illustrating a configuration example of the selection information storage unit. In the figure, the selection information storage unit 115 stores correspondence information between the issuer URL (that is, identification information of the license issuer) and the license introduction processing unit 12. That is, the selection information storage unit 115 stores the identification information of the license introduction processing unit 12 for each issuer URL. The identification information of the license introduction processing unit 12 is, for example, a program file name of a program for causing the device management apparatus 10 to function as the license introduction processing unit 12. In consideration of the increase / decrease of the license source, it is desirable that the program is a dynamically linkable program (for example, DLL (Dynamic Link Library)). By doing so, when the number of license management servers 50 increases, a program related to the license introduction processing unit 12 corresponding to the new license management server 50 can be added without changing the source code of the existing part. It is.

  In step S <b> 110, the selection unit 114 selects the license introduction processing unit 12 associated with the received issuer URL, and sends device information, issuer URL, and issuer to the license introduction processing unit 12. Specify the product key for use and instruct the execution of the process.

  Subsequently, the license introduction processing unit 12 instructed to execute the process introduces the license to the image forming apparatus 20 according to the processing procedure implemented by itself (that is, the processing procedure related to the license management method supported by itself). Execute the process.

  For example, when the license introduction processing unit 12A is selected, the license introduction processing unit 12A transmits a license use request to the license management server 50A by designating an issuer product key or the like (S121). The license management server 50A generates a license file indicating the license related to the product key, and returns the license file (S122). The license introduction processing unit 12A transmits the returned license file to the image forming apparatus 20 (S123). As a result, the user can use the licensed component related to the license file in the image forming apparatus 20 within the scope of the license (for example, the expiration date).

  When the license introduction processing unit 12B is selected, the license introduction processing unit 12B designates an issuer product key and transmits a license use request to the license management server 50B (S131). The license management server 50B generates a license file indicating the license related to the product key, and returns the license file (S132). The license introduction processing unit 12B transmits the returned license file to the image forming apparatus 20 (S133). As a result, the user can use the licensed component related to the license file in the image forming apparatus 20 within the scope of the license (for example, the expiration date).

  Although the case where the license introduction processing unit 12C is selected is not shown, this is for convenience. When the license introduction processing unit 12C is selected, the same processes as those in steps S121 to S123 or S131 to S133 may be executed using the license management server 50C.

  As described above, according to the first embodiment, the license issuer is automatically determined based on the product key input by the user, and the license file is acquired from the issuer. Therefore, the user does not need to be aware of the license issuer. Specifically, there is no need to use different client-side applications depending on the license issuer. Therefore, according to the first embodiment, even when there are a plurality of license issuers, it is possible to appropriately suppress an increase in the workload of the license introduction work.

  The device management apparatus 10 may have the function of the license source determination apparatus 80. Specifically, the device management apparatus 10 may include an issuer information providing unit 81 and an issuer information storage unit 82.

  By the way, the processing procedure executed by each license introduction processing unit 12 is not necessarily common. Steps S121 to S123 or S131 to S133 shown in FIG. 4 are only an outline. That is, each step indicates a basic information or data flow realized by the processing executed by each license introduction processing unit 12. Therefore, the description of the step has a relatively high level of abstraction. Therefore, as an example, a specific embodiment of the license management method by the license management server 50A will be described below.

  FIG. 7 is a diagram illustrating a system configuration example of a license introduction support system according to the second embodiment. In FIG. 7, the same parts as those in FIG.

  In FIG. 7, the component management server 60 is connected to the network 70. The component management server 60 is a computer that manages the entity of the component whose license is managed by the license management server 50A. In the second embodiment, the license introduction processing unit 12 </ b> A downloads a component from the component management server 60 and installs it in the image forming apparatus 20 with the introduction of the license into the image forming apparatus 20. Therefore, in the second embodiment, the component management server 60 corresponding to the license management server 50A is arranged.

  In FIG. 7, the license management servers 50B and 50C are not shown, but this is for convenience.

  FIG. 8 is a diagram illustrating a functional configuration example of the license introduction support system according to the second embodiment. 8, the same parts as those in FIG. 3 are denoted by the same reference numerals, and the description thereof will be omitted as appropriate.

  In FIG. 1, the image forming apparatus 20 includes a request processing unit 21, a license check unit 22, an installation information management table 23, and the like. In response to a request from the device management apparatus 10, the request processing unit 21 transmits device information, installs components, installs a license file 90, and the like.

  The license file 90 is a license file issued from the license management server 50A. The license check unit 22 determines whether or not to use the component based on the license file 90 when the component is used in the image forming apparatus 20. The installation management table 23 is a table for managing information such as components installed in the image forming apparatus 20 and is stored in a storage device of the image forming apparatus 20.

  The license management server 50A includes a license management unit 51, a license management table 52, and the like. The license management unit 51 issues a license related to a component (that is, generates a license file). The license management table 52 is a table in which the usage status of the component license is recorded, and is stored in the storage device of the license management server 50A.

  The component management server 60 includes a validity verification unit 61, a component management unit 62, a dependency relationship management table 63, a component storage unit 64, and the like.

  The validity verification unit 61 refers to the dependency management table 63 to determine whether or not the dependency of the component to be installed is resolved by the component already installed in the image forming apparatus 20 that is the installation destination. Judgment. Specifically, the validity verification unit 61 determines whether or not a component or the like on which the component to be installed is dependent has already been installed in the image forming apparatus 20.

  The component management unit 62 manages component entities (for example, files) recorded in the component storage unit 64. For example, in response to receiving a component download request, the component management unit 62 acquires the component from the component storage unit 64 and returns it to the request source.

  The dependency relationship management table 63 is a table in which information indicating the dependency relationship between components is recorded, and is stored in the storage device of the component management server 60. The component storage unit 64 is a storage area that stores component entities in association with respective component IDs in the storage device of the component management server 60.

  The device management apparatus 10 is detailed with respect to the license introduction processing unit 12A. In the figure, the license introduction acquisition unit A includes a validity confirmation unit 121, a component acquisition unit 122, a license acquisition unit 123, an installation control unit 124, and the like.

  The validity confirmation unit 121 causes the component management server 60 to verify the validity of installation on the image forming apparatus 20 that is the installation destination for the component that is the installation target.

  The component acquisition unit 122 downloads (acquires) the component to be installed from the component management server 60. The license acquisition unit 123 acquires the license file 90 related to the component to be installed from the license management server 50A. The installation control unit 124 transmits the component and license file 90 to the image forming apparatus 20.

  The processing procedure of the license introduction support system 1 according to the second embodiment will be described below. In the second embodiment, the details of the processing procedure corresponding to the portion described in a simplified manner as steps S121 to S123 in FIG. 4 (that is, the processing procedure executed by the license introduction processing unit 12A after step S110). Explained. Note that steps S101 to S110 are also executed in the second embodiment, but the description thereof is omitted.

  FIG. 9 is a sequence diagram for explaining an example of the processing procedure of the license introduction processing in the second embodiment.

  Step S201 is a loop process executed for each image forming apparatus 20 from 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”.

  In step S 201-1, the validity checking unit 121 requests a validity verification including the component ID of the component related to the license to be introduced (hereinafter referred to as “current component”) and the device information of the current device. Is transmitted to the component management server 60. Here, “validity” refers to the validity of installing the current component on the current device. The validity verification unit 61 of the component management server 60 verifies the validity with reference to the dependency management table 63 in response to reception of the validity verification request.

  FIG. 10 is a diagram illustrating a configuration example of the dependency relationship management table. In the same figure, in the dependency relationship management table 63, for each component, the component ID of the component and the component ID of the component on which the component depends (the dependency destination of the component) are registered. A plurality of component IDs of the dependence destination components may be registered. In the figure, “0” indicates that there is no dependent component.

  In the validity verification, the validity verification unit 61 specifies a component to which the current component depends (hereinafter referred to as “dependence destination component”) based on the component ID of the current component and the dependency management table 63. . When there is a dependency destination component, the validity verification unit 61 determines whether or not the component ID of the dependency destination component is included in the device information. When the component IDs of all the dependence destination components are included in the device information, the validity verification unit 61 determines that there is validity. If there is at least one dependency destination component (hereinafter referred to as “unresolved component”) that is not included in the device information, the validity verification unit 61 determines that there is no validity. There can be a plurality of dependent components for one component. Also, the dependency search is performed recursively.

  Subsequently, the validity verification unit 61 returns a validity verification result to the validity confirmation unit 121 (S201-2). When it is determined that there is no validity, the verification result includes the component ID of the unresolved component.

  Subsequently, the component acquisition unit 122 specifies the component ID of the current component and transmits a download request to the component management server 60 (S201-3). The component management unit 62 of the component management server 60 acquires the component corresponding to the specified component ID from the component storage unit 64, and returns the acquired component to the component acquisition unit 122 (S201-4). If a verification result indicating that there is no validity is received in step S201-2, the unresolved component is also downloaded.

  Subsequently, the license acquisition unit 123 specifies the product key (issuer product key) acquired in step S109 of FIG. 4, the component ID of the current component, and the machine number of the current device, and uses the license. A request (request for acquiring the license file 90) is transmitted to the license management server 50A (S201-5).

  The license management unit 51 of the license management server 50A generates a license file 90 based on the information included in the license use request and the license management table 52, and returns the generated license file 90 to the license acquisition unit 123. (S201-6).

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

  In the component ID of the license file 90, the component ID related to the product key included in the license use request is registered. The machine number included in the license use request is registered in the machine number of the license file 90. The expiration date of the license file 90 includes a time period obtained by adding the effective period registered in the license management table 52 to the product key and component ID included in the license use request (for example, Date) is registered.

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

  Among these items, the management number, product key, component ID, status, license type, and license validity period are recorded in the license management table 52 when a license is purchased. That is, when purchasing a license, the component ID, license type, and license expiration date are designated by the user.

  The license form is information indicating whether the license relating to the component is a sold-out type, a timed license, a trial license, or the like. The sold-out type is a license that can be used indefinitely after purchase. The timed license is a license that is valid (usable) only for a predetermined period. The trial license is a license for use as a trial. The license validity period is an attribute that is valid when the license form is a timed license or trial license, and indicates the period during which the license is valid.

  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) assigned to each record as a record is generated for the license management table 52. The product key and component ID are as described above.

  When the license file 90 is issued, the machine number of the image forming apparatus 20 designated as the device that uses the component is registered in the machine number. The status is information indicating the usage status of the license. In the present embodiment, the license has usage states of “no license”, “check-out”, and “check-in”. “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 released (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.

  In the figure, the product keys and component IDs of the records with management numbers 1 to 3 are common. This indicates that the product related to the product key “KEY001” is a product related to a volume license with a license number of three. The volume license refers to a license that allows the same component to be used in a plurality of image forming apparatuses 20 corresponding to the number specified in the volume license.

  Note that the license acquisition unit 123 executes Step S201-5 when the component acquisition unit 122 succeeds in acquiring (downloading) the component. That is, the license acquisition unit 123 does not acquire the license file 90 when the component cannot be normally acquired. If a component cannot be obtained, it cannot be installed. Nevertheless, if the license file 90 related to the component is acquired, it is assumed that the use of the license is started for the component that is not actually used, which causes a disadvantage to the user. is there.

  Subsequently, when an unresolved component is acquired in step S201-4, the installation control unit 124 transmits the unresolved dependency component to the current device, and requests the current device to install the unresolved component (S201). -7). The request processing unit 21 of the current device installs the unresolved component and records information (component ID or the like) regarding the unresolved component in the installation information management table 23.

  FIG. 13 is a diagram illustrating a configuration example of the installation information management table. In the figure, in the installation information management table 23, a component ID, a version, an activation flag, an expiration date, and the like are registered for each component installed in the image forming apparatus 20.

  The version is the version of the component. The activation flag indicates whether the component has been activated (whether it has been activated). Activation means installing a license and making a component available. The license expiration date is the expiration date of the license introduced for the component (the expiration date of the license file 90).

  Subsequently, the installation control unit 124 inquires of the current device about the installation result of the unresolved component (S201-8). The inquiry (polling) is repeated until the installation is completed in the current device and the installation result is returned.

  The reason why the unresolved component is installed first is to avoid failure of component installation due to the fact that the dependency destination component is not installed.

  Subsequently, the installation control unit 124 transmits the component acquired in step S201-4 (current component) and the license file 90 acquired in step S204-6 to the current device, and installs and activates the component. The activation is requested to the current device (S201-9). The request processing unit 21 of the current device installs the component, and records the component information (component ID or the like) in the installation information management table 23. The request processing unit 21 records the license file 90 in a predetermined storage area.

  Subsequently, the installation control unit 124 inquires of the current device about the component installation result (S201-10). The inquiry (polling) is repeated until the installation is completed in the current device and the installation result is returned.

  Next, details of processing executed by the license management unit 51 of the license management server 50A in response to the license use request in step S201-5 in FIG. 9 will be described.

  FIG. 14 is a flowchart for explaining the processing procedure of the license file generation processing by the license management unit. In FIG. 14, one product key is described as a processing target. Therefore, when a plurality of product keys are received, step S302 and subsequent steps are executed for each product key.

  In step S301 (step S201-5 in FIG. 9), the license management unit 51 receives a license use request including the product key, component ID, and machine number from the installation control unit 124. Subsequently, the license management unit 51 determines whether or not the license relating to the product key can be used. Specifically, the license management unit 51 confirms whether or not the received product key is registered in the license management table 52 (S302). When the product key is registered (Yes in S302), the license management unit 51 confirms whether the same machine number as the received machine number is registered in the license management table 52 for the product key. (S303). When the same machine number is not registered (No in S303), the license management unit 51 indicates that the record with the status “check-in” among the records related to the product key and the received component ID is the license management table 52. (S304). When there is a corresponding record (Yes in S304), the license management unit 51 records the machine number received for the record, and sets the status of the record to “checkout” (S306). That is, it is recorded that the license corresponding to the product key is being used. In addition, when the “license validity period” is recorded in the record (that is, when the record is a record corresponding to the timed license), the license management unit 51 adds the license validity period to the current date and time. Is recorded in the record as the license expiration date.

  Subsequently, the license management unit 51 generates a license file 90 (see FIG. 11) including the component ID, the machine number, and the expiration date in the record (S307). The license file 90 is generated for each record of the license management table 52, that is, for each license for the component. Subsequently, the license management unit 51 returns the generated license file 90 to the installation control unit 124 of the device management apparatus 10 (S308).

  On the other hand, if there is a record in which the same machine number as the machine number received for the product key is registered (Yes in S303), the license management unit 51 determines whether the status of the record is “check-in”. It is confirmed whether or not (S305). When the status is “check-in” (Yes in S305), the processes in and after step S306 are executed.

  If there is no record related to the product key in the license management table 52 (No in S302), among the records related to the product key and the received component ID, a record whose status is “check-in” is the license management table. If not in 52 (No in S304), or if the status of the record in which the same machine number as the machine number received for the product key is registered is not “check-in” (No in S305), license management If the unit 51 detects an error, the license file 90 is not generated, that is, the license is not issued.

  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 component is activated. That is, the license check unit 22 confirms that the license file 90 corresponding to the component to which the component to be activated belongs, the machine number of the license file 90 and the machine number of the image forming apparatus 20 that the component is about to be activated. Are satisfied and that the license file 90 has not expired, activation of the component is permitted. Otherwise, the component is not allowed to start.

  The second embodiment shows an example of a processing procedure based on the license management method by the license management server 50A. Therefore, when another license management server 50 is the license issuer, a different processing procedure can be executed. For example, in the second embodiment, component installation is automatically executed with the introduction of a license. However, component installation may be separately required. Further, the configuration of the license file 90 may differ depending on the license issuer. Accordingly, the functional configuration of the image forming apparatus 20 may also vary depending on the license issuer.

  However, a common matter among the license issuers is that the use state of the license is managed using a storage unit such as the license management table 52. This is to prevent the use of components that exceed the scope of the purchased license.

  In view of such a situation, when the first embodiment is simply implemented, there is a possibility that components may be used beyond the scope of the license. Specifically, issuer information relating to the same input product key “1111111111” is recorded in the first and second lines of the issuer information storage unit 82 in FIG. 5. The model information on the first line is “A”, and the model information on the second line is “B”. The issuer URL on the first line is a URL related to the license management server 50A, and the issuer URL on the second line is a URL related to the license management server 50B. Accordingly, the license issuer relating to the input product key differs depending on the model of the image forming apparatus 20 to which the license is introduced. It is assumed that the number of licenses (volume number) related to the product key is “1”.

  In the above situation, it is assumed that a license relating to the product key “1111111111” is introduced to the image forming apparatus 20 of model B. As a result, the license management server 50B records that the license related to the product key is in use. Here, since the number of licenses of the license is “1”, further introduction of licenses based on the product key should be prohibited.

  However, in the license management table 52 of the license management server 50A, the status of the license remains “check-in”. Then, if a license introduction process related to the product key is executed for the model A image forming apparatus 20, the license is introduced into the image forming apparatus 20.

  Therefore, in order to suppress the occurrence of such a situation, each license management server 50 may mutually notify the product key for which the license has been issued when issuing the license.

  Specifically, the license management server 50 that has received the license use request inquires the license source determination device 80 about the issuer information related to the product key specified in the use request. The license management server 50 issues a license by specifying the product key for issuer included in the issuer information to the other license management server 50 related to the issuer information returned from the license source determination device 80. To be notified. Upon receiving the notification, the other license management server sets the usage status for one license related to the issuer product key specified in the notification. By doing so, the license usage status can be synchronized between the license management servers 50. As a result, the use of components beyond the scope of the license can be suppressed.

  Further, there are cases where it is difficult to construct a mechanism for exchanging information between the license management servers 50, such as when the operating entities of the license management servers 50 are different. In consideration of such a case, the following processing procedure may be executed.

  In step S109 of FIG. 4, the issuer information providing unit 81 of the license source determination device 80 returns all issuer information related to the product key specified in the issuer information acquisition request (S106). That is, the issuer information to be returned is not limited based on the model information.

  In the device management apparatus 10 that has received the issuer information, the selection unit 114 issues an execution instruction to each license introduction processing unit 12 corresponding to each issuer information. In other words, the execution instruction target is not limited to one license introduction processing unit 12. As a result, each license introduction processing unit 12 performs license introduction processing in parallel. However, the license is introduced to the specific image forming apparatus 20 selected in step S102 in FIG. Accordingly, when the model of the image forming apparatus 20 is model A, communication with the license introduction processing unit 12A is possible, but communication with other license introduction processing units 12 cannot be performed. Therefore, the license introduction is successful only for the license introduction processing unit 12A. On the other hand, each license introduction processing unit 12 has already received a license from the corresponding license management server 50. That is, it is recorded in each license management server 50 that the license relating to the same product key is in use. As a result, the license usage status can be substantially synchronized between the license management servers 50.

  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 License introduction support system 10 Device management apparatus 11 Common processing part 12A, 12B, 12C License introduction process part 20 Image forming apparatus 21 Request processing part 22 License check part 23 Installation information management table 20 Image forming apparatus 50A, 50B, 50C License management Server 51 License management unit 52 License management table 60 Component management server 61 Validity verification unit 62 Component management unit 63 Dependency management table 64 Component storage unit 80 License source determination device 81 Issuer information provision unit 82 Issuer information 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 request reception unit 112 device information acquisition unit 113 issuer information acquisition unit 114 selection unit 115 selection information storage unit 121 validity check unit 122 component acquisition unit 123 license acquisition unit 124 installation control unit B bus

JP 2008-243179 A

Claims (9)

Corresponding information with issuer information including issuer identification information for identifying the issuer of the license data, for each license identification information for identifying license data used by the electronic device for determining whether to permit or not to start the program Stored issuer information storage means;
In response to the issuer information acquisition request, the issuer information corresponding to the license identification information specified in the acquisition request is acquired using the issuer information storage unit, and the issuer information is returned. A license source determination device having information providing means. Receiving means for receiving input of first license identification information for receiving issuance of the license data;
The issuer information that specifies the first license identification information, sends the issuer information acquisition request to the previous issuer information providing means connected via the network, and is returned from the issuer information providing means Issuer information acquisition means for receiving,
The license data corresponding to the first license identification information is acquired from a license management apparatus according to the issuer information among a plurality of license management apparatuses connected via a network, and the license data is transferred to the electronic device. A license introduction processing means to send;
The license source determination apparatus according to claim 1, comprising: The license introduction processing means is provided for each license management device,
Selection information storage means for storing correspondence information between the issuer information and the license introduction processing means;
Selection means for selecting the license introduction processing means corresponding to the issuer information received by the issuer information acquisition means using the selection information storage means;
3. The license source determination device according to claim 2, wherein the license introduction processing unit selected by the selection unit acquires the license data from the license management device and transmits the license data to the electronic device. The issuer information includes second license identification information corresponding to the license management apparatus related to the issuer identification information included in the issuer information,
4. The license source determination apparatus according to claim 2, wherein the license introduction processing unit acquires the license data corresponding to the second license identification information from the license management apparatus. The issuer information acquisition means specifies the issuer of the license data by designating the first license identification information and the model information of the electronic device into which the license data related to the first license identification information is introduced. Sending an issuer information acquisition request including the issuer identification information to the issuer information providing means,
The issuer information storage means stores correspondence information with the issuer information for each combination of the first license identification information and the model information of the electronic device,
The issuer information providing unit issues the issuer information corresponding to the first license identification information and the model information specified in the acquisition request in response to the acquisition request from the issuer information acquisition unit. 5. The license source determination device according to claim 2, wherein the license source determination device acquires the source information by using the original information storage unit and returns the issuer information. An acquisition request receiving procedure for receiving an issuer information acquisition request including issuer identification information for identifying an issuer of license data used by an electronic device for permission to start a program;
The computer executes the issuer information provision procedure for acquiring the issuer information corresponding to the license identification information specified in the acquisition request using an issuer information storage unit and returning the issuer information,
The issuer information storage means stores, for each license identification information for identifying the license data, correspondence information with issuer information including issuer identification information for identifying the issuer of the license data. Original judgment method. A license determination system including one or more electronic devices and a license source determination device connected to the electronic devices via a network,
The license source determination device includes:
Correspondence information with issuer information including issuer identification information for identifying the issuer of the license data, for each license identification information for identifying the license data used by the electronic device for determining whether or not to start the program Issuer information storage means storing
In response to the issuer information acquisition request, the issuer information corresponding to the license identification information specified in the acquisition request is acquired using the issuer information storage unit, and the issuer information is returned. A license source determination system having information providing means. A license determination system including one or more information processing devices,
Corresponding information with issuer information including issuer identification information for identifying the issuer of the license data, for each license identification information for identifying license data used by the electronic device for determining whether to permit or not to start the program Stored issuer information storage means;
In response to the issuer information acquisition request, the issuer information corresponding to the license identification information specified in the acquisition request is acquired using the issuer information storage unit, and the issuer information is returned. A license source determination system having information providing means. An acquisition request receiving procedure for receiving an issuer information acquisition request including issuer identification information for identifying an issuer of license data used by an electronic device for permission to start a program;
Obtaining the issuer information corresponding to the license identification information specified in the acquisition request using an issuer information storage unit, and causing the computer to execute an issuer information provision procedure for returning the issuer information;
The issuer information storage means stores, for each license identification information for identifying the license data, correspondence information with issuer information including issuer identification information for identifying the issuer of the license data. Original judgment program.

Images