Network Device Pseudo-Device Interface for Service Extension
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Conventional approaches to enhancing network service capabilities in routers are costly and time-consuming, requiring custom hardware blades or clustering, which increases operational complexity and costs, and lacks integration with existing routers.
Innovation Solution
The implementation of a network device with a consistent interface for both internal and external service complexes, utilizing a pseudo-device interface that applies metadata to packets for inline tunneling, allowing seamless interaction with off-the-shelf or custom service complexes, and enabling a simplified path to custom hardware deployment.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If custom hardware blades are built for a particular router to provide new services, then service capabilities are improved, but deployment cost and time increase significantly
Solution Approach 1:
The patent implements a universal service interface architecture where service complexes can be deployed as software on standard hardware platforms rather than requiring custom hardware blades. The service complex interface defines standardized protocols that allow multiple service types (firewall, caching, CDN, etc.) to run on generic server hardware, making the system universally adaptable to different services without custom manufacturing for each service type.
Solution Approach 2:
The patent uses virtualization to create virtual instances of service complexes that can be copied and deployed across multiple physical hosts. Service complexes are represented as software images or containers that can be replicated and instantiated on demand, eliminating the need to physically build custom hardware for each service deployment.
2Adaptability or versatility
If multiple routers or servers are clustered to provide services, then service capabilities are improved, but operational complexity and costs increase
Solution Approach 1:
The patent merges the control plane and forwarding plane functions with service complex management into a unified router architecture. The router's control plane directly manages service complexes through standardized interfaces, eliminating the need for separate clustering infrastructure and reducing operational complexity by consolidating management functions.
Solution Approach 2:
The patent introduces a service complex interface as an intermediary layer between the router's forwarding plane and external service complexes. This interface abstracts the complexity of service management, providing standardized protocols for packet forwarding, metadata exchange, and service control, thereby simplifying operations while maintaining service capabilities.
3Adaptability or versatility
If service complexes are externally deployed, then service flexibility is improved, but integration with router forwarding plane deteriorates
Solution Approach 1:
The patent segments the service complex functionality into distinct software modules that can be independently deployed and managed while maintaining standardized interfaces with the router. The service complex interface separates concerns between routing functions and service processing, allowing external deployment while preserving integration through defined protocol boundaries.
Solution Approach 2:
The patent implements feedback mechanisms where the router's control plane continuously monitors service complex performance and dynamically adjusts service configurations. Metadata is exchanged between the forwarding plane and service complexes to maintain synchronized state information, ensuring reliable integration even when service complexes are externally deployed.
Data Source
AI summary
An example network device includes a network interface and a control unit that receives a packet having header information. The control unit includes a forwarding structure having a plurality of entries that each refers to one of a plurality of logical interfaces, a forwarding engine configured to access the forwarding structure to select a first logical interface to which to forward the packet based on the header information, wherein the first logical interface comprises a pseudo-device interface (PDI). The control unit also includes a PDI module that tunnels the packet to an external service complex (ESC) by at least applying a set of metadata to the packet, encapsulating the packet with a header, and forwarding the packet to the ESC via the network interface, and wherein the metadata allows the ESC to determine a set of services to be applied to the packet based on the metadata.