Complementary and shadow calendars
First Claim
1. A method for enabling a computing device to construct a complementary calendar for a user of a user device, the method comprising:
- receiving schedule data from a primary calendar;
identifying a user signal associated with the user of the user device, based on data received from the user device, wherein the user signal comprises a user activity performed by the user and one or more of time data, or location data, associated with the user activity performed by the user;
evaluating a device context of the device to identify the activity of the user as the user signal;
automatically generating an entry based on one or more inferences derived from the user signal comprising the user activity performed by the user, data received from the primary calendar, and one or more of the time data, or the location data, associated with the user activity performed by the user;
populating the complementary calendar, wherein the complementary calendar is automatically populated with the entry based on the user signal; and
generating a notification to the user based upon the automatically-generated entry in the complementary calendar.
2 Assignments
0 Petitions
Accused Products
Abstract
One or more techniques and/or systems are provided for constructing a complementary calendar and/or a shadow calendar. A user may maintain a primary calendar within which the user may schedule user specified tasks and/or meetings, but may inadvertently omit other entries. Accordingly, a complementary calendar may be constructed based upon inferences derived from user signal data (e.g., information used to identify/infer activities of the user, such as social network profile information, messages, temporal information, locational information, documents, etc.). The complementary calendar may be automatically populated with entries corresponding to inferences derived from user signals and/or real-time conditions (e.g., weather, store hours, traffic conditions, etc.). The primary calendar and the complementary calendar may be merged to create a shadow calendar. The complementary calendar and/or the shadow calendar may be displayed to the user and/or may be used to provide dynamic notifications and/or suggestions to the user (e.g. regarding conflicting entries/obligations, etc.).
20 Citations
20 Claims
-
1. A method for enabling a computing device to construct a complementary calendar for a user of a user device, the method comprising:
-
receiving schedule data from a primary calendar; identifying a user signal associated with the user of the user device, based on data received from the user device, wherein the user signal comprises a user activity performed by the user and one or more of time data, or location data, associated with the user activity performed by the user; evaluating a device context of the device to identify the activity of the user as the user signal; automatically generating an entry based on one or more inferences derived from the user signal comprising the user activity performed by the user, data received from the primary calendar, and one or more of the time data, or the location data, associated with the user activity performed by the user; populating the complementary calendar, wherein the complementary calendar is automatically populated with the entry based on the user signal; and generating a notification to the user based upon the automatically-generated entry in the complementary calendar. - View Dependent Claims (2, 3, 4, 5, 6, 7)
-
-
8. One or more computer-storage media having embodied thereon computer-usable instructions which, when executed by one or more processors, implement a method for enabling a computing device to construct a complementary calendar for a user of a user device, the method comprising:
-
receiving schedule data from a primary calendar; identifying a user signal associated with the user of the user device, based on data received from the user device, wherein the user signal comprises a user activity historically performed by the user and one or more of time data, or location data, associated with the user activity; evaluating a device context of the device to identify the user activity as the user signal; automatically generating an entry based on the user signal, data received from the primary calendar, and one or more of the time data, or the location data, associated with the user activity, wherein the entry corresponds to a future activity that may be performed by the user; populating the complementary calendar, wherein the complementary calendar is automatically populated with the entry based on the user signal; and generating a notification to the user based upon the automatically-generated entry in the complementary calendar. - View Dependent Claims (9, 10, 11, 12, 13, 14)
-
-
15. A system for constructing a complementary calendar for a user of a user device, the system comprising:
-
one or more processors; one or more computer storage media having embodied thereon instructions which, when executed by the one or more processors, cause the one or more processors to implement steps comprising; receive schedule data from a primary calendar; identify a user signal associated with the user of the user device, based on data received from the user device, wherein the user signal comprises a user activity performed by the user and one or more of time data, or location data, associated with the user activity performed by the user; evaluate a device context of the device to identify the activity of the user as the user signal; automatically generate an entry based on one or more inferences derived from the user signal comprising the user activity performed by the user, data received from the primary calendar, and one or more of the time data, or the location data, associated with the user activity performed by the user; populate the complementary calendar, wherein the complementary calendar is automatically populated with the entry based on the user signal; and generate a notification to the user based upon the automatically-generated entry in the complementary calendar. - View Dependent Claims (16, 17, 18, 19, 20)
-
Specification