Calendar Event Data Aggregation via Intermediary Mediator

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing calendar applications are limited in their ability to identify and access data related to calendar events from content sources outside their execution context, resulting in a lack of personalized and engaging user experiences.

Innovation Solution

A computing device selects a calendar event and obtains data from memory areas outside its execution context, presenting this data intermittently in a user interface element associated with the application, allowing for personalized and enhanced user interaction.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If calendar applications only access data within their execution context, then data security and system stability are maintained, but the ability to provide personalized and engaging user experiences is limited

Engineering Contradiction:
Improveability to access external dataVSAvoiddata security
Core Design Contradiction:
Adaptability or versatilityVSReliability

Solution Approach 1:

The patent introduces an intermediary component that mediates between the calendar application and external data sources. This intermediary selectively allows access to external data while maintaining security boundaries, enabling the application to obtain personalized event information without compromising system stability or data security.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The system architecture is segmented into distinct execution contexts with controlled access boundaries. The patent divides the data access mechanism into internal execution context (for core functionality) and external execution context (for enhanced personalization), allowing selective data flow between segments while maintaining isolation for security.

Inventive Principle:
Principle #1Segmentation

2Adaptability or versatility

If calendar applications access data from multiple external sources, then user experience personalization is enhanced, but system complexity increases

Engineering Contradiction:
Improvedata aggregation capabilityVSAvoidsystem architecture
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent implements a universal data access interface that can handle multiple external data sources through a single standardized mechanism. This multi-functional approach allows the system to aggregate diverse data types (weather, traffic, event information) from various sources without requiring separate access pathways for each source, thereby reducing overall system complexity.

Inventive Principle:
Principle #6Universality (Multi-functionality)

3Productivity

If calendar applications continuously monitor and update event data, then user experience remains current and engaging, but energy consumption increases

Engineering Contradiction:
Improvedata freshnessVSAvoidenergy consumption
Core Design Contradiction:
ProductivityVSUse of energy by moving object

Solution Approach 1:

The patent implements periodic action by updating event-related data at specific intervals or triggers rather than continuously monitoring. The system refreshes information such as weather forecasts, traffic conditions, and event details at predetermined times or when specific conditions are met, maintaining data freshness while significantly reducing energy consumption compared to continuous monitoring.

Inventive Principle:
Principle #19Periodic action

Data Source

PatentUS10331305B2Aggregating and presenting event information
Publication Date: 2019.06.25 MICROSOFT TECHNOLOGY LICENSING LLC
  • US10331305B2 patent drawing
  • US10331305B2 patent drawing
  • US10331305B2 patent drawing

AI summary

Embodiments of the disclosure aggregate and present event information relating to a calendar event associated with an application executing on a computing device. In some embodiments, data relating to the calendar event is obtained from a content source that is outside an execution context of the application. The data relating to the calendar event is obtained and/or presented intermittently in a user interface element associated with the application. The content source that is outside the execution context of the application may be within an execution context of one or more other applications, an operating system of the computing device, and/or a web service.