Residential Gateway Wake-Up via Localization Server Mapping
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Residential gateways in sleep mode cannot be remotely awakened by client devices due to unknown physical location and the need for fully qualified domain name registration, leading to power wastage and inconvenience for end users.
Innovation Solution
A method and apparatus that utilizes a localization server in the service provider's network to store and manage residential gateway localization information, enabling remote wake-up through subnet directed broadcasts and IP address retrieval, without requiring end-user FQDN registration.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If the residential gateway is kept powered on 24 hours a day, then remote access is always available, but power consumption increases significantly
Solution Approach 1:
The system performs preliminary actions by registering the FQDN and IP address mapping in the DNS server before the gateway needs to be accessed. When the gateway enters sleep mode, its physical location is pre-preserved in the DNS infrastructure, enabling immediate wake-up capability without requiring continuous power consumption.
Solution Approach 2:
The DNS server acts as an intermediary between the client device and the sleeping gateway. It stores and manages the mapping between FQDN and gateway IP address, enabling the client to locate and wake up the gateway through standard DNS resolution without needing to maintain continuous connection or know the gateway's physical location.
2Use of energy by moving object
If the residential gateway enters sleep mode to save power, then power consumption decreases, but remote access becomes difficult due to unknown physical location
Solution Approach 1:
The DNS server serves as a persistent intermediary that maintains the gateway's digital identity (FQDN to IP mapping) even when the gateway is physically disconnected or in sleep mode. This allows the client device to resolve the gateway's address through standard DNS queries without needing to track the gateway's physical location or connection state.
Solution Approach 2:
The gateway automatically performs DNS registration of its FQDN and IP address when it first connects to the network, and automatically updates this registration when it wakes from sleep mode. This self-service mechanism eliminates the need for manual configuration or continuous monitoring, allowing the gateway to maintain remote accessibility autonomously throughout sleep and wake cycles.
3Reliability
If FQDN registration is required for remote access, then remote connectivity can be established, but additional service costs and configuration complexity increase
Solution Approach 1:
The gateway automatically performs FQDN registration in the DNS server when it first connects to the network and when it wakes from sleep mode. This self-service mechanism handles the configuration automatically without requiring end-user intervention, manual DNS setup, or additional service subscriptions, thereby reducing both complexity and cost while maintaining reliable remote connectivity.
Data Source
Figure 1
Figure 2
Figure 3
AI summary
A method and apparatus are described including transmitting localization information to a localization server, transitioning into sleep mode, receiving a wake up frame from an access router, transitioning to awake mode, transmitting updated localization information to the localization server and establishing a connection between a network access device and a client device. Also described are a method and apparatus including transmitting a request to connect to a network access device, receiving localization information of the network access device from a localization server and establishing a connection between the network access device and the client device based on the localization information.