JP5510535B2 - Information processing apparatus, license determination method, program, and recording medium - Google Patents

Description

  The present invention relates to an information processing apparatus, a license determination method, a program, and a recording medium.

  In recent years, there are some image forming apparatuses called mainly multifunction peripherals or multi-function peripherals that allow new applications to be developed and installed after shipment. If a license for such an application can be provided in accordance with the usage pattern of the user, it is not only convenient for the user, but also an expansion of business opportunities can be expected for the side selling the application.

  For example, Patent Document 1 discloses a license management method that can limit an image forming apparatus that can use an application to a predetermined one. According to the technique according to Patent Document 1, the billing amount can be changed according to the number of applications using the application. Further, unauthorized use due to unauthorized copying of an application can be prevented appropriately.

  By the way, one application is not necessarily composed of one program module, and may be composed of a plurality of program modules modularized according to function. For such an application, if the license unit is a program module unit, use of only a part of the functions of the application can be restricted or permitted. By doing so, various product forms can be configured.

  However, when the license unit is a program module unit, it is necessary to check the license for each program module when the application is activated. Then, for a huge application including a large number of program modules, the time required for the license check becomes so large that it cannot be ignored, and there is a problem that the activation time of the application increases beyond an allowable range.

  The present invention has been made in view of the above points, and is an information processing apparatus, a license determination method, and a program that can appropriately suppress an increase in the startup time of an application due to a license check related to a program module constituting the application And to provide a recording medium.

  Accordingly, in order to solve the above-described problem, the present invention provides an information processing apparatus capable of starting an application including a plurality of program modules, and the program module associated with each program module is subject to license management. A license object identification information generating unit configured to generate license object identification information capable of identifying a program module to be license-managed among the plurality of program modules based on information indicating whether or not the application module is started; In response to a request, when a program module that cannot be used is included in a program module that is a target of license management based on the license target identification information, a startup limiting unit that limits startup of the program module is included. To.

  In such an information processing apparatus, it is possible to appropriately suppress an increase in the activation time of the application due to a license check related to the program module constituting the application.

  ADVANTAGE OF THE INVENTION According to this invention, the increase in the starting time of an application by the license check regarding the program module which comprises an application can be suppressed appropriately.

1 is a diagram illustrating an example of a hardware configuration of an image forming apparatus according to an embodiment of the present invention. FIG. 3 is a diagram illustrating a software configuration example of an image forming apparatus according to an embodiment of the present invention. It is a figure which shows the license management function in an SDK platform, and the structural example of an SDK application. FIG. 5 is a diagram for explaining a procedure for introducing a license key into an image forming apparatus. It is a figure which shows the structural example of a license key. It is a flowchart for demonstrating the production | generation process of a license list. It is a figure which shows the example of a license list. It is a state transition diagram for demonstrating the life cycle of the SDK application in this Embodiment. It is a flowchart for demonstrating the process sequence at the time of starting of an SDK application. It is a figure for demonstrating the process sequence at the time of starting of an SDK application when there is no license list. It is a figure for demonstrating the reason that starting of an SDK application is speeded up by a license list.

  Hereinafter, embodiments of the present invention will be described with reference to the drawings. FIG. 1 is a diagram illustrating a hardware configuration example of an image forming apparatus according to an embodiment of the present invention. In FIG. 1, the image forming apparatus 10 includes hardware such as a controller 11, a scanner 12, a printer 13, a modem 14, a network interface 15, and an operation panel 16.

  The controller 11 includes a CPU 111, a RAM 112, a ROM 113, an HDD 114, and the like. The ROM 113 stores various programs and data used by the programs. The RAM 112 is used as a storage area for loading a program, a work area for the loaded program, and the like. The CPU 111 realizes various functions by processing a program loaded in the RAM 112. The HDD 114 records programs and various data used by the programs.

  The scanner 12 is hardware for reading image data from a document. The printer 13 is hardware for printing image data on printing paper. The modem 14 is hardware for connecting to a telephone line, and is used to execute transmission / reception of image data by FAX communication. The network interface 15 is hardware for connecting to a network (regardless of wired or wireless) such as a LAN (Local Area Network). The operation panel 16 is hardware including a button, a liquid crystal panel, and the like for receiving input from the user and notifying information to the user.

  FIG. 2 is a diagram illustrating a software configuration example of the image forming apparatus according to the embodiment of the present invention. In FIG. 1, the image forming apparatus 10 includes software such as an OS 121, a control service 122, and an application 123.

  The OS 121 is a so-called OS (Operating System) such as UNIX (registered trademark), and starts various software in parallel on a process basis.

  The control service 122 is a software module group that commonly provides services for controlling various hardware resources and the like to upper applications and the like. For example, the control service 122 provides means for controlling the scanner 12 or the printer 13, communication means via the modem 14 or the network interface 15, and the like.

  The application 123 is a program that causes the image forming apparatus 10 to execute various jobs requested by the user using the control service 122, the OS 121, and the like. The application 123 is roughly divided into a standard application 130 and an SDK application 140.

  The standard application 130 refers to an application that is mounted on the image forming apparatus 10 in a standard manner (in advance at the time of shipment). In the figure, a copy application 131 that controls a copy job, a scan application 132 that controls a scan job, a fax application 133 that controls a fax transmission job, a print application 134 that controls a print job, and the like are illustrated.

  The SDK application 140 is an application developed using a dedicated SDK (software development kit) for the image forming apparatus 10 and operates on the SDK platform 150. That is, a new application can be added to the image forming apparatus 10 after shipment using a dedicated SDK. In the figure, three SDK applications 140, SDK applications 141, 142, and 143 are illustrated. The activation of the SDK application 140 in the image forming apparatus 10 is premised on the acquisition of a license key for each. The license key is data acquired by purchasing usage authority of the SDK application 140. In the present embodiment, the SDK application 140 is a program written in the Java (registered trademark) language. However, when implementing the present invention, the SDK application 140 is not limited to a program written in the Java (registered trademark) language.

  The SDK platform 150 is software that provides an operating environment for the SDK application 140. For example, classes and controls provided as standard in a Java (registered trademark) virtual machine or Java (registered trademark) ME (Micro Edition). The class group etc. which wrapped the function of the service 122 are included. In addition, the SDK platform 150 performs license management regarding the SDK application 140. For example, the SDK application 140 manages a license key for each SDK application 140 and performs activation control of the SDK application 140 based on the license key.

  FIG. 3 is a diagram illustrating a license management function and a configuration example of an SDK application in the SDK platform.

  As shown in the figure, one SDK application 140 includes one or more function modules (for example, a program module such as JAR (Java (registered trademark) Archive)) and a license associated with each function module (corresponding). Contains information files. Some function modules may not be accompanied by a license information file. Each functional module realizes a part of functions constituting a job executed by the SDK application 140 to which the functional module belongs. The license information file is a file including information (license information) related to the license for the corresponding functional module. The license information includes, for example, a function module identifier (function name), a function module file name, and a function module display name (display character string).

  The SDK application 140 of FIG. 2 includes functional modules 1401a, 1401b, and 1401c (hereinafter, collectively referred to as “functional modules 1401”) as functional modules. Further, the license information file includes a license information file 1402a and a license information file 1402b (hereinafter collectively referred to as “license information file 1402”). The license information file 1402a is a license information file attached to the function module 1401a. The license information file 1402b is a license information file attached to the function module 1401b. The function module 1401c is not accompanied by a license information file. This indicates that the functional module 1401c is not a license target (license check is unnecessary (for example, license free)).

  On the other hand, the SDK platform 150 includes a license introduction unit 151, a license management unit 152, an activation control unit 153, an encryption processing unit 154, a true / false determination unit 155, and the like.

  The license introduction unit 151 acquires a license key from a computer connected via a network, stores the license key in the license file 160, and stores it in the HDD 114.

  The activation control unit 153 controls activation and termination of the SDK application 140. When the SDK application 140 is activated, the activation control unit 153 controls activation (loading to the RAM 112) in units of functional modules 1401 by inquiring the license management unit 152 about the license status of the SDK application 140.

  The license management unit 152 manages the license file 160 and generates the license list 170. The license list 170 has a one-to-one correspondence with the SDK application 140. Therefore, when a plurality of SDK applications 140 are installed, a plurality of license lists 170 are generated. One license list 170 includes a list of license information stored in the license information file 1402 included in the corresponding SDK application 140. The license management unit 152 also determines the function modules 1401 (function modules 1401a and 1401b in the figure) to be licensed based on the license list 170 corresponding to the SDK application 140 for which the license status is inquired by the activation control unit 153. Then, it is determined whether or not the activation is permitted (permitted or not) based on the license key stored in the license file 160. The license management unit 152 responds to the activation control unit 153 with the determination result.

  The encryption processing unit 154 encrypts the license list 170 when the license list 170 generated by the license management unit 152 is stored, and decrypts the license list 170 when the encrypted license list 170 is used. The encryption processing unit 154 prevents the license list 170 from being falsified.

  The authenticity determination unit 155 determines whether the license list 170 has been tampered with.

  Hereinafter, a processing procedure of the image forming apparatus 10 will be described.

  FIG. 4 is a diagram for explaining a procedure for introducing a license key into the image forming apparatus. In FIG. 1, a PC 20 is a computer connected to the image forming apparatus 10 via a network, and includes an operation unit 21, a license transmission unit 22, and the like.

  The operation unit 21 receives an input of a product key of the SDK application 140 that can be used in the image forming apparatus 10 (to be issued as a license key) from the user.

  The product key is identification information uniquely assigned to a product identified by the combination of the SDK application 140 and the function module 1401. Specifically, even for the same SDK application 140, the product key is different between a product that can use some of the function modules 1401 and a product that can use all the functions. In the case of a product that can use some of the functional modules 1401, the product key varies depending on which functional module 1401 can be used. That is, the input of the product key by the user means selection by the user as to which function (functional module 1401) of which SDK application 140 is to be used.

  In response to the input of the product key, the license transmission unit 22 requests the image forming apparatus 10 to transmit the machine number. The machine number is a number uniquely assigned to each image forming apparatus 10 at the time of factory shipment. In response to the request, the license introduction unit 151 of the image forming apparatus 10 acquires the machine number of the image forming apparatus 10 from, for example, the ROM 113, and returns the machine number to the license transmission unit 22 (S11). Subsequently, the license transmission unit 11 transmits to the image forming apparatus 10 a license key that gives the right to use the SDK application 140 and the functional module 1401 identified by the product key only in the image forming apparatus 10 identified by the received machine number. (S12).

  FIG. 5 is a diagram illustrating a configuration example of the license key. In the figure, one license key is composed of an application ID, a machine number of the image forming apparatus 10, usable functions (a list of identifiers of function modules 1401), an expiration date, and the like. Using the license key, the use of the SDK application 140 identified by the application ID on the image forming apparatus 10 identified by the machine number is permitted within the range of the function and the expiration date specified by the license key. That is, the license unit related to the SDK application 140 is managed in function units (functional module 1401 units). The application ID, function, and expiration date are values determined based on the product key. The license key is not simply an application ID, a machine number of the image forming apparatus 10, an available function, and an expiration date, but may be encoded and further encrypted. The license key may be generated in the PC 20 or in response to a request from the PC 20 in another computer connected to the PC 20 via a network (for example, a server computer that centrally manages license information in a global environment). May be generated. Upon receiving the license key, the license introduction unit 151 stores the license key in the license file 160 and saves it in the HDD 114 (S13).

  FIG. 6 is a flowchart for explaining a license list generation process. The process in FIG. 5 is performed for each SDK application 140.

  First, the license management unit 152 generates an empty license list 170 (file) on the HDD 114 in association with the SDK application 140 (S101). The method of associating the license list 170 with the SDK application 140 is not limited to a predetermined method. For example, an application ID may be included in the license list 170, or the license list 170 may be generated under a folder whose name is the application ID.

  Subsequently, in steps S102 to S105, the license management unit 152 searches for the functional module 1401 included in the SDK application 140 that is the processing target. When the license information file 1402 is attached to the searched function module 1401 (Yes in S103), the license management unit 152 adds the license information stored in the license information file 1402 to the license list 170 (S104). ). When the search for all the functional modules 1401 is completed (S105), the license management unit 152 causes the encryption processing unit 154 to encrypt the generated license list 170 (S106). The encryption method is not limited to a predetermined one.

  For example, taking the configuration of the SDK application 140 in FIG. 3 as an example, first, the function module 1401a is searched in step S102. Since the license information file 1402a is attached to the functional module 1401a, the process proceeds to Yes in step S103. In step S104, the license information stored in the license information file 1402a of the functional module 1401a is registered in the license list 170.

  Subsequently, returning to step S102, the function module 1401b is searched. Since the license information file 1402b is attached to the function module 1401b, the process proceeds to Yes in step S103. In step S104, the license information stored in the license information file 1402b of the functional module 1401b is registered in the license list 170.

  Subsequently, the process returns to step S102, and the function module 1401c is searched. Since the license information file is not attached to the function module 1401c, the process proceeds to No in step S103, and the search ends in step S105. As a result, a license list 170 as shown in FIG. 7 is generated.

  FIG. 7 is a diagram illustrating an example of a license list. As shown in the figure, in the license list 170, the identifier (function name) of the function module, the file name of the function module, the display name of the function module, and the date and time are registered for each function module. The date and time is the date and time when the license was issued (license key was issued). For example, in step S104, the date and time may be the date and time when the license file 160 including the license key for the corresponding functional module in the license file 160 corresponding to the SDK application 140 to be processed is transferred. At that time, the association information (for example, the file name of the license file 160 or the license key itself) may be recorded in the license list 170.

  In FIG. 7, the functional module A corresponds to the functional module 1401a in FIG. The function module B corresponds to the function module 1401b. As described above, since the license information file is not attached to the function module 1401c, it is not registered in the license list 170.

  A generation time of the license list 170 (a timing at which the process of FIG. 6 is executed) will be described. The SDK application 140 has a life cycle as shown in FIG. FIG. 8 is a state transition diagram for explaining the life cycle of the SDK application in the present embodiment.

  The SDK application 140 is in an uninstalled state before being installed in the image forming apparatus 10, and transitions to an installed state by installation. In the installed state, first, the SDK application 140 is stopped and is in an unlicensed state in which no corresponding license key exists. In this unlicensed state, the SDK application 140 cannot be activated. When the license key is introduced from the PC 20 in the unlicensed state, the SDK application 140 shifts to the licensed state. The licensed state is a state where the SDK application 140 can be activated.

  When activated in the licensed state, the SDK application 140 transitions to the activated state. In the activated state, the user can use the functions installed in the SDK application 140 within a licensed range. When the SDK application 140 is stopped, the SDK application 140 returns to the licensed state. If the SDK application 140 is uninstalled when the SDK application 140 is in the stopped state, the SDK application 140 returns to the non-installed state.

  In the life cycle as described above, the license list 170 is generated when the SDK application 140 is installed or when the SDK application 140 is activated.

  Next, FIG. 9 is a flowchart for explaining a processing procedure when the SDK application is activated. When an activation instruction (use request) for a certain SDK application 140 is input by the user via the operation panel 16 or the like, the activation control unit 153 causes the license management unit 152 to select the SDK application 140 to be activated. The application ID is notified, and the license status of the SDK application 140 is inquired. In response to the inquiry, the process of FIG. 9 is started.

  First, the license management unit 152 reads the license list 170 corresponding to the activation target SDK application 140 onto the RAM 112 (S201). Subsequently, the license management unit 152 causes the encryption processing unit 154 to decrypt the license list 170 (S202). Subsequently, the license management unit 152 causes the authenticity determination unit 155 to execute the validity of the license list 170 (S203). The authenticity determination unit 155 determines the validity of the license list 170 by, for example, checking whether the decryption by the encryption processing unit 154 is successful or whether the data format of the license list 170 conforms to a predetermined format. That is, if decryption fails or if the license list 170 does not conform to a predetermined format, the license list 170 is determined to be invalid.

  An electronic signature may be used to determine the validity of the license list 170. For example, when the license list 170 is generated, a hash value of the license list 170 before encryption is generated and stored in association with the license list 170. The authenticity determination unit 155 compares the hash value of the license list 170 decrypted in step S202 with the hash value stored in association with the license list 170 to determine whether the license list 170 has been tampered with ( Legitimacy).

  When the authenticity determination unit 155 denies the validity of the license list 170 (when it is determined that the license list 170 is invalid) (No in S203), the license management unit 152 causes the SDK application 140 to be activated to start. As a processing target, the processing of FIG. 6 is executed again to regenerate the license list 170 (S204). Even if the license list 170 does not exist in step S201, the generation process of the license list 170 is executed in step S204.

  If the validity of the license list 170 is affirmed by the authenticity determination unit 155 (Yes in S203), or following step S204, the function module 1401 that cannot be activated (not permitted) in the activation target SDK application 140 Is determined using the license list 170 (S205 to S209).

  First, in step S206, the license management unit 152 acquires one entry (license information for one functional module 1401) from the license list 170 (S206). Subsequently, the license management unit 152 corresponds to the license information based on the identifier included in the acquired license information and the license key stored in the license file 160 corresponding to the SDK application 140. It is determined whether the function module 1401 can be used (activated) (S207).

  That is, if the license key is valid and the identifier is included in the “function” item of the license key, the function module 1401 is determined to be usable. In other cases (including the case where there is no license file 160 corresponding to the SDK application 140), it is determined that the functional module 1401 cannot be used. Note that the license key is valid means that the machine number of the license key matches the machine number of the image forming apparatus 10 and the expiration date of the license key has not expired.

  When it is determined that it cannot be used (No in S207), the license management unit 152 adds the identifier of the functional module to the unbootable list (S208).

  When the processing of steps S206 to S08 is completed for all entries (license information) included in the license list 170 (S209), the license management unit 152 sets the activation disabled list as the license status of the SDK application 140 to be activated. Is output to the activation control unit 153 (S209).

  Subsequently, the activation control unit 153 performs activation control of the SDK application 140 based on the activation impossibility list (S210). Specifically, the activation or use of the activation module 1401 included in the activation impossibility list is restricted (suppressed). As a result, for example, the SDK application 140 relating to a copy job restricts the use of some functions, such as color copy cannot be used.

  The processing contents of FIG. 9 will be specifically described based on the SDK application 140 of FIG. For example, in FIG. 3, it is assumed that only the functional module 1401a is licensed with the license key included in the license file 160. In this case, when activation of the SDK application 140 is requested, the functional module 1401b is included in the activation impossibility list, and activation is suppressed. Therefore, the functions of the function module 1401a and the function module 1401c can be used. The function of the function module 1401c can be used because the function module 1401c is not subject to license management.

  In FIG. 9, an example in which the activation disable list is notified to the activation control unit 153 as the license status of the SDK application 140 has been described. However, the list information of function modules that can be activated is transferred from the license management unit 152 to the activation control unit 153. Notification may be made.

  As described above, the image forming apparatus 10 according to the present embodiment generates in advance the license list 170 that is the list information of the functional modules 1401 that need to be checked for the license, and the license information 170 is activated when the SDK application 140 is activated. Only the functional modules entered in the list 170 are checked for licenses. Therefore, the number of license checks can be reduced, and an increase in the startup time of the entire SDK application 140 can be appropriately suppressed.

  For example, FIG. 10 is a diagram for explaining a processing procedure when the SDK application is activated when there is no license list.

  In steps S301 to S305, it is determined whether or not all functional modules 1401 included in the SDK application 140 to be activated are license targets (S303). For the function module 1401 determined to be a license target, the presence / absence of a license key, the validity of the license key, etc. are determined (S304, S305), and the unusable function module 1401 is added to the function disable list ( S306). When the check is completed for all the functional modules 1401 (S307), the activation control of the SDK application 140 is performed based on the check result (S308).

  The difference between the processing content of FIG. 10 and the processing content executed by the image forming apparatus 10 of the present embodiment can be expressed more simply as shown in FIG.

  FIG. 11 is a diagram for explaining the reason why the activation of the SDK application is accelerated by the license list.

  In FIG. 10, (A) shows the processing contents of FIG. In (A), it is shown that when the SDK application 140 is activated, the license-related check is performed on all the function modules 1401 of the SDK application 140. In the example shown in the figure, nine checks are performed at each activation.

  On the other hand, (B) shows the processing contents executed by the image forming apparatus 10 of the present embodiment. In the present embodiment, when the SDK application 140 is installed, it is checked whether or not all functional modules 1401 of the SDK application 140 are license targets, and the license list 170 is generated. In the drawing, an example in which two function modules 1401 are determined to be licensed is shown. At the time of activation, a license check is executed only for these two function modules 1401 entered in the license list 170.

  Thus, as the number of functional modules included in the SDK application 140 increases, the effect of the present embodiment becomes more prominent. Note that the license list 170 does not necessarily have to be generated at the time of installation. This is because the license list 170 is generated at the first activation even if it is not generated at the time of installation.

  The license list 170 is encrypted and stored, and is checked for tampering when used. Accordingly, it is possible to appropriately prevent an illegal license from being obtained by falsification of the license list 170 (deleting an entry from the license list 170 to avoid a license check of the functional module 1401 related to the entry).

  Even when tampering of the license list 170 is detected at the time of activation, the license list 170 is generated again, so that the SDK application 140 can be smoothly activated within the range of the license. .

  In the present embodiment, the example in which the license information of the functional module 1401 to be license managed is included in the license list 170 has been described. However, the license list 170 may be configured by license information of functional modules 1401 that are not subject to license management. That is, it suffices if it is possible to identify which functional module 170 is the target of license management from the license list 170.

  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 10 Image forming apparatus 11 Controller 12 Scanner 13 Printer 14 Modem 15 Network interface 16 Operation panel 20 PC
21 Operation unit 22 License transmission unit 111 CPU
112 RAM
113 ROM
114 HDD
121 OS
122 Control service 123 Application 130 Standard application 150 SDK platform 131 Copy application 132 Scan application 133 Fax application 134 Print application 140, 141, 142, 143 SDK application 151 License introduction unit 152 License management unit 153 Start control unit 154 Encryption processing unit 155 True False determination unit 160 License file 170 License list

JP 2008-016013 A

Claims (16)

An information processing apparatus capable of starting an application composed of a plurality of program modules,
A license that can identify a program module that is subject to license management among the plurality of program modules based on information indicating whether the program module associated with each program module is subject to license management. A license object identification information generating means for generating object identification information;
In response to a request for starting the application, if a program module that cannot be used is included in the program module that is the target of license management based on the license target identification information, the start of the program module is restricted, and the license management target A non-program module includes an activation restriction unit that activates without determining whether or not it can be used . When the license object identification information is not generated when the application activation request is input, the license object identification information generating unit generates the license object identification information,
The information processing apparatus according to claim 1, wherein the activation restriction unit restricts activation of the program module based on the license object identification information generated in response to the activation request. In response to the activation request of the application, it has a legitimacy judging means for judging legitimacy of the license object identification information,
The license object identification information generating unit regenerates the license object identification information when the validity determination unit determines that the license object identification information is invalid,
The information processing apparatus according to claim 1, wherein the activation restriction unit restricts activation of the program module based on the regenerated license object identification information.   4. The information processing apparatus according to claim 1, wherein the license target identification information includes identification information of the program module to be licensed. 5. The license subject identification information generating means, the license subject identification information processing apparatus according to claim 1 to 3 any one wherein Rukoto turn into cipher. A license determination method executed by an information processing apparatus capable of starting an application composed of a plurality of program modules,
A license that can identify a program module that is subject to license management among the plurality of program modules based on information indicating whether the program module associated with each program module is subject to license management. A license object identification information generation procedure for generating object identification information;
In response to a request for starting the application, if a program module that cannot be used is included in the program module that is the target of license management based on the license target identification information, the start of the program module is restricted, and the license management target A non-program module includes a start restriction procedure that starts without determining whether or not the program module can be used . When the license object identification information is not generated when the application activation request is input, the license object identification information generation procedure generates the license object identification information,
7. The license determination method according to claim 6, wherein the activation restriction procedure restricts activation of the program module based on the license object identification information generated in response to the activation request. In response to the application activation request, a validity determination procedure for determining the validity of the license object identification information;
A license object identification information regeneration procedure for regenerating the license object identification information when the license object identification information is determined to be invalid in the validity determination procedure;
8. The license determination method according to claim 6, wherein the activation restriction procedure restricts activation of the program module based on the regenerated license object identification information.   9. The license determination method according to claim 6, wherein the license object identification information includes identification information of the program module to be licensed. The license subject identification information generating step, the license determination method of any one of claims 7 to 9, wherein Rukoto turn into cipher the license subject identification information. In an information processing device that can start an application composed of a plurality of program modules,
A license that can identify a program module that is subject to license management among the plurality of program modules based on information indicating whether the program module associated with each program module is subject to license management. A license object identification information generation procedure for generating object identification information;
In response to a request for starting the application, if a program module that cannot be used is included in the program module that is the target of license management based on the license target identification information, the start of the program module is restricted, and the license management target The non-program module is a program for executing an activation restriction procedure that activates without determining whether or not it can be used. When the license object identification information is not generated when the application activation request is input, the license object identification information generation procedure generates the license object identification information,
12. The program according to claim 11, wherein the activation restriction procedure restricts activation of the program module based on the license object identification information generated in response to the activation request. In response to the application activation request, a validity determination procedure for determining the validity of the license object identification information;
A license object identification information regeneration procedure for regenerating the license object identification information when the license object identification information is determined to be invalid in the validity determination procedure;
The program according to claim 11 or 12, wherein the activation restriction procedure restricts activation of the program module based on the regenerated license object identification information.   14. The program according to claim 11, wherein the license object identification information includes identification information of the program module to be licensed. The license subject identification information generating procedure, claims 11 to 14 to any one claim of a program, characterized in Rukoto turn into cipher the license subject identification information.   A computer-readable recording medium on which the program according to claim 11 is recorded.

Images