JP2001109625A - Software charging system - Google Patents

Abstract

PROBLEM TO BE SOLVED: To prevent charging processing to the license of software and a user to be the object of user identification information while illegally using the user identification information of the other person. SOLUTION: A public key A and a secret key A are prepared by using a user processor ID (S301), and a public key B and a secret key B are prepared on the side of a charging device as well (S302). When desired software and information on a person to be charged are inputted (S303), the license key B, the public key A and input information are transmitted to the charging device (S304), license information is restored/updated/enciphered (S305-S310), the license key A and the public key B are transmitted to a user processor (S311) and charging is executed (S312). The license key transmitted from the charging device is deciphered (S313) and when a license is remained, the execution of software is permitted (S315-S316). Then, corresponding to the execution time of software, license information is updated (S317)/enciphered (S318).

Description

DETAILED DESCRIPTION OF THE INVENTION

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to a user processing apparatus and a software billing system for managing software licenses, and more particularly to a user processing for permitting use of software in a specific user processing apparatus based on a request from a user. The present invention relates to a software billing system suitable for device and software license management.

[0002]

2. Description of the Related Art Conventionally, for example, JP-A-9-282157, JP-A-10-20956, and JP-A-10-3
No. 33901 discloses a software license management system corresponding to a user's desired use time, number of times, and functions. In such a license management system, software identification information, user identification information for charging, license request contents (use time, number of times,
Function) is provided to the billing device via the network. The license management system also provides a software use key (a ticket for executing the program, a decryption key for a part of an encrypted program, etc.) corresponding to the request, and incorporates the software into the software on the user processing device side. By making the software executable,
Provision of a license corresponding to the user's request is realized.

[0003]

However, the above-mentioned conventional technology has the following problems because the identification information of the charging device is not taken into account when the software license is provided. . The first problem is that the use of software cannot be restricted to a particular user processing device. The reason is that at the time of software execution or use key issuance, only the identification information of the software part, the user identification information, and the content of the license request are considered in the user processing device and the billing device, and the identification information of the user processing device is considered. It is not done.

[0004] The second problem is that, when executing software or issuing a use key, it is necessary to always connect a user processing device to be actually used to a charging device via a network. The reason is that in order to obtain a use key for the software and incorporate it into the software,
This is because software must be executed on the user processing device at the time of connection to the network, and an environment in which the user processing device can directly communicate with the billing device via a network or the like must be provided. In providing a software use key in a file or the like, there is a high possibility that the use key is illegally copied, and there is a problem in terms of security.

A third problem is that the license management unit is not flexible. The reason is that although there are license provision modes managed only by time or number of times, the license cannot be flexibly provided for each software. A fourth problem is that, even when the user identification information of another person is illegally used, a software license is provided, and a process for charging the target user is performed. The reason is that only the user identification information is considered at the time of providing the license and charging the user, and the identification information of the user processing device is not considered.

The present invention solves the above-mentioned problems, and
A first object is to provide a software billing system in which a software license is provided in a specific user processing device, and a software license is not provided even if the user identification information of another person is misused. A second object of the present invention is to provide a software billing system in which a software license can be provided without connecting the user processing device main body to a billing device via a network. A third object of the present invention is to provide a software billing system in which a flexible license can be provided for each software. Fourth Embodiment of the Present Invention
The purpose of this is, even if the user identity of another person is misused,
An object of the present invention is to provide a software billing system in which software license provision and user billing processing are not performed.

[0007]

According to a first software billing system of the present invention, an identification means of a user processing device, an information input means, a software identification means for licensing based on input information from a user, Updating means for reflecting the license addition content of the software to be licensed based on the input information from the user and the user processing identification information, billing means corresponding to the license content, and specifying whether the licensed software can be used in the user processing device Means, software control means corresponding to the remaining license information, and means for updating the remaining license information corresponding to the used license, software that can be executed only by a specific user processing device for the license requested by the user is licensed, It operates so that charging is performed.

The second software billing system of the present invention provides a license based on license information encryption / decryption means, a user processing device identification means, information input means, and input information from a user. Software specifying means, updating means for reflecting the additional license content of software to be licensed based on input information from a user and user processing identification information, charging means corresponding to the license content, and And a software control unit corresponding to the remaining license information, and a unit for updating the remaining license information corresponding to the used license.
Software that can be executed only by a specific user processing device for the license requested by the user is licensed, and operates so as to be charged.

The third software billing system according to the present invention further comprises a public key encryption / decryption means for license information, an identification means for a user processing device based on whether or not the encrypted license information can be decrypted, and an information input means. Means for specifying software to be licensed based on input information from a user, updating means for reflecting additional license content of software to be licensed based on input information from a user and user processing identification information, and Billing means, specifying means that the licensed software can be used by the user processing device, software control means corresponding to the remaining license information, and updating means of the remaining license information corresponding to the used license,
Software that can be executed only by a specific user processing device for the license requested by the user is licensed, and operates so as to be charged.

A fourth software billing system according to the present invention comprises: a public key encryption / decryption means for license information; an identification means for a user processing device based on whether or not the encrypted license information can be decrypted; Verification means, information input means, software specification means for licensing based on input information from the user, and update reflecting the additional license content of software to be licensed based on input information from the user and user processing identification information Means, a billing means corresponding to the license content, a means for specifying whether the licensed software can be used by the user processing device, a software control means corresponding to the remaining license information, and a request for the remaining license information corresponding to the used license. Updating means only for the license requested by the user Software that can only be run at a constant user processing device is licensed to operate as charging is performed.

A fifth software billing system according to the present invention comprises: a public key encryption / decryption means for license information; an identification means for a user processing device based on whether or not the encrypted license information can be decrypted; Verification means, license unit type selection means, information input means, software specification means for licensing based on input information from the user, and licensing based on input information from the user and user processing identification information Update means to reflect the software license additions;
A charging unit corresponding to the license content, a specifying unit for determining whether the licensed software can be used in the user processing device, a software control unit corresponding to the remaining license information, and an updating unit for the remaining license information corresponding to the used license. In addition, software that can be executed only by a specific user processing device for the number of licenses requested in units of a license selected by the user is licensed, and operation is performed so that charging is performed.

Further, a sixth software billing system of the present invention includes a public key encryption / decryption means for license information, an identification means for a user processing device based on whether the encrypted license information can be decrypted, and a user using a storage device. Means for exchanging information between the processing device and the billing device, means for inputting information, means for specifying software to be licensed based on input information from the user, and licensing based on input information from the user and user processing identification information Update means for reflecting the software license addition content, billing means corresponding to the license content, and means for specifying whether the licensed software can be used by the user processing device;
Software control means corresponding to the remaining license information;
Software for updating remaining license information corresponding to the used license is provided, and software that can be executed only by a specific user processing device for the number of licenses requested by the user is licensed, and is licensed between the user processing device and the charging device via a storage device. It operates so that information can be exchanged and billing is performed.

Further, a seventh software billing system according to the present invention includes a public key encryption / decryption unit for license information, a storage unit identification unit based on whether or not the encrypted license information can be decrypted, and a user process by the storage unit. Means for exchanging information between the device and the billing device, means for inputting information, means for specifying software to be licensed based on information input from the user, and software for licensing based on information input from the user and storage device identification information Updating means for reflecting the added license content, charging means corresponding to the license content, means for specifying whether the licensed software can be used by the user processing device, and software control means corresponding to the remaining license information. A means for updating the remaining license information corresponding to the license is provided, and the user requests License amount corresponding licensed software that can be executed only by a particular user processor, via the storage device can exchange the license information with the user apparatus and the billing system, it operates as the charging is performed.

An eighth software billing system according to the present invention comprises: a public key encryption / decryption means for license information; a means for identifying a user processing device based on whether or not the encrypted license information can be decrypted; Identification means based on user information and user processing device identification information, information input means, software identification means licensing based on user input information, and software licensing based on user input information and user processing identification information Update means for reflecting the license addition content, charging means corresponding to the license content, and identification means for determining whether the licensed software can be used in the user processing device;
Software control means corresponding to the remaining license information;
Software that has means for updating remaining license information corresponding to the license used and can be executed only by a specific user processing device for the number of licenses requested by the user uses a payee ID and user processing device registered in advance. It operates so that it is licensed only to the user who has been charged and charging is performed. The present invention for solving the above problems is characterized by comprising:

[0015]

Next, embodiments of the present invention will be described in detail with reference to the drawings. FIG. 1 is a configuration block diagram showing a first embodiment of the invention. In the figure,
The user processing device 100 includes a user processing device storage unit 11
0, software 120, license information updating unit 13
0, a charging device transmitting unit 140, a remaining license information checking unit 150, and a user processing device specifying unit 160. The charging device 200 is connected to the user processing device 100 via a network, and includes a payee checker 210, a license information updating unit 220, a license information transmitting unit 230, and a charging processing unit 240.

Next, the configuration of each component will be described in detail. The user processing device storage unit 110 holds license information. FIG. 3 is a configuration diagram illustrating license information. The license information includes a software ID, a user processing device ID, and remaining license information. FIG. 4 is an explanatory diagram of license information stored in the user processing device storage unit.

The software 120 is used by the user processing device 1
This is software that can be executed on Windows. The license information updating unit 130 updates the remaining license information (number of times, time, etc.) in the license information according to the usage amount of the software 120. The billing device transmitting section 140 includes license information and software I for identifying software.
D, information on the license addition, and information such as payee information (ID, password, etc.) are transmitted to the charging device 200. The remaining license information check unit 150 controls the execution of the software 120 according to the remaining license information in the license information. The user processing specifying unit 160 sets the billing device 2
It is determined whether the license information transmitted from 00 is information for a user processing device.

The payee checker 210 verifies that the payee ID and password are correct when the charge form is a credit card or the like. License information update unit 2
20 updates the license information according to the content of the additional license requested by the user. The license information transmitting unit 230 transmits the license information updated by the license information updating unit 220 to the user processing device 100.
After completing the transmission of the license information, the billing processing unit 240
The payee is charged for the additional license.

Next, the overall operation of the present embodiment will be described in detail with reference to the flowchart of FIG. First, the user selects desired software (software ID) using the user processing device 100, and inputs a desired license amount (license addition content) and payee information (step 101). Next, the user processing device 100 transmits the license information, the software ID, the license addition content, and the payee information to the charging device 200 (step 10).
2).

In the billing device 200, the user processing device 10
It is verified whether the payee information transmitted from 0 is correct, and if not correct, the process is terminated (step 10).
3). Subsequently, the charging device 200 updates the license information by adding the selected software by the amount of the added license (step 104). Then, the billing device 200 transmits the updated license information to the user processing device 100 (Step 105). Furthermore,
The charging device 200 charges the payee (step 106).

The user processing device 100 includes a billing device 200
User processing device ID in license information sent from
Are checked to see if they match, and if they do not match, the process ends (step 107). Subsequently, the user processing device 1
In step 00, it is checked from the remaining license information in the license information whether a license remains, and if not, the process ends (step 108). If the license remains in step 108, the user processing device 100 permits execution of the software (step 10).
9). In step 109, the user processing device 100 updates the license information for the used license (step 110).

Next, a second embodiment of the present invention will be described in detail with reference to the drawings. Referring to FIG. 5, in the second embodiment of the present invention, an encryption unit 131 is added to license information update unit 130 having the configuration shown in FIG. 1, and a decryption unit 161 is added to user processing device identification unit 160. , A decryption unit 221 is added to the license information update unit 220, and an encryption unit 222 is added. FIG. 7 is an explanatory diagram of storage information stored in the user processing device storage unit 110. The user processing device storage unit 110 holds a license key (encrypted license information), a decryption key, and encryption key information. License information is software ID
, User processing device ID, and remaining license information (see FIG. 3).

Next, the configuration of each component will be described in detail. The encryption unit 131 encrypts license information of the user processing device 100. The decryption unit 161 decrypts license information from the license key transmitted from the charging device 200. The decryption unit 221 decrypts the license key transmitted from the charging device transmission unit 140 into license information. The encryption unit 222 encrypts the license information updated by the license information update unit 220 and creates a license key.

Next, the overall operation of this embodiment will be described in detail with reference to the flowchart of FIG. Using the user processing apparatus 100, the user selects desired software (software ID), and inputs a desired license amount (license addition content) and payee information (step 201). The user processing device 100 transmits the license key or the user processing device ID, the software ID, the added license content, and the payee information to the charging device 200 (Step 202).

The billing device 200 includes the user processing device 100
It is verified whether the payee information transmitted from is correct or not, and if not correct, the process is terminated (step 20).
3). Billing device 200 determines whether a license key has been sent from user processing device 100 (step 204). If it has not been sent, license information is created from the software ID and the user processing device ID (step 205). On the other hand, if the license key has been sent from the user processing device 100, the license key is decrypted (step 206). Billing device 20
0 adds the selected software to the license addition content and updates the license information (step 207). Billing device 200 encrypts the license information and creates a license key (step 208).
Billing device 200 transmits the created license key to user processing device 100 (step 209),
Billing is performed on the payee (step 210).

The user processing device 100 decrypts the license key transmitted from the user processing device 100 (step 211). Subsequently, the user processing device 100 checks whether the user processing device IDs in the license information match, and ends the processing if they do not match (step 2).
12). The user processing device 100 checks the remaining license information in the license information to check whether any licenses remain. If no licenses remain, the process ends (step 213). In step 213, if a license remains, execution of the software is permitted (step 214), and the license information is updated by the used license (step 215), and the updated license information is encrypted (step 216). .

Next, a third embodiment of the present invention will be described in detail with reference to the drawings. The third embodiment of the present invention has the same configuration as FIG. FIG. 9 is an explanatory diagram of storage information stored in the user processing device storage unit 110. The user processing device storage unit 110 stores a license key (encrypted license information), a public key (A), a secret key (A) (created with a user processing device ID), a public key (B) (a billing device side). The license information includes a software ID, a user processing device ID, and remaining license information (see FIG. 3).

Next, the overall operation of the present embodiment will be described in detail with reference to the flowchart of FIG. First, the user processing device 100 creates a public key (A) and a secret key (A) using the user processing device ID (step 30).
1). Next, the public key (B) and the private key (B) are created on the billing device 200 side (step 302). Using the user processing device 100, the user selects desired software (software ID), and inputs a desired license amount (license addition content) and payee information (step 303). Then, the user processing device 100 stores the license key (B) (the license information is encrypted with the public key (B)) or the user processing device ID, the software ID, the additional license content, the payee information, and the public key (A). The data is transmitted to the billing device (step 304).

The billing device 200 includes the user processing device 100
It verifies whether the payee information transmitted from is correct or not, and ends the processing if it is not correct (step 30).
5). Billing device 200 determines whether a license key has been sent from user processing device 100 (step 30).
6) If the license key has been sent, the license key (B) is decrypted with the private key (B) (step 308). If not, the software ID and the user processing device ID are sent. Then, the license information is created (step 307). The billing device 200 updates the license information of the selected software by the content of the license (step 309), encrypts the license information with the public key (A), and creates the license key (A) (step 309). 310), the created license key (A) and public key (B) are
(Step 311). And the billing device 20
0 means that the payee is charged (step 31).
2).

The user processing device 100 includes a billing device 200
Decrypts the license key (A) transmitted from the server with the secret key (A) (step 313). User processing device 100
Executes the step 315 when the license key (A) can be decrypted, and terminates the processing when the license key (A) cannot be decrypted (the user processing device ID is different) (step 314).
The user processing device 100 checks the remaining license information in the license information to check whether any licenses remain, and if not, ends the process (step 315). The user processing device 100 proceeds to step 315
If the license remains, execution of the software is permitted (step 316), and step 315 is executed.
, The license information is updated by the used license (step 317), and the license information updated in step 317 is encrypted (step 318).

Next, a fourth embodiment of the present invention will be described in detail with reference to the drawings. Referring to FIG.
The fourth embodiment of the present invention has a configuration in which a random number comparing unit 170 is added to the user processing device 100 having the configuration shown in FIG. 5, and a random number generating unit 132 is added to the license information updating unit 130.

Next, the configuration of each component will be described in detail. The random number generation unit 132 generates a random number, and stores the random number of the license information and the data in the random number unit of the user processing device storage unit 110. The random number comparing section 170 compares the random number section of the user processing device storage section 110 with the random number section of the license information. The user processing device storage unit 110 holds a license key (encrypted license information), a public key (A), a secret key (A), and a public key (B) (see FIG. 9). , A software ID, a user processing device ID, remaining license information, and a random number unit (a different value can be held for each software) (see FIG. 12).

Next, the overall operation of this embodiment will be described in detail with reference to the flowchart of FIG. The user processing device 100 creates a public key (A) and a secret key (A) using the user processing device ID (step 401).
On the other hand, the billing device 200 creates a public key (B) and a secret key (B) (step 402). Using the user processing device 100, the user selects desired software (software ID), and inputs a desired license amount (license addition content) and payee information (step 403). The user processing device 100 transmits the license key (B) (encrypting the license information with the public key (B)) or the user processing device ID, software ID, additional license content, payee information, and public key (A) to the charging device. (Step 404).

The charging apparatus 200 verifies whether the payee information transmitted from the user processing apparatus is correct, and terminates the processing if not correct (step 405). The billing device 200 determines whether the license key has been sent from the user processing device 100 (step 406), and if so, decrypts the license key (B) with the secret key (B). (Step 408) If not sent, license information is created from the software ID and the user processing device ID (Step 40).
7). The billing device 200 updates the license information by adding the selected software to the license addition content (step 409). The billing device 200
The license information is encrypted with the public key (A), a license key (A) is created (step 410), and the created license key (A) and public key (B) are sent to the user processing device 10.
0 (step 411), and billing is performed on the payee (step 412).

The user processing device 100 includes a billing device 200
Decrypts the license key (A) transmitted from the server with the secret key (A) (step 413). User processing device 100
Executes the step 415 if the license key (A) can be decrypted, and ends the processing if the license key (A) cannot be decrypted (the user processing device ID is different) (step 414).
The user processing device 100 compares the random number portion in the license information with the random number portion in the user processing device storage portion. If the two match, the process proceeds to step 416. If not, the process ends (step 416). 415). The user processing device 100 checks the remaining license information in the license information, checks whether a license remains, and terminates the process if no license remains (step 416).

The user processing device 100 proceeds to step 416
If the license remains, execution of the software is permitted (step 417), and the license information is updated by the used license (step 41).
8). The user processing device 100 generates a random number and stores it in the random number portion of the license information and the random number portion of the user processing device storage unit (step 419), and encrypts the license information updated in step 419 (step 42).
0).

Next, a fifth embodiment of the present invention will be described in detail with reference to the drawings. The fifth embodiment of the present invention has the same configuration as FIG. The user processing device storage unit 110 holds a license key (encrypted license information), a public key (A), a secret key (A), and a public key (B) (see FIG. 9). , A software ID, a user processing device ID, a remaining license type, a remaining license amount, and a random number part (see FIG. 12). The difference from the fourth embodiment is that the remaining license information is divided into types and amounts, so that the remaining licenses are managed for each software in units of a plurality of licenses such as time, frequency, number of sheets, and number of licenses. It becomes possible.

Next, a sixth embodiment of the present invention will be described in detail with reference to the drawings. Referring to FIG.
According to the sixth embodiment of the present invention, instead of the billing device transmitting unit of the user processing device 100 having the configuration shown in FIG.
0 instead of the charging unit 260 and the charging device 200
, A storage device 300 for providing license information to the user processing device 100 and an information storage unit 310.

Next, the configuration of each component will be described in detail. The information writing unit 180 includes the user processing device 1
The information of the license key No. 00 is recorded in the information storage unit 310 of the storage device 300. The information writing unit 250 records information on the license key of the charging device 200 in the information storage unit 310 of the storage device 300. The billing processing unit 260 implements a post-payment method such as credit or billing on the spot.
The information stored in the user processing device storage unit 110 holds a license key (encrypted license information) or a user processing device ID, a public key (A), a secret key (A), and a public key (B) ( The license information includes a software ID, a user processing device ID, and remaining license information (see FIG. 3).

Next, the overall operation of this embodiment will be described in detail with reference to the flowchart of FIG. First, the user processing device 100 uses the user processing device ID to
Create a public key (A) and a secret key (A) (step 60)
1). On the other hand, the charging device 200 also creates a public key (B) and a secret key (B) (Step 602). Then, the user processing device 100 sets the user processing device ID and the public key (A)
Is transferred to the storage device 300 (step 603).

Subsequently, from the storage device 300 to the charging terminal,
The license key (B), the user processing device ID, and the public key (A) are transferred (step 604). Using the charging terminal, the user can select the desired software (software I
D) is selected and a desired license amount (license addition content) is input (step 605). The charging terminal transmits the input license key (B) or user processing device ID, software ID, additional license content, and public key (A) to the charging device 200 (step 606).

The billing device 200 includes the user processing device 100
(Step 607), and if so, decrypts the license key (B) with the secret key (B) (step 60).
9) If it has not been sent, the software ID
Then, license information is created from the user processing device ID (step 608). The billing device 200 updates the license information of the selected software by the amount of the added license (step 610), encrypts the license information with the public key (A), and creates the license key (A) (step 611). ). Then, charging apparatus 200 transmits the created license key (A) and public key (B) to user processing apparatus 100 (step 612), and charges the payee with the charging terminal (step 612). Step 613).

The storage device 300 stores the license key or the user processing device ID and the public keys (A) and (B) transmitted from the charging device 200 (step 614). Then, the storage device 300 transfers the license key (A) to the user processing device 100 (Step 615). The user processing device 100 decrypts the license key (A) with the secret key (A) (Step 616). User processing device 100
If the license key (A) can be decrypted, the step 618 is performed. If the license key (A) cannot be decrypted (the user processing device ID is different), the process ends (step 617).
The user processing device 100 checks the remaining license information in the license information, checks whether any license remains, and terminates the process if there is no remaining license (step 618). The user processing device 100 proceeds to step 618
If the license remains, the execution of the software is permitted (step 619) and the step 619 is executed.
, The license information is updated by the used license (step 620), and the license information updated in step 620 is encrypted (step 621).

Next, a seventh embodiment of the present invention will be described in detail with reference to the drawings. Referring to FIG.
The seventh embodiment of the present invention includes a storage device specifying unit 190 and a decoding unit 191 instead of the user processing device 160 of the user processing device 100 having the configuration shown in FIG.

Next, the configuration of each component will be described in detail. The storage device identification unit 190 identifies whether the license information transmitted from the charging device 200 is information for a storage device. The decryption unit 191 decrypts license information from the license key transferred from the storage device. The user processing device storage unit 110 stores a license key (encrypted license information) or a storage device ID,
The public key (A), the private key (A), and the public key (B) are held (see FIG. 20).
, User processing device ID, and remaining license information (see FIG. 3).

Next, the overall operation of the present embodiment will be described in detail with reference to the flowchart of FIG. Billing device 2
On the 00 side, a public key (B) and a secret key (B) are created (step 701). On the other hand, the storage device 300
D is transferred to the user processing device 100 (step 70).
2). The user processing device 100 creates a public key (A) and a secret key (A) using the storage device ID (step 703), and transfers the public key (A) to the storage device 300 (step 704). .

Then, the storage device 300 transfers the license key (B) or the user processing device ID and the public key (A) to the charging terminal (Step 705). Using the charging terminal, the user can select the desired software (software I
D), and inputs a desired license amount (contents of additional license) (step 706), and a license key (B) or user processing device ID, software I
D, the license addition content, and the public key (A)
0 (step 707).

The billing device 200 includes the user processing device 100
(Step 708), and if so, decrypts the license key (B) with the secret key (B) (step 71).
0) If not sent, software ID
Then, license information is created from the user processing device ID (step 709). Then, the billing device 200 updates the license information of the selected software by the content of the license (step 711), encrypts the license information with the public key (A), and creates the license key (A) (step 711). Step 712). Billing device 200 transmits the created license key (A) and public key (B) to user processing device 100 (step 713). The charging terminal performs charging for the payee (step 714).

The storage device 300 stores the license key or the storage device ID and the public keys (A) and (B) transmitted from the charging device 200 (step 715).
The storage device 300 transfers the license key (A) to the user processing device 100 (Step 716). The user processing device 100 decrypts the license key (A) with the secret key (A) (Step 717). If the license key (A) can be decrypted, the user processing device 100 proceeds to step 71
9 and if the decryption is not possible (the user processing device ID is different), the process ends (step 718). The user processing device 100 checks the remaining license information in the license information, checks whether a license remains, and terminates the process if no license remains (step 71).
9). In step 719, if there is a license remaining, the user processing device 100 permits execution of the software (step 720), and in step 720, updates the license information for the used license (step 721). Then, the user processing device 100
Encrypts the license information updated in step 721 (step 722).

Next, an eighth embodiment of the present invention will be described in detail with reference to the drawings. Referring to FIG.
An eighth embodiment of the present invention is a charging apparatus 2 having the configuration shown in FIG.
Payer I instead of payer checker 210 of 00
D, a public key check unit 270, a payee ID, and a public key table 280.

Next, the configuration of each component will be described in detail. The payee ID and public key check unit 270
Identify whether the public key is for the payee. The payee ID and public key table 280 stores the correspondence status between the payee ID and the public key. The information stored in the user processing device storage unit 110 holds a license key (encrypted license information), a public key (A), a secret key (A), and a public key (B) (see FIG. 9). The license information includes a software ID, a user processing device ID, and remaining license information (see FIG. 3).

Next, the overall operation of the present embodiment will be described in detail with reference to the flowchart of FIG. The user processing device 100 creates a public key (A) and a secret key (A) using the user processing device ID (step 801).
On the other hand, the billing device 200 creates a public key (B) and a secret key (B) (step 802). The user processing device 100 transmits (prior registration) the payee information (ID) and the public key (A) to the charging device 200 (step 80).
3). Billing apparatus 200 creates a correspondence table between the biller ID transmitted from user processing apparatus 100 and public key (A) (step 804).

Using the user processing device 100, the user selects desired software (software ID),
A desired license amount (license addition content) and payee information are input (step 805), and a license key (B) (the license information is encrypted with a public key (B)).
Alternatively, the user processing device ID, software ID, license addition content, payee information, public key (A)
00 (step 806).

The billing device 200 includes the user processing device 100
It is verified that the payee information transmitted from is correct and that the payee ID and the public key (A) correspond to each other. If the payee ID is not correct, the process ends (step 80).
7). Further, the billing device 200 includes the user processing device 10
It is determined whether or not the license key has been sent from 0 (step 808). If the license key has been sent, the license key (B) is decrypted with the secret key (B) (step 810).
And if it has not been sent,
License information is created from D and the user processing device ID (step 809).

The billing device 200 updates the license information of the selected software by the amount of the added license (step 811), encrypts the license information with the public key (A), and creates the license key (A). (Step 812). Billing device 200 transmits the created license key (A) and public key (B) to user processing device 100 (step 813), and bills the payee (step 814).

The user processing device 100 includes a billing device 200
Decrypts the license key (A) transmitted from the server with the secret key (A) (step 815). If the license key (A) can be decrypted, the user processing device 100
If step 817 is executed and decoding is not possible (user processing device ID is different), the process is terminated (step 81).
6). The user processing device 100 checks the remaining license information in the license information to check whether any licenses remain, and if not, ends the processing (step 817). In step 817, if there is a license remaining, the user processing device 100 permits execution of the software (step 818), and in step 818, updates the license information for the used license (step 819). 8
The license information updated in step 19 is encrypted (step 820).

In the above embodiment, the user processing device and the billing device have been described in many cases. However, the present invention is not limited to this, and various design changes may be made within a range obvious to those skilled in the art. May be used.

[0058]

According to the software billing system of the present invention described above, the following effects can be obtained. First, the first effect is that the use of software can be limited to a specific user processing device. The reason is that when the software is executed in the user processing device, it is verified whether the license information is for the user processing device.

A second effect is that a software license can be provided not only by connecting the user processing apparatus main body to a charging apparatus via a network, but also by using a storage device (such as a memory card) for a home game or the like. It is. The reason is that by restricting the use of the software to a specific main unit and verifying the license information with encryption and random numbers, it is possible to prevent unauthorized use of the license even in a means other than a network that is difficult to secure. This is because

A third effect is that a license form can be selected for each piece of software executed on the user processing device. The reason is that the license form can be selected for each software by dividing and managing the remaining license information into a license type and a remaining license amount.

A fourth effect is that it is possible to prevent a license of software by improperly using the user identification information of another person and a billing process to a user who is a target of the user identification information. The reason is that when updating the license, both the user identification information and the information of the user processing device are verified and charging is performed, so that the user is not charged incorrectly.

[Brief description of the drawings]

FIG. 1 is a block diagram showing a configuration of a first exemplary embodiment of the present invention.

FIG. 2 is a flowchart showing an operation of the first embodiment.

FIG. 3 is an example of license information according to the first to third and sixth to eighth embodiments.

FIG. 4 is an example of information stored in a user storage device storage unit according to the first embodiment;

FIG. 5 is a block diagram showing the configuration of the second and third embodiments of the present invention.

FIG. 6 is a flowchart showing the operation of the second embodiment.

FIG. 7 is an example of information stored in a user storage device storage unit according to the second embodiment;

FIG. 8 is a flowchart showing the operation of the third embodiment.

FIG. 9 is an example of information stored in a user storage device storage unit according to the third and eighth embodiments.

FIG. 10 is a block diagram showing a configuration of the fourth and fifth embodiments of the present invention.

FIG. 11 is a flowchart showing the operation of the fourth and fifth embodiments.

FIG. 12 is an example of license information according to the fourth embodiment.

FIG. 13 is an example of information stored in a user storage device storage unit according to the fourth and fifth embodiments.

FIG. 14 is an example of license information according to the fifth embodiment.

FIG. 15 is a block diagram showing a configuration of a sixth exemplary embodiment of the present invention.

FIG. 16 is a flowchart showing the operation of the sixth embodiment.

FIG. 17 illustrates an example of information stored in a user storage device storage unit according to the sixth embodiment;

FIG. 18 is a block diagram illustrating a configuration of a seventh exemplary embodiment of the present invention.

FIG. 19 is a flowchart showing the operation of the seventh embodiment.

FIG. 20 is an example of information stored in a user storage device storage unit according to the seventh embodiment;

FIG. 21 is a block diagram showing a configuration of an eighth embodiment of the present invention.

FIG. 22 is a flowchart showing the operation of the eighth embodiment.

[Explanation of symbols]

 REFERENCE SIGNS LIST 100 user processing device 110 user processing device storage unit 120 software 130 license information updating unit 131 encryption unit (user processing device) 132 random number generation unit 140 billing device transmission unit 150 remaining license information check unit 160 user processing device identification unit 161 decryption Unit (user processing device) 170 random number comparing unit 180 information writing unit (user processing device) 190 storage device specifying unit 200 billing device 210 payee check unit 220 license information updating unit 221 decryption unit (billing device) 222 encryption unit (Charging device) 230 License information transmitting unit 240 Charging processing unit 250 Information writing unit (charging device) 260 Charging unit 270 Charger ID, public key check unit 280 Charger ID, public key table 300 Storage device 310 Information storage Department

Claims (8)

[Claims] 1. An identification means of a user processing device, an information input means, a software specifying means to be licensed based on input information from a user, and a license based on input information from a user and user processing identification information. Updating means for reflecting the software license addition content, billing means corresponding to the license content, means for specifying whether the licensed software can be used by the user processing device, software control means corresponding to the remaining license information, use Software updating system for updating remaining license information corresponding to the license. 2. An encryption / decryption means for license information,
Identification means of the user processing device, information input means, identification means for software to be licensed based on input information from the user, and additional license content of software to be licensed based on input information from the user and user processing identification information Updating means for reflecting the license, charging means corresponding to the license content, specifying means for determining whether the licensed software can be used by the user processing device, software controlling means corresponding to the remaining license information, and corresponding to the used license. A software billing system comprising: means for updating remaining license information. 3. A public key encryption / decryption means for license information, an identification means for a user processing device based on whether encrypted license information can be decrypted, an information input means, and a license based on input information from a user. Means for specifying software to be licensed, updating means for reflecting the additional content of the software to be licensed based on input information from the user and user processing identification information, billing means corresponding to the license content, and processing of the licensed software by the user processing. A software billing system comprising: a unit for specifying whether the apparatus can be used by a device; a software control unit corresponding to remaining license information; and a unit for updating remaining license information corresponding to a used license. 4. A public key encryption / decryption means for license information, a means for identifying a user processing device based on whether or not the encrypted license information can be decrypted, a license information verification means using a random number, an information input means, Means for identifying software to license based on input information from
Updating means for reflecting the license addition content of the software to be licensed based on the input information from the user and the user processing identification information, billing means corresponding to the license content, and specifying whether the licensed software can be used in the user processing device Means, software control means corresponding to the remaining license information, and means for updating the remaining license information corresponding to the used license. 5. Public key encryption / decryption means for license information, identification means for a user processing device based on whether the encrypted license information can be decrypted, license information verification means using random numbers, and license unit type selection means Means for inputting information, means for specifying software to be licensed based on input information from the user, and updating means for reflecting the additional license content of the software to be licensed based on the information input from the user and the user process identification information. Charging means corresponding to the license content, specifying means for determining whether the licensed software can be used in the user processing device, software controlling means corresponding to the remaining license information, and updating means for the remaining license information corresponding to the used license. And a software billing system comprising: 6. A means for public key encryption / decryption of license information, a means for identifying a user processing device based on whether or not the encrypted license information can be decrypted, and a means for exchanging information between the user processing device and a billing device using a storage device Means for inputting information, means for specifying software to be licensed based on input information from the user, and updating means for reflecting the additional license content of the software to be licensed based on the information input from the user and the user process identification information. A billing unit corresponding to the license content, a specifying unit for determining whether the licensed software can be used in the user processing device,
Software control means corresponding to the remaining license information;
A software billing system comprising: means for updating remaining license information corresponding to a used license. 7. A public key encryption / decryption unit for license information, a storage device identification unit based on whether the encrypted license information can be decrypted, and an information exchange unit between the user processing device and the billing device using the storage device. Information input means, means for specifying software to be licensed based on input information from the user, updating means for reflecting the additional content of the license of the software to be licensed based on the input information from the user and the storage device identification information, A charging unit corresponding to the license content, a specifying unit for determining whether the licensed software can be used by the user processing device, a software control unit corresponding to the remaining license information, and an updating unit for the remaining license information corresponding to the used license. A software billing system comprising: 8. Public key encryption / decryption means for license information, identification means for a user processing device based on whether the encrypted license information can be decrypted, and user identification means based on a payee ID and user processing device identification information. Information input means, specifying means for software to be licensed based on the input information from the user, updating means for reflecting the additional content of the software to be licensed based on the input information from the user and the user processing identification information, A billing unit corresponding to the license content, a specifying unit for determining whether the licensed software can be used in the user processing device,
Software control means corresponding to the remaining license information;
A software billing system comprising: means for updating remaining license information corresponding to a used license.