JP2008243179A - Information processing system and information processing method - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To provide an information processing system and an information processing method, efficiently setting a license of an application to a plurality of pieces of equipment. <P>SOLUTION: This information processing system includes a plurality of pieces of equipment capable of performing the application and an information processor connected to the equipment through a network. The system includes a license status information obtaining means for obtaining the license status information of the application installed in the equipment from the plurality of pieces of through the network, a license data obtaining means for obtaining license data for permitting the use of the application based on the license status information through the network, and a license data delivery means for delivering the license data to the plurality of pieces of equipment, respectively. <P>COPYRIGHT: (C)2009,JPO&INPIT

Description

  The present invention relates to an information processing system and an information processing method, and more particularly to an information processing system and an information processing method for setting a license for an application executed in a device.

In recent years, there are image forming apparatuses mainly called multifunction peripherals or multi-function peripherals that can develop and install new applications after shipment (for example, Patent Document 1). The usage forms of such applications are diversified, and there are users who need to be able to use only for a predetermined period and users who need to be able to use only specific functions among all functions of the application. If an application license can be set for the image forming apparatus in accordance with the usage form of each user, not only is this convenient for the user, but the business opportunity can also be expected for the application seller.
JP 2005-269619 A

  However, in a user environment using a large number of image forming apparatuses, there is a problem that it is very complicated to perform such setting for each image forming apparatus. Such a problem is considered to be a common problem not only for image forming apparatuses but also for devices that can execute applications.

  SUMMARY An advantage of some aspects of the invention is that it provides an information processing system and an information processing method capable of efficiently setting application licenses for a plurality of devices.

  Therefore, in order to solve the above problem, the present invention provides an information processing system including a plurality of devices that can execute an application and an information processing device that is connected to the devices via a network. The license status information acquisition means for acquiring the license status information of the application installed in the device via the network and the license data permitting the use of the application based on the license status information are connected via the network. License data acquisition means for acquiring from a computer, and license data distribution means for distributing the license data to each of the plurality of devices.

  In such an information processing system, it is possible to efficiently set application licenses for a plurality of devices.

  According to the present invention, it is possible to provide an information processing system and an information processing method capable of efficiently setting application licenses for a plurality of devices.

  Hereinafter, embodiments of the present invention will be described with reference to the drawings. FIG. 1 is a diagram illustrating a configuration example of a license management system according to an embodiment of the present invention. In FIG. 1, the license management system includes a user site A, a license issuance site B, a license registration site C, and the like.

  The user site A is a user environment of the image forming apparatus (device), and corresponds to the user's office or the like. Therefore, a plurality of user sites A can exist depending on the user of the image forming apparatus. In the user site A, the license acquisition apparatus 10 and one or more MFPs 20 are connected via a network 30 (whether wired or wireless) such as a LAN (Local Area Network). An MFP (Multifunction Peripheral) 20 is an image forming apparatus generally called a multifunction peripheral or a multifunction peripheral. That is, the MFP 20 includes hardware for realizing a plurality of functions such as a copy function, a printer function, a scanner function, and a fax function in a single casing. Various applications using these functions can be installed in the MFP 20. However, the image forming apparatus to which the present invention is applied is not limited to a multifunction peripheral, and it is sufficient that at least an application can be installed and executed. Therefore, it may be an image forming apparatus that realizes a single function such as a copier, a facsimile, a printer, or a scanner.

  The license acquisition apparatus 10 is a computer such as a PC (Personal Computer) for collectively acquiring licenses (usage authority) of applications operating in the MFP 20 at the user site A. In other words, various applications installed in the MFP 20 can be used with the license acquired by the license acquisition apparatus 10.

  The license issuance site B is an environment in which a license for an application of the MFP 20 used at the user site A is issued to the user site A. For example, the license issuance site B is operated by the manufacturer of the MFP 20. A license server 50 is installed in the license issuance site B. The license server 50 is a computer that executes generation and issuance of a license.

  The license registration site C is an environment for requesting the license issuance site B to register information related to the license managed application and information related to the license of the application (license information). For example, the license registration site C corresponds to the vendor of each application. Therefore, a plurality of license registration sites C can exist depending on the vendor of the application. A license registration device 60 is installed at the license registration site C. The license registration device 60 is a computer such as a PC (Personal Computer) for inputting a license information registration request.

  The license acquisition device 10, the license server 50, and the license registration device 60 are connected via a wide area network 70 such as the Internet.

  The license server 50, the license acquisition apparatus 10, and the MFP 20 will be described in more detail. FIG. 2 is a diagram illustrating a functional configuration example of the license server. 2, the license server 50 includes a license registration unit 51, a Web screen display unit 52, a product key generation unit 53, a license DB management unit 54, a license issue unit 55, a license DB (Data Base) 56, and the like.

  The license DB 56 is a database constructed in the storage device of the license server 50 in order to manage information related to the license, and includes, for example, an application license table and a license issuance table.

  FIG. 3 is a diagram illustrating an example of an application license table constituting the license DB. In FIG. 3, an application license table 561 is a table for managing license information of the SDK application 24 registered as a sales target. For each license, a product key, an application ID, a function, an expiration date, a price, etc. to manage.

  The product key is identification information assigned for each license (type) of the application. That is, even for the same application, different product keys are assigned depending on available functions and expiration dates (that is, license types). As will be described later, when a license is purchased, the type of license is designated by the product key. The application ID is identification information assigned uniquely for each application. The function indicates a function that can be used in the license among the functions of the application identified by the application ID. For example, “ALL” indicates that all functions can be used. The expiration date indicates the expiration date of the license. The price indicates the price of the license. In addition, when a plurality of licenses are defined for the same application, an inclusive relationship is not required between functions available in each license. That is, licenses with completely different usable functions can be registered.

  FIG. 4 is a diagram showing an example of a license issuance table constituting the license DB. In FIG. 4, a license issuance table 562 is a table for managing purchased (issued) licenses, and manages a product key, a machine number, a license code, and the like for each purchased license.

  The machine number is identification information assigned to each MFP 20 and uniquely identifying each MFP 20. The license code is data generated for each purchased license. As apparent from FIG. 4, a license for one SDK application 24 is issued to a specific MFP 20. That is, with one license, the SDK application 24 corresponding to the license can be used only in the MFP 20 corresponding to the license. The license code is used as data for restricting the usable range while permitting the use of the SDK application 24.

  Returning to FIG. In response to a license registration request from the license registration site C, the license registration unit 51 controls processing for registering information related to a new license in the application license table 561. The Web screen display unit 52 provides the license registration apparatus 60 with a Web page or the like for inputting a license registration instruction. In response to a license registration request, the product key generation unit 53 generates a product key for the license. The license DB management unit 54 manages the license DB 56. The license issuing unit 55 controls processing for issuing a license when a license issuance (purchase) is requested from the user site A.

  FIG. 5 is a diagram illustrating a functional configuration example of the license acquisition apparatus. In FIG. 5, the license acquisition apparatus 10 includes a license server communication unit 11, a screen display unit 12, a device communication unit 13, a budget management unit 14, and the like.

  The license server communication unit 11 controls communication with the license server 10 and acquisition processing of a license (license code) from the license server 10. The screen display unit 12 causes the display device to display various types of information provided to the user when purchasing a license. The device communication unit 13 controls acquisition of various types of information from the MFP 20, distribution of license codes to the MFP 20, and the like. The budget management unit 14 supports budget management associated with the purchase of a license.

  FIG. 6 is a diagram illustrating a functional configuration example of the MFP. In FIG. 6, the MFP 20 includes a screen display unit 21, a license file 22, an SDK platform 23, an SDK application 24 that operates on the SDK platform 23, an application management unit 25, an application activation unit 26, a license service 27, and a license analysis library. 28 and the like.

  The license file 22 is a file that stores a license code distributed from the license acquisition apparatus 10.

  The SDK platform 23 is an environment for executing an application developed using a dedicated SDK (software development kit) for the MFP 20. After the shipment, the MFP 20 can newly install and execute an application developed using a dedicated SDK. The SDK application 24 is an application developed using SDK. A plurality of SDK applications 24 can be installed in one MFP 20. The application management unit 25 manages information regarding the SDK application 24 installed in the MFP 20. The application activation unit 26 performs activation control of the SDK application 24 based on the license code stored in the license file 22.

  The license service 27 mainly executes processing for receiving distribution of a license code from the license acquisition apparatus 10. The license service 27 includes a PC communication unit 271 and a license file management unit 272. The PC communication unit 271 controls communication with the license acquisition apparatus 10. The license file management unit 272 performs access control of the license file 22 and the like.

  The license analysis library 28 performs decoding and decoding of the encoded and encrypted license code, and further determines whether or not the MFP 20 has a license for the SDK application 24 to be activated.

  Next, a hardware configuration example of the license acquisition apparatus 10 will be described. FIG. 7 is a diagram illustrating a hardware configuration example of the license acquisition apparatus according to the embodiment of the present invention. The license acquisition device 10 of FIG. 7 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 license acquisition 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. 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 license acquisition apparatus 10 according to a program stored in the memory device 103. The interface device 105 is used as an interface for connecting to the network 30 in FIG. 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.

  The program need not always be installed from the recording medium 101, and may be downloaded from another computer via a network.

  The license server 50 can also be configured by the same hardware as the license acquisition apparatus 10. However, when operating the license server 50 via the network, the display device 106 and the input device 107 are not necessarily required. Further, the controller of the MFP 20 can also be configured by hardware similar to that shown in FIG. In the case of the MFP 20, an operation panel is provided as hardware corresponding to the display device 106 and the input device 107. The MFP 20 has hardware unique to the image forming apparatus, such as a scanner (imaging unit) and a plotter (printing unit).

  Hereinafter, the processing procedure of the license management system in the present embodiment will be described. For example, a vendor who develops and sells the SDK application 24 registers a license to be sold for the SDK application 24 with respect to the license issuance site B prior to sale. First, the process at this time will be described. FIG. 8 is a flowchart for explaining the processing procedure of the license registration processing. In FIG. 8, a state where the license registration screen (Web page) transmitted from the Web screen display unit 52 of the license server 50 is displayed by the Web browser 61 of the license registration device 60 is an initial state.

  For example, the administrator of the license registration site C uses, as registration information of a license to be newly registered, an application ID assigned in advance to the SDK application 24 related to the license and the license among all functions of the SDK application 24. When the function that permits the license, the expiration date of the license, the price of the license, and the like are input, the Web browser 61 transmits a license registration request including the registration information to the license server 50 (S101). When receiving the license registration request, the Web screen display unit 52 of the license server 50 notifies the license registration unit 51 of the license registration request (S102). The license registration unit 51 notifies the license DB management unit 54 of the license registration request (S103).

  The license DB management unit 54 requests registration of registration information from the license DB 56 (S104). The license DB 56 registers the registration information, that is, the application ID, function, expiration date, and price of the license relating to the registration request as a new record in the application license table 561 (hereinafter, this record is referred to as “current record”). (S105).

  Subsequently, the license DB management unit 54 specifies registration information and requests the product key generation unit 53 to generate a product key for the license related to the registration request (S107). For example, the product key generation unit 53 generates a unique product key for each license based on the application ID, function, expiration date, price, and the like included in the registration information, and the product key is stored in the application license table 561. Is registered in the current record (S108).

  FIG. 9 is a diagram illustrating an example of updating the application license table by registering a new license. FIG. 9 shows an example in which the last line is the current line. As described above, each time a license is registered, a record corresponding to the license is newly added to the application license table 561.

  Subsequently, the product key generation unit 53 outputs the generated product key to the license DB management unit 54 (S109). The product key is notified to the Web screen display unit 52 via the license registration unit 51 (S110, S111). The Web screen display unit 52 generates a Web page (license registration completion page) for displaying that the license has been successfully registered and the license key, and sends the license registration completion page to the Web browser 61 as a response to the license registration request. A reply is made (S112). The web browser 61 displays a license registration completion page (S113). As a result, the administrator of the license registration site C can confirm the license key for the registered license. The license key is attached to the SDK application 24 related to the license. That is, when the SDK application 24 is distributed, the license key can be recognized at the acquisition destination of the SDK application 24. A plurality of types of licenses can be registered for one SDK application 24. Therefore, a plurality of license keys can be attached to one SDK application 24.

  Next, FIG. 10, FIG. 12, FIG. 12, FIG. 10, FIG. 12, FIG. 10, FIG. 12, FIG. This will be described with reference to the sequence diagrams of FIGS. 13, 19, and 24. The SDK application 24 is obtained, for example, by being downloaded in advance from a predetermined server. The predetermined server may be a server for downloading an application managed at the license registration site C or the license issuance site B, or may be a server managed at another site.

  FIG. 10 is a sequence diagram for explaining an MFP detection process for purchasing a license by the license acquisition apparatus. The process of FIG. 10 is a process for the license acquisition apparatus 10 to detect the MFP 20 connected to the network 30 of the user site A.

  The MFP 20 from an operator (for example, a service person dispatched from the license issuance site B or an administrator at the user site A) via a screen displayed on the display device 106 by the screen display unit 12 of the license acquisition apparatus 10. When the detection instruction is input, the screen display unit 12 requests the device communication unit 13 to create list information (device list) of the MFP 20 (S201). The device communication unit 13 transmits information (device detection information) for detecting the MFP 20 to the network 30 (S202). The device detection information varies depending on various known protocols and communication methods. However, in implementing the present invention, the protocols and communication methods are not limited to predetermined ones. The device detection information may be transmitted by issuing a broadcast, for example.

  When receiving the device detection information, the PC communication unit 271 of the MFP 20 returns the IP address and machine number of the MFP 20 to the license acquisition apparatus 10 (S203). Note that steps S202 and S203 are executed for each MFP 20 connected to the network 30. Accordingly, the respective IP addresses and machine numbers are returned from each MFP 20 to the device communication unit 13 of the license acquisition apparatus 10.

  Upon receiving the IP address and machine number from each MFP 20, the device communication unit 13 collects the IP address and machine number as list information (device list) and outputs the list information to the screen display unit 12 (S204). The screen display unit 12 records and holds the device list in the auxiliary storage device 102 or the memory device 103.

  FIG. 11 is a diagram illustrating an example of a device list. As shown in FIG. 11, the screen display unit 12 holds an IP address and a machine number for each MFP.

  Next, processing in which the license acquisition apparatus 10 acquires list information (application list) of the SDK applications 24 installed in the MFP 20 from each detected MFP 20 will be described.

  FIG. 12 is a sequence diagram for explaining application list acquisition processing of each MFP for license purchase by the license acquisition apparatus.

  The screen display unit 12 designates an IP address included in the held device list and requests the device communication unit 13 to acquire the application list of the MFP 20 related to the IP address (S301). The device communication unit 13 requests the PC communication unit 271 of the MFP 20 related to the designated IP address to provide an application list (S302). The PC communication unit 271 requests the application management unit 25 of the MFP 20 to acquire an application list (S303). The application management unit 25 searches for the SDK application 24 installed in the MFP 20 (S304), and acquires an application ID from each searched SDK application 24 (S305). Therefore, when a plurality of SDK applications 24 are installed, a plurality of application IDs are acquired. Subsequently, the application management unit 25 outputs the acquired list of application IDs (application ID list) to the PC communication unit 271 (S306). The PC communication unit 271 returns an application ID list to the license acquisition apparatus 10 (S307).

  Subsequently, upon receiving the returned application ID list, the device communication unit 13 outputs the application ID list and the IP address of the MFP 20 that is the transmission source of the application ID list to the screen display unit 12 (S308). The screen display unit 12 records the IP address and the application ID list in association with each other in the auxiliary storage device 102 or the memory device 103 and holds them.

  Note that the process of FIG. 12 may be automatically executed following the process of FIG. In this case, the processing of FIG. 12 may be repeated or executed in parallel for all the MFPs 20 included in the device list. 10 is completed, the screen display unit 12 displays a screen including a device list (device list screen) on the display device 106, and executes the processing of FIG. 12 on the MFP 20 selected on the device list screen. You may make it do.

  Next, a process in which the license acquisition apparatus 10 acquires the license status of each SDK application 24 whose application ID is included in the acquired application list will be described. FIG. 13 is a sequence diagram for explaining the license state acquisition processing of each application for license purchase by the license acquisition apparatus.

  The screen display unit 12 designates the held IP address of the MFP 20 and one or more application IDs associated with the IP address, and the SDK application related to the application ID in the MFP 20 related to the IP address. The device communication unit 13 is requested to acquire information indicating the license status (license status information) 24 (S401). The device communication unit 13 requests the PC communication unit 271 of the MFP 20 related to the IP address to provide license status information by specifying an application ID (S402). The PC communication unit 271 requests the license file management unit 272 of the MFP 20 to acquire license status information by specifying an application ID (S403). The license file management unit 272 searches and acquires the license code corresponding to the designated application ID from the license file 22 in the MFP 20 (S404, S405).

  FIG. 14 is a diagram illustrating a configuration example of information stored in the license file. As shown in FIG. 14, the license file 22 stores (records) an application ID and a license code for each SDK application 24 installed in the MFP 20.

  If a plurality of application IDs are designated, a license code is acquired for each application ID. However, for the SDK application 24 that is not licensed, the license code is not registered in the license file 22. Therefore, the license code is not acquired for the unlicensed SDK application 24, and the value thereof is, for example, a NULL value (empty).

  Subsequently, the license file management unit 272 displays a list (license status information list) of a set of each specified application ID and each license code (NULL value for the unlicensed SDK application 24) (PC communication unit). It outputs to 271 (S406). The configuration of the license status information list may be the same as that shown in FIG. However, a list of application IDs of unlicensed SDK applications 24 (that is, application IDs for which no license code is registered in the license file 22) may be used as the license status information list. In this case, the license status information list shows a list of unlicensed SDK applications 24. Subsequently, the PC communication unit 271 returns a license status information list to the license acquisition apparatus 10 (S407).

  Upon receiving the returned license status information list, the device communication unit 13 outputs the license status information list and the IP address of the MFP 20 that is the transmission source of the license status information list to the screen display unit 12 (S408). The screen display unit 12 records the license status information corresponding to each application ID associated with the IP address in association with the IP address in the auxiliary storage device 102 or the memory device 103 and stores the license status information. .

  FIG. 15 is a diagram showing license status information held in the license acquisition apparatus. As shown in FIG. 15, the license acquisition apparatus 10 holds the license code of the application ID for each combination of the IP address of the MFP 20 and the application ID. For the SDK application 24 that is not licensed, the value of the license code is held as a NULL value (empty). Therefore, the license state of each SDK application 24 in each MFP 20 can be identified depending on whether the license code is registered (associated with the application ID).

  Subsequently, the screen display unit 12 causes the display device 106 to display a screen (license operation screen) for operating the license of each SDK application 24 based on the license status information shown in FIG. 15 (S409).

  FIG. 16 is a diagram illustrating a display example of the license operation screen. In FIG. 16, the license operation screen 150 includes a list area 151, a purchase button 152, a distribution button 153, and the like.

  Based on the license status information, the list area 151 includes, for each combination of the IP address, the machine number, and the application ID, the function licensed in the SDK application 24 related to the application ID, the license code for the SDK application 24, and the This is an area where the license status of the SDK application 24 is displayed.

  The screen display unit 12 displays the value of the license code in the license code column and “transmitted” in the status column for the SDK application 24 for which the license code has been acquired by the processing of FIG. For the SDK application 24 for which the license code has not been acquired, “None” is displayed in the license code column, and “Not purchased” is displayed in the Status column. The license operation screen 150 allows the operator to check the license status (presence / absence) for each application installed in each MFP 20. “Transmitted” means that the license code acquired by purchasing the license has been transmitted to the MFP 20.

  Next, a process for purchasing a license for the SDK application 24 whose license has been confirmed to have not been purchased on the license operation screen 150 will be described.

  In the list area 151 of the license operation screen 150, when a row for the SDK application 24 for which a license is to be purchased is selected, the screen display unit 12 inverts the selected row.

  FIG. 17 is a diagram illustrating a state in which a license purchase target is selected on the license operation screen. FIG. 17 shows a state in which the second and third lines are selected in the list area 151. That is, the SDK application 24 with the application ID “00000002” in the MFP 20 with the machine number “11111111” and the SDK application 24 with the application ID “00000001” in the MFP 20 with the machine number “11111112” are license purchase targets. It will be selected. When the purchase button 152 is clicked (selected) in this state, the screen display unit 12 displays a dialog (product key input dialog) for inputting the product key of the license to be purchased.

  FIG. 18 is a diagram showing a display example of the product key input dialog. In FIG. 18, the product key input dialog 160 has a text box 161, an OK button 162, and the like. The text box 161 is an area for inputting a product key. The operator inputs a product key corresponding to a necessary function and an expiration date. FIG. 18 shows an example in which “CCCCCCCC” is input as the product key. When the OK button 162 is clicked, a product key input dialog 160 for inputting a product key for the next SDK application 24 is displayed. When the product keys of all the SDK applications 24 that are the license purchase targets are input, the processing shown in FIG. 19 is started. Note that in one product key input dialog 160, the product keys of all the SDK applications 24 for which licenses are to be purchased may be input at a time. Further, such information may be displayed on the product key input dialog 160 so that the licensed function and the expiration date for each product key can be easily recognized.

  FIG. 19 is a sequence diagram for explaining a license purchase process by the license acquisition apparatus.

  The screen display unit 12 designates the machine number associated with each row selected on the license operation screen 150 and the product key input for each line, and the SDK application associated with the product key in the MFP 20 associated with the machine number. The license server communication unit 11 is requested to purchase 24 licenses (S501). The license server communication unit 11 requests the license issuing unit 55 of the license server 50 to purchase a license by specifying the machine number and the product key (S502). The license issuing unit 55 requests the license DB management unit 54 to issue a license by specifying the machine number and the product key (S503). The license DB management unit 54 requests the license DB 56 to issue a license by specifying the machine number and the product key (S504). The license DB 56 generates a license code based on the designated machine number, product key, and application license table 561 (see FIG. 3) (S505).

  FIG. 20 is a diagram illustrating a configuration example of a license code. As shown in FIG. 20, one license code includes an application ID, a machine number of the MFP 20, usable functions, an expiration date, and the like. Based on the license code, use of the SDK application 24 identified by the application ID on the MFP 20 identified by the machine number is permitted within the range of the function and expiration date specified by the license code. For the application ID, function, and expiration date, values searched from the application license table 561 based on the product key designated by the license DB 56 are used. As the machine number of the MFP 20, the designated machine number is used as it is. Note that the license code is not simply an application ID, the machine number of the MFP 20, an available function, and an expiration date, but is generated by encoding and further encrypting the information.

  Subsequently, the license DB 56 registers the machine number, product key, and license code in the license issuance table 562 (S506).

  FIG. 21 is a diagram illustrating a state where a new license is registered in the license issuance table. The license issuance table 562 in FIG. 21 shows a state in which the last two lines are added to the state in FIG. That is, the CCCCCCCC, 11111111 and ABCDEFGI lines, the BBBBBBBBB and 11111112 lines, and the ABCDEFHH line are added to the product key, the machine number, and the license code.

  Subsequently, the license DB 56 outputs the license code for the new license and the machine number corresponding to the license code to the license DB management unit 54 (S507). The license code and the machine number are transmitted to the license server communication unit 11 of the license acquisition apparatus 10 via the license issuing unit 55 (S508, S509), and are output from the license communication unit 11 to the screen display unit 12 (S510). The license code is generated for each combination of the machine number (MFP 20) and the product key (SDK application 24). Accordingly, when a plurality of lines are selected on the license operation screen 150 and the purchase of a license is instructed, a license code is generated and issued for the machine number and product key associated with the plurality of lines.

  The screen display unit 12 that has acquired the machine number and the license code updates the held license status information. FIG. 22 is a diagram illustrating how the license status information is updated. FIG. 22 shows a state in which a newly issued license code is added to the license status information on the second and third rows as compared to the status shown in FIG. The screen display unit 12 makes it possible to identify the updated part in the license status information. For example, the flag information regarding the updated part may be turned ON.

  Subsequently, the screen display unit 12 reflects the update of the license status information on the display content of the license operation screen 150 (S511).

  FIG. 23 is a diagram illustrating an example of updating the display contents of the license operation screen by purchasing a license. Comparing FIG. 23 and FIG. 17, in the license operation screen 150 shown in FIG. 23, the issued license code is displayed in the second and third lines, and the status is updated to “purchased”. .

  When the operator clicks the distribution button 153 in a state where the row “purchased” is selected, the processing in FIG. 24 is started. However, the processing of FIG. 24 may be automatically started in response to acquisition of the license code. FIG. 24 is a sequence diagram for explaining license code distribution processing by the license acquisition apparatus.

  The screen display unit 12 designates the IP address and license code associated with the selected row on the license operation screen 150, and requests the device communication unit 13 to distribute the license to the IP address (S601). The device communication unit 13 transmits a license code to the PC communication unit 271 of the MFP 20 associated with the IP address (S602). The PC communication unit 271 extracts an application ID from the license code by decoding the license code using the license analysis library 28. The PC communication unit 271 designates the extracted application ID and license code, and requests the license file management unit 272 of the MFP 20 to save the license code (S603). The license file management unit 272 registers (stores) the designated application ID and the license code in the license file 22 in the MFP 20 in association with each other (S604, S605).

  When the license code is registered normally, the license file management unit 272 notifies the PC communication unit 271 of a response indicating normal registration (S606). The notification of normal registration is notified to the screen display unit 12 via the PC communication unit 271 and the device communication unit 13 (S607, S608). The screen display unit 12 updates the display content of the license operation screen 150 in response to the notification of normal registration.

  FIG. 25 is a diagram illustrating an example of updating the display contents of the license operation screen upon completion of license distribution. In the license operation screen 150 of FIG. 25, it can be seen that the status columns in the second and third rows are both updated to “sent”. Thus, the use of the SDK application 24 related to the application ID in the MFP 20 related to the row can be performed within a licensed range.

  If a plurality of rows are selected on the license operation screen 150, the processing of FIG. 24 is executed for each row. Therefore, licenses can be delivered to a plurality of MFPs 20 in a single operation.

  By the way, for example, when an arbitrary line is selected in the list area 151 of the license operation screen 150 and the property menu item of the file menu is selected, the screen display unit 12 displays the license property dialog (license for the selected line). Display the property dialog.

  FIG. 26 is a diagram showing a display example of the license property dialog. As shown in FIG. 26, the license property dialog 170 displays properties of the license selected on the license operation screen 150 (license code, application ID, function, expiration date, price, etc.). By displaying the license property dialog 170, the user can confirm more detailed information regarding the license. Note that the information displayed in the license property dialog 170 may be acquired by the screen display unit 12 decoding and decoding the license code.

  Next, a process when the MFP 20 is requested to use the SDK application 24 will be described. FIG. 27 is a sequence diagram for explaining the activation process of the SDK application in the MFP.

  As an initial state of FIG. 27, the screen display unit 21 displays a list of the SDK applications 24 installed in the MFP 20 on the operation panel. In this state, when the user selects a desired SDK application 24 and instructs execution, the screen display unit 21 designates the application ID of the selected SDK application 24 and activates the SDK application 24 to start the application. 26 (S701). The application activation unit 26 designates the application ID and requests the license file management unit 272 to confirm whether or not there is a license for the SDK application 24 (hereinafter simply referred to as “license confirmation”) (S702). The license file management unit 272 specifies the application ID and requests the license analysis library 28 to confirm the license (S703). The license analysis library 28 searches the license file 22 (S704), and acquires a license code stored in association with the application ID (S705). Subsequently, the license analysis library 28 determines whether or not there is a license (usability) in the SDK application 24 related to the application ID based on the license code (S706). Specifically, the license analysis library 28 decodes and decodes the license code, and acquires the application ID, the machine number, and the expiration date included in the license code. Subsequently, the license analysis library 28 compares the machine number and application ID obtained from the license code with the machine number and activation ID of the MFP 20. If they match and the current time is within the expiration date, the license analysis library 28 determines that there is a license. On the other hand, if the machine number or application ID does not match, or if the current time is not within the expiration date, the license analysis library 28 determines that there is no license. In step S705, if the license code corresponding to the application ID is not acquired, it is determined that there is no license for the SDK application 24.

  The determination result by the license analysis library 28 is output to the license file management unit 272 (S707). The license file management unit 272 notifies the application activation unit 26 of the presence / absence of a license based on the determination result (S708). If there is a license, the application activation unit 26 activates the SDK application 24 instructed to activate, and notifies the screen display unit 31 of the activation success (S709). On the other hand, when there is no license, the application activation unit 26 does not activate the SDK application 24 instructed to activate, and notifies the screen display unit 31 of activation failure (S709). When the SDK application 24 is successfully activated, the screen display unit 21 displays the operation screen of the SDK application 24 on the operation panel. If startup fails, an error screen is displayed on the operation panel.

  Next, a process for discarding or invalidating (deactivating) the license of the SDK application 24 will be described. FIG. 28 is a sequence diagram for explaining the deactivation process. For example, when the operator clicks the deactivate button 154 in a state in which a row whose state is “sent” is selected on the license operation screen 150, the processing in FIG. 28 is started.

  The screen display unit 12 designates the IP address and license code associated with the selected row on the license operation screen 150, and requests the device communication unit 13 to deactivate the license for the MFP 20 associated with the IP address (S801). The device communication unit 13 designates a license code and transmits a license deactivation request to the PC communication unit 271 of the MFP 20 (S802). The PC communication unit 271 extracts an application ID from the license code by decoding the license code using the license analysis library 28. The PC communication unit 271 designates the extracted application ID and license code, and requests a license deactivation request from the license file management unit 272 of the MFP 20 (S803). The license file management unit 272 invalidates the license by deleting the license code registered for the designated application ID from the license file 22 in the MFP 20 (S804, S805). However, the license may be invalidated by recording flag information (deactivation flag) indicating deactivation without deleting the license code.

  FIG. 29 is a diagram illustrating an example of a license file including a deactivation flag. In the license file 22 shown in FIG. 29, the deactivation flag is associated with the license code. In the figure, “◯” indicates that the program has been deactivated.

  When the license is normally deactivated, the license file management unit 272 notifies the PC communication unit 271 of a response indicating the completion of deactivation (S806). The notification is notified to the screen display unit 12 via the PC communication unit 271 and the device communication unit 13 (S807, S808). Next, the screen display unit 12 requests the license server communication unit 11 to notify the license server 50 of the deactivated debate by designating the machine number and the license code related to the deactivated license (S809). The license server communication unit 11 designates the machine number and the license code, and notifies the license DB management unit 54 of the license server 50 that the license has been deactivated (S810).

  The license DB management unit 54 designates the machine number and the license code, and requests the license DB 55 to delete the license (S811). The license DB 55 deletes the record that matches the specified machine number and license code from the license issuance table 562 (see FIG. 4). However, in the license issuance table 562 as well as the license file 22, flag information indicating that the record has been deactivated may be recorded instead of deleting the record.

  Note that the license deactivation is effective when the purchased license is transferred to another MFP 20. That is, when the license is deactivated, the MFP 20 is not permitted to use the SDK application 24 based on the license. However, by transmitting the license to another MFP 20, the function corresponding to the license can be used in the other MFP 20.

  Incidentally, the license price may be displayed on the license operation screen 150.

  FIG. 30 is a diagram illustrating a display example of a license operation screen that enables budget management. In the list display area 151a of the license operation screen 150a in FIG. 30, the price of each license is displayed. The budget management unit 14 obtains the price from the license code by decoding and decoding the license code, and displays the price. By displaying the price of each license, it is possible to appropriately support the purchase of a license that matches the budget (ie, budget management).

  The license operation screen 150 a has a machine unit total button 155 and an application unit total button 156. When the machine unit aggregation button 155 is clicked, the budget management unit 14 calculates the total price of the licenses purchased in the MFP 20 for each machine (MFP 20), and the calculation result is displayed on the license operation screen 150a. Display.

  FIG. 31 is a diagram showing a display example of a license operation screen on which the total value of license prices for each unit is displayed. In FIG. 31, the list display area 151a of the license operation screen 150a displays the total price of purchased licenses for each machine (for each MFP 20). Also, the total value (121,000 yen) of the license price for all the MFPs 20 is displayed.

  When the application unit aggregation button 156 is clicked on the license operation screen 150a, the budget management unit 14 calculates the total price of the purchased license for each SDK application 24 across the plurality of MFPs 20, and displays the calculation result. It is displayed on the license operation screen 150a.

  FIG. 32 is a diagram illustrating a display example of a license operation screen on which the total value of license prices for each application is displayed. In FIG. 32, in the list display area 151a of the license operation screen 150a, the total price of purchased licenses is displayed for each SDK application 24 (application ID). In addition, the total license price (121,000 yen) for all the SDK applications 24 is also displayed.

  The budget management unit 14 is not necessarily installed in the license acquisition apparatus 10. FIG. 33 is a diagram illustrating a functional configuration example of a license server having a budget management unit. In FIG. 33, the budget management unit 57 of the license acquisition apparatus 10 calculates the total value of the license price for each machine and for the SDK application 24 based on the license issuance table 562, and the calculation result is sent to the license acquisition apparatus 10. provide.

  FIG. 34 is a diagram illustrating a functional configuration example of an MFP having a budget management unit. In FIG. 34, the budget management unit 273 of the license acquisition apparatus 10 determines the license price for each machine unit and for each SDK application 24 in the MFP 20 based on information included in the license code stored in the license file 22. And the calculation result is provided to the license acquisition apparatus 10.

  In the above-described embodiment, the example in which the license registration function and the issue function are implemented in the license server 20 has been described. However, these functions may be implemented in the license acquisition apparatus 10.

  FIG. 35 is a diagram illustrating a functional configuration example of a license acquisition apparatus having license registration and issue functions. In the license acquisition apparatus 10 in FIG. 35, a Web screen display unit 15, a license registration unit 16, a product key generation unit 17, and a license issue unit 18 are added to the configuration example shown in FIG. These implement the same functions as the Web screen display unit 52, license registration unit 51, product key generation unit 53, and license issuance unit 55 in the license server 50. Therefore, in this case, the license server 50 and the license DB 56 only need to be mounted on the license server 50.

  As shown in FIG. 36, the license registration device 60 may be installed in the license issuance site B. This is because the SDK application 24 can also be developed by the manufacturer of the MFP 20. In this case, the license server 50 and the license registration device 60 may be configured by a single computer.

  As described above, according to the license management system of the present embodiment, the license acquisition apparatus 10 can acquire licenses of a plurality of MFPs 20 in a lump and distribute them to each MFP 20. Therefore, it is possible to efficiently set a license for each MFP 20.

  Further, since each MFP 20 does not need to directly access the license server 50, each MFP 20 does not need to be directly connected to a wide area network such as the Internet. Therefore, higher security can be ensured for the MFP 20.

  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.

It is a figure which shows the structural example of the license management system in embodiment of this invention. It is a figure which shows the function structural example of a license server. It is a figure which shows the example of the application license table which comprises license DB. It is a figure which shows the example of the license issue table which comprises license DB. It is a figure which shows the function structural example of a license acquisition apparatus. 2 is a diagram illustrating an example of a functional configuration of an MFP. FIG. It is a figure which shows the hardware structural example of the license acquisition apparatus in embodiment of this invention. It is a flowchart for demonstrating the process sequence of a license registration process. It is a figure which shows the example of an update of the application license table by registration of a new license. FIG. 10 is a diagram for explaining MFP detection processing for license purchase by the license acquisition apparatus. It is a figure which shows the example of an apparatus list. FIG. 11 is a sequence diagram for explaining an acquisition process of an application list of each MFP for license purchase by the license acquisition apparatus. FIG. 10 is a sequence diagram for explaining a process for acquiring a license state of each application for license purchase by the license acquisition apparatus. It is a figure which shows the structural example of the information stored in the license file. It is a figure which shows the license status information hold | maintained in a license acquisition apparatus. It is a figure which shows the example of a display of a license operation screen. It is a figure which shows the state from which the purchase target of the license was selected in the license operation screen. It is a figure which shows the example of a display of a product key input dialog. It is a sequence diagram for demonstrating the license purchase process by a license acquisition apparatus. It is a figure which shows the structural example of a license code. It is a figure which shows a mode that the new license was registered into the license issue table. It is a figure which shows a mode that the license status information was updated. It is a figure which shows the example of an update of the display content of the license operation screen by license purchase. It is a sequence diagram for demonstrating the delivery process of the license code by a license acquisition apparatus. It is a figure which shows the example of update of the display content of the license operation screen by completion of distribution of a license. It is a figure which shows the example of a display of a license property dialog. FIG. 10 is a sequence diagram for explaining an activation process of an SDK application in an MFP. It is a sequence diagram for demonstrating a deactivation process. It is a figure which shows the example of the license file containing a deactivation flag. It is a figure which shows the example of a display of the license operation screen which enabled budget management. It is a figure which shows the example of a display of the license operation screen on which the total value of the license price of the body unit was displayed. It is a figure which shows the example of a display of the license operation screen on which the total value of the license price of an application unit was displayed. It is a figure which shows the function structural example of the license server which has a budget management part. 3 is a diagram illustrating an example of a functional configuration of an MFP having a budget management unit. FIG. It is a figure which shows the function structural example of the license acquisition apparatus which has a registration and issuing function of a license. It is a figure which shows the example by which a license registration apparatus is arrange | positioned in a license issue site.

Explanation of symbols

DESCRIPTION OF SYMBOLS 10 License acquisition apparatus 11 License server communication part 12 Screen display part 13 Equipment communication part 14 Budget management part 15 Web screen display part 16 License registration part 17 Product key generation part 18 License issue part 20 MFP
21 Screen display unit 22 License file 23 SDK platform 24 SDK application 25 Application management unit 26 Application activation unit 27 License service 28 License analysis library 30 Network 50 License server 51 License registration unit 52 Web screen display unit 53 Product key generation unit 54 License DB Management unit 55 License issuing unit 56 License DB
57 Budget Management Unit 60 License Registration Device 70 Wide Area Network 100 Drive Device 101 Recording Medium 102 Auxiliary Storage Device 103 Memory Device 104 CPU
105 interface device 106 display device 107 input device 271 PC communication unit 272 license file management unit 273 budget management unit B bus

Claims (10)

An information processing system comprising a plurality of devices capable of executing an application, and an information processing device connected to the devices via a network,
License status information acquisition means for acquiring license status information of an application installed in the device from each of the plurality of devices via a network;
License data acquisition means for acquiring license data permitting use of an application from a computer connected via a network based on the license status information;
An information processing system comprising: license data distribution means for distributing the license data to each of the plurality of devices. Device detection means for detecting the device connected via a network;
The information processing system according to claim 1, wherein the license status information acquisition unit acquires license status information of an application installed in the detected device. License information display means for displaying the license status information on a display device for each application based on the license status information of the application;
The information processing system according to claim 1, wherein the license data acquisition unit acquires the license data for an application selected by an operator according to the display of the license status information.   The information processing system according to any one of claims 1 to 3, wherein the license data differs according to a function that is permitted to be used among functions of the application.   The information processing system according to any one of claims 1 to 4, wherein the license data differs according to a time limit for permitting use of the application. An information processing method executed by a plurality of devices capable of executing an application and an information processing apparatus connected to the devices via a network,
A license status information acquisition procedure for acquiring license status information of an application installed in the device from each of the plurality of devices via a network;
Based on the license status information, a license data acquisition procedure for acquiring license data permitting use of an application from a computer connected via a network;
A license data distribution procedure for distributing the license data to each of the plurality of devices. A device detection procedure for detecting the device connected via a network;
The information processing method according to claim 6, wherein the license status information acquisition procedure acquires license status information of an application installed in the detected device. A license information display procedure for causing the display unit to display the license status information for each application based on the license status information of the application;
8. The information processing method according to claim 6, wherein the license data acquisition procedure acquires the license data for an application selected by an operator according to the display of the license status information.   The information processing method according to any one of claims 6 to 8, wherein the license data differs according to a function that is permitted to be used among functions of the application.   The information processing method according to claim 6, wherein the license data differs according to a time limit for permitting use of the application.

Images