Calendar Series Event Protection for Fast Exception Item Access

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing calendar applications require multiple encryption and decryption processes for series events with exception items, leading to performance degradation and user frustration due to long delays.

Innovation Solution

A data structure and protection scheme that stores series event information and exception item information in the same file, allowing for single encryption/decryption operations, reducing the need for multiple processes.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If exception items are stored as embedded attachments in the series event data structure, then data protection and access control are maintained, but multiple decryption processes are required to access exception items, degrading application performance

Engineering Contradiction:
Improvedata protectionVSAvoidapplication performance
Core Design Contradiction:
ReliabilityVSProductivity

Solution Approach 1:

The patent segments the series event data structure by separating exception items from the main series event data. Instead of embedding exception items within the series event attachment, the patent stores exception items as separate attachments in the calendar item data structure. This segmentation allows the series event data to be decrypted once and stored in memory, while exception items can be individually decrypted and accessed without re decrypting the entire series event data, thus maintaining data protection while improving access performance.

Inventive Principle:
Principle #1Segmentation

2Reliability

If multiple encryption/decryption processes are performed for series events with exceptions, then security is maintained, but user experience deteriorates due to long delays and blocked operations

Engineering Contradiction:
ImprovesecurityVSAvoiduser experience
Core Design Contradiction:
ReliabilityVSEase of operation

Solution Approach 1:

The patent applies preliminary action by decrypting the series event data in advance and storing it in memory before the user needs to access exception items. When a user views or modifies an exception item, the system only needs to decrypt the specific exception item attachment rather than the entire series event data. This preliminary decryption of the main series data eliminates repeated decryption operations, maintaining security while significantly reducing delays and improving user experience.

Inventive Principle:
Principle #10Preliminary action

3Productivity

If exception items are stored as separate attachments, then access efficiency is improved, but data structure complexity increases

Engineering Contradiction:
Improveaccess efficiencyVSAvoiddata structure complexity
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

The patent uses a nested doll approach by embedding the exception item attachments within the overall calendar item data structure, which itself contains references to the series event data. The exception items are nested as attachments within the calendar item that contains the series event reference. This nested structure maintains a clear hierarchical relationship between series events and exceptions while allowing efficient individual access to exception items without flattening the entire data structure, thus balancing access efficiency with manageable complexity.

Inventive Principle:
Principle #7Nested doll (Nesting)

Data Source

PatentUS12468823B2Efficient protection of recurrent event data for calendar applications
Publication Date: 2025.11.11 MICROSOFT TECHNOLOGY LICENSING LLC
  • US12468823B2 patent drawing
  • US12468823B2 patent drawing
  • US12468823B2 patent drawing

AI summary

Systems and methods of protecting series event data for a calendar application include identifying an exception item of a series event to display in the user interface of a calendar application, locating a series data container for the series event that includes the exception item, and locating an exception container element in the series data container that stores the identified exception item. When the exception container element includes an exception attachment, the exception item is decrypted to retrieve body and attachment data for the exception item which is then displayed in the user interface of the calendar application. When the exception container element does not include an exception attachment, a series master attachment stored in a series container element of the series data container is decrypted to retrieve the body and attachment data for the exception item which is then displayed in the user interface of the calendar application.