Network QoS Classification via Destination Port Substitution
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Conventional methods for setting network traffic flow Quality of Service (QoS) are inefficient due to limitations in configuring intermediate switches and routers to inspect deeper packet layers, leading to increased latency, reduced throughput, and problematic segmentation of data packets, especially when large packet sizes exceed the Maximum Transmission Unit (MTU).
Innovation Solution
Configuring a network device to replace the destination port number in a data packet header with a Quality of Service classification port number at the source node, allowing intermediate devices to prioritize packets based on the 5-tuple classification without deep packet inspection, thereby reducing latency and improving throughput.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Measurement precision
If deep packet inspection is used to classify traffic and provide QoS, then QoS classification accuracy is improved, but networking latency increases and throughput decreases
Solution Approach 1:
The source node performs preliminary classification of data packets based on application-layer information before transmission. By pre-classifying packets and setting appropriate destination port numbers in the packet header, the network avoids the need for deep packet inspection at intermediate devices, thereby reducing latency while maintaining classification accuracy.
Solution Approach 2:
The destination port number in the packet header serves as an intermediary mechanism that carries QoS classification information. Instead of requiring intermediate devices to inspect packet contents, the classification information is embedded in the port number field, which intermediate devices can read without deep inspection, thus reducing processing time and latency.
2Measurement precision
If deep packet inspection is performed by intermediate devices, then QoS provision according to packet contents is improved, but device complexity and software requirements increase
Solution Approach 1:
The invention extracts the QoS classification function from the packet inspection process and embeds it in the destination port number field. This removes the need for complex deep packet inspection software on intermediate devices, as they only need to read the port number field which already contains the classification information.
Solution Approach 2:
The destination port number field serves multiple functions: it identifies the destination application and simultaneously carries QoS classification information. This multi-functionality eliminates the need for separate QoS inspection mechanisms, reducing device complexity while maintaining classification capabilities.
3Adaptability or versatility
If data packets are segmented when exceeding path MTU, then network compatibility is improved, but header separation from data segments causes QoS configuration problems
Solution Approach 1:
The source node performs preliminary classification and sets the QoS-indicating destination port number before packet segmentation occurs. Since the classification information is set in advance in the original packet header, it remains intact even after the packet is segmented by intermediate devices, ensuring QoS configuration reliability despite MTU constraints.
Data Source
AI summary
In one exemplary aspect, a method of managing computer network traffic flow quality of service includes the step of configuring a configurable network device to provide a specified quality of service to a data packet with a specified quality of service configuration based on a quality of service classification port number in a data packet header of the data packet. At the source node, a data packet is generated. At the source node, replacing the destination port number in the data packet header with a quality of service classification port number. At the source node, the destination port number is included in an options field of the data packet's header. The data packet is communicated to the configurable network device. At the destination node, receiving the data packet, replacing the quality of service classification port number with the original destination port number, and forwarding the packet to a destination process.