Enabling and disabling software features

• US 20050044367A1
• Filed: 10/02/2003
• Published: 02/24/2005
• Est. Priority Date: 04/02/2001
• Status: Abandoned Application

• Current Assignee: Google Technology Holdings LLC (Alphabet Inc.)
• Original Assignee: Google Technology Holdings LLC (Alphabet Inc.)
• Inventors: Khair, Pascal, Bertrand, Yan Nicolas, Gasparini, Stephane Christian
• Application Number:
  US10/677,775
• Publication Number:
  US 20050044367A1
• Time in Patent Office: Days
• US Class Current: 713/172
• CPC Class Codes: G06F 21/121 Restricting unauthorised execution of programs

Abstract

This application relates to a method of enabling and disabling software features in a software-implemented feature set, to the software itself and to a device with the software thereon. In accordance with the method of the invention, a token formed from identification and feature related information is sent to an authorization device. The authorization device creates a key from this information and sends the key and information on the authorized feature set back to the device. The device generates its own version of the key and compares its version with the received version. If the two keys match, the authorized feature set is implemented.

Claims

1. A method of changing the available features in a software-implemented feature set containing a plurality of features, comprising the steps:

forming a token from identification information and feature related information and issuing the token;

receiving the token and obtaining identification information and desired feature related information from the token;

in response to a determination to authorize change in the feature set, the further steps;

using the identification information to generate an authorization key;

forming a feature change code from the authorization key and information related to an authorized feature set and issuing the feature change code; and

receiving the feature change code and obtaining the authorization key and information related to the authorized feature set from the feature change code;

generating a local authorization key using the identification information;

comparing the received authorization key with the local authorization key; and

implementing the authorized feature set if the received authorization key and the local authorization key match.

3. The method as claimed in claim 1, wherein a random number is also used in the step of forming the token.

4. The method as claimed in claim 1, wherein a random number is also used in the step of generating the local authorization key.

5. The method as claimed in claim 1, wherein the identification information comprises data relating to at least one of a software identification number;

a Device Identification number;

a Subscriber Identification Number.

6. The method as claimed in claim 5, wherein the identification information also comprises hardware version number data or software version number data.

7. The method as claimed in claim 1, where the step of forming a token comprises the step of forming a secret key from the identification data and using the secret key as an encryption key to encrypt the feature related information.

8. The method as claimed in claim 1, where the step of generating a local authorization key comprises the step of forming a secret key from the identification data.

9. The method as claimed in claim 1, where the step of generating a local authorization key uses a non-reversible operation.

10. The method as claimed in claim 1, where the token contains payment information in respect of the requested feature alteration.

2. A method of changing the available features in a software-implemented feature set containing a plurality of features, comprising the steps:

forming a token from identification information and feature related information and issuing the token;

receiving a feature change code and obtaining an authorization key and information related to an authorized feature set from the feature change code;

generating a local authorization key using the identification information;

comparing the received authorization key with the local authorization key; and

implementing the authorized feature set if the received authorization key and the local authorization key match.

11. Apparatus comprising:

means for forming a token from identification information and feature related information

means for issuing the token;

means for receiving a feature change code

means for obtaining an authorization key and information related to an authorized feature set from the feature change code;

means for generating a local authorization key using the identification information;

means for comparing the received authorization key with the local authorization key; and

means for implementing the authorized feature set if the received authorization key and the local authorization key match.

12. A method of authorizing change in the available features in a software-implemented feature set containing a plurality of features, comprising the steps:

receiving a token;

obtaining identification information and feature related information from the token;

in response to a determination to authorize change in the feature set, the further steps;

using the identification information to generate an authorization key;

forming a feature change code from the authorization key and information related to the authorized feature set; and

issuing the feature change code.

13. The method as claimed in claim 12, wherein a random number is also obtained from the received token.

14. The method as claimed in claim 13, wherein the random number is used in the step of generating the authorization key.

15. The method as claimed in claim 12, wherein the identification information comprises data relating to at least one of a software identification number;

a Device Identification number;

a Subscriber Identification Number.

16. The method as claimed in claim 12, wherein the identification information also comprises hardware version number data or software version number data.

17. The method as claimed in claim 12, where the step of obtaining information from the token comprises the step of deriving a secret key and encrypted data from the received token and using the secret key as a decryption key to decrypt the encrypted data to obtain feature related information.

18. The method as claimed in claim 12, where the step of generating an authorization key comprises the step of forming a secret key from the identification data.

19. The method as claimed in claim 12, where the step of generating a local authorization key uses a non-reversible operation.

20. The method as claimed in claim 12 where payment information in respect of the requested feature alteration is obtained from the token.

21. Apparatus for authorizing change in the available features in a software-implemented feature set containing a plurality of features, comprising:

means for obtaining identification information and feature related information from a token;

means for determining to authorize change in the feature set

means for generating an authorization key using the identification information;

means for forming a feature change code from the authorization key and information related to the authorized feature set; and

means for issuing the feature change code.