Instance Message Structure for Legacy Scheduling Compatibility
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Legacy versions of computer systems cannot natively implement advanced scheduling features like modern systems, leading to compatibility issues when adding or modifying appointments in a series, resulting in loss of exception information and disrupted series integrity.
Innovation Solution
A method that creates instance messages with default and exception values, allowing modern and legacy systems to interact seamlessly by identifying user input for new or modified events, preserving the series integrity even when changes would not be compatible with legacy systems.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Ease of operation
If legacy systems are used to maintain compatibility with older clients, then ease of operation is improved, but advanced scheduling features and series integrity are lost
Solution Approach 1:
The patent introduces an intermediary mechanism that translates between legacy system formats and modern scheduling features. When a modern client performs operations on appointment series, the system creates instance messages that preserve exception information in a format that can be understood by both modern and legacy clients, acting as a bridge between the two systems.
Solution Approach 2:
The patent segments the appointment series data into master messages and instance messages. The master message contains the series definition, while instance messages contain specific appointment data and exceptions. This segmentation allows legacy clients to work with individual instances while modern clients can manage the entire series, resolving the contradiction between compatibility and advanced features.
2Adaptability or versatility
If modern scheduling features are implemented, then adaptability and advanced functionality are improved, but compatibility with legacy systems deteriorates
Solution Approach 1:
The patent applies local quality by allowing different parts of the system to use different formats. Modern clients interacting with the server use the new instance message format with exception support, while legacy clients continue to use their traditional formats. The server translates between these formats locally at the point of interaction, enabling advanced features without forcing legacy clients to upgrade.
Solution Approach 2:
The instance message format is designed to be universal, serving both modern and legacy clients. It contains fields that modern clients can utilize for advanced scheduling while maintaining compatibility with legacy system requirements. This multi-functionality allows a single message format to satisfy both compatibility and advanced feature requirements.
3Measurement precision
If exceptions are added to appointment series in modern systems, then scheduling precision is improved, but series integrity is lost when legacy clients are involved
Solution Approach 1:
The patent performs preliminary action by pre-defining the instance message structure with exception fields before legacy client interactions occur. The master message is prepared with all necessary exception information, and instance messages are generated in advance with proper formatting. This preliminary preparation ensures that when legacy clients access the series, the exception information is already preserved in a compatible format, maintaining both precision and integrity.
Solution Approach 2:
The patent uses copying to create instance messages that replicate the master message structure while incorporating specific exception data. Each instance message is a copy of the master message template, filled with specific appointment data and exceptions. This copying mechanism ensures consistency across the series while preserving individual exceptions, maintaining series integrity even with advanced scheduling features.
Data Source
AI summary
Adding an instance to a series in a fashion that preserves the series for both modern and legacy systems, even when the addition would not ordinarily be compatible with the legacy system. A method includes identifying a master message. The master message includes default values for events in the series. The method further includes identifying user input for a new event in the series. The user input identifies exceptions to the default values. The method further includes creating an instance message that includes default values from the master message for which there are no exceptions identified in the user input and includes the exceptions from the user input.