Service Function Chain Context Sharing via Control Plane
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Conventional Service Function Chaining (SFC) in communication networks lacks sufficient context awareness, particularly for dynamic service conditions and user-specific policies, leading to inadequate processing of user plane packets across the service function chain, as upstream service functions are not aware of downstream states.
Innovation Solution
A control plane function is introduced to manage and share context information across the service function chain, enabling dynamic adjustments to traffic flow and enforcing preconditions, with a condition function acting as a shared data structure or controller to coordinate service functions based on user feedback and resource attributes.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Productivity
If a simple packet classification operation based on five tuple of packet headers is used, then the classification process is simple and fast, but it does not provide sufficient context for subsequent actions in the service function chain
Solution Approach 1:
The patent introduces a classifier as an intermediary component that enriches packet headers with additional context information (metadata) before packets are processed by service functions. This classifier acts as a mediator between the simple packet identification and the complex service function processing, adding necessary context without significantly impacting classification speed.
Solution Approach 2:
The patent applies preliminary action by pre-defining service chain encapsulations and metadata structures that will be attached to packets before they enter the service function chain. This preparation of context information in advance allows service functions to make informed decisions without real-time computation overhead.
2Device complexity
If context information is only delivered to downstream service functions following the flow of packets, then the data flow is simple, but upstream service functions are not aware of the state of downstream service functions
Solution Approach 1:
The patent implements feedback mechanisms where downstream service functions can report their state back to upstream service functions and the controller. This allows upstream functions to make decisions based on downstream status, creating a closed-loop control system that maintains context awareness throughout the service chain.
Solution Approach 2:
The controller is designed as a universal component that handles multiple functions: managing context information, coordinating service functions, collecting metadata from downstream functions, and making routing decisions. This multi-functional controller centralizes information management without requiring complex peer-to-peer communication between service functions.
3Adaptability or versatility
If a control plane function is introduced to manage and share context information across the service function chain, then context-aware conditionality is enabled, but the system complexity increases
Solution Approach 1:
The control plane function serves as an intermediary that manages context information and coordinates service functions. By centralizing control logic in this mediator component, the patent enables complex context-aware routing and service chain management without requiring each service function to implement complex decision-making logic.
Solution Approach 2:
The patent segments the system into distinct components: the control plane function for management and coordination, service functions for processing, and a classifier for packet handling. This segmentation allows each component to focus on specific tasks, making the overall complex system more manageable and maintainable.
Data Source
AI summary
A service function chain including service functions which process user plane packets is controlled by providing (S21) a shared context comprising rules and policies for processing the user plane packets, the shared context being shared between the service functions of the service function chain, reading (S22) the shared context, and adjusting (S23) traffic flow across the service function chain based on the rules and policies associated with the read shared context.