Licensing management system and method in which datagrams including an address of a licensee and indicative of use of a licensed product are sent from the licensee's site

• US 5,940,504 A
• Filed: 06/29/1992
• Issued: 08/17/1999
• Est. Priority Date: 07/01/1991
• Status: Expired due to Term

• Current Assignee: Intertrust Technologies Corporation (Fidelio Acquisition Co LLC)
• Original Assignee: Infologic Software Incorporated
• Inventors: Griswold, Gary N.
• Primary Examiner(s): Kim, Kenneth S.
• Application Number:
  US07/907,934
• Time in Patent Office: 2,605 Days
• Field of Search: 364/401, 364/406, 364/464.01, 364/464.04, 380/3, 380/4, 380/5, 380/25, 395/200, 395/325, 395/575, 395/700, 395/725, 705/32, 705/44, 705/412
• US Class Current: 705/59
• CPC Class Codes: G06F 11/3419 by assessing time
• CPC Class Codes: G06F 11/3466 Performance evaluation by tracing or monitoring
• CPC Class Codes: G06F 21/1077 Recurrent authorisation
• CPC Class Codes: G06F 21/1078 Logging; Metering
• CPC Class Codes: G06F 2201/865 Monitoring of software
• CPC Class Codes: G06F 2201/88 Monitoring involving counting
• CPC Class Codes: G06F 2211/007 Encryption, En-/decode, En-/decipher, En-/decypher, Scramble, (De-)compress
• CPC Class Codes: G06F 2221/2135 Metering
• CPC Class Codes: G06F 2221/2151 Time stamp
• CPC Class Codes: G06Q 10/1091 Recording time for administrative or management purposes
• CPC Class Codes: G06Q 20/085 involving remote charge determination or related payment systems
• CPC Class Codes: G06Q 20/40 Authorisation, e.g. identification of payer or payee, verification of customer or shop credentials; Review and approval of payers, e.g. check credit lines or negative lists
• CPC Class Codes: G06Q 30/04 Billing or invoicing
• CPC Class Codes: G06Q 50/06 Energy or water supply
• CPC Class Codes: G06Q 99/00 Subject matter not provided for in other groups of this subclass

Abstract

A license management system and method for recording the use of a licensed product, and for controlling its use in accordance with the terms of the license. A licensed product invokes a license check monitor at regular time intervals. The monitor generates request datagrams which identify the licensee and the product and sends the request datagrams over a communications facility to a license control system. The license control system maintains a record of the received datagrams, and compares the received datagrams to data stored in its licensee database. Consequently, the license control system transmits reply datagrams with either a denial or an approval message to the monitor. The monitor terminates further use of the product if it receives a denial message. The monitor generates its own denial message if its request datagrams are unanswered after a predetermined interval of time. The datagrams are counted at the control system to provide billing information.

Claims

1. A method for monitoring the use of a licensed product at at least one licensee'"'"'s site, the method comprising the steps of:

generating datagrams at regular time intervals from at least one licensee'"'"'s site with a device using said licensed product;

including in each of said datagrams an address of said licensee on a communications facility, said address being designated by said communications facility without any data being provided by said licensee;

sending said datagrams including said address from said licensee'"'"'s site over said communications facility to a licensor'"'"'s site at regular time intervals while said licensed product is in use;

receiving said datagrams at said licensor'"'"'s site using a license control system;

storing in said license control system an indication of receipt of each of said datagrams; and

counting said datagrams from each licensee, using said license control system, as an indication of the use by the licensee of said licensed product.

2. A method as in claim 1, wherein:

said generating step includes the step of incorporating a model number of said licensed product in said datagrams; and

said counting step includes the step of separately counting datagrams for each product model number for each licensee.

3. A method for controlling use of a licensed product at at least one licensee'"'"'s site, the method comprising the steps of:

generating a request datagram from at least one licensee'"'"'s site with a device using said licensed product, said request datagrams including an address of the licensee on a communications facility;

first sending said request datagram including said address of said licensee from said licensee'"'"'s site over said communications facility to a licensor'"'"'s site while said licensed product is in use;

first receiving said request datagram at said licensor'"'"'s site using a license control system;

comparing said request datagram with rules and license data using said license control system at said licensor'"'"'s site to determine if use by said licensee of said licensed product is authorized, said license control system using said address in said request datagram to identify said licensee;

second sending, via said communications facility, a reply authorizing datagram to said address specified in said request datagram using said license control system, if use of said licensed product is approved; and

second receiving said reply authorizing datagram at said address and authorizing use of said licensed product for a predetermined period of time, and denying the use of said licensed product when no reply authorizing datagram is received.

4. A method as in claim 3, wherein:

said generating step includes the step of incorporating a model number of said licensed product in said request datagram;

said comparing step includes the step of comparing said rules and license data for a particular model number; and

said second sending step includes the step of transmitting said reply authorizing datagram for each product model number if use of said licensed product is approved.

5. A method as in claim 3, wherein:

said generating step includes the step of obtaining said address of said licensee from said communications facility without any data being provided by said licensee.

6. A method as in claim 3, further comprising the step of third sending to said address, via said communications facility, a reply denial datagram using said license control system if use of said licensed product is not approved as determined in said comparing step, said first sending step including the step of resending said request datagram including said address if neither a reply authorizing datagram nor a reply denial datagram is received from said licensor'"'"'s site within a predetermined time from sending said request datagram including said address.

7. A method as in claim 3, wherein:

said first sending step includes the step of sending a request datagram at regular time intervals.

8. A method as in claim 3, wherein:

said generating step includes the step of providing a datagram identification code within said request datagram;

said second sending step includes the step of inserting said datagram identification code in said reply authorizing datagram; and

said second receiving step includes the step of rejecting said reply authorizing datagram if said datagram identification code included in said reply authorizing datagram does not match said datagram identification code included in said request datagram.

9. A method as in claim 3, wherein:

said comparing step includes the step of comparing said address designating said licensee with a list of licensee addresses to determine if said address is on said list; and

said second sending step prohibits sending said reply authorizing datagram if said address designating said licensee is not on said list.

10. A method as in claim 9 further comprising the step of third sending a reply denial datagram if said facility address that identifies said licensee is not on said list.

11. A method as in claim 3, wherein:

said comparing step includes the step of comparing a license expiration date with a date at which said request datagram is received; and

said second sending step prohibits sending said reply authorizing datagram if the license expiration date is earlier than the date at which said request datagram is received.

12. A method as in claim 11, further comprising the step of third sending a reply denial datagram if the license expiration date is earlier than the date at which said datagram is received.

13. A method as in claim 3, wherein:

said comparing step includes the step of checking currentness of payments from said license; and

said second sending step prohibits sending said reply authorizing datagram if payment is overdue.

14. A method as in claim 13, further comprising the step of third sending a reply denial datagram if payment is overdue.

15. A method as in claim 3, wherein:

said generating step includes the step of incorporating in said request datagram data indicative of the number of processes currently using said licensed product at said licensee'"'"'s site;

said comparing step includes the step of comparing said number of processes using said licensed product at said licensee'"'"'s site to an authorized number; and

said second sending step prohibits sending said reply authorizing datagram if said number of processes using said licensed product exceeds said authorized number.

16. A method as in claim 15, further comprising the step of third sending a reply denial datagram if said number of processes using said licensed product exceeds said authorized number.

17. A method as in claim 3, wherein:

said second sending step includes the steps of sending said reply authorizing datagram when use of said licensed product is approved and sending a reply denial datagram when use of said licensed product is not approved, said second receiving step denying use of said licensed product when said reply denial datagram is received.

18. A method as in claim 17, wherein:

said receiving and denying step denies use of said licensed product when neither a reply authorizing datagram nor a reply denial datagram is received within a predetermined time after said request datagram is sent.

19. A method as in claim 17, further comprising the step of indicating, at a licensee'"'"'s site, a reason for denial when said reply denial datagram is received.

20. A method as in claim 3, wherein:

said licensed product comprises an executable portion and a data portion; and

said method further comprises a step of controlling use of said data portion with said executable portion.

21. A method as in claim 3 further comprising a step of allowing use of said licensed product before a reply datagram is received.

22. A system for controlling use of a licensed product comprising:

a communications facility which delivers and receives datagrams, and to which at least one licensee having a license for operating a licensed product from a licensor is connected, said licensed product having an executable portion and a data portion;

monitoring means, connected to said communications facility at a site of each licensee, for generating a request datagram including an address of said licensee on said communications facility, for transmitting said request datagram including said address over said communications facility to a site of said licensor, and for receiving and processing a reply datagram;

controlling means, connected to said communications facility at said licensor'"'"'s site, for receiving said request datagram, comparing said request datagram with rules and license data to determine if use of said licensed product is authorized, said controlling means using said address included in said request datagram to identify said licensee, and sending, via said communications facility, a reply authorizing datagram to said address if use of said licensed product is approved; and

means for controlling use of said data portion with said executable portion;

wherein said monitoring means includes means for denying use of said licensed product when no reply authorizing datagram is received.

23. A system as in claim 22, wherein:

said monitoring means sends request datagrams at regular time intervals during use of said licensed product; and

said controlling means further comprises means for counting said request datagrams received at said controlling means and means for computing an amount to be billed to said licensee in response to said counting.

24. A system as in claim 22, wherein:

said monitoring means incorporates a model number for said licensed product in said request datagram; and

said controlling means comprises means for counting request datagrams for each product model number for each licensee, in order to compute an amount to be billed to each licensee.

25. A system as in claim 22, wherein:

said monitoring means obtains said address of said licensee from said communications facility without any input from said licensee.

26. A system as in claim 22, wherein:

said controlling means sends a reply denial datagram to said address if use of said licensed product is not approved; and

said monitoring means resends said request datagram if no reply authorizing datagram and no reply denial datagram is received within a predetermined period of time after said requesting datagram is sent.

27. A system as in claim 22, wherein:

said monitoring means transmits request datagrams at predetermined time intervals.

28. A system as in claim 22, wherein:

said monitoring means incorporates a unique identification code in said request datagram;

said controlling means incorporates said identification code in said reply authorizing datagram; and

said monitoring means rejects any reply authorizing datagram which does not include said identification code as included in said request datagram.

29. A system as in claim 22, wherein:

said controlling means compares said address of said licensee with a list of licensee addresses and does not generate a reply authorizing datagram if said address of said licensee is not on said list.

30. A system as in claim 29, wherein:

said controlling means sends a reply denial datagram when said facility address is not on said list.

31. A system as in claim 22, wherein:

said controlling means compares an expiration date of a license of said licensed product with a date at which said request datagram is received by said controlling means, and does not generate a reply authorizing datagram, thus denying use of said licensed product, if the license expiration date is earlier than the date at which said request datagram is received.

32. A system as in claim 31, wherein:

said controlling means sends a reply denial datagram if the license expiration date is earlier than the date at which said request datagram is received.

33. A system as in claim 22, wherein:

said controlling means generates a reply authorizing datagram, thus denying use of said licensed product, if a payment for the use of said licensed product is overdue.

34. A system as in claim 33, wherein:

said controlling means sends a reply denial datagram if payment for the use of said licensed product is overdue.

35. A system as in claim 32, wherein:

said monitoring means includes in said request datagram data indicative of the number of processes, at a licensee'"'"'s site, currently using said licensed product; and

said controlling means does not generate a reply authorizing datagram, thus denying a use of said licensed product, if more than a predetermined number of processes using said licensed product are running at the licensee'"'"'s site.

36. A system as in claim 35, wherein:

said controlling means sends a reply denial datagram if more than said predetermined number of processes using said product are running at the licensee'"'"'s site.

37. A system as in claim 22, wherein:

said controlling means sends a reply denial datagram if use of said licensed product is not approved.

38. A system as in claim 37, wherein:

said monitoring means denies use of said licensed product when no reply authorizing datagram and no reply denial datagram is received within a predetermined time from the sending of said request datagram.

39. A system as in claim 37, further comprising means for indicating, at a licensee'"'"'s site, a reason for denial when said reply denial datagram is received.

40. A system as in claim 22, wherein:

said monitoring means includes means for permitting use of said licensed product before a reply datagram is received.

41. A system as in claim 22, wherein:

said data portion controlling means is disposed within said executable portion.

42. A system as in claim 22, wherein:

said data portion controlling means comprises a first partial controlling means disposed within said executable portion and a second partial controlling means disposed within said monitoring means.

43. A system for monitoring a licensed product comprising:

a communications facility which designates addresses to and from which said communications facility delivers and receives datagrams, and to which at least one licensee having a license for operating a licensed product from the licensor is connected, said licensee having an address designated by said communications facility;

monitoring means, connected to said communications facility at a site of each licensee, for generating datagrams including said address of said licensee, and for transmitting said datagrams including said address at periodic intervals over said communications facility to a site of said licensor; and

control means, connected to said communications facility at said licensor'"'"'s site, for receiving said request datagrams at regular time intervals, storing an indication of receipt of each of said request datagrams and counting said request datagrams from each licensee as an indication of the use by the licensee of said licensed product.

44. A system as in claim 43, wherein:

said monitoring means obtains said address of said licensee from said communications facility without any input from said licensee.

45. A system as in claim 43, wherein:

said monitoring means incorporates a product model number in said request datagrams; and

said controlling means separately counts request datagrams for each product model number for each licensee.

46. A method for notifying a licensor of the use of a licensed product at at least one licensee'"'"'s site, the method comprising the steps of:

generating datagrams at regular time intervals from at least one licensee'"'"'s site with a device using said licensed product;

including in each of said datagrams an address of said licensee on a communications facility, said address being designated by said communications facility without any data being provided by said licensee; and

sending said datagrams including said address from said licensee'"'"'s site over said communications facility to a licensor'"'"'s site at regular time intervals while said licensed product is in use.

47. A method as in claim 46 wherein:

said generating step includes the step of incorporating a model number of said licensed product in said datagrams.

48. A method for controlling use of a licensed product at at least one licensee'"'"'s site, the method comprising the steps of:

generating a request datagram from at least one licensee'"'"'s site with a device using said licensed product, said request datagrams including an address of the licensee on a communications facility;

sending said request datagram including said address of said licensee from said licensee'"'"'s site over said communications facility to a licensor'"'"'s site while said licensed product is in use; and

receiving a reply datagram at said address and denying the use of said licensed product when no reply datagram is received.

49. A method as in claim 48 wherein:

said generating step includes the step of incorporating a model number of said licensed product in said datagram.

50. A method as in claim 48, wherein:

said generating step includes the step of obtaining said address of said licensee from said communications facility without any data being provided by said licensee.

51. A method as in claim 48, wherein:

said reply datagram is one of at least a reply authorization datagram and a reply denial datagram; and

said sending step includes a step of resending said request datagram if neither a reply authorizing datagram nor a reply denial datagram is received within a predetermined time from sending said request datagram including said address.

52. A method as in claim 48, wherein said sending step includes the step of sending a request datagram at regular time intervals.

53. A method as in claim 48, wherein:

said generating step includes the step of providing a datagram identification code within said request datagram; and

said receiving step includes the step of rejecting said reply datagram if said datagram identification code included in said reply datagram does not match said datagram identification code included in said request datagram.

54. A method as in claim 48, wherein:

said generating step includes the step of incorporating, in said request datagram, data indicative of the number of processes currently using said licensed product at said licensee'"'"'s site.

55. A method as in claim 48, further comprising the steps of:

receiving a reply denial datagram; and

displaying, at a licensee'"'"'s site, a reason for denial when said reply denial datagram is received.

56. A method as in claim 48, wherein:

said licensed product comprises an executable portion and a data portion; and

said method further comprises a step of controlling use of said data portion with said executable portion.

57. A method as in claim 48 further comprising a step of allowing use of said licensed product before a reply datagram is received.

58. A system for controlling use of a licensed product comprising:

a communications facility which delivers and receives datagrams, and to which at least one licensee having a license for operating a licensed product from a licensor is connected, said licensed product including an executable portion and a data portion;

monitoring means, connected to said communications facility at a site of each licensee, for generating a request datagram including an address of said licensee on said communications facility, for transmitting said request datagram including said address over said communications facility to a site of said licensor;

for receiving and processing a reply datagram; and

for denying use of said licensed product when no reply datagram is received; and

means for controlling use of said data portion with said executable portion.

59. A system as in claim 58, wherein:

said monitoring means sends request datagrams at regular time intervals during use of said licensed product.

60. A system as in claim 58 wherein:

said monitoring means incorporates a model number for said licensed product in said request datagram.

61. A system as in claim 58, wherein said monitoring means obtains said facility address of said licensee from said communications facility without any input from said licensee.

62. A system as in claim 58, wherein:

said monitoring means resends said request datagram if no reply authorizing datagram and no reply denial datagram is received within a predetermined period of time after said requesting datagram is sent.

63. A system as in claim 58, wherein said monitoring means transmits request datagrams at predetermined time intervals.

64. A system as in claim 58, wherein:

said monitoring means incorporates a unique identification code in said request datagram; and

said monitoring means rejects any reply authorizing datagram which does not include the same identification code as included in said request datagram.

65. A system as in claim 58, wherein:

said monitoring means includes, in said request datagram, data indicative of the number of processes at a licensee'"'"'s site currently using said licensed product.

66. A system as in claim 58, wherein:

said monitoring means denies use of said licensed product when no reply authorizing datagram and no reply denial datagram is received within a predetermined time from the sending of said request datagram.

67. A system as in claim 58, further comprising means for indicating, at a licensee'"'"'s site, a reason for denial when a reply denial datagram is received.

68. A system as in claim 58, wherein said data portion controlling means is disposed within said executable portion.

69. A system as in claim 58, wherein said data portion controlling means comprises a first partial controlling means disposed within said executable portion and a second partial controlling means disposed within said monitoring means.

70. A system as in claim 58, wherein said monitoring means includes means for permitting use of said licensed product before a reply datagram is received.

71. A system for notifying a licensor of use of a licensed product comprising:

a communications facility which designates addresses to and from which said communications facility delivers and receives datagrams, and to which at least one licensee having a license for operating a licensed product from the licensor is connected, said licensee having an address designated by said communications facility; and

monitoring means, connected to said communications facility at a site of each licensee, for generating datagrams including said address of said licensee, and for transmitting said datagrams including said address at periodic intervals over said communications facility to a site of said licensor.

72. A system as in claim 71, wherein said monitoring means obtains said address of said licensee from said communications facility without any input from said licensee.

73. A system as in claim 71, wherein:

said monitoring means incorporates a product model number in said request datagrams.

74. A method for monitoring the use of a licensed product at at least one licensee'"'"'s site, the method comprising the steps of:

receiving datagrams at regular time intervals at a licensor'"'"'s site using a license control system, said licensor'"'"'s site being connected to a communications facility having at least one licensee'"'"'s site connected thereto, said datagrams being generated at regular time intervals and including a facility address designated by the communications facility without any data being provided by said licensee which identifies a licensee connected to said communications facility;

storing in said license control system an indication of receipt of each of said datagrams; and

counting said datagrams from each licensee, using said licensee control system, as an indication of the use of said licensed product.

75. A method as in claim 74 further wherein:

said datagrams include a model number of each licensed product; and

said counting step includes the step of separately counting datagrams for each product model number for each licensee.

76. A method for controlling use of a licensed product at at least one licensee'"'"'s site, the method comprising the steps of:

receiving a request datagram at a licensor'"'"'s site using a license control system, said licensor'"'"'s site being connected to a communications facility having at least one licensee'"'"'s site connected thereto, said request datagram including an address of the licensee on the communications facility and being sent over said communications facility to said licensor'"'"'s site while said licensed product is in use;

comparing said received request datagram with rules and license data using said license control system at said licensor'"'"'s site to determine if use by said licensee of said licensed product is authorized, said license control system using said address in said request datagram to identify said licensee; and

sending, via said communications facility, a reply authorizing datagram to said address specified in said request datagram using said license control system if use of said licensed product is approved.

77. A method as in claim 76 wherein:

said request datagrams include a model number of said licensed product;

said comparing step includes the step of comparing said rules and license data for a particular model number; and

said sending step includes the step of transmitting said reply authorizing datagram for each product model number.

78. A method as in claim 76 further comprising the step of sending a reply denial datagram if use of said licensed product is not approved as determined in said comparing step.

79. A method as in claim 76, wherein:

said request datagrams include a datagram identification code; and

said sending step includes the step of inserting the same datagram identification code in said reply authorizing datagram.

80. A method as in claim 76, wherein:

said comparing step includes the step of comparing said address that identifies said licensee with a list of licensee addresses to determine if said facility address is on said list; and

said reply authorizing datagram is not sent if said address that identifies said licensee is not on said list.

81. A method as in claim 80 further comprising the step of sending a reply denial datagram if said facility address that identifies said licensee is not on said list.

82. A method as in claim 76, wherein:

said comparing step includes the step of comparing a license expiration date with a date at which said request datagram is received; and

said sending step includes the step of prohibiting the sending of said reply authorizing datagram if the license expiration date is earlier than the date at which said request datagram is received.

83. A method as in claim 82, further comprising the step of sending a reply denial datagram if the license expiration date is earlier than the date at which said request datagram is received.

84. A method as in claim 76, wherein:

said comparing step includes the step of checking currentness of payments from said license; and

said sending step includes the step of prohibiting the sending of said reply authorizing datagram if payment is overdue.

85. A method as in claim 84, further comprising the step of sending a reply denial datagram if payment is overdue.

86. A method as in claim 76, wherein:

said datagrams include data indicative of the number of processes currently using said licensed product at said licensee'"'"'s site;

said comparing step includes the step of comparing said number of processes using said licensed product to an authorized number; and

said sending step includes the step of prohibiting the sending of said reply authorizing datagram if said number of processes using said product exceeds said authorized number.

87. A method as in claim 86, further comprising the step of sending a reply denial datagram if said number of processes using said product exceeds said authorized number.

88. A method as in claim 76, wherein said sending step includes the steps of sending said reply authorizing datagram when use of said licensed product is approved and sending a reply denial datagram when use of said product is not approved.

89. A system for controlling use of a licensed product comprising:

a communications facility which delivers and receives datagrams, and to which at least one licensee having a license for operating a licensed product from a licensor is connected, said licensed product including an executable portion and a data portion;

controlling means, connected to said communications facility at said licensor'"'"'s site, for receiving a request datagram, said request datagram including an address of said licensee on said communications facility and being transmitted with said address over said communications facility to a site of said licensor;

comparing said request datagram with rules and license data to determine if use of said licensed product is authorized, said controlling means using said address included in said request datagram to identify said licensee; and

sending, via said communications facility, a reply authorizing datagram to said address if use of said licensed product is approved; and

means for controlling use of said data portion with said executable portion.

90. A system as in claim 89, wherein:

said request datagrams are sent at regular time intervals during use of said licensed product; and

said controlling means comprises means for counting said request datagrams received at said controlling means and means for computing an amount to be billed to said licensee in response to said counting.

91. A system as in claim 89 wherein:

said request datagrams include a model number for said licensed product; and

said controlling means comprises means for counting request datagrams for each product model number for each licensee, in order to compute an amount to be billed to each licensee.

92. A system as in claim 89, wherein:

said controlling means sends a reply denial datagram to said licensee'"'"'s site if use of said licensed product is not approved.

93. A system as in claim 89, wherein:

said request datagrams include a unique identification code; and

said controlling means incorporates the same request datagram identification code in said reply authorizing datagram.

94. A system as in claim 89, wherein said controlling means compares said address of said licensee with a list of licensee addresses and does not generate a reply authorizing datagram if said address of said licensee is not on said list.

95. A system as in claim 94, wherein said controlling means sends a reply denial datagram when said address is not on said list.

96. A system as in claim 89, wherein said controlling means compares an expiration date of a license of said licensed product with a date at which said request datagram is received by said controlling means, and does not generate a reply authorizing datagram, thus denying use of said licensed product, if the license expiration date is earlier than the date at which said request datagram is received.

97. A system as in claim 96, wherein said controlling means sends a reply denial datagram if the license expiration date is earlier than the date at which said request datagram is received.

98. A system as in claim 89, wherein said controlling means generates a reply authorizing datagram, thus denying use of said product, if a payment for the use of said licensed product is overdue.

99. A system as in claim 98, wherein said controlling means sends a reply denial datagram if payment for the use of said licensed product is overdue.

100. A system as in claim 89, wherein:

said request datagrams include data indicative of the number of processes, at a licensee'"'"'s site, currently using said licensed product; and

said controlling means does not generate a reply authorizing datagram, thus denying a use of said licensed product, if more than a predetermined number of processes using said licensed product are running at the licensee'"'"'s site.

101. A system as in claim 100, wherein said controlling means sends a reply denial datagram if more than said predetermined number of processes using said licensed product are running at the licensee'"'"'s site.

102. A system as in claim 89, wherein said controlling means sends a reply denial datagram if use of said licensed product is not approved.

103. A system as in claim 89, wherein said data portion controlling means is disposed within said executable portion.

104. A system for monitoring a licensed product comprising:

a communications facility which designates addresses to and from which said communications facility delivers and receives datagrams, and to which at least one licensee having a license for operating a licensed product from the licensor is connected, said licensee having an address designated by said communications facility; and

control means, connected to said communications facility at a licensor'"'"'s site, for;

receiving request datagrams, said request datagrams including an address of said licensee on said communications facility and being transmitted at periodic intervals over said communications facility to said licensor'"'"'s site;

storing an indication of receipt of each of said request datagrams; and

counting said request datagrams from each licensee as an indication of the use by the licensee of said licensed product.

105. A system as in claim 104, wherein:

said request datagrams include a product model number; and

said controlling means separately counts request datagrams for each product model number for each licensee.