Patent Publication Number: US-2004047095-A1

Title: Method and/or system and/or apparatus for multiple interface remotely configurable power supply

Description:
CROSS REFERENCE TO RELATED APPLICATIONS  
     [0001] This application claims priority from provisional patent application No. 60/378,342, filed May 6, 2002, incorporated herein by reference. 
    
    
     
       COPYRIGHT NOTICE  
       [0002] Pursuant to 37 C.F.R. 1.71(e), Applicants note that a portion of this disclosure contains material that is subject to and for which is claimed copyright protection (such as, but not limited to, source code listings, screen shots, user interfaces, or user instructions, or any other aspects of this submission for which copyright protection is or may be available in any jurisdiction.). The copyright owner has no objection to the facsimile reproduction by anyone of the patent document or patent disclosure, as it appears in the Patent and Trademark Office patent file or records. All other rights are reserved, and all other reproduction, distribution, creation of derivative works based on the contents, public display, and public performance of the application or any part thereof are prohibited by applicable copyright law.  
       FIELD OF THE INVENTION  
       [0003] This invention relates to electronic circuits. More particularly, the invention relates to a method and apparatus for an intelligent power supply that provides novel features.  
       BACKGROUND OF THE INVENTION  
       [0004] Early in the development of modem networking equipment such as routers, it was realized that at times a particular piece of network equipment might hang or “crash.” In such instances, a human operator often had to intervene by traveling to the location of the equipment and rebooting or power cycling the equipment in order to get that particular piece of equipment working. Power cycling and information about consumed power are also of interest in a number of computer equipment and other equipment settings.  
       [0005] The discussion of any work, publications, sales, or activity anywhere in this submission, including in any documents submitted with this application, shall not be taken as an admission that any such work constitutes prior art. The discussion of any activity, work, or publication herein is not an admission that such activity, work, or publication existed or was known in any particular jurisdiction.  
       SUMMARY OF THE INVENTION  
       [0006] The present invention relates to a method and/or system and/or apparatus for providing new capabilities in power supply and/or power cycling management. In specific embodiments, the invention involves a method and/or system and/or apparatus for remotely managing and monitoring a power supply over two or more different interfaces including, for example, a telephone interface and/or a network-based (e.g., HTTP, SNMP) interface and/or a serial interface. In further embodiments, the invention involves one or methods that may be implemented using a data handling device or system, such as a computer or other information enabled device. In further embodiments, the invention involves methods and/or systems for power management over a communication network and/or telephone network.  
       [0007] Various strategies have been proposed for performing remote power switching and/or management and/or performing intelligent scheduling of the turning on and turning off of power cycling. According to specific embodiments, the present invention is involved with methods and/or systems and/or devices that can be used together or independently to monitor and/or control power supplies. In specific embodiments, the present invention can be understood as involving new methods related to power management.  
       [0008] A smart power supply according to specific embodiments of the invention further includes one or more novel features such as: individual current monitoring of power outlets; user adjustable stagger starting and/or outlet scheduling; and text-based menu drive telnet and serial interface.  
       [0009] The invention and various specific aspects and embodiments will be better understood with reference to the following drawings and detailed descriptions. For purposes of clarity, this discussion refers to devices, methods, and concepts in terms of specific examples. However, the invention and aspects thereof may have applications to a variety of types of devices and systems. It is therefore intended that the invention not be limited except as provided in the attached claims and equivalents.  
       [0010] Furthermore, it is well known in the art that logic systems and methods such as described herein can include a variety of different components and different functions in a modular fashion. Different embodiments of the invention can include different mixtures of elements and functions and may group various functions as parts of various elements. For purposes of clarity, the invention is described in terms of systems that include many different innovative components and innovative combinations of innovative components and known components. No inference should be taken to limit the invention to combinations containing all of the innovative components listed in any illustrative embodiment in this specification.  
       [0011] In some of the drawings and detailed descriptions below, the present invention is described in terms of the important independent embodiment of a system operating on a digital data network. This should not be taken to limit the invention, which, using the teachings provided herein, can be applied to other situations, such as cable television networks, wireless networks, etc. Furthermore, in some aspects, the present invention is described in terms of client/server systems. A number of computing systems and computing architectures are described in the art as client/server art. For the purposes of this description, client/server should be understood to include any architecture or configuration wherein an element acting as a client accesses a remote and/or separate program or device that is providing the desired service (e.g., a server).  
       [0012] All references, publications, patents, and patent applications cited herein are hereby incorporated by reference in their entirety for all purposes. 
     
    
    
     BRIEF DESCRIPTIONS OF THE DRAWINGS  
     [0013]FIG. 1 is a block diagram illustrating an example initial serial interface and method according to specific embodiments of the present invention.  
     [0014]FIG. 2 is a block diagram illustrating an example serial settings interface and method according to specific embodiments of the present invention.  
     [0015]FIG. 3 is a block diagram illustrating an example serial time/date interface and method according to specific embodiments of the present invention.  
     [0016]FIG. 4 is a block diagram illustrating an example serial network interface and method according to specific embodiments of the present invention.  
     [0017]FIG. 5 is a block diagram illustrating an example serial telephone interface and method according to specific embodiments of the present invention.  
     [0018]FIG. 6 is a block diagram illustrating an example email interface and method according to specific embodiments of the present invention.  
     [0019]FIG. 7 is a block diagram illustrating an example user settings interface and method according to specific embodiments of the present invention.  
     [0020]FIG. 8 is a block diagram illustrating an example user modification interface and method according to specific embodiments of the present invention.  
     [0021]FIG. 9 is a block diagram illustrating an example initial web-based interface and method according to specific embodiments of the present invention.  
     [0022]FIG. 10 is a block diagram illustrating an example outlet scheduling interface and method according to specific embodiments of the present invention.  
     [0023]FIG. 11 is a block diagram illustrating an example outlet label and properties modification interface and method according to specific embodiments of the present invention.  
     [0024]FIG. 12 is a block diagram illustrating an example logging interface and method according to specific embodiments of the present invention.  
     [0025]FIG. 13 is a block diagram illustrating an example user interface and method according to specific embodiments of the present invention.  
     [0026]FIG. 14 is a block diagram illustrating an example user modification interface and method according to specific embodiments of the present invention.  
     [0027]FIG. 15 is a block diagram illustrating an example web-based setup interface and method according to specific embodiments of the present invention.  
     [0028]FIG. 16 is a block diagram illustrating an example network identification interface and method according to specific embodiments of the present invention.  
     [0029]FIG. 17 is a block diagram illustrating an example telephone setup interface and method according to specific embodiments of the present invention.  
     [0030]FIG. 18 is a block diagram illustrating an example logging setup interface and method according to specific embodiments of the present invention.  
     [0031]FIG. 19 is a block diagram illustrating an example date/time setup interface and method according to specific embodiments of the present invention.  
     [0032]FIG. 20 is a block diagram illustrating an example SNMP setup interface and method according to specific embodiments of the present invention.  
     [0033]FIG. 21 is a block diagram illustrating an example options setup interface and method according to specific embodiments of the present invention.  
     [0034] FIGS.  22 A-B is a diagram illustrating an example of external features and appearance of an example three connector configurable power supply according to specific embodiments of the present invention.  
     [0035] FIGS.  23 A-B is a diagram illustrating an example of external features and appearance of an example two connector power supply according to specific embodiments of the present invention.  
     [0036]FIG. 24 is a block diagram illustrating an example logic modules of a configurable power supply according to specific embodiments of the present invention.  
     [0037] FIGS.  25 A-B is a block diagram illustrating in further details major functional components of an example configurable power supply according to specific embodiments of the present invention.  
     [0038]FIG. 26 is a block diagram illustrating details a microcontroller and other control logic of an example configurable power supply according to specific embodiments of the present invention.  
     [0039]FIG. 27 is a block diagram illustrating details of three power relays of an example configurable power supply according to specific embodiments of the present invention.  
     [0040] FIGS.  28 A-B is a block diagram illustrating details of three current sensors of an example configurable power supply according to specific embodiments of the present invention.  
     [0041]FIG. 29 is a block diagram showing a representative example logic device in which various aspects of the present invention may be embodied. 
    
    
     DESCRIPTIONS OF SPECIFIC EMBODIMENTS  
     [0042] According to specific embodiments, the present invention can be embodied into an example power switch product, sometimes referred to as the SPS (Smart Power Switch)™ power controller. In specific embodiments, a device built according to specific embodiments of the invention can include three different interfaces, such as, for example, serial, telephone, network. Such embodiments may be referred to here as the TriCom™ or the Tri-n (with n indicated the number of controlled outlets provided and tri indicated the presence of three interfaces, e.g., Tri-8™). In other embodiments, a device built according to specific embodiments of the invention can include two different interfaces, such as, for example, serial/telephone or serial/network or telephone/network. Such embodiments may be referred to herein as the DualCom™ or the Dual-n (with n indicated the number of controlled outlets provided and tri indicated the presence of three interfaces.  
     [0043] 1. Interfaces  
     [0044] Thus, a device according to specific embodiments of the present invention is a power distribution unit that utilizes multiple different modes of communication. In particular embodiments, an SPS can be accessed via serial, Ethernet or direct phone. These interfaces can provided either identical functionality or functionality can vary for different interfaces. For example, through the serial and Ethernet interfaces a user can determine and change the state of each outlet, determine the amount of current that each outlet is drawing, and add or modify scheduled on/off events on outlets. In specific embodiments, all of these functions can be performed in real time.  
     [0045] Serial Interface  
     [0046] According to specific embodiments of the present invention, a serial interface uses a standard serial port protocol, so that any information devices (e.g., a laptop, personal computer, or digital controller) with an available corn or com-like port can use this direct connection to the SPS. The serial port can also be used as an initial setup port for the unit. The serial interface can also be an USB-type serial interface.  
     [0047] Other interfaces according to specific embodiments of the present invention are generally setup before they are used. Generally, after initialization, all the settings can be managed through the serial or Ethernet ports.  
     [0048] Ethernet and Network Interface  
     [0049] According to specific embodiments of the present invention, an Ethernet port can be utilized either through a text based Telnet session or through an HTTP web interface. The telnet session is similar to the serial interface in that its text based and the menus can generally be very similar or identical. A web interface according to specific embodiments of the invention can, for example, utilizes a web browser and the Hypertext Transfer Protocol (HTTP). According to specific embodiments of the present invention, this interface looks and feels different from the others because it is a GUI (graphical user interface). An SNMP interface can be used to control various settings and retrieve various information from the SPS using a standard network management protocol, such as SNMP.  
     [0050] Email Interface  
     [0051] In addition, the SPS can be configured to email logged events. When this feature is enabled, according to specific embodiments of the present invention, a running log of events is kept and once memory is filled, the log file is sent to a designated email address. Logs can contain information such as the user name, which outlets were changed, time and date of event, and interface and or IP address used.  
     [0052] Telephone Interface  
     [0053] According to specific embodiments of the present invention, a telephone interface uses a standard analog phone line. This interface is unique in that it uses a few inexpensive parts (such as, for example, a Clare™ CPC5611 as the data access arrangement and a Sunplus™ SPC122a as the voice processor) along with a few other parts. An SPS according to specific embodiments of the present invention has DTMF decoding, caller id, and voice feedback. Once enabled and attached to a phone line, the unit is now ready to receive and process calls. The SPS can be set to accept all calls, block calls without caller ID enabled, or not accept any incoming calls. The SPS is designed so that if a user uses the phone interface he or she is greeted with a voice prompted menu. The unit will ask for a numeric pass code and then prompt the user for the next command. In specific embodiments, though the SPS has a voice prompted menu, it will only respond to (DTMF) telephone tones as commands and not to speech. In further embodiments, speech recognition can be included in a device according to the invention.  
     [0054] An embedded hardware arrangement along with its caller id and voice feedback capabilities according to specific embodiments of the present invention has never been utilized in the present combination in any comparable smart power switch or power distribution units. This interface is not included in all embodiments of the invention.  
     [0055] Interface Features and Functions  
     [0056] According to specific embodiments of the present invention, the serial and/or Ethernet interfaces have the ability to:  
     [0057] change the state of outlets  
     [0058] assign outlet labels  
     [0059] assign outlet schedule  
     [0060] edit and assign users  
     [0061] edit network, email, and phone interface settings.  
     [0062] A wide variety of configurations are possible according to various specific embodiments of the present invention. Some of these configurations are described herein as examples of the invention. Various configuration details are also elements in novel embodiments of the invention.  
     [0063] According to specific embodiments of the present invention, different features may be accessible from different interfaces. Table 1 below provides an example feature set indicating particular interfaces according to specific embodiments of the present invention.  
                                       TABLE 1                                   TCP/IP-WEB   TCP/IP-TELNET   TCP/IP-SNMP   SERIAL   PHONE                                                            Switch outlets on and off   •   •   •   •   •       Monitor outlet on/off status   •   •   •   •   •       Monitor current consumption of each outlet   •   •   •   •       Program outlet schedules   •       •       Protect with Password/PIN security   •   •   •   •   •       Control outlet access with users and passwords   •   •   •   •       Manage users   •   •   •   •       Control multiple units from a single           •                  
 
     [0064] 2. Per Outlet Current Monitoring  
     [0065] According to specific embodiments of the invention, the invention provides per-outlet current monitoring for a plurality of controlled outlets. In particular embodiments, this novel feature is integrated into the user interfaces as provided herein.  
     [0066] Per-outlet current monitoring according to specific embodiments of the invention provides a mechanism of remotely managing current load on a individual device basis.  
     [0067] 3. User-Controllable Scheduling  
     [0068] According to specific embodiments of the invention, the invention features user-controllable scheduling of each outlet. While other power devices have provided various staged power up operation, the present invention allows a user to flexible manage scheduling features.  
     [0069] 4. Detailed Interface Examples and operation  
     [0070] Many different particular arrangements of menus and functions are possible according to specific embodiments of the invention. In order to provide a complete description of example methods of operation according to specific embodiments of the invention, the following describes specific example menus and methods of one or more systems according to the invention.  
     [0071] Example Serial Connection Interfaces  
     [0072] In specific embodiments, the invention includes a set of interfaces for a direct serial connection. The discussion below and the referenced figures provide specific example embodiments of such interfaces.  
     [0073] Initialize:  
     [0074]FIG. 1 provides an example of an initial serial interface screen. An example configuration and method of this screen is as follows. Using an appropriate serial cable attached between an SPS according to specific embodiments of the invention and an information screen, such as a terminal or PC, start a Hyper Terminal type session. For example, a connection can be made to COM 1 with the settings: 19200 bit rate, 8 data bits, parity=none, stop bits=1, and Flow control=none.  
     [0075] Once connected, log on with a user name and password. Once logged in type 0 for editing outlet states, 1 to view logs or 2 to edit settings.  
     [0076] Edit Settings  
     [0077]FIG. 2 provides an example settings menu according to specific embodiments of the invention. In the settings menu a user can set such things as Time/Date, Network Settings, E-mail Settings, and Manage Users. For example, to edit a category a user can use arrow keys or a mouse to select the category or type a corresponding number or letter for the listed function. Note, in a Dual-Com, for example, either the network settings or phone setting may not be present.  
     [0078] Settings Time/Date:  
     [0079]FIG. 3 provides an example time/date settings menu according to specific embodiments of the invention. This interface can be used by, for example, scrolling to the proper heading and pressing enter to change a value and once the values have been changed press enter to finalize.  
     [0080] Settings Network:  
     [0081]FIG. 4 provides an example network settings menu according to specific embodiments of the invention. This interface can be used by, for example, scrolling to the proper heading and pressing enter to change a value and once the values have been changed press enter to finalize. This procedure may be repeated for all network settings. Network settings can include such things as values for IP addressing, host and/or domain names, enablement of DHCP, SNMP, or other functions, etc. In specific embodiments, once all network settings have been made the Tricom must be rebooted in order for the new settings to take affect.  
     [0082] According to specific embodiments of the invention, seven settings are provided here: Enable DHCP (This is set to on as default so that if there is a a DHCP server the SPS will get it&#39;s IP address from it. If so it will show up under the Using: section and it will be different than 192.168.1.2 [the default if no DHCP Server is found].); IP; Subnet Mask; DNS; Gateway; Host; and Domain.  
     [0083] Settings Telephone:  
     [0084]FIG. 5 provides an example telephone settings menu according to specific embodiments of the invention. This interface can be used by, for example, scrolling to the proper heading and pressing enter to change a value. Telephone settings can include such things as values for a phone personal identification number (PIN) and/or enablement of various telephone functions. In embodiments without a telephone interface, this menu may not be available.  
     [0085] Settings Email:  
     [0086]FIG. 6 provides an example email settings menu according to specific embodiments of the invention. This interface can be used by, for example, scrolling to the proper heading and pressing enter to change a value. Email settings can include such things as values for a email address and/or server and/or email heading values and/or and/or enablement of various email functions. In embodiments without an email interface, this menu may not be available.  
     [0087] Settings Users:  
     [0088]FIG. 7 provides an example initial user settings menu and FIG. 8 provides an example user modification settings menu according to specific embodiments of the invention. This interface can be used by, for example, scrolling to the proper heading and pressing enter to change a value. User settings can include such things as user names, passwords, administrator indications, permissions. Permissions can include individual outlet modification permissions.  
     [0089] Example Web Connection Interfaces  
     [0090] In specific embodiments, the invention includes a set of interfaces for a web-based connection. The discussion below and the referenced figures provide specific example embodiments of such interfaces. Once a network port (such as Ethernet) has been configured with the proper addressing, a user can access a SPS according to specific embodiments of the present invention through such things as a telnet session or through a web browser. According to specific embodiments of the invention, the Telnet session is text based and menu driven and has the same look and feel as the serial connection described above. A web interface is optimized for use in all web browsers, such as Internet Explorer.  
     [0091] To begin using the web interface, start a web browser and input an SPS&#39;s network identification (e.g., an IP and/or domain name address) Once found, an example SPS can prompt for a log on, for example using a popup window requesting a user name and password or alternatively, by retrieving saved passwords.  
     [0092]FIG. 9 provides an example of web-based interface screen according to specific embodiments of the invention. This example figure shows a number of different possible functionalities according to specific embodiments of the invention.  
     [0093] For example, the four underlined links at the top of the interface can have the following functions:  
     [0094] OUTLETS: change the state of outlets, setup scheduling, rename outlets and view current draw (e.g., amperage) per outlet.  
     [0095] LOGS: shows previous events (e.g., the last 30) that have occurred.  
     [0096] USERS: add, edit and delete users to the unit  
     [0097] SETUP: network, time/date and preference settings. Generally, only users with administrator privilege&#39;s can access the setup and users tabs.  
     [0098] According to specific embodiments of the invention, outlet management can be handled as follows. To change the state of any outlet simply click the outlet indication on or off. A round indicator button can provide a color indication of outlet status, e.g., green indicating that the outlet is on and white indicating that the outlet is off. To rename an outlet, click on a label given to the outlet, e.g., “Com Server 2” and in either a popup box or the link enter the new name then click Save Label. Generally, according to specific embodiments of the invention, unless a user is an administrator, the user&#39;s selection of outlets is limited to what your administrator has assigned. Common users also have no access to logs, users, and setup.  
     [0099] According to specific embodiments of the invention, scheduling for individual outlets can be performed as follows. To set a scheduled task select, for example, a clock icon that corresponds to the outlet for which it is desired to set the schedule. FIG. 10 is a block diagram illustrating an example outlet scheduling interface and method according to specific embodiments of the present invention. Once the outlet is selected, add events by for example changing time, day and then clicking on the Add Event button. Before clicking the Save Schedule Options button, click in the box that indicates scheduling is enabled for this outlet.  
     [0100]FIG. 11 is a block diagram illustrating an example outlet label and properties modification interface and method according to specific embodiments of the present invention. This interface can be used to change outlet labels and adjust other outlet properties.  
     [0101]FIG. 12 is a block diagram illustrating an example logging interface and method according to specific embodiments of the present invention. According to specific embodiments of the invention, an SPS keeps a running log of events which, if enabled, can be e-mailed to a designated person. For example, in specific embodiments, once the log file is filled the log is then e-mailed and the memory buffer is then cleared and refreshed. If not setup to E-mail, the unit will then overwrite the oldest event, keeping the log current. Logs may generally also be sent or cleared manually be clicking an appropriate heading that can be provided in specific embodiments.  
     [0102]FIG. 13 is a block diagram illustrating an example user interface and method according to specific embodiments of the present invention. To access the users tab generally a user has to be an administrator. To add or edit an existing user click edit in the row desired. In the popup box enter a user name, password and select the outlets the new user will be able to access. Once the information is complete click the Save User button and the user may now log in. To completely remove a user, indicate delete. FIG. 14 is a block diagram illustrating an example user modification interface and method according to specific embodiments of the present invention.  
     [0103]FIG. 15 is a block diagram illustrating an example web-based setup interface and method according to specific embodiments of the present invention. This interface provides information about such things as time/date, network settings, logging settings, SNMP settings, can also provide information about telephone settings in an SPS with a telephone interface. Generally, this interface is only accessible to administrators. To make changes using this interface, use the edit button that corresponds to the appropriate heading. For example, to set TIME/DATE, click the corresponding edit button, make the proper changes then click Save.  
     [0104]FIG. 16 is a block diagram illustrating an example network identification interface and method according to specific embodiments of the present invention. This interface can, for example, be provided as a popup box from the overall settings interface. In this interface, enter the IP address to assign to the unit. Enter the units Subnet Mask, DNS, host, and domain name. Once all fields are filled in, click the Save and Reboot button. Generally, network settings will not take affect until the unit has been rebooted.  
     [0105]FIG. 17 is a block diagram illustrating an example telephone setup interface and method according to specific embodiments of the present invention. To setup the telephone interface, click on the corresponding edit button. By placing a check mark in the “enable interface” box, all calls will be processed by the Tricom. However, if there is no check mark at “Allow callers with no caller ID” the unit will then only answer calls with a caller ID tag and reject all others.  
     [0106] In SPS units with a telephone interface, enabled as described above, the physical interface according to specific embodiments of the present invention can be connected using a standard analog phone line to the phone jack on the front panel of the SPS. Once connected to an analog phone line and the interface is enabled, the SPS can now be reached and controlled independently from a network or a computer. From an office desk phone to a private cell phone, there is a truly remote means of control. The SPS can be configured to block calls from restricted or unavailable phones. The phone number of the telephone from which a user is calling from must be received by the SPS in order to access the main menu. According to specific embodiments of the present invention, a system can be configured to “Allow callers with no caller ID,” though due to security reasons this is not recommended.  
     [0107]FIG. 18 is a block diagram illustrating an example logging setup interface and method according to specific embodiments of the present invention. Under the Logging heading administrators can setup E-mail properties and server settings. To enable the E-mail logs feature click the corresponding edit button. In the popup box, enter the SMTP server name as well as the E-mail address of the person to receive the logs. The “From” and “Subject” boxes are not required to send the log as well as fill in the “From” and “Subject” boxes. Once all entries and the “Dump logs to E-mail . . . ” box is checked, click the save button. The unit is now ready to send the log once the buffer is full. According to specific embodiments of the present invention, the SMTP server acts as an outgoing E-mail server. If you don&#39;t have this information please consult your network administrator. With out the proper SMTP server, the unit will not be able to E-mail out the logs regardless of all the other settings.  
     [0108]FIG. 19 is a block diagram illustrating an example date/time setup interface and method according to specific embodiments of the present invention. To configure the NTP settings with an NTP Server addressing delete the default settings and ensure that there is a check in the “Enable NTP” checkbox. Once settings are entered a user can indicate “Save” and the page will refresh with the new time/date that the SPS received from the local NTP servers. To manually set “Time/Date” uncheck the “Enable NTP” check box, though it is highly recommend use an NTP server.  
     [0109]FIG. 20 is a block diagram illustrating an example SNMP setup interface and method according to specific embodiments of the present invention. SNMP is by default set to enabled which may cause a security risk. It is therefore suggested to set this to disabled if not used. The MIB listing below provides additional information about a specific example SNMP interface according to specific embodiments of the present invention.  
     [0110]FIG. 21 is a block diagram illustrating an example options setup interface and method according to specific embodiments of the present invention. This interface can be provided to change behavioral settings such as refresh rates and outlet change confirmations. To avoid accidental on/offs, require confirmation for each on/off event on the web by placing a check in the Require confirmation box. With this feature enabled users will have to click on or off then OK or cancel for each outlet change. The Refresh rate is user definable from 1-999 seconds. Once set the Outlets page will now refresh to the specified time. If the refresh rate is set too fast, the system may not have enough time to load the entire page. Regardless of the refresh rate setting the network speed will determine how fast a page is loaded. A default example setting is at 10 seconds.  
     [0111] Software Implementations  
     [0112] Thus, in further embodiments, the present invention may be understood in the context of providing power management over a communication media. An important application for the present invention, and an independent embodiment, is in the field of providing power cycling and monitoring over the Internet, optionally using Internet media protocols and formats, such as HTTP, RTTP, XML, HTML, dHTML, VRML, as well as image, audio, or video formats etc. However, using the teachings provided herein, it will be understood by those of skill in the art that the methods and apparatus of the present invention could be advantageously used in other related situations where users access content over a communication channel, such as modem access systems, institution network systems, wireless systems, etc.  
     [0113] Various embodiments of the present invention provide methods and/or systems for power management and/or monitoring that can be implemented on a general purpose or special purpose information handling appliance using a suitable programming language such as Java, C++, Cobol, C, Pascal, Fortran., PL1, LISP, assembly, etc., and any suitable data or formatting specifications, such as HTML, XML, dHTML, TIFF, JPEG, tab-delimited text, binary, etc. In the interest of clarity, not all features of an actual implementation are described in this specification. It will be understood that in the development of any such actual implementation (as in any software development project), numerous implementation-specific decisions must be made to achieve the developers&#39; specific goals and subgoals, such as compliance with system-related and/or business-related constraints, which will vary from one implementation to another. Moreover, it will be appreciated that such a development effort might be complex and time-consuming, but would nevertheless be a routine undertaking of software engineering for those of ordinary skill having the benefit of this disclosure.  
     [0114] As will be further understood from the teachings provided herein, the present invention encompasses a variety of specific embodiments for performing these steps. As further described below, request for power management and monitoring information may be received in a variety of ways, including through one or more graphical user interfaces provided by an SPS to the client system or by the SPS system receiving an email or other digital message or communication from the client system. Thus, according to specific embodiments of the present invention, data and/or indications can be transmitted to the SPS using any method for transmitting digital data, including HTML communications, FTP communications, email communications, wireless communications, etc. In various embodiments, indications of desired data can be received from a human user selecting from a graphical interface at a computing device.  
     [0115] example system as illustrated in FIG. 24.  
     [0116] Example External Hardware System Configuration  
     [0117] FIGS.  22 A-B is a diagram illustrating an example of external features and appearance of an example three connector configurable power supply according to specific embodiments of the present invention. The figures illustrate the following example elements:  
     [0118] 1 : Unit power indicator  
     [0119] 2 : Over-all amperage usage meter  
     [0120] 3 : Outlet indicator  
     [0121] 4 : Serial port  
     [0122] 5 : Direct phone line connection (not a modem port)  
     [0123] 6 : Ethernet port  
     [0124] 7 : AC outlets  
     [0125] 8 : Outlets on/standby switch  
     [0126] 9 : AC inlet receptacle  
     [0127] FIGS.  23 A-B is a diagram illustrating an example of external features and appearance of an example two connector power supply according to specific embodiments of the present invention. In this example embodiment, the phone interface and outlets on/standby switch are not provided on the panels shown.  
     [0128] According to specific embodiments of the invention, an SPS is designed to be mounted into a standard, 19 inch, network rack or cabinet. If mounted in the horizontal position the SPS takes up 1 rack unit of space. While many other dimensions are possible, in specific embodiments, the invention provides the described functionality in a system having total dimensions less than about a 1 RU for 19″ rack, or 17″ wide×8.38″ deep×1.75″ high.  
     [0129] Including the functionalities described herein in a design having the appearance and dimensions indicated above is consider a further novel and beneficial feature of the invention, various modifications of this basic design are encompassed by the broad descriptions of the invention according to specific embodiments. As just one example, designs can have various desired numbers of controlled outlets, such as 1, 2, 3, 4, 8, 16, 24 and be provided in different dimensions. As a further example, one or more of the controlled power outlets can be controlled together, such as a system providing four pairs of power outlets. As a further example, the outlet shapes shown above can be varied, for example for connecting to different power systems, including various international power systems and different voltages. The design elements illustrated can also be varied.  
     [0130] Example Hardware Functional Components  
     [0131]FIG. 24 is a block diagram illustrating an example logic modules of a configurable power supply according to specific embodiments of the present invention. This is one example embodiment showing a number of different elements in one or more novel arrangements not of all which will be a part of all embodiments.  
     [0132] In this example embodiment, various functions as described above are provided by a microprocessor executing a stored-program, such as, for example, a Rabbit2000 Microcontroller and Memory. According to specific embodiments of the invention, the microcrontroller provides the logical execution ability to both control the outlets using a relay driver and relays as shown and also to provide communications ability through two or more interfaces, such as an Ethernet interface comprising an Ethernet connector (jack) and driver, a phone interface comprising a phone connector (jack) and phone DAA &amp; DTMF along with an audio processor for generating audio status indications and/or for recognizing speech commands, a serial interface comprising a serial connector (e.g., a RJ45 serial jack and/or a USB connection) and appropriate drivers, and an external LED interface comprising one or more LEDs and an LED driver.  
     [0133] According to specific embodiments of the invention, current sensors are provided for each outlet and a sensor signal conditioning module and/or function provides information to the microcontroller for use in reporting current status and/or also for use in providing current control. A surge protector, switch/circuit breaker, and digital operating voltage power supply (e.g., 5 volts or 3.3 volts, etc.) are also included.  
     [0134] Any number of different brands of available modules can be used in specific embodiments of the invention.  
     [0135] Portions of an Example Circuit Description  
     [0136]FIG. 25 through FIG. 28 provide selected details of an example system according to specific embodiments of the invention. These figures include component listings and circuit descriptions that will be familiar in the art. For clarity of disclosure, these figures do not include every detail of every element of an example system, but do show example embodiments of salient features of an SPS according to specific embodiments of the invention.  
     [0137] FIGS.  25 A-B is a block diagram illustrating in further details major functional components of an example configurable power supply according to specific embodiments of the present invention. In this embodiment, a microcontroller as shown in the center of the figure is connected to functional components of the invention including an Ethernet module, a Phone &amp; Voice module, a Serial Port module, an LED module, a current Sense module, and a Relays module. The Ethernet module, Phone &amp; Voice module, Serial Port module, and LED module can represent standard configurations of known circuit elements that are not further described herein. The Ethernet module, for example, can consist primarily of an RTL8019AS Ethernet integrated circuit or similar off-the-shelf circuits or custom or integrated components. The Serial Port module, for example, can consist primarily of an SP232E integrated circuit or similar off-the-shelf circuits or custom or integrated components. The Phone &amp; Voice module, for example, can consist primarily of available components such as a CLARE-CPC5620, a SUNPLUS-SPC122ABOARD and/or a NPC-SM8223A integrated circuits or similar off-the-shelf circuits or custom or integrated components. An LED and bar-graph display can be provided using components such as an ALLEGRO 6275 and/or an ALLEGRO 6276 or similar off-the-shelf circuits or custom or integrated components.  
     [0138]FIG. 26 is a block diagram illustrating details a microcontroller and other control logic of an example configurable power supply according to specific embodiments of the present invention. In this embodiment, a RABBIT 2000 microcontroller is shown with an SRAM memory and CMOS FLASH MEMORY.  
     [0139]FIG. 27 is a block diagram illustrating details of three power relays of an example configurable power supply according to specific embodiments of the present invention. According to specific embodiments of the invention, the number of power relays will correspond to the number of managed power outlets, such as eight. In alternative embodiments, each relay may provided on-off management of multiple grouped power outlets.  
     [0140] FIGS.  28 A-B is a block diagram illustrating details of three current sensors of an example configurable power supply according to specific embodiments of the present invention. According to specific embodiments of the invention, the number of sensors will correspond to the number of managed power outlets, such as eight. In alternative embodiments, each sensor relay may provided sensing of multiple grouped power outlets.  
     [0141] Example SNMP MIB  
     [0142] As is known in the art, SNMP operates using data structures known as MIBs. Provided below is one example MIB that provides further details of a specific embodiment of the invention.  
                                  CYBERSWITCHING-MIB DEFINITIONS : := BEGIN       IMPORTS                         enterprises, IpAddress,           TimeTicks, Counter, Gauge, Opaque FROM RFC1155-SMI           OBJECT-TYPE FROM RFC-1212           TRAP-TYPE FROM RFC-1215           DisplayString FROM RFC1213-MIB;                 --                     --   Copyright (C) 2003, CyberSwitching. All rights reserved.                     cyberswitching   OBJECT IDENTIFIER : := { enterprises 14300 }       cyberswitching-products   OBJECT IDENTIFIER : := { cyberswitching 1 }                 -- = = = = = = = = = = CyberSwitching NMS products = = = = = = = = = =                     tricom-8   OBJECT IDENTIFIER : := { cyberswitching-products 1 }       tricom-8-ctrl   OBJECT IDENTIFIER : := { tricom-8 1 }       tricom-8-mgmt   OBJECT IDENTIFIER : := { tricom-8 2 }       tricom-8-traps   OBJECT IDENTIFIER : := { tricom-8 3 }       oNumber OBJECT-TYPE                             SYNTAX   INTEGER           ACCESS   read-only           STATUS   mandatory                         DESCRIPTION                         “The number of managed outlets present on this system.”                         : := { tricom-8-ctrl 1 }                 oTable OBJECT-TYPE                             SYNTAX   SEQUENCE OF OEntry           ACCESS   not-accessible           STATUS   mandatory                         DESCRIPTION                         “A list of outlet entries. The number of           entries is given by the value of oNumber.”                         : := { tricom-8-ctrl 2 }                 oEntry OBJECT-TYPE                             SYNTAX   OEntry           ACCESS   not-accessible           STATUS   mandatory                         DESCRIPTION                         “An outlet entry containing status and properties           of a managed outlet.”                             INDEX   { oIndex }                         : := { oTable 1 }                 OEntry : :=                         SEQUENCE {                         oIndex                         INTEGER,                         oLabel                         DisplayString,                         oState                         INTEGER,                         oCurrentStr                         DisplayString,                         oCurrentFloat                         Opaque,                         oCurrentInt                         INTEGER                         }                 oIndex OBJECT-TYPE                             SYNTAX   INTEGER (1 . . . 8)           ACCESS   read-only           STATUS   mandatory                         DESCRIPTION                         “A unique value for each outlet. Its value           ranges between 1 and the value of oNumber.”                         : := { oEntry 1 }                 oLabel OBJECT-TYPE                             SYNTAX   DisplayString (SIZE (0 . . . 15))           ACCESS   read-write                                 STATUS   mandatory   )                         DESCRIPTION                         “A textual string containing the outlet&#39;s           user-friendly name.”                         : := { oEntry 2 }                 oState OBJECT-TYPE                             SYNTAX   INTEGER {                             off(1),   -- outlet is on           on(2),   -- outlet is off           error(3)   -- outlet has a problem                         }                             ACCESS   read-write           STATUS   mandatory                         DESCRIPTION                         “The outlet&#39;s state. (ON/OFF/ERROR). Reading oState           returns the outlet&#39;s state. Setting oState to off           turns the outlet off. Setting oState to on turns the           outlet on. Setting oState to error is invalid.”                         : := { oEntry 3 }                 oCurrentStr OBJECT-TYPE                             SYNTAX   DisplayString           ACCESS   read-only           STATUS   mandatory                         DESCRIPTION                         “The amount of current the outlet is drawing, string           formatted.”                         : := { oEntry 4 }                 oCurrentFloat OBJECT-TYPE                             SYNTAX   Opaque           ACCESS   read-only           STATUS   mandatory                         DESCRIPTION                         “The amount of current the outlet is drawing, in Amps.”                         : := { oEntry 5 }                 oCurrentInt OBJECT-TYPE                             SYNTAX   INTEGER           ACCESS   read-only           STATUS   mandatory                         DESCRIPTION                         “The amount of current the outlet is drawing, in Amps           This is rounded to an integer for applications that can&#39;t           handle strings or floats.”                         : := { oEntry 6 }                 oTotCurrentFloat OBJECT-TYPE                             SYNTAX   Opaque           ACCESS   read-only           STATUS   mandatory                         DESCRIPTION                         “The total amount of current the unit is supplying, in Amps.”                         : := { tricom-8-ctrl 3 }                 oTotCurrentStr OBJECT-TYPE                             SYNTAX   DisplayString           ACCESS   read-only           STATUS   mandatory                         DESCRIPTION                         “The total amount of current the unit is supplying.           (String Formatted)”                         : := { tricom-8-ctrl 4 }                 oTotCurrentInt OBJECT-TYPE                             SYNTAX   INTEGER           ACCESS   read-only           STATUS   mandatory                         DESCRIPTION                         “The total amount of current the unit is supplying, in Amps.           This is rounded to an integer for applications that can&#39;t           handle strings or floats.”                         : := { tricom-8-ctrl 5 }                 oStateMask OBJECT-TYPE                             SYNTAX   INTEGER           ACCESS   read-only           STATUS   mandatory                         DESCRIPTION                         “Bits 0-8 = the state of all eight outlets. 0 is off           1 is on.”                         : := { tricom-8-ctrl 6 }                 triSysTimeDate OBJECT-TYPE                             SYNTAX   TimeTicks           ACCESS   read-write           STATUS   mandatory                         DESCRIPTION                         “Time in hundredths of a second since Jan. 1, 1980.”                         : := { tricom-8-mgmt 1 }                 triTimeZone OBJECT-TYPE                             SYNTAX   INTEGER (−13 . . . 13)           ACCESS   read-write           STATUS   mandatory                         DESCRIPTION                         “Time zone as an offset from GMT”                         : := { tricom-8-mgmt 2 }                 triDaylightSavings OBJECT-TYPE                             SYNTAX   INTEGER {                             disabled(1),   -- Time is in standard time.           enabled(2)   -- Time is in daylight savings time.                         }                             ACCESS   read-write           STATUS   mandatory                         DESCRIPTION                         “When enabled, the clock is adjusted for daylight savings.”                         : := { tricom-8-mgmt 3 }                 triNTPEnabled OBJECT-TYPE                             SYNTAX   INTEGER {                             disabled(1),   -- NTP is disabled. Time must be set manually.           enabled(2)   -- NTP is enabled. Unit will attempt to get network time.                         }                             ACCESS   read-write           STATUS   mandatory                         DESCRIPTION                         “When enabled, the unit will attempt to set its clock from the           network using NTP servers 1 &amp; 2.”                         : := { tricom-8-mgmt 4 }                 triNTPServer1 OBJECT-TYPE                             SYNTAX   DisplayString (SIZE (0 . . . 59))           ACCESS   read-write           STATUS   mandatory                         DESCRIPTION                         “Time server #1. Set to 255.255.255.255 to broadcast time requests.”                         : := { tricom-8-mgmt 5 }                 triNTPServer2 OBJECT-TYPE                             SYNTAX   DisplayString (SIZE (0 . . . 59))           ACCESS   read-write           STATUS   mandatory                         DESCRIPTION                         “Time server #2. Will be used if Timer Server #1 fails.           Set to 255.255.255.255 to broadcast time requests.”                         : := { tricom-8-mgmt 6 }                 triDHCPEnabled OBJECT-TYPE                             SYNTAX   INTEGER {                             disabled(1),   -- DHCP is disabled. Network Settings must be set manually.           enabled(2)   -- DHCP is enabled. Unit will attempt to get settings from                 DHCP server.                         }                             ACCESS   read-write           STATUS   mandatory                         DESCRIPTION                         “When enabled, the unit will attempt to get its network settings from a DHCP           server upon booting. If this fails, it will revert to the manual settings.”                         : := { tricom-8-mgmt 7 }                 triNetworkIP OBJECT-TYPE                             SYNTAX   IpAddress           ACCESS   read-write           STATUS   mandatory                         DESCRIPTION                         “IP of this TRICOM-8 Unit.”                         : := { tricom-8-mgmt 8 }                 triSubnetMask OBJECT-TYPE                             SYNTAX   IpAddress           ACCESS   read-write           STATUS   mandatory                         DESCRIPTION                         “Subnet Mask of this TRICOM-8 Unit.”                         : := { tricom-8-mgmt 9 }                 triGateway OBJECT-TYPE                             SYNTAX   IpAddress           ACCESS   read-write           STATUS   mandatory                         DESCRIPTION                         “Gateway of this TRICOM-8 Unit.”                         : := { tricom-8-mgmt 10 }                 triDNS OBJECT-TYPE                             SYNTAX   IpAddress           ACCESS   read-write           STATUS   mandatory                         DESCRIPTION                         “Domain Name Server of this TRICOM-8 Unit.”                         : := { tricom-8-mgmt 11 }                 triHostName OBJECT-TYPE                             SYNTAX   DisplayString (SIZE (0 . . . 15))           ACCESS   read-write           STATUS   mandatory                         DESCRIPTION                         “Host Name of this TRICOM-8 Unit.”                         : := { tricom-8-mgmt 12 }                 triDomain OBJECT-TYPE                             SYNTAX   DisplayString (SIZE (0 . . . 15))           ACCESS   read-write           STATUS   mandatory                         DESCRIPTION                         “Domain of this TRICOM-8 Unit.”                         : := { tricom-8-mgmt 13 }                 triPhoneEnabled OBJECT-TYPE                             SYNTAX   INTEGER {                             disabled(1),   -- Phone interface is DISABLED           enabled(2)   -- Phone interface is ENABLED                         }                             ACCESS   read-write           STATUS   mandatory                         DESCRIPTION                         “Operational mode of the phone interface.”                         : := { tricom-8-mgmt 14 }                 triBlockNoCallerID OBJECT-TYPE                             SYNTAX   INTEGER {                             noblock(1),   -- Calls with no CallerID are allowed           block(2)   -- Calls with no CallerID are blocked                         }                             ACCESS   read-write           STATUS   mandatory                         DESCRIPTION                         “No CallerID blocking mode.”                         : := { tricom-8-mgmt 15 }                 triPhonePin OBJECT-TYPE                             SYNTAX   DisplayString (SIZE (0 . . . 15))           ACCESS   read-write           STATUS   mandatory                         DESCRIPTION                         “PIN used to access the phone interface. This must be           at least 6 characters.”                         : := { tricom-8-mgmt 16 }                 triSyslogServer OBJECT-TYPE                             SYNTAX   DisplayString (SIZE (0 . . . 59))           ACCESS   read-write           STATUS   mandatory                         DESCRIPTION                         “Server name to send BSD Syslog style log events to. Set this to a           NULL string to disable Syslog. (events will still be logged locally)”                         : := { tricom-8-mgmt 17 }                 triLoggingFacility OBJECT-TYPE                             SYNTAX   INTEGER {                         local-0(1),           local-1(2),           local-2(3),           local-3(4),           local-4(5),           local-5(6),           local-6(7),           local-7(8)                         }                             ACCESS   read-write           STATUS   mandatory                         DESCRIPTION                         “BSD Syslog Logging Facility.”                         : := { tricom-8-mgmt 18 }                 triLoggingLevel OBJECT-TYPE                             SYNTAX   INTEGER {                         emergency(1),           alert(2),           critical(3),           error(4),           warning(5),           notice(6),           informational(7),           debug(8)                         }                             ACCESS   read-write           STATUS   mandatory                         DESCRIPTION                         “BSD Syslog Logging Level. This affects the amount of logging performed.”                         : := { tricom-8-mgmt 19 }                 triDumpLogs OBJECT-TYPE                             SYNTAX   INTEGER {                             nodump(1),   -- do not dump logs to email           dump(2)   -- dump logs to email                         }                             ACCESS   read-write           STATUS   mandatory                         DESCRIPTION                         “Dump Logs to email when full option.”                         : := { tricom-8-mgmt 20 }                 triSMTPServer OBJECT-TYPE                             SYNTAX   DisplayString (SIZE (0 . . . 59))           ACCESS   read-write           STATUS   mandatory                         DESCRIPTION                         “Server used to send email.”                         : := { tricom-8-mgmt 21 }                 triEmailTo OBJECT-TYPE                             SYNTAX   DisplayString (SIZE (0 . . . 59))           ACCESS   read-write           STATUS   mandatory                         DESCRIPTION                         “Address to send email to.”                         : := { tricom-8-mgmt 22 }                 triEmailFrom OBJECT-TYPE                             SYNTAX   DisplayString (SIZE (0 . . . 59))           ACCESS   read-write           STATUS   mandatory                         DESCRIPTION                         “Address to send email from.”                         : := { tricom-8-mgmt 23 }                 triEmailSubject OBJECT-TYPE                             SYNTAX   DisplayString (SIZE (0 . . . 59))           ACCESS   read-write           STATUS   mandatory                         DESCRIPTION                         “Subject of email.”                         : := { tricom-8-mgmt 24 }                 triOutletConfirmation OBJECT-TYPE                             SYNTAX   INTEGER {                             noconfirm(1),   -- do not confirm outlet changes           confirm(2)   -- confirm outlet changes                         }                             ACCESS   read-write           STATUS   mandatory                         DESCRIPTION                         “Whether or not to confirm outlet changes from web           interface.”                         : := { tricom-8-mgmt 32 }                 triWebRefresh OBJECT-TYPE                             SYNTAX   INTEGER (5 . . . 999)           ACCESS   read-write           STATUS   mandatory                         DESCRIPTION                         “Number of seconds (5-999) to wait before refreshing           outlets on web interface.”                         : := { tricom-8-mgmt 33 }                 triOutletStaggerTime OBJECT-TYPE                             SYNTAX   INTEGER (0 . . . 5000)           ACCESS   read-write           STATUS   mandatory                         DESCRIPTION                         “Number of milliseconds (0-5,000) to pause between outlets when           turning on/off multiple outlets at once.”                         : := { tricom-8-mgmt 34 }                 triOSchedules OBJECT-TYPE                             SYNTAX   SEQUENCE OF TriScheduleEntry           ACCESS   not-accessible           STATUS   mandatory                         DESCRIPTION                         “A List of Schedules.”                         : := { tricom-8-mgmt 35 }                 triScheduleEntry OBJECT-TYPE                             SYNTAX   TriScheduleEntry           ACCESS   not-accessible           STATUS   mandatory                         DESCRIPTION                         “An outlet schedule entry”                             INDEX   { triScheduleIndex }                         : := { triOSchedules 1 }                 TriScheduleEntry : :=                         SEQUENCE {                         triScheduleIndex                         INTEGER,                         triScheduleEnabled                         INTEGER                         }                 triScheduleIndex OBJECT-TYPE                             SYNTAX   INTEGER (1 . . . 8)           ACCESS   read-only           STATUS   mandatory                         DESCRIPTION                         “A unique value for each outlet. Its value           ranges between 1 and oNumber.”                         : := { triScheduleEntry 1 }                 triScheduleEnabled OBJECT-TYPE                             SYNTAX   INTEGER {                             disabled(1),   -- outlet is disabled           enabled(2)   -- outlet is enabled                         }                             ACCESS   read-write           STATUS   mandatory                         DESCRIPTION                         “Enable status of schedule.”                         : := { triScheduleEntry 2 }                 trilogs OBJECT-TYPE                             SYNTAX   SEQUENCE OF TriLogEntry           ACCESS   not-accessible           STATUS   mandatory                         DESCRIPTION                         “A List of Log Entries.”                         : := { tricom-8-mgmt 38 }                 triLogEntry OBJECT-TYPE                             SYNTAX   TriLogEntry           ACCESS   not-accessible           STATUS   mandatory                         DESCRIPTION                         “A Log Entry Display String.”                             INDEX   { triLogIndex }                         : := { trilogs 1 }                 TriLogEntry : :=                         SEQUENCE {                         triLogIndex                         INTEGER,                         triLogString                         DisplayString                         }                 triLogIndex OBJECT-TYPE                             SYNTAX   INTEGER (1 . . . 32)           ACCESS   read-only           STATUS   mandatory                         DESCRIPTION                         “A unique value for each log entry. Its value           ranges between 1 and trinumlogs.”                         : := { triLogEntry 1 }                 triLogString OBJECT-TYPE                             SYNTAX   DisplayString           ACCESS   read-only           STATUS   mandatory                         DESCRIPTION                         “The log entry in string form.”                         : := { triLogEntry 2 }                 triNumLogs OBJECT-TYPE                             SYNTAX   INTEGER           ACCESS   read-only           STATUS   mandatory                         DESCRIPTION                         “The number of Log entries available”                         : := { tricom-8-mgmt 39 }                 -- TRAPS       triOutletCurrentTraps OBJECT-TYPE                             SYNTAX   SEQUENCE OF TriCurrentTrapEntry           ACCESS   not-accessible           STATUS   mandatory                         DESCRIPTION                         “Table of current trap limits.”                         : := { tricom-8-traps 1 }                 triCurrentTrapEntry OBJECT-TYPE                             SYNTAX   TriCurrentTrapEntry           ACCESS   not-accessible           STATUS   mandatory                         DESCRIPTION                         “An outlet entry containing status and properties           of a managed outlet.”                             INDEX   { triCurIndex }                         : := { triOutletCurrentTraps 1 }           TriCurrentTrapEntry : :=           SEQUENCE {                         triCurIndex                         INTEGER,                         triCurLoEnabled                         INTEGER,                         triCurLoBound                         DisplayString,                         triCurLoGracePeriod                         INTEGER (0 . . . 65535),                         triCurHiEnabled                         INTEGER,                         triCurHiBound                         DisplayString,                         triCurHiGracePeriod                         INTEGER (0 . . . 65535)                         }                 triCurIndex OBJECT-TYPE                             SYNTAX   INTEGER (1 . . . 8)           ACCESS   read-only           STATUS   mandatory                         DESCRIPTION                         “A unique value for each outlet. Its value           ranges between 1 and the value of oNumber.”                         : := { triCurrentTrapEntry 1 }                 triCurLoEnabled OBJECT-TYPE                             SYNTAX   INTEGER {                             disabled(1),   -- trap is disabled           enabled(2)   -- trap is enabled                         }                             ACCESS   read-write           STATUS   mandatory                         DESCRIPTION                         “Low current bound trap enable. When enabled, a trap will           be generated when current falls below triCurLoBound and           stays below for longer than triCurLoGracePeriod.”                         : := { triCurrentTrapEntry 2 }                 triCurLoBound OBJECT-TYPE                             SYNTAX   DisplayString (SIZE(0 . . . 20))           ACCESS   read-write           STATUS    mandatory                         DESCRIPTION                         “Low current boundary. This string must contain only a valid           floating-point number representing current in Amps between           0.0 and 99.9. When the outlet current falls below this value,           and stays below for longer than triCurLoGracePeriod a trap           will be generated.”                         : := { triCurrentTrapEntry 3 }                 triCurLoGracePeriod OBJECT-TYPE                             SYNTAX   INTEGER (0 . . . 65535)           ACCESS   read-write           STATUS   mandatory                         DESCRIPTION                         “Low current grace period in Seconds. When the outlet           current falls below triCurLoBound, and stays below for longer           than this value, a trap will be generated. Care should be           taken not to set this too low, or the network might be           flooded with traps if the current rapidly fluctuates around           triCurLoBound.”                         : := { triCurrentTrapEntry 4 }                 triCurHiEnabled OBJECT-TYPE                             SYNTAX   INTEGER {                             disabled(1),   -- trap is disabled           enabled(2)   -- trap is enabled                         }                             ACCESS   read-write           STATUS   mandatory                         DESCRIPTION                         “High current bound trap enable. When enabled, a trap will           be generated when current rises above triCurHiBound and           stays above for longer than triCurHiGracePeriod.”                         : := { triCurrentTrapEntry 5 }                 triCurHiBound OBJECT-TYPE                             SYNTAX   DisplayString (SIZE(0 . . . 20))           ACCESS   read-write           STATUS   mandatory                         DESCRIPTION                         “High current boundary. This string must contain only a valid           floating-point number representing current in Amps between           0.0 and 99.9. When the outlet current rises above this value,           and stays above for longer than triCurHiGracePeriod a trap           will be generated.”                         : := { triCurrentTrapEntry 6 }                 triCurHiGracePeriod OBJECT-TYPE                             SYNTAX   INTEGER (0 . . . 65535)           ACCESS   read-write           STATUS   mandatory                         DESCRIPTION                         “High current grace period in Milliseconds. When the outlet           current rises above triCurHiBound, and stays above for longer           than this value, a trap will be generated. Care should be           taken not to set this too low, or the network might be           flooded with traps if the current rapidly fluctuates around           triCurHiBound.”                         : := { triCurrentTrapEntry 7 }                 triOutletTrapped OBJECT-TYPE                             SYNTAX   INTEGER           ACCESS   read-only           STATUS   mandatory                         DESCRIPTION                         “The outlet that caused a trap (1-oNumber). This trap variable           is supplied for convenience. It should allow a management tool           to respond to outlet-specific traps with less parsing.”                         : := { tricom-8-traps 2 }                 tricomTotalCurrentCritical TRAP-TYPE                         ENTERPRISE cyberswitching           VARIABLES { oTotCurrentStr, oTotCurrentFloat 4 }           DESCRIPTION                         “Total current has gone above unit&#39;s circuit protection.”                         : := 1                 tricomTotalCurrentWarning TRAP-TYPE                         ENTERPRISE cyberswitching           VARIABLES { oTotCurrentStr, oTotCurrentFloat }           DESCRIPTION                         “Total current has gone above rated unit capacity.”                         : := 2                 tricomOutletLowCurrentWarning TRAP-TYPE                         ENTERPRISE cyberswitching           VARIABLES { triOutletTrapped, oCurrentStr, oCurrentFloat }           DESCRIPTION                         “Current has gone below triCurLoBound and           stayed there for longer than triCurLoGracePeriod.”                         : := 3                 tricomOutletHighCurrentWarning TRAP-TYPE                         ENTERPRISE cyberswitching           VARIABLES { triOutletTrapped, oCurrentStr, oCurrentFloat 4 }           DESCRIPTION                         “Current has gone above triCurHiBound and           stayed there for longer than triCurHiGraceperiod.”                         : := 4                 END                  
 
     [0143] Embodiment in a Programmed Information Appliance  
     [0144]FIG. 29 is a block diagram showing a representative example logic device in which various aspects of the present invention may be embodied. As will be understood to practitioners in the art from the teachings provided herein, the invention can be implemented in hardware and/or software. In some embodiments of the invention, different aspects of the invention can be implemented in either client-side logic or server-side logic. As will be understood in the art, the invention or components thereof may be embodied in a fixed media program component containing logic instructions and/or data that when loaded into an appropriately configured computing device cause that device to perform according to the invention. As will be understood in the art, a fixed media containing logic instructions may be delivered to a viewer on a fixed media for physically loading into a viewer&#39;s computer or a fixed media containing logic instructions may reside on a remote server that a viewer accesses through a communication medium in order to download a program component.  
     [0145]FIG. 29 shows an information appliance (or digital device)  700  that may be understood as a logical apparatus that can read instructions from media  717  and/or network port  719 , which can optionally be connected to server  720  having fixed media  722 . Apparatus  700  can thereafter use those instructions to direct server or client logic, as understood in the art, to embody aspects of the invention. One type of logical apparatus that may embody the invention is a computer system as illustrated in  700 , containing CPU  707 , optional input devices  709  and  711 , disk drives  715  and optional monitor  705 . Fixed media  717 , or fixed media  722  over port  719 , may be used to program such a system and may represent a disk-type optical or magnetic media, magnetic tape, solid state dynamic or static memory, etc. In specific embodiments, the invention may be embodied in whole or in part as software recorded on this fixed media. Communication port  719  may also be used to initially receive instructions that are used to program such a system and may represent any type of communication connection.  
     [0146] The invention also may be embodied in whole or in part within the circuitry of an application specific integrated circuit (ASIC) or a programmable logic device (PLD). In such a case, the invention may be embodied in a computer understandable descriptor language, which may be used to create an ASIC, or PLD that operates as herein described.  
     [0147] Other Embodiments  
     [0148] The invention has now been described with reference to specific embodiments. Other embodiments will be apparent to those of skill in the art. In particular, a viewer digital information appliance has generally been illustrated as a personal computer. However, the digital computing device is meant to be any information appliance for interacting with a remote data application, and could include such devices as a digitally enabled television, cell phone, personal digital assistant, laboratory or manufacturing equipment, etc. It is understood that the examples and embodiments described herein are for illustrative purposes and that various modifications or changes in light thereof will be suggested by the teachings herein to persons skilled in the art and are to be included within the spirit and purview of this application and scope of the claims.  
     [0149] Furthermore, various different actions can be used to effect power management. For example, a voice command may be spoken by the purchaser, a key may be depressed by the purchaser, a button on a client-side scientific device may be depressed by the user, or selection using any pointing device may be effected by the user.  
     [0150] All publications, patents, and patent applications cited herein or filed with this application, including any references filed as part of an Information Disclosure Statement, are incorporated by reference in their entirety.