Patent Grant
9870426
Generally described, computing devices and communication networks can be utilized to exchange information. In one use, a computing device can request information from content providers via a communication network. Content providers can be, for example, Web sites such as blog sites, e-commerce sites, search engines, social network sites, and the like. For example, a user of a personal computing device can utilize a browser to request content (e.g., a Web page) from a server computing device via the Internet. In such embodiments, the user computing device can be referred to as a client computing device and the server computing device can be referred to as the content provider.
To facilitate accessing a history of accessed network resources, browsers provide navigation controls that allow users to provide an indication that they wish to return to a previously accessed network resource. For example, browsers provide a graphical icon or control that corresponds to a user request to access the most recent previously accessed network resource, often referred to as a “back button” or “back arrow.” Upon receipt of such a request, a browser can utilize an access history of the network resource identifiers (e.g., URLs) that have been accessed over a defined period of time to identify the most recent resource identifier listed in the history and attempt to display and/or access the network resource corresponding to the identifier again. Multiple selections of such a back button navigation control cause the browser to display the network resources in the reverse order of a particular user's access history. A “forward button” navigation control further facilitates selection of content from network resources in the forward order of the user's access history.
Because users can access the same network resources multiple times, browsers often attempt to improve performance and/or convenience by maintaining information about the network resources (e.g., Web pages) that have been accessed. As previously discussed, the information maintained by the browser applications can include an access history of the network resource identifiers (e.g., URLs) that have been accessed over a defined period of time. The information maintained by the browser application can also include user or account identifiers that are exchanged between the browser application and the content provider that allow for the identification of users and customization of content by the content provider. This information may be retained or referenced in what is known as “Web cookies,” among other possibilities. Additionally, the information maintained by the browser application can include information provided by a user while accessing a network resource, such as user identifiers/login data, password data, form or text entry data, and the like. Still further, the information maintained by the browser can include locally stored (e.g. cached) copies of embedded text, images, and other content utilized in the rendering of the network resource, such as in a file or memory.
The foregoing aspects and many of the attendant advantages will become more readily appreciated by reference to the following detailed description, when taken in conjunction with the accompanying drawings, wherein:
Generally described, aspects of the present disclosure relate to the management of content and information corresponding to the access of content. Specifically, aspects of the present disclosure relate to the selective management of information collected by a software application such as a browser. The browser obtains content by accessing a network resource, such as a Web page, from a content provider and collects information associated with the display and interaction of the network resource by a user. In one embodiment, the browser presents, among other controls or icons, a graphical icon that is representative of an integrated command to remove access information collected while accessing the current network resource and to cause the browser application to return to display a previously accessed network resource. Thus, responsive to a selection of the graphical icon, the browser removes at least a portion of the access information associated with the current network resource and also returns to display the previously accessed network resource without any additional interaction from the user. Accordingly, the user is able to return to the previously displayed Web page and remove the appropriate access information from the computing device such that the computing device returns to a state before the Web browser accessed the current network resource, all in a single action.
For purposes of illustration, a user accesses a series of Web pages utilizing a browser on a client computing device, e.g., a tablet computer, a personal computer, an e-book reader, etc. As the browser is accessing each Web page under the control of a user, the browser is configured to collect and maintain access information, such as by adding the URL of the current Web page to a history, storing cookies transmitted by the content provider, and saving password and form information utilized while the user accessed the Web page. During the particular browsing session, the user utilizes conventional navigation controls to access a previously accessed Web page (e.g., a “back button”) and return to the Web page (e.g., a “forward button”). At some point, however, the user decides that he or she wishes to not only return to the previously accessed Web page, but that at least some or all information associated with the current Web page should be removed by the browser application. In this respect, the computing device returns to a state before the Web browser accessed the Web page and electronic artifacts stored on the computing device are removed. Accordingly, the user selects a different navigation control that corresponds to an integrated command to access the previously accessed Web page and to remove all the access information the browser application had collected when the user accessed the current Web page (“integrated command”). From the user perspective, the browser deletes at least some or all information corresponding to the current Web page and automatically accesses the previously accessed Web page by simply selecting the integrated command.
In another illustrative example, a user accesses a Web page that corresponds to a search provider. Based on a search query, the search provider returns a listing of URLs that may be relevant to the search query. Upon accessing one of the identified URLs, the user determines that this URL was either not appropriate or not relevant. By selecting a graphical control that corresponds to the integrated command, the user can return to the previously accessed Web page that included the search results and cause the removal of at least some or all information from the browser that is associated with the URL that was determined to be not appropriate or not relevant. Additionally, in the same or another embodiment, the browser can be configured to transmit a notification to the search provider that informs the search provider that the user utilized the integrated command. As such, the search provider can utilize the information to, among other possibilities, modify its relevance ranking systems such that the search listings for subsequent queries by the users and/or others is modified. In some embodiments, the search provider can modify the presentation of the URL to the user to be indicative of the user's previous utilization of the integrated command with respect to the network resource at that URL. In some embodiments the search provider can alert other users that the integrated action of deleting and displaying the previous Web page has occurred with one or more other users.
According to another example, a user accesses a Web page that corresponds to an e-commerce provider. The user is browsing a selection of items for consumption (e.g. sale, rental, etc.) presented through a browser interface. The e-commerce provider uses the browsing activity of the users to later make suggestions to the user in which the user may be interested. For example, if the user has browsed mystery books in the past, the e-commerce Web site may provide automated recommendations for mystery books in the future. While the user is searching for items in the catalog the user views a product Web page listing details for an item that does not accurately reflect the user's interests and for which the user does not want their automated recommendations to present related products. To avoid this issue, the user then selects the graphical control that corresponds to the integrated command causing the software browsing application to return to displaying the previously accessed Web page (e.g. a prior product page, browse page, search result page) and causes the removal of all access information from the browser that is associated with the URL associated with the product page that lists details for the item that does not accurately reflect the user's interests. Additionally, in one embodiment, without any additional action by the user, the browser transmits a notification to the e-commerce provider informing it that the user utilized the integrated command. As such, the e-commerce provider can utilize the information to, among other possibilities, remove the product page from the user's browsing history such that its visit does not affect the user's recommendations. In some embodiments the e-commerce provider could modify the presentation of the URL to the user be indicative of previous utilization of the integrated command or could alert other users that the integrated action of deleting and displaying the previous product page has occurred with one or more other users.
Although examples are provided in which the browser displays the most recently accessed network resource in response to a user selecting the integrated command, in other embodiments the integrated command may cause the browser to display any of a number of other network resources. For example, the browser application may display a predefined network resource, such as a “home page.” Additionally, in some embodiments the browser application could display a subsequent viewed page in a user's access history in response to the integrated command.
With reference to the previous illustrative examples, the user can be presented with a number of graphical icons that are associated with an integrated command. In one approach, a browser can include a first graphical icon that corresponds to a traditional “back button” and a second graphical icon that corresponds to the integrated command. In this approach, the two graphical icons can be distinguished based on size, color, or placement on the display screen. In another approach, a browser can include a single graphic icon that corresponds to a combination of a conventional “back button” and the integrated command. In one example, a graphical icon can include a portion for selecting the functionality traditionally associated with a back navigation control and a second portion for selecting the integrated command. In another example, the control corresponding to the functionality traditionally associated with a back navigation control is embodied as a small back button icon that can be at least partially superimposed over a larger icon corresponding to the integrated command.
In accordance with another illustrative example, a user accesses one or more Web pages utilizing a computing device that has a touch user interface. As the user is accessing a particular Web page, the user decides that he or she wishes to not only return to a previously accessed Web page, but that information associated with the current Web page should be removed by the browser. In lieu of manipulating any type of graphical icon, the user makes some type of gesture on the touch interface (e.g., a swipe pattern) or selects a quadrant of the touch interface (e.g., holding a finger down for a predetermined time). Based on the gesture, the browser, without any additional interaction from the user, deletes all access information on the computing device corresponding to the current Web page and accesses the previously accessed Web page.
In accordance with a further illustrative example, a user accesses one or more Web pages utilizing a computing device that has audio input (e.g., a microphone). As the user is accessing a particular Web page, the user decides that he or she wishes to not only return to a previously accessed Web page, but that at least some or all information associated with the current Web page should be removed by the browser. In this example, to initiate the integrated command control, the user utters a predetermined phrase, such as “Back and Forget.” Based on processing and matching the received voice data, the browser, without any additional interaction from the user, deletes at least some or all information corresponding to the current Web page and accesses the previously accessed Web page.
With reference to yet another illustrative example, a user initiates a request for a Web page utilizing a browser. In this example, the request for the Web page is transmitted to a network accessible computing provider that initiates a network-based virtual machine instance that requests the Web page on behalf of the client computing device via a browser executing on the virtual machine instance. The browser executing on the virtual machine instance works in conjunction with the browser on the client computing device in order to process the content associated with the current Web page. During a particular browsing session, the user utilizes traditional navigation controls to access one or more Web pages, information of which is maintained as browser access information at both at the client computing device and the virtual machine instance. At some point, the user selects or initiates a control corresponding to the integrated command (e.g., the selection of a graphical icon) and the browser, without any additional interaction from the user, deletes all access information corresponding to the current Web page that maintained on the client computing device. Additionally, the browser transmits a notification to the virtual machine instance to cause the same processing of the received integrated command on the browser executing on the virtual machine instance.
As used herein, the information collected or generated by the browser or client computing device while accessing network resources will be collectively referred to as “browser access information.” However, reference to “browser access information” does not imply any limitation as to any singular type or specific instance of information or any combination of information. Additionally, although various examples in the detailed description describe removal of the browser access information, any modification of the information that effectively removes any history of the computing system accessing the network resource is contemplated. For example, modifications such as deletion, encryption, or obfuscation of the browser access information is contemplated. The browser access information could also be modified by moving it to another location (e.g. in a location not accessible by the browser). Additionally, reference to “client computing device” will not necessarily be limited to any particular type of device or to the illustrative examples of devices described herein. Still further, reference to “browser” will not necessarily be limited as to any type of software application and does not prevent the incorporation of aspects of the present disclosure into other types of software applications or operating system functionality. For example, although a browser application is used to describe various embodiments the application could be, among others, an application dedicated for the navigation content of a specific remote content provider such as commonly used on mobile devices, tablets, e-readers, and the like. Although aspects of the present disclosure will be described with regard to an illustrative network environments and component interactions, flow diagrams, graphical icons and user interfaces, one skilled in the relevant art will appreciate that the disclosed embodiments are illustrative in nature and should not be construed as limiting.
Accordingly,
With reference now to
In an illustrative embodiment, the client computing devices 102 include necessary hardware and software components for establishing communications over a communication network 116, such as a wide area network or local area network. For example, the client computing devices 102 may be equipped with networking equipment and browsers that facilitate communications via the Internet or an intranet.
Illustratively, the client computing devices 102 may have varied local computing resources such as central processing units and architectures, memory, mass storage, graphics processing units, communication network availability and bandwidth, etc. Generally, however, each computing device 102 may include one or more processing units, such as one or more CPUs. The client computing device 102 may also include system memory, which may correspond to any combination of volatile and/or non-volatile storage mechanisms. The system memory may store information that provides an operating system component, various program modules, program data, or other components. The client computing device 102 performs functions by using the processing unit(s) to execute instructions provided by the system memory. The client computing device 102 may also include one or more input devices (keyboard, mouse device, specialized selection keys, touch screen interface, stylus, etc.) and one or more output devices (displays, printers, audio output mechanisms, etc.). The client computing device 102 may also include one or more types of removable storage and one or more types of non-removable storage. Still further, the client computing device 102 can include communication components for facilitating communication via wired and wireless communication networks, such as the wireless communication network 116.
As illustrated in
The content delivery environment 100 can also include one or more content providers 110 in communication with the one or more client computing devices 102 or other service providers via the communication network 116. The content provider 110 illustrated in
With continued reference to
With reference now to
With reference to
Upon accessing the network resource, e.g., a Web page, document, video object, audio object, etc., and receiving any associated content from the content provider 110, the client computing device 102, such as through the browser 104, begins collecting (3) various information related to the access of the specific network resource. As previously described, such information can be generally referred to as browser access information (or access information). Illustratively, the browser access information can include the URL, or other network resource identifier, that can then be added to a history of URLs maintained by the browser 104. The browser access information can also include user identification information or account identification information provided by the content provider 110 or generated on behalf of a user/user account associated with the client computing device 102. Examples of the user or account identification information can include display preferences, content filtering preferences, cookies, electronic tokens, and the like. The browser access information can further include information associated with the presentation of content on the client computing device 102 or with the interaction with the network resource, including, but not limited to, form data, password data, downloaded images and text, advertisements, video content, and the like.
With reference to
In addition to the deletion of selected browser access information, the browser 104 can request (6) a previously accessed network resource, such as the network resource that immediately preceded the current network resource, or some other specified network resource, such as one associated with a browser “home” page. The browser 104 may be able to display and/or access the previously accessed network resource, at least in part, with the utilization of cached information and proxy server components. Thus, in some embodiments the access of the previously accessed network resource causes the browser to retrieve the network resource from the content provider again before displaying it. However, in some embodiments the browser retrieves the previously accessed network resource from its internal cache and/or intermediate client computing devices rather than accessing the network resource by retrieving it over the network (again) from the content provider.
As further illustrated in
With reference now to
With continued reference to
One skilled in the relevant art will appreciate that NCCs utilize physical computing device resources and software to provide multiple instances of a virtual machine or to dynamically cause the creation of instances of a virtual machine. As applied to the present disclosure, the virtual machine instances execute a browser 126 that is in communication with the browser 104 on the client computing device 102. In this embodiment, the browser executed on the virtual machine instance works in conjunction with the browser 104 on the client computing device 102 to process content retrieved from content provider 110. The NCCs may further include additional software or hardware components that facilitate communications including, but not limited to, load balancing or load sharing software or hardware components for selecting instances of a virtual machine supporting a requested application or providing information to a DNS nameserver to facilitate request routing. Although embodiments of the NCC are described as using virtual machines to host browsers 126 in communication with the browser 104 on the client computing device, in some embodiments the browsers may hosted on physical (non-virtual) machines such as computing device 122.
With reference now to
With reference to
As illustrated in
With reference to
With reference to
In addition to the deletion of the selected browser access information, the browser 104 accesses and/or displays (10) a previously accessed network resource, such as the network resource that immediately preceded the currently accessed network resource. The browser 104 may be able to access the previously accessed network resource, at least in part, with the utilization of cached information and proxy server components. As further illustrated in
Turning now to
At block 302, the browser 104 obtains user input or indications of user input, such as via information provided to the input interface component 106. In one embodiment, the user input can correspond to a selection of a graphical icon or control provided by, or otherwise associated with, the browser 104. Example graphical icons and controls that are associated with a browser 104 will be described with regard to
At decision block 304, a test is conducted to determine whether the received input corresponds to an integrated command to remove information associated with a current network resource and access a previously accessed network resource. In one embodiment, if a graphical icon is reflective solely of the integrated command to remove information associated with a current network resource and access a previously accessed network resource, a selection of the graphical icon will be indicative of selection of the integrated command. In another embodiment, if a graphical icon combines multiple controls into distinct portions, the input interface component 106 can conduct additional processing to determine whether or not the selection corresponds to a selection of an integrated command. For example, if the combined graphical icon includes multiple, distinct portions, a selection of the appropriate portion will be indicative of the selection of the integrated command. In another example, a length of time in which a combined graphical icon is selected through a user interface, such as through a mouse interface or touch screen interface, can be indicative of the selection of the integrated command. In this example, the input interface component 106 (
In a further embodiment, the input interface component 106 may utilize additional data processing techniques such as voice data processing, pattern matching, video matching and the like to determine whether received user input is indicative of a selection of the integrated command. For example, the input interface component 106 can have video pattern processing functionality that can detect user movements and attempt to match the detected movements to a predetermined pattern indicative of a selection of the integrated command. In yet another embodiment, the input interface component 106 may establish one or more timing thresholds or implement various pattern matching routines that process inputs from a touch screen interface. For example, the input interface component 106 may have a time and location threshold that is applied to determine whether a consistent touching of the screen (e.g., holding a stylus or finger on the touch screen interface for more than 2 seconds) is indicative of a selection of the integrated command.
If at decision block 304, the input is not indicative of a selection of an integrated command to remove access information associated with a current network resource and access a previously accessed network resource, at block 306, the browser 104 processes the other input. For example, the input may correspond only to a selection of a “back button” in which the browser 104 would access a previously accessed network resource without causing the selective deletion of the browser access information. One skilled in the relevant art will appreciate that type and processing of other input can vary with specific implementations of the browser 104. The routine 300 then terminates at block 314.
Alternatively, if at decision block 304, the input is indicative of a selection of control or icon corresponding to an integrated command, at block 308, the browser 104 obtains configuration information associated with the integrated command. Specifically, in one embodiment, the configuration information can include a specification of the type of browser access information that should be deleted or otherwise removed. For example, a user may configure the browser to delete all collected browser access information. In another example, the user may configure the browser to delete the entry in the URL history and any stored personal information, but allow cached images and text to remain behind. In some embodiments, the browser 104 may be configured with default settings, which may or may not be capable of adjustment by a user or system administrator.
At block 310, the browser 104, through the information management component 108 (
At block 312, the browser 104, through the interface component 106, transmits any optional notifications or notices. As previously described, the client computing device 102, either directly or via the network accessible computing provider 120, can transmit one or more notifications indicative of the receipt of an integrated command for specific network resources. The notification may be transmitted to the content provider 110 associated with the current network resource or one or more network based service providers 118 (
With reference to
With reference to
With reference to
With reference to
With reference to
In an illustrative embodiment, a network based service provider 118, such as search provider or rating service, may monitor the number of times a particular network resource has been the subject of an integrated command. Based on the number integrated commands (cumulatively over a number of users) or a severity associated with a particular integrated command (assuming some type of metadata or feedback mechanism is provided), the network resources can implement various mitigation or notification techniques. In one embodiment, the network based service provider 118 can define one or more thresholds based on a number of integrated commands for determining whether to initiate additional actions or mitigation techniques. In one example, the network based service provider 118 can establish a maximum threshold that, when exceeded, causes the network based service provider 118 to contact a respective content provider 110. In another example, the network based service provider can modify the appearance of URLs or other network identifiers that allow the network based service provider 118 to identify network resources that are more commonly subject to an integrated command. For example, if a total of twenty-thousand users have viewed a particular network resource and ten-thousand of those users used the integrated command after accessing it, the network service provider may change the color of the URL to a more prominent color (e.g. red, orange, neon, etc.). In still another example, if a particular network based service provider 118 has financial dealings with various content providers 110, the network based service provider 118 can initiate the modification of financial compensation paid to one or more content providers 110 based on the number integrated commands or severity associated with one or more integrated commands.
Turning now to
At block 502, the network based service provider 118 obtains a notification of the initiation of an integrated command to remove information associated with a current network resource and to access a previously accessed network resource. The notification may be transmitted by a browser 104 or network accessible computing provider 120, as previously described. Illustratively, the notification can include an identification of the network resource identifier (e.g., URL) that was subject the integrated command. Additionally, the notification can include additional information about the browser application 104 or user, including additional comments or explanations provided by the user.
At decision block 504, a test is conducted to determine whether notification for a particular network resource has exceeded one or more thresholds. In one embodiment, the one or more thresholds can correspond to a total number of received integrated commands over a defined period of time. In another embodiment, the one or more thresholds can correspond to a maximum severity rating that cannot be exceeded. If one or more thresholds have not been exceeded, the routine 500 returns to block 502 to await any potential notifications from a browser.
Alternatively, if the one or more thresholds have been exceeded, at block 506, the network based service provider 118 processes one or more network resource identifiers based on the exceeded threshold. In one embodiment, the network based service provider 118 can modify the appearance of URLs or other network identifiers associated with specific network resources, such as via instructions provided to content providers 110 or browsers 104. An illustrative screen display for the modification of the appearance of network resource identifiers is described with regard to
According to another embodiment a search provider can implement functionality to completely remove the network resource identifier from the search results when a user uses the integrated command. For example, if a user is provider with search results shown in
While illustrative embodiments have been disclosed and discussed, one skilled in the relevant art will appreciate that additional or alternative embodiments may be implemented within the spirit and scope of the present disclosure. Additionally, although many embodiments have been indicated as illustrative, one skilled in the relevant art will appreciate that the illustrative embodiments do not need to be combined or implemented together. As such, some illustrative embodiments do not need to be utilized or implemented in accordance with the scope of variations to the present disclosure.
Conditional language, such as, among others, “can,” “could,” “might,” or “may,” unless specifically stated otherwise, or otherwise understood within the context as used, is generally intended to convey that certain embodiments include, while other embodiments do not include, certain features, elements, or steps. Thus, such conditional language is not generally intended to imply that features, elements or steps are in any way required for one or more embodiments or that one or more embodiments necessarily include logic for deciding, with or without user input or prompting, whether these features, elements or steps are included or are to be performed in any particular embodiment. Moreover, unless specifically stated otherwise, or otherwise understood within the context as used, is generally intended to convey utilization of the conjunction “or” in enumerating a list of elements does not limit the selection of only a single element and can include the combination of two or more elements.
Any process descriptions, elements or blocks in the flow diagrams described herein and/or depicted in the attached figures should be understood as potentially representing modules, segments, or portions of code which include one or more executable instructions for implementing specific logical functions or steps in the process. Alternate implementations are included within the scope of the embodiments described herein in which elements or functions may be deleted, executed out of order from that shown or discussed, including substantially concurrently or in reverse order, depending on the functionality involved, as would be understood by those skilled in the art. It will further be appreciated that the data and/or components described above may be stored on a computer-readable medium and loaded into memory of the client computing device using a drive mechanism associated with a computer-readable medium storing the computer executable components, such as a CD-ROM, DVD-ROM, or network interface. Further, the component and/or data can be included in a single device or distributed in any manner. Accordingly, general purpose computing devices may be configured to implement the processes, algorithms, and methodology of the present disclosure with the processing and/or execution of the various data and/or components described above. Alternatively, some or all of the methods described herein may alternatively be embodied in specialized computer hardware. In addition, the components referred to herein may be implemented in hardware, software, firmware or a combination thereof.
It should be emphasized that many variations and modifications may be made to the above-described embodiments, the elements of which are to be understood as being among other acceptable examples. All such modifications and variations are intended to be included herein within the scope of this disclosure and protected by the following claims.
This application is a continuation of U.S. patent application Ser. No. 13/211,188, entitled MANAGING INFORMATION ASSOCIATED WITH NETWORK RESOURCES and filed Aug. 16, 2011, now U.S. Pat. No. 9,037,696, the entirety of which is incorporated by reference herein.
| Number | Name | Date | Kind |
|---|---|---|---|
| 5634064 | Warnock et al. | May 1997 | A |
| 5872850 | Klein et al. | Feb 1999 | A |
| 5961593 | Gabber et al. | Oct 1999 | A |
| 6049812 | Bertram et al. | Apr 2000 | A |
| 6108637 | Blumenau | Aug 2000 | A |
| 6138156 | Fletcher et al. | Oct 2000 | A |
| 6195679 | Bauersfeld et al. | Feb 2001 | B1 |
| 6430624 | Jamtgaard et al. | Aug 2002 | B1 |
| 6453342 | Himmel | Sep 2002 | B1 |
| 6549941 | Jaquith et al. | Apr 2003 | B1 |
| 6560620 | Ching | May 2003 | B1 |
| 6625624 | Chen et al. | Sep 2003 | B1 |
| 6633316 | Maddalozzo et al. | Oct 2003 | B1 |
| 6704024 | Robotham et al. | Mar 2004 | B2 |
| 6725269 | Megiddo | Apr 2004 | B1 |
| 6785864 | Te et al. | Aug 2004 | B1 |
| 6871236 | Fishman et al. | Mar 2005 | B2 |
| 6944665 | Brown et al. | Sep 2005 | B2 |
| 6963850 | Bezos et al. | Nov 2005 | B1 |
| 7003442 | Tsuda | Feb 2006 | B1 |
| 7051084 | Hayton et al. | May 2006 | B1 |
| 7054952 | Schwerdtfeger et al. | May 2006 | B1 |
| 7085736 | Keezer et al. | Aug 2006 | B2 |
| 7159023 | Tufts | Jan 2007 | B2 |
| 7171478 | Lueckhoff et al. | Jan 2007 | B2 |
| 7191211 | Tuli | Mar 2007 | B2 |
| 7353252 | Yang et al. | Apr 2008 | B1 |
| 7373313 | Kahle et al. | May 2008 | B1 |
| 7543059 | Johnson et al. | Jun 2009 | B2 |
| 7565425 | Van Vleet et al. | Jul 2009 | B2 |
| 7792944 | DeSantis et al. | Sep 2010 | B2 |
| 7831582 | Scofield et al. | Nov 2010 | B1 |
| 7975000 | Dixon et al. | Jul 2011 | B2 |
| 7996912 | Spalink et al. | Aug 2011 | B2 |
| 8010545 | Stefik et al. | Aug 2011 | B2 |
| 8015496 | Rogers | Sep 2011 | B1 |
| 8060463 | Spiegel | Nov 2011 | B1 |
| 8073850 | Hubbard et al. | Dec 2011 | B1 |
| 8103742 | Green | Jan 2012 | B1 |
| 8185621 | Kasha | May 2012 | B2 |
| 8190682 | Paterson-Jones et al. | May 2012 | B2 |
| 8249904 | DeSantis et al. | Aug 2012 | B1 |
| 8271887 | Offer et al. | Sep 2012 | B2 |
| 8316124 | Baumback et al. | Nov 2012 | B1 |
| 8336049 | Medovich | Dec 2012 | B2 |
| 20010039490 | Verbitsky et al. | Nov 2001 | A1 |
| 20020030703 | Robertson et al. | Mar 2002 | A1 |
| 20020191020 | Kaply | Dec 2002 | A1 |
| 20020194302 | Blumberg | Dec 2002 | A1 |
| 20030023712 | Zhao et al. | Jan 2003 | A1 |
| 20030041106 | Tuli | Feb 2003 | A1 |
| 20030084121 | De Boor | May 2003 | A1 |
| 20030137531 | Katinsky et al. | Jul 2003 | A1 |
| 20040049541 | Swahn | Mar 2004 | A1 |
| 20040073713 | Pentikainen et al. | Apr 2004 | A1 |
| 20040083294 | Lewis | Apr 2004 | A1 |
| 20040093376 | De Boor et al. | May 2004 | A1 |
| 20040139208 | Tuli | Jul 2004 | A1 |
| 20040181613 | Hashimoto et al. | Sep 2004 | A1 |
| 20040205448 | Grefenstette et al. | Oct 2004 | A1 |
| 20040220905 | Chen et al. | Nov 2004 | A1 |
| 20040243622 | Morisawa | Dec 2004 | A1 |
| 20050010863 | Zernik | Jan 2005 | A1 |
| 20050060643 | Glass et al. | Mar 2005 | A1 |
| 20050138382 | Hougaard et al. | Jun 2005 | A1 |
| 20050183039 | Revis | Aug 2005 | A1 |
| 20050246193 | Roever et al. | Nov 2005 | A1 |
| 20060085766 | Dominowska et al. | Apr 2006 | A1 |
| 20060095336 | Heckerman et al. | May 2006 | A1 |
| 20060122889 | Burdick et al. | Jun 2006 | A1 |
| 20060168510 | Bryar et al. | Jul 2006 | A1 |
| 20060184421 | Lipsky et al. | Aug 2006 | A1 |
| 20060248442 | Rosenstein et al. | Nov 2006 | A1 |
| 20060277167 | Gross et al. | Dec 2006 | A1 |
| 20060294461 | Nadamoto et al. | Dec 2006 | A1 |
| 20070022072 | Kao et al. | Jan 2007 | A1 |
| 20070027672 | Decary et al. | Feb 2007 | A1 |
| 20070094241 | Blackwell et al. | Apr 2007 | A1 |
| 20070124693 | Dominowska et al. | May 2007 | A1 |
| 20070139430 | Korn et al. | Jun 2007 | A1 |
| 20070157094 | Lemay et al. | Jul 2007 | A1 |
| 20070240160 | Paterson-Jones et al. | Oct 2007 | A1 |
| 20070288589 | Chen et al. | Dec 2007 | A1 |
| 20080028334 | De Mes | Jan 2008 | A1 |
| 20080104502 | Olston | May 2008 | A1 |
| 20080183672 | Canon et al. | Jul 2008 | A1 |
| 20080184128 | Swenson et al. | Jul 2008 | A1 |
| 20080320225 | Panzer et al. | Dec 2008 | A1 |
| 20090012969 | Rail et al. | Jan 2009 | A1 |
| 20090164924 | Flake et al. | Jun 2009 | A1 |
| 20090204478 | Kaib et al. | Aug 2009 | A1 |
| 20090217199 | Hara et al. | Aug 2009 | A1 |
| 20090241191 | Keromytis | Sep 2009 | A1 |
| 20090248680 | Kalavade | Oct 2009 | A1 |
| 20090254867 | Farouki et al. | Oct 2009 | A1 |
| 20090282021 | Bennett | Nov 2009 | A1 |
| 20090287698 | Marmaros et al. | Nov 2009 | A1 |
| 20090327914 | Adar et al. | Dec 2009 | A1 |
| 20100024015 | Hardt | Jan 2010 | A1 |
| 20100036740 | Barashi | Feb 2010 | A1 |
| 20100057639 | Schwarz et al. | Mar 2010 | A1 |
| 20100125507 | Tarantino, III et al. | May 2010 | A1 |
| 20100131594 | Kashimoto | May 2010 | A1 |
| 20100138293 | Ramer et al. | Jun 2010 | A1 |
| 20100198742 | Chang et al. | Aug 2010 | A1 |
| 20100218106 | Chen et al. | Aug 2010 | A1 |
| 20100293190 | Kaiser et al. | Nov 2010 | A1 |
| 20100312788 | Bailey | Dec 2010 | A1 |
| 20100318892 | Teevan et al. | Dec 2010 | A1 |
| 20100332513 | Azar et al. | Dec 2010 | A1 |
| 20110022957 | Lee | Jan 2011 | A1 |
| 20110029854 | Nashi et al. | Feb 2011 | A1 |
| 20110055203 | Gutt et al. | Mar 2011 | A1 |
| 20110066982 | Paulsami | Mar 2011 | A1 |
| 20110078140 | Dube et al. | Mar 2011 | A1 |
| 20110078705 | Maclinovsky et al. | Mar 2011 | A1 |
| 20110119661 | Agrawal et al. | May 2011 | A1 |
| 20110161849 | Stallings et al. | Jun 2011 | A1 |
| 20110173177 | Junqueira et al. | Jul 2011 | A1 |
| 20110173637 | Brandwine et al. | Jul 2011 | A1 |
| 20110178868 | Garg et al. | Jul 2011 | A1 |
| 20110185025 | Cherukuri et al. | Jul 2011 | A1 |
| 20110191327 | Lee | Aug 2011 | A1 |
| 20110191696 | Jain | Aug 2011 | A1 |
| 20110197121 | Kletter | Aug 2011 | A1 |
| 20110208840 | Blackman | Aug 2011 | A1 |
| 20110246873 | Tolle et al. | Oct 2011 | A1 |
| 20110289074 | Leban | Nov 2011 | A1 |
| 20110296341 | Koppert | Dec 2011 | A1 |
| 20110302510 | Harrison et al. | Dec 2011 | A1 |
| 20110310431 | Uchikawa | Dec 2011 | A1 |
| 20120005600 | Ito | Jan 2012 | A1 |
| 20120072821 | Bowling | Mar 2012 | A1 |
| 20120084644 | Robert et al. | Apr 2012 | A1 |
| 20120096365 | Wilkinson et al. | Apr 2012 | A1 |
| 20120110017 | Gu et al. | May 2012 | A1 |
| 20120137201 | White et al. | May 2012 | A1 |
| 20120143944 | Reeves et al. | Jun 2012 | A1 |
| 20120150844 | Lindahl et al. | Jun 2012 | A1 |
| 20120166922 | Rolles | Jun 2012 | A1 |
| 20120198516 | Lim | Aug 2012 | A1 |
| 20120215834 | Chen et al. | Aug 2012 | A1 |
| 20120215919 | Labat et al. | Aug 2012 | A1 |
| 20120284629 | Peters et al. | Nov 2012 | A1 |
| 20120317295 | Baird et al. | Dec 2012 | A1 |
| 20120331406 | Baird et al. | Dec 2012 | A1 |
| 20130007101 | Trahan et al. | Jan 2013 | A1 |
| 20130007102 | Trahan et al. | Jan 2013 | A1 |
| 20130031461 | Hou et al. | Jan 2013 | A1 |
| 20130080611 | Li et al. | Mar 2013 | A1 |
| Number | Date | Country |
|---|---|---|
| 2004-295722 | Oct 2004 | JP |
| WO 2013003631 | Jan 2013 | WO |
| Entry |
|---|
| International Search Report and Written Opinion received in PCT/US2012/050793 dated Mar. 1, 2013. |
| International Search Report and Written Opinion received in PCT/US2012/050793 dated Feb. 18, 2014. |
| “EyeBrowse: Record, Visualize and Share your Browser History”, Information Aesthetics, Sep. 18, 2009, accessed Jan. 25, 2013, 2 pages. |
| “What Internet Users Do on a Typical Day, Trend Data (Adults)”, Pew Internet & American Life Project, available at http://pewinternet.org/Static-Pages/Trend-Data-(Adults)/Online-Activities-Daily.aspx, accessed Nov. 29, 2012, 4 pages. |
| Bango, R., “How JS & Ajax work in Opera Mini 4”, available at http://ajaxian.com/archives/how-js-ajax-work-in-opera-mini-4, Nov. 2, 2007, 3 pages. |
| Baumann et al., “Enhancing STEM Classes Using Weave: A Collaborative Web-Based Visualization Environment”, IEEE Integrated Stem Education Conference, Apr. 2, 2011, Ewing, New Jersey, pp. 2A-1-2A-4. |
| Brinkmann, M., “Record and Share your browser history with Hooeey,” available at ghacks.net, Feb. 26, 2008, accessed on Jan. 25, 2013, 6 pages. |
| Chen et al., “Bringing Order to the Web: Automatically Categorizing Search Results”, Proceedings of the SIGCHI Conference on Human Factors in Computing Systems, Apr. 1-6, 2000, pp. 145-152. |
| Considine, A., “The Footprints of Web Feet”, The New York Times, Mar. 4, 2011, accessed Jan. 25, 2013, 3 pages. |
| De Carvalho et al., “Synchronizing Web Browsing Data With Browserver”, Proceedings of the IEEE Symposium on Computers and Communications, Jun. 22-25, 2010, Riccione, Italy, pp. 738-743. |
| Feuerstein, A., “Flyswat Takes Aim”, San Francisco Business Times, available at http://www.bizjournals.com/sanfrancisco/stories/1999/10/25/story2.html?t=printable, Oct. 22, 1999, accessed Jun. 4, 2004, 2 pages. |
| Finke, C., “RSS Ticker: Add-ons for Firefox”, available at https://addons.mozilla.org/en-US/firefox/addon/rss-ticker/, accessed Feb. 7, 2013, 3 pages. |
| Gabber et al., “How to Make Personalized Web Browsing Simple, Secure, and Anonymous”, Financial Cryptography, 1997, 16 pages. |
| Gingerich, J., “Keycorp Making Site Into Portal”, KRTBN Knight-Ridder Tribune Business News (South Bend Tribune, Indiana), Oct. 25, 1999, 2 pages. |
| Hopper, D.I., “Desktops now have power to comparison-shop”, http://www.cnn.com/TECH/computing/9910/18/r.u.sure/index.html, Oct. 18, 1999, accessed May 16, 2004, 3 pages. |
| Kevin, “Close ‘n’ Forget Firefox add on”, Evilfantasy's Blog, available at http://evilfantasy.wordpress.com/2009/03/24/close-%E2%80%98n%E2%80%99-forget-firefox-add-on/, Mar. 24, 2009, accessed Jul. 2, 2013, 1 page. |
| Rao et al., “A Proxy-Based Personal Web Archiving Service”, Operating Systems Review, 2001, vol. 35(1): 61-72. |
| Teevan et al., “Changing How People View Changes on the Web”, Proceedings of the 22nd Annual ACM Symposium on User Interface Software and Technology, 2009, New York, pp. 237-246. |
| Van Kleek, M., “Introducing ‘Eyebrowse’—Track and share your web browsing in real time”, Haystack Blog, Aug. 28, 2009, accessed Jan. 25, 2013, 3 pages. |
| Number | Date | Country | |
|---|---|---|---|
| 20150254361 A1 | Sep 2015 | US |
| Number | Date | Country | |
|---|---|---|---|
| Parent | 13211188 | Aug 2011 | US |
| Child | 14715458 | US |
