Source: https://patents.google.com/patent/US20170293335A1/en
Timestamp: 2019-12-14 10:06:16
Document Index: 597253461

Matched Legal Cases: ['art 600', 'art 600', 'art 600', 'art 600', 'art 600', 'art 600', 'art 500', 'art 500', 'art 500', 'art 500', 'art 500']

US20170293335A1 - Adjustable power delivery apparatus for universal serial bus (usb) type-c - Google Patents
Adjustable power delivery apparatus for universal serial bus (usb) type-c Download PDF
US20170293335A1
US20170293335A1 US15/169,175 US201615169175A US2017293335A1 US 20170293335 A1 US20170293335 A1 US 20170293335A1 US 201615169175 A US201615169175 A US 201615169175A US 2017293335 A1 US2017293335 A1 US 2017293335A1
US15/169,175
2016-04-08 Priority to US201662320319P priority Critical
2016-05-31 Priority to US15/169,175 priority patent/US20170293335A1/en
2016-10-07 Assigned to INTEL CORPORATION reassignment INTEL CORPORATION ASSIGNMENT OF ASSIGNORS INTEREST (SEE DOCUMENT FOR DETAILS). Assignors: NGUYEN, DON J., NGE, Chee Lim, YODER, JAMES M., DUNSTAN, ROBERT A.
2017-10-12 Publication of US20170293335A1 publication Critical patent/US20170293335A1/en
TABLE 6-4 Power Data Object Bit(s) Description B31 . . . 30 Value Parameter 00b Fixed supply (Vmin = Vmax) 01b Battery 10b Variable Supply (non-battery) 11b Reserved
FIG. 1 illustrates a typical USB PD system 100 using a Variable power source. System 100 consists of an Alternating Current (AC) Main receptacle 101 (e.g., a typical wall socket to provide AC voltage and current), a USB Type-C AC/DC (where DC is Direct Current) Adaptor 102 (also referred to as the programmable power supplies) with Variable Output, and USB Type-C enabled computer system 103. System 103 is also referred to as the Power Consumer or Consumer while Adaptor 102 is also referred to as the Power Provider or Provider. Power Provider 102 is coupled to the AC Main 101 via an AC Power Cord. Power Provider 102 communicates with the Power Consumer 103 via VBUS and CC wire(s), which may be part of USB Type-C Cable bundle. A Type-C cable bundle may include VBUS and CC wires and other wires (“not shown”), such as USB2, USB3, SBU1/SBU2, GND, etc. The Power Provider 102 includes a Power Deliver (PD) Controller 102 a to control the output voltage on VBUS. PD Controller 103 a may be implemented in hardware or software (or a combination of both) and is responsible for communicating with Consumer 103.
Consumer 103 may be any consumer device (e.g., phone, laptop, printer, etc.) that uses the power supply provided by VBUS to operate. Consumer 103 may include a regulation module or logic 103 a such as a battery, charger, and/or voltage regulator (e.g., DC-DC switching regulator). Regulation module or logic 103 a is a hardware block that receives power supply from VBUS and uses that power supply to provide regulated power supply to other blocks in Consumer 103. Consumer 103 also includes PD Controller 103 b just as Provider 102 includes PD Controller 102 a. PD Controller 103 b may be implemented in hardware or software (or a combination of both) and is responsible for communicating with Provider 102. The rest of the system circuits (e.g., sensor, memory, phone hardware, etc.) of Consumer 103 are lumped here in module 103 c. A typical power delivery process performed by PD Controllers 103 b and 103 a of Consumer 103 and Provider 102, respectively, is illustrated with reference to FIG. 2.
TABLE 6-3 Data Message Types Valid Start of Bits 3 . . . 0 Type Sent by Description Packet 0000 Reserved All values not explicitly defined are Reserved and shall not be used 0001 Source_Capabilities Source or See Section 6.4.1.2 SOP only Dual-Role 0010 Request Sink only See Section 6.4.2 SOP only 0011 BIST Tester, Source See Section 6.4.3 SOP* or Sink 0100 Sink_Capabilities Sink or Dual- See Section 6.4.1.3 SOP only Role
In some embodiments, Provider 402 includes hardware 402 a to use SBU pins (1 and/or 2) to receive an indication that an adjusted power supply can be provided to Power Consumer 403. In some embodiments, Power Provider 402 (or power adapter) ties one of these pins to a voltage through an impedance and uses that pin to control its output voltage on VBUS. In some embodiments, Provider 402 includes PD Controller 402 b which is used to control various functions of Provider 402 including the voltage level of VBUS. In some embodiments, when the SBU pin(s) (1 and/or 2) is not asserted, for example, when connected to a legacy power Consumer 103, the power adapter 402 simply outputs the voltage negotiated by USB PD Controller 402 a/b. In some embodiments, when the SBU (1 and/or 2) pin is asserted, the power adapter's output voltage is reduced according to voltage/current modulation on the SBU pin.
In some embodiments, hardware 402 a includes a pull-up resistor Rup coupled to the SBU pins (1 and/or 2) and internal power supply Vdd. In some embodiments, when a Power Consumer detects that the SBU pin (1 and/or 2) is not an open (or high impedance) pin and instead is pulled-up to a supply level, then the Power Consumer knows that the VBUS is adjustable by using SBU (1 and/or 2). The VBUS value is negotiated using USB PD Controller 402 a/b, in accordance with some embodiments. The various embodiments allow USB Provider 402 to provide adjustable power supply on VBUS when desired by USB Consumer 403, while maintaining the capability to provide fixed power supply on VBUS when USB Provider 402 is connected to a legacy Consumer.
The pull-up resistor Rup serves two functions—first to signal presence of the ability of a power adaptor to provide adjustable supply and second to provide the place for the power consumer to control the output voltage. In some embodiments, hardware 402 a includes p-type transistor MP which represents the element that actually controls the power adapter's output voltage (e.g., instantaneous output voltage) on VBUS. In some embodiments, the function of p-type transistor MP is implemented in a voltage regulator (VR) control circuit of Power Adaptor 402. In some embodiments, Provider 402 includes part or all of blocks of FIG. 5 to execute the process of providing a new voltage and/or current.
In some embodiments, Consumer 403, like Consumer 103, may be any consumer device (e.g., phone, laptop, printer, etc.) that uses the power supply provided by VBUS to operate and uses the USB Type-C interface. In some embodiments, Consumer 403 may include a regulation module or logic 403 a such as a battery, charger, and/or voltage regulator (e.g., DC-DC switching regulator). Regulation module or logic 403 a is a hardware block that receives power supply from VBUS and uses that power supply to provide regulated power supply to other blocks in Consumer 403.
In some embodiments, Consumer 403 also includes PD Controller 403 b. In some embodiments, PD Controller 403 b may be implemented in hardware or software and is responsible for communicating with Provider 402. The rest of the system circuits of Consumer 403 are lumped here in module 403 c. In some embodiments, PD Controller 403 b includes part or all of blocks of FIG. 5 to execute the process of requesting and receiving a new power supply.
In some embodiments, Power Consumer 403 includes hardware 403 d which can pull-down the voltage on SBU (1 and/or 2) pins and/or adjust the voltage/current on the SBU (1 and/or 2) pins. In some embodiments, hardware 403 d comprises an n-type transistor MN with a drain terminal coupled to one of the SBU pins and a source terminal coupled to ground. In some embodiments, hardware 403 d represents the element that Power Consumer 403 uses to signal Power Provider 402 how much voltage to supply on VBUS. In some embodiments, block 403 a may have intimate knowledge of the power consumer's battery's charge level, the amount of power the system is consuming, etc. In some embodiments, Power Consumer 403 includes Controller 403 e to control hardware 403 b. In some embodiments, 403 a communicates with Controller 403 e to manage turn on/off of hardware 403 d (e.g., transistor MN). In some embodiments, hardware 403 d uses that information to compute what voltage it needs and drive the transistor MN to actually control Power Provider 402 to deliver it that voltage.
In some embodiments, Power Consumer 403 may assert the SBU pin to change the output voltage on VBUS from Power Adapter 402 in several ways. For example, Controller 403 e of Power Consumer 403 may provide a PWM (Pulse Width Modulated) signal to transistor MN which causes the SBU pin to be periodically pulled low for short intervals. In some embodiments, the duty cycle of the PWM signal can be used to instruct Power Provider 402 to adjust the voltage on VBUS. For example, when the larger amount of time the SBU pin is pulled low, the lower the output voltage on the VBUS is provided by Power Provider 402. In another example, Power Consumer 403 may reduce the voltage on the SBU pin that in turn lowers the output voltage on the VBUS of Power Provider 402. In another example, Power Consumer 403 may draw current from the SBU pin that in turn lowers the output voltage on the VBUS by Power Provider 402. In other embodiments, other mechanisms can be used to inform Power Provider 402 to adjust the output voltage on VBUS using SBU pin(s).
In some embodiments, USB powered device 700 (e.g., Consumer 403) comprises a low power Processor 701 (e.g., a Digital Signal Processor (DSP), an Application Specific Integrated Circuit (ASIC), a general purpose Central Processing Unit (CPU), or a low power logic implementing a simple finite state machine to perform the method of flowchart 600 associated with Consumer 403, etc.), Machine-Readable Storage Medium 702 (also referred to as tangible machine readable medium), Antenna 705, Network Bus 706, and USB PD Controller 707 (e.g., PD Controller 403 b).
In some embodiments, the various logic blocks of Consumer 403 are coupled together via Network Bus 706. Any suitable protocol may be used to implement Network Bus 706. In some embodiments, Machine-Readable Storage Medium 702 includes Instructions 702 a (also referred to as the program software code/instructions) for requesting and accepting a new power supply (e.g., new voltage and/or current) as described with reference to various embodiments and flowchart. Here, Instructions 702 a are the instructions performed by Consumer 403 in flowchart 600 as described with reference to FIG. 6.
Referring back to FIG. 7, program software code/instructions 702 a, associated with Consumer 403 part of flowchart 600, as described with reference to FIG. 6, and executed to implement embodiments of the disclosed subject matter may be implemented as part of an operating system or a specific application, component, program, object, module, routine, or other sequence of instructions or organization of sequences of instructions referred to as “program software code/instructions,” “operating system program software code/instructions,” “application program software code/instructions,” or simply “software” or firmware embedded in processor. In some embodiments, the program software code/instructions associated with Consumer 403 end of flowchart 600, as described with reference to FIG. 6, are executed by Consumer 403.
Referring back to FIG. 7, in some embodiments, the program software code/instructions 702 a associated with flowchart 600 are stored in a computer executable storage medium 702 and executed by Processor 701. Here, computer executable storage medium 702 is a tangible machine readable medium that can be used to store program software code/instructions and data that, when executed by a computing device, causes one or more processors (e.g., Processor 701) to perform a method(s) as may be recited in one or more accompanying claims directed to the disclosed subject matter.
The tangible machine readable medium 702 may include storage of the executable software program code/instructions 702 a and data in various tangible locations, including for example ROM, volatile RAM, non-volatile memory and/or cache and/or other tangible memory as referenced in the present application. Portions of this program software code/instructions 702 a and/or data may be stored in any one of these storage and memory devices. Further, the program software code/instructions can be obtained from other storage, including, e.g., through centralized servers or peer to peer networks and the like, including the Internet. Different portions of the software program code/instructions and data can be obtained at different times and in different communication sessions or in the same communication session.
The software program code/instructions 702 a (associated with Consumer 403 part of flowchart 600 as described with reference to FIG. 6 and other embodiments) and data can be obtained in their entirety prior to the execution of a respective software program or application by the computing device. Alternatively, portions of the software program code/instructions 702 a and data can be obtained dynamically, e.g., just in time, when needed for execution. Alternatively, some combination of these ways of obtaining the software program code/instructions 702 a and data may occur, e.g., for different applications, components, programs, objects, modules, routines or other sequences of instructions or organization of sequences of instructions, by way of example. Thus, it is not required that the data and instructions be on a tangible machine readable medium in entirety at a particular instance of time.
In some embodiments, the various logic blocks of Provider 402 are coupled together via Network Bus 806. Any suitable protocol may be used to implement Network Bus 806. In some embodiments, Machine-Readable Storage Medium 802 includes Instructions 802 a (also referred to as the program software code/instructions) for requesting and accepting a new power supply (e.g., new voltage and/or current) as described with reference to various embodiments and flowchart. Here, Instructions 802 a are the instructions performed by Provider 402 in flowchart 500 as described with reference to FIG. 5.
Program software code/instructions 502 a, associated with Provider 402 of flowchart 500, as described with reference to FIG. 5, and executed to implement embodiments of the disclosed subject matter may be implemented as part of an operating system or a specific application, component, program, object, module, routine, or other sequence of instructions or organization of sequences of instructions referred to as “program software code/instructions,” “operating system program software code/instructions,” “application program software code/instructions,” or simply “software” or firmware embedded in processor. In some embodiments, the program software code/instructions associated with Provider 402 of flowchart 500, as described with reference to FIG. 5, are executed by Processor or logic (e.g., finite state machine) 801 of Provider 402.
In some embodiments, the program software code/instructions 802 a associated with flowchart 500 are stored in a computer executable storage medium 802 and executed by Processor 801. Here, computer executable storage medium 802 is a tangible machine readable medium that can be used to store program software code/instructions and data that, when executed by a computing device, causes one or more processors (e.g., Processor 801) to perform a method(s) as may be recited in one or more accompanying claims directed to the disclosed subject matter.
The tangible machine readable medium 802 may include storage of the executable software program code/instructions 802 a and data in various tangible locations, including for example ROM, volatile RAM, non-volatile memory and/or cache and/or other tangible memory as referenced in the present application. Portions of this program software code/instructions 802 a and/or data may be stored in any one of these storage and memory devices. Further, the program software code/instructions can be obtained from other storage, including, e.g., through centralized servers or peer to peer networks and the like, including the Internet. Different portions of the software program code/instructions and data can be obtained at different times and in different communication sessions or in the same communication session.
The software program code/instructions 802 a (associated with Provider 402 of flowchart 500 as described with reference to FIG. 5 and other embodiments) and data can be obtained in their entirety prior to the execution of a respective software program or application by the computing device. Alternatively, portions of the software program code/instructions 802 a and data can be obtained dynamically, e.g., just in time, when needed for execution. Alternatively, some combination of these ways of obtaining the software program code/instructions 802 a and data may occur, e.g., for different applications, components, programs, objects, modules, routines or other sequences of instructions or organization of sequences of instructions, by way of example. Thus, it is not required that the data and instructions be on a tangible machine readable medium in entirety at a particular instance of time.
In some embodiments, USB power delivery system 900 comprises AC Main 101, Provider 402, Wireless Charging Mat Transmitter (Tx) 901, and Wireless Charging-enabled Computer System 903. In some embodiments, Wireless Charging Mat Transmitter (Tx) 901 comprises Power Amplifier (PA) 901 a, Impedance Matching stage 901 b, Auto Tune Relay 901 c, Management Microcontroller 901 d (e.g., system 500), Bluetooth Low Energy (LE) compliant Communication module 901 e, and Power Transmitter Unit (PTU) Coil. In some embodiments, Wireless Charging Mat Tx 901 includes hardware 403 d and/or Controller 403 e as described with reference to Power Consumer 403 of FIG. 4A. Referring back to FIG. 6, the Auto Tune Relay 901 c together with the PTU Coil sends power 902 wirelessly to Wireless Charging-enabled Computer System 903, in accordance with some embodiments.
In some embodiments, radio frequency Power Amplifier (PA 901 a) is a type of electronic amplifier used to convert a low-power signal into a larger signal of significant power, typically for driving the antenna of a transmitter. In some embodiments, Impedance Matching (Z-Match 901 b) provides an output impedance of a signal source to match with the physical impedance characteristics of an antenna in order to maximize the power transfer and/or minimize the signal reflection. In some embodiments, Auto Tune Relay 901 c is a switching circuit that automatically adjusts the frequency of a radio transmission. In some embodiments, the PTU Coil is a wire winding, typically circular, oval, or rectangular, which acts as the antenna for the transmission of wireless power. In some embodiments, a Management Microcontroller 901 d is a general-purpose microprocessor embedded with firmware which is able to execute code (e.g., code to manage the Power Delivery algorithms and communications for a device). In some embodiments, Bluetooth LE Communications module 901 e is a kind of radio by which two devices may exchange data messages (e.g., Power Delivery management messages).
In some embodiments, Wireless Charging-enabled Computer System 903 comprises: Power Receiver Unit (PRU) Coil, Power Receiver 903 a, Voltage Regulation module 903 b (e.g., Battery, Charger, low-dropout regulator, etc.), Bluetooth LE Communication module 903 c, Management Microcontroller 903 d, and Rest of System Circuits 903 e. In some embodiments, the PRU Coil receives the power 902 transmitted by PTU Coil of Tx 901 c.
In some embodiments, the PRU Coil is a wire winding, typically circular, oval, or rectangular, which acts as the antenna for the reception of wireless power. In some embodiments, a Battery (e.g., part of 903 b) is provided which is a reservoir for the storage of electrical power until later use is required. In some embodiments, a Charger (part of 903 b) is provided which is an electronic circuit that uses methods for the optimal insertion and storage of electrical charge into the Battery. In some embodiments, a voltage regulator (part of 903 b) is provided which is provides voltage regulation to constrain the delivery of a voltage to a load circuit to within a narrow range (for example, ±5%) even over a wide range of load conditions (for example, the current demands of the load circuit rise and fall dynamically). The input of the voltage regulator may be close to the target output voltage (e.g., input=+5V±20% and output=+5V±5%) or it may be a very different voltage (e.g., “buck regulator”: input=+20V±20% and output=+5V±5%, or “boost regulator”: input=+3.3V±10% and output=+9V±5%).
In some embodiments, Management Microcontroller 903 d is provided which is a general-purpose microprocessor embedded with firmware which is able to execute code (e.g., code to manage the Power Delivery algorithms and communications for a device). In some embodiments, Bluetooth LE Communications module 903 c is provided which is an example of one kind of radio by which two devices may exchange data messages (e.g., Power Delivery management messages).
In some embodiments, power efficiency information collected by/from the PRU is passed over Bluetooth LE Comm. 903 c from Management Microcontroller 903 d to Management Microcontroller 901 d of Wireless Charging Mat 901. Here, power efficiency generally refers to the power provided by Provider 402 over VBUS compared to the power 902 transmitted by Wireless Charging Mat 901.
In some embodiments, in response to this power efficiency information, Management Microcontroller 903 d sends a request for a more optimal power level to Management Microcontroller 901 d over Bluetooth LE, whereupon Management Microcontroller 901 d instructions hardware 403 d to modulate voltage or current on SBU pin to communicate with Power Provider 402 to adjust supply on VBUS. In some embodiments, Provider 402 adjusts its voltage and/or current output and supplies it to Wireless Charging Mat 901 over VBUS to better meet the needs determined by the analysis at the PRU. As such, power efficiency is brought closer to or at one.
US15/169,175 2016-04-08 2016-05-31 Adjustable power delivery apparatus for universal serial bus (usb) type-c Pending US20170293335A1 (en)
US201662320319P true 2016-04-08 2016-04-08
US15/169,175 US20170293335A1 (en) 2016-04-08 2016-05-31 Adjustable power delivery apparatus for universal serial bus (usb) type-c
TW106105705A TW201826079A (en) 2016-04-08 2017-02-21 Adjustable power delivery apparatus for universal serial bus (usb) type-c
PCT/US2017/021216 WO2017176413A1 (en) 2016-04-08 2017-03-07 Adjustable power delivery apparatus for universal serial bus (usb) type-c
US20170293335A1 true US20170293335A1 (en) 2017-10-12
ID=59998193
US15/169,175 Pending US20170293335A1 (en) 2016-04-08 2016-05-31 Adjustable power delivery apparatus for universal serial bus (usb) type-c
US (1) US20170293335A1 (en)
TW (1) TW201826079A (en)
WO (1) WO2017176413A1 (en)
US20180027330A1 (en) * 2016-07-25 2018-01-25 Cirrus Logic International Semiconductor Ltd. Connectors for data transfer
US10009029B1 (en) * 2017-03-22 2018-06-26 Hong Fu Jin Precision Industry (Wuhan) Co., Ltd. Interface control circuit to match voltage levels between USB devices upon connection
US10218129B1 (en) 2018-04-11 2019-02-26 Cypress Semiconductor Corporation Overvoltage protection for universal serial bus type-C (USB-C) connector systems
US10282333B2 (en) * 2015-04-28 2019-05-07 Samsung Electronics Co., Ltd. Electronic device operating method and electronic device for supporting the same
US10353853B1 (en) 2018-04-11 2019-07-16 Cypress Semiconductor Corporation USB type-C sideband signal interface circuit
TWI666875B (en) * 2018-12-25 2019-07-21 瑞昱半導體股份有限公司 Connection circuit and connection method thereof
WO2019177811A1 (en) * 2018-03-13 2019-09-19 Cypress Semiconductor Corporation Programmable gate driver control in usb power delivery
US10491030B2 (en) * 2016-07-26 2019-11-26 Guangdong Oppo Mobile Telecommunications Corp., Ltd. Charging system and charging method for terminal and terminal
US20150024939A1 (en) * 2011-05-05 2015-01-22 Dow Agrosciences Llc Stable high strength oil-in-water emulsions
US20160033522A1 (en) * 2014-08-01 2016-02-04 Osama AL-DIRBASHI Methylcitrate analysis in dried blood spots
US20160110305A1 (en) * 2014-10-15 2016-04-21 Icron Technologies Corporation Devices and methods for providing concurrent superspeed communication and four-lane displayport communication via a usb type-c receptacle
US20160179648A1 (en) * 2014-12-23 2016-06-23 Intel Corporation System to detect charger and remote host for type-c connector
US20160275031A1 (en) * 2015-03-16 2016-09-22 Samsung Electronics Co., Ltd. Method for improving data transmission speed and electronic device implementing the same
2016-05-31 US US15/169,175 patent/US20170293335A1/en active Pending
2017-02-21 TW TW106105705A patent/TW201826079A/en unknown
2017-03-07 WO PCT/US2017/021216 patent/WO2017176413A1/en active Application Filing
US10187727B2 (en) * 2016-07-25 2019-01-22 Cirrus Logic, Inc. Connectors for data transfer
TW201826079A (en) 2018-07-16
WO2017176413A1 (en) 2017-10-12
US9680337B2 (en) 2017-06-13 Multi-protocol ubiquitous wireless power transmitter
KR20150036765A (en) 2015-04-07 Cascading power for accessories
EP2803126A2 (en) 2014-11-19 System and method for providing wireless power transfer functionality to an electrical device
CN103312015A (en) 2013-09-18 Wireless charging circuit, wireless charging system and semiconductor device
TWI431462B (en) 2014-03-21 Supply voltage control based at least in part on power state of integrated circuit
Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:DUNSTAN, ROBERT A.;NGUYEN, DON J.;NGE, CHEE LIM;AND OTHERS;SIGNING DATES FROM 20160601 TO 20160610;REEL/FRAME:039966/0694