The patent badge is an abbreviated version of the USPTO patent document. The patent badge does contain a link to the full patent document.
The patent badge is an abbreviated version of the USPTO patent document. The patent badge covers the following: Patent number, Date patent was issued, Date patent was filed, Title of the patent, Applicant, Inventor, Assignee, Attorney firm, Primary examiner, Assistant examiner, CPCs, and Abstract. The patent badge does contain a link to the full patent document (in Adobe Acrobat format, aka pdf). To download or print any patent click here.
Patent No.:
Date of Patent:
Aug. 27, 2019
Filed:
May. 15, 2017
Microsoft Technology Licensing, Llc, Redmond, WA (US);
Iulian Calinov, Sammamish, WA (US);
Sandeep Prabhakar, Bellevue, WA (US);
Samarth Shah, Seattle, WA (US);
Jihad Tafas, Redmond, WA (US);
Zachary Sandburg Holmes, Redmond, WA (US);
Tapan Ansel, Redmond, WA (US);
Gabriel Knezek, Seattle, WA (US);
Paresh Maisuria, Issaquah, WA (US);
James Kennyth Truckle, Redmond, WA (US);
Rahul Nair, Bellevue, WA (US);
Taofiq Ezaz, Redmond, WA (US);
Microsoft Technology Licensing, LLC, Redmond, WA (US);
Abstract
Consumption of power by device components is profiled on a per-session basis of user interaction. A session engine determines start of a user interaction session with the device (e.g., by detecting screen turn on). The engine generates a session identifier (SID) and broadcasts same to device component(s). In response to the SID, the component(s) record power consumption data. Upon receiving a signal indicating end of the user interaction session (e.g., screen turn off), the session engine broadcasts a notice allowing component(s) to stop recording power consumption data. The components communicate aggregated data to the session engine for storage in a centralized location (e.g., trace buffer). In response to a query posed within a command line prompt, stored data may be parsed on a per-session basis for inclusion in a detailed report of power consumption. Power consumption inefficiencies endemic to components and/or user behaviors may be thus be identified and remediated.