Hostless mDNS-SD Responder for Authenticated Host Wake
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current host devices cannot provide an authenticated wake service without activating the host processor, which limits their ability to respond to queries and conserve power when idle.
Innovation Solution
A method is implemented where a host processor configures a WiFi controller with an mDNS-SD responder module, allowing it to remain in a sleep state while still responding to queries by exchanging a secret key and using a random number to authenticate trusted client devices, enabling power conservation without requiring the host processor to be active.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Use of energy by moving object
If the host processor is turned off to save power, then power consumption is reduced, but the ability to respond to mDNS-SD queries and provide services is lost
Solution Approach 1:
The system divides functionality between the host processor and WiFi controller. The host processor handles complex procedures when active, while the WiFi controller independently handles mDNS-SD query responses and service discovery tasks when the host is in low-power state, allowing power savings without losing service availability.
Solution Approach 2:
The WiFi controller acts as an intermediary between the external network and the host processor. It receives and responds to mDNS-SD queries independently, and can authenticate wake requests from trusted clients without requiring the host processor to be active, thus maintaining service reliability while enabling power savings.
2Reliability
If the host processor remains active to respond to queries, then service availability is maintained, but power consumption increases
Solution Approach 1:
The host processor operates periodically rather than continuously. It activates to exchange secret keys and configure the WiFi controller, then enters low-power state. The WiFi controller continues to operate periodically to respond to queries and authenticate wake requests, achieving service availability with reduced overall power consumption.
Solution Approach 2:
The WiFi controller is empowered to serve itself by independently responding to mDNS-SD queries and authenticating wake requests using pre-configured credentials. This self-service capability allows the controller to maintain service availability without continuous host processor involvement, reducing power consumption.
3Use of energy by moving object
If the host processor is turned off, then power is saved, but authenticated wake service capability is lost
Solution Approach 1:
The host processor performs preliminary actions by exchanging secret keys with trusted clients and configuring the WiFi controller with authentication credentials before entering low-power state. This preliminary configuration enables the WiFi controller to independently authenticate wake requests from trusted clients without host processor involvement, maintaining wake service capability while enabling power savings.
Solution Approach 2:
The WiFi controller serves as an intermediary that handles authenticated wake requests using pre-configured credentials. It verifies wake requests from trusted clients independently and can activate the host processor when needed, preserving authenticated wake service capability while allowing the host to remain in low-power state.
Data Source
AI summary
Conventional wireless interface (WiFi) controllers cannot resolve authentication for trusted client devices without calculation from a host processor. Leaving the host processor on or awaking it from a sleep state each time a non-authenticated trusted client device attempts to connect wastes power. A hostless authenticated wake service allows a host controller to enter a sleep state while the WiFi controller responds to multicast domain name service-service discovery (mDNS-SD) queries from trusted client devices. Once a client device is authenticated, the WiFi controller may respond to a trusted client request to awake the host processor for further command processing and service provision. Not only does this approach reduce power consumption by allowing the host processor to remain in the sleep state, it allows trusted client devices to discover its presence while ensuring security.