IP Address Management via Dynamic Cooling Queue
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
In IP networks, dynamically allocated addresses can lead to overbilling due to brutal disconnects, where old user's sessions persist, causing new users to receive unwanted packets, especially in GPRS and 3G networks, as existing solutions like stateful FireWalls and NATs are inefficient in managing address reassignment.
Innovation Solution
A network device with a cooling queue that detects and returns released addresses to the end of the queue upon receiving packets, sending error notifications to manage address reassignment adaptively, independent of FireWall and NAT locations, and applicable to any access network.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If a cooling queue is used to hold released addresses, then address reassignment is prevented from causing overbilling, but the queue size may become uncomfortably large for IPv4
Solution Approach 1:
The patent implements a dynamic cooling queue mechanism where addresses are actively managed based on packet reception. When a packet is received for a released address, the address is moved to the end of the queue, creating dynamic repositioning. This allows the queue to adapt its effective size and behavior based on actual network conditions rather than maintaining a static large queue structure.
Solution Approach 2:
The patent changes the parameter of address priority in the cooling queue based on packet reception history. Addresses that receive packets are reprioritized by moving them to the end of the queue, while addresses without packet reception remain at the front. This parameter change allows efficient use of queue space by prioritizing addresses based on actual usage patterns rather than static timing.
2Reliability
If stateful FireWalls are used to stop incoming unsolicited packets, then security is improved, but the FW states are not reset after brutal disconnect, allowing old packets to get through
Solution Approach 1:
The patent implements preliminary action by proactively managing the cooling queue of released addresses before packets arrive. The system continuously tracks released addresses and their packet reception history, preparing the queue structure in advance to handle incoming packets correctly, rather than reacting after security issues arise.
Solution Approach 2:
The patent uses feedback from packet reception to dynamically adjust the cooling queue. When packets are received for released addresses, the system receives feedback about actual usage and uses this to reposition addresses in the queue. This feedback mechanism allows the system to adapt to real network conditions and improve both security and efficiency.
3Reliability
If IPv6 cooling mechanism is used, then address reassignment is managed, but the cooling queue size estimate is based on maximum cooling period which is uncomfortably large
Solution Approach 1:
The patent applies partial action by implementing cooling queue management that focuses on actual packet reception patterns rather than preparing for maximum possible cooling periods. The system manages only the addresses that actually receive packets during their cooling period, rather than allocating space for all possible addresses, thus reducing the required queue capacity.
4Reliability
If two FireWalls are deployed to manage address reassignment, then overbilling is prevented, but the solution is very expensive and requires installing FWs in many places
Solution Approach 1:
The patent implements universality by creating a cooling queue mechanism that can be integrated into existing network devices performing address management functions. The solution works with standard IP networking components and can be deployed in various network configurations (GPRS, 3G, and other access networks) without requiring specialized hardware or complex multi-device deployments.
Data Source
AI summary
Managing addresses to be assigned to users of an IP network is described, in which it is detected that a packet has been addressed to a released address held in a queue for holding released addresses, and the held address to which the packet has been addressed is returned to the end of the queue.