Calendar Conflict Notification via Cache Segmentation

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Current handheld electronic devices lack the capability to automatically check for scheduling conflicts with new appointments or meetings due to memory and processing constraints, requiring users to manually navigate through the calendar application, which is inconvenient and time-consuming.

Innovation Solution

A handheld electronic device with a calendar application that maintains a cache of recent calendar entries, allowing for automatic conflict checking and notification when entering new appointments or meetings, by comparing the proposed event to the cached entries rather than the entire database.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If the entire database of calendar information is searched to detect scheduling conflicts, then the reliability of conflict detection is improved, but the loss of time and processing resources increases significantly

Engineering Contradiction:

Improveconflict detection accuracyVSAvoidtime to check for conflicts

Core Design Contradiction:

ReliabilityVSLoss of time

Solution Approach 1:

The calendar database is segmented into a cache portion containing recent entries and a full database portion. The system performs conflict detection by searching only the cache portion first, which is a smaller, segmented subset of the entire database. This segmentation allows rapid conflict checking for recently scheduled events without requiring a time-consuming search of the complete calendar database.

Inventive Principle:

Principle #1Segmentation

Solution Approach 2:

The system performs preliminary action by maintaining a cache of recent calendar entries in advance. This cache is populated and updated beforehand, allowing the conflict detection function to immediately query pre-organized data rather than searching the entire database when a conflict check is needed. The preliminary organization of data in the cache accelerates the conflict detection process.

Inventive Principle:

Principle #10Preliminary action

2Device complexity

If manual conflict checking is implemented to conserve memory and processing resources, then the device complexity is reduced, but the ease of operation deteriorates

Engineering Contradiction:

Improvememory and processing requirementsVSAvoiduser effort to check for conflicts

Core Design Contradiction:

Device complexityVSEase of operation

Solution Approach 1:

The calendar application performs self-service by automatically detecting scheduling conflicts without requiring user intervention. The system autonomously queries the cache for conflicts, processes the results, and notifies the user of any conflicts found. This eliminates the need for users to manually navigate through calendar entries to check for conflicts, significantly improving ease of operation while maintaining low device complexity.

Inventive Principle:

Principle #25Self-service

Solution Approach 2:

The system implements feedback by automatically notifying the user of scheduling conflicts. When a conflict is detected in the cache, the system provides immediate feedback to the user through notifications or alerts, informing them of the conflicting events. This automated feedback loop eliminates the need for users to manually check for conflicts and makes the scheduling process more user-friendly.

Inventive Principle:

Principle #23Feedback

3Extent of automation

If automatic conflict detection is implemented by searching the entire database, then the extent of automation is improved, but the productivity of the device deteriorates due to processing constraints

Engineering Contradiction:

Improveautomatic conflict checkingVSAvoidscheduling efficiency

Core Design Contradiction:

Extent of automationVSProductivity

Solution Approach 1:

Inventive Principle:

Principle #1Segmentation

Solution Approach 2:

The system performs partial action by checking only a subset of the calendar database (the cache of recent entries) rather than the entire database. This partial search is sufficient for detecting most conflicts, as conflicts are most likely to occur with recently scheduled events. The partial action approach maintains high automation while preserving device productivity by avoiding unnecessary processing of the complete database.

Inventive Principle:

Principle #16Partial or excessive action

Data Source

PatentUS9047592B2Handheld electronic device including appointment and meeting conflict notification, and associated method

Publication Date: 2015.06.02 MALIKIE INNOVATIONS LTD

AI summary

A method of checking a new entry in a calendar application having a cache that includes a first subset of existing entries falling within a first date range. Also, an electronic device implementing the method. The method includes determining whether the date of the new entry falls within the first date range. If so, the method determines whether the new entry directly conflicts with or is adjacent to one of the existing entries in the first subset, and provides a notification if appropriate. If the date is outside the first date range, the method creates a new calendar cache including a second subset of existing entries falling within a second date range around the new entry date, determines whether the new calendar entry directly conflicts with or is adjacent to one of the existing calendar entries in the second subset, and provides a notification if appropriate.