Licensing duplicated systems

• US 7,216,363 B2
• Filed: 08/30/2002
• Issued: 05/08/2007
• Est. Priority Date: 08/30/2002
• Status: Active Grant

• Current Assignee: Avaya Incorporated
• Original Assignee: Avaya Technology Corporation Miami Lakes FLA US
• Inventors: Serkowski, Robert J., Walker, William T.
• Primary Examiner(s): Barrón, Jr.; Gilberto
• Assistant Examiner(s): Nalven; Andrew L.
• Application Number:
  US10/231,957
• Publication Number:
  US 20040054909A1
• Time in Patent Office: 1,712 Days
• Field of Search: 726/10, 726/6, 726/20
• US Class Current: 726/20
• 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/629 to features or functions of an application
• CPC Class Codes: G06F 2221/2137 Time limited access, e.g. to a computer or data

Abstract

The present invention is directed to a system, comprising: (i) first and second computational components 102a and b having, respectively, first and second unique identifiers; (ii) a license file 112 comprising third and fourth identifiers 212a and b respectively associated with the first and second computational components; (iii) a license manager 113 operable to (a) obtain, from the first and second computational components, the first and second unique identifiers, (b) access the license file to obtain the third and fourth identifiers, (c) compare each of the first and second unique identifiers with one or both of the third and fourth identifiers; and (iv) a mode setting agent 124 operable to permit the one or both of the first and second computational components to perform an operation, when both the first and second identifiers match one of the third and fourth identifiers, and not permit the first and second computational components to perform the operation, when only one of the first and second identifiers matches one of the third and fourth identifiers.

Claims

1. A method for protecting actuation of a computational component, comprising:

(a) retrieving, from at least first and second computational components, at least first and second unique identifiers respectively associated with the at least first and second computational components, wherein the second computational component is a duplicate of the first computational component;

(b) accessing a license file to obtain at least third and fourth identifiers;

(c) comparing each of the at least first and second unique identifiers with at least one of the at least third and fourth identifiers;

(d) when both the first and second identifiers matches a respective one of the third and fourth identifiers, permitting at least one of the at least first and second computational components to perform an operation; and

(e) when both of the first and second identifiers do not match a respective one of the third and fourth identifiers, not permitting the at least one of the at least first and second computational components to perform an operation.

2. The method of claim 1, wherein the not permitting step is performed when one of the first and second identifiers matches one of the third and fourth identifiers and the other one of the first and second identifiers does not match one of the third and fourth identifiers and wherein in the not permitting step the at least one of the at least first and second computational components is permitted to execute a first set of instructions but not a second set of instructions.

3. The method of claim 1 further comprising:

(f) receiving a first message from a third computational component requesting permission to execute and/or continue execution and wherein the obtaining, accessing and comparing steps are performed in response to the first message, wherein the stimulus for generating the first message is at least one of initialization of the third computational component, restoration of translations by the third computational component, installation of a new license file, and periodically as the third computational component is being executed.

4. The method of claim 3, wherein the third computational component is one of a plurality of controlled applications, wherein the first message requests permission to continue execution and/or execute selected ones of a plurality of features that are to be provided by the one of the plurality of controlled applications, wherein the first and second computational components are respectively first and second processors and at least one of the first and second processors will execute the one of the plurality of controlled applications, and wherein the third and fourth identifiers are associated with the first and second processors.

5. The method of claim 4, wherein the license file comprises a plurality of controlled application definitions, each application definition corresponding to one of the plurality of controlled applications.

6. The method of claim 5, wherein each of the controlled application definitions comprises release information, license expiration information, and feature keyword information.

7. The method of claim 4, wherein the step of sending comprises the step of including a first version number of the one of the plurality of controlled applications in the first message, wherein the step of accessing comprises the step of reading a second version number from the license file of a set of the plurality of controlled applications that are allowed to execute on the at least one of the first and second processors defined by one of the first and second identifiers, wherein the step of comparing further compares the first version number with the second version number, and wherein the step of permitting further requires the first and second version numbers to match.

8. The method of claim 3, wherein the first and second computational components are processors, wherein the third computational component is a telecommunications application, and wherein each of the permitting and not permitting steps comprises sending a second message to the third computational component indicating whether or not the third computational component can execute.

9. The method of claim 1, wherein the license file comprises a duplication flag indicating whether or not the first computational component is duplicated by the second computational component, a platform type, and a platform identifier.

10. The method of claim 1, wherein the permitting step comprises the step of setting an operational mode of at least one of the at least first and second computational components to a license normal mode and wherein the not permitting step comprises the step of setting an operational mode of at least one of the at least first and second computational components to one of a license error mode and a no license mode.

11. The method of claim 10, wherein the not permitting step comprises the sub-steps of:

(e1) setting the operational mode of the at least one of the at least first and second computational components to the license error mode; and

(e2) after a predetermined time, if the license error mode is not changed to the license-normal mode setting the operational mode of the at least one of the at least first and second computational components to the no-license mode.

12. The method of claim 1, further comprising:

(f) determining whether or not a duplication flag is set, the duplication flag indicating whether or not the first computational component is duplicated.

13. A computer readable medium storing instructions for performing the steps of claim 1.

14. The method of claim 1, wherein a third computational component requests permission to execute and wherein steps (c), (d), and (e) comprise the sub-steps:

determining if the first unique identifier matches at least one of the third and fourth identifiers;

when the first unique identifier fails to match at least one of the third and fourth identifiers, not permitting the third computational component to execute after a predetermined period of time;

determining a value of a duplication flag;

when the duplication flag has a first value and when the first unique identifier matches at least one of the third and fourth identifiers, determining if the second unique identifier matches at least one of the third and fourth identifiers;

when the second unique identifier fails to match at least one of the third and fourth identifiers, not permitting the third computational component to execute after a predetermined period of time; and

when the first and second unique identifiers each match a respective one of the third and fourth identifiers, permitting the third computational component to execute longer than the predetermined period of time.

15. The method of claim 14, wherein, when the first and second unique identifiers each match a respective one of the third and fourth identifiers and when the second computational component is active, the third computational component is not permitted to execute after a predetermined period of time and, when the first and second unique identifiers each match a respective one of the third and fourth identifiers and when the first computational component is active, the third computational component is permitted to execute longer than the predetermined time period of time.

16. The method of claim 1, wherein the second computational component is designed to be on standby, wherein, when the second computational component is active and the first computational component is inactive and each of the first and second identifiers matches a respective one of the third and fourth identifiers, not permitting the second computational component to perform an operation, and wherein, when the first computational component is active and the second computational component is on standby and each of the first and second identifiers matches a respective one of the third and fourth identifiers, permitting the first computational component to perform an operation.

17. A system for protecting actuation of a computational component, comprising:

a processor;

at least first and second computational components having, respectively, at least first and second unique identifiers, wherein the second computational component is a duplicate of the first computational component;

a license file comprising at least third and fourth identifiers;

a license manager operable within a telecommunications switching system to retrieve, from the at least first and second computational components, the at least first and second unique identifiers, access the license file to obtain the at least third and fourth identifiers, compare each of the at least first and second identifiers with at least one of the at least third and fourth identifiers; and

a mode setting agent operable within the telecommunications switching system to permit at least one of the at least first and second computational components to perform an operation, when both the first and second identifiers match a respective one of the third and fourth identifiers, and not permit the at least one of the at least first and second computational components to perform the operation, when both of the first and second identifiers do not match a respective one of the third and fourth identifiers.

18. The system of claim 17, wherein the mode setting agent does not permit the at least one of the first and second computational components to perform the operation when one of the first and second identifiers matches one of the third and fourth identifiers and the other one of the first and second identifiers does not match one of the third and fourth identifiers and permits the at least one of the at least first and second computational components to execute a first set of instructions but not a second set of instructions.

19. The system of claim 17, further comprising:

an input operable to receive a first message from the mode setting agent requesting permission to execute and/or continue execution and wherein the license manager performs the obtaining, accessing and comparing steps are preformed in response to the first message, wherein the first message is generated by the third computational component during initialization of the third computational component, restoration of translations by the third computational component, installation of a new license file, and periodically as the third computational component is running.

20. The system of claim 19, wherein the operation is associated with a plurality of controlled applications, wherein the first message requests permission to continue execution and/or execute identified ones of a plurality of features that are to be provided by the one of the plurality of controlled applications, wherein the first and second computational components are respectively first and second processors and at least one of the first and second processors will execute the one of the plurality of controlled applications, and wherein the third and fourth identifiers are associated with the first and second processors.

21. The system of claim 20, wherein the license file comprises a plurality of controlled application definitions, each controlled application definition corresponding to one of the plurality of controlled applications.

22. The system of claim 21, wherein each of the application definitions comprises software name and/or release information, license expiration information, and one or more types feature keyword information.

23. The system of claim 20, wherein the first message includes a first version number of the one of the plurality of controlled applications, wherein the license manager is operable to read a second version number from the license file of a set of the plurality of controlled applications that are allowed to execute on the at least one of the first and second processors defined by one of the first and second identifiers, wherein the license manager is operable to compare the first version number with the second version number, and wherein the license manager further requires the first and second version numbers to match to permit the at least one of the at least first and second computational components to perform the operation.

24. The system of claim 19, wherein the first and second computational components are processors, wherein the third computational component is a telecommunications application, and wherein the license manager sends a second message to the mode setting agent indicating whether or not the operation can be performed.

25. The system of claim 17, wherein the license file comprises a duplication flag indicating whether or not the first computational component is duplicated by the second computational component, a platform type, and a platform identifier.

26. The system of claim 17, wherein the mode setting agent is operable to set a first operation of at least one of the at least first and second computational components to a license normal mode and set a different, second operation of at least one of the at least first and second computational components to one of a license error mode and a license-error mode.

27. The system of claim 17, wherein the mode setting agent is operable to set an operational mode of the at least one of the at least first and second computational components to the license-error mode and, after a predetermined time if the license-error mode is not changed to a license-normal mode, set the operational mode of the at least one of the at least first and second computational components to a no-license mode and wherein a common set of call processing functions are enabled in the license-normal and license-error modes and wherein at least some of the call processing functions in the set of call processing functions are disabled in the no-license mode.

28. The system of claim 17, wherein the license manager is operable to determine whether or not a duplication flag is set, the duplication flag indicating whether or not the first computational component is duplicated by the second computational component.

29. The system of claim 17, wherein a third computational component requests permission to execute, wherein the license manager determines if the first unique identifier matches at least one of the third and fourth identifiers and, when the first unique identifier fails to match at least one of the third and fourth identifiers, the mode setting agent does not permit the third computational component to execute after a predetermined period of time;

wherein the license manager determines a value of a duplication flag and, when the duplication flag has a first value and when the first unique identifier matches at least one of the third and fourth identifiers, determines if the second unique identifier matches at least one of the third and fourth identifiers, and, when the second unique identifier fails to match at least one of the third and fourth identifiers, the mode setting agent does not permit the third computational component to execute after a predetermined period of time; and

wherein, when the first and second unique identifiers each match a respective one of the third and fourth identifiers, the mode setting agent permits the third computational component to execute longer than the predetermined period of time.

30. The system of claim 29, wherein, when the first and second unique identifiers each match a respective one of the third and fourth identifiers and when the second computational component is active, the mode setting agent does not permit the third computational component to execute after a predetermined period of time and wherein, when the first and second unique identifiers each match a respective one of the third and fourth identifiers and when the first computational component is active, the mode setting agent permits the third computational component to execute longer than the predetermined time period of time.

31. The system of claim 17, wherein the second computational component is designed to be on standby, wherein, when the second computational component is active and the first computational component is inactive and each of the first and second identifiers matches a respective one of the third and fourth identifiers, the mode setting agent does not permit the second computational component to perform an operation, and wherein, when the first computational component is active and the second computational component is on standby and each of the first and second identifiers matches a respective one of the third and fourth identifiers, the mode setting agent does not permit the first computational component to perform an operation.

32. A computer readable medium in a computer system executable on a processor, comprising:

a license file for use in controlling activation of a computational component, the license file including;

first and second unique identifiers, each corresponding to a respective identifier of first and second computational components, the second component being a duplicate of the first component and

a duplication flag indicating that the second computational component is a duplicate of the first computational component; and

a license manager operable within a telecommunications switching system to access the license file to obtain the first and second identifiers, compare each of the first and second identifiers with the respective identifier received from the corresponding one of the first and second computational components; and

a mode setting agent operable within the telecommunications switching system to permit the at least one of the first and second computational components to perform an operation, when both the first and second computational components match a respective one of the retrieved identifiers, and not permit the at least one of the first and second computational components to perform the operation when both of the first and second identifiers do not match a respective one of the retrieved identifiers.

33. The medium of claim 32, wherein the first and second computational components are processors.

34. The medium of claim 33, further comprising at least one application definition comprising expiration information relating to expiration of a license associated with the license file, release information, and feature keyword information.

35. The medium claim 34, further comprising platform-type information and a platform identifier.

36. A method, comprising:

(a) receiving from a third computational component a request for permission to execute and/or continue execution;

(b) in response, retrieving from at least first and second computational components, at least first and second unique identifiers, respectively, associated with the at least first and second computational components, the second component being a duplicate of the first component;

(c) accessing a license file to obtain at least third and fourth identifiers;

(d) determining whether the first unique identifier matches at least one of the third and fourth identifiers;

(e) when the first unique identifier fails to match at least one of the third and fourth identifiers, not permitting the third computational component to execute after a predetermined period of time;

(f) determining a value of a duplication flag;

(g) when the duplication flag has a first value and when the first unique identifier matches at least one of the third and fourth identifiers, determining whether the second unique identifier matches at least one of the third and fourth identifiers;

(h) when the second unique identifier fails to match at least one of the third and fourth identifiers, not permitting the third computational component to execute after a predetermined period of time; and

(i) when the first and second unique identifiers each match a respective one of the third and fourth identifiers, permitting the third computational component to execute longer than the predetermined period of time.

37. The method of claim 36, wherein, when the first and second unique identifiers each match a respective one of the third and fourth identifiers and when the second computational component is active, the third computational component is not permitted to execute after a predetermined period of time and, when the first and second unique identifiers each match a respective one of the third and fourth identifiers and when the first computational component is active, the third computational component is permitted to execute longer than the predetermined time period of time.

38. The method of claim 37, wherein the third computational component is one of a plurality of controlled applications, wherein the first message requests permission to continue execution and/or execute identification of ones of a plurality of features that are to be provided by the one of the plurality of controlled applications, wherein the first and second computational components are respectively first and second processors and at least one of the first and second processors will execute the one of the plurality of controlled applications, and wherein the third and fourth identifiers are associated with the first and second processors.

39. The method of claim 38, wherein the license file comprises a plurality of controlled application definitions, each application definition corresponding to one of the plurality of controlled applications.

40. The method of claim 39, wherein each of the controlled application definitions comprises release information, license expiration information, and one or more types feature keyword information.

41. The method of claim 36, wherein the second computational component is designed to be on standby, wherein, when the second computational component is active and the first computational component is inactive and each of the first and second identifiers matches a respective one of the third and fourth identifiers, not permitting the third computational component to execute after the predetermined period of time, and wherein, when the first computational component is active and the second computational component is on standby and each of the first and second identifiers matches a respective one of the third and fourth identifiers, permitting the third computational component to execute longer than the predetermined period of time.