This invention relates in general to methods and data processing system program products, and more particularly, to methods and data processing system program products related to activity of a user at one or more electronic sites.
The Internet allows the access of information by a wide variety of users.
One of the challenges of the Internet has been for an entities that substantially control or own the electronic sites, such as electronic site 16, to obtain reliable information about users including user 12. While the entities may have information regarding activities of the users at their respective electronic sites, this information is typically sparse and gives only a small part of the profiles of the users.
Another attempt to get more information about users is for the entities that substantially control or own the electronic sites to form an alliance with one another to collect and share information about users at their respective electronic sites. Typically, the alliances cover a relatively small fraction of all electronic sites. To the extent users are accessing electronic sites outside the alliance, the members of the alliance do not have access to that information. Therefore, the profiles of the users include just a small portion of information regarding activities of the users.
ESAP 14 typically collects information regarding activities of its users with respect to electronic sites. However, the ESAP 14 may use the information for limited purposes, such as determining if the ESAP 14 needs additional servers, activity of one user is significantly more than all other users, and the like. Due to privacy concerns or policy considerations of the ESAP 14, it typically does not share all information that it collects regarding its subscribers' (users') activities with the entities that substantially control or own the electronic sites for the specific purpose of creating profiles of the ESAP's subscribers.
Information related to activity of a user may be provided using a method or a data processing system program product. The data processing system program product has a code embodied within a data processing system readable medium, and the code includes a set of instructions executable by a data processing system to perform the method. In one embodiment, the method includes an act of sending a first view request to a first electronic site. The electronic site is typically substantially controlled or owned by a first entity. The method further includes receiving a first view from the first electronic site. The first view substantially corresponds to the first view request. The method also includes sending first information related to the first view request to a second entity that is different from the first entity. In a specific implementation of the embodiment, the acts of sending the first view request, receiving, and sending the first information are performed by the user.
In another embodiment, a data processing system program product has a code embodied within a data processing system readable medium. The code comprises instructions executable by a data processing system of a user to perform a method of sending information related to a view request from the user for an electronic site. The information is to be sent to an entity that is different from an entity that substantially controls or owns the electronic site and is different from an Internet service provider or electronic site access provider of the user, if the user is to use such provider in accessing the electronic site.
The present invention is illustrated by way of example and not limitation in the accompanying figures, in which like references indicate same elements, and in which:
Skilled artisans appreciate that elements in the figures are illustrated for simplicity and clarity and have not necessarily been drawn to scale. For example, the dimensions of some of the elements in the figure may be exaggerated relative to other elements to help to improve understanding of embodiments of the present invention.
Embodiments of the present invention allow information to be gathered regarding a user, where the information is more accurate than data collected at an individual electronic site or by an alliance of different entities having their own electronic sites because information regarding the user's activities outside individual electronic site and the alliance is collected. In one embodiment, the user sends a view request to an electronic site and also sends information related to the view request to a user information system that includes a data base of the user's activities at electronic sites. In one embodiment, the user may be able to enable or disable the information collection. The present invention is defined in the appended claims and is better understood after reading the descriptions of the embodiments that follow.
Before describing the embodiments in more detail, some terms are defined or clarified to improve understanding. “Electronic site” includes any site where information is sent to and received from an electronic communication device, such as a computer, mobile phone, personal digital assistant, or the like. A web site is an example of a common type of electronic site. “Entity” is any individual, partnership, company, corporation, or organization.
The ESAP 14 is also bi-directionally coupled to a user information system 28 that includes a server 282 and a database 284, which is that is bi-directionally coupled to the server 282. The database 284 may be part of or separate from the server 282. In still other embodiments, the database 284 may be coupled to the ESAP 14 without an intervening data processing system. The balance of the description of the embodiments are described with respect to the server/database configuration as shown in
Unlike the data processing system for user 12, the data processing system of user 22 includes a data processing system program product that allows the user 22 to have his or her activities with respect to electronic sites recorded, as will be explained in more detail later. The data processing system program product of user 22 typically includes code embodied within a data processing system readable medium. The code includes instructions executable by a data processing system for carrying out at least one method.
In one specific implementation, the data processing system program product may be a plug-in for a browser program. Before being loaded, the plug-in may reside within a hard disk, CD-ROM, floppy diskette, or other nonvolatile memory within the data processing system of the user 22. During or after the browser program is launched, the plug-in is loaded into the random access memory or other similar volatile memory within data processing system of the user 22. Each of the memories mentioned within this paragraph includes a data processing system readable medium. The data processing system program product is not limited to a plug-in for a browser program. The data processing system program product can be part of the browser program (not a separate plug-in), a different software application, an operating system, or the like.
Many variables are possible with the code of the data processing system program product. In one embodiment, the code may include instructions where information related to view requests is always sent (cannot be disabled unless code is removed or altered). In another embodiment, the code may include instructions to allow the user 22 to determine whether the information is to be sent. The data processing system program product may have code for a user 22 to select a first mode of operation or a second mode of operation. The first mode of operation may be to enable (activate) sending the information to the user information system 28, and the second mode of operation may be to disable (deactivate) sending the information to the user information system 28. Even if the first mode of operation is activated, the user 22 is not sent a view solely in response to the information being sent to the user information system 28.
The selection of the different modes may be achieved by a pull-down menu in the browser program, buttons as part of a graphical user interface, a separate screen for reconfiguring the settings, or the like. Depending on the product, the browser program may or may not need to be relaunched for the changes to take effect. The change may be permanent until the user 22 modifies the configuration, or the code may be configured to return to the original default when the browser program is closed and later relaunched. Clearly, the product could be configured with an opposite default normally disabled). The use of the product is better understood in conjunction with the description of the method illustrated in
Unlike conventional browser programs, the product may allow recording of information related to the view request. Referring to the “YES” branch from diamond 324), the user sends information related to the view request to user information system 28 (block 346). The information can include site information related to the view request (e.g., the URL or the like), an identifier of the user 22 (e.g., Internet Protocol address, pre-assigned user identifier, a cookie, or the like), temporal information related to the view request (e.g., time stamp, time-at-view, or the like), or the like. The entity that substantially controls or owns the user information system 28 is usually different from the entities that substantially control or own the ESAP 14 or the electronic site 16. In one specific implementation, the information may be sent to the user information system 28 via the ESAP 14 as shown in
Returning to
Regardless which path is used in
Privacy issues and selection of the mode of operation (enable versus disable) for recording by the user 22 can depend on the identity of the various entities. Typically, the data processing system of user 22, the ESAP 14, the electronic site 16, and user information system 28 are not significantly or substantially controlled or owned by a single entity. In many instances, an entity does not significantly or substantially control or own more than one of the data processing systems of the user 22, the ESAP 14, the electronic site 16, and the user information system 28. However, the server 282 and database 284 are substantially controlled or owned by a single entity in most instances. Note that one of the entities may control or own part of a different entity, but such control or ownership is typically not significant (less than approximately 10% ownership of the different entity or less than approximately 10% ownership of the voting shares of the different entity). These various scenarios are not meant to prevent an entity from substantially controlling or owning one, two, three, or all four of the data processing systems of the user 22, the ESAP 14, the electronic site 16, and the user information system 28.
The entity that substantially controls or owns the user information system 28 may use the information collected or obtained as that entity deems appropriate. The entity may allow the user 22 to access his or her information. In one embodiment, the user 22 may send and the system 28 may receive an inquiry for at least some of the information collected on that user 22. In response to the request, the system 28 may send and the user would receive information regarding that the user 22 that substantially corresponds to the inquiry.
The system 28 may also be configured in a hierarchical manner, such that user 22, who has a higher priority, can obtain information on all or a portion of other users having a lower priority. In still other embodiments, the entity that substantially controls or owns the system 28 may provide a commercial service that sells part or all the information within database 284 to others, such as an entity that substantially controls or owns the electronic site 16. Although not shown, the electronic site 16 and the system 28 may be bi-directionally coupled to each other. The electronic 16 may access the system 28 to determine the content of advertising or other similar information that may be sent user 22. This content may be sent as part of the view or sent separately to the user 22.
The systems and methods described above allow a more accurate user profile to be achieved compared to information collected on a user only at an electronic site or only at electronic sites that are part of an alliance. The ability to enable/disable recording allows the user 22 to let most of his or her activities at electronic sites be recorded while not having all activities recorded. The user 22 may want activities not recorded where the user 22 might be harmed if knowledge of such activity would become publicly available.
In the foregoing specification, the invention has been described with reference to specific embodiments. However, one of ordinary skill in the art appreciates that various modifications and changes can be made without departing from the scope of the present invention as set forth in the claims below. Accordingly, the specification and figures are to be regarded in an illustrative rather than a restrictive sense, and all such modifications are intended to be included within the scope of present invention.
Benefits, other advantages, and solutions to problems have been described above with regard to specific embodiments. However, the benefits, advantages, solutions to problems, and any element(s) that may cause any benefit, advantage, or solution to occur or become more pronounced are not to be construed as a critical, required, or essential feature or element of any or all the claims. As used herein, the terms “comprises,” “comprising,” or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus.
This application is a continuation of, and claims a benefit of priority under 35 U.S.C. 120 of the filing date of U.S. patent application Ser. No. 12/902,735, filed Oct. 12, 2010, now U.S. Pat. No. 9,172,761, entitled “METHOD OF GATHERING INFORMATION RELATED TO ACTIVITY OF A USER AND A DATA PROCESSING SYSTEM PROGRAM PRODUCT,” which is a continuation of, and claims a benefit of priority from U.S. patent application Ser. No. 11/137,723, filed May 25, 2005, issued as U.S. Pat. No. 7,831,706, entitled “METHOD OF GATHERING INFORMATION RELATED TO ACTIVITY OF A USER AND A DATA PROCESSING SYSTEM PROGRAM PRODUCT,” which is a continuation of, and claims a benefit of priority from U.S. patent application Ser. No. 09/752,184, filed Dec. 29, 2000, issued as U.S. Pat. No. 6,996,612, entitled “METHOD OF PROVIDING INFORMATION RELATED TO ACTIVITY OF A USER AND A DATA PROCESSING SYSTEM PROGRAM PRODUCT,” which in turn claims priority under 35 U.S.C. § 119(e) to U.S. Patent Application No. 60/173,831, filed Dec. 30, 1999, entitled “METHOD FOR CONTROLLING WEB USAGE PATTERNS VIA THIRD-PARTY ANNOTATION SERVICES,” all of which are incorporated by reference herein for all purposes.
Number | Name | Date | Kind |
---|---|---|---|
4754428 | Schultz et al. | Jun 1988 | A |
4811207 | Hikita et al. | Mar 1989 | A |
5210824 | Putz et al. | May 1993 | A |
5212787 | Baker et al. | May 1993 | A |
5226161 | Khoyi et al. | Jul 1993 | A |
5257369 | Skeen et al. | Oct 1993 | A |
5312787 | Uchida et al. | May 1994 | A |
5331673 | Elko et al. | Jul 1994 | A |
5339392 | Risberg et al. | Aug 1994 | A |
5421015 | Khoyi et al. | May 1995 | A |
5557717 | Wayner | Sep 1996 | A |
5572643 | Judson | Nov 1996 | A |
5704017 | Heckerman et al. | Dec 1997 | A |
5727129 | Barrett et al. | Mar 1998 | A |
5732218 | Bland et al. | Mar 1998 | A |
5740430 | Rosenberg et al. | Apr 1998 | A |
5761416 | Mandal et al. | Jun 1998 | A |
5774660 | Brendel et al. | Jun 1998 | A |
5790426 | Robinson | Aug 1998 | A |
5790790 | Smith et al. | Aug 1998 | A |
5796952 | Davis et al. | Aug 1998 | A |
5870559 | Leshem et al. | Feb 1999 | A |
5878223 | Becker et al. | Mar 1999 | A |
5884282 | Robinson | Mar 1999 | A |
5918014 | Robinson | Jun 1999 | A |
5958008 | Pogrebisky et al. | Sep 1999 | A |
5960411 | Hartman et al. | Sep 1999 | A |
5999908 | Abelow | Dec 1999 | A |
6041311 | Chislenko et al. | Mar 2000 | A |
6041335 | Merritt et al. | Mar 2000 | A |
6049777 | Sheena et al. | Apr 2000 | A |
6067565 | Horvitz | May 2000 | A |
6012052 | Altschuler et al. | Jun 2000 | A |
6073241 | Rosenburg | Jun 2000 | A |
6085226 | Horvitz | Jul 2000 | A |
6092049 | Chislenko et al. | Jul 2000 | A |
6094662 | Hawes | Jul 2000 | A |
6112186 | Bergh et al. | Aug 2000 | A |
6112240 | Pogue | Aug 2000 | A |
6112279 | Wang | Aug 2000 | A |
6119103 | Basch et al. | Sep 2000 | A |
6128665 | Fields et al. | Oct 2000 | A |
6138141 | DeSimone et al. | Oct 2000 | A |
6138155 | Davis et al. | Oct 2000 | A |
6141737 | Krantz et al. | Oct 2000 | A |
6144962 | Weinberg et al. | Nov 2000 | A |
6185586 | Judson | Feb 2001 | B1 |
6185608 | Hon et al. | Feb 2001 | B1 |
6185614 | Cuomo et al. | Feb 2001 | B1 |
6199099 | Gershman et al. | Mar 2001 | B1 |
6205472 | Gilmour | Mar 2001 | B1 |
6285987 | Roth et al. | Sep 2001 | B1 |
6304904 | Sathyanarayan et al. | Oct 2001 | B1 |
6308203 | Itabashi et al. | Oct 2001 | B1 |
6321206 | Honarvar | Nov 2001 | B1 |
6321256 | Himmel et al. | Nov 2001 | B1 |
6393479 | Glommen | May 2002 | B1 |
6430539 | Lazarus et al. | Aug 2002 | B1 |
6446261 | Rosser | Sep 2002 | B1 |
6449604 | Hansen et al. | Sep 2002 | B1 |
6456305 | Qureshi et al. | Sep 2002 | B1 |
6460079 | Blumenau | Oct 2002 | B1 |
6559882 | Kerchner | May 2003 | B1 |
6581072 | Mathur et al. | Jun 2003 | B1 |
6606657 | Zilberstein et al. | Aug 2003 | B1 |
6629136 | Naidoo | Sep 2003 | B1 |
6640215 | Galperin et al. | Oct 2003 | B1 |
6643696 | Davis et al. | Nov 2003 | B2 |
6654804 | Fleming, III | Nov 2003 | B1 |
6701363 | Chiu et al. | Mar 2004 | B1 |
6732331 | Alexander | May 2004 | B1 |
6745367 | Bates | Jun 2004 | B1 |
6757740 | Parekh et al. | Jun 2004 | B1 |
6771290 | Hoyle | Aug 2004 | B1 |
6836799 | Philyaw et al. | Dec 2004 | B1 |
6839682 | Blume et al. | Jan 2005 | B1 |
6996612 | McCullough | Feb 2006 | B1 |
7155506 | McCullough | Dec 2006 | B1 |
7502994 | Kocol | Mar 2009 | B2 |
7831706 | McCullough | Nov 2010 | B1 |
7966259 | Bui | Jun 2011 | B1 |
8612891 | Singh et al. | Dec 2013 | B2 |
9172761 | McCullough | Oct 2015 | B2 |
20010037321 | Fishman et al. | Nov 2001 | A1 |
20020026519 | Itabashi et al. | Feb 2002 | A1 |
20020099815 | Davis et al. | Jul 2002 | A1 |
20030188263 | Bates | Oct 2003 | A1 |
20060123105 | Parekh et al. | Jun 2006 | A1 |
20090063656 | Blumenau et al. | Mar 2009 | A1 |
20090172159 | Kocol | Jul 2009 | A1 |
20110029663 | McCullough | Feb 2011 | A1 |
Entry |
---|
thirdvoice.com—Home Page and Frequently Asked Questions (7 pages), www.thirdvoice.com, www.thirdvoice.com/help.20/faq.htm, 2000. |
Kitts, “An Evaluation of Customer Retention and Revenue Forecasting in the Retail Sector: Investigation into the effects of Seasonality, Spending an Method” by DataSage, Inc., Oct. 25, 1999. 63 pages. |
Kitts, “RMS Revenue and Retention Forecasting Final Phase Model Specification” by DataSage, Inc., Jan. 31, 2000, 16 pages. |
Discount Store News, “Datasage Customer Analyst,” 1998. |
Montgomery, et al., “Estimating Price Elasticities with Theory-Based Priors,” J. Marketing Research, vol. 36, pp. 413-423, 1999. |
Simon, “Price Management,” Elsevier Sci Pub, pp. 13-41, 1989. |
Subrahmanyan and Shoemaker, “Developing Optimal Pricing and Inventory Policies for Retailers Who Face Uncertain Demand,” J. Retailing, vol. 72, pp. 7-30, 1996. |
Vilcassim and Chintagunta, “Investigating Retailer Product Category Pricing from Household Scanner Panel Data,” J. Retailing, vol. 71, pp. 103-128, 1995. |
Weinstein, “Tackling Technology,” Progressive Grocer, 1999. |
Wellman, “Down in the (Data) Mines,” Supermarket Business, pp. 33-35, 1999. |
RT News, “New Customer Management System Returns Lost Sales to Dick's,” RT Magazine, 1999. |
DataSage, Inc., “DataSage Customer Analyst,” Progressive Grocer, 1998. |
Miller, M., “Applications Integration—Getting It Together,” PC Magazine, Feb. 8, 1994, pp. 111-112, 116-120, 136, 138. |
PointCast 2.0 Eases Burden on Network, 3 pp., Jun. 2, 1997. |
Strom, David, The Best of Push, 7 pp., Apr. 1997. |
When Shove Comes to Push, 7 pp., Feb. 10, 1997. |
Office Action issued in U.S. Appl. No. 09/752,184, dated Mar. 26, 2004. |
Office Action issued in U.S. Appl. No. 09/752,184, dated Oct. 8, 2004. |
Cabena, Peter et al., Intelligent Miner for Data Applications Guide, IBM RedBook SG24-5252-00, Mar. 1999. |
Datasage.com News and Events—DataSage Releases netCustomer, the 1st Individualization Solution for E-Commerce, retrieved Feb. 16, 2005 from Archive.org , Aug. 2, 1999, 3 pgs. |
Datasage.com—Executive Overview—Retail, Retail Data Mining Executive Overview, retrieved Feb. 16, 2005 from Archive.org, Dec. 1998, 7 pgs. |
Gallant, Steve et al., Successful Customer Relationship Management in Financial Applications (Tutorial PM-1), Conference on Knowledge Discovery in Data, ISBN:1-58113-305-7, 2000, pp. 165-241. |
Vignette Corporation to Acquire DataSage, Inc., retrieved from Archive.org Feb. 16, 2005, Jan. 10, 2000, 3 pgs. |
Chapman, Pete et al., CRISP-DM 1.0—Step-by-step data mining guide, retrieved from www.crisp-dm.org Feb. 17, 2005, 2000, pp. 1-78. |
Office Action issued in U.S. Appl. No. 11/137,723, dated Oct. 3, 2006. |
Office Action issued in U.S. Appl. No. 11/137,723, dated Feb. 6, 2008. |
Office Action issued in U.S. Appl. No. 11/137,723, dated Aug. 20, 2008. |
Office Action issued in U.S. Appl. No. 11/137,723, dated Dec. 23, 2009. |
Office Action for U.S. Appl. No. 12/902,735, dated Feb. 1, 2011, 13 pgs. |
Office Action for U.S. Appl. No. 12/902,735, dated Jul. 20, 2011, 12 pgs. |
Office Action for U.S. Appl. No. 12/902,735, dated May 28, 2013, 10 pgs. |
Office Action for U.S. Appl. No. 12/902,735, dated Dec. 17, 2013, 10 pgs. |
Office Action for U.S. Appl. No. 12/902,735, dated May 21, 2014, 7 pgs. |
Office Action for U.S. Appl. No. 12/902,735, dated Dec. 17, 2014, 4 pgs. |
Notice of Allowance for U.S. Appl. No. 12/902,735, dated Jun. 12, 2014, 7 pgs. |
Number | Date | Country | |
---|---|---|---|
20160021203 A1 | Jan 2016 | US |
Number | Date | Country | |
---|---|---|---|
60173831 | Dec 1999 | US |
Number | Date | Country | |
---|---|---|---|
Parent | 12902735 | Oct 2010 | US |
Child | 14868068 | US | |
Parent | 11137723 | May 2005 | US |
Child | 12902735 | US | |
Parent | 09752184 | Dec 2000 | US |
Child | 11137723 | US |