Bridge Layer FIB Management for Multi-NOS Data Nodes
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing network operating systems (NOS) are not designed to efficiently share hardware resources, leading to conflicts and inefficiencies when multiple NOSs attempt to use the same hardware resources, such as an ASIC, resulting in lost routing information.
Innovation Solution
A data node with a bridge layer that mediates messages between hardware and multiple NOSs, utilizing a setting storage unit and message conversion unit to manage resource allocation and prevent conflicts by converting messages to ensure each NOS can use the hardware resources without overlap.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Productivity
If multiple NOSs share the same hardware resources (ASIC), then resource efficiency is improved, but conflicts occur and routing information is lost
Solution Approach 1:
The patent introduces a bridge layer as an intermediary component between the hardware layer and multiple NOSs. This bridge layer mediates all interactions, converting messages from multiple NOSs into hardware-specific commands and managing resource allocation. The bridge layer prevents direct conflicts by acting as a controlled interface, allowing multiple NOSs to share hardware resources (improving productivity) while maintaining routing information integrity through centralized management.
Solution Approach 2:
The patent segments the system into three distinct layers: hardware layer, bridge layer, and NOS layer. This segmentation allows each layer to operate independently with well-defined interfaces. The bridge layer specifically segments the control plane from the data plane, enabling multiple NOSs to coexist without direct interference (preventing routing information loss) while still allowing efficient hardware resource sharing through the unified bridge interface.
2Quantity of substance
If a single ASIC is shared by multiple NOSs, then cost is reduced, but operational complexity increases
Solution Approach 1:
The bridge layer is designed as a universal interface that can handle messages from multiple different NOSs and translate them into hardware-specific commands. This multi-functional bridge layer allows a single ASIC to be shared by multiple NOSs (reducing the number of hardware devices) while the bridge layer itself manages the operational complexity through standardized message conversion and resource allocation mechanisms.
3Ease of operation
If existing NOS is used without modification, then ease of operation is maintained, but resource sharing capability is limited
Solution Approach 1:
The bridge layer serves as an intermediary that translates between the existing NOS message formats and hardware-specific commands. This allows existing NOSs to be used without modification (maintaining ease of operation) while the bridge layer provides the adaptability needed for hardware resource sharing by converting and managing messages from multiple NOSs according to hardware capabilities.
Data Source
AI summary
A data node includes: a bridge layer adapted to mediate messages between a hardware layer adapted to transfer data with reference to an FIB indicating a forwarding address and a plurality of NOSs that set contents of the FIB for the hardware layer, wherein the bridge layer includes: a setting storage unit adapted to store setting information that associates the NOSs with those resources of the hardware layer which are available for use by the NOSs, and a message conversion unit adapted to receive messages setting the contents of the FIB from the NOSs, convert the messages according to the setting information in the setting storage unit so as to contain those resources of the hardware layer which are available for use by the NOSs, and update the contents of the FIB based on the converted messages.