The present disclosure relates generally to audio, video and automation devices in and about residential and commercial structures, and more specifically to Power-over-Ethernet (PoE) powered devices.
PoE is becoming an increasingly popular method of powering audio devices (e.g., speakers, amplifiers, receivers, etc.), video device (e.g., televisions, monitors, video decoders. etc.), automation devices (e.g., controllers, cameras, door locks, lighting devices, motor-actuated devices, etc.) and other types of powered devices in and about residential and commercial structures. Using PoE technology, power sourcing equipment (PSE), such as a PoE switch, delivers both power and data to a powered device over twisted pair Ethernet cabling (e.g., Cat 5 cabling, Cat 6 cabling, etc.). Providing both power and data over Ethernet cabling can greatly simply wiring installation and save cost. Different PoE standards have been released by the Institute of Electrical and Electronic Engineers (IEEE) to regulate the amount of power delivered to powered devices. These standards include IEEE 802.3af, 802.3at and 802.3bt. IEEE 802af was the first PoE standard, being introduced in 2003. It provided 12.95-15.4 watts (W) of continuous power per port, which at the time was sufficient for the capabilities of powered devices.
However, as technology developed, many devices demanded more power. For that reason, IEEE 802.3at was released in 2009, which specified 25-30 W of continuous power per port. However, again new technology demanded more power. In 2018, IEEE 802.3bt was developed, which further increased continuous power per port to 51 W-100 W, depending on the variant. One variant of IEEE 802.3bt, referred to as Type 3 PoE, can carry up to 60 W of continuous power per port, with a minimum ensured continuous power on each port of 51 W. Another variant of IEEE 802.3bt, referred to as Type 4 PoE, can carry up to 100 W of continuous power per port, with a minimum ensured continuous power on each port of 71 W.
While the 71 W of ensured continuous power of Type 4 PoE is an improvement over past standards, even at its time of release it is insufficient for some devices that could benefit from PoE technology. For example, some audio device, such as speakers, may have a peak power requirement that exceeds 71 W at the highs in the audio waveform. Likewise, some home automation devices, such as motor-actuated devices, may draw inrush current that exceeds 71 W when energized. In general, audio, video, home automation devices and other devices may require large amounts of power during at least some periods of their operation. As technology progresses, it is likely more and more devices will demand more power, causing Type 4 PoE to lose its viability, much like its predecessors.
While additional standards may be developed to supersede IEEE 802.3bt, that provide more than 71 W of ensured continuous power, ever increasing standards are not a long term solution. As technology marches forward, power demands are likely to go up and up, while there are theoretical limits on how much continuous power can be passed over Ethernet cabling. At some point, new standards will be unable to further increase continuous power that can be sent over Ethernet cabling. While other cabling may support greater continuous power, there is a massive pre-installed base of legacy cabling, and installers are familiar with its installation procedures. Accordingly, shifting to a new cabling technology may not be a desirable solution.
Accordingly, there is a need for new techniques for addressing the power requirements of PoE powered devices, that can address the problem in a different way.
In various example embodiments, a battery-assisted PoE powered device is provided that includes a local battery pack for providing a burst of power to a device load in excess of the continuous power available via PoE. A charger/path controller charges the local battery pack during periods of time when the device load consumes less power than available via PoE (e.g., consumes less than the 71 W of guaranteed continuous power under IEEE 802.3bt). During periods of time when the device load demands more power than available via PoE (e.g., when peak power is demanded by an audio speaker, when inrush occurs in a motor, or for various types of intermittent devices when they are activated) the charger/path controller discharges the battery pack, to drive the device load with a combination of PoE and battery power. The charger/path controller may monitor battery charge level, and upon reaching a charge threshold, throttle power consumption of the device load (such that the powered device provides a reduced-level of functionality) or deactivate the device load completely (such that functionality is temporarily suspended) to allow the local battery pack to recharge. With proper battery pack sizing, the battery-assisted PoE powered device may provide high power levels in the vast majority of typical use cases, with functionality reductions/deactivations only occurring under atypical use.
In one example embodiment, a battery-assisted PoE powered device includes at least a port configured to receive an Ethernet cable via which PoE is provided, a local battery pack including one or more cells, a device load configured to consume power to provide functionality of the powered device, and a charger/path controller. The consumed power may sometimes exceed an amount of power available via PoE. The charger/path controller may charge the local battery pack during periods of time when the device load consumes less power than the amount available via PoE, and discharge the local battery pack and drive the device load with a combination of PoE and battery power from the local battery pack during periods of time when the device load demands more power than the amount of power available via PoE.
It should be understood that a variety of additional features and alternative embodiments may be implemented other than those discussed in this Summary. This Summary is intended simply as a brief introduction to the reader, and does not indicate or imply that the examples mentioned herein cover all aspects of the disclosure, or are necessary or essential aspects of the disclosure.
The description below refers to the accompanying drawings of example embodiments, of which:
The battery-assisted PoE powered device 100 includes a port (e.g., a RJ-45 port) 110 configured to receive an Ethernet cable (e.g., a Cat 5 cable, a Cat 6 cable, etc.) via which PoE is provided. A PoE powered device controller 120 is coupled to the port. The PoE powered device controller 120 is responsible for communicating with a PSE that provides the power, exchanging signature and classification information in accordance with a standard, so that the PSE provides the right amount of power over the Ethernet cable. In one embodiment, the standard is IEEE 802.3bt and the amount of power is up to 71 W of guaranteed continuous power. The PoE powered device controller 120 may include an integrated dc-to-dc converter.
The PoE powered device controller 120 is coupled to a charger/path controller 130 (the details of which are discussed further below), which is in turn coupled to a device load 140 and a local battery pack 150. The device load 140 is configured to consume power to provide functionality of the battery-assisted PoE powered device 100. Depending on the nature of the battery-assisted PoE powered device 100, the device load 140 and the functionality it provides may take many forms. For instance, in an example embodiment where the battery-assisted PoE powered device 100 is a powered speaker, the device load 140 may include one or more built-in amplifiers that amplify a low-level audio signal, or portion thereof, to a power level sufficient to run a driver (not shown) coupled to speaker cone, to provide the functionality of playing audio. The low-level audio single may be provided over the Ethernet cable, or otherwise provided to the powered speaker. Likewise, in an example embodiment where the battery-assisted PoE powered device 100 is a motor-actuated device, the device load 140 may include a motor and the functionality may be to actuate some object in or about the residential or commercial structure (e.g., open a window blind, close a door, etc.). It should be understood that a wide variety of other type of device loads 140 are possible.
The device load 140 may have power consumption that sometimes exceeds the amount of power available via PoE. For example, in the case of IEEE 802.3bt, the device load may sometimes consume more than 71 W. Such higher power consumption may be due to any of a number of reasons. For instance, in an example embodiment where the battery-assisted PoE powered device 100 is a powered speaker, a built-in amplifier may have a peak power requirement that exceeds the amount of power available via PoE at the highs in the audio waveform. As a rule of thumb, audio may be assumed to have a peak power requirement that is about eight times larger (referred to as a “crest factor”) than and average power requirement, with the exact crest factor depending on the actual audio content. While the average power requirement of a powered speaker may be below the amount of continuous power available via PoE, the peak power requirement may exceed it.
Likewise, in an example embodiment where the battery-assisted PoE powered device 100 is a motor-actuated device, a motor may draw an in-rush current such that it has a momentary power requirement that exceeds the amount of power available via PoE. As a general rule, the power requirement at inrush may be several times larger than the steady state power requirement. While the steady state power requirement may be below the amount of continuous power available via PoE, the power requirement at inrush may exceed it.
Further, a variety of battery-assisted PoE powered devices 100 (including powered speakers, motor-actuated devices, and others) may typically be operated only intermittently. For example, in an example embodiment where the battery-assisted PoE powered device 100 is a powered speaker, the speaker may be used in an application where the built-in amplifier is typically only operated for a limited period of time (e.g., 5 minutes, 1 hour, etc.). The rest of the time it may be idle. Likewise, in an example embodiment where the battery-assisted PoE powered device 100 is a motor-actuated device the device may be used in an application where the motor is typically is only operate briefly (e.g., for 10 seconds, 1 minute, etc.) to perform a certain task. Again, for the rest of the time it may be idle. During periods of operation, the device load 140 may have a power requirement that exceeds the amount of power available via PoE. However, there may be long periods where the device load 140 does not have, or has a negligible, power requirement.
The local battery pack 150 includes one or more cells, for example, lithium ion cells, or cells utilizing another battery chemistry. The cells may be selected to have a maximum discharge rate that accommodates the difference between the maximum power consumption of the device load 140 (e.g., the peak power requirement, inrush power requirement, operating power requirement, etc.) and the power available via PoE, and a capacity that accommodates a maximum desired run time of the device load 140 given its average draw rate from the local battery pack 150. Depending on the embodiment, the local battery pack 150 may be hard-wired, such that it is substantially a permanent part of the battery-assisted PoE powered device 100, or connected via one or more sockets or plugs, such that it is user-replaceable. In some cases, the local battery pack 150 may be located within a wall or ceiling cavity. For example, in an example embodiment where the battery-assisted PoE powered device 100 is an in-wall or in-ceiling powered speaker, the local battery pack 150 may be disposed internal to the speaker can within a wall or ceiling cavity.
The charger/path controller 130 is configured to control charging and discharging of the local battery pack 150, to provide a burst of power when needed by the device load 140. The charger/path controller 130 may be a programmable voltage and current controller with support for battery charging and power management. The charger/path controller 130 charges the local battery pack 150 during periods of time when the device load 140 consumes less power than the amount available via PoE. During periods of time when the device load 140 consumes less power than the amount available via PoE, the charger/path controller 130 drives the device load 140 with only power from PoE. During periods of time when the device load 140 demands more power than the amount of power available via PoE, the charger/path controller 130 drives the device load 150 with a combination of PoE and battery power from the local battery pack 150, balancing the amount of power drawn from the battery pack 150 as the power demand fluctuates.
While the local battery pack 150 is preferably sized to have sufficient capacity to support typical use cases, under atypical use it may become depleted. The charger/path controller 130 may monitor battery charge level and determine whether the level has reached one or more charge thresholds. In response to battery charge level having reached a charge threshold, the local battery pack 150 may throttle power consumption of the device load 140 such that it still provides functionality, but at a reduced level, or may deactivate the device load 140 completely. For instance, in an example embodiment where the battery-assisted PoE powered device 100 is a powered speaker, the charger/path controller 130 may adjust the volume of the built-in amplifier when a first “low battery” threshold is reached. Further, the charger/path controller 130 may deactivate the built-in amplifier entirely when a second “empty” threshold is reached, to prevent damage to the cells of the local battery pack 150. In an example embodiment where the battery-assisted PoE powered device 100 is a motor-actuated device, the charger/path controller 130 may simply deactivate the motor when a single charge threshold is reached, as it may not be possible or practical to throttle the motor (e.g., the motor may be incapable of performing its task at reduced power).
In some implementations, the charger/path controller 130 may also determine a state of health (SOH) (i.e. a measure of the battery pack's ability to store and deliver power in comparison to a new battery pack) of the local battery pack 150. In response to the SOH having reached a SOH threshold, the charger/path controller 130 may provide a signal that the local battery pack 150 should be replaced (e.g., in the case of user-replaceable local battery pack) or that the entire battery-assisted PoE powered device 100 should be replaced (e.g., in the case of a hard-wired local battery pack). The signal may be a local signal (e.g., a tone, indicator light, audio message, etc.) that is perceived by a user from the device itself, or a remote signal (e.g., a message sent the Ethernet cable) to a remote system controller or other remote device that provides a message to the user in its own user interface.
It should be understood that a wide variety of adaptations and modifications may be made to the above described techniques, producing a number of alternative embodiments. In general, programmable functions may be implemented in software, hardware or various combinations thereof. Software implementations may include electronic device-executable instructions stored in a non-transitory electronic device-readable medium, such as a volatile memory, a persistent storage device, or other tangible medium. Hardware implementations may include programmable logic circuits, application specific integrated circuits, and/or other types of hardware components. Further, combined software/hardware implementations may execute some functionality using electronic device-executable instructions stored in a non-transitory electronic device-readable medium, and other functionality using hardware components. The above description should not be limited to one mode of construction or operation. Above all, it should be understood that the above description is meant to be taken only by way of example.
Number | Name | Date | Kind |
---|---|---|---|
7941677 | Penning | May 2011 | B2 |
8214680 | Tassinari | Jul 2012 | B1 |
8873370 | Robitaille | Oct 2014 | B2 |
9377794 | Dwelley | Jun 2016 | B1 |
10749375 | Kanarellis | Aug 2020 | B2 |
20060186739 | Grolnic | Aug 2006 | A1 |
20060263925 | Chandler | Nov 2006 | A1 |
20080168283 | Penning | Jul 2008 | A1 |
20080175227 | Moore | Jul 2008 | A1 |
20080250255 | Diab | Oct 2008 | A1 |
20090243391 | Susong, III | Oct 2009 | A1 |
20100223480 | Fratti | Sep 2010 | A1 |
20100244573 | Karnick | Sep 2010 | A1 |
20110115430 | Saunamaki | May 2011 | A1 |
20110133551 | Moller | Jun 2011 | A1 |
20120200157 | Ohi | Aug 2012 | A1 |
20120271477 | Okubo | Oct 2012 | A1 |
20130169050 | Tseng | Jul 2013 | A1 |
20140167918 | Stern | Jun 2014 | A1 |
20140270235 | Shin et al. | Sep 2014 | A1 |
20150177800 | Kanan | Jun 2015 | A1 |
20150180276 | Kanarellis | Jun 2015 | A1 |
20150237424 | Wilker | Aug 2015 | A1 |
20150312048 | Bodo | Oct 2015 | A1 |
20160006242 | Yamada | Jan 2016 | A1 |
20160064938 | Balasubramanian | Mar 2016 | A1 |
20160197732 | Burnett | Jul 2016 | A1 |
20160273722 | Crenshaw | Sep 2016 | A1 |
20160294184 | Al-Atat | Oct 2016 | A1 |
20160349829 | Spiel | Dec 2016 | A1 |
20170026188 | Herzel | Jan 2017 | A1 |
20170046289 | Hundal | Feb 2017 | A1 |
20170104603 | Chen | Apr 2017 | A1 |
20170250828 | Buchanan | Aug 2017 | A1 |
20170356243 | Feldstein | Dec 2017 | A1 |
20180013319 | Kanarellis | Jan 2018 | A1 |
20180035518 | Cook | Feb 2018 | A1 |
20180054083 | Hick | Feb 2018 | A1 |
20180054347 | Kojima | Feb 2018 | A1 |
20180219635 | Sipes, Jr. | Aug 2018 | A1 |
20180220237 | Tabatabai | Aug 2018 | A1 |
20180228007 | Siefer | Aug 2018 | A1 |
20180235055 | Yadav | Aug 2018 | A1 |
20180294982 | Boemi | Oct 2018 | A1 |
20190013696 | Kanarellis | Jan 2019 | A1 |
20190081805 | Frezza | Mar 2019 | A1 |
20190116104 | Mei | Apr 2019 | A1 |
20190165575 | Long | May 2019 | A1 |
20190212797 | Karidis | Jul 2019 | A1 |
20190235600 | Staude | Aug 2019 | A1 |
20190278347 | Goergen | Sep 2019 | A1 |
20190297710 | Crenshaw | Sep 2019 | A1 |
20190301241 | Campagna | Oct 2019 | A1 |
20190312741 | Chen | Oct 2019 | A1 |
20200092052 | MacAfee | Mar 2020 | A1 |
20200145495 | Coffey | May 2020 | A1 |
20200235607 | Kanarellis | Jul 2020 | A1 |
Number | Date | Country |
---|---|---|
WO-2017062995 | Apr 2017 | WO |
WO-2020086204 | Apr 2020 | WO |
Entry |
---|
“IP POE Powered Ceiling Speaker IP-600POE,” CMX, CMX Audio, Apr. 24, 2015, pp. 1-3. |
“Notification of Transmittal of the International Search Report and the Written Opinion of the International Searching Authority, or the Declaration,” International Filing Date: Jun. 16, 2020, International Application No. PCT/US2020/037857, Applicant: Savant Systems, Inc., dated Sep. 15, 2020, pp. 1-13. |