System and method of distributed license management

• US 8,745,223 B2
• Filed: 10/14/2005
• Issued: 06/03/2014
• Est. Priority Date: 10/14/2005
• Status: Active Grant

• Current Assignee: Psion PLC (Motorola Solutions, Inc.)
• Original Assignee: Psion PLC (Motorola Solutions, Inc.)
• Inventors: Hodul, Rastislav
• Primary Examiner(s): Vu, Viet
• Assistant Examiner(s): BELCHER, HERMAN A
• Application Number:
  US11/251,603
• Publication Number:
  US 20070088825A1
• Time in Patent Office: 3,154 Days
• Field of Search: 709/203, 709/225, 709/229, 705/59, 705/51, 726/27, 707/781
• US Class Current: 709/225
• CPC Class Codes: G06F 21/10 Protecting distributed programs or content, e.g. vending or licensing of copyrighted material protection in video systems or pay television H04N7/16 ; Digital rights management [DRM]
• CPC Class Codes: G06F 21/105 Arrangements for software license management or administration, e.g. for managing licenses at corporate level
• CPC Class Codes: G06F 2221/2137 Time limited access, e.g. to a computer or data
• CPC Class Codes: H04L 2209/603 Digital right managament [DRM]
• CPC Class Codes: H04L 2463/101 applying security measures for digital rights management data processing systems or methods, specially adapted for commerce, e.g. marketing, shopping, billing, auctions or e-commerce G06Q30/00
• CPC Class Codes: H04L 63/0876 based on the identity of the terminal or configuration, e.g. MAC address, hardware or software configuration or device fingerprint
• CPC Class Codes: H04L 63/10 for controlling access to devices or network resources
• CPC Class Codes: H04L 63/101 Access control lists [ACL]
• CPC Class Codes: H04L 9/32 including means for verifying the identity or authority of a user of the system or for message authentication, e.g. authorization, entity authentication, data integrity or data verification, non-repudiation, key authentication or verification of credentials

Abstract

A distributed license management system and method for managing software licenses are provided. The disturbed license management system comprises a repository for storing workstation information, a message interceptor for intercepting a message call coming from a workstation to a server, a workstation identification module for determining if a workstation identifier associated with the message call is defined in the repository, and a device verification module for allowing access to the server if a device identifier of a workstation is associated with the workstation identifier. The method comprises the steps of storing workstation information, intercepting a message call coming from a workstation to a server, determining if a workstation identifier associated with the message call is defined in stored workstation information, and allowing access to the server if a device identifier of the workstation is associated with the workstation identifier.

Claims

1. A computer implemented method of sharing a software license of a software among a plurality of mobile devices, the method comprising:

at a server, assigning, to a mobile device, on a first come first served basis, a server defined identifier, the server defined identifier identifying device information of the mobile device, the device information being stored on a repository and associating the mobile device with a software license, the license being shared by a plurality of mobile devices, including associating a device identifier of the mobile device with the server defined identifier in the repository, wherein the associations indicate that the mobile device is a licensed device for using the software;

at the server, managing a message call from each mobile device to the server, including;

intercepting the message call coming from first mobile device to the server, the message call having a header containing the device identifier and the server defined identifier of the first mobile device;

determining, using the server defined identifier in the header of the message call, whether the first mobile device is defined by searching the repository for the device information associated with the first mobile device;

when the first mobile device is not defined, denying the first mobile device access to the server;

when the first mobile device is defined and the device information is not associated with any device identifier, associating the device identifier in the header of the message call with the device information and accepting access from the first mobile device to the server, wherein the association indicates that the first mobile device is a licensed device for using the software;

when the first mobile device is defined and a device identifier in the device information matches the device identifier in the header of the message call, accepting access from the first mobile device to the server; and

at the server, disassociating the device identifier from the server defined identifier by clearing the device identifier in the device information in the repository in a predetermined condition so that the server defined identifier with no association with a device identifier in the repository is assignable at the step of assigning.

2. The method as claimed in claim 1, wherein the message call comprises a server defined identifier, and wherein determining comprises:

obtaining the server defined identifier from the message call.

3. The method as claimed in claim 2, wherein determining comprises:

obtaining the device identifier from the message call when the server defined identifier obtained from the message call is defined on the server,

access to the server from the first mobile device being denied when the server defined identifier obtained from the message call is associated to a device identifier different from that of the message call.

4. The method as claimed in claim 2, comprising at least one of:

denying access to the server from the first mobile device when the server defined identifier obtained from the message call is not defined in the repository; and

denying access to the server from the first mobile device when the server defined identifier obtained from the message call is associated to a device identifier different from that of the message call, in the repository.

5. The method as claimed in claim 1, comprising:

installing a license on the server to describe how many mobile devices are given connection access to the server.

6. The method as claimed in claim 1, wherein the message call comprises the server defined identifier, and wherein determining comprises:

comparing the server defined identifier obtained from the message call with the server defined identifier defined in the repository; and

sending an error message to the first mobile device when a match is not found at the step of comparing.

7. The method as claimed in claim 1, wherein associating comprises:

associating the device identifier with an available server defined identifier in the repository when there is no device identifier associated with the available server defined identifier.

8. The method as claimed in claim 5, comprising:

receiving an updated message call having a message header with a different server defined identifier.

9. The method as claimed in claim 1, comprising:

at the mobile device, storing the server defined identifier assigned during assigning, in the mobile device.

10. The method as claimed in claim 1, comprising:

at the mobile device, requesting an available server defined identifier to the server.

11. The method as claimed in claim 1, comprising:

at the server sending an error message to the first mobile device when the message call does not include a message header having the server defined identifier or the device identifier.

12. A computer-readable storage memory storing computer-executable codes for sharing a software license of a software among a plurality of mobile devices, comprising:

code for assigning, to a mobile device, on a first come first served basis, a server defined identifier, the server defined identifier identifying device information of the mobile device, the device information being stored on a repository, and associating the mobile device with a software license, the license being shared by a plurality of mobile devices, including code for associating a device identifier of the mobile device with the server defined identifier in the repository, wherein the associations indicate that the mobile device is a licensed device for using the software;

code for managing a message call from each mobile device to the server, including;

code for intercepting the message call coming from a first mobile device to the server, the message call having a header containing the device identifier and the server defined identifier of the first mobile device;

code for determining, using the server defined identifier in the header of the message call, whether the first mobile device is defined by searching the repository for the device information associated with the first mobile device;

code for denying the first mobile device access to the server when the first mobile device is not defined;

code for associating the device identifier in the header of the message call with the device information and accepting access from the mobile device to the server, when the first mobile device is defined but the device information is not associated with any identifier, wherein the association indicates that the first mobile device is a licensed device for using the software;

code for accepting access from the first mobile device to the server, when a device identifier in the device information matches the device identifier in the header of the message call; and

code for disassociating the device identifier from the server defined identifier clearing the device identifier in the device information in the repository in a predetermined condition so that the server defined identifier with no association with a device identifier in the repository is assignable for the code for assigning.

13. The method as claimed in claimed 5, comprising:

installing client software on the mobile device.