JP2001236219A - Agent for carrying out license managing function, license managing system using the agent and semiconductor device for realizing the function - Google Patents

Abstract

PROBLEM TO BE SOLVED: To provide a license managing system for effectively preventing the illegal use of a software license and reducing the workload of a user or a manager and a semiconductor device for realizing the license managing system. SOLUTION: A client 10 for executing prescribed software and a license managing server 30 for managing license to software are connected to a network 100, and an agent 50 for carrying out a license request and the transfer of the answer is also connected to the network 100. At the time of receiving the license request from the client 10 to the software to be executed by the client 10, the agent 50 selects one license managing server 30 for managing the license to the software, and transmits the license request to the selected license managing server 30, and receives an answer to the license request from the license managing server 30, and transfers the answer to the client 10.

Description

DETAILED DESCRIPTION OF THE INVENTION

[0001]

The present invention relates to a software license management system used on a computer connected to a network and a semiconductor device for realizing the management system.

[0002]

2. Description of the Related Art Conventionally, license management is performed for most software used on computers connected to a network such as a LAN in order to prevent unauthorized use.

FIG. 10 shows a conventional license management system. In FIG. 10, license management servers 30a ', 30b', 30c 'manage software licenses. License management server A
(Server A) 30a 'is the license of application A, license management server B (server B) 30b' is the license of application A and application B, and license management server C (server C) 30c 'is the license of application C. Is managing. As described above, the license management server includes one or a plurality of computers.

When executing an application, the clients 10a and 10b first make a license request to a license management server determined based on the application to be executed. Here, the license request is to request the license management server to permit the use of the application, and the license management server grants a license to the client when permitting the use of the application. The client can execute the application only when receiving the license from the server. Thereafter, when the client ends the execution of the application, the client notifies the server of the end of the execution. That is, the license is returned. Returning this license is called "license release".

[0005] For example, when the client 10a executes the application A, a predetermined server A
A license request is made to 30a '. Server B3
0b 'determines whether or not the client 10a is permitted to use the application A, in consideration of the maximum number of applications A that can be used as determined by the contract. As a result, when permitting use of the application A, the server A 30a ′ grants a license to the client 10a. The client 10a can execute the application A only when receiving the license from the server B 30a '. After that, when the client 10a finishes the execution of the application A, the server A30
Release the license for a '.

When the client 10b executes the application A, it issues a license request to the server B 30b '. In this case, the client 10b
Is set in advance to make a license request to the application A to the server B 30b '.

[0007]

In the conventional license management system, since the license management server individually manages the license, the license that has been properly obtained can be managed by a plurality of servers. Therefore, more software than the number of licenses can be used illegally. For example, the license acquired for the application A is transmitted to the server A 30a 'and the server B 30b'.
, The number of licenses received is 2
Double the number of software can be used illegally.

When using separate software for performing the same type of license management, since a software license management server exists on the network, a software user (user) can use the software at the client. It is necessary to set a license management server for managing licenses of software to be used for each software. In addition, it is necessary for each license management server to make a condition for obtaining a license. These settings become complicated as the network scale increases due to an increase in the number of clients and license management servers, and the load on the system administrator increases.

SUMMARY OF THE INVENTION The present invention has been made to solve the above problems, and an object of the present invention is to effectively prevent unauthorized use of a software license and reduce a work load on a user or an administrator. An object of the present invention is to provide a license management system and a semiconductor device realizing the management system.

[0010]

A license management agent according to the present invention is connected to a network in which at least one client that executes predetermined software and at least one license management server that manages a license for the software are connected. Is done. The license management agent receives, from a client, a license request that is a request for permission to use the software for the software executed by the client, and manages a license for the software when the license request is received. Selection means for selecting one license management server, transmission means for transmitting a license request to the selected license management server, and transfer for receiving a response to the license request from the license management server about use permission in response to the license request and transferring the reply to the client Means.

The license management agent collects at least one of a software name, a license management server identification number, a license identification number assigned to each license agreement, and a license generation number indicating whether the license is new or old. And means for creating server information that is information about the license management server. At this time, the selecting means selects one license management server in response to the license request with reference to the server information.

In the case where the license management server manages a license identification number assigned to each license contract managed by the license management server and a license generation number indicating whether the license is new or old, the selection means may be the same software. When the same license identification number is managed by a plurality of license management servers, a license management server that manages the latest license generation number may be selected in response to a license request.

[0013] The selection means may be capable of setting selection conditions for selecting one license management server.

Preferably, the selection conditions include at least one of an IP address of the client, a host name, a user name of a user who uses the client, and a use time zone.
One is included.

[0015] The license management system according to the present invention comprises:
(A) At least one license management server that manages a license for predetermined software and an agent. At this time, the agent includes a receiving unit that receives a license request from the client using the predetermined software, the request for permission to use the software executed by the client, and a license for the software when the license request is received. Selecting means for selecting one license management server to be managed, transmitting means for transmitting a license request for software to the selected license management server, receiving a response from the license management server to the transmitted license request, and transferring the reply to the client Transfer means.

Preferably, the license management server does not respond to a license request from a client, but transmits a response only to a license request from an agent.

A semiconductor device according to the present invention comprises at least one client executing predetermined software and at least one client managing a license for the software.
This is a semiconductor device used for an agent that performs license management in a network to which two license management servers are connected. The semiconductor device manages, from a client, a reception function for receiving a license request for requesting use of the software executed by the client, and manages a license for the software when the license request is received. The license management server includes a selection function of selecting one license management server, a transmission function of transmitting a license request to the selected license management server, and a transfer function of receiving a response to the license request from the license management server and transferring the reply to the client.

The semiconductor device further includes a software name,
Collecting at least one of an identification number of the license management server, a license identification number assigned to each license agreement, and a license generation number indicating a new or old license grant;
It may have a function of creating server information that is information on the license management server. In this case, the selection function
One license management server is selected in response to a license request by referring to the server information.

In the case where the license management server manages the license identification number assigned to each license contract managed by the license management server and the license generation number indicating the new or old license, the selection function preferably has the same software. When the same license identification number is managed by a plurality of license management servers, a license management server that manages the latest license generation number is selected in response to a license request.

Further, the selection means may be capable of setting selection conditions for selecting one license management server.

Preferably, the selection condition includes at least one of an IP address, a host name, a user name of a user who uses the client, and a use time zone.
One is included.

Another semiconductor device according to the present invention is a semiconductor device used for a license management server for receiving a license request from an agent realized by the above-described semiconductor device. It has a function of transmitting the above response only to the license request from the agent without responding.

[0023]

DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS Hereinafter, an embodiment of a license management system according to the present invention will be described in detail with reference to the accompanying drawings.

Embodiment 1 (Configuration of Entire License Management System) FIG. 1 is a configuration diagram of a license management system according to the present invention. The license management system includes a client (client A, client B) 10, a license management server (server A, server B, server C) 30, and an agent 50, which are connected to a local area network (LA).
N) 100.

The client 10 is generally an information processing terminal on which a user executes a predetermined application such as a document creation program. A license management server (hereinafter abbreviated as “server”) 30 manages licenses of various applications executed on the client 10.

The agent 50 receives a license request /
A function of acting as an exchange between the client 10 and the server 30 for license release and the like is realized. That is, the agent 50 includes the client 10 and the server 3
0 relays license requests / license releases and the passing of replies to them. Agent 50
Is the server database D to realize such a function.
1, the selection policy D2 and the server list D3 are referred to.
Details of these pieces of information D1 to D3 will be described later.

(Operation of the Entire License Management System) In the license management system configured as described above, for example, the procedure for executing the application A on the client A is as follows. The client A sends a license request for the application A to the agent 50 in order to obtain a permission to use the application A.
(A1). Upon receiving the license request, the agent 50 selects a server A for the license request of the application A of the client A according to a predetermined selection rule (hereinafter, referred to as “selection policy”), and transmits the license request to the server A. Yes (A
2). Upon receiving the license request, the server A determines whether or not the use permission of the application A is permitted, and returns a result of the permission / non-permission to the agent 50 (A3).
The agent 50 transfers the reply to the client A who has requested the license (A4). Client A sends application A from server A via agent 50
When the use permission is received, that is, when the license is granted, the application A can be executed.

As described above, the license management system according to the present embodiment
By exchanging the license request and the response between the server and the server 30, unauthorized use of the license is prevented. In this case, since the client 10 and the server 30 do not need to directly communicate with each other,
Even if the number of software used increases, it is only necessary to perform the necessary setting change processing in the agent 50, the setting change processing on the client 10 and the server 30 side can be minimized, and license management becomes easy. realizable.

Next, the detailed configuration and control of the agent 50 and the license management server 30 for realizing the above functions will be described.

(Configuration of Agent) FIG. 2 is a functional block diagram of the agent 50. In the agent 50, the communication receiving unit 51 receives a request from the client 10, and determines the type of the received request. The received request includes a license request and a license release.
When the request from the client 10 is a license request, the server selecting unit 53 refers to the server database D1 and the selection policy D2 to select one server 30 for which a license is requested. The license release unit 55 notifies the server 30 of the license release when the request from the client 10 is the license release. The license request transmission unit 57 transmits a license request to the selected one server 30. The response receiving unit 59 receives a response to the license request from the server 30, and
1 forwards the answer to the client. Server DB
The creating unit 63 creates a server database D1 with reference to the server list D3.

Next, the information D referred to by the agent 50
1 to D3 will be described. Server database D1
Stores information that specifies which server 30 manages which application. FIG. 3A shows an example of information included in the server database D1. Application name, license I
D, the license generation number, the license server name, the request availability status, and the number of licenses. The name of the server that manages the license of the application program specified by the application name is recorded in the license server name. The request availability status is a status indicating whether the server 30 has a valid license for the application or not.
"K" indicates a valid license, and "NG" indicates an invalid license. That is, the request availability status indicates whether or not a license request for the application is available to the server 30. The number of licenses indicates the number licensed for the application, that is, the number of clients that can simultaneously use the application.

The selection policy D2 manages a license acquisition (grant) condition, that is, a selection policy that defines conditions for selecting a server for which a license request is made. FIG. 3B shows an example of information included in the selection policy D2. In this figure, the selection policy on the first line defines that server B is selected when a license request for application B (indicated by “AppB” in the figure) from client A, The selection policy in the second line defines that the server C is selected when the license request of the application B from the client B is between 9:00 and 12:00. The selection policy may be determined by referring to the IP address or user name of the client 10 in addition to the host name of the client 10, the name of the application to be executed, and the usage time.

The server list D3 manages information about servers existing on the network, for example, server host names and the like. FIG. 3C shows an example of information included in the server list D3. As shown in the figure, the server list D3 stores the server names (here, server A, server B, server C) of all available servers on the network. The server name may be information unique to the server that can specify the server (the same applies to the host name, client name, software name, and the like described in the present embodiment).

(Control of Agent) FIG. 4 is a flowchart showing the control of the agent 50. Immediately after startup, the agent 50 obtains server information from the server list D3, inquires of the server that has obtained the information about the managed software name and the license generation number, and creates a server database D1 (S11). Here, when the same license ID exists for a plurality of servers for the same software, the server managing the latest license generation number is changed to a valid server (“O
K)) in the server database D1. On the other hand, a server that manages licenses of other old license generation numbers is out of selection, that is, not valid (“N
G)).

Thereafter, the process waits for a request from the client 10 (S12). When a request is received from the client 10, the type of the received request is determined (S13),
If the type of request is a license release notification (S14),
The server 30 is notified that the license has been used, and the process returns to step S12. If the type of request is a license request (S14), one server to request a license is referred to based on the requested software license name, requesting client name, and user name with reference to the selection policy information D2. Server database D1
(S15). Details of this selection processing will be described later. If there is an available server as a result of the selection (S16), a license request is made to the selected server (S17). Then, server 3
0 is received (S18), and the response is transferred to the client 10 (S19). On the other hand, when there is no available server 30 (S16), the process returns to step S12,
It waits for the next request from the client 10.

FIG. 5 is a flowchart showing details of the server selection process (step S15). When the agent 50 selects the server 10, predetermined information such as a requested software name, a requesting client name, and a user name of a user who executes an application is acquired from the client 30 (S151). Next, a selection policy is read from the selection policy D2 (S152), and a selection policy matching the previously acquired predetermined information is searched (S153).

If there is no matching policy (S15
4), the server database D1 of the agent 50
, And selects one server from the servers that manage the license of the corresponding application and whose request availability status is “OK” (S157).
If there is a matching selection policy (S154), one server 30 is selected according to the selection policy, and the validity of the server 30 is confirmed (S155). For example, FIG.
In the case of the selection policy shown in (b), if the software requested by the client A is “application B”, the first selection policy matches, and the server B is selected as one server that makes a license request. According to the server database shown in FIG. 3A, the request availability status of the server B with respect to the application B is “OK”.
Therefore, the validity of the server B is confirmed.

If there is a corresponding server in step S157, or if it is possible to request a license for the selected server as a result of checking the validity in step S155, the selected server is licensed. The server is determined to be the requesting server, otherwise, it is determined that there is no corresponding server (S156).

In this way, the agent 50 can determine one selected server that makes a license request.

(Structure of License Management Server) The license management server 30 of this embodiment does not respond to a direct license request from the client 10,
It responds only to the request from the agent 50. The server 30 holds a license ID and a license generation number unique to each software in a license file described later. Each server 30 has a license file containing information on the applications it manages. FIG.
Here is a specific example of a license file for.

FIG. 6A shows a license file stored in the server A 30a, FIG. 6B shows a license file stored in the server B 30b, and FIG.
30c shows license files stored respectively.
As shown in FIG. 6A, the license file includes information on an application name, an encryption part, a use period, the number of licenses, a license ID, and a license generation number. The application name is information on the name of the application that has been officially licensed. The encrypted part is information obtained by encrypting information indicating the validity of use of an application by a public key method or the like. The term of use indicates the term of validity of the license. The number of licenses is the number of licensed users, that is, the number of clients 10 that can be used at one time. The license ID is an identification number assigned for each software license agreement. The license generation number is a generation number that is updated each time a license is issued based on a license agreement, and is information for indicating a license file that is valid at that time.

FIG. 7 is a functional block diagram of the license management server 30. The license file reading unit 31 reads the license file D11, determines the validity of the license file D11, and manages the license status D that manages the information indicating the license grant status.
12 is managed. The license status D12 includes, for example, information indicating a license grant status such as the number of terminals for which a license is permitted or the number of remaining license grantable terminals. The reception processing unit 33 receives the request from the agent 50 and determines the content. The license control unit 35 performs a predetermined process such as granting a license according to the content of the request from the agent 50. Transmission processing unit 37
Responds to the agent 50 with the result obtained by the predetermined processing.

(Control of License Management Server) FIG.
5 is a flowchart illustrating control of a license management server 30. When the server 30 starts up, the license file D1
The license file D1 is read (S31).
1 is checked for validity (S32). If the license file D11 is invalid (S33), the process is stopped. If the license file D11 is valid (S3
3), the license status D12 is initialized (S34), and a state of waiting for reception (S35). In addition,
The validity of the license file D11 is determined by the encrypted part of the data included in the license file.
When there is a communication request from the client 10 (S35),
The communication partner is determined (S36), and if the communication partner is other than the agent 50 (S37), the communication is not established and the reception standby state is set again. On the other hand, when the communication partner is the agent 50 (S37), the communication is established and the content of the communication request is determined (S38). If the request content is the license use information confirmation (S39), the license status D12 is set. The license usage status is confirmed with reference to the license (S40). If the request is for management information confirmation (S
39), and confirm the management information (S42). afterwards,
The confirmation result is transmitted to the requesting agent 50 (S4
1). For example, as a result of checking the usage status, if the client 10 can be used, a permission is transmitted.
If the use of 0 is not possible, a non-permission is sent. Although not shown in the figure, when the agent 50 notifies the license release from the agent 50, the server 30 updates the license status D12 based on the result of the license release.

As described above, the agent 5
0, the license request is exchanged between the client 10 and the license management server 30. Therefore, even when a large number of application programs are used or a large number of clients and the license management server are present, the license management server 30 can perform license management. Complex operations can be reduced, and license management can be simplified. Further, based on the license file managed by the license management server 30, the validity of the license file is determined to create a server database, and referring to the server database to determine a server that issues a license request. It can be reliably prevented.

Embodiment 2 Hereinafter, a semiconductor device that realizes the license management system described in Embodiment 1 will be described.

The agent 50 is actually the one shown in FIG.
The information processing device has a hardware configuration as shown in FIG. As shown in this figure, the agent 50 has a CPU (Central Processing Unit) 500 that executes a program, and the CPU 500 stores a program and data via a bus 501 by a RAM (random access memory) 503 or a ROM ( A read-only memory) 505; a display unit 513 for displaying information;
1. It is configured to be connected to a network interface unit 515 for connecting to a network and an external interface unit 517 for connecting to an external information device. The agent 50 includes a hard disk device 507 as an auxiliary storage device and a CD-RO as an information recording medium.
A CD drive 509, which is a device for reading programs and data from M, is provided.

CPU for controlling the function of agent 50
The RAM 503 and the ROM 505 for storing programs and data executed by the CPU 500 and the CPU 500 are semiconductor devices as shown in FIG. 9B, in which a large number of circuits and elements are integrated on a semiconductor substrate. It is.

Each function of the agent 50 shown in the first embodiment is implemented by the CPU
3 and a program stored in the ROM 505 are executed. In this case, the semiconductor device R
In the AM 503 or the ROM 505, a program for realizing each functional unit as shown in FIG. 2 and performing the control shown in FIGS. 4 and 5 is stored. Further, the CPU 500, RA
The M503 and the ROM 505 may be integrated and realized as one semiconductor device (so-called “system LSI”). In this case, the semiconductor device realizes each functional unit as shown in FIG. , Is designed to perform the control as shown in FIG. The server DB (D1),
Each information of the selection policy D2 and the server list D3 is RA
M503, memory such as ROM505 and hard disk 5
07.

Like the agent 50, the server 30 is also realized by an information processing device having a hardware configuration as shown in FIG. Also in this case, the CPU and memories (RAM, ROM) configuring the server 30 are:
Each functional unit as shown in FIG. 7 is realized, and a program for performing control as shown in FIG. 8 is stored, or realized by a semiconductor device programmed to perform such control.

[0050]

According to the license management agent of the present invention, a license request and a response to the license request are exchanged between the client and the license management server on behalf of the client and the license management server. Since various settings may be changed by the agent in accordance with a change, a license change, and the like, complicated operations for these settings can be reduced, and license management can be facilitated.

The license management agent receives information on the license management server based on the software name, the identification number of the license management server, the license identification number assigned to each license agreement, and the license generation number indicating the new or old license. May be created, and a server for which a license request is made may be selected based on the server information. This makes it possible to reliably prevent unauthorized use of the license.

Further, even when software having the same license identification number is managed by a plurality of servers, the license management agent selects a license management server that manages the latest license generation number as a server that issues a license request. By doing so, unauthorized use of the license can be reliably prevented.

The license management agent can set selection conditions for selecting one license management server. As a result, a license management server that is preferentially selected for each client and each user can be designated, and flexible license management operation becomes possible. Specifically, it is possible to specify a license management server that is preferentially selected based on the client's IP address, host name, user name of a user who uses the client, use time zone, and the like.

According to the license management system of the present invention, between the client and the license management server,
Since the exchange of the license request and the response to the request are performed through the agent, various setting changes accompanying the addition of the application program, the addition and the change of the license management server, the change of the license, etc. may be performed only in the agent. The complicated work of changing these settings can be reduced, and license management can be simplified. At this time, the license management server may respond only to the license request from the agent, thereby preventing useless processing other than the license request.

According to the semiconductor device of the present invention, it is possible to reduce cumbersome work in changing various settings accompanying addition of an application program, addition and change of a license management server, change of a license, and the like, and facilitate license management. It can provide a license management agent that can realize licensing.

Further, according to the semiconductor device of the present invention, it is possible to provide a license management agent capable of reliably preventing unauthorized use of a license.

Further, according to the semiconductor device of the present invention, it is possible to provide a license management agent which enables flexible license management operation.

According to another semiconductor device of the present invention,
A license management server that can prevent useless processing other than a license request can be realized.

[Brief description of the drawings]

FIG. 1 is a configuration diagram of a license management system according to the present invention.

FIG. 2 is a functional block diagram of an agent.

FIG. 3 is a diagram showing specific examples of information (a) stored in a server database, information (b) stored in a selection policy, and information (c) stored in a server list.

FIG. 4 is a flowchart showing control of an agent.

FIG. 5 is a flowchart showing a server selection process in controlling the agent.

FIG. 6 is a view showing specific examples of a license file (a) of a server A, a license file (b) of a server B, and a license file (c) of a server C.

FIG. 7 is a functional block diagram of a license management server.

FIG. 8 is a flowchart showing main control of the license management server.

9A is a diagram illustrating a hardware configuration of an agent, and FIG. 9B is an external view of a semiconductor device that realizes functions of an agent and a license management server.

FIG. 10 is a diagram illustrating a conventional license management system.

[Explanation of symbols]

10 clients, 30 license management server,
50 agents, 100 local area network, D1 server database, D2 selection policy, D3 server list.

Claims (13)

[Claims] 1. A software which is connected to a network in which at least one client executing predetermined software and at least one license management server which manages a license for the software are connected. Receiving means for receiving a license request that is a request for permission to use the software, and selecting means for selecting one license management server that manages a license for the software when the license request is received, Transmission means for transmitting the license request to the selected license management server; and transfer means for receiving a response to the license request from the license management server about the use permission in response to the license request and transferring the reply to the client. The license management agent, characterized in that was example. 2. The license is obtained by collecting at least one of a software name, an identification number of a license management server, a license identification number assigned to each license agreement, and a license generation number indicating a new or old license. The apparatus according to claim 1, further comprising: a unit that creates server information that is information on a management server, wherein the selection unit refers to the server information and selects the one license management server in response to the license request. The license management agent according to 1. 3. The license management server manages a license identification number assigned to each license contract managed by the license management server and a license generation number indicating whether the license is new or old. 2. The license management agent according to claim 1, wherein when the license identification number is managed by a plurality of license management servers, a license management server that manages the latest license generation number is selected in response to the license request. 4. The license management agent according to claim 1, wherein said selection means is capable of setting a selection condition when selecting one license management server. 5. The selection condition includes a client IP address.
The license management agent according to claim 4, wherein at least one of an address, a host name, a user name of a user using the client, and a use time zone is included. (A) at least one license management server that manages a license for predetermined software; and (b) a request from a client that uses the predetermined software for permission to use the software executed by the client. Receiving means for receiving a license request; selecting means for selecting one license management server for managing a license for the software when receiving the license request; and requesting the selected license management server for a license of the software. And a transfer means for receiving a response from the license management server to the transmitted license request and transferring the reply to the client. 7. The license management system according to claim 6, wherein the license management server does not respond to a license request from the client and transmits the answer only to a license request from the agent. . 8. A semiconductor device used for an agent that performs license management in a network in which at least one client that executes predetermined software and at least one license management server that manages a license for the software are connected. A receiving function for receiving, from the client, a license request to the software executed by the client, requesting permission to use the software; and a function for managing a license for the software when receiving the license request. Selecting a license management server, transmitting a license request to the selected license management server, receiving a response to the license request from the license management server, The semiconductor device is characterized in that a transfer function of transferring to the client. 9. Collecting at least one of a software name, an identification number of a license management server, a license identification number assigned to each license agreement, and a license generation number indicating whether a license is new or old. The server further includes a function of creating server information that is information on a management server, wherein the selection function refers to the server information and selects the one license management server in response to the license request. Item 9. The semiconductor device according to item 8. 10. When the license management server manages a license identification number assigned to each license contract managed by the license management server and a license generation number indicating a new or old license grant, the selection function is the same software. 9. The semiconductor device according to claim 8, wherein when the same license identification number is managed by a plurality of license management servers, a license management server that manages the latest license generation number is selected in response to the license request. apparatus. 11. The semiconductor device according to claim 8, wherein said selection means is capable of setting a selection condition for selecting one license management server. 12. The selection condition includes a client I
12. The semiconductor device according to claim 11, wherein at least one of a P address, a host name, a user name of a user using the client, and a use time zone is included. 13. Receiving a license request from an agent realized by the semiconductor device according to claim 8.
A semiconductor device used for a license management server, the semiconductor device having a function of not responding to a license request from the client but transmitting the answer only to a license request from the agent.