DOCSIS IPinIP Classifier Mixed IPv4 IPv6 Rules
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
The DOCSIS specification lacks the capability to effectively classify tunneled IPinIP packets that combine IPv4 and IPv6 protocols, limiting the granularity of traffic classification to the outer protocol header and restricting Quality of Service (QoS) management, as it prohibits mixing IPv4 and IPv6 rules in a single classification rule, leading to errors and reduced functionality.
Innovation Solution
A system and method that implement a network device with a processor and memory to classify tunneled IPinIP packets using classification parameters from both IPv6 and IPv4 encodings, along with TCP/UDP encodings, allowing extended classification capabilities by evaluating headers and mapping packets to service flows, even when IPv4 is embedded within IPv6, using Vendor-Specific Extensions to avoid errors.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If DOCSIS classification rules prohibit mixing IPv4 and IPv6 rules in a single classification rule, then classification errors are avoided and system stability is maintained, but classification granularity is limited and functionality is reduced
Solution Approach 1:
The patent segments the classification rule into multiple independent classification fields (IPv6 classification field, IPv4 classification field, TCP/UDP classification field) that can be selectively applied. This allows the system to process tunneled IPinIP packets with both IPv6 outer headers and IPv4 inner headers by applying appropriate classification fields from the segmented rule set, resolving the contradiction between maintaining reliability and enabling mixed protocol classification functionality.
2Productivity
If only the outer protocol header is used for classification, then processing complexity is reduced and processing speed is improved, but classification granularity is limited and QoS management capability is reduced
Solution Approach 1:
The patent implements nested classification by examining multiple protocol headers at different encapsulation levels. The classifier first processes the outer IPv6 header, then nests into the inner IPv4 header, and finally examines the TCP/UDP header. This nested approach enables fine-grained QoS management for tunneled packets while maintaining efficient processing through hierarchical evaluation, resolving the contradiction between processing speed and QoS management capability.
3Adaptability or versatility
If IPv4 and IPv6 classification rules are mixed in a single upstream or downstream traffic classifier, then enhanced classification capability is achieved, but DOCSIS specification compliance is violated and errors are generated
Solution Approach 1:
The patent introduces an intermediary mechanism (Vendor-Specific Extensions and extended classification fields) that mediates between the DOCSIS specification requirements and the need for mixed IPv4/IPv6 classification. The extension fields act as a bridge, allowing the system to process tunneled packets with both protocol types while maintaining compliance with the base DOCSIS specification, thus resolving the contradiction between enhanced classification capability and specification compliance.
Data Source
AI summary
A network device includes a memory and a processor. The processor implements at least one classifier to provide classification for tunneled IPinIP traffic based on classification parameters provided by Internet Protocol Version 6 (IPv6) classification encoding, Internet Protocol Version 4 (IPv4) classification encoding, and Transport Control Protocol/User Datagram Protocol (TCP/UDP) classification encodings, wherein one of the IPv6 classification encoding and the IPv4 classification encoding is provided by extension information to provide extended classification capabilities. The processor uses the at least one classifier to compare the classification parameters provided by the IPv6 classification encoding, the IPv4 classification encoding, and the TCP/UDP classification encodings to fields in an IPv6 header, an IPv4 header, and a TCP/UDP header of the IPinIP packet. Based on the comparison, the processor maps the IPinIP packet to a service flow identified by the classification parameters.