System and method for controlling the power states of a mobile computing device

• US 10,372,923 B2
• Filed: 08/24/2018
• Issued: 08/06/2019
• Est. Priority Date: 01/09/2018
• Status: Active Grant

• Current Assignee: BOOZ Allen Hamilton Holding Corporation
• Original Assignee: BOOZ Allen Hamilton Holding Corporation
• Inventors: Myers, Gary Jason, Welsh, Matthias, Knight, Robert Wayne, Schaefer, Timothy
• Primary Examiner(s): Chen, Shin-Hon (Eric)
• Application Number:
  US16/112,100
• Publication Number:
  US 20190213339A1
• Time in Patent Office: 347 Days
• Field of Search: None
• CPC Class Codes: G06F 1/3203 Power management, i.e. event-based initiation of a power-saving mode
• CPC Class Codes: G06F 1/3209 Monitoring remote activity, e.g. over telephone lines or network connections
• CPC Class Codes: G06F 21/572 Secure firmware programming, e.g. of basic input output system [BIOS]
• CPC Class Codes: G06F 21/575 Secure boot
• CPC Class Codes: G06F 21/604 Tools and structures for managing or administering access control systems
• CPC Class Codes: G06F 21/62 Protecting access to data via a platform, e.g. using keys or access control rules
• CPC Class Codes: G06F 21/81 by operating on the power supply, e.g. enabling or disabling power-on, sleep or resume operations
• CPC Class Codes: G06F 2221/2139 Recurrent verification
• CPC Class Codes: G06F 2221/2143 Clearing memory, e.g. to prevent the data from being stolen
• CPC Class Codes: G06K 19/0723 the record carrier comprising an arrangement for non-contact communication, e.g. wireless communication circuits on transponder cards, non-contact smart cards or RFIDs

Abstract

An exemplary mobile computing device, including a memory device for storing a control policy defining a functional configuration of the mobile computing device; and a processor configured to place the mobile computing device in one of one of plural states based on a validation result of the control policy.

Claims

1. The mobile computing device, comprising:

a memory device for storing a control policy defining a functional configuration of the mobile computing device;

a processor configured to place the mobile computing device in one of plural states based on a validation result of the control policy; and

a power controller configured for controlling a power state of the mobile computing device; and

an interface for communicating with remote devices on a network,

wherein the processor is configured to execute an operating system runtime policy module (OSRPM) for retrieving the control policy from a remote device on the network, storing the control policy in the memory device when retrieved from the remote device, executing a power control module for communicating with the power controller, and evaluating the control policy for expired, corrupted, or malicious instructions,

wherein when the control policy is valid, the processor is configured to;

determine, via the OSRPM, whether the control policy allows a power on state; and

when the control policy allows a power on state, keep the power controller in a power on state;

or

when the control policy does not allow the power on state;

control the power controller to enter a power off state and stop communication between the OSRPM and the power control module; and

force the power controller to power off via the power control module.

2. The mobile computing device according to claim 1, wherein:

when the control policy is not valid, the processor is configured to;

determine whether a wipe threshold is expired; and

when the wipe threshold is exceeded;

dump encryption keys from trusted memory and initiating a disk wipe;

or

when the wipe threshold is not exceeded;

control the power controller to enter a power off state.

3. The mobile computing device according to claim 1, wherein if the control policy is not valid, the processor is configured to determine whether a wipe threshold is expired via the power control module, and if the wipe threshold is expired, the processor is configured to:

execute the OSRPM to initiate a reboot of the mobile computing device and stop communication with the power control module;

execute the boot control program;

initiate a first firmware application in the boot control program; and

dump encryption keys from trusted memory and initiate a disk wipe via the first firmware application.

4. The mobile computing device according to claim 1, wherein:

when the control policy is valid, the processor is configured to;

determine whether a valid control policy allows boot up of the mobile computing device; and

when boot up is allowed;

initiate an operating system (OS) application;

or

when boot up is not allowed;

control the power controller to enter a power off state.

5. A method of controlling a power state of a mobile computing device, the mobile computing device having a memory device, a processor configured to execute the method via at least one of a plurality of programming modules, and an interface for communicating with remote devices on a network and the plurality of programming modules includes a boot control program for execution by the processor, the method comprising:

storing a control policy in the memory device, the control policy defining a functional configuration of the mobile computing device;

retrieving the control policy from the memory device for validation;

placing the mobile computing device in one of plural states based on whether the control policy is valid;

executing the boot control program to initiate boot up of the mobile computing device;

executing a first firmware application in a boot sequence of the boot control program;

establishing communication with a remote device on the network via the first application;

receiving the control policy from the remote device; and

storing the control policy in the memory device,

wherein validation of the control policy via the first firmware application comprises;

retrieving the control policy from the memory device; and

determining whether the control policy includes at least one of expired, corrupted, and malicious instructions,

wherein when the control policy is valid, the processor is configured to;

determine, via the OSRPM, whether the control policy allows a power on state; and

when the control policy allows a power on state;

 

keep the power controller in a power on state;

or

when the control policy does not allow the power on state;

 

control the power controller to enter a power off state and stop communication between the OSRPM and the power control module; and

 

force the power controller to power off via the power control module.

6. The method according to claim 5, wherein if the control policy is not valid, the method comprising:

determining whether a wipe threshold has expired;

when the wipe threshold has expired;

dumping encryption keys from trusted memory via the first firmware application; and

initiating a disk wipe via the first firmware application;

or

when the wipe threshold has not expired;

forcing a power off of the mobile computing device via the first firmware application if the control policy is not valid.