CA1310425C - License management methods and systems - Google Patents
License management methods and systemsInfo
- Publication number
- CA1310425C CA1310425C CA000580262A CA580262A CA1310425C CA 1310425 C CA1310425 C CA 1310425C CA 000580262 A CA000580262 A CA 000580262A CA 580262 A CA580262 A CA 580262A CA 1310425 C CA1310425 C CA 1310425C
- Authority
- CA
- Canada
- Prior art keywords
- license
- computer program
- node
- licenses
- copy
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Expired - Lifetime
Links
- 238000007726 management method Methods 0.000 title claims 87
- 238000004590 computer program Methods 0.000 claims abstract description 303
- 238000000034 method Methods 0.000 claims abstract description 38
- 238000012546 transfer Methods 0.000 claims abstract description 26
- 230000004044 response Effects 0.000 claims description 43
- 230000006870 function Effects 0.000 claims description 20
- 238000013475 authorization Methods 0.000 claims description 5
- 238000005065 mining Methods 0.000 claims 1
- 238000009877 rendering Methods 0.000 claims 1
- 238000009434 installation Methods 0.000 description 4
- 238000013459 approach Methods 0.000 description 3
- 238000010586 diagram Methods 0.000 description 2
- 230000000694 effects Effects 0.000 description 2
- 150000002500 ions Chemical class 0.000 description 2
- 238000012986 modification Methods 0.000 description 2
- 230000004048 modification Effects 0.000 description 2
- 102100022704 Amyloid-beta precursor protein Human genes 0.000 description 1
- 240000001973 Ficus microcarpa Species 0.000 description 1
- 101000823051 Homo sapiens Amyloid-beta precursor protein Proteins 0.000 description 1
- DZHSAHHDTRWUTF-SIQRNXPUSA-N amyloid-beta polypeptide 42 Chemical compound C([C@@H](C(=O)N[C@@H](C)C(=O)N[C@@H](CCC(O)=O)C(=O)N[C@@H](CC(O)=O)C(=O)N[C@H](C(=O)NCC(=O)N[C@@H](CO)C(=O)N[C@@H](CC(N)=O)C(=O)N[C@@H](CCCCN)C(=O)NCC(=O)N[C@@H](C)C(=O)N[C@H](C(=O)N[C@@H]([C@@H](C)CC)C(=O)NCC(=O)N[C@@H](CC(C)C)C(=O)N[C@@H](CCSC)C(=O)N[C@@H](C(C)C)C(=O)NCC(=O)NCC(=O)N[C@@H](C(C)C)C(=O)N[C@@H](C(C)C)C(=O)N[C@@H]([C@@H](C)CC)C(=O)N[C@@H](C)C(O)=O)[C@@H](C)CC)C(C)C)NC(=O)[C@H](CC=1C=CC=CC=1)NC(=O)[C@@H](NC(=O)[C@H](CC(C)C)NC(=O)[C@H](CCCCN)NC(=O)[C@H](CCC(N)=O)NC(=O)[C@H](CC=1N=CNC=1)NC(=O)[C@H](CC=1N=CNC=1)NC(=O)[C@@H](NC(=O)[C@H](CCC(O)=O)NC(=O)[C@H](CC=1C=CC(O)=CC=1)NC(=O)CNC(=O)[C@H](CO)NC(=O)[C@H](CC(O)=O)NC(=O)[C@H](CC=1N=CNC=1)NC(=O)[C@H](CCCNC(N)=N)NC(=O)[C@H](CC=1C=CC=CC=1)NC(=O)[C@H](CCC(O)=O)NC(=O)[C@H](C)NC(=O)[C@@H](N)CC(O)=O)C(C)C)C(C)C)C1=CC=CC=C1 DZHSAHHDTRWUTF-SIQRNXPUSA-N 0.000 description 1
- 238000005516 engineering process Methods 0.000 description 1
- 101150014278 nodP gene Proteins 0.000 description 1
- 239000002674 ointment Substances 0.000 description 1
- 230000002093 peripheral effect Effects 0.000 description 1
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F12/00—Accessing, addressing or allocating within memory systems or architectures
- G06F12/14—Protection against unauthorised use of memory or access to memory
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F21/00—Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
- G06F21/10—Protecting distributed programs or content, e.g. vending or licensing of copyrighted material ; Digital rights management [DRM]
- G06F21/105—Arrangements for software license management or administration, e.g. for managing licenses at corporate level
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F21/00—Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
- G06F21/10—Protecting distributed programs or content, e.g. vending or licensing of copyrighted material ; Digital rights management [DRM]
- G06F21/12—Protecting executable software
- G06F21/121—Restricting unauthorised execution of programs
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F2211/00—Indexing scheme relating to details of data-processing equipment not covered by groups G06F3/00 - G06F13/00
- G06F2211/007—Encryption, En-/decode, En-/decipher, En-/decypher, Scramble, (De-)compress
Abstract
ABSTRACT OF THE DISCLOSURE
License management systems and methods allow licenses for a computer program to be available for use at each of a plurality of nodes of a network. If a valid license file at a local node contains an unexpired, available license, a license manager at the local node permits the computer program to be executed at the requesting local node. If no such license is available in a valid license file at such local node, the license manager searches the other nodes for a valid license file containing an unexpired, available license. In one embodiment, if an unexpired available license is located in a valid license file at a second for "remote") node, the license manager transfers such license to the local node, and assigns and encrypts a unique identification to such transferred license. The original record of the transferred license is modified by erasing it from the license file at the remote node so that the transferred license is no longer available there.
In a second embodiment, the license manager modifies the license file to indicate use of the license at the local node without such transfer. The number of copies of the computer program that are authorized for execution simultaneously on the network is thus limited to the number of licenses that have been loaded into the license files on the network.
License management systems and methods allow licenses for a computer program to be available for use at each of a plurality of nodes of a network. If a valid license file at a local node contains an unexpired, available license, a license manager at the local node permits the computer program to be executed at the requesting local node. If no such license is available in a valid license file at such local node, the license manager searches the other nodes for a valid license file containing an unexpired, available license. In one embodiment, if an unexpired available license is located in a valid license file at a second for "remote") node, the license manager transfers such license to the local node, and assigns and encrypts a unique identification to such transferred license. The original record of the transferred license is modified by erasing it from the license file at the remote node so that the transferred license is no longer available there.
In a second embodiment, the license manager modifies the license file to indicate use of the license at the local node without such transfer. The number of copies of the computer program that are authorized for execution simultaneously on the network is thus limited to the number of licenses that have been loaded into the license files on the network.
Description
~3~2~
LIC~NS~ MAN~GEMENT M~THODS AND SYSTEMS
Speciication BAC~GROV~D OF TE~ INVENTI9 Field of the I~ve~tion The present invention relates to the field of controlling the use of computPr programs and more particularly to the field of managing the availability of licenses for computer programs on nodes oonnected in a network.
~escrip~ o~ the Prior Art In the past, various attempts have been made to prevent unauthorized copying and use of computer program~. So-called copy protection methods and devices were developed to control use of a computer program on a stand-alone computer, such as a personal computer (PC). Such PC would include a CPU, system memory and, optionally, a disk storage device such as a disk drive, referred to simply as a disk. In general, there are limitations when such copy protection is used and many PC's are connected together by a network link to form a computer network.
When PC's are connected together to form a network, the PC ~ 9 can be called nodes of that network. Such network can also include a file server, which functions as a central, master controller of system data, including the availability of a computer program for use at a given node. Some file server systems cause an application program to check the serial number on the file ~erver on which it is running. For example, in "Software Prot~ction," an article by ~oug and Dale 1 3 ~
Cabell published in Micro_Communications, Vol. Z, No. 5, May, 1~85, p. 35-37, it is noted that the application program checks the serial number by making a special networ~ call and comparing the result with the expected respon~e. The applica-tion program receives a completion code if the numbers match.
To prevent the application program from running if the numbers do not match, the user is logged off the network.
Other systems that control the running of computer programs require a specific hardware board on a node on which the computer program is to run. The applicability of such systems is thus limited to workstations that ha~e the required hardware board. One hardware-based copy protection approach includes an identifying code in the hardware board at a given node and requires the protected computer program to carry a matching code in order to unction at that node. Such approach solves the copy protection problem with respect to the computer program since an unauthorized copy would not have an identifying code that matches the identifying code of the workqtation's hardware board. However, such copy protection approach doesn't address the situation in which the demand for running copies of the computer program simultaneously is in excess of the number of authorized licenses for such computer program, where the authorized number can be executed on any of the nodes of the network.
Even though these and other methods and systems have been proposed, the literature indicates that users are still expariencing problems in the use of network~ in which limitations are placed on how many copies of a given computer program may run simultaneously on the network.
\
1 3 1 ~ ~ 2 ~
SUMMARY 0~ T~ INV~NTION
An object of the present invention is to provide methods and systems for controlling the use of computer programs.
Another ob~ect of the present invention i5 to manage the availability, on nodes connected in a ne~work, of licenses for computer programs that are to run on such nodes.
A related object of the present invention is to enable a copy of a ~iven computer program to be executed on any node of a network at any time, provided that, at the time a request is made to execute such copy at a particular node, the aggregate number of other copies of the given program that are being executed on the network is one 1ess than the number of licenses for such given program that are authorized to be executed simultaneously on the network.
Yet another obJect of the present invention is to provide a license file on a node of a network, such license file including, first, at least one license that is effective to authorize the execution of a copy of a given computer program and, secondly, a unique identification; wherein a Pacility is associated with such copy of the given computer program for determining that such unique identification is valid before such license is used to authorize the execution of such copy of such given computer program.
A further object of the present invention is to provide licenses that can be transferred from node to node to allow the execution of a particular computer program at a particular node, where the tran~fer of the licenses i9 controlled by an identification that is assigned to each license and that is ~ 3 ~
unique according to the particular node to which the license is transferred.
A still further ob~ect of the present invention is to provide for each computer program in the network, a license manager facility that enables a copy of the computer program to run on a particular node if a license file containing at least one license has a unique identification that matches a system record of such identification, and when such a valid license file is not at such particular node, the license mana8er facility searches other nodes for a valid license file having a lic~nse that is available for use at such particular node.
An additional ob~ect of the present invention reside~ in a license manager facility that transfers an available license from a remote node to a local node at which it is desired to use a computer program, wherein the facility assigns a new unique identification to the transferred license at the local node and erases the record from the remote node so that the license is effective only at the local node to which it was transferred.
With these and other ob~ects in view, a management system according to the present invention is provided for controlling the operability of computer programs on any of a plurality of nodes (or workstations) coupled together in a network. The vendor of the computer programs may require that a license be available for each such node at which one or more of ~aid computer program~ are to run. However, the owner of the network may want the number of licen~e9 that are to be avail-able for a given computer program on ~uch network to be le~s ~ ~ 3 ~
than the total quantity of the nodes that are included in the network, or at leas~ less than the aggregate number of copies o the computer program that all network users could possibly want to run simultaneously. The system accommodates the interests of both the vendor and the network owner as follows.
To serve the interests of the network owner, the total quantity of licenses to be loaded on the network may be less than the total quantity of the nodes in the network and, in any event, is generally less than the aggregate number of copies of the computer program that all network users could possibly want to run simultaneously. In a general sense, a license file is provided on the network, such as on a particular node. In one embodiment of the present invention the license file may include ~ust one such license and many such license files are loaded onto one or more nodes. In another embodiment of the present invention, the license file may include any number of licenses for the given computer program. A system facility (such as an operating system) assigns to each license file a unique identification ~UID) that is different from the UID of all other ones of the license files. In response to a request for operation of a copy of the given computer program at a selected node, the license file is searched to determine whether the license file is valid, which req~lires comparison of the UID of the license file to the UID
assigned by the system facility to that licen~e file. If such UIDs match, a further determination is made as to whether one of the licenses in such license file iq available for use at the selected node. In response to locating the available license in the valid license ile, the mana~ement system ~L 3 ~ 3 enables the computer program at the ~elected node to run. If no valid license file is located, or if all valid license files contain licenses that are in use, or unavailable, then the management system returns a status to the computer program indicating that it is not a~thorized to run.
Other objects of the present invention relate to a method of managing licenses to limi~ the number (S) of copies of a given computer program that are executing simultaneously on the nodes oi a network. Such limiting i9 according to the number (L) of licenses for the given computer program that are available on such network. To protect the interests of the computer program vendor, the method limits S to less than or equal to L. Each of the nodes at which a copy of the given computer program is executing has licens~ memory (such as a disk) and system memory. The license memory stores license files that include one or more licenses for the given computer program, and a directory file. Th~ directory file contains the name of the license file and the UlD for such license file.
The method includes the steps of installing a given com-puter program onto the license memory of at lea~t one of thenodes of the network. The computer program is current with respect to time when its term of authorized use has not e~pired. The next step is loading one or more license files onto the license memory of at least one node of the network.
In a first embodiment of the present method, the license file contains one license for the given computer program and many license iiles are used to provide L licenses. In a second embodiment of the present method, only one license file need be used, and such licen9e file contain~ L licenses.
1 3 1 ~ ~ 2 ~
The loading i~ followed by a~signing to each o~ the loaded license files an identification that is unique to the license file at the time of such loading. A license is inactive when it has not been used to authorize the execution of a copy of the computer program. The nodes are referred to as local nodes or remote nodes. The local node is the node at which a user desires to run the computer program. The remote node is any other node in the network.
In the first embodiment, the license in the license file can only authorize the execution of a copy at the local node on which the license file is stored, and the license files are transferred, if necessary, to the local node. In the second embodiment, any license in the license file can authorize use of a copy of the given computer pro~ram at any local or remote node.
In response to a request to run a copy of the given computer program at a local node, the directory at the local node is searched for a license file. Upon determining that no such license file is valid, or ii valid, that no licenses therein are available, directories at the remote nodes are searched for a license file that is valid.
In the first embodiment, if the license file at the remote node is valid and the license therein is inactive and thus available, the inactive current license located at the remote node is trans~erred to the local node. Then, a unique identification is assigned to the license that wa3 transferred to the local node and the license file is erased from the remote node. A 3tatus iS returned to the computer program ~3~ ~21~
indicating that it has a license and is allowed to run on the local node.
In the second embodiment, if a valid license file is located at a remote node, and a license therein is available, a license manager associated with the copy at the local node authorizes use of the copy and modifies ~he record in the license file at th~ remote node to indicate that such available license is now in use.
BRIEF DESCRIPTION OF THE DRAWINGS
Other objectives, features and advantages of the present invention will be apparent from an examination of the following detailPd descriptions which include the attached drawings in which:
FIG. 1 is a block diagram of a computer network showing nodes connected in a network by a network link; where fewer licenses are available on the network for a given computer program than the possible demand for such licenses;
FIGS. 2A, 2B and 2C are block diagrams of a portion of a disk at a node, showing for a first embodiment of the invention a directory file for indicating that a license file and a computer program are on the node, and showing a license manager program in a computer program file for controlling the use of a copy of the computer program according to whether the license file is valid and contains an available license;
FIGS. 3A and 3B form a flow chart showing the functions performed by the license manager program of the first embodiment of the invention to enable a copy oP the computer program to be executed at a local node both when a licen~e is :~ 3 ~
or is not initially on and available for use on the local node;
FIG. 4 is a flow chart showing how a license of the first ..
embodiment of the invention is initially loaded into a license file on a node and a unique identificatioll is assigned to the license file, wherein such unique identifica~ion is changed each time the license is transferred to a different node;
FIGS. 5A, 5B and 5C are block dia~rams of a portion of a disk at a node, showing for a second embodiment of the invention a directory file ~or indicating that a license file and a computer program are on a node, where the license file contains a license pool including many licenses, and showing the license file and a license manager program in a computer file;
FIG. 6 is a flow chart showing the function~ performed by the license manager program of the second embodiment for controlling the use of a copy of the computer program according to the validity of the license file and whether the license pool includes an available license;
FIG. 7A is a flow chart showing how a license file of the second embodiment is initially loaded onto a nodP and assigned a unique identification; and FIG. 7B is a chart showing a pool source file that is supplied to a customer for providing licenses for the second embodiment of the present invention.
13~2~
D~TAIL~D D~SCRIPTION OF TH~ PR~ERX~D EMBODIM~NTS
General Description Referring now to FIG. 1, the management system 10 of the present invention is shown for use with a network 11 having a plurality of nodes 12 that are interconnected by a network link 13. For purposes of description, one of the nodes 12 is referred to as a local or first node 14. Any of the nodes 12 may be a local node 14. Each node 12 includes an operating system 15, system memory 16, an installation program 17 and a CPU 18. The nodes 12 also include a peripheral storage device such as a disk 19. The nodes 12 other than the local node 14 are referred to as remote nodes 20 with respect to the local node 14.
Files of License Transfer Embodiment As shown in FIGs. 1, 2A through 2C, and FIGs. 5A through 5C, there are files in the disk 19. For a first embodiment of the present invention ~referred to as the license transfer embodiment for convenience), the files include a directory file 21A (FIG. 2A), a license file 22A (FIG. 2B) and a com-puter program file 23A (FIG. 2C). A computer program 24A in the file 23A may be a standard applications program, such as the Series 5000 Advanced Graphics Software pro~ram marketed by Auto-trol Technology Corporation. The computer program file 23A may also include a license manager computer program. For the license transfer embodiment, the licen8e manager computer program is referred to as a license manager 25A and is ~hown in detail in FIGS. 3A and 3B. A directory 26A of the license ~ 3 ~
transfer embodiment is contained in the directory file 21A.
The license file 23A may or may not be on the disk 19, depending upon condition~ at any particular time in the operation of the network 11. For the license transfer embodiment, the license file 22A contains one license 27.
Files of License Pool Embodiment For a second embodiment of the present invention (referred to as the license pool embodiment for convenience) the license file is referred to by the reference number 22B
(FIG. 5B) and may have as many licenses 27 therein as the number of copies of a given computer program 24B (FIG. 5C) ~hat are authorized to be run simultaneously. Similarly, the directory file is referred to by the reference number 21B
(FIG. 5A) and con~ains a directory 26B relating to a license pool 28 that is in the license file 22B. The computer program 24B is in a computer program file 23B (FIG. 5C) and is associated with a license manager referred to by the reference number 25B (FIG. 5C). The computer program 24B may be a different applications computer program, for example, from the computer program 24A.
Control of Computer Programs 24A and 24B
The apparatus and the methods of the pre3ent invention are effective to control the execution of the computer programs 24A and 24B on the local node 14, for example. Ini-tially, the computer program~ 24A and 24B will be in the respective computer program ~iles 23A and 23B on the local node 14 or on one of the remote node~ 20. In either case, 3 ~ 3 when a user want~ to run a copy of the computer programs 24A
and 24B on the local node 14, the computer programs 24A and 24B and the respective license manager 25A or 25B will be written from the respective computer program file 23A or 23B
into the system memory 16 at the local node 14. Further, under the control of the owner of the network 11, fewer licenses 27 may be stored on the nodes 12 of the network 11 than the aggregate number of nodes 12 in the network 11. Also under the owner's control, since ~any copies of the computer programs 24A or 24B may be operated simultaneously at a given node 12, the number of licenses 27 stored in the license files 22A-22A or in the license file 22B on the nodes 12 need not be related to the number of node 12, and may be less than the total possible number of copies of the given computer program 24A or 24B that all network users desire to execute simultaneously. The computer program vendor's interests are protected since the owner must purchase the licenses 27 for the given computer programs 24A and 24B, and the total quantity of licenses 27 purchased will limit the total quantity of copies of the given computer programs 24A and 24B that can be executed simultaneously.
The operating system 15 assigns an identification to each license file 22A or 22B such as the license file 22A
containing the license 27 at the local node 14. In connection with the installation program 17 at the local node 14, the assigned identification is unique to the license file 22A or 22B that was stored on the local node 14 at a particular time.
For ease of expression, the identification assigned to a given ~3~ ~2~
license file 22A or 22B at a given node 12 at a particular time is referred to as the UID.
When a user at the local node 14 make~ a request to run the computer programs 24A or 24B on the local node 14, the respective license manager 25A or 25~ is effective to search the respective directory 26A or 26B of the respective license file 22A or 22B at the local node 14 to determine whether one of the license files 22A or 22B is on the local node 14. If so, then the actual VID of such license file 22A or 22B is compared to the UID for such license file 22A or 22B that was assigned to it by the operating sy3tem 15. If the compared UID's are the same, the respective license manager 25A or 25B
then determines whether a license 27 in such respective license file 23A or 23B is available to be run on the local node 14. If such license 27 is available and i such license 27 has not expired, then the respective license manager 25A or 25B enables the computer program 24A or 24B at the local node 14 to run on the local node 14.
Methods of the present inYentiOn may be used for controlling the execution of the computer programs 24A and 24B
on the local node 14 when the license files 22A or 22B are on the disk 19 of the local node 14. Such methods may also be used when no license file 22A or 22B i~ at the local node 14 at the time of a request to run the computer program9 24A or 24B
on the local node 14. In both eases, the methods manage the licenses 27 to limit the number of copies of the computer programs 24A or 24~ that may be run simultaneously on the nodes 12 of the network, where such limiting i9 according to the .,.,, ~, ,,. . , ~, , .
~ 3 ~
aggregate number L o the licenses 27 that are available on the network 11.
In the use of one method, afte~ loading of the ~ompute~
program 24A or 24s onto at least one node lZ, the desired number of L licenses 27 are loaded onto any de~ired ones of the nodes 12. In the license transfer embodiment, this is done by loading the desired number L of license files 22A onto selected ones of the nodes 12, or in the license pool embodiment by loading as few as one license file 22B onto one node 12, where such license file 22B contains the license pool 28 having the desired number L of licenses 27. Such number L
of licenses 27 for the computer programs 24A or 24B i5 generally less than the total quantity of the nodes 12 of the network 11. However, when it is desired to run more than one copy of the computer program 24A on any given node 12, the total number L of licenses 27 loaded onto the network 11 would be less than the ag~regate number of copies of the computer program 24A that all network user3 could possibly want to run simultaneously.
Each license file 22A or 22B that is loaded onto a node 12 is assigned a UID. In response to a request at the local node 14 to run a copy o~ the computer program 24A or 24B, the respective directory 26A or 26B at the local node 14 is searched and, in this example, it is determined that no license file 22A or 22B is on the di~k 19 of such local node 14. The directories 26A-26A or 26B-26B respectively of the remote nodes 20-20 are then searched. Upon locating the licen e file 22A or 22B at one of the remote node9 20-20, the UID contained in the respective license file 22A or 22B is .. , ... ".~ .
~ 3 ~
compared to the UID corresponding to such license file 22A or 22B that the opersting system 15 caused to be written into the respecti~e directory 26A or 26B at such remote node 20. If such UID's match, then in both embodiments a determination is made as to whether the license 27 in the respective license ~ile 22A or 22B is in use, and if not, the computer program 24A
or 24B that was the sub~ect of the request to run on the local node 14 is then enabled to run.
In the license transfer embodiment, when the UID's match and the license in the license file 22A is available, then the license file 22A is modified by causing the license 27 at the remote node 20 to be transferred to the system memory 16 in the local node 14. The operating system 15 at the local node 14 then assigns a new UID to the transferred license 27 and writes such UID into the system memory 16 at the local node 14. The modification of the license file 22A at the remote node 20 is completed by erasing the license 27 so that only one license 27 exists on the network 11 corresponding to the original license 27 that was at the remote node 20. Then the record of the transferred license 27 in such system memory 16 and the new UID
for such transferred license 27 are identified as being in use (FIG. 2B). The new UID of the trahsferred license 27 and the other license information shown in FIG. 2B are encrypted and as encrypted are stored in the system memory 16 at the local node 14. The encrypted information for the transferred license 27 is then written to the disk 19 at the local node 14.
In the license pool embodiment, when the UID's match and any license 27 in the license pool 28 of the license file 22B
is available, the license file 22B i9 also modified by .. ..
~ 3 ~
decrementing the number of available licenses 27 therein (FIG.
5B) qo that the available pool of licenses 27 i8 one less.
DETAILED DESCRIPTION OF LICENSE TRANSFER EMBODIMENT
Referring now to FIG. l in detail, each node 12 of the network 11 may be a stand-alone computer, such as an Apollo DN3000 computer, for example. Such computer has the CPU 18, the ~ystem memory 16 and in such memory 16 the operating system 15 and the ins~allation procedure 17.
In the initialization of each node 12 of the network 11, each computer program 24A that is to be run on any of the node~ 12, such as the local node 14 or the remote node 20, is loaded onto at least one of the nodes 12 in a standard manner.
FIG. 2C shows the file 23A on the disk 19 for the computer program 24A, including the license manager 25A.
License Loading Procedure Referring now to FIG. 4, the ag~regate number L of licenses 27 loaded onto the nodes 12 is determined by how many copies of the given computer program 24A the owner of the network 11 has purchased. Thus, as to that given computer program 24A, the number L of licenses 27 that have been purchased is the maximum number of copies of such given computer program 24A that are permitted to run at any given time. For example, if there are ten nodes 12 included in the network 11, and if a maximum of three copies of the given computer program 24A can run on any ~iven node 12 at any one time, then there can be a demand to run thirty copies of the ~ 3~ ~ ~2 ~
given computer program 24A at any particular time. However, if only ten licenses 27 are loaded onto the network 11 for the given computer program 24A, the license managers 25A-25A
~FIGS. 2C, 3A and 3B) will permit only ten of the thirty copies of the computer program 24A to run at any given time. Thus, when either fewer licenses 27 than the aggregate number of nodes 12 (where only one copy of the given computer program 24A
can run on one node 12~, or when fewer licenses 27 than the total demand for licenses (where more than one copy of the given computer program 24A can run on a node 12) are loaded onto the network 11, the license managers 25A-25A are effective to limit the aggregate number of copies of the given computer program 24A that can run on the network 11 at any given time.
FIG. 4 illustrates the steps utilized to load a given license 27 onto a node 12 of the network 11. Initially, the license 27 is copied from an installation media 29 onto the license file 22A on the disk 19 at the local node 14, for example. As shown in FIG. 2B, the license file 22A will include at least an expiration date for the license 27. At the same time, the operating system 15 a~signs a UID to the license file 22A. Since there is only one license 27 in the license file 22A, such UID is thus the UID of the license 27 as well. At this ~uncture, the license 27 is not yet a~-thorized. To authorize the license 27, the installation program 17 reads the UID of the license file 22A from the disk 19 and encrypts it to form a fir~t authorization codè, referred to as Cl. The user or customer calls the vendor of the computer program 24A that has been loaded onto the local node 12 and advises the vendor of the encrypted Cl. The ~3~2~
vendor checks the encrypted Cl to determine whether the li-cense 27 is an authorized license Z7. If so, the v~ndor re-encrypts the Cl in a different form to form a second authorization code, referred to as C2. The vendor sends the encrypted C2 to the customer. The customer then enters the encrypted C2 into the installation program 17, and the installation program 17 checks the encrypted C2 to see if it was generated by the vendor's computer program. If so, the installation program 17 encrypts the UID of the license file 22A and the other license information of the licens~ file 22A
and writes it into the license file 22A on the disk 19 of the local node 14. It is to be understood, then, that the UID is stored with the license 27 in the license file 22A on the local node 14 before any request to use the given computer program 24A has or can be made.
This license loading procedure is then repeated until the desired aggregate number L of license files 22A having an aggregate of L licenses 27 for the given computer program 24A
have been loaded onto the nodes 12 of the network 11. At this ~0 juncture, the network 11 will have been loaded with at least one copy of the given computer program 24A and with the de~ired aggregate number L of licenses 27 for the given computer program 24A. The network 11 is ready for a user to make a request to run a copy of the given co~puter program 24A
on one of the nodes 12, such as on the local node 14.
Request To Run Computer Program 24~ 0n LocaL Nod~ 14 The method and apparatus of th~ licen~e tran9fer embodiment of the present invention may be under~tood by ---` 13~2~
referring to FIGS. 3A and 3B. There, the functions performed by the license manager 25A are shown in flow chart for~.
Initially, it should be understood that one license manager 25A
(FIG. 2C) is part of each copy of the given computer program 24A that is contained in a computer program file 23A. In a preferred etnbodiment of the present invention, this can be achieved by having the computer program 24A in the file 23A on the disk 19 include the license manager 25A, such that as each copy of the computer program 24A is written into the system ~0 memory 16 at a given node 12, the corresponding licens~ manager 25A will also be written into the system memory 16.
Each license manager 25A pPrforms the functions shown in FIGS. 3A and 3B with respect to it~ respective copy of the given computer program 24A. Assume for purposes of illustration that the customer's network user desires to use a copy of the given computer program 24A at the local node 14.
The copy of the given computer program 24A on the local node 14 contacts the license manager 25A at the local node 14 by making a subroutine call. In response, the license manager 25A asks (Step 30) whether a license 27 exists on the local node 14 for the given computer program 24A. This question first causes a determination to be made as to whether there is a license file 22A (and thus a license 27) on the disk 19 at the local node 14. If so, the license manager 25A takes a "yes" path 31 and in step 32 determines whether such license 27 is then "in use"
or "active". That i~, such determination made by the step 32 indicates whether the CPU 18 is at that time "u~ing" the licen~e 27 by running a copy o~ the computer program 24A on the local node 14 under the authorization of such license 27. If - lg -`` ~3~ 2, ~
so, the license manager 25A then takes a "yes" path 33 and returns to a next step 34. If the license 27 i~ not active on the local node 14, the 3.icense manager 25A then determines whether the inactive license 27 is "valid". This is done by asking the operating system 15 for the UID for the license 27 that the operating system 15 caused to be stored in a record in the system memory 16 at the local node 14. The license manager 25A then decrypts the UID contained in the license file 22 for the license 27 and compares it to the ~ID for such license 27 that was received from the operating system 15. The license is not valid if the UIDs are not the same. In such event, then the l;cense manager Z5A takes the "yes" path 33 and returns to the step 34. If the UIDs are the same, the license manager 25A
then determines whether the current date is later than the expiration date of the inactive licen~e 27 (see FIG. 2B). If so, then the license 27 has "expired" and the license manager 25A takes the path 33 and returns to the next step 34. If not expired, the license manager 25A then takes a path 35 indicating that the license 27 is inactive, current and valid.
The pa~h 35 leads to step 36 that now marks such license 27 as being "active" or "in use" in respon5e to the new request to use the computer program 24A (see item 2 in file 22A, FIG. 2B).
This prevents the inactive, current, valid license 27 from being assigned to any other node 12. The licen~e manager 25A
then takes a path 37 to a step 38 that returns a 3tatus to the computer program 24A indicating that it is authorized to run, which enable9 the oomputer program 24A to run on the CPU 18 at the local node 14.
~31~2~
~equest for License 27 - Licen~e at Remote Node 20 As indicated above, with respect to the local node 14, ! the questions asked in ~tep 32 can be answered in the affirmative or negative and if any one is answered "yes", it results in no license 27 being available for the computer program 24A on the local node 14. In any "yes" event 9 the license manager 25A then returns via path 33 to step 34. In step 34 the nodes 14 and 20-20 that have been ~earched are noted. If all nodes have been searched, a "yes" answer is given and a path 39 ls taken to ~tep 40. If, as in the example, the first remote node 20 has not been searched, path 41 is taken to step 42. Step 42 determines whether a license 27 exists on the next node 12 in the network 11 which in this example, is the first remote node 20. If the license 27 is not in the license file 22A on the remote node 20, then a "no"
path 43 is taken and the license manager 25A performs step 34 and determines whether all nodes 12 have been searched for a license 27. In this example, since only the local node 14 and the irst remote node 20 have been searched, the "no" path 41 is taken and the licen3e manager 25A loops to step 42 and then agsin determines whether a license ~7 exists on the next or second remote node 20 in the network 11. Assuming the next node 12 is the next remote node counterclockwise around the network ll, and that a license 27 exists in the license file 22A on the disk 19 in such remote node 20, then a "yes" path 44 i9 taken to a step 45. The license manager 25A then determines (as described above in respect to step 32) whether the license 27 in the licence file 22A on the ~econd remote node 20 is in use or whether the expiration date ha~ expired or whether it is ~ 3 ~ 2 ~
invalid. In any of these events, a "yes" path 46 is tak~n to the step 34 and the determination as to whether all nodes 12 ha~e been searched i9 again made.
Transfer of License 27 to Local Node 14 If the license 27 in the license file 22A on the second remote node 20 has not expired, is not in use and i~ valid, a "no" path 47 is taken to a step 48. The ~tep 48 is the first step in the transfer of the license 27 to the local node 14.
The license 27 so transferred is referred to as a "transferred license". In step 48, the license manager 25A causes the li-cense 27 to be stored in the ~y~tem memory 16 at the local node 14. The license manager 25A then takes path 49 to a step 50 that causes the operating system 15 at the local node 14 to create a new empty l~cense file 22A on the local node 14 at which it i5 desired to use the copy of the computer program 24A. In step 50, the operating system 15 also assigns a new unique identification (UID) to the license 27 and cause~ same to be written into the system memory 16 at the local node 14.
A path 51 leads from step 50 to the next step 52 in the trans-fer operation, which is to delete or erase the tran~ferred license 27 from the licen~e file 22A at the second remote node 20. The license manager 25A request~ the operating system 15 to effect ~uch erasure. The erasure i~ effected only if the transferred license 27 ha9 not previously been erased from the license file 22A at the second remote node 20. ~ path 53 is taken to step 54 that a9k9 whether 9uch erasure wa~ done. If ~uch erasure ha9 not been accompli~hed, the operating system replie~ by sending a "no" me9sage to the license manager 25A
~ 3 1 ~ ~
and a path 55 is taken to step 56. Step 56 deletes the new license file 22A from the second remote node 20 and the program re~urns to step 34 so that the "all nodes searched?" question is askad again.
Referring to FIG. 1, assuming the transferred license 27 was erased from the license file 22A at the second remote node 20, this leaves only the transferred license 27 in the system memory 16 at the local node 14, such that it is no longer possible to use the transferred license 27 on the second remote node 20. Moreover, such erasure deals with the situation in which users at two different nodes 12 both want to use a copy of a computer program 24A that is not at each user's respective local node 14, but is, for example, at a remote node 20B. In this situation, the first user (e.g. at the node 14A) t~
complete the erasure step 52 (by erasing the transferred license 27 from the license file 22A at the remote node 20C) will be enabled to use such transferred license 27. When the license manager 25A on the other local node 14B attempts to again erase the transferred license 27 from the license file 22A at the remote node 20C, the message from step 54 will prevent completion of the transfer of the license 27 to the local node 14B, such that the re~uest from the local node 14B
is processed further by performing the "all nodes searched?"
step 34.
After erasure from the second remote node 20C, the li-cense manager 25A takes path 57 to step 58 that identifies the transferred licens~ 27 in the system memory 16 at the local node 14 as being "in use" so a~ to prevent a user at 8 different node 12 from having acce3~ to the transferred 1 3 ~ ~ Lf~ 2 ~
license 27 and transferring it away from the local node 14.
The license manager 25A then takes path 59 to step 60 and encrypts all of the data or license information (see FIG. 2B) of the transferred license 27, including the UID of the new license file 22A, that is in the system memory 16 at the local node 14. The license manager 25A then takes path 61 to step 62 and writes this encrypted license information into the new license file 22A on the disk 19 at the local node 14. Path 63 is taken to the step 38 that return~ the status to the computer program 24A indicating that the computer program 24A is authorized to run, which enables the computer program 24A to run on the CPU 18 at the local node 14.
The flow chart in FIGS. 3A and 3B can also be e~pre9sed in terms of in~tructions that are used by the licen~e manager 25A
to cause the above-described functicns to ~e performed. Such instructions are set forth in Appendix A.
DETAILED DESCRIPTION OF_LICENSE POOL EMBODIMENT
Referring again to FIG. l in detail, the network 11 is also used for the license pool embodiment, and thus includes the CPU 18, the system memory 16 and in such memory 16 the operating system 15 and the installation procedure 17.
In the initialization of each node 12 of the network 11, each computer program 24~ that is to be run on any of the nodes 12, such as the local node 14 or the remote node 20 3 i~
loaded onto at least one of the node9 12 in a standard manner.
FIG. 5C show~ the ile 23B that is on the di~k 19 for the computer program 24B, including the licen~e manager 25B.
LIC~NS~ MAN~GEMENT M~THODS AND SYSTEMS
Speciication BAC~GROV~D OF TE~ INVENTI9 Field of the I~ve~tion The present invention relates to the field of controlling the use of computPr programs and more particularly to the field of managing the availability of licenses for computer programs on nodes oonnected in a network.
~escrip~ o~ the Prior Art In the past, various attempts have been made to prevent unauthorized copying and use of computer program~. So-called copy protection methods and devices were developed to control use of a computer program on a stand-alone computer, such as a personal computer (PC). Such PC would include a CPU, system memory and, optionally, a disk storage device such as a disk drive, referred to simply as a disk. In general, there are limitations when such copy protection is used and many PC's are connected together by a network link to form a computer network.
When PC's are connected together to form a network, the PC ~ 9 can be called nodes of that network. Such network can also include a file server, which functions as a central, master controller of system data, including the availability of a computer program for use at a given node. Some file server systems cause an application program to check the serial number on the file ~erver on which it is running. For example, in "Software Prot~ction," an article by ~oug and Dale 1 3 ~
Cabell published in Micro_Communications, Vol. Z, No. 5, May, 1~85, p. 35-37, it is noted that the application program checks the serial number by making a special networ~ call and comparing the result with the expected respon~e. The applica-tion program receives a completion code if the numbers match.
To prevent the application program from running if the numbers do not match, the user is logged off the network.
Other systems that control the running of computer programs require a specific hardware board on a node on which the computer program is to run. The applicability of such systems is thus limited to workstations that ha~e the required hardware board. One hardware-based copy protection approach includes an identifying code in the hardware board at a given node and requires the protected computer program to carry a matching code in order to unction at that node. Such approach solves the copy protection problem with respect to the computer program since an unauthorized copy would not have an identifying code that matches the identifying code of the workqtation's hardware board. However, such copy protection approach doesn't address the situation in which the demand for running copies of the computer program simultaneously is in excess of the number of authorized licenses for such computer program, where the authorized number can be executed on any of the nodes of the network.
Even though these and other methods and systems have been proposed, the literature indicates that users are still expariencing problems in the use of network~ in which limitations are placed on how many copies of a given computer program may run simultaneously on the network.
\
1 3 1 ~ ~ 2 ~
SUMMARY 0~ T~ INV~NTION
An object of the present invention is to provide methods and systems for controlling the use of computer programs.
Another ob~ect of the present invention i5 to manage the availability, on nodes connected in a ne~work, of licenses for computer programs that are to run on such nodes.
A related object of the present invention is to enable a copy of a ~iven computer program to be executed on any node of a network at any time, provided that, at the time a request is made to execute such copy at a particular node, the aggregate number of other copies of the given program that are being executed on the network is one 1ess than the number of licenses for such given program that are authorized to be executed simultaneously on the network.
Yet another obJect of the present invention is to provide a license file on a node of a network, such license file including, first, at least one license that is effective to authorize the execution of a copy of a given computer program and, secondly, a unique identification; wherein a Pacility is associated with such copy of the given computer program for determining that such unique identification is valid before such license is used to authorize the execution of such copy of such given computer program.
A further object of the present invention is to provide licenses that can be transferred from node to node to allow the execution of a particular computer program at a particular node, where the tran~fer of the licenses i9 controlled by an identification that is assigned to each license and that is ~ 3 ~
unique according to the particular node to which the license is transferred.
A still further ob~ect of the present invention is to provide for each computer program in the network, a license manager facility that enables a copy of the computer program to run on a particular node if a license file containing at least one license has a unique identification that matches a system record of such identification, and when such a valid license file is not at such particular node, the license mana8er facility searches other nodes for a valid license file having a lic~nse that is available for use at such particular node.
An additional ob~ect of the present invention reside~ in a license manager facility that transfers an available license from a remote node to a local node at which it is desired to use a computer program, wherein the facility assigns a new unique identification to the transferred license at the local node and erases the record from the remote node so that the license is effective only at the local node to which it was transferred.
With these and other ob~ects in view, a management system according to the present invention is provided for controlling the operability of computer programs on any of a plurality of nodes (or workstations) coupled together in a network. The vendor of the computer programs may require that a license be available for each such node at which one or more of ~aid computer program~ are to run. However, the owner of the network may want the number of licen~e9 that are to be avail-able for a given computer program on ~uch network to be le~s ~ ~ 3 ~
than the total quantity of the nodes that are included in the network, or at leas~ less than the aggregate number of copies o the computer program that all network users could possibly want to run simultaneously. The system accommodates the interests of both the vendor and the network owner as follows.
To serve the interests of the network owner, the total quantity of licenses to be loaded on the network may be less than the total quantity of the nodes in the network and, in any event, is generally less than the aggregate number of copies of the computer program that all network users could possibly want to run simultaneously. In a general sense, a license file is provided on the network, such as on a particular node. In one embodiment of the present invention the license file may include ~ust one such license and many such license files are loaded onto one or more nodes. In another embodiment of the present invention, the license file may include any number of licenses for the given computer program. A system facility (such as an operating system) assigns to each license file a unique identification ~UID) that is different from the UID of all other ones of the license files. In response to a request for operation of a copy of the given computer program at a selected node, the license file is searched to determine whether the license file is valid, which req~lires comparison of the UID of the license file to the UID
assigned by the system facility to that licen~e file. If such UIDs match, a further determination is made as to whether one of the licenses in such license file iq available for use at the selected node. In response to locating the available license in the valid license ile, the mana~ement system ~L 3 ~ 3 enables the computer program at the ~elected node to run. If no valid license file is located, or if all valid license files contain licenses that are in use, or unavailable, then the management system returns a status to the computer program indicating that it is not a~thorized to run.
Other objects of the present invention relate to a method of managing licenses to limi~ the number (S) of copies of a given computer program that are executing simultaneously on the nodes oi a network. Such limiting i9 according to the number (L) of licenses for the given computer program that are available on such network. To protect the interests of the computer program vendor, the method limits S to less than or equal to L. Each of the nodes at which a copy of the given computer program is executing has licens~ memory (such as a disk) and system memory. The license memory stores license files that include one or more licenses for the given computer program, and a directory file. Th~ directory file contains the name of the license file and the UlD for such license file.
The method includes the steps of installing a given com-puter program onto the license memory of at lea~t one of thenodes of the network. The computer program is current with respect to time when its term of authorized use has not e~pired. The next step is loading one or more license files onto the license memory of at least one node of the network.
In a first embodiment of the present method, the license file contains one license for the given computer program and many license iiles are used to provide L licenses. In a second embodiment of the present method, only one license file need be used, and such licen9e file contain~ L licenses.
1 3 1 ~ ~ 2 ~
The loading i~ followed by a~signing to each o~ the loaded license files an identification that is unique to the license file at the time of such loading. A license is inactive when it has not been used to authorize the execution of a copy of the computer program. The nodes are referred to as local nodes or remote nodes. The local node is the node at which a user desires to run the computer program. The remote node is any other node in the network.
In the first embodiment, the license in the license file can only authorize the execution of a copy at the local node on which the license file is stored, and the license files are transferred, if necessary, to the local node. In the second embodiment, any license in the license file can authorize use of a copy of the given computer pro~ram at any local or remote node.
In response to a request to run a copy of the given computer program at a local node, the directory at the local node is searched for a license file. Upon determining that no such license file is valid, or ii valid, that no licenses therein are available, directories at the remote nodes are searched for a license file that is valid.
In the first embodiment, if the license file at the remote node is valid and the license therein is inactive and thus available, the inactive current license located at the remote node is trans~erred to the local node. Then, a unique identification is assigned to the license that wa3 transferred to the local node and the license file is erased from the remote node. A 3tatus iS returned to the computer program ~3~ ~21~
indicating that it has a license and is allowed to run on the local node.
In the second embodiment, if a valid license file is located at a remote node, and a license therein is available, a license manager associated with the copy at the local node authorizes use of the copy and modifies ~he record in the license file at th~ remote node to indicate that such available license is now in use.
BRIEF DESCRIPTION OF THE DRAWINGS
Other objectives, features and advantages of the present invention will be apparent from an examination of the following detailPd descriptions which include the attached drawings in which:
FIG. 1 is a block diagram of a computer network showing nodes connected in a network by a network link; where fewer licenses are available on the network for a given computer program than the possible demand for such licenses;
FIGS. 2A, 2B and 2C are block diagrams of a portion of a disk at a node, showing for a first embodiment of the invention a directory file for indicating that a license file and a computer program are on the node, and showing a license manager program in a computer program file for controlling the use of a copy of the computer program according to whether the license file is valid and contains an available license;
FIGS. 3A and 3B form a flow chart showing the functions performed by the license manager program of the first embodiment of the invention to enable a copy oP the computer program to be executed at a local node both when a licen~e is :~ 3 ~
or is not initially on and available for use on the local node;
FIG. 4 is a flow chart showing how a license of the first ..
embodiment of the invention is initially loaded into a license file on a node and a unique identificatioll is assigned to the license file, wherein such unique identifica~ion is changed each time the license is transferred to a different node;
FIGS. 5A, 5B and 5C are block dia~rams of a portion of a disk at a node, showing for a second embodiment of the invention a directory file ~or indicating that a license file and a computer program are on a node, where the license file contains a license pool including many licenses, and showing the license file and a license manager program in a computer file;
FIG. 6 is a flow chart showing the function~ performed by the license manager program of the second embodiment for controlling the use of a copy of the computer program according to the validity of the license file and whether the license pool includes an available license;
FIG. 7A is a flow chart showing how a license file of the second embodiment is initially loaded onto a nodP and assigned a unique identification; and FIG. 7B is a chart showing a pool source file that is supplied to a customer for providing licenses for the second embodiment of the present invention.
13~2~
D~TAIL~D D~SCRIPTION OF TH~ PR~ERX~D EMBODIM~NTS
General Description Referring now to FIG. 1, the management system 10 of the present invention is shown for use with a network 11 having a plurality of nodes 12 that are interconnected by a network link 13. For purposes of description, one of the nodes 12 is referred to as a local or first node 14. Any of the nodes 12 may be a local node 14. Each node 12 includes an operating system 15, system memory 16, an installation program 17 and a CPU 18. The nodes 12 also include a peripheral storage device such as a disk 19. The nodes 12 other than the local node 14 are referred to as remote nodes 20 with respect to the local node 14.
Files of License Transfer Embodiment As shown in FIGs. 1, 2A through 2C, and FIGs. 5A through 5C, there are files in the disk 19. For a first embodiment of the present invention ~referred to as the license transfer embodiment for convenience), the files include a directory file 21A (FIG. 2A), a license file 22A (FIG. 2B) and a com-puter program file 23A (FIG. 2C). A computer program 24A in the file 23A may be a standard applications program, such as the Series 5000 Advanced Graphics Software pro~ram marketed by Auto-trol Technology Corporation. The computer program file 23A may also include a license manager computer program. For the license transfer embodiment, the licen8e manager computer program is referred to as a license manager 25A and is ~hown in detail in FIGS. 3A and 3B. A directory 26A of the license ~ 3 ~
transfer embodiment is contained in the directory file 21A.
The license file 23A may or may not be on the disk 19, depending upon condition~ at any particular time in the operation of the network 11. For the license transfer embodiment, the license file 22A contains one license 27.
Files of License Pool Embodiment For a second embodiment of the present invention (referred to as the license pool embodiment for convenience) the license file is referred to by the reference number 22B
(FIG. 5B) and may have as many licenses 27 therein as the number of copies of a given computer program 24B (FIG. 5C) ~hat are authorized to be run simultaneously. Similarly, the directory file is referred to by the reference number 21B
(FIG. 5A) and con~ains a directory 26B relating to a license pool 28 that is in the license file 22B. The computer program 24B is in a computer program file 23B (FIG. 5C) and is associated with a license manager referred to by the reference number 25B (FIG. 5C). The computer program 24B may be a different applications computer program, for example, from the computer program 24A.
Control of Computer Programs 24A and 24B
The apparatus and the methods of the pre3ent invention are effective to control the execution of the computer programs 24A and 24B on the local node 14, for example. Ini-tially, the computer program~ 24A and 24B will be in the respective computer program ~iles 23A and 23B on the local node 14 or on one of the remote node~ 20. In either case, 3 ~ 3 when a user want~ to run a copy of the computer programs 24A
and 24B on the local node 14, the computer programs 24A and 24B and the respective license manager 25A or 25B will be written from the respective computer program file 23A or 23B
into the system memory 16 at the local node 14. Further, under the control of the owner of the network 11, fewer licenses 27 may be stored on the nodes 12 of the network 11 than the aggregate number of nodes 12 in the network 11. Also under the owner's control, since ~any copies of the computer programs 24A or 24B may be operated simultaneously at a given node 12, the number of licenses 27 stored in the license files 22A-22A or in the license file 22B on the nodes 12 need not be related to the number of node 12, and may be less than the total possible number of copies of the given computer program 24A or 24B that all network users desire to execute simultaneously. The computer program vendor's interests are protected since the owner must purchase the licenses 27 for the given computer programs 24A and 24B, and the total quantity of licenses 27 purchased will limit the total quantity of copies of the given computer programs 24A and 24B that can be executed simultaneously.
The operating system 15 assigns an identification to each license file 22A or 22B such as the license file 22A
containing the license 27 at the local node 14. In connection with the installation program 17 at the local node 14, the assigned identification is unique to the license file 22A or 22B that was stored on the local node 14 at a particular time.
For ease of expression, the identification assigned to a given ~3~ ~2~
license file 22A or 22B at a given node 12 at a particular time is referred to as the UID.
When a user at the local node 14 make~ a request to run the computer programs 24A or 24B on the local node 14, the respective license manager 25A or 25~ is effective to search the respective directory 26A or 26B of the respective license file 22A or 22B at the local node 14 to determine whether one of the license files 22A or 22B is on the local node 14. If so, then the actual VID of such license file 22A or 22B is compared to the UID for such license file 22A or 22B that was assigned to it by the operating sy3tem 15. If the compared UID's are the same, the respective license manager 25A or 25B
then determines whether a license 27 in such respective license file 23A or 23B is available to be run on the local node 14. If such license 27 is available and i such license 27 has not expired, then the respective license manager 25A or 25B enables the computer program 24A or 24B at the local node 14 to run on the local node 14.
Methods of the present inYentiOn may be used for controlling the execution of the computer programs 24A and 24B
on the local node 14 when the license files 22A or 22B are on the disk 19 of the local node 14. Such methods may also be used when no license file 22A or 22B i~ at the local node 14 at the time of a request to run the computer program9 24A or 24B
on the local node 14. In both eases, the methods manage the licenses 27 to limit the number of copies of the computer programs 24A or 24~ that may be run simultaneously on the nodes 12 of the network, where such limiting i9 according to the .,.,, ~, ,,. . , ~, , .
~ 3 ~
aggregate number L o the licenses 27 that are available on the network 11.
In the use of one method, afte~ loading of the ~ompute~
program 24A or 24s onto at least one node lZ, the desired number of L licenses 27 are loaded onto any de~ired ones of the nodes 12. In the license transfer embodiment, this is done by loading the desired number L of license files 22A onto selected ones of the nodes 12, or in the license pool embodiment by loading as few as one license file 22B onto one node 12, where such license file 22B contains the license pool 28 having the desired number L of licenses 27. Such number L
of licenses 27 for the computer programs 24A or 24B i5 generally less than the total quantity of the nodes 12 of the network 11. However, when it is desired to run more than one copy of the computer program 24A on any given node 12, the total number L of licenses 27 loaded onto the network 11 would be less than the ag~regate number of copies of the computer program 24A that all network user3 could possibly want to run simultaneously.
Each license file 22A or 22B that is loaded onto a node 12 is assigned a UID. In response to a request at the local node 14 to run a copy o~ the computer program 24A or 24B, the respective directory 26A or 26B at the local node 14 is searched and, in this example, it is determined that no license file 22A or 22B is on the di~k 19 of such local node 14. The directories 26A-26A or 26B-26B respectively of the remote nodes 20-20 are then searched. Upon locating the licen e file 22A or 22B at one of the remote node9 20-20, the UID contained in the respective license file 22A or 22B is .. , ... ".~ .
~ 3 ~
compared to the UID corresponding to such license file 22A or 22B that the opersting system 15 caused to be written into the respecti~e directory 26A or 26B at such remote node 20. If such UID's match, then in both embodiments a determination is made as to whether the license 27 in the respective license ~ile 22A or 22B is in use, and if not, the computer program 24A
or 24B that was the sub~ect of the request to run on the local node 14 is then enabled to run.
In the license transfer embodiment, when the UID's match and the license in the license file 22A is available, then the license file 22A is modified by causing the license 27 at the remote node 20 to be transferred to the system memory 16 in the local node 14. The operating system 15 at the local node 14 then assigns a new UID to the transferred license 27 and writes such UID into the system memory 16 at the local node 14. The modification of the license file 22A at the remote node 20 is completed by erasing the license 27 so that only one license 27 exists on the network 11 corresponding to the original license 27 that was at the remote node 20. Then the record of the transferred license 27 in such system memory 16 and the new UID
for such transferred license 27 are identified as being in use (FIG. 2B). The new UID of the trahsferred license 27 and the other license information shown in FIG. 2B are encrypted and as encrypted are stored in the system memory 16 at the local node 14. The encrypted information for the transferred license 27 is then written to the disk 19 at the local node 14.
In the license pool embodiment, when the UID's match and any license 27 in the license pool 28 of the license file 22B
is available, the license file 22B i9 also modified by .. ..
~ 3 ~
decrementing the number of available licenses 27 therein (FIG.
5B) qo that the available pool of licenses 27 i8 one less.
DETAILED DESCRIPTION OF LICENSE TRANSFER EMBODIMENT
Referring now to FIG. l in detail, each node 12 of the network 11 may be a stand-alone computer, such as an Apollo DN3000 computer, for example. Such computer has the CPU 18, the ~ystem memory 16 and in such memory 16 the operating system 15 and the ins~allation procedure 17.
In the initialization of each node 12 of the network 11, each computer program 24A that is to be run on any of the node~ 12, such as the local node 14 or the remote node 20, is loaded onto at least one of the nodes 12 in a standard manner.
FIG. 2C shows the file 23A on the disk 19 for the computer program 24A, including the license manager 25A.
License Loading Procedure Referring now to FIG. 4, the ag~regate number L of licenses 27 loaded onto the nodes 12 is determined by how many copies of the given computer program 24A the owner of the network 11 has purchased. Thus, as to that given computer program 24A, the number L of licenses 27 that have been purchased is the maximum number of copies of such given computer program 24A that are permitted to run at any given time. For example, if there are ten nodes 12 included in the network 11, and if a maximum of three copies of the given computer program 24A can run on any ~iven node 12 at any one time, then there can be a demand to run thirty copies of the ~ 3~ ~ ~2 ~
given computer program 24A at any particular time. However, if only ten licenses 27 are loaded onto the network 11 for the given computer program 24A, the license managers 25A-25A
~FIGS. 2C, 3A and 3B) will permit only ten of the thirty copies of the computer program 24A to run at any given time. Thus, when either fewer licenses 27 than the aggregate number of nodes 12 (where only one copy of the given computer program 24A
can run on one node 12~, or when fewer licenses 27 than the total demand for licenses (where more than one copy of the given computer program 24A can run on a node 12) are loaded onto the network 11, the license managers 25A-25A are effective to limit the aggregate number of copies of the given computer program 24A that can run on the network 11 at any given time.
FIG. 4 illustrates the steps utilized to load a given license 27 onto a node 12 of the network 11. Initially, the license 27 is copied from an installation media 29 onto the license file 22A on the disk 19 at the local node 14, for example. As shown in FIG. 2B, the license file 22A will include at least an expiration date for the license 27. At the same time, the operating system 15 a~signs a UID to the license file 22A. Since there is only one license 27 in the license file 22A, such UID is thus the UID of the license 27 as well. At this ~uncture, the license 27 is not yet a~-thorized. To authorize the license 27, the installation program 17 reads the UID of the license file 22A from the disk 19 and encrypts it to form a fir~t authorization codè, referred to as Cl. The user or customer calls the vendor of the computer program 24A that has been loaded onto the local node 12 and advises the vendor of the encrypted Cl. The ~3~2~
vendor checks the encrypted Cl to determine whether the li-cense 27 is an authorized license Z7. If so, the v~ndor re-encrypts the Cl in a different form to form a second authorization code, referred to as C2. The vendor sends the encrypted C2 to the customer. The customer then enters the encrypted C2 into the installation program 17, and the installation program 17 checks the encrypted C2 to see if it was generated by the vendor's computer program. If so, the installation program 17 encrypts the UID of the license file 22A and the other license information of the licens~ file 22A
and writes it into the license file 22A on the disk 19 of the local node 14. It is to be understood, then, that the UID is stored with the license 27 in the license file 22A on the local node 14 before any request to use the given computer program 24A has or can be made.
This license loading procedure is then repeated until the desired aggregate number L of license files 22A having an aggregate of L licenses 27 for the given computer program 24A
have been loaded onto the nodes 12 of the network 11. At this ~0 juncture, the network 11 will have been loaded with at least one copy of the given computer program 24A and with the de~ired aggregate number L of licenses 27 for the given computer program 24A. The network 11 is ready for a user to make a request to run a copy of the given co~puter program 24A
on one of the nodes 12, such as on the local node 14.
Request To Run Computer Program 24~ 0n LocaL Nod~ 14 The method and apparatus of th~ licen~e tran9fer embodiment of the present invention may be under~tood by ---` 13~2~
referring to FIGS. 3A and 3B. There, the functions performed by the license manager 25A are shown in flow chart for~.
Initially, it should be understood that one license manager 25A
(FIG. 2C) is part of each copy of the given computer program 24A that is contained in a computer program file 23A. In a preferred etnbodiment of the present invention, this can be achieved by having the computer program 24A in the file 23A on the disk 19 include the license manager 25A, such that as each copy of the computer program 24A is written into the system ~0 memory 16 at a given node 12, the corresponding licens~ manager 25A will also be written into the system memory 16.
Each license manager 25A pPrforms the functions shown in FIGS. 3A and 3B with respect to it~ respective copy of the given computer program 24A. Assume for purposes of illustration that the customer's network user desires to use a copy of the given computer program 24A at the local node 14.
The copy of the given computer program 24A on the local node 14 contacts the license manager 25A at the local node 14 by making a subroutine call. In response, the license manager 25A asks (Step 30) whether a license 27 exists on the local node 14 for the given computer program 24A. This question first causes a determination to be made as to whether there is a license file 22A (and thus a license 27) on the disk 19 at the local node 14. If so, the license manager 25A takes a "yes" path 31 and in step 32 determines whether such license 27 is then "in use"
or "active". That i~, such determination made by the step 32 indicates whether the CPU 18 is at that time "u~ing" the licen~e 27 by running a copy o~ the computer program 24A on the local node 14 under the authorization of such license 27. If - lg -`` ~3~ 2, ~
so, the license manager 25A then takes a "yes" path 33 and returns to a next step 34. If the license 27 i~ not active on the local node 14, the 3.icense manager 25A then determines whether the inactive license 27 is "valid". This is done by asking the operating system 15 for the UID for the license 27 that the operating system 15 caused to be stored in a record in the system memory 16 at the local node 14. The license manager 25A then decrypts the UID contained in the license file 22 for the license 27 and compares it to the ~ID for such license 27 that was received from the operating system 15. The license is not valid if the UIDs are not the same. In such event, then the l;cense manager Z5A takes the "yes" path 33 and returns to the step 34. If the UIDs are the same, the license manager 25A
then determines whether the current date is later than the expiration date of the inactive licen~e 27 (see FIG. 2B). If so, then the license 27 has "expired" and the license manager 25A takes the path 33 and returns to the next step 34. If not expired, the license manager 25A then takes a path 35 indicating that the license 27 is inactive, current and valid.
The pa~h 35 leads to step 36 that now marks such license 27 as being "active" or "in use" in respon5e to the new request to use the computer program 24A (see item 2 in file 22A, FIG. 2B).
This prevents the inactive, current, valid license 27 from being assigned to any other node 12. The licen~e manager 25A
then takes a path 37 to a step 38 that returns a 3tatus to the computer program 24A indicating that it is authorized to run, which enable9 the oomputer program 24A to run on the CPU 18 at the local node 14.
~31~2~
~equest for License 27 - Licen~e at Remote Node 20 As indicated above, with respect to the local node 14, ! the questions asked in ~tep 32 can be answered in the affirmative or negative and if any one is answered "yes", it results in no license 27 being available for the computer program 24A on the local node 14. In any "yes" event 9 the license manager 25A then returns via path 33 to step 34. In step 34 the nodes 14 and 20-20 that have been ~earched are noted. If all nodes have been searched, a "yes" answer is given and a path 39 ls taken to ~tep 40. If, as in the example, the first remote node 20 has not been searched, path 41 is taken to step 42. Step 42 determines whether a license 27 exists on the next node 12 in the network 11 which in this example, is the first remote node 20. If the license 27 is not in the license file 22A on the remote node 20, then a "no"
path 43 is taken and the license manager 25A performs step 34 and determines whether all nodes 12 have been searched for a license 27. In this example, since only the local node 14 and the irst remote node 20 have been searched, the "no" path 41 is taken and the licen3e manager 25A loops to step 42 and then agsin determines whether a license ~7 exists on the next or second remote node 20 in the network 11. Assuming the next node 12 is the next remote node counterclockwise around the network ll, and that a license 27 exists in the license file 22A on the disk 19 in such remote node 20, then a "yes" path 44 i9 taken to a step 45. The license manager 25A then determines (as described above in respect to step 32) whether the license 27 in the licence file 22A on the ~econd remote node 20 is in use or whether the expiration date ha~ expired or whether it is ~ 3 ~ 2 ~
invalid. In any of these events, a "yes" path 46 is tak~n to the step 34 and the determination as to whether all nodes 12 ha~e been searched i9 again made.
Transfer of License 27 to Local Node 14 If the license 27 in the license file 22A on the second remote node 20 has not expired, is not in use and i~ valid, a "no" path 47 is taken to a step 48. The ~tep 48 is the first step in the transfer of the license 27 to the local node 14.
The license 27 so transferred is referred to as a "transferred license". In step 48, the license manager 25A causes the li-cense 27 to be stored in the ~y~tem memory 16 at the local node 14. The license manager 25A then takes path 49 to a step 50 that causes the operating system 15 at the local node 14 to create a new empty l~cense file 22A on the local node 14 at which it i5 desired to use the copy of the computer program 24A. In step 50, the operating system 15 also assigns a new unique identification (UID) to the license 27 and cause~ same to be written into the system memory 16 at the local node 14.
A path 51 leads from step 50 to the next step 52 in the trans-fer operation, which is to delete or erase the tran~ferred license 27 from the licen~e file 22A at the second remote node 20. The license manager 25A request~ the operating system 15 to effect ~uch erasure. The erasure i~ effected only if the transferred license 27 ha9 not previously been erased from the license file 22A at the second remote node 20. ~ path 53 is taken to step 54 that a9k9 whether 9uch erasure wa~ done. If ~uch erasure ha9 not been accompli~hed, the operating system replie~ by sending a "no" me9sage to the license manager 25A
~ 3 1 ~ ~
and a path 55 is taken to step 56. Step 56 deletes the new license file 22A from the second remote node 20 and the program re~urns to step 34 so that the "all nodes searched?" question is askad again.
Referring to FIG. 1, assuming the transferred license 27 was erased from the license file 22A at the second remote node 20, this leaves only the transferred license 27 in the system memory 16 at the local node 14, such that it is no longer possible to use the transferred license 27 on the second remote node 20. Moreover, such erasure deals with the situation in which users at two different nodes 12 both want to use a copy of a computer program 24A that is not at each user's respective local node 14, but is, for example, at a remote node 20B. In this situation, the first user (e.g. at the node 14A) t~
complete the erasure step 52 (by erasing the transferred license 27 from the license file 22A at the remote node 20C) will be enabled to use such transferred license 27. When the license manager 25A on the other local node 14B attempts to again erase the transferred license 27 from the license file 22A at the remote node 20C, the message from step 54 will prevent completion of the transfer of the license 27 to the local node 14B, such that the re~uest from the local node 14B
is processed further by performing the "all nodes searched?"
step 34.
After erasure from the second remote node 20C, the li-cense manager 25A takes path 57 to step 58 that identifies the transferred licens~ 27 in the system memory 16 at the local node 14 as being "in use" so a~ to prevent a user at 8 different node 12 from having acce3~ to the transferred 1 3 ~ ~ Lf~ 2 ~
license 27 and transferring it away from the local node 14.
The license manager 25A then takes path 59 to step 60 and encrypts all of the data or license information (see FIG. 2B) of the transferred license 27, including the UID of the new license file 22A, that is in the system memory 16 at the local node 14. The license manager 25A then takes path 61 to step 62 and writes this encrypted license information into the new license file 22A on the disk 19 at the local node 14. Path 63 is taken to the step 38 that return~ the status to the computer program 24A indicating that the computer program 24A is authorized to run, which enables the computer program 24A to run on the CPU 18 at the local node 14.
The flow chart in FIGS. 3A and 3B can also be e~pre9sed in terms of in~tructions that are used by the licen~e manager 25A
to cause the above-described functicns to ~e performed. Such instructions are set forth in Appendix A.
DETAILED DESCRIPTION OF_LICENSE POOL EMBODIMENT
Referring again to FIG. l in detail, the network 11 is also used for the license pool embodiment, and thus includes the CPU 18, the system memory 16 and in such memory 16 the operating system 15 and the installation procedure 17.
In the initialization of each node 12 of the network 11, each computer program 24~ that is to be run on any of the nodes 12, such as the local node 14 or the remote node 20 3 i~
loaded onto at least one of the node9 12 in a standard manner.
FIG. 5C show~ the ile 23B that is on the di~k 19 for the computer program 24B, including the licen~e manager 25B.
- 2~ -~3~2~
License Loadin~ Procedure Referring now to FIG. 7A, the aggregate number L of licenses 27 loaded onto the nodes 12 is determined by how many copies of the given computer program 24B the owner of the network 11 has purchased. When either fewer licenses 27 than the aggregate number of nodes 12 (where only one copy of the given computer program 24B can run on one node 12), or when fewer licenses 27 than the total demand for licenses (where more than one copy of the given computer program 24B can run on a node 12) are loaded onto the network 11, the license managers 25B-25B are effectiYe to limit the aggregate number of copies of the given computer program 24B that can run on the network 11 at any gi~en time.
FIG. 7B shows a pool source file 64 that is stored on the media 29 that the owner of the network 11 receives from the vendor. The file 64 includes the i.d. of that node 12 onto which the license file 22B for the license pool 28 is to be loaded, the total number L of licenses that are to be authorized ~or the computer program 24B and the e~piration date of the license pool 28. One of the pool source files 64 may be loaded onto various ones of the nodes 12, and in that case Ll licenses would be in one file 64A and L2 licenses would be in another file 64B, where Ll + L2 = L.
FIG. 7A illustrates the steps utilized to load the licenses 27 onto the node 12 of the network 11 according to the node i.d. in the file 64. Initially~ the pool source file 64 is copied from the installation media 29 onto any node 12, such as on the local node 14. The installation program 17 2~) decrypts the information in the source file 64 for the license pool 28. The installation program 17 creates the license file 22B on the disk 19 of the node 12 corresponding to the node i.d. in the source file 64 (see FIG. 7A, item 2), and the operating system 15 then assigns a UID to ~hat license file 22B. Since there may be many licen~es 27 in that license file 22B, such UID is the UI~ that is common to all cf the licenses 27 in the license pool 28. At this ~uncture, the license pool 28 is not yet authorized. To authorize the license pool 28, the installation program 17 gets the UID of the license file 22B rom the operating system 1~ and the installation program 17 encrypts the UID of the license file 22B and the other license information of the pool source 64 and writes it into the license file 22B on the disk 19 of the node 12, as designated by the node i.d. It is to be understood, then, that the UID is stored with the license pool 28 and with the L
licenses 27 in the license file 22B on the designated node 12 befor~ any request to use the given computer program 24B has or can be made.
As compared to the license transfer embodiment, the license pool embodiment is preferred because the installation of the license source pool 64 can be performed by the owner of the network without contacting the vendor. Also, if one license pool 28 is used, for example, only one loading operation is required. To provide more access to the licen~es 27 should one node 12 be inoperative, however, it i~ preferred that at least two license pools 28-28 be u9ed, and installed on separate nodes 12, one having Ll and the other having L2 licen~es 27 as noted above.
~3~ ~17~
At this ~uncture, ~he network 11 will have been loaded with at least one copy of the given computer program 24B and with the desired aggregate number L of licenses 27 for the given computer program 24B. The network 11 is ready for a user make a request to run a copy of the given computer pro~ram 24B on one of the nodes 12, such as on the local node 14.
Request To_Run Computer Pro~ram 24B On Local Node 14 The method and apparatus of the license pool embodiment of the present invention may be understood by reerring to FIG. 6. There, the functions performed by the license manager . 25B are shown in flow chart form. Initially, it should be under~tood that one license manager 25B (FIG. 5C) is part of each copy of the given computer program 24B that i~ contained in a computer program file 22B in system memory 16. In the preferred embodiment of the present invention in which the Apollo DN3000 computer is used, separate iles 23B for the computer program 24B and the license manager 25B are on the disk 19. When the files 23B are loaded into the system memory 16, they are linked. On the other hand, such linking can also be achieved by having the computer program 24B in the file 23B
on the disk ~9 be linked to the license manager 25B, such that as each copy of the computer program Z4B is written into the system memory 16 at ~ given node 12, the corresponding licen~e manager 25B will also be written into the system memory 16.
Each license manager 25B perform9 the function~ shown in FIG. 6 with respect to it9 re9pective copy of the given computer program 24~. Assume for purposeq of illustration ~ 3 that the customer's network user degires to use a copy of the given computer program 24B at the local node 14. The copy of the given computer program 24B on the local node 14 contact~
the license manager 25B at the local node 14 by making a subroutine call (Step 65). In response, the license manager 25B in effect asks (Step 66) whether a license 28 exists on the local node 14 for the given computer program 24B. This question is answered by first causing a determination to be made as to whether there is a license file 22B (and thus a license pool 28 and a license 27) on the disk 19 at the local node 14. If so, the license manager 25B takes a "yes~' path 67 and in a step 72 determines whether the license pool 28 is "valid". This is done by asking the operating system 15 for the UID for the license pool 28 that the operating system 15 caused to be stored in a record in the system memory 16 at the local node 14. The license manager 25B then decrypts the UID
contained in the license file 22B for the license pool 28 and compares it to the UID for such license pool 28 that was received from the operating system 15. The license is not valid if the UIDs are not the same. In such event, then the license manager 25B takes a "no" path 73 and proceeds to step 70. If the UID~ are the same, the licen~e manager 25B
determines whether the current date is later than the expiration date of the valid license pool 28 (see FIG. 5B).
If so, then the license pool 2~ has expired and the license manager 25B takes path 73 and returns to step 70. If not expired, the licer5e manager 25B then determines whether any of the licenses 27 in the pool 28 are not in use. That i9, such determination made by the step 72 indicate~ whether the `~
~3~ ~2 3 CPUs 18 are at that time "using" all of the licenses 27 by running copies of the computer program 24B on the nodes 12 under the authorization of all such licenses 27. If all licenses 27 are being used, the license manager 25B then takes the "no" path 73 and returns step 70. If one license 27 is not active, the license manager 25B then takes a path 74 indicating that at least one of the licenses 27 is inactive 3 current and valid. The path 74 leads to step 75 that marks such license 27 as being "active" or "in use" (see item 3 in file 22B, FIG.
5B). This is done by modifying the license file 22B, such as by decrementing item 3 in file 22B to reduce the number of licenses 27 that are available in the license pool 28. This prevents that inactive, current, valid license 27 from being assigned to any other node 12. The license manager 25B thPn takes path 76 to step 77 that writes into the license pool 28 in the license file 22B information that the local node is using the license 27 that was just rendered active. The license manager 25B then takes path 78 to step 79 that returns a status to the computer program 24B indicating that it is authori2ed to run, which enables the computer program 24B to run on the CPU 18 at the local node 14.
Request for License 27 -_License at Remote Node 20 As indicated above, with respeot to the local node 14, the question asked in step 66 can be answered in the affirmative or negative and if it is answered "no" it indicates that no license pool 28 and thus no licen~e9 27 are available for the computer program 24B on the local node 14.
In the "no" event, the licen~e manager 25B then takes path 80 2 ~
to step 70. In step 70, the nodes 14 and 20-20 that have been searched are noted. If all node~ 14 and 20-20 ha~e been searched, a "yes" answer is given and a path 81 i3 taken to step 82. If, as in the example, the first remote node 20 has not been searched, an attempt is made to locate the license pool 28 on the first remote node 20, path 83 i9 taken to step 68. Step 68 determines whether a license pool 28 exists on the next node 12 in the network 11 which in this example, i9 the first remote node 20. If the license pool 28 is not on the remote node 20, then the license manager 25B performs another search if all nodes 12 have not been searched for a license pool 28. In this example, since only the local node 14 and the first remote node 20 have been searched, the license manager 25B loops and then again determines whether a license pool 28 exists on the next or second remote node 20 in the network ll.
Assuming the next node 12 is the next remote node counterclockwise around the network 11, and that a license pool 28 exists in the license file 22B on the disk 19 in such remote node 20, then "yes" path 83 is taken to step 68. The license manager 25B then determines (as described above in respect to step 72) whether the licen~e pool 28 in the license file 22B on the second remote node 20 is valid, and if so, performs the rest o~ step 72 to determine whether any license 27 in the valid license pool 28 is available, and if so, whether the expiration date has expired. In either of these events (e.g.
no licen~e 27 available in the valid license pool 28 or license pool 28 is expired), the "no" path 73 is taken to the ~tep 70 and the determination as to whether all nodes 12 have been searched is again made.
1 31 ~25 Use of License 27 on Local Node 14 If the license file 22B on the second remote node 20 has not expired and a license 27 is not in use and the pool 28 is valid, path 74 is taken to step 75. Rather ~han transferring the available, current license 27 from the licen~e pool 28, the license manager 25B on,the local node 14 causes step 75 to be performed in the license pool 28 aL- the second remote node 20, such that item 3 in the license file 22B (FIG. SB) is decremented one unit. The accounting fcr the use of the license 27 only also requires per~orming step 75 instead of steps 50, 52, 54 and 60 as in the license tran~fer embodiment.
Then step 79 is performed to return the status to the computer program 24~ indicating that the computer program 24B is authorized to run, which enables the computer program 24B to run on the CPU 18 at the local node 14.
The flow chart in FIG. 6 can also be expressed in terms of instructions that are used by the license manager 25B to cause the abo~e-described function3 to be performed. Such instructions are set forth in Appendix B.
Release of License 27 When the user finishes use of the copy of the computer program 24A or 24B that was authorized by a license 27, that copy calls its respective license manager 25A or 25B.
If the license manager is number 25A in the license transfer embodimen~, then it is at the local node 14. The license manager 25A modifies the license file 22A at the local node 14 by changing item 2 to not be "in use" (FIG. 2B).
1 3 ~
If the license manager is nutnber 25B in the license pool embodiment, it is a~ the second remote node 20 in the example.
The copy of the computer program 24B calls the license manger 25B and requests a release of the license 27. Via item 4 in the license file 22B for the license pool 28 (FIG. 5B), the i.d. of the second node 20 is known, such that the appropriate license pool 28 is identified. Item 3 in license file 22B
(FIG. 5B) is then incremented by one unit and the "in use" i.d.
for the second remote node is deleted from item 4.
The license manager 25B then returns to the copy of the computer program 24B at the local node 14 which causes the execution of the copy to stop in a known manner, e.g. via an "EXIT" command.
SUMMARY
It may be understood that both embodiments of the present invention avoid the use of a file server on a single node 12 of the network ll. Notwithstanding that, the license files 22A or 22B must be valid, otherwise a licen~e 27 will not be usable to authorize a copy of the computer programs 24A or 24B to be executed, and such copies may be executed on any node 12.
Since license files 22A and 22B can be on any of the nodes 12, even when the lin~ 13 or another node 12 i3 inoperative access can still be made to the license file 22A or 22B on the local node 14 for an available license 27.
While the preferred embodiment has been de~cribed in order to illustrate the fundamental relationships of the present invention, it qhould be understood that numerous variations and modifications may be made to the~e embodiments 1 3 ~ 2 ~
without departing from the teachings and concepts of the pre-sent invention. Accordingly, it should be clearly understood that ~he form of the present invention described above and shown in the accompanying drawings is illustrative only and is not intended to limit the scope of the invention to less than that described in the following claims.
~ ~ 3 ~
APPI :NDIX A
Instructions For License Mana~er Program 25A
IF (license exists on local node AND
license is not in use AND
license is valid AND
license has not lapsed) TH~N
Mark the license in use Tell computer program it can run ELSE
WHILE (not all nodes in network have been searched AND
a license has not been found) D0 IF ( license exists on ne~ct remote node AND
license is not in use AND
expiration date has not lapsed AND
license is valid on next remote node) THEN
Save the license information in memory Create new license file on local node Delete old license file from second remote node IF (old license file deleted) THEN
Mark license file information as being in use Encrypt UID of new license and license inf o rmat i on Write encrypted UID and information into new licen~e file Tell computer program it can run ELSE
delete new license file END IF
END IF
11 3 ~
END WHILE
IF ( license was not found) THEN
Tell computer proE~ram that it cannot run ENI) IF
END IF
. .
_~ ~ 3 ~
APPENDIX B
Instruc~ions For License Manager Program 25B
found = FALSE
IF (license pool exists on local node AND
license pool is valid AND
a license is available in license pool) THEN
found = TRUE
END IF
WHILE (found = FALSE AND
not all nodes searched) D0 IF (license pool is valid AND
a license is available in license pool) THEN
found = TRUE
END IF
END WHILE
IF (found = TRUE) THEN
Decrement number of available licenses in pool Write information related to Computer Pro~ram into license pool Set status to "authorized to run"
ELSE
Set status to "not authorized to run"
END IF
RETURN (status) 3 Foreign.AT5
License Loadin~ Procedure Referring now to FIG. 7A, the aggregate number L of licenses 27 loaded onto the nodes 12 is determined by how many copies of the given computer program 24B the owner of the network 11 has purchased. When either fewer licenses 27 than the aggregate number of nodes 12 (where only one copy of the given computer program 24B can run on one node 12), or when fewer licenses 27 than the total demand for licenses (where more than one copy of the given computer program 24B can run on a node 12) are loaded onto the network 11, the license managers 25B-25B are effectiYe to limit the aggregate number of copies of the given computer program 24B that can run on the network 11 at any gi~en time.
FIG. 7B shows a pool source file 64 that is stored on the media 29 that the owner of the network 11 receives from the vendor. The file 64 includes the i.d. of that node 12 onto which the license file 22B for the license pool 28 is to be loaded, the total number L of licenses that are to be authorized ~or the computer program 24B and the e~piration date of the license pool 28. One of the pool source files 64 may be loaded onto various ones of the nodes 12, and in that case Ll licenses would be in one file 64A and L2 licenses would be in another file 64B, where Ll + L2 = L.
FIG. 7A illustrates the steps utilized to load the licenses 27 onto the node 12 of the network 11 according to the node i.d. in the file 64. Initially~ the pool source file 64 is copied from the installation media 29 onto any node 12, such as on the local node 14. The installation program 17 2~) decrypts the information in the source file 64 for the license pool 28. The installation program 17 creates the license file 22B on the disk 19 of the node 12 corresponding to the node i.d. in the source file 64 (see FIG. 7A, item 2), and the operating system 15 then assigns a UID to ~hat license file 22B. Since there may be many licen~es 27 in that license file 22B, such UID is the UI~ that is common to all cf the licenses 27 in the license pool 28. At this ~uncture, the license pool 28 is not yet authorized. To authorize the license pool 28, the installation program 17 gets the UID of the license file 22B rom the operating system 1~ and the installation program 17 encrypts the UID of the license file 22B and the other license information of the pool source 64 and writes it into the license file 22B on the disk 19 of the node 12, as designated by the node i.d. It is to be understood, then, that the UID is stored with the license pool 28 and with the L
licenses 27 in the license file 22B on the designated node 12 befor~ any request to use the given computer program 24B has or can be made.
As compared to the license transfer embodiment, the license pool embodiment is preferred because the installation of the license source pool 64 can be performed by the owner of the network without contacting the vendor. Also, if one license pool 28 is used, for example, only one loading operation is required. To provide more access to the licen~es 27 should one node 12 be inoperative, however, it i~ preferred that at least two license pools 28-28 be u9ed, and installed on separate nodes 12, one having Ll and the other having L2 licen~es 27 as noted above.
~3~ ~17~
At this ~uncture, ~he network 11 will have been loaded with at least one copy of the given computer program 24B and with the desired aggregate number L of licenses 27 for the given computer program 24B. The network 11 is ready for a user make a request to run a copy of the given computer pro~ram 24B on one of the nodes 12, such as on the local node 14.
Request To_Run Computer Pro~ram 24B On Local Node 14 The method and apparatus of the license pool embodiment of the present invention may be understood by reerring to FIG. 6. There, the functions performed by the license manager . 25B are shown in flow chart form. Initially, it should be under~tood that one license manager 25B (FIG. 5C) is part of each copy of the given computer program 24B that i~ contained in a computer program file 22B in system memory 16. In the preferred embodiment of the present invention in which the Apollo DN3000 computer is used, separate iles 23B for the computer program 24B and the license manager 25B are on the disk 19. When the files 23B are loaded into the system memory 16, they are linked. On the other hand, such linking can also be achieved by having the computer program 24B in the file 23B
on the disk ~9 be linked to the license manager 25B, such that as each copy of the computer program Z4B is written into the system memory 16 at ~ given node 12, the corresponding licen~e manager 25B will also be written into the system memory 16.
Each license manager 25B perform9 the function~ shown in FIG. 6 with respect to it9 re9pective copy of the given computer program 24~. Assume for purposeq of illustration ~ 3 that the customer's network user degires to use a copy of the given computer program 24B at the local node 14. The copy of the given computer program 24B on the local node 14 contact~
the license manager 25B at the local node 14 by making a subroutine call (Step 65). In response, the license manager 25B in effect asks (Step 66) whether a license 28 exists on the local node 14 for the given computer program 24B. This question is answered by first causing a determination to be made as to whether there is a license file 22B (and thus a license pool 28 and a license 27) on the disk 19 at the local node 14. If so, the license manager 25B takes a "yes~' path 67 and in a step 72 determines whether the license pool 28 is "valid". This is done by asking the operating system 15 for the UID for the license pool 28 that the operating system 15 caused to be stored in a record in the system memory 16 at the local node 14. The license manager 25B then decrypts the UID
contained in the license file 22B for the license pool 28 and compares it to the UID for such license pool 28 that was received from the operating system 15. The license is not valid if the UIDs are not the same. In such event, then the license manager 25B takes a "no" path 73 and proceeds to step 70. If the UID~ are the same, the licen~e manager 25B
determines whether the current date is later than the expiration date of the valid license pool 28 (see FIG. 5B).
If so, then the license pool 2~ has expired and the license manager 25B takes path 73 and returns to step 70. If not expired, the licer5e manager 25B then determines whether any of the licenses 27 in the pool 28 are not in use. That i9, such determination made by the step 72 indicate~ whether the `~
~3~ ~2 3 CPUs 18 are at that time "using" all of the licenses 27 by running copies of the computer program 24B on the nodes 12 under the authorization of all such licenses 27. If all licenses 27 are being used, the license manager 25B then takes the "no" path 73 and returns step 70. If one license 27 is not active, the license manager 25B then takes a path 74 indicating that at least one of the licenses 27 is inactive 3 current and valid. The path 74 leads to step 75 that marks such license 27 as being "active" or "in use" (see item 3 in file 22B, FIG.
5B). This is done by modifying the license file 22B, such as by decrementing item 3 in file 22B to reduce the number of licenses 27 that are available in the license pool 28. This prevents that inactive, current, valid license 27 from being assigned to any other node 12. The license manager 25B thPn takes path 76 to step 77 that writes into the license pool 28 in the license file 22B information that the local node is using the license 27 that was just rendered active. The license manager 25B then takes path 78 to step 79 that returns a status to the computer program 24B indicating that it is authori2ed to run, which enables the computer program 24B to run on the CPU 18 at the local node 14.
Request for License 27 -_License at Remote Node 20 As indicated above, with respeot to the local node 14, the question asked in step 66 can be answered in the affirmative or negative and if it is answered "no" it indicates that no license pool 28 and thus no licen~e9 27 are available for the computer program 24B on the local node 14.
In the "no" event, the licen~e manager 25B then takes path 80 2 ~
to step 70. In step 70, the nodes 14 and 20-20 that have been searched are noted. If all node~ 14 and 20-20 ha~e been searched, a "yes" answer is given and a path 81 i3 taken to step 82. If, as in the example, the first remote node 20 has not been searched, an attempt is made to locate the license pool 28 on the first remote node 20, path 83 i9 taken to step 68. Step 68 determines whether a license pool 28 exists on the next node 12 in the network 11 which in this example, i9 the first remote node 20. If the license pool 28 is not on the remote node 20, then the license manager 25B performs another search if all nodes 12 have not been searched for a license pool 28. In this example, since only the local node 14 and the first remote node 20 have been searched, the license manager 25B loops and then again determines whether a license pool 28 exists on the next or second remote node 20 in the network ll.
Assuming the next node 12 is the next remote node counterclockwise around the network 11, and that a license pool 28 exists in the license file 22B on the disk 19 in such remote node 20, then "yes" path 83 is taken to step 68. The license manager 25B then determines (as described above in respect to step 72) whether the licen~e pool 28 in the license file 22B on the second remote node 20 is valid, and if so, performs the rest o~ step 72 to determine whether any license 27 in the valid license pool 28 is available, and if so, whether the expiration date has expired. In either of these events (e.g.
no licen~e 27 available in the valid license pool 28 or license pool 28 is expired), the "no" path 73 is taken to the ~tep 70 and the determination as to whether all nodes 12 have been searched is again made.
1 31 ~25 Use of License 27 on Local Node 14 If the license file 22B on the second remote node 20 has not expired and a license 27 is not in use and the pool 28 is valid, path 74 is taken to step 75. Rather ~han transferring the available, current license 27 from the licen~e pool 28, the license manager 25B on,the local node 14 causes step 75 to be performed in the license pool 28 aL- the second remote node 20, such that item 3 in the license file 22B (FIG. SB) is decremented one unit. The accounting fcr the use of the license 27 only also requires per~orming step 75 instead of steps 50, 52, 54 and 60 as in the license tran~fer embodiment.
Then step 79 is performed to return the status to the computer program 24~ indicating that the computer program 24B is authorized to run, which enables the computer program 24B to run on the CPU 18 at the local node 14.
The flow chart in FIG. 6 can also be expressed in terms of instructions that are used by the license manager 25B to cause the abo~e-described function3 to be performed. Such instructions are set forth in Appendix B.
Release of License 27 When the user finishes use of the copy of the computer program 24A or 24B that was authorized by a license 27, that copy calls its respective license manager 25A or 25B.
If the license manager is number 25A in the license transfer embodimen~, then it is at the local node 14. The license manager 25A modifies the license file 22A at the local node 14 by changing item 2 to not be "in use" (FIG. 2B).
1 3 ~
If the license manager is nutnber 25B in the license pool embodiment, it is a~ the second remote node 20 in the example.
The copy of the computer program 24B calls the license manger 25B and requests a release of the license 27. Via item 4 in the license file 22B for the license pool 28 (FIG. 5B), the i.d. of the second node 20 is known, such that the appropriate license pool 28 is identified. Item 3 in license file 22B
(FIG. 5B) is then incremented by one unit and the "in use" i.d.
for the second remote node is deleted from item 4.
The license manager 25B then returns to the copy of the computer program 24B at the local node 14 which causes the execution of the copy to stop in a known manner, e.g. via an "EXIT" command.
SUMMARY
It may be understood that both embodiments of the present invention avoid the use of a file server on a single node 12 of the network ll. Notwithstanding that, the license files 22A or 22B must be valid, otherwise a licen~e 27 will not be usable to authorize a copy of the computer programs 24A or 24B to be executed, and such copies may be executed on any node 12.
Since license files 22A and 22B can be on any of the nodes 12, even when the lin~ 13 or another node 12 i3 inoperative access can still be made to the license file 22A or 22B on the local node 14 for an available license 27.
While the preferred embodiment has been de~cribed in order to illustrate the fundamental relationships of the present invention, it qhould be understood that numerous variations and modifications may be made to the~e embodiments 1 3 ~ 2 ~
without departing from the teachings and concepts of the pre-sent invention. Accordingly, it should be clearly understood that ~he form of the present invention described above and shown in the accompanying drawings is illustrative only and is not intended to limit the scope of the invention to less than that described in the following claims.
~ ~ 3 ~
APPI :NDIX A
Instructions For License Mana~er Program 25A
IF (license exists on local node AND
license is not in use AND
license is valid AND
license has not lapsed) TH~N
Mark the license in use Tell computer program it can run ELSE
WHILE (not all nodes in network have been searched AND
a license has not been found) D0 IF ( license exists on ne~ct remote node AND
license is not in use AND
expiration date has not lapsed AND
license is valid on next remote node) THEN
Save the license information in memory Create new license file on local node Delete old license file from second remote node IF (old license file deleted) THEN
Mark license file information as being in use Encrypt UID of new license and license inf o rmat i on Write encrypted UID and information into new licen~e file Tell computer program it can run ELSE
delete new license file END IF
END IF
11 3 ~
END WHILE
IF ( license was not found) THEN
Tell computer proE~ram that it cannot run ENI) IF
END IF
. .
_~ ~ 3 ~
APPENDIX B
Instruc~ions For License Manager Program 25B
found = FALSE
IF (license pool exists on local node AND
license pool is valid AND
a license is available in license pool) THEN
found = TRUE
END IF
WHILE (found = FALSE AND
not all nodes searched) D0 IF (license pool is valid AND
a license is available in license pool) THEN
found = TRUE
END IF
END WHILE
IF (found = TRUE) THEN
Decrement number of available licenses in pool Write information related to Computer Pro~ram into license pool Set status to "authorized to run"
ELSE
Set status to "not authorized to run"
END IF
RETURN (status) 3 Foreign.AT5
Claims (64)
1. A license management system for limiting the number of copies of a given computer program that are permitted to run simultaneously on one or more nodes of a network in which said nodes are connected, said limiting being according to the number of licenses for said given computer program that are authorized for said network; said system comprising:
license file means on at least one of said nodes for storing at least one of said licenses;
program storage means for storing a copy of said given computer program on each of said nodes at which it is desired to run a copy of said given computer program; and license management means operatively linked to each said copy, said license management means being responsive to a request from said copy to which it is operatively linked for searching said nodes to locate one of said license file means that has a license that is available for authorizing use at a local one of said nodes at which said requesting copy is stored, said search first being made at said local node and if no such license file means having an available license is located at said local node, said search continuing in seriatim among said nodes other than said local node until one such license file means having an available license is located or until all said nodes have been searched without locating one such license file means having an available license;
said license management means being responsive to the search of all of said nodes without locating one such license file means having an available license for returning to said copy at said local node a message preventing said copy from being run at said local node in response to said request.
license file means on at least one of said nodes for storing at least one of said licenses;
program storage means for storing a copy of said given computer program on each of said nodes at which it is desired to run a copy of said given computer program; and license management means operatively linked to each said copy, said license management means being responsive to a request from said copy to which it is operatively linked for searching said nodes to locate one of said license file means that has a license that is available for authorizing use at a local one of said nodes at which said requesting copy is stored, said search first being made at said local node and if no such license file means having an available license is located at said local node, said search continuing in seriatim among said nodes other than said local node until one such license file means having an available license is located or until all said nodes have been searched without locating one such license file means having an available license;
said license management means being responsive to the search of all of said nodes without locating one such license file means having an available license for returning to said copy at said local node a message preventing said copy from being run at said local node in response to said request.
2. A license management system according to claim 1, further comprising:
means for assigning a unique identification to each of said license file means;
said license management means being effective upon location of any one of said license file means to compare the unique identification of said located license file means to the unique identification assigned to said located license file means by said assigning means to determine whether said located license file means is valid, said license management means being effective in response to a determination that said located license file means is valid for determining whether said license in aid located license file means is being used, said license being not available to authorize use of said copy of said given computer program if either said unique identification of said located license file means is invalid or if said license is being used.
means for assigning a unique identification to each of said license file means;
said license management means being effective upon location of any one of said license file means to compare the unique identification of said located license file means to the unique identification assigned to said located license file means by said assigning means to determine whether said located license file means is valid, said license management means being effective in response to a determination that said located license file means is valid for determining whether said license in aid located license file means is being used, said license being not available to authorize use of said copy of said given computer program if either said unique identification of said located license file means is invalid or if said license is being used.
3. A management system for controlling the operability of computer programs on any of a plurality of workstations coupled together in a network, wherein it is required that a license be available for one of said workstations in order to enable a copy of a given one of said computer programs to run on said one workstation and wherein the number of licenses for said given computer program that is authorized on said network is less than or equal to the number of copies of said given computer program that can run simultaneously on said network, said system comprising:
license file means for storing at least one of said licenses on at least a selected one of said workstations;
system means for assigning to said license file means and storing an identification (UID) that is unique to said license file means; and means responsive to a request to run a copy of said given computer program on said selected workstation for searching said selected workstation to locate said license file means at said selected workstation, said searching means being responsive to locating said license file means for comparing said UID of said license file means to the UID stored by said system means for said license file means and, if said compared UIDs are the same, and if said license in said located license file means is not in use, enabling said copy of said given computer program to run on said selected workstation.
license file means for storing at least one of said licenses on at least a selected one of said workstations;
system means for assigning to said license file means and storing an identification (UID) that is unique to said license file means; and means responsive to a request to run a copy of said given computer program on said selected workstation for searching said selected workstation to locate said license file means at said selected workstation, said searching means being responsive to locating said license file means for comparing said UID of said license file means to the UID stored by said system means for said license file means and, if said compared UIDs are the same, and if said license in said located license file means is not in use, enabling said copy of said given computer program to run on said selected workstation.
4. A computer that is programmed to perform functions selected to control the operability of computer programs on any of a plurality of workstations coupled together in a network, wherein it is required that a license be available when a request is made to execute a copy of a given one of said computer programs on a particular one of said workstations, and wherein an aggregate number of said licenses authorized for said network is less than the number of copies of said given computer program that can be executed simultaneously on said workstations of said network, said selected functions comprising:
storing a license file on at least one of said workstations, said license file including at least one of said licenses, the aggregate number of said licenses that are stored being lass than the number of copies of said given computer program that can be executed simultaneously on said workstations;
assigning to each said stored license file an identification (UID) that is different from the UID of all other ones of said license files;
in response to a request to execute a copy of said given computer program at a particular one of said workstations, searching said particular workstation to determine whether one of said license files is stored on said particular workstation;
in response to locating said license file on said particular workstation, comparing said UID of said located license file to a system record of the UID for said located license file;
in response to said compared UIDs being the same, determining whether one of said licenses in said located license file is available to authorize execution of a copy of said given computer program at said particular workstation; and enabling said computer program to be executed on said particular workstation if said license is available.
storing a license file on at least one of said workstations, said license file including at least one of said licenses, the aggregate number of said licenses that are stored being lass than the number of copies of said given computer program that can be executed simultaneously on said workstations;
assigning to each said stored license file an identification (UID) that is different from the UID of all other ones of said license files;
in response to a request to execute a copy of said given computer program at a particular one of said workstations, searching said particular workstation to determine whether one of said license files is stored on said particular workstation;
in response to locating said license file on said particular workstation, comparing said UID of said located license file to a system record of the UID for said located license file;
in response to said compared UIDs being the same, determining whether one of said licenses in said located license file is available to authorize execution of a copy of said given computer program at said particular workstation; and enabling said computer program to be executed on said particular workstation if said license is available.
5. A license management system for controlling the running, at nodes connected in a network, of copies of a given computer program, wherein a license is required for each copy of said given computer program that is to run simultaneously with other copies of said given computer program, and wherein the number of licenses authorized for said network and said given computer program is less than the number of copies of said given computer program that can run simultaneously on said network, wherein a directory is on a given node for indicating which licenses, if any, are on said given node, and wherein a request can be made to run a copy of said given computer program at a first node when no license is available at said first node but is available at a second node, said system comprising:
license file means provided at each said node for containing at least one of said licenses;
system means for assigning a unique identification to each of said license file means on said nodes and for storing a record of each of said unique identifications;
and first management means operatively linked to a copy of said given computer program at said first node for receiving said request and searching said license file means at said second node to determine that said license file means is at said second node;
said first management means being effective in response to said determination that said license file means is at said second node for comparing said unique identification of said license file means at said second node to said record of said unique identification in said system means to determine that said license file means at said second node is valid, and then to determine that at least one license therein is not in use;
said first management means being effective upon making both of said last-mentioned determinations for returning a status to said copy of said given computer program at said first node indicating that said copy of said given computer program is authorized to run.
license file means provided at each said node for containing at least one of said licenses;
system means for assigning a unique identification to each of said license file means on said nodes and for storing a record of each of said unique identifications;
and first management means operatively linked to a copy of said given computer program at said first node for receiving said request and searching said license file means at said second node to determine that said license file means is at said second node;
said first management means being effective in response to said determination that said license file means is at said second node for comparing said unique identification of said license file means at said second node to said record of said unique identification in said system means to determine that said license file means at said second node is valid, and then to determine that at least one license therein is not in use;
said first management means being effective upon making both of said last-mentioned determinations for returning a status to said copy of said given computer program at said first node indicating that said copy of said given computer program is authorized to run.
6. A management system for controlling the operability of copies of a given computer program on any of a plurality of workstations coupled together in a network, wherein more than one copy of said given computer program can be permitted to run simultaneously on a given one of said workstations, and wherein it is required that a license be available for each copy of said given computer program that is to run, and wherein an aggregate number of licenses for said given computer program that are available for said network is less than an aggregate number of copies of said given computer program that can run simultaneously on the workstations of said network; said management system comprising:
license file means stored on a selected one of said workstations at which it is desired to operate more than one copy of said given computer program, said license file means including at least two of said licenses;
system means for assigning to said license file means and storing therefor a unique identification;
means responsive to a request to run at least two of said computer programs on said selected workstation for searching said selected workstation to locate said license file means; and means responsive to said searching means locating said license file means on said selected workstation for comparing said identification of said located stored license file means to the identification stored by said system means for said respective license file means, and if said respective compared identifications are the same and two of the licenses in said license file means are not in use, enabling both of said corresponding copies of said given computer program to run on said selected workstation.
license file means stored on a selected one of said workstations at which it is desired to operate more than one copy of said given computer program, said license file means including at least two of said licenses;
system means for assigning to said license file means and storing therefor a unique identification;
means responsive to a request to run at least two of said computer programs on said selected workstation for searching said selected workstation to locate said license file means; and means responsive to said searching means locating said license file means on said selected workstation for comparing said identification of said located stored license file means to the identification stored by said system means for said respective license file means, and if said respective compared identifications are the same and two of the licenses in said license file means are not in use, enabling both of said corresponding copies of said given computer program to run on said selected workstation.
7. A method of controlling the operability of copies of a computer program on any of a plurality of workstations coupled together in a network, wherein it is required that a license be available for each copy of said computer program that is to be executed, and wherein the number of licenses for said computer program that are authorized for said network is limited, said method comprising the steps of:
storing at least one of said licenses in a license file on at least a selected one of said workstations;
assigning to each stored license file an identification (UID) that is different from the UID of all other ones of said license files;
searching said selected workstation in response to a request for execution of a copy of said computer program at said selected workstation to determine whether one of said license files is on said selected workstation;
upon locating said license file on said selected workstation, comparing said UID of said located stored license file to a record of said assigned UID for said located license file; and if said compared UIDs are the same, and if said license in said license file is available, then enabling said copy of said computer program to be executed at said selected workstation.
storing at least one of said licenses in a license file on at least a selected one of said workstations;
assigning to each stored license file an identification (UID) that is different from the UID of all other ones of said license files;
searching said selected workstation in response to a request for execution of a copy of said computer program at said selected workstation to determine whether one of said license files is on said selected workstation;
upon locating said license file on said selected workstation, comparing said UID of said located stored license file to a record of said assigned UID for said located license file; and if said compared UIDs are the same, and if said license in said license file is available, then enabling said copy of said computer program to be executed at said selected workstation.
8. A method of managing licenses to limit the number (S) of copies of a given computer program that may be executed simultaneously on the nodes of a network to less than or equal to the number (L) of licenses that are authorized for said network and said given computer program, each of said nodes having a system memory, license memory means for storing up to L ones of said licenses and a directory for identifying said licenses stored in said license memory means, said method comprising the steps of:
loading a copy of said given computer program onto each of said nodes on which it is desired to execute a copy of said given computer program, each said copy of said given computer program being current with respect to time when its term of authorized use has not expired;
loading an aggregate of L licenses into said license memory means on said nodes of said network such that a maximum of L copies of said given computer program can be executed simultaneously on said network;
assigning to each said license memory means an identification that is unique to said license memory means at each said node at the time of such loading;
in response to a request for the execution of a copy of said given computer program at a first of said nodes, searching said directory at said first node for license memory means thereon, and upon determining that no license memory means is at said first node or that all licenses in said license memory means located at said first node are active or that the unique identification of said license memory means located at said first node is invalid, then sequentially searching said directories at other ones of said nodes for said license memory means; and upon locating license memory means that is at another node and that has a valid unique identification and that has an inactive, current license therein, returning a run message to said copy of said given program at said first node to enable said copy of said computer program to be executed on said first node.
loading a copy of said given computer program onto each of said nodes on which it is desired to execute a copy of said given computer program, each said copy of said given computer program being current with respect to time when its term of authorized use has not expired;
loading an aggregate of L licenses into said license memory means on said nodes of said network such that a maximum of L copies of said given computer program can be executed simultaneously on said network;
assigning to each said license memory means an identification that is unique to said license memory means at each said node at the time of such loading;
in response to a request for the execution of a copy of said given computer program at a first of said nodes, searching said directory at said first node for license memory means thereon, and upon determining that no license memory means is at said first node or that all licenses in said license memory means located at said first node are active or that the unique identification of said license memory means located at said first node is invalid, then sequentially searching said directories at other ones of said nodes for said license memory means; and upon locating license memory means that is at another node and that has a valid unique identification and that has an inactive, current license therein, returning a run message to said copy of said given program at said first node to enable said copy of said computer program to be executed on said first node.
9. A means for storing a copy of said given computer program on each of said nodes at which it is desired to run a copy of said given computer program; and license management means operatively linked to each said copy, said license management means being responsive to a request from said copy to which it is operatively linked for searching said nodes to locate one of said licenses that is available for use at a local one of said nodes at which said requesting copy is stored, said search first being made at said local node and if no available license is located at said local node, said search continuing in seriatim among said nodes other than said local node until an available license is located or until all said nodes have been searched without locating an available license; said license management means being responsive to the search of all said nodes without locating an available license for returning to said copy at said local node a message preventing said copy from being run at said local node in response to said request.
10. A management system for controlling the operability of computer programs on any of a plurality of workstations coupled together in a network, wherein it is required that a license be available at one of said workstations in order to enable a copy of one of said computer programs to run on said one workstation and wherein the number of licenses for a given computer program that is authorized to run on said network is less than the number of copies of said given computer program that can run simultaneously on said network, said system comprising:
means for storing one of said licenses on at least a selected one of said workstations, the number of said workstations on which said licenses are stored being less than the number of copies of said given computer program that can run simultaneously on said workstations;
system means for assigning to each said stored license and storing an identification (UID) that is different from the UID of all other ones of said license ;
means responsive to a request to run a copy of said given computer program on said selected workstation for searching said selected workstation to determine whether one of said licenses is available to authorize a copy of said given computer program to run on said selected workstation; and means responsive to locating said available license for comparing said UID of said located available stored license to the UID stored by said system means fox said located available license and, if said compared UIDS are the same, enabling said copy of said computer program to run at said selected workstation.
means for storing one of said licenses on at least a selected one of said workstations, the number of said workstations on which said licenses are stored being less than the number of copies of said given computer program that can run simultaneously on said workstations;
system means for assigning to each said stored license and storing an identification (UID) that is different from the UID of all other ones of said license ;
means responsive to a request to run a copy of said given computer program on said selected workstation for searching said selected workstation to determine whether one of said licenses is available to authorize a copy of said given computer program to run on said selected workstation; and means responsive to locating said available license for comparing said UID of said located available stored license to the UID stored by said system means fox said located available license and, if said compared UIDS are the same, enabling said copy of said computer program to run at said selected workstation.
11. A computer that is programmed to perform functions selected to control the operability of computer programs on any of a plurality of workstations coupled together in a network, wherein it is required that a license be available at one of said workstations in order to enable a copy of a given one of said computer programs to run on said one workstation, and wherein the number of said licenses authorized for said network is less than the number of copies of said given computer program that can run simultaneously on said network, said selected functions comprising:
storing one of said licenses on at least a selected one of said workstations, the number of said workstations on which one of said licenses is stored being less than the number of copies of said given computer program than can run simultaneously on said workstations;
assigning to each said stored license an identification (UID) that is different from the UID of all other ones of said stored licenses;
in response to a request to run a copy of said given computer program at said selected workstation, searching said selected workstation to determine whether one of said licenses is stored and available on said selected workstation;
in response to locating said available license stored on said selected workstation, comparing said UID of said located stored license to a system record of the UID for said located stored license; and in response to said compared UIDs being the same, enabling said copy of said given computer program to run on said selected workstation.
storing one of said licenses on at least a selected one of said workstations, the number of said workstations on which one of said licenses is stored being less than the number of copies of said given computer program than can run simultaneously on said workstations;
assigning to each said stored license an identification (UID) that is different from the UID of all other ones of said stored licenses;
in response to a request to run a copy of said given computer program at said selected workstation, searching said selected workstation to determine whether one of said licenses is stored and available on said selected workstation;
in response to locating said available license stored on said selected workstation, comparing said UID of said located stored license to a system record of the UID for said located stored license; and in response to said compared UIDs being the same, enabling said copy of said given computer program to run on said selected workstation.
12. A license management system for controlling the availability for operation, at nodes connected in a network, of copies of a given computer program on said nodes, wherein a license is required on each said node at which a copy of said given computer program is to run, and wherein the number of licenses authorized for said network and said given computer program is less than or equal to the number of copies of said given computer program that can run simultaneously on said network, wherein a license file is provided at each said node for indicating that one of said licenses is on said node, wherein a directory is on each of said nodes for indicating which licenses, if any, are on a given node, and wherein a request can be made to run a copy of said given computer program at a first node when no license is available at said first node but is available at a second node, said network including system means for assigning a unique identification to each license on said nodes, said system means being effective to store a record of said unique identifications, said system comprising:
first management means linked to said copy of said given computer program at said first node for receiving said request and searching said license file at said second node to determine whether or not said license is available on said second node;
said first management means being effective in response to said determination that said license is available on said second node for transferring said available license from said second node to said first node if said available license is valid at said second node and has not expired; and said first management means being effective for requesting said system means to assign a unique identification to said available license transferred to said first node.
first management means linked to said copy of said given computer program at said first node for receiving said request and searching said license file at said second node to determine whether or not said license is available on said second node;
said first management means being effective in response to said determination that said license is available on said second node for transferring said available license from said second node to said first node if said available license is valid at said second node and has not expired; and said first management means being effective for requesting said system means to assign a unique identification to said available license transferred to said first node.
13. A management system for controlling the oper-ability of copies of a given computer program on any of a plurality of workstations coupled together in a network, wherein more than one copy of said given computer program can be permitted to run simultaneously on a given one of said workstations, and wherein it is required that a license be available for each copy of said given computer program that is to run, and wherein the aggregate number of licenses for said given computer program that are available for said network is less than the aggregate number of copies of said given computer program that can run simultaneously on the workstations of said network; said management system comprising:
means for storing at least two of said licenses on a selected one of said workstations at which it is desired to operate more than one copy of said given computer program;
system means for assigning to each said stored license and storing therefor an identification that is different from the identification of all other ones of said licenses stored on said network;
means responsive to a request to run at least two copies of said given computer program on said selected workstation for searching said selected workstation to determine whether one or more of said licenses is available on said selected workstation; and means responsive to said searching means locating at least one of said licenses on said selected workstation for comparing said identification of each said respective located stored license to the identification stored by said system means for said respective located stored license, and if said respective compared identifications are the same and the corresponding license is available on said selected workstation, enabling an amount of said copies of said given computer program equal to the number of available compared licenses located on said selected workstation to run on said selected workstation.
means for storing at least two of said licenses on a selected one of said workstations at which it is desired to operate more than one copy of said given computer program;
system means for assigning to each said stored license and storing therefor an identification that is different from the identification of all other ones of said licenses stored on said network;
means responsive to a request to run at least two copies of said given computer program on said selected workstation for searching said selected workstation to determine whether one or more of said licenses is available on said selected workstation; and means responsive to said searching means locating at least one of said licenses on said selected workstation for comparing said identification of each said respective located stored license to the identification stored by said system means for said respective located stored license, and if said respective compared identifications are the same and the corresponding license is available on said selected workstation, enabling an amount of said copies of said given computer program equal to the number of available compared licenses located on said selected workstation to run on said selected workstation.
14. A license management system for limiting the number (S) of copies of a given computer program that may be executed simultaneously on the nodes of a network to less than or equal to the number (L) of licenses that are authorized on said network for said given computer program, each of said nodes having a system memory, license memory means for indicating characteristics of said licenses and a directory for identifying said licenses stored in said license memory means, said license management system comprising:
means for loading a copy of said given computer program onto each of said nodes on which it is desired to execute said given computer program, each said copy of said given computer program being current with respect to time when its term of authorized use has not expired;
means for loading L licenses into said license memory means on said nodes of said network such that no more than L copies of said given computer program can be executed simultaneously on said network, said loading means assign-ing to each said license an identification that is unique to said license at said node at the time of such assignment;
license management means for identifying an inactive one of said licenses at a selected one of said nodes at which it is desired to execute a copy of said given computer program, said license being inactive when said copy of said given computer program at said one of said nodes is not being executed, said license management means including for each said node a separate license manager corresponding to said copy of said given computer program at said node such that at a first of said nodes there is a first license manager and a first copy of said given computer program and at a second of said nodes there is a second license manager and a second copy of said given computer program;
said first copy of said given computer program being adapted to request from said first license manager the execution of said first copy of said given computer program at said first node;
said first license manager being responsive to said request for searching said directory at said first node for one of said licenses, and upon determining that none of said licenses is inactive at said first node said first license manager searching said directories at said second node for a license;
in response to locating an inactive current license at said second node, said license manager transferring said located inactive current license to said system memory at said first node, and upon said transfer said first license manager causing a unique identification to be assigned to said license transferred to said first node;
means effective upon transfer of said transferred license to said system memory for erasing said transferred license from said license memory means at said second node;
said first license manager writing said unique identification and said license into said license memory means at said first node; and said first license manager comparing said unique identification in said license memory means to said unique identification in said system memory and in the event of a match, said first license manager then returning a message for enabling said first copy of said given computer program to be executed on said first node.
means for loading a copy of said given computer program onto each of said nodes on which it is desired to execute said given computer program, each said copy of said given computer program being current with respect to time when its term of authorized use has not expired;
means for loading L licenses into said license memory means on said nodes of said network such that no more than L copies of said given computer program can be executed simultaneously on said network, said loading means assign-ing to each said license an identification that is unique to said license at said node at the time of such assignment;
license management means for identifying an inactive one of said licenses at a selected one of said nodes at which it is desired to execute a copy of said given computer program, said license being inactive when said copy of said given computer program at said one of said nodes is not being executed, said license management means including for each said node a separate license manager corresponding to said copy of said given computer program at said node such that at a first of said nodes there is a first license manager and a first copy of said given computer program and at a second of said nodes there is a second license manager and a second copy of said given computer program;
said first copy of said given computer program being adapted to request from said first license manager the execution of said first copy of said given computer program at said first node;
said first license manager being responsive to said request for searching said directory at said first node for one of said licenses, and upon determining that none of said licenses is inactive at said first node said first license manager searching said directories at said second node for a license;
in response to locating an inactive current license at said second node, said license manager transferring said located inactive current license to said system memory at said first node, and upon said transfer said first license manager causing a unique identification to be assigned to said license transferred to said first node;
means effective upon transfer of said transferred license to said system memory for erasing said transferred license from said license memory means at said second node;
said first license manager writing said unique identification and said license into said license memory means at said first node; and said first license manager comparing said unique identification in said license memory means to said unique identification in said system memory and in the event of a match, said first license manager then returning a message for enabling said first copy of said given computer program to be executed on said first node.
15. A method of controlling the operability of copies of a computer program on any of a plurality of workstations coupled together in a network, wherein it is required that a license be available at each said workstation at which one or more copies of said computer program are to be executed, and wherein the number of licenses for said computer program that are authorized for said network is limited, said method comprising the steps of:
storing one of said licenses on at least a selected one of said workstations;
assigning to each said stored license an identification (UID) that is different from the UID of all other ones of said licenses;
searching said selected workstation in response to a request for execution of a copy of said computer program at said selected workstation to determine whether one of said stored licenses is available for use at said selected workstation;
upon locating said available stored license at said selected workstation, comparing said UID of said located available stored license to a record of said assigned UID
for said located, available and stored license and if said compared UIDs are the same, enabling said copy of said computer program to be executed at said selected workstation.
storing one of said licenses on at least a selected one of said workstations;
assigning to each said stored license an identification (UID) that is different from the UID of all other ones of said licenses;
searching said selected workstation in response to a request for execution of a copy of said computer program at said selected workstation to determine whether one of said stored licenses is available for use at said selected workstation;
upon locating said available stored license at said selected workstation, comparing said UID of said located available stored license to a record of said assigned UID
for said located, available and stored license and if said compared UIDs are the same, enabling said copy of said computer program to be executed at said selected workstation.
16. A method of managing licenses to limit the number (S) of copies of a given computer program that may be executed simultaneously on the nodes of a network to less than or equal to the number (L) of licenses that are authorized for said network and said given computer program, each of said nodes having a system memory, license memory means for indicating characteristics of said licenses and a directory for identifying said licenses stored in said license memory means, said method comprising the steps of:
loading a copy of said given computer program into said license memory means on each of said nodes on which it is desired to execute a copy of said given computer program, each said copy of said given computer program being current with respect to time when its term of authorized execution has not expired;
loading L licenses into said license memory means on said nodes of said network such that a maximum of L copies of said given computer program can be executed simultaneously on said network;
assigning to each said loaded license an identifica-tion that is unique to said license at a particular one of said nodes at the time of such loading;
identifying an inactive one of said licenses at a selected one of said nodes at which it is desired to execute a copy of said given computer program, said license being inactive when said copy of said given computer program at said selected one of said nodes is not being executed;
in response to a request for the execution of a copy of said given computer program at a first of said nodes, searching said directory at said first node for a license, and upon determining that no license is at said first node or that all licenses are active at said first node, sequentially searching said directories at ones of said nodes other than at said first node for an inactive, current license;
transferring to said first node an inactive current license located at another one of said nodes;
assigning a unique identification to said license transferred to said first node;
erasing the unique identification of said transferred license from said other node; and returning a run message to enable said copy of said given computer program to be executed on said first node.
loading a copy of said given computer program into said license memory means on each of said nodes on which it is desired to execute a copy of said given computer program, each said copy of said given computer program being current with respect to time when its term of authorized execution has not expired;
loading L licenses into said license memory means on said nodes of said network such that a maximum of L copies of said given computer program can be executed simultaneously on said network;
assigning to each said loaded license an identifica-tion that is unique to said license at a particular one of said nodes at the time of such loading;
identifying an inactive one of said licenses at a selected one of said nodes at which it is desired to execute a copy of said given computer program, said license being inactive when said copy of said given computer program at said selected one of said nodes is not being executed;
in response to a request for the execution of a copy of said given computer program at a first of said nodes, searching said directory at said first node for a license, and upon determining that no license is at said first node or that all licenses are active at said first node, sequentially searching said directories at ones of said nodes other than at said first node for an inactive, current license;
transferring to said first node an inactive current license located at another one of said nodes;
assigning a unique identification to said license transferred to said first node;
erasing the unique identification of said transferred license from said other node; and returning a run message to enable said copy of said given computer program to be executed on said first node.
17. A management system according to claim 10, further comprising:
said storing means also stores one of said licenses on one of said workstations other than said selected workstation;
means responsive to said searching means not locating an available one of said licenses at said selected workstation but locating of one of said licenses at said workstation other than said selected workstation for determining that said license at said other workstation is available at said other workstation, said determining means being effective to transfer said available license from said other workstation to said selected workstation; and means responsive to said transfer of said license to said selected workstation for causing said system means to assign a new and different UID to said license transferred to said selected workstation, said new and different UID
assigned to said transferred license being different from the UID assigned thereto prior to said transfer of said transferred license to said selected workstation and being different from the UID of all other ones of said licenses.
said storing means also stores one of said licenses on one of said workstations other than said selected workstation;
means responsive to said searching means not locating an available one of said licenses at said selected workstation but locating of one of said licenses at said workstation other than said selected workstation for determining that said license at said other workstation is available at said other workstation, said determining means being effective to transfer said available license from said other workstation to said selected workstation; and means responsive to said transfer of said license to said selected workstation for causing said system means to assign a new and different UID to said license transferred to said selected workstation, said new and different UID
assigned to said transferred license being different from the UID assigned thereto prior to said transfer of said transferred license to said selected workstation and being different from the UID of all other ones of said licenses.
18. A management system according to claim 17 wherein:
said comparing means is responsive to said assignment of said new and different UID to said license transferred to said selected workstation for comparing said new and different UID to the UID stored by said system means for said transferred license, said comparing means enabling said copy of said given computer program to be executed on said selected workstation in the event that said compared UIDs are the same.
said comparing means is responsive to said assignment of said new and different UID to said license transferred to said selected workstation for comparing said new and different UID to the UID stored by said system means for said transferred license, said comparing means enabling said copy of said given computer program to be executed on said selected workstation in the event that said compared UIDs are the same.
19. A management system according to claim 10, wherein:
said comparing means also determines whether said available license at said selected workstation is current, and if current and if said compared UID's are the same, said comparing means enables said copy of said given computer program at said selected workstation to be executed.
said comparing means also determines whether said available license at said selected workstation is current, and if current and if said compared UID's are the same, said comparing means enables said copy of said given computer program at said selected workstation to be executed.
20. A management system according to Claim 10, wherein:
said storing means includes means for encrypting said UID; and said comparing means decrypts said UID before performing said comparison.
said storing means includes means for encrypting said UID; and said comparing means decrypts said UID before performing said comparison.
21. A management system according to claim 10, wherein:
said storing means also stores data indicating whether said license is valid and is being run.
said storing means also stores data indicating whether said license is valid and is being run.
22. A management system according to claim 17, further comprising:
means for encrypting said UID of said license transferred to said selected workstation; and means for erasing said transferred license from said other workstation so that said transferred license may run only at said selected workstation.
means for encrypting said UID of said license transferred to said selected workstation; and means for erasing said transferred license from said other workstation so that said transferred license may run only at said selected workstation.
23. A management system according to claim 22, in which:
said transferred license is originally in a license file at said other workstation;
said determining means includes means for copying said license file onto said selected workstation; and said erasing means is effective in response to said operation of said copying means.
said transferred license is originally in a license file at said other workstation;
said determining means includes means for copying said license file onto said selected workstation; and said erasing means is effective in response to said operation of said copying means.
24. The computer defined in claim 11, said selected functions further comprising:
in response to not locating one of said available licenses on said selected workstation, searching said workstations other than said selected workstation to determine whether one of said licenses is stored on said other workstation;
in response to locating one of said available licenses at said other workstation, determining that said license at said other workstation is current and valid;
transferring said available, current and valid license from said other workstation to said selected workstation;
and in response to said transfer of said available, current and valid license to said selected workstation, causing a new and different UID to be assigned to said available, current and valid license transferred to said selected workstation.
in response to not locating one of said available licenses on said selected workstation, searching said workstations other than said selected workstation to determine whether one of said licenses is stored on said other workstation;
in response to locating one of said available licenses at said other workstation, determining that said license at said other workstation is current and valid;
transferring said available, current and valid license from said other workstation to said selected workstation;
and in response to said transfer of said available, current and valid license to said selected workstation, causing a new and different UID to be assigned to said available, current and valid license transferred to said selected workstation.
25. The computer defined in claim 24, said selected functions further comprising:
storing said last-mentioned UID assigned to said transferred license;
deleting said UID that was assigned to said transferred license when said transferred license was stored at said other workstation; and enabling said copy of said given computer program to be run on said selected workstation once said deleting has occurred.
storing said last-mentioned UID assigned to said transferred license;
deleting said UID that was assigned to said transferred license when said transferred license was stored at said other workstation; and enabling said copy of said given computer program to be run on said selected workstation once said deleting has occurred.
26. The computer defined in claim 11, wherein said selected functions further comprising:
encrypting said UIDs;
storing said encrypted UIDs; and decrypting said stored UIDs before performing said comparison.
encrypting said UIDs;
storing said encrypted UIDs; and decrypting said stored UIDs before performing said comparison.
27. The computer defined in claim 11, said selected functions further comprising:
in response to not locating an available license on said selected workstation, searching other of said workstations for an available license; and in response to not locating an available license on any of said other workstations, preventing said requested copy of said given computer program from being enabled to run on said selected workstation.
in response to not locating an available license on said selected workstation, searching other of said workstations for an available license; and in response to not locating an available license on any of said other workstations, preventing said requested copy of said given computer program from being enabled to run on said selected workstation.
28. The computer defined in claim 11, wherein a directory is provided at a workstation other than said selected workstation and said storing function also stores at least one of said licenses on said other workstation;
said selected functions further comprising:
updating said directory to record said storage of one of said licenses at said other workstation;
in response to said request and the determining that no license is available at said selected workstation, searching said directory to locate one of said licenses therein;
determining that said license located in said directory is available;
performing said comparing function to determine whether said available license in said directory is valid;
and if said available license in said directory is valid, transferring said available valid license to said selected workstation.
said selected functions further comprising:
updating said directory to record said storage of one of said licenses at said other workstation;
in response to said request and the determining that no license is available at said selected workstation, searching said directory to locate one of said licenses therein;
determining that said license located in said directory is available;
performing said comparing function to determine whether said available license in said directory is valid;
and if said available license in said directory is valid, transferring said available valid license to said selected workstation.
29. A system according to claim 12, which further comprises:
said first management means including means for determining the validity of said unique identification of said license on said second node, said first management means comparing said unique identification of said license on said second node to the record of said unique iden-tification stored in said system means for said license on said second node.
said first management means including means for determining the validity of said unique identification of said license on said second node, said first management means comparing said unique identification of said license on said second node to the record of said unique iden-tification stored in said system means for said license on said second node.
30. A system according to claim 29, wherein:
said determining means prevents said transfer operation of said first management means unless said validity has been confirmed and said compared unique identifications are found to be the same.
said determining means prevents said transfer operation of said first management means unless said validity has been confirmed and said compared unique identifications are found to be the same.
31. A system according to claim 12, said first management means further comprising the following to determine said validity:
means for encrypting and decrypting said unique identification assigned to said available license at said second node;
means responsive to said decrypted assigned unique identification for said available license at said second node for receiving from said system means said record of said unique identification corresponding to said license on said second node;
means for comparing said unique identification of said license at said second node to said record thereof from said system means; and means responsive to a match of said two last-mentioned unique identifications for rendering said available license at said second node transferable to said first node.
means for encrypting and decrypting said unique identification assigned to said available license at said second node;
means responsive to said decrypted assigned unique identification for said available license at said second node for receiving from said system means said record of said unique identification corresponding to said license on said second node;
means for comparing said unique identification of said license at said second node to said record thereof from said system means; and means responsive to a match of said two last-mentioned unique identifications for rendering said available license at said second node transferable to said first node.
32. A system according to claim 12 in which a request can be made to execute a copy of said given computer program at said second node when said transferred license is still on said first node, said system further comprising:
second management means linked to a copy of said given computer program at said second node for receiving said request for execution at said second node and searching said directory at said second node to determine that said license is not on said second node, said second management means searching said directory on said first node to determine that said license is on said first node;
in response to said latter determination, said second management means transferring said license from said first node to said second node if said license is valid and not in use at said first node and has not expired; and upon completion of said transfer said second management means requesting said system means to assign a unique identification to said license transferred to said second node.
second management means linked to a copy of said given computer program at said second node for receiving said request for execution at said second node and searching said directory at said second node to determine that said license is not on said second node, said second management means searching said directory on said first node to determine that said license is on said first node;
in response to said latter determination, said second management means transferring said license from said first node to said second node if said license is valid and not in use at said first node and has not expired; and upon completion of said transfer said second management means requesting said system means to assign a unique identification to said license transferred to said second node.
33. A license management system according to claim 14, wherein:
in response to a request to execute a copy of said given computer program made when L copies of said given computer program are already being executed, each of said first and second license managers preventing the execution of any other copies of said given computer program until one of said L licenses becomes inactive.
in response to a request to execute a copy of said given computer program made when L copies of said given computer program are already being executed, each of said first and second license managers preventing the execution of any other copies of said given computer program until one of said L licenses becomes inactive.
34. A license management system according to claim 33, wherein:
said first license manager means encrypts said unique identification assigned to said transferred license and causes said encrypted unique identification to be stored in said license memory means at said first node.
said first license manager means encrypts said unique identification assigned to said transferred license and causes said encrypted unique identification to be stored in said license memory means at said first node.
35. The method according to claim 15, wherein said storing step also stores at least one of said licenses on an other one of said workstations, further comprising the steps of:
upon failing to locate an available license at said selected workstation, continuing said search at said another workstation of said network;
upon locating one of said licenses at one of said workstations other than said selected workstation, deter-mining that said license on said other workstation is available for use at said other workstation and then performing said comparing step;
transferring said available license from said other workstation to said selected workstation; and upon transferring said available license to said selected workstation, causing a new and different UID to be assigned to said license at said selected workstation.
upon failing to locate an available license at said selected workstation, continuing said search at said another workstation of said network;
upon locating one of said licenses at one of said workstations other than said selected workstation, deter-mining that said license on said other workstation is available for use at said other workstation and then performing said comparing step;
transferring said available license from said other workstation to said selected workstation; and upon transferring said available license to said selected workstation, causing a new and different UID to be assigned to said license at said selected workstation.
36. A method according to claim 35, wherein: said comparing step is performed upon said assignment of said new and different UID to said license transferred to said selected workstation, said comparing being of said new and different UID to the record of said new and different UID
for said transferred license, further comprising the steps of:
enabling said copy of said computer program to be ex-ecuted at said selected workstation in the event that said last-mentioned compared UIDs are the same.
for said transferred license, further comprising the steps of:
enabling said copy of said computer program to be ex-ecuted at said selected workstation in the event that said last-mentioned compared UIDs are the same.
37. The method according to claim 15, further comprising the steps of:
encrypting said UID assigned to a stored license; and decrypting said UID before performing said comparison step.
encrypting said UID assigned to a stored license; and decrypting said UID before performing said comparison step.
38. The method according to claim 15, further comprising the steps of:
storing data with said located license to indicate whether or not said located license is valid and is in use, and said comparing step is performed in response to said data indicating that said located license is available for use at said selected workstation.
storing data with said located license to indicate whether or not said located license is valid and is in use, and said comparing step is performed in response to said data indicating that said located license is available for use at said selected workstation.
39. The method according to claim 16, further comprising the step of:
encrypting said UID of said license transferred to said first node;
said erasing from said other node of the UID of said transferred license being performed so that said transferred license may be executed only at said first node.
encrypting said UID of said license transferred to said first node;
said erasing from said other node of the UID of said transferred license being performed so that said transferred license may be executed only at said first node.
40. The license management method according to claim 16, further comprising the steps of:
encrypting the unique identification assigned to each said license; and decrypting the unique identification of said license at another one of said nodes so that said license can be identified as a current, inactive license prior to transfer thereof to said first node.
encrypting the unique identification assigned to each said license; and decrypting the unique identification of said license at another one of said nodes so that said license can be identified as a current, inactive license prior to transfer thereof to said first node.
41. A license management system according to claim 5, wherein:
if said license is not available on said second node, said first management means searches said nodes in addition to said first and second nodes until an available one of said licenses is located or all of said nodes of said network have been searched without locating an available license; and in response to said search of all said nodes without locating an available license, said first management means returns a message to said copy of said given computer program at said first node to prevent said copy of said given computer program from running on said first node so that the number of copies of said given computer program running simultaneously on said network is limited to the number authorized.
if said license is not available on said second node, said first management means searches said nodes in addition to said first and second nodes until an available one of said licenses is located or all of said nodes of said network have been searched without locating an available license; and in response to said search of all said nodes without locating an available license, said first management means returns a message to said copy of said given computer program at said first node to prevent said copy of said given computer program from running on said first node so that the number of copies of said given computer program running simultaneously on said network is limited to the number authorized.
42. A license management system according to claim 2, wherein:
said license file means includes a license pool capable of storing up to the authorized number of licenses;
and said license management means being effective, in response to determining that said located license file means is valid and that a license in said located license file means is available, for decrementing the number of available licenses in said located file means.
said license file means includes a license pool capable of storing up to the authorized number of licenses;
and said license management means being effective, in response to determining that said located license file means is valid and that a license in said located license file means is available, for decrementing the number of available licenses in said located file means.
43. A license management system according to claim 42, wherein:
said license management means also writes data into said license pool to indicate the nodes at which a copy of said given computer program is being run under one of said licenses.
said license management means also writes data into said license pool to indicate the nodes at which a copy of said given computer program is being run under one of said licenses.
44. A license management system according to claim 2, wherein:
said license management means includes means for encrypting said unique identification assigned to said license file means and for decrypting said unique identifications prior to comparing said unique identifications.
said license management means includes means for encrypting said unique identification assigned to said license file means and for decrypting said unique identifications prior to comparing said unique identifications.
45. A management system according to claim 3, wherein:
said license file means includes a license pool capable of storing up to the authorized number of license;
and said license management means being effective, in response to determining that said located license file means is valid and that a license in said located license file means is available, for decrementing the number of available licenses in said located file means.
said license file means includes a license pool capable of storing up to the authorized number of license;
and said license management means being effective, in response to determining that said located license file means is valid and that a license in said located license file means is available, for decrementing the number of available licenses in said located file means.
46. A management system according to claim 45, wherein:
said license management means also writes data into said license pool to indicate the nodes at which a copy of said given computer program is being run under one of said licenses.
said license management means also writes data into said license pool to indicate the nodes at which a copy of said given computer program is being run under one of said licenses.
47. A computer according to claim 4, wherein a plurality of licenses are in said license file, and wherein said computer is programmed to perform the following additional function:
in response to determining that one of said licenses is so available, modifying said license file so that it indicates that one fewer license is available for authorizing execution of a copy of said given computer program.
in response to determining that one of said licenses is so available, modifying said license file so that it indicates that one fewer license is available for authorizing execution of a copy of said given computer program.
48. A computer according to Claim 47, that is programmed to perform the following additional function:
further modifying said license file so that it indicates said particular workstation at which said copy of said given computer program is being executed under authorization of said formerly available license.
further modifying said license file so that it indicates said particular workstation at which said copy of said given computer program is being executed under authorization of said formerly available license.
49. A license management system according to claim 5, wherein:
each said license file means at said nodes contains more than one of said licenses;
said first management means searches said license file means at said second node only when said license file means at said first node is invalid or all said licenses at said first node are in use; and said first management means being effective to modify said license file means at said second node before returning said status so that said license file means at said second node indicates that one more license is in use.
each said license file means at said nodes contains more than one of said licenses;
said first management means searches said license file means at said second node only when said license file means at said first node is invalid or all said licenses at said first node are in use; and said first management means being effective to modify said license file means at said second node before returning said status so that said license file means at said second node indicates that one more license is in use.
50. A method of controlling the operability of copies of a computer program according to claim 7, wherein said storing step stores the total number of authorized licenses in said license file on said selected workstation, said method further comprises the step of:
each time a copy of said computer program is enabled to be executed, said license file is updated to decrease the number of available licenses therein.
each time a copy of said computer program is enabled to be executed, said license file is updated to decrease the number of available licenses therein.
51. A method of controlling the operability of copies of a computer program according to Claim 50, wherein:
each time said license file is updated data is entered therein indicating the copy of said computer program that is authorized to be executed and the workstation on which it is authorized.
each time said license file is updated data is entered therein indicating the copy of said computer program that is authorized to be executed and the workstation on which it is authorized.
52. A method according to claim 8, wherein said loading step loads said L licenses only onto said license memory means at said first node, and said method comprising the further step of:
upon determining that no available licenses for said copy of said given computer program are at any of said nodes, returning a status to said copy of said given computer program at said first node indicating that said copy is not authorized to be executed.
upon determining that no available licenses for said copy of said given computer program are at any of said nodes, returning a status to said copy of said given computer program at said first node indicating that said copy is not authorized to be executed.
53. A license management system for limiting the number of copies of a given computer program that are permitted to run simultaneously on one or more nodes of a network in which said nodes are connected, said limiting being according to the number of licenses for said given computer program that are authorized for said network; said system comprising:
license file means on at least one of said nodes for storing at least one and up to a selectable authorized number of said licenses;
program storage means for storing a copy of said given computer program on at least one of said nodes without limiting the running of said given computer program to running on said one node; and license management means responsive to a request to run, said request being from one of said copies at a particular one of said nodes, for searching as many of said nodes as are necessary to locate one of said license file means that has a license that is available for authorizing a copy of said given computer program to run at said particular one of said nodes;
said license management means being responsive to said search not locating any of said license file means having an available license for returning to said requesting copy a message preventing said copy from running in response to said request.
license file means on at least one of said nodes for storing at least one and up to a selectable authorized number of said licenses;
program storage means for storing a copy of said given computer program on at least one of said nodes without limiting the running of said given computer program to running on said one node; and license management means responsive to a request to run, said request being from one of said copies at a particular one of said nodes, for searching as many of said nodes as are necessary to locate one of said license file means that has a license that is available for authorizing a copy of said given computer program to run at said particular one of said nodes;
said license management means being responsive to said search not locating any of said license file means having an available license for returning to said requesting copy a message preventing said copy from running in response to said request.
54. A license management system according to claim 53, wherein:
said license file means includes a license pool capable of storing up to the authorized number of licenses;
and said license management means, in response to locating one of said license file means having a license that is available, decrements the number of available licenses in said located file means.
said license file means includes a license pool capable of storing up to the authorized number of licenses;
and said license management means, in response to locating one of said license file means having a license that is available, decrements the number of available licenses in said located file means.
55. A license management system according to claim 54, wherein:
said license management means also writes data into said located license file means to indicate the node at which said copy of said given computer program is being run under said license.
said license management means also writes data into said located license file means to indicate the node at which said copy of said given computer program is being run under said license.
56. A license management system according to claim 53, further comprising:
means for assigning a unique identification to each of said license file means;
said license management means being effective upon location of any one of said license file means to compare the unique identification of said located license file means to the unique identification assigned to said located license file means by said assigning means to determine whether said license file means is valid, said license management means being effective in response to a determination that said located license file means is valid for determining whether any of said licenses in said located license file is available for authorizing a copy of said given program to run, said licenses being not available to authorize running of said copy of said given computer program if either said unique identification of said license file means is invalid or if all of said licenses are being used.
means for assigning a unique identification to each of said license file means;
said license management means being effective upon location of any one of said license file means to compare the unique identification of said located license file means to the unique identification assigned to said located license file means by said assigning means to determine whether said license file means is valid, said license management means being effective in response to a determination that said located license file means is valid for determining whether any of said licenses in said located license file is available for authorizing a copy of said given program to run, said licenses being not available to authorize running of said copy of said given computer program if either said unique identification of said license file means is invalid or if all of said licenses are being used.
57. A license management system according to claim 53, further comprising:
said license file means includes a license file on each of at least two of said nodes, said license files including a license pool for storing said licenses, the aggregate number of licenses stored in all of said license pools equalling said selectable authorized number of said licenses, the number of said licenses in said pools that are available being variable according to the number of licenses in current usage; and said license management means, in response to locating one of said license pools having an available license, reduces the number of available licenses in said located license pool.
said license file means includes a license file on each of at least two of said nodes, said license files including a license pool for storing said licenses, the aggregate number of licenses stored in all of said license pools equalling said selectable authorized number of said licenses, the number of said licenses in said pools that are available being variable according to the number of licenses in current usage; and said license management means, in response to locating one of said license pools having an available license, reduces the number of available licenses in said located license pool.
58. A management system for controlling the operability of computer programs accessed from any of a plurality of nodes coupled together in a network, wherein it is required that a license be available in order to enable said node to operate using a copy of a given one of said computer programs and wherein the number of licenses for said given computer program that is authorized to operate on said network is limited 90 that the number of copies of said given computer program that can operate simultaneously on said network is limited, said system comprising:
license file means for storing at least one of said licenses on at least one of said nodes;
system means for assigning to said license file means and storing an identification (UID) that is unique to said license file means; and means responsive to a request from any of said nodes for operation of a copy of said given computer program for searching to locate said license file means at any of said nodes, said searching means being responsive to locating said license file means at said one node for comparing said UID of said license file means to the UID stored by said system means for said license file means and, if said compared UIDs are the same, and if a license in said located license file means is not in use, enabling said selected node to operate using said copy of said given computer program.
license file means for storing at least one of said licenses on at least one of said nodes;
system means for assigning to said license file means and storing an identification (UID) that is unique to said license file means; and means responsive to a request from any of said nodes for operation of a copy of said given computer program for searching to locate said license file means at any of said nodes, said searching means being responsive to locating said license file means at said one node for comparing said UID of said license file means to the UID stored by said system means for said license file means and, if said compared UIDs are the same, and if a license in said located license file means is not in use, enabling said selected node to operate using said copy of said given computer program.
59. A management system according to claim 58, wherein:
said license file means includes a license pool capable of storing up to the authorized number of licenses;
and said license management means being effective, in response to determining that said located license file means is valid and that a license in said located license file means is available, for decrementing the number of available licenses in said located file means.
said license file means includes a license pool capable of storing up to the authorized number of licenses;
and said license management means being effective, in response to determining that said located license file means is valid and that a license in said located license file means is available, for decrementing the number of available licenses in said located file means.
60. A management system according to claim 59 wherein:
said license management means also writes data into said license pool to indicate the one of said nodes at which a copy of said given computer program is being used under one of said licenses.
said license management means also writes data into said license pool to indicate the one of said nodes at which a copy of said given computer program is being used under one of said licenses.
61. A license management system for controlling the availability for use of copies of a given computer program, said copies being used in response to requests for use from nodes connected in a network, wherein a license is required for each copy of said given computer program that is to be used simultaneously with other copies of said given computer program, and wherein the number of licenses authorized for said network and said given computer program is limited, wherein a directory is on each of said nodes for indicating which licenses are on particular ones of said nodes, and wherein said requests can be made to use a copy of said given computer program when no license is available at the node that requests such use but is available at a second node, said system comprising:
at least one license file means for containing at least one of said licenses;
system means for assigning a unique identification to each of said license file means and for storing a record of each of said unique identifications; and first management means for receiving said request and searching to determine that said license file means is at said second node;
said first management means being effective in response to said determination for comparing said UID of said license file means at said second node to said record of said UID in said system means to determine that said license file means at said second node is valid, and then to determine that at least one license therein is available for use;
said first management means being effective upon making all of said determinations for returning a status to said requesting node indicating that said copy of said given computer program is authorized to be used.
at least one license file means for containing at least one of said licenses;
system means for assigning a unique identification to each of said license file means and for storing a record of each of said unique identifications; and first management means for receiving said request and searching to determine that said license file means is at said second node;
said first management means being effective in response to said determination for comparing said UID of said license file means at said second node to said record of said UID in said system means to determine that said license file means at said second node is valid, and then to determine that at least one license therein is available for use;
said first management means being effective upon making all of said determinations for returning a status to said requesting node indicating that said copy of said given computer program is authorized to be used.
62. A license management system according to claim 61, wherein:
each said license file means contains more than one of said licenses;
said first management means searches said license file means at said second node only when a license file means at said requesting node is invalid or all said licenses at said first node are in use; and said first management means being effective to modify said license file means at said second node before returning said status so that one more license is recorded in said license file means as being in use at said second node.
each said license file means contains more than one of said licenses;
said first management means searches said license file means at said second node only when a license file means at said requesting node is invalid or all said licenses at said first node are in use; and said first management means being effective to modify said license file means at said second node before returning said status so that one more license is recorded in said license file means as being in use at said second node.
63. a plurality of license storage keys;
a plurality of computers each in association with one of said license storage keys;
means for transferring a license from one of said keys to another of said keys; and means for preventing a program from running on a computer if the key associated with that computer does not contain an available license for that program.
a plurality of computers each in association with one of said license storage keys;
means for transferring a license from one of said keys to another of said keys; and means for preventing a program from running on a computer if the key associated with that computer does not contain an available license for that program.
64. The computer network of claim 63 wherein communications between a license storage key and a computer are encrypted.
Applications Claiming Priority (2)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| US07/118,909 US5390297A (en) | 1987-11-10 | 1987-11-10 | System for controlling the number of concurrent copies of a program in a network based on the number of available licenses |
| US118,909 | 1987-11-10 |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CA1310425C true CA1310425C (en) | 1992-11-17 |
Family
ID=22381483
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CA000580262A Expired - Lifetime CA1310425C (en) | 1987-11-10 | 1988-10-14 | License management methods and systems |
Country Status (8)
| Country | Link |
|---|---|
| US (1) | US5390297A (en) |
| EP (1) | EP0355132A4 (en) |
| JP (1) | JPH02501171A (en) |
| KR (1) | KR890702131A (en) |
| CN (1) | CN1035192A (en) |
| AU (1) | AU2782289A (en) |
| CA (1) | CA1310425C (en) |
| WO (1) | WO1989004520A1 (en) |
Families Citing this family (328)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| DE69228039T2 (en) * | 1991-05-08 | 1999-08-05 | Digital Equipment Corp | LICENSE MANAGEMENT SYSTEM |
| WO1993011480A1 (en) * | 1991-11-27 | 1993-06-10 | Intergraph Corporation | System and method for network license administration |
| NZ255971A (en) * | 1992-09-21 | 1997-05-26 | Uniloc Singapore Private Ltd | Software registration and licensing system uses matching of licensee indentification codes |
| GB9303595D0 (en) * | 1993-02-23 | 1993-04-07 | Int Computers Ltd | Licence management mechanism for a computer system |
| JP3243331B2 (en) * | 1993-05-14 | 2002-01-07 | 富士通株式会社 | Method for creating layered medium for software management, apparatus for creating layered medium for software management, and layered medium for software management |
| JP3553993B2 (en) * | 1993-08-30 | 2004-08-11 | キヤノン株式会社 | Program use contract management method and program execution device |
| US7080051B1 (en) | 1993-11-04 | 2006-07-18 | Crawford Christopher M | Internet download systems and methods providing software to internet computer users for local execution |
| US5771354A (en) | 1993-11-04 | 1998-06-23 | Crawford; Christopher M. | Internet online backup system provides remote storage for customers using IDs and passwords which were interactively established when signing up for backup services |
| US5809237A (en) * | 1993-11-24 | 1998-09-15 | Intel Corporation | Registration of computer-based conferencing system |
| US5699518A (en) * | 1993-11-29 | 1997-12-16 | Microsoft Corporation | System for selectively setting a server node, evaluating to determine server node for executing server code, and downloading server code prior to executing if necessary |
| JPH07230380A (en) * | 1994-02-15 | 1995-08-29 | Internatl Business Mach Corp <Ibm> | Method and system for controlling utilization of application program |
| JPH07271865A (en) | 1994-04-01 | 1995-10-20 | Mitsubishi Corp | Method for managing copyright of data base |
| US7036019B1 (en) | 1994-04-01 | 2006-04-25 | Intarsia Software Llc | Method for controlling database copyrights |
| US5553139A (en) * | 1994-04-04 | 1996-09-03 | Novell, Inc. | Method and apparatus for electronic license distribution |
| JPH07311752A (en) * | 1994-05-11 | 1995-11-28 | Internatl Business Mach Corp <Ibm> | Decentralized data processing system and initial program loading method |
| US5701463A (en) * | 1994-09-09 | 1997-12-23 | Cheyenne Advanced Technology Limited | Method of replacing the identity of a file with another as part of a file open request in a computer system |
| US7302415B1 (en) | 1994-09-30 | 2007-11-27 | Intarsia Llc | Data copyright management system |
| US5579479A (en) * | 1994-10-03 | 1996-11-26 | Plum Hall Inc. | Computer software licensing authentication method and apparatus |
| JPH08123681A (en) * | 1994-10-26 | 1996-05-17 | Canon Inc | Management system and terminal device |
| EP0715241B1 (en) | 1994-10-27 | 2004-01-14 | Mitsubishi Corporation | Apparatus for data copyright management system |
| US6424715B1 (en) | 1994-10-27 | 2002-07-23 | Mitsubishi Corporation | Digital content management system and apparatus |
| US5845065A (en) * | 1994-11-15 | 1998-12-01 | Wrq, Inc. | Network license compliance apparatus and method |
| JPH08263438A (en) | 1994-11-23 | 1996-10-11 | Xerox Corp | Distribution and use control system of digital work and access control method to digital work |
| US6963859B2 (en) * | 1994-11-23 | 2005-11-08 | Contentguard Holdings, Inc. | Content rendering repository |
| DE9420092U1 (en) * | 1994-12-15 | 1995-02-02 | Marx Datentechnik Gmbh | Software protection module |
| US7133845B1 (en) * | 1995-02-13 | 2006-11-07 | Intertrust Technologies Corp. | System and methods for secure transaction management and electronic rights protection |
| EP1643340B1 (en) * | 1995-02-13 | 2013-08-14 | Intertrust Technologies Corp. | Secure transaction management |
| US7143290B1 (en) * | 1995-02-13 | 2006-11-28 | Intertrust Technologies Corporation | Trusted and secure techniques, systems and methods for item delivery and execution |
| US5892900A (en) * | 1996-08-30 | 1999-04-06 | Intertrust Technologies Corp. | Systems and methods for secure transaction management and electronic rights protection |
| US6948070B1 (en) | 1995-02-13 | 2005-09-20 | Intertrust Technologies Corporation | Systems and methods for secure transaction management and electronic rights protection |
| US6157721A (en) * | 1996-08-12 | 2000-12-05 | Intertrust Technologies Corp. | Systems and methods using cryptography to protect secure computing environments |
| US5943422A (en) | 1996-08-12 | 1999-08-24 | Intertrust Technologies Corp. | Steganographic techniques for securely delivering electronic digital rights management control information over insecure communication channels |
| US7133846B1 (en) | 1995-02-13 | 2006-11-07 | Intertrust Technologies Corp. | Digital certificate support system, methods and techniques for secure electronic commerce transaction and rights management |
| US7124302B2 (en) * | 1995-02-13 | 2006-10-17 | Intertrust Technologies Corp. | Systems and methods for secure transaction management and electronic rights protection |
| US20060206397A1 (en) * | 1995-02-13 | 2006-09-14 | Intertrust Technologies Corp. | Cryptographic methods, apparatus and systems for storage media electronic right management in closed and connected appliances |
| US7095854B1 (en) * | 1995-02-13 | 2006-08-22 | Intertrust Technologies Corp. | Systems and methods for secure transaction management and electronic rights protection |
| US6658568B1 (en) * | 1995-02-13 | 2003-12-02 | Intertrust Technologies Corporation | Trusted infrastructure support system, methods and techniques for secure electronic commerce transaction and rights management |
| US6134549A (en) * | 1995-03-31 | 2000-10-17 | Showcase Corporation | Client/server computer system having personalizable and securable views of database data |
| US5696898A (en) * | 1995-06-06 | 1997-12-09 | Lucent Technologies Inc. | System and method for database access control |
| US5592549A (en) * | 1995-06-15 | 1997-01-07 | Infosafe Systems, Inc. | Method and apparatus for retrieving selected information from a secure information source |
| US5758068A (en) * | 1995-09-19 | 1998-05-26 | International Business Machines Corporation | Method and apparatus for software license management |
| US8595502B2 (en) | 1995-09-29 | 2013-11-26 | Intarsia Software Llc | Data management system |
| US5764770A (en) * | 1995-11-07 | 1998-06-09 | Trimble Navigation Limited | Image authentication patterning |
| US6282362B1 (en) | 1995-11-07 | 2001-08-28 | Trimble Navigation Limited | Geographical position/image digital recording and display system |
| US5799082A (en) * | 1995-11-07 | 1998-08-25 | Trimble Navigation Limited | Secure authentication of images |
| US5752041A (en) * | 1995-12-15 | 1998-05-12 | International Business Machines Corporation | Method and system for licensing program management within a distributed data processing system |
| US20010011253A1 (en) * | 1998-08-04 | 2001-08-02 | Christopher D. Coley | Automated system for management of licensed software |
| US20060265336A1 (en) * | 1996-02-26 | 2006-11-23 | Graphon Corporation | Automated system for management of licensed digital assets |
| US5758069A (en) * | 1996-03-15 | 1998-05-26 | Novell, Inc. | Electronic licensing system |
| US5905860A (en) * | 1996-03-15 | 1999-05-18 | Novell, Inc. | Fault tolerant electronic licensing system |
| DE19612999C2 (en) * | 1996-03-22 | 1999-04-01 | Wasy Ges Fuer Wasserwirtschaft | System for protecting protected software against unauthorized use in computer networks |
| US5864620A (en) * | 1996-04-24 | 1999-01-26 | Cybersource Corporation | Method and system for controlling distribution of software in a multitiered distribution chain |
| US5742757A (en) * | 1996-05-30 | 1998-04-21 | Mitsubishi Semiconductor America, Inc. | Automatic software license manager |
| US7555458B1 (en) | 1996-06-05 | 2009-06-30 | Fraud Control System.Com Corporation | Method of billing a purchase made over a computer network |
| US20030195846A1 (en) * | 1996-06-05 | 2003-10-16 | David Felger | Method of billing a purchase made over a computer network |
| US8229844B2 (en) | 1996-06-05 | 2012-07-24 | Fraud Control Systems.Com Corporation | Method of billing a purchase made over a computer network |
| US5796941A (en) * | 1996-09-06 | 1998-08-18 | Catalyst Semiconductor, Inc. | Method for supervising software execution in a license restricted environment |
| US5754763A (en) * | 1996-10-01 | 1998-05-19 | International Business Machines Corporation | Software auditing mechanism for a distributed computer enterprise environment |
| US6272523B1 (en) | 1996-12-20 | 2001-08-07 | International Business Machines Corporation | Distributed networking using logical processes |
| US6058423A (en) * | 1996-12-23 | 2000-05-02 | International Business Machines Corporation | System and method for locating resources in a distributed network |
| US6029145A (en) * | 1997-01-06 | 2000-02-22 | Isogon Corporation | Software license verification process and apparatus |
| US20050021477A1 (en) * | 1997-01-29 | 2005-01-27 | Ganapathy Krishnan | Method and system for securely incorporating electronic information into an online purchasing application |
| US6073124A (en) * | 1997-01-29 | 2000-06-06 | Shopnow.Com Inc. | Method and system for securely incorporating electronic information into an online purchasing application |
| JP3924342B2 (en) * | 1997-02-14 | 2007-06-06 | 富士通株式会社 | Software license management system and software license management apparatus |
| US6233684B1 (en) * | 1997-02-28 | 2001-05-15 | Contenaguard Holdings, Inc. | System for controlling the distribution and use of rendered digital works through watermaking |
| US5923842A (en) * | 1997-03-06 | 1999-07-13 | Citrix Systems, Inc. | Method and apparatus for simultaneously providing anonymous user login for multiple users |
| US5905889A (en) * | 1997-03-20 | 1999-05-18 | International Business Machines Corporation | Resource management system using next available integer from an integer pool and returning the integer thereto as the next available integer upon completion of use |
| US5995625A (en) * | 1997-03-24 | 1999-11-30 | Certco, Llc | Electronic cryptographic packing |
| US6021438A (en) * | 1997-06-18 | 2000-02-01 | Wyatt River Software, Inc. | License management system using daemons and aliasing |
| US6012033A (en) * | 1997-06-30 | 2000-01-04 | Vlsi Technology, Inc. | Proprietary information protection method |
| US6233600B1 (en) | 1997-07-15 | 2001-05-15 | Eroom Technology, Inc. | Method and system for providing a networked collaborative work environment |
| US7013294B1 (en) * | 1997-07-15 | 2006-03-14 | Shinko Electric Industries Co., Ltd. | License management system |
| US6314408B1 (en) | 1997-07-15 | 2001-11-06 | Eroom Technology, Inc. | Method and apparatus for controlling access to a product |
| US6230185B1 (en) | 1997-07-15 | 2001-05-08 | Eroom Technology, Inc. | Method and apparatus for facilitating communication between collaborators in a networked environment |
| US7092914B1 (en) * | 1997-11-06 | 2006-08-15 | Intertrust Technologies Corporation | Methods for matching, selecting, narrowcasting, and/or classifying based on rights management and/or other information |
| US6151707A (en) * | 1997-11-20 | 2000-11-21 | Remedy Corporation | System and method for product registration |
| US5978916A (en) * | 1997-11-25 | 1999-11-02 | International Business Machines Corporation | Method, system and computer program product for updating region-dependent software using a common update module for multiple regions |
| US6334189B1 (en) | 1997-12-05 | 2001-12-25 | Jamama, Llc | Use of pseudocode to protect software from unauthorized use |
| US6643775B1 (en) | 1997-12-05 | 2003-11-04 | Jamama, Llc | Use of code obfuscation to inhibit generation of non-use-restricted versions of copy protected software applications |
| US6480959B1 (en) | 1997-12-05 | 2002-11-12 | Jamama, Llc | Software system and associated methods for controlling the use of computer programs |
| US6324649B1 (en) | 1998-03-02 | 2001-11-27 | Compaq Computer Corporation | Modified license key entry for pre-installation of software |
| US7171662B1 (en) * | 1998-03-18 | 2007-01-30 | Microsoft Corporation | System and method for software licensing |
| US6009401A (en) * | 1998-04-06 | 1999-12-28 | Preview Systems, Inc. | Relicensing of electronically purchased software |
| US6282653B1 (en) * | 1998-05-15 | 2001-08-28 | International Business Machines Corporation | Royalty collection method and system for use of copyrighted digital materials on the internet |
| IL124571A0 (en) | 1998-05-21 | 1998-12-06 | Miki Mullor | Method of restricting software operation within a licensed limitation |
| US20040117631A1 (en) * | 1998-06-04 | 2004-06-17 | Z4 Technologies, Inc. | Method for digital rights management including user/publisher connectivity interface |
| US20040117644A1 (en) * | 1998-06-04 | 2004-06-17 | Z4 Technologies, Inc. | Method for reducing unauthorized use of software/digital content including self-activating/self-authenticating software/digital content |
| US20040117664A1 (en) * | 1998-06-04 | 2004-06-17 | Z4 Technologies, Inc. | Apparatus for establishing a connectivity platform for digital rights management |
| US20040107368A1 (en) * | 1998-06-04 | 2004-06-03 | Z4 Technologies, Inc. | Method for digital rights management including self activating/self authentication software |
| US20040117663A1 (en) * | 1998-06-04 | 2004-06-17 | Z4 Technologies, Inc. | Method for authentication of digital content used or accessed with secondary devices to reduce unauthorized use or distribution |
| US20040225894A1 (en) * | 1998-06-04 | 2004-11-11 | Z4 Technologies, Inc. | Hardware based method for digital rights management including self activating/self authentication software |
| US20040117628A1 (en) * | 1998-06-04 | 2004-06-17 | Z4 Technologies, Inc. | Computer readable storage medium for enhancing license compliance of software/digital content including self-activating/self-authenticating software/digital content |
| US6324546B1 (en) * | 1998-10-12 | 2001-11-27 | Microsoft Corporation | Automatic logging of application program launches |
| US6751670B1 (en) * | 1998-11-24 | 2004-06-15 | Drm Technologies, L.L.C. | Tracking electronic component |
| US6272469B1 (en) | 1998-11-25 | 2001-08-07 | Ge Medical Systems Global Technology Company, Llc | Imaging system protocol handling method and apparatus |
| US20030195974A1 (en) * | 1998-12-04 | 2003-10-16 | Ronning Joel A. | Apparatus and method for scheduling of search for updates or downloads of a file |
| US7058597B1 (en) | 1998-12-04 | 2006-06-06 | Digital River, Inc. | Apparatus and method for adaptive fraud screening for electronic commerce transactions |
| US7617124B1 (en) * | 1998-12-04 | 2009-11-10 | Digital River, Inc. | Apparatus and method for secure downloading of files |
| US7127515B2 (en) | 1999-01-15 | 2006-10-24 | Drm Technologies, Llc | Delivering electronic content |
| DE19906432C1 (en) * | 1999-02-16 | 2000-06-21 | Fraunhofer Ges Forschung | Second data stream generation method from first stream including start and functional audiovisual, data blocks, involves insertion of origination information |
| US7257554B1 (en) | 1999-03-19 | 2007-08-14 | Hewlett-Packard Development Company, L.P. | Anonymous purchases while allowing verifiable identities for refunds returned along the paths taken to make the purchases |
| US7134145B1 (en) | 1999-04-30 | 2006-11-07 | Koninklijke Philips Electronics N.V. | Registering copy protected material in a check-out, check-in system |
| US6959291B1 (en) * | 1999-05-19 | 2005-10-25 | International Business Machines Corporation | Management of a concurrent use license in a logically-partitioned computer |
| US6453305B1 (en) * | 1999-05-21 | 2002-09-17 | Compaq Computer Corporation | Method and system for enforcing licenses on an open network |
| US7171567B1 (en) * | 1999-08-02 | 2007-01-30 | Harris Interactive, Inc. | System for protecting information over the internet |
| EP1076279A1 (en) * | 1999-08-13 | 2001-02-14 | Hewlett-Packard Company | Computer platforms and their methods of operation |
| US7716348B1 (en) | 1999-09-03 | 2010-05-11 | Safenet, Inc. | License management system and method with license balancing |
| US7035918B1 (en) | 1999-09-03 | 2006-04-25 | Safenet Canada. Inc. | License management system and method with multiple license servers |
| US6842896B1 (en) | 1999-09-03 | 2005-01-11 | Rainbow Technologies, Inc. | System and method for selecting a server in a multiple server license management system |
| US6968384B1 (en) | 1999-09-03 | 2005-11-22 | Safenet, Inc. | License management system and method for commuter licensing |
| GB9922665D0 (en) | 1999-09-25 | 1999-11-24 | Hewlett Packard Co | A method of enforcing trusted functionality in a full function platform |
| US20060195400A1 (en) * | 2000-10-13 | 2006-08-31 | Patrick Patterson | Controlling access to electronic content |
| JP2001236081A (en) * | 1999-11-12 | 2001-08-31 | Sony Corp | Information processor, information processing method and program storage medium |
| US6868405B1 (en) | 1999-11-29 | 2005-03-15 | Microsoft Corporation | Copy detection for digitally-formatted works |
| US7032240B1 (en) | 1999-12-07 | 2006-04-18 | Pace Anti-Piracy, Inc. | Portable authorization device for authorizing use of protected information and associated method |
| EP1156478A4 (en) * | 1999-12-17 | 2004-12-15 | Sony Corp | Method and apparatus for information processing, and medium for storing program |
| US8117644B2 (en) * | 2000-01-07 | 2012-02-14 | Pennar Software Corporation | Method and system for online document collaboration |
| JP2001273122A (en) * | 2000-03-23 | 2001-10-05 | Hitachi Ltd | Method and device for installing program of parallel computing system |
| JP4306921B2 (en) * | 2000-03-30 | 2009-08-05 | パナソニック株式会社 | Content distribution server and community site server |
| US6859792B1 (en) | 2000-04-20 | 2005-02-22 | Altair Engineering, Inc. | Product suite licensing method |
| DE10023820B4 (en) * | 2000-05-15 | 2006-10-19 | Siemens Ag | Software protection mechanism |
| US7024696B1 (en) | 2000-06-14 | 2006-04-04 | Reuben Bahar | Method and system for prevention of piracy of a given software application via a communications network |
| US7020773B1 (en) | 2000-07-17 | 2006-03-28 | Citrix Systems, Inc. | Strong mutual authentication of devices |
| JP2002049435A (en) * | 2000-08-03 | 2002-02-15 | Naretsuji Moderingu Kenkyusho:Kk | Method and device for managing license |
| US7051211B1 (en) | 2000-08-21 | 2006-05-23 | International Business Machines Corporation | Secure software distribution and installation |
| US20030196109A1 (en) * | 2000-08-28 | 2003-10-16 | Contentguard Holdings, Inc. | Method and apparatus for content transaction aggregation |
| US7743259B2 (en) * | 2000-08-28 | 2010-06-22 | Contentguard Holdings, Inc. | System and method for digital rights management using a standard rendering engine |
| US6931545B1 (en) * | 2000-08-28 | 2005-08-16 | Contentguard Holdings, Inc. | Systems and methods for integrity certification and verification of content consumption environments |
| AU2001292692A1 (en) * | 2000-09-15 | 2002-03-26 | Wonderware Corporation | A method and system for administering a concurrent user licensing agreement on amanufacturing/process control information portal server |
| US7096469B1 (en) | 2000-10-02 | 2006-08-22 | International Business Machines Corporation | Method and apparatus for enforcing capacity limitations in a logically partitioned system |
| US6986040B1 (en) | 2000-11-03 | 2006-01-10 | Citrix Systems, Inc. | System and method of exploiting the security of a secure communication channel to secure a non-secure communication channel |
| US7343324B2 (en) | 2000-11-03 | 2008-03-11 | Contentguard Holdings Inc. | Method, system, and computer readable medium for automatically publishing content |
| US6912294B2 (en) | 2000-12-29 | 2005-06-28 | Contentguard Holdings, Inc. | Multi-stage watermarking process and system |
| US7774279B2 (en) * | 2001-05-31 | 2010-08-10 | Contentguard Holdings, Inc. | Rights offering and granting |
| US6754642B2 (en) * | 2001-05-31 | 2004-06-22 | Contentguard Holdings, Inc. | Method and apparatus for dynamically assigning usage rights to digital works |
| US8069116B2 (en) | 2001-01-17 | 2011-11-29 | Contentguard Holdings, Inc. | System and method for supplying and managing usage rights associated with an item repository |
| US7028009B2 (en) | 2001-01-17 | 2006-04-11 | Contentguardiholdings, Inc. | Method and apparatus for distributing enforceable property rights |
| EP1243998B1 (en) * | 2001-03-21 | 2017-04-19 | Excalibur IP, LLC | A technique for license management and online software license enforcement |
| US7512986B2 (en) | 2001-03-28 | 2009-03-31 | Nds Limited | Digital rights management system and method |
| JP3820581B2 (en) * | 2001-04-04 | 2006-09-13 | ソニー株式会社 | Information processing apparatus and method, recording medium, program, and recording apparatus |
| JP2004537095A (en) * | 2001-04-24 | 2004-12-09 | ヒューレット・パッカード・カンパニー | Information security system |
| US7424747B2 (en) * | 2001-04-24 | 2008-09-09 | Microsoft Corporation | Method and system for detecting pirated content |
| US6954860B1 (en) * | 2001-05-01 | 2005-10-11 | Apple Computer, Inc. | Network copy protection for database programs |
| US7672972B1 (en) * | 2001-05-15 | 2010-03-02 | Altair Engineering, Inc. | Digital content licensing method involving application service provider |
| US8073780B2 (en) * | 2001-05-15 | 2011-12-06 | Altair Engineering, Inc. | Token based club digital content licensing method |
| US9633182B2 (en) * | 2001-05-15 | 2017-04-25 | Altair Engineering, Inc. | Token based digital content licensing method |
| US20100228679A1 (en) * | 2001-05-15 | 2010-09-09 | Altair Engineering, Inc. | Hardware Unit-Based License Management Method |
| US8275716B2 (en) * | 2001-05-31 | 2012-09-25 | Contentguard Holdings, Inc. | Method and system for subscription digital rights management |
| US6876984B2 (en) | 2001-05-31 | 2005-04-05 | Contentguard Holdings, Inc. | Method and apparatus for establishing usage rights for digital content to be created in the future |
| US8275709B2 (en) | 2001-05-31 | 2012-09-25 | Contentguard Holdings, Inc. | Digital rights management of content when content is a future live event |
| US20030009424A1 (en) * | 2001-05-31 | 2003-01-09 | Contentguard Holdings, Inc. | Method for managing access and use of resources by verifying conditions and conditions for use therewith |
| US6895503B2 (en) * | 2001-05-31 | 2005-05-17 | Contentguard Holdings, Inc. | Method and apparatus for hierarchical assignment of rights to documents and documents having such rights |
| US8001053B2 (en) * | 2001-05-31 | 2011-08-16 | Contentguard Holdings, Inc. | System and method for rights offering and granting using shared state variables |
| US7725401B2 (en) * | 2001-05-31 | 2010-05-25 | Contentguard Holdings, Inc. | Method and apparatus for establishing usage rights for digital content to be created in the future |
| US8099364B2 (en) | 2001-05-31 | 2012-01-17 | Contentguard Holdings, Inc. | Digital rights management of content when content is a future live event |
| CN1539115A (en) * | 2001-06-07 | 2004-10-20 | ��̹�е¿عɹɷ�����˾ | Method and apparatus for managing transfer of rights |
| WO2002101490A2 (en) * | 2001-06-07 | 2002-12-19 | Contentguard Holdings, Inc. | Cryptographic trust zones in digital rights management |
| US7774280B2 (en) * | 2001-06-07 | 2010-08-10 | Contentguard Holdings, Inc. | System and method for managing transfer of rights using shared state variables |
| US7100200B2 (en) * | 2001-06-13 | 2006-08-29 | Citrix Systems, Inc. | Method and apparatus for transmitting authentication credentials of a user across communication sessions |
| US20050198379A1 (en) * | 2001-06-13 | 2005-09-08 | Citrix Systems, Inc. | Automatically reconnecting a client across reliable and persistent communication sessions |
| US7562146B2 (en) * | 2003-10-10 | 2009-07-14 | Citrix Systems, Inc. | Encapsulating protocol for session persistence and reliability |
| US7343297B2 (en) * | 2001-06-15 | 2008-03-11 | Microsoft Corporation | System and related methods for managing and enforcing software licenses |
| WO2002103499A2 (en) * | 2001-06-15 | 2002-12-27 | Versada Networks, Inc. | System and method for specifying security, privacy, and access control to information used by others |
| US7203966B2 (en) * | 2001-06-27 | 2007-04-10 | Microsoft Corporation | Enforcement architecture and method for digital rights management system for roaming a license to a plurality of user devices |
| CN100419616C (en) * | 2001-07-17 | 2008-09-17 | 松下电器产业株式会社 | Content usage device and network system, and license information acquisition method |
| US20030028592A1 (en) * | 2001-08-03 | 2003-02-06 | Masahiro Ooho | Backup-restoration system and right management server |
| JP2003099142A (en) * | 2001-09-26 | 2003-04-04 | Mitsubishi Electric Corp | System for managing license of software |
| JP2003122537A (en) * | 2001-10-15 | 2003-04-25 | Minolta Co Ltd | License management device and management system |
| US20030083892A1 (en) * | 2001-11-01 | 2003-05-01 | Arun Ramachandran | Process for one-stop shopping of all available license deals available using a usage based licensing server data structure |
| US20030083995A1 (en) * | 2001-11-01 | 2003-05-01 | Arun Ramachandran | Process for usage based suite licensing of resources from one or more vendors |
| US20030083999A1 (en) * | 2001-11-01 | 2003-05-01 | Arun Ramachandran | Temporal processing of usage data in a usage based licensing |
| US20030084343A1 (en) * | 2001-11-01 | 2003-05-01 | Arun Ramachandran | One protocol web access to usage data in a data structure of a usage based licensing server |
| US20030083994A1 (en) * | 2001-11-01 | 2003-05-01 | Arun Ramachandran | Process to build and use usage based licensing server data structure for usage based licensing |
| US20030084000A1 (en) * | 2001-11-01 | 2003-05-01 | Arun Ramachandran | Server data structure for modelling distribution system |
| US7840488B2 (en) * | 2001-11-20 | 2010-11-23 | Contentguard Holdings, Inc. | System and method for granting access to an item or permission to use an item based on configurable conditions |
| AU2002350209A1 (en) * | 2001-11-20 | 2003-06-10 | Contentguard Holdings, Inc. | An extensible rights expression processing system |
| US7974923B2 (en) * | 2001-11-20 | 2011-07-05 | Contentguard Holdings, Inc. | Extensible rights expression processing system |
| US6679885B2 (en) * | 2001-11-29 | 2004-01-20 | Bioplate, Inc. | Bone alignment and fixation device and installation method, using multiple clip section attachment structure |
| US7984157B2 (en) * | 2002-02-26 | 2011-07-19 | Citrix Systems, Inc. | Persistent and reliable session securely traversing network components using an encapsulating protocol |
| US7661129B2 (en) * | 2002-02-26 | 2010-02-09 | Citrix Systems, Inc. | Secure traversal of network components |
| US20030225700A1 (en) * | 2002-03-14 | 2003-12-04 | Guillermo Lao | System and method for graphical rights expressions |
| US20030229593A1 (en) * | 2002-03-14 | 2003-12-11 | Michael Raley | Rights expression profile system and method |
| US7805371B2 (en) | 2002-03-14 | 2010-09-28 | Contentguard Holdings, Inc. | Rights expression profile system and method |
| US20030200178A1 (en) * | 2002-04-18 | 2003-10-23 | International Business Machines Corporation | Managing licensing of distributed applications |
| CN1659559A (en) | 2002-04-29 | 2005-08-24 | 康坦夹德控股股份有限公司 | System and method for specifying and processing legality expressions |
| US20030212905A1 (en) * | 2002-05-08 | 2003-11-13 | Sun Microsystems, Inc. | Method, computer product and network to regulate software licensure authentication in a computer network environment |
| US7885896B2 (en) | 2002-07-09 | 2011-02-08 | Avaya Inc. | Method for authorizing a substitute software license server |
| US8041642B2 (en) | 2002-07-10 | 2011-10-18 | Avaya Inc. | Predictive software license balancing |
| DE10236458A1 (en) * | 2002-08-08 | 2004-03-04 | Siemens Ag | Data communication system and method for licensing software in a distributed network |
| GB2392262A (en) * | 2002-08-23 | 2004-02-25 | Hewlett Packard Co | A method of controlling the processing of data |
| US7216363B2 (en) * | 2002-08-30 | 2007-05-08 | Avaya Technology Corp. | Licensing duplicated systems |
| US7681245B2 (en) * | 2002-08-30 | 2010-03-16 | Avaya Inc. | Remote feature activator feature extraction |
| US7707116B2 (en) * | 2002-08-30 | 2010-04-27 | Avaya Inc. | Flexible license file feature controls |
| US7966520B2 (en) * | 2002-08-30 | 2011-06-21 | Avaya Inc. | Software licensing for spare processors |
| US7228567B2 (en) * | 2002-08-30 | 2007-06-05 | Avaya Technology Corp. | License file serial number tracking |
| US7698225B2 (en) * | 2002-08-30 | 2010-04-13 | Avaya Inc. | License modes in call processing |
| JP2004118327A (en) * | 2002-09-24 | 2004-04-15 | Sony Corp | Contents usage control device, contents usage control method and computer program |
| US20040078339A1 (en) * | 2002-10-22 | 2004-04-22 | Goringe Christopher M. | Priority based licensing |
| US7137114B2 (en) * | 2002-12-12 | 2006-11-14 | International Business Machines Corporation | Dynamically transferring license administrative responsibilities from a license server to one or more other license servers |
| US7890997B2 (en) * | 2002-12-26 | 2011-02-15 | Avaya Inc. | Remote feature activation authentication file system |
| US7260557B2 (en) * | 2003-02-27 | 2007-08-21 | Avaya Technology Corp. | Method and apparatus for license distribution |
| US7262869B2 (en) * | 2003-03-10 | 2007-08-28 | Hewlett-Packard Development Company, L.P. | Controlling font usage based on printer identification information |
| US7373657B2 (en) * | 2003-03-10 | 2008-05-13 | Avaya Technology Corp. | Method and apparatus for controlling data and software access |
| US7408656B2 (en) * | 2003-03-10 | 2008-08-05 | Hewlett-Packard Development Company, L.P. | Controlling printer macro usage based on printer identification information |
| US20040181696A1 (en) * | 2003-03-11 | 2004-09-16 | Walker William T. | Temporary password login |
| CA2519116C (en) * | 2003-03-13 | 2012-11-13 | Drm Technologies, Llc | Secure streaming container |
| US7685642B2 (en) * | 2003-06-26 | 2010-03-23 | Contentguard Holdings, Inc. | System and method for controlling rights expressions by stakeholders of an item |
| US20050010531A1 (en) * | 2003-07-09 | 2005-01-13 | Kushalnagar Nandakishore R. | System and method for distributing digital rights management digital content in a controlled network ensuring digital rights |
| US20050050319A1 (en) * | 2003-08-12 | 2005-03-03 | Zeev Suraski | License control for web applications |
| US7437457B1 (en) * | 2003-09-08 | 2008-10-14 | Aol Llc, A Delaware Limited Liability Company | Regulating concurrent logins associated with a single account |
| US20050071273A1 (en) * | 2003-09-25 | 2005-03-31 | Utstarcom, Inc. | Method and Apparatus for Feature Rights Management in a Multilevel Hierarchy |
| US20050071274A1 (en) * | 2003-09-27 | 2005-03-31 | Utstarcom, Inc. | Method and Apparatus in a Digital Rights Client and a Digital Rights Source and associated Digital Rights Key |
| US7421741B2 (en) * | 2003-10-20 | 2008-09-02 | Phillips Ii Eugene B | Securing digital content system and method |
| EP1544705A1 (en) * | 2003-12-10 | 2005-06-22 | Alcatel | Method for software protection |
| US20050132347A1 (en) * | 2003-12-15 | 2005-06-16 | Harper Eric D. | System for controlling the use of a software application on a plurality of computers |
| US20050149529A1 (en) * | 2004-01-02 | 2005-07-07 | Andi Gutmans | Efficient handling of download requests |
| US7353388B1 (en) | 2004-02-09 | 2008-04-01 | Avaya Technology Corp. | Key server for securing IP telephony registration, control, and maintenance |
| US20050192905A1 (en) * | 2004-03-01 | 2005-09-01 | Rutan Caleb C. | Licensing method for an electronic file |
| US7272500B1 (en) | 2004-03-25 | 2007-09-18 | Avaya Technology Corp. | Global positioning system hardware key for software licenses |
| US20050282607A1 (en) * | 2004-06-21 | 2005-12-22 | Michael Gauselmann | Game for a gaming device that changes automatically over time |
| JP4827467B2 (en) | 2004-09-10 | 2011-11-30 | キヤノン株式会社 | License transfer system and license information issuing server |
| JP4380480B2 (en) * | 2004-09-16 | 2009-12-09 | ソニー株式会社 | License processing apparatus, program, and license processing method |
| US7707405B1 (en) | 2004-09-21 | 2010-04-27 | Avaya Inc. | Secure installation activation |
| US7747851B1 (en) | 2004-09-30 | 2010-06-29 | Avaya Inc. | Certificate distribution via license files |
| US8229858B1 (en) | 2004-09-30 | 2012-07-24 | Avaya Inc. | Generation of enterprise-wide licenses in a customer environment |
| US7965701B1 (en) | 2004-09-30 | 2011-06-21 | Avaya Inc. | Method and system for secure communications with IP telephony appliance |
| US20060075222A1 (en) * | 2004-10-06 | 2006-04-06 | Seamus Moloney | System for personal group management based on subscriber certificates |
| US20060107326A1 (en) * | 2004-11-12 | 2006-05-18 | Demartini Thomas | Method, system, and device for verifying authorized issuance of a rights expression |
| US8660961B2 (en) | 2004-11-18 | 2014-02-25 | Contentguard Holdings, Inc. | Method, system, and device for license-centric content consumption |
| US7725721B2 (en) * | 2004-11-18 | 2010-05-25 | Cisco Technology, Inc. | Method and system for transferring software and hardware feature licenses between devices |
| US20060225055A1 (en) * | 2005-03-03 | 2006-10-05 | Contentguard Holdings, Inc. | Method, system, and device for indexing and processing of expressions |
| JP4440825B2 (en) * | 2005-05-17 | 2010-03-24 | 株式会社バンダイナムコゲームス | Game program recording medium |
| US20060271493A1 (en) * | 2005-05-24 | 2006-11-30 | Contentguard Holdings, Inc. | Method and apparatus for executing code in accordance with usage rights |
| US20060287959A1 (en) * | 2005-06-17 | 2006-12-21 | Macrovision Corporation | Software license manager employing license proofs for remote execution of software functions |
| US20060294022A1 (en) * | 2005-06-22 | 2006-12-28 | Dayan Richard A | Apparatus, system, and method for enabling a service |
| US20060294019A1 (en) * | 2005-06-22 | 2006-12-28 | Lenovo (Singapore) Pte. Ltd. | On demand business model to reuse software license |
| US7814023B1 (en) | 2005-09-08 | 2010-10-12 | Avaya Inc. | Secure download manager |
| US7720767B2 (en) | 2005-10-24 | 2010-05-18 | Contentguard Holdings, Inc. | Method and system to support dynamic rights and resources sharing |
| KR100877470B1 (en) * | 2005-11-22 | 2009-01-07 | 인터내셔널 비지네스 머신즈 코포레이션 | Method, system and computer program for a secure backup license server in a license management system |
| US7584943B2 (en) * | 2005-12-29 | 2009-09-08 | Frommelt Industries Of Canada, Inc. | Loading dock bumper with replaceable metal faceplate |
| US7702781B2 (en) * | 2006-03-03 | 2010-04-20 | Teoco Corporation | System and method of storing data files at a remote storage facility |
| US20070250711A1 (en) * | 2006-04-25 | 2007-10-25 | Phonified Llc | System and method for presenting and inputting information on a mobile device |
| KR101346734B1 (en) * | 2006-05-12 | 2014-01-03 | 삼성전자주식회사 | Multi certificate revocation list support method and apparatus for digital rights management |
| US7788272B2 (en) * | 2006-08-04 | 2010-08-31 | Xerox Corporation | Document catalog system |
| EP1901191B1 (en) * | 2006-09-18 | 2013-02-27 | Siemens Enterprise Communications GmbH & Co. KG | Method and system for administration of licences |
| JP4250655B2 (en) * | 2006-11-27 | 2009-04-08 | キヤノン株式会社 | Information processing system, information processing apparatus, and information processing method |
| US8566960B2 (en) * | 2007-11-17 | 2013-10-22 | Uniloc Luxembourg S.A. | System and method for adjustable licensing of digital products |
| WO2009105702A2 (en) * | 2008-02-22 | 2009-08-27 | Etchegoyen Craig S | License auditing for distributed applications |
| US9355224B1 (en) * | 2008-05-16 | 2016-05-31 | Kaspersky Lab, Zao | System and method for dynamic adjustment of expiration date for authorization key for antivirus products |
| US20090319635A1 (en) * | 2008-06-19 | 2009-12-24 | International Business Machines Corporation | Centrally managed inventory and entitlement data |
| US10453003B2 (en) * | 2008-09-18 | 2019-10-22 | Microsoft Technology Licensing, Llc | Digital rights management license identification |
| WO2010108006A2 (en) * | 2009-03-18 | 2010-09-23 | Altair Engineering, Inc. | Digital content licensing method |
| US9424399B2 (en) | 2009-05-12 | 2016-08-23 | Microsoft Technology Licensing, Llc | Availability of permission models in roaming environments |
| US8423473B2 (en) * | 2009-06-19 | 2013-04-16 | Uniloc Luxembourg S. A. | Systems and methods for game activation |
| US9633183B2 (en) | 2009-06-19 | 2017-04-25 | Uniloc Luxembourg S.A. | Modular software protection |
| US20100324983A1 (en) * | 2009-06-22 | 2010-12-23 | Etchegoyen Craig S | System and Method for Media Distribution |
| CN101651564B (en) * | 2009-09-08 | 2011-07-06 | 杭州华三通信技术有限公司 | License detection method, distributed network management system and server |
| JP5377282B2 (en) * | 2009-12-28 | 2013-12-25 | キヤノン株式会社 | Information processing apparatus, control method therefor, and computer program |
| US9065825B2 (en) * | 2010-02-05 | 2015-06-23 | International Business Machines Corporation | Method and system for license management |
| JP5545037B2 (en) * | 2010-05-28 | 2014-07-09 | 株式会社リコー | Information processing device |
| US9262595B2 (en) * | 2010-10-29 | 2016-02-16 | Qualcomm Incorporated | Methods and systems for accessing licensable items in a geographic area |
| US8725645B1 (en) | 2013-01-04 | 2014-05-13 | Cetrus LLC | Non-invasive metering system for software licenses |
| US9473303B2 (en) * | 2013-05-23 | 2016-10-18 | Rosemount Inc. | Method and system for product authentication |
| US10679151B2 (en) | 2014-04-28 | 2020-06-09 | Altair Engineering, Inc. | Unit-based licensing for third party access of digital content |
| CN105991578A (en) * | 2015-02-12 | 2016-10-05 | 中兴通讯股份有限公司 | Method and device for implementing login of terminal |
| US9614829B1 (en) * | 2015-03-27 | 2017-04-04 | EMC IP Holding Company LLC | Deauthentication in multi-device user environments |
| US10685055B2 (en) | 2015-09-23 | 2020-06-16 | Altair Engineering, Inc. | Hashtag-playlist content sequence management |
| CN105447346B (en) * | 2015-11-10 | 2018-08-28 | 国云科技股份有限公司 | A kind of distribution of facing cloud operating system, the license authentication method of High Availabitity |
| US11334882B1 (en) * | 2016-03-28 | 2022-05-17 | United Services Automobile Association (Usaa) | Data access management on a distributed ledger system |
| US10701141B2 (en) * | 2016-06-30 | 2020-06-30 | International Business Machines Corporation | Managing software licenses in a disaggregated environment |
| US11449370B2 (en) | 2018-12-11 | 2022-09-20 | DotWalk, Inc. | System and method for determining a process flow of a software application and for automatically generating application testing code |
| US11799864B2 (en) | 2019-02-07 | 2023-10-24 | Altair Engineering, Inc. | Computer systems for regulating access to electronic content using usage telemetry data |
| JP2020135344A (en) * | 2019-02-19 | 2020-08-31 | 富士ゼロックス株式会社 | Software providing device and program |
| US11068565B2 (en) * | 2019-06-13 | 2021-07-20 | International Business Machines Corporation | System obtains software features information of another system |
| US11025508B1 (en) | 2020-04-08 | 2021-06-01 | Servicenow, Inc. | Automatic determination of code customizations |
| US11296922B2 (en) | 2020-04-10 | 2022-04-05 | Servicenow, Inc. | Context-aware automated root cause analysis in managed networks |
| US10999152B1 (en) | 2020-04-20 | 2021-05-04 | Servicenow, Inc. | Discovery pattern visualizer |
| US11301435B2 (en) | 2020-04-22 | 2022-04-12 | Servicenow, Inc. | Self-healing infrastructure for a dual-database system |
| US11392768B2 (en) | 2020-05-07 | 2022-07-19 | Servicenow, Inc. | Hybrid language detection model |
| US11263195B2 (en) | 2020-05-11 | 2022-03-01 | Servicenow, Inc. | Text-based search of tree-structured tables |
| US11470107B2 (en) | 2020-06-10 | 2022-10-11 | Servicenow, Inc. | Matching configuration items with machine learning |
| US11277359B2 (en) | 2020-06-11 | 2022-03-15 | Servicenow, Inc. | Integration of a messaging platform with a remote network management application |
| US11451573B2 (en) | 2020-06-16 | 2022-09-20 | Servicenow, Inc. | Merging duplicate items identified by a vulnerability analysis |
| US11379089B2 (en) | 2020-07-02 | 2022-07-05 | Servicenow, Inc. | Adaptable user interface layout for applications |
| US11277321B2 (en) | 2020-07-06 | 2022-03-15 | Servicenow, Inc. | Escalation tracking and analytics system |
| US11301503B2 (en) | 2020-07-10 | 2022-04-12 | Servicenow, Inc. | Autonomous content orchestration |
| US11449535B2 (en) | 2020-07-13 | 2022-09-20 | Servicenow, Inc. | Generating conversational interfaces based on metadata |
| US11632300B2 (en) | 2020-07-16 | 2023-04-18 | Servicenow, Inc. | Synchronization of a shared service configuration across computational instances |
| US11748115B2 (en) | 2020-07-21 | 2023-09-05 | Servicenow, Inc. | Application and related object schematic viewer for software application change tracking and management |
| US11343079B2 (en) | 2020-07-21 | 2022-05-24 | Servicenow, Inc. | Secure application deployment |
| US11272007B2 (en) | 2020-07-21 | 2022-03-08 | Servicenow, Inc. | Unified agent framework including push-based discovery and real-time diagnostics features |
| US11582106B2 (en) | 2020-07-22 | 2023-02-14 | Servicenow, Inc. | Automatic discovery of cloud-based infrastructure and resources |
| US11095506B1 (en) | 2020-07-22 | 2021-08-17 | Servicenow, Inc. | Discovery of resources associated with cloud operating system |
| US11275580B2 (en) | 2020-08-12 | 2022-03-15 | Servicenow, Inc. | Representing source code as implicit configuration items |
| US11372920B2 (en) | 2020-08-31 | 2022-06-28 | Servicenow, Inc. | Generating relational charts with accessibility for visually-impaired users |
| US11245591B1 (en) | 2020-09-17 | 2022-02-08 | Servicenow, Inc. | Implementation of a mock server for discovery applications |
| US11625141B2 (en) | 2020-09-22 | 2023-04-11 | Servicenow, Inc. | User interface generation with machine learning |
| US11150784B1 (en) | 2020-09-22 | 2021-10-19 | Servicenow, Inc. | User interface elements for controlling menu displays |
| US11632303B2 (en) | 2020-10-07 | 2023-04-18 | Servicenow, Inc | Enhanced service mapping based on natural language processing |
| US11734025B2 (en) | 2020-10-14 | 2023-08-22 | Servicenow, Inc. | Configurable action generation for a remote network management platform |
| US11342081B2 (en) | 2020-10-21 | 2022-05-24 | Servicenow, Inc. | Privacy-enhanced contact tracing using mobile applications and portable devices |
| US11258847B1 (en) | 2020-11-02 | 2022-02-22 | Servicenow, Inc. | Assignments of incoming requests to servers in computing clusters and other environments |
| US11363115B2 (en) | 2020-11-05 | 2022-06-14 | Servicenow, Inc. | Integrated operational communications between computational instances of a remote network management platform |
| US11868593B2 (en) | 2020-11-05 | 2024-01-09 | Servicenow, Inc. | Software architecture and user interface for process visualization |
| US11281442B1 (en) | 2020-11-18 | 2022-03-22 | Servicenow, Inc. | Discovery and distribution of software applications between multiple operational environments |
| US11693831B2 (en) | 2020-11-23 | 2023-07-04 | Servicenow, Inc. | Security for data at rest in a remote network management platform |
| US11269618B1 (en) | 2020-12-10 | 2022-03-08 | Servicenow, Inc. | Client device support for incremental offline updates |
| US11216271B1 (en) | 2020-12-10 | 2022-01-04 | Servicenow, Inc. | Incremental update for offline data access |
| US11630717B2 (en) | 2021-01-06 | 2023-04-18 | Servicenow, Inc. | Machine-learning based similarity engine |
| US11301365B1 (en) | 2021-01-13 | 2022-04-12 | Servicenow, Inc. | Software test coverage through real-time tracing of user activity |
| US11418586B2 (en) | 2021-01-19 | 2022-08-16 | Servicenow, Inc. | Load balancing of discovery agents across proxy servers |
| US11301271B1 (en) | 2021-01-21 | 2022-04-12 | Servicenow, Inc. | Configurable replacements for empty states in user interfaces |
| US11921878B2 (en) | 2021-01-21 | 2024-03-05 | Servicenow, Inc. | Database security through obfuscation |
| US11513885B2 (en) | 2021-02-16 | 2022-11-29 | Servicenow, Inc. | Autonomous error correction in a multi-application platform |
| US11277369B1 (en) | 2021-03-02 | 2022-03-15 | Servicenow, Inc. | Message queue architecture and interface for a multi-application platform |
| US11831729B2 (en) | 2021-03-19 | 2023-11-28 | Servicenow, Inc. | Determining application security and correctness using machine learning based clustering and similarity |
| US11640369B2 (en) | 2021-05-05 | 2023-05-02 | Servicenow, Inc. | Cross-platform communication for facilitation of data sharing |
| US11635752B2 (en) | 2021-05-07 | 2023-04-25 | Servicenow, Inc. | Detection and correction of robotic process automation failures |
| US11635953B2 (en) | 2021-05-07 | 2023-04-25 | Servicenow, Inc. | Proactive notifications for robotic process automation |
| US11277475B1 (en) | 2021-06-01 | 2022-03-15 | Servicenow, Inc. | Automatic discovery of storage cluster |
| US11762668B2 (en) | 2021-07-06 | 2023-09-19 | Servicenow, Inc. | Centralized configuration data management and control |
| US11418571B1 (en) | 2021-07-29 | 2022-08-16 | Servicenow, Inc. | Server-side workflow improvement based on client-side data mining |
| US11516307B1 (en) | 2021-08-09 | 2022-11-29 | Servicenow, Inc. | Support for multi-type users in a single-type computing system |
| US11734381B2 (en) | 2021-12-07 | 2023-08-22 | Servicenow, Inc. | Efficient downloading of related documents |
| US11829233B2 (en) | 2022-01-14 | 2023-11-28 | Servicenow, Inc. | Failure prediction in a computing system based on machine learning applied to alert data |
| US11582317B1 (en) | 2022-02-07 | 2023-02-14 | Servicenow, Inc. | Payload recording and comparison techniques for discovery |
| US11734150B1 (en) | 2022-06-10 | 2023-08-22 | Servicenow, Inc. | Activity tracing through event correlation across multiple software applications |
| CN115630341B (en) * | 2022-12-22 | 2023-03-10 | 湖南国科亿存信息科技有限公司 | Software license authorization control method and system in high-availability storage equipment |
Family Cites Families (12)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US4446519A (en) * | 1981-05-26 | 1984-05-01 | Corban International, Ltd. | Method and apparatus for providing security for computer software |
| US4658093A (en) * | 1983-07-11 | 1987-04-14 | Hellman Martin E | Software distribution system |
| US4558413A (en) * | 1983-11-21 | 1985-12-10 | Xerox Corporation | Software version management system |
| US4791565A (en) * | 1984-06-20 | 1988-12-13 | Effective Security Systems, Inc. | Apparatus for controlling the use of computer software |
| US4694396A (en) * | 1985-05-06 | 1987-09-15 | Computer X, Inc. | Method of inter-process communication in a distributed data processing system |
| US4754395A (en) * | 1985-05-06 | 1988-06-28 | Computer X, Inc. | Network interface module with minimized data paths |
| US4683968A (en) * | 1985-09-03 | 1987-08-04 | Burroughs Corporation | System for preventing software piracy employing multi-encrypted keys and single decryption circuit modules |
| US4800488A (en) * | 1985-11-12 | 1989-01-24 | American Telephone And Telegraph Company, At&T Bell Laboratories | Method of propagating resource information in a computer network |
| US4780821A (en) * | 1986-07-29 | 1988-10-25 | International Business Machines Corp. | Method for multiple programs management within a network having a server computer and a plurality of remote computers |
| US4796220A (en) * | 1986-12-15 | 1989-01-03 | Pride Software Development Corp. | Method of controlling the copying of software |
| US4866769A (en) * | 1987-08-05 | 1989-09-12 | Ibm Corporation | Hardware assist for protecting PC software |
| US4924378A (en) * | 1988-06-13 | 1990-05-08 | Prime Computer, Inc. | License mangagement system and license storage key |
-
1987
- 1987-11-10 US US07/118,909 patent/US5390297A/en not_active Expired - Lifetime
-
1988
- 1988-10-14 CA CA000580262A patent/CA1310425C/en not_active Expired - Lifetime
- 1988-11-03 WO PCT/US1988/003923 patent/WO1989004520A1/en not_active Application Discontinuation
- 1988-11-03 AU AU27822/89A patent/AU2782289A/en active Granted
- 1988-11-03 JP JP63509411A patent/JPH02501171A/en active Pending
- 1988-11-03 EP EP19880910309 patent/EP0355132A4/en not_active Withdrawn
- 1988-11-09 CN CN88107735A patent/CN1035192A/en active Pending
-
1989
- 1989-07-10 KR KR1019890701292A patent/KR890702131A/en not_active Application Discontinuation
Also Published As
| Publication number | Publication date |
|---|---|
| CN1035192A (en) | 1989-08-30 |
| EP0355132A4 (en) | 1991-10-23 |
| JPH02501171A (en) | 1990-04-19 |
| KR890702131A (en) | 1989-12-22 |
| US5390297A (en) | 1995-02-14 |
| WO1989004520A1 (en) | 1989-05-18 |
| EP0355132A1 (en) | 1990-02-28 |
| AU2782289A (en) | 1989-06-01 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CA1310425C (en) | License management methods and systems | |
| US6968384B1 (en) | License management system and method for commuter licensing | |
| EP0598587B1 (en) | Verifying software programs | |
| US6378071B1 (en) | File access system for efficiently accessing a file having encrypted data within a storage device | |
| US6842896B1 (en) | System and method for selecting a server in a multiple server license management system | |
| US6507911B1 (en) | System and method for securely deleting plaintext data | |
| US7716348B1 (en) | License management system and method with license balancing | |
| US7269741B2 (en) | Recording apparatus, medium, method, and related computer program | |
| US6131165A (en) | Permit for controlling access to services in protected memory systems | |
| US6834799B2 (en) | IC card with capability of having plurality of card managers installed | |
| US5822771A (en) | System for management of software employing memory for processing unit with regulatory information, for limiting amount of use and number of backup copies of software | |
| US20050132347A1 (en) | System for controlling the use of a software application on a plurality of computers | |
| US20090237418A1 (en) | Useability features in on-line delivery of applications | |
| US5987497A (en) | System and method for managing the configuration of distributed objects | |
| US6298401B1 (en) | Object oriented storage device having a disc drive controller providing an interface exposing methods which are invoked to access objects stored in a storage media | |
| US20070136606A1 (en) | Storage system with built-in encryption function | |
| US7895124B2 (en) | Method for protecting sensitive data during execution | |
| JP2001312374A (en) | Storage device and access control method | |
| US20060031172A1 (en) | License management system, license management method, license management server, and license management software | |
| JPH1027123A (en) | Method for protecting computer software from copying | |
| JP2003517645A (en) | Data storage device and storage method | |
| KR20010022942A (en) | Redundancy implementation on object oriented data storage device | |
| JP4118032B2 (en) | IC card operation management system | |
| AU618056B2 (en) | Computer program license management system | |
| JPH08202659A (en) | Common information processing system |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| MKEX | Expiry |