NAT Port Allocation for High-Priority Network Data Flows
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Conventional network apparatuses face challenges in managing mixed data flows with differing Quality of Service (QoS) requirements, particularly in CPE and automotive networks, leading to increased latency, hardware costs, and inefficient resource allocation due to the coexistence of real-time and latency-tolerant data flows sharing the same data radio bearers and buffers.
Innovation Solution
Implementing a network apparatus that assigns dedicated NAT port ranges or designated IP address ranges to data flows, reserves buffers for high-priority data, and employs dual-threshold or tiered threshold strategies to prioritize and manage data flows in both uplink and downlink directions, aligning with 3GPP standards for efficient packet filtering and routing.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Productivity
If real-time and latency-tolerant data flows share the same data radio bearers and buffers, then resource utilization is improved, but latency for high-priority data increases
Solution Approach 1:
The patent segments the shared buffer into multiple priority levels, creating separate buffer regions for high-priority real-time data flows and latency-tolerant data flows. This segmentation allows high-priority packets to be transmitted first without being blocked by lower-priority traffic, thereby reducing latency while still utilizing the same physical buffer resources.
Solution Approach 2:
The patent applies different quality attributes to different regions of the buffer by assigning priority levels to specific buffer segments. High-priority data flows are allocated buffer regions with preferential transmission rights, while latency-tolerant flows use other regions. This local differentiation of quality enables simultaneous optimization for both resource utilization and latency requirements.
2Loss of time
If dedicated buffer resources are allocated to high-priority data flows, then latency is reduced, but hardware costs increase
Solution Approach 1:
The patent implements dynamic buffer allocation where the amount of buffer space assigned to different priority levels can change based on current network conditions and traffic demands. The system can dynamically adjust the size of high-priority buffer regions when traffic patterns change, allowing efficient use of hardware resources while maintaining low latency when needed.
Solution Approach 2:
The patent makes the buffer serve multiple functions by allowing it to handle both high-priority and latency-tolerant data flows simultaneously with different service qualities. The same physical buffer infrastructure provides differentiated service levels, eliminating the need for completely separate hardware resources for different priority traffic.
3Productivity
If packet filtering and routing are streamlined for high-priority data, then QoS enforcement efficiency is improved, but device complexity increases
Solution Approach 1:
The patent performs preliminary classification of data packets into priority levels at the point of ingress, before packets enter the buffer system. By determining priority early and assigning packets to appropriate buffer regions immediately, the system avoids complex real-time decision-making during transmission, thereby improving QoS enforcement efficiency without requiring complex processing during critical transmission phases.
Data Source
AI summary
Various embodiments include methods of managing mixed data flow types in communications in a network apparatus. The network apparatus may determine data flow priority levels of a plurality of data flows, identify high-priority data flows associated with a particular LAN interface, and assign a designated public IP address range or a designated public port range for the high-priority data. Upon receiving an uplink, the apparatus may select a source port number from the previously reserved range dedicated for high-priority data flows in response to the received packet matching one or more prioritized data flow packet filters, modify the received uplink packet, and forward the modified uplink packet to the next hop in the path towards the destination IP address in response to determining that the packet is enqueued successfully.