Modular Packet Processing at Forwarder Interfaces
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing data network forwarders implement unnecessary processing logic across all interfaces due to a single generic interface module, leading to inefficiencies in resource usage, maintenance complexity, and management issues with vendor proprietary information.
Innovation Solution
A modular and flexible system where software modules for packet processing are assigned per interface and direction, allowing only necessary processing logic to be implemented, with modules prioritized and enabled/disabled at runtime, enabling vendor-specific features without affecting the rest of the system.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If a single generic interface module is used at all interfaces, then interface functionality is provided, but CPU resources are excessively consumed and software maintenance becomes complicated
Solution Approach 1:
The patent divides the interface module into separate inbound and outbound processing modules, each handling specific processing tasks at different directions. This segmentation allows the system to load only the necessary modules at each interface based on actual traffic direction and requirements, reducing unnecessary CPU processing while maintaining full interface functionality where needed.
2Adaptability or versatility
If a single generic interface module is used at all interfaces, then interface functionality is provided, but software maintenance becomes unnecessarily complicated
Solution Approach 1:
By separating inbound and outbound processing into distinct modules, the patent creates independent code units that can be maintained and updated separately. This reduces maintenance complexity compared to a monolithic generic interface module, as changes can be isolated to specific directional processing paths without affecting the entire interface software.
Solution Approach 2:
The patent implements dynamic loading of processing modules based on actual interface requirements and traffic conditions. This dynamic approach allows the system to adapt its processing capabilities to actual needs, simplifying maintenance by only loading and maintaining modules that are currently in use, rather than maintaining a complete generic module set at all interfaces.
3Adaptability or versatility
If a single generic interface module is used at all interfaces, then interface functionality is provided, but vendor proprietary features cannot be independently managed
Solution Approach 1:
The patent segments processing logic into separate inbound and outbound modules, allowing vendor proprietary features to be independently implemented and managed in specific modules without affecting other interfaces or processing directions. This enables selective loading and management of vendor-specific code at each interface based on actual requirements.
Solution Approach 2:
The patent allows different processing modules to be loaded at different interfaces based on local requirements and vendor features. Each interface can have its processing modules customized according to local needs, enabling independent management of vendor proprietary information at each location without requiring system-wide changes.
Data Source
AI summary
A system and method for processing information transport elements, such as ethernet packets, at interfaces to a forwarder. Modules that implement processing logic are allocated per interface and per direction (i.e., inbound or outbound). At any given interface, a series of modules would be used to process inbound packets; likewise, a set of modules would be used to process outbound packets. For inbound packets, the modules allocated for inbound processing are executed when the packet is received from the interface, before sending the packet on to the forwarder. For packets that are outbound from the forwarder, the modules allocated for outbound processing are applied when the packet is sent by the forwarder, prior to any other processing, e.g., queuing to hardware. To assign modules to different interfaces at a forwarder, a registration process is performed during the system start-up process, or dynamically at runtime. For any given interface and direction, modules can be prioritized, so that a packet is processed sequentially in a specific order, one module after the other.