Active charge through of a peripheral device

A method for port policy management for active charge through of a peripheral device that has a first communication port and a second communication port may include detecting whether a valid power connection exists at the peripheral device, in response to detecting the valid power connection, determining a relationship between the first communication port and the second communication port, based on the relationship, determining, by the peripheral device, a power relationship among the peripheral device, the first communication port, and the second communication port, selectively configuring the first communication port, the second communication port, and the peripheral device to match the power relationship, and enabling active charging through of the peripheral device if active charging through is supported by the power relationship.

FIELD OF DISCLOSURE

The present disclosure relates in general to circuits for electronic devices, including without limitation audio devices, including personal audio devices such as wireless telephones and media players, and more specifically, to systems and methods relating to providing and managing active charge through of a peripheral device.

BACKGROUND

Electronic devices are prevalent and in everyday use. Electronic devices utilize communication bus protocols to be able to communicate with and transmit/receive power to and from each other in a more uniform or standardized manner Universal bus communication protocols, such as Universal Serial Bus (“USB”), as well as proprietary bus communication protocols, such as the bus protocol for Apple's Lightning® bus connectors, exist and are well known.

USB is a well-known industry bus communication protocol for electronic devices. USB provides a well-defined standard protocol that allows electronic devices to communicate with each other. Various versions of the USB protocol exist, such as USB 1.x, USB 2.0, USB 3.0, USB 3.1. USB-C and USB-PD protocols add the ability to provide power delivery. Apple, Inc. has established its own proprietary bus communication protocol that is compatible and compliant with its Lightning bus connector that allows devices to communicate with and respectively provide/receive power to and from Apple devices.

It is well known that many portable hosts implementing bus communication protocol connectors (such as USB-C or Lightning connectors) provide a single port only that is useful for either communicating data or providing power or both under specific conditions. Hubs and docks provide multiple ports that resolve the single port limitation and have the ability to provide power to an electronic device and a portable host. However, both hubs and docks add a significant amount of complexity and cost to overcoming the single port limitation and power provision problem. Furthermore, hubs and ports (such as USB-C hubs and ports) with at least one downward facing port (DFP) require additional testing for certification (e.g., USB-C certification).

To avoid the complexity of hubs and docks and certification requirements, passthrough charging (or pass-through charging) has been adopted and used in electronic devices via some bus communication protocols. Passthrough charging allows an electronic device that is coupled to a power source and to a host to use the bus communication protocol to allow normal operations between the electronic device and the host, and also to allow charge to pass through the device to a host. The host receives the power/charge from the power source and the host, in turn, powers/charges the electronic device also via the bus communication protocol. Passthrough charging may not allow the power source to directly power/charge the electronic device but always requires that the host first receive the passthrough power/charge and then, secondly in turn, the host uses its power source to power/charge the electronic device. Passthrough charging allows devices to avoid having to have at least one DFP.

FIGS. 1A and 1Billustrate an example Apple Lightning compatible headphone device10(or a generic peripheral device) that provides the passthrough charging feature, as is known in the art.FIG. 1Adepicts an external view of headphone device10whileFIG. 1Bis an illustration of a block diagram depicting headphone device10interfaced with a power charger (PW CHG)11and a host14. Example hosts14include but are not limited to smart phones, tablets, and personal computers. Referring toFIGS. 1A and 1B, headphone device10may be coupled to host14via Lightning port12B and Lightning host port16. First contacts of Lightning ports12B and16may be used to provide normal operations and communicate data via data block (DATA)19of host14and headphone data block (HP DATA)15of headphone device10between the headphone device10and host14. When power charger11is coupled to headphone device10via Lightning port12A, charge may be passed through headphone device10via passthrough line (PT) to host14from Lightning port12A through Lighting port12B to Lightning host port16. Second contacts of Lightning ports12B and16may be used to provide power between the host14and the headphone device10. Host14may receive charge (e.g., from power charger11) at its battery (BATT)17. Host14, in turn, may provide the charge to headphone device10by providing charge from its power (PWR) block18to headphone power block (HP PWR)13. In this embodiment, power charger11may never directly power/charge headphone device10, and power/charge for headphone device10may also have to be passed through headphone device10to host14and host14, in turn, may have to power/charge the headphone device10. An example of such headphone device10is Pioneer Rayz Plus® Lightning headphones/earbuds.

FIGS. 2A, 2B, and 2Cillustrate an example adapter device20, as known in the art, that may allow electronic device operations between it and a host as well as providing passthrough charging which allows charge to pass through the electronic device to the host and may allow powering/charging of the electronic device by the host.FIG. 2Adepicts adapter device20having bus communication ports22A,22B, and22C. Bus communication ports22A,22B,22C,12C, and14A may be Lighting ports, USB-C ports, or any other type of bus communication ports. Ports22A,22B,22C,12C, and16A are not limited to any type and can each be of a female type and/or a male type. Similar to host14, example hosts14A may include but are not limited to smart phones, tablets, and personal computers.

Referring now toFIG. 2B, headphone device10A is shown coupled to adapter device20via ports12C and22B, and host14A is shown coupled to adapter device20via ports16A and22C. First contacts of ports16A,22C, and12C may be used to provide normal operations and communicate data via data block (DATA)19A of host14A and headphone device data block (HP DATA)15A of headphone device10A through adapter device20. When power charger11is coupled to adapter device20via port22A, charge may pass from power charger11through adapter device20to host14A (e.g., passthrough charging) via passthrough line (PT) from22A to port22C to host port16A. Second contacts of ports22C and16A may be used to provide power from the power charger11to the host14A. Host14A may receive the charge (e.g., from power charger11) at its battery (BATT)17A. Host14A, in turn, may provide the charge to headphone device10A through adapter device20by providing the power/charge from a power (PWR) block18A of host14A to a headphone power block (HP PWR)13A via ports16A,22C, and22A. In this embodiment, the power charger11may never directly power/charge headphone device10A, and power/charge for the headphone device10A may also have to be first passed through adapter device20from power charger11to host14A and then host14A, in turn, may have to power/charge headphone device10A.

Referring now toFIG. 2C, headphone device10A is shown instead coupled to adapter device20via ports12C and22A, and host14A is shown coupled to adapter device20via ports16A and22C. First contacts of ports16A,22C, and12C may be used to provide normal operations and communicate data via data block (DATA)19A of host14A and headphone device data block (HP DATA)15A of headphone device10A through the adapter device20. When power charger11is coupled to adapter device20via port22B, charge may be passed from power charger11through adapter device20to host14A (e.g., passthrough charging) via passthrough line (PT) from port22B through port22C to host port16A. Second contacts of ports22C and16A may be used to provide power from power charger11to host14A. Host14A may receive the charge (e.g., from power charger11) at its battery (BATT)17A. Host14A, in turn, may provide the charge to headphone device10A through adapter device20by providing the charge from power (PWR) block18A of host14A to headphone power block (HP PWR)13A via ports16A,22C, and22B. In this embodiment, power charger11may never directly power/charge headphone device10A, and power/charge for headphone device10A may also have to be first passed through adapter device20from power charger11to host14A and then host14A, in turn, may have to power/charge headphone device10A.

An example of such adapter device20is Belkin International Inc.'s Lightning Audio+Charge RockStar™ adapter. Also, as indicated before, another example of adapter device20is a USB-C adapter device that may provide a passive analog audio adapter with passthrough charging capability. Such a USB-C adapter may have the three ports22A,22B, and22C in which ports22A and22B may be the respective headphone (e.g., data) port and power port while port22C may be the host port. However, such a USB-C adapter device has limits to minimum default power (e.g., 500 milliamps), and thus charge times of the host may be long. Also, such adapter may be a fixed function analog interface and thus may not support any of the other functions defined by the USB standard (e.g., mass storage device, keyboard, mouse, etc.).

Peripheral devices are well known in the art. A peripheral device is not a hub or a dock or an adapter device, such as adapter device20. A peripheral device may be an ancillary device that is used to communicate information to a host and vice versa. One key disadvantage of existing approaches to passthrough charging is that power provided through a power charger may have to be managed and split between the host and the peripheral device.FIG. 3illustrates an example high-level block diagram depicting this disadvantage of existing approaches to passthrough charging. Passthrough charging using existing approaches may be done serially, such that power from a power charger is provided serially. Because power is provided serially, the amount of power being provided to the host and peripheral device may need to be split accordingly. Also, the amount of power being provided by the power charger11may be limited to the maximum power that the host14is able to receive. In the example ofFIG. 3, the block diagram depicts that power charger11may be capable of providing 12 watts. The 12 watts provided by power charger11may be passed through the peripheral device10via passthrough line (PT) and may first be received by host14. Because host14needs to in turn provide peripheral device10with 3 Watts (3 W), host14is powered with only the remaining 9 Watts (9 W=12 W−3 W). Another key disadvantage is that if the host14is not coupled to peripheral device10, using existing approaches, peripheral device10cannot be charged at all because power charger11cannot directly charge peripheral device10. Such a direct charging feature is important and beneficial if peripheral device10is to be a standalone or wireless device, such as a wireless headphone/headset/earbuds.

SUMMARY

In accordance with the teachings of the present disclosure, one or more disadvantages and problems associated with providing and managing active charge through in a peripheral device may be reduced or eliminated.

In accordance with embodiments of the present disclosure, a method may be provided for port policy management for active charge through of a peripheral device that operates on a communication protocol and has a first communication port and a second communication port, wherein the first communication port and the second communication port each comprises a respective first electrical contact for carrying signals of the communication protocol, and a respective second electrical contact for transmitting and receiving electrical power from a source of electrical energy. The method may include detecting whether a valid power connection exists at the peripheral device, in response to detecting the valid power connection, determining a relationship between the first communication port and the second communication port, based on the relationship, determining, by the peripheral device, a power relationship among the peripheral device, the first communication port, and the second communication port, selectively configuring the first communication port, the second communication port, and the peripheral device to match the power relationship, and enabling active charging through of the peripheral device if active charging through is supported by the power relationship.

In accordance with these and other embodiments of the present disclosure, a method may be provided for port policy management for active charge through of a peripheral device that operates on a communication protocol and has a first communication port and a second communication port, wherein the first communication port and the second communication port each comprises a respective first electrical contact for carrying signals of the communication protocol, and a respective second electrical contact for transmitting and receiving electrical power from a source of electrical energy. The method may include estimating power losses associated with charging a host coupled to the device through one of the first communication port and the second communication port and accounting for the power losses when the power is being provided to the host via active charging through of the peripheral device between the second electrical contact of the first communication port and the second electrical contact of the second communication port.

In accordance with these and other embodiments of the present disclosure, a peripheral device that operates on a communication protocol may be integral to a peripheral device assembly including a first communication port, a second communication port, wherein the first communication port and the second communication port each comprises a respective first electrical contact for carrying signals of the communication protocol and a respective second electrical contact for transmitting and receiving electrical power from a source of electrical energy, and a peripheral device, wherein the peripheral device may be configured to perform port policy management for active charge through of the peripheral device. The peripheral device may be configured to detect whether a valid power connection exists at the peripheral device, in response to detecting the valid power connection, determining a relationship between the first communication port and the second communication port, based on the relationship, determine a power relationship among the peripheral device, the first communication port, and the second communication port, selectively configure the first communication port, the second communication port, and the peripheral device to match the power relationship, and enable active charging through of the peripheral device if active charging through is supported by the power relationship.

In accordance with these and other embodiments of the present disclosure, a peripheral device that operates on a communication protocol may be integral to a peripheral device assembly including a first communication port, a second communication port, wherein the first communication port and the second communication port each comprises a respective first electrical contact for carrying signals of the communication protocol and a respective second electrical contact for transmitting and receiving electrical power from a source of electrical energy, and a peripheral device, wherein the peripheral device may be configured to perform port policy management for active charge through of the peripheral device. The peripheral device may be further configured to estimate power losses associated with charging a host coupled to the device through one of the first communication port and the second communication port and account for the power losses when the power is being provided to the host via active charging through of the peripheral device between the second electrical contact of the first communication port and the second electrical contact of the second communication port.

DETAILED DESCRIPTION

A system and method for port policy management in actively charging through a peripheral device that has a first communication port and a second communication port are disclosed. A host and a power charger may couple to the peripheral device. The peripheral device, host, power charger, and other such devices and their respective ports may communicate and transmit/receive power in accordance with a communication bus protocol. Such a protocol may include but is not limited to standard protocols, such as USB protocols (USB-C and USB-PD protocols), or a proprietary bus communication protocol, including but not limited to the proprietary bus communication protocol that supports and is compatible/compliant with the Apple Lightning bus connector.

FIG. 4illustrates an example high-level block diagram of a system for active charge through, in accordance with embodiments of the present disclosure. In contrast to existing approaches to passthrough charging that perform charge through in a serial manner, in the system depicted inFIG. 4, active charge through may be performed in parallel, such that power is provided in parallel to both a peripheral device and a host. Because power is provided in parallel, the amount of power being provided to the host and the peripheral device does not need to be split as required by existing approaches (e.g., as shown inFIG. 3). In the example ofFIG. 4, power charger11may provide 15 watts, as opposed to the 12 watts provided in the prior art system ofFIG. 3. For example, 12 watts of the 15 watts provided by power charger11may be directly provided to host14and is not passed through peripheral device101. Because peripheral device101is also directly coupled to power charger11and because host14does not need to manage and in turn provide power to peripheral device101, peripheral device101may obtain 3 watts directly from power charger11without any loss or reduction of power being provided from power charger11to host14. Such a direct charging feature for peripheral device101is beneficial because peripheral device101may be a standalone or wireless device, such as a wireless headphone/headset/earbuds. Such an approach to active charge through may allow a peripheral device to be charged without the presence of a host.

FIG. 5Aillustrates an example peripheral device assembly100having a peripheral device101, a first communication port102, a second communication port104, and a power coupling network106, in accordance with embodiments of the present disclosure. Power coupling network106may have switches108,110, and112coupled in the manner shown inFIG. 5A. When only first communication port102provides a valid power connection, switch108may be activated and switches110and112may remain inactive. Thus, in such a scenario, power may only be provided from first communication port102to peripheral device101. By switches110and112remaining inactive, second communication port104may be isolated from the peripheral device101and first communication port102. When only second communication port104provides a valid power connection, switch112may be activated and switches110and108may remain inactive. Thus, in this case, power is only provided from second communication port104to peripheral device101. By switches110and108remaining inactive, first communication port102may be isolated from the peripheral device101and second communication port104.

One skilled in the art may recognize that first communication port102and second communication port104may be logically and operationally equivalent, and thus the description below of the various embodiments of the disclosure for one of the ports may apply to the other, as appropriate.

FIG. 5Billustrates another example diagram of a peripheral device101implemented as a USB-C device in a USB-C device assembly with a first communication port102(first USB-C port102), a second communication port104(second USB-C port104), and a power coupling network106that uses threshold voltages VTH1and VTH2to enable or disable active charge through operation, in accordance with embodiments of the present disclosure.FIG. 5Bmay be identical toFIG. 5Ain all material respects except thatFIG. 5Bdepicts peripheral device101as a USB-C device that uses threshold voltages VTH1and VTH2.

FIG. 6Aillustrates an example flowchart of a method200A for active charge through entry for a peripheral device101, in accordance with embodiments of the present disclosure. As noted above, teachings of the present disclosure may be implemented in a variety of configurations of peripheral device assembly100. As such, the preferred initialization point for method200A and the order of the steps comprising method200A may depend on the implementation chosen. According to certain embodiments, method200may begin at step202. At step206, peripheral device101may make a determination whether a physical connection exists at both first communication port102and second communication port104. If at step206, peripheral device101determines that a physical connection does not exist at both first communication port102and second communication port104, then method200A may remain at step206until such determination is made. On the other hand, if peripheral device101determines that a physical connection does exist at both first communication port102and second communication port104, method200A may proceed to step208A, at which peripheral device101may determine a port relationship within peripheral device101ofFIG. 5A.FIG. 7A, described in further detail below, depicts an example flowchart of a method for carrying out step208A. At step210, peripheral device101may determine whether active charge through is enabled on peripheral device101. If peripheral device101determines that active charge through is not to be enabled, then method200A may proceed again to step206. Otherwise, if peripheral device101determines that active charge through is enabled, method200A may end at step216.

AlthoughFIG. 6Adiscloses a particular number of steps to be taken with respect to method200A, method200A may be executed with greater or fewer steps than those depicted inFIG. 6A. In addition, althoughFIG. 6Adiscloses a certain order of steps to be taken with respect to method200A, the steps comprising method200A may be completed in any suitable order.

Method200A may be implemented using peripheral device101, components thereof, or any other system operable to implement method200A. In certain embodiments, method200A may be implemented partially or fully in software and/or firmware embodied in computer-readable media.

FIG. 6Billustrates an example flowchart of a method200B for active charge through entry for a peripheral device101that is a USB-C device (e.g., as shown inFIG. 5B), in accordance with embodiments of the present disclosure. As noted above, teachings of the present disclosure may be implemented in a variety of configurations of peripheral device assembly100. As such, the preferred initialization point for method200B and the order of the steps comprising method200B may depend on the implementation chosen. Method200B may be similar in many material respects to method200A described above. Accordingly, for purposes of clarity and exposition, only the material differences between method200B and method200A may be discussed below. In method200B, a step204may be added between steps202and206, a step214may be added between steps210and216, and a step208B may be used instead of step208A. In method200B, at step204, peripheral device101may cause a first threshold voltyage VTH1to be made equal to a second threshold voltage VTH2, such that both threshold voltages are made equal to a USB default voltage value in accordance with the USB-C specification. At step206, peripheral device101may make a determination whether a physical connection exists at both first communication port102and second communication port104. If at step206, peripheral device101determines that a physical connection does not exist at both first communication port102and second communication port104, then method200B may remain at step206until such determination is made. On the other hand, if peripheral device101determines that a physical connection does exist at both first communication port102and second communication port104, method200B may proceed to step208B, at which peripheral device101may determine a port relationship within peripheral device101ofFIG. 5B.FIG. 7B, described in further detail below, depicts an example flowchart of a method for carrying out step208B. At step210, peripheral device101may determine whether active charge through is enabled on peripheral device101. If peripheral device101determines that active charge through is not to be enabled, then method200B may proceed again to step206. Otherwise, if peripheral device101determines that active charge through is enabled, method200B may proceed to step214. At step214, peripheral device101may cause a threshold voltage adjustment to be made.FIG. 8, described in further detail below, depicts an example flowchart of a method for carrying out step214. After completion of step214, method200may end at step216.

AlthoughFIG. 6Bdiscloses a particular number of steps to be taken with respect to method200B, method200B may be executed with greater or fewer steps than those depicted inFIG. 6B. In addition, althoughFIG. 6Bdiscloses a certain order of steps to be taken with respect to method200B, the steps comprising method200B may be completed in any suitable order.

Method200B may be implemented using peripheral device101, components thereof, or any other system operable to implement method200B. In certain embodiments, method200B may be implemented partially or fully in software and/or firmware embodied in computer-readable media.

FIG. 7Aillustrates an example flowchart of a method208A for determining the port relationship within a peripheral device101, in accordance with embodiments of the present disclosure. As noted above, teachings of the present disclosure may be implemented in a variety of configurations of peripheral device assembly100. As such, the preferred initialization point for method208A and the order of the steps comprising method208A may depend on the implementation chosen. According to certain embodiments, method208A may begin at step702. At step702, peripheral device101may determine whether the two ports (e.g., first communication port102and second communication port104) are providing power. If at step702, peripheral device101determines that both of the two ports are providing power, then method208A may proceed to step704. Otherwise, if peripheral device101determines at least one of the two ports is not providing power, then method208B may proceed to step710.

At step704, peripheral device101may determine whether one of the two ports (e.g., either first communication port102or second communication port104) is coupled to a power charger (e.g., power charger11). If peripheral device101determines that neither of the two ports is connected to a power charger, method208A may proceed to step706. Otherwise, if peripheral device101determines that one of the two ports is connected to a power charger, method208A may proceed to step712.

At step706, peripheral device101may be powered from the first communication port102. At step708, peripheral device101may enable second communication port104for communication with the bus communication protocol. After completion of step708, step208A of method200may proceed to step210of method200.

At step710, peripheral device101may determine whether a port providing power (e.g., a powered port) is being powered by a power charger. If peripheral device101determines that a powered port is being powered by a power charger, method208A may proceed to step712.

At step712, peripheral device101may be powered from the powered port being powered by a power charger. At step714, peripheral device101may enable the other port (e.g., the non-powered port) as a host port for communication with the bus communication protocol. At step716, peripheral device101may attempt or allow active charge through from the powered port being powered by a power charger to the host port to enable charging of a host coupled to peripheral device101. After completion of step716, step208A of method200may proceed to step210of method200.

At step718, peripheral device101may be powered from the powered port being powered by a power charger and peripheral device101may enable the same port for communication with the bus communication protocol. At step720, peripheral device101may attempt or allow active charge through from a host coupled to peripheral device101to the other port (e.g., the non-powered port). After completion of step720, step208A of method200may proceed to step210of method200.

AlthoughFIG. 7Adiscloses a particular number of steps to be taken with respect to method208A, method208A may be executed with greater or fewer steps than those depicted inFIG. 7A. In addition, althoughFIG. 7Adiscloses a certain order of steps to be taken with respect to method208A, the steps comprising method208A may be completed in any suitable order.

Method208A may be implemented using peripheral device101, components thereof, or any other system operable to implement method208A. In certain embodiments, method208A may be implemented partially or fully in software and/or firmware embodied in computer-readable media.

FIG. 7Billustrates an example flowchart of a method208B for determining the port relationship within peripheral device101implemented as a USB-C device, in accordance with embodiments of the present disclosure. As noted above, teachings of the present disclosure may be implemented in a variety of configurations of peripheral device assembly100. As such, the preferred initialization point for method208B and the order of the steps comprising method208B may depend on the implementation chosen. According to certain embodiments, method208B may begin at step304. At step304, peripheral device101may determine whether the two ports (e.g., first communication port102and second communication port104) are providing power. If at step304, peripheral device101determines that both of the two ports are providing power, then method208B may proceed to step306. Otherwise, if peripheral device101determines that at least one of the two ports are not providing power, then method208B may proceed to step316.

At step306, peripheral device101may determine whether second USB-C port104is willing to accept a power role swap. If second USB-C port104is not willing to accept a power role swap, then method208B may proceed to step308. Otherwise, if USB-C port104is willing to accept a power role swap, then method208B may proceed to step310.

At step308, peripheral device101may accept both first USB-C port102and second USB-C port104acting as power sources. After completion of step308, method208B may proceed to step328.

At step310, peripheral device101may offer a power contract to second USB-C port104(e.g., power contract is negotiated). At step312, peripheral device101may determine whether second USB-C port104accepts the power contract. If second USB-C port104does not accept the power contract, method208B may proceed again to step310. On the other hand, if second USB-C port104accepts the power contract, method208B may proceed to step314. At step314, peripheral device101may enable active charge through. After completion of step314, step208B of method200may proceed to step210of method200.

At step316, peripheral device101may determine whether the power source is a USB charger. If peripheral device101determines that the power source is not a USB charger, method208B may proceed to step318. Otherwise, if peripheral device101determines that the power source is a USB charger, method208B may proceed to step322.

At step318, peripheral device101may cause both first USB-C port102and second USB-C port104to operate as Upstream Facing Ports. At step320, peripheral device101may cause first USB-C port102to provide a data role in communication. After completion of step320, step208B of method200may proceed to step210of method200.

At step322, peripheral device101may cause first USB-C port102to operate as an Upstream Facing Port and second USB-C port104to operate as a dual-rate port. At step324, peripheral device101may cause first USB-C port102to have no data role in communication. At step326, peripheral device101may determine whether a dead battery is coupled to second USB-C port104. If peripheral device101determines that a dead battery is coupled to second USB-C port104, method208B may proceed to step314. On the other hand, if peripheral device101determines that a dead battery is not connected to second USB-C port104, method208B may proceed to step328, at which peripheral device101may disable active charge through. After completion of step328, step208B of method200may proceed to step210of method200.

AlthoughFIG. 7Bdiscloses a particular number of steps to be taken with respect to method208B, method208B may be executed with greater or fewer steps than those depicted inFIG. 7B. In addition, althoughFIG. 7Bdiscloses a certain order of steps to be taken with respect to method208B, the steps comprising method208B may be completed in any suitable order.

Method208B may be implemented using peripheral device101, components thereof, or any other system operable to implement method208B. In certain embodiments, method208B may be implemented partially or fully in software and/or firmware embodied in computer-readable media.

FIG. 8illustrates an example flowchart of a method214for adjusting a threshold voltage VTHassociated with peripheral device101implemented as a USB-C device, in accordance with embodiments of the present disclosure. Threshold voltage VTHis based on a relationship between first threshold voltage VTH1and second threshold voltage VTH2shown inFIG. 5B. As noted above, teachings of the present disclosure may be implemented in a variety of configurations of peripheral device assembly100. As such, the preferred initialization point for method214and the order of the steps comprising method214may depend on the implementation chosen. According to certain embodiments, method214may begin at step404. At step404, peripheral device101may set second threshold voltage VTH2equal to a supply contract minimum. At step406, peripheral device101may set first threshold voltage VTH1equal to a sum of second threshold voltage VTH2and voltage stored voltage drop magnitude. At step408, peripheral device101may determine whether the voltage at second USB-C port104is less than second threshold voltage VTH2. If the voltage at second USB-C port104is not less than second threshold voltage VTH2, then method214may remain at step408until the voltage at second USB-C port104is less than second threshold voltage VTH2. Otherwise, if the voltage at second USB-C port104is less than second threshold voltage VTH2, method214may proceed to step410.

At step410, peripheral device101may determine whether peripheral device101has a lower power mode. If peripheral device101has a lower power mode, method214may proceed to step412. Otherwise, if peripheral device101does not have a lower power mode, method214may proceed to step414.

At step412, peripheral device101may switch to its lower power mode. After completion of step412, method214may proceed again to step408.

At step414, peripheral device101may determine whether a power at second USB-C port104is greater than a USB default power amount. If the power at second USB-C port104is not greater than the USB default power amount, method214may proceed to step416. Otherwise, if the power at second USB-C port104is greater than the USB default power amount, method214may proceed to step418.

At step416, peripheral device101may negotiate a lower source power contract. After completion of step416, method214may proceed again to step408.

At step418, peripheral device101may increase threshold voltage VTH1. At step420, peripheral device101may determine if a first port voltage is below threshold voltage VTH1. If the first port voltage is not below threshold voltage VTH1, method214may proceed again to step408. Otherwise, if the first port voltage is below threshold voltage VTH1, method214may proceed to step422.

At step422, peripheral device101may end active charge through. After completion of step422, step214of method200B may proceed to step216.

AlthoughFIG. 8discloses a particular number of steps to be taken with respect to method214, method214may be executed with greater or fewer steps than those depicted inFIG. 8. In addition, althoughFIG. 8discloses a certain order of steps to be taken with respect to method214, the steps comprising method214may be completed in any suitable order.

Method214may be implemented using peripheral device101, components thereof, or any other system operable to implement method214. In certain embodiments, method214may be implemented partially or fully in software and/or firmware embodied in computer-readable media.

FIG. 9Aillustrates a block diagram of an example peripheral device101coupled to a power charger504A via first communication port102and a host512powered by a battery510, wherein host512is coupled via second communication port104, in accordance with embodiments of the present disclosure. Peripheral device101includes power coupling network106that may be managed and operated by a port policy management for enabling and disabling active charge through (or active-charge-through) operation through peripheral device assembly100. The port policy management may be controlled within the power coupling network106or as a separate block (not shown) outside of the power coupling network106. The port policy management may detect whether a valid power connection exists at the peripheral device101. InFIG. 9A, a valid power connection exists and may be detected at first communication port102because power charger504A, which is coupled to a power source502A via port506A of power charger504A, is coupled to first communication port102.

In response to the valid power connection being detected, a relationship between the first communication port102and the second communication port104may be determined. InFIG. 9A, the first communication port102may have the power role because it is coupled to power charger504A that is, in turn, coupled to power source502A. The second communication port104may be determined in this case to not take on the power role, even though second communication port104is coupled to host512via port508in which host512is driven by battery510. Because the power relationship is determined that first communication port102is to have the power role and second communication port104is to not have the power role, peripheral device101may selectively negotiate between first communication port102and second communication port104so that first communication port102may be assigned the power role while second communication port may not be assigned the power role. After peripheral device101negotiates the power role, power coupling network106may selectively couple first communication port102, second communication port104, and peripheral device101to match a power contract. Peripheral device101may also negotiate a power contract with second communication port104so that a sum of a power representative of a current of the peripheral device101and a maximum power of second communication port104is less than or equal to a power contract with first communication port102.

Depending upon the power contract, power coupling network106may be controlled to respectively allow or not allow active charge through (or active-charging-through) operation through peripheral device assembly100as well as the direct charging of peripheral device101itself. For the embodiments represented byFIG. 9Aand based on the power contract, power coupling network106may be controlled so that switches108and110are activated (e.g., on, enabled, closed) while switch112is deactivated (e.g., off, disabled, open). Activated switch108may allow for directly charging peripheral device101itself via first communication port102while activated switch110may allow for active charge through (or active-charging-through) of peripheral device101from first communication port102to second communication port104so that power charger504A driven by power source502A also charges battery510of host512. Switch112may remain deactivated so that host512may be prevented from having the power role and from being in a power contract to provide power from host512.

For the embodiments represented byFIG. 9A, the valid power connection may be at first communication port102only, and thus first communication port102only may have the power role. For this case, the power contract allows the active charge through (or active-charging-through) of peripheral device assembly100from first communication port102to second communication port104.

FIG. 9Billustrates a block diagram of an example peripheral device101coupled to a power source504B driven by a battery502B and a host512powered by another battery510, in accordance with embodiments of the present disclosure.FIG. 9Bmay be similar toFIG. 9Ain all material respects, except that first communication port102may be coupled to a power source504B driven by a battery502B. Thus, the power source is not in any way limited to a specific power source but may be a power charger driven by a power source, a battery driving a power source, or any other suitable source that provides power to peripheral device101.

If the valid power connection has decoupled and is no longer detected at first communication port102, such as power charger504A being unplugged from power source502A in the embodiments represented byFIG. 9Aor battery502B being decoupled from first communication port102or fully discharging in the embodiments represented byFIG. 9B, power coupling network106may be controlled to disable the active charge through (or active-charge-through) of peripheral device assembly100.

FIG. 9Cillustrates a block diagram of an example peripheral device101in which only a host512powered by a battery510is coupled to second communication port104and nothing is coupled to first communication port102, in accordance with embodiments of the present disclosure. Thus,FIG. 9Cmay be similar in all material respects toFIG. 9AorFIG. 9Bexcept that a device(s) at the first communication port102is not coupled or decoupled from that port.

In the embodiments represented byFIG. 9C, a detection may be performed to determine whether a valid power connection exists at second communication port104. In response to the valid power connection being detected at second communication port104, the port policy management may swap the power role from first communication port102to second communication port104and may also switch the power contract to allow the power to be provided to peripheral device101from second communication port104. In a USB-C implementation of peripheral device101and host512inFIG. 9C, the power role swap may be accomplished by the port policy management signaling a fast role swap from first communication port102(e.g., first USB-C port) to second communication port104(e.g., second USB-C port).

InFIG. 9C, if the valid power connection is no longer detected at second communication port104, a determination may be made whether a physical connection exists at first communication port102. In response to the physical connection being detected at first communication port102, a lower current power contract may be selectively negotiated with second communication port104or the current draw of peripheral device101may be reduced.

As discussed with method214for adjusting a threshold voltage as described above with reference toFIG. 8, the valid power connection may be detected at first communication port102(e.g., first USB-C port) by comparing the bus voltage to a first threshold voltage VTH1, and the valid power connection may be detected at second communication port104(e.g., second USB-C port) by comparing the bus voltage to a second threshold voltage VTH2. First threshold voltage VTH1may be higher than second threshold voltage VTH2, and second threshold voltage VTH2may be equal to the minimum valid voltage for the power contract. A difference between first threshold voltage VTH1and second threshold voltage VTH2may be greater than or equal to a voltage drop between first communication port102(e.g., first USB-C port) and second communication port104(e.g., second USB-C port) during active charge through (or active-charge-through) operation of peripheral device101(e.g., USB-C device) from first communication port102and second communication port104. The voltage drop may be a value stored within a non-volatile memory within the peripheral device101(e.g., USB-C device). When the physical connection is detected at first communication port102, first threshold voltage VTH1may be increased.

The voltage drop may be determined by peripheral device101(e.g., USB-C device) by: 1) measuring the voltage at first communication port102(e.g., first USB-C port); 2) measuring the voltage at second communication port104(e.g., second USB-C port); 3) measuring a current through power coupling network106, that is, the active charging network; and 4) calculating a resistance between first communication port102and second communication port104(e.g., first USB-C port and second USB-C port).

As indicated before, example power sources may be provided through a power charger coupled to a power source or a battery that provides a power source. The battery may be the battery of a host, such as host512ofFIGS. 9A, 9B, and 9C. An example of how the valid power connection may no longer be detected at one of first communication port102and second communication port104may be when the power charger is decoupled from the power source or the battery is decoupled from the host or the battery is fully discharged or no longer has a sufficient amount of power for operating or powering devices. When the valid power connection is no longer detected by the peripheral device101, the active charge through (or active-charging-through) operation of the peripheral device101may be disabled.

The valid power connection may also exist at both first communication port102and second communication port104. When the valid power connection exists at both first communication port102and second communication port104, the port policy management may need to determine which of the two communication ports is to have the power role and to also provide the power contract that determines the direction of the active charge through (or active-charge-through) operation within the peripheral device101, that is, whether the active charge through (or active-charge-through) operation is from first communication port102to second communication port104or alternately from second communication port104to first communication port102.