Time-to-Leave Reminders Using Location History and Calendar Matching
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing electronic devices with touch-sensitive displays provide reminders based on default values or outdated information, failing to account for user's location history, leading to inefficient and cognitively burdensome interactions.
Innovation Solution
The device automatically identifies calendar entries with unknown locations, retrieves previously-visited addresses, determines a departure time based on these addresses, and provides intelligent reminders without user intervention, using a touch-sensitive display and integrated modules for route calculation and preference-based routing.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Measurement precision
If the device uses default values or outdated information for reminders, then the reminder system is simple to implement, but the accuracy and timeliness of reminders deteriorates
Solution Approach 1:
The system pre-calculates travel time between locations and stores it in advance. When creating a reminder, the system retrieves pre-computed travel time data rather than calculating it in real-time, enabling accurate departure time suggestions without complex real-time computation
Solution Approach 2:
The system automatically retrieves location history data and computes optimal departure times without requiring user input or manual location entry. The reminder system serves itself by autonomously gathering necessary data from the device's location history and calendar applications
2Ease of operation
If the device requires users to manually search for and review address/navigation details, then the user has full control over reminder information, but the cognitive burden and number of touch inputs increases
Solution Approach 1:
The system automatically identifies the destination address from the user's location history and retrieves navigation details without requiring the user to manually search or input information. The system serves itself by autonomously gathering all necessary data from stored location history and calendar information
Solution Approach 2:
The system acts as an intermediary between the user's location history data and the reminder creation process. It automatically bridges the gap by retrieving relevant address and navigation information from stored data, presenting a simplified interface to the user
3Adaptability or versatility
If the device provides generic default reminders, then the implementation is straightforward, but the reminders do not account for user's actual location and travel time
Solution Approach 1:
The system pre-processes and stores location history data, including addresses, timestamps, and geographical information, before it is needed for reminder creation. This preliminary data preparation enables the system to quickly retrieve relevant location information and compute personalized travel times without complex real-time processing
Solution Approach 2:
The system utilizes feedback from the device's location sensors and calendar applications to continuously improve reminder accuracy. By analyzing past location data and event patterns, the system adapts to user behavior and provides increasingly personalized departure time recommendations
Data Source
AI summary
Systems and methods for identifying on an electronic device an identifier and an associated time, date, or time and date, wherein the identifier is a name of an entity that a user is scheduled to visit at the associated time, date, or time and date. Determining, at around the time, date, or time and date, using a location sensor, a location of the electronic device as an entity address. Associating the identifier with the entity address and storing the identifier and associated entity address. Upon receipt of the identifier as an input: retrieving, using the identifier, the entity address, displaying, at the touch-sensitive display, a selectable user interface element corresponding to the entity address, receiving a selection of the selectable user interface element corresponding to the entity address, and in response to receiving the selection, providing the entity address to an application on the electronic device for use.