JP3042309B2 - Software license system - Google Patents

Description

DETAILED DESCRIPTION OF THE INVENTION

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to a software licensing system.

[0002]

2. Description of the Related Art Conventionally, software usage right information relating to license of software of licensed software is encrypted and stored in a nonvolatile memory (for example, a flash memory).
When the license software is executed, the operating system decrypts the software usage right information and presents the software usage right information. For example, the number of software types (product code, etc.) that specifies the type of software, the availability of use, and the version of software use rights are stored in non-volatile memory that remains the same as the number of software units even after the power is turned off. It had been.

In recent years, software license forms have become more complicated. For example, (a) for test sale,
An execution period is set in the software, and the software can be used during the period. However, after the execution period expires, the right to use is automatically extinguished. It is usually desirable to have a complicated license form such as a method for determining whether to support the program, (c) a method for limiting the number of users who can execute programs simultaneously in one network instead of limiting the sites where programs are executed. It is becoming more and more.

[0004] As described above, the license form of software is becoming more complicated, and with this, software usage right information is significantly increasing. For this reason, the capacity of the non-volatile memory for storing the software usage right information is insufficient. However, since the non-volatile memory is expensive, there is a problem that it cannot be mounted in a computer in large numbers.

When licensing the software, the user sends a certificate to the maker that he / she has paid the fee, and the maker sends the software usage right to the user as a key which is encrypted with a unique encryption algorithm. Notification may be used. However, this method has a problem in that it is necessary to exchange telephone, fax, electronic mail, and the like with the user.

Further, the software usage right file is
Since it exists as a file, it is vulnerable to being exposed before the system administrator, and there is a problem that the usage right information is falsified and easily used illegally, and the security level is low.

Further, the description format of the software usage right file must conform to the interpretation mechanism provided by the operating system supply side, and it is difficult to adopt a more flexible usage right information interpretation system for each software. There is a problem that there is.

Further, in recent years, with the spread of local area networks, a network license system for limiting the number of users for each network has become mainstream instead of a site license system for giving execution permission for each site. The licensing method has the same problem as described above.

[0009]

As described above, the conventional software licensing system has the following problems. First, in the conventional software licensing method, there is a problem that a lot of expensive non-volatile memories need to be installed in a computer in response to an increase in software usage right information accompanying the complexity of software licensing. . Also, if the manufacturer notifies the user of the software usage right as an encrypted key when licensing the software, there is a problem that the exchange with the user is complicated. Furthermore, in the conventional software licensing method, since the software usage right file exists as a file, the software usage right file is exposed unprotected before the system administrator, the usage right information is falsified and easily used illegally, and the security level is low. There is a problem. In addition, the description format of the software usage right file must conform to the interpretation mechanism provided by the operating system supply side, and it is difficult to adopt a more flexible usage right information interpretation method for each software. There is. Further, there is a similar problem in the network license system.

An object of the present invention is to provide a software licensing system capable of retaining a large number of software usage right information using a limited amount of non-volatile memory by solving the above-mentioned conventional disadvantages. With the goal.

[0011]

According to one aspect of the present invention, there is provided software license information for reading software license information of a license software from a floppy disk when installing the license software. A read unit and a memory for securing the software usage right information and reading (adding) the memory into the memory
A software usage right information file writing means for writing the software usage right information file into a software usage right information file; and a software usage right key for compressing and encrypting the software usage right information read into the memory and converting it into fixed-size key code data. Code generation means; software usage right key code writing means for writing the software usage right key code created by the software usage right key code generation means into a software usage right key code storage area comprising a non-volatile memory; Software usage right information erasing means for erasing software usage right information of the disk. According to a second aspect of the present invention, there is provided a machine ID reading means for reading a machine ID when installing license software, a password generating means for generating a password from a machine ID and a software name, a password inquiring means for inquiring a password to a terminal, Password checking means for checking whether the passwords match, and if the passwords match, software for securing the use right information in the memory and reading (adding) it into the memory, and writing it to the software use right information file Software usage right information file writing means, software usage right key code generation means for compressing and encrypting the software usage right information read into the memory, and converting the software usage right information into fixed-size key code data; Code generation means Thus it has a configuration and a software license key code writing means for writing the software license key code created software license key code storing area consisting of the non-volatile memory. According to a third aspect of the present invention, when the system is started, the software usage right information of the license software is read from the software usage right information file, and the software usage right information is secured in a memory and read into the memory (additional writing). Software usage right information reading means; software usage right key code generation means for compressing and encrypting the software usage right information read into the memory and converting the same into fixed-size key code data; Software usage right key code reading means for reading out the software usage right key code created in advance by the code generation means and previously written in the software usage right key code storage area formed of the non-volatile memory by the software usage right key code writing means And these futo (A) tamper checking means for comparing the usage right key codes, releasing the memory and turning off the usage right information flag if they do not match, and turning on the usage right information flag if they match, and software read into the memory; Software use right information providing means for providing use right information to the application program. According to a fourth aspect of the present invention, there is provided a software which reads out the software usage right information of the license software from the software usage right information file when the system is started up, secures a memory for the software usage right information, and reads the software usage right information into the memory. Means for reading usage right information, means for providing software usage right information for providing the software usage right information read into the memory to the application program, and a connection for establishing a connection if there is a request for waiting for a network connection request from the license software. Software use right information obtaining means for obtaining software use right information using the software use right information providing means according to claim 3 in response to the establishment means and the inquiry about the presence or absence of the use right from the license software. And the software And software license information interpreting means for interpreting the information in the license server use right information, and configured to have a software license information notifying means for notifying the license software that requested the presence of software licenses. The invention according to claim 5 has an information interpreting mechanism conversion table including a set of a software name and an information interpreting mechanism, and in the case of software existing in the table, executes a corresponding use right information interpreting mechanism. In the case of software that does not exist in the table, the information is interpreted using the software use right information interpreting means according to claim 4.

[0012]

According to the software licensing method of the present invention, software usage right key code generation means is used to compress and encrypt software usage right information and convert it into fixed-size key code data. Write the key code to the software usage right key code storage area consisting of nonvolatile memory. Therefore, a large amount of software usage right information can be held using a limited amount of nonvolatile memory.

[0013]

Embodiments of the present invention will be described below in detail with reference to the drawings. In the embodiment, a workstation is used as a computer, and UNIX is used as a base operating system. However, the present invention can be similarly applied to other systems.

Further, in the embodiment, the software usage right information file is placed in the path "/ etc / license" and is described in the format shown in FIG. In FIG.
One line for each piece of software, the information from the beginning to the next appearing space is the information for identifying the software, the next appearing ":" is the number of users who can run simultaneously on the network, and the next appearing ":" is the Indicates the period of use. FIG.
In the example shown in FIG. 1, use of LenseSoftWare1 is permitted until March 31, 1994, and the number of users permitted to use on the network is up to two. In LicenseSoftWare2 and 3, the number of users permitted to use indefinitely and permitted to use on the network is three or two, respectively.

FIG. 1 is a block diagram showing a system configuration of a software licensing system according to one embodiment of the present invention. In FIG. 1, the software licensing method according to the present embodiment includes a software usage right information reading unit 17, a software usage right information file writing unit 11, a software usage right key code generation unit 12, The software use right key code writing means 16 and the software use right information erasing means 18 are provided. These means are set in the kernel.

The software usage right information reading means 17 comprises:
When the license software is installed, the software use right information of the license software is read from the floppy disk 60. The software usage right information file writing means 11 secures a predetermined area in the memory 30 and reads the software usage right information into the area (additional writing).
At the same time, it is written to the software usage right information file 40. Software usage right key code generation means 12
Compresses and encrypts the software usage right information read into the memory 30 and converts it into fixed-size key code data. The software use right key code writing means 16
The software usage right key code created by the software usage right key code generation means 12 is stored in the nonvolatile memory 5.
0: Software use right key code storage area 51
Write to. The software usage right information erasing means 18
The software usage right information of the floppy disk 60 is deleted.

Next, the operation of this embodiment will be described with reference to the processing flow shown in FIG. Software installation right information reading means 1 when installing license software
Then, the software use right information of the license software stored in the floppy disk 60 is read out using the command 7 (step 601). At this time, if the software usage right information that should have been stored in the floppy disk 60 has already been erased (step 602), it is considered that this floppy disk has already been used, and the processing ends there. If the software usage right information 60 is correctly read, this information is secured in a memory and this memory 3
0 is read (added) as software usage right information, and written to the software usage right information file 40 by using the software usage right information file writing means 11 (step 603). Thereafter, the software use right information of the floppy disk 60 is deleted using the software use right information erasing means 18 (step 604).
By doing so, the floppy disk 60 becomes used and cannot be used for reading the software usage right information thereafter. Next, a software usage right key code is created by using the software usage right key code generation means 12 (step 605), and the software usage right key code is written by using the software usage right key code writing means 16. The data is written into the software usage right key code storage area 51 provided in the nonvolatile memory 50 (step 606).

As shown in FIG. 1, the software licensing system according to the present embodiment includes a machine ID reading unit 19,
Password generation means 20, password inquiry means 21, password check means 22, software usage right information file writing means 11, software usage right key code generation means 12, software usage right key code writing means 16.

When installing the license software, the machine ID reading means 19 stores the nonvolatile memory 50
The machine ID 51 stored in the file is read. The password generation means 20 generates a password from the machine ID 51 and the software name. The password inquiry means 21
The terminal inquires of a terminal (not shown) provided in a maker or the like for a password. The password checking unit 22 checks whether the password generated by the password generating unit 20 matches the password inquired to the terminal by the password inquiring unit 21. If the passwords match, the software usage right information file writing means 11 secures a memory for the usage right information, reads (writes) the usage right information into the memory, and writes the information into the software usage right information file 40. The software usage right key code generation means 12 compresses and encrypts the software usage right information 30 read into the memory and converts it into fixed size key code data. The software usage right key code writing unit 16 writes the software usage right key code created by the software usage right key code generation unit 12 into the software usage right key code storage area 51 provided in the nonvolatile memory 50.

Next, the operation will be described with reference to the processing flow shown in FIG. The licensed software user must provide the machine that manages the licensed software with the machine I
D and a document certifying purchase (for example, a copy of a slip or a registration card) are sent. Sending is done by mail, electronic mail, FAX, telephone, etc. The maker shall pay out a password unique to the machine from the terminal through a communication line. The password to be paid out here is of the same logic as that calculated (generated) inside the machine,
It shall be generated on the manufacturer side.

First, when installing the license software, the machine ID reading means 19 is used to read the machine ID 51 from the non-volatile memory 50 (step 701). Then, using the password generation means 20,
A password is generated from the machine ID 51 and the software name (Step 702). Next, the password inquiry means 21 is used to inquire of the terminal provided at the maker about the password (step 703). Using the password checking means 22, the password generating means 20
Password and password inquiry means 21
It is checked whether the password inquired to the terminal matches (step 704). If the passwords do not match, the process ends there. If the passwords match, a predetermined area is secured in the memory 30 and the software usage right information incorporated in the installation program is read (added) as software usage right information into this area, and the software usage right information is read. The file is written into the software use right information file 40 using the file writing means 11 (step 705). Thereafter, the software use right information incorporated in the installation program is deleted using the software use right information erasing means 18 (step 706). Next, a software use right key code is created using the software use right key code generation means 12 (step 707), and the software use right key code is written using the software use right key code writing means 16. Writing to the software usage right key code storage area 51 composed of a nonvolatile memory (step 70)
8).

The present system differs from the above-mentioned system using a floppy disk in that a maker must pay out a keyword, but is advantageous in that software can be provided on a read-only medium. Further, in a sales form between a maker and a user, it can be sold out once.

As shown in FIG. 1, the software licensing system according to the present embodiment transmits software license information of the license software from the software license information file 40 when the system is started up. At the same time, the software usage right information reading means 10 which secures a predetermined area in the memory 30 and reads (adds) the software usage right information into this area, compresses the software usage right information read into the memory 30 and A software usage right key code generating means 12 for encrypting and converting to fixed size key code data; Software usage right key code storage area 5 provided in 50 The software usage right key code reading means 13 for reading out the software usage right key code written in the above is compared with these software usage right key codes. If they do not match, the memory is released and the usage right information flag is turned off. And a tampering checking unit 14 for turning on the usage right information flag when they match, and a software usage right information providing unit 15 for providing the software usage right information read into the memory to the application program.

Next, the operation will be described with reference to the processing flow shown in FIG. First, when starting up the system, "/ e
At the same time as reading "tc / init", the software usage right information reading means 10 is used to read the software usage right information file 40 ("/ etc / license" file).
, The software usage right information of the license software is read out, a predetermined area is secured in the memory 30 (allocated), and the software usage right information is read (added) into this area (steps 401 and 402). next,
Using the software usage right key code generation means 12,
The software usage right information read into the memory 30 is compressed and encrypted and converted into fixed-size key code data (step 403). Specifically, for example, the data is converted into data of a fixed size by an algorithm as shown in FIG. This algorithm is extremely important in protecting usage rights. This conversion scheme must be devised by the operating system provider and kept secret from users. That is, the format of the software usage right information file is made public, but the encryption / compression algorithm and the interface for writing to the nonvolatile memory 50 are kept private. This prevents the user from falsifying the software usage right information file and using the license program illegally. The disclosure of the format of the software usage right information file facilitates provision of the license program by VAR, ISV, or the like. Note that the conversion mechanism may be irreversible. That is, the software usage right file may not be able to be decrypted from the converted data. As a result, the size of the data required to store the usage right information can be reduced, and the usage right information can be stored in a memory of a limited size. Next, using the software usage right key code reading means 13, the software usage right key code previously written in the software usage right key code storage area 51 formed of a non-volatile memory is read (step 404). Then, Step 40
The software usage right key codes obtained in Steps 3 and 404 are compared (Step 405). If the software usage right key codes do not match using the falsification checking means 14, the memory is released (Step 407). The use right information flag is turned off (step 408). If the software use right key codes match, the use right information flag is turned on (step 406).

FIG. 2 is a block diagram showing the configuration of a license server (software usage right information server) 80 that constitutes a software license system according to this embodiment. In FIG. 2, a license server 80 waits for a network connection request from the license software, and establishes a connection if there is a request. Software usage right information obtaining means 82 for obtaining software usage right information using the software usage right information providing means 15, and software usage right information interpreting means for interpreting information of the software usage right information in the license server 80. 83 and software use right information notifying means 84 for notifying the license software which has requested the presence or absence of the software use right
And

The license server 80 has an information interpreting mechanism conversion table 85 comprising a set of a software name and an information interpreting mechanism.
If the software does not exist in the information interpretation conversion table 85, the software interprets the information using the software use right information interpreting means 83. There is a configuration to perform.

Next, the operation will be described with reference to the processing flow shown in FIG. Note that the processing flow shown in FIG. 8 shows the processing flow of both the license program 100 and the license server 80 and the exchange of data between both processes.
The left side shows the processing flow of the license program 100, and the right side shows the processing flow of the software use right information license server 80, and the dotted arrow connecting the left and right processing flows shows the data flow.

When the site license method is adopted, the license program 100 may directly inquire of the kernel about the execution right information. However, when the network license method is adopted, a system-resident process such as the license server 80 handles this. To do.

The software use right information providing means 15 comprises:
Provided by a system call that takes the name of the software as an argument. For example, a C language interface has a format as shown in FIG. Licenses in FIG.
In the example of e-SoftWare, since the number of users who can run simultaneously in the network is 2, the license program first issues a broadcast at startup to inquire which host the license server 80 is. The lower layer interface of the network uses, for example, TCP / IP.

The software use right information license server responds to an inquiry as to whether or not it is a host (step 8).
01), and reply that they are the license server 80. The license server 80 waits for a network connection request from the license software (step 811), and if so, establishes a connection via the connection establishing means 81 (steps 812, 80).
2).

Here, it is also possible to adopt a method in which the license server 80 is set in advance in the machine that executes the license software. In this case, the broadcast inquiry process is not required. In addition, restrictions on the underlying network,
If broadcast cannot be used for the purpose of operational security protection, it is also possible to adopt the server fixing method as described above.

When the connection is established, the license program inquires of the license server 80 whether or not there is an execution right (step 803). License server 8
0 is kernel software usage right information providing means 15
Then, the use right information of the corresponding software is obtained (step 813), and the information is interpreted.

Here, when a software information acquisition system call occurs in the kernel, it is first checked whether or not the usage right information flag is on. If the flag is on and there is information of this software on the table, Returns this usage right information.

The information interpreting mechanism 90 in FIG. 2 is installed as a program on the host running the license server 80 when the license software is installed. For example, "/ opt / License
The file is placed as a file with a name such as “SoftWare1 / resolve”.

The software use right information interpreting means 83
Check the information interpreting mechanism conversion table 85 (step 81
4), the corresponding program (above, "/ opt / Lic
enseSoftWare1 / resolve ") is loaded into the memory and the information is interpreted (step 815). The license information thus obtained is notified to the license program 100 using the software use right information notifying means 84 (step 816).

Normally, in order to avoid complication of the processing on the side of the license program 100, this notification (response) is made in binary of with / without use right. However, the security is not limited to this, and a more secure system can be adopted. For example, data on the network is encrypted and the license program 100
To be interpreted on the side of the license program 100.

However, at least the number of users on the network is counted on the license server 80 side. For example, in the case of LicenseSoftWare1 in FIG. 3, since the number of users who can run simultaneously in the network is two, the license server responds that up to the second user has the execution right, but does not execute the third user. Answer no right.

On the license program side, the execution is started when the information indicating the right to use is returned (steps 804 and 8).
05), if information indicating that there is no use right is returned, execution is stopped (steps 804 and 806).

During the execution of the license program, the connection with the license server is kept connected. When the connection is disconnected, the license server considers that the execution of the license program has been interrupted, and decrements the counter. In other words, execution is stopped immediately after disconnection. This is to prevent unauthorized use by disconnecting the network after activating the license program.

Although the present invention has been described with reference to the preferred embodiments, the present invention is not necessarily limited to the above embodiments.

[0041]

As described above, according to the software licensing method of the present invention, it is possible to hold a large amount of software use right information using a limited amount of nonvolatile memory. . In addition, the disclosure of software usage right information in a file format facilitates the provision of application programs.

[Brief description of the drawings]

FIG. 1 is a block diagram showing a system configuration of a software licensing system according to an embodiment of the present invention.

FIG. 2 is a block diagram illustrating a configuration of a license server in the embodiment.

FIG. 3 is a diagram illustrating an example of a software use right information file.

FIG. 4 is a flowchart for explaining a processing procedure at the time of system startup.

FIG. 5 is a flowchart illustrating a procedure for creating key code data.

FIG. 6 is a flowchart for explaining a processing procedure in the embodiment.

FIG. 7 is a flowchart illustrating a processing procedure in the embodiment.

FIG. 8 is a flowchart showing the processing flow of both the license program and the software use right information license server, and the transfer of data between them.

FIG. 9 is a diagram illustrating an example of software usage right information provided by software usage right information providing means.

[Explanation of symbols]

 10 software usage right information file reading means 11 software usage right information file writing means 12 software usage right key code generation means 13 software usage right key code reading means 14 falsification checking means 15 software usage right information providing means 16 Software usage right key code writing means 17 Software usage right information reading means 18 Software usage right information erasing means 19 Machine ID reading means 20 Password generating means 21 Password inquiry means 22 Password checking means 50 Nonvolatile memory 81 Connection establishing means 82 software usage right information obtaining means 83 software usage right information interpretation means 84 software usage right information notifying means 85 interpretation mechanism conversion table 90 information interpretation mechanism

────────────────────────────────────────────────── ─── Continuation of front page (56) References JP-A-58-87631 (JP, A) JP-A-2-277128 (JP, A) JP-A-3-278161 (JP, A) JP-A-4- 238536 (JP, A) JP-A-2-14321 (JP, A) JP-A-61-25261 (JP, A) JP-A-4-100148 (JP, A) JP-A-5-274275 (JP, A) JP-A-7-110767 (JP, A) (58) Fields investigated (Int. Cl. ⁷ , DB name) G06F 9/06, 12/00, 12/14

Claims (4)

(57) [Claims] 1. A software use right information reading means for reading software use right information of a license software from a floppy disk at the time of installation of the license software, and securing a memory of the software use right information and storing the software use right information in the memory. A software usage right information file writing means for reading and writing the software usage right information file to a software usage right information file ;
Key code data of fixed size by shrinking and encrypting
Software usage right key code generating means for converting the software usage right key code generated by the software usage right key code generation means into the software
A) separate from the usage rights information file
In the software usage right key code storage area
And software license key code writing means burn them, software licensing scheme characterized by having a software license information erasing means for erasing the software license information of the floppy disk. 2. A machine ID reading means for reading a machine ID when installing license software, a password generating means for generating a password from a machine ID and a software name, a password inquiring means for inquiring a password to a terminal, Password checking means for checking whether the passwords match, and, if the passwords match, securing a memory of the usage right information, reading the memory into the memory, and writing the software usage right information file to the software usage right information file Software usage right key code generation means for compressing and encrypting the software usage right information read into the memory and converting it into fixed-size key code data, and the software usage right key code generation means A software usage right key code writing means for writing the software usage right key code into a software usage right key code storage area comprising a non-volatile memory. 3. The software usage right information read out of the software usage right information file from the software usage right information file when the system is started up, and the software usage right information secured in the memory and read into the memory. Reading means for reading the software usage right information read into the memory ;
Key code data of fixed size by shrinking and encrypting
Software usage right key code generation means for converting the software usage right key code generation means, and the software usage right information file
Compare the software usage right key code with the software usage right key code reading means that reads the software usage right key code separately written in the software usage right key code storage area composed of non-volatile memory. Tamper checking means for releasing the memory and turning off the usage right information flag if they do not match, and turning on the usage right information flag if they match, using software read into the memory when the system is started up. And a software use right information providing means for providing the right information to the application program. 4. The software usage right information read out of the software usage right information file from the software usage right information file when the system is started up, and the software usage right information secured in the memory and read into the memory. Reading means, software usage right information providing means for providing the software usage right information read into the memory when the system is started up to the application program, and a network connection request from the license software. Means for establishing a connection to be established, and means for acquiring software usage right information for obtaining software usage right information using the software usage right information providing means in response to an inquiry about the presence or absence of the usage right from the licensed software. The soft And software license information interpretation means for interpreting the information of the license server software usage rights information, and software license information notification means for notifying the license software that requested the presence or absence of software of the right-of-use, and the software name An information interpreter consisting of a set of information interpreting mechanisms
Software having a composition conversion table and existing in the information interpretation mechanism conversion table
In the case of, execute the applicable use right information interpretation mechanism,
Software that does not exist in the information interpreter conversion table
In the case of (a), the software use right information interpretation means is used.
Software licensing scheme and performs information interpreted are.