JP2000276350A - Computer terminal device and license management server - Google Patents

Abstract

(57) [Summary] In a software license management system on a network, a license management function of software to be used is realized not only for a network connection environment but also for an information terminal device in a mobile environment. It is in. A mobile client connected to a network receives license information issued from a license server and stores the license information in a memory. The mobile client 4 executes software whose use is permitted by the license information stored in the memory 40 even in a mobile environment separated from the network 1.

Description

DETAILED DESCRIPTION OF THE INVENTION

[0001]

The present invention relates to a computer terminal connected to a network, and more particularly to a software license management function.

[0002]

2. Description of the Related Art Conventionally, for example, a LAN (Local Ar
ea Network).
Software (for example, various application programs) whose license is managed by a client (for example, a personal computer) connected to the network
Is used, there is provided a license management system that involves a server having a license management function (hereinafter referred to as a license server).

In the license management system, a client starts by inquiring a license server for issuing a license for software to be used. The license server checks the issuance of a license for licensing the software in response to the inquiry. When the license is issued from the license server, the client executes the software licensed by the license.

[0004]

In a conventional license management system in a network environment, a license server is involved and manages issuance of a license to a client connected to a network.

In recent years, not only desktop personal computers but also clients have been used as clients.
2. Description of the Related Art A portable information terminal device (sometimes called an intelligent terminal) has been developed. In the case of such a mobile client (information terminal device in a mobile environment), a user often connects to a network and uses it separately from the network. Therefore, in a license management system premised on network connection, software license management for a mobile client used separately from the network does not function sufficiently.

Therefore, an object of the present invention is to provide a software license management system on a network,
An object of the present invention is to realize a license management function of software to be used not only in a network connection environment but also in an information terminal device in a mobile environment.

[0007]

SUMMARY OF THE INVENTION A first aspect of the present invention is as follows.
A computer terminal device connectable to a network, comprising: a license storage unit for receiving license information issued from a server in response to a license request and storing the license information in a predetermined storage unit; and a license stored in the license storage unit. Means for executing software permitted to be used based on the information.

Specifically, the computer terminal device of the present invention is applied to a mobile client, which is an information terminal device in a mobile environment, and stores license information issued from a license server on a network in an internal storage device. (For example, a hard disk device), so to speak, a caching function.

Therefore, in the apparatus of the present invention, since the license information obtained from the server by connecting to the network first is stored therein, the software licensed by the license information can be used even if the apparatus is disconnected from the network. It is possible to execute. In this case, for example, if the expiration date of the license is set, the server can manage the license even when the server is away from the network.

[0010] A second aspect of the present invention relates to a license management server for issuing a license for software requested by a client on a network. That is, the server includes a means for managing license information for giving permission to use the software installed on the client side, and a means for judging permission to use the corresponding software based on the use restriction of the license requested by the client. Means for issuing license information corresponding to the software whose use is permitted to the requesting client.

With such a license management server, by setting the amount of license information to be issued and the expiration date of the license, it is possible to reliably perform software license management for mobile clients disconnected from the network. Becomes

[0012]

Embodiments of the present invention will be described below with reference to the drawings.

(System Configuration) As shown in FIG. 1, in the system of the embodiment, a license server 2, a client 3, and a mobile client 4 are connected to a network 1 such as a LAN. Assume a connected network environment.

The license server 2 has clients 3,
Assuming a dedicated server that issues (rents) a license for licensing the software used by 4, multiple pieces of license information (20-1 to 20-N) are assigned to the same software (specified by the software name). A storage device (such as a hard disk drive) 20 for storing is provided. The license server 2 has a function of issuing license information so as to limit the total number of issued licenses, that is, restrict usable software. The license information is specifically in a format as shown in FIGS. 2 to 5 (the use method will be described later).

The client 3 is generally assumed to be a personal computer or the like that operates while connected to the network 1 and has a storage device (such as a hard disk drive) 31 for storing software such as application programs. Client 3
Has a memory 30 for storing (caching) license information issued from the license server 2 in a file format. This memory 30 has a nonvolatile EEP
It is an IC memory such as a ROM (including a flash EEPROM) or a storage area of the storage device 31.

The mobile client 4 is assumed to be a portable information terminal device (including a notebook personal computer) that can be connected to and disconnected from the network 1. The mobile client 4 has basically the same functions as the client 3 and has an application
It has a storage device (such as a hard disk drive) 41 for storing software such as programs, and a memory 40 for storing (caching) license information issued from the license server 2 in a file format. The memory 40 is an IC memory such as a nonvolatile EEPROM (including a flash EEPROM) or a storage area of the storage device 41.

(License Management Operation) Hereinafter, with reference to FIG.
The basic operation of license management according to the embodiment will be described with reference to the flowchart of FIG.

First, as shown in FIG.
It is assumed that the client 3 and the mobile client 4 are connected. In this state, since the operations of the clients 3 and 4 are basically the same, the operation between the mobile client 4 and the license server 2 will be described.

The mobile client 4 issues a license inquiry to the license server 2 via the network 1 in order to use the software already installed in its own storage device 41 (step S1). . The license server 2 is a client 4
In response to the inquiry from, it is checked whether there is a usable license (step S2). That is, usually, the total number of licenses (20-1 to 20-N) that can be issued (rented) to the same software is limited.

If there is no license available at this time (ie, if the license has been issued to another client up to the limited number), the license server 2 rents the license to the mobile client 4. Notify that it is not possible (NO in step S3,
S6).

On the other hand, if there is a usable license, the license server 2 executes a license issuance (rent) process (YES in step S3, S3).
4). Specifically, the license server 2 sends license information as shown in FIG. 2 to the requesting mobile client 4 via the network 1. mobile·
Upon receiving the license information from the license server 2, the client 4 stores (caches) the internal memory 40 in a file format (step S5).

As described above, according to the license management system of the embodiment, when the mobile client 4 receives the license information corresponding to the software to be used from the server 2 via the network 1, the mobile client 4 To cache. In the case of other clients 3 as well, when the license information corresponding to the software to be used is received from the server 2 via the network 1, the license information is cached in the internal memory 30.

Therefore, the mobile client 4 can execute the software licensed by the license information stored in the internal memory 40 as needed. Thus, even when the user operates the mobile client 4 while disconnecting it from the network 1,
It is possible to use software that has already been licensed according to the license information.

(License management operation on client side)
In the embodiment, when issuing license information requested from the mobile client 4, the license server 2 limits the number of issued licenses based on a preset total number of usable licenses. On the other hand, the mobile client 4 often operates while being disconnected from the network 1. Therefore, the license server 2 cannot manage the license for the mobile client 4 disconnected from the network 1. Therefore, the license server 2 issues license information in which the expiration date of the license is set in advance, so that the network 1
And implements a license management function for the mobile client 4 disconnected from the client.

As shown in FIG. 2, as license information, in addition to information such as “software name”, “client name”, and “user name”, information in which “expiration date” is set (indicating usage period). Add. As shown in FIG. 3, the “expiration date” information may be the usage time from the start of using the software. Further, as shown in FIG. 4, the use start time and the end time of the software may be set as the information of the “use period”. Further, as shown in FIG. 5, information (that corresponds to reservation information) in which the time until the license becomes valid may be added together with the information on the “expiration date”.

Hereinafter, the license management operation on the mobile client 4 side when the license information shown in FIG. 5 is adopted will be described with reference to the flowchart of FIG.

First, when the mobile client 4 receives the license information (the information shown in FIG. 5) corresponding to the software to be used from the server 2 via the network 1, it caches it in the internal memory 40 (step S10). ). In the mobile client 4, when the software is activated based on the license information, the expiration date of the license is determined (step S11). Here, "expiration date information" and "reservation information"
The expiration date determination process is executed based on the above. That is,
If both conditions are satisfied, the mobile client 4 can start the software based on the license information (YES in step S12, S13).

Here, when the software license becomes valid after a certain time due to the reservation information added to the license information shown in FIG. 5, the mobile client 4 waits until the specified time elapses. The software can be started later (NO in step S12, YES in S14, YES in S15). Naturally, if there is no “reservation information” in the license information and the validity period of the license has expired according to the “expiration date information”, the mobile client 4 cannot start the software (NO in step S14). In this case, the user connects the mobile client 4 to the network 1 and performs processing for re-executing the license inquiry to the license server 2.

As described above, by setting the expiration date of the license to be issued in advance, it is possible to prohibit the mobile client 4 disconnected from the network 1 from using the expired software. it can. In other words, the license server 2 can reliably manage the license even for the mobile client 4 disconnected from the network 1.

(Modification) FIG. 8 is a flowchart relating to a modification of the embodiment. As described above, this modified example relates to the function of the mobile client 4 for the situation where the expiration date is imminent when the expiration date of the license is set. Hereinafter, a specific description will be given with reference to the flowchart of FIG.

When the software is activated based on the license information, the mobile client 4 executes a process of determining the expiration date of the license (step S20). Here, on mobile client 4,
It is assumed that the information shown in FIG. 3 is cached as license information. That is, by the expiration date determination process, it is determined whether or not there is a remaining time equal to or more than a predetermined time until the expiration date of the license (step S2)
1). If there is a remaining time equal to or more than a predetermined time, the software is naturally activated and can be executed until the expiration date (YES in step S21, S22).

On the other hand, when the expiration date of the license is less than a predetermined time, a process of notifying a warning that the expiration date is imminent is executed (NO in step S21, S2).
23). Specifically, a process of displaying the warning on the display of the mobile client 4 is executed.
Even in this case, the software is activated and can be executed until the license expiration date. Here, if the license expires while the software is running,
The license is valid until the software is completed (YES in step S27, S28). After the software is terminated, the license becomes invalid and execution of the software is prohibited (step S29).

In this modification, it is assumed that a function of extending the license expiration date during execution of software is added as a function of the mobile client 4 (YES in step S24). That is, a process of displaying a message urging extension of the validity period of the license is executed during execution of the software. Then, the mobile client 4 generates emergency license information for extending the use of the original license (step S2).
5). This emergency license information includes the user name and host ID (client name) of the original license information,
It also includes restrictions on software usage for emergency use. As the use restriction of the software, for example, only a file saving process can be executed (step S26).

When the expiration date of the licensed license is imminent as described above, the function of notifying the user that the expiration date is imminent enables the user of the mobile client 4 to cope with the expiration date. Thus, for example, the user may connect the mobile client 4 to the network 1 and make a request to the license server 2 to extend the validity period of the license. Further, when the license expires during execution of the software, the license can be effectively extended until the software ends, thereby substantially extending the license. In this case, after the software is terminated,
Since the execution of the software is prohibited by invalidating the license, the server 2 can maintain the license management function.

Further, the function of generating an emergency license on the mobile client 4 side can extend the expiration date of the license as a result. In this case, since the emergency license includes the use restriction of the software, it is possible to restrict the use to the minimum necessary software such as only the file storage processing. The use restriction naturally includes a new expiration date, for example, until the execution of the software is completed. Therefore, the license management function of the license server 2 can be maintained by extending the validity period of the license and restricting the use of the software during the extended period.

(Other Modifications) When the expiration date of the license described above is imminent, the mobile client 4 may perform unauthorized use such as intentionally shifting the time. The present modification relates to a function for dealing with such unauthorized use.

First, the format of the license information to be issued is
In order not to be affected by the system time (the internal clock function of the client), the clock function is included. Also, the license information format includes a function for measuring the elapsed time since the license was issued. When the time of the system is shifted as the format of the license information, the license information is invalidated. Change the system time format to "GM
By setting the format to "T + 9", the license can be prevented from being affected even when the time zone is changed and the time is changed to the time of each country. "GM
T + 9 "means Greenwich Mean Time (Greenwich
Means Japan Standard Time, which is 9 hours ahead of the mean time.

[0038]

As described in detail above, according to the present invention, a license management function of software to be used is realized not only for a network connection environment but also for a client such as an information terminal device in a mobile environment. be able to. Specifically, first, a client in a mobile environment can use software under a license licensed on a network. Second, by incorporating a function related to the expiration date into the license, license management for the client in a mobile environment disconnected from the network can be reliably performed as a result.

[Brief description of the drawings]

FIG. 1 is a block diagram showing a configuration of a network system related to an embodiment of the present invention.

FIG. 2 is an exemplary conceptual view showing an example of license information related to the embodiment.

FIG. 3 is an exemplary conceptual view showing an example of license information related to the embodiment.

FIG. 4 is an exemplary conceptual view showing an example of license information related to the embodiment.

FIG. 5 is an exemplary conceptual view showing an example of license information related to the embodiment;

FIG. 6 is an exemplary flowchart for explaining a basic operation of license management related to the embodiment;

FIG. 7 is an exemplary flowchart for explaining a license management operation on the mobile client side related to the embodiment;

FIG. 8 is an exemplary flowchart for explaining a license management operation relating to a modification of the embodiment;

[Explanation of symbols]

DESCRIPTION OF SYMBOLS 1 ... Network 2 ... License server 3 ... Client 4 ... Mobile client 20, 30, 40 ... Storage device (hard disk drive) 31, 41 ... Memory

Claims (6)

[Claims] 1. A computer terminal device connectable to a network, comprising: a unit for requesting a license of software to be executed from a server on the network; and the server in response to a request from the request unit. A license storage unit for receiving the license information issued from the storage unit and storing the license information in a predetermined storage unit; and a unit for executing software permitted by the license information stored in the license storage unit. A computer terminal device characterized by the above-mentioned. 2. A method according to claim 1, further comprising: means for executing software permitted by use of the license information stored in said license storage means within a range limited by said license information when said network is not connected to said network. The computer terminal device according to claim 1. 3. A license management server for connecting to a network and issuing a license for software requested by a client on the network, wherein the license management server manages license information for giving permission to use the software installed on the client side. Means, based on a license use restriction requested by the client, means for determining permission to use the corresponding software, and license information corresponding to the software for which use is permitted,
Means for issuing to a requesting client. 4. A method for setting a license expiration date corresponding to a software expiration date, and after the expiration date, issuing the license information with a function of prohibiting use of the software. The license management server according to claim 3, wherein 5. A means for issuing the license information having a function of generating emergency license information with an extension of the validity period of the license when the remaining time until the validity period of the license is less than a predetermined time. The license management server according to claim 4, further comprising: 6. A means for issuing the license information added with a function of validating the license until the end of the software when the license expires during execution of the software whose use is permitted. The license management server according to claim 4, comprising: