New! View global litigation for patent families

US20050102240A1 - System and method for software licensing - Google Patents

System and method for software licensing Download PDF

Info

Publication number
US20050102240A1
US20050102240A1 US11016641 US1664104A US2005102240A1 US 20050102240 A1 US20050102240 A1 US 20050102240A1 US 11016641 US11016641 US 11016641 US 1664104 A US1664104 A US 1664104A US 2005102240 A1 US2005102240 A1 US 2005102240A1
Authority
US
Grant status
Application
Patent type
Prior art keywords
license
client
server
software
id
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.)
Granted
Application number
US11016641
Other versions
US7809648B2 (en )
Inventor
Pradyumna Misra
Bradley Graziadio
Terence Spies
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.)
Microsoft Technology Licensing LLC
Original Assignee
Microsoft 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

Links

Images

Classifications

    • GPHYSICS
    • G06COMPUTING; CALCULATING; COUNTING
    • G06QDATA PROCESSING SYSTEMS OR METHODS, SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL, SUPERVISORY OR FORECASTING PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL, SUPERVISORY OR FORECASTING PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q30/00Commerce, e.g. shopping or e-commerce
    • G06Q30/06Buying, selling or leasing transactions
    • GPHYSICS
    • G06COMPUTING; CALCULATING; COUNTING
    • G06QDATA PROCESSING SYSTEMS OR METHODS, SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL, SUPERVISORY OR FORECASTING PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL, SUPERVISORY OR FORECASTING PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q30/00Commerce, e.g. shopping or e-commerce
    • G06Q30/06Buying, selling or leasing transactions
    • G06Q30/0601Electronic shopping
    • G06Q30/0633Lists, e.g. purchase orders, compilation or processing
    • GPHYSICS
    • G06COMPUTING; CALCULATING; COUNTING
    • G06QDATA PROCESSING SYSTEMS OR METHODS, SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL, SUPERVISORY OR FORECASTING PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL, SUPERVISORY OR FORECASTING PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q50/00Systems or methods specially adapted for a specific business sector, e.g. utilities or tourism
    • G06Q50/10Services
    • G06Q50/18Legal services; Handling legal documents
    • G06Q50/184Intellectual property management

Abstract

A software licensing system includes a license generator located at a licensing clearinghouse and at least one license server and multiple clients located at a company or entity. When a company wants a software license, it sends a purchase request (and appropriate fee) to the licensing clearinghouse. The license generator at the clearinghouse creates a license pack containing a set of one or more individual software licenses. The license generator digitally signs the license pack and encrypts it with the license server's public key. The license server is responsible for distributing the software licenses from the license pack to individual clients. When a client needs a license, the license server determines the client's operating system platform and grants the appropriate license. The license server digitally signs the software license and encrypts it using the client's public key. The license is stored locally at the client.

Description

    RELATED APPLICATIONS
  • [0001]
    This application is a continuation of U.S. patent application Ser. No. 09/724,703, filed Nov. 28, 2000, which is hereby incorporated by reference herein. U.S. patent application Ser. No. 09/724,703 is a continuation of U.S. patent application Ser. No. 09/040,813, filed Mar. 18, 1998, now U.S. Pat. No. 6,189,146.
  • TECHNICAL FIELD
  • [0002]
    This invention relates to systems and methods for licensing software. This invention further relates to systems and methods for enforcing software licenses.
  • BACKGROUND
  • [0003]
    Software licensing has historically been based on a “trust” model in which the user (i.e., licensee) is presumed to be honest and trustworthy and to abide by the legal requirements of the license. Under the trust model, a software license typically accompanies a software product to explain the terms of use. For instance, the software license might dictate that the program code is to be installed on only one computer, and may be used to make one backup copy.
  • [0004]
    Common types of licenses include “shrink wrap” licenses, “online” licenses, and “site” licenses. A “shrink wrap” license is a license that accompanies each software product that is sold individually in a shrink-wrapped package through retail stores. The user is typically assumed to accept the terms of the shrink wrap license upon breaking the seal of the package, or the container that holds the disk itself.
  • [0005]
    An “online” license is one that accompanies software products that are downloaded online, such as from the Internet. The license is typically presented to the user prior to downloading the code. The user is presented with a choice to accept or reject the license. If the user accepts the license (e.g., by clicking an “Accept” button on the screen), the user is presumed to have accepted the terms of the license and the code is downloaded to the user's computer.
  • [0006]
    A “site” license is a single license that allows installation of multiple copies of software on many different computers at a particular site or many sites. It is commonly used to sell software to corporations, firms, or other entities having many computers. The purchaser pays for a certain number of copies (e.g., hundreds or thousands), and the site license enables the purchaser to install that many copies on its computers. The site license is beneficial because the software vendor need not supply a large number of program disks, but merely supplies one or a few copies of the software and lets the purchaser install the copies without is violating the agreement.
  • [0007]
    Each of the above license arrangements assumes that the purchaser is honest. The software purchaser must abide by the license terms in order to legally use the software. If the purchaser fails to abide by the provisions, the purchaser can be charged with civil and criminal violations.
  • [0008]
    However, enforcement of such licenses is impractical, if not impossible. Unscrupulous users might make multiple copies of the software code and install it on more computers than the license allows. Yet, software vendors cannot begin to monitor these abuses because they occur in the privacy of the home or company. Thus, it is believed that the software industry loses a large percentage of revenues each year simply due to illegitimate use of software by the licensees. This loss does not even account for the problems of overseas pirating.
  • [0009]
    Another problem with conventional software licensing practices concerns internal monitoring and bookkeeping on the part of large-site licensees. In most cases, the licensees want to comply with the terms of the software licenses, but are unable to adequately track the software as it is used throughout the site. For example, a large corporation might purchase several thousand copies of the software and begin installing the copies. However, computers and personnel change over time and it is difficult to centrally monitor how many copies have been installed, whether the copies have expired, whether they need upgrading, and so forth.
  • [0010]
    Accordingly, there is a need to develop a new approach to licensing software in a manner that assures that the terms are being meet and assists the licensee with monitoring whether it is in compliance with the software license.
  • SUMMARY
  • [0011]
    This invention concerns a system and method for licensing software. The system and method provides confidence to the vendor that the software license is being complied with, while also assisting the purchaser in monitoring its own compliance with the license.
  • [0012]
    According to one aspect of this invention, computer software licenses are electronically issued as digital certificates that can be distributed in one-to-one correlation with individual client computers and traced to an issuing authority.
  • [0013]
    According to another aspect, the system includes a license generator located at a licensing clearinghouse and at least one license server and multiple clients located at or affiliated with a company or other entity. Because the clients might not have network connectivity to the license server, one or more intermediate servers may act as an intermediary for the clients. These intermediate servers are otherwise common servers that provide resources to clients, but with the added ability to facilitate connectivity to the license server for purposes of distributing software licenses to the clients.
  • [0014]
    When a company wants a software license, it sends a purchase request (and an appropriate fee) to the licensing clearinghouse. The license generator at the licensing clearinghouse creates a license pack containing a set of one or more individual software licenses. To prevent the license pack from being copied and installed on multiple license servers, the license generator assigns a unique license pack ID to the license pack and associates the license pack ID with the license server in a master license database kept at the licensing clearinghouse. The license generator also digitally signs the license pack and encrypts it with the license server's public key. The license generator sends the license pack to the license server using standard communications, such as over a data communication network (e.g., Internet) or via a portable data medium (e.g., floppy diskette, CD-ROM, etc.).
  • [0015]
    The license server verifies the license generator's digital signature on the license pack and if valid, installs the license pack for subsequent distribution of licenses. The license server maintains an inventory of software licenses that have been purchased from the licensing clearinghouse. The license server is responsible for distributing the software licenses contained in the license pack to individual clients. It monitors the software licenses that have been granted to clients and continues to distribute licenses as long as non-assigned licenses remain available. Once the supply of non-assigned licenses is exhausted, however, the license server can no longer grant licenses to the clients and the customer must purchase a new pack from the license clearinghouse.
  • [0016]
    When a client connects to a server, the client presents a valid license (if it has one). If the client does not have an appropriate license, the server assists the client in obtaining a license from the license server. This provides an automated mechanism for clients to obtain and license server to distribute licenses to clients.
  • [0017]
    When a license is requested, the license server initially checks if the requesting client has already been issued a license. When this situation is detected, the license server issues the existing license to the client. This is actually reissuing of the same license that was previously issued. This allows the client to gracefully recover licenses when they are lost.
  • [0018]
    In one implementation, the license server determines an appropriate type of license based in part on the client's operating system platform. The license server derives the platform information by establishing a trust relationship with the client and then querying its platform type. If a software license is available for allocation, the license server grants a software license that is appropriate for the client's platform.
  • [0019]
    To prevent an issued license from being copied from one client machine to another, the software license is assigned to a specific client by including its client ID within the license. The software license also has a corresponding license ID that is associated with the client ID in a database record kept at the license server.
  • [0020]
    The license server digitally signs the software license. The license is passed to the client, where it is stored in a local cache at the client. Once a client has obtained a license, it is responsible for managing the storage of that license.
  • BRIEF DESCRIPTION OF THE DRAWINGS
  • [0021]
    The same reference numbers are used throughout the drawings to reference like components and features.
  • [0022]
    FIG. 1 shows a software licensing system.
  • [0023]
    FIG. 2 shows a block diagram of a computer used to implement the software licensing system.
  • [0024]
    FIG. 3 shows a functional block diagram showing software components and databases that implement the software licensing system.
  • [0025]
    FIG. 4 shows steps in a method for issuing a license pack of individual licenses.
  • [0026]
    FIG. 5 shows steps in a method for initiating a connection between a client and a server and determining whether the client has a valid license.
  • [0027]
    FIG. 6 shows steps in a method for distributing a software license to a client.
  • [0028]
    FIG. 7 shows steps in a method for challenging a client prior to granting a software license to that client.
  • [0029]
    FIG. 8 shows steps in a method for upgrading a software license.
  • DETAILED DESCRIPTION
  • [0030]
    The following discussion assumes that the reader is familiar with public key cryptography. For a basic introduction to cryptography, the reader is directed to a text written by Bruce Schneier and entitled, “Applied Cryptography: Protocols, Algorithms, and Source Code in C,” published by John Wiley & Sons, copyright 1994 (second edition 1996), which is hereby incorporated by reference.
  • [0031]
    FIG. 1 shows a system 20 for licensing software. The system 20 has a licensing clearinghouse 22 that creates and issues valid software licenses to one or more companies, firms, agencies, or other entities, as represented by company 24. The clearinghouse 22 is a separate entity from the company 24. Examples of the clearinghouse include a software manufacturer, a software vendor, or a third party agent that is authorized to issue software licenses on behalf of the software manufacturer or vendor.
  • [0032]
    The company 24 contacts the clearinghouse 22 when it desires to purchase a software license to run software on the company computers. The clearinghouse 22 has a license generator 26 that creates a “license pack” containing a set of one or more individual software licenses. The clearinghouse 22 encrypts the license pack using the destination license server's public key and digitally signs the license pack with a digital signature unique to the clearinghouse.
  • [0033]
    The company 24 has at least one designated license server 28. The license pack is sent to the company 24 using standard communications, such as over a data communication network (e.g., Internet) or via a portable data medium (e.g., floppy diskette, CD-ROM, etc.), and installed on the license server 28.
  • [0034]
    The license server 28 is responsible for distributing the software licenses contained in the license pack to individual clients, as represented by clients 30(1)-30(6). The license server 28 verifies the license generator's digital signature on the license pack, decrypts the contents of the license pack, and stores the individual software licenses for subsequent distribution to individual clients.
  • [0035]
    The license server 28 maintains an inventory of software licenses that have been purchased from the licensing clearinghouse 22. The license server 28 monitors the software licenses that have been granted to clients. The license server 28 can distribute licenses to new clients as long as it has available non-assigned licenses. Once the supply of non-assigned licenses is exhausted, however, the license server 28 can no longer grant licenses to the clients. The only way for the license server 28 to obtain new non-assigned licenses is to purchase a license pack from the clearinghouse 22.
  • [0036]
    Because the clients might not have network connectivity to the license server 28, one or more intermediate servers, as represented by servers 32(1) and 32(2), can act as an intermediary for the clients. Each intermediate server 32 is a common server that provides conventional resources to the clients. In addition, each intermediate server 32 has network connectivity to the license server 28 to facilitate license distribution from the license server 28 to the clients 30. The intermediate servers 32 accept software licenses issued by the license server 28; therefore, the intermediate server associations determine the scope of the license pack to a particular license server.
  • [0037]
    The clients 30 may be directly coupled to the intermediate servers 32 via a LAN (local access network) or WAN (wide area network), as represented by clients 30(1)-30(4). Additionally, the clients 30 may be indirectly coupled to the intermediate servers 32, such as using a dialup connection as represented by clients 30(5) and 30(6).
  • [0038]
    When a client 30 connects to the intermediate server 32, it must present a valid license. If the client does not have an appropriate license, the intermediate server 32 assists the client in obtaining a license from the license server 28. This provdes an automated mechanism for distributing licenses to clients. The license server 28 initially checks if the requesting client already has been issued a license. When this situation is detected, the license server 28 issues the existing license to the client. This allows the client to gracefully recover licenses when they are lost.
  • [0039]
    In one particular implementation, the license server 28 determines an appropriate type of license based in part on the client's platform operating system type. The license server 28 derives the platform information by establishing a trust relationship with the client 30 and then querying its platform type. Once a client 30 has obtained a license, it is responsible for managing the storage of that license. The platform challenge process is described below in more detail.
  • [0000]
    Exemplary Computer Used to Implement Servers and/or Client
  • [0040]
    The license generator 26, license server 28, and intermediate server 32 are preferably implemented as computer servers, such as Windows NT servers that run Windows NT server operating systems from Microsoft Corporation or UNIX-based servers. It is noted, however, that the license generator 26 and license server 28 may be implemented using other technologies, including mainframe technologies, as long as they share an inter-operable communication mechanism like remote procedure call (RPC) and these systems are secure.
  • [0041]
    The clients 30 can be implemented as many different kinds of computers, including a desktop personal computer, a workstation, a laptop computer, a notebook computer, a handheld PC, and so forth. The clients 30 may further represent a terminal device, which is a low cost machine with limited local processing and local memory. The terminal device includes a display, a keyboard, a mouse (optional), limited computer resources like memory, and enough intelligence to connect to an intermediate server. All applications run at the server. The terminal merely provides a connection point to the server-based processing.
  • [0042]
    The clients 30 might also represent a network-centric computer, such as a Network Computer (or NC) or a Net PC.
  • [0043]
    FIG. 2 shows an example implementation of a computer 40, which can be used to implement the license generator 26, license server 28, and intermediate server 32. The server 40 includes a processing unit 42, a system memory 44, and a system bus 46 that interconnects various system components, including the system memory 44 to the processing unit 42. The system bus 46 may be implemented as any one of several bus structures and using any of a variety of bus architectures, including a memory bus or memory controller, a peripheral bus, and a local bus.
  • [0044]
    The system memory 44 includes read only memory (ROM) 48 and random access memory (RAM) 50. A basic input/output system 52 (BIOS) is stored in ROM 48.
  • [0045]
    The computer 40 has one or more of the following drives: a hard disk drive 54 for reading from and writing to a hard disk or hard disk array, a magnetic disk drive 56 for reading from or writing to a removable magnetic disk 58, and an optical disk drive 60 for reading from or writing to a removable optical disk 62 17 such as a CD ROM or other optical media. The hard disk drive 54, magnetic disk drive 56, and optical disk drive 60 are connected to the system bus 46 by a hard disk drive interface 64, a magnetic disk drive interface 66, and an optical drive interface 68, respectively. The drives and their associated computer-readable media provide nonvolatile storage of computer readable instructions, data structures, program modules and other data for the computer 40.
  • [0046]
    Although a hard disk, a removable magnetic disk 58, and a removable optical disk 62 are described, other types of computer readable media can be used to store data. Other such media include magnetic cassettes, flash memory cards, digital video disks, Bernoulli cartridges, random access memories (RAMs), read only memories (ROM), and the like. Additionally, the computer 40 may be configured to serve data stored on an independent storage systems, such as disk array storage systems.
  • [0047]
    A number of program modules may be stored on the hard disk, magnetic disk 58, optical disk 62, ROM 48, or RAM 50. These programs include a server operating system 70, one or more application programs 72, other program modules 74, and program data 76. The operating system 70 is preferably a Windows-brand operating system such as Windows NT, Windows 95, Windows CE or other form of Windows. The operating system 70 may alternatively be other types, including Macintosh and UNIX-based operating systems.
  • [0048]
    A user may enter commands and information into the computer 40 through input devices such as a keyboard 78 and a mouse 80. Other input devices (not shown) may include a microphone, joystick, game pad, satellite dish, scanner, or the like. These and other input devices are connected to the processing unit 42 through a serial port interface 82 that is coupled to the system bus 46, but may alternatively be connected by other interfaces, such as a parallel port, game port, or a universal serial bus (USB).
  • [0049]
    Almonitor 84 or other type of display device is also connected to the system bus 46 via an interface, such as a video adapter 86. The computer 40 has a network interface or adapter 88, a modem 90, or other means for establishing communications over a network 92.
  • [0000]
    System Architecture
  • [0050]
    FIG. 3 shows an exemplary software/hardware architecture of the system 20. The architecture includes four components: a license generator 26, a license server 28, a client 30, and an intermediate server 32. The license generator 26 produces license packs for a fee and the license server 28 consumes the licenses by installing them. In turn, the license server 28 distributes a license to the client 30 with the help of the intermediate server 32. The client 30 then uses the license to gain access to the resources provided by the intermediate server 32.
  • [0051]
    The entity or organization that owns, or is responsible for, the license server 28 registers itself with an independent certifying authority that is trusted by both the organization and the clearinghouse. The organization submits information identifying itself and various license servers to the certifying authority. The certifying authority performs a verification analysis of the organization to verify that it is a real entity and that the identification information is true and accurate. The certifying authority issues a certificate to the organization. The certificate contains the public key of the organization (or particular license server), which is signed by the certifying authority. This certificate becomes the license server's 18 certificate during the initial purchase request process when the license server requests a license pack from the clearinghouse.
  • [0052]
    Similarly, the clearinghouse also registers with the certifying authority to receive a public certificate. The clearinghouse certificate contains the clearinghouse's public key, signed by the certifying authority.
  • [0053]
    The license generator 26 has a master license database 100, a licensing producer 102, and a request handler 104. The request handler 104 receives a purchase request 106 from the license server 28 asking to purchase one or more license packs. The purchase request includes information pertaining to the licenses and license server 28. For example, the purchase request might contain such information as a license server ID, the license server's certificate (which contains the license server's public key), a client's platform type, the quantity of licenses desired, a product ID, and a list of features that the licenses should enable. Additional information about a customer (e.g., name, contract number, etc.) may also be requested for purposes of tracking and report generation. This information is stored in the master license database 100.
  • [0054]
    In response to the request, the license producer 102 generates one or more license packs 108, each of which contains a set of one or more non-assigned licenses that are purchased from the license clearinghouse. The license generator 26 creates licensing packs in a way that prevents them from being copied and installed on multiple license servers 28 or being applied multiple times on the same server. In the preferred implementation, this is accomplished using IDs and cryptographic tools. The license producer 102 assigns a unique license pack ID to each license pack and associates the license pack ID with the license server 28 in the master license database 100. The license pack ID is embedded in the license pack 108. This prevents users from multiplying the number of licenses they purchase by installing the same license pack multiple times on the same license server.
  • [0055]
    The license generator 26 encrypts the license packs 108 with the license server's public key to ensure protected transport to the license server 28 and to ensure that only the license server 28 can open the packs 108. The license generator 26 also digitally signs the license packs 108 with a private signing key of the license generator 26. The license server 28 uses this signature to validate that the license pack came from an authorized license generator and has not been altered.
  • [0056]
    The license pack 108 is a data structure that contains various information to enable the license server to distribute software licenses. The data structure contains fields with the licensing information. Table 1 shows the data fields of a license pack data structure.
    TABLE 1
    License Pack Contents
    Field Description/Purpose
    Message Version An ID used to distinguish different
    versions of the data structure.
    License Pack Serial A serial number assigned by the license
    Number generator to prevent the license pack from
    being installed multiple times on the same
    license server.
    Issue Date The date the license pack is issued by the
    clearinghouse.
    First Active Date The date on which the licenses within the
    license pack can first be used.
    Expiration Date The date on which the licenses within the
    license pack will expire. A license could
    be set such that it does not expire.
    Begin Serial Number The beginning serial number for the
    licenses in the license pack. The number
    is used to assign a unique serial number to
    each license within the license pack.
    Quantity of Licenses The number of licenses contained within
    the license pack.
    Number of Human The number of Human descriptions
    Descriptions included for the license pack.
    Array of Human Locale-Identifies the locale for the
    Descriptions (Locale, Human Description.
    Description) Human Description-A description of the
    contents of the license pack in a localized
    form.
    Manufacturer Identity of the manufacturer of the product
    being licensed.
    Manufacturer-Specific Manufacturer-dependent information used
    Product Data to identify the product. As an example,
    this data might include:
    1. Product Family Code
    2. Product Version
    3. License Type
    Signature Digital signature generated by the license
    generator using the clearinghouse private
    key.
    Clearinghouse's Public The certificate issued to the clearinghouse
    Key Certificate and containing the clearinghouse's public
    key. This public key is used to sign the
    encrypted license pack.
  • [0057]
    One parameter of the purchase request and subsequent license pack is the client platform type. As one possible implementation, the system 20 is configured to reliably recognize four different platform types: Windows, Non-Windows, Legacy, and Direct-Connect. A “Windows”-type platform means the client computer runs a 32-bit version of Microsoft Windows operating system (e.g., Windows 95, Windows 98, Windows NT, etc.). A “Non-Windows”-type platform means the client computer runs an operating system other than a Windows brand operating system. A “Legacy”-type platform indicates that the client runs an older version of an operating system that cannot be adequately determined by the license server as a “Windows”-type or a “Non-Windows”-type. A “Direct-Connect” platform means the client is a terminal that attaches directly to the server's bus and thus, all of the operating system functionality is provided directly by the server. Table 2 summarizes the platform types.
    TABLE 2
    Platform Types
    Platform Type Description
    Windows Authenticated client platforms that are Win32-
    based.
    Non-Windows Authenticated client platforms that are not Win32-
    based.
    Legacy Clients that are implemented with older operating
    systems that are incapable of fielding a client
    platform challenge from the license server. There is
    no way of determining whether or not the client's
    platform is Win32 capable.
    Direct-Connect Multi-console clients that are attached directly to the
    server's BUS. These clients derive the operating
    system capabilities from the server itself.
  • [0058]
    The license server 28 has a license pack installer 110 and a secure license store 112. The license pack installer 110 installs the license pack(s) 108 received from the license generator on the secure license store 112. The license pack installer 110 may also be used to order the license packs, when such purchase requests are made electronically.
  • [0059]
    The license pack is stored in a secured database. A library of routines for adding, removing, querying, upgrading and extracting licenses are used to man age the licenses within the license store. As noted above, the license packs are encrypted using the license server's private key to prevent users from tampering with the licenses or moving them to anot her license server. License store APIs (application program interfaces) are used to encrypt the licenses as they are placed on the secure license store 112 and to decrypt the licenses as they are removed from the store.
  • [0060]
    To prevent the same licenses from being applied multiple times on the same license server, each license pack 108 contains a unique license pack ID assigned by the license generator 26 when the license pack is created. The licenses are stored in the license store 112 based on the license pack ID.
  • [0061]
    The license store 112 contains two tables: a license pack (LP) table 114 and a client assignment (CA) table 116. The license pack table 114 records information pertaining to the license packs 108. The license pack table 114 is indexed using the license pack ID, which enables quick access and a convenient way to check if a particular license pack is already installed in the secure store.
  • [0062]
    Table 3 shows the fields in the license pack table 114.
    TABLE 3
    License Pack Table
    Field Description
    License Pack ID A unique identifier assigned by the license
    generator.
    Quantity The number of software licenses contained in the
    license pack.
    Number Assigned The number of software licenses that have been
    assigned to clients.
    First Active Date The date on which the licenses within the license
    pack can first be used.
    Expiration Date The date on which the software licenses in the
    license pack will expire.
    Begin Serial The beginning serial number for the licenses in
    Number the license pack. The number is used to assign a
    unique serial number to each license within the
    license pack.
    Product-Specific Product-dependent information to indicate
    Attributes specific features of a product. As an example,
    this date might include:
    1. Product ID
    2. Product Flags
    3. Platform Type
  • [0063]
    The number assigned field need not be kept, but it helps eliminate the need to count the number of assigned licenses each time an administrator wants to determine how many free licenses are available.
  • [0064]
    The client assignment table 116 contains a list of all licenses that have been distributed to the clients. Each record in the client assignment table 116 is assigned a unique license ID. The license ID serves two purposes: (1) it allows the table 116 to be indexed and (2) it provides a license tracking mechanism for the client. The client assignment table 116 also contains the license pack ID from which each license is derived.
  • [0065]
    Table 4 shows the fields in the client assignment table 116.
    TABLE 4
    Client Assignment Table
    Field Description
    License ID A unique identifier assigned by the license server
    to each software license, based on the begin
    serial number.
    License Pack ID The unique identifier assigned by the license
    generator.
    Client ID A unique identifier of the client to which the
    software license is granted.
    Issue Date The date on which the software license is issued
    to the client.
  • [0066]
    The license pack ID fields in the license pack table 114 and the client assignment table 116 can be used to join the tables in a one-to-many relationship; that is, one record identified in the license pack table 114 to many records in the client assignment table 116 as software licenses are issued to clients. This joinder yields a list of all software licenses assigned to clients from a given license pack. The client ID field enables the administrator to query all licenses for a particular client.
  • [0067]
    In this manner, the two tables 114 and 116 help the company's license administrator track the number of licenses available, the number installed, and which clients have which licenses. This tracking mechanism is useful because the administrator can quickly determine whether the company is in compliance with the terms of the license. Additionally, the tracking mechanism allows the administrator to plan for purchasing of additional licenses.
  • [0068]
    With continuing reference to FIG. 3, the license server 28 also has a client image installer 118 and a client image cache 120. The client image installer 118 installs executable images and client signatures of authorized clients in the client image cache 120. The client images are used to challenge clients during software distribution. The reason that the entire client image is stored on the license server is to prevent a third party from replaying exchanges between client and server for platform challenge and response.
  • [0069]
    The client digital signatures are based on client information provided by the manufacturer (i.e., OEM). The OEM submits a client executable image to a third party, or to the software manufacturer of the server software, or to a signing authority (hereinafter, collectively referred to as the signing authority). The signing authority computes a value as a one-way function of a client executable image. Preferably, the signing authority hashes the image, or slices of the image, using a hashing algorithm to produce a hash value. The signing authority then signs the client image hash with a private key associated with the license server.
  • [0070]
    The client's digital signature is presented to a license server 28 when installing client images in the server's client image cache 120. The client image installer 118 has access to the corresponding public key, which is maintained at the license server, and uses this public key to verify the client's signature before installing the client image on the cache 120.
  • [0071]
    The license server 28 also has a request handler 122, a client authenticating module 124, and a granting module 126. The request handler 122 receives requests for software licenses from clients. The client request typically includes the client ID. The request handler 122 passes the request to the client authenticating module 124, which determines whether the client is authentic and able to receive a software license.
  • [0072]
    As part of the authentication process, the client authenticating module 124 initiates a platform challenge requesting a client executable image from the client 30. One preferred approach to performing a platform challenge is described below in more detail under the sub-heading “Platform Challenge”.
  • [0073]
    The client authenticating module 124 compares the client executable image received from the client to the client executable image stored in the client image cache 120. The client is deemed authentic if the two images match. The client authenticating module 124 informs the granting module 126 when the client is authenticated.
  • [0074]
    The granting module 126 grants a software license from the secure license store 112 to the authenticated client. To prevent an issued license from being copied from machine to machine, the software license is assigned to a specific client by assigning a client ID to the license and including that ID within the license. The software license is also given a license ID. The license ID is associated with the client ID in the client assignment table 116 to track which client receives the issued license.
  • [0075]
    The license server 28, based on information derived from the license pack, fills in fields of a license data structure at the time the license is issued. As one example, the license data structure is implemented using an X.509 certificate, which is well known in the art. The license server 28 then digitally signs the software license using a signing key that is not disclosed to the client. Table 5 shows the data fields of a software license data structure.
    TABLE 5
    Software License Contents
    Field Description/Purpose
    Version Identifies the “data structure” version of the
    software license so newer licenses can be used on
    older servers.
    License ID A unique ID assigned to the software license by the
    license server at the time of issuance to the client.
    Client ID The unique identifier of the client to which the
    software license is assigned.
    Issue Date The date on which the software license is assigned
    to the client.
    Expiration Date The date on which the software licenses in the
    license pack will expire.
    Product-Specific Product-dependent information to indicate specific
    Attributes features of a product. As an example, this date
    might include:
    1. Product ID
    2. Product Flags
    3. Platform Type
    Signature Digital signature generated by the license generator
    using the clearinghouse private key.
    License Server's The license server's public key in certificate form,
    Certificate as issued by the certifying authority.
  • [0076]
    As part of the granting process, the client assignment table 116 is updated to reflect that a particular license having a specific license ID is issued to a particular client having a specific client ID. Additionally, the number assigned field in the license pack table 114 is updated to reflect that another license has been assigned to a client.
  • [0077]
    The license pack installer 110, client image installer 118, request handler 122, client authenticating module 124, and granting module 126 are preferably implemented as software programs executing on the license server 28. These software programs are preferably implemented as part of the operating system at the license server.
  • [0078]
    The intermediate server 32 acts as a go between for the client 30 and license server 28. The intermediate server is a full-service server that is used regularly by the client to perform normal tasks that are customary for the company or entity. But, the intermediate server is further equipped with a client licensing unit 128 to facilitate communication between the client 30 and license server 28. The intermediate server 32 also has a legacy license store 130, which stores licenses for clients whose platforms cannot generate a unique system ID.
  • [0079]
    The client 30 has a license requestor 132, a challenge handler 134, and a license cache 136. The license requestor 132 initiates the license requests for obtaining a software license from the license server 28. This involves connecting to the intermediate server 32 and presenting a software license and a client ID to the intermediate server 32. The client ID submitted by the client is validated against the client ID within the license. To prevent a client from simply looking within a license to find its associated client ID, the license server encrypts the software license with a key that is never disclosed to clients and hence the client is incapable of decrypting the software license. Furthermore, license tampering is prevented by digitally signing the software licenses when the license server issues them.
  • [0080]
    The client ID is passed onto the license server 28, which then initiates a platform challenge. The client's challenge handler 134 handles the platform challenge from the license server 28. It computes a response to the challenge that contains the client's image, which can be used by the license server 28 to authenticate the client.
  • [0081]
    If the client is deemed authentic, the license server downloads a software license to the client. The license server 28 encrypts the license using the client's public key and digitally signs the license. Additionally, the license generator assigns a unique license ID to the issued license. Because the licenses are tied to a specific client through a client ID, digitally signed by the license server and encrypted, the software licenses cannot be activated on other clients.
  • [0082]
    The license requestor 132 verifies the signature on the license to confirm that it came from the license server 28 and stores the software license in the license cache 136. It is the responsibility of the license requestor 132 to manage the licenses stored in the cache 136. The licenses are organized in the license cache 136 according to information about the license issuing authority and product ID.
  • [0083]
    The license cache 136 is kept in persistent (non-volatile) storage. Clients that do not have persistent storage can be issued licenses as long as they can generate a unique client ID and can respond to the client platform challenge protocol. The licensing system handles this case in the same way it recovers lost licenses. On connect, the intermediate server contacts the license server for a new license. The license server realizes, through the system ID, that the license has already been issued. In this case, the old license is simply returned to the client. Clients that cannot generate a system ID or respond to the platform challenge protocol use the legacy licenses stored in the legacy license store 130 at the intermediate server 32.
  • [0084]
    The license requestor 132 and the challenge handler 134 are preferably implemented in software executing on the client 30. These software programs are preferably implemented as part of the client's operating system.
  • [0085]
    It is noted that FIG. 3 illustrates one possible implementation of the software licensing system 20. Other implementations are possible. As one example, the components associated with a client platform challenge may be removed. These components include the client image installer 118, the client image cache 120, and the client authenticating module 124 in the license server 28, and the challenge handler 134 in the client 30.
  • [0000]
    System IDs
  • [0086]
    One aspect of system 20 is the ability to generate unique identifiers for the servers and clients. These unique IDs include the license server ID in license server certificate 140 and the client's system ID 142 (collectively referred to as “System IDs”). The system 20 employs a per-seat licensing technique, in which licenses are associated with a particular client or machine (i.e., “seat” or “node”). The license server certificate 140 contains a unique ID for the license server 28, which is passed to the license generator during a request for a license pack. The client's system ID 142 is a unique identifier of the client computer. It is noted that the client ID assigned by the license server to a software license may be client's system ID, although it will typically be a separate identifier created by the license server solely for tracking purposes.
  • [0087]
    As one possible implementation, the system IDs can be based on information collected form a computer's hardware and installed software. For example, hard disk volume numbers, network cards, registered software, video cards, and some microprocessors contain unique identifiers. On PCs, this information can be combined to uniquely identify a particular PC. Other information that might be used includes total RAM and floppy disk drive configuration. Because these components can be removed or replaced, thus changing the system ID, procedures for accepting system IDs allow for some variations. For instance, the procedures might allow for a few parameters to vary.
  • [0088]
    However, relying on a machine's hardware characteristics may not always be sufficient when generating unique machine IDs. For example, the hardware characteristics of some computers may not vary, so they would all generate the same machine ID. In these cases, manufacturers “brand” the computers with a unique identifier that it can be used to generate a unique machine ID. Client platforms that cannot generate a unique machine ID are still permitted to connect to an intermediate server and are deemed legacy platforms. Legacy licenses maintained in the legacy license store 130 are used for these machines.
  • [0000]
    Issuance of License Pack
  • [0089]
    FIG. 4 shows steps in a method for requesting and issuing a license pack from a license generator. At step 150, the license server 28 generates and sends a purchase request 106 to an authorized license generator 26. The request 106 contains information used by the license generator 26 to issue one or more software license packs to the requesting license server 28. The purchase request 106 contains the platform type (see Table 2), the quantity of licenses desired, the product ID, the license server's certificate (containing the license server's public key KLS pub and the license server ID), and the list of features that the license should enable. The license server can submit this information electronically to the I license generator via the Internet, modem, e-mail, on a floppy diskette, or other electronic means. Additionally, the administrator at the company or entity might submit a purchase request to the licensing clearinghouse 22 in writing on paper, or place an order orally by telephone. The license server 28 typically submits a licensing fee with the purchase request, or sometime following the initial communication.
  • [0090]
    After collecting the fee for the software licenses, the license generator 26 creates a license pack containing a set of one or more individual software licenses and assigns a unique license pack ID to the license pack (step 152 in FIG. 4). The license generator 26 stores the collected information in the master license database 100 (step 154). The information from the license server 28 is correlated within the database 100 to the license pack ID. In this manner, the license pack ID is associated with a particular license server having a specific license server ID (step 156).
  • [0091]
    The license generator 26 encrypts the license pack of software licenses using the license server's public key KLS pub, thus binding the license pack to the requesting license server 28. The license generator 26 digitally signs the license pack using its (i.e., the clearinghouse's) private signing key KCH pri (step 160 in FIG. 4) and sends the license pack to the requesting license server 28.
  • [0092]
    The license pack 108 contains a set of one or more non-assigned licenses and the license pack ID. Table 1 lists the contents of the license pack 108.
  • [0093]
    At step 164 in FIG. 4, the license server 28 uses the clearinghouse's public signing key KCH pub to verify that the digital signature accompanying the license pack 108 belongs to the license generator 26 of clearinghouse 22 and that the license pack 108 has not been altered. If the signature is authentic and from a known clearinghouse, the license server 28 decrypts the license pack contents using its private key KLS pri (step 166). The license server 28 extracts the license pack ID and queries the secure license store 112 to see if it already contains the same license pack (step 168). If the license pack is new, the license server installs it on the secure license store 112 (step 170).
  • [0000]
    Distribution of Licenses
  • [0000]
    Client Connection
  • [0094]
    FIG. 5 shows steps in a process that facilitates a client's initial connection to the intermediate server. The client connects to the intermediate server 32 to ask for services or data provided by the server. Prior to working with the client and providing access to files, the intermediate server 32 wants to verify first that the client has a valid software license issued by a recognized license server. The client 30 may or may not have a valid license, so the intermediate server makes an initial evaluation when the client attempts to connect. Generally, if the client 30 has a valid license, the client is permitted to connect and use the server's resources. If the client 30 offers an invalid license, the client is disconnected. If the client 30 does not offer a valid license or offers an expired license, the intermediate server 32 facilitates the process of obtaining a new software license.
  • [0095]
    At step 172, the client 30 submits a connection request to the intermediate server 32. The connection request includes the client's system ID that uniquely identifies the computer. In response, the intermediate server 32 passes a list of the product IDs required (step 174). In this manner, the intermediate server 32 limits its acceptance of software licenses to those that are issued by legitimate and authorized license servers.
  • [0096]
    With this information, the client 30 queries its license cache 136 to search for a suitable license from a license server that appears on the list (step 176 in FIG. 5). If a software license is found, the client 30 sends the software license to the intermediate server 32 along with the client ID; otherwise, the client 30 submits only a client ID (step 178). The software license contains the digital signature of the license server.
  • [0097]
    At step 180 in FIG. 5, the intermediate server 32 determines whether the client submitted a software license. If so, the intermediate server 32 verifies whether the digital signature belongs to an authorized license server and whether the license contains a valid client ID (step 182). The client ID is checked by extracting the client ID from the license (which was provided originally by the licensing server, as described below) and comparing it to the client ID received from the client. If the two match, the client ID passes.
  • [0098]
    If the digital signature or the client ID is not valid (i.e., the “not valid” branch from step 182), the software license is deemed invalid. The client's request for connection is then rejected and the client is disconnected. On the other hand, if the digital signature and the client ID are both valid (i.e., the “valid” branch from step 182), the intermediate server 32 checks if the license has expired (step 184), the connection is completed if the license is still valid i.e. has not expired and the client is allowed access to the services and files of the intermediate server (step 186).
  • [0099]
    In the event that the client 30 does not submit a valid license or submits an expired license, the intermediate server requests a new software license from the license server (step 188 in FIG. 5).
  • [0000]
    New License Grant
  • [0100]
    Software licenses are distributed to the client automatically by the license server. As discussed above, when a client 30 connects to an intermediate server 32, the client must present a valid license. If it cannot, the intermediate server acts as a proxy for the client and requests a license from its associated license server.
  • [0101]
    FIG. 6 shows steps in a method for granting a new software license from the license server 28 to the client 30. The method begins with step 188, which is the same new license request discussed above with respect to step 188 of FIG. 5. The new license request includes the client's system ID and the product ID. In response to the request, the license server 28 initiates a client challenge to determine who the client is and what platform it is running (step 190). In general, this involves generating a challenge and sending it to the intermediate server 32 (step 192). The intermediate server 32 forwards the challenge to the client 30 (step 194).
  • [0102]
    At step 196 in FIG. 6, the client responds to the challenge in a manner that provides trusted information about client, including the platform type and the client's public key. The response is passed to the intermediate server 32, which forwards it to the license server 28 (step 198).
  • [0103]
    At step 200 in FIG. 6, the license server determines whether the response is proper, and hence, whether the client is authentic. If the client is authenticated (i.e., the “yes” branch from step 200), the license server proceeds with granting a 10 software license. The license server 28 first queries the secure license store 112 to determine if a license for that client has already been issued (step 202). This procedure accommodates the case in which the client has lost its valid software license. If a non-expired license is found, the license server 28 forwards it to the client 30.
  • [0104]
    Otherwise, the license server 28 attempts to allocate a software license for the client, assuming a non-assigned license still exists in the license pack. If a license can be allocated, the license server 28 retrieves a software license that is appropriate for the client's platform from the secure software store 112 and grants 19 the software license to the client (step 204 in FIG. 6). The license server 28 adds a record to the client assignment table 116 and the corresponding number assigned field is updated to reflect one additional allocation.
  • [0105]
    To prevent the software license from being copied from one client machine to another, the software license is assigned to the specific client by including its client ID within the license. The software license also has a corresponding license ID that is associated with the client ID in the client assignment table 116 in the secure license store 112 at the license server. The contents of the license are described above in Table 5.
  • [0106]
    The license server 32 digitally signs the software license (step 206) and encrypts it using the client's public key KC pub (step 208), thereby binding the license to the client. The encrypted license is forwarded to the intermediate server 32, which passes it on to the client 30 and completes the connection (step 210). By encrypting the license, the client or the license server need not trust the intermediate server because the intermediate server cannot maliciously utilize or modify the encrypted license. It also removes the risk of a rogue server masquerading as intermediate server. At step 212, the client 30 decrypts the license 11 using the client's private key KC pri and stores the license in the license cache 136.
  • [0107]
    In the event that the client's response to the challenge is deemed improper (i.e., the “no” branch from step 200), the license server returns a rejection notice (step 214 in FIG. 6). This rejection notice is passed on by the intermediate server 32 (step 216) and used to inform the user (step 218).
  • [0000]
    Platform Challenge
  • [0108]
    FIG. 7 shows a more detailed method for providing a platform challenge to 19 the client. In this illustration, the intermediate server 32 is shown as the go between, with the forwarding steps omitted for ease of description.
  • [0109]
    An aspect of platform validation is establishing the authenticity of the client. The system utilizes the client's executable image to generate a digital signature that uniquely identifies the client. As noted above, the client's executable image is available to the license server 28 because it is stored in the client image cache 120.
  • [0110]
    When a client requests a software license from the license server, the client 30 submits a client software ID (step 220 in FIG. 7). The software ID is assigned by the software manufacturer/vendor to be unique for each client release. The client software ID is a bit field that contains a platform identifier, a vendor identifier, and a client revision field. The arrangement of the bits depends on how many platforms and clients are supported.
  • [0111]
    At step 222, the license server 28 uses the software ID to lookup the client's executable image in the client image cache 120. If the image is not present in the cache (i.e., the “no” branch from step 222), the client is denied a software license and a rejection is returned to the client and informs the user (steps 224 and 226).
  • [0112]
    On the other hand, if an image is present (i.e., the “yes” branch from step 222), the license server 28 sends a challenge to the client 30 to establish a trust relationship with the client (step 228). The challenge is preferably a 128-bit random number.
  • [0113]
    The client 30 applies a one-way function to a combination of the challenge and the client's image (step 230). Preferably, the client concatenates the challenge and the client image and computes a hash value, as follows:
    Challenge Response=Hash(challenge|client image|challenge)
  • [0114]
    The client 30 sends the challenge response (i.e., the hash value) back to the license server 28 (step 232).
  • [0115]
    Meanwhile, the license server 28 uses the software ID to retrieve a reference copy of the client image from its cache 120 (step 234 in FIG. 7). The license server then computes a test hash value using the same hash function, and a concatenated version of the same 128-bit challenge and the client image retrieved from the cache 120 (step 236).
  • [0116]
    The license server 28 compares the test hash value (H′) with the hash value (H) returned from the client (step 238). If the two values are the same, the client's platform information is extracted from the client software ID and a trust relationship established (i.e., the “yes” branch from step 238). Otherwise, the client is denied a software license and a rejection is returned to the client (i.e., the “no” branch from step 238).
  • [0000]
    Upgrading Licenses
  • [0117]
    The process for upgrading an existing license is very similar to the license distribution process. The primary difference is that a platform challenge is not performed because a valid, digitally signed license is presented to the license server.
  • [0118]
    FIG. 8 shows the steps in a method for upgrading an existing license. Steps 172-176 are identical to those defined above with respect to FIG. 5. At step 240, the client 30 submits a valid software license to the intermediate server 32.
  • [0119]
    At step 242 in FIG. 8, the intermediate server 32 determines whether the license has expired and/or is for an older version. Assuming it meets one of these conditions, the intermediate server automatically contacts the license server 28 and requests that the license be upgraded (step 244). The intermediate server passes the old license and the client's system ID to the license server 28.
  • [0120]
    The license server 28 validates the old license and extracts the license's ID, which is used as an index into the client assignment table 116 in the secure license store 112. The license server 28 examines the table 116 to determine whether an upgrade is available (step 246). If so, the license server 28 upgrades a record in the table, consuming one upgrade license, and returns an upgraded licese to the intermediate server 32 (step 248). The intermediate server 32 forwards the upgraded license to the client and completes the connection (step 250). The client 30 replaces the old license with the upgraded one in the license cache 136 (step 252).
  • [0121]
    As a matter of policy, licenses are assumed to be backward compatible. That is, a next generation 5.X license is always accepted by a current generation 4.X server. This allows a customer to have a seamless mix of different servers. Variances in the licenses internal data structures are taken into account by including a version number within the license.
  • [0000]
    Temporary Licenses
  • [0122]
    Suppose a client 30 requests a software license, but the license server 28 does not have an available license in the secure license store. In this case, the license server 28 issues a temporary license that is valid for a finite duration (e.g., 60 days).
  • [0123]
    With reference to FIG. 3, the requesting client submits its system ID 142 to the intermediate server 32, which forwards the client's system ID 142 to the license server 28. The license server 28 generates a temporary license and associates it with the client's system ID 142. The temporary license is passed back through the intermediate server 32 to the client 30. Each time the client presents the temporary license, a new license request is generated. Once the license server has an available license (e.g., the license server purchased additional licenses from the license clearinghouse), it issues a permanent license to the client. Temporary licenses are replaced only by a valid permanent license.
  • [0124]
    When a temporary license expires, the license server 28 no longer accepts it and services are denied. Furthermore, the client is only granted one temporary license and will not be permitted to request a second temporary. If a client attempts to request a second temporary license, the license server will detect the system ID and recognize that this ID is already associated with a previously issued temporary license. The license server 28 simply returns the previously issued temporary license, which is inoperable because it has expired.
  • [0125]
    Although the invention has been described in language specific to structural features and/or methodological steps, it is to be understood that the invention defined in the appended claims is not necessarily limited to the specific features or steps described. Rather, the specific features and steps are disclosed as preferred forms of implementing the claimed invention.

Claims (16)

  1. 1. One or more computer-readable media having computer readable instructions that, when executed by one or more processors, cause the one or more processors to:
    receive a request for a software license from a particular client;
    determine an authenticity of the particular client;
    select a software license from a pack of software licenses that is appropriate for the particular client, the software license having an associated license ID;
    associate the license ID with the particular client;
    grant the software license to the particular client; and
    determine whether the particular client already has a non-expired license, and if so, forward the non-expired license to the particular client rather than granting the software license.
  2. 2. One or more computer-readable media as recited in claim 1, wherein to determine the authenticity is to:
    receive a client software ID from the particular client; and
    evaluate the client software ID to determine whether the client is authentic.
  3. 3. One or more computer-readable media as recited in claim 1, wherein to determine the authenticity is to:
    maintain a set of client images;
    receive a client software ID from the particular client; and
    compare the client software ID to the client images to evaluate whether the client is authentic.
  4. 4. One or more computer-readable media as recited in claim 1, wherein the computer readable instructions further cause the one or more processors to encrypt the software license using a public key of the particular client.
  5. 5. One or more computer-readable media having computer readable instructions that, when executed by one or more processors, cause the one or more processors to:
    receive a request for a software license from a particular client;
    determine an authenticity of the particular client;
    select a software license from a pack of software licenses that is appropriate for the particular client, the software license having an associated license ID;
    associate the license ID with the particular client;
    grant the software license to the particular client; and
    grant a temporary software license that expires in a substantially shorter duration in comparison to the software license.
  6. 6. One or more computer-readable media as recited in claim 5, wherein to grant the software license is to grant the software license containing the license ID, a platform type indicating a type of operating platform for which the software license can be used, an issue date that indicates a date on which the software license is issued to the particular client, an expiration date that indicates a date on which the software license will expire, a product ID that identifies a product with which the software license can be used, a client ID that identifies the particular client, and a version of the software license.
  7. 7. One or more computer-readable media as recited in claim 5, wherein to determine the authenticity is to:
    receive a client software ID from the particular client; and
    evaluate the client software ID to determine whether the client is authentic.
  8. 8. One or more computer-readable media as recited in claim 5, wherein to determine the authenticity is to:
    maintain a set of client images;
    receive a client software ID from the particular client; and
    compare the client software ID to the client images to evaluate whether the client is authentic.
  9. 9. One or more computer-readable media as recited in claim 5, wherein the computer readable instructions further cause the one or more processors to:
    determine a platform of the particular client; and
    select the software license as is appropriate for the platform of the particular client.
  10. 10. One or more computer-readable media as recited in claim 5, wherein the computer readable instructions further cause the one or more processors to encrypt the software license using a public key of the particular client.
  11. 11. A license server for issuing individual software licenses from a software pack received from a licensing clearinghouse, comprising:
    means for storing the software pack of individual software licenses, each I software license having an associated license ID;
    means for receiving a request for a software license from a client;
    means for determining whether the client is authentic and can receive a software license;
    means for granting a software license from the license store to an authenticated client and to associate the license ID with the authenticated client; and
    client assignment table means for containing a list of the software licenses that are granted to clients.
  12. 12. A license server as recited in claim 11, wherein the means for granting is further for upgrading the client assignment table means after granting the software license to the authenticated client.
  13. 13. A license server as recited in claim 11, further comprising:
    client image cache means for storing a set of client images; and
    the means for determining receiving a client image from the client and comparing the received client image to the set of client images to evaluate whether the client is authentic.
  14. 14. A license server as recited in claim 11, wherein the means for determining is further for determining an operating platform of the client.
  15. 15. A license server as recited in claim 11, wherein the software license contains at least one of the following items:
    a version indicator of a software license;
    a license ID;
    a client ID that identifies the authenticated client;
    an issue date on which the license is issued to the client;
    a platform type of the client's operating platform for which the software license can be used;
    an expiration date on which the software license will expire; and
    a product ID that identifies a product with which the software licenses can be used.
  16. 16. A license server as recited in claim 11, further comprising license pack table means for storing information pertaining to the license pack that is stored in the license store.
US11016641 1998-03-18 2004-12-17 System and method for software licensing Active 2021-02-06 US7809648B2 (en)

Priority Applications (3)

Application Number Priority Date Filing Date Title
US09040813 US6189146B1 (en) 1998-03-18 1998-03-18 System and method for software licensing
US09724703 US7171662B1 (en) 1998-03-18 2000-11-28 System and method for software licensing
US11016641 US7809648B2 (en) 1998-03-18 2004-12-17 System and method for software licensing

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
US11016641 US7809648B2 (en) 1998-03-18 2004-12-17 System and method for software licensing

Publications (2)

Publication Number Publication Date
US20050102240A1 true true US20050102240A1 (en) 2005-05-12
US7809648B2 US7809648B2 (en) 2010-10-05

Family

ID=34555086

Family Applications (2)

Application Number Title Priority Date Filing Date
US09724703 Active 2020-11-22 US7171662B1 (en) 1998-03-18 2000-11-28 System and method for software licensing
US11016641 Active 2021-02-06 US7809648B2 (en) 1998-03-18 2004-12-17 System and method for software licensing

Family Applications Before (1)

Application Number Title Priority Date Filing Date
US09724703 Active 2020-11-22 US7171662B1 (en) 1998-03-18 2000-11-28 System and method for software licensing

Country Status (1)

Country Link
US (2) US7171662B1 (en)

Cited By (61)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20030055788A1 (en) * 2001-09-20 2003-03-20 Toshiyuki Sakuma Fee imposition system for application software
US20030177073A1 (en) * 2002-03-15 2003-09-18 Yamaha Corporation Distribution system of contents embedding license machine ID
US20030204723A1 (en) * 2002-04-30 2003-10-30 Microsoft Corporation Digital license with referral information
US20050044048A1 (en) * 2003-08-21 2005-02-24 Intel Corporation Access control apparatus, systems, and methods
US20050076334A1 (en) * 2003-10-03 2005-04-07 Michael Demeyer System and method for licensing software
US20060015465A1 (en) * 2004-07-13 2006-01-19 Hiroshi Kume Apparatus, method and program for license information ascertainment
US20060064388A1 (en) * 2004-09-22 2006-03-23 Nokia Corporation Method and system for the total decoupling of licenses from associated license protected configuration
US20060150180A1 (en) * 2003-02-25 2006-07-06 Siemens Aktiengesellschaft Method for carrying out the premium-based recomendation of content objects that can be downloaded to a mobile terminal
US20060167809A1 (en) * 2005-01-24 2006-07-27 Microsoft Corporation Software assistant for multi-merchant purchasing environment for downloadable products
US20060190409A1 (en) * 2000-04-28 2006-08-24 Hillegass James C Method and system for licensing digital works
US20060229994A1 (en) * 2005-04-07 2006-10-12 Moulckers Ingrid M Automatic generation of license package for solution components
US20060235802A1 (en) * 2005-04-19 2006-10-19 Realnetworks, Inc. License confirmation via embedded confirmation challenge
US20060272031A1 (en) * 2005-05-24 2006-11-30 Napster Llc System and method for unlimited licensing to a fixed number of devices
US20070022017A1 (en) * 2005-01-24 2007-01-25 Microsoft Corporation Extended Data Collection For Multi-Merchant Purchasing Environment For Downloadable Products
US20070027815A1 (en) * 2005-07-29 2007-02-01 Symantec Corporation Systems and methods for centralized subscription and license management in a small networking environment
US20070041584A1 (en) * 2005-08-16 2007-02-22 O'connor Clint H Method for providing activation key protection
US20070106617A1 (en) * 2005-11-08 2007-05-10 Paul Mabray Legal compliance system for the sale of regulated products or services
US20070299779A1 (en) * 2006-06-27 2007-12-27 Edmund Yu Liang Sung Method and apparatus for authorizing a software product to be used on a computer system
US20080005033A1 (en) * 2006-06-30 2008-01-03 Clark Charles F Secure device licensing
US20080195548A1 (en) * 2005-04-11 2008-08-14 Hyun Gon Chu License Data Structure and License Issuing Method
US20080244754A1 (en) * 2007-04-02 2008-10-02 Edward Curren System and Method for Software License Management for Concurrent License Management and Issuance
US20080243699A1 (en) * 2007-03-29 2008-10-02 Microsoft Corporation License optimization and automated management
US20080281625A1 (en) * 2006-01-19 2008-11-13 Tokyo Electon Limited Substrate processing apparatus, license management program, license information serving apparatus, license information providing program, license management system, and recording medium
US20090012871A1 (en) * 2007-07-05 2009-01-08 Medical Justice Corp. Method and system for reducing consumption of addictive commodities
US20090048691A1 (en) * 2007-08-16 2009-02-19 Honeywell International Inc. Embedded building conroller with stored software license information
US20090089864A1 (en) * 2007-09-28 2009-04-02 Nokia Corporation Remote management of telecommunications network element during license expire and renewal period
US20090249488A1 (en) * 2008-03-28 2009-10-01 Sap Ag Flexible appliance hosting with coordination of deployment, licensing and configuration
US7603318B1 (en) * 2006-10-24 2009-10-13 Adobe Systems Incorporated License distribution
US20090290716A1 (en) * 2008-05-22 2009-11-26 Dell Products L.P. Digital software license procurement
US20090326964A1 (en) * 2008-06-25 2009-12-31 Microsoft Corporation Extensible agent-based license structure
US20100004938A1 (en) * 2004-12-30 2010-01-07 Abb Ab Software licensing system
US20100043075A1 (en) * 2008-08-13 2010-02-18 Autodesk, Inc. Licensing management utility
US20100057703A1 (en) * 2008-08-29 2010-03-04 Brandt Matthew K Systems and Methods for Automating Software Updates/Maintenance
CN101118579B (en) 2006-08-01 2010-05-12 华为技术有限公司 Verification permissive method and system
US20100191795A1 (en) * 2005-10-06 2010-07-29 Gerhard Hering Hardware Triggering in a Management System
US20100227681A1 (en) * 2009-03-03 2010-09-09 Microsoft Corporation Limited-rights local playback of digital content
US20100287303A1 (en) * 2009-05-11 2010-11-11 Smith Michael R Network traffic rate limiting system and method
US20110023127A1 (en) * 1999-02-05 2011-01-27 O'donnell Lawrence Internet system for facilitating human user advisement and licensing of copyrighted works of authorship
US7962424B1 (en) 2006-10-24 2011-06-14 Adobe Systems Incorporated Overdraft licenses and license distribution
US20110238710A1 (en) * 1999-03-05 2011-09-29 International Business Machines Corporation Software Product Inventory and Usage Information Correlated with License Agreement Information
US20110321025A1 (en) * 2010-02-09 2011-12-29 Accenture Global Services Gmbh Enhanced Upgrade Path
US20120047205A1 (en) * 2002-02-01 2012-02-23 Masaya Yamamoto License information exchange system
US20120089733A1 (en) * 2010-10-12 2012-04-12 Ansca, Inc. Managing Access to an Application
US20120221709A1 (en) * 2011-02-24 2012-08-30 Bowes James R Mechanism to allow hosted and on-site implementations to manage product assets as specified by a third party
US8412588B1 (en) * 2010-09-24 2013-04-02 Amazon Technologies, Inc. Systems and methods for fabricating products on demand
CN103221957A (en) * 2010-11-22 2013-07-24 英特尔公司 Secure software licensing and provisioning using hardware based security engine
US8856867B1 (en) * 2007-06-28 2014-10-07 Intuit Inc. Technique for controlling access to program assets
US9075688B2 (en) 2010-02-09 2015-07-07 Accenture Global Services Limited Enhanced upgrade path
US9122998B2 (en) * 2010-07-28 2015-09-01 International Business Machines Corporation Catalog-based software license reconciliation
EP2009524A3 (en) * 2007-01-26 2015-09-02 Rockwell Automation Technologies, Inc. Authentication for licensing in an embedded system
US9135409B2 (en) 2011-05-18 2015-09-15 Hewlett-Packard Development Company, L.P. Distributing update information based on validated license information
US9224111B2 (en) 2011-02-25 2015-12-29 Red Hat, Inc. Message queue based product asset management auditing system
US20150379526A1 (en) * 2014-06-26 2015-12-31 Adobe Systems Incorporated Tracking and linking mobile device activity
US9230273B2 (en) 2010-07-28 2016-01-05 International Business Machines Corporation Creation and use of constraint templates
US9264902B1 (en) 2007-03-02 2016-02-16 Citigroup Global Markets Inc. Systems and methods for remote authorization of financial transactions using public key infrastructure (PKI)
US9361435B1 (en) * 2015-01-14 2016-06-07 Flexera Software Llc Multi-tier digital supply chain management
US20160364213A1 (en) * 2014-10-29 2016-12-15 International Business Machines Corporation Automatic generation of license terms for service application marketplaces
US9672550B2 (en) 2010-09-24 2017-06-06 Amazon Technologies, Inc. Fulfillment of orders for items using 3D manufacturing on demand
US9684919B2 (en) 2010-09-24 2017-06-20 Amazon Technologies, Inc. Item delivery using 3D manufacturing on demand
US9858604B2 (en) 2010-09-24 2018-01-02 Amazon Technologies, Inc. Vendor interface for item delivery via 3D manufacturing on demand
US9898776B2 (en) 2010-09-24 2018-02-20 Amazon Technologies, Inc. Providing services related to item delivery via 3D manufacturing on demand

Families Citing this family (105)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US7103574B1 (en) * 1999-03-27 2006-09-05 Microsoft Corporation Enforcement architecture and method for digital rights management
US7073063B2 (en) 1999-03-27 2006-07-04 Microsoft Corporation Binding a digital license to a portable device or the like in a digital rights management (DRM) system and checking out/checking in the digital license to/from the portable device or the like
US7953671B2 (en) 1999-08-31 2011-05-31 American Express Travel Related Services Company, Inc. Methods and apparatus for conducting electronic transactions
US7343351B1 (en) * 1999-08-31 2008-03-11 American Express Travel Related Services Company, Inc. Methods and apparatus for conducting electronic transactions
KR100847596B1 (en) 2000-03-02 2008-07-21 소니 가부시끼 가이샤 Communication network system, gateway, data communication method and program providing medium
US7797373B1 (en) * 2000-03-03 2010-09-14 Martin S Berger System and method for promoting intellectual property
US7725427B2 (en) 2001-05-25 2010-05-25 Fred Bishop Recurrent billing maintenance with radio frequency payment devices
WO2002079981A1 (en) * 2001-03-30 2002-10-10 Nokia Corporation Downloading application software to a mobile terminal
US8294552B2 (en) 2001-07-10 2012-10-23 Xatra Fund Mx, Llc Facial scan biometrics on a payment device
US8548927B2 (en) 2001-07-10 2013-10-01 Xatra Fund Mx, Llc Biometric registration for facilitating an RF transaction
US7668750B2 (en) * 2001-07-10 2010-02-23 David S Bonalle Securing RF transactions using a transactions counter
US9031880B2 (en) * 2001-07-10 2015-05-12 Iii Holdings 1, Llc Systems and methods for non-traditional payment using biometric data
US20040236699A1 (en) 2001-07-10 2004-11-25 American Express Travel Related Services Company, Inc. Method and system for hand geometry recognition biometrics on a fob
US8001054B1 (en) 2001-07-10 2011-08-16 American Express Travel Related Services Company, Inc. System and method for generating an unpredictable number using a seeded algorithm
US9024719B1 (en) 2001-07-10 2015-05-05 Xatra Fund Mx, Llc RF transaction system and method for storing user personal data
US7735725B1 (en) 2001-07-10 2010-06-15 Fred Bishop Processing an RF transaction using a routing number
US7705732B2 (en) * 2001-07-10 2010-04-27 Fred Bishop Authenticating an RF transaction using a transaction counter
US7303120B2 (en) * 2001-07-10 2007-12-04 American Express Travel Related Services Company, Inc. System for biometric security using a FOB
US7889052B2 (en) 2001-07-10 2011-02-15 Xatra Fund Mx, Llc Authorizing payment subsequent to RF transactions
US7360689B2 (en) 2001-07-10 2008-04-22 American Express Travel Related Services Company, Inc. Method and system for proffering multiple biometrics for use with a FOB
USRE45416E1 (en) 2001-07-10 2015-03-17 Xatra Fund Mx, Llc Processing an RF transaction using a routing number
US9454752B2 (en) * 2001-07-10 2016-09-27 Chartoleaux Kg Limited Liability Company Reload protocol at a transaction processing entity
US8284025B2 (en) 2001-07-10 2012-10-09 Xatra Fund Mx, Llc Method and system for auditory recognition biometrics on a FOB
KR100616217B1 (en) * 2001-12-13 2006-08-25 가부시키가이샤 소니 컴퓨터 엔터테인먼트 Methods and apparatus for secure distribution of program content
KR100983179B1 (en) * 2001-12-21 2010-09-20 소니 컴퓨터 엔터테인먼트 인코포레이티드 Methods and apparatus for secure distribution of program content
JP4098723B2 (en) * 2002-02-13 2008-06-11 テレフオンアクチーボラゲット エル エム エリクソン(パブル) Reconstruction of the server system (Reconfiguring) METHOD AND APPARATUS
US7885896B2 (en) 2002-07-09 2011-02-08 Avaya Inc. Method for authorizing a substitute software license server
US8041642B2 (en) 2002-07-10 2011-10-18 Avaya Inc. Predictive software license balancing
US7707116B2 (en) * 2002-08-30 2010-04-27 Avaya Inc. Flexible license file feature controls
US7966520B2 (en) * 2002-08-30 2011-06-21 Avaya Inc. Software licensing for spare processors
US7681245B2 (en) * 2002-08-30 2010-03-16 Avaya Inc. Remote feature activator feature extraction
US7698225B2 (en) * 2002-08-30 2010-04-13 Avaya Inc. License modes in call processing
US6805287B2 (en) 2002-09-12 2004-10-19 American Express Travel Related Services Company, Inc. System and method for converting a stored value card to a credit card
US7890997B2 (en) * 2002-12-26 2011-02-15 Avaya Inc. Remote feature activation authentication file system
US7370212B2 (en) 2003-02-25 2008-05-06 Microsoft Corporation Issuing a publisher use license off-line in a digital rights management (DRM) system
US7260557B2 (en) * 2003-02-27 2007-08-21 Avaya Technology Corp. Method and apparatus for license distribution
US20040267590A1 (en) * 2003-06-30 2004-12-30 International Business Machines Corporation Dynamic software licensing and purchase architecture
DE10330191A1 (en) * 2003-07-03 2005-02-10 Siemens Ag System and method for releasing freigabebedürftigter software programs
US8548170B2 (en) * 2003-12-10 2013-10-01 Mcafee, Inc. Document de-registration
US8060923B2 (en) * 2004-04-23 2011-11-15 Microsoft Corporation Trusted license removal in a content protection system or the like
US7949607B2 (en) * 2004-06-21 2011-05-24 Canon Kabushiki Kaisha Image forming apparatus, license managing method for applications executed by image forming apparatus, program for implementing the method, and storage medium storing the program
US7318550B2 (en) 2004-07-01 2008-01-15 American Express Travel Related Services Company, Inc. Biometric safeguard method for use with a smartcard
US7314164B2 (en) * 2004-07-01 2008-01-01 American Express Travel Related Services Company, Inc. System for biometric security using a smartcard
US7341181B2 (en) * 2004-07-01 2008-03-11 American Express Travel Related Services Company, Inc. Method for biometric security using a smartcard
US7314165B2 (en) * 2004-07-01 2008-01-01 American Express Travel Related Services Company, Inc. Method and system for smellprint recognition biometrics on a smartcard
US20060020553A1 (en) * 2004-07-26 2006-01-26 Septon Daven W License proxy process to facilitate license sharing between a plurality of applications
JP4334521B2 (en) * 2004-09-20 2009-09-30 株式会社ソニー・コンピュータエンタテインメント Method of enabling execution of a software program in a single processor system
WO2006033419A1 (en) * 2004-09-20 2006-03-30 Sony Computer Entertainment Inc. Methods and apparatus for distributing software applications
US7707405B1 (en) 2004-09-21 2010-04-27 Avaya Inc. Secure installation activation
US7747851B1 (en) * 2004-09-30 2010-06-29 Avaya Inc. Certificate distribution via license files
US8229858B1 (en) 2004-09-30 2012-07-24 Avaya Inc. Generation of enterprise-wide licenses in a customer environment
US20060089917A1 (en) * 2004-10-22 2006-04-27 Microsoft Corporation License synchronization
CN101057447B (en) * 2004-12-03 2010-12-08 诺基亚公司 Method and device for re-dispatching specifically coded access objects from a server to a mobile terminal device
JP4704233B2 (en) * 2005-03-04 2011-06-15 株式会社リコー The information processing apparatus and control method thereof
US8725646B2 (en) * 2005-04-15 2014-05-13 Microsoft Corporation Output protection levels
US7552429B2 (en) * 2005-04-21 2009-06-23 International Business Machines Corporation Integrated development environment for managing software licensing restrictions
US8438645B2 (en) * 2005-04-27 2013-05-07 Microsoft Corporation Secure clock with grace periods
US20060265758A1 (en) * 2005-05-20 2006-11-23 Microsoft Corporation Extensible media rights
US20060294022A1 (en) * 2005-06-22 2006-12-28 Dayan Richard A Apparatus, system, and method for enabling a service
WO2007001285A1 (en) * 2005-06-23 2007-01-04 Thomson Licensing Digital rights management (drm) enabled portable playback device, method and system
US7814023B1 (en) 2005-09-08 2010-10-12 Avaya Inc. Secure download manager
US8745223B2 (en) * 2005-10-14 2014-06-03 Psion Inc. System and method of distributed license management
KR100754189B1 (en) * 2005-11-01 2007-09-03 삼성전자주식회사 Information storage medium recording digital contents, method and system for managing digital contents
US7788181B2 (en) * 2005-12-27 2010-08-31 Microsoft Corporation Software licensing using certificate issued by authorized authority
US20070198428A1 (en) * 2006-02-22 2007-08-23 Microsoft Corporation Purchasing of computer service access licenses
US20070198427A1 (en) * 2006-02-22 2007-08-23 Microsoft Corporation Computer service licensing management
US9043934B2 (en) * 2012-04-06 2015-05-26 Wayne Odom System, method, and device for delivering communications and storing and delivering data
US20080114695A1 (en) * 2006-11-10 2008-05-15 Semantic Components S.L. Process for implementing a method for the on-line sale of software product use licenses through a data network, and software component which allows carrying out said process
US8341616B2 (en) * 2007-03-28 2012-12-25 International Business Machines Corporation Updating digitally signed active content elements without losing attributes associated with an original signing user
US8392713B2 (en) * 2007-06-01 2013-03-05 Microsoft Corporation Secure offline activation process for licensed software application programs
US7865444B1 (en) * 2007-06-12 2011-01-04 Adobe Systems Incorporated License tracking and management
US8266062B2 (en) * 2007-06-27 2012-09-11 Microsoft Corporation Server side reversible hash for telephone-based licensing mechanism
US8407669B2 (en) * 2007-07-25 2013-03-26 Oracle International Corporation Device based software authorizations for software asset management
US9336369B2 (en) * 2007-09-28 2016-05-10 Abbyy Development Llc Methods of licensing software programs and protecting them from unauthorized use
US9129098B2 (en) 2007-09-28 2015-09-08 Abbyy Development Llc Methods of protecting software programs from unauthorized use
US20090094044A1 (en) * 2007-10-06 2009-04-09 Peterson Jr Harold Lee System, method and computer-readable medium for configuring a computer via a network to generate a personalized user experience
US8347374B2 (en) * 2007-11-15 2013-01-01 Red Hat, Inc. Adding client authentication to networked communications
US8341751B2 (en) * 2007-12-26 2012-12-25 Wilson Kelce S Software license management
JP4533935B2 (en) * 2008-01-22 2010-09-01 日立ソフトウエアエンジニアリング株式会社 License authentication system and authentication method
US20090199299A1 (en) * 2008-01-31 2009-08-06 Microsoft Corporation Integrated user experience while allocating licenses within volume licensing systems
ES2326949B1 (en) 2008-03-18 2010-07-14 Clarity Systems, S.L. Procedure used by a streaming server to perform a transmission of a multimedia file on a data network.
US7984097B2 (en) 2008-03-18 2011-07-19 Media Patents, S.L. Methods for transmitting multimedia files and advertisements
US8935528B2 (en) * 2008-06-26 2015-01-13 Microsoft Corporation Techniques for ensuring authentication and integrity of communications
JP2010086461A (en) * 2008-10-02 2010-04-15 Sony Corp License management device and license management method, and license management system
US8473442B1 (en) 2009-02-25 2013-06-25 Mcafee, Inc. System and method for intelligent state management
US8447722B1 (en) 2009-03-25 2013-05-21 Mcafee, Inc. System and method for data mining and security policy management
US20100262963A1 (en) * 2009-04-09 2010-10-14 Gary Michael Wassermann Systems and methods for activating a network appliance
KR101053680B1 (en) * 2009-04-13 2011-08-02 계영티앤아이 (주) Software management apparatus and method, wherein the user terminal and its management, which is controlled by this
US9154532B2 (en) 2009-04-27 2015-10-06 Zaron Remote Llc Methods and apparatus for transmitting multimedia files in a data network
US9424399B2 (en) * 2009-05-12 2016-08-23 Microsoft Technology Licensing, Llc Availability of permission models in roaming environments
US20100293103A1 (en) * 2009-05-12 2010-11-18 Microsoft Corporation Interaction model to migrate states and data
US20100293536A1 (en) * 2009-05-12 2010-11-18 Microsoft Corporation Enhanced product functionality based on user identification
US9582776B2 (en) 2009-10-09 2017-02-28 Oracle International Corporation Methods and systems for providing a comprehensive view of it assets as self service inquiry/update transactions
US20110087604A1 (en) * 2009-10-09 2011-04-14 Oracle International Corporation Micro-blogging for enterprise resources planning (erp)
US9342825B2 (en) 2010-06-10 2016-05-17 International Business Machines Corporation Software license and installation process management within an organization
US20120066089A1 (en) * 2010-09-14 2012-03-15 Ncr Corporation Multi-media content at a digital download kiosk
US8806615B2 (en) 2010-11-04 2014-08-12 Mcafee, Inc. System and method for protecting specified data combinations
US8677346B1 (en) * 2011-09-27 2014-03-18 Symantec Corporation Providing installer package information to a user
US20130246336A1 (en) 2011-12-27 2013-09-19 Mcafee, Inc. System and method for providing data protection workflows in a network environment
US9165332B2 (en) * 2012-01-27 2015-10-20 Microsoft Technology Licensing, Llc Application licensing using multiple forms of licensing
US8751567B2 (en) 2012-02-09 2014-06-10 Oracle International Corporation Quantify and measure micro-blogging for enterprise resources planning (ERP)
US9122676B2 (en) 2012-10-12 2015-09-01 International Business Machines Corporation License reconciliation with multiple license types and restrictions
GB2508645A (en) * 2012-12-07 2014-06-11 Ibm Software licence management in a peer-to-peer network
US9607189B2 (en) 2015-01-14 2017-03-28 Tactilis Sdn Bhd Smart card system comprising a card and a carrier
US9910967B2 (en) 2015-07-27 2018-03-06 International Business Machines Corporation File origin determination

Citations (25)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US4796220A (en) * 1986-12-15 1989-01-03 Pride Software Development Corp. Method of controlling the copying of software
US4924378A (en) * 1988-06-13 1990-05-08 Prime Computer, Inc. License mangagement system and license storage key
US5138712A (en) * 1989-10-02 1992-08-11 Sun Microsystems, Inc. Apparatus and method for licensing software on a network of computers
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
US5343524A (en) * 1991-06-21 1994-08-30 Mu Xiao Chun Intelligent security device
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
US5553143A (en) * 1994-02-04 1996-09-03 Novell, Inc. Method and apparatus for electronic licensing
US5671412A (en) * 1995-07-28 1997-09-23 Globetrotter Software, Incorporated License management system for software applications
US5708709A (en) * 1995-12-08 1998-01-13 Sun Microsystems, Inc. System and method for managing try-and-buy usage of application programs
US5724425A (en) * 1994-06-10 1998-03-03 Sun Microsystems, Inc. Method and apparatus for enhancing software security and distributing software
US5734425A (en) * 1994-02-15 1998-03-31 Eastman Kodak Company Electronic still camera with replaceable digital processing program
US5745879A (en) * 1991-05-08 1998-04-28 Digital Equipment Corporation Method and system for managing execution of licensed programs
US5752041A (en) * 1995-12-15 1998-05-12 International Business Machines Corporation Method and system for licensing program management within a distributed data processing system
US5790677A (en) * 1995-06-29 1998-08-04 Microsoft Corporation System and method for secure electronic commerce transactions
US5935246A (en) * 1996-04-26 1999-08-10 International Computers Limited Electronic copy protection mechanism using challenge and response to prevent unauthorized execution of software
US6005935A (en) * 1996-11-20 1999-12-21 At&T Corp. Method and system of using personal information as a key when distributing information
US6049612A (en) * 1997-03-10 2000-04-11 The Pacid Group File encryption method and system
US6056786A (en) * 1997-07-11 2000-05-02 International Business Machines Corp. Technique for monitoring for license compliance for client-server software
US6105069A (en) * 1997-01-22 2000-08-15 Novell, Inc. Licensing controller using network directory services
US6188995B1 (en) * 1997-07-28 2001-02-13 Apple Computer, Inc. Method and apparatus for enforcing software licenses
US6188146B1 (en) * 1998-05-21 2001-02-13 Paris Michaels Supplying power for communications devices
US6189146B1 (en) * 1998-03-18 2001-02-13 Microsoft Corporation System and method for software licensing
US6233567B1 (en) * 1997-08-29 2001-05-15 Intel Corporation Method and apparatus for software licensing electronically distributed programs
US6343280B2 (en) * 1998-12-15 2002-01-29 Jonathan Clark Distributed execution software license server

Patent Citations (25)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US4796220A (en) * 1986-12-15 1989-01-03 Pride Software Development Corp. Method of controlling the copying of software
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
US4924378A (en) * 1988-06-13 1990-05-08 Prime Computer, Inc. License mangagement system and license storage key
US5138712A (en) * 1989-10-02 1992-08-11 Sun Microsystems, Inc. Apparatus and method for licensing software on a network of computers
US5745879A (en) * 1991-05-08 1998-04-28 Digital Equipment Corporation Method and system for managing execution of licensed programs
US5343524A (en) * 1991-06-21 1994-08-30 Mu Xiao Chun Intelligent security device
US5260999A (en) * 1991-06-28 1993-11-09 Digital Equipment Corporation Filters in license management system
US5204897A (en) * 1991-06-28 1993-04-20 Digital Equipment Corporation Management interface for license management system
US5553143A (en) * 1994-02-04 1996-09-03 Novell, Inc. Method and apparatus for electronic licensing
US5734425A (en) * 1994-02-15 1998-03-31 Eastman Kodak Company Electronic still camera with replaceable digital processing program
US5724425A (en) * 1994-06-10 1998-03-03 Sun Microsystems, Inc. Method and apparatus for enhancing software security and distributing software
US5790677A (en) * 1995-06-29 1998-08-04 Microsoft Corporation System and method for secure electronic commerce transactions
US5671412A (en) * 1995-07-28 1997-09-23 Globetrotter Software, Incorporated License management system for software applications
US5708709A (en) * 1995-12-08 1998-01-13 Sun Microsystems, Inc. System and method for managing try-and-buy usage of application programs
US5752041A (en) * 1995-12-15 1998-05-12 International Business Machines Corporation Method and system for licensing program management within a distributed data processing system
US5935246A (en) * 1996-04-26 1999-08-10 International Computers Limited Electronic copy protection mechanism using challenge and response to prevent unauthorized execution of software
US6005935A (en) * 1996-11-20 1999-12-21 At&T Corp. Method and system of using personal information as a key when distributing information
US6105069A (en) * 1997-01-22 2000-08-15 Novell, Inc. Licensing controller using network directory services
US6049612A (en) * 1997-03-10 2000-04-11 The Pacid Group File encryption method and system
US6056786A (en) * 1997-07-11 2000-05-02 International Business Machines Corp. Technique for monitoring for license compliance for client-server software
US6188995B1 (en) * 1997-07-28 2001-02-13 Apple Computer, Inc. Method and apparatus for enforcing software licenses
US6233567B1 (en) * 1997-08-29 2001-05-15 Intel Corporation Method and apparatus for software licensing electronically distributed programs
US6189146B1 (en) * 1998-03-18 2001-02-13 Microsoft Corporation System and method for software licensing
US6188146B1 (en) * 1998-05-21 2001-02-13 Paris Michaels Supplying power for communications devices
US6343280B2 (en) * 1998-12-15 2002-01-29 Jonathan Clark Distributed execution software license server

Cited By (93)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US8214295B2 (en) * 1999-02-05 2012-07-03 Icopyright, Inc. Internet system for facilitating human user advisement and licensing of copyrighted works of authorship
US20110023127A1 (en) * 1999-02-05 2011-01-27 O'donnell Lawrence Internet system for facilitating human user advisement and licensing of copyrighted works of authorship
US20110238710A1 (en) * 1999-03-05 2011-09-29 International Business Machines Corporation Software Product Inventory and Usage Information Correlated with License Agreement Information
US20060190409A1 (en) * 2000-04-28 2006-08-24 Hillegass James C Method and system for licensing digital works
US7065504B2 (en) * 2001-09-20 2006-06-20 Hitachi, Ltd. Fee imposition system for application software
US20030055788A1 (en) * 2001-09-20 2003-03-20 Toshiyuki Sakuma Fee imposition system for application software
US20120047205A1 (en) * 2002-02-01 2012-02-23 Masaya Yamamoto License information exchange system
US8745751B2 (en) 2002-02-01 2014-06-03 Panasonic Corporation License information exchange system
US8639751B2 (en) * 2002-02-01 2014-01-28 Panasonic Corporation License information exchange system
US20030177073A1 (en) * 2002-03-15 2003-09-18 Yamaha Corporation Distribution system of contents embedding license machine ID
US8086537B2 (en) 2002-03-15 2011-12-27 Yamaha Corporation Distribution system of contents embedding license machine ID
US20080295182A1 (en) * 2002-03-15 2008-11-27 Yamaha Corporation Distribution System of Contents Embedding License Machine ID
US20030204723A1 (en) * 2002-04-30 2003-10-30 Microsoft Corporation Digital license with referral information
US7366915B2 (en) * 2002-04-30 2008-04-29 Microsoft Corporation Digital license with referral information
US7970710B2 (en) * 2003-02-25 2011-06-28 Siemens Aktiengesellschaft Method for carrying out the premium-based recommendation of content objects that can be downloaded to a mobile terminal
US20060150180A1 (en) * 2003-02-25 2006-07-06 Siemens Aktiengesellschaft Method for carrying out the premium-based recomendation of content objects that can be downloaded to a mobile terminal
US20050044048A1 (en) * 2003-08-21 2005-02-24 Intel Corporation Access control apparatus, systems, and methods
US20050076334A1 (en) * 2003-10-03 2005-04-07 Michael Demeyer System and method for licensing software
US20060015465A1 (en) * 2004-07-13 2006-01-19 Hiroshi Kume Apparatus, method and program for license information ascertainment
US20060064388A1 (en) * 2004-09-22 2006-03-23 Nokia Corporation Method and system for the total decoupling of licenses from associated license protected configuration
US20100004938A1 (en) * 2004-12-30 2010-01-07 Abb Ab Software licensing system
US8099365B2 (en) 2005-01-24 2012-01-17 Microsoft Corporation Extended data collection for multi-merchant purchasing environment for downloadable products
US20070022017A1 (en) * 2005-01-24 2007-01-25 Microsoft Corporation Extended Data Collection For Multi-Merchant Purchasing Environment For Downloadable Products
US20060167809A1 (en) * 2005-01-24 2006-07-27 Microsoft Corporation Software assistant for multi-merchant purchasing environment for downloadable products
US20110060660A1 (en) * 2005-01-24 2011-03-10 Microsoft Corporation Digital content purchase management
US20070027779A1 (en) * 2005-01-24 2007-02-01 Microsoft Corporation Add License Anonymously To Product Locker For Multi-Merchant Purchasing Environment
US7797678B2 (en) * 2005-04-07 2010-09-14 International Business Machines Corporation Automatic generation of license package for solution components
US20060229994A1 (en) * 2005-04-07 2006-10-12 Moulckers Ingrid M Automatic generation of license package for solution components
US20080195548A1 (en) * 2005-04-11 2008-08-14 Hyun Gon Chu License Data Structure and License Issuing Method
US20060235802A1 (en) * 2005-04-19 2006-10-19 Realnetworks, Inc. License confirmation via embedded confirmation challenge
US8336090B2 (en) * 2005-05-24 2012-12-18 Rhapsody International Inc. System and method for unlimited licensing to a fixed number of devices
RU2472216C2 (en) * 2005-05-24 2013-01-10 Рэпсоди Интернэшнл Инк. System and method of providing unlimited licensing to limited number of devices
US20080134312A1 (en) * 2005-05-24 2008-06-05 Napster Llc System and method for unlimited licensing to a fixed number of devices
US20060272031A1 (en) * 2005-05-24 2006-11-30 Napster Llc System and method for unlimited licensing to a fixed number of devices
WO2006127359A3 (en) * 2005-05-24 2007-10-25 Napster Llc System and method for unlimited licensing to a fixed number of devices
US20070027815A1 (en) * 2005-07-29 2007-02-01 Symantec Corporation Systems and methods for centralized subscription and license management in a small networking environment
US20070041584A1 (en) * 2005-08-16 2007-02-22 O'connor Clint H Method for providing activation key protection
US8886702B2 (en) * 2005-10-06 2014-11-11 Nokia Siemens Networks Gmbh & Co. Kg Hardware triggering in a management system
US20100191795A1 (en) * 2005-10-06 2010-07-29 Gerhard Hering Hardware Triggering in a Management System
US20070106617A1 (en) * 2005-11-08 2007-05-10 Paul Mabray Legal compliance system for the sale of regulated products or services
US20080281625A1 (en) * 2006-01-19 2008-11-13 Tokyo Electon Limited Substrate processing apparatus, license management program, license information serving apparatus, license information providing program, license management system, and recording medium
US9471756B2 (en) * 2006-06-27 2016-10-18 Intuit Inc. Method and apparatus for authorizing a software product to be used on a computer system
US20070299779A1 (en) * 2006-06-27 2007-12-27 Edmund Yu Liang Sung Method and apparatus for authorizing a software product to be used on a computer system
US8660964B2 (en) * 2006-06-30 2014-02-25 Hewlett-Packard Development Company, L.P. Secure device licensing
US20080005033A1 (en) * 2006-06-30 2008-01-03 Clark Charles F Secure device licensing
CN101118579B (en) 2006-08-01 2010-05-12 华为技术有限公司 Verification permissive method and system
US7603318B1 (en) * 2006-10-24 2009-10-13 Adobe Systems Incorporated License distribution
US7962424B1 (en) 2006-10-24 2011-06-14 Adobe Systems Incorporated Overdraft licenses and license distribution
EP2009524A3 (en) * 2007-01-26 2015-09-02 Rockwell Automation Technologies, Inc. Authentication for licensing in an embedded system
US9264902B1 (en) 2007-03-02 2016-02-16 Citigroup Global Markets Inc. Systems and methods for remote authorization of financial transactions using public key infrastructure (PKI)
US9462473B2 (en) 2007-03-02 2016-10-04 Citigroup Global Markets, Inc. Systems and methods for remote authorization of financial transactions using public key infrastructure (PKI)
US20080243699A1 (en) * 2007-03-29 2008-10-02 Microsoft Corporation License optimization and automated management
US8069119B2 (en) 2007-04-02 2011-11-29 Edward Curren System and method for software license management for concurrent license management and issuance
US20080244754A1 (en) * 2007-04-02 2008-10-02 Edward Curren System and Method for Software License Management for Concurrent License Management and Issuance
US20090177740A1 (en) * 2007-04-02 2009-07-09 Edward Curren System and Method for Software License Management for Concurrent License Management and Issuance
US8856867B1 (en) * 2007-06-28 2014-10-07 Intuit Inc. Technique for controlling access to program assets
US20090012871A1 (en) * 2007-07-05 2009-01-08 Medical Justice Corp. Method and system for reducing consumption of addictive commodities
US8732021B2 (en) * 2007-07-05 2014-05-20 Medical Justice Corp. Method and system for reducing consumption of addictive commodities
US20090048691A1 (en) * 2007-08-16 2009-02-19 Honeywell International Inc. Embedded building conroller with stored software license information
US9147049B2 (en) 2007-08-16 2015-09-29 Honeywell International Inc. Embedded building conroller with stored software license information
US20090089864A1 (en) * 2007-09-28 2009-04-02 Nokia Corporation Remote management of telecommunications network element during license expire and renewal period
US20090249488A1 (en) * 2008-03-28 2009-10-01 Sap Ag Flexible appliance hosting with coordination of deployment, licensing and configuration
US8321948B2 (en) * 2008-03-28 2012-11-27 Sap Ag Flexible appliance hosting with coordination of deployment, licensing and configuration
US8646091B2 (en) * 2008-05-22 2014-02-04 Dell Products L.P. Digital software license procurement
US20090290716A1 (en) * 2008-05-22 2009-11-26 Dell Products L.P. Digital software license procurement
US20090326964A1 (en) * 2008-06-25 2009-12-31 Microsoft Corporation Extensible agent-based license structure
US20100043075A1 (en) * 2008-08-13 2010-02-18 Autodesk, Inc. Licensing management utility
US20100057703A1 (en) * 2008-08-29 2010-03-04 Brandt Matthew K Systems and Methods for Automating Software Updates/Maintenance
US20100227681A1 (en) * 2009-03-03 2010-09-09 Microsoft Corporation Limited-rights local playback of digital content
US8825889B2 (en) * 2009-05-11 2014-09-02 Hewlett-Packard Development Company, L.P. Network traffic rate limiting system and method
US20100287303A1 (en) * 2009-05-11 2010-11-11 Smith Michael R Network traffic rate limiting system and method
US8443084B2 (en) * 2010-02-09 2013-05-14 Accenture Global Services Limited Enhanced upgrade path
US9075688B2 (en) 2010-02-09 2015-07-07 Accenture Global Services Limited Enhanced upgrade path
US9262154B2 (en) 2010-02-09 2016-02-16 Accenture Global Services Limited Enhanced upgrade path
US20110321025A1 (en) * 2010-02-09 2011-12-29 Accenture Global Services Gmbh Enhanced Upgrade Path
US9672578B2 (en) 2010-07-28 2017-06-06 International Business Machines Corporation Catalog-based software license reconciliation
US9122998B2 (en) * 2010-07-28 2015-09-01 International Business Machines Corporation Catalog-based software license reconciliation
US9230273B2 (en) 2010-07-28 2016-01-05 International Business Machines Corporation Creation and use of constraint templates
US9684919B2 (en) 2010-09-24 2017-06-20 Amazon Technologies, Inc. Item delivery using 3D manufacturing on demand
US8412588B1 (en) * 2010-09-24 2013-04-02 Amazon Technologies, Inc. Systems and methods for fabricating products on demand
US9159106B1 (en) 2010-09-24 2015-10-13 Amazon Technologies, Inc. Systems and methods for fabricating products on demand
US9898776B2 (en) 2010-09-24 2018-02-20 Amazon Technologies, Inc. Providing services related to item delivery via 3D manufacturing on demand
US9858604B2 (en) 2010-09-24 2018-01-02 Amazon Technologies, Inc. Vendor interface for item delivery via 3D manufacturing on demand
US9672550B2 (en) 2010-09-24 2017-06-06 Amazon Technologies, Inc. Fulfillment of orders for items using 3D manufacturing on demand
US20120089733A1 (en) * 2010-10-12 2012-04-12 Ansca, Inc. Managing Access to an Application
CN103221957A (en) * 2010-11-22 2013-07-24 英特尔公司 Secure software licensing and provisioning using hardware based security engine
US20120221709A1 (en) * 2011-02-24 2012-08-30 Bowes James R Mechanism to allow hosted and on-site implementations to manage product assets as specified by a third party
US9224111B2 (en) 2011-02-25 2015-12-29 Red Hat, Inc. Message queue based product asset management auditing system
US9135409B2 (en) 2011-05-18 2015-09-15 Hewlett-Packard Development Company, L.P. Distributing update information based on validated license information
US20150379526A1 (en) * 2014-06-26 2015-12-31 Adobe Systems Incorporated Tracking and linking mobile device activity
US9779409B2 (en) * 2014-06-26 2017-10-03 Adobe Systems Incorporated Tracking and linking mobile device activity
US20160364213A1 (en) * 2014-10-29 2016-12-15 International Business Machines Corporation Automatic generation of license terms for service application marketplaces
US9361435B1 (en) * 2015-01-14 2016-06-07 Flexera Software Llc Multi-tier digital supply chain management

Also Published As

Publication number Publication date Type
US7171662B1 (en) 2007-01-30 grant
US7809648B2 (en) 2010-10-05 grant

Similar Documents

Publication Publication Date Title
US6510513B1 (en) Security services and policy enforcement for electronic data
US6330670B1 (en) Digital rights management operating system
US6374357B1 (en) System and method for regulating a network service provider's ability to host distributed applications in a distributed processing environment
US6421779B1 (en) Electronic data storage apparatus, system and method
US5893910A (en) Method and apparatus for establishing the legitimacy of use of a block of digitally represented information
US6857067B2 (en) System and method for preventing unauthorized access to electronic data
US6799277B2 (en) System and method for monitoring software
US7415509B1 (en) Operations architectures for netcentric computing systems
US6233567B1 (en) Method and apparatus for software licensing electronically distributed programs
US6948073B2 (en) Protecting decrypted compressed content and decrypted decompressed content at a digital rights management client
US5925127A (en) Method and system for monitoring the use of rented software
US5553143A (en) Method and apparatus for electronic licensing
US7483860B2 (en) Method and system for managing software licenses
US6308266B1 (en) System and method for enabling different grades of cryptography strength in a product
US20020010863A1 (en) Method for protecting software
US20020006204A1 (en) Protecting decrypted compressed content and decrypted decompressed content at a digital rights management client
US6334118B1 (en) Software rental system and method for renting software
US20050149759A1 (en) User/product authentication and piracy management system
US20030149670A1 (en) Method and system for delivery of secure software license information
US20050289072A1 (en) System for automatic, secure and large scale software license management over any computer network
US6993664B2 (en) Method and system for licensing a software product
US6105131A (en) Secure server and method of operation for a distributed information system
US6772340B1 (en) Digital rights management system operating on computing device and having black box tied to computing device
US20020065780A1 (en) License compliance verification system
US20020042884A1 (en) Remote printing of secure and/or authenticated documents

Legal Events

Date Code Title Description
CC Certificate of correction
FPAY Fee payment

Year of fee payment: 4

AS Assignment

Owner name: MICROSOFT TECHNOLOGY LICENSING, LLC, WASHINGTON

Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:MICROSOFT CORPORATION;REEL/FRAME:034543/0001

Effective date: 20141014