Patent Grant
11495984
Universal Serial Bus (USB) communications occur between a Host having a downstream facing port (DFP) and a Device having an upstream facing port (UFP). The DFP and the UFP are sometimes implemented by a single port referred to as a dual role port (DRP) that is controllable to operate as either a DFP or a UFP. In some USB technologies, such as USB Type-C (USB-C), the single DRP port can both source and sink power. The DRP port can also dynamically or automatically change rolls between DFP or UFP and/or between sourcing power or sinking power automatically based on one or more monitored conditions. This dynamic or automatic changing can sometimes be disadvantageous.
Aspects of the present disclosure provide for a circuit. In at least some examples, the circuit includes a dual-role port for transferring power to the circuit and from the circuit. The circuit also includes a micro-processing unit. The micro-processing unit is configured to control the circuit to operate as a sink device to receive power from a source device via the dual-role port when the power supply includes a first amount of stored energy, detect, at the dual-role port, a change in a termination resistance of the source device, and control the circuit to limit power transfer from the circuit to the power supply via the dual-role port when the power supply changes in status from a sourcing state to a sinking state.
Other aspects of the disclosure provide for a system. In at least one example, the system includes a power bank configured to act as a source device. The power bank comprises a battery, a dual-role bus voltage terminal for transferring power to the battery and from the battery, and a micro-processing unit. The micro-processing unit is configured to control the battery to source power to a sink device via the dual-role bus voltage terminal when the battery includes a first amount of stored energy and inhibit power transfer from the sink device to the battery via the dual-role port when the battery includes less energy than the first amount of stored energy.
Other aspects of the present disclosure provide for a computer program product comprising a computer readable storage medium that comprises program instructions. In at least one example, the program instructions are executable by a micro-processing unit to cause the micro-processing unit to cause a device communicatively coupled to the micro-processing unit to receive power from a source device via a dual-role port capable of non-concurrent operation as both an input terminal and an output terminal, the source device having terminated a communication channel coupling the source device and the dual-role port with a pull-up signal at a source side of the communication channel while the source device is outputting power. Executing the program instructions further causes the micro-processing unit to detect removal of the pull-up signal at the source side of the communication channel and begin a timer when the removal of the pull-up signal is detected. Executing the program instructions further causes the micro-processing unit to detect a pull-down signal terminating the communication at the source side of the communication channel and inhibit a transfer of power to the source device via the dual-role port when the pull-down signal terminating the communication at the source side of the communication channel is detected prior to expiration of the timer.
For a detailed description of various examples, reference will now be made to the accompanying drawings in which:
For the purposes of this disclosure, a source device refers to a device having a finite power supply (e.g., a power bank including a rechargeable battery, a portable computing device having a rechargeable battery, etc.) that discharges to charge another device. Further for the purposes of this disclosure, a sink device refers to a device that couples to a source device to receive power from the source device, for operation and/or charging of the sink device. The source device and the sink device each have a capability to reverse roles (e.g., the source acting as a sink and vice versa). When a source device, such as a rechargeable battery pack (e.g., a power bank), is electrically coupled to a sink device, such as a mobile phone, tablet device, wearable device, portable computer, etc., often an intention is to charge the sink device using power stored in the source device. Wasted energy, such as in the form of transfer losses, can occur and be counterproductive to a desired result of charging if the source and sink device reverse roles during charging.
When the source device and the sink device are each Universal Serial Bus (USB) type-C (USB-C) devices utilizing dual role ports (DRPs), the ports can dynamically reverse roles based on charge states of the source device and the sink device. For example, when the source device is coupled to the sink device and has stored more charge than the sink device, power passes from the source device to the sink device. During this time, the source device is in a sourcing state or mode of operation. When power stored by the source device is expended, in at least some examples the source device presents (e.g., such as to the initial sink device) as itself being a sink device. During this time, the source device is now in a sinking state or mode of operation. Because of the dynamic role reversal capability of the DRPs, the sink device can then begin recharging the battery of the source device if the sink device enters a sourcing state or mode of operation. In at least some circumstances, this role reversal is undesirable because energy may be lost due to heat and other transfer related losses, reducing an amount of power available for further charging. In certain circumstances this role reversal is further undesirable because the sink device that a user intended to charge by coupling the source device to the sink device may charge and then discharge again, leaving the user with little to no additional time of use of the sink device. For example, if a user couples an external rechargeable battery to a laptop computer via DRPs, an internal rechargeable battery of the laptop computer may charge based on energy received from the external rechargeable battery. When little to no energy remains in the external rechargeable battery, charging ceases. However, the laptop computer now sees the discharged external rechargeable battery as a device for charging, similar to if a discharged mobile phone were coupled to the laptop computer. Accordingly, the laptop computer may begin transferring energy from the internal rechargeable battery to the external rechargeable battery automatically. If a user is not present to observe this automatic change in roles, such as if the charging is being performed unattended, the internal rechargeable battery and the external rechargeable battery may continue transferring energy back and forth. In at least some examples, this role reversal can continue, repeating until all available energy has been expended due to losses and no energy remains for charging, or operation, of the laptop computer. Accordingly, in at least some circumstances it is desirable to prevent the automatic reversal of roles of a DRP in a source and/or sink device.
At least some aspects of the present disclosure provide for a mechanism for preventing automatic reversal of roles of a DRP. Further, at least some aspects of the present disclosure otherwise inhibit power transfer from a sink device to a source device from which the sink device was receiving power. Some implementations are performed at least partially mechanically, such as through a switch, button, or the plugging and re-plugging of a coupling. For example, when the switch is in a first position, the DRP is controlled to source power but not sink power. When the switch is in a second position, the DRP is controlled to sink power but not source power. The switch is actuated by a user based on a user's desired operation of the DRP at a given time. Accordingly, the mechanical implementation of the present disclosure requires user input in some form. Alternatively, the role reversal is prevented until a coupling between two devices is de-coupled and then re-coupled. Other implementations can be performed at least partially through software. For example, the software implementation is timer-based. In other examples, the software implementation is based on one or more alerts or messages warning of an impending role reversal of the DRPs and allowing a user to provide input to permit or deny the role reversal of the DRPs. In at least some examples, the software implementation further utilizes user input, such as preventing the role reversal until a user provides user input instructing operation in a sourcing mode.
Turning now to
The power supply 108 receives the control signal from the voltage control circuit 112. In some examples, the power supply 108 receives the control signal from the voltage control circuit 112 via optical communication (e.g., an optocoupler). In other examples, the power supply 108 receives the control signal from the voltage control circuit 112 via a physical coupling between the power supply 108 and the voltage control circuit 112. In yet other examples, the power supply 108 itself is not adjustable but an external component coupled, or configured to couple, to an output of the power supply 108 adjusts a value of a signal output by the power supply 108. For example, the output of the power supply 108 may be a signal having a substantially constant voltage value that is manipulated to output one or more other signals having different voltage values than the output of the power supply 108. For example, the output of the power supply 108 may be manipulated by a power converter (not shown), such as a buck converter, a boost converter, or a buck-boost converter, and an output of the power converter may be provided to the node 118. In at least some examples, the power converter is controlled by the voltage control circuit 112 to manipulate the output of the power supply 108 to form the one or more other signals. The USB PD controller 110, in at least one example, is a microcontroller having processing capabilities. In other examples, the USB PD controller 110 is any processing element capable of receiving one or more inputs and generating one or more outputs based on rules, analysis, or other processing applied to at least some of the inputs.
The voltage control circuit 112 is any circuit capable of regulating and/or controlling a value of the signal that is present at node 118. For example, the voltage control circuit 112 is any circuit capable of receiving a reference voltage (VREF) from the USB PD controller 110 and controlling the power supply 108 according to VREF to control the value of the a bus voltage (VBUS) signal present at node 118. For example, the voltage control circuit 112 controls the power supply 108 according to VREF to cause the signal present at node 118 to have a value approximately equal, proportional, or otherwise having a relationship to a value of VREF, a scope of which is not limited herein.
The USB PD controller 110, in at least some examples, includes and/or implements at least a portion of a micro-processing unit 114. In various examples, the micro-processing unit 114 is a processor, a micro-processor, a field-programmable gate array (FPGA), a component suitable for, or capable of, implementing a state machine, or any other suitable component or device having processing capabilities. For example, when the USB PD controller 110 is a microcontroller, at least a portion of the micro-processing unit 114 is implemented as particular programming within the USB PD controller 110 to perform at least some of the operations disclosed herein. For example, the micro-processing unit 114 executes or implements software or other code for preventing automatic role reversal of a DRP port of the source device 102. The DRP port is, in at least one example, a VBUS terminal 122. For example, the VBUS terminal 122 may be a DRP port capable of providing power to the sink device 106 via the USB cable 104 or receiving power from the sink device 106 via the USB cable 104. In some examples, the source device 102 further includes a transistor 116 operable as a switch to control output of the VBUS signal via the VBUS terminal 122 and a receptacle 124 configured to receive a plug to provide a communicative coupling with the source device 102. The transistor 116 may be of any suitable technology, including at least p-type field-effect transistor (FET) or n-type FET.
In at least one example architecture, an output of the power supply 108 is coupled to a node 118 and an input of the voltage control circuit 112 is coupled to the node 118. A first terminal of the micro-processing unit 114 (which is a power supply terminal of USB PD controller 110 as shown in
In at least one example, the USB cable 104 includes a plug 126 configured to interact with the receptacle 124 to communicatively couple the USB cable 104 to the source device 102. The plug 126 houses, includes, or otherwise interacts with a VBUS terminal 140, a CC terminal 136, and a VCONN terminal 138 each configured to communicatively couple the USB cable 104 to the source device 102.
The sink device 106 is any device suitable for coupling to the USB cable 104 to receive power from the source device 102 and/or communicate data with the source device 102 and the scope of the sink device 106, its hardware architecture, or its method of operation are not limited herein. In at least some examples, the sink device 106 also implements a USB controller substantially similar to the USB PD controller 110 and/or includes functionality substantially similar to the micro-processing unit 114.
In an example of operation of the system 100, after the source device 102 (e.g., the USB PD controller 110) determines that a sink device 106 has been connected to the source device 102 via the USB cable 104, the USB PD controller 110 controls the power supply 108 to output a signal having a voltage level specified by a control signal received by the power supply 108. The USB PD controller 110 controls the power supply 108 to output the signal, for example, by controlling the voltage control circuit 112.
In at least some examples, the USB PD controller 110 applies pull-up signals on both the CC1 terminal 132 and the CC2 terminal 134 and monitors the value of the signal present at each of the CC1 terminal 132 and the CC2 terminal 134. The pull-up signals are applied, in some examples, by coupling the CC1 terminal 132 and the CC2 terminal 134 to a voltage supply 150 through a pull-up termination resistor (Rp) 142. In at least some examples, the voltage supply 150 outputs a signal having a different voltage value than the power supply 108. For example, in at least some implementations the voltage supply 150 outputs a signal having a voltage of about 5V, about 3.3V, or another suitable voltage. The voltage of the signal output by the voltage supply 150, in some examples, is based on a signal output by the power supply 108 (e.g., such as an output of a regulator or converter that accepts an output of the power supply 108 as an input for generating the voltage provided by the voltage supply 150). In some examples, each of the pull-up signals has a substantially same voltage level. In other examples, each of the pull-up signals has a different voltage level. For example, the USB PD controller 110 compares the value of the signal present at each of the CC1 terminal 132 and the CC2 terminal 134 to a threshold value to determine whether it is less than a value of the pull-up signal (or some proportionate amount of the value of the pull-up signal). In various implementations, the source device 102 monitors the CC1 terminal 132 and/or the CC2 terminal 134 for the presence of an Open state, a Rd-attached state, or a Ra-attached state. The Open state exists for a CCx terminal (e.g., either of the CC1 terminal 132 or the CC2 terminal 134) when the value of the signal present at that CCx terminal is above a first threshold (in one example, 1.6V). The Rd-attached state exists for a CCx terminal when the signal present at that CCx terminal is below the first threshold and above a second threshold (in one example, 0.25V). The Ra-attached state exists for a CCx terminal when the signal present at that CCx terminal is below the second threshold. The CCx or CCy terminal (e.g., either of the CC1 terminal 132 or the CC2 terminal 134 that is not the CCx terminal) determined to be in the Rd-attached state, in at least some examples, is terminated by the sink device 106 with a pull-down termination resistor (Rd) coupled to a ground node 152.
In some examples, the USB PD controller 110 ignores the presence of the USB cable 104 when the sink device 106 is not coupled to the USB cable 104 (and thereby, the source device 102). For example, when the CCx terminal is in the Ra-attached state and the CCy terminal is in the Open state, the USB PD controller 110 ignores the presence of the USB cable 104 and does not communicate with the USB cable 104. In other examples, the USB PD controller 110 communicates with the USB cable 104 (such as when the USB cable 104 includes an electronic marker) when the CCx terminal is in the Ra-attached state and the CCy terminal is in the Open state.
In at least some examples, when the USB PD controller 110 detects the presence of the sink device 106, the USB PD controller 110 applies a signal to the VBUS terminal 122, for example, by controlling the power supply 108 to output VBUS. In some examples, the USB PD controller 110 detects the presence of the sink device 106 in one of two ways. First, when the CCx terminal is in the Rd-attached state and the CCy terminal is in the Open state or the Ra-attached state, the USB PD controller 110 determines the sink device 106 to be coupled to the source device 102. Second, when the CCx terminal is in the Open state or Ra-attached state and the CCy terminal is in the Rd-attached state, the USB PD controller 110 also determines the sink device 106 to be coupled to the source device 102. The USB PD controller 110 determines the CCx terminal or the CCy terminal to be in the Rd-attached state, in at least some examples, based on the USB PD controller 110 terminating the CCx or CCy terminal with Rp 142. The USB PD controller 110 terminates the CCx or CCy terminal with Rp 142 by controlling a switch 144 and a switch 146 to couple the CCx and the CCy terminal to Rp 142. In at least some examples, the switch 144 and the switch 146 are each controlled by the micro-processing unit 114.
Similarly, when the source device 102 is coupled to the sink device 106 (e.g., via the USB cable 104 utilizing plug 126 and receptacle 124), the sink device 106 loads or pulls down (e.g., such as via an approximately 5.1 kilo-Ohm resistance) whichever of the CC1 terminal 132 or the CC2 terminal 134 that is coupled to the CC terminal 136. Pulling down the one of the CC1 terminal 132 or the CC2 terminal 134 reduces the value of the signal present at the one of the CC1 terminal 132 or the CC2 terminal 134 that is coupled to the CC terminal 136 and places that one of the CC1 terminal 132 or the CC2 terminal 134 in the Rd-attached state.
The micro-processing unit 114, in at least some examples, controls the providing of VBUS to the VBUS terminal 122. For example, the micro-processing unit 114 controls the transistor 116 to couple the node 118 to the VBUS terminal 122. When the power supply 108 becomes discharged, the micro-processing unit 114 toggles the switch 144 and the switch 146 to couple the CCx or CCy terminal to a pull-down termination resistor (Rd) 148. When the sink device 106 performs a Rd to Rp toggle and sees the CCx or CCy terminal of the source device 102 terminated with Rd 148, the sink device 106 transitions to become a new source device and the source device 102 becomes a new sink device. However, in at least some examples the micro-processing unit 114 provides a signal to the sink device 106 (e.g., as a bit or component of a PD message or an alert message) indicating that the source device 102 and the sink device 106 should not reverse roles. When the sink device 106 has received a signal indicating that it should not reverse roles with the source device 102, in at least some examples, the sink device 106 implements a timer when the sink device 106 detects a disconnection of Rp at the source device 102. If the sink device 106 then detects Rd at the source device 102 prior to expiration of the timer, the sink device 106 does not reverse roles and become a new source device. However, if the sink device 106 detects Rd at the source device 102 after expiration of the timer, the sink device 106 reverses roles and becomes a new source device, providing power to the source device 102 which acts as the new sink device.
In other examples, when the micro-processing unit 114 determines a power level of the power supply 108 to be at or below a predefined threshold, the micro-processing unit 114 communicates an alert or other message to the sink device 106. The predefined threshold may be a percentage of a maximum charge of the power supply 108, such as about 10% maximum charge remaining, 5% maximum charge remaining, or any other predefined threshold. The alert is, for example, a notification of the declining charge of the power supply 108. In at least some examples, the alert further includes one or more interactive elements enabling a user to provide feedback. For example, the interactive elements includes an option for permitting role reversal of the source device 102 and the sink device 106 or an option for preventing role reversal of the source device 102 and the sink device 106. In at least some examples, if a user does not respond to the alert within a predefined period of time, the user's inaction is assumed to be a negative response such that role reversal of the source device 102 and the sink device 106 is prevented.
In yet other examples, the source device 102 includes a hardware switch 154, which is coupled to an input of USB PD controller 110 (and of micro-processing unit 114) as shown in
In yet other examples, when the sink device 106 detects removal of the Rp 142 termination by the source device 102, the sink device 106 initiates a timer. In some examples, the timer begins at a non-zero value and counts down to zero, expiring when the count reaches zero. In other examples, the timer begins at zero and counts up, expiring when the count reaches a predefined non-zero value. When the sink device 106 initiates the timer, the sink device disables dual-role functionality of the sink device 106. If the sink device 106 detects the Rd 148 termination by the source device 102 prior to expiration of timer, the sink device 106 maintains the disabled state of the dual-role functionality. For example, the dual-role functionality is maintained in the disabled state until user input is received instructing the source device 106 to operate as a source device, or until the Rd 148 termination by the source device 102 is no longer present. If the sink device 106 detects the Rd 148 termination by the source device 102 after expiration of timer, the sink device 106 re-enables the dual-role functionality and begins to operate in a sourcing mode to source power to the source device 102 that is now operating in a sinking mode.
While discussed above as preventing power transfer between the sink device 106 and the source device 102, in at least some other examples the power transfer is inhibited. In some examples, when power transfer is inhibited, power transfer is entirely prevented. In other examples, when power transfer is inhibited, power transfer is permitted but at a reduced rate. For example, when power transfer is inhibited, a rate of that power transfer is less than when power transfer is not inhibited.
While discussed herein and illustrated in
Turning now to
At operation 202, the second device determines that Rp is no longer detected. For example, the second device determines that Rp is no longer detected when the first device ceases presenting Rp on a CC line coupling the first and second devices. The determination that Rp is no longer present is made, in some examples, by comparing a value of a voltage present on the CC line to a threshold value. For example, when Rp is present, the voltage present on the CC line exceeds the threshold value. When Rp is not present, the voltage present on the CC line is less than the threshold value. In at least some examples, Rp no longer being detected indicates that power is no longer being delivered to the second device by the first device.
At operation 204, the second device detects the presence of Rd on a CC line coupling the first and second devices. The determination that Rd is present is made, in some examples, by comparing a value of a voltage present on the CC line to a threshold value. For example, when Rd is present, the voltage present on the CC line may be between a pair of threshold values. When Rd is not present, the voltage present on the CC line may be outside the pair of threshold values. When Rd is not detected, the method remains at operation 206. In at least some implementations, the presence of Rd on the CC line indicates that the first device is now operating as a sink device. When the second device detects Rd on the CC line, in at least some examples, the second device begins sourcing power back to the first device. However, as previously discussed herein, such an action can result in undesirable operation of the first and second devices. Accordingly, prior to the second device sourcing power to the first device, the second device proceeds to operation 206.
At operation 206, the second device determines whether Rd has been detected within a predetermined period of time of Rp no longer being detected. For example, when Rd is detected within the predetermined period of time of Rp no longer being detected, it may be an indicator that the first device has become discharged but remains coupled to the second device. In such examples, an undesirable transfer of charge back from the second device to the first device may occur when the first and second devices are coupled via a DRP. For example, when a power supply of the first device discharges, in some examples a terminal of the first device becomes terminated by Rd. This termination occurs, in at least some examples, in about 10 milliseconds (ms). In other examples, the termination occurs within about 10 ms to about 100 ms. When the first device is uncoupled from the second device and then recoupled to the second device, the terminal of the first device is still terminated by Rd. However, the physical action of decoupling and recoupling the first device and the second device may exceed the amount of time consumed in terminating the terminal of the first device when the power supply of the first device discharges. For example, the physical action of decoupling and recoupling the first device and the second device may consume about 100 ms or more. In this way, the second device is able to differentiate between a first device in which a power supply has discharged but the first device has not been de-coupled from the second device and a device that is coupled to the second device with intent for the second device to source power to the newly coupled device.
When Rd is detected within the predetermined period of time, the method 200 proceeds to operation 208. In at least some examples, the determination of whether Rd is detected within the predetermined period of time includes initiating or otherwise beginning a counter or timer when Rp is no longer detected at operation 202. When Rd is detected at operation 204, a value of the counter or timer is compared to a timer threshold value to determine whether the timer value has exceeded the timer threshold value. In at least some examples, the timer threshold value is configurable. For example, the timer threshold value is configured to expire after about 10 ms, about 50 ms, about 100 ms, about 200 ms, or any other suitable amount of time.
At operation 208, the second device disables a DRP functionality of the second device. In at least some examples, disabling the DRP functionality prevents the second device from presenting Rp on the CC line and beginning to operate as a source device to recharge the first device when the first device is presenting Rd on the CC line. Alternatively, in at least some examples instead of disabling the DRP functionality at operation 208, the second device limits a permitted rate of power transfer such that power transfer is inhibited but not entirely prevented.
At operation 210, the second device determines whether a user wishes for the second device to operate as a source device. The second device makes the determination, in at least some examples, based on input received from the user. The input is received, in some examples, via a physical, articulable input source such as a switch, toggle, button, etc. In other examples, the input is received via a soft input source such as a software button, graphical user interface button, software settings toggle, etc. In yet other examples, the input is received by way of the user unplugging and plugging back in a coupling between the first device and the second device. When the user does not wish for the second device to operate as a source device, the method 200 remains at the operation 210. When the user wishes for the second device to operation as a source device, the method 200 proceeds to operation 212.
At operation 212, the second device enables the DRP functionality of the second device. In at least some examples, enabling the DRP functionality permits the second device to present Rp on the CC line and begin to operate as a source device to recharge the first device when the first device (or another device coupled to the second device) is presenting Rd on the CC line. After enabling the DRP functionality, the method 200 proceeds to operation 214. Alternatively, when the second device did not disable the DRP functionality at operation 208 and instead inhibited the power transfer, at operation 212 the second device removes the limit to the permitted rate of power transfer that was imposed at operation 208.
Returning now to operation 206, when Rd is not detected within the predetermined period of time, it may be an indicator that the first device has become discharged and was uncoupled from the second device, but the first device, or another device operating as a sink device, has been coupled to the second device. In such examples, the method 200 proceeds to operation 214.
At operation 214, the second device begins sourcing power to a device (which may be the first device) that is coupled to the second device and is presenting Rd. The second device sources the power, in at least some examples, via a DRP that previously received power from the first device prior to Rp no longer being detected at operation 202.
Turning now to
The table 300 illustrates RpConnectionDetected, RpDisconnectDetected, and DiconnectHandler operational routines. In at least some examples, the routines illustrated in the table 300 are part of another software program or process such that the routines of the table 300 are sub-routines of the software program or process that are called by the software program or process. For example, when the software program or process receives an input signal that indicates that Rp is detected, the software program or process calls the RpConnectionDetected routine to set a variable RpLossSignal to false. Similarly, when the software program or process receives an input signal that indicates that Rp is no longer detected, the software program or process calls the RpDisconnectDetected routine to set a variable RpLossSignal to true. Additionally, as illustrated in the table 300 the RpDisconnectDetected routine calls the DisconnectHandler routine as a result of the failure to detect Rp. In other examples, after setting RpLossSignal to true, the RpDisconnectDetected routine returns to a software program or process that called the RpDisconnectDetected routine and that software program or process then calls the DisconnectHandler routine.
As illustrated in the DisconnectHandler routine, after a disconnection of Rp is detected, DRP functionality is disabled by calling a routine DisableDRPConfiguration. After disabling the DRP functionality a variable DisconnectTimeOut is initialized to zero and incremented as a timer delay, as long as RpLossSignal remains true, one unit per ms until 200 ms have elapsed or a user provides input overriding the timer delay. For example, when a user indicates that a device implementing the pseudocode of the table 300 should operate as a source device (causing the variable OperateAsSourceDevice to have a value of true, such as set by another routine or sub-routine), DisconnectHandler ceases incrementing the counter and enables the DRP functionality. Additionally, in some examples when 200 ms have elapsed since initialization of DisconnectTimeOut, DisconnectHandler ceases incrementing the counter and enables the DRP functionality. In at least some examples, the DRP functionality is enabled by calling a routine EnableDRPConfiguration.
While the table 300 illustrates pseudocode that includes certain variables, operations, functions, and a process flow, various other programming implementations of the method 200 exist. The pseudocode of table 300 is not meant to exclude these other programming implementations from the scope of the present disclosure. Instead, the pseudocode of table 300 merely illustrates one exemplary implementation while retaining other programming implementations of the method 200 within the scope of the present disclosure.
Turning now to
For example, the method includes a first portion 405 and a second portion 410. The first portion 405 is implemented, in at least some examples, in the first device that initially operates as a source device. The second portion 410 is implemented, in at least some examples, in the second device that initially operates as a sink device. At operation 415, the first device determines whether a remaining charge of a power supply of the first device is less than about 5% of a maximum capacity. When the remaining charge is not less than 5% of the maximum capacity, the first portion 405 remains at the operation 415. When the remaining charge is less than 5% of the maximum capacity, the first portion proceeds to operation 420. In other examples, the alert message is sent based on another threshold of remaining charge such as about 10%, about 20%, about 2%, or any other suitable amount of charge remaining. In at least some examples, the alert message is sent based on a rate of discharge of the power supply of the first device, such that at a particular current draw, the alter message is sent with a particular amount of time of charging remaining (e.g., the alert message is sent about 5 minutes before charging terminates, etc.). In at least some examples, the alert message is, or is sent as a component of, a PD message.
At operation 420, the first device transmits an alert message. In at least some examples, the alert message includes a status of the first device and indicates the remaining charge of the power supply of the first device. For example, in some implementations the power supply of the first device is a battery and the status of the first device indicates a charge remaining in the battery. The alert message is transmitted, in at least some examples, to the second device when the second device is coupled to the first device and receiving power from the first device.
At operation 425, the second device receives an alert message. In at least some examples, the alert message is received from the first device. For example, in at least some implementations the alert message received at operation 425 is the alter message transmitted by the first device at operation 420. In other examples, the alert message received by the second device at the operation 425 is received from any suitable source, the scope of which is not limited herein, such that the second portion 410 of the method is separable and can stand alone from the first portion 405 of the method. The alert message, in at least some examples, indicates a status of a device operating as a source device to provide power to the second device. For example, the status includes a remaining charge of a power supply, such as a battery, of the source device.
At operation 430, the second device disables a DRP functionality of the second device. In at least some examples, disabling the DRP functionality prevents the second device from presenting Rp on a CC line coupling the second device to the first device and beginning to operate as a source device to recharge the first device when the first device is presenting Rd on the CC line. Alternatively, in at least some examples instead of disabling the DRP functionality at operation 430, the second device limits a permitted rate of power transfer such that power transfer is inhibited but not entirely prevented.
At operation 435, the second device determines whether a user wishes for the second device to operate as a source device. The second device makes the determination, in at least some examples, based on input received from the user. The input is received, in some examples, via a physical, articulable input source such as a switch, toggle, button, etc. In other examples, the input is received via a soft input source such as a software button, graphical user interface button, software settings toggle, etc. When the user does not wish for the second device to operate as a source device, the second portion 410 of the method remains at the operation 435. When the user wishes for the second device to operation as a source device, the second portion 410 of the method proceeds to operation 440.
At operation 440, the second device enables the DRP functionality of the second device. In at least some examples, enabling the DRP functionality permits the second device to present Rp on the CC line and begin to operate as a source device to recharge the first device when the first device (or another device coupled to the second device) is presenting Rd on the CC line. Alternatively, when the second device did not disable the DRP functionality at operation 430 and instead inhibited the power transfer, at operation 440 the second device removes the limit to the permitted rate of power transfer that was imposed at operation 430.
Turning now to
As illustrated by the pseudocode of the table 505, the first device continuously monitors a charge to determine whether the charge level is less than an alter threshold. In at least some examples, the charge level is of a power supply, such as a battery, of the first device and the alert threshold is a percentage of maximum charge remaining, an amount of time remaining until charge termination, or any other suitable threshold. When the charge level is less than the alert threshold, an alert message is sent.
As illustrated by the pseudocode of the table 510, when the second device has not received an alert message, the second device calls a Delay sub-routine that implements a delay for a predetermined period of time before returning to again determine whether an alert message has been received. When the second device receives an alert message, the second device disables DRP functionality by calling a routine DisableDRPConfiguration. After disabling the DRP functionality the second device monitors for user input, delaying until input is received. In some examples, the user input takes the form of a user unplugging and re-plugging a coupling between the first device and the second device. For example, when a user indicates that the second device should operate as a source device (causing the variable OperateAsSourceDevice to have a value of true, such as set by another routine or sub-routine), the second device enables the DRP functionality. In at least some examples, the DRP functionality is enabled by calling a routine EnableDRPConfiguration.
While the table 505 and the table 510 illustrate pseudocode that includes certain variables, operations, functions, and a process flow, various other programming implementations of the method of
Turning now to
At operation 602, power is transferred from a source device and a sink device. The power is transferred, for example, from the source device to the sink device. While the power is transferred from the source device to the sink device the source device is in a sourcing state or mode of operation and terminates a coupling between the source device and the sink device with a pull-up termination. Similarly, while the power is transferred from the source device to the sink device the sink device is in a sinking state or mode of operation and terminates the coupling between the source device and the sink device with a pull-down termination.
At operation 604, power transfer from the sink device to the source device is inhibited. Inhibiting the power transfer, in some examples, prevents the power transfer such as until user input is received directing the power transfer to occur. In other examples, inhibiting the power transfer permits the power transfer to occur but at a reduced rate of transfer (e.g., when compared to a rate of transfer when uninhibited).
Multiple suitable processes exist for inhibiting the power transfer. In at least one example, in one implementation the source device sends the sink device an alert message that indicates a charge remaining in a power supply of the source device. Based at least partially on this alert message, the sink device inhibits transfer of power back to the source device from the sink device. The power transfer is inhibited, in at least some examples, until a timer expires and/or until user input is received. The user input can include a user unplugging and re-plugging the coupling between the source device and the sink device, the user pushing a hardware or software button, the user toggling a switch, etc.
In another example, when the power supply of the source device depletes, the source device changes charging states or modes from sourcing to sinking. The change is accomplished by the source device removing a pull-up termination of the coupling between the source device and the sink device and providing a pull-down termination to the coupling between the source device and the sink device. The sink device detects the removal of the pull-up termination and begins a timer. If the sink device detects the pull-down termination of the coupling between the source device and the sink device, the sink device inhibits power transfer back to the source device. For example, the sink device permits the power transfer at a reduced rate or the sink device prevents the power transfer. The inhibiting of the power transfer continues, in at least some examples, until user input is received instructing the sink device to transfer power to the source device.
In the foregoing discussion, the terms “including” and “comprising” are used in an open-ended fashion, and thus should be interpreted to mean “including, but not limited to . . . .” The term “couple” is used throughout the specification. The term may cover connections, communications, or signal paths that enable a functional relationship consistent with the description of the present disclosure. For example, if device A generates a signal to control device B to perform an action, in a first example device A is coupled to device B, or in a second example device A is coupled to device B through intervening component C if intervening component C does not substantially alter the functional relationship between device A and device B such that device B is controlled by device A via the control signal generated by device A. A device that is “configured to” perform a task or function may be configured (e.g., programmed and/or hardwired) at a time of manufacturing by a manufacturer to perform the function and/or may be configurable (or re-configurable) by a user after manufacturing to perform the function and/or other additional or alternative functions. The configuring may be through firmware and/or software programming of the device, through a construction and/or layout of hardware components and interconnections of the device, or a combination thereof. Furthermore, a circuit or device that is said to include certain components may instead be configured to couple to those components to form the described circuitry or device. For example, a structure described as including one or more semiconductor elements (such as transistors), one or more passive elements (such as resistors, capacitors, and/or inductors), and/or one or more sources (such as voltage and/or current sources) may instead include only the semiconductor elements within a single physical device (e.g., a semiconductor die and/or integrated circuit (IC) package) and may be configured to couple to at least some of the passive elements and/or the sources to form the described structure either at a time of manufacture or after a time of manufacture, for example, by an end-user and/or a third-party.
While certain components are described herein as being of a particular process technology (e.g., FET, metal oxide semiconductor FET (MOSFET), n-type, p-type, etc.), these components may be exchanged for components of other process technologies (e.g., replace FET and/or MOSFET with bi-polar junction transistor (BJT), replace n-type with p-type or vice versa, etc.) and reconfiguring circuits including the replaced components to provide desired functionality at least partially similar to functionality available prior to the component replacement. Components illustrated as resistors, unless otherwise stated, are generally representative of any one or more elements coupled in series and/or parallel to provide an amount of impedance represented by the illustrated resistor. Additionally, uses of the phrase “ground voltage potential” in the foregoing discussion are intended to include a chassis ground, an Earth ground, a floating ground, a virtual ground, a digital ground, a common ground, and/or any other form of ground connection applicable to, or suitable for, the teachings of the present disclosure. Unless otherwise stated, “about”, “approximately”, or “substantially” preceding a value means +/−10 percent of the stated value.
The above discussion is meant to be illustrative of the principles and various examples of the present disclosure. 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 present disclosure be interpreted to embrace all such variations and modifications.
| Number | Name | Date | Kind |
|---|---|---|---|
| 9310868 | Waters et al. | Apr 2016 | B2 |
| 10079499 | Sporck et al. | Sep 2018 | B2 |
| 10860517 | Wang | Dec 2020 | B1 |
| 10868521 | Choi | Dec 2020 | B2 |
| 20160191313 | Chen et al. | Jun 2016 | A1 |
| 20180292880 | Nakadokoro | Oct 2018 | A1 |
| Number | Date | Country |
|---|---|---|
| 2018052553 | Mar 2018 | WO |
| Entry |
|---|
| Search Report for PCT Patent Application No. PCT/US2020/067117, date of mailing of the international search report dated Apr. 8, 1 page. |
| Number | Date | Country | |
|---|---|---|---|
| 20210203168 A1 | Jul 2021 | US |
