Dynamic Service Function Chain Context Insertion
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current service function chain (SFC) models are inflexible and unable to dynamically insert or update application-specific contextual data, leading to inefficient service flow configurations and resource overprovisioning in service-provider networks, as they rely on static network-specific information and lack application awareness.
Innovation Solution
The implementation of a method that dynamically creates service flows based on application criteria, inserts and updates application-specific contextual data into SFCs, and selectively forwards this data using a service header that includes a classification policy and forwarding scope, enabling dynamic configuration of service function chains according to application requirements.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If static service function chain configuration is used, then network device reconfiguration is simplified, but service quality and resource utilization cannot adapt to dynamic application requirements
Solution Approach 1:
The patent implements dynamic service function chain configuration by introducing application-specific contextual data that changes according to application operations. The system dynamically inserts, updates, and removes services in the SFC based on real-time application requirements, transforming the static configuration model into a dynamic one that adapts to changing service quality needs without requiring manual reconfiguration of network devices.
Solution Approach 2:
The patent introduces an intermediary mechanism (application-specific contextual data and SFC management entity) that mediates between application requirements and network service configuration. This intermediary automatically translates application needs into appropriate service chain configurations, eliminating the need for direct manual reconfiguration of network devices while maintaining adaptability to application requirements.
2Adaptability or versatility
If service chaining is implemented with static configuration, then traffic flow steering is achieved, but application awareness and dynamic configuration capability are lost
Solution Approach 1:
The patent implements feedback mechanisms where application-specific contextual data is continuously monitored and fed back to the SFC management entity. This feedback loop enables the system to detect changes in application requirements and automatically adjust the service function chain configuration accordingly, providing both application awareness and dynamic configuration capability while maintaining ease of operation through automated control.
Solution Approach 2:
The patent enables the service function chain to self-configure based on application requirements. The system automatically inserts, updates, and removes services in the SFC without requiring manual intervention, allowing the network to serve itself in adapting to application needs. This self-service capability maintains ease of operation while achieving full application awareness and configuration flexibility.
3Reliability
If overprovisioning of services is used, then service capacity is ensured, but network resource consumption increases
Solution Approach 1:
The patent dynamically changes service chain parameters (insertion, update, removal of services) based on application-specific contextual data. Instead of maintaining fixed overprovisioned service capacity, the system adjusts the service chain configuration in real-time to match actual application needs, ensuring service capacity reliability while minimizing network resource consumption by removing unnecessary services from the chain.
Data Source
AI summary
A method implemented by a network element (NE), comprising receiving a classification message comprising a classification rule for identifying a service function chain (SFC) in a network, wherein the SFC comprises an ordered set of service functions (SFs) that provides services to an application, and a dynamic application-specific contextual data associated with an operation of the application, receiving a first of a plurality of application data packets, determining that the first of the application data packets matches the classification rule, generating a first SFC packet by adding the dynamic application-specific contextual data to the first of the application data packets according to the classification rule to enable communication of the dynamic application-specific contextual data to at least one of the SFs in the SFC, and sending the first SFC packet towards a next NE according to an SF path in the network associated with the SFC.