This application is related to U.S. patent application Ser. No. 12/111,065 entitled “SEARCH CUSTOMIZATION BY GEO-LOCATED PROXY OF USER SEGMENT” by Levin, et al., filed on Apr. 28, 2008, which is hereby incorporated herein by reference.
This application is also related to U.S. patent application Ser. No. 10/853,552 (now U.S. Pat. No. 7,181,447) entitled “METHODS AND SYSTEMS FOR CONCEPTUALLY ORGANIZING AND PRESENTING INFORMATION,” by Curtis, et al., filed on May 24, 2004, which is hereby incorporated herein by reference.
1). Field of the Invention
Embodiments of this invention relate to a data processing system and method that erases search activity data.
2). Discussion of Related Art
The internet is a global network of computer systems and has become a ubiquitous tool for finding information regarding news, businesses, events, media, etc. based on a user search criteria. A user can interact with the internet through a user interface that is typically stored on a server computer system.
Because of increased user activity on the Internet and sophisticated tracking methods, more behavioral information concerning a user is being recorded through the internet. Unfortunately, a user's personal information can be abused and thus raises serious privacy concerns about retaining such information.
Often times, a user's internet activity is recorded on a remote computer. For example, a user searching for a specific product may click on various search results which are subsequently recorded by a server computer system. The recorded information may be later utilized for commercial purposes against the user's will. Providing search results while also respecting a user's privacy could alleviate privacy concerns in the search industry and result in a more enjoyable user experience.
The invention provides a method of data processing including receiving at least one search activity record and a user preference from a client computer system over a network at a server computer system.
The method of data processing may further include storing at least one search activity record on the server computer system and deleting the at least one search activity record on the server computer system based on the user preference.
The method of data processing may further include the at least one search activity record being at least one search query that is received at a search engine which extracts at least one search result from a data source and transmits the at least one search result from the server computer system to the client computer system.
The method of data processing may further include the at least one search activity record being at least one of an IP address, a user ID, a session ID cookie, and user pick data.
The method of data processing may further include the at least one search activity record being deleted from the server computer system before the at least one search activity record can be used to derive additional information.
The method of data processing may further include the additional information being information that is related to a user pick pattern or user search pattern.
The method of data processing may further include retaining user provided personal information on the server computer system after the at least one search activity record is deleted from the server computer system.
The method of data processing may further include storing an eraser identification cookie on the client computer system that represents the user preference. The eraser identification cookie indicates whether the at least one search activity record is to be deleted from the server computer system.
The method of data processing may further include the eraser identification cookie being user modifiable to allow or prevent the deletion of the at least one search activity record from the server computer system.
The method of data processing may further include storing an unfiltered results cookie that identifies whether the user is capable of viewing unfiltered search results.
The invention provides a machine-readable storage medium that provides executable instructions which, when executed by a computer system, cause the computer system to perform a method.
In the machine-readable storage medium, the computer system may execute the method including receiving at least one search activity record and a user preference from a client computer system over a network at a server computer system and storing at least one search activity record on the server computer system. In addition, the method may further include deleting the at least one search activity record on the server computer system based on the user preference.
In the machine-readable storage medium, the computer system may execute the method further including receiving the at least one search query at a search engine and extracting at least one search result from a data source and transmitting the at least one search result from the server computer system to the client computer system.
In the machine-readable storage medium, the computer system may execute the method further including the at least one search activity record being at least one of an IP address, a user ID, a session ID cookie, and user pick data.
In the machine-readable storage medium, the computer system may execute the method further including the at least one search activity record being deleted from the server computer system before the at least one search activity record can be used to derive additional information.
In the machine-readable storage medium, the computer system may execute the method further including the additional information being information that is related to a user pick pattern or user search pattern.
In the machine-readable storage medium, the computer system may execute the method further including retaining user provided personal information on the server computer system after the at least one search activity record is deleted from the server computer system.
In the machine-readable storage medium, the computer system may execute the method further including storing an identification cookie on the client computer system that represents the user preference. The eraser identification cookie indicates whether the at least one search activity record is to be deleted from the server computer system.
In the machine-readable storage medium, the computer system may execute the method further including the eraser identification cookie being user modifiable to allow or prevent the deletion of the at least one search activity record from the server computer system.
In the machine-readable storage medium, the computer system may execute the method further including storing an unfiltered results cookie that identifies whether the user is capable of viewing unfiltered search results.
The invention provides a system for processing data including a server computer system and a module stored on the server computer system for receiving a search activity record and a user preference.
The system for data processing may further include a data store to store at least one search activity record on the server computer system and a deleting module to delete the at least one search activity record on the data store based on the user preference.
The system for data processing may further include at least one search activity record is at least one search query and a search engine that utilizes the query to extract at least one search result from a data source. The system may further include a transmission module to transmit the at least one search result from the server computer system to the client computer system.
The system for data processing may further include at least one search activity record being at least one of an IP address, a user ID, a session ID cookie, and user pick data.
The invention is further described by way of example with reference to the accompanying drawings, wherein.
The client computer system 26 includes search activity data 22 and a cookie 58. The client computer system 26 and server computer system 24 are connected through the network 28.
The server computer system 24 includes a receiving module 30, a data store 34, an eraser module 32, a processing module 56, a data source or database 38, a search engine 36, and a transmission module 40.
The receiving module 30 is connected with the data store 34, search engine 36, and network 28. The receiving module 30 receives search activity data 22 from the client computer system 26 through the network 28.
The data store 34 is connected with the receiving module 30, an eraser module 32, and a processing module 56. The data store 34 includes raw log information 46 which contains recorded query search terms, user picks such as clicked links, IP addresses, user identifiers and session identifiers. It is understood that the raw log information 46 can contain any information related to user search activity data 22.
Raw log information 46 includes recorded user interactions with the search engine 36 and user interface. The raw log information 46 is a record of user picks or clicks on links of a web page (what the user clicked on), search queries (what the user searched for), Internet Protocol address (hereinafter, “IP address”) information (where the user is searching from), and user or session IDs (who the user is in relation to other searches). Client computer system 26 activity can be continuously or non-continuously recorded as raw log information 46 by the data store 34.
The eraser module 32 includes a determining module 42 and a deleting module 44. The eraser module 32 is connected with the data store 34 so that information can be transmitted and received between the eraser module 32 and data store 34.
The search engine 36 is connected with the receiving module 30 to receive a search query 52 from the client computer system 26 and is further connected with a transmission module 40. Moreover, the data source 38 is further connected with the search engine 36 so that the search engine 36 can transmit and receive information with the data source 38 to search for a search result 54 based on a search query 52. The search engine 36 can be of the type described in U.S. application Ser. No. 10/853,552, the contents of which are hereby incorporated by reference.
A transmission module 40 is connected with the search engine 36 and the network 28 to transmit search results 54 from the search engine 36 to the client computer system 26.
In use,
Search activity data 22 is generated on the client computer system 26 and is received by the receiving module 30. Search activity data 22 is any general input related to information searching over a network. The search activity data 22 can be an internet search query 52 received from the client computer system 26. However, the query is not necessarily a search query but may be words extracted from a web document or stored document.
Furthermore, the search activity data 22 includes any user pick, click data, or user input related to a Uniform Resource Locator (hereinafter, “URL”) link. The user pick data or input can be a user mouse click, input, or selection of a search result 54, web link, advertising link, or any trackable user interaction with a web browser representing the will of the user.
In addition, the search activity data 22 includes additional data related to a client computer's IP address, user IDs, and session IDs. Moreover, the search activity data 22 can alternatively further include timestamp information related to the time and day a user entered a certain query or selected a certain search result.
Upon enabling the eraser feature, the client computer system 26 receives 64 an “Eraser” cookie 58 file configured to indicate a user preference. The cookie 58 is initially obtained from the server computer system 24 but can alternatively be obtained from a third-party. Generally, a cookie is a piece of text that a server can store on a client data store. In general, cookies include text containing name-value pairs for purposes of identifying a specific user or search characteristics.
In one example, a cookie file having the name “cookie:user_name@ask.com/” is stored on the client computer system 26. With the eraser feature selected by the user, the Eraser cookie 58 file contains the following information:
As shown in the above example, the Eraser cookie 58 simply shows the title of the cookie and the domain name from which the cookie was created. In the example, the domain “ask.com” has created the Eraser cookie named “askeraser”. Most importantly, the Eraser cookie 58 contains no other significant identification or search activity data 22 except for the simple text “on” which indicates that the eraser feature is enabled by the user as a user preference. In the example above, the “askeraser” cookie is set to expire after 30 years although it is understood that any expiration time may be selected.
The Eraser cookie 58 is the only cookie from the server computer system 24 that is present on the client computer system 26 when the eraser feature is enabled. Furthermore, when the eraser feature is enabled, all other cookies previously received from the server computer system 24 are deleted 66 except the Eraser cookie 58 containing the indication of the user preference. The Eraser cookie 58 acts as a constant indicator to client and server computer systems for determining whether a user has turned on or enabled the eraser feature.
Furthermore, third-party cookies are suppressed when the eraser feature is enabled. New third party cookies cannot be placed on the client computer system 26 and third party cookies that already reside on the client computer system 26 cannot gather information about the search activity being conducted. However, third parties can still receive search query information through referrer data.
When the eraser feature is enabled, all subsequent search activity data 22 will be deleted 68 from the server computer system 24. The eraser module 32 will continue 70 to delete search activity data 22 from the data store 34 until the user preference in the Eraser cookie is changed or the Eraser cookie 58 is deleted from the client computer system.
In another example, the eraser feature is turned off and the cookie text is modified to contain the following information:
As shown in the exemplary cookie text above, the text “on” is no longer present. Instead, the text “accepting” is provided along with other name-value pair information indicating the user ID, session ID and other search activity data 22. In the above example, the server computer system 24 stores search activity data 22 in the data store 34 as raw log information 46. Because the cookie text does not indicate a user preference to enable the eraser feature, an unlimited number of cookies from the server computer system 24 may be stored on the client computer system 26. In addition, the eraser module 32 is not enabled and does not erase search activity data 22 from the data store 34, as discussed in further detail below.
The determining module 42 determines 80,82 whether certain raw log information 46 was received while the Eraser cookie 58 was enabled (enabling the eraser feature) based on the user preference. If the eraser feature is enabled, the deleting module 44 of the eraser module 32 will delete 86 from the data store 34 all search activity data 22 received while the eraser feature is enabled.
However, if the eraser feature is not enabled, the deleting module 44 will not delete search activity data 22 that was received by the server computer system 24 when the eraser feature was not enabled. For example, searches, user clicks or picks, and search activity 22 previously conducted when the eraser feature was not enabled will not be deleted as will be discussed in further detail.
Furthermore, the deleting module 44 does not delete personally identifiable information including names and e-mail addresses that a user voluntarily provides to the server computer system 24.
In one example, a website contains a personal folder (named “MyStuff”, for example) where a user may click and login with a personal email or user name. While the user is logged in, the personal folder allows the user to track recently conducted searches, saved results, and create special folders and tags for the user's own personal use and reference.
If the user enables the eraser feature, the content within the personal folder is not affected. However, the tracking ability of the personal folder is disabled while the eraser feature is enabled.
It should be noted that while the eraser feature is enabled, the deleting module will not immediately delete search activity data 22 on the server computer system 24 for various reasons. In one example, the search activity 22 is not deleted immediately in order to run automated systems to detect and block users or automatic bots that abuse the server computer system 24.
In another example, the search activity data 22 is not deleted at all (even though the eraser feature is enabled) in order to solve a critical technical issue emanating from internal sources (instability, etc.), or external sources (denial-of-service attack, etc.). Additionally, the search activity data 22 is not deleted if search activity data 22 must be retained on the server computer system 24 due to legal obligations.
In the processing module 56, the clean log information 50 is correlated to obtain additional information according to Query-to-Pick history data. The additional information can be based on user pick patterns or user query search patterns. Query-to-Pick history data refers to the correlation between a query entered by a user and the URL picked by the user. According to the Query-to-Pick History, a raw score is assigned to each URL pick by any scoring method. The URL picks are ranked according to the raw score and stored in the data source 38. The additional information can also include geographic location data, demographic data, and any relevant information related to the user as described in U.S. patent application Ser. No. 12/111,065 and U.S. application Ser. No. 10/853,552, which are herein incorporated by reference.
If the eraser cookie 58 is not enabled, the raw log information 46 containing search query 52 related data is retained 106 on the data store 34. The search query 52 related data is further processed 108 by the processing module 56 and filtered 48 to produce clean log information 50, as previously described. The search query 52 related data can be correlated or associated with the pick or selection information, as already described. The correlations or associations between query and pick data are stored on the data source 38 for access by the search engine 36.
A user can enter a query search term 52 into the query input field 114. Upon selecting the search button or entering a command to accept the search, search results 54 will be provided to the user based on the vertical 116 selected.
However, before searching and choosing picks within a vertical 116, a user has the option of selecting the eraser option 118 within the web page 112. If the user does not select the eraser option 118, the search terms and picks or clicks received from the user will be recorded on the server computer system 24 as a default operation.
It is understood that a user may close the web browser containing the web page or visit another web page. However, if the eraser feature is enabled, when the user returns to the web page associated with the server computer system 24, the eraser feature will remain enabled and the status identifier 132 will still highlight the “on” option. As long as the eraser feature is enabled through the Eraser cookie, the status identifier will remain “on” for subsequent user visits to an associated web page.
The server computer system 24 has stored thereon a crawler 176, a collected data store 178, an indexer 180, a plurality of search databases 36, a plurality of structured databases and data sources 222, a search engine 36, an eraser module 32, and the user interface 170. The novelty of the present invention revolves around the user interface 170, the search engine 36, the eraser module 32, data store 34, and one or more of the structured databases and data sources 222. The crawler 176 is connected over the internet 172A to the remote sites 174. The collected data store 178 is connected to the crawler 176, and the indexer 180 is connected to the collected data store 178. The search databases 38 are connected to the indexer 180. The search engine 36 and geo-bias system 38 are connected to the search databases 38 and the structured databases and data sources 222. The client computer systems 26 are located at respective client sites and are connected over the internet 172B and the user interface 170 to the search engine 36, data store 34 and eraser module 32.
Reference is now made to
A user at one of the client computer systems 26 accesses the user interface 170 over the internet 172B (step 188). The user can enter a search query in a search box in the user interface 170, and either hit “Enter” on a keyboard or select a “Search” button or a “Go” button of the user interface 170 (step 190). The search engine 36 then uses the “Search” query to parse the search databases 38 or the structured databases or data sources 222. In the example of where a “Web” search is conducted, the search engine 36 parses the search database 38 having general Internet Web data (step 192). Various technologies exist for comparing or using a search query to extract data from databases, as will be understood by a person skilled in the art.
The search engine 36 then transmits the extracted data over the internet 172B to the client computer system 26 (step 194). The extracted data includes URL links to one or more of the remote sites 174. The user at the client computer system 26 can select one of the links to the remote sites 174 and access the respective remote site 174 over the internet 172C (step 196). The server computer system 24 has thus assisted the user at the respective client computer system 26 to find or select one of the remote sites 174 that have data pertaining to the query entered by the user.
The exemplary client computer system 26 includes a processor 198 (e.g., a central processing unit (CPU), a graphics processing unit (GPU), or both), a main memory 200 (e.g., read-only memory (ROM), flash memory, dynamic random access memory (DRAM) such as synchronous DRAM (SDRAM) or Rambus DRAM (RDRAM), etc.), and a static memory 202 (e.g., flash memory, static random access memory (SRAM), etc.), which communicate with each other via a bus 204.
The client computer system 26 may further include a video display 206 (e.g., a liquid crystal display (LCD) or a cathode ray tube (CRT)). The client computer system 26 includes an alpha-numeric input device 208 (e.g., a keyboard), a cursor control device 210 (e.g., a mouse), a disk drive unit 212, a signal generation device 214 (e.g., a speaker), and a network interface device 216.
The disk drive unit 212 includes a machine-readable medium 218 on which is stored one or more sets of instructions 220 (e.g., software) embodying any one or more of the methodologies or functions described herein. The software may reside, completely or at least partially, within the main memory 200 and/or within the processor 198 during execution thereof by the client computer system 26, the memory 200 and the processor 198 also constituting machine readable media. The software may further be transmitted or received over a network 28 via the network interface device 216.
While the instructions 220 are shown in an exemplary embodiment to be on a single medium, the term “machine readable medium” should be taken to understand a single medium or multiple media (e.g., a centralized or distributed database or data source and/or associated caches and servers) that store the one or more sets of instructions. The term “machine readable medium” shall be taken to include any storage medium that is capable of storing, encoding, or carrying a set of instructions for execution by the machine and that caused the machine to perform any one or more of the methodologies of the present invention. The term “machine readable medium” shall accordingly be taken to include, but not be limited to, solid-state memories, and optical and magnetic media.
It is understood that the eraser module 32 only erasers activity associated with the server computer system 24. Search activity related to the servers of third-party organizations that enable the server computer system 24 to provide users with certain types of search results (for example: videos, weather, shopping, and stock market summaries) are not deleted.
Furthermore, search or pick activity related to a third-party organization that enables the application of sponsored links or text-based ads are not deleted. The third party organizations would delete search activity in accordance with their own data retention policies.
Moreover, a third party organization may receive search query information related to a pick or click via “referrer data” when the eraser feature is enabled on the server computer system 24.
In an alternative embodiment, the eraser feature is enabled when a search is conducted within a search box that is embedded into an internet browser.
In an alternative embodiment, the eraser feature is disabled when a user search is performed through a search toolbar or search box available on a third-party website or third-party software that the user chooses to install on the client computer system 26.
In another alternative embodiment, the client computer system 26 receives from the server computer system 24 an additional cookie, in addition to the Eraser cookie.
In one alternative embodiment, the additional cookie is an unfiltered results cookie. The unfiltered results cookie allows the server computer system 24 to identify whether the user is capable of viewing unfiltered search results or has chosen an option for unfiltered results. When the user picks a link to view unfiltered results, a pop-up window is presented to request the user to accept the unfiltered results cookie (in addition to the Eraser cookie that may be activated on the client system). The unfiltered results cookie is a non-identifiable temporary cookie created by the server computer system 24 and will expire in 20 minutes. Unlike the Eraser cookie, subsequent user visits to the associated server web page still require a user to confirm that unfiltered results are desired. In other words, subsequent attempts by a user to retrieve unfiltered results will require the user to re-confirm a desire to view unfiltered search results.
One advantage of the present invention is that a user's privacy needs are met in the context of the search industry.
Another advantage is that the users have the power to control the usage of their search history and therefore provides users with a sense of security with respect to privacy concerns.
While certain exemplary embodiments have been described and shown in the accompanying drawings, it is to be understood that such embodiments are merely illustrative and not restrictive of the current invention, and that this invention is not restricted to the specific constructions and arrangements shown and described since modifications may occur to those ordinarily skilled in the art.
Number | Name | Date | Kind |
---|---|---|---|
5845278 | Kirsch et al. | Dec 1998 | A |
5963940 | Liddy et al. | Oct 1999 | A |
5966695 | Melchione et al. | Oct 1999 | A |
5966710 | Burrows | Oct 1999 | A |
5983216 | Kirsch et al. | Nov 1999 | A |
5987446 | Corey et al. | Nov 1999 | A |
6009459 | Belfiore et al. | Dec 1999 | A |
6018733 | Kirsch et al. | Jan 2000 | A |
6026388 | Liddy et al. | Feb 2000 | A |
6026391 | Osborn et al. | Feb 2000 | A |
6029195 | Herz | Feb 2000 | A |
6038561 | Snyder et al. | Mar 2000 | A |
6067539 | Cohen | May 2000 | A |
6145003 | Sanu et al. | Nov 2000 | A |
6178416 | Thompson et al. | Jan 2001 | B1 |
6182068 | Culliss | Jan 2001 | B1 |
6185558 | Bowman et al. | Feb 2001 | B1 |
6208988 | Schultz | Mar 2001 | B1 |
6223215 | Hunt et al. | Apr 2001 | B1 |
6269368 | Diamond | Jul 2001 | B1 |
6269394 | Kenner et al. | Jul 2001 | B1 |
6321228 | Crandall et al. | Nov 2001 | B1 |
6347313 | Ma et al. | Feb 2002 | B1 |
6370527 | Singhal | Apr 2002 | B1 |
6401084 | Ortega et al. | Jun 2002 | B1 |
6401118 | Thomas | Jun 2002 | B1 |
6421675 | Ryan et al. | Jul 2002 | B1 |
6424966 | Meyerzon et al. | Jul 2002 | B1 |
6438579 | Hosken | Aug 2002 | B1 |
6446035 | Grefenstette et al. | Sep 2002 | B1 |
6480837 | Dutta | Nov 2002 | B1 |
6480843 | Li | Nov 2002 | B2 |
6480894 | Courts et al. | Nov 2002 | B1 |
6490577 | Anwar | Dec 2002 | B1 |
6545209 | Flannery et al. | Apr 2003 | B1 |
6546388 | Edlund et al. | Apr 2003 | B1 |
6578025 | Pollack et al. | Jun 2003 | B1 |
6606657 | Zilberstein et al. | Aug 2003 | B1 |
6631369 | Meyerzon et al. | Oct 2003 | B1 |
6633867 | Kraft et al. | Oct 2003 | B1 |
6678611 | Khavakh et al. | Jan 2004 | B2 |
6718324 | Edlund et al. | Apr 2004 | B2 |
6735518 | Kim | May 2004 | B2 |
6757661 | Blaser et al. | Jun 2004 | B1 |
6785671 | Bailey et al. | Aug 2004 | B1 |
6785683 | Zodik et al. | Aug 2004 | B1 |
6832218 | Emens et al. | Dec 2004 | B1 |
6847969 | Mathai et al. | Jan 2005 | B1 |
6886009 | Jeng et al. | Apr 2005 | B2 |
6901411 | Li et al. | May 2005 | B2 |
6915204 | Heideman | Jul 2005 | B1 |
6920448 | Kincaid et al. | Jul 2005 | B2 |
6957226 | Attias | Oct 2005 | B2 |
6957390 | Tamir et al. | Oct 2005 | B2 |
6963867 | Ford et al. | Nov 2005 | B2 |
6965900 | Srinivasa et al. | Nov 2005 | B2 |
6969763 | Ecker et al. | Nov 2005 | B1 |
6974860 | Quirk | Dec 2005 | B2 |
7003517 | Seibel et al. | Feb 2006 | B1 |
7013238 | Weare | Mar 2006 | B1 |
7047502 | Petropoulos et al. | May 2006 | B2 |
7080073 | Jiang et al. | Jul 2006 | B1 |
7082573 | Apparao et al. | Jul 2006 | B2 |
7152061 | Curtis et al. | Dec 2006 | B2 |
7158878 | Rasmussen et al. | Jan 2007 | B2 |
7181447 | Curtis et al. | Feb 2007 | B2 |
7373244 | Kreft | May 2008 | B2 |
7451131 | Curtis et al. | Nov 2008 | B2 |
7523099 | Egnor et al. | Apr 2009 | B1 |
7620496 | Rasmussen | Nov 2009 | B2 |
7634463 | Katragadda et al. | Dec 2009 | B1 |
7739274 | Curtis et al. | Jun 2010 | B2 |
7925789 | Li | Apr 2011 | B2 |
20010053999 | Feinberg | Dec 2001 | A1 |
20020065802 | Uchiyama | May 2002 | A1 |
20020078035 | Frank et al. | Jun 2002 | A1 |
20020147724 | Fries et al. | Oct 2002 | A1 |
20030004995 | Novaes | Jan 2003 | A1 |
20030011629 | Rouse et al. | Jan 2003 | A1 |
20030069877 | Grefenstette et al. | Apr 2003 | A1 |
20030154196 | Goodwin et al. | Aug 2003 | A1 |
20030220844 | Marnellos et al. | Nov 2003 | A1 |
20030225885 | Rochberger et al. | Dec 2003 | A1 |
20030236771 | Becker | Dec 2003 | A1 |
20040249796 | Azzam | Dec 2004 | A1 |
20040249801 | Kapur | Dec 2004 | A1 |
20040260677 | Malpani et al. | Dec 2004 | A1 |
20050033803 | Vleet et al. | Feb 2005 | A1 |
20050060289 | Keenan et al. | Mar 2005 | A1 |
20050060290 | Herscovivi et al. | Mar 2005 | A1 |
20050071328 | Lawrence | Mar 2005 | A1 |
20050097089 | Nielsen et al. | May 2005 | A1 |
20050120045 | Klawon | Jun 2005 | A1 |
20050165753 | Chen | Jul 2005 | A1 |
20050228780 | Diab et al. | Oct 2005 | A1 |
20050270311 | Rasmussen et al. | Dec 2005 | A1 |
20060004716 | Hurst-Hiller et al. | Jan 2006 | A1 |
20060026170 | Kreitler et al. | Feb 2006 | A1 |
20060100956 | Ryan et al. | May 2006 | A1 |
20060112081 | Qureshi | May 2006 | A1 |
20060173617 | Sladky et al. | Aug 2006 | A1 |
20060206264 | Rasmussen | Sep 2006 | A1 |
20060206454 | Forstall et al. | Sep 2006 | A1 |
20060223509 | Fukazawa et al. | Oct 2006 | A1 |
20060224574 | Dettinger et al. | Oct 2006 | A1 |
20060230040 | Curtis et al. | Oct 2006 | A1 |
20060271280 | O'Clair | Nov 2006 | A1 |
20060271287 | Gold et al. | Nov 2006 | A1 |
20060271531 | O'Clair et al. | Nov 2006 | A1 |
20070060114 | Ramer et al. | Mar 2007 | A1 |
20070088616 | Lambert et al. | Apr 2007 | A1 |
20070094042 | Ramer | Apr 2007 | A1 |
20070118512 | Riley et al. | May 2007 | A1 |
20070174244 | Jones | Jul 2007 | A1 |
20070214454 | Edwards et al. | Sep 2007 | A1 |
20070283287 | Taylor et al. | Dec 2007 | A1 |
20070294233 | Sheu et al. | Dec 2007 | A1 |
20080005104 | Flake et al. | Jan 2008 | A1 |
20080005668 | Mavinkurve et al. | Jan 2008 | A1 |
20080040678 | Crump | Feb 2008 | A1 |
20080082578 | Hogue et al. | Apr 2008 | A1 |
20080104530 | Santanche et al. | May 2008 | A1 |
20080133124 | Sarkeshik | Jun 2008 | A1 |
20080140603 | Babikov et al. | Jun 2008 | A1 |
20080208824 | Curtis et al. | Aug 2008 | A1 |
20080208825 | Curtis et al. | Aug 2008 | A1 |
20080222119 | Dai et al. | Sep 2008 | A1 |
20080222132 | Pan et al. | Sep 2008 | A1 |
20080235189 | Rayman et al. | Sep 2008 | A1 |
20080235623 | Li | Sep 2008 | A1 |
20080243783 | Santi et al. | Oct 2008 | A1 |
20080281776 | Goradia | Nov 2008 | A1 |
20080281806 | Wang et al. | Nov 2008 | A1 |
20080281821 | Chen et al. | Nov 2008 | A1 |
20080292213 | Chau | Nov 2008 | A1 |
20080307333 | McInerney et al. | Dec 2008 | A1 |
20090006082 | Harris et al. | Jan 2009 | A1 |
20090006169 | Wetzer et al. | Jan 2009 | A1 |
20090063452 | Ahn et al. | Mar 2009 | A1 |
20090094223 | Berk et al. | Apr 2009 | A1 |
20090132929 | Reed, Jr. et al. | May 2009 | A1 |
20090183097 | Bayiates | Jul 2009 | A1 |
20100023392 | Merriman et al. | Jan 2010 | A1 |
20100030735 | Curtis et al. | Feb 2010 | A1 |
20100082634 | Leban | Apr 2010 | A1 |
20100138400 | Curtis et al. | Jun 2010 | A1 |
Number | Date | Country |
---|---|---|
2378789 | Feb 2003 | GB |
09-153060 | Jun 1997 | JP |
2006-236699 | Aug 2002 | JP |
2002-318801 | Oct 2002 | JP |
2003-167852 | Jun 2003 | JP |
WO 0031625 | Jun 2000 | WO |
WO 0118665 | Mar 2001 | WO |
WO 2004114162 | Dec 2004 | WO |
Number | Date | Country | |
---|---|---|---|
20100017414 A1 | Jan 2010 | US |