Notification platform architecture

• US 7,243,130 B2
• Filed: 03/16/2001
• Issued: 07/10/2007
• Est. Priority Date: 03/16/2000
• Status: Expired due to Fees

• Current Assignee: Microsoft Technology Licensing LLC (Microsoft Corporation)
• Original Assignee: Microsoft Corporation
• Inventors: Horvitz, Eric J., Jacobs, Andrew W., Kadie, Carl M., Hovel, David O.
• Primary Examiner(s): Vaughn; William
• Assistant Examiner(s): MESFIN, YEMANE
• Application Number:
  US10/220,419
• Publication Number:
  US 20040128359A1
• Time in Patent Office: 2,307 Days
• Field of Search: 709/223, 709/224, 709/245, 709/206, 709/207, 709/219, 709/238, 709/240, 709/225, 709/232
• US Class Current: 709/207
• CPC Class Codes: G05B 19/404 characterised by control arrangements for compensation, e.g. for backlash, overshoot, tool offset, tool wear, temperature, machine construction errors, load, inertia G05B19/19, G05B19/41 take precedence
• CPC Class Codes: H04L 51/04 Real-time or near real-time messaging, e.g. instant messaging [IM]
• CPC Class Codes: H04L 51/224 providing notification on incoming messages, e.g. pushed notifications of received messages
• CPC Class Codes: H04L 51/226 Delivery according to priorities
• CPC Class Codes: H04L 51/56 Unified messaging, e.g. interactions between e-mail, instant messaging or converged IP messaging [CPM]
• CPC Class Codes: H04L 67/306 User profiles
• CPC Class Codes: H04L 67/51 Discovery or management thereof, e.g. service location protocol [SLP] or web services
• CPC Class Codes: H04L 67/52 specially adapted for the location of the user terminal
• CPC Class Codes: H04L 67/54 Presence management, e.g. monitoring or registration for receipt of user log-on information, or the connection status of the users
• CPC Class Codes: H04L 67/55 Push-based network services
• CPC Class Codes: H04L 67/61 taking into account QoS or priority requirements
• CPC Class Codes: H04L 67/62 Establishing a time schedule for servicing the requests
• CPC Class Codes: H04L 67/63 Routing a service request depending on the request content or context
• CPC Class Codes: H04L 67/75 Indicating network or usage conditions on the user display
• CPC Class Codes: H04L 69/329 in the application layer [OSI layer 7]
• CPC Class Codes: H04L 9/40 Network security protocols

Abstract

The present invention relates to a system (10) and methodology (170, 173, 180, 400, 600, 1000) to enable a variety of information associated with one or more notification sources (26-28) to be directed to one or more notification sinks (36-38) via a notification platform architecture (10). The architecture (10) includes a context analyzer (22) for determining a user'"'"'s state such as location and attentional focus, wherein the user'"'"'s state is employed by a notification manager (24) to make decisions regarding what, when and how information generated by the notification sources (26-28) should be forwarded to the notification sinks (36-38), for example. These decisions can include a cost benefit analysis wherein considerations are given as to whether the benefits of notifying the user are outweighed by the costs of disrupting the user. Decision-theoretic policies (177, 180) and/or somewhat less formal heuristic policies (177) can be employed to enable the decision-making process within the notification manager (24).

Claims

1. A notification system, comprising:

a context analyzer to determine a context associated with an entity and to access and store information regarding context information and notification parameters;

a notification manager to convey one or more notifications to the entity based at least in part on the determined context;

at least one notification source to generate the one or more notifications; and

at least one notification sink to receive the one or more notifications, the at least one notification sink having parameters associated with it representing;

a cost of communication of the notification sink indicating a communication cost incurred by the entity when receiving information contained within a notification conveyed to the notification sink; and

a cost of disruption of the notification sink indicating a disruption cost incurred by the entity when receiving information contained within a notification conveyed to the notification sink.

2. The system of claim 1, wherein the entity comprises a user, an agent, a process, a server, a computer, a machine, a company, an organization, a business, a computer program, a service, or a thread or combinations thereof.

3. The system of claim 1, wherein the at least one notification source is configured to generate one or more notifications intended for the entity.

4. The system of claim 1, wherein the at least one sink is configured to provide the notifications to the entity.

5. The system of claim 1, wherein the context analyzer comprises a notification parameters store to store default notification preferences for the entity as a profile.

6. The system of claim 1, wherein the context analyzer is configured to determine a current context of a user based on at least one context source.

7. The system of claim 6, wherein the at least one context source comprises visual information of the user, desktop information of the user, personal-information-manager (PIM) information of the user, current time and day, mobile device usage of the user, or location of the user or combinations thereof.

8. The system of claim 6, wherein the context analyzer is configured to determine the current context based on the at least one context source by utilizing a statistical model, a profile, a direct access of user location and activity, or a real-time user specification of user state or combinations thereof.

9. The system of claim 1, wherein the notifications generated by the at least one notification source comprise e-mail, instant messaging, system messages, automated assistance, results from persistent, ongoing queries to one or more search facilities or services, updates to the number or content of documents available in a shared file system, updates about organizational information, information that comes available that is related to a specified content, document or topic, Internet-related information and news services, people availability, location, proximity, scheduling queries, proximities or locations of companies and organizations or combinations thereof.

10. The system of claim 1, wherein the at least one notification source has one or more parameters associated with it representing:

a classification of a current notification generated by the notification source indicating value of information contained in the current notification;

or

a time criticality of the current notification generated by the notification source indicating time-dependent decay of the value of the information contained in the current notification or a combination thereof.

11. The system of claim 1, wherein the at least one notification source has parameters associated with it representing:

a message class of a current notification generated by the notification source indicating a type of communication of the current notification;

a relevance of the current notification indicating a likelihood of the relevance of information contained in the current notification;

a novelty of the current notification indicating a likelihood of whether an entity already knows the information;

or

a fidelity of the current notification indicating a loss of value to the entity of the information upon truncation of the information

or combinations thereof.

12. The system of claim 1, wherein the at least one notification source comprises a pull-type notification source or a push-type notification source or a combination thereof.

13. The system of claim 1, wherein the at least one notification sink comprises a desktop computer, a PDA, a cellular phone, a pager or an automotive computerized device or combinations thereof.

14. The system of claim 1, wherein the notification manager is configured to perform a decision-theoretic analysis of the notifications from the at least one notification source based on the information stored by the context analyzer to determine which of the notifications from the at least one notification source should be conveyed to which of the at least one notification sink.

15. The system of claim 1, wherein the notification manager is configured to perform a heuristic analysis of the notifications from the at least one notification source based on the information stored by the context analyzer to determine which of the notifications from the at least one notification source should be conveyed to which of the at least one notification sinks.

16. A notification system, comprising:

a context analyzer to store information regarding notification parameters, the context analyzer comprising;

a user notification parameters store to store default notification preferences for a user, and

a user context module to determine a current context of the user based on at least one context source;

at least one notification source to generate notifications intended for the user;

at least one notification sink to provide the notifications to the user; and

a notification manager to convey the notifications generated by the at least one notification source to the at least one notification sink based on the information stored in the context analyzer by performing a decision-theoretic analysis,

wherein the at least one notification sink is configured to provide the notifications to the user and has parameters associated with it representing;

a cost of communication of the notification sink indicating a communication cost incurred by the user when receiving information contained within a notification conveyed to the notification sink; and

a cost of disruption of the notification sink indicating a disruption cost incurred by the user when receiving information contained within a notification conveyed to the notification sink.