US7249159B1 - Notification platform architecture - Google Patents
Notification platform architecture Download PDFInfo
- Publication number
- US7249159B1 US7249159B1 US09/596,365 US59636500A US7249159B1 US 7249159 B1 US7249159 B1 US 7249159B1 US 59636500 A US59636500 A US 59636500A US 7249159 B1 US7249159 B1 US 7249159B1
- Authority
- US
- United States
- Prior art keywords
- notification
- user
- information
- sink
- source
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Expired - Fee Related, expires
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q10/00—Administration; Management
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L51/00—User-to-user messaging in packet-switching networks, transmitted according to store-and-forward or real-time protocols, e.g. e-mail
- H04L51/21—Monitoring or handling of messages
- H04L51/214—Monitoring or handling of messages using selective forwarding
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/2866—Architectures; Arrangements
- H04L67/30—Profiles
- H04L67/306—User profiles
Definitions
- This invention relates generally to unified receipt and notification of alerts generated by varied devices and applications for conveyance to a user, and more particularly to an architecture for such unified context sensing and analysis, alert receipt, and notification.
- a user may receive e-mail and instant messages over a computer, pages over a pager, voice-mail over a phone, such as a cellular (“cell”) or landline phone, news information over the computer, etc. This makes it difficult for the user to receive all his or her different information wherever the user happens to be.
- a phone such as a cellular (“cell”) or landline phone
- a user may be away from his or her computer, but receive an important e-mail.
- the user may have access only to a cell phone or a pager, however.
- the user may be working on the computer, and have turned off the ringer and voice-mail indicator on the phone. When an important voice-mail is left, the user has no way of receiving this information on the computer.
- alerts may not be important to the user—for example, an e-mail from the user's manager or co-worker should receive higher priority than the latest sports scores. More generally, the value of the information contained in an alert should be balanced with the costs associated with the disruption of the user by an alert. Both the costs and value may be context sensitive. Beyond notifications about communications, users are alerted with increasing numbers of services, error messages, and computerized offers for assistance.
- the architecture includes a user mechanism, one or more notification sources and sinks, and a notification manager.
- the user mechanism is designed to both store user profile information regarding notification parameters of a user, such as the user's default notification preferences, and to provide a user context identification and updating service.
- Each notification source is designed to generate notifications intended for the user, while each notification sink is designed to provide the notifications to the user.
- the notification manager is designed to convey the notifications generated by the sources to the sinks, based on information stored by the user mechanism and on information provided or inferred about the urgencies of the notifications. For example, the notification manager can access or infer the context of the user (e.g., the user's current location and focus of attention).
- Such sources of information can include the user's context profile, the user's online calendar, the time of day, events about the world, organization, system, and/or the user's activity.
- the notification can then determine through an analysis of the context and the urgency of the information which of the notifications should be conveyed to the user, via which of the sinks, and in which manner or modality provided by the sinks.
- a user may, for example, receive e-mail alerts on a cell phone, or voice-mail on a desktop computer, as is determined appropriate by the notification manager.
- notifications from notification sources are passed to the notification manager, which determines whether the user should be notified. If the manager determines that the user should be notified, then the manager also determines how the user should be notified. This can be based on the information stored in the user profile, including such information as the user's preferences and current context, and notifies the appropriate notification sinks.
- the sinks can include, for example, a desktop computer, a cell phone, a pager, etc.
- notification platform generalize to any notification, including those associated with the potential provision of a service by a software component in a desktop or mobile setting.
- notifications include:
- the invention includes computer-implemented methods, machine-readable media, computerized systems, and computers of varying scopes.
- Other aspects, embodiments and advantages of the invention, beyond those described here, will become apparent by reading the detailed description and with reference to the drawings.
- FIG. 1 is a diagram of an example computerized device in conjunction with which embodiments of the invention can be practiced;
- FIG. 2 is a diagram of a notification architecture according to an embodiment of the invention.
- FIG. 3 is a diagram illustrating the user mechanism of the architecture of FIG. 2 in more detail, in accordance with an embodiment of the invention
- FIG. 4 is a diagram of a graph showing an example decay of the utility of information contained within a notification over time, according to an embodiment of the invention.
- FIG. 5 is a flowchart of a method according to an embodiment of the invention.
- FIG. 1 a diagram of an example computerized device 100 in conjunction with which embodiments of the invention may be practiced is shown.
- the example computerized device can be, for example, a desktop computer, a laptop computer, a personal digital assistant (PDA), a cell phone, etc.; the invention is not so limited.
- the description of FIG. 1 is intended to provide a brief, general description of a suitable computerized device in conjunction with which the invention may be implemented.
- Those skilled in the art will appreciate that the invention may be practiced with other computer system configurations, including hand-held devices, multiprocessor systems, microprocessor-based or programmable consumer electronics, network PC's, minicomputers, mainframe computers, and the like.
- the invention may also be practiced in distributed computing environments where tasks are performed by remote processing devices that are linked through a communications network.
- the device 100 includes one or more of the following components: processor(s) 102 , memory 104 , storage 106 , a communications component 108 , input device(s) 110 , a display 112 , and output device(s) 114 . It is noted, that for a particular instantiation of the device 100 , one or more of these components may not be present. For example, a PDA may not have any output device(s) 114 , while a cell phone may not have storage 106 , etc. Thus, the description of the device 100 is to be used as an overview as to the types of components that typically reside within such a device 100 , and is not meant as a limiting or exhaustive description of such computerized devices.
- the processor(s) 102 may include a single central-processing unit (CPU), or a plurality of processing units, commonly referred to as a parallel processing environment.
- the memory 104 may include read only memory (ROM) 24 and/or random access memory (RAM) 25 .
- the storage 106 may be any type of storage, such as fixed-media storage devices such as hard disk drives, flash or other non-volatile memory, as well as removable-media storage devices, such as tape drives, optical drives like CD-ROM's, floppy disk drives, etc.
- the storage and their associated computer-readable media provide non-volatile storage of computer-readable instructions, data structures, program modules, and other data.
- a communications component 108 can be present in or attached to the device 100 .
- a component 108 may be one or more of a network card, such as an Ethernet card, an analog modem, a cable modem, a digital subscriber loop (DSL) modem, an Integrated Services Digital Network (ISDN) adapter, etc.; the invention is not so limited.
- the input device(s) 110 are the mechanisms by which a user indicates input to the device 100 .
- Such device(s) 110 include keyboards, pointing devices, microphones, joysticks, game pads, satellite dishes, scanners, etc.
- the display 112 is how the device 100 typically shows output to the user, and can include, for example, cathode-ray tube (CRT) display devices, flat-panel display (FPD) display devices, etc.
- the device 100 may indicate output to the user via other output device(s) 114 , such as speakers, printers, etc.
- the architecture 200 of FIG. 2 includes a user mechanism 202 , a notification manager 204 (also referred to as an event broker), a number of notification sources 206 a , 206 b , . . . , 206 n , and a number of notification sinks 208 a , 208 b , . . . , 208 m .
- the sources are also referred to as event publishers, while the sinks are also referred to as event subscribers. There can be any number of sinks and sources.
- the notification manager 204 conveys notifications, which are also referred to as events or alerts, from the sources 206 to the sinks 208 , based on information stored in the user mechanism 202 .
- notifications which are also referred to as events or alerts
- the sources 206 to the sinks 208 , based on information stored in the user mechanism 202 .
- the user mechanism 202 stores information regarding variables and parameters of a user that influence notification decision-making.
- the parameters may include contextual information, such as the user's typical locations and attentional focus or activities per the time of day and the day of the week, and additional parameters conditioned on such parameters, such as the devices users tend to have in different locations.
- Such parameters may also be functions of observations made autonomously via one or more sensors.
- profiles may be selected or modified based on information about a user's location as might be provided by a global positioning system (GPS) subsystem, on information about the type of device being used and/or the pattern of usage of the device, the last time a device of a particular type was accessed by the user, etc.
- GPS global positioning system
- automated inference may also be employed, to dynamically infer parameters such as location and attention.
- the profile parameters may be stored as a user profile that can be edited by the user.
- the notification architecture can also allow users to specify in real-time his or her state, such as the user not being available except for important notifications for the next x hours, or until a given time.
- the parameters can also include default notification preference parameters regarding a user's preference as to being disturbed by notifications of different kinds in different settings, which can be used as the basis from which to make notification decisions by the notification manager 204 , and to the basis upon which a particular user can make changes.
- the parameters may include default parameters as to how the user wishes to be notified in different situations, such as by cell phone, by pager, etc.
- the parameters can include such assessments as the costs of disruption associated with being alerted by different modes in different settings.
- the parameters can include contextual parameters indicating the likelihoods that the user is in different locations, the likelihoods that different devices are available, and the likelihoods of his or her attentional status at a given time, as well as notification parameters indicating how the user desires to be notified at a given time.
- the information stored by the user mechanism 202 is in one embodiment inclusive of contextual information determined by the mechanism 202 .
- the contextual information is determined by the mechanism 202 by discerning the user's location and attentional status based on one or more contextual information sources, as is described in more detail in a later section of the detailed description.
- the mechanism 202 may be able to determine with precision the actual location of the user via a global positioning system (GPS) that is a part of a user's car, cell phone, etc.
- GPS global positioning system
- the mechanism 202 may also use a statistical model to determine the likelihood that the user is in a given state of attention by considering background assessments and/or observations gathered through considering such information as the type of day, the time of day, the data in the user's calendar, and observations about the user's activity. This is described in more detailed in the cofiled, copending and coassigned patent application entitled “Contextual Models and Methods for Inferring Attention and Location.” Ser. No. 09/596,364
- the given state of attention can include whether the user is open to receiving notification, busy and not open to receiving notification, etc.
- the type of day can include weekdays, weekends, holidays, etc.
- Each of the sources 206 a , 206 b , . . . , 206 n is able to generate notifications intended for the user.
- the sources 206 may include communications, such as Internet and network-based communications, local desktop computer-based communications, and telephony communications, as well as software services, such as intelligent help, background queries, automated scheduling, etc.
- a notification source is defined generally herein as that which generates events, which can also be referred to as notifications and alerts, intended to alert a user, or a proxy for the user, about information, services, or a system or world event.
- a notification source can also be referred to as an event source.
- e-mail may be generated as notifications by an e-mail notification source such that it is prioritized, where the host application program generating the notification assigns the e-mail with a relative priority corresponding to the likely importance or urgency of the e-mail to the user.
- the e-mail may also be sent without regard to their relative importance to the user.
- Desktop-centric notifications can include an automated dialog with the goal of alerting a user to a potentially valuable service that he or she may wish to execute (e.g., scheduling from a message), information that the user may wish to review (e.g., derived from a background query), or errors and other alerts generated by a desktop computer.
- Internet-related services can include notifications including information that the user has subscribed to, such as headlines of current news every so often, stock quotes, etc.
- Notification sources 206 can themselves be push-type or pull-type sources.
- Push-type sources are those that automatically generate and send information without a corresponding request, such as headline news and other Internet-related services that send information automatically once subscribed to.
- Pull-type sources are those that send information in response to a request, such as e-mail being received after a mail server is polled.
- Still other notification sources include the following:
- Each of the notification sinks 208 a , 208 b , . . . , 208 n is able to provide the notifications to the user.
- such notification sinks 208 can include computers, such as desktop and/or laptop computers, handheld computers, cell phones, landline phones, pagers, automotive-based computers, etc. It is noted that some of the sinks 208 can convey notifications more richly than other of the sinks 208 .
- a desktop computer typically has speakers and a relatively large color display attached to it, as well as having a high bandwidth for receiving information when attached to a local network or to the Internet. Therefore, notifications can be conveyed by the desktop computer to the user in a relatively rich manner.
- a notification sink can in one embodiment refer to that which subscribes, via an event subscription service, to events or notifications.
- the notification manager 204 accesses the information stored by the user mechanism 202 , and makes a decision as to which of the notifications it receives from the sources 206 to convey to which of the sinks 208 based on this information. Furthermore, the manager 204 is able to determine how the notification is to be conveyed, depending on which of the sinks 208 it has selected to send the information to. For example, it may determine that the notification should be summarized before being provided to a given of the sinks 208 .
- the manager 204 is in one embodiment a computer program executed by a processor of a computer from a machine-readable medium such as a memory thereof.
- the invention is not limited to how the manager 204 makes its decisions as to which of the notifications to convey to which of the notification sinks, and in what manner the notifications are conveyed.
- a decision-theoretic analysis can be made.
- the notification manager can be designed to infer important uncertainties about variables including a user's location, attention, device availability, and amount of time until the user will access the information if there were no alert.
- the notification manager can then make notification decisions about whether to alert a user to a notification, and if so, the nature of the summarization and the best device or devices to employ for relaying the notification.
- Such a particular embodiment is described in the cofiled, copending and coassigned case entitled “Decision-Theoretic Principles and Policies for Notification.” Ser. No. 09/596,348
- the manager 204 determines the net expected value of a notification. In doing so, it can consider the following:
- the inferences made about uncertainties thus may be generated as expected likelihoods of values such as the cost of disruption to the user with the use of a particular mode of a particular device given some attentional state of the user, etc.
- the notification manager 204 makes decisions as to one or more of the following:
- inference refers generally to the process of reasoning about or inferring states of the system, environment, or user from a set of observations as captured via events and/or data. Inference can be used to identify a specific context or action, or can be employed to generate a probability distribution over states. The inference can be probabilistic—that is, the computation of a probability distribution over states of interest based on a consideration of data and events. Inference can also refer to techniques used for composing higher-level events from a set of events and/or data. Such inference results in the construction of new events or actions from a set of observed events and/or stored event data, whether or not the events are correlated in close temporal proximity, and whether the events and data come from one or several event and data sources.
- the notification manager 204 accesses information stored in a user profile by the user mechanism 202 in lieu of or to support a personalized decision-theoretic analysis.
- the user profile may indicate that at a given time, the user prefers to be notified via a pager, and only if the notification has a predetermined importance level.
- Such information can be used as a baseline from which to start a decision-theoretic analysis, or can be the only manner by which the manager 204 determines how and whether to notify the user.
- the notification platform architecture is constructed as a layer that resides over an eventing or messaging infrastructure.
- eventing and messaging systems and protocols include:
- the user mechanism 202 the notification sources 206 , and the notification sinks 208 are each described in more detail, according to varying embodiments of the invention. Thereafter, a method of the manner by which the architecture operates according to an embodiment of the invention is presented.
- FIG. 3 is a diagram 300 showing the user mechanism 202 of FIG. 2 in more detail.
- the user mechanism 202 as shown in FIG. 3 includes a user notification preferences store 302 , a user context module 304 that includes a user context profile store 305 , and a whiteboard 307 .
- the user mechanism 202 is in one embodiment implemented as one or more computer programs executable by a processor of a computer from a machine-readable medium thereof, such as a memory.
- the store 302 stores notification parameters for a user, such as the default notification preferences for the user, as a user profile, which can then be edited and modified by the user.
- the store 302 can be considered as that which stores information on parameters that influence how a user is to be notified.
- the user context module 304 determines a user's current context, based on the context information sources 306 as published to the whiteboard 307 ; the user context profile store 305 stores the context parameters for a user, such as the default context settings for the user, which can be edited and modified by the user. That is, the user context module 304 provides a best guess about current context information by accessing information from the store 305 and/or updating the prior set of beliefs in the store 305 with live sensing, via one or more context sources 306 .
- the store 305 can be considered as that which stores a priori where a user is, and what the user is doing.
- the module 304 is in one embodiment implemented as a computer program executable by a processor of a computer from a machine-readable medium thereof, such as a memory.
- the user context profile store 305 is a pre-assessed or predefined user profile that captures such information as a deterministic or probabilistic profile.
- the profile can be of typical locations, activities, device availabilities, and costs and values of different classes of notification as a function of such observations as time of day, type of day, and user interactions with one or more devices.
- the type of day can include weekdays, weekends, holidays, etc.
- the user context module 304 can then actively determine or infer key aspects of the context of the user, such as the user's current or future location and attentional state.
- the actual states of context can be accessed directly from the sources 306 via the whiteboard 307 , or, can be inferred from a variety of such observations through inferential methods such as Bayesian reasoning as known within the art.
- the context information sources 306 provide information to the module 304 via the whiteboard 307 regarding the user's attentional state and location, from which the module 304 can make a determination as to the user's current context (that is, the user's current attentional state and location). Furthermore, the invention is not limited to a particular number or type of context sources 306 , nor the type of information inferred or accessed by the user context module. However, in one embodiment, the context sources 306 include multiple desktop information and events, such as mouse information, keyboard information, application information (e.g., which application is currently receiving the focus of the user), ambient sound and utterance information, text information in the windows on the desktop, etc.
- the whiteboard 307 is in one embodiment a common storage area, to which the context information sources 306 can publish information, and from which multiple components, including sources and the module 304 can access this information; it is not necessary for implementation of the invention, however.
- An event also referred to as a notification or alert, can in one embodiment generally include information about an observation about one or more states of the world. Such states can include the status of system components, the activity of a user, or a measurement about the environment. Furthermore, events can be generated by an active polling of a measuring device or source of events, by the receipt of information that is sent on a change, or per a constant or varying event heartbeat.
- context sources 306 include personal-information manager (PIM) information of the user, which usually can provide scheduling information regarding the schedule of the user, etc.
- PIM personal-information manager
- GPS global positioning system
- real-time mobile device usage is a type of context source 306 .
- a mobile device such as a cell phone may be able to determine if it is currently being used by the user, as well as its orientation and tilt (indicating information regarding its usage as well), and acceleration and speed (indicating information as to whether the user is moving or not).
- the notification sources 206 of the architecture 200 of FIG. 2 are described in more detail.
- the notification sources generally generate notifications that are conveyed to the notification manager, which determines when notifications should occur, and, if so, which of the notifications should be conveyed to which of the notification sinks and in what order, as has also been already described.
- each notification source has identified with it one or more of the following parameters within a standard description of key attributes and relationships, referred to herein as a notification source schema or source schema.
- schema are provided for sources, for sinks, and for context-information sources.
- Such schemas provide declarative information about different component and provide a mechanism for the sources, the notification manager, the sinks, and the user mechanism (including the context mechanism described in the previous section of the detailed description) to share semantic information with one another.
- different schemas provide information about the nature, urgency, and device signaling modalities associated with notification.
- schema can be defined generally as a collection of classes and relationships among classes that defines the structure of notifications and events, containing information including event or notification class, source, target, event or notification semantics, ontological content information, observational reliability, and any quality-of-service attributes.
- the parameters for each notification source schema include one or more of: message class; relevance; importance; time criticality; novelty; content attributes; and fidelity tradeoffs, and source information summary information.
- the message class for a notification generated by a notification source indicates the type of communication of the notification, such as e-mail, instant message, numerical financial update, desktop service, etc.
- the relevance for a notification generated by a notification sources indicates a likelihood that the information contained within the notification is relevant, for one or more specified contexts. In one embodiment, the relevance is a logical flag, indicating whether the source is relevant for a given context or not.
- the novelty of the notification indicates the likelihood that the user already knows the information contained within the notification. That is, the novelty is whether the information is new to the user, over time (indicating if the user knows the information now, and when, if ever, the user will learn the information in the future without being alerted to it).
- Fidelity tradeoffs associated with the notification indicate the loss of value of the information within the notification that can result from different forms of specified allowed truncation, summarization, etc. Such truncation and/or summarization may be required for the notification to be conveyed to certain types of notification sinks that may have bandwidth or other limitations preventing them from receiving the full notification as originally generated. Fidelity in general refers to the nature and/or degree of completeness of the original content associated with a notification. For example, a long e-mail message may be truncated, or otherwise summarized to the maximum of 100 characters allowed by a cell phone, incurring a loss of fidelity.
- Fidelity tradeoffs refer to a set of fidelity preferences of a source stated either in terms of orderings (e.g., rendering importance in order of graphics first, then sound) and/or costs functions that indicate how the total value of the content of the notification diminishes with changes in fidelity.
- orderings e.g., rendering importance in order of graphics first, then sound
- costs functions that indicate how the total value of the content of the notification diminishes with changes in fidelity.
- a fidelity tradeoff might describe how the full value associated with the transmission of a complete e-mail message changes with increasingly greater amounts of truncation.
- Content attributes contain a summary of the nature of the content, representing such information as whether the core message includes text, graphics, and audio components. The content itself is the actual graphics, text, and/or audio that make up the message content of the notification.
- the importance of a notification refers to the value of the information contained in the notification to the user, assuming the information is relevant in the current context. In one embodiment, it is expressed as a dollar value of the information's worth to the user.
- Time criticality indicates the time-dependent change in the value of the information contained in the notification—that is, how the value of the information changes over time. In most but not all cases, the value of the information of a notification decays with time. This is particularly shown in the diagram 400 of FIG. 4 .
- the graph 402 shows the utility of a notification mapped over time. At the point 404 within the graph, representing the initial time, the importance of the notification is indicated, while the curve 406 indicates the decay of the utility over time.
- Source summary information allows a source to post general summaries of the status of information and potential notifications available from a source.
- source summary information from a messaging source might include information about the total number of unread messages that are at least some priority, the status of attempts by people to communicate with a user, etc.
- the notification sinks 208 of the architecture 200 of FIG. 2 are described in more detail.
- the notification sinks are devices, etc., by which the user can be notified of information contained in notifications.
- the choice as to which sink or sinks are to be used to convey a particular notification is determined by the notification manager.
- each notification sink has identified with it one or more of the following parameters within a schema: device class; modes of signaling (alerting); and, for each mode, fidelity/rendering capabilities, transmission reliability, actual cost of communication, and attentional cost of disruption.
- the schema for the devices can additionally include a description of the alerting attributes and parameters for controlling the attributes, and functions by which other attributes (e.g., transmission reliability, cost of distribution, etc.) change with the different settings of the alerting attributes.
- the schema for notification sinks provides for the manner by which the notification devices communicate semantic information about their nature and capabilities with the notification manager and other components of the system.
- Default attributes and schema templates for different device types can be made available in device profiles stored in the user notification preferences store, such as the store 302 of FIG. 3 as described in the previous section. Such default templates can be directed to overrule values provided by devices or to provide attributes when they are missing from schema provided by devices.
- the class of the device refers to the type of the device: a cell phone, a desktop computer, a laptop computer, etc.
- the class can also be more general, such as a mobile device, a stationery device, etc.
- the modes of signaling refer to the different ways in which a given device can alert the user about a notification.
- Devices may have one or more notification modes. For example, a cell phone can only vibrate, only ring with some volume, or it can both vibrate and ring.
- a desktop display for an alerting system can in one embodiment be decomposed into several discrete modes (e.g., a small notification window in the upper right hand of the display vs.
- a device can allow for modes with alerting attributes that are functions of parameters, as part of its definition.
- alerting attributes that are functions of parameters, as part of its definition.
- Such continuous alerting parameters for a mode represent such controls as the volume at which an alert is played at the desktop, rings on a cell phone, the size of an alerting window, etc.
- the transmission reliability for a mode of a notification sink indicates the likelihood that the user will receive the communicated alert about a notification, which is conveyed to the user via the sink with that mode.
- transmission reliability may be dependent on the device availability and context of the user, the transmission reliability of different modes of a device can be conditioned on such contextual attributes as the location and attention of a user.
- Transmission reliability for each of one or more unique contextual states defined by the cross product of such attributes as unique locations and unique attentional states, defined as disjunctions created as abstractions of such attributes (e.g., for any location away from the home, and any time period after 8 am and before noon), can also be specified.
- Contexts can also influence transmission reliability because of the ambient noise or other masking or distracting properties of the context.
- the actual cost of communication indicates the actual cost of communicating the information to the user when contained within a notification that is conveyed to the sink. For example, this cost can include the fees associated with a cell phone transmission.
- the cost of disruption includes the attentional costs associated with the disruption associated with the alert employed by the particular mode of a device, in a particular context. Attentional costs are typically sensitive to the specific focus of attention of the user.
- the fidelity/rendering capability is a description of the text, graphics, and audio/tactile capabilities of a device, also given a mode. For example, a cell phone's text limit may be 100 characters for any single message, and the phone may have no graphics abilities.
- a computer-implemented method is desirably realized at least in part as one or more programs running on a computer—that is, as a program executed from a computer-readable medium such as a memory by a processor of a computer.
- the programs are desirably storable on a machine-readable medium such as a floppy disk or a CD-ROM, for distribution and installation and execution on another computer.
- the program or programs can be a part of a computer system or a computer, such as that described in conjunction with FIG. 1 in a previous section of the detailed description. The invention is not so limited, however.
- the method 500 can be executed by the notification architecture 200 of FIG. 2 , which has been already described.
- one or more notification sources generate notifications, which are received by a notification manager.
- the user mechanism generates context information regarding the user, which in 506 is received by the notification manager. That is, in one embodiment, in 504 , the user mechanism accesses a user contextual information profile that indicates the user's current attentional status and location, and/or assesses real-time information regarding the user's current attentional status and location from one or more contextual information sources, as has been described in the previous sections of the detailed description.
- the notification manager determines which of the notifications to convey to which of the notification sinks, based in part on the context information received from the user mechanism.
- the notification also makes it determination based on information regarding notification parameters of the user as stored by the user mechanism, in one embodiment. That is, in one embodiment, in 508 , the manager performs a decision-theoretic analysis as to whether a user should be alerted for a given notification, and how the user should be notified.
- Notification parameters regarding the user can be utilized to personalize the analysis by filling in missing values or by overwriting parameters provided in the schema of sources or sinks. Notification preferences can also provide policies that are employed in lieu of the decision-theoretic analysis, as has been described in the previous sections of the detailed description. Based on this determination, the notification manager conveys the notifications to the sinks in 510 .
- Embodiments of the invention have been described herein thus far as applicable to users.
- the invention itself is not so limited. That is, the invention is applicable to any type of entity, including users.
- Other types of entities include agents, processes, computer programs, threads, services, servers, computers, machines, companies, organizations, businesses, etc.
- the agent for example, may be a software agent, which can be generally defined as a computer program that performs a background task for a user and reports to the user when the task is done or some expected event has taken place. Still other types of entities are encompassed under the invention, as can be appreciated by those of ordinary skill within the art.
- the invention itself is applicable to any type of entity.
- the user mechanism of a system according to an embodiment of the invention can be generalized as a mechanism, applicable to any type of entity.
- notification sinks can generate notifications, alerts and events regarding and for entities other than users.
- notification sinks can receive notifications, alerts and events regarding and for entities other than users.
Abstract
Description
-
- alerts about services such as those that seek to automatically provide assistance or tips to a user working with a software application and/or automatically perform scheduling by examining e-mail at the focus of a user's attention;
- alerts that notify the user to upcoming appointments or engagements;
- alerts that relay important changes in the location, proximity, or attentional status of friends and colleagues; and,
- alerts that issue background queries based on text being composed or reviewed by users and present the results of such background searches to the user.
-
- e-mail desktop applications such as calendar systems;
- computer systems (e.g., that may alert the user with messages that information about alerts about system activity or problems);
- Internet-related services, appointment information, scheduling queries;
- changes in documents or numbers of certain kinds of documents in one or more shared folders;
- availability of new documents in response to standing or persistent queries for information; and,
- information sources for information about people and their presence, their change in location, their proximity (e.g., let me know when I am traveling if another employee of Microsoft is within 10 miles of me”), or their availability (e.g., let me know when Steve is available for a conversation and is near a high-speed link that can support full video teleconferencing”).
-
- the fidelity and transmission reliability of each available notification sink;
- the attentional cost of disturbing the user;
- the novelty of the information to the user;
- the time until the user will review the information on his or her own;
- the potentially context-sensitive value of the information; and,
- the increasing and/or decreasing value over time of the information contained within the notification.
-
- what the user is currently attending to and doing (based on, for example, contextual information);
- where the user currently is;
- how important the information is;
- what is the cost of deferring the notification;
- how distracting would a notification be;
- what is the likelihood of getting through to the user; and,
- what is the fidelity loss associated with the use of a specific mode of a given notification sink.
Therefore, ultimately, the notification manager 204 performs an analysis, such as a decision-theoretic analysis, of pending and active notifications, evaluates context-dependent variables provided by information sinks and sources, and infers key uncertainties, such as the time until a user is likely to review provided information and the user's location and current attentional state.
-
- HyperText Transport Protocol (HTTP), or HTTP extensions as known within the art;
- Simple Object Access Protocol (SOAP), as known within the art;
- Windows Management Instrumentation (WMI), as known within the art;
- Jini, as known within the art; and,
- any type of communications protocols, such as those based on packet-switching protocols, etc.
Furthermore, in one embodiment, the architecture is constructed as a layer that resides over a flexible distributed computational infrastructure, as can be appreciated by those of ordinary skill within the art. Thus, the notification platform architecture can utilize an underlying infrastructure as a manner by which sources send notifications, alerts and events, as a manner by which sinks receive notifications, alerts and events, etc. The invention is not so limited, however.
Claims (28)
Priority Applications (24)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US09/596,365 US7249159B1 (en) | 2000-03-16 | 2000-06-17 | Notification platform architecture |
KR1020027010700A KR100938518B1 (en) | 2000-03-16 | 2001-03-16 | Notification platform architecture |
EP07013320A EP1852789A1 (en) | 2000-03-16 | 2001-03-16 | Priorities generation and management |
DE60129434T DE60129434T2 (en) | 2000-03-16 | 2001-03-16 | GENERATION AND MANAGEMENT OF PRIORITIES |
PCT/US2001/008711 WO2001069387A2 (en) | 2000-03-16 | 2001-03-16 | Notification platform architecture |
US10/220,419 US7243130B2 (en) | 2000-03-16 | 2001-03-16 | Notification platform architecture |
PCT/US2001/008710 WO2001069432A2 (en) | 2000-03-16 | 2001-03-16 | Priorities generation and management |
EP01920508A EP1287444B1 (en) | 2000-03-16 | 2001-03-16 | Priorities generation and management |
CN2004100797636A CN1591398B (en) | 2000-03-16 | 2001-03-16 | Notification platform architecture |
JP2001567443A JP5192624B2 (en) | 2000-03-16 | 2001-03-16 | Priority generation and management |
AU2001249261A AU2001249261A1 (en) | 2000-03-16 | 2001-03-16 | Notification platform architecture |
KR1020087012535A KR20080056320A (en) | 2000-03-16 | 2001-03-16 | Priorities generation and management |
KR1020097015992A KR101143167B1 (en) | 2000-03-16 | 2001-03-16 | Priorities generation and management |
CN2004100797689A CN1734440B (en) | 2000-03-16 | 2001-03-16 | Notification platform architecture |
CN2004100797725A CN1591399B (en) | 2000-03-16 | 2001-03-16 | Notification platform architecture |
AT01920508T ATE367611T1 (en) | 2000-03-16 | 2001-03-16 | GENERATION AND MANAGEMENT OF PRIORITIES |
KR1020027010701A KR100869624B1 (en) | 2000-03-16 | 2001-03-16 | Priorities generation and management |
CNB018095135A CN1221912C (en) | 2000-03-16 | 2001-03-16 | Priorities generation and management |
AU2001247555A AU2001247555A1 (en) | 2000-03-16 | 2001-03-16 | Priorities generation and management |
EP01922463A EP1264238A2 (en) | 2000-03-16 | 2001-03-16 | Notification platform architecture |
JP2001568198A JP5243679B2 (en) | 2000-03-16 | 2001-03-16 | Notification platform architecture |
CN01809514A CN100594701C (en) | 2000-03-16 | 2001-03-16 | Notification system |
JP2011251641A JP2012084160A (en) | 2000-03-16 | 2011-11-17 | Notification platform architecture |
JP2011251640A JP2012074061A (en) | 2000-03-16 | 2011-11-17 | Notification platform architecture |
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US18980100P | 2000-03-16 | 2000-03-16 | |
US09/596,365 US7249159B1 (en) | 2000-03-16 | 2000-06-17 | Notification platform architecture |
Publications (1)
Publication Number | Publication Date |
---|---|
US7249159B1 true US7249159B1 (en) | 2007-07-24 |
Family
ID=38266969
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US09/596,365 Expired - Fee Related US7249159B1 (en) | 2000-03-16 | 2000-06-17 | Notification platform architecture |
Country Status (1)
Country | Link |
---|---|
US (1) | US7249159B1 (en) |
Cited By (39)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20020054117A1 (en) * | 2000-03-16 | 2002-05-09 | Van Dantzich Maarten R. | Scope user interface for displaying the priorities and properties of multiple informational items |
US20020133564A1 (en) * | 2001-03-13 | 2002-09-19 | Norihisa Takayama | Apparatus for sending/receiving data and computer program therefor |
US20030093327A1 (en) * | 2001-11-13 | 2003-05-15 | Bellsouth Intellectual Property Corporation | Systems and methods for processing an electronic request to purchase goods or services |
US20040143795A1 (en) * | 2002-10-25 | 2004-07-22 | Takaya Matsuishi | Display data creating technique for automatically Providing efficient representation of portal pages with improved visual recognition |
US20040254998A1 (en) * | 2000-06-17 | 2004-12-16 | Microsoft Corporation | When-free messaging |
US20050102235A1 (en) * | 2001-01-10 | 2005-05-12 | Michael Waidner | Method and system for processing of documents with electronic signatures |
US20050278366A1 (en) * | 2001-03-14 | 2005-12-15 | Microsoft Corporation | Schemas for a notification platform and related information services |
US20060004575A1 (en) * | 2000-12-08 | 2006-01-05 | At&T Corp. | Method and apparatus for creation and user-customization of speech-enabled services |
US20060195583A1 (en) * | 2003-02-27 | 2006-08-31 | Fabio Bellifemine | Method and system for providing information services to a client using a user profile |
US20070011314A1 (en) * | 2000-03-16 | 2007-01-11 | Microsoft Corporation | Notification platform architecture |
US20070015520A1 (en) * | 2005-07-12 | 2007-01-18 | Qwest Communications International Inc. | Efficiently determining the location of a mobile communications device system and methods |
US20070015521A1 (en) * | 2005-07-12 | 2007-01-18 | Qwest Communications International Inc. | Correlating activities with the location of a mobile communications device systems and methods |
US20070191023A1 (en) * | 2006-02-13 | 2007-08-16 | Sbc Knowledge Ventures Lp | Method and apparatus for synthesizing presence information |
US20080126282A1 (en) * | 2005-10-28 | 2008-05-29 | Microsoft Corporation | Multi-modal device power/mode management |
US20080189376A1 (en) * | 2001-06-12 | 2008-08-07 | Verizon Business Network Services Inc. | Automated message handling system and process |
US20090327169A1 (en) * | 2008-06-27 | 2009-12-31 | Microsoft Corporation | Combining predictive models of forgetting, relevance, and cost of interruption to guide automated reminding |
US20100088364A1 (en) * | 2008-10-08 | 2010-04-08 | International Business Machines Corporation | Social networking architecture in which profile data hosting is provided by the profile owner |
EP2224682A1 (en) | 2009-02-27 | 2010-09-01 | Research In Motion Limited | Communications system providing mobile device notification content type selection features and related method |
US20100222027A1 (en) * | 2009-02-27 | 2010-09-02 | Research In Motion Limited | Communications system providing mobile device notification content type selection features and related methods |
US7873742B1 (en) * | 2003-11-20 | 2011-01-18 | Microsoft Corporation | Providing content per delivery endpoint |
US7899469B2 (en) * | 2005-07-12 | 2011-03-01 | Qwest Communications International, Inc. | User defined location based notification for a mobile communications device systems and methods |
US20110060803A1 (en) * | 2009-04-23 | 2011-03-10 | Microsoft Corporation | Message Notification Campaigns |
US20110061091A1 (en) * | 2009-09-10 | 2011-03-10 | Motorola, Inc. | Method and System for Intermediating Content Provider Website and Mobile Device |
US20110128144A1 (en) * | 2009-11-30 | 2011-06-02 | Baron Services, Inc. | System and method of providing real-time site specific information |
EP2357766A1 (en) * | 2010-02-17 | 2011-08-17 | Cellco Partnership D/B/A Verizon Wireless | Business hour notification delivery |
US20120158866A1 (en) * | 2010-12-20 | 2012-06-21 | Motorola-Mobility, Inc. | Method and System for Facilitating Interaction with Multiple Content Provider Websites |
US8566413B2 (en) | 2000-03-16 | 2013-10-22 | Microsoft Corporation | Bounded-deferral policies for guiding the timing of alerting, interaction and communications using local sensory information |
US8572576B2 (en) | 2001-03-14 | 2013-10-29 | Microsoft Corporation | Executing dynamically assigned functions while providing services |
US8599013B1 (en) | 2005-09-29 | 2013-12-03 | Baron Services, Inc. | System and method for providing environmental information to a wireless transmitter coverage area |
US8700781B2 (en) | 2001-06-12 | 2014-04-15 | Verizon Business Global Llc | Automated processing of service requests using structured messaging protocols |
US8738723B1 (en) * | 2013-12-10 | 2014-05-27 | Google Inc. | Predictive forwarding of notification data |
US8816876B2 (en) * | 2005-09-29 | 2014-08-26 | Baron Services, Inc. | System for providing environmental condition information to vehicles and related methods |
US8990338B2 (en) | 2009-09-10 | 2015-03-24 | Google Technology Holdings LLC | Method of exchanging photos with interface content provider website |
US9386102B2 (en) | 2010-11-04 | 2016-07-05 | Panasonic Intellectual Property Corporation Of America | Gateway apparatus, communication apparatus, apparatus co-operation network system, and apparatus co-operation method |
US9503409B2 (en) | 2013-02-25 | 2016-11-22 | Google Inc. | Suppression of extraneous alerts on multiple devices |
US9872087B2 (en) | 2010-10-19 | 2018-01-16 | Welch Allyn, Inc. | Platform for patient monitoring |
US9886309B2 (en) | 2002-06-28 | 2018-02-06 | Microsoft Technology Licensing, Llc | Identity-based distributed computing for device resources |
US10621602B2 (en) | 2015-09-22 | 2020-04-14 | Adobe Inc. | Reinforcement machine learning for personalized intelligent alerting |
US11272330B1 (en) * | 2020-12-04 | 2022-03-08 | Capital One Services, Llc | Methods and systems for facilitating digital notifications in mobile communication networks |
Citations (17)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
WO1998000787A1 (en) | 1996-06-28 | 1998-01-08 | Datalink Systems Corporation | Electronic mail system for receiving and forwarding e-mail messages based on subscriber supplied criteria |
US5742905A (en) * | 1994-09-19 | 1998-04-21 | Bell Communications Research, Inc. | Personal communications internetworking |
US5864848A (en) | 1997-01-31 | 1999-01-26 | Microsoft Corporation | Goal-driven information interpretation and extraction system |
US6021403A (en) | 1996-07-19 | 2000-02-01 | Microsoft Corporation | Intelligent user assistance facility |
US20020046299A1 (en) * | 2000-02-09 | 2002-04-18 | Internet2Anywhere, Ltd. | Method and system for location independent and platform independent network signaling and action initiating |
US20020078204A1 (en) | 1998-12-18 | 2002-06-20 | Dan Newell | Method and system for controlling presentation of information to a user based on the user's condition |
US20020080156A1 (en) | 1998-12-18 | 2002-06-27 | Abbott Kenneth H. | Supplying notifications related to supply and consumption of user context data |
US20020083158A1 (en) | 1998-12-18 | 2002-06-27 | Abbott Kenneth H. | Managing interactions between computer users' context models |
US6505167B1 (en) * | 1999-04-20 | 2003-01-07 | Microsoft Corp. | Systems and methods for directing automated services for messaging and scheduling |
US6571279B1 (en) * | 1997-12-05 | 2003-05-27 | Pinpoint Incorporated | Location enhanced information delivery system |
US20030154476A1 (en) | 1999-12-15 | 2003-08-14 | Abbott Kenneth H. | Storing and recalling information to augment human memories |
US6618716B1 (en) * | 1999-07-30 | 2003-09-09 | Microsoft Corporation | Computational architecture for managing the transmittal and rendering of information, alerts, and notifications |
US6622160B1 (en) * | 1999-07-30 | 2003-09-16 | Microsoft Corporation | Methods for routing items for communications based on a measure of criticality |
US6714967B1 (en) * | 1999-07-30 | 2004-03-30 | Microsoft Corporation | Integration of a computer-based message priority system with mobile electronic devices |
US20040193444A1 (en) * | 1999-12-28 | 2004-09-30 | Wendy Hufford | Computer system for managing litigation risk early warning system |
US20050013417A1 (en) * | 2000-02-11 | 2005-01-20 | Zimmers Steven L. | Alert notification system |
US6931434B1 (en) * | 1998-09-01 | 2005-08-16 | Bigfix, Inc. | Method and apparatus for remotely inspecting properties of communicating devices |
-
2000
- 2000-06-17 US US09/596,365 patent/US7249159B1/en not_active Expired - Fee Related
Patent Citations (19)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US5742905A (en) * | 1994-09-19 | 1998-04-21 | Bell Communications Research, Inc. | Personal communications internetworking |
WO1998000787A1 (en) | 1996-06-28 | 1998-01-08 | Datalink Systems Corporation | Electronic mail system for receiving and forwarding e-mail messages based on subscriber supplied criteria |
US6021403A (en) | 1996-07-19 | 2000-02-01 | Microsoft Corporation | Intelligent user assistance facility |
US5864848A (en) | 1997-01-31 | 1999-01-26 | Microsoft Corporation | Goal-driven information interpretation and extraction system |
US6571279B1 (en) * | 1997-12-05 | 2003-05-27 | Pinpoint Incorporated | Location enhanced information delivery system |
US6931434B1 (en) * | 1998-09-01 | 2005-08-16 | Bigfix, Inc. | Method and apparatus for remotely inspecting properties of communicating devices |
US20020080156A1 (en) | 1998-12-18 | 2002-06-27 | Abbott Kenneth H. | Supplying notifications related to supply and consumption of user context data |
US20020083158A1 (en) | 1998-12-18 | 2002-06-27 | Abbott Kenneth H. | Managing interactions between computer users' context models |
US20020099817A1 (en) | 1998-12-18 | 2002-07-25 | Abbott Kenneth H. | Managing interactions between computer users' context models |
US6466232B1 (en) * | 1998-12-18 | 2002-10-15 | Tangis Corporation | Method and system for controlling presentation of information to a user based on the user's condition |
US20020078204A1 (en) | 1998-12-18 | 2002-06-20 | Dan Newell | Method and system for controlling presentation of information to a user based on the user's condition |
US6505167B1 (en) * | 1999-04-20 | 2003-01-07 | Microsoft Corp. | Systems and methods for directing automated services for messaging and scheduling |
US6714967B1 (en) * | 1999-07-30 | 2004-03-30 | Microsoft Corporation | Integration of a computer-based message priority system with mobile electronic devices |
US6618716B1 (en) * | 1999-07-30 | 2003-09-09 | Microsoft Corporation | Computational architecture for managing the transmittal and rendering of information, alerts, and notifications |
US6622160B1 (en) * | 1999-07-30 | 2003-09-16 | Microsoft Corporation | Methods for routing items for communications based on a measure of criticality |
US20030154476A1 (en) | 1999-12-15 | 2003-08-14 | Abbott Kenneth H. | Storing and recalling information to augment human memories |
US20040193444A1 (en) * | 1999-12-28 | 2004-09-30 | Wendy Hufford | Computer system for managing litigation risk early warning system |
US20020046299A1 (en) * | 2000-02-09 | 2002-04-18 | Internet2Anywhere, Ltd. | Method and system for location independent and platform independent network signaling and action initiating |
US20050013417A1 (en) * | 2000-02-11 | 2005-01-20 | Zimmers Steven L. | Alert notification system |
Non-Patent Citations (54)
Title |
---|
Andy Harter, et al., A Distributed Location System for the Active Office, IEEE Network, 1994, pp. 62-70. |
Bill N. Schilit, et al., Customizing Mobile Applications, Proceedings USENIX Symposium on Mobile and Location Independent Computing, Aug. 1993, 9 pages. |
Bill N. Schilit, et al., Disseminationg Active Map Information to Mobile Hosts, IEEE Network, 1994, pp. 22-32, vol. 8 - No. 5. |
Bill N. Schilit, et al., The ParcTab Mobile Computing System, IEEE WWOS-IV, 1993, 4 pages. |
Bill Schilit, et al., Context-Aware Computing Applications, In Proceedings of the Workshop on Mobile Computing Systems and Applications, Dec. 1994. pp. 85-90. |
Birnbaum et al., Compelling Intelligent User Interfaces- How much AI?, pp. 173-175, ACM. * |
Bradley J. Rhodes, Remembrance Agent: A continuously running automated information retrieval system, The Proceedings of The First International Conference on The Practical Application Of Intelligent Agents and Multi Agent Technology, 1996, pp. 487-495. |
Bradley J. Rhodes, The Wearable Remembrance Agent: A System for Augmented Memory, Personal Technologies Journal Special Issue on Wearable Computing, 1997, 12 pages. |
Bradley J. Rhodes, The Wearable Remembrance Agent: A System for Augmented Theory, The Proceedings of The First International Symposium on Wearable Computers, Oct. 1997, pp. 123-128. |
Breese et al (1998) Empirical analysis of predictive algorithms for collaborative filtering, in Proceedings of the 14<SUP>th </SUP>conf on uncertainty in AI, pp. 43-52, AUAI, Morgan Kaufmann, San Francisco. |
Cohen, Learning Rules that Classify E-mail, 1996. * |
D. Koller er al, (1996), Toward optimal feature selection, in proceedings of 13<SUP>th </SUP>conference on machine learning, pp. 284-292, Morgan Kaufmann, San Francisco. |
E. Horvitz et al, (1998) The Lumiere project, Bayesian user modeling for inferring the goals and needs of software users, in proceedings of the 14<SUP>th </SUP>conf on uncertainty in AI, pp. 256-265, Morgan Kaufmann, San Francisco. |
Eric Horvitz, et al., Attention-Sensitive Alerting in Computing Systems, Microsoft Research, Aug. 1999. |
Eric Horvitz, et al., In Pursuit of Effective Handsfree Decision Support: Coupling Bayesian Inference, Speech Understanding, and User Models, 1995, 8 pages. |
Guanling Chen, et al., A Survey of Context-Aware Mobile Computing Research, Dartmouth Computer Science Technical Report, 2000, 16 pages. |
H. Lieberman (1995), Letizia, An agent that assists web browsing, in proceedings of IJCAI-95, Montreal Canada, Morgan Kaufmann, San Francisco. |
Helm, Improbable Inspiration, Oct. 1996, Los Angles Times. * |
Horvitz (1999), Principles of mixed-initiative user interfaces, in Proceedings of CHI'99, ACM SIGCHI Conf on Human Factors in Computing Systems, Pittsburgh, PA, 159-166, ACM. |
Horvitz et al, (1995) Display of information for time-critical decision making, in proceedings of the 11<SUP>th </SUP>conf on uncertainty in AI, pp. 296-305, Monetrea, Canada. |
Horvitz, Agents with Beliefs: Reflections on Bayesian Methods for User Modeling, Jun. 5, 1997, 6th International Conference on User Modeling. * |
Horvitz, Rutledge (1991), Time dependent utility and action under uncertainty, in proceedings of 7<SUP>th </SUP>conf on uncertainty in AI, LA, CA, pp. 151-158, Morgan Kaufmann, San Francisco. |
Horvitz, Seivier (1977), Time-critical action: representations and application, in proceedings of the 13<SUP>th </SUP>conf on uncertainty in AI (UAI-97), pp. 250-257, Providence, RI, Morgan Kaufmann, San Francisco. |
International Search Report dated Sep. 29, 2003 for PCT Application Ser. No. 00/20685, 3 pages. |
J. Platt (1999), Probabilistic outputs for support vector machines and comparisons to regularized likelihood methods, in Advances in Large Margin Classifiers, MIT Press, Cambridge, MA. |
M. Billinghurst, et al., An Evalution of Wearable Information Spaces, Proceedings of the Virtual Reality Annual International Symposium, 1998, 8 pages. |
M. Czerwinski et al (1999), Visualizing implicit queries for information management and retrieval, in proceedings of CHI'99, ACM SIGCHI Conf on informational and knowledge management, pp. 560-567, ACM. |
M. Sahami et al, (1998), A Bayesian approach to filtering junk email, in Workshop on learning for text categorizations, AAAI Technical Report WS-98-05, AAAI. |
Macskassy et al. EmailValet: Learning Email Preferences for Wireless Platforms, Jun. 3, 1999. * |
Macskassy et al. EmailValet: Learning User Preferences for Wieless Email, 1999. * |
Mark Billinghurst, et al., Wearable Devices: New Ways to Manage Information, IEEE Computer Society, Jan. 1999, pp. 57-64. |
Mark Billinghurst, Research Directions in Wearable Computing, University of Washington, May, 1998, 48 pages. |
Mark Weiser, Some Computer Science Issues in Ubiquitous Computing, Communications of the ACM, Jul. 1993, pp. 75-84, vol. 36 - No. 7. |
Mark Weiser, The Computer for the 21st Century, Scientific American, Sep. 1991, 8 pages. |
Marvin Theimer, et al., Operating System Issues for PDAs, In Fourth Workshop on Workstation Operating Systems, 1993, 7 pages. |
Mike Spreitzer, et al., Architectural Considerations for Scalable, Secure, Mobile Computing with Location Information, In The 14th International Conference on Distributed Computing Systems, Jun. 1994, pp. 29-38. |
Mike Spreitzer, et al., Providing Location Information in a Ubiquitous Computing Environment, SIGOPS '93, 1993, pp. 270-283. |
Mike Spreitzer, et al., Scalable, Secure, Mobile Computing with Location Information, Commmunications of the ACM, Jul. 1993, 1 page, vol. 36 - No. 7. |
Platt (1999), Fast training of support vector machines using sequential minimal optimization, in advances in kernel methods, support vector learning, MIT Press, Cambridge, MA. |
Robert M. Losee, Jr., Minimizing information overload: the ranking of electronic messages, Journal of Information Science 15, Elsevier Science Publishers B.V., 1989, pp. 179-189. |
Roy Want, Active Badges and Personal Interactive Computing Objects, IEEE Transactions on Consumer Electronics, 1992, 11 pages, vol. 38 - No. 1. |
Roy Want, et al., The Active Badge Location System, ACM Transactions on Information Systems, Jan. 1992, pp. 91-102, vol. 10 - No. 1. |
S. Dumais et al (1998), Inductive learning algorithms and representations for text categorization, in Proceedings of 7<SUP>th </SUP>Intl Conf on Information and Knowledge Management, pp. 148-155, ACM. |
T. Joachims, Text categorization with support vector machines: learning with many relevant features, Machine Learning, European Conference on Machine Learning, Apr. 21, 1998, pp. 137-142. |
Thad Eugene Starner, Wearable Computing and Contextual Awareness, Massachusetts Institute of Technology, Jun. 1999, 248 pages. |
U.S. Appl. No. 09/007,894, filed Jan. 15, 1998, Horvitz. |
U.S. Appl. No. 09/055,477, filed Apr. 6, 1998. |
U.S. Appl. No. 09/364,522, filed Jul. 30, 1999, Horvitz. |
U.S. Appl. No. 09/364,527, filed Jul. 30, 1999, Horvitz. |
U.S. Appl. No. 09/364,528, filed Jul. 30, 1999, Horvitz. |
U.S. Appl. No. 09/365,287, filed Jul. 30, 1999, Horvitz. |
U.S. Appl. No. 09/365,293, filed Jul. 30, 1999, Horvitz. |
William Noah Schilt, A System Architecture for Context-Aware Mobile Computing, Columbia University, 1995, 153 pages. |
Workshop on Wearable Computing Systems, Aug. 19-21, 1996. |
Cited By (75)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20020054117A1 (en) * | 2000-03-16 | 2002-05-09 | Van Dantzich Maarten R. | Scope user interface for displaying the priorities and properties of multiple informational items |
US20070011314A1 (en) * | 2000-03-16 | 2007-01-11 | Microsoft Corporation | Notification platform architecture |
US8701027B2 (en) | 2000-03-16 | 2014-04-15 | Microsoft Corporation | Scope user interface for displaying the priorities and properties of multiple informational items |
US8566413B2 (en) | 2000-03-16 | 2013-10-22 | Microsoft Corporation | Bounded-deferral policies for guiding the timing of alerting, interaction and communications using local sensory information |
US20040254998A1 (en) * | 2000-06-17 | 2004-12-16 | Microsoft Corporation | When-free messaging |
US8086672B2 (en) | 2000-06-17 | 2011-12-27 | Microsoft Corporation | When-free messaging |
US7912726B2 (en) * | 2000-12-08 | 2011-03-22 | At&T Intellectual Property Ii, L.P. | Method and apparatus for creation and user-customization of speech-enabled services |
US20060004575A1 (en) * | 2000-12-08 | 2006-01-05 | At&T Corp. | Method and apparatus for creation and user-customization of speech-enabled services |
US20050102235A1 (en) * | 2001-01-10 | 2005-05-12 | Michael Waidner | Method and system for processing of documents with electronic signatures |
US20020133564A1 (en) * | 2001-03-13 | 2002-09-19 | Norihisa Takayama | Apparatus for sending/receiving data and computer program therefor |
US7613702B2 (en) * | 2001-03-14 | 2009-11-03 | Microsoft Corporation | Schemas for a notification platform and related information services |
US20050278344A1 (en) * | 2001-03-14 | 2005-12-15 | Microsoft Corporation | Schemas for a notification platform and related information services |
US9460421B2 (en) | 2001-03-14 | 2016-10-04 | Microsoft Technology Licensing, Llc | Distributing notifications to multiple recipients via a broadcast list |
US20050278366A1 (en) * | 2001-03-14 | 2005-12-15 | Microsoft Corporation | Schemas for a notification platform and related information services |
US7613722B2 (en) * | 2001-03-14 | 2009-11-03 | Microsoft Corporation | Schemas for a notification platform and related information services |
US20060036642A1 (en) * | 2001-03-14 | 2006-02-16 | Microsoft Corporation | Schemas for a notification platform and related information services |
US9413817B2 (en) | 2001-03-14 | 2016-08-09 | Microsoft Technology Licensing, Llc | Executing dynamically assigned functions while providing services |
US8572576B2 (en) | 2001-03-14 | 2013-10-29 | Microsoft Corporation | Executing dynamically assigned functions while providing services |
US7613721B2 (en) * | 2001-03-14 | 2009-11-03 | Microsoft Corporation | Schemas for a notification platform and related information services |
US20080189376A1 (en) * | 2001-06-12 | 2008-08-07 | Verizon Business Network Services Inc. | Automated message handling system and process |
US8364800B2 (en) * | 2001-06-12 | 2013-01-29 | Verizon Business Network Services Inc. | Automated message handling system and process |
US8700781B2 (en) | 2001-06-12 | 2014-04-15 | Verizon Business Global Llc | Automated processing of service requests using structured messaging protocols |
US20030093327A1 (en) * | 2001-11-13 | 2003-05-15 | Bellsouth Intellectual Property Corporation | Systems and methods for processing an electronic request to purchase goods or services |
US9886309B2 (en) | 2002-06-28 | 2018-02-06 | Microsoft Technology Licensing, Llc | Identity-based distributed computing for device resources |
US20040143795A1 (en) * | 2002-10-25 | 2004-07-22 | Takaya Matsuishi | Display data creating technique for automatically Providing efficient representation of portal pages with improved visual recognition |
US20060195583A1 (en) * | 2003-02-27 | 2006-08-31 | Fabio Bellifemine | Method and system for providing information services to a client using a user profile |
US7873742B1 (en) * | 2003-11-20 | 2011-01-18 | Microsoft Corporation | Providing content per delivery endpoint |
US20070015520A1 (en) * | 2005-07-12 | 2007-01-18 | Qwest Communications International Inc. | Efficiently determining the location of a mobile communications device system and methods |
US9420453B2 (en) | 2005-07-12 | 2016-08-16 | Qwest Communications International Inc. | Correlating and mapping mobile device locations on a mobile device |
US8725173B2 (en) * | 2005-07-12 | 2014-05-13 | Qwest Communications International Inc. | User defined location based notification for a mobile communications device systems and methods |
US20070015521A1 (en) * | 2005-07-12 | 2007-01-18 | Qwest Communications International Inc. | Correlating activities with the location of a mobile communications device systems and methods |
US20110081921A1 (en) * | 2005-07-12 | 2011-04-07 | Owest Communications International Inc. | User Defined Location Based Notification for a Mobile Communications Device Systems and Methods |
US9462461B2 (en) | 2005-07-12 | 2016-10-04 | Qwest Communications International Inc. | Correlating mobile device locations |
US9462462B2 (en) | 2005-07-12 | 2016-10-04 | Qwest Communications International Inc. | Providing location-based information to a user of a mobile communication device |
US7336964B2 (en) | 2005-07-12 | 2008-02-26 | Qwest Communications International Inc. | Correlating activities with the location of a mobile communications device systems and methods |
US7515917B2 (en) | 2005-07-12 | 2009-04-07 | Qwest Communications International Inc. | Efficiently determining the location of a mobile communications device system and methods |
US7899469B2 (en) * | 2005-07-12 | 2011-03-01 | Qwest Communications International, Inc. | User defined location based notification for a mobile communications device systems and methods |
US8599013B1 (en) | 2005-09-29 | 2013-12-03 | Baron Services, Inc. | System and method for providing environmental information to a wireless transmitter coverage area |
US8816876B2 (en) * | 2005-09-29 | 2014-08-26 | Baron Services, Inc. | System for providing environmental condition information to vehicles and related methods |
US8180465B2 (en) * | 2005-10-28 | 2012-05-15 | Microsoft Corporation | Multi-modal device power/mode management |
US20080126282A1 (en) * | 2005-10-28 | 2008-05-29 | Microsoft Corporation | Multi-modal device power/mode management |
US20070191023A1 (en) * | 2006-02-13 | 2007-08-16 | Sbc Knowledge Ventures Lp | Method and apparatus for synthesizing presence information |
US8195584B2 (en) | 2008-06-27 | 2012-06-05 | Microsoft Corporation | Combining predictive models of forgetting, relevance, and cost of interruption to guide automated reminding |
US20090327169A1 (en) * | 2008-06-27 | 2009-12-31 | Microsoft Corporation | Combining predictive models of forgetting, relevance, and cost of interruption to guide automated reminding |
US7996338B2 (en) | 2008-06-27 | 2011-08-09 | Mircrosoft Corporation | Combining predictive models of forgetting, relevance, and cost of interruption to guide automated reminding |
US20100088364A1 (en) * | 2008-10-08 | 2010-04-08 | International Business Machines Corporation | Social networking architecture in which profile data hosting is provided by the profile owner |
US8463242B2 (en) | 2009-02-27 | 2013-06-11 | Research In Motion Limited | Communications system providing mobile device notification content type selection features and related methods |
EP2224682A1 (en) | 2009-02-27 | 2010-09-01 | Research In Motion Limited | Communications system providing mobile device notification content type selection features and related method |
US20100222027A1 (en) * | 2009-02-27 | 2010-09-02 | Research In Motion Limited | Communications system providing mobile device notification content type selection features and related methods |
CN101867611A (en) * | 2009-02-27 | 2010-10-20 | 捷讯研究有限公司 | Provide the mobile device notification content type to select the communication system and the method thereof of feature |
US20110060803A1 (en) * | 2009-04-23 | 2011-03-10 | Microsoft Corporation | Message Notification Campaigns |
US8990338B2 (en) | 2009-09-10 | 2015-03-24 | Google Technology Holdings LLC | Method of exchanging photos with interface content provider website |
US8589516B2 (en) | 2009-09-10 | 2013-11-19 | Motorola Mobility Llc | Method and system for intermediating content provider website and mobile device |
US9026581B2 (en) | 2009-09-10 | 2015-05-05 | Google Technology Holdings LLC | Mobile device and method of operating same to interface content provider website |
US20110061091A1 (en) * | 2009-09-10 | 2011-03-10 | Motorola, Inc. | Method and System for Intermediating Content Provider Website and Mobile Device |
US9450994B2 (en) | 2009-09-10 | 2016-09-20 | Google Technology Holdings LLC | Mobile device and method of operating same to interface content provider website |
US8937546B1 (en) | 2009-11-30 | 2015-01-20 | Baron Services, Inc. | Method and system of providing real-time site specific information |
US8264345B2 (en) | 2009-11-30 | 2012-09-11 | Baron Services, Inc. | System and method of providing real-time site specific information |
US20110128144A1 (en) * | 2009-11-30 | 2011-06-02 | Baron Services, Inc. | System and method of providing real-time site specific information |
EP2357766A1 (en) * | 2010-02-17 | 2011-08-17 | Cellco Partnership D/B/A Verizon Wireless | Business hour notification delivery |
US8260314B2 (en) | 2010-02-17 | 2012-09-04 | Cellco Partnership | Business hour notification delivery |
US20110201346A1 (en) * | 2010-02-17 | 2011-08-18 | Cello Partnership D/B/A Verizon Wireless | Business hour notification delivery |
US9872087B2 (en) | 2010-10-19 | 2018-01-16 | Welch Allyn, Inc. | Platform for patient monitoring |
US9386102B2 (en) | 2010-11-04 | 2016-07-05 | Panasonic Intellectual Property Corporation Of America | Gateway apparatus, communication apparatus, apparatus co-operation network system, and apparatus co-operation method |
US9037656B2 (en) * | 2010-12-20 | 2015-05-19 | Google Technology Holdings LLC | Method and system for facilitating interaction with multiple content provider websites |
US20120158866A1 (en) * | 2010-12-20 | 2012-06-21 | Motorola-Mobility, Inc. | Method and System for Facilitating Interaction with Multiple Content Provider Websites |
US9503409B2 (en) | 2013-02-25 | 2016-11-22 | Google Inc. | Suppression of extraneous alerts on multiple devices |
US9853931B2 (en) | 2013-12-10 | 2017-12-26 | Google Llc | Predictive forwarding of notification data |
US9407591B2 (en) | 2013-12-10 | 2016-08-02 | Google Inc. | Predictive forwarding of notification data |
US8738723B1 (en) * | 2013-12-10 | 2014-05-27 | Google Inc. | Predictive forwarding of notification data |
US10469430B2 (en) | 2013-12-10 | 2019-11-05 | Google Llc | Predictive forwarding of notification data |
US10621602B2 (en) | 2015-09-22 | 2020-04-14 | Adobe Inc. | Reinforcement machine learning for personalized intelligent alerting |
US11272330B1 (en) * | 2020-12-04 | 2022-03-08 | Capital One Services, Llc | Methods and systems for facilitating digital notifications in mobile communication networks |
US20220182798A1 (en) * | 2020-12-04 | 2022-06-09 | Capital One Services, Llc | Methods and systems for facilitating digital notifications in mobile communication networks |
US11523256B2 (en) * | 2020-12-04 | 2022-12-06 | Capital One Services, Llc | Methods and systems for facilitating digital notifications in mobile communication networks |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US7249159B1 (en) | Notification platform architecture | |
US20070011314A1 (en) | Notification platform architecture | |
US7975015B2 (en) | Notification platform architecture | |
US7243130B2 (en) | Notification platform architecture | |
US8024415B2 (en) | Priorities generation and management | |
US6513026B1 (en) | Decision theoretic principles and policies for notification | |
US6601012B1 (en) | Contextual models and methods for inferring attention and location | |
EP1287444B1 (en) | Priorities generation and management | |
JP5243679B2 (en) | Notification platform architecture | |
US20020087649A1 (en) | Bounded-deferral policies for reducing the disruptiveness of notifications | |
WO2001084764A2 (en) | Transmitting information given constrained resources | |
US7417650B1 (en) | Display and human-computer interaction for a notification platform | |
US7209916B1 (en) | Expression and flexibility framework for providing notification(s) | |
KR101064769B1 (en) | Use of a bulk-email filter within a system for classifying messages for urgency or importance | |
JP5189768B2 (en) | System and method for extending application preference classes | |
JP4896726B2 (en) | System, method and storage device for performing actions based on evaluation of conditions of preference | |
US20040002988A1 (en) | System and method for modeling subscriptions and subscribers as data | |
US20040002972A1 (en) | Programming model for subscription services | |
US20090037832A1 (en) | Method and System for Mashing Up and Presenting Contextual Suggestions to Mobile Users | |
JP2012074061A (en) | Notification platform architecture | |
EP1852789A1 (en) | Priorities generation and management |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
AS | Assignment |
Owner name: MICROSOFT CORPORATION, WASHINGTON Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:HORVITZ, ERIC J.;KADIE, CARL M.;JACOBS, ANDREW W.;REEL/FRAME:011227/0752 Effective date: 20001003 |
|
STCF | Information on status: patent grant |
Free format text: PATENTED CASE |
|
FPAY | Fee payment |
Year of fee payment: 4 |
|
AS | Assignment |
Owner name: MICROSOFT TECHNOLOGY LICENSING, LLC, WASHINGTON Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:MICROSOFT CORPORATION;REEL/FRAME:034541/0001 Effective date: 20141014 |
|
FPAY | Fee payment |
Year of fee payment: 8 |
|
FEPP | Fee payment procedure |
Free format text: MAINTENANCE FEE REMINDER MAILED (ORIGINAL EVENT CODE: REM.); ENTITY STATUS OF PATENT OWNER: LARGE ENTITY |
|
LAPS | Lapse for failure to pay maintenance fees |
Free format text: PATENT EXPIRED FOR FAILURE TO PAY MAINTENANCE FEES (ORIGINAL EVENT CODE: EXP.); ENTITY STATUS OF PATENT OWNER: LARGE ENTITY |
|
STCH | Information on status: patent discontinuation |
Free format text: PATENT EXPIRED DUE TO NONPAYMENT OF MAINTENANCE FEES UNDER 37 CFR 1.362 |
|
FP | Lapsed due to failure to pay maintenance fee |
Effective date: 20190724 |