JP2002073191A - System and method for meter-rate program use permission - Google Patents

Abstract

PROBLEM TO BE SOLVED: To provide a meter-rate program use permission system which enables speedy charging processing to a program to be the object of meter-rate charging without fail. SOLUTION: This system is composed of a vender side system 20, which is a computer system on the side to permit the use of the program to be the object of meter-rate charging, and a user side system 30, which is a computer system on the side to use the program, connected with the vender side system 20 through a communication network 25 or the like, the user side system 30 is composed of clients 31-32 of computers for running a program of which the use is permitted, and a license server 33 having a use result managing part 35 for recording the user result of the program by the clients 31-32 and reporting it to the vender side system 20 and the vender side system 20 is provided with a bill issuing device 22 for issuing a bill on the basis of the use result transmitted from the license server 33.

Description

DETAILED DESCRIPTION OF THE INVENTION

[0001]

[0001] 1. Field of the Invention [0002] The present invention relates to a computer system for licensing a program subject to pay-as-you-go billing and managing the license, and more particularly to a method for counting usage fees and billing.

[0002]

2. Description of the Related Art In recent years, with the expansion of use of computers, a program providing company (a so-called vendor side) has not licensed a program for each individual user, but a company having a large number of users (a so-called user). side)
The number of users (users) that can be used simultaneously can be determined in advance and the license is extremely licensed, and a fee corresponding to the number is collected. However, in such a business form, the user must contract with the vendor before deciding on the appropriate number of programs that will not hinder use and will not be excessive before the actual use. You are forced to feel difficult.

[0003] For this reason, there has been proposed a system in which charging is performed in accordance with the usage record for a certain period (for example, every month), that is, a so-called pay-per-use system. With the pay-as-you-go system, there is no need to predict and contract in advance for the required number, and there is no problem that the user cannot use the program and waits because the number of contracts is insufficient. Also,
If the usage record is low, the usage fee is correspondingly low, so it can be said that the user is highly convinced. As such a pay-as-you-go system, there is, for example, a "program license management system of a pay-as-you-go system" disclosed in JP-A-10-320070.

[0004]

By the way, in order to perform pay-as-you-go billing, it is essential that the licensor accumulates the actual usage and issues a bill. It is desired that such a process of totalizing the usage results and issuing a bill be quickly performed without error. However, in the conventional system of the pay-as-you-go system, there is no system that supports the totalization of usage results and the issuance of bills.

Accordingly, a first object of the present invention is to provide a pay-as-you-use program licensing system which enables quick and error-free billing for a pay-as-you-go program. That is. Further, in the pay-as-you-go system, there is a possibility that a problem occurs in the management of the user's balance that a large amount of bill exceeding the budget is received because the usage record is much larger than expected.
On the other hand, there has been proposed a method in which the user is notified of the usage record on the terminal each time (for example, the method disclosed in the above-mentioned Japanese Patent Application Laid-Open No. 10-320070). This problem cannot be solved when it is an organization and there are a large number of operators, because it is difficult to ensure that all the operators suppress the use results.

In view of the above problems, it is a second object of the present invention to use a program which is charged in accordance with the usage record in an organization such as a company so as not to greatly exceed a planned amount. To provide a pay-as-you-go program license system capable of suppressing the above.

[0007]

In order to achieve the first object, a pay-as-you-go program licensing system is a vender-side system which is a computer system for licensing a program subject to pay-as-you-go billing. And a user-side system connected to the vendor-side system via a communication network, the user-side system being a computer system that uses the program, wherein the user-side system comprises:
A client that is a computer that executes the licensed program, and a use record management unit that records the use record of the program by the client and reports the record to the vendor system.
And a billing data generating means for generating billing data for billing a billing amount for the use result based on the use result reported from the use result management means.

In order to achieve the second object,
The pay-per-use program license system further includes a license key issuing unit that generates a license key that is data indicating the content of a license agreement that has been previously exchanged and transmits the license key to the user system. A license management unit for managing the client to use the program within a license agreement indicated by the license key transmitted from the license key issuing unit; and a license management unit for limiting use of the program. Use restriction acquisition means for acquiring an instruction from an administrator, wherein the license management means uses the program by the client within the range of the license agreement and within the range of the instruction acquired from the administrator. It is characterized in that it is managed so that

Further, in order to achieve the first and second objects, the present invention is realized as a method in which characteristic components of the pay-as-you-use program licensing system are steps, or a program for causing a computer to execute those steps. It can also be realized as.

[0010]

DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS An embodiment of a pay-per-use program license system according to the present invention will be described below with reference to the drawings. FIG. 1 is a block diagram showing the overall configuration of a pay-as-you-use program license system 10 according to the present embodiment. The pay-as-you-use program licensing system 10 includes a vendor system 20 that licenses (licenses) a program to be charged for pay-as-you-go and performs a billing process. User side system 30 ~
And a communication network 25 such as a WAN connecting the vendor system 20 and the user systems 30 to 40.

The vendor system 20 is based on a license key issuing device 21 which is a computer for issuing an encrypted text file (license key) indicating the contents of the license, and based on reports of use results from the user systems 30 to 40. And a LAN 29 connecting the license key issuing device 21 and the bill issuing device 22 to each other.

The license key issuing device 21 has a license DB 21a consisting of a set of records in which the contents of each license are recorded for all target programs.
And generates a license key by encrypting the contents of the license DB 21a for each record, and transmits the generated license key to the target user or based on the dialog with the operator.
license key generation / transmission unit 21b for updating a
Consists of

FIG. 2 is a diagram showing the contents of the license DB 21a. Each row (record) corresponds to an individual license, and “License I” for identifying an individual license.
"D", a "server ID" such as a MAC address, host ID, or IP address for identifying a license server in the license, a "program name" for identifying a target program, and an execution place (client) of the program. It is composed of a “license type” indicating whether or not (node knock / floating), a “license start date” indicating a license start date, and a “license end date” indicating an end date.

The bill issuing device 22 accumulates reports on the results of program use periodically transmitted from the user side systems 30 to 40 via the communication network 25, collects the reports on a monthly basis, and calculates the total billing amount. A bill creation unit 23 for calculating and creating a bill (electronic file) indicating the contents thereof, and a bill sending unit 24 for sending the bill by e-mail to a pre-registered user (communication terminal). .

The user side system 30 (40) includes clients 31 to 32, which are computers on which programs to be licensed are installed and executed,
A license server 33 which is a computer for managing that the use of the programs by the clients 31 to 32 is within the range licensed from the vendor side system 20 and for reporting the use results to the vendor side system 20; A LAN 39 connects the clients 31 to 32 and the license server 33.

The license server 33 manages the use of the target program within the range of the license indicated by the license key sent from the license key issuing device 21, and records the use status of the program. And a use result management unit 35 that reports (transmits) a table showing the use results for each day to the bill issuing device 22 via the communication network 25.

The clients 31 to 32 are general-purpose computer platforms that execute programs to be licensed. However, for all programs to be licensed, in addition to the processing unique to the program, (i) at the time of startup, a request for permission to start from the license server 33, and processing for starting only when permission is obtained. , (Ii) at the end of that, the license server 33
A certain routine is incorporated in advance so as to perform the process of reporting to the user.

FIG. 3 is a sequence diagram showing an overall communication flow in the pay-per-use program license system 10 shown in FIG. Here, the vendor system 2
0 shows the exchange of communication between the license key issuing device 21 and the bill issuing device 22 constituting the license server 33 and the clients 31 to 32 constituting the user system 30 to be licensed. ing.

First, the license key issuing device 21 sends a license key to the license server 33 of the user-side system 30 to be licensed. The license server 33 receiving the license key,
Each time a use request (a program activation request) is received from a client 31-32, it is confirmed that the license is used within the range of the contract (program name, license type, license period, etc.) indicated by the license key. Later, we will give permission. The clients 31 to 32 that have finished executing the program notify the license server 33 of the fact.

The license server 33 records such exchanges with the clients 31 to 32 as a log, creates a table showing one day's usage record, and transmits the table to the bill issuing device 22. The bill issuing device 22
The received usage results are accumulated, and when a certain date is reached each month, the usage results of the previous month are totaled for each license, and a bill for the charge is issued.

Next, the individual devices 2 in the pay-as-you-go program licensing system 10 configured as described above.
Detailed functions and operations of 1, 22, 31, 32, and 33 will be specifically described. FIG. 4 is a flowchart showing the operation of the license key issuing device 21 when a new license is established.

The license key issuing device 21 receives an input for each item of the license DB 21a shown in FIG. 2 from an administrator or the like of the vendor system 20, and adds and stores it as a new record in the license DB 21a. (Step S100). Here, if the administrator or a specific communication device receives a notice to update the license period for an existing specific license, the license key issuing device 21 records the license key in the record. A new license is registered (updated) by updating the “license start date” and the “license end date” (for example, changing the date to one month later).

Next, in accordance with an instruction from the vendor-side administrator, the license key generation / transmission unit 21b of the license key issuing device 21 reads one record from the license DB 21a and stores the secret key that has been shared with the license server 33 in advance. The license key is generated by encrypting the record using (step S101).
FIG. 5 is a diagram illustrating an example of a license key. It is composed of a set of a plaintext indicating the contents of one record registered in the license DB 21a and a corresponding ciphertext, and these are in a relationship between the message and the digital signature.

The license key generation / transmission unit 21b stores the generated license key in the license server 33 registered as the “server ID” of the license.
(Step S102). FIG. 6 is a functional block diagram for explaining detailed functions of the license management unit 34 and the usage record management unit 35 of the license server 33.

The user of the system 30 on the user side sets the license management unit 34 as a voluntary use restriction as the number of concurrently used programs, that is, the maximum number of clients that can use the target program at the same time (upper limit number of users). The maximum number of users setting unit 34d for acquiring the maximum number of users, and the maximum number of users storage unit 34 for storing and holding the acquired maximum number of users
c and the license key transmitted from the license key issuing device 21, and encrypts the plaintext contained therein using a secret key shared in advance with the license key issuing device 21. After confirming that the cipher text included in the license key matches, the license key holding unit 34b for holding the license key therein, and the license of the license indicated by the license key held in the license key holding unit 34b. A use permission / non-permission determining unit 34a that permits use of the program in response to a use request from the client 31 within the range and within the range of the upper limit number of users stored in the upper limit user number storage unit 34c.

The usage record management unit 35 is a client 31 for starting (permission of use) and terminating the target program.
Log recording unit 3 that accumulates and records the communication log between .about.32 and the license server 33 as a program use log
5a and a validity verification unit 35b for referring to the usage log to identify an individual session (a continuous section from the start to the end of the program) and verify that there is no fraudulent activity in the session; Aggregation unit 35c that writes information indicating the contents of a session whose validity has been verified into usage record table storage unit 35d.
And a use result table storage unit 35d for holding a use result table composed of a group of written sessions, and, at a certain time every day, extract all sessions for the previous day from the use result table storage unit 35d and hold a license key. The report unit 35e transmits the license key read from the unit 34b together with the usage record for one day to the bill issuing apparatus 22.

FIG. 7 is an example of a screen display by the upper limit user number setting unit 34d of the license server 33 shown in FIG. The upper limit user number setting unit 34 d
When an instruction from the administrator at 0 is received, the maximum number of users already set (stored in the maximum number of users storage unit 34c) (“the current maximum value”) is displayed on a screen such as a CRT provided in the license server 33. ), An input form for acquiring the new maximum number of users ("new upper limit"), and a confirmation button ("update" / "cancel") for the update are displayed. I do. When the “update” button is pressed, the “new upper limit value” set at that time is overwritten in the upper limit user number storage unit 34c, thereby updating the upper limit user number.

The administrator in the user system 30
Through this screen, the number of users (programs) that can be used simultaneously can be limited to three (three) in consideration of the monthly scheduled usage fee. FIG. 8 is a flowchart showing the operation of the use permission / refusal determination unit 34a of the license server 33 shown in FIG.

The usage permission / non-permission determining unit 34a
When signals related to the start / end of the target program are received from the LAN devices 1 to 32 via the LAN 39 (step S11)
0), it is determined whether the signal is a "use request" or an "end notification" (step S111). as a result,
In the case of "end notification", a variable J indicating the number of users is reduced by one and stored in order to store that the number of users using the program has decreased by one (step S1). S112).

On the other hand, if the received signal is a "use request", the use permission / non-permission determining unit 34a first refers to the license key held in the license key holding unit 34b, and determines the "use request". Is within the range of the license indicated by the license key (step S113). Specifically, by referring to an internal calendar timer, it is possible to confirm that the date is within the period indicated by the license key, or when the license mode is “node locked”,
Confirm that the requesting client corresponds to the permitted node.

As a result, if it is within the range of the license, subsequently, it is determined whether or not the number J of users already licensed has reached the maximum number of users MAX stored in the maximum number of users storage section 34c. (Step S11)
4). If the number has not yet been reached, a “license” is returned to the client that issued the “use request” via the LAN 39 (step S115). J is incremented by 1 and stored (step S116).

On the other hand, if the “use request” from the client exceeds the range of the license, or if the number of users J who have already licensed the use has reached the maximum number of users MAX, the client "Refusal of use"
Is returned (step S117). In this way,
When a client issues a "use request" for a program, it checks both the license restrictions and the user's voluntary restrictions, and only when both are met, will the program be used. Allowed.

FIG. 9 shows the usage log recording unit 3 shown in FIG.
FIG. 5A is a diagram showing an example of a usage log recorded by 5a. Each row (entry) corresponds to one event of “use request” or “end notification”, and “date and time” at which the event occurred,
“Time”, “Status” indicating its type, “Program name” of the target, “User name” used by logging in to the client, “Host ID” identifying the client, and the target in the client "Process ID" that identifies the execution (process) of the program
Consists of

Note that "GET_SU" shown in "Status"
"CCESSED" indicates that the client has issued a "use request" and that it has been granted, and "RELEASE" indicates that the client has issued an "end notification". These information are stored in the usage log recording unit 35a by the client 31.
32 or directly from the use permission / non-permission determining unit 34a.

FIG. 10 shows the validity verifying unit 3 shown in FIG.
It is a flowchart which shows operation | movement of 5b. Each time an entry whose “status” is “RELEASE” is written in the usage log recorded by the usage log recording unit 35a, the validity verification unit 35b performs “GET” corresponding to the “RELEASE”.
By searching for the entry “_SUCCESSED”, one session consisting of a set of these two entries is specified (step S120). Specifically, “program name”, “user name”, “host ID”, and “process I”
D "is searched for two entries, and
Identify one session.

Then, in order to verify that no fraudulent activity has been performed on the specified session, the validity verification unit 35b determines that there is no temporal contradiction (step S121) and that the logical contradiction does not exist. It is confirmed that it does not exist (step S122). Specifically, the usage log recording unit 35a periodically presses a time stamp regardless of whether or not the program is used (for example, “2000/05/26
16: 00: 00: 00 TIMESTAMP 05/26/200 ”etc. shall be recorded in the usage log), and that the times of the events that compose the session do not contradict the flow of time based on those timestamps. Check "Process I
For events having the same "D", it is confirmed that the "program name", the "user name", and the "host name" are also the same.

As a result, if neither a time inconsistency nor a logical inconsistency is found, the session (the contents of the two entries) is transmitted to the totaling unit 35c and added to the usage record table (step S123). On the other hand, if any inconsistency is found, the validity verification unit 35b executes a predetermined abnormality process (step S124). Specifically, it records and accumulates that fact, displays it on the screen of the license server 33 together with a warning message, and reports it to the vendor system 20 via the communication network 25.

FIG. 11 is a diagram showing an example of the usage record stored in the usage record storage 35d shown in FIG.
The usage record is a collection of records recorded by the counting unit 35c for each session. Each record indicates the usage record of each session whose validity has been verified, a “session number” which is a serial number for identifying the session, a “start date and time when the program was started”, and “ End date and time "and other items which are the same as those of the usage log shown in FIG.

FIG. 12 is a flowchart showing the operation of the clients 31 to 32. When the target program is started, the client 31 first makes a “use request” to the license server 33 via the LAN 39 in accordance with a license acquisition routine incorporated at the top of the target program.
Is issued (step S130). In response to the request, when the license server 33 receives a “license” reply from the license server 33, the client 31 exits the license acquisition routine and executes the main part of the target program, that is, the main processing routine for performing the specific application processing. (Step S132).

Then, when a command to end the program is input from an operator or the like (step S13).
3), exits from the main processing routine and issues an "end notification" to the license server 33 according to a license end routine incorporated in the last part of the program (step S134). This completes the use of the program in one session.

On the other hand, if a “use refusal” is received in response to the “use request” to the license server 33,
After outputting an error message to that effect on the screen of the client 31 (step S135), the execution of this program is terminated. FIG. 13 is a functional block diagram showing a detailed configuration of the bill issuing device 22. Invoice creation unit 2
3 is a communication network 25 from the license server 33.
And a use result storage unit 23c for storing and holding the use result of each session reported every day via the license key for each license ID indicated by the license key transmitted together with the use result. The unit price table storage unit 23a storing the unit price table in which the time unit price and the license ID are associated with each other and the usage record stored in the usage record storage unit 23c are read, and the usage time for one month is totaled. And a calculation unit 23b that calculates a one-month billing total for each license by referring to the unit price table stored in the unit price table storage unit 23a, and notifies the billing unit 24 of the total with the license ID.

The bill sending unit 24 includes a destination table storing unit 24a storing a destination table in which a bill sending destination for each predetermined license is associated with a license ID, and a calculating unit 23b. Upon receiving the billing amount and the license ID, the transmitting unit transmits the invoice describing the billing amount by e-mail to the corresponding destination registered in the destination table stored in the destination table storage unit 24a. 24b.

FIG. 14 is a flowchart showing the operation of the bill issuing device 22 having the configuration shown in FIG. The license server 3 is used by the usage record storage unit 23c.
The usage record sent from 3 is for a certain period (one month)
When the data is accumulated (step S140), the calculation unit 23b
By referring to the “start date and time” and the “end date and time” in the usage results, the total usage time for one month is totaled (step S141).

The calculation unit 23b stores the unit price table storage unit 2
The corresponding "time unit price" registered in the unit price table stored in 3a is read out, and multiplied by the total time to calculate a billing amount (step S142), and notifies the transmitting unit 24b together with the license ID. Upon receiving the notification, the transmitting unit 24b reads out the “destination” corresponding to the destination table stored in the destination table storage unit 24a (step S143), and notifies the destination from the calculating unit 23b. The charged amount is transmitted by e-mail (step S144).

As described above, the cooperation play between the license server 33 and the bill issuing device 22 automatically creates a bill for use of the program for one month for each license, and sends the bill to the designated billing destination. Will be sent.
As described above, the pay-per-use program license system according to the present invention has been described based on the embodiment. However, it is needless to say that the present invention is not limited to this embodiment.

For example, the bill issuing apparatus 22 sends a bill for use of the program to the user by e-mail, but instead of (or in addition to) this bill, the card with which the user has contracted is used. It may be sent to a credit company or the like, and the billed amount may be deducted from the user's bank account. Also, the license server 33
The use results of the programs by the clients 31 to 32 are accumulated, and the use results of the previous day are reported to the vendor system 20 only once a day. Alternatively, a report may be sent to the vendor system 20 for each entry in the usage log. As a result, the use results in the vendor system 20 can be grasped more finely.

The license server 33 transmits the license key together with the usage record to the invoicing device 22. The license server 33 encrypts the transmission record data using a MAC address, a secret key, or the like, and then transmits the encrypted data. Is also good. As a result, the confidentiality in transmission on the communication network 25 is increased, and the falsification of the usage record by an unauthorized third party is prevented, and the invoicing device 22 that has received the report makes the genuine user-side system 30 It is possible to confirm that the message is transmitted from.

As a license item, a domain name on the Internet may be added. For example, the nodes (clients) permitted to execute the program may be limited to computers belonging to a certain domain. Conversely, the “license start date” may be deleted from the license item. This is because, for example, the issuance of a license key (distribution from the vendor side system to the user side system) can replace the start of the license.

Also, as the usage log, a status “GET___________” indicating a case where the usage request from the client has been rejected.
FAILED ”may be added. This can be useful for finding unauthorized access and counting the frequency at which use requests are rejected. In addition, the pay-as-you-go program licensing system 10 issues a license key, tallies usage records, and issues a bill for each license (license ID), but identifies the user of each license. A user identifier may be provided, and issuing and billing may be performed for each user identifier.

In the present embodiment, the license server 33 restricts the use of the program by limiting the maximum number of programs that can be used simultaneously (upper limit number of users). However, the present invention is not limited to this. For example, the client that can execute the program, the usage time, and the like may be limited. Further, the pay-as-you-go program license system of the present invention is not limited to specific programs and physical conditions (hardware environment) of processes for realizing the functions. For example, the license server and the client configuring the user side system may be the same machine,
The license server of the user side system may be separately located in the vendor side system.

In the present embodiment, the target programs are installed in the clients 31 to 32 in advance, but these programs are collectively installed on a disk or the like of an external device on a network such as the vendor system 20 or the license server 33. So, client 3
1 to 32 may take the form of executing the target program by mounting the disk.

[0052]

As is apparent from the above description, the pay-as-you-go program licensing system according to the present invention includes a vender-side system which is a computer system that permits use of a program subject to pay-as-you-go billing, A pay-per-use program license system comprising a vendor system and a user system which is a computer system using the program and connected to the user system via a communication network, wherein the user system has a license A client that is a computer that executes the obtained program, and a use record management unit that records the use record of the program by the client and reports the record to the vendor system. The vendor record system includes the use record management unit. Based on usage reports from
And a billing data generating means for generating billing data for billing a billing amount for the usage record.

As a result, the use record of the program is recorded in the user side system and the billing data based on the use record is generated in the vendor side system.
Automated and done quickly without errors. Here, the vendor-side system further generates a license key that is data indicating the contents of a license agreement that has been previously exchanged,
A license key issuing unit for transmitting to the user side system, wherein the user side system further uses the program within a range of a license agreement indicated by the license key transmitted from the license key issuing unit. A license management unit that manages the program so that the client requests a license from the license management unit when starting use of the program, and informs the user when the use of the program ends. Notifying the license management means, the use result management means records data indicating the communication history between the client and the license management means as a use log, and determines and records the use result of the program based on the use log. May be.

As a result, the usage record is determined based on the exchange between the client and the license management means for managing the program so that it is used within the range of the contract. At the same time, it becomes possible to finely aggregate usage results reflecting actual usage conditions. Further, the use record management means confirms that there is no time inconsistency and logical inconsistency in the communication history indicated by the use log, thereby verifying that the program has not been used improperly. It may have a part.

As a result, a false use record is recorded due to unauthorized use of the program, and it is possible to prevent a problem that the vendor is damaged. Further, the user-side system further includes a use restriction acquisition unit that acquires an instruction to restrict the use of the program from an administrator, wherein the license management unit is within the scope of the license agreement, and The client may be managed so as to use the program within a range of an instruction acquired from the administrator.

For example, the use restriction obtaining means obtains, from the administrator, the maximum number of clients that can use the program at the same time, and the license management means obtains the maximum number of clients within the range of the license agreement. The client may use the program so that the number of clients that use the program at the same time does not exceed the upper limit.

As a result, not only is it ensured that the program is used within the range of the license agreement, but also that the program is used within the range of use restrictions voluntarily set by the user. Therefore, it is possible to avoid the occurrence of an unexpected situation in which a large amount of bill exceeding the budget is received due to a use result greatly exceeding expected. As described above, according to the present invention, not only the license management of the pay-as-you-go program but also the charging process thereof is automated, and the practical significance in today's information technology society is extremely large.

[Brief description of the drawings]

FIG. 1 is a block diagram showing the overall configuration of a pay-per-use program license system according to the present invention.

FIG. 2 is a diagram showing the contents of a license DB.

FIG. 3 is a sequence diagram showing an overall communication flow in the pay-per-use program license system.

FIG. 4 is a flowchart showing the operation of the license key issuing device.

FIG. 5 is a diagram illustrating an example of a license key.

FIG. 6 is a functional block diagram for explaining a detailed function of each of a license management unit and a usage record management unit of the license server.

FIG. 7 is an example of a screen displayed by an upper limit user number setting unit of the license server.

FIG. 8 is a flowchart showing an operation of a license approval / disapproval determination unit of the license server.

FIG. 9 is a diagram illustrating an example of a usage log recorded by a usage log recording unit of the license server.

FIG. 10 is a flowchart illustrating an operation of a validity verification unit of the license server.

FIG. 11 is a diagram showing an example of a usage record table stored in a usage record table storage unit of the license server.

FIG. 12 is a flowchart showing the operation of the client.

FIG. 13 is a functional block diagram showing a detailed configuration of a bill issuing device of the vendor system.

FIG. 14 is a flowchart showing the operation of the bill issuing device.

[Explanation of symbols]

 Reference Signs List 10 Usage-based program licensing system 20 Vendor-side system 21 License key issuing device 21a License DB 21b License key generation / transmission unit 22 Bill issuing device 23 Bill creation unit 23a Unit price table storage unit 23b Calculation unit 23c Usage record storage unit 24 Bill sending unit 24a Transmission destination table storage unit 24b Transmission unit 25 Communication network 29 LAN 30, 40 User system 31 Client 31, 32 Client 33 License server 34 License management unit 34a Usage permission / refusal determination unit 34b License key holding unit 34c Upper limit user Number storage unit 34d Maximum number of users setting unit 35 Usage record management unit 35a Usage log recording unit 35b Validity verification unit 35c Aggregation unit 35d Usage record table storage unit 35e Report unit 39 LAN

──────────────────────────────────────────────────続 き Continued on the front page (51) Int.Cl. ⁷ Identification symbol FI Theme coat ゛ (Reference) G06F 17/60 330 G06F 17/60 332 332 9/06 660A

Claims (8)

[Claims] 1. A vendor system, which is a computer system permitting use of a program subject to pay-as-you-go billing, and a computer using the program, which is connected to the vendor system via a communication network. A usage-based program licensing system comprising a user-side system that is a system, wherein the user-side system includes a client that is a computer that executes a licensed program, and a record of use of the program by the client. And a use result management means for recording and reporting to the vendor-side system, wherein the vendor-side system is for charging a billing amount for the use result based on the use result reported from the use result management means. Providing billing data generating means for generating billing data Pay-as-you-go program license system which is characterized. 2. The system according to claim 1, further comprising: a license key issuing unit configured to generate a license key, which is data indicating the contents of a license agreement previously exchanged, and transmit the generated license key to the user system. The system further includes a license management unit that manages the client to use the program within a license agreement indicated by the license key transmitted from the license key issuing unit. When the use of the program is started, the license management unit is requested to use the license, and when the use of the program is finished, the effect is notified to the license management unit. Use log indicating data indicating the communication history with the license management means 2. A pay-as-you-use program licensing system according to claim 1, wherein the usage record of the program is determined and recorded based on the usage log. 3. The use record management unit verifies that the program is not used improperly by confirming that there is no time inconsistency and logical inconsistency in the communication history indicated by the use log. 3. The system according to claim 2, further comprising a validity verification unit. 4. The user-side system further includes a use restriction acquisition unit that acquires an instruction to restrict the use of the program from an administrator, wherein the license management unit is configured to execute the license control within a range of the license agreement. 3. The system according to claim 2, wherein the client manages the program so that the client uses the program within a range of an instruction acquired from the manager. 5. The use restriction obtaining unit obtains, from the administrator, an upper limit number of clients that can use the program at the same time, and the license management unit obtains the maximum number of clients within a range of the license agreement. 5. The pay-per-use program license system according to claim 4, wherein management is performed such that the clients use the program within a range in which the number of clients simultaneously using the program does not exceed the upper limit number. 6. A vendor system which is a computer system which permits use of a program which is subject to pay-as-you-go billing, and a computer which uses the program and which is connected to the vendor system via a communication network. A method of licensing a pay-as-you-go program in a communication system including a user-side system, wherein the client-side computer is a computer that executes the licensed program in the user-side system. And a use result management step of recording the use result and reporting the use result to the vendor side system, wherein the vendor side system generates billing data for charging a charge amount for the use result based on the reported use result. And a data generation step. License method of pay-as-you-go program to be. 7. The method according to claim 1, further comprising the step of: generating a license key, which is data indicating the contents of a license agreement previously exchanged, in the vendor-side system and transmitting the license key to the user-side system. In the user system, a use restriction obtaining step of obtaining an instruction to restrict the use of the program from an administrator; and in the user system, a license agreement indicated by the transmitted license key is transmitted. A license management step of managing the client to use the program within a range and within an instruction obtained from the administrator. Method. 8. A vendor system, which is a computer system that permits use of a program subject to pay-as-you-go billing, and a computer that uses the program and is connected to the vendor system via a communication network. A computer-readable recording medium on which is recorded a program used in a pay-as-you-use program licensing system comprising a user side system as a system, wherein the program includes the steps of claim 6. Recording medium.