Managed Object Member Architecture for Software Defined Radio Data Consistency
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
In software defined radio systems, data replication leads to issues with stale and inconsistent data across nodes, particularly due to latency and bandwidth concerns in update mechanisms, such as pull and push architectures, which are challenging to manage effectively.
Innovation Solution
A method utilizing managed object members (MOMs) for automatic data updates, where changes are propagated system-wide as soon as they occur, eliminating the need for polling mechanisms and ensuring consistency across the system, with MOMs subscribing to data topics and validating changes before updating, allowing for efficient data propagation and storage.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Loss of time
If polling mechanisms are used to retrieve data updates in each node, then system latency is reduced, but network bandwidth is wasted
Solution Approach 1:
Instead of nodes polling the server to check for updates (traditional approach), the server actively pushes update notifications to nodes when data changes occur. This inversion of the update initiation direction eliminates the need for continuous polling, reducing network bandwidth consumption while maintaining real-time update capability and minimizing latency.
2Loss of time
If update period between data updates is shortened, then system latency is minimized, but network bandwidth is wasted
Solution Approach 1:
The system implements event-driven periodic action where update notifications are sent only when data changes occur, rather than using fixed-interval polling. This allows the system to maintain real-time consistency (effectively zero latency) while transmitting data only when necessary, eliminating wasted bandwidth from unnecessary updates during stable states.
3Loss of time
If push architecture is used to send update messages directly to nodes, then latency and network bandwidth usage are minimized, but implementation complexity increases
Solution Approach 1:
The patent introduces an intermediary update notification mechanism that mediates between the server and multiple nodes. The server publishes update notifications to a subscription-based notification system, which automatically routes updates to relevant nodes. This intermediary layer simplifies the push architecture by handling the complexity of tracking and notifying multiple nodes, reducing implementation complexity while maintaining the benefits of direct push updates.
4Reliability
If data is replicated across multiple nodes, then system reliability is improved, but data consistency becomes challenging to maintain
Solution Approach 1:
The system implements a feedback mechanism where nodes subscribe to update notifications and automatically update their local data copies when changes occur. The server publishes notifications about data changes, and this feedback loop ensures all replicated nodes receive and apply updates simultaneously, maintaining data consistency across the distributed system while preserving the reliability benefits of data replication.
Data Source
AI summary
A method for managing a flow of information in an object oriented software environment. A master MOM (130) and at least a second MOM (135) can be initialized. A third MOM (140) also can be initialized. A change resolution (150), which includes data correlating to a change in a device in a system, can be automatically propagated from the second MOM to the master MOM. The change can be a change in configuration data or a change in a run-time state of the device. Data in the master MOM correlating to the change resolution can be updated. In response to the change resolution, a change publication (160), which includes data correlating to the change resolution, can be automatically propagated from the master MOM to at least the third MOM. Data in the third MOM correlating to the change publication can be updated.