|Publication number||US7653757 B1|
|Application number||US 11/198,698|
|Publication date||Jan 26, 2010|
|Filing date||Aug 5, 2005|
|Priority date||Aug 6, 2004|
|Also published as||US8452897|
|Publication number||11198698, 198698, US 7653757 B1, US 7653757B1, US-B1-7653757, US7653757 B1, US7653757B1|
|Inventors||Kenneth W. Fernald, James W. Templeton, John A. Wishneusky|
|Original Assignee||Zilker Labs, Inc.|
|Export Citation||BiBTeX, EndNote, RefMan|
|Patent Citations (34), Non-Patent Citations (66), Referenced by (35), Classifications (8), Legal Events (5)|
|External Links: USPTO, USPTO Assignment, Espacenet|
This application claims benefit of priority of provisional application Ser. No. 60/599,369 titled “Method For Using A Multi-Master Multi-Slave Bus For Power Management” and filed Aug. 6, 2004, which is hereby incorporated by reference as though fully and completely set forth herein.
1. Field of the Invention
This invention relates generally to the field of data communications, and more particularly, to the design of bus interfaces.
2. Description of the Related Art
Power distribution in complex systems is often accomplished by distributing a high-voltage, low-current power source to a set of local direct-current to direct-current (DC-to-DC) converters. These converters, typically known as point-of-load (POL) devices, convert the higher voltage to a level more appropriate for the load or multiple loads that require power. Generally, each POL may be configured to generate a different voltage potential or multiple POLs may be configured to generate the same voltage potential. POLs generating the same voltage potential may be designed to drive separate loads. Similarly, two or more POLs may be connected in parallel to drive one or more common loads.
In systems that utilize multiple POL devices, it is common for the POL devices to exchange information in order to implement necessary power management features. Typical power management features may include voltage tracking, load balancing, sequencing, phase spreading, and clock synchronization. With the rising complexity and robustness requirements of many systems, the ability to monitor and control the power distribution sub-system has become increasingly more critical. Traditionally, information exchanged by POL devices has been represented by analog voltage and/or current signals. There are, however, several advantages to representing the exchanged information as digital data that may be transferred across a bus interconnecting all related POL devices. Monitoring of power distribution sub-systems has typically been implemented via a standard digital interface coupling the major components of the power distribution system to a host microprocessor (oftentimes identified as a Local Controller). The digital interface may allow the Local Controller to continuously monitor the health of the power system. It may also control the power system in order to implement system-level features such as standby and sleep modes.
One digital interface that is particularly well suited for such applications is the I2C (Inter-IC) bus. The I2C bus is a multi-master, multi-slave, two-wire bus that offers support for any device on the bus to access any other device. Transactions on the I2C bus typically consist of a start event, a destination slave address, a read/write bit, and a variable number of data bytes. The transactions are generally terminated by a stop event or another start event. The data byte immediately following the destination slave address may be interpreted as a command or tag byte, which identifies the nature and/or type of the packet.
During typical operation, Local Controller 108 may address each POL and/or other device by its unique slave address as required, writing control information and reading status and data.
Another bus standard, developed after the I2C bus standard, is the SMBus (System Management Bus), which is backward compatible with the I2C bus standard while introducing additional features to support error detection, hazard recovery, and dynamic address assignment among others. It should be noted that both the I2C bus and the SMBus have predefined means for identifying a slave or destination device, but neither has predefined means for identifying the master or source of a bus transaction. The information transfer requirements of several common power management features will now be presented below.
It is a common requirement that the POL devices in a system enable and disable their power outputs in a predefined order, or sequence. This has commonly been referred to as “sequencing”, and is necessary to avoid both temporary and permanent interference with the operation of the system. The sequencing is traditionally accomplished by connecting a “POWER GOOD” (PG) output pin of each POL device to an “ENABLE” (EN) input pin of the next POL device to be enabled. This is illustrated in
As an alternative to sequencing, some systems may require that multiple POL devices enable their outputs simultaneously, while also operating to have their outputs maintain a predefined relationship with one another. This has commonly been referred to as “voltage tracking”. For example, a given POL device may be required to never allow its output to exceed that of another designated POL device as the POL devices ramp their output voltages.
In digital implementations of power conversion devices, the output voltage generated during turn-on and turn-off may be controlled by a precision digital-to-analog converter driven by a digital ramp generator. If the oscillator used to drive the ramp generator is precise, and the POL devices are enabled simultaneously, their outputs may ramp together in a predictable fashion. This may provide a means for voltage tracking without the need for additional bus traffic, and is often referred to as “open-loop” voltage tracking (as described in the above paragraph). However, mismatch between the oscillators configured within different POL devices may result in the turn-on and turn-off ramps of the different POL devices to change at different rates, and thereby introduce a mismatch between the POL devices' respective output voltages.
It is often more practical to provide a large amount of supply current to a load by connecting two or more POL devices in parallel, with each POL device intended to provide a roughly equal share of the total load current. Due to possible systematic and/or random mismatches between POL devices, the respective currents provided by different interconnected POL devices may vary considerably. Various methods, such as current balancing and load sharing have typically been used to correct such current mismatches.
Typically, current balancing is accomplished by allowing the POL devices to exchange information about their respective load currents. For example, if a master POL device in the group passes its measured load current to the other POL devices in the group, the other POL devices may adjust their own respective currents such that they match the value of the current they have received from the master POL device. In addition, by virtue of the slave POL devices' outputs being connected in parallel, the master POL device's output must decrease as the slave devices increase their respective output currents, in order to maintain a constant total load current. Other methods may allow for all POL devices to pass their respective measured load currents to other members of the group. In all, the communication between POL devices for maintaining current balance has traditionally been accomplished via one or more shared analog signals.
Additionally, in order to reduce both the input and output voltage ripple, groups of switching regulators, specifically POL devices in this case, are often required to spread their switching times across the switch period such that the respective times at which the POL devices are charging their respective output capacitors (from the input bus) have minimum overlap with one another. This is generally referred to as “phase spreading”. Phase spreading has typically been accomplished by configuring each POL device to switch at a set, predefined position within the switching period.
Other corresponding issues related to the prior art will become apparent to one skilled in the art after comparing such prior art with the present invention as described herein.
In one set of embodiments, a power management system may be configured to allow digital information corresponding to power management functions to be passed between POL devices using a standard multi-master multi-slave interface such as I2C bus interface or SMBus interface. POL devices may report information to multiple other POL devices while maintaining compatibility with non-POL devices also connected to the bus. Power management systems thereby designed to use a common bus to transmit digital information corresponding to power management functions may be configured without the traditional analog connections typically required in systems where multiple power management features need to be implemented.
In one embodiment, as an alternative to the dedicated analog signal connections traditionally used for communication between POL devices, each POL device is configured to generate an event on the shared bus, (such as the I2C bus), in which the POL device generating the event both identifies itself to the other POL devices on the bus, and transmits a command corresponding to one of many possible power management functions. The POL devices on the same bus may be equally configured to monitor the bus for events, and respond to the event according to the requirements inherent within the command, the POL devices thereby performing the necessary tasks to enable power management functions.
In one embodiment, information is distributed to multiple destinations, such as multiple POL devices coupled to the shared bus, by an originating device, which may be one of the POL devices, identifying itself as a master device and effectively transmitting the information to itself. The action of performing a bus write in which a given POL device may send the packet to its own address may both identify the source of the data, and may allow any slave device (e.g. POL devices configured to respond to the address of the master POL device) that needs the data to identify and receive the data from the bus during the transaction. Therefore, in addition to having its own respective assigned bus address, each POL device may be assigned or configured with one or more other addresses or address groups. The additional addresses may define one or more POL device groups, which may enable the specialized group data exchange required by various power management features. The additional address, addresses, or address groups may be used to receive data placed on the bus by a POL device acting as bus master, and to recognize the identity of that bus master POL device. Such configuration or configurations are compatible with normal features of shared buses such as the I2C and System Management Bust (SMBus).
In one embodiment, voltage tracking is accomplished by requiring a master POL device to transmit its target or measured output on the shared common digital bus. The slave POL device may receive the data while observing the master POL device transmission, and may use it to control its own output. The master POL device may be configured to both identify itself on the bus, and to transmit its digital output voltage. Therefore, one or more slave POL devices (configured to track the master POL device's output) may recognize the master POL device, monitor the master POL device's transmitted output voltage, and control their own output accordingly.
Current balancing functionality may be implemented by digitizing the load current information for each device and transmitting the resulting digital information across a shared digital bus. In one set of embodiments, the POL devices may also be configured to dynamically adjust their switching times based on information exchanged on the common digital bus. Other power management functions, such as phase spreading, fault recovery, clock synchronization, over-temperature shutdown, and most remaining power management functions may also be accomplished in a similar manner.
The foregoing, as well as other objects, features, and advantages of this invention may be more completely understood by reference to the following detailed description when read together with the accompanying drawings in which:
While the invention is susceptible to various modifications and alternative forms, specific embodiments thereof are shown by way of example in the drawings and will herein be described in detail. It should be understood, however, that the drawings and detailed description thereto are not intended to limit the invention to the particular form disclosed, but on the contrary, the intention is to cover all modifications, equivalents, and alternatives falling within the spirit and scope of the present invention as defined by the appended claims. Note, the headings are for organizational purposes only and are not meant to be used to limit or interpret the description or claims. Furthermore, note that the word “may” is used throughout this application in a permissive sense (i.e., having the potential to, being able to), not a mandatory sense (i.e., must).” The term “include”, and derivations thereof, mean “including, but not limited to”. The term “coupled” means “directly or indirectly connected”.
As used herein, a device coupled to a bus that is “uniquely identified by an address” refers to a device identified by an address that is not shared with any other device that is also coupled to the bus. That is, the address that identifies a specified device does not identify any other device. However, more than one address may uniquely identify a single device. For example, a device may be uniquely identified by address ‘34ef45’ and also by address ‘34ef44’, but neither ‘34ef45’ nor ‘34ef44’ may identify any other device. Furthermore, “targeting an address” during a bus operation refers to initiating the bus operation addressing a device uniquely identified by the address. For example, if a first device coupled to the bus has a specified first address that uniquely identifies the first device, and a second device initiates a write operation “targeting the specified first address”, then the address information transmitted by the first device as part of initiating the write operation is the specified first address.
In one set of embodiments, a method for using a multi-master multi-slave bus for power management is realized as a broadcast technique, which may be implemented in conjunction with a pre-existing bus protocol, to co-ordinate the behavior of a plurality of devices coupled to the bus that operates according to the pre-existing bus protocol.
In one embodiment, the broadcast technique is configured to facilitate the exchange of information between a plurality of point-of-load (POL) converters or devices in a power management system. The exchanged information may have a single origination point, for example a master POL device during voltage tracking, and multiple destination points, for example slave POL devices during voltage tracking. The information may be exchanged digitally, providing improved noise immunity and reduced system complexity by minimizing the number of signals connected between devices. In one embodiment, in order to maintain a minimum number of interconnected signal lines, the signal exchange may be performed on an existing digital interface within the system.
One set of embodiments may be configured with an Inter-IC (I2C) bus for system level monitoring and control. Typically, the I2C bus and other similar busses do not inherently support transactions that require multiple destinations, and/or transactions for which the originator needs to be identified. Transactions for multiple destinations may be performed on an I2C bus via a general broadcast transaction, but a general broadcast transaction used for performing power management functions may not be compatible with other (non-POL related) devices that are also coupled to the I2C bus. In addition, while the originator of a transaction may be identified through including an identifier data byte in the transaction, such inclusion may come at the cost of additional bus traffic and may therefore lead to higher bandwidth requirements. Furthermore, the inclusion of an identifier byte in the packet may not solve the problem of addressing a selected group of POL devices.
In one embodiment, a multi-master multi-slave bus architecture may be configured to have information identified as having originated from a particular device, and to have the information distributed to multiple destinations by allowing the originating device to effectively transmit the information to itself. For example, a given POL device having address 0x01 may transmit its measured output voltage to other POL devices on the bus by performing a bus write, where the target address for the bus write is the given POL device's own address. The write operation itself may not necessarily occur, given that the POL device may act as the bus master to send the packet, and may therefore not need to respond as a slave to its own address within the packet. The action of performing a bus write in which a given POL device may be sending the packet to its own address may both identify the source of the data (e.g. address 0x01), and may allow any slave device (e.g. POL devices configured to voltage track device 0x01) that needs the data to identify and receive the needed data from the bus during the transaction.
Since in conventional use no two devices are allowed to share a bus address, it is safe for a device to perform a write to its own address without the risk of bus failure or contention. Also, since all devices not associated with power delivery may simply ignore the transaction, this method of transferring information to a set of POL devices would remain compatible with non-power devices. Furthermore, in addition to having its own respective assigned bus address, each POL device may be assigned or configured with one or more other addresses or address groups. The additional addresses may define one or more POL device groups, which may enable the specialized group data exchange required by various power management features. The additional address, addresses, or address groups may be used to receive data placed on the bus by a POL device acting as bus master, and to recognize the identity of that bus master POL device. Such configuration or configurations are compatible with normal features of the I2C and System Management Bust (SMBus), both of which allow for bus arbitration and clock stretching that may be required by master and slave devices. Packets sent to a POL device by the Local Controller may be differentiated from packets that may be transmitted by a master POL device by the value of the command or tag following the address within any given packet. Alternatively, each POL device may be configured with an additional assigned address or addresses, which are uniquely different from the respective address used by the Local Controller to address a given POL device. The additional addresses may be used exclusively for implementing a select set of features, for example power management features, in which case the use of these additional addresses may uniquely distinguish the group communication packets corresponding to that set of features from conventional bus traffic originated by the Local Controller.
In one embodiment, each POL device required to transfer information to other POL devices first becomes the bus master and transmits its own address, followed by a transaction tag that identifies the type of transaction.
In one embodiment, POL devices may be configured with an I2C, SMBus, or other shared bus interface in a novel POL controller design. Each POL device may include at least two slave address registers. The slave address registers may support concurrent comparisons with an address contained in a packet transmitted onto the bus. If the address in the packet is a match for either of the slave address register values, the controller may recognize the address and may respond to the packet, receiving data written by the external master if the packet is writing data to the slave device identified by the address, and providing data to the external master if the packet reads data from the slave device identified by the address.
Referring again to
For example, if the 7 address bits in the Address 2 register are ‘1101011’, as shown for POL device 1002 in
It should be noted that the number of bits within an address register and the number of address registers within each POL device were selected for illustrative purposes, and alternative embodiments may be configured with buses featuring packet sizes other than one byte, and may include more or less than two address registers and one mask register, where an address register and/or mask register may be configured with more or less than seven bits.
Example packet tags transfers (such as described above) may include, but may not be limited to, a “power good” event tag, a “power fail” event tag, a measured output voltage tag, a measured load current tag, a fault event tag, or various configuration information tags. For transactions that include data, the tag may be followed by the actual digital data. Power sequencing functionality may be implemented by configuring any given POL device to enable its output, following a transmitting POL device having issued its own respective “power good” event, as illustrated in
For voltage tracking, all POL devices configured to track a particular POL device may monitor the bus for the particular POL device's transactions as determined by the particular POL device's address and tag, and may control their own outputs according to the data values retrieved from those transactions. Current sharing and other power management features may also be implemented in similar fashion. In addition, a given POL device's configuration information may similarly be transmitted to other POL devices. For example, each POL device may transmit its programmed target voltage to the other POL devices, allowing the other POL devices to determine if their own respective target voltage is larger or smaller than the transmitted voltage value. The other POL devices may thereby automatically configure themselves to sequence or track according to a prescribed order, such as a “largest output first” order. For example, upon having generated 5V, 3V and 2V outputs, the 5V POL device may detect based on transmitted configuration information that it should enable first, followed by the 3V POL device, then the 2V POL device. A group of POL devices may therefore be configured to automatically sequence according to their respective target voltage levels.
Other power management features including, but not limited to, phase spreading, fault recovery, clock synchronization, and over-temperature shutdown may also be implemented in a similar manner. Phase locking—when a group of POL devices are configured to lock with switching clocks in phase—may also be accomplished in a similar manner by transmitting data or edges on the standard bus.
In one set of embodiments, high bit-rate data may be transmitted via a low bit-rate standard synchronous bus while maintaining compatibility with existing bus devices. Synchronous bus architectures typically distribute a clock signal and one or more data signals. Each pulse on the clock signal may trigger the transfer of one bit of information on the data signals. In the case of the I2C bus, the data signal SDA 604 may transition to the next bit value to be transmitted after each falling edge of the clock signal SCL 602, as illustrated in
Standard devices on a bus like the I2C bus are generally configured to ignore transitions on SDA line 604 while SCL signal line 602 resides in a low state. The clock rate typically used in such systems may be relatively low. Furthermore, the I2C specifications and related SMBus specifications include clock stretching capability, that is, where both master and slave devices may be able to extend the time period during which SCL signal 602 resides in a low state. Therefore, data traffic may be embedded on SDA line 604 even while SCL signal 602 resides in a low state. In one embodiment, additional data is transmitted in bursts on the data signal (SDA) while the bus clock (SCL signal) resides in its low state. As illustrated in
The device may be configured to guarantee that the burst has been completed by the next rising edge on SCL signal line 902 by employing the clock stretching capability of the bus, thereby meeting the setup and hold times requirements set forth in the bus specification (and also illustrated in
In one set of embodiments, if a device other than the device transmitting data onto the bus is generating transitions on SCL line 902, the device transmitting a burst of data may employ clock stretching to insure that the next transition of SCL signal 902 to a high state does not occur during the burst. If the device transmitting the burst of data is the master device for the packet transmission, it may also control SCL 902 transitions and may insure that the burst of data is completed before the next transition of SCL 902 to a high state. For bus standards featuring a weak pull-up for driving a signal high, the transmitting device may use a strong push-pull driver during the data bursts to achieve higher bit rates. However, in the case of a multi-master bus, the data bursts may need to be inhibited until the transmitting device has acquired the bus.
In one set of embodiments, the bus addresses assigned to the POL devices (for example as shown in
In one embodiment, a common switch clock is used by a group of POL devices that are driving a common load, as illustrated in
In one set of embodiments, POL devices or groups of POL devices that are driving different loads may have independent clocks per each load device. In such embodiments, each POL device may generate its own clock locally, from an internal oscillator. Accordingly, a mismatch between respective oscillators configured in different POL devices may be addressed by calibrating the oscillators against each other, in-system. Referring again to
Following completion of the measurements, the master device, in this case POL device 1002, may send its own measured count to which the slave devices may compare their own respective counts, and determine the relative error between the master device's oscillator and their own respective oscillator. The packet structure for this command, according to one embodiment, is shown in
In one set of embodiments, some or all of the POL devices in a POL group may write required data to the bus within a single packet that is initiated by one of the POL devices. Each POL device may have one or more assigned data elements within the single packet or packet type as determined by the tag written by the initiating POL master device. In one embodiment, the assigned addresses of the POL devices determine the order of transmission within the single packet. As shown in
In one set of embodiments, when configuring various devices, for example POL devices, to communicate with each other as heretofore described, using a pre-existing bus such as an I2C bus or SMBus, only a subset of the pins normally required for a standard implementation of the pre-existing bus may be needed. In other words, proprietary bus functionality embedded in the standard bus protocol of the utilized bus (to provide the required communication capabilities for power management functions) may be accomplished with fewer pins than what a standard bus interface for the utilized bus may require. For example, in case of applications requiring an I2C interface only for implementing POL device communications, a single pin, rather than two I2C pins, may be sufficient for a single-wire bus, to implement the necessary communication capabilities for power management functions on that pin.
It should also be noted that while the above examples presented a bus write as a means for transmitting information from one POL device to another, a bus read may be used in a similar manner to transfer the information. That is, the originating POL device may effectively read from itself. However, other POL devices in its group may need to be configured to recognize the POL master's address without responding to the packet in the same manner in which they would respond to a conventional bus read from the Local Controller. In other words, the POL devices may be required to not supply data in response to the read bit. This mode of operation may involve additional non-standard device behavior, and may introduce additional overhead in the packet by adding a repeated start signal and address to accomplish setting the read bit.
Although the embodiments above have been described in considerable detail, other versions are possible. Numerous variations and modifications will become apparent to those skilled in the art once the above disclosure is fully appreciated. It is intended that the following claims be interpreted to embrace all such variations and modifications. Note the section headings used herein are for organizational purposes only and are not meant to limit the description provided herein or the claims attached hereto.
|Cited Patent||Filing date||Publication date||Applicant||Title|
|US5117430||Feb 8, 1991||May 26, 1992||International Business Machines Corporation||Apparatus and method for communicating between nodes in a network|
|US5646509||Dec 1, 1995||Jul 8, 1997||International Business Machines Corporation||Battery capacity test and electronic system utilizing same|
|US5675480||May 29, 1996||Oct 7, 1997||Compaq Computer Corporation||Microprocessor control of parallel power supply systems|
|US5935252||Aug 18, 1997||Aug 10, 1999||International Business Machines Corporation||Apparatus and method for determining and setting system device configuration relating to power and cooling using VPD circuits associated with system devices|
|US6003139 *||Jan 27, 1998||Dec 14, 1999||Compaq Computer Corporation||Computer system including power supply circuit with controlled output power|
|US6079026||Dec 11, 1997||Jun 20, 2000||International Business Machines Corporation||Uninterruptible memory backup power supply system using threshold value of energy in the backup batteries for control of switching from AC to DC output|
|US6199130 *||Jun 4, 1998||Mar 6, 2001||International Business Machines Corporation||Concurrent maintenance for PCI based DASD subsystem with concurrent maintenance message being communicated between SPCN (system power control network) and I/O adapter using PCI bridge|
|US6262900||May 21, 1999||Jul 17, 2001||Muuntolaite Oy||Modular power supply system with control command verification|
|US6396167||Mar 30, 1999||May 28, 2002||The Aerospace Corporation||Power distribution system|
|US6396169 *||Feb 29, 2000||May 28, 2002||3Com Corporation||Intelligent power supply control for electronic systems requiring multiple voltages|
|US6421259 *||Dec 28, 2000||Jul 16, 2002||International Business Machines Corporation||Modular DC distribution system for providing flexible power conversion scalability within a power backplane between an AC source and low voltage DC outputs|
|US6470382 *||May 26, 1999||Oct 22, 2002||3Com Corporation||Method to dynamically attach, manage, and access a LAN-attached SCSI and netSCSI devices|
|US6563294 *||Apr 1, 2002||May 13, 2003||Primarion, Inc.||System and method for highly phased power regulation|
|US6754720 *||Mar 2, 2001||Jun 22, 2004||Adaptec, Inc.||Automatic addressing of expanders in I/O subsystem|
|US6788035 *||Jun 12, 2002||Sep 7, 2004||Primarion, Inc.||Serial bus control method and apparatus for a microelectronic power regulation system|
|US6915440||Jun 12, 2001||Jul 5, 2005||International Business Machines Corporation||Apparatus, program product and method of performing power fault analysis in a computer system|
|US6936999||Mar 14, 2003||Aug 30, 2005||Power-One Limited||System and method for controlling output-timing parameters of power converters|
|US6949916 *||Nov 12, 2002||Sep 27, 2005||Power-One Limited||System and method for controlling a point-of-load regulator|
|US6965502 *||Mar 22, 2002||Nov 15, 2005||Primarion, Inc.||System, device and method for providing voltage regulation to a microelectronic device|
|US7000125||Dec 21, 2002||Feb 14, 2006||Power-One, Inc.||Method and system for controlling and monitoring an array of point-of-load regulators|
|US7049798 *||Nov 13, 2002||May 23, 2006||Power-One, Inc.||System and method for communicating with a voltage regulator|
|US7080265 *||Mar 14, 2003||Jul 18, 2006||Power-One, Inc.||Voltage set point control scheme|
|US7082488 *||Jun 12, 2003||Jul 25, 2006||Hewlett-Packard Development Company, L.P.||System and method for presence detect and reset of a device coupled to an inter-integrated circuit router|
|US7206944 *||Oct 30, 2002||Apr 17, 2007||Lenovo Singapore, Pte, Ltd||Electrical apparatus, computer, and power switching method|
|US20030070020 *||Oct 22, 2002||Apr 10, 2003||Hitachi, Ltd.||Bus control system|
|US20030142513 *||Oct 1, 2002||Jul 31, 2003||Patrizio Vinciarelli||Factorized power architecture with point of load sine amplitude converters|
|US20040093533||Nov 13, 2002||May 13, 2004||Power-One Limited||System and method for communicating with a voltage regulator|
|US20040123164 *||Dec 21, 2002||Jun 24, 2004||Power-One Limited||Method and system for controlling and monitoring an array of point-of-load regulators|
|US20040123167 *||Dec 23, 2002||Jun 24, 2004||Power -One Limited||System and method for interleaving point-of-load regulators|
|US20040135560 *||Nov 14, 2002||Jul 15, 2004||Kent Kernahan||Power converter circuitry and method|
|US20040255070 *||Jun 12, 2003||Dec 16, 2004||Larson Thane M.||Inter-integrated circuit router for supporting independent transmission rates|
|US20060172783 *||Mar 31, 2006||Aug 3, 2006||Silicon Laboratories Inc.||Digital DC/DC converter with SYNC control|
|US20060172787 *||Mar 27, 2006||Aug 3, 2006||Ellis Anthony M||Internet enabled multiply interconnectable environmentally interactive character simulation module method and system|
|WO2002031943A2||Oct 10, 2001||Apr 18, 2002||Primarion, Inc.||System and method for highly phased power regulation|
|1||"3-V to 6-V Input, 6-A Output Tracking Synchronous Buck PWM Switcher with Integrated FETs (SWIFT(TM)) for Sequencing"; Oct. 2002-Apr. 2005; 21 pages; Texas Instruments Incorporated; http://focus.ti.com/lit/ds/symlink/tps54680.pdf.|
|2||"Advanced Configuration and Power Interface Specification"; Feb. 2, 1999; 397 pages; Intel Microsoft Toshiba.|
|3||"APC-3000-R Front End AC-DC Power Shelf"; Advanced Power Conversion PLC (Data Sheet); Nov. 2002; 6 pages.|
|4||"Chemistry-Independent Battery Chargers"; Maxim Integrated Products; http://pdfserv.maxim-ic.com/en/ds/MAX1647-MAX1648.pdf; 25 pages.; Sunnyvale, CA, U.S.A.|
|5||"HDSX-600P: I2C Serial Bus Interface (for IPMI implementation):"; Switching Power, Inc.; www.switchpwr.com/I2C.pdf; 3 pages.|
|6||"HDX-600P HOT SWAP-600 Watts-1U High"; Switching Power, Inc.; www.switchpwr.com/hdx-600p.pdf; 2 pages.|
|7||"How to Design Battery Charger Applications that Require External Microcontrollers and Related System-Level Issues"; Dallas Semiconductor; www.maxim-ic.com/appnotes.cfm/appnote-number/680; Mar. 15, 2000.; 20 pages.|
|8||"Installation Guide-Agilent Technologies MPS Mainframe Model 66000A"; Apr. 2000; 29 pages; Agilent Technologies; Malaysia.|
|9||"Intelligent charge switches for charging circuit applications"; Jul. 2002; 2 pages; Philips Semiconductors; The Netherlands.|
|10||"LNBH21-LNB Supply and Control IC with Step-up Converter and I2C Interface" (Datasheet); Apr. 2004; 20 pages; STMicroelectronics; www.st.com/stonline/products/literature/ds/9890.pdf.|
|11||"Operating Manual for Internal RS-232 Interface for XT 60 Watt and HPC 300 Watt Series Programmable DC Power Supplies"; 2002; 62 pages; Xantrex Technology Inc.; Burnaby, B.C., Canada.|
|12||"PCF50604 Power Management Unit-2.5G/3G controller for power supply and battery management"; Jul. 2001; 4 pages; Philips Semiconductors; The Netherlands.|
|13||"Programmable Four-Channel Step-Down DC/DC Converter"; Texas Instruments Incorporated; 2005; 16 pages; http://focus.ti.com/lit/ds/symlink/tps54900.pdf.|
|14||"Providing a DSP Power Solution from 5-V or 3.3-V Only System"; Texas Instruments; http://focus.ti.com/lit/an/slva069/slva069.pdf; May 1999; 12 pages.|
|15||"Six-Channel Power Supply Supervisor and Cascade Sequence Controller" (Preliminary Information Data Sheet); SUMMIT Microelectronics, Inc.; www.summitmicro.com/prod-select/summary/sms66/SMS66DS.pdf; 2003; 26 pages;.|
|16||"Smart Battery System Specifications-System Management Bus Specification"; Dec. 11, 1998; 39 pages; SBS Implementers Forum.|
|17||"SPI-Appnotes: Alarm & Monitoring Signals"; Switching Power Inc.; 2 pages; www.switchpwr.com/alarm-signals.pdf.|
|18||"TDA8020HL Dual Smart Card Interface-Objective Specification v4.2-Data Sheet"; Feb. 24, 2001; 22 pages; Philips Semiconductors;.|
|19||"The I2C-Bus Specification-Version 2.1"; Jan. 2000; 46 pages; Philips Semiconductors.|
|20||"User's Guide Agilent Technologies Series 661xxA MPS Power Modules & Model 6001A MPS Keyboard"; Apr. 2000; 55 pages; Agilent Technologies; Malaysia.|
|21||"3-V to 6-V Input, 6-A Output Tracking Synchronous Buck PWM Switcher with Integrated FETs (SWIFT™) for Sequencing"; Oct. 2002-Apr. 2005; 21 pages; Texas Instruments Incorporated; http://focus.ti.com/lit/ds/symlink/tps54680.pdf.|
|22||"HDX-600P HOT SWAP—600 Watts—1U High"; Switching Power, Inc.; www.switchpwr.com/hdx-600p.pdf; 2 pages.|
|23||"How to Design Battery Charger Applications that Require External Microcontrollers and Related System-Level Issues"; Dallas Semiconductor; www.maxim-ic.com/appnotes.cfm/appnote—number/680; Mar. 15, 2000.; 20 pages.|
|24||"Installation Guide—Agilent Technologies MPS Mainframe Model 66000A"; Apr. 2000; 29 pages; Agilent Technologies; Malaysia.|
|25||"LNBH21—LNB Supply and Control IC with Step-up Converter and I2C Interface" (Datasheet); Apr. 2004; 20 pages; STMicroelectronics; www.st.com/stonline/products/literature/ds/9890.pdf.|
|26||"PCF50604 Power Management Unit—2.5G/3G controller for power supply and battery management"; Jul. 2001; 4 pages; Philips Semiconductors; The Netherlands.|
|27||"Six-Channel Power Supply Supervisor and Cascade Sequence Controller" (Preliminary Information Data Sheet); SUMMIT Microelectronics, Inc.; www.summitmicro.com/prod—select/summary/sms66/SMS66DS.pdf; 2003; 26 pages;.|
|28||"Smart Battery System Specifications—System Management Bus Specification"; Dec. 11, 1998; 39 pages; SBS Implementers Forum.|
|29||"SPI—Appnotes: Alarm & Monitoring Signals"; Switching Power Inc.; 2 pages; www.switchpwr.com/alarm—signals.pdf.|
|30||"TDA8020HL Dual Smart Card Interface—Objective Specification v4.2—Data Sheet"; Feb. 24, 2001; 22 pages; Philips Semiconductors;.|
|31||"The I2C-Bus Specification—Version 2.1"; Jan. 2000; 46 pages; Philips Semiconductors.|
|32||A. Akiyama, T. Nakamura, M. Yoshida, T. Kubo, N. Yamamoto and T. Katoh; "KEKB Power Supply Interface Controller Module"; KEK, High Energy Accelerator Research Organization; 4 pages; Japan.|
|33||A. Jossen, V. Spath, H. Doring & J. Garche; "Battery Management Systems (BMS) for Increasing Battery Life Time"; The Third International Conference on Telecommunications Energy Special, (TELESCON); May 2000; pp. 81-88; Dresden, Germany.|
|34||Advisory Action of Feb. 19, 2008, in U.S. Appl. No. 11/405,294, 3 pages.|
|35||Advisory Action of Oct. 26, 2007, in U.S. Appl. No. 10/820,976, 3 pages.|
|36||Chrisotphe Chausset; "Application Note-TDA802OHL/C2 Dual Smart Card Interface"; May 20, 2003; 28 pages; Philips Semiconductors.|
|37||Chrisotphe Chausset; "Application Note—TDA802OHL/C2 Dual Smart Card Interface"; May 20, 2003; 28 pages; Philips Semiconductors.|
|38||Examiner's Answer of Mar. 18, 2008, in U.S. Appl. No. 10/820,976, 18 pages.|
|39||Final Office Action of Apr. 4, 2008, in U.S. Appl. No. 11/425,489, 29 pages.|
|40||Final Office Action of Aug. 14, 2007, in U.S. Appl. No. 10/820,976, 12 pages.|
|41||Final Office Action of Dec. 27, 2007, in U.S. Appl. No. 11/405,294, 32 pages.|
|42||Final Office Action of May 8, 2007, in U.S. Appl. No. 11/405,294, 37 pages.|
|43||H. Taylor and L.W. Hruska; "Standard Smart Batteries for Consumer Applications" Proceedings of the Tenth Annual Battery Conference on Applications and Advances; Jan 1995; p. 183; Long Beach, CA, U.S.A.|
|44||James P. Earle; "IPMI/IMPB Satellite Controller Test Procedure" (Application Guide); C&D Technologies, Inc.; www.cdpowerelectronics.net/products/appnotes/acan04.pdf; 12 pages.|
|45||James P. Earle; "IPMI/IPMB Satellite Controller for Power Supply Applications" (Preliminary Specification);C&D Technologies, Inc.; http://www.cd4power.com/data/apnotes/acan-02.pdf; 92 pages.|
|46||Jerry G. Williford and James T. Dubose; "30 kVA LF/VLF Power Amplifier Module"; IEEE Military Communications Conference (MILCOM '95); Nov. 1995; pp. 748-751, vol. 2.|
|47||John M. Hawkins; "Characteristics of automated power system monitoring and management platforms"; Twenty-second International Telecommunications Energy Conference (INTELEC); Sep. 2000; pp. 46-50.|
|48||John Perzow; "Point-of-load regulation adds flexibility to set-top-box design"; Jun. 27, 2002; pp. 73-80; vol. 47, Part 14; www.ednmag.com.|
|49||M. Castro, R. Sebastian, F. Yeves, J. Peire, J. Urrutia and J. Quesada; "Well-Known Serial Buses for Distributed Control of Backup Power Plants. RS-485 versus Controller Area Network (CAN) Solutions"; IEEE 28th Annual Conference of the Industrial Electronics Society (IECON 02); Nov. 2002; pp. 2381-2386; vol. 3.|
|50||Office Action of Aug. 19, 2008, in U.S. Appl. No. 11/435,629, 31 pages.|
|51||Office Action of Aug. 20, 2008, in U.S. Appl. No. 11/425,489, 37 pages.|
|52||Office Action of Feb. 21, 2007, in U.S. Appl. No. 10/820,976, 12 pages.|
|53||Office Action of Jul. 25, 2007, in U.S. Appl. No. 11/405,294, 35 pages.|
|54||Office Action of Jun. 16, 2008, in U.S. Appl. No. 11/405,293, 20 pages.|
|55||Office Action of Jun. 17, 2008, in U.S. Appl. No. 10/820,976, 13 pages.|
|56||Office Action of Mar. 6, 2008, in U.S. Appl. No. 11/356,674, 39 pages.|
|57||Office Action of Nov. 13, 2006, in U.S. Appl. No. 11/405,294, 35 pages.|
|58||Office Action of Oct. 9, 2007, in U.S. Appl. No. 11/425,489, 35 pages.|
|59||Office Action of Sep. 20, 2006, in U.S. Appl. No. 10/820,976, 19 pages.|
|60||Paul Birman and Sarkis Nercessian; "Programmable supplies use switch-mode topologies"; Mar. 1995; pp. 33-34; Electronic Products Magazine; Garden City, New York, U.S.A.|
|61||Programming Guide Agilent Technologies Series 661xxA MPS Power Modules; Sep. 1997-Apr. 2000; 116 pages; Agilent Technologies.|
|62||R. Sebastian, M. Castro, E. Sancristobal, F. Yeves, J. Peire, and J. Quesada; "Approaching hybrid wind-diesel systems and Controller Area Network"; IEEE 28th Annual Conference of the Industrial Electronics Society; Nov. 2002; pp. 2300-2305, vol. 3.|
|63||Ron Vinsant, John Difiore and Richard Clarke; "Digitally-controlled SMPS extends power system capabilities"; Powerconversion & Intelligent Motion; 1994; pp. 30-37; vol. 20, No. 6.|
|64||T. T. Nakaura, A. Akiyama, T. Katoh, Ta. Kubo, N. Yamamoto, and M. Yoshida; "Magnet Power Supply Control System in KEKB Accelerators"; International Conference on Accelerator and Large Experimental Physics Control Systems; 1999; pp. 406-408; Trieste, Italy.|
|65||Tom Lock; "Digitally Controlled Power Systems: How Much Intelligence Is Needed and Where It Should Be"; IEEE; 1998; pp. 345-348.|
|66||V. C. H. Nicholas, C. T. Lau, and B. S. Lee; "A Power LAN for Telecommunication Power Supply Equipment"; IEEE Conference on Computer, Communication, Control and Power Engineering (TENCON, Region 10); Oct. 1993; pp. 24-27; vol. 3; Beijing.|
|Citing Patent||Filing date||Publication date||Applicant||Title|
|US8080981 *||Nov 6, 2009||Dec 20, 2011||Delta Electronics, Inc.||Interleaved-PWM power module system and method with phase-locking operation|
|US8239597 *||Jul 17, 2009||Aug 7, 2012||Intersil Americas Inc.||Device-to-device communication bus for distributed power management|
|US8515342 *||Oct 12, 2006||Aug 20, 2013||The Directv Group, Inc.||Dynamic current sharing in KA/KU LNB design|
|US8948209 *||Dec 10, 2009||Feb 3, 2015||Stmicroelectronics (Rousset) Sas||Transmission over an 12C bus|
|US9210015 *||Jun 30, 2014||Dec 8, 2015||Infineon Technologies Ag||Edge-based communication|
|US9300235 *||Mar 27, 2013||Mar 29, 2016||Allegro Microsystems, Llc||System and method for serial communication by an electronic circuit|
|US9325203 *||Jul 24, 2012||Apr 26, 2016||Binh Nguyen||Optimized power consumption in a gaming device|
|US9454215||May 31, 2013||Sep 27, 2016||Stmicroelectronics S.R.L.||Power management architecture based on microprocessor architecture with embedded and external non-volatile memory|
|US9455849 *||Nov 6, 2015||Sep 27, 2016||Infineon Technologies Ag||Edge-based communication|
|US9486697||Mar 13, 2013||Nov 8, 2016||Nguyen Gaming Llc||Asynchronous persistent group bonus games with preserved game state data|
|US9486704||Mar 15, 2013||Nov 8, 2016||Nguyen Gaming Llc||Social gaming|
|US9509444||Jun 27, 2014||Nov 29, 2016||Infineon Technologies Ag||Efficient checksum communication between devices|
|US9559519||Aug 16, 2016||Jan 31, 2017||Yehuda Binder||Sequentially operated modules|
|US9564018||Mar 15, 2013||Feb 7, 2017||Nguyen Gaming Llc||Temporary grant of real-time bonus feature|
|US9576425||Mar 15, 2013||Feb 21, 2017||Nguyen Gaming Llc||Portable intermediary trusted device|
|US9583940||Jun 23, 2016||Feb 28, 2017||Yehuda Binder||Sequentially operated modules|
|US9590420||Jun 23, 2016||Mar 7, 2017||Yehuda Binder||Sequentially operated modules|
|US9595161||Nov 14, 2011||Mar 14, 2017||Nguyen Gaming Llc||Social gaming|
|US9595828||Jun 23, 2016||Mar 14, 2017||Yehuda Binder||Sequentially operated modules|
|US9600976||Mar 14, 2014||Mar 21, 2017||Nguyen Gaming Llc||Adaptive mobile device gaming system|
|US9607474||Mar 13, 2013||Mar 28, 2017||Nguyen Gaming Llc||Reconfigurable gaming zone|
|US9612994 *||Sep 18, 2013||Apr 4, 2017||Nvidia Corporation||Snoop and replay for completing bus transaction|
|US9621339 *||Jun 23, 2016||Apr 11, 2017||Quanta Computer Inc.||Host devices and data transmission methods|
|US9626826||Jun 10, 2010||Apr 18, 2017||Nguyen Gaming Llc||Location-based real-time casino data|
|US9630096||Oct 1, 2012||Apr 25, 2017||Nguyen Gaming Llc||Control of mobile game play on a mobile vessel|
|US20070082610 *||Oct 12, 2006||Apr 12, 2007||Kesse Ho||Dynamic current sharing in Ka/Ku LNB design|
|US20100017654 *||Jul 17, 2009||Jan 21, 2010||Wishneusky John A||Device-to-Device Communication Bus for Distributed Power Management|
|US20110110130 *||Nov 6, 2009||May 12, 2011||Wang Hsueh-Cheng||Interleaved-pwm power module system and method for operating the same|
|US20110255560 *||Dec 10, 2009||Oct 20, 2011||Stmicroelectronics (Rousset) Sas||Transmission over an 12c bus|
|US20120066423 *||Sep 13, 2010||Mar 15, 2012||Boon Siang Choo||Inter-integrated circuit bus multicasting|
|US20140031126 *||Jul 24, 2012||Jan 30, 2014||Binh Nguyen||Optimized power consumption in a gaming device|
|US20140292247 *||Mar 27, 2013||Oct 2, 2014||Allegro Microsystems, Inc.||System and Method for Serial Communication by an Electronic Circuit|
|US20150048779 *||Feb 28, 2014||Feb 19, 2015||Samsung Sdi Co., Ltd.||Battery system, method of controlling battery system and energy storage system including the same|
|US20150081937 *||Sep 18, 2013||Mar 19, 2015||Nvidia Corporation||Snoop and replay for bus communications|
|US20150270994 *||Jun 30, 2014||Sep 24, 2015||Infineon Technologies Ag||Edge-based communication|
|U.S. Classification||710/3, 323/282, 713/340, 323/222|
|International Classification||G06F3/00, G05F1/40|
|Aug 5, 2005||AS||Assignment|
Owner name: ZILKER LABS, INC., TEXAS
Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:FERNALD, KENNETH W.;TEMPLETON, JAMES W.;WISHNEUSKY, JOHNA.;REEL/FRAME:016878/0283
Effective date: 20050805
|Apr 29, 2010||AS||Assignment|
Owner name: MORGAN STANLEY & CO. INCORPORATED,NEW YORK
Free format text: SECURITY AGREEMENT;ASSIGNORS:INTERSIL CORPORATION;TECHWELL, INC.;INTERSIL COMMUNICATIONS, INC.;AND OTHERS;REEL/FRAME:024312/0001
Effective date: 20100427
Owner name: MORGAN STANLEY & CO. INCORPORATED, NEW YORK
Free format text: SECURITY AGREEMENT;ASSIGNORS:INTERSIL CORPORATION;TECHWELL, INC.;INTERSIL COMMUNICATIONS, INC.;AND OTHERS;REEL/FRAME:024312/0001
Effective date: 20100427
|Jul 3, 2012||CC||Certificate of correction|
|Jul 26, 2013||FPAY||Fee payment|
Year of fee payment: 4
|Mar 18, 2014||AS||Assignment|
Owner name: ZILKER LABS LLC, DELAWARE
Free format text: CHANGE OF NAME;ASSIGNOR:ZILKER LABS, INC.;REEL/FRAME:032467/0199
Effective date: 20111223
Owner name: INTERSIL AMERICAS LLC, CALIFORNIA
Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:ZILKER LABS LLC;REEL/FRAME:032466/0332
Effective date: 20130329