Gateway Device Wake-Up via HTTP Tunneling
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Firewalls block inbound data from cloud servers, preventing the wake-up of gateway-enabled devices from deep sleep mode and causing excessive load on management servers due to frequent authentication and negotiation processes when establishing HTTP tunneling sessions.
Innovation Solution
A communication system that includes a cloud server, a management server, and a gateway-enabled device, where the management server uses alternative protocols like facsimile or email to wake up the gateway-enabled device from deep sleep mode and establish an HTTP tunneling session, allowing the device to access the cloud server without re-establishing a new XMPP session.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Use of energy by moving object
If the gateway-enabled device enters deep sleep mode to save energy, then energy consumption is reduced, but the device cannot receive wake-up requests from the cloud server due to firewall blocking
Solution Approach 1:
The patent introduces a management server as an intermediary that receives wake-up requests from the cloud server and forwards them to the gateway-enabled device through alternative communication channels (email, fax) that are not blocked by firewalls. This mediator enables indirect communication when direct communication is blocked, allowing the device to be woken up from deep sleep mode while maintaining energy savings.
2Reliability
If the gateway-enabled device wakes up from deep sleep mode to establish HTTP tunneling session, then communication with cloud server is enabled, but authentication and negotiation processes create excessive load on management server
Solution Approach 1:
The patent implements preliminary authentication and session establishment before the device enters deep sleep mode. The management server stores authentication results and session information, so when the device needs to wake up for HTTP tunneling, the authentication and negotiation processes have already been completed in advance, eliminating the need to repeat these processes and reducing server load.
3Productivity
If the gateway-enabled device maintains continuous communication to receive print jobs, then print job reception is ensured, but the device cannot enter deep sleep mode and energy is wasted
Solution Approach 1:
The patent implements periodic wake-up checks where the gateway-enabled device periodically wakes up from deep sleep mode to check for pending print jobs or communication requests. During these periodic wake-ups, the device can receive wake-up requests through alternative channels (email, fax) and establish HTTP tunneling sessions only when necessary, rather than maintaining continuous communication. This periodic action pattern ensures print job reception capability while allowing the device to remain in energy-saving mode most of the time.
Data Source
AI summary
A communication system includes a cloud server, a management server, a gateway-enabled device, and a printing apparatus, and these are connected to each other. The gateway-enabled device includes a mode switch that wakes up the device from power saving mode when a HTTP tunneling request is received from the cloud server via a second requesting portion of the management server, a tunneling portion that accesses the cloud server by HTTP tunneling if the request is received via a first requesting portion of the management server during normal operation mode or that does the same after back to normal operation mode if the request is received via the second requesting portion by a method allowing waking up from power saving mode, a receiver that receives a print job from the cloud server having being accessed by HTTP tunneling, and a transfer portion that transfers the print job to the printing apparatus.


