Source: http://www.google.com/patents/US20050086174?dq=No.+6,411,949&ei=AUR7T-LGJqSr0AHy2aSiBg
Timestamp: 2017-07-28 01:57:25
Document Index: 337271930

Matched Legal Cases: ['art 200', 'art 250', 'art 290', 'art 370', 'art 410', 'art 460', 'art 500', 'art 520', 'art 540']

Patent US20050086174 - Distributed run-time licensing - Google PatentsSearch Images Maps Play YouTube News Gmail Drive More »Sign inPatentsMethods and systems are disclosed for managing software licenses in a distributed computer network. The number of software licenses allocated to software users can be determined on a node-by-node basis in realtime with little or no additional processing overhead incurred by the network. Upon of the occurrence...http://www.google.com/patents/US20050086174?utm_source=gb-gplus-sharePatent US20050086174 - Distributed run-time licensingAdvanced Patent SearchTry the new Google Patents, with machine-classified Google Scholar results, and Japanese and South Korean patents.Publication numberUS20050086174 A1Publication typeApplicationApplication numberUS 10/973,226Publication dateApr 21, 2005Filing dateOct 26, 2004Priority dateMay 11, 2001Also published asUS7359882, US7536356, US20020169725Publication number10973226, 973226, US 2005/0086174 A1, US 2005/086174 A1, US 20050086174 A1, US 20050086174A1, US 2005086174 A1, US 2005086174A1, US-A1-20050086174, US-A1-2005086174, US2005/0086174A1, US2005/086174A1, US20050086174 A1, US20050086174A1, US2005086174 A1, US2005086174A1InventorsMay EngOriginal AssigneeBea Systems, Inc.Export CitationBiBTeX, EndNote, RefManPatent Citations (32), Referenced by (60), Classifications (11), Legal Events (4) External Links: USPTO, USPTO Assignment, EspacenetDistributed run-time licensing
DETAILED DESCRIPTION [0032] FIG. 2 provides a block diagram 30 of a distributed computer network system comprising multiple nodes which can be used in accordance with the present invention. A plurality of nodes 32 and 34 are coupled to network 36. In one embodiment, a node is designated the master node 32. The remaining nodes are designated remote nodes 34. All nodes are in data communication with the other nodes of the network through communication software known in the art. Nodes 32 and 34 can be coupled to the network using any networking hardware known in the art. This hardware can include, but is not limited to: bridges, routers, hubs, or other hardware. Network communication can take place over any combination of electrical, optical, wireless, or other mediums. [0033] Although a plurality of nodes 32 and 34 are illustrated in FIG. 2, the present invention can be scaled for use with computing environments having any number of nodes in any desired distribution. In one embodiment, the present invention is implemented on a single node comprising a single server, while other embodiments implement the present invention across a plurality of nodes employing a wide range of computer systems as further described herein. [0034] A plurality of users 38 can access the master node 32 and remote nodes 34. In accordance with the present invention, users 38 can be any physical or virtual entities that seek to interact with software licensed in accordance with the present invention. Possible users include, but are not limited to: human beings, application software, operating systems, middleware, network protocols, other nodes of system 30, individual software threads, and other software or hardware. As will be apparent to those skilled in the art, many types of physical and virtual entities beyond those described above can be viewed as users in accordance with the present invention. In one embodiment, a maximum of 10,000,000 users can access a software program licensed in accordance with the present invention. [0035] Each remote node 34 periodically counts the number of users 38 currently accessing licensed software on the remote mode 34. In one embodiment, this count is performed during a sanity scan on a remote node. The remote node user counts are periodically transmitted to master node 32. In one embodiment, these transmissions are asynchronous. Master node 32 periodically sums the user counts received from the remote nodes 34 in order to determine a total number of users using the licensed software on system 30. This total indicates the number of software licenses currently in use by users 38 on system 30. In one embodiment, user licenses are automatically allocated to new users 38 after they log in, are counted, and included in the total number of users. As further described herein, processes running on the master node 32 can initiate appropriate actions depending on the total number of users counted (which represents the number of software licenses required), the total number of licenses available to all network users, and whether a remote node 38 fails to transmit a count. These actions include, but are not limited to: issuing messages, displaying messages, initiating license lockouts in order to prevent additional software licenses from being allocated, terminating license lockouts, initiating grace periods, and other actions including those further described herein. [0036] Although a preferred embodiment of the present invention is described herein in relation to a CORBA-based implementation of BEA TUXEDOä version 7.1 available from BEA Systems, Inc., of San Jose, Calif., it will be appreciated by those skilled in the art that the present invention can be implemented in accordance with many types of transaction processing monitoring software, middleware, applications, operating systems, and other software and hardware combinations known in the art. [0037] FIG. 3 illustrates a block diagram 40 of a computer system which can be used for the components of the present invention. The computer system of FIG. 3 includes a processor unit 50 and main memory 52. Processor unit 50 may contain a single microprocessor, or may contain a plurality of microprocessors for configuring the computer system as a multi-processor system. Main memory 52 stores, in part, instructions and data for execution by processor unit 50. If the present invention is wholly or partially implemented in software, main memory 52 can store the executable code when in operation. Main memory 52 may include banks of dynamic random access memory (DRAM), high speed cache memory, as well as other types of memory known in the art. [0038] The system of FIG. 3 further includes a mass storage device 54, peripheral devices 56, user input devices 60, portable storage medium drives 62, a graphics subsystem 64, and an output display 66. For purposes of simplicity, the components shown in FIG. 3 are depicted as being connected via a single bus 68. However, as will be apparent to those skilled in the art, the components may be connected through one or more data transport means. For example, processor unit 50 and main memory 52 may be connected via a local microprocessor bus, and the mass storage device 54, peripheral devices 56, portable storage medium drives 62, and graphics subsystem 64 may be connected via one or more input/output (I/O) buses. Mass storage device 54, which may be implemented with a magnetic disk drive, optical disk drive, as well as other drives known in the art, is a non-volatile storage device for storing data and instructions for use by processor unit 50. In one embodiment, mass storage device 54 stores software for implementing the present invention for purposes of loading to main memory 52. [0039] Portable storage medium drive 62 operates in conjunction with a portable non-volatile storage medium, such as a floppy disk, to input and output data and code to and from the computer system of FIG. 3. In one embodiment, the system software for implementing the present invention is stored on such a portable medium, and is input to the computer system via the portable storage medium drive 62. Peripheral devices 56 may include any type of computer support device, such as an input/output (I/O) interface, to add additional functionality to the computer system. For example, peripheral devices 56 may include a network interface for connecting the computer system to a network, as well as other networking hardware such as modems, routers, or other hardware known in the art. [0040] User input devices 60 provide a portion of a user interface. User input devices 60 may include an alpha-numeric keypad for inputting alpha-numeric and other information, or a pointing device, such as a mouse, a trackball, stylus, or cursor direction keys. In order to display textual and graphical information, the computer system of FIG. 3 includes graphics subsystem 64 and output display 66. Output display 66 may include a cathode ray tube (CRT) display, liquid crystal display (LCD) or other suitable display device. Graphics subsystem 64 receives textual and graphical information, and processes the information for output to display 66. Additionally, the system of FIG. 3 includes output devices 58. Examples of suitable output devices include speakers, printers, network interfaces, monitors, and other output devices known in the art. [0041] The components contained in the computer system of FIG. 3 are those typically found in computer systems suitable for use with certain embodiments of the present invention, and are intended to represent a broad category of such computer components known in the art. Thus, the computer system of FIG. 3 can be a personal computer, workstation, server, minicomputer, mainframe computer, or any other computing device. Computer system 40 can also incorporate different bus configurations, networked platforms, multi-processor platforms, etc. Various operating systems can be used including Unix, Linux, Windows, Macintosh OS, Palm OS, and other suitable operating systems. [0042] As will be appreciated by those skilled in the art, the components of computer system 40 can comprise all or parts of any of the components of block diagram 30 including master node 32 as well as any of remote nodes 34. It will also be appreciated that any of nodes 32 and 34 of FIG. 2 can comprise multiple computer systems, such as multiples of computer system 40 depicted in FIG. 3. [0043] FIGS. 4 and 5 illustrate subsets of data accessible by nodes of system 30, as well as processes running on the nodes for performing steps of methods in accordance with the present invention. FIG. 4 provides a block diagram 70 depicting components residing in memory of a remote node 34. Bulletin Board 72 (“BB”) is a shared memory accessible by processes running on a remote node 34. Bulletin Board Liaison 74 (“BBL”) is a process running on remote node 34 responsible for passing information between BB 72 and components of system 30. BBL 74 can also perform a plurality of processes in accordance with the present invention as further described herein. Transaction initiator 76 is a process running on remote node 34 responsible for initiating a user login as further described herein. Transaction terminator 78 is a process running on remote node 34 responsible for terminating a user logout as further described herein. Licensed software 80 is software licensed in accordance with the present invention running on a remote node 34 that is accessed by users 38. In one embodiment, licensed software 80 is at least one component of BEA TUXEDOä version 7.1. [0044] FIG. 5 is a block diagram 100 depicting components residing in memory of a master node 32 of a system 30. Distinguished Bulletin Board (“DBB”) 102 is a shared memory accessible by processes running on master node 32. Distinguished Bulletin Board Liaison (“DBBL”) 104 is a process running on master node 32 responsible for passing information between DBB 102 and components of system 30. License file 106 contains information describing the licenses available to system 30 for licensed software 80, as further described herein. Grace period clock 108 is a process which measures time elapsed since an error threshold was reached and is used to determine when a grace period has expired as further described herein. Grace period 112 stores the value of a maximum length of time that an error condition can be met before a license lockout is initiated as further described herein. In one embodiment, grace period 112 is set to a value of 24 hours. [0045] As further illustrated in FIG. 5, master node 32 can also comprise components 72, 74, 76, 78, and 80 previously described above. This allows master node 32 to also operate as a remote node. It will be appreciated that these remote node components are not required to be present in master node 32, but can be present in order to provide master node 32 with the functionality of remote nodes 34. [0046] The set of components depicted in FIGS. 4 and 5 is not intended to be exhaustive. It is well within the scope and contemplation of the present invention that master node 32 and remote nodes 34 can comprise additional components including processes, data, and other components not directly discussed herein. As will be appreciated by those skilled in the art, the components of FIGS. 4 and 5 can reside in any combination of memories such as random access memory, mass storage, portable storage, various components of FIG. 3, as well as any storage or memory means known in the art. [0047] FIG. 6 is a block diagram depicting data components stored in BB 72 of a remote node 34. Registry table 132 stores user entries 134 which are entered and deleted as user licenses are allocated and deallocated, as further described herein. Lockout flag 136 is set in response to the initiation of a license lockout, as further described herein. [0048] FIG. 7 is a block diagram depicting data components in DBB 102 of master node 32. Total licenses 162 is a maximum number of user licenses available to users of system 30 for accessing licensed software 80. Accordingly, total licenses 162 can include licenses already allocated to users, as well as licenses not yet allocated to users. In one embodiment, total licenses 162 is a system-wide parameter that does not vary with the number of nodes 32 and 34 running licensed software 80. In another embodiment, total licenses 162 equals the number of licenses purchased by an administrator. N0, N1, . . . , Nn 168, are counts of users made at each of remote nodes 34. Error threshold 170 is a variable used to determine whether too many licenses have been allocated across system 30. Warning threshold 172 is a variable used to determine whether all of total licenses 162 have been exhausted. Information threshold 174 is a variable used to determine whether enough licenses have been allocated across system 30 to pose a substantial risk that all of total licenses 162 will be exhausted. In one embodiment, thresholds 170, 172, and 174 can be employed as license allocation conditions that are evaluated by DBBL 104. [0049] FIG. 8 provides a flow chart 200 describing a process for determining total licenses 162. In one embodiment, the steps of FIG. 8 are performed by DBBL 104. At step 202, DBBL 104 on master node 32 is booted. In one embodiment, master node 32 is booted before nodes 34 are booted. At boot time, DBBL 104 accesses license file 106 and reads the total number of user licenses available across system 30 (step 204). DBBL 104 stores this data as total licenses 162 in DBB 102 (step 206). [0050] FIG. 9 illustrates the format of an exemplar license file 106. In one embodiment, license file 106 is an ASCII file. License file 106 comprises the name and version number of the licensed software, name of the licensee, serial number, orderid, number of users, type, number of developers, expiration date of the licenses, and a digital signature. In the example of FIG. 9, software entitled SOFTWARENAME version 1.1 is licensed to LICENSEENAME. The license file 106 has a serial number of 123456789. The orderid identifies the entity requesting license file 106. In the example of FIG. 9, an internal user requests the license file. The license file provides for 200,000 total user licenses and 100,000 total developer licenses system-wide. It will be appreciated that developer licenses can be managed in accordance with the present invention as described herein with respect to user licenses. The type parameter indicates whether the license file 106 is part of a software developer's kit or a run-time kit. In the example of FIG. 9, a software developer's kit (SDK) is specified. The expiration parameter indicates when licenses provided by license file 106 expire. In the sample of FIG. 9, the licenses expire on Feb. 20, 2005. A digital signature is provided which prevents administrators from tampering with the number of user and developer licenses specified by license file 106. In one embodiment, the digital signature is derived using parameters contained in the license file 106. In another embodiment, a subset of the components illustrated in FIG. 9 comprise license file 106. [0051] FIG. 10 provides a flow chart 250 describing a process for determining a number of licenses allocated to users 38 of licensed software 80 running on a remote node 34. In one embodiment, the steps of FIG. 10 are performed by BBL 74. In step 252, BBL 74 performs a periodic sanity scan on remote node 34. This sanity scan detects any failed, locked, partially inoperative, or completely inoperative processes running on the remote node 34 as well as the status of transactions between remote node 34 and other nodes. In one embodiment, sanity scans are performed at two minute intervals. In another embodiment, sanity scans are performed at intervals specified by an administrator. In yet another embodiment, a sanity scan at a remote node 34 can be initiated from master node 32. In step 254, BBL 74 counts the number of users 38 at remote node 34 accessing licensed software 80. In one embodiment, BBL 74 counts user entries 134 during step 254. In another embodiment, each user counted in step 254 requires a software license to access licensed software 80. Thus, the number of counted users can equal the number of software licenses required to be allocated to the node. [0052] At step 256, BBL 74 determines whether the sanity scan of step 252 was successful. If a full sanity scan was performed, then the sanity scan is deemed successful, and the method proceeds to step 260. At step 260, BBL 74 transmits a scan result message from remote node 34 to master node 32. If the sanity scan did not complete successfully (step 256), no scan result message is sent (step 258), and the method proceeds to step 262. In one embodiment, the sanity scan will be unsuccessful if the remote node 34 has become partitioned or has otherwise failed. At step 262, BBL 74 waits for a periodic sanity scan time interval before looping back to step 252 where another periodic sanity scan is performed. [0053] FIG. 11 provides a block diagram 270 of a sanity scan result message transmitted in step 260 of FIG. 10. Scan result message 270 comprises Nn 168 which is a count of users 38 accessing licensed software 80 on a remote node 34 obtained in step 254 of FIG. 10. In one embodiment, the opcode of scan result message 270 indicates that the sanity scan of step 252 of FIG. 10 was successful [0054] FIG. 12 provides a flow chart 290 describing a process for allocating and deallocating licenses to users 38 of licensed software 80. In one embodiment, the steps of FIG. 12 are performed by components of a remote node 34. At step 292, transaction initiator 76 receives a login request from a user 38. Transaction initiator 76 then checks lockout flag 136 stored in BB 72 (step 294). If the lockout flag 136 is set (step 296), BBL 74 recognizes that a license lockout is in progress (step 298). As a result, no license is allocated, and the user 38 is denied access (step 300). [0055] If lockout flag 136 is not set (step 296), transaction initiator 76 requests BBL 74 to add a user entry 134 to registry table 132 of BB 72 (step 302). BBL 74 adds the user entry 134 in step 304. Thus, during the next execution of step 254 of FIG. 10, BBL 74 will count the newly added user entry 134 along with other user entries 134 previously entered. This results in one more software license being required by the node. At step 306, licensed software 80 processes transactions requested by the non-licensed user 38. After the user 38 has finished interacting with licensed software 80, transaction terminator 78 receives a user logout request from user 38 in step 308. In response to the logout request, transaction terminator 78 requests BBL 74 to remove the user entry 134 from registry table 132 (step 310). BBL 74 removes the user entry 134 at step 312. After the user entry 134 is removed, BBL 74 will not detect the user entry 134 during the next count of users in step 254 of FIG. 10. As a result, one less license is required by the node. The license previously allocated to user 38 is deallocated from the user, freeing the license to be allocated to other users. [0056] FIG. 13 provides a flow chart 370 describing a process for determining a number of total users. In one embodiment, the steps of FIG. 13 are performed by DBBL 104. At step 371, DBBL 104 receives and stores user counts 168 received with scan result messages 270 in DBB 102. At step 372, DBBL 104 begins a BBL query cycle. During the BBL query cycle, DBBL 104 determines whether a scan result message 270 has been received from all of remote nodes 34 since a previous BBL query cycle (step 374). If a scan result message 270 has been received from each of remote nodes 34, then the method proceeds to step 378. Otherwise, DBBL 104 proceeds to step 376. [0057] If a scan result message 270 was not received from one or more remote nodes 34 in step 371, then DBBL 104 queries the non-reporting nodes, requesting a scan result message 270 (step 376). In steps 384, 386, and 388, DBBL 104 determines a user count 168 for each of the non-reporting nodes. It will be appreciated that DBBL 104 repeats steps 384, 386, and 388 for each non-reporting node. At step 384, DBBL 104 determines whether a scan result message 270 has been received from a first non-reporting node. If a scan result message not been received, then DBBL 104 assumes that the user count 168 for the non-reporting node equals zero users (step 386) and proceeds to step 388. On the other hand, if a scan result message 270 has been received from the node, then DBBL 104 will know the user count 168 of the node from the scan result message 270. DBBL 104 then proceeds to step 388. At step 388, if additional non-reporting nodes remain to be considered, then DBBL selects a next non-reporting node (step 390) and loops back to step 384. After all non-reporting nodes have been considered (step 388), then DBBL 104 will have a determined user count 168 for all nodes 34 of system 30. DBBL 104 then proceeds to step 378. [0058] At step 378, DBBL 104 sums the user counts 168 in order to obtain the number of total users. In one embodiment, each user 38 included in the number of total users requires a single software license. Software licenses are automatically allocated to new users 38 once they log in to a remote node 34, are included in a user count 168 received by DBBL 104, and included in the number of total users. In one embodiment, individual software licenses are not associated with specific users 38. Rather, the total number of users determined in step 378 is a system-wide number of licenses required by all currently logged in users 38 of system 30. A license is deemed allocated when a user is included in the sum obtained in step 378. [0059] Any nodes 34 from which a scan result message 270 was not received (step 371) will not have a user count 168 equal to zero as set in step 386. This effectively deallocates any software licenses formerly required by any previously counted users at nodes that have since failed. When a node fails, the number of total users will be lower than if user licenses on the failed node were included in summation step 378 (assuming at least one license was allocated to the failed node). With a lower number of total users, more licenses can be allocated to users of properly functioning nodes before the error 170, warning 172, or information thresholds 174 are met, as further described herein. [0060] At step 382, DBBL 104 compares the number of total users to license allocation conditions as further described herein. In one embodiment, step 382 allows DBBL to determine whether too many user licenses have been allocated. DBBL 104 then loops back to step 371 where it resumes receiving and storing user counts before beginning another BBL query cycle upon the expiration of a BBL query cycle interval. In one embodiment, BBL query cycles are performed in five minute intervals. In another embodiment, BBL query cycles are performed at tunable intervals set by an administrator. [0061] FIG. 14 provides a flow chart 410 describing a process for evaluating license allocation conditions and performing steps in response to license allocation results obtained from evaluations of the conditions. In one embodiment, the license allocation conditions are thresholds 170, 172, and 174. In another embodiment, the steps of FIG. 14 are performed by DBBL 104. In another embodiment, the method of FIG. 14 is called by step 382 of FIG. 13. At step 412, DBBL compares the number of total users obtained in step 378 of FIG. 13 with error threshold 170. In one embodiment, error threshold 170 is equal to 110 percent of total licenses 162. In another embodiment, error threshold 170 is 5 licenses greater than total licenses 162. If the error threshold 170 has been met, DBBL 104 displays an error message at master node 32 (step 414). In one embodiment, the error message is displayed in realtime and indicates that a license lockout is imminent. DBBL 104 then generates and transmits an error system event to all remote nodes 34 (step 416). In one embodiment, the error system event is a notification displayed on all remote nodes 34 in realtime containing the same information as the error message of step 414. At step 418, DBBL 104 evaluates lockout criteria to determine whether a license lockout will be initiated or is already in progress. If error threshold 170 is not met in step 412, then the method proceeds to step 426. [0062] At step 426, DBBL 104 determines whether the number of total users equals or exceeds warning threshold 172. In one embodiment, warning threshold 172 equals the number of total licenses 162. If the warning threshold 172 has been met, DBBL 104 checks whether a license lockout or grace period is in effect (step 427). DBBL 104 then proceeds to step 428 where it displays a warning message at master node 32 (step 428). In one embodiment, the warning message is displayed in realtime and indicates that all licenses have been exhausted. DBBL 104 then generates and transmits a warning system event to all remote nodes 34 (step 430). In one embodiment, the warning system event is a notification displayed on all remote nodes 34 in realtime containing the same information as the warning message of step 428. If warning threshold 172 is not met in step 426, the method proceeds to step 432. [0063] In step 432, DBBL 104 determines whether the number of total users equals or exceeds information threshold 174. In one embodiment, information threshold 174 is equal to ninety percent of total licenses 162. In another embodiment, information threshold 174 is one license less than the number of total licenses 162. If the information threshold 174 has been met, DBBL 104 checks whether a license lockout or grace period is in effect (step 433). DBBL 104 then proceeds to step 434 where it displays an information message at master node 32. In one embodiment, the information message is displayed in realtime and indicates that ninety percent of all available licenses have been exhausted. In another embodiment, the information message indicates that only five licenses are available for new users. DBBL 104 then generates and transmits an information system event to all of remote nodes 34 (step 436). In one embodiment, the information system event is a notification displayed on all remote nodes 34 in realtime containing the same information as the message of step 434. If information threshold 174 is not met in step 432, the method proceeds to step 438 where DBBL 104 checks whether a license lockout or grace period is in effect. The method then proceeds to step 420 where it returns to the process of FIG. 13. [0064] It will be appreciated that steps 414, 428, and 434 can notify administrators of the number and/or proportion of total licenses 162 available to be allocated across nodes 32 and 34 of system 30. These notifications can put administrators on notice to take steps to increase the number of total licenses 162 and/or decrease the number of total users in order to prevent the initiation of a license lockout in accordance with the present invention. [0065] FIG. 15 provides a flow chart 460 describing a process for determining whether license lockout criteria are met. In one embodiment, the steps of FIG. 15 are performed by DBBL 104. In another embodiment, the method of FIG. 15 is called by step 418 of FIG. 14. At step 464, DBBL 104 determines whether a lockout flag internal to the DBBL process 104 has been set. If so, a license lockout is already in progress and is allowed to continue (step 466). Otherwise, the method proceeds to step 472. At step 472, DBBL 104 checks whether grace period clock 108 has been set. In one embodiment, grace period clock 108 is set to the value of grace period 112 whenever error threshold 170 has been met in step 412 of FIG. 14. Grace period clock 108 measures a grace period during which software licenses can be allocated even though the number of total users has reached or exceeded the number of total licenses 162. In one embodiment, this grace period will run while grace period clock 108 is decremented. Once grace period clock 108 is decremented to a value less than or equal to zero, the grace period is tolled and a license lockout ensues. The grace period allows an administrator to purchase additional user licenses if necessary to prevent a license lockout, or take steps necessary to reduce the number of users 38, even if the notifications of steps 414, 428, or 434 of FIG. 14 were not heeded. [0066] At step 472, DBBL 104 checks whether grace period clock 108 has already been set. If not, DBBL 104 starts grace period clock 108 (step 474) which triggers the start of the grace period. If grace period clock 108 has already been set (step 472), the grace period is already running. Accordingly, the grace period clock 108 is decremented in step 473 before the method proceeds to step 476. In step 476, DBBL 104 determines whether the grace period has expired. In one embodiment, if the value of grace period clock 108 is less than or equal to zero, the grace period is deemed to have expired, and DBBL 104 begins a license lockout (step 478), as further described herein. Otherwise, DBBL 104 notifies an administrator of the time remaining in the grace period (step 480) and the method returns to the process of FIG. 14. [0067] FIG. 16 provides a flow chart 500 describing a process for initiating a license lockout. In one embodiment, the steps of FIG. 16 are performed by DBBL 104 and BBL 74. In another embodiment, the method of FIG. 16 is called by step 478 of FIG. 15. At step 502, DBBL 104 sets a lockout flag stored by the DBBL process itself. DBBL 104 then instructs each BBL 74 of remote nodes 34 to initiate a license lockout (step 504). In response, each BBL 74 of remote nodes 34 sets the lockout flag 136 of each BB 72 (step 506). At step 508, DBBL 104 displays a “lockout initiated” message at master node 32. In one embodiment, the lockout initiated message displayed at master node 32 indicates that a license lockout has begun. At step 510, DBBL 104 generates a lockout initiated event that is transmitted to the remote nodes 34. At step 514, the method returns to the process of FIG. 15. [0068] FIG. 17 provides a flow chart 520 describing a process for checking whether a grace period or license lockout is in progress. In one embodiment, the steps of FIG. 17 are performed by DBBL 104. In another embodiment, the method of FIG. 17 is called by each of steps 427, 433, and 438 of FIG. 14. At step 522, DBBL 104 determines whether a grace period is in progress. In one embodiment, this is determined by checking the value of grace period clock 108. If the value of grace period clock 108 is greater than zero, then a grace period is assumed to be in progress. If so, DBBL 104 resets the grace period clock 108 in step 524, thus terminating the grace period. In one embodiment, this grace period clock 108 is reset to a null value. On the other hand, if the value of the grace period clock 108 found in step 522 is not greater than zero, then DBBL 104 determines that no grace period is in progress requiring termination. DBBL 104 then proceeds to step 526. At step 526, DBBL 104 determines whether a license lockout is currently in progress. In one embodiment, DBBL 104 checks a lockout flag internal to the DBBL process 104 in step 522. If the flag is set, a lockout is assumed to be in progress. In response, DBBL 104 terminates the license lockout (step 528), as further described herein. Otherwise, the method proceeds to step 530 where it returns to FIG. 14. [0069] FIG. 18 provides a flow chart 540 describing a process for terminating a license lockout. In one embodiment, the steps of FIG. 18 are performed by DBBL 104. In another embodiment, the method of FIG. 18 is called by step 528 of FIG. 17. At step 542, DBBL 104 resets its internal lockout flag. DBBL 104 also resets grace period clock 108, thus allowing a new grace period to run if error threshold 170 is once again met (step 544). At step 546, DBBL 104 instructs each BBL 74 on remote nodes 34 to reset their lockout flags 136. In response, the lockout flags 136 are reset by the BBL's (step 548). At step 550, BBL 104 displays a “lockout terminated” message at master node 32. In one embodiment, the lockout terminated message indicates that a license lockout has ended. At step 552, DBBL 104 generates a lockout terminated event that is transmitted to the remote nodes 34. The method then returns to the process of FIG. 14 (step 556). [0070] In one embodiment, all messages generated by DBBL 104 or displayed at master node 32 can be stored in one or more log files on system 30. In one embodiment, such a log file resides on master node 32. In yet another embodiment, events generated by DBBL 104 can trigger actions by application programs running on system 30. [0071] The foregoing detailed description of the invention has been presented for purposes of illustration and description. It is not intended to be exhaustive or to limit the invention to the precise form disclosed. Many modifications and variations are possible in light of the above teaching. The described embodiments were chosen in order to best explain the principles of the invention and its practical application to thereby enable others skilled in the art to best utilize the invention in various embodiments and with various modifications as are suited to the particular use contemplated. It is intended that the scope of the invention be defined by the claims appended hereto. Patent CitationsCited PatentFiling datePublication dateApplicantTitleUS4511969 *May 20, 1983Apr 16, 1985At&T Information Systems Inc.Control channel interface circuitUS4937863 *Mar 7, 1988Jun 26, 1990Digital Equipment CorporationSoftware licensing management systemUS5023907 *Sep 30, 1988Jun 11, 1991Apollo Computer, Inc.Network license serverUS5329579 *Jul 27, 1992Jul 12, 1994At&T Bell LaboratoriesModular adjunct processor made of identical multi-function modules adaptable under direction of one of them to perform any of the adjunct-processor functionsUS5343526 *Oct 30, 1992Aug 30, 1994At&T Bell LaboratoriesMethod for establishing licensor changeable limits on software usageUS5438508 *Sep 12, 1994Aug 1, 1995Digital Equipment CorporationLicense document interchange format for license management systemUS5579222 *Dec 14, 1992Nov 26, 1996Intergraph CorporationDistributed license administration system using a local policy server to communicate with a license server and control execution of computer programsUS5671279 *Nov 13, 1995Sep 23, 1997Netscape Communications CorporationElectronic commerce using a secure courier systemUS5671285 *Dec 13, 1995Sep 23, 1997Newman; Bruce D.Secure communication systemUS5673315 *Jul 24, 1995Sep 30, 1997International Business Machines CorporationMethod and system for software asset usage detection and managementUS5758068 *Sep 19, 1995May 26, 1998International Business Machines CorporationMethod and apparatus for software license managementUS5790664 *Feb 26, 1996Aug 4, 1998Network Engineering Software, Inc.Automated system for management of licensed softwareUS5940504 *Jun 29, 1992Aug 17, 1999Infologic Software, Inc.Licensing management system and method in which datagrams including an address of a licensee and indicative of use of a licensed product are sent from the licensee's siteUS6009173 *Jan 31, 1997Dec 28, 1999Motorola, Inc.Encryption and decryption method and apparatusUS6014688 *Apr 25, 1997Jan 11, 2000Postx CorporationE-mail program capable of transmitting, opening and presenting a container having digital content using embedded executable softwareUS6029145 *Jan 6, 1997Feb 22, 2000Isogon CorporationSoftware license verification process and apparatusUS6055413 *Jul 21, 1998Apr 25, 2000Motorola, Inc.System and method for including origination time and update lifetime with updateable messagesUS6056786 *Jul 11, 1997May 2, 2000International Business Machines Corp.Technique for monitoring for license compliance for client-server softwareUS6189146 *Mar 18, 1998Feb 13, 2001Microsoft CorporationSystem and method for software licensingUS6324578 *Dec 14, 1998Nov 27, 2001International Business Machines CorporationMethods, systems and computer program products for management of configurable application programs on a networkUS6446136 *Dec 31, 1998Sep 3, 2002Computer Associates Think, Inc.System and method for dynamic correlation of eventsUS6453305 *May 21, 1999Sep 17, 2002Compaq Computer CorporationMethod and system for enforcing licenses on an open networkUS6609128 *Jul 30, 1999Aug 19, 2003Accenture LlpCodes table framework design in an E-commerce architectureUS6640244 *Aug 31, 1999Oct 28, 2003Accenture LlpRequest batcher in a transaction services patterns environmentUS6691175 *Feb 25, 2000Feb 10, 2004Sun Microsystems, Inc.Method and apparatus for managing data propagation between software modulesUS6760752 *Jun 28, 1999Jul 6, 2004Zix CorporationSecure transmission systemUS6766305 *Mar 12, 1999Jul 20, 2004Curl CorporationLicensing system and method for freely distributed informationUS6917976 *Aug 31, 2000Jul 12, 2005Sun Microsystems, Inc.Message-based leasing of resources in a distributed computing environmentUS7143093 *Dec 15, 1999Nov 28, 2006Webmethods, Inc.Enterprise computer systemUS7234103 *Apr 26, 2000Jun 19, 2007Accenture LlpNetwork-based tax framework databaseUS7359882 *May 11, 2001Apr 15, 2008Bea Systems, Inc.Distributed run-time licensingUS20020065780 *Nov 29, 2000May 30, 2002Isogon Corp.License compliance verification system* Cited by examinerReferenced byCiting PatentFiling datePublication dateApplicantTitleUS7228567Aug 30, 2002Jun 5, 2007Avaya Technology Corp.License file serial number trackingUS7260557 *Feb 27, 2003Aug 21, 2007Avaya Technology Corp.Method and apparatus for license distributionUS7272500Mar 25, 2004Sep 18, 2007Avaya Technology Corp.Global positioning system hardware key for software licensesUS7681245Aug 30, 2002Mar 16, 2010Avaya Inc.Remote feature activator feature extractionUS7698225Aug 30, 2002Apr 13, 2010Avaya Inc.License modes in call processingUS7707116Aug 30, 2002Apr 27, 2010Avaya Inc.Flexible license file feature controlsUS7707405Sep 21, 2004Apr 27, 2010Avaya Inc.Secure installation activationUS7747851Sep 30, 2004Jun 29, 2010Avaya Inc.Certificate distribution via license filesUS7814023Sep 8, 2005Oct 12, 2010Avaya Inc.Secure download managerUS7844572Oct 30, 2007Nov 30, 2010Avaya Inc.Remote feature activator feature extractionUS7865765 *Jun 9, 2005Jan 4, 2011International Business Machines CorporationGrid licensing server and fault tolerant grid system and method of useUS7885896Jul 9, 2002Feb 8, 2011Avaya Inc.Method for authorizing a substitute software license serverUS7890997Jan 20, 2003Feb 15, 2011Avaya Inc.Remote feature activation authentication file systemUS7913301Oct 30, 2006Mar 22, 2011Avaya Inc.Remote feature activation authentication file systemUS7966520Aug 30, 2002Jun 21, 2011Avaya Inc.Software licensing for spare processorsUS8041642 *Jul 10, 2002Oct 18, 2011Avaya Inc.Predictive software license balancingUS8229858Feb 4, 2005Jul 24, 2012Avaya Inc.Generation of enterprise-wide licenses in a customer environmentUS8347078Dec 20, 2004Jan 1, 2013Microsoft CorporationDevice certificate individualizationUS8438645 *Apr 27, 2005May 7, 2013Microsoft CorporationSecure clock with grace periodsUS8620819Oct 30, 2009Dec 31, 2013Avaya Inc.Remote feature activator feature extractionUS8700535Mar 21, 2008Apr 15, 2014Microsoft CorporationIssuing a publisher use license off-line in a digital rights management (DRM) systemUS8719171Jul 8, 2010May 6, 2014Microsoft CorporationIssuing a publisher use license off-line in a digital rights management (DRM) systemUS8725646Apr 15, 2005May 13, 2014Microsoft CorporationOutput protection levelsUS8781969Jul 13, 2010Jul 15, 2014Microsoft CorporationExtensible media rightsUS8825889 *May 11, 2009Sep 2, 2014Hewlett-Packard Development Company, L.P.Network traffic rate limiting system and methodUS8898085Jan 30, 2009Nov 25, 2014Hewlett-Packard Development Company, L.P.License management solution for central-management productsUS9122998 *Jul 28, 2010Sep 1, 2015International Business Machines CorporationCatalog-based software license reconciliationUS9135409May 18, 2011Sep 15, 2015Hewlett-Packard Development Company, L.P.Distributing update information based on validated license informationUS9224168Dec 11, 2012Dec 29, 2015Microsoft Technology Licensing, LlcTuning product policy using observed evidence of customer behaviorUS9230273Jul 28, 2010Jan 5, 2016International Business Machines CorporationCreation and use of constraint templatesUS9336359Feb 6, 2012May 10, 2016Microsoft Technology Licensing, LlcDevice certificate individualizationUS9363481Apr 27, 2005Jun 7, 2016Microsoft Technology Licensing, LlcProtected media pipelineUS9424399May 12, 2009Aug 23, 2016Microsoft Technology Licensing, LlcAvailability of permission models in roaming environmentsUS9436804Sep 15, 2005Sep 6, 2016Microsoft Technology Licensing, LlcEstablishing a unique session key using a hardware functionality scanUS9672578Jun 3, 2015Jun 6, 2017International Business Machines CorporationCatalog-based software license reconciliationUS20040010440 *Jul 10, 2002Jan 15, 2004Rohan LenardPredictive software license balancingUS20040044629 *Aug 30, 2002Mar 4, 2004Rhodes James E.License modes in call processingUS20040044630 *Aug 30, 2002Mar 4, 2004Walker William T.Software licensing for spare processorsUS20040044631 *Aug 30, 2002Mar 4, 2004Avaya Technology Corp.Remote feature activator feature extractionUS20040044901 *Aug 30, 2002Mar 4, 2004Serkowski Robert J.License file serial number trackingUS20040054930 *Aug 30, 2002Mar 18, 2004Walker William T.Flexible license file feature controlsUS20040078339 *Oct 22, 2002Apr 22, 2004Goringe Christopher M.Priority based licensingUS20040128551 *Jan 20, 2003Jul 1, 2004Walker William T.Remote feature activation authentication file systemUS20040172367 *Feb 27, 2003Sep 2, 2004Chavez David L.Method and apparatus for license distributionUS20040181695 *Mar 10, 2003Sep 16, 2004Walker William T.Method and apparatus for controlling data and software accessUS20040181696 *Mar 11, 2003Sep 16, 2004Walker William T.Temporary password loginUS20060242083 *Jun 26, 2006Oct 26, 2006Avaya Technology Corp.Method and apparatus for license distributionUS20060248596 *Apr 27, 2005Nov 2, 2006Microsoft CorporationSecure clock with grace periodsUS20060282519 *Jun 9, 2005Dec 14, 2006Trevathan Matthew BGrid licensing server and fault tolerant grid system and method of useUS20070094710 *Oct 30, 2006Apr 26, 2007Avaya Technology Corp.Remote feature activation authentication file systemUS20080052295 *Oct 30, 2007Feb 28, 2008Avaya Technology LlcRemote feature activator feature extractionUS20080189131 *Apr 10, 2008Aug 7, 2008Avaya Technology Corp.Method and apparatus for license distributionUS20090199299 *Jan 31, 2008Aug 6, 2009Microsoft CorporationIntegrated user experience while allocating licenses within volume licensing systemsUS20100049725 *Oct 30, 2009Feb 25, 2010Avaya Inc.Remote feature activator feature extractionUS20100287303 *May 11, 2009Nov 11, 2010Smith Michael RNetwork traffic rate limiting system and methodUS20100293103 *May 12, 2009Nov 18, 2010Microsoft CorporationInteraction model to migrate states and dataUS20100293536 *May 12, 2009Nov 18, 2010Microsoft CorporationEnhanced product functionality based on user identificationUS20100293622 *May 12, 2009Nov 18, 2010Microsoft CorporationAvailability of permission models in roaming environmentsUS20110023133 *Oct 5, 2010Jan 27, 2011International Business Machines CorporationGrid licensing server and fault tolerant grid system and method of useUS20110131315 *Nov 30, 2009Jun 2, 2011James Michael FerrisMethods and systems for verifying software license compliance in cloud computing environments* Cited by examinerClassifications U.S. Classification705/59International ClassificationG06Q30/00, G06Q20/38, G06Q30/06Cooperative ClassificationG06Q20/382, G06Q30/06, G06Q30/018, Y10S707/99938European ClassificationG06Q30/06, G06Q30/018, G06Q20/382Legal EventsDateCodeEventDescriptionJun 1, 2010CCCertificate of correctionOct 15, 2010ASAssignmentOwner name: ORACLE INTERNATIONAL CORPORATION, CALIFORNIAFree format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:BEA SYSTEMS, INC.;REEL/FRAME:025192/0244Effective date: 20101008Oct 1, 2012FPAYFee paymentYear of fee payment: 4Nov 3, 2016FPAYFee paymentYear of fee payment: 8RotateOriginal ImageGoogle Home - Sitemap - USPTO Bulk Downloads - Privacy Policy - Terms of Service - About Google Patents - Send FeedbackData provided by IFI CLAIMS Patent Services