Methods and systems for providing contextual information

Information

  • Patent Grant
  • 11195206
  • Patent Number
    11,195,206
  • Date Filed
    Thursday, July 10, 2014
    9 years ago
  • Date Issued
    Tuesday, December 7, 2021
    2 years ago
Abstract
Methods for providing contextual information about communication devices and/or services. Profile information indicating a user's communication devices and/or services is stored. When profile information or a message log is displayed, the user may identify a communication device and/or service. A query inquires whether the user would like contextual information. The contextual information may be obtained from a gateway in a data network or a telecommunications manager in a telecommunication network. The contextual information is displayed. Profile information about a user's communicating partner may be stored. When the user makes an effort to communicate with the partner, a check may be made of the partner's profile information for a preferred communication device and/or service. If the user does not have a communication device and/or service corresponding to that of the communicating partner, a query may inquire whether the user would like contextual information. If so, the contextual information is presented.
Description
FIELD OF THE INVENTIONS

The inventions relate to methods and systems of providing contextual information relating to communication devices and/or communication services to a user.


BACKGROUND

Consumers are inundated with marketing and the advertising of new products and services. A lot of this advertising is wasted because consumers do not always pay attention to the advertising. The trick then, as marketing executives have known for a long time, is to get the consumers to pay attention.


When would a consumer pay attention to advertising? A consumer may pay attention to advertising if the products or services being advertised have some relevance to the consumer. For example, a consumer may pay attention to advertising presented at a time when the consumer's interest is heightened with respect to the products or services being advertised. A consumer's interest generally is heightened when he or she is using or thinking about a product or service. Thus, advertising presented when the consumer is using or thinking about a product or service may be more successful in grabbing the consumer's attention than when the same advertising is presented at other times. Advertising presented when the consumer is using or thinking about a product or service is referred to as “contextual advertising”.


With respect to communication devices and services, it has been difficult to present contextual advertising to a consumer. As noted, contextual advertising is advertising that is relevant to the consumer when presented. Contextual advertising of communication devices or services could be presented when a consumer is using a communication device and/or service. But when a consumer is using a communication device and/or service, generally most of the consumer's attention is given to the communication in progress. The consumer talking on a telephone or wireless unit typically is fully engaged in a conversation, and advertising presented during the conversation, even though it is contextual advertising, goes largely unnoticed.


Accordingly, there is a need for a method or system to deliver contextual advertising of communication devices and/or services in such a manner as to gain the attention of consumers.


SUMMARY

Stated generally, the inventions provide a user with contextual information such as contextual advertising of communication devices and/or services. Advantageously, the contextual information is presented to a user at a time when the user's interest in the communication devices and/or services is heightened. As a result, the user may pay more attention to the information than otherwise, and it is more likely the user may act on the information.


The inventions take advantage of a user's heightened interest in communication devices and services demonstrated at various times in the use of features of a communications manager. For example, a user's interest is interpreted as a heightened interest when the user accesses his or her profile information or message log in the communications manager. As another example, the user's interest is interpreted as heightened when the user makes an effort or otherwise initiates a communication with a communicating partner. During the user's heightened interest, the user is provided with the option of being presented with contextual information. The user is presented with the option so as not to cause the contextual information to be considered as annoying or bothersome. If the user responds positively, then the contextual information presented.


More particularly, the inventions may be implemented through the use of a communications (“com”) manager operating in a personal computer (PC) of a user. The com manager may store profile information relating to the user. The profile information may indicate the communication devices and/or communication services of the user. In particular, the profile information may indicate the type, brand, features, functionalities, specifications, configurations, etc. of the communication device or service.


The user may cause the com manager to display the profile information on the screen of the computer. If the user activates an entry in the profile information, such activation is noted, and a determination is made as to whether the activated entry identifies a communication device and/or communication service. The identification may include the type, brand, features, functions, specifications, configurations, etc. of the communication device and/or communication service. At this point, the user's interest in identified communication devices and/or communication services is heightened because the user has activated an entry including the identified communication devices and/or communication services in his or her profile information. With the user's interest heightened, it is a good time to present contextual advertising to the user.


The user, however, may find it annoying or bothersome to be presented with contextual advertising when the user activates an entry in his or her profile information. If the user finds the contextual information to be annoying or bothersome, then the presentation of the contextual information may have an undesirable negative impact on the user.


Advantageously, the inventions include a mechanism with respect to the presentation of the contextual information so that any annoyance or bother is minimized. As a convenience to the user, a query appears on the computer screen inquiring whether the user would like contextual information about the communication device and/or communication service. Thus, a user may avoid the presentation of the contextual information or select such presentation.


The query presented to the user may inquire whether the user would like to see contextual information about the type, brand, features, functions, specifications, etc. of the communication device and/or communication service. If the user responds positively, then the contextual information may be presented to the user. The user's positive response to the query also may be interpreted as a demonstration of a particularly heightened interest in the contextual information. Thus, the presentation of the contextual information may be particularly effective.


As explained above, the com manager may store profile information about the user, and the user may be presented with contextual information through the use of his or her profile information. But the user may be presented with contextual information in other ways. For example, the user may be presented with contextual information through the use of a message log provided by the com manager. The com manager may provide the message log including, respectively, entries for communications of the user. Each entry may include types of data relating to a communication. The user can display the message log on a computer screen. The user may activate a type of data in an entry of the message log relating to a communication. At this point, the user's interest in the data in the entry in the message log is heightened because the user has activated the data in the entry in his or her message log. With the user's interest heightened, it is a good time to present contextual advertising to the user.


With respect to the message log, the type of data in an entry that may be activated may include an identification of a communicator, a communication device, a communication service, a subject, and/or a date. The activation is noted and a query is displayed. Advantageously, as with the profile information, the user is provided with an opportunity to accept or decline the presentation of the contextual information through the mechanism of the query. The query inquires whether the user would like to be presented with contextual information based on the activated type of data in the entry. If the user responds positively to the query, then the contextual information is presented to the user.


Another instance of a user's heightened interest in communication devices and/or services is the user's effort at communication with a communicating partner. To take advantage of this instance of heightened interest, the inventions provide mechanisms for presenting contextual information to the user.


The com manager may store profile information relating to a communicating partner of the user. The profile information may indicate a preferred communication device and/or communication service of the communicating partner. The com manager notes an effort by the user to communicate with the communicating partner. The identification of the communicating partner is used to check the profile information of the communicating partner for the preferred communication device and/or communication service of the communicating partner. The preferred communication device and/or service of the communicating partner is compared with the communication devices and/or services of the user.


Based on the comparison, a determination may be made that the user has or does not have a communication device and/or a communication service corresponding to the preferred communication device of the communicating partner. If the user does not have such a communication device and/or communication service, the inventions take advantage of the situation to ask whether the user would like to see contextual information. If the response is positive, then the contextual information is presented.


As with the profile information and the message log, the user is not automatically presented with contextual information when a comparison yields a difference between the user's devices/services and the communicating partner's preferred device/service. Instead, so as not to annoy the user with unwanted contextual information, the user is presented with a query. The user is asked whether the user would like contextual information on the preferred communication device and/or service of the communicating partner. If a positive response is received, then the contextual information is presented to the user.


Generally, with respect to contextual information, the com manager may be in direct or functional control of the contextual information to be presented to the user. Alternatively, the com manager may take action to obtain the contextual information. For example, the com manager may obtain the contextual information from a gateway in a data network or from a telecommunications manager in a communications network. As yet another alternative, the com manager may be provided with particular contextual information to present to the user as the opportunity arises. For example, a service provider of wireless service may provide an updated service program advertisement to the com manager. Of course, the service provider may post the contextual information with a telecom manager in the PSTN or a server in a data network for retrieval by the com manager.


In sum, the inventions allow for the delivery of contextual information such as advertising of communication devices and/or services in such a manner as to gain the attention of a user. The inventions take advantage of instances of a user's heightened interest in the subject matter. For example, the contextual information may be delivered in connection with a user's activation of an entry in profile information or message log relating to the user's communications. Further, the contextual information may be presented in connection with a communication initiated by the user to a communicating partner. Moreover, the contextual information is presented at the direction of the user in response to a query to avoid being annoying or burdensome to the user. Thus, the contextual information is presented to a user at a time when the user's interest in the communication devices and/or services is heightened, and the user is more likely to act on the presented information.





BRIEF DESCRIPTION OF THE DRAWINGS


FIG. 1 illustrates an exemplary environment for operation of the inventions.



FIG. 2 illustrates an exemplary message log as may be used with the inventions.



FIG. 3 illustrates an example of profile information as may be used with the inventions.



FIG. 4 is a flow chart illustrating exemplary actions of the inventions.



FIG. 5 illustrates an example of profile information including contextual information as may be used with the inventions.



FIG. 6 illustrates an exemplary message log including contextual information as may be used with the inventions.



FIG. 7 is a flow chart illustrating exemplary actions of the inventions.



FIG. 8 illustrates an example of the presentation of contextual information.





DETAILED DESCRIPTION

The inventions provide contextual information regarding communication devices and/or services. For example, a user may review his or her communication devices and/or services by reviewing his or her profile information stored by a communications (“com”) manager. The user may activate an entry in the profile information such as an entry relating to wireless units. As a result, a query appears inquiring whether the user would like information about wireless units. If the response is positive, then information about wireless units is presented.


Advantageously, the information regarding wireless units is provided at a time when the user's interest in wireless units is heightened as a result of the user's check of the profile information. Thus, the likelihood of the user's paying attention to, and acting on, the information presented about wireless units is heightened.


In addition to the inventions described herein, additional inventions relating to the presentation of contextual information are described in the commonly owned and assigned patent application entitled Methods and Systems for Providing Contextual Information on Communication Devices and Services, filed concurrently with this application in the United States Patent and Trademark Office, and which is incorporated herein by reference.


As noted, the inventions may be implemented through the use of a communications (“com”) manager. In a related patent application, a communications and information resource (CIR) manager is described. See U.S. patent application Ser. No. 09/966,703, entitled “Methods and Systems for a Communications and Information Resource Manager,” filed Sep. 28, 2001, which is incorporated herein by this reference. The CIR manager may be used to implement the inventions described in this application. Prior to describing the inventions, some background about the CIR manager is provided.


The CIR Manager


A CIR manager may function as a “super” manager with respect to the communications devices, services, and systems of a user. In particular, the CIR manager may be used to centralize communications activities and information such that the user does not have to (but may) use multiple communications devices. For example, the CIR manager may be used to keep a log of all types of communications related to the user—whatever the device, whatever the service, whatever the network.


An advantage of the CIR manager is the user does not have to check or use each type of device for its own type of messages. Another advantage is the CIR manager may obtain information from resources including third party resources so as to facilitate communications and information gathering activities of the user. With the CIR manager, the user is provided with a centralized, efficient, and user-friendly way to handle communications activities including ways to receive, view, listen to, play, respond to, store, log, monitor, delete, copy, forward, obtain, create, and to take other actions. Moreover, the CIR manager provides the user with personalized management of communications and information resources.


In addition, in managing the communications and information resources of the user, the CIR manager may provide the user with one or more of the following features and advantages:

    • Recognition of the user and of others as authorized by the user;
    • Remembrance and implementation of authorized users' preferences;
    • Aid in finding information and resources;
    • Information related to an authorized users' activities and communications including call management and detail;
    • Service set-ups, configurations, changes, deletions, additions, updates, and synchronizations;
    • Maintenance of user account and preference information, logs, activity logs, schedules, calendars, general directories, personal directories, and the like;
    • Unified messaging including notice to the user relating to communications and/or other actions; and
    • Suggestions, help, updates, reminders, warnings, alerts, and other comments.


The CIR manager may integrate the features described above pursuant to a user's preferences so as to provide efficient, organized, and user-friendly communications and information resource management.


Even though the inventions are described herein by reference to a CIR manager installed in a personal computer (PC), the inventions may be practiced with other computer system configurations, including hand-held devices, multiprocessor systems, microprocessor based or programmable consumer electronics, mini-computers, mainframe computers, etc.


Exemplary Operating Environment of a CIR Manager—FIG. 1

Exemplary functions of a CIR manager 10 are described above. To provide these functions and others, the CIR manager 10 may interact with a variety of systems, networks, and elements that may be directly connected to the CIR manager 10, may be hosted by the same host(s) as the CIR manager 10, may be functionally connected to the CIR manager 10, and/or may be accessible to the CIR manager 10 either directly and/or through other systems, networks, and/or elements.



FIG. 1 illustrates an exemplary operating environment of a CIR manager 10 implemented on a personal computer (PC) 24. For details of an exemplary PC 24 as may be used with the CIR manager 10, see the previously referenced related application U.S. patent application Ser. No. 09/966,703, entitled “Methods and Systems for a Communications and Information Resource Manager,” filed Sep. 28, 2001.


The operating environment of FIG. 1 illustrates the CIR manager 10 may communicate through the PC 24 with another computer(s) 25 connected or otherwise networked with the PC 24. The CIR manager 10 also may communicate through the Internet 26 with one or more of the following or other devices:

    • Other computer(s) 27;
    • A gateway 28 serving the CIR manager 10;
    • An information resource 30 such as a database;
    • A messaging system 32;
    • A voicemail system 34;
    • An administrative center 36; and
    • The public switched telephone network (PSTN) 38.


In addition, the CIR manager 10 may communicate through the PSTN 38 with one or more of the following or other devices:

    • A telecommunications manager 40;
    • A telephone (wireline unit) 42;
    • A wireless unit 44;
    • A pager 46; and
    • A fax device (not illustrated).


The CIR manager 10 may have access to other computers 25 through local area networks (LANs), wide area networks (WANs), direct connections, and other networks.


The CIR manager 10 also may have access through the PC 24 to a global communications network such as the Internet 26, and through the Internet 26 to other units, networks, and systems. Particularly, the CIR manager 10 may communicate with a gateway 28 connected to or operating on the Internet. The gateway 28 may be a service platform, server, or other device. The gateway 28 may be provided by the service provider of the CIR manager 10, and may serve the CIR manager 10. Communications activities to and from the CIR manager 10 on the PC 24 may be directed to the gateway 28 and/or may pass through the gateway 28 to other systems, networks, and/or elements. In passing through the gateway 28, the communications activities may be facilitated by the gateway 28.


For example, assume a user is a new subscriber to the CIR manager 10. In setting up the user for services available through the CIR manager 10, the CIR manager 10 may send a communication to the gateway 28 for routing to the appropriate element to handle such set-up activities. In an exemplary embodiment, Administrative Center 36 may handle administrative matters including set-up activities for the service provider. The gateway 28 delivers or otherwise routes the communication to the Administrative Center 36 for the set-up activity. The Administrative Center 36 may respond to the gateway 28 with questions, information, and instructions for the CIR manager 10.


Another way in which the gateway 28 may facilitate communications activities of the CIR manager 10 is to function as a router or director of communications and messages. For example, the CIR manager 10 may forward a request for data to the gateway 28. The gateway 28 may determine the data may be obtained from the information resource 30. The gateway 28 then forwards the request for data or the appropriate message to the information resource 30. The information resource 30 may respond to the CIR manager 10 or to the gateway 28, which then communicates with the CIR manager 10.


Further, the gateway 28 may facilitate communications activities between the CIR manager 10 and the PSTN 38, and other elements reached through the PSTN 38 such as the telecom manager 40, and the communications devices including the wireline unit 42, the wireless unit 44, the pager 46, and the fax device 48. Generally, the telecom manager 40 provides general functions and features related to communications of a user. Specifically, the telecom manager 40 may be implemented in a computer, on a service platform, in a network node, or other device. The telecom manager 40 may include connections to devices and networks through integrated services digital network (ISDN) lines and signaling system 7 (SS7) data links. The telecom manager 40 may be capable of functions similar to those of a service switching point (SSP) or service node (SN) of an Advanced Intelligent Network (AIN). For example, the telecom manager 40 may have the following capabilities: signaling, call set-up, routing, and access to databases.


Exemplary Message Log—FIG. 2


FIG. 2 illustrates an exemplary message log 50 such as may be provided by the CIR manager 10 and used in connection with the inventions described herein. Message log 50 includes entries relating to the exemplary user's communications using the CIR manager 10. Specifically, message log 50 includes eight entries 52, 54, 56, 58, 60, 62, 64, and 66. Each entry includes data 68, and in this example, each entry includes four types of data: “from” 70; “type” 72; “subject” 74; and “date” 76. The from data 70 refers to the source or origin of the communication. The type data 72 refers to the type or kind of communication. The subject data 74 refers to the content, the substance, or other feature of the communication. The date data 76 refers to the date of receipt (or transmittal if from the user) of the communication.


Exemplary Profile Information—FIG. 3

The CIR manager may store profile information 102 about a user. Profile information about the user's communicating partners also may be stored as is described below in connection with FIG. 8. FIG. 2 illustrates in block diagram form the profile information 102 that may be stored about a user.


The profile information 102 for the user may include, among other things, a list of the communication devices and services used by the user. In this example, the user has three communication devices: a telephone 104; a wireless unit 106; and a computer (PC) 108. Each of the entries for the respective devices may include a description of the respective device. For example, the telephone 104 is described as Brand X. The wireless unit 106 is described as a Motorola unit. The computer 108 is described as a Dell unit. The descriptions of the devices provided herein are minimal as they are examples only. Generally, the description of a device includes as much information as necessary to be useful in the comparison process described below. For example, the description of a wireless unit may include its brand, trademark, type, operating specifications, functions, and features.


Also in this example, the user makes use of four communication services. Each service is included in the profile information relating to the user and associated with the appropriate device. Further, each of the services is described in the profile information. As FIG. 2 illustrates, the telephone 104 is associated with local (communication) service 110 from BellSouth and long distance service 112 from AT&T. The wireless unit 106 is associated with service 114 from Cingular. The computer 108 is associated with e-mail service 116 from Microsoft. As with the communication devices, the description of a communication service in the profile information includes as much information as necessary to be useful in the comparison process described below. For example, the description of a long distance service may identify the service provider and operating specifications, functions and features.


An Exemplary Process of the Presentation of Contextual Information—FIG. 4


FIG. 4 is a flow chart illustrating exemplary actions of the inventions in presenting contextual information to a user. The actions described in connection with FIG. 4 are further referenced through the description of examples provided below in connection with FIGS. 5-6.


After start action 120, an opportunity to present contextual information is noted in action 122. Such an opportunity may be presented by the user's access to his or her profile information or message log, by the user's initiation of a communication, or other event. In response to noting the opportunity, preliminary information is presented to the user in action 124. The preliminary information may be a query inquiring of the user whether he or she desires to be presented with contextual information. The query also may be referred to as a “trial balloon” when the query is presented on a computer screen such as text in the form of a circumscribed question.


In decision action 126, if the user provides a negative response to the query, then the process ends in end action 128. A failure to respond to the query may be set as a default negative response to the query. But if the user provides a positive response to the query, then the contextual information is presented in action 130. Thereafter, the process ends in end action 128.


Exemplary Presentation of Contextual Information with Profile Information—FIG. 5

The above-described exemplary process of the presentation of contextual information is now described in further detail by reference to an example including the profile information of the user originally described above in connection with FIG. 3.



FIG. 5 illustrates the profile information 102 of the user as illustrated in FIG. 3, but FIG. 5 also illustrates three trial balloons 150, 152, 154 that may be presented to the user with regard to the presentation of contextual information. As a first example, assume the user is checking his or her profile information 102. The user activates the entry 112 corresponding to long distance service in the profile information 102. The activation of the entry may indicate an opportunity to present the user with contextual information. As a result of the activation, the user is presented with a query as to whether the user would like contextual information on the activated entry. In this example, trial balloon 150 includes text that asks the user: “Would you like to see information on long distance service?” This particular trial balloon 150 is presented to the user because the user activated the entry 112 corresponding to long distance service in the profile information. If the user had activated a different entry, then a different query may be presented in the trial balloon.


The user may decline or accept through use of yes/no options (not illustrated) or otherwise. If the user declines, then the trial balloon 150 disappears. If the user accepts, then the trial balloon 150 disappears and is replaced with a presentation of contextual information. Alternatively, the trial balloon 150 remains on the screen, for example, until the user finishes with the contextual information or the trial balloon 150 is otherwise is caused to disappear from the screen.


In this example, the contextual information relates to long distance service such as advertising for a particular long distance carrier. The contextual information may be stored by or readily obtainable by the com manager. Alternatively, the contextual information may be obtained by or provided to the com manager through a telecommunications manager 40 in the PSTN 38, or through a gateway 28 in a data network 26 (see FIG. 1). For example, the com manager may present the contextual information on long distance service by linking to a web site of a particular long distance carrier.


As another example, assume the user is interested in acquiring a new or different wireless unit. The user activates the entry 106 corresponding to wireless units in the profile information 102. The user's activation of the entry 106 corresponding to wireless units is interpreted as showing a heightened interest in wireless units. If the user's interest is understood to be heightened, then an opportunity to present contextual information exists.


In this example, the user is presented with trial balloon 152 that includes the following text: “Would you like to see information on wireless units?” The presentation (or non-presentation) of contextual information proceeds as described above in connection with the previous example of a user's activation of the entry 112 relating to long distance service in the profile information 102.


As yet another example, assume the user is interested in a particular manufacturer, provider or brand of telephone. Advantageously, the inventions allow the user to “drill down” and obtain contextual information on particular elements in an entry of the profile information. In this example, the entry 102 for “telephone” in the profile information 102 identifies the user's telephone as “Brand X”. The user may activate a particular element of an entry, such as the “Brand X” element, and obtain contextual information on that element.


In this example, the user is presented with trial balloon 154 that includes the following text: “Would you like to see information on Brand X?” If the user answers positively, then more drill-down possibilities may exist. Another trial balloon (not illustrated) may be presented to the user that presents the user with models of Brand X and asks whether the user would like to have information on any of the models. The drill-down trial balloons may continue until the appropriate level of details is reached. The presentation (or non-presentation) of contextual information proceeds as described above in connection with the previous examples of a user's activation of the entry 112 relating to long distance service or the entry 106 relating to wireless units in the profile information 102.


In the three examples described in connection with FIG. 5, three different kinds of contextual information are made available to the user, to-wit: long distance service information; wireless unit information; and information about Brand X. By these three examples, the generality of the definition of contextual information is made apparent. Contextual information generally is any type of information that may be associated with or related to a term or element identified by the user. Contextual information may include advertising, marketing, education, consumer, technical, sales, service, safety, quantity, cost, or quality information, etc.


Exemplary Presentation of Contextual Information with a Message Log—FIG. 6

The general process of the presentation of contextual information in connection with a message log is the same as with the profile information 102 described above. Thus, the seven examples presented in association with a message log are set forth in abbreviated form below.



FIG. 6 illustrates a message log 50 of the user as illustrated in FIG. 2, but FIG. 6 also illustrates seven trial balloons 160, 162, 164, 166, 168, 170, and 172 that may be presented to the user with regard to the presentation of contextual information. As a first example, assume the user is checking his or her message log and notes the entry 52 regarding Maude Davis' e-mail. The user activates the part of entry 52 corresponding to the identification of the type of communication from Maude Davis, i.e., e-mail. In this example, trial balloon 160 includes text that asks the user: “Would you like to see information on e-mail service providers?”


Typically, the query or trial balloon presented to the user relates to the contextual information to be provided. The query or trial balloon may include a general question about the activated term, i.e., “Would you like information about e-mail?” The query or trial balloon may include a more particular or directed question about the activated term, i.e., “Would you like information about e-mail service?” or “service providers?” or “technical description of e-mail?” Of course, the query or trial balloon may include more than one question. In fact, as noted above, the query may provide a set of questions that “drill down” from the general to the specific so as to determine with greater particularity the type of contextual information sought by the user. For example, if the user responds positively to trial balloon 160 (“Would you like information on e-mail service providers?”), the trial balloon 160 may substitute a specific question such as: “Which e-mail service providers would you like information on?” or “Which of the following three e-mail service providers (A, B, C) would you like information on?”. Advantageously, the inventions provide the contextual information based on the responses of the user.


Referring again to FIG. 6, an additional six examples of queries/contextual information are described that may be presented to the user as follows:

    • User activates the “subject” in entry 52 corresponding to Maude Davis' e-mail. The “subject” is “Chef Jean-Louis Restaurant”. The following query 162 is presented: “Would you like to see a menu?” If the answer is “yes”, then the inventions may link to the restaurant's website so as to present a menu.
    • User activates the “subject” in entry 54 corresponding to Bill Jones' voice message. The “subject” is a wireless number: “(703) 345-6789”. The following query 164 is presented: “Would you like information on wireless units?”
    • User activates the “date” in entry 62 corresponding to the user's chat room message. The “date” is “5-13-99”. The following query 166 is presented: “Would you like to know what happened on May 13th in history?”
    • User activates the “subject” in entry 66 corresponding to Nancy Woodard's i-page. The “subject” is “status report”. The following query 168 is presented: “Would you like to see the status reports?” If the answer is “yes”, then the user may be presented with the status reports. For example, the user may keep electronic versions of the status reports in his or her word processing program stored in the PC. The com manager may have a path set up so as to be able to retrieve the status reports for presentation to the user in response to an affirmative answer to the query 168.
    • User activates the “type” in entry 60 corresponding to Emily Guida's instant message. The “type” is “instant message”. The following query is presented to the user: “Would you like to upgrade your service?” If the answer is “yes”, then the com manager may compare the version of the user's service (as detailed in the user's profile information in the coin manager) to upgraded versions. The com manager may offer the user various options. With the user's selection, the com manager may contact the appropriate service provider and cause the user's service to be upgraded.
    • User activates the “from” in entry 58 corresponding to Dale Malik's wireless call. The “from” is “Dale Malik”. The following query is presented to the user: “Would you like to see Dale Malik's information?” The com manager may store profile information on communicating partners of the user. If the user responds positively to the query, then the com manager may present the user with Dale Malik's profile information as the contextual information.


An Exemplary Process of the Presentation of Contextual Information—FIG. 7


FIG. 7 is a flow chart illustrating exemplary actions of the inventions in presenting contextual information to a user. The actions described in connection with FIG. 7 are further referenced through the description of examples provided below in connection with FIG. 8.


As noted, the inventions take advantage of the user's heightened interest in certain subject matter to ask the user whether he or she would like information, and if the answer is yes, then to present the information. An instance of a user's heightened interest in communication devices and/or services may be the user's effort at communication with a communicating partner. For example, a user's effort to send an e-mail to a customer may be a good opportunity to present information to the user on the customer's favorite method of communication, especially if the customer's favorite is not e-mail. If the user chooses to communicate via the customer's preference, then the inventions may present the user with a template or otherwise facilitate the user's communications with the customer. If the user does not have facility to communicate using the customer's preference, then the user may be presented with information on how to gain such facility.



FIG. 7 is a flow chart illustrating exemplary actions of the inventions in seizing the opportunity of a user's effort at communication to present the user with contextual information. After start action 180, in action 182 the user's effort at communication with a communicating partner is detected. For example, if a user is using the com manager, the user may click on or otherwise activate a “new communication” feature of the com manager. The user supplies the identity of the communicating partner.


In action 184, the profile information is checked to determined whether the communicating partner has a profile, and if so, whether the communicating partner has a preference for communicating. A preference may relate to communication devices and/or communication services, and may include details about such preference(s). For example, the communicating partner may prefer to communicate by e-mail, and by e-mail as provided by Service Provider X. If the communicating partner has no preference, the lack of preference may be presented to the user and the user may continue the communication effort without the presentation of additional information.


In action 186, the communicating partner's preference(s) is/are compared to the information in the user's profile. Specifically, the comparison is made to determine whether the user has available the preference(s) of the communicating partner for the user's own use. For example, the user may have an e-mail system provided by Service Provider X. If the user has the preference or can make use of it, then in action 188 the user's communication with the communicating partner is facilitated. Facilitation may include any action taken to help the user with the communication. As an example, if the communicating partner's preference is for e-mail, then an e-mail template may be presented to the user for the user's use. Information in the template regarding the communicating partner, the user, etc. may be supplied so as to further facilitate the user's communication. The process then ends in action 190.


Referring again to action 186 wherein a comparison is carried out to determine whether the user uses the communicating partner's preference(s). If the user does not use one or more of the preference(s), then the inventions take advantage of the situation to ask whether the user would like to see contextual information. In action 192 the user is presented with a trial balloon.


Advantageously, the user is not automatically presented with contextual information when a comparison yields a difference between the user's devices/services and the communicating partner's preferred device(s)/service(s). Instead, so as not to annoy the user with unwanted contextual information, the user is presented with a query in the form of the trial balloon in action 192. The user is asked whether the user would like contextual information on the preferred communication devices and/or services of the communicating partner. In this example, the user may be asked whether he or she would like information on the preferred e-mail system or service provider of the communicating partner.


In action 194 a determination is made as to whether the user responded positively or negatively to the query of action 192. If a positive response is received, then the contextual information is presented to the user in action 196 and the process progresses to action 198. But if a negative response is received to the query of action 192, then the process does not present the contextual information, but proceeds to action 198.


In action 198, a check whether the user desires to continue with the communication may be made in action 198. If the check is negative, then the process ends in action 190. On the other hand, if the check in action 198 is positive, then in action 200 the communication of the user is facilitated.


An Exemplary Presentation of Contextual Information—FIG. 8

The exemplary process of the presentation of contextual information described in connection with FIG. 7 is now further illustrated with an example discussed in connection with FIG. 8.


Assume the user desires to communicate with a communicating partner—Dale Malik and makes an effort at such communication as illustrated by the new communication 202. The user's com manager includes profile information on Dale Malik 204. A preference for fax communication 206 is indicated in Dale Malik's profile information 205. The preference for fax communication 206 is compared to the user's profile information 208. The result of the comparison is that the user does not have a facility for fax communication. Thus, the user is presented with a query 210 as follows: “Would you like information about fax machines? fax service?” If the user responds positively, then contextual information is presented to the user. Advantageously, the inventions allow a fax service provider to present Dale Malik with information on their fax machines or service at a time Dale Malik's interest in faxing is heightened. Thus, Dale Malik is more likely to act on the advertising.


Conclusion

In sum, the inventions allow for the delivery of contextual information such as advertising of communication devices and/or services in such a manner as to gain the attention of a user. The inventions take advantage of instances of a user's heightened interest in the subject matter. For example, the contextual information may be delivered in connection with a user's activation of an entry in profile information or message log relating to the user's communications. Further, the contextual information may be presented in connection with a communication initiated by the user to a communicating partner. Moreover, the contextual information is presented at the direction of the user in response to a query to avoid being annoying or burdensome to the user. Thus, the contextual information is presented to a user at a time when the user's interest in the communication devices and/or services is heightened, and the user is more likely to act on the presented information.


The exemplary embodiments of the inventions described herein were chosen and described in order to explain the principles of the inventions and their practical applications so as to enable others skilled in the art to utilize the inventions including various embodiments and various modifications as are suited to the particular uses contemplated. The examples provided herein in the written description or in the drawings are not intended as limitations of the inventions. Other embodiments will suggest themselves to those skilled in the art. Therefore, the scope of the inventions is to be limited only by the claims below.

Claims
  • 1. A method comprising: receiving, from a first client device associated with a first user, a communication request for a first user to communicate with a second user associated with a second client device, the communication request received based on the first user selecting a first option within a communication graphical user interface on the first client device associated with the first user;accessing, based on receiving the communication request, user profile information for the second user to determine one or more communication types that are available on the second client device associated with the second user;comparing, by at least one processor, user profile information for the first user to the user profile information for the second user to determine a communication type from the one or more communication types based on the communication type being available on the first client device associated with the first user;automatically providing, within the communication graphical user interface of the first client device and based on the determined communication type, a communication template that utilizes the determined communication type that is available on the first client device and the second client device; andfacilitating a communication between the first client device and the second client device using the determined communication type.
  • 2. The method of claim 1, further comprising: determining from the user profile information for the second user a communication type preference of the second user; andwherein determining the communication type from the one or more communication types is further based on the communication type preference of the second user.
  • 3. The method of claim 2, wherein the communication type preference of the second user comprises a communication device or communication service.
  • 4. The method of claim 1, wherein the first option within the communication graphical user interface on the first client device associated with the first user comprises a user identifier of the second user.
  • 5. The method of claim 1, further comprising: determining a communication preference for the first user from the user profile information for the first user; andproviding, based on the determined communication preference for the first user, contextual information to the second client device in association with the communication between the first client device and the second client device using the determined communication type.
  • 6. The method of claim 5, further comprising determining, based on the user profile information for the second user, the communication type associated with the determined communication preference for the first user is not available on the second client device.
  • 7. The method of claim 1, further comprising automatically populating the communication template with contact information for the second user.
  • 8. The method of claim 7, wherein the determined communication type comprises email or instant messaging.
  • 9. The method of claim 1, further comprising: detecting a user interaction from the second user corresponding to the communication between the first client device and the second client device using the determined communication type; andproviding, to the second client device and in response to the detected user interaction from the second user, contextual information associated with the communication type.
  • 10. The method of claim 9, wherein the contextual information provided to the second client device comprises a communication type preferred by the first user and available on the second client device associated with the second user.
  • 11. The method of claim 10, further comprising providing, within the contextual information, a selectable option to allow the second user to facilitate a communication between the first client device and the second client device using the determined communication type preferred by the first user and available on the second client device.
  • 12. A non-transitory computer readable medium storing instructions that, when executed by at least one processor, cause a computer system to: receive, from a first client device associated with a first user a communication request for a first user to communicate with and a second user associated with a second client device, the communication request received based on the first user selecting a first option within a communication graphical user interface on the first client device associated with the first user;access, based on receiving the communication request, user profile information for the second user to determine one or more communication types that are available on the second client device associated with;compare user profile information for the first user to the user profile information for the second user to determine a communication type from the one or more communication types based on the communication type being available on the first client device associated with the first user;automatically provide, within the communication graphical user interface of the first client device and based on the determined communication type, a communication template that utilizes the determined communication type that is available on the first client device and the second client device; andfacilitate a communication between the first client device and the second client device using the determined communication type.
  • 13. The non-transitory computer readable medium of claim 12, wherein the instructions, when executed by the at least one processor, cause the computer system to: determine from the user profile information for the second user a communication type preference of the second user; andwherein determining the communication type from the one or more communication types is further based on the communication type preference of the second user.
  • 14. The non-transitory computer readable medium of claim 12, further comprising instructions that, when executed by the at least one processor, cause the computer system to: determine a communication preference for the first user from the user profile information for the first user; andprovide, based on the determined communication preference for the first user, contextual information to the second client device in association with the communication between the first client device and the second client device using the determined communication type.
  • 15. The non-transitory computer readable medium of claim 14, further comprising instructions that, when executed by the at least one processor, cause the computer system to determine, based on the user profile information for the second user, that the communication type associated with the determined communication preference for the first user is not available on the second client device.
  • 16. The non-transitory computer readable medium of claim 12, further comprising instructions that, when executed by the at least one processor, cause the computer system to automatically populate the communication template with contact information for the second user.
  • 17. The non-transitory computer readable medium of claim 12, wherein the first option within the communication graphical user interface on the first client device associated with the first user comprises a user identifier of the second user.
  • 18. The non-transitory computer readable medium of claim 12, wherein the determined communication type comprises email or instant messaging.
  • 19. A system comprising: at least one processor; andat least one non-transitory computer readable storage medium storing instructions thereon that, when executed by the at least one processor, cause the system to: receive, from a first client device associated with a first user a communication request for a first user to communicate with a second user associated with a second client device, the communication request received based on the first user selecting a first option within a communication graphical user interface on the first client device associated with the first user;access, based on receiving the communication request, user profile information for the second user to determine one or more communication types that are available on the second client device associated with the second user;compare user profile information for the first user to the user profile information for the second user to determine a communication type from the one or more communication types based on the communication type being available on the first client device associated with the first user;automatically provide, within the communication graphical user interface of the first client device and based on the determined communication type, a communication template that utilizes the determined communication type that is available on the first client device and the second client device; andfacilitate a communication between the first client device and the second client device using the determined communication type.
  • 20. The system of claim 19, further comprising instructions, that when executed by the at least one processor, cause the system to: determine from the user profile information for the second user a communication type preference of the second user; andwherein determining the communication type from the one or more communication types is further based on the communication type preference of the second user.
RELATED APPLICATION

The present application is a continuation of U.S. patent application Ser. No. 14/323,969, filed Jul. 3, 2014, which is a continuation of U.S. patent application Ser. No. 10/184,670, filed Jun. 28, 2006, which is a continuation in part of U.S. patent application Ser. No. 09/966,703, filed on Sep. 28, 2001 now issued as U.S. Pat. No. 7,313,617. Each of the aforementioned patent(s) and application(s) is hereby incorporated by reference in its entirety.

US Referenced Citations (265)
Number Name Date Kind
4266098 Novak May 1981 A
4703423 Bado et al. Oct 1987 A
4706242 Harland Nov 1987 A
4850007 Marino et al. Jul 1989 A
4935954 Thompson et al. Jun 1990 A
4969136 Chamberlin et al. Nov 1990 A
4975896 D'Agosto et al. Dec 1990 A
5311583 Friedes et al. May 1994 A
5404505 Levinson Apr 1995 A
5436965 Grossman et al. Jul 1995 A
5570417 Byers Oct 1996 A
5592470 Rudrapatna et al. Jan 1997 A
5604492 Abdul-Halim Feb 1997 A
5608786 Gordon Mar 1997 A
5621790 Grossman et al. Apr 1997 A
5644624 Caldwell Jul 1997 A
5661783 Assis Aug 1997 A
5703571 Cannon et al. Dec 1997 A
5708775 Nakamura Jan 1998 A
5802510 Jones Sep 1998 A
5812654 Anderson et al. Sep 1998 A
5818438 Howe et al. Oct 1998 A
5818447 Wolf et al. Oct 1998 A
5822410 McCausland et al. Oct 1998 A
5852775 Hidary Dec 1998 A
5872841 King et al. Feb 1999 A
5889799 Grossman et al. Mar 1999 A
5892508 Howe et al. Apr 1999 A
5909589 Parker et al. Jun 1999 A
5937047 Stabler Aug 1999 A
5943417 Cox et al. Aug 1999 A
5946386 Rogers Aug 1999 A
5966437 Cox et al. Oct 1999 A
5974388 Durham Oct 1999 A
5978475 Schneier et al. Nov 1999 A
5987100 Fortman et al. Nov 1999 A
6002394 Schein et al. Dec 1999 A
6014135 Fernandes Jan 2000 A
6023700 Owens et al. Feb 2000 A
6052730 Felciano et al. Apr 2000 A
6055512 Dean et al. Apr 2000 A
6065047 Carpenter et al. May 2000 A
6075850 Ali et al. Jun 2000 A
6084628 Sawyer Jul 2000 A
6088588 Osborne Jul 2000 A
6091802 Smith et al. Jul 2000 A
6097942 Laiho Aug 2000 A
6118856 Paarsmark et al. Sep 2000 A
6125108 Shaffer et al. Sep 2000 A
6128624 Papeirniak et al. Oct 2000 A
6133853 Obradovich et al. Oct 2000 A
6134235 Goldman et al. Oct 2000 A
6144644 Bajzath et al. Nov 2000 A
6147975 Bowman-Amuah Nov 2000 A
6148261 Obradovich et al. Nov 2000 A
6148329 Meyer Nov 2000 A
6151584 Papeirniak et al. Nov 2000 A
6154530 Letellier Nov 2000 A
6157709 Lawser et al. Dec 2000 A
6167119 Bartholomew et al. Dec 2000 A
6182142 Win et al. Jan 2001 B1
6185433 Lele et al. Feb 2001 B1
6205211 Thomas et al. Mar 2001 B1
6208721 Feinberg et al. Mar 2001 B1
6216104 Moshfeghi et al. Apr 2001 B1
6233317 Homan et al. May 2001 B1
6236768 Rhodes May 2001 B1
6237027 Namekawa May 2001 B1
6247043 Bates et al. Jun 2001 B1
6252672 Sugawara et al. Jun 2001 B1
6253188 Witek et al. Jun 2001 B1
6266690 Shankarappa et al. Jul 2001 B1
6272150 Hrastar et al. Aug 2001 B1
6272537 Kekic et al. Aug 2001 B1
6282275 Gurbani Aug 2001 B1
6301245 Luzeski et al. Oct 2001 B1
6301342 Ander et al. Oct 2001 B1
6304635 Iwani et al. Oct 2001 B1
6308328 Bowcutt et al. Oct 2001 B1
6317485 Homan et al. Nov 2001 B1
6320947 Joyce et al. Nov 2001 B1
6330079 Dugan et al. Dec 2001 B1
6338066 Martin et al. Jan 2002 B1
6339639 Henderson Jan 2002 B1
6345239 Bowman-Amuah Feb 2002 B1
6351771 Craddock et al. Feb 2002 B1
6353659 VanRyzin et al. Mar 2002 B1
6353852 Nestoriak et al. Mar 2002 B1
6360254 Linden et al. Mar 2002 B1
6385311 Bauer May 2002 B1
6400810 Skladman et al. Jun 2002 B1
6404762 Luzeski et al. Jun 2002 B1
6411685 O'Neal Jun 2002 B1
6421725 Vermilyea et al. Jul 2002 B1
6424966 Meyerzon et al. Jul 2002 B1
6424995 Shuman Jul 2002 B1
6430177 Luzeski et al. Aug 2002 B1
6430188 Kadambi et al. Aug 2002 B1
6434747 Khoo et al. Aug 2002 B1
6445682 Weitz Sep 2002 B1
6445913 Ezuriko Sep 2002 B1
6453353 Win et al. Sep 2002 B1
6459782 Bedrosian Oct 2002 B1
6460082 Lumelsky et al. Oct 2002 B1
6493437 Olshansky Dec 2002 B1
6496838 Zamora-Mckelvy et al. Dec 2002 B1
6502242 Howe et al. Dec 2002 B1
6515968 Combar et al. Feb 2003 B1
6518984 Maeckel et al. Feb 2003 B1
6526044 Cookmeyer et al. Feb 2003 B1
6529954 Cookmeyer et al. Mar 2003 B1
6535585 Hanson et al. Mar 2003 B1
6556666 Beyda et al. Apr 2003 B1
6560633 Roberts May 2003 B1
6564261 Gudjonsson et al. May 2003 B1
6567982 Howe et al. May 2003 B1
6570855 Kung et al. May 2003 B1
6574678 Nykaned et al. Jun 2003 B1
6594255 Neuman Jul 2003 B1
6608637 Beaton et al. Aug 2003 B1
6609253 Swix et al. Aug 2003 B1
6611501 Owen et al. Aug 2003 B1
6615184 Hicks Sep 2003 B1
6615241 Miller et al. Sep 2003 B1
6625258 Ram Sep 2003 B1
6631186 Adams et al. Oct 2003 B1
6631402 Devine Oct 2003 B1
6633630 Owens et al. Oct 2003 B1
6640230 Alexander et al. Oct 2003 B1
6640241 Ozzie et al. Oct 2003 B1
6665378 Spielman et al. Dec 2003 B1
6699007 Huang et al. Mar 2004 B2
6701348 Sommerer Mar 2004 B2
6708202 Shuman et al. Mar 2004 B1
6711154 O'Neal Mar 2004 B1
6717513 Sandelman et al. Apr 2004 B1
6721748 Knight et al. Apr 2004 B1
6731927 Stern et al. May 2004 B1
6735286 Hansen et al. May 2004 B1
6738462 Brunson May 2004 B1
6741697 Benson et al. May 2004 B2
6745229 Gobin et al. Jun 2004 B1
6747970 Lamb et al. Jun 2004 B1
6748056 Capriotti et al. Jun 2004 B1
6754181 Elliott et al. Jun 2004 B1
6757732 Sollee et al. Jun 2004 B1
6760601 Suoknunti Jul 2004 B1
6760727 Schroeder et al. Jul 2004 B1
6763102 Chen Jul 2004 B1
6766369 Haitsuka et al. Jul 2004 B1
6768722 Katseff et al. Jul 2004 B1
6772188 Cloutier Aug 2004 B1
6782086 Clapper Aug 2004 B2
6785266 Swartz Aug 2004 B2
6785379 Rogers Aug 2004 B1
6788926 Frangione et al. Sep 2004 B1
6798868 Montgomery et al. Sep 2004 B1
6804707 Ronning Oct 2004 B1
6804716 Koch et al. Oct 2004 B1
6806977 Freeny et al. Oct 2004 B1
6807423 Armstrong et al. Oct 2004 B1
6807574 Partovi et al. Oct 2004 B1
6816469 Kung et al. Nov 2004 B1
6820204 Desai et al. Nov 2004 B1
6826639 Pasumansky Nov 2004 B2
6829233 Gilboy Dec 2004 B1
6834195 Brandenberg et al. Dec 2004 B2
6839414 Enzmann et al. Jan 2005 B1
6842767 Partovi et al. Jan 2005 B1
6853711 Brisebois et al. Feb 2005 B2
6857024 Chen Feb 2005 B1
6879995 Chinta et al. Apr 2005 B1
6882709 Sherlock Apr 2005 B1
6892083 Shostak May 2005 B2
6895426 Cotright et al. May 2005 B1
6895559 Forder May 2005 B2
6904137 Brandt et al. Jun 2005 B2
6910186 Kim Jun 2005 B2
6914967 Baca et al. Jul 2005 B1
6917610 Kung Jul 2005 B1
6920208 Rosen Jul 2005 B1
6920213 Pershan Jul 2005 B2
6928154 Cheaito Aug 2005 B1
6940958 Clapper Sep 2005 B2
6947979 Pon Sep 2005 B1
6948838 Ruthfield et al. Sep 2005 B2
6961751 Bates et al. Nov 2005 B1
6973556 Milligan et al. Dec 2005 B2
6980982 Geddes et al. Dec 2005 B1
6981023 Hamilton et al. Dec 2005 B1
6981040 Konig et al. Dec 2005 B1
6981223 Becker Dec 2005 B2
6988128 Alexander et al. Jan 2006 B1
7007085 Malik Feb 2006 B1
7031961 Pitkow et al. Apr 2006 B2
7062535 Stark Jun 2006 B1
7088805 Moore Aug 2006 B1
7092936 Alonso et al. Aug 2006 B1
7096232 Doss Aug 2006 B2
7107275 Quinn et al. Sep 2006 B2
7117504 Smith et al. Oct 2006 B2
7130891 Bernardin et al. Oct 2006 B2
7171448 Danielson et al. Jan 2007 B1
7213005 Mourad et al. May 2007 B2
7225409 Schnarel May 2007 B1
7272633 Malik Sep 2007 B2
7313617 Malik Dec 2007 B2
7325032 Zuberec et al. Jan 2008 B2
7441027 Malik Oct 2008 B2
7472187 Malik Dec 2008 B2
7496189 Clarisse et al. Feb 2009 B2
7525955 Velez-Rivera et al. Apr 2009 B2
7778399 Ambrose Aug 2010 B2
7860804 Littrell Dec 2010 B2
7929951 Stevens Apr 2011 B2
8023622 Timmins et al. Sep 2011 B2
8271591 Malik Sep 2012 B2
8341018 Malik Dec 2012 B2
8423412 Vierl Apr 2013 B2
8554693 Littrell Oct 2013 B2
8554718 Gage Oct 2013 B2
8560673 Malik Oct 2013 B2
20010013050 Shah Aug 2001 A1
20010013069 Shah Aug 2001 A1
20010027478 Meier Oct 2001 A1
20010029468 Yamaguchi Oct 2001 A1
20020029163 Joao Mar 2002 A1
20020055924 Liming May 2002 A1
20020059117 Yoch et al. May 2002 A1
20020069048 Sadhwani et al. Jun 2002 A1
20020073142 Moran Jun 2002 A1
20020076015 Norwitz et al. Jun 2002 A1
20020078151 Wickam et al. Jun 2002 A1
20020091829 Wood Jul 2002 A1
20020092021 Yap et al. Jul 2002 A1
20020098849 Bloebaum et al. Jul 2002 A1
20020099657 Black et al. Jul 2002 A1
20020099775 Gupta et al. Jul 2002 A1
20020099777 Gupta et al. Jul 2002 A1
20020111813 Capps Aug 2002 A1
20020124057 Besprosvan Sep 2002 A1
20020174188 Clark et al. Nov 2002 A1
20020180776 Fishman Dec 2002 A1
20020184329 Chen et al. Dec 2002 A1
20020194274 Kroeger Dec 2002 A1
20030009530 Philonenko et al. Jan 2003 A1
20030014553 Zhao Jan 2003 A1
20030023757 Ishioka et al. Jan 2003 A1
20030065778 Malik Apr 2003 A1
20030087652 Simon May 2003 A1
20030156134 Kim Aug 2003 A1
20040091091 Maruyama May 2004 A1
20040125133 Pea et al. Jul 2004 A1
20040236619 Gundersen et al. Nov 2004 A1
20040254999 Bulleit et al. Dec 2004 A1
20050038863 Onyon et al. Feb 2005 A1
20050120305 Engstrom et al. Jun 2005 A1
20050149487 Celik Jul 2005 A1
20050188043 Cortright et al. Aug 2005 A1
20050204030 Koch et al. Sep 2005 A1
20060062205 Doherty et al. Mar 2006 A1
20070100967 Smith May 2007 A1
20070130338 Malik Jun 2007 A1
20120078725 Maitra et al. Mar 2012 A1
20130138513 Malik May 2013 A1
Foreign Referenced Citations (3)
Number Date Country
2000-105739 Apr 2000 JP
WO 9717774 May 1997 WO
WO 03056821 Jul 2003 WO
Non-Patent Literature Citations (128)
Entry
U.S. Appl. No. 11/638,546, Mar. 22, 2016, Office Action.
U.S. Appl. No. 14/323,447, Jan. 5, 2016, Office Action.
U.S. Appl. No. 10/184,670, Dec. 29, 2014, Office Action.
U.S. Appl. No. 14/323,447, Jan. 16, 2015, Office Action.
U.S. Appl. No. 14/323,464, Jan. 16, 2015, Office Action.
U.S. Appl. No. 14/323,472, Jan. 15, 2015, Office Action.
U.S. Appl. No. 14/323,973, filed Jul. 3, 2014, Malik et al.
U.S. Appl. No. 14/325,039, filed Jul. 7, 2014, Malik et al.
U.S. Appl. No. 14/325,053, filed Jul. 7, 2014, Malik et al.
U.S. Appl. No. 14/448,725, filed Jul. 31, 2014, Malik et al.
U.S. Appl. No. 14/323,447, filed Jul. 3, 2014, Malik et al.
U.S. Appl. No. 14/323,464, filed Jul. 3, 2014, Malik et al.
U.S. Appl. No. 14/323,472, filed Jul. 3, 2014, Malik et al.
U.S. Appl. No. 14/323,969, filed Jul. 3, 2014, Malik et al.
U.S. Appl. No. 14/328,516, filed Jul. 10, 2014, Malik et al.
“Microsoft Outlook 2000 SR-1 Readme File,” www.microsoft.com/assistance/offhelp/off2000/outlook/outlhlp9/html/olread9.htm, as of Apr. 30, 2002.
“Microsoft Outlook version 2002 (included in office XP),” Microsoft Outlook Product Guide, pp. 1-11.
“Microsoft Office,” Microsoft Outlook 2000 Product Enhancements Guide, Oct. 1998.
Microsoft Outlook 2000 “About” screen capture printout (1 page).
Microsoft Outlook Programming, webpage printout (5 pages) retrieved from www.outlookcode.com, Apr. 17, 2006.
Gordon Padwick and Helen Ferddema, “Special Edition Using Microsoft Outlook”, May 12, 1999.
Kox, Klass, Mobile Contextual Advertising: HAIT Master Thesis series nr. 08-005, pp. 1-27, Dec. 2008.
“Delivering dollars on demand: cable industry weighs different models to build revenue,” Nov. 3, 2003; Braodcasting & Cable, v133, n44, p. S3, 8pp.
VH1, “Pop-Up Video,” 1980s, VH1.com, www.vh1.com/shows/dyn/pop_up_video/series_about.html, pp. 1-2, retrieved May 2, 2007.
VH1, “Pop-Up Video,” Oct. 26, 2002, VH1.com, web.archive.org/web/20021026183153/http://www.vhi.com/shows/dyn/pop_up_video/series_abouthtml, p. 1.
U.S. Appl. No. 09/966,703, Nov. 17, 2005, Office Action.
U.S. Appl. No. 09/966,703, May 26, 2006, Office Action.
U.S. Appl. No. 09/966,703, May 2, 2007, Office Action.
U.S. Appl. No. 09/966,703, Oct. 25, 2007, Notice of Allowance.
U.S. Appl. No. 10/109,909, Jul. 15, 2004, Office Action.
U.S. Appl. No. 10/109,909, Jan. 24, 2005, Office Action.
U.S. Appl. No. 10/109,909, Jul. 21, 2005, Notice of Allowance.
U.S. Appl. No. 10/184,588, Nov. 20, 2005, Office Action.
U.S. Appl. No. 10/184,588, Aug. 11, 2006, Office Action.
U.S. Appl. No. 10/184,588, Apr. 9, 2007, Office Action.
U.S. Appl. No. 10/184,588, Sep. 13, 2007, Office Action.
U.S. Appl. No. 10/184,588, Jan. 9, 2008, Office Action.
U.S. Appl. No. 10/184,588, Aug. 4, 2008, Office Action.
U.S. Appl. No. 10/184,588, Dec. 10, 2008, Office Action.
U.S. Appl. No. 10/184,588, May 21, 2009, Office Action.
U.S. Appl. No. 10/184,588, Nov. 10, 2009, Office Action.
U.S. Appl. No. 10/184,588, May 7, 2010, Office Action.
U.S. Appl. No. 10/184,588, Oct. 13, 2010, Office Action.
U.S. Appl. No. 10/184,588, Aug. 20, 2012, Notice of Allowance.
U.S. Appl. No. 10/184,670, Jun. 9, 2008, Office Action.
U.S. Appl. No. 10/184,670, Nov. 18, 2008, Office Action.
U.S. Appl. No. 10/184,670, Apr. 1, 2009, Office Action.
U.S. Appl. No. 10/184,670, Oct. 23, 2009, Office Action.
U.S. Appl. No. 10/184,670, May 26, 2010, Office Action.
U.S. Appl. No. 10/184,670, Nov. 24, 2010, Office Action.
U.S. Appl. No. 10/184,670, Aug. 14, 2013, Office Action.
U.S. Appl. No. 10/184,670, Nov. 26, 2013, Office Action.
U.S. Appl. No. 10/251,025, Nov. 4, 2005, Office Action.
U.S. Appl. No. 10/251,025, Apr. 24, 2006, Office Action.
U.S. Appl. No. 10/251,025, Jan. 5, 2007, Office Action.
U.S. Appl. No. 10/251,025, Jul. 5, 2007, Notice of Allowance.
U.S. Appl. No. 10/251,025, Jul. 20, 2007, Notice of Allowance.
U.S. Appl. No. 10/739,599, May 30, 2006, Office Action.
U.S. Appl. No. 10/739,599, Dec. 19, 2006, Office Action.
U.S. Appl. No. 10/739,599, May 9, 2007, Office Action.
U.S. Appl. No. 10/739,599, Jun. 28, 2007, Office Action.
U.S. Appl. No. 10/739,599, Mar. 17, 2008, Office Action.
U.S. Appl. No. 10/739,599, Aug. 19, 2010, Notice of Allowance.
U.S. Appl. No. 10/997,305, May 2, 2006, Office Action.
U.S. Appl. No. 10/997,305, Oct. 17, 2006, Office Action.
U.S. Appl. No. 10/997,305, Apr. 10, 2007, Office Action.
U.S. Appl. No. 10/997,305, Dec. 18, 2007, Office Action.
U.S. Appl. No. 10/997,305, May 19, 2008, Office Action.
U.S. Appl. No. 10/997,305, Oct. 6, 2008, Notice of Allowance.
U.S. Appl. No. 11/236,907, May 2, 2006, Office Action.
U.S. Appl. No. 11/236,907, Oct. 19, 2006, Office Action.
U.S. Appl. No. 11/236,907, Mar. 6, 2007, Office Action.
U.S. Appl. No. 11/236,907, Aug. 24, 2007, Office Action.
U.S. Appl. No. 11/236,907, Jan. 25, 2008, Office Action.
U.S. Appl. No. 11/236,907, Aug. 7, 2008, Notice of Allowance.
U.S. Appl. No. 11/638,546, Apr. 10, 2009, Office Action.
U.S. Appl. No. 11/638,546, Oct. 8, 2009, Office Action.
U.S. Appl. No. 11/638,546, Feb. 6, 2012, Office Action.
U.S. Appl. No. 11/638,546, Jul. 18, 2012, Office Action.
U.S. Appl. No. 11/638,546, Aug. 2, 2013, Office Action.
U.S. Appl. No. 11/638,546, Feb. 10, 2014, Office Action.
U.S. Appl. No. 11/900,153, Dec. 3, 2010, Office Action.
U.S. Appl. No. 11/900,153, Apr. 21, 2011, Office Action.
U.S. Appl. No. 11/900,153, Jun. 21, 2012, Notice of Allowance.
U.S. Appl. No. 12/335,792, May 23, 2011, Office Action.
U.S. Appl. No. 12/335,792, Apr. 20, 2012, Office Action.
U.S. Appl. No. 12/335,792, Oct. 2, 2012, Office Action.
U.S. Appl. No. 12/335,792, Jun. 20, 2013, Notice of Allowance.
U.S. Appl. No. 12/948,962, Dec. 5, 2012, Office Action.
U.S. Appl. No. 12/948,962, Jun. 12, 2013, Notice of Allowance.
U.S. Appl. No. 13/687,068, Jan. 2, 2014, Office Action.
U.S. Appl. No. 13/687,068, Oct. 7, 2014, Office Action.
U.S. Appl. No. 10/184,670, Jul. 9, 2015, Office Action.
U.S. Appl. No. 11/638,546, Jul. 13, 2015, Office Action.
U.S. Appl. No. 13/687,068, Jun. 24, 2015, Office Action.
U.S. Appl. No. 14/323,447, Jun. 24, 2015, Office Action.
U.S. Appl. No. 14/323,464, Jun. 25, 2015, Office Action.
U.S. Appl. No. 14/323,472, Jun. 25, 2015, Office Action.
U.S. Appl. No. 13/687,068, Aug. 24, 2018, Office Action.
U.S. Appl. No. 14/323,464, Sep. 11, 2018, Office Action.
U.S. Appl. No. 14/325,053, Aug. 28, 2018, Office Action.
U.S. Appl. No. 14/325,039, Oct. 4, 2018, Office Action.
U.S. Appl. No. 14/448,725, Oct. 4, 2018, Office Action.
U.S. Appl. No. 14/328,516, Sep. 27, 2018, Office Action.
U.S. Appl. No. 11/638,546, Feb. 16, 2018, Office Action.
U.S. Appl. No. 13/687,068, Jan. 29, 2018, Office Action.
U.S. Appl. No. 14/323,464, Dec. 28, 2017, Office Action.
U.S. Appl. No. 14/325,053, Dec. 13, 2017, Office Action.
U.S. Appl. No. 14/325,039, Mar. 14, 2018, Office Action.
U.S. Appl. No. 14/328,516, Dec. 13, 2017, Office Action.
U.S. Appl. No. 14/323,464, Apr. 23, 2018, Office Action.
U.S. Appl. No. 14/448,725, Apr. 20, 2018, Office Action.
U.S. Appl. No. 14/323,464, May 17, 2019, Notice of Allowance.
U.S. Appl. No. 14/325,053, Apr. 25, 2019, Office Action.
U.S. Appl. No. 14/328,516, May 24, 2019, Office Action.
U.S. Appl. No. 14/323,447, Jul. 25, 2016, Office Action.
U.S. Appl. No. 14/323,973, Jun. 9, 2016, Office Action.
U.S. Appl. No. 10/184,670, Jul. 27, 2017, Office Action.
U.S. Appl. No. 14/323,447, Jul. 28, 2017, Office Action.
U.S. Appl. No. 14/448,725, May 23, 2017, Office Action.
U.S. Appl. No. 10/184,670, Jan. 13, 2017, Office Action.
U.S. Appl. No. 11/638,546, Mar. 28, 2017, Office Action.
U.S. Appl. No. 14/325,053, Apr. 3, 2017, Office Action.
U.S. Appl. No. 14/325,039, Apr. 5, 2017, Office Action.
U.S. Appl. No. 14/328,516, Apr. 5, 2017, Office Action.
U.S. Appl. No. 14/325,039, Dec. 19, 2019, Office Action.
U.S. Appl. No. 14/325,039, dated Jun. 16, 2020, Office Action.
U.S. Appl. No. 14/448,725, dated Sep. 18, 2020, Notice of Allowance.
Related Publications (1)
Number Date Country
20140324595 A1 Oct 2014 US
Continuations (2)
Number Date Country
Parent 14323969 Jul 2014 US
Child 14328509 US
Parent 10184670 Jun 2002 US
Child 14323969 US
Continuation in Parts (1)
Number Date Country
Parent 09966703 Sep 2001 US
Child 10184670 US