Layer-Agnostic Transport Framework for Content-Centric Networks
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Traditional protocol stacks impose a fixed direction on messages, limiting flexibility in communication between components of the same or different stacks, especially in content-centric networks, where standardization and directional dependencies restrict the flow of control and notification messages.
Innovation Solution
A transport framework that enables layer-agnostic communication by using unique names for command messages, allowing them to flow up or down the stack based on originator direction, and utilizing a message delivery system to dynamically route messages between components, APIs, and forwarders across the same or different stacks.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If a traditional protocol stack is used where each layer communicates only with adjacent layers, then the system provides standardized communication protocols, but the flexibility in message flow direction and component communication is reduced
Solution Approach 1:
The patent introduces a message broker as an intermediary component that receives messages from any component in the stack and routes them to the appropriate target component regardless of layer boundaries. This broker acts as a mediator that decouples the strict layer-to-layer communication requirement, allowing flexible message routing while maintaining the overall stack architecture.
Solution Approach 2:
The message broker is designed as a universal component that handles multiple types of messages (data, control, notification) between various components (applications, stack components, forwarders) across different stacks. This multi-functional approach allows a single component to serve multiple communication needs, increasing flexibility without proportionally increasing complexity.
2Adaptability or versatility
If command messages are restricted to specific directional flow within a stack, then the message routing becomes simpler, but the adaptability to dynamically configured networks is reduced
Solution Approach 1:
The message routing system is designed to be dynamic rather than static. The message broker can adapt routing decisions based on real-time network conditions, component availability, and message priority. This dynamic approach allows the system to respond to changing network configurations while maintaining manageable routing logic through centralized broker control.
Solution Approach 2:
The system changes the routing parameters from fixed directional constraints to flexible destination-based routing. Instead of messages being constrained by layer boundaries and flow directions, messages are routed based on target component identification parameters that the broker interprets to determine the optimal path, allowing adaptability without proportional complexity increase.
3Adaptability or versatility
If layer-agnostic communication is implemented allowing any component to communicate with any other component, then the flexibility and adaptability are improved, but the difficulty of managing communication protocols increases
Solution Approach 1:
The message broker serves as an intermediary that manages the complexity of layer-agnostic communication. It receives messages from any component with any protocol format and handles the routing logic, protocol conversion, and delivery to target components. This centralizes the protocol management complexity within the broker rather than requiring each component to manage complex communication rules.
Solution Approach 2:
Components in the stack are designed to send messages with self-describing information including destination identification and protocol metadata. The message broker uses this self-service information to automatically route messages without requiring complex manual configuration or intervention, reducing the operational difficulty of managing flexible communication.
Data Source
Figure 1
Figure 2A
Figure 2B
AI summary
One embodiment provides a transport-framework system that facilitates command messages to be communicated in a layer-agnostic manner. During operation, the system generates, by a component of a stack of communication modules, a first command message for a target entity. The first command message includes a name unique to the target entity, and the stack does not require a respective communication module to communicate only with a layer above or below thereof The component sends the first command message to the target entity by inserting the first command message into a queue corresponding to the component. The component can also receive a second command message from a sending entity via a queue corresponding to the sending entity, and the second command message includes a name unique to the component. This facilitates command messages to be communicated in a layer-agnostic manner.