Service Function Chain Version-Aware Packet Encapsulation
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Traditional service node deployment in computer networking is often dictated by network topology, limiting flexibility and agility, especially with the rise of virtual platforms and dynamic networks, where service nodes need to be deployed anywhere to efficiently manage traffic flows and apply network functions such as security and load balancing.
Innovation Solution
The implementation of a service function chain (SFC) that encapsulates headers in packets with version information, allowing for dynamic ordering and topological independence of network functions, enabling flexible deployment and management of service nodes by specifying the required network functions and their versions within the network.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If service nodes are deployed according to network topology, then network structure is simple and easy to manage, but deployment flexibility and agility are limited
Solution Approach 1:
The patent segments service node deployment from network topology constraints by introducing service function chains that can be independently configured. Service nodes are divided into discrete functional units (firewall, load balancer, etc.) that can be deployed anywhere in the network rather than being bound to specific topological positions, enabling flexible deployment while maintaining manageable complexity through modular organization.
Solution Approach 2:
The patent introduces service function chain headers as an intermediary mechanism that decouples service node deployment from network topology. These headers carry service path information that enables packets to be routed through service nodes regardless of their physical or logical position in the network, thus providing deployment flexibility without increasing management complexity.
2Adaptability or versatility
If service function chains are used to enable service nodes anywhere on network, then deployment flexibility is improved, but packet processing complexity increases due to header encapsulation and version matching
Solution Approach 1:
The patent applies preliminary action by pre-encapsulating service function chain headers with version information at the service chain endpoint before packets enter the network. This allows service nodes to be pre-configured with specific software versions, and packets carry version identifiers that enable direct matching without complex runtime negotiation or processing, thus reducing packet processing complexity while maintaining deployment flexibility.
Solution Approach 2:
The patent changes the parameter of packet headers by adding service function chain information including version identifiers. This parameter addition enables service nodes to quickly identify and process packets destined for their specific software versions without complex matching logic, reducing processing complexity while allowing flexible deployment of multi-version service nodes throughout the network.
3Reliability
If multiple versions of network functions are supported, then service level agreements and smooth updates are improved, but version management complexity increases
Solution Approach 1:
The patent extracts version information from service node configurations and embeds it directly in service function chain headers. This allows multiple software versions of network functions to coexist in the network, with each packet carrying the specific version identifier it requires. Service nodes can maintain multiple versions without increasing management complexity because version routing is handled automatically by header matching rather than complex version management protocols.
Data Source
AI summary
Certain aspects of the present disclosure are generally directed to version-aware service function chaining. One example method generally includes determining version information corresponding to one or more of a plurality of network functions to be performed for a packet for a service function chain (SFC) and encapsulating a service header in the packet for the SFC, the service header indicating the plurality of network functions to be performed for the packet and the version information corresponding to the one or more network functions. In certain aspects, the method also includes sending the packet to one or more service nodes for performing the plurality of network functions in accordance with the service header.