Keep Alive Management for Network Power Optimization
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Conventional techniques for accessing networks on computing devices are inefficient, consuming significant resources like power and processing, and limit functionality by keeping network interface devices constantly active, even when not in use.
Innovation Solution
A network broker module coordinates the use of network interface devices, employing a wake pattern manager to wake specific applications in response to network traffic, a network device manager to enter low power modes when traffic ceases, and a keep alive manager to maintain connections and adjust keep alive intervals dynamically.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If network interface devices are kept constantly active to maintain network connectivity, then network availability and user experience are improved, but power consumption and resource usage increase significantly
Solution Approach 1:
The system implements periodic keep alive messages sent at calculated intervals to maintain network connections. The network broker module wakes the network interface device at specific intervals to transmit keep alive messages, then allows the device to enter low power mode until the next scheduled wake time. This periodic action maintains network availability while significantly reducing power consumption compared to constant activation.
Solution Approach 2:
The keep alive manager module dynamically calculates and adjusts keep alive intervals based on network conditions and application requirements. The system automatically manages the wake-sleep cycles of the network interface device without requiring manual intervention, adapting the activation pattern to maintain connections while optimizing power usage based on actual network needs.
2Speed
If network interface devices remain active to handle incoming traffic immediately, then response time and network performance are improved, but processing resources and power are consumed continuously
Solution Approach 1:
The system pre-calculates keep alive intervals and schedules wake times in advance. The network broker module determines optimal intervals based on network conditions and application requirements, then proactively wakes the network interface device at these predetermined times to send keep alive messages. This preliminary planning ensures timely network responses while avoiding unnecessary continuous operation.
Solution Approach 2:
The network broker module acts as an intermediary between applications and the network interface device. It manages the wake-sleep cycles of the network interface device, coordinating keep alive message transmission and incoming traffic handling. This intermediary layer allows the network interface device to enter low power modes while ensuring it wakes at appropriate times to maintain connectivity and handle traffic efficiently.
3Adaptability or versatility
If network connections are maintained continuously to ensure always-on functionality, then user experience and service availability are improved, but resource consumption and power usage increase
Solution Approach 1:
The system dynamically adjusts keep alive intervals based on network conditions, application requirements, and observed traffic patterns. The keep alive manager module monitors network state and modifies the wake-sleep schedule in real-time, extending intervals when conditions permit and reducing them when connectivity needs increase. This dynamic adaptation maintains always-on functionality while minimizing energy waste through flexible resource management.
Solution Approach 2:
The system changes the temporal parameters of network interface device operation by adjusting keep alive intervals. Instead of fixed continuous operation, the interval between wake events is dynamically modified based on network conditions and application needs. This parameter change enables the system to maintain connectivity functionality while optimizing power consumption by adapting the activation frequency to actual requirements.
Data Source
Figure 1
Figure 2
Figure 3
AI summary
Techniques are described for monitoring network traffic between the computing device and a network; transitioning the computing device from a high power mode to a low power mode, in response to determining that network traffic corresponding to one or more applications of the computing device has completed; maintaining connectivity between the computing device and the network while the computing device is in the low power mode; receiving a pre-registered notification; and responsive to receiving the pre-registered notification, transitioning the computing device from the low power mode to the high power mode.