Independent Protocol Stack Segmentation for Embedded Network Memory Optimization
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current operating systems, such as BSD OS and its variants, do not effectively separate the data link layer (L2) from the network layer (L3) in terms of initialization, operation, runtime control, and shutdown, leading to increased memory footprint and performance issues, especially on embedded devices that handle both IPv4 and IPv6 traffic.
Innovation Solution
An operating system with independent components for processing IPv4 and IPv6 data packets, allowing for separate initialization, shutdown, and management of each protocol stack, including a data link layer component that directs packets to the appropriate protocol component and a management information base for remote variable control.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Device complexity
If L2 and L3 protocols are not separated in terms of initialization and operation, then the system maintains operational simplicity and ease of implementation, but the memory footprint increases and device performance degrades
Solution Approach 1:
The patent segments the network protocol stack by separating L2 (data link layer) and L3 (network layer) protocols into independent components. Each protocol can be initialized, controlled, and shut down separately through independent initialization functions and separate control variables, allowing the system to load only necessary protocols into memory and reduce overall memory footprint.
2Ease of operation
If L2 and L3 protocols are not separated in terms of runtime control, then the system maintains operational simplicity, but fine-grained control capability is lost
Solution Approach 1:
The patent implements separate control variables (e.g., if_flags for L2 and separate flags for L3 protocols) and independent runtime control functions that allow each protocol layer to be enabled or disabled independently. This segmentation provides fine-grained control while maintaining ease of operation through standardized control interfaces.
Solution Approach 2:
The patent introduces dynamic runtime control mechanisms where protocol components can be activated or deactivated on-demand based on operational requirements. This allows the system to adapt its configuration dynamically, enabling fine-grained control over which protocols are active at any given time while maintaining simple operation through unified control interfaces.
3Ease of operation
If L2 and L3 protocols are not separated, then the system maintains operational simplicity, but shutdown control becomes coarse-grained
Solution Approach 1:
The patent separates shutdown control by implementing independent shutdown functions for L2 and L3 protocols. Each protocol component has its own shutdown routine that can be invoked independently, allowing the system to shut down specific protocols without affecting others, thereby achieving fine-grained shutdown control while maintaining operational simplicity through standardized function interfaces.
4Reliability
If internal code and data structure dependencies are increased, then the system maintains functional integration, but the memory footprint of the final system increases
Solution Approach 1:
The patent reduces unnecessary internal dependencies by segmenting code and data structures into separate L2 and L3 protocol components. Each component has its own data structures and code paths, eliminating redundant dependencies between protocols. This segmentation maintains functional integration within each protocol while reducing overall memory footprint by allowing selective loading and sharing of common infrastructure code.
Data Source
AI summary
An operating system, comprising a first component including a first protocol stack configured to process data packets of a first type, wherein the first component is initialized independently of other components in the operating system, a second component including a second protocol stack configured to process data packets of a second type, wherein the second component is initialized independently of the other components in the operating system, and a third component configured to receive data packets of the first type and the second type and direct the data packets of the first type to the first component and the data packets of the second type to the second component.