Service Function Chaining via Overlay SFC Header
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Conventional service chain architectures face processing latency and inefficiencies in forwarding packets through service function instances, as packets sequentially traverse multiple network elements, necessitating techniques to enhance processing efficiency and reduce latency.
Innovation Solution
The implementation of a new service function chain (SFC) header embedded in an overlay virtual network encapsulated frame allows for one-way transportation of information, enabling network nodes to perform packet routing and forwarding efficiently by classifying traffic flows and inserting SFC headers, which steer packets to designated service function instances, even when service functions are not on the direct data path, leveraging software-defined networking (SDN) controllers.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If packets sequentially traverse multiple network elements in conventional service chain architectures, then service functions can be applied to traffic flows, but processing latency increases and forwarding efficiency decreases
Solution Approach 1:
The patent segments the service chain processing by introducing dedicated service function instances that can be independently deployed and executed. Each service function instance processes specific service functions (firewall, NAT, DPI, etc.) separately, allowing parallel processing and reducing sequential traversal delays. The service chain is divided into discrete, manageable units that can be processed concurrently rather than strictly sequentially.
Solution Approach 2:
The patent introduces service chain descriptors and service function instances as intermediaries between the traffic flow and the service functions. These intermediaries manage the packet forwarding process, determining which service functions need to be applied and routing packets accordingly. This intermediary layer optimizes the forwarding path and reduces unnecessary sequential processing steps.
2Adaptability or versatility
If service function instances are placed in centralized locations through which all traffic traverses, then service functions can be applied uniformly, but network complexity increases and forwarding efficiency decreases
Solution Approach 1:
The patent enables service function instances to be deployed in distributed locations across the network rather than centralized. Each network node can host service function instances locally, allowing service functions to be applied at the appropriate location in the network. This local deployment reduces network complexity by eliminating the need for all traffic to traverse centralized service function points.
Solution Approach 2:
The patent creates a universal service function instance architecture where the same service function instances can be deployed across multiple network nodes. A service function instance can handle multiple service functions (firewall, NAT, DPI, etc.) and can be instantiated at different locations in the network, providing both uniformity and flexibility. This multi-functional approach maintains consistent service application while reducing network complexity.
3Productivity
If service function instances are distributed across various network nodes, then forwarding efficiency improves and latency reduces, but determining the next service function instance becomes more complex
Solution Approach 1:
The patent implements preliminary action by pre-establishing service chain descriptors that contain information about the sequence of service functions to be applied. The service chain descriptor is created in advance and includes the ordered list of service function instances. When a packet arrives, the network node can quickly determine the next service function instance by consulting the pre-configured service chain descriptor, eliminating the need for complex real-time decision-making.
Solution Approach 2:
The patent incorporates feedback mechanisms where service function instances report their processing status and results back to the network node. This feedback allows the network node to track which service functions have been applied and determine the next service function instance in the chain. The feedback loop simplifies the determination process by providing real-time information about the current state of service function processing.
Data Source
AI summary
Service function chaining is a sequence of service function instances that traffic flows need to traverse through in order. Those service function instances are not required to reside on the direct path and traffic flow, but steered through network nodes. Service function instances and network nodes process the packets that carry a service function chain (SFC) header. The packets are encapsulated by a virtual network overlay header and forwarded through the service function instances in an SFC. The SFC header in specific format will prompt the network nodes to re-route the packets in the traffic flow using destination based forwarding or path based forwarding method in the packet network as well as an SDN controller and/or in-band control plane, and able to carry the metadata with the packets.