Software license management system configurable for post-use payment business models

• US 20040167859A1
• Filed: 02/14/2003
• Published: 08/26/2004
• Est. Priority Date: 02/14/2003
• Status: Abandoned Application

• Current Assignee: Flexera Software LLC
• Original Assignee: Flexera Software LLC
• Inventors: Mirabella, Richard
• Application Number:
  US10/367,205
• Publication Number:
  US 20040167859A1
• Time in Patent Office: Days
• US Class Current: 705/59
• CPC Class Codes: G06Q 10/10 Office automation; Time management
• CPC Class Codes: G06Q 30/04 Billing or invoicing

Abstract

A software license management system configurable for post-use payment business models is described. A front-end server is configured to control usage of licensed software distributed on computers within a network including the front-end server, generate an authenticatable report of such usage according to a report schedule, and securely transmit the authenticatable report to a vendor designated destination. A back-end server corresponding to the destination is configured to receive, authenticate, and process the authenticatable report to generate processed information, and provide the processed information to business operations software for post-use payment business model purposes and other business operation purposes for software vendors.

Claims

1. A software license management system configurable for post-use payment business models, comprising:

front-end server configured to control usage of licensed software, generate an authenticatable report including information of said usage according to a report schedule, and securely transmit said authenticatable report to a designated destination; and

back-end server corresponding to said designated destination and configured to receive, authenticate, and process said authenticatable report to generate processed information, and provide said processed information to business operations software for post-use payment business model purposes.

2. The system according to claim 1, wherein said licensed software is distributed on computers within a network including said front-end server.

3. The system according to claim 1, wherein said front-end server includes:

license file including said report schedule and license terms for said licensed software;

license manager that controls usage of said licensed software and creates a report log of said usage; and

report generator that generates said authenticatable report from information within said report log and according to information in said report schedule.

4. The system according to claim 3, wherein at least one digital signature is used for authenticating said authenticatable report.

5. The system according to claim 3, wherein said license manager verifies authenticity of said report generator according to information within said report schedule before said report generator generates said authenticatable report from said information within said report log.

6. The system according to claim 3, wherein said license manager verifies authenticity of said report generator according to information within said report schedule before allowing usage of said licensed software to exceed said license terms.

7. The system according to claim 3, wherein said front-end server further includes an agent that causes said report generator to generate said authenticatable report and causes said authenticatable report to be securely transmitted to said designated destination according to information within said report schedule.

8. The system according to claim 7, wherein said back-end server includes a capture controller that receives said authenticatable report, stores said authenticable report as a file, and generates a capture indication indicating receipt of said authenticatable report.

9. The system according to claim 8, wherein said back-end server further includes a schedule table including information of when a next report is scheduled to be received from said front-end server, and wherein said capture controller updates said information of when a next report is scheduled to be received after receiving said authenticatable report from said front-end server.

10. The system according to claim 9, wherein said back-end server further includes a verify controller that responds to said capture indication to verify timeliness of said authenticatable report and to authenticate said authenticatable report according to said information in said schedule table, indicate successful verification and authentication in said schedule table, and generate a verify indication upon successful verification and authentication of said authenticatable report.

11. The system according to claim 10, wherein said back-end server further includes a calculator that responds to said verify indication to process said authenticatable report to generate said processed information.

12. The system according to claim 11, wherein said processed information includes information of whether said license terms have been exceeded.

13. The system according to claim 11, wherein said authenticatable report is an HTML file with XML tags.

14. The system according to claim 11, wherein said back-end server further includes a web query module that facilitates queries of said file storing said authenticatable report by application software.

15. The system according to claim 11, wherein said back-end server further includes a web query module that facilitates queries of said file storing said authenticatable report through a web browser.

16. The system according to claim 15, wherein said web browser runs on a computer within a network including said front-end server.

17. The system according to claim 1, wherein said front-end server securely transmits said authenticatable report to said designated destination over the Internet using secure sockets layer protocol.

18. The system according to claim 1, wherein said front-end server securely transmits said authenticatable report to said designated destination over the Internet using an encrypted email attachment.

19. A software license management system configurable for post-use payment business models, comprising:

means for generating an authenticatable report including information of usage of said licensed software by a customer according to a report schedule, and securely transmitting said authenticatable report to a destination designated by a vendor of said licensed software; and

means corresponding to said destination for receiving, authenticating, and processing said authenticatable report to generate processed information to be provided to business operations software for post-use payment business model purposes.

20. The system according to claim 19, wherein said licensed software is distributed on computers within a network including said authenticatable report generating means.

21. The system according to claim 19, wherein said authenticatable report generating means includes:

license file including said report schedule and license terms for said licensed software;

license manager that controls usage of said licensed software and creates a report log of said usage; and

report generator that generates said authenticatable report from information within said report log and according to information in said report schedule.

22. The system according to claim 21, wherein at least one digital signature is used for authenticating said authenticatable report.

23. The system according to claim 21, wherein said license manager verifies authenticity of said report generator before said report generator generates said authenticatable report from information within said report log.

24. The system according to claim 21, wherein said license manager verifies authenticity of said report generator before allowing usage of said licensed software to exceed said license terms.

25. The system according to claim 21, wherein said authenticatable report generating means further includes an agent provided by said vendor that activates said report generator and causes said authenticatable report to be securely transmitted to said designated destination according to information within said report schedule.

26. The system according to claim 25, wherein said authenticatable report receiving, authenticating, and processing means includes a capture controller that receives said authenticatable report, stores said authenticable report as a file, and generates a capture indication in a capture log indicating receipt of said authenticatable report.

27. The system according to claim 26, wherein said authenticatable report receiving, authenticating, and processing means further includes a schedule table including information of when a next report is scheduled to be received from said authenticatable report generating means, and wherein said capture controller updates said information of when a next report is scheduled to be received after receiving said authenticatable report.

28. The system according to claim 27, wherein said authenticatable report receiving, authenticating, and processing means further includes a verify controller that responds to said capture indication to verify timeliness of said authenticatable report and to authenticate said authenticatable report according to said information in said schedule table, indicate successful verification and authentication in said schedule table, and generate a verify indication in a verify log upon successful verification and authentication of said authenticatable report.

29. The system according to claim 28, wherein said authenticatable report receiving, authenticating, and processing means further includes a calculator that responds to said verify indication to process said authenticatable report to generate said processed information.

30. The system according to claim 29, wherein said processed information includes information of whether said license terms have been exceeded.

31. The system according to claim 29, wherein said authenticatable report is an HTML file with XML tags.

32. The system according to claim 29, wherein said authenticatable report, receiving, authenticating, and processing means further includes a web query module that facilitates queries of said file storing said authenticatable report by application software.

33. The system according to claim 29, wherein said authenticatable report receiving, authenticating, and processing means further includes a web query module that facilitates queries of said file storing said authenticatable report through a web browser.

34. The system according to claim 33, wherein said web browser runs on a computer within a network including said authenticatable report generating means.

35. The system according to claim 19, wherein said authenticatable report generating means securely transmits said authenticatable report to said designated destination over the Internet using secure sockets layer protocol.

36. The system according to claim 19, wherein said authenticatable report generating means securely transmits said authenticatable report to said designated destination using an encrypted email attachment.

37. A method for reporting usage of licensed software for post-use payment business model purposes, comprising:

generating an authenticatable report including information of usage of licensed software by a licensee according to a report schedule;

transmitting said authenticatable report from a customer designated source to a vendor designated destination;

receiving and authenticating said authenticatable report at said vendor designated destination; and

if authenticated, generating processed information from said authenticated report to be provided to business operations software for post-use payment business model purposes.

38. The method according to claim 37, wherein said licensed software is distributed on computers within a network.

39. The method according to claim 37, wherein at least one digital signature is used in generating said authenticatable report.

40. The method according to claim 37, wherein said transmitting said authenticatable report from a customer designated source to a vendor designated destination, comprises transmitting said authenticatable report over the Internet using secure sockets layer protocol.

41. The method according to claim 37, wherein said transmitting said authenticatable report from a customer designated source to a vendor designated destination, comprises transmitting said authenticatable report using an encrypted email attachment.

42. The method according to claim 37, wherein said receiving and authenticating said authenticatable report at said vendor designated destination, comprises authenticating said authenticatable report according to information in a schedule table corresponding to information in said report schedule.

43. The method according to claim 37, further comprising verifying the timeliness of receiving said authenticatable report according to information in a schedule table corresponding to information in said report schedule.

44. The method according to claim 37, wherein said generating processed information from said authenticatable report to be provided to business operations software, comprises generating information of usage exceeding license terms of said licensed software.

45. An apparatus comprising at least one computer configured to conditionally allow overusage of licensed software beyond license terms, generate an authenticatable report including information of said overusage, and transmit said authenticatable report to a destination for post-use payment business model purposes.

46. The apparatus according to claim 45, wherein copies of said licensed software are distributable according to said license terms on one or more computers communicatively coupled to said at least one computer.

47. The apparatus according to claim 45, wherein said overusage is recorded in one or more report logs individually maintained by corresponding ones of said at least one computer.

48. The apparatus according to claim 47, wherein said one or more report logs contain redundant information such that if one of said corresponding ones of said at least one computer malfunctions, at least one other of said one or more report logs contains correct information that is usable to correct the report log of said malfunctioning one of said at least one computer.

49. The apparatus according to claim 47, wherein said one or more report logs contain non-redundant information corresponding to different reporting entities.

50. The apparatus according to claim 45, wherein said at least one computer is further configured to provide information for a first plurality of time periods in said authenticatable report so as to overlap with information for a second plurality of time periods provided in a prior authenticatable report by said at least one computer.

51. The apparatus according to claim 45, wherein individual of said at least one computer include:

license file including a report schedule and said license terms;

license manager for controlling usage of said licensed software and creating a report log of said usage; and

report generator for generating said authenticatable report from information within said report log and according to information in said report schedule.

52. The apparatus according to claim 51, wherein at least one digital signature is used for authenticating said authenticatable report.

53. The apparatus according to claim 51, wherein said license manager verifies authenticity of said report generator according to information within said report schedule before said authenticatable report is transmitted to said destination.

54. The apparatus according to claim 51, wherein said individual of said at least one computer further include a configuration file indicating a format for said authenticatable report, and said license manager verifies authenticity of said configuration file according to information within said report schedule before said authenticatable report is transmitted to said destination.

55. The apparatus according to claim 51, wherein said license manager verifies authenticity of said report generator according to information within said report schedule before allowing said overusage of said licensed software.

56. The apparatus according to claim 51, wherein said license manager causes said report generator to generate said authenticatable report according to time information in said report schedule.

57. A method for reporting usage of licensed software, comprising providing a software module adapted to generate a plurality of authenticatable reports at scheduled times such that individual of said plurality of authenticatable reports includes information of usage of licensed software for a plurality of time periods that overlap with immediately prior and succeeding ones of said plurality of authenticatable reports generated by said software module.

58. The method according to claim 57, further comprising verifying authenticity of said software module each time before transmitting an authenticatable report generated by said software module to a destination.

59. The method according to claim 57, further comprising verifying authenticity of said software module each time before allowing an overusage of said licensed software.

60. A method for reporting usage of licensed software, comprising providing a software module adapted to generate an authenticatable report including information of usage of licensed software organized such that total time over a reporting period when N, N−

1, N−

2, and so on down to M of a counted computer resource were active using a particular feature of the licensed software, wherein N is a maximum number of said counted computer resource concurrently using said feature in said reporting period and M is an integer greater than or equal to zero.

61. The method according to claim 60, wherein said counted computer resource is a host computer being used by a user of said licensed software.

62. The method according to claim 60, wherein said software module is further adapted to generate said authenticatable report so as to provide highlighted information of overusage of said licensed software exceeding a prespecified trigger value.

63. The method according to claim 62, wherein said prespecified trigger value is based upon a prespecified period of time.

64. The method according to claim 62, wherein said prespecified trigger value is based upon a prespecified number of licenses.

65. The method according to claim 62, wherein said prespecified trigger value is greater than a purchased usage value according to license terms of said licensed software.

66. The method according to claim 60, wherein reporting of said usage of said licensed software is limited to reporting of overusage of said licensed software, wherein said overusage is determined from license terms of said licensed software.

67. A method for reporting usage of licensed software, comprising providing a software module adapted to generate an authenticatable report including information of usage of licensed software organized such that total time over a reporting period when N, N−

1, N−

2, and so on down to M users who are active using a particular feature of the licensed software, wherein N is a maximum number of said users concurrently using said feature in said reporting period and M is an integer greater than or equal to zero.

68. An apparatus comprising at least one computer configured to securely receive an authenticatable report including information of overusage of licensed software, authenticate said authenticatable report, and store information from said authenticated authenticatable report so as to be available to business operations software for post-use payment business model purposes.

69. The apparatus according to claim 68, wherein at least one digital signature included in said authenticatable report is used for authenticating said authenticatable report.

70. The apparatus according to claim 68, wherein individual of said at least one computer include a capture controller that receives said authenticatable report, stores information provided in said authenticatable report in a file, and generates a capture indication indicating receipt of said authenticatable report.

71. The apparatus according to claim 70, wherein said individual of said at least one computer further include a schedule table including information of when a next authenticatable report is scheduled to be received, and said capture controller updates said information of when said next authenticatable report is scheduled to be received after receiving said authenticatable report.

72. The apparatus according to claim 71, wherein said individual of said at least one computer further include a verify controller that responds to said capture indication to verify the timeliness of receiving said authenticatable report.

73. The apparatus according to claim 72, wherein said verify controller further authenticates said authenticatable report according to said information in said schedule table, and upon successful verification and authentication of said authenticatable report, generates a verify indication and indicates such successful verification and authentication in said schedule table.

74. The apparatus according to claim 73, wherein said individual of said at least one computer further include a calculator that responds to said verify indication to process said authenticatable report to generate processed information, and store said processed information in said file so as to be available to business operations software for post-use payment business model purposes.

75. The apparatus according to claim 74, wherein said individual of said at least one computer further include a web query module that facilitates controlled database queries through a web browser operated by an authorized user for information stored in said file.

76. The apparatus according to claim 68, wherein said business operations software includes enterprise resource planning software.

77. The apparatus according to claim 68, wherein said business operations software includes e-commerce software.

78. The apparatus according to claim 68, wherein said business operations software includes customer relationship management software.

79. The apparatus according to claim 68, wherein said business operations software includes sales force automation software.

80. A method for implementing a post-use payment business model, comprising:

receiving an authenticatable report including information of usage of licensed software;

authenticating said authenticatable report; and

processing said information of said usage of said licensed software to identify instances where said usage has exceeded license terms by a predetermined amount so as to trigger a post-use payment request.

81. The method according to claim 80, wherein said license terms includes a maximum number of concurrent users of said licensed software, and said prespecified amount is a cumulative period of time during which said usage of said licensed software exceeds said maximum number.