Content Router with Command Memory for Payload Analysis
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing synchronization systems lack flexibility and efficiency in routing changes between content nodes, as they rely solely on packet addresses and do not analyze payload data, leading to increased complexity and storage requirements, especially when handling diverse content types like audio or image files.
Innovation Solution
A content routing system with store and forward logic that processes incoming commands, selects destination nodes based on content type, and uses a command memory to generate and store outgoing commands, allowing for flexible routing and reduced storage needs by translating between protocols and adapting commands for limited-capability nodes.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If known routers forward packets based solely on address information without analyzing payload data, then routing simplicity is maintained, but synchronization flexibility and efficiency deteriorate
Solution Approach 1:
The patent introduces a synchronization server as an intermediary component between content nodes and routers. This server analyzes payload data, determines synchronization requirements, and generates appropriate routing commands. By placing the intelligence in the intermediary layer rather than in every router, the system achieves synchronization flexibility without increasing individual router complexity
Solution Approach 2:
The system performs preliminary analysis of payload data and determination of synchronization requirements before actual packet forwarding occurs. The synchronization server pre-processes content information, identifies relevant nodes, and prepares routing commands in advance, enabling efficient and flexible synchronization without requiring complex real-time decision-making at each router
2Reliability
If synchronization systems maintain master copies of all records at multiple locations, then data availability is improved, but storage requirements increase substantially
Solution Approach 1:
The patent extracts only the essential synchronization metadata and routing information from complete content records, storing these lightweight data structures at multiple locations rather than maintaining full master copies. The synchronization server holds minimal information about content nodes and their relationships, enabling data availability through distributed routing without the storage burden of replicated master copies
Solution Approach 2:
Instead of copying entire master records to multiple locations, the system creates and distributes lightweight routing commands and node information that reference the actual content. These minimal copies enable nodes to locate and access content efficiently without requiring substantial storage capacity at each location
3Productivity
If routers forward packets only when destination nodes are simultaneously connected, then network resource usage is optimized, but synchronization capability for disconnected devices deteriorates
Solution Approach 1:
The synchronization server performs preliminary analysis and command generation while the source node is connected, creating routing commands that contain all necessary information for future delivery. These pre-prepared commands are stored and can be executed later when destination nodes become available, enabling synchronization of disconnected devices without wasting network resources during disconnection periods
Solution Approach 2:
The synchronization server acts as a mediator that decouples the connection requirements of source and destination nodes. It receives content from connected sources, processes synchronization requirements, and manages delivery to destinations when they are available, optimizing network usage by batching operations while maintaining full synchronization capability for disconnected devices
Data Source
AI summary
A method, apparatus and system for routing changes to information between a plurality of content nodes and a command memory of a content router. Content nodes may be user devices (such as mobile phones) and user accounts (such as email accounts). Content nodes may hold one or more content types such as email, contacts, tasks, events and library items. A command memory centralizes conflict detection, resolution and error handling within a content routing system.