Menu
Home
People
Places
Arts
History
Plants & Animals
Science
Life & Culture
Technology
Reference.org
BatteryMAX
open-in-new
<h2 id="description">Description</h2> <p>Power saving in laptop computers traditionally relied on hardware inactivity timers to determine whether a computer was idle. It would typically take several minutes before the computer could identify idle behavior and switch to a lower power consumption state. By monitoring software applications from within the <a href="/facts/Operating_system/8XTuvMh2">operating system</a>, BatteryMAX is able to reduce the time taken to detect idle behavior from minutes to microseconds. Moreover, it can switch power states around 18 times a second between a user's keystrokes. The technique was named <i>Dynamic Idle Detection</i> and includes <a href="/facts/HLT_(x86_instruction)/3uRtLUe4">halting</a>, or stopping the <a href="/facts/CPU/Jxp1bqMV">CPU</a> for periods of just a few microseconds until a hardware event occurs to restart it. </p><p><a href="/facts/DR_DOS_5.0/GcCTKutW">DR DOS 5.0</a> in 1990 was the first <a href="/facts/Personal_computer/koaYfNce">personal computer</a> <a href="/facts/Operating_system/8XTuvMh2">operating system</a> to incorporate an idle detection system for power management.<a class="footnote-ref" id="fnref:1" href="#fn:1"><sup>1</sup></a><a class="footnote-ref" id="fnref:2" href="#fn:2"><sup>2</sup></a> It was invented by British engineers Roger Alan Gross and John P. Constant in August 1989.<a class="footnote-ref" id="fnref:3" href="#fn:3"><sup>3</sup></a> A US patent describing the idle detection system was filed on 9 March 1990 and granted on 11 October 1994.<a class="footnote-ref" id="fnref:4" href="#fn:4"><sup>4</sup></a> </p><p>Despite taking an early lead and having the protection of a patent, BatteryMAX did not enjoy significant commercial success having been sidelined after the disarray that followed the integration of Digital Research into <a href="/facts/Novell%2c_Inc./lABGMT7U">Novell, Inc.</a> in 1991. It was not until 1992, some three years after the invention, that software power management under operating system control became ubiquitous following the launch of <a href="/facts/Advanced_Power_Management/tdvVyaP5">Advanced Power Management</a> (APM) by <a href="/facts/Microsoft/nGIDDXdx">Microsoft</a> and <a href="/facts/Intel/SMF0gJJX">Intel</a>. </p> <h2 id="functional-overview">Functional overview</h2> <p>BatteryMAX uses the technique of dynamic idle detection to provide power savings by detecting what the application is doing (whether it is idle), and switching power states (entering low power mode) therefore extending the battery life of the product. </p><p>BatteryMAX employs a layered model of detection software encapsulated into an <a href="/facts/DOS/sWwDXNmX">DOS</a> character device driver called $IDLE$ that contains all the <a href="/facts/Hardware-dependent_code/bpwpz92u">hardware-dependent code</a> to support dynamic idle detection.<a class="footnote-ref" id="fnref:5" href="#fn:5"><sup>5</sup></a> It can either be linked into the DR-DOS operating system <a href="/facts/DOS_BIOS/gDj9lqoY">BIOS</a> or loaded dynamically using the <a href="/facts/CONFIG.SYS/a1QSEJhj">CONFIG.SYS</a> <a href="/facts/DEVICE_(CONFIG.SYS_directive)/a1QSEJhj">DEVICE</a> directive, overloading the built-in default driver. All versions of DR-DOS since version 5.0 have contained dynamic idle detection support inside the operating system <a href="/facts/Kernel_(operating_system)/uEj4U3Rz">kernel</a>. When the operating system believes an application is idle, it calls the $IDLE$ BIOS/driver layer, which executes custom code written by the computer manufacturer or third parties to verify the request and switch power states. Using the device driver concept, BatteryMAX can be integrated with hardware-related power management facilities, which might be provided by the underlying hardware, including interfacing with <a href="/facts/Advanced_Power_Management/tdvVyaP5">APM</a> or <a href="/facts/Advanced_Configuration_and_Power_Interface/GnLLzfyr">ACPI</a> <a href="/facts/System_BIOS/AYYPUogS">system BIOSes</a>. </p><p>Power states are computer dependent and will vary from manufacturer to manufacturer. Power savings can be made in a number of ways including slowing/stopping the processor clock speed or shutting off power to complete sub-systems. </p><p>Before switching power states, the $IDLE$ driver uses any available hardware assistance to detect if the application has been accessing other components in the system. For example, the application may be polling a serial port, or updating a graphics screen. If this is the case, the device driver determines that the application is not in fact idle and overrides the kernel's call to switch power states by passing information back up the layers and allowing application execution to resume. </p><p><a href="/facts/COMMAND.COM/06Sz5wle">COMMAND.COM</a> in DR DOS 5.0 and higher implements an internal command IDLE taking ON|OFF parameters to enable or disable the dynamic idle detection.<a class="footnote-ref" id="fnref:6" href="#fn:6"><sup>6</sup></a> </p> <h2 id="detecting-when-an-application-is-idle">Detecting when an application is idle</h2> <p>An application is idle if it is waiting for some external event to occur, for example for a keystroke or a mouse movement, or for a fixed amount of time to pass. The DR-DOS kernel monitors all DOS <a href="/facts/Application_program_interface/GMlN4vUr">API</a> calls building up a profile of the applications behavior. Certain combinations of API calls suggest that the application is idle. </p><p>The $IDLE$ driver is able to make the subtle distinction between a program that is genuinely idle, for instance one that is polling the keyboard in a tight loop, and one that is active but also polling the keyboard, to test for an abort key to be pressed. The driver makes this distinction by monitoring the time taken to go idle. If the time is within a specified period, the driver assumes that the program is idle, e.g. polling in a tight loop for a key to be pressed. If the time is outside the specified limit, the driver assumes that some processing has occurred in between polling the keyboard, and allows application execution to resume without switching power states. A local variable, IDLE_CNTDN, specifies the time against which the actual time taken to go idle is compared. The value for this variable is dynamically calculated at initialization and recalculated periodically. </p> <h2 id="origins-of-batterymax">Origins of BatteryMAX</h2> <p>The idle detection technique was first used to improve <a href="/facts/Computer_multitasking/Q4acPNMv">multi-tasking</a> of single-tasking DOS applications in Digital Research's multi-tasking/multi-user <a href="/facts/Concurrent_DOS_386/2Hh4WH3m">Concurrent DOS 386</a> (CDOS386) operating system. </p><p>Programs written for single-tasking operating systems such as MS-DOS/PC DOS can go into endless loops until interrupted; for example when waiting for a user to press a key. Whilst this is not a problem where there is no other process waiting to run, it wastes valuable processor time that could be used by other programs in a multi-tasking/multi-user environment like CDOS386. Applications designed for a multi-tasking environment use API calls to "sleep" when they are idle for a period of time but normal DOS applications do not do this so idle detection must be used. </p><p>The Concurrent DOS 386 release included an Idle Detection function in the operating system kernel which monitored <a href="/facts/DOS_API/MTvtV65u">DOS API</a> calls to determine whether the application was doing useful work or in fact idle. If it was idle, the process was suspended allowing the dispatcher to schedule another process for execution. </p> <h2 id="patent-litigation">Patent litigation</h2> <p>BatteryMAX and the "idle detection" patent played an important role in an alleged <a href="/facts/Patent_infringement/7vH9JvMF">patent infringement</a> relating to software power management under operating system control. </p><p>On 15 May 2009, St. Clair Intellectual Property Consultants. filed <a href="/facts/Lawsuit/gFeKr9ra">civil action</a> No. 09-354 in the United States District Court D. Delaware, against defendants <a href="/facts/Acer_Inc/HQ3INX1c">Acer</a>, <a href="/facts/Dell/wLlYNTMM">Dell</a>, <a href="/facts/Gateway%2c_Inc/VoMlyFsL">Gateway</a> and <a href="/facts/Lenovo/4UNdKGUU">Lenovo</a> and on 18 September 2009 filed civil action No. 09-704 against <a href="/facts/Apple_Inc/oTJYta3k">Apple</a>, and <a href="/facts/Toshiba/QHRaw8Tr">Toshiba</a> The actions alleged infringement of several U.S. patents that they owned relating to software power management under operating system control. </p><p>St. Clair asserted that Henry Fung had invented software power management under operating system control and alleged that these companies had infringed St. Clair's patents and therefore owed St. Clair <a href="/facts/Royalty_payments/8caVPHCP">royalty payments</a>. Microsoft intervened on behalf of the defendants and filed a <a href="/facts/Declaratory_judgment/29Kp0ylj">declaratory judgment</a> against St. Clair on 7 April 2010, seeking judgments of non-infringement and invalidity of the Fung patents. (D.I. 1, C.A. No. 10-282). <a href="/facts/Intel/SMF0gJJX">Intel</a> filed an intervention on behalf of the defendants and this was granted on 4 June 2010 (D.I. 178, C.A. No. 09-354). </p><p>Seattle law firm <a href="/facts/Perkins_Coie/aNfH4F6L">Perkins Coie</a>, acting for the defendants, discovered BatteryMAX and Gross's idle detection patent during a <a href="/facts/Prior_art/AEPs7QFA">prior art</a> search. Gross's patent had an earlier <a href="/facts/Priority_date/hrDRwNga">priority date</a> than Fung's patents which if proven would undermine St. Clair's case. On 28 February 2011, Gross was hired by Intel as a subject matter expert to provide <a href="/facts/Expert_witness/DxyLYY51">expert witness</a> testimony for the defendants in the case. Gross provided evidence in his <a href="/facts/Expert_report/rI3cmXYc">expert report</a> that he, not Fung, had invented software power management under operating system control and cited the Idle Detection patent and the existence of BatteryMAX as proof of this. </p><p>St. Clair filed a motion to exclude opinions concerning BatteryMAX, in an attempt to have Gross's expert report dismissed, but on 29 March 2013, the district court denied St. Clair's motion declaring Gross's testimony for the defendants as admissible,<a class="footnote-ref" id="fnref:7" href="#fn:7"><sup>7</sup></a>[<i>non-primary source needed</i>] stating that "The Court agrees with Defendants that there is sufficient corroborating evidence that BatteryMAX was available to the public prior to the Fung patents' priority date. Further, the Court concludes that even if BatteryMAX did not predate the Fung patents, Mr. Gross's testimony […] would be relevant and helpful to the fact finder in an <a href="/facts/Inventive_step_and_non-obviousness/gK88Y1ja">obviousness inquiry</a>”. </p> <h2 id="see-also">See also</h2> <ul><li><a href="/facts/Advanced_Power_Management/tdvVyaP5">Advanced Power Management</a> (APM)</li> <li><a href="/facts/Advanced_Configuration_and_Power_Interface/GnLLzfyr">Advanced Configuration and Power Interface</a> (ACPI)</li></ul> <h2 id="external-links">External links</h2> <ul><li><a href="https://web.archive.org/web/20170108132034/http://www.drdos.net/documentation/bmaxhtml/front.htm">"Implementing Power Management (BatteryMAX) in DR-DOS"</a>. <a href="/facts/Caldera%2c_Inc./kynkzN7d">Caldera, Inc.</a> 1997. Archived from <a href="http://www.drdos.net/documentation/bmaxhtml/front.htm">the original</a> on 2017-01-08. Retrieved 2017-01-08.</li></ul> <h2 id="references">References</h2> <ol> <li id="fn:1"><p>"Kompatibles PC-Betriebssystem kann mehr als MS-DOS und PC-DOS - Digital Research stellt sich dem Monopolisten mit DR-DOS 5.0". Computerwoche (in German). IDG Business Media GmbH. 1990-07-06. Archived from the original on 2019-07-25. Retrieved 2019-07-26. <a href="https://www.computerwoche.de/a/digital-research-stellt-sich-dem-monopolisten-mit-dr-dos-5-0,1146584" target="_blank">https://www.computerwoche.de/a/digital-research-stellt-sich-dem-monopolisten-mit-dr-dos-5-0,1146584</a> <a href="#fnref:1" class="footnote-back-ref">↩</a></p></li> <li id="fn:2"><p>Rosch, Winn L. (1991-02-12). "DR DOS 5.0 - The better operating system?". PC Magazine. Vol. 10, no. 3. pp. 241–246, 257, 264, 266. Archived from the original on 2019-07-25. Retrieved 2019-07-26. <a href="https://books.google.com/books?id=YxFTezF9-sMC&pg=PT246" target="_blank">https://books.google.com/books?id=YxFTezF9-sMC&pg=PT246</a> <a href="#fnref:2" class="footnote-back-ref">↩</a></p></li> <li id="fn:3"><p>Glass, Brett (1991-05-27). "DR DOS 5.0 Adds Value To Compete With The Leading Brand". InfoWorld: 91–94. Retrieved 2017-01-07. <a href="https://books.google.com/books?id=ZFAEAAAAMBAJ&pg=PT90" target="_blank">https://books.google.com/books?id=ZFAEAAAAMBAJ&pg=PT90</a> <a href="#fnref:3" class="footnote-back-ref">↩</a></p></li> <li id="fn:4"><p>US patent 5355501, Gross, Roger Alan & Constant, John P., "Idle Detection System", issued 1994-10-11 <a href="https://patents.google.com/patent/US5355501A/en" target="_blank">https://patents.google.com/patent/US5355501A/en</a> <a href="#fnref:4" class="footnote-back-ref">↩</a></p></li> <li id="fn:5"><p>Paul, Matthias R. (1997-07-30) [1994-05-01]. NWDOS-TIPs — Tips & Tricks rund um Novell DOS 7, mit Blick auf undokumentierte Details, Bugs und Workarounds. Release 157 (in German) (3 ed.). Archived from the original on 2017-09-10. Retrieved 2014-08-06. {{cite book}}: |work= ignored (help) (NB. NWDOSTIP.TXT is a comprehensive work on Novell DOS 7 and OpenDOS 7.01, including the description of many undocumented features and internals. It is part of the author's yet larger MPDOSTIP.ZIP collection maintained up to 2001 and distributed on many sites at the time. The provided link points to a HTML-converted older version of the NWDOSTIP.TXT file.) [1] <a href="http://www.antonis.de/dos/dos-tuts/mpdostip/html/nwdostip.htm" target="_blank">http://www.antonis.de/dos/dos-tuts/mpdostip/html/nwdostip.htm</a> <a href="#fnref:5" class="footnote-back-ref">↩</a></p></li> <li id="fn:6"><p>Paul, Matthias R. (1997-04-13) [1993-12-01]. Zusammenfassung der dokumentierten und undokumentierten Fähigkeiten von DR DOS 6.0 [Summary of documented and undocumented features of DR DOS 6.0]. Release 60 (in German). Archived from the original on 2018-10-11. Retrieved 2019-08-14. {{cite book}}: |work= ignored (help) [2] <a href="http://www.antonis.de/dos/dos-tuts/mpdostip/html/drdos6un.htm" target="_blank">http://www.antonis.de/dos/dos-tuts/mpdostip/html/drdos6un.htm</a> <a href="#fnref:6" class="footnote-back-ref">↩</a></p></li> <li id="fn:7"><p>"In the United States District Court for the District of Delaware - Civil Action No. 09-354-LPS consolidated: St. Clair Intellectual Property Consultants, Inc. (Plaintiff) vs. Acer Inc. et al. (Defendants); Civil Action No. 10-282-LPS: Microsoft, Inc. (Plaintiff) vs. St. Clair Intellectual Property Consultants, Inc. (Defendant)" (PDF) (Memorandum order). 2013-03-29. Archived from the original (PDF) on 2016-12-30. <a href="https://web.archive.org/web/20161230030023/http://www.ded.uscourts.gov/sites/default/files/opinions/lps/2013/march/09-354_2.pdf" target="_blank">https://web.archive.org/web/20161230030023/http://www.ded.uscourts.gov/sites/default/files/opinions/lps/2013/march/09-354_2.pdf</a> <a href="#fnref:7" class="footnote-back-ref">↩</a></p></li> </ol>