Abstract: Architecture that enables alerts and notifications to have priorities and time/space durations. Non-critical alerts can be displayed in a non-obtrusive manner and alert/notifications coalesced. Alerts/notifications can be assigned priorities, thereby enabling the alerts/notifications to be non-intrusive to the user. Methods include detecting when the user is using a mobile phone (or other suitable device) and then sending the alert/notification in response to the detected use based on threshold criteria relative to an accumulated sum of alerts/notifications, and an importance level (e.g., of each). Additionally, alert/notification priority can be changed (e.g. elevated, lowered) according to time (when) and space (where), thereby enabling the user to be intrusively notified based on the level, even if not previously signaled. Time and space bounds (criteria) can be assigned to alerts/notifications for merger/grouping and/or set to be auto-dismissed if no longer applicable.

Abstract: Location-based notification architecture that provides notification relevance to a user and/or a user goal. The size of the virtual perimeter or boundary is changed dynamically based on changes in relevance to a user and/or user goal, and thus, can be made dependent on various factors. The size of the perimeter can increase or decrease according to user preferences that are learned over time (e.g., preference for a gas station of a specific company). These capabilities improve the relevance of the notification the user receives. The relevance of a notification to the user can be improved by tuning the perimeter size according to known parameters that depend on the point of interest (e.g., business) itself and/or by tuning of the size of virtual perimeter according to parameters associated with user behavior. Other parameters can be considered as well, such as environmental conditions, and traffic conditions, for example.

Abstract: Architecture that provides location broker services which share the user location with other parties (e.g., based on user consent). Stationary computing devices can also determine the location of the user operator and interact accordingly. In one embodiment, the user location is retrieved from the user mobile device (e.g., smart phone) and is transmitted to other mobile or non-mobile devices with which the user interacts. Moreover, existing infrastructure and systems can be employed using a device driver that emulates the user location so that any software that uses the location services does not need modification.

Abstract: The disclosed architecture facilitates the capture of data associated with a specific geographic location, as captured by a mobile device of a user at the geographic location, for the purpose of guiding the user back to that specific geographic location. When applied to vehicles or other types of user mobility (e.g., walking) the architecture automatically detects that a user has controlled a means of transportation to a stationary (or parked) state, such as associated with a parked car. When the stationary state is reached, the location is detected (e.g., using user device sensing systems). Detection can include recording images, sounds, speech, geolocation data, etc., associated with the location and/or means of transportation. The user can configure a reminder to activate at the location to assist in the user recalling the location when returning to the means of transportation.

Abstract: Architecture that enables communication of a message from a requesting (sending) user to a single target user and/or group of target users based on current geographic location of the target user(s) while hiding the identities of the requesting user and the target user(s). This anonymity capability is provided by mediating messages between the users (requesting and target) via an anonymous messaging component (e.g., a service) that maintains anonymity of the users relative to one another. The anonymous messaging component does not publish user identities, since the component mediates between the sender and the receiver(s).

Abstract: Location-based notification architecture that provides notification relevance to a user and/or a user goal. The size of the virtual perimeter or boundary is changed dynamically based on changes in relevance to a user and/or user goal, and thus, can be made dependent on various factors. The size of the perimeter can increase or decrease according to user preferences that are learned over time (e.g., preference for a gas station of a specific company). These capabilities improve the relevance of the notification the user receives. The relevance of a notification to the user can be improved by tuning the perimeter size according to known parameters that depend on the point of interest (e.g., business) itself and/or by tuning of the size of virtual perimeter according to parameters associated with user behavior. Other parameters can be considered as well, such as environmental conditions, and traffic conditions, for example.

Abstract: Architecture that enables alerts and notifications to have priorities and time/space durations. Non-critical alerts can be displayed in a non-obtrusive manner and alert/notifications coalesced. Alerts/notifications can be assigned priorities, thereby enabling the alerts/notifications to be non-intrusive to the user. Methods include detecting when the user is using a mobile phone (or other suitable device) and then sending the alert/notification in response to the detected use based on threshold criteria relative to an accumulated sum of alerts/notifications, and an importance level (e.g., of each). Additionally, alert/notification priority can be changed (e.g. elevated, lowered) according to time (when) and space (where), thereby enabling the user to be intrusively notified based on the level, even if not previously signaled. Time and space bounds (criteria) can be assigned to alerts/notifications for merger/grouping and/or set to be auto-dismissed if no longer applicable.