Master and Instance Message Segmentation for Legacy System Compatibility
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Legacy versions of computer systems cannot natively implement advanced scheduling features supported by modern systems, leading to compatibility issues and incomplete information sharing between modern and legacy clients.
Innovation Solution
A method that involves creating a master message with default information for a series of events and instance messages with exception information, allowing both modern and legacy systems to receive and interpret the messages, enabling modern functionality to be propagated to legacy systems without breaking existing interactions.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Productivity
If modern systems implement advanced scheduling features, then functionality and productivity are improved, but compatibility with legacy systems deteriorates
Solution Approach 1:
The patent segments the event data into a master message containing default information for all events in a series, and separate instance messages containing exception information for specific events. This segmentation allows modern systems to implement advanced scheduling features while maintaining compatibility with legacy systems that can process the segmented messages individually.
Solution Approach 2:
The server acts as an intermediary that translates modern scheduling features into a format compatible with both modern and legacy clients. The server sends master and instance messages that can be interpreted by legacy clients, enabling them to access advanced features without requiring direct support for the new data formats.
2Productivity
If legacy systems are updated to support new features, then functionality is improved, but system complexity and migration cost increase
Solution Approach 1:
Instead of requiring legacy systems to fully implement modern scheduling features, the patent allows them to process partial information through master andinstance messages. Legacy systems can function with the updated features by processing the segmented messages, without needing to rewrite their entire scheduling architecture.
3Productivity
If modern clients use advanced scheduling features, then functionality is improved, but information sharing with legacy clients deteriorates
Solution Approach 1:
The patent segments scheduling information into master messages (containing default information applicable to all events in a series) andinstance messages (containing exception information for specific events). This segmentation ensures that modern clients can access full advanced features while legacy clients receive and process the same information in a compatible format, preventing information loss.
Solution Approach 2:
The system establishes feedback mechanisms where updates to master orinstance messages are propagated to all clients. When modern clients make changes to scheduling series or individual events, these updates are reflected in the messages sent to legacy clients, ensuring continuous information sharing and synchronization across the heterogeneous client environment.
Data Source
AI summary
A method includes identifying a series of events formatted for a modern system. The series of events includes a master message usable by modern systems. The master message includes default information for all events in the series. The method further includes identifying a plurality of instance messages. Each of the instance messages includes default information and exception information for a given event in the series of events. The method further includes sending both the master message and the instance messages to other systems without regard to whether the other systems are modern or legacy systems.