The present invention relates generally to field of client-server computer network systems, and in particular to providing informational items to a user in conjunction with an application program.
Every day, people send and receive millions of email (also written as “e-mail”) messages over computer networks for business and leisure. Email, being convenient, easy to use and close to instantaneous in many cases, has become an extremely popular communication channel for people to exchange information.
Traditionally, email messages arriving at a user's email account are displayed by a dedicated email client or in web browser window individually, in a chronological order, e.g., the most recent message appears at top of the browser window while the oldest one appears at the bottom of the browser window. Newer applications may provide for a conversation-based approach to viewing and interacting with e-mail messages (e.g., messages are grouped together based on their relationship to each other).
According to some aspects of the invention, a method (e.g., a method performed at a server) for enhancing client message display includes identifying a display view type of a client message display, where the client message display displays client message information. At least one informational item is identified in accordance with the identified display view type. The at least one informational item is formatted for the client message display as an item in a scrollable display area and the formatted at least one informational item is sent to a client device.
According to some aspects of the invention, a method (e.g., a method performed at a client) for enhancing client message display on a client device includes identifying a display view type of a client message display, where the client message display is for displaying client message information. At least one informational item is identified in accordance with the identified display view type and the at least one informational item for the client message display is displayed as an item in a scrollable display area.
The aforementioned features and advantages of the invention as well as additional features and advantages thereof will be more clearly understood hereinafter as a result of a detailed description of embodiments of the invention when taken in conjunction with the drawings. Like reference numerals refer to corresponding parts throughout the several views of the drawings.
According to some embodiments of the invention, informational items may be displayed in a scrollable area of a message display. The informational items may be any number of type of items (e.g., RSS feeds, new items, images, application tips, and so on). A user is provided the ability to scroll forward and backward through the informational items. A user may select the informational item (e.g., by clicking) and more detailed information about the informational item is presented to the user. In some embodiments, depending on the display view of the message application (e.g., InBox, conversation), different informational item types will have different probabilities of display. In some embodiments, a user may customize the types of informational items to be displayed.
RSS feeds 114 are content distributed from various sources on the web. RDF Site Summary (RSS) is an XML-based lightweight multipurpose extensible metadata description and syndication format. RSS is typically used for distributing various types of content to a number of receivers simultaneously. News items 116 may include news items from one or more sources. In some embodiments, the news items are retrieved by the informational item display manager 108 in an active mode (e.g., requesting the news items from identified sources) and in some embodiments the news items are received by the informational item display manager 108 in a passive mode (e.g., the news item source sends news items to the informational item display manger 108 automatically—for example, when the news items are sent to registered subscribers). The blog events 118 are events generated from one or more web logs (blogs). As with the new items 116, the blog events may be passively received or actively retrieved. The application tips 120 are one or more tips for using the particular application with which the user is interacting. In some embodiments, the application is an application used to create, read and send messages and in some embodiments, the application is any other type of application with which the user can interact (e.g., word processor). The advertisements 122 are on-line advertisements which may be selected based on relevancy to the information displayed (or about to be displayed) at the client 104 (e.g., information in a displayed message or conversation). The user polls 124 are polls in which the user has participated, or in which others have participated. User polls may come from a variety of sources. Other types of information 126 may also be gathered and presented on the client 104.
The conversation/message server 206 includes a conversation engine 210, an updater engine 212, a message index 214, a query engine 216, a message database 218, one or more auxiliary services servers 220, a spell checker 222, an SMTP gateway 224, and an informational item display manager 226. The informational item display manager 226 is connected to a user information database 228 and to the communication network 204.
Each client 202 includes a client application 230 and a client assistant 232. The client 202 can be any number of devices (e.g., computer, internet kiosk, personal digital assistant, cell phone, gaming device, desktop computer, laptop computer, set-top box) which may be used to connect to the communication network 204. The communication network 204 may be a wireless, optical, wired or other type of network that facilitates the passage of information. It may include the Internet, one or more local area networks (LANs), one or more wide are networks (WANs), other types networks, or a combination of such networks. The client application 230 is an application that is executed by the client (e.g., browser, e-mail client, word processor) and that displays or presents information to a user of the client (the client application may also perform other tasks not relevant to the present discussion). The client assistant 232 is an application that facilitates the display or presentation of information by the client application 230. The client assistant 232 can be part of the client application 230, a plug-in to the client application 230, stand-alone application, or otherwise (e.g., a JavaScript application downloaded as part of a web page). In some embodiments, the client assistant 232, or portions of the client assistant are downloaded along with messages or other information sent to the client 202. For instance, the client assistant 232 may be one or more scripts (e.g., JavaScript programs) embedded in other content. In this way, different versions of the client assistant 232 are provided to the client 202 without requiring any explicit action by the user of the client 202.
The conversation engine 210 handles requests from and responses to the client assistant 232, via its connection with communication network 204. The conversation engine 210 is also connected to various auxiliary services such as auxiliary services servers 220 and spell checker 222. A query engine 216 is connected to the conversation engine 210, the message index 214, and the message database 218. An updater engine 212 is connected between the conversation engine 210 and message index 214 as well as message database 218. The SMTP gateway 224 is connected between the conversation engine 210 and the communication network 204.
As briefly mentioned above, the conversation engine 210 may respond to a variety of requests from the client assistant 232 related to messages and return conversation-based responses via its connection with the communication network 204. Although, the SMTP gateway 224 may also be connected to the communication network 204, the SMTP gateway 224 may be more directly involved in receiving and sending messages. In some embodiments, the SMTP gateway 224, for example, transmits and receives messages using the simple mail transfer protocol (SMTP). The SMTP gateway 224 may receive a new message from the communication network 204 and send the message to conversation engine 210 for additional processing. Additionally, the SMTP gateway 224 receives messages from the conversation engine 210 and then transmits (via the communication network 204) those messages to the recipient addresses specified in the messages.
The conversation engine 210 may also handle requests for spell checking a message composed by a user of the client 202. The conversation engine 210 sends the portions of the text to be checked to the spell checker 222 for spell checking. The spell checker 222 returns information including an identification of any text identified as potentially incorrectly spelled.
The one or more auxiliary services servers 220 provide additional services to the conversation engine 210. In some embodiments, the auxiliary services servers 220 include a spam detection module. In some embodiments, the auxiliary services servers 220 include an attachment management module, which manages the efficient storage and retrieval of files attached to email messages.
The conversation engine 210 is also attached to the informational item display manager 226. The informational item display manager 226 determines which informational items should be displayed along with the messages and/or conversations based on, depending on the circumstances, one or more of the display view of the messaging application, the content of the messages and/or conversations, and certain probabilistic display characteristics (described below). The user information database 228 contains information about users, including any preferences they may have with respect to the display of the informational items. For example, a user may select one or more types of informational items to be displayed. The user may also identify desired or preferred sources of informational items for a one or more types of informational items (e.g., Google news as a news source). The informational item display manager 226 is also connected to the communication network 204. The informational item display manager 226 passively receives and/or actively retrieves (as the case may be) various information associated with the informational items. For example, the informational item display manager 226 may query a news server for recent news stories.
In some embodiments, the display view of the messaging application impacts the selection of informational items to display. Accordingly, a current view is identified (306). A request for informational items to the client assistant 232 includes an indicator of the view for the informational items to be displayed. As will be explained below in more detail, the request can be generated from a current view or the request can be for a view which will be the next view displayed to the user. Using the identified display view, an associated probability is identified for each informational item or type of informational item identified in 304 (308). In some embodiments, the identification of informational items (304) is performed after the identification of the display view (306). For instance, first and second display views may have different sets of associated informational item types.
According to some embodiments, each display view has associated with it a different set of display probabilities for the various types of informational items. For example, the display probability of a particular informational item type (e.g., advertisements, or news items) may be higher for a first type of display view (e.g., InBox) than a second type of display view (e.g., a conversation or message view).
Different embodiments make use of different applications of the probabilities. For example, in some embodiments, the probabilities are associated with information types (e.g., news items, advertisements), and in some embodiments, the probabilities are associated with specific information sources (e.g., news items from Google news might have different display probabilities than news items from another news source). In some embodiments, the probabilities are determined according to a default set of probabilities. For example, the default set of probabilities may include default probability values for N information types (where N is an integer greater than 1, such as a value between 2 and 10). In some embodiments the default set of probabilities may include default probability values for specific information sources when an information type is associated with more than one information source. In some embodiments, the user sets the probabilities of one or more of the information types or one or more of the information sources. And, in some embodiments, the probabilities are set using a combination of system supplied probabilities and user assigned or adjusted probabilities.
Using the associated probabilities, one of the informational items is chosen for display to the user in the scrollable display area (310). In one embodiment, this is accomplished by generating a number within a defined range (e.g., 0 to 1) using a random or pseudo-random number generator, and then mapping that number to an informational item in accordance with the set of probabilities values associated to the information sources. To be more specific, each of the information sources or information types is assigned a portion of the defined range in accordance with its probability value. In this way, all values in the defined range are associated with a single information source or information type. When a randomly or pseudo-randomly selected value is generated, it identifies a single information source or type.
In some embodiments, a plurality of informational items are identified. For instance, a plurality of randomly or pseudo-randomly selected values may be generated and then mapped to a corresponding number of informational items. Once the item (or items as the case may be) is identified, the associated information of the informational item is obtained (312). In some embodiments, this means requesting information from the informational item source (e.g., querying the news source for the item). In some embodiments, the information is received during background processing and the information may be obtained by querying the location holding the received information (e.g., from informational item display manager 226). In some embodiments, information may be retrieved from either location. In some embodiments, the informational item is related to the content of one or more areas of the display. For example, in some embodiments, an advertisement is obtained based on a relation to the content being displayed to the user (e.g., the text of an e-mail message or conversation). Certain advertisements may be associated with the presence of words or phrases in the content displayed to the user. In some embodiments, advertisers may bid on certain key words or phrases and the advertisement associated with the winning bid is selected.
The information is formatted for display in the scrollable area and sent to the client (314). The formatting consists of extracting and formatting information to display in accordance with a scrollable area template. For example, the extracted information may include a title and a link to the information source (e.g., a network location). Optionally, the extracted information may also include one or more of the following: a snippet of information about the informational item, and/or a date/time value associated with the informational item. The formatted information may be sent in a number of ways depending on the various embodiments. For example, the formatted information can be sent to a JavaScript program (e.g., client assistant 232) which is downloaded and used to process message information. In one embodiment, the JavaScript program does not stay resident at the client 202 after the client assistant 232 is terminated. This embodiment provides an advantage in that the JavaScript program may be modified at the conversation/message server 206 without requiring any modification to the client or software residing at the client. As another example, the formatted information can be sent in a separate data stream to the client assistant 232.
After the informational item is formatted and sent to the client 204, the process waits until a next trigger event (316) before identifying another informational item to format and send. In some embodiments, the trigger event is receiving a request for more informational items from the client assistant 232. As will be described below, the client assistant may request more informational items based on various events. In some embodiments, new informational items may be periodically determined by the process. For example, the client assistant 232 may automatically generate a request for a new informational item after the expiration of a determined period of time (e.g., one minute). Or, in some embodiments, the conversation engine 210 may indicate a change in display view and the process will generate an informational item to be sent along with the new display view information.
In
The client assistant 232 then generates a request for informational items (604). In some embodiments this is done prior to rendering the display view, and in some embodiments, this is done during or after rendering the display view. In some embodiments, the client sends identifiers of the content being displayed such that informational items to be content related can be identified. The client assistant 232 receives the informational item from the conversation/message server 206 (606) and displays it in the message area in the scrollable display portion of the display area using the formatted information received (e.g., identifying the title and textual description of the informational item). The user's activities are monitored (610). If the user chooses to see a previously displayed informational item (612) (e.g., by selecting an appropriate button or icon) then a determination is made as to whether the informational item is currently in a memory associated with the client assistant 232 (e.g., a cache). In some embodiments, the client assistant 232 maintains a number of previously displayed informational items in memory. If the applicable informational item is present (614—yes) then the informational item is displayed again (608). If the informational item is not present (614—no), then in some embodiments another informational item can be requested beginning at 602. In other embodiments, the last informational item still present in memory is displayed when the user makes a previous request for an item that is not present. If, on the other hand a user makes a forward request (616) (e.g., by selecting an appropriate button or icon) a determination is then a determination is made as to whether the next informational item is currently the memory. In some embodiments, the informational items received at 606 include a number of future informational items associated with the current display. In some embodiments, the future informational items include informational items associated with other display views (e.g., in anticipation of a change of display view). If the informational item is in the memory (614—yes), then it is displayed (608). On the other hand, if is not (614—no) then another informational item is requested beginning at 602. Instead of choosing to see a previous or next informational item, the user may choose an option that changes the display view (618) (e.g., by selecting a conversation view from an InBox view). In this instance, a new request for informational items including the new display view type is begun starting at 602.
In the event that the user clicks or otherwise selects a currently displayed informational item (620), the client application or client assistant opens a new display window, fetches a web page or other information at a location associated with the selected informational item, and displays that information in the new window (622).
Application portion 904 permits a user to select from one or more information types or sources associated with the application, such as tips for using the application or promotions for future products.
According to some embodiments, when an information type is associated with a plurality of information sources, each information source will have an equal probability of being the source of an informational item to be displayed when that information type is selected for display. For example, if the “news” information type has a display probability of 60%, and there are four information sources associated with the news information type, then each of the news sources has a 15% change of being the source of the informational item displayed at any selected point in time. According to some embodiments, within the same information type, the associated information sources are selected in round-robin order. In some embodiments, a user is presented with various settings or options for setting or changing the priorities associated with particular information types and/or particular information sources.
In some embodiments, the configuration display 900 includes a user defined sources portion 906 that enables a user to add one or more information sources to his or her preferences profile. The identified information sources are added to the set of information sources used for generating informational items to presented to the user. In this example, a user may choose to select an informational item from a list of informational items sources by selecting the option at 908. When a user selects the option at 908, the user is presented with a list of sources from which to select. Further, in this example, a user may enter a source at option 910 in the text box associated with the option. After the user has entered the source address the user selects the “add” button 912. Sources that the user has added (via option 908 and/or option 910) appear in the user defined portions (e.g., Source#2914). In this example, information sources may be removed by selecting a “remove” button (e.g., “remove” button 916).
Referring to
Referring to
In some embodiments, the conversation/message server 206 includes the following elements, or a subset or superset of such elements: an updater engine 202 for updating a message database 218; a message index 214 containing index information for messages in the message database 218; a query engine 216 for performing various queries using the message index 214 and message database 218; a auxiliary services server 220 for performing various auxiliary services; spell checker 222 for enabling various spell checking features; and SMTP gateway 224 for sending and receiving messages.
Although illustrated and described in relation to a conversation-based message system, it should be understand that the techniques described herein apply equally well to a message-based message system (e.g., Outlook). Furthermore, one of ordinary skill in the art of computer science will readily recognize that the techniques described herein can be applied to client applications other than applications for viewing and composing messages.
Each of the above identified modules or programs corresponds to a set of instructions for performing a function described above. These modules and programs (i.e., sets of instructions) need not be implemented as separate software programs, procedures or modules, and thus various subsets of these modules may be combined or otherwise re-arranged in various embodiments. In some embodiments, memory 1006 or 1016 may store a subset of the modules and data structures identified above. Furthermore, memory 1006 or 1016 may store additional modules and data structures not described above.
Although some of various drawings illustrate a number of logical stages in a particular order, stages which are not order dependent may be reordered and other stages may be combined or broken out. Alternative orderings and groupings, whether described above or not, may be appropriate or obvious to those of ordinary skill in the art of computer science. Moreover, it should be recognized that the stages could be implemented in hardware, firmware, software or any combination thereof.
The foregoing description, for purpose of explanation, has been described with reference to specific embodiments. However, the illustrative discussions above are not intended to be exhaustive or to limit the invention to the precise forms disclosed. Many modifications and variations are possible in view of the above teachings. The embodiments were chosen and described in order to best explain the principles of the invention and its practical applications, to thereby enable others skilled in the art to best utilize the invention and various embodiments with various modifications as are suited to the particular use contemplated.
This application is a continuation-in-part of U.S. patent application Ser. No. 10/914,035, filed Aug. 6, 2004, which application is incorporated by reference herein in its entirety.
Number | Name | Date | Kind |
---|---|---|---|
5208748 | Flores et al. | May 1993 | A |
5216603 | Flores et al. | Jun 1993 | A |
5613108 | Morikawa | Mar 1997 | A |
5734837 | Flores et al. | Mar 1998 | A |
5740549 | Reilly et al. | Apr 1998 | A |
5761689 | Rayson et al. | Jun 1998 | A |
5832502 | Durham et al. | Nov 1998 | A |
5905863 | Knowles et al. | May 1999 | A |
5913040 | Rakavy et al. | Jun 1999 | A |
5948058 | Kudoh et al. | Sep 1999 | A |
5959621 | Nawaz et al. | Sep 1999 | A |
6029164 | Birrell et al. | Feb 2000 | A |
6085206 | Domini et al. | Jul 2000 | A |
6151596 | Hosomi | Nov 2000 | A |
6182098 | Selker | Jan 2001 | B1 |
6185551 | Birrell et al. | Feb 2001 | B1 |
6330589 | Kennedy | Dec 2001 | B1 |
6350066 | Bobo, II | Feb 2002 | B1 |
6408297 | Ohashi | Jun 2002 | B1 |
6421694 | Nawaz et al. | Jul 2002 | B1 |
6493702 | Adar et al. | Dec 2002 | B1 |
6493703 | Knight et al. | Dec 2002 | B1 |
6507351 | Bixler | Jan 2003 | B1 |
6549957 | Hanson et al. | Apr 2003 | B1 |
6594693 | Borwankar | Jul 2003 | B1 |
6606644 | Ford et al. | Aug 2003 | B1 |
6665668 | Sugaya et al. | Dec 2003 | B1 |
6683627 | Ullmann et al. | Jan 2004 | B1 |
6708205 | Sheldon et al. | Mar 2004 | B2 |
6725228 | Clark et al. | Apr 2004 | B1 |
6742042 | Orton et al. | May 2004 | B1 |
6745197 | McDonald | Jun 2004 | B2 |
6757889 | Ito | Jun 2004 | B1 |
6771291 | DiStefano, III | Aug 2004 | B1 |
6785869 | Berstis | Aug 2004 | B1 |
6820081 | Kawai et al. | Nov 2004 | B1 |
6889361 | Bates et al. | May 2005 | B1 |
6892196 | Hughes | May 2005 | B1 |
7017173 | Armstrong et al. | Mar 2006 | B1 |
7035903 | Baldonado | Apr 2006 | B1 |
7043690 | Bates et al. | May 2006 | B1 |
7089278 | Churchill et al. | Aug 2006 | B1 |
7120668 | Manber et al. | Oct 2006 | B2 |
7139850 | Amemiya et al. | Nov 2006 | B2 |
7143135 | Smith et al. | Nov 2006 | B2 |
7356772 | Brownholtz et al. | Apr 2008 | B2 |
7359936 | Gruen et al. | Apr 2008 | B2 |
7383307 | Kirkland et al. | Jun 2008 | B2 |
7421690 | Forstall et al. | Sep 2008 | B2 |
7433920 | Blagsvedt et al. | Oct 2008 | B2 |
7484175 | Kirkland | Jan 2009 | B2 |
7599852 | Bosarge et al. | Oct 2009 | B2 |
20010016845 | Tribbensee | Aug 2001 | A1 |
20010042100 | Guedalia et al. | Nov 2001 | A1 |
20010047294 | Rothschild | Nov 2001 | A1 |
20020010775 | Rakavy et al. | Jan 2002 | A1 |
20020194229 | Decime et al. | Dec 2002 | A1 |
20030009385 | Tucciarone et al. | Jan 2003 | A1 |
20030020749 | Abu-Hakima et al. | Jan 2003 | A1 |
20030055711 | Doherty | Mar 2003 | A1 |
20030093315 | Sato | May 2003 | A1 |
20030101065 | Rohall et al. | May 2003 | A1 |
20030110227 | O'Hagan | Jun 2003 | A1 |
20030145285 | Miyahira et al. | Jul 2003 | A1 |
20030163537 | Rohall et al. | Aug 2003 | A1 |
20030167310 | Moody et al. | Sep 2003 | A1 |
20030233419 | Beringer | Dec 2003 | A1 |
20040054737 | Daniell | Mar 2004 | A1 |
20040059712 | Dean et al. | Mar 2004 | A1 |
20040078432 | Manber et al. | Apr 2004 | A1 |
20040133564 | Gross et al. | Jul 2004 | A1 |
20040199589 | Keohane et al. | Oct 2004 | A1 |
20040205141 | Goland | Oct 2004 | A1 |
20040210587 | Reysa | Oct 2004 | A1 |
20040260710 | Marston et al. | Dec 2004 | A1 |
20050004990 | Durazo et al. | Jan 2005 | A1 |
20050060643 | Glass et al. | Mar 2005 | A1 |
20050086598 | Marshall, III et al. | Apr 2005 | A1 |
20050091320 | Kirsch et al. | Apr 2005 | A1 |
20050114781 | Brownholtz et al. | May 2005 | A1 |
20050138002 | Giacobbe et al. | Jun 2005 | A1 |
20050144157 | Moody et al. | Jun 2005 | A1 |
20050144241 | Stata et al. | Jun 2005 | A1 |
20050198173 | Evans | Sep 2005 | A1 |
20050198256 | Moody et al. | Sep 2005 | A1 |
20050223066 | Buchheit et al. | Oct 2005 | A1 |
20060123091 | Ho | Jun 2006 | A1 |
20060248209 | Chiu et al. | Nov 2006 | A1 |
20070047697 | Drewry et al. | Mar 2007 | A1 |
20070067404 | Brown et al. | Mar 2007 | A1 |
20070143411 | Costea et al. | Jun 2007 | A1 |
20070143428 | Kumar et al. | Jun 2007 | A1 |
20070198639 | Litwin et al. | Aug 2007 | A1 |
20080147815 | Damm et al. | Jun 2008 | A1 |
20080313292 | Forstall et al. | Dec 2008 | A1 |
Number | Date | Country |
---|---|---|
WO 0023931 | Apr 2000 | WO |
Number | Date | Country | |
---|---|---|---|
Parent | 10914035 | Aug 2004 | US |
Child | 11084379 | US |