SFC Header Propagating Flow Characteristics Across DiffServ Domains
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing service function chaining (SFC) technologies face challenges in propagating traffic flow characteristics across multiple DiffServ domains, leading to inconsistencies in quality of service (QoS) requirements, as DSCP markings are site-specific and often modified or removed, affecting network traffic prioritization and user experience.
Innovation Solution
The solution involves a service function classifier device that determines packet classification, selects a service function path, and generates an SFC header with traffic flow characteristics, such as QoS requirements, to ensure proper forwarding and prioritization across multiple domains, using an NSH-based header to encapsulate packets and maintain QoS consistency.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If DSCP markings are used for QoS in DiffServ domains, then network traffic prioritization can be implemented, but the markings are site-specific and often modified or removed, leading to inconsistency in QoS requirements across multiple domains
Solution Approach 1:
The patent introduces an intermediary mechanism (SFC header with flow characteristics) that mediates between different DiffServ domains. Instead of relying on direct DSCP markings that get modified at each domain boundary, the system uses a standardized flow characteristics field in the SFC header to propagate QoS requirements consistently across multiple domains, acting as a mediator that preserves QoS information through domain boundaries.
Solution Approach 2:
The patent changes the parameter representation from site-specific DSCP markings to standardized flow characteristics (bandwidth, delay, jitter, loss) in the SFC header. This parameter transformation allows QoS requirements to be expressed in a universal manner that is consistent across different DiffServ domains, eliminating the inconsistency caused by domain-specific marking interpretations.
2Productivity
If service function chains are used to control network traffic functions, then service orchestration is improved, but existing SFC technologies cannot effectively propagate flow characteristics across multiple DiffServ domains
Solution Approach 1:
The patent extends the SFC header to provide multi-functionality by incorporating universal flow characteristics fields that work across multiple DiffServ domains. The same SFC header structure serves both service function orchestration within a domain and QoS propagation across domain boundaries, making the system universally applicable without requiring domain-specific extensions.
3Adaptability or versatility
If DSCP markings are modified or removed at network nodes, then network flexibility is improved, but QoS prioritization and user experience are affected
Solution Approach 1:
The patent implements a feedback mechanism where flow characteristics are explicitly signaled in the SFC header at each domain boundary. This feedback loop ensures that QoS requirements are re-established and reinforced at each domain transition, compensating for any modifications or removals of DSCP markings and maintaining consistent traffic prioritization throughout the service function chain.
Data Source
AI summary
In one embodiment, a service function classifier device determines a classification of a packet using one or more packet classification rules. The device selects a service function path based on the classification of the packet. The device determines one or more traffic flow characteristics based on the classification of the packet. The device generates a service function chaining (SFC) header that identifies the selected service function path and the determined one or more traffic flow characteristics. The SFC header is configured to cause a device along the service function path to forward the encapsulated packet based on the identified service function path and the determined one or more traffic flow characteristics. The device sends the packet along the selected service function path as an encapsulated packet that includes the generated SFC header.