Method for attributing and allocating revenue related to embedded software

• US 8,645,941 B2
• Filed: 03/06/2006
• Issued: 02/04/2014
• Est. Priority Date: 03/07/2005
• Status: Active Grant

• Current Assignee: Gula Consulting Limited Liability Company (Intellectual Ventures LLC)
• Original Assignee: Carhamm Limited LLC (Intellectual Ventures LLC)
• Inventors: Goulden, David L., Gilbert, Charles, Zeldin, Craig
• Primary Examiner(s): Wong, Don
• Assistant Examiner(s): KRETZMER, ERIKA A
• Application Number:
  US11/368,858
• Publication Number:
  US 20060235784A1
• Time in Patent Office: 2,892 Days
• Field of Search: None
• US Class Current: 717/170
• CPC Class Codes: G06Q 30/0274 Split fees
• CPC Class Codes: G06Q 30/04 Billing or invoicing
• CPC Class Codes: G06Q 40/00 Finance; Insurance; Tax strategies; Processing of corporate or income taxes

Abstract

A method for attributing revenue for embedded software. The method includes the first step of determining the presence of more than one type of embedded software on a given client site. Then, the process assigns priority based on the length of time each type has resided on the client system and the source of each type, followed by classifying each software type, based on the history of present and predecessor copies of the software. A distribution factor is applied to each software type, based on priority and classification, partner revenue is distributed based on the distribution factor applied to each software type.

Claims

1. A method, comprising:

determining a first revenue distribution factor for a client computer system based at least in part on a first tenure of a first embedded software on the client computer system, the first tenure including a first length of time from installation of the first embedded software until the determining the first revenue distribution factor;

determining a second revenue distribution factor for the client computer system based at least in part on a second tenure of a second embedded software on the client computer system, the second tenure including a second length of time from installation of the second embedded software until the determining the second revenue distribution factor,

wherein the second tenure is less than the first tenure, and

wherein the first and second embedded software includes a first and second behavior monitoring application configured to provide targeted content to the client computer system, the targeted content based on at least a recorded behavior;

determining a third revenue distribution factor for the client computer system based at least in part on an uninstallation of the first embedded software and in response to the uninstallation, configuring the second behavior monitoring application to provide the targeted content to the client computer system; and

distributing partner revenue based at least in part on the first, second, and third revenue distribution factors and a rate schedule, the rate schedule configured to distribute a largest share of the partner revenue to an entity associated with the first revenue distribution factor.

2. The method of claim 1, further comprising determining a fourth revenue distribution factor based at least in part on a previous copy of the first embedded software that was resident in the client computer system.

3. The method of claim 1, further comprising determining a fourth revenue distribution factor based at least in part on a prior embedded software that was installed on the client computer system prior to at least a partially duplicative embedded software installed on the client computer system.

4. The method of claim 1, further comprising determining a fourth revenue distribution factor based at least in part on uninstalled embedded software which remained in response to an uninstallation of at least a partially duplicative embedded software on the client computer system.

5. The method of claim 1, further comprising determining a fourth revenue distribution factor based at least in part on other embedded software installed after uninstallation of at least a partially duplicative embedded software on the client computer system.

6. The method of claim 1, further comprising:

determining a presence of the first embedded software in a computer-readable storage medium of the client computer system.

7. The method of claim 6, further comprising:

determining an other presence of an other embedded software in the computer readable storage medium of the client computer system; and

identifying the other embedded software as duplicative of the first embedded software.

8. The method of claim 7, wherein the first embedded software is considered to be duplicative of the other embedded software in response to the first embedded software being duplicative of the other embedded software.

9. The method of claim 7, wherein the first embedded software is an earlier version of the other embedded software.

10. The method of claim 1, wherein another embedded software is associated with another entity and wherein the entity is distinct from the another entity.

11. The method of claim 1, further comprising determining a fourth revenue distribution factor based at least in part on a previous copy of an other embedded software that has been resident in the client computer system.

12. The method of claim 1, wherein the first, second, and third revenue distribution factors are determined at predetermined times.

13. The method of claim 12, wherein the first, second, and third revenue distribution factors are determined on a monthly basis.

14. The method of claim 1, wherein the rate schedule is further configured to distribute a smaller share of the partner revenue to a second entity associated with the third revenue distribution factor.

15. The method of claim 14, wherein the rate schedule is further configured to distribute a smallest share of the partner revenue to a third entity associated with the second revenue distribution factor.

16. A non-transitory computer-readable medium storing executable instructions that, when executed, cause a computer to perform operations comprising:

determining a first revenue distribution factor for a client computer system based at least in part on a first tenure of a first embedded software on the client computer system, the first tenure including a first length of time from installation of the first embedded software until the determining the first revenue distribution factor;

determining a second revenue distribution factor for the client computer system based at least in part on a second tenure of a second embedded software on the client computer system, the second tenure including a second length of time from installation of the second embedded software until the determining the second revenue distribution factor,

wherein the second tenure is less than the first tenure, and

wherein the first and second embedded software includes a first and second behavior monitoring application configured to provide targeted content to the client computer system, the targeted content based on at least a recorded behavior;

determining a third revenue distribution factor for the client computer system based at least in part on an uninstallation of the first embedded software and in response to the uninstallation, configuring the second behavior monitoring application to provide the targeted content to the client computer system; and

distributing partner revenue based at least in part on the first, second, and third revenue distribution factors and a rate schedule, the rate schedule configured to distribute a largest share of the partner revenue to an entity associated with the first revenue distribution factor.