Symmetric Service Chain Binding for Stateful IP Services
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current network service chains are unidirectional and cannot fully satisfy the requirements of stateful Internet Protocol (IP) services, which need traffic to be forwarded through the same set of service functions in both directions, requiring manual configuration and separate headers for forward and reverse paths.
Innovation Solution
Automated association and binding of forward/reverse service chains using a controller that generates and manages symmetric service-chain-ids for both paths, enabling bi-directional traffic flow management and correlation of service headers for stateful services.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If unidirectional service chains are used, then the network service structure is simple and easy to implement, but stateful IP services cannot be properly supported because traffic cannot be forwarded through the same service functions in both directions
Solution Approach 1:
The service chain is segmented into forward path and reverse path components, each with their own service function identifiers. The controller separates the management of forward and reverse traffic flows, allowing independent configuration and optimization of each direction while maintaining overall service chain functionality.
Solution Approach 2:
The controller merges the management of forward and reverse service chains by binding them together through a binding relationship. This allows the system to treat bidirectional stateful services as a unified entity while still maintaining the ability to independently configure and manage each direction's service functions.
2Ease of operation
If separate service headers are used for forward and reverse paths, then each direction can be independently configured, but manual configuration is required and management becomes complex
Solution Approach 1:
The controller automatically generates service headers for both forward and reverse paths based on the service chain configuration. The system performs self-service by automatically binding forward and reverse service chain identifiers without requiring manual intervention, reducing operational complexity while maintaining independent configurability.
Solution Approach 2:
The controller implements feedback mechanisms to automatically correlate and bind forward and reverse service chain identifiers. The system monitors service chain configurations and automatically updates service headers and bindings accordingly, eliminating the need for manual configuration while maintaining proper bidirectional service function routing.
3Productivity
If automated binding of forward and reverse service chains is implemented, then service provisioning is simplified and consistency is ensured, but the controller complexity increases
Solution Approach 1:
The controller is designed with multi-functionality to handle both forward and reverse service chain management, binding operations, and service header generation in a unified manner. This universal approach allows the controller to automate multiple tasks across different service chain directions using the same core mechanisms, improving productivity while managing complexity through consolidation.
Data Source
AI summary
A plurality of network nodes are deployed in a network, each network node configured to apply a service function to traffic that passes through the respective network nodes. A controller generates information for a service chain that involves application to traffic of one or more service functions at corresponding ones of the plurality of network nodes along a forward path through the one or more network nodes. The controller identifies one or more of the service functions within the service chain that is stateful. When one or more of the service functions of the service chain is stateful, the controller generates information for a reverse path through the one or more service nodes for the one or more stateful service functions. The controller binds a forward chain identifier for the forward path with a reverse chain identifier for the reverse path for the service chain.