Unified Time-Relationship Model for Recurring Events
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing data storage systems face difficulties in modeling recurring time relationships and exceptions across different objects, leading to a complex and fragmented representation of time-based data, which hinders the creation of a unified view of time-related objects.
Innovation Solution
A unified scheme is proposed where time-related properties are stored independently of the base object, using a model that separates recurrence patterns and exceptions into distinct tables, allowing for a consistent representation of recurring events and exceptions, thereby decoupling objects from time and recurrence information.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If time-based relationships are modeled separately for each object type, then each object type can have its own time representation, but it becomes difficult to provide a unified view of time-related objects and increases system complexity
Solution Approach 1:
The patent segments the time-based relationship model into separate components: object definitions, time slot definitions, and recurrence/exception rules. Each component is independent and can be defined separately, yet they work together through references to create a unified time-based system that handles diverse object types without increasing overall complexity
Solution Approach 2:
The patent creates a universal time-based relationship model that can represent multiple object types (meetings, tasks, messages, etc.) using the same structure. The time slot and recurrence models are object-agnostic, allowing a single unified view of all time-related objects while maintaining adaptability to specific object requirements
2Adaptability or versatility
If recurrence information is stored with each object occurrence, then each object can have its own recurrence pattern, but it becomes difficult to manage and modify recurring events without altering the object itself
Solution Approach 1:
The patent extracts recurrence information and exception rules from the object definitions and stores them in separate time slot records. This allows recurrence patterns to be managed independently from the objects themselves, making it easier to modify, add, or remove recurring instances without altering the core object definitions
Solution Approach 2:
The patent establishes recurrence patterns and exception rules in advance as part of the time slot definition. Once defined, these pre-configured patterns automatically generate recurring time slots, eliminating the need to manually create each occurrence and simplifying management of recurring events
3Manufacturing precision
If exceptions are added to each recurring event to handle holidays and special cases, then accurate time representation is achieved, but the number of objects increases and consistency becomes difficult to maintain
Solution Approach 1:
The patent merges the exception handling mechanism into the recurrence rule definition rather than creating separate exception objects. Exceptions are specified as part of the recurrence pattern (e.g., excluding specific dates or applying to specific occurrences), which reduces the number of objects while maintaining accurate time representation
Solution Approach 2:
Instead of adding exceptions to each recurring object, the patent inverts the approach by defining the regular recurrence pattern and then specifying exceptions as deviations from that pattern. This reduces complexity by starting with the general case and adding only necessary deviations rather than starting with individual objects and adding exceptions to each
Data Source
AI summary
Time-related properties may be modeled independent of a base object. Rather than storing time properties with the object, they may be stored independently. A given object may be stored once, even if it has a recurrent time property. The description of a “meeting,” for example, may be stored once. Each occurrence of that object over time may be stored in a “timeslot” (object <foo> occurs at time ‘t’ on day ‘d’). If it is a recurring property, recurrence information may be stored independently. “Exception” information may be stored independently as well.