Embedded Controller Command Retrieval Across Power States
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Managing mobile computing devices that roam between networks and frequently enter low-powered states, making them unreachable and unmanageable due to the management server's inability to locate them reliably and the processor's reduced functionality.
Innovation Solution
A controller within the computing device determines if the processor is in a low-powered state and establishes a network connection to a management server to retrieve commands independently, allowing for remote management across various networks and power states.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Use of energy by moving object
If the processor enters a low-powered state to conserve energy, then energy consumption is reduced, but the device becomes unreachable and unmanageable by the management server
Solution Approach 1:
The system divides the computing device into two independent operational paths: a low-powered processor state for energy conservation and a management server communication path that operates independently through alternative hardware components (such as a coprocessor or embedded controller) to maintain manageability without requiring the main processor to be fully active
Solution Approach 2:
An intermediary component (such as an embedded controller, coprocessor, or management engine) is introduced that can independently handle communication with the management server when the main processor is in a low-powered state, acting as a mediator between the powered-down processor and the network management infrastructure
2Reliability
If the processor remains active to maintain manageability, then the device remains reachable by the management server, but energy consumption increases
Solution Approach 1:
The system segments management functions from main processor operations, allowing the processor to enter low-powered states while dedicated management hardware (embedded controller, coprocessor) handles server communications independently, eliminating the need to keep the main processor active for manageability
Solution Approach 2:
The system implements periodic or on-demand activation of the processor only when management commands require execution, while the intermediary component maintains continuous or periodic communication with the management server, reducing overall processor active time and energy consumption
3Reliability
If the device roams between networks to maintain connectivity, then network availability is improved, but the complexity of network location and management increases
Solution Approach 1:
The embedded controller or coprocessor acts as an intermediary that maintains network connectivity and communicates with the management server independently of the main processor's network state, simplifying the overall system's ability to be located and managed across networks without requiring complex processor-level network management
Solution Approach 2:
The intermediary component performs preliminary network registration and maintains presence information with the management server before the main processor becomes active, ensuring the device is locatable and manageable on the network before full system operations begin
Data Source
AI summary
Examples herein disclose establishing a connection from a controller in a computing device to a management server over a network. The examples retrieve a command from the management server.