EP0852349A2 - Procédé et dispositif d'authentification des droits d'utilisation de logiciels - Google Patents

Procédé et dispositif d'authentification des droits d'utilisation de logiciels Download PDF

Info

Publication number
EP0852349A2
EP0852349A2 EP97123041A EP97123041A EP0852349A2 EP 0852349 A2 EP0852349 A2 EP 0852349A2 EP 97123041 A EP97123041 A EP 97123041A EP 97123041 A EP97123041 A EP 97123041A EP 0852349 A2 EP0852349 A2 EP 0852349A2
Authority
EP
European Patent Office
Prior art keywords
computer
event
sites
program
software
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.)
Withdrawn
Application number
EP97123041A
Other languages
German (de)
English (en)
Other versions
EP0852349A3 (fr
Inventor
Robert Barritz
Peter Kassan
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Isogon Corp
Original Assignee
Isogon Corp
Priority date (The priority date 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 date listed.)
Filing date
Publication date
Application filed by Isogon Corp filed Critical Isogon Corp
Publication of EP0852349A2 publication Critical patent/EP0852349A2/fr
Publication of EP0852349A3 publication Critical patent/EP0852349A3/fr
Withdrawn legal-status Critical Current

Links

Images

Classifications

    • 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/107—License processing; Key processing
    • G06F21/1078—Logging; Metering
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q30/00—Commerce
    • G06Q30/02—Marketing; Price estimation or determination; Fundraising
    • G06Q30/0283—Price estimation or determination
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q30/00—Commerce
    • G06Q30/04—Billing or invoicing
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q40/00—Finance; Insurance; Tax strategies; Processing of corporate or income taxes
    • G06Q40/12—Accounting
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F2221/00—Indexing scheme relating to security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
    • G06F2221/21—Indexing scheme relating to G06F21/00 and subgroups addressing additional information or applications relating to security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
    • G06F2221/2101—Auditing as a secondary aspect
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F2221/00—Indexing scheme relating to security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
    • G06F2221/21—Indexing scheme relating to G06F21/00 and subgroups addressing additional information or applications relating to security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
    • G06F2221/2117—User registration
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F2221/00—Indexing scheme relating to security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
    • G06F2221/21—Indexing scheme relating to G06F21/00 and subgroups addressing additional information or applications relating to security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
    • G06F2221/2135—Metering

Definitions

  • the present invention relates to a method and apparatus for monitoring software license compliance and more particularly to a method and apparatus for collating, correlating, and redistributing information about events and conditions pertaining to the installation and use of documents and images generally including licensed computer software products.
  • Software products are often licensed for use only on particular computers, as determined by their serial numbers, or for use on a maximum number of computers, or for use on a maximum aggregate amount of computing power (typically measured in MIPS, millions of instructions per second). Or products may be licensed only for use by certain named users, or by a stipulated maximum number of concurrent users.
  • Products may also be licensed based on particular usage metrics, as appropriate for the product in question. For example, a sorting product might be licensed based on how many sort operations the licensee uses it for, or based on the number of bytes of data sorted, or on the number of records sorted, or on some combination of these factors.
  • a product providing database inquiry capability might be licensed based on the number of inquiries performed, perhaps weighted by the complexity level of each inquiry.
  • a product that performs a number of disparate scientific or engineering calculations might assign a charge-value for each type of calculation, then base license fees on the aggregate of these values. Or, it might instead simply keep track of the total CPU-time used in performing calculations, and base licenses on this.
  • Licenses based on usage metrics may be of the "electric meter” type, in which actual usage is measured, and paid for by the licensee on a periodic basis (monthly, quarterly, etc.). Licenses may be based on a mutually agreed-to "cap”, such that any amount of usage that does not exceed the cap is covered by a fixed periodic payment, or perhaps by a single initial payment, with additional fees due only if the cap is exceeded in a given measurement period. This latter arrangement is similar to the maintenance contracts on office copiers, commonly permitting no more than, but any amount fewer than, a stated maximum number of copies per month.
  • Some software products incorporate functions and facilities that monitor their own usage and enforce license terms (for example, by limiting the number of concurrent users of the product, or limiting usage to registered users, who sign on with unique passwords), or which merely report on usage and warn at usage beyond the terms of the license. In many cases, these functions are provided by products supplied by third-party vendors to be incorporated by software developers.
  • a further object of the invention is to provide a software license verification method which operates automatically.
  • Yet another object of the invention is to provide, at a central processing facility, a system which communicates with individual software usage sites and users, monitors/audits the use of various software products at the various sites, and generates reports for each individual vendor about the use of that vendor's products at the various sites.
  • a report can be in the form of electronically transmitted information.
  • a further object of the invention is to provide an apparatus and system for automatically billing users of a diverse range of software products from a central location.
  • the method and apparatus of the present invention comprises a system for collating, correlating and redistributing information about the use of licensed software products at various computer sites.
  • the system consolidates information (originally captured by other systems) by time period, such as day, week or month, about which licensed software products are installed at each computer site, as well as to what particulars of use are relevant. This may include the number of invocations of various software products, the number of logons, the number of concurrent users, as well as other usage metrics.
  • the information is sorted by vendor, so that the information about all of the software products licensed from a particular vendor can be periodically (or as it develops) sent to that vendor, automatically, or in response to prompting by vendors or from within the central computer system.
  • the apparatus of the invention serves for software license verification at plural, discrete computer sites and includes a local software usage monitoring facility.
  • a local software usage monitoring facility may (but need not) comprise:
  • the central computer includes software facilities for, among other things, prompting the local reports to issue from the discrete computer sites, in response to prompting commands from the central computer to the discrete computer sites.
  • Another software facility serves for transmitting vendor originated authorization codes to the discrete computer sites.
  • Another software facility receives authorization data from the plural discrete computer sites.
  • Yet another software facility prepares and transmits to the discrete computer site software usage billings.
  • a further software facility at the central computer calculates the amount of royalties owed for the use of software products at the discrete computer sites.
  • a further software facility controls disbursements to the vendors of monies received on account of the discrete computer sites.
  • Figure 1 is a block diagram illustrating a computing system for surveying and monitoring the use of various software products at a given licensee site.
  • Figure 2 is a flow chart illustrating the flow of a survey program of the system of Figure 1.
  • Figure 3 is a flow chart illustrating the flow of a monitoring program of the system of Figure 1.
  • Figure 4 is a flow chart illustrating the flow of a reporting program.
  • Figure 5 is a block diagram of a computing system incorporating a plurality of the systems illustrated in Figure 1 and a central processor (CP) of a central software license verification system.
  • CP central processor
  • Figure 6 is a flow chart of a survey results gathering and redistributing program.
  • Figure 7 is a flow chart of a software license authorization, billing and compliance monitoring program.
  • the computer system 10 includes an operating system 24 and may include an automatic job scheduler 32.
  • the computer system 10 connects to peripheral devices, examples of which are shown in Fig. 1 and may include storage devices 14, 16 and 18, interactive user terminals 26, 28 and 30, and a hatch reader 34. Not all of these peripheral devices are required to be present, and varying computer systems will have differing peripherals.
  • the operating system 24 may contain a centralized handler 44 for the processing of service requests, where this is the case, services 46a-46e are usually also provided.
  • program or program module is used synonymously with executable file.
  • a "software product”, or “product” is a related group of files comprising at least one module.
  • a product may comprise additional modules and/or non-executable files.
  • product generally refers to a particular "version" of a given product.
  • Figure 1 comprises a system for monitoring, tracking, and controlling the use of software products and the module or modules that comprise them.
  • the invention includes a computer system having four main components, three of which are executable programs and one of which is an arrangement of information for use by those programs.
  • the four main components are a surveying program, a monitoring program, a reporting program and a knowledge base.
  • the surveying program 12 examines all the storage devices 14, 16 and 18 on computer system 10 to determine the program modules present.
  • the user can restrict surveying program 12 to examine, for example, only selected storage devices or selected libraries.
  • the surveying program 12 surveys storage devices 14, 16 and 18 when requested to do so by an operator (e.g.,operator 26), any other program (e.g., the monitoring program 22), or periodically.
  • an operator 26 invokes the surveying program 12 to survey storage devices 14, 16 and 18 when the present invention is first introduced into a computer system 10.
  • An operator 26 may request the surveying program 12 to survey a single storage device, (e.g., storage device 14), for instance, because the operator 26 knows either that a software product has been installed on that storage device 14 or that a software product has been removed from that storage device 14 since the last time the survey program 12 surveyed that device 14.
  • the surveying program 12 has two main sub-components.
  • the first subcomponent is a directory surveyor 12A which examines entries in a program directory to determine what program modules are present.
  • the second sub-component is a file reader 12B that scans the contents of program files not recognized on the basis of its directory entry alone.
  • the directory surveyor 12A reads the program directory of the storage devices 14, 15 and 16, and ascertains which entries represent executable files on the basis of the entries in the directory. How a particular operating system 24 designates any of the entries as referring to program modules or non-executable files varies. An operating system 24 may indicate that a directory entry is associated with a program module by special flags, naming conventions, or otherwise. This is familiar to persons skilled in the particular operating system 24. On PCs, for example, executable files have extensions of .EXE or .COM. (Of course, one can name a non-executable text file as if it were executable, so this is not completely reliable).
  • the system configuration log 66, the knowledge base 20 and the recorded information log 62 are general collections of information.
  • the information comprising each of these collections may be stored in a single file or may be stored a multiplicity of separate files and other memory areas.
  • the knowledge base 20 comprises the following types of information:
  • the knowledge base 20 modules can be represented through the use of a wild card, i.e., in a generic fashion. For example, a single module record for the name "ABC*”, would be considered to match any actual name beginning with "ABC”.
  • wild cards in a search is well known in the art.
  • the file reader 12B scans, or reads, the files associated with directory entries and searches for copyright statements "COPYRIGHT”, “COPR”, or "(C)" (in either upper or lower case), recognized vendor names, recognized product names, and unique sequences or strings of text conforming to patterns recognized as product codes of particular vendors. As described above, this information, including copyright statements, vendor names, etc., which file reader 12B looks for may be stored in the knowledge base 20 or hard coded into the file reader 12B.
  • the surveying program 12 creates two types of records: one for modules identified by the directory surveyor 12A and one for modules identified by the file reader 12B. Both types of records contain module name, library name, volume name (i.e., the physical disk on which the library resides) and product ID.
  • the latter record type which are identified on the basis of a recognizable string, also contains data in the neighborhood of that string; the amount of the data that is contained therein can be varied. In a preferred embodiment it is 200 bytes of data.
  • the second major component of the system of Figure 1 is a monitoring program 22.
  • the monitoring program 22 records pertinent information in a recorded information log 62 when certain events occur.
  • the information recorded by the monitor consists of the module name, the library name from which it was loaded, the volume of the library, the product ID, the job name using the module, the step name using the module, the job start date and time, the job number assigned by the job scheduling/managing program, and the user ID. If the module is not loaded from a library but is resident, an indication of this is recorded. Depending on the operating system, other relevant information may be available, and is recorded, and some of this information may be unavailable. For compactness, this information may be reorganized.
  • one record is created containing all the job-related information (start date and time, job number, etc.), another record is created containing step related information (step name, etc.), and another record is created for each module used during that step. Later, in the reporting phase, this information is reorganized as appropriate.
  • program execution would be monitored as such an event, thus, when a program module is executed, pertinent information is recorded by the monitoring program 22.
  • the operating system performs, it accepts instructions as input from a variety of sources including interactive user, 26, 28, 30 automated job schedulers 32, batch job readers 34, and other programs. From these many sources of instructions, the operating system constructs one or more instruction streams which are lists of instructions to execute sequentially. In a multi-processing, multi-threading, or multi-tasking environment, several instruction streams may be operated upon concurrently.
  • the monitoring program 22 can monitor, or "see,” a system service request as an event regardless of whether the particular operating system 24 permits services to be invoked directly or whether they are invoked through a centralized handler 44.
  • the monitoring program 22 is introduced at one or more appropriate points of the operation of the operating system 24 so that every event desired to be monitored can be known to, or "seen” by, the program.
  • Techniques for introducing, or "hooking", an additional set of instructions into an existing program or operating system 24 are familiar to those skilled in the art. These may include techniques such as renaming an existing module and substituting a module with the original name or dynamically changing an address vector to point to the new program, and retaining the address of the original program so it can be invoked after the new program completes its operations.
  • monitoring program 22 would "hook” into numerous places in the operating system, such as program loading and termination calls. The places to "hook” into, of course, depend upon the events to be monitored. Thus, where there is no centralized handler 44, monitoring program 22 would "hook” into appropriate points of the operating system 24 which would likely include the execution of the individual service routines, for instance: a program loader, in the case where program "load” is being monitored.
  • reporting program 60 which sorts, correlates, consolidates, summarizes, formats and outputs reports 64 based upon the information gathered by surveying program 12 and monitoring program 22, e.g. the information stored in system configuration log 66 and recorded information log 62 respectively.
  • reporting program 60 can, using the information stored in system configuration log 66 and recorded information log 62, produce output reports 64.
  • reporting program 60 correlates the recorded information regarding events that have occurred and surveyed products on the computer system and can produce an almost infinite variety of reports. For instance, after correlating this information, reporting program 60 could produce reports: listing the products that are installed in duplicate along with a list of users which are accessing each copy; listing the number of accessed per unit time for any product; listing products which are routinely denied access due to the number of licenses; listing products that are accessed (or attempted) by unauthorized users; and/or listing all versions of a product currently installed, along with a list of the number of users that utilize each.
  • many other reports can be made using this information; once the event data is correlated with the associated software product, the analysis and assembly of the remainder of this information into useful reports would be familiar to one of skill in the art.
  • the reporting program 60 comprises two components, the identifier 60A and the reporter 60B.
  • the identifier 60A does the most of the correlating, consolidating and filtering that would be necessary to produce any report. (The identifier, for example, associates the product ID code and module records and searches for various text strings stored for records identified on the basis of a recognizable string.)
  • the reporter 60B performs only the final stages of sorting, consolidating and formatting.
  • the fourth main component of the present invention is the knowledge base 20 which comprises module names and the relationship of the modules to products with which they are associated. Knowledge base 20 may contain other information, such as product names, vendor names, vendors' products numbers, etc.
  • the present invention is loaded into the computer system 10 and the surveying program 12 is run.
  • the monitoring program 22 may be run continuously or for a sampling period. (Note that it is typical, but not required, that the surveying program 12 is run prior to running the monitoring program 22.)
  • the reporting program 60 may be run to report on system usage during the sampling period.
  • the surveying program 12 is executed so that it may examine the storage devices 14, 16 and 18 on computer system 10 and determine what executable files are present. Using the information contained in knowledge base 20, surveying program 12 determines which products are installed on computer system 10. This information is recorded in system configuration log 66 for use at a later time and may be optionally presented to the user in printed format, on-line display, or output in some other suitable form 64.
  • the information is presented to the user at an on-line display 68 where the information may be searched, scanned, and otherwise manipulated.
  • This information may be presented to the user by surveying program 12 itself, by reporting program 60, or by another program. Programs to display and manipulate information are well known in the art.
  • the monitoring program 22 could be configured to monitor the installation of new software as an event. When monitoring program 22 detects that new software has been installed, it could invoke surveying program 12. By so invoking surveying program 12, the information regarding installed products would be kept up to data automatically.
  • the monitoring program 22 could be configured to monitor the deletion of software as an event. Upon detecting this event, monitoring program could invoke surveying program 12, similarly keeping the information regarding installed products current.
  • the monitoring program 22 may be activated for a sample period, or it may be operated constantly. Typically, when used to monitor licensed software, user accesses and the like, the monitoring program 22 would normally be operated constantly. On the other hand, when used to accumulate information regarding utilization of various products and/or product versions, and to determine usage patterns, the monitoring program 22 may be activated for a sample period.
  • the length of the sample period in which to operate the monitoring program 22 depends upon the particular characteristics of the computer system 10 and the operating system 24 upon which the monitoring program is being run. In a preferred embodiment, such a sample period would be between a week and about two months. It is, however, important to note that certain products may only be executed, e.g., annually. Where this is the case, the monitoring program 22 would not "see” the activation of these products unless its sample period included the time when at least one of its modules were executed.
  • the monitoring program 22 may be used to monitor a sample period, and produce a report reflecting system usage.
  • the information obtained by it, and stored in recorded information log 62 can be processed by reporting program 60 and presented to the user in a usable format. For example, a user may request a listing of a particular product indicating how many times any module of the product was executed during the period monitored.
  • reporting program 60 would check the system configuration log 66 to determine which modules are associated with a given product, thereafter, the recorded information log is scanned for execution events for the module names associated with the product occurring during the period in question.
  • Total executions may be maintained in memory and the information can then be presented to the user in printed format, on-line display, or some other suitable form 64.
  • the user can be permitted to search, scan, and otherwise manipulate it.
  • monitoring program 22 when each monitored event occurs, information relevant to that event is recorded in the recorded information log 62.
  • this information includes the time and date, the name of the file being executed and the identity of the user, job, or program that initiated the file. Also included can be the location from which the program was obtained, for example, the program library or area of main storage.
  • This recorded information log 62 may be recorded in main storage or in auxiliary storage such as magnetic tape or disk, printed out, etc.
  • the recorded information log 62 would comprise recorded information in main storage and recorded information written to auxiliary storage.
  • monitoring program 22 would periodically write a cached portion of the recorded information log 62 in main storage to the recorded information log 62 in auxiliary storage.
  • the monitoring program 22 may, under the control of user specifications, restrict its attention to certain modules, certain types of modules, modules obtained from certain locations, certain products, certain kinds of events, certain times of day, or days of the week, etc.
  • the monitoring program 22 can also be used to ensure compliance with licenses, both in terms of whether a given computer is licensed to use a given software product and whether the licensed number of users on a given computer has been exceeded. In order to monitor this type of information, it is preferred that monitoring program 22 is run continuously, rather than for sampling period.
  • monitoring program 22 is supplied with a list of software products to be monitored, optionally this list may include information regarding which computers are authorized to run each product and the number of concurrent users permitted. Monitoring program 22 may check the list whenever an event occurs which would require authorization, e.g. a program execution.
  • monitoring program 22 determines that authorization is to be denied, it causes the event to fail, for example, by "abending" rather than permitting execution of a program in the case of program execution.
  • Monitoring program 22 may additionally issuing a warning message and would, in a preferred embodiment, write an entry in recorded information log 62.
  • monitoring program 22 may obtain identifying information as to which computer originated the request to execute the program in a similar fashion as it obtains other event information. In the case of checking the number of concurrent users, monitoring program 22 would maintain an individual count for each program to be monitored, incrementing the count each time it allows the program to be initiated and decrementing it each time the task (job, address space, etc.) that initiated the request terminates. In this case, monitoring program 22 would also monitor such terminating events.
  • surveying program 12, monitoring program 22 and reporting program 60 can be directed to survey, monitor, and report only a user-specified list of products, or can be confined in their operations in other ways.
  • knowledge base 20 can be supplemented by information provided by the user.
  • the surveying program 12 can make use of other data bases it finds on the system to relate program module names to product names.
  • a possible major enhancement to the basic invention applies to networks of computers.
  • a number of PC computers or microcomputers can be linked.
  • monitoring program 12, or a separate program can automate the periodic downloading and execution of surveying program 12 and/or monitoring program 22 on the computers, as well as the periodic uploading of the resulting information.
  • This could be carried out with PC computers or microcomputers linked to a mainframe computer, or alternatively, in a peer computer network.
  • information can be gathered about products installed on a number of other computers, as well as information about their actual usage.
  • monitoring program 22 can be enhanced to monitor the execution of transactions that run under the control of a teleprocessing monitor such as CICS, IMS, and INTERCOMM.
  • a teleprocessing monitor provides an environment in which on-line applications are run concurrently. Such applications, known as transactions, are typically executed from within the teleprocessing monitor without using the system services used to recognize execution of ordinary files.
  • This enhancement involves analyzing each teleprocessing monitor that the monitoring program is to support, identifying the mechanism by which the teleprocessing monitor invokes a transaction and, as discussed above, introducing additional instructions at the appropriate points to capture and write out the required information.
  • the survey program 12 is initiated at 100. Once initiated, the survey program at 110 determines whether there is a storage device (14, 16 and 18, Figure 1) that requires surveying. If there is a storage devices that requires surveying, survey program 12, at 120 reads the directory or directories of that storage device. If there are no storage devices which require surveying, the survey program 12 terminates at 99.
  • Survey program 12 then, at 130 reviews the directory or directories of the storage device to determine whether there are modules therein which have not been recorded in the system configuration log (66, Figure 1). If it finds that there are no such modules, survey program 12 returns to location 105, so that it may proceed to the next storage device. If, however, there are modules which have not been "surveyed” by survey program 12, at 140 survey program 12 searches the knowledge base for the module's name.
  • survey program 12 gets the information record stored in the knowledge base that is associated with the module's name. Subsequently, at 150b the module name and the associated information record are written to the system configuration log 66. If, however, the module's name is not located in the knowledge base, at 160a the module itself is scanned for a module identifier. As discussed above, a module identifier could include a product code or copyright found in the module itself, among other identifiers. Once the module identifier is located, at 160b, the module name and its associated identifier are written to the system configuration log 66. Having stored the appropriate information in the system configuration log 66, the survey program proceeds to location 125 so that it may determine whether additional "surveying" of modules on this storage device is required.
  • the monitoring program 22 is initiated at 200. Once initiated, the monitoring program, at 210 introduces itself at the appropriate points of the computer system 10 and the operating system 24. As discussed above, these appropriate points depend upon the type of computer system, operating system into which they are introduced, and also depend upon the events that will be monitored.
  • monitoring program 22 Once monitoring program 22 is introduced into the computer system 10 and operating system 24, at 220, it awaits an event. If it receives an instruction to terminate, at 299a, it takes appropriate actions to remove itself from the points it had introduced itself to at 210, and then, at 299b, it terminates.
  • monitoring program 22 When monitoring program 22 receives indication that one of its monitored events has occurred, at 230, it obtains event information. At 240, this event information is recorded in the event information log (62, Figure 1), and the program goes to location 215 to await another event.
  • monitoring program 22 could introduce itself at 210 to receive many types of events. Once an event is received, at 220, monitoring program 22 could determine whether the event is the type it will record in step 240; if it is such an event, monitoring program 22 may proceed to 230 and obtain event information, if it is not such an event, monitoring program 22 may ignore the event, remain at 220 and await another event. This latter method of filtering events by the monitoring program 22 is useful because it permits dynamic changes in the events that are monitored without additional introduction into points in computer system 10 and operating system 24.
  • reporting program 60 is initiated at 300. Once initiated, the reporting program at 310 obtains access to both the system configuration log (66, Figure 1) and the recorded information log (62, Figure 1). Subsequently, at 320, reporting program 60 correlates at least event information in the recorded information log 62 and product associations in the system configuration log 66.
  • reporting program 60 formats the correlated data, and other desired data for output as a report.
  • the report is output. Once the report is output, at 399, reporting program 60 terminates.
  • the method and apparatus described above monitors events relating to executable program modules, for example, the usage of computer programs.
  • the method automatically records each monitored event at a particular program execution site, i.e., at a given computer, as described in the parent application.
  • a method and apparatus for collating, correlating, and redistributing information about the events and conditions pertaining to the installation and use of licensed computer software products have not previously provided a method and apparatus for collating, correlating, and redistributing information about the events and conditions pertaining to the installation and use of licensed computer software products.
  • the data collected at the local computer sites 10 is outputted from each site in the form of reports 64, which reports are transmitted to a central processor (CP) 500 for consolidation, processing and transmission to various vendors 520 such as the vendors 1, 2, 3 ... m.
  • the licensed software users 10 periodically send all their gathered data, as a single bundle to the CP 500, which then redistributes it to the vendors 520 in a form usable by the vendors.
  • the periodic transmission of data from the users 10 to the CP 500 could be initiated by an automatic scheduling process, without any user involvement. Alternatively, such data could be transmitted from a user installation as it is created (for example, each time a product is invoked, or whenever a product completes a stage of processing, such as the end of a transaction or a sort job).
  • the data from the multiplicity of user sites 10 is intended to be processed concurrently, with each data element marked as to which user it originated from, which product(s) was used, the nature of use, etc.
  • the data is then further sorted by vendor, user, and licensed product. All data pertaining to a particular vendor is then separately reported over the lines 530 for transmission to the corresponding vendor 520. This enables the vendors 520 to monitor user compliance with the licensed terms, and, if applicable, levy additional fees if usage activity exceeds licensed limits, etc.
  • the CP 500 could retransmit the usage data to the appropriate vendor when it was received, rather than collecting it.
  • Transmission of data from the user 10 to the CP 500, and then from the CP 500 to the vendors 520 may be in the form of computer files, or data that is stored on tape or diskette or information transmitted electronically or via an Internet hookup.
  • the CP 500 could also perform centralized billing and collections of monies that might be due from users 10 to the vendors 520.
  • the CP 500 stores within its memory a database of the license terms that pertain between each vendor and each user or product, so that if the periodic usage information received from a particular user discloses that license limits have been exceeded for one or more of the multiplicity of licensed products contained in the gathered data, then the CP 500 would render an invoice to that user for the sum total of all monies due to all of the vendors of those licensed products.
  • the CP 500 is designed and programmed to remit to each vendor a single payment, representing the total of collections received, within a given reporting period, from all the users that pertain to that vendor's licensed product.
  • the CP 500 performs centralized authorization.
  • the CP 500 distributes, on user requests or in response to information received from the various vendors 520, new authorization codes reflecting changes (typically increases) in the usage authorization of particular products licensed by each user 10.
  • the CP 500 records these changes, and transmits them to the vendors in the same manner as usage data.
  • new authorization codes could originate with a vendor (for example, if now codes are to be sent to a licensed user of a particular product), in which case the CP 500 broadcasts the authorization code to all users of that product.
  • reference numeral 550 denotes the starting/initialization portion of the survey and gathering program 550 which queries at step 552 whether any reports 64 have been received from the various users 10 ( Figure 5) over the lines 532. If yes, the incoming data is collated and sorted, at 554, based on software products and allocated to one of the many different vendors 520 for which the CP 500 maintains records.
  • step 556 the particular vendor's reporting schedules are consulted to determine whether each given vendor requires immediate reporting of the information that has been received or whether that information is to be collected for periodic (daily, weekly, monthly, etc.) reporting. If reports need to be transmitted to the vendors 520, a decision to that effect is made at step 558 which proceeds to transmit the necessary report as indicated at 560. On the other hand, if no reports are required and/or after the reports have been sent, the program proceeds to decisional box 562 where the program queries whether any of the sites 10 ( Figure 5) require prompting to cause them to issue reports 64.
  • the reports 64 are received at the CP 500 from the users 10 only in response to prompting by the CP 500, rather than periodically. If so, appropriate prompting commands are issued to the users at step 564 and the program returns to monitor whether incoming reports have been received. Otherwise, the program proceeds to decisional box 566 to determine whether other functions are to be carried out by the central processor 500. If so, the program exits at 568 to attend to the various functions which are illustrated in Figure 7. Alternatively, the program returns to decisional box 552 and the process continues.
  • step 576 If any authorization of computer sites 10 is required, the necessary codes are sent to the site at step 576. Moreover, some systems require recordation of authorization data from the users and this is effected at step 578.
  • the program then proceeds to step 580 where the program checks whether it has received from the various vendors updated authorization data that is relevant. If step 574 indicates that authorization is not presently required, the program proceeds to step 580 to detect whether it has received and recorded such authorization data from the vendors 520, in which event, the program is caused to run through end box 598 to return and reexecute the process including the steps 574 and 576 which transmit the updated authorization data to the various users.
  • step 582 If the function to be performed is billing, collection or disbursement, the program proceeds via step 582 to step 584 to collect and correlate the usage data for each account.
  • the usage information is collated at stop 586 with the billing/license terms that is stored in the memory of the CP 500.
  • Software routine 590 calculates the amount due from each vendor and then prepares and transmits billing and invoices to the various users 10 as indicated at 592.
  • Another software function performed by the CP 500 is to collate the various monies received from the users 10 and, as indicated at 594, to thereafter disburse these monies to vendors under the control of software routine 596. As before, the program returns through step 598.
  • routine 602 which carries out various compliance procedures. These may include random checks on the contents of the memory at the user sites 10 to verify license compliance, thus ensuring that users have not tampered with or altered the software monitoring codes and/or verify payment. As indicated at 604, such compliance monitoring may involve the transmission from the CP 500 to the various user sites of special executable programs (which may change from time to time) that, for example, command the execution of programs which verify that the invocation of various software routines creates the appropriate outputs at the user site.
  • Compliance may also include surprise monitoring of authorization codes as indicated at 606. If any irregularities are noted as indicated at 608, the CP 500 may optionally disable the user's system. As yet another alternative, the CP 500 may operate to issue appropriate warnings to the user sites. For example, a message may be caused to be printed on the printer at the user site or appear on the display console in the form of a warning that failure to comply with certain payment schedules will result in disablement of the system within a given time period, as generally indicated at 610.
  • the program may be used as indicated in software routine 612, for posting various notices of the vendors, in response to program conditions or in response to information received from the vendors 520.
  • notices may comprise information about upcoming upgrades to the licensed software and the like.
  • the availability of the CP 500 which communicates directly with the user sites, can also be deployed to automatically upgrade software packages to reflect latest changes.
  • Such updates may be caused to be automatically installed during non-working hours, enhancing efficiency, promoting customer satisfaction and improving the vendors' control over their proprietary software products.
  • Payment for software could be made by having the user purchase a "debit card", a secure, encoded value that could then be “worked off” through usage of one or more products.
  • This function would reside at the user's site, within the usage monitoring or license management function, or within the process that gathers usage info for transmittal to the central site. When the debit card needs refilling, this would be done by communication with the central site, with the central site allocating payments to the vendors based on the way the prior fillup was used.
  • Distribution of software could be centralized, with master copies of software supplied by the vendors to the central site, which then transmits the software to all licensees, either at the command of the vendor, or at the request of the licensee. Users could also use this mechanism to license (and pay for) additional software or additional license rights, on demand, with the central site consolidating this information for transmittal to the vendors, and possibly performing the billing. Updates to software (either new versions, or corrections to existing versions) could be handled as above. All usage information, instead of being gathered, batched, and periodically transmitted to the central site, could be sent to the central site in real time, with accumulation occurring at the central site. Similarly, the central site could redistribute the usage information to the vendors in real time rather than batching it.
  • usage as used herein and/or a reported event includes all detected events, including those relating to compliance issues, such as software or database access requests that may have been denied because they violated license terms, or that were permitted even though they violated the license terms.
  • the act of installing software or data (even without using) may similarly be reported as a usage event.
  • the "policy” information that is, the license terms and conditions that apply to a particular user's use of a particular product, which are typically supplied by the vendor in encrypted from, and which may be input into a license manager to manage compliance, could also be consolidated at the central site for transmission to the vendors so that they might verify that the terms put in effect matched those they had authorized.
  • the central site at the direction of a vendor, might send a directive to the license management or usage gathering functions at one or more users, causing it to modify the manner in which license terms are administered and/or usage is measured (for example, if multiple types of usage are weighted, then combined into a single number, the weighing factors could be changed).
  • central site computer it is not necessary that the "central site" computer be physically located away from the local sites.
  • a central site computer may be located at or even operated by the user. That is, all or most of the central site functions might be done on or at the user's central system, on behalf of several of the user's other systems.
  • An “event” includes the monitoring of the usage of proprietary information, e.g. copyrighted text, pictorial and data stored in databases. Owners, vendors, licensors, licensees, etc. of valuable copyrighted material are becoming increasingly concerned about the piracy of such information when transmitted over public communication systems such as the Internet.
  • the present invention provides a technological solution in the form of the above-described system which may be deployed as an instrumentality in monitoring the use of copyrighted subject matter. To this end, digitized copyrighted subject matter can embed code that provides proof of ownership and copy protection.
  • the present invention takes a different approach that can be implemented in several ways.
  • One approach interposes the "local" monitoring software of the present invention (or a similar system) between the Internet and the user.
  • the "local” monitoring software then receives, monitors, tags, and quantifies the usage, e.g., downloading, using, etc. of copyrighted subject matter. That software then prepares local reports reflecting the usage, which reports are then collated by the central site computer of the present invention, to provide reports to the vendors/owners of the copyrighted subject matter usage for billing purposes.

Landscapes

  • Engineering & Computer Science (AREA)
  • Business, Economics & Management (AREA)
  • Development Economics (AREA)
  • Theoretical Computer Science (AREA)
  • Accounting & Taxation (AREA)
  • Finance (AREA)
  • General Physics & Mathematics (AREA)
  • Physics & Mathematics (AREA)
  • Strategic Management (AREA)
  • Marketing (AREA)
  • General Business, Economics & Management (AREA)
  • Economics (AREA)
  • Software Systems (AREA)
  • Technology Law (AREA)
  • Multimedia (AREA)
  • Computer Hardware Design (AREA)
  • Computer Security & Cryptography (AREA)
  • General Engineering & Computer Science (AREA)
  • Entrepreneurship & Innovation (AREA)
  • Game Theory and Decision Science (AREA)
  • Storage Device Security (AREA)
  • Management, Administration, Business Operations System, And Electronic Commerce (AREA)
EP97123041A 1997-01-06 1997-12-31 Procédé et dispositif d'authentification des droits d'utilisation de logiciels Withdrawn EP0852349A3 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US08/779,140 US6029145A (en) 1997-01-06 1997-01-06 Software license verification process and apparatus
US779140 1997-01-06

Publications (2)

Publication Number Publication Date
EP0852349A2 true EP0852349A2 (fr) 1998-07-08
EP0852349A3 EP0852349A3 (fr) 1999-06-16

Family

ID=25115455

Family Applications (1)

Application Number Title Priority Date Filing Date
EP97123041A Withdrawn EP0852349A3 (fr) 1997-01-06 1997-12-31 Procédé et dispositif d'authentification des droits d'utilisation de logiciels

Country Status (2)

Country Link
US (1) US6029145A (fr)
EP (1) EP0852349A3 (fr)

Cited By (22)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP1006447A2 (fr) * 1998-11-30 2000-06-07 General Electric Company Surveillance à distance de cartes électroniques/routines de logiciel
WO2000052559A1 (fr) * 1999-03-05 2000-09-08 Isogon Corporation Procede et processus de visualisation d'informations concernant l'inventaire et l'utilisation de produits logiciels correlees a des informations concernant les conventions de droits d'utilisation
WO2001016674A1 (fr) * 1999-09-02 2001-03-08 Isogon Corporation Procede et dispositif servant a mettre en correlation des informations de contrat de licence avec des configurations logicielles et materielles
US6272469B1 (en) 1998-11-25 2001-08-07 Ge Medical Systems Global Technology Company, Llc Imaging system protocol handling method and apparatus
WO2001077795A2 (fr) * 2000-04-07 2001-10-18 Viatech Technologies Inc. Systeme et mecanisme integre de controle des licences pour la creation et la distribution de fichiers numeriques et de l'application de l'utilisation autorisee des fichiers numeriques
WO2001079970A2 (fr) * 2000-04-18 2001-10-25 Isogon Corporation Procede d'administration et de gestion de permis d'utilisation de logiciel
EP1178406A1 (fr) * 2000-07-31 2002-02-06 Avaya Technology Corp. Masquage automatique des données d'identification d'un produit
EP1203336A1 (fr) * 2000-01-17 2002-05-08 Sony Computer Entertainment Inc. Procede souple de paiement de redevances destine a des systemes de commerce electronique
GB2373605A (en) * 2001-03-23 2002-09-25 Ibm Updating license information
GB2375411A (en) * 2001-03-15 2002-11-13 Hewlett Packard Co Automatic installation of licenced software components to a network server
WO2003038570A2 (fr) * 2001-10-30 2003-05-08 International Business Machines Corporation Procede et systeme informatiques permettant de reguler l'utilisation de produits a codage numerique
WO2003071404A1 (fr) * 2002-02-19 2003-08-28 Douglas Lundholm Procede et dispositif de protection d'un logiciel
FR2848692A1 (fr) * 2002-12-17 2004-06-18 Thomson Licensing Sa Dispositifs et procedes de comptabilisation et d'analyse temporelle d'evenements
US6799084B2 (en) * 1998-07-31 2004-09-28 Benjamin Filmalter Grobler Data vending system
WO2006066789A2 (fr) * 2004-12-17 2006-06-29 Abb Research Ltd. Procede d'attribution et de gestion de licence
WO2007071465A1 (fr) * 2005-12-22 2007-06-28 International Business Machines Corporation Procede et appareil pour garnir un catalogue de logiciels avec une generation automatisee de signature d'utilisation
WO2007118638A3 (fr) * 2006-04-11 2008-01-17 Giesecke & Devrient Gmbh Détection de l'utilisation de ressources
US7359882B2 (en) * 2001-05-11 2008-04-15 Bea Systems, Inc. Distributed run-time licensing
WO2008077653A2 (fr) * 2006-12-27 2008-07-03 International Business Machines Corporation Procédé, système et programme informatique pour surveiller des composants dans un cadre de service
EP2013697A1 (fr) * 2006-04-07 2009-01-14 Microsoft Corporation Morphe d'interface utilisateur fondée sur des autorisations
EP2073443A1 (fr) * 2007-04-16 2009-06-24 Huawei Technologies Co., Ltd. Système de communication, dispositif de communication et procédé de contrôle de capacité
EP2116947A1 (fr) * 2008-05-08 2009-11-11 Ricoh Company, Ltd. Dispositif de gestion d'équipements, système de gestion d'équipements, procédé de gestion d'équipements et support d'enregistrement

Families Citing this family (97)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6397195B1 (en) * 1997-06-27 2002-05-28 Hyperion Solutions Corporation System for managing accounting information in a multi-dimensional database
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
US20040117664A1 (en) * 1998-06-04 2004-06-17 Z4 Technologies, Inc. Apparatus for establishing a connectivity platform for digital rights management
US6799277B2 (en) 1998-06-04 2004-09-28 Z4 Technologies, Inc. System and method for monitoring software
US20040107368A1 (en) * 1998-06-04 2004-06-03 Z4 Technologies, Inc. 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
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
US6044471A (en) 1998-06-04 2000-03-28 Z4 Technologies, Inc. Method and apparatus for securing software to reduce unauthorized use
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
US20040117631A1 (en) * 1998-06-04 2004-06-17 Z4 Technologies, Inc. Method for digital rights management including user/publisher connectivity interface
US20040225894A1 (en) * 1998-06-04 2004-11-11 Z4 Technologies, Inc. Hardware based method for digital rights management including self activating/self authentication software
US6986063B2 (en) * 1998-06-04 2006-01-10 Z4 Technologies, Inc. Method for monitoring software using encryption including digital signatures/certificates
AU4568299A (en) * 1998-06-15 2000-01-05 Dmw Worldwide, Inc. Method and apparatus for assessing the security of a computer system
US6425023B1 (en) * 1999-03-24 2002-07-23 International Business Machines Corporation Method and system for gathering and buffering sequential data for a transaction comprising multiple data access requests
US20020019814A1 (en) * 2001-03-01 2002-02-14 Krishnamurthy Ganesan Specifying rights in a digital rights license according to events
DE60039861D1 (de) * 1999-04-20 2008-09-25 Samsung Electronics Co Ltd Werbeverwaltungssystem für digitale videoströme
US6606657B1 (en) * 1999-06-22 2003-08-12 Comverse, Ltd. System and method for processing and presenting internet usage information
US7430670B1 (en) * 1999-07-29 2008-09-30 Intertrust Technologies Corp. Software self-defense systems and methods
US7743133B1 (en) * 1999-11-16 2010-06-22 Ricoh Company, Ltd. Remote system usage monitoring with flexible encoding and decoding objects
JP2001357312A (ja) * 1999-11-24 2001-12-26 Sega Corp 情報処理装置、ファイルサーバ、課金管理システムおよび課金管理方法並びにプログラムを記録した記録媒体
EP1134643A3 (fr) * 2000-03-14 2007-01-17 Sony Corporation Appareil fournisseur d'informations et son procédé, appareil de traitement d'informations et son procédé, support d'enregistrement de programme, programme, et système fournisseur d'informations
DE10023820B4 (de) * 2000-05-15 2006-10-19 Siemens Ag Software-Schutzmechanismus
US20070043675A1 (en) * 2000-05-15 2007-02-22 Siemens Aktiengesellschaft Software license manager
DE10023827A1 (de) * 2000-05-15 2001-12-06 Siemens Ag Lizenzierung und Zugangsauthorisierung
US8086697B2 (en) * 2005-06-28 2011-12-27 Claria Innovations, Llc Techniques for displaying impressions in documents delivered over a computer network
US7475404B2 (en) 2000-05-18 2009-01-06 Maquis Techtrix Llc System and method for implementing click-through for browser executed software including ad proxy and proxy cookie caching
WO2001092993A2 (fr) * 2000-06-02 2001-12-06 Vigilant Systems, Inc. Systeme et procede de gestion d'octroi de licence
AU2001271291A1 (en) * 2000-06-07 2001-12-17 Quark Media House Sarl System for software license control and method therefore
DE10032015A1 (de) * 2000-07-01 2002-01-10 Roche Diagnostics Gmbh Testelement-Analysegerät
US20020078217A1 (en) * 2000-07-28 2002-06-20 Jonathan Thomas Online alcoholic beverage license verification system
JP2002049435A (ja) * 2000-08-03 2002-02-15 Naretsuji Moderingu Kenkyusho:Kk ライセンス管理方法及び装置
US20020069098A1 (en) * 2000-08-31 2002-06-06 Infoseer, Inc. System and method for protecting proprietary material on computer networks
US6857067B2 (en) * 2000-09-01 2005-02-15 Martin S. Edelman System and method for preventing unauthorized access to electronic data
AU2001294555A1 (en) * 2000-09-14 2002-03-26 Bea Systems Inc. Xml-based graphical user interface application development toolkit
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
US20020038269A1 (en) * 2000-09-25 2002-03-28 Kazuya Nishino Accounting method
US20020083003A1 (en) * 2000-09-26 2002-06-27 Halliday David C. Method and apparatus for the accurate metering of software application usage and the reporting of such usage to a remote site on a public network
US6556926B1 (en) * 2000-10-16 2003-04-29 Hewlett-Packard Development Co., L.P. System for determining when a component in a printer should be replaced
US7197466B1 (en) 2000-11-02 2007-03-27 General Electric Capital Corporation Web-based system for managing software assets
US20030046395A1 (en) * 2000-12-12 2003-03-06 Robert Fleming System and method for bounding the life of an event subscription to the availability of an object
JP4185363B2 (ja) * 2001-02-22 2008-11-26 ビーイーエイ システムズ， インコーポレイテッド トランザクション処理システムにおけるメッセージ暗号化及び署名のためのシステム及び方法
JP2004528631A (ja) * 2001-02-28 2004-09-16 ミュージックレベリオン．コム・インコーポレーテッド デジタルオンライン交換
US7472104B2 (en) * 2001-03-13 2008-12-30 Sony Corporation Method and system for distributing product information
JP2002318971A (ja) * 2001-04-23 2002-10-31 Dainippon Screen Mfg Co Ltd 機能別課金のための方法および装置
US20030065670A1 (en) * 2001-04-25 2003-04-03 Michel Bisson Personalization server unified user profile
US7505936B2 (en) * 2001-05-11 2009-03-17 Accenture Global Services Gmbh Digital content subscription conditioning system
US7185105B2 (en) * 2001-05-11 2007-02-27 Bea Systems, Inc. Application messaging system with flexible message header structure
KR20010079081A (ko) * 2001-06-12 2001-08-22 전용옥 소프트웨어 무단복제 단속을 위한 대행업체의 단속 방법
US7895123B1 (en) 2001-06-12 2011-02-22 Accenture Global Services Limited Digital content publication
US7143409B2 (en) 2001-06-29 2006-11-28 International Business Machines Corporation Automated entitlement verification for delivery of licensed software
US7249139B2 (en) * 2001-07-13 2007-07-24 Accenture Global Services Gmbh Secure virtual marketplace for virtual objects and services
DE60216940T2 (de) * 2001-08-01 2007-07-05 Matsushita Electric Industrial Co., Ltd., Kadoma Einrichtung und verfahren zur verwaltung des inhaltsbenutzungsrechts
US20030084060A1 (en) * 2001-11-01 2003-05-01 Arun Ramachandran Process in a usage based licensing server to convert metric data in data structure to CSU data
US20030130953A1 (en) * 2002-01-09 2003-07-10 Innerpresence Networks, Inc. Systems and methods for monitoring the presence of assets within a system and enforcing policies governing assets
CA2371985C (fr) * 2002-02-15 2015-12-29 Teranet Enterprises Inc. Methode et systeme d'elaboration de structures de prix de produits et services complexes
JP3697247B2 (ja) * 2002-04-22 2005-09-21 キヤノン株式会社 情報処理装置及び監視方法及びプログラム並びに記憶媒体
CA2485053A1 (fr) * 2002-05-10 2003-11-20 Protexis Inc. Systeme et procede de gestion et de delivrance de licenses a plusieurs niveaux faisant intervenir des chambres de compensation en reseau
US7552205B2 (en) * 2002-05-21 2009-06-23 Accenture Global Services Gmbh Distributed transaction event matching
US20040068667A1 (en) * 2002-10-03 2004-04-08 International Business Machines Corporation Method and apparatus for securing and managing cluster computing in a network data processing system
US20060155711A1 (en) * 2002-11-05 2006-07-13 Jackson Wayne A Method and system for management of software product licences
US7603341B2 (en) 2002-11-05 2009-10-13 Claria Corporation Updating the content of a presentation vehicle in a computer network
JP4082251B2 (ja) * 2003-03-18 2008-04-30 マックス株式会社 ステープラーのクリンチャ装置
JP2004302685A (ja) * 2003-03-28 2004-10-28 Ricoh Co Ltd 管理システム、機器管理装置および保守作業指示方法
US8898657B2 (en) 2003-10-03 2014-11-25 Cyberlink Corp. System and method for licensing software
US20050114266A1 (en) * 2003-11-26 2005-05-26 Lingan Satkunanathan System and method for managing licenses using interactive wizards
US20050114265A1 (en) * 2003-11-26 2005-05-26 Lingan Satkunanathan Real-time license enforcement system and method
US7770034B2 (en) * 2003-12-16 2010-08-03 Intel Corporation Performance monitoring based dynamic voltage and frequency scaling
US8255413B2 (en) 2004-08-19 2012-08-28 Carhamm Ltd., Llc Method and apparatus for responding to request for information-personalization
US8078602B2 (en) 2004-12-17 2011-12-13 Claria Innovations, Llc Search engine for a computer network
US7693863B2 (en) 2004-12-20 2010-04-06 Claria Corporation Method and device for publishing cross-network user behavioral data
US20060174346A1 (en) * 2005-01-31 2006-08-03 Lieberman Software Corporation Instrumentation for alarming a software product
US8645941B2 (en) * 2005-03-07 2014-02-04 Carhamm Ltd., Llc Method for attributing and allocating revenue related to embedded software
WO2006096700A2 (fr) * 2005-03-07 2006-09-14 Claria Corporation Procede de quantification de propension a repondre a une annonce
US8073866B2 (en) 2005-03-17 2011-12-06 Claria Innovations, Llc Method for providing content to an internet user based on the user's demonstrated content preferences
US8494966B2 (en) 2005-06-03 2013-07-23 Adobe Systems Incorporated Method and apparatus for facilitating the transfer of a software license between computer systems
WO2007002728A2 (fr) * 2005-06-28 2007-01-04 Claria Corporation Procede et systeme pour reguler et adapter un flux multimedia
US20070192641A1 (en) * 2006-02-10 2007-08-16 Intel Corporation Method and apparatus to manage power consumption in a computer
US20080148253A1 (en) * 2006-12-15 2008-06-19 Microsoft Corporation Automatic software license reconciliation
DE102007016200A1 (de) * 2007-04-02 2008-10-09 Deutsche Telekom Ag Verfahren und System zur Durchführung eines Lizenzmanagements mittels eines Telekommunikationsnetzwerks
US8607226B2 (en) * 2008-01-22 2013-12-10 International Business Machines Corporation Solution for locally staged electronic software distribution using secure removable media
US10346835B1 (en) 2008-10-07 2019-07-09 United Services Automobile Association (Usaa) Systems and methods for presenting recognizable bank account transaction descriptions compiled through customer collaboration
CN102257528A (zh) * 2008-10-20 2011-11-23 贝阳奥林公司 用于对下载交易和社会网络交互进行计费的方法和系统
US8401925B1 (en) 2010-01-26 2013-03-19 Hewlett-Packard Development Company, L.P. Multi-product software license selection
US9230273B2 (en) 2010-07-28 2016-01-05 International Business Machines Corporation Creation and use of constraint templates
US9122998B2 (en) 2010-07-28 2015-09-01 International Business Machines Corporation Catalog-based software license reconciliation
US8984293B2 (en) 2010-11-19 2015-03-17 Microsoft Corporation Secure software product identifier for product validation and activation
US8775797B2 (en) 2010-11-19 2014-07-08 Microsoft Corporation Reliable software product validation and activation with redundant security
US8683579B2 (en) * 2010-12-14 2014-03-25 Microsoft Corporation Software activation using digital licenses
US8839101B2 (en) * 2011-01-07 2014-09-16 General Electric Company Flexible meter configuration software architecture
US8577809B2 (en) * 2011-06-30 2013-11-05 Qualcomm Incorporated Method and apparatus for determining and utilizing value of digital assets
KR20140050323A (ko) * 2012-10-19 2014-04-29 삼성전자주식회사 라이선스 검증 방법 및 그 장치
US10694352B2 (en) 2015-10-28 2020-06-23 Activision Publishing, Inc. System and method of using physical objects to control software access
US10861079B2 (en) 2017-02-23 2020-12-08 Activision Publishing, Inc. Flexible online pre-ordering system for media
US10977361B2 (en) 2017-05-16 2021-04-13 Beyondtrust Software, Inc. Systems and methods for controlling privileged operations
US10621313B2 (en) 2017-10-04 2020-04-14 Servicenow, Inc. Distribution and enforcement of per-feature-set software application licensing
GB2584018B (en) 2019-04-26 2022-04-13 Beyondtrust Software Inc Root-level application selective configuration
US11900674B2 (en) 2021-07-08 2024-02-13 Bank Of America Corporation System for real-time identification of unauthorized access

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
GB2236604A (en) * 1989-10-02 1991-04-10 Sun Microsystems Inc Protecting against the unauthorised use of software in a computer network
US5023907A (en) * 1988-09-30 1991-06-11 Apollo Computer, Inc. Network license server

Family Cites Families (23)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US2883255A (en) * 1954-04-28 1959-04-21 Panellit Inc Automatic process logging system
US3351910A (en) * 1964-08-05 1967-11-07 Communitron Inc Apparatus for collecting and recording data
US3540003A (en) * 1968-06-10 1970-11-10 Ibm Computer monitoring system
US3906454A (en) * 1973-05-18 1975-09-16 Bell Telephone Labor Inc Computer monitoring system
US4740890A (en) * 1983-12-22 1988-04-26 Software Concepts, Inc. Software protection system with trial period usage code and unlimited use unlocking code both recorded on program storage media
US4821178A (en) * 1986-08-15 1989-04-11 International Business Machines Corporation Internal performance monitoring by event sampling
US4858152A (en) * 1987-01-23 1989-08-15 International Business Machines Corp. Operator access to monitoring applications
US5390297A (en) * 1987-11-10 1995-02-14 Auto-Trol Technology Corporation System for controlling the number of concurrent copies of a program in a network based on the number of available licenses
US4937863A (en) * 1988-03-07 1990-06-26 Digital Equipment Corporation Software licensing management system
US4924378A (en) * 1988-06-13 1990-05-08 Prime Computer, Inc. License mangagement system and license storage key
EP0444315B1 (fr) * 1990-02-26 1997-10-01 Digital Equipment Corporation Système et procédé pour recueillir des évènements d'applications de logiciel
US5204897A (en) * 1991-06-28 1993-04-20 Digital Equipment Corporation Management interface for license management system
US5260999A (en) * 1991-06-28 1993-11-09 Digital Equipment Corporation Filters in license management system
US5438508A (en) * 1991-06-28 1995-08-01 Digital Equipment Corporation License document interchange format for license management system
JPH0815277B2 (ja) * 1991-08-09 1996-02-14 インターナショナル・ビジネス・マシーンズ・コーポレイション パフォーマンス測定値を得るためのシステムおよび方法
US5343526A (en) * 1992-10-30 1994-08-30 At&T Bell Laboratories Method for establishing licensor changeable limits on software usage
US5386369A (en) * 1993-07-12 1995-01-31 Globetrotter Software Inc. License metering system for software applications
US5475753A (en) * 1993-11-12 1995-12-12 Matsushita Electric Corporation Of America Apparatus and method for certifying the delivery of information
US5499340A (en) * 1994-01-12 1996-03-12 Isogon Corporation Method and apparatus for computer program usage monitoring
US5528753A (en) * 1994-06-30 1996-06-18 International Business Machines Corporation System and method for enabling stripped object software monitoring in a computer system
US5852812A (en) * 1995-08-23 1998-12-22 Microsoft Corporation Billing system for a network
US5790664A (en) * 1996-02-26 1998-08-04 Network Engineering Software, Inc. Automated system for management of licensed software
US5898777A (en) * 1996-03-07 1999-04-27 Portland Software, Inc. Digital product dissemination and sale

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5023907A (en) * 1988-09-30 1991-06-11 Apollo Computer, Inc. Network license server
GB2236604A (en) * 1989-10-02 1991-04-10 Sun Microsystems Inc Protecting against the unauthorised use of software in a computer network

Cited By (44)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6799084B2 (en) * 1998-07-31 2004-09-28 Benjamin Filmalter Grobler Data vending system
US6988074B2 (en) * 1998-11-25 2006-01-17 Ge Medical Systems Global Technology Company, Llc Imaging system protocol handling method and apparatus
US6901371B1 (en) 1998-11-25 2005-05-31 Ge Medical Systems Global Technology Company, Llc Imaging system protocol handling method and apparatus
US6272469B1 (en) 1998-11-25 2001-08-07 Ge Medical Systems Global Technology Company, Llc Imaging system protocol handling method and apparatus
EP1006447A2 (fr) * 1998-11-30 2000-06-07 General Electric Company Surveillance à distance de cartes électroniques/routines de logiciel
EP1006447A3 (fr) * 1998-11-30 2001-09-19 General Electric Company Surveillance à distance de cartes électroniques/routines de logiciel
US10049192B2 (en) 1999-03-05 2018-08-14 International Business Machines Corporation Software product inventory and usage information correlated with license agreement information
WO2000052559A1 (fr) * 1999-03-05 2000-09-08 Isogon Corporation Procede et processus de visualisation d'informations concernant l'inventaire et l'utilisation de produits logiciels correlees a des informations concernant les conventions de droits d'utilisation
WO2001016674A1 (fr) * 1999-09-02 2001-03-08 Isogon Corporation Procede et dispositif servant a mettre en correlation des informations de contrat de licence avec des configurations logicielles et materielles
EP1203336A1 (fr) * 2000-01-17 2002-05-08 Sony Computer Entertainment Inc. Procede souple de paiement de redevances destine a des systemes de commerce electronique
EP1203336A4 (fr) * 2000-01-17 2004-11-03 Sony Computer Entertainment Inc Procede souple de paiement de redevances destine a des systemes de commerce electronique
WO2001077795A2 (fr) * 2000-04-07 2001-10-18 Viatech Technologies Inc. Systeme et mecanisme integre de controle des licences pour la creation et la distribution de fichiers numeriques et de l'application de l'utilisation autorisee des fichiers numeriques
WO2001077795A3 (fr) * 2000-04-07 2003-01-03 Viatech Technologies Inc Systeme et mecanisme integre de controle des licences pour la creation et la distribution de fichiers numeriques et de l'application de l'utilisation autorisee des fichiers numeriques
WO2001079970A2 (fr) * 2000-04-18 2001-10-25 Isogon Corporation Procede d'administration et de gestion de permis d'utilisation de logiciel
WO2001079970A3 (fr) * 2000-04-18 2003-07-10 Isogon Corp Procede d'administration et de gestion de permis d'utilisation de logiciel
EP1178406A1 (fr) * 2000-07-31 2002-02-06 Avaya Technology Corp. Masquage automatique des données d'identification d'un produit
GB2375411B (en) * 2001-03-15 2005-08-31 Hewlett Packard Co System and method for installing a software product on a network server device
GB2375411A (en) * 2001-03-15 2002-11-13 Hewlett Packard Co Automatic installation of licenced software components to a network server
GB2373605A (en) * 2001-03-23 2002-09-25 Ibm Updating license information
US7069595B2 (en) 2001-03-23 2006-06-27 International Business Machines Corporation Method of controlling use of digitally encoded products
GB2373605B (en) * 2001-03-23 2005-04-27 Ibm A method of metering use of digitally encoded products
US7359882B2 (en) * 2001-05-11 2008-04-15 Bea Systems, Inc. Distributed run-time licensing
US7536356B2 (en) 2001-05-11 2009-05-19 Bea Systems, Inc. Distributed run-time licensing
US7661147B2 (en) 2001-10-30 2010-02-09 International Business Machines Corporation System for controlling use of digitally encoded products
WO2003038570A3 (fr) * 2001-10-30 2004-02-05 Ibm Procede et systeme informatiques permettant de reguler l'utilisation de produits a codage numerique
US7376971B2 (en) 2001-10-30 2008-05-20 International Business Machines Corporation Computer implemented method and system for controlling use of digitally encoded products
WO2003038570A2 (fr) * 2001-10-30 2003-05-08 International Business Machines Corporation Procede et systeme informatiques permettant de reguler l'utilisation de produits a codage numerique
WO2003071404A1 (fr) * 2002-02-19 2003-08-28 Douglas Lundholm Procede et dispositif de protection d'un logiciel
FR2848692A1 (fr) * 2002-12-17 2004-06-18 Thomson Licensing Sa Dispositifs et procedes de comptabilisation et d'analyse temporelle d'evenements
WO2004055673A1 (fr) * 2002-12-17 2004-07-01 Thomson Licensing S.A. Dispositifs et procédés de comptabilisation et d'analyse temporelle d'événements
WO2006066789A2 (fr) * 2004-12-17 2006-06-29 Abb Research Ltd. Procede d'attribution et de gestion de licence
WO2006066789A3 (fr) * 2004-12-17 2006-10-26 Abb Research Ltd Procede d'attribution et de gestion de licence
WO2007071465A1 (fr) * 2005-12-22 2007-06-28 International Business Machines Corporation Procede et appareil pour garnir un catalogue de logiciels avec une generation automatisee de signature d'utilisation
US8521865B2 (en) 2005-12-22 2013-08-27 International Business Machines Corporation Method and apparatus for populating a software catalog with automated use signature generation
EP2013697A1 (fr) * 2006-04-07 2009-01-14 Microsoft Corporation Morphe d'interface utilisateur fondée sur des autorisations
EP2013697A4 (fr) * 2006-04-07 2011-01-26 Microsoft Corp Morphe d'interface utilisateur fondée sur des autorisations
WO2007118638A3 (fr) * 2006-04-11 2008-01-17 Giesecke & Devrient Gmbh Détection de l'utilisation de ressources
WO2008077653A3 (fr) * 2006-12-27 2011-02-03 International Business Machines Corporation Procédé, système et programme informatique pour surveiller des composants dans un cadre de service
WO2008077653A2 (fr) * 2006-12-27 2008-07-03 International Business Machines Corporation Procédé, système et programme informatique pour surveiller des composants dans un cadre de service
US9632897B2 (en) 2006-12-27 2017-04-25 International Business Machines Corporation Monitoring components in a service framework
US11327816B2 (en) 2006-12-27 2022-05-10 International Business Machines Corporation Monitoring components in a service framework
EP2073443A1 (fr) * 2007-04-16 2009-06-24 Huawei Technologies Co., Ltd. Système de communication, dispositif de communication et procédé de contrôle de capacité
EP2073443A4 (fr) * 2007-04-16 2010-02-24 Huawei Tech Co Ltd Système de communication, dispositif de communication et procédé de contrôle de capacité
EP2116947A1 (fr) * 2008-05-08 2009-11-11 Ricoh Company, Ltd. Dispositif de gestion d'équipements, système de gestion d'équipements, procédé de gestion d'équipements et support d'enregistrement

Also Published As

Publication number Publication date
US6029145A (en) 2000-02-22
EP0852349A3 (fr) 1999-06-16

Similar Documents

Publication Publication Date Title
US6029145A (en) Software license verification process and apparatus
US5499340A (en) Method and apparatus for computer program usage monitoring
US6938027B1 (en) Hardware/software management, purchasing and optimization system
US6049670A (en) Identifier managing device and method in software distribution system
US6014651A (en) Commercial online software distribution systems and methods using encryption for security
US8655785B2 (en) Computer data product license installation / update confirmation
US10049192B2 (en) Software product inventory and usage information correlated with license agreement information
CN101151593B (zh) 自治计算：利用动作策略进行操作的管理代理
US5023907A (en) Network license server
US10101973B1 (en) Adaptively shrinking software
US8321554B2 (en) System and program to automatically identify a server on which to deploy an application
US7143067B1 (en) System and method for installing personal computer software
CN100487626C (zh) 用于控制数字编码产品使用的计算机实现方法和系统
US8321352B1 (en) Fingerprinting for software license inventory management
US5479612A (en) Automated system and method to discourage access of unlicensed peripheral devices by a computer system
CN101485129A (zh) 强制的基于席位的许可
US20070055641A1 (en) Method and apparatus for providing a reward for the use of a processor in a parallel processing environment
CN106897096B (zh) Java商店
WO2002093300A2 (fr) Systeme de determination du montant des redevances respectives pour l'acces a un contenu numerique
WO2009055040A1 (fr) Marquage logiciel sécurisé dynamique pour la gestion d'actifs logiciels logicielle en ce qui concerne le déploiement, la configuration et l'utilisation
US7600228B2 (en) Information processing device and information processing terminal
US20070271162A1 (en) Invoice Management For Distributed Content
US20020032664A1 (en) Accounting system, accounting method, content executing device, accounting monitoring device, accounting control device and recording medium
US20050149447A1 (en) Method and apparatus to estimate software charges and analyze computer operating logs
US20070067260A1 (en) System, method and program to assess value of a computer program to a company

Legal Events

Date Code Title Description
PUAI Public reference made under article 153(3) epc to a published international application that has entered the european phase

Free format text: ORIGINAL CODE: 0009012

AK Designated contracting states

Kind code of ref document: A2

Designated state(s): AT BE CH DE DK ES FR GB GR IE IT LI NL SE

AX Request for extension of the european patent

Free format text: AL;LT;LV;MK;RO;SI

PUAL Search report despatched

Free format text: ORIGINAL CODE: 0009013

AK Designated contracting states

Kind code of ref document: A3

Designated state(s): AT BE CH DE DK ES FI FR GB GR IE IT LI LU MC NL PT SE

AX Request for extension of the european patent

Free format text: AL;LT;LV;MK;RO;SI

17P Request for examination filed

Effective date: 19991216

AKX Designation fees paid

Free format text: AT BE CH DE DK ES FR GB GR IE IT LI NL SE

17Q First examination report despatched

Effective date: 20020704

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: THE APPLICATION IS DEEMED TO BE WITHDRAWN

18D Application deemed to be withdrawn

Effective date: 20050811