WO2015068043A2 - Charging device and method - Google Patents

Abstract

A charging device is configured to deliver power to a portable, power-consuming device, having a profile sensor which can detect information relating to the identity of power-consuming device to which the charging device is connected and may also have a communication channel configured to transmit said information to a remote server. In use, data can be collected or aggregated relating to power-consuming devices by connecting the charging device to the portable power-consuming device; sensing, by a profile sensor in the charging device, information relating to the identity of the power- consuming device; and transmitting the information to a remote server over a communication channel. Collected data may, for example, be used to identify when fuel for a charging device may need replenishment

Description

INTERNATIONAL PATENT APPLICATION

FOR

CHARGING DEVICE AND METHOD INVENTORS:

HENRI WINAND, JOHN JOSEPH MURRAY, AND CHRISTOPHER WILLIAM BISHOP

This application claims the full Paris Convention benefit of and priority to U.S.

provisional application no. 61/900,937 filed November 6, 2013, the contents of which is incorporated by this reference as if fully set forth herein in its entirety.

BACKGROUND

1. Field

[0001 ] The present disclosure relates to charging devices suitable for recharging portable, power-consuming devices such as mobile telephones, personal computing devices, music players, e-readers etc.

2. Disclosure

[0002] There are many portable consumer electronic devices in use which are powered by rechargeable power sources, such as batteries, and require frequent recharging from a more powerful energy source, such as the electricity grid or an electrical energy-generating module such as a fuel cell or a vehicle electrical system.

[0003] In most instances, a charging device is used to deliver power to the power- consuming device. In examples, the charging device may comprise a mains adaptor for converting the domestic mains or grid voltage from a high voltage alternating current to a low voltage direct current, or a DC-DC converter for converting a 12V or 24V vehicle supply to a suitable low voltage current for charging the power-consuming device. In many instances, the charging device is coupled to the power-consuming device using a standard interface such as a USB interface, which also provides data transfer capability. FIGURES

[0004] The disclosure may be better understood by referring to the following figures and appendix. The components in the figures and appendix are not necessarily to scale, emphasis instead being placed upon illustrating the principles of the disclosure.

[0005] Figure 1 shows a schematic diagram of a networked charging device and power-consuming device;

[0006] Figure 2 shows a schematic diagram of a charging device and power- consuming device as in figure 1 , with alternative networking arrangement.

FURTHER DISCLOSURE

[0007] Aspects of the devices, systems and methods disclosed herein include a charging device for delivering power to a portable, power-consuming device, having a profile sensor configured to detect information relating to the identity of power- consuming device to which the charging device is connected; and, a communication channel configured to transmit said information to a remote server. In some instances the profile sensor is configured to receive an identity of the power-consuming device via a data exchange protocol for connectivity of the charging device and the power consuming device. In some instances the profile sensor is configured to detect information relating to the identity of the power-consuming device by recording current and/or voltage supplied to the power-consuming device as a function of time.

[0008] The devices disclosed herein may further include a data log for temporarily storing data relating to the identity of power-consuming devices to which the charging device is or has been connected for charging or power supply.

[0009] The devices disclosed herein may further include a data relating to the identity of power-consuming devices comprises one or more of: a device unique identifier; a device generic type identifier; a device manufacturer identifier; a current-time profile; a voltage-time profile; a voltage-current profile; a charge state-time profile; a device usage profile. [0010] Aspects of the devices, systems and methods disclosed include methods for aggregating data relating to power consuming devices whereby a charging device for delivering power to a portable power-consuming device is provided; it is connected to a charging device; sensing is rakes place via a profile sensor in the charging device, information relating to the identity of the power-consuming device; and, collected or aggregated data is transmitted to a remote server over a communication channel. In some instances the information relating to the identity of the consuming device is one or more of: a device unique identifier; a device generic type identifier; a device manufacturer identifier; a current-time profile; a voltage-time profile; a voltage-current profile; a charge state-time profile; a device usage profile. In some instances the sensing step comprises analyzing one or more the profiles and determining a device identity based on the profile. The method may also include sensing environment data and providing that data to at least the server wherein system parameters and data may be correlated to said environment data.

The method may include the remote server, via a communication channel indicating when a fuel source for a charging device may need replenishment. The method may include sensing, by a profile sensor in the charging device, operational data of the power-consuming device.

[0011] Aspects of the devices, systems and methods disclosed include methods for aggregating data relating to power consuming devices including connecting a plurality of charging device for delivering power to a plurality of portable power-consuming devices sensing, by a profile sensor in each charging device, information relating to the identity of the power-consuming device; sensing, by a profile sensor in each charging device, operational data of the power-consuming device; andtransmitting said information to a remote server over a communication channel.

[0012] operational data , in some instances is at least one of the date and / or time of each charging event, the voltage and / or current profile or 'signature' of each charging event, the geographical location of each charging event, and the condition of the charging device 1 at, before, during or after each charging event. In some instances the aggregated data is used to predict performance of power consuming device is in a variety of conditions.

[0013] Persons of ordinary skill in the art of computer programming will recognize that the disclosure herein references operations that are performed by a computer system. Operations which are sometimes referred to as being computer-executed. It will be appreciated that such operations are symbolically represented to include the

manipulation by a processor, such as a CPU, with electrical signals representing data bits and the maintenance of data bits at memory locations, such as in system memory, as well as other processing of signals. Memory locations wherein data bits are maintained are physical locations that have particular electrical, magnetic, optical, or organic properties corresponding to the data bits.

[0014] When implemented in software, elements disclosed herein are aspects of some of the code segments to perform necessary tasks. The code segments can be stored in a non-transitory processor readable medium, which may include any medium that can store information. Examples of the non-transitory processor readable mediums include an electronic circuit, a semiconductor memory device, a read-only memory (ROM), a flash memory or other non-volatile memory, an optical disk, a hard disk, etc. The term "module" may refer to a software-only implementation, a hardware-only implementation, or any combination thereof. Moreover, the term "servers" may both refer to the physical servers on which an application may be executed in whole or in part. The regular or periodic connection of a charging device to one or more power-consuming devices offers a useful mechanism by which to gather data from the power-consuming devices to which the charging device is connected, and to transmit that data to a central resource via a communication network. With reference to Figure 1 , a charging device 1 is periodically connected to a power-consuming device 2 by way of a detachable or otherwise disconnectable charging and data link 3. The charging device 1 is connected, via a data link 7 and data communication network 4, to a server 5 having a database 6.

[0015] The charging device 1 may comprise any device capable of supplying power to a portable power-consuming device 2 in sufficient quantity to facilitate recharging, or at least partial recharging, of a battery or other charge storage device in the power- consuming device 2, or for powering the power-consuming device for extended periods of normal operation when auxiliary power is available. The expression 'charging device' may therefore encompass devices commonly referred to as power adaptors. The expression 'recharging' is intended to encompass any form of providing electrical energy to a storage device capable of storing energy for later release and may include regeneration of device in which chemical reaction takes place. In some instances the device 1 is a fuel cell power source, e.g. a hydrogen-powered proton exchange membrane fuel cell system capable of generating electrical power for recharging a power-consuming device 2 or for generally providing auxiliary power thereto. In other instances the charging device 1 could be a mains power adaptor for converting the domestic mains or line voltage from a high voltage alternating current to a low voltage direct current suitable for recharging or powering the power-consuming device 2. The charging device 1 could comprise a DC-DC voltage converter for use in, for example, a vehicle taking its input from a 12 or 24V vehicle electrical system and providing a low voltage direct current suitable for recharging or powering the power-consuming device 2.

[0016] The power-consuming device 2 may comprise any portable, self-contained and/or autonomous device which relies on an internal, rechargeable power source for operation which must be periodically recharged. Particular examples of such power- consuming devices include: mobile telephones including so-called 'smart phones';

personal computing devices including notebook computers, netbooks, tablet computers, personal digital assistants, etc.; entertainment devices such as music players, game playing devices or consoles; electronic books or 'e-readers'; video players, etc.;

cameras or video recording devices; and many other items commonly referred to as consumer electronics.

[0017] The charging device has a permanent or an intermittent data link 7 to a data communication network 4. The data communication network 4 may be the Internet or a local area network, for example. The data link 7 may be a wired connection or a wireless connection, using any suitable technology and transport protocol. For example, a short range wireless connection to a local WiFi router may be used for data link 7. Alternatively, a power connection 8 (shown as a dashed line) to a utility power line 9 could be used for data transfer to a router connected to the utility power line and to the network 4. In another arrangement (shown in Figure 2), the power-consuming device 2 itself may provide the data link between the charging device 1 and the network 4. This arrangement is shown in Figure 2 as link 7a (i.e. the charging and data link 3) and a communication channel 7b between the power-consuming device 2 and the network 4. In such an arrangement, the direct link 7 between the charging device 1 and the communication network 4 could be omitted. In other instances, the data link may be separate from the charging link. In yet other instances, the data may be transmitted back via the mains (or other low voltage network, for example, a telephone network), Ethernet, or other low voltage wired systems.

[0018] In a particularly convenient arrangement, where the power-consuming device 2 is a mobile telephone, the link 7a may comprise a USB cable and the communication channel 7b may comprise a cellular telephone network. In such an arrangement, communication between the charging device 1 and the network 4 and server 5 can conveniently be controlled by an application program loaded onto the power-consuming device 2 (e.g. smart phone).

[0019] The data link 7a could be the combined charging and data link 3 itself (e.g. USB cable), or the data link 7a could be separate from the hardwired charging link 3. In this respect, the data link 7a could be a short range wireless communication channel such as Bluetooth.

[0020] The server 5 may be any suitable remote computing resource including a database 6 which is capable of receiving data relating to the relationship between the charging device 1 and the power-consuming device 2 as will be explained in more detail below. The server 5 is preferably capable of managing data received from many such charging devices 1 , the data relating to relationships between the many such charging devices 1 and the power consuming devices to which they are periodically connected. The server 5 may be capable of aggregating data from these many relationships and providing the data to other entities such as one or more service providers 10. [0021] The charging device 1 includes a profile sensor 1 1 which may be configured to collect environment data relating geolocation, altitude, pressure, temperature, humidity. Some of said data can be collected via local sensors, other dat may be collected or approximated via a weather database and the rules and decision engines within the server correlate such data. Those of ordinary skill in the art will recognize that such data may be important in system with batteries and fuel cell components as they performance characteristics will vary based on variations in same. In addition to the environment data the system will also collect the identity of some or all of the power- consuming devices 2 to which the charging device 1 is connected for charging or power supply. The data can be stored or buffered in an internal data log 12. The data can be transferred either in real time, or in periodic bursts, to the server 5 at suitable times consistent with the availability of the data link 7 or 7a, 7b.

[0022] The data can be technically and/or commercially useful to: (i) manufacturers and/or vendors of the power-consuming devices 2, (ii) manufacturers and/or vendors of the charging devices 1 ; and, (iii) vendors of consumer services and products associated with the power-consuming devices 2 and /or the charging devices 1.

[0023] For example, the service provider 10 could be a manufacturer or vendor of power-consuming devices 2, or a service provider connected with the use of such power-consuming devices 2, e.g. mobile telephones. The charging device 1 may provide useful information relating to the performance of the charging process, indicative of the technical performance of the battery or power management system of the power-consuming device, its identity and its patterns or mode of use. In another example, the service provider 10 could be a manufacturer or vendor of charging devices 1 , or a service provider connected with the use of such power-consuming devices 1 , e.g. a fuel cell power supply manufacturer. The charging device 1 may then provide the service provider 10 with useful information relating to the performance of the charging process as it relates to different types of power-consuming device, and to different modes of use.

By way of example, the data gathered by the charging device 1 may include any or all of the following types of data: (i) a unique identifier, e.g. the individual identity or serial number of any power-consuming device 2 that has been connected to the charging device 1 ; (ii) a generic type identifier, e.g. the device type or class of device any power- consuming device 2 that has been connected to the charging device 1 ; (iii) a

manufacturer identity, e.g. the identity of the manufacturer of any power-consuming device 2 that has been connected to the charging device 1 ; (iv) the date and/or time of each charging event; (v) the voltage and/or current profile or 'signature' of each charging event, e.g. a current-time profile, a voltage-time profile, a voltage-current profile, a charge state-time profile, which may be derived over time from a separate database which can match the profile of what is measured through the intelligence of the charging device comparing with other database records to match or approximate what the device is in the event that the device cannot be detected then and there by asking it "what it is" with a query from the charger to the device for instance; (vi) the geographical location of each charging event, which could be automatically sensed either by the charging device 1 or the power-consuming device 2, e.g. using GPS sensing, collected environment data, network address sensing or a combination thereof; (vii) the condition of the charging device 1 at, before, during or after each charging event (e.g. for a hydrogen fuel cell, the hydrogen level remaining or fuel cell

performance parameter); (viii) a usage profile of the power-consuming device 2 or the charging device 1 , e.g. time and frequency of use, power demand, modes of use etc.

[0024] The above list is not intended to be exhaustive but provides examples of information relating to the identity of the power-consuming device to which the charging device is connected.

[0025] Such information can be usefully deployed for a wide range of purposes.

[0026] The data can be used to authorize use of the charger 1 for a particular charging event (e.g. to prevent unauthorized or inappropriate use that could damage either the charger 1 or power-consuming device 2). Environment data may be provided to at least one of the device, charger and the server wherein system parameters and data may be correlated to the environment data.

[0027] The data can be used to control a mode of use of the charger, e.g. by ensuring use of a particular charging mode or operational profile of the charging device for each power-consuming device 2 to which it is connected to prevent damage to either device. Examples of a charging mode or operational profile could include determining maximum current or voltage as a function of time and/or existing charge state or voltage, or could include limiting current for some or all of a charging event.

[0028] The data can be used to provide information on the technical performance of either the charging device 1 or the power-consuming device 2 under varying conditions of use, including frequency of charging, location of charging, and conditions prevailing during charging. Such conditions could include local conditions of temperature or humidity or air pressure, for example. Environment data, as previously noted, may be derived locally, or acquired from remote locations (i.e. weather websites).

[0029] Such technical data may be useful in assessing the performance of devices over many hundreds or thousands of power-consuming devices in widely varying conditions of use. Such data when aggregated for particular types of power-consuming device, over many thousands or millions of charging events, can be used to very accurately identify problems with the technical design of the power-consuming device or te charging device, or with different users' modes of use of the devices. This can direct product improvement either to the existing devices or to future devices. The data could direct product improvement to existing devices by facilitating the re-design and download of, for example, software upgrades to either the charger 1 or the power- consuming device. The software could control power management in the devices.

[0030] The data may be used to indicate when device servicing or replacement is required, or to optimize service plans of the devices, including indicating when a fuel source (e.g. hydrogen source) for a charging device may need replenishment. The data may be used to manage such servicing, e.g. by enabling a service provider to indicate directly to the user how and where to effect such servicing, based on the gathered data. The data may be used to collect data on user choice of devices and such data may predict trends of use. The data may also track brand (device such as cell phone) to market dominance as well as success or decline in a brand.

[0031] Where the power-consuming device 2 has on-board intelligence, such as a data processing capability and/or data communication facility (e.g. USB connectivity), the charging device 1 may be able to interrogate the power-consuming device 2 to supply at least some if not all the required data directly, using a suitable data exchange protocol for connectivity of the charging device and the power-consuming device. This could be supported by USB protocols, for example.

[0032] In other arrangements, the charging device 1 may be configured to deduce some or all of the required data itself by monitoring an observable characteristic of the power-consuming device during operation or charging, such as the voltage and/or current profile as a function of time or 'signature' of the charging process. By collecting detailed information on charging per user, per location and per device(s) energy (or utility) packages may be narrowly tailored for the needs of the user.

[0033] As demanded by the power-consuming device during the charging or power supply event, the charging device 1 may be able to deduce an identity of, or a device type of, the connected power-consuming device 2 by comparing a voltage and/or current profile or signature with a set of templates each of which indicates a particular device type or device identity. The templates could be stored at a suitable location such as within the charging device 1 or at the remote server 5. The identities of the power- consuming devices 2 that are connected to the charging device 1 can therefore be determined either by the charging device, or by the server 5, or partially in both the charging device and server 5, for example.

[0034] In general, the data can be aggregated, analyzed and/or buffered either on the charging device 1 itself in the data log 12 for periodic upload to the central server 5 or can be transmitted unprocessed or partially processed and/or in real time to the central server 5, depending on the availability of a data communication link 7 or 7a, 7b.

[0035] The charging device 1 could be supplied to end users together with an application program for use on the power-consuming device 2 (e.g. mobile telephone, portable computer) which controls or monitors operation of the charging device 1 , particularly where this is a fuel cell charging device requiring sophisticated management for optimal performance. The application program then also serves as a suitable conduit, via communication channels 7a, 7b, for the data gathered by the charging device 1. The application program can readily be configured and authorized to use the telecommunication data channel 7b of a mobile phone, in order to transfer data to the server 5 over the communication network 4. In such a case, the communication network 4 can be a combination of the cellular telephone network and the Internet. The application program can also provide any required credentials required for access to the server 5.

[0036] In a general aspect, reference to the communication channels 7, 7a may include the transmit/receive components in each of the charging device 1 or power consuming device 2 as appropriate at the device level, and the data connections between them at the overall system level. Thus, in the context of a charging device 1 , the expression 'communication channel' can be understood to refer to the transmit and receive and interface components and connectors within the device necessary to achieve a communication with the network 4 or power consuming device 2. In the context of the overall system level, the expression 'communication channel' can be understood to refer to all elements in the communication chain between the charging device and the server 5.

FURTHER DESCRIPTION

[0037] In the following description of examples of implementations, reference is made to the accompanying drawings that form a part hereof, and which show, by way of illustration, specific implementations of the present disclosure that may be utilized.

[0038] While the method and apparatus have been described in terms of what are presently considered to be the most practical and preferred implementations, it is to be understood that the disclosure need not be limited to the disclosed implementations. It is intended to cover various modifications and similar arrangements included within the spirit and scope of the claims, the scope of which should be accorded the broadest interpretation so as to encompass all such modifications and similar structures. The present disclosure includes any and all implementations of the following claims.

[0039] It should also be understood that a variety of changes may be made without departing from the essence of the disclosure. Such changes are also implicitly included in the description. They still fall within the scope of this disclosure. It should be understood that this disclosure is intended to yield a patent covering numerous aspects of the disclosure both independently and as an overall system and in both method and apparatus modes.

[0040] Further, each of the various elements of the disclosure and claims may also be achieved in a variety of manners. This disclosure should be understood to encompass each such variation, be it a variation of an implementation of any apparatus

implementation, a method or process implementation, or even merely a variation of any element of these.

[0041] Particularly, it should be understood that as the disclosure relates to elements of the disclosure, the words for each element may be expressed by equivalent apparatus terms or method terms - even if only the function or result is the same.

[0042] Such equivalent, broader, or even more generic terms should be considered to be encompassed in the description of each element or action. Such terms can be substituted where desired to make explicit the implicitly broad coverage to which this disclosure is entitled.

[0043] It should be understood that all actions may be expressed as a means for taking that action or as an element which causes that action.

[0044] Similarly, each physical element disclosed should be understood to encompass a disclosure of the action which that physical element facilitates.

[0045] Any patents, publications, or other references mentioned in this application for patent are hereby incorporated by reference. In addition, as to each term used it should be understood that unless its utilization in this application is inconsistent with such interpretation, common dictionary definitions should be understood as incorporated for each term and all definitions, alternative terms, and synonyms such as contained in at least one of a standard technical dictionary recognized by artisans and the Random House Webster's Unabridged Dictionary, latest edition are hereby incorporated by reference.

[0046] Finally, all referenced listed in the Information Disclosure Statement or other information statement filed with the application are hereby appended and hereby incorporated by reference; however, as to each of the above, to the extent that such information or statements incorporated by reference might be considered inconsistent with the patenting of this/these disclosure(s), such statements are expressly not to be considered as made by the applicant(s).

[0047] In this regard it should be understood that for practical reasons and so as to avoid adding potentially hundreds of claims, the applicant has presented claims with initial dependencies only.

[0048] Support should be understood to exist to the degree required under new matter laws - including but not limited to United States Patent Law 35 USC 132 or other such laws - to permit the addition of any of the various dependencies or other elements presented under one independent claim or concept as dependencies or elements under any other independent claim or concept.

[0049] To the extent that insubstantial substitutes are made, to the extent that the applicant did not in fact draft any claim so as to literally encompass any particular implementation, and to the extent otherwise applicable, the applicant should not be understood to have in any way intended to or actually relinquished such coverage as the applicant simply may not have been able to anticipate all eventualities; one skilled in the art, should not be reasonably expected to have drafted a claim that would have literally encompassed such alternative implementations.

[0050] Further, the use of the transitional phrase "comprising" is used to maintain the "open-end" claims herein, according to traditional claim interpretation. Thus, unless the context requires otherwise, it should be understood that the term "compromise" or variations such as "comprises" or "comprising", are intended to imply the inclusion of a stated element or step or group of elements or steps but not the exclusion of any other element or step or group of elements or steps.

[0051] Such terms should be interpreted in their most expansive forms so as to afford the applicant the broadest coverage legally permissible.

Claims

1. A charging device for delivering power to a portable, power-consuming device, comprising:

a profile sensor configured to detect information relating to the identity of power- consuming device to which the charging device is connected; and,

a communication channel configured to transmit said information to a remote server.

2. The charging device of claim 1 in which the profile sensor is configured to receive an identity of the power-consuming device via a data exchange protocol for connectivity of the charging device and the power consuming device.

3. The charging device of claim 1 in which the profile sensor is configured to receive an identity of the power-consuming device via a USB connection.

4. The charging device of claim 1 in which the profile sensor is configured to detect information relating to the identity of the power-consuming device by recording current and/or voltage supplied to the power-consuming device as a function of time.

5. The charging device of claim 1 comprising a fuel cell power supply device.

6. The charging device of claim 1 comprising a mains power adaptor or a DC-DC converter.

7. The charging device of claim 1 further including a data log for temporarily storing data relating to the identity of power-consuming devices to which the charging device is or has been connected for charging or power supply.

8. The charging device of claim 7 in which the data relating to the identity of power- consuming devices comprises one or more of: a device unique identifier; a device generic type identifier; a device manufacturer identifier; a current-time profile; a voltage- time profile; a voltage-current profile; a charge state-time profile; a device usage profile.

9. A method for aggregating data relating to power consuming devices comprising: providing a charging device for delivering power to a portable power-consuming device;

connecting the charging device to a said portable power-consuming device; sensing, by a profile sensor in the charging device, information relating to the identity of the power-consuming device; and,

transmitting said information to a remote server over a communication channel.

10. The method of claim 9, wherein transmitting said information is via a

communication channel provided by the power-consuming device.

1 1. The method of claim 9, wherein information relating to the identity of the consuming device is one or more of: a device unique identifier; a device generic type identifier; a device manufacturer identifier; a current-time profile; a voltage-time profile; a voltage-current profile; a charge state-time profile; a device usage profile.

12. The method of claim 11 , wherein the sensing step comprises analyzing one or more the profiles and determining a device identity based on the profile.

13. The method of claim 12, further comprising sensing environment data and providing that data to at least the server wherein system parameters and data may be correlated to said environment data.

14. The method of claim 12, further comprising the remote server, via a communication channel indicating when a fuel source for a charging device may need replenishment.

15. The method of claim 12, the method further comprising sensing, by a profile sensor in the charging device, operational data of the power-consuming device.

16. A method for aggregating data relating to power consuming devices comprising: connecting a plurality of charging device for delivering power to a plurality of portable power-consuming devices;

sensing, by a profile sensor in each charging device, information relating to the identity of the power-consuming device;

sensing, by a profile sensor in each charging device, operational data of the power-consuming device; and,

transmitting said information to a remote server over a communication channel.

17. The method of claim 16 wherein the operational data is at least one of

the date and / or time of each charging event, the voltage and / or current profile or 'signature' of each charging event, the geographical location of each charging event, and the condition of the charging device at, before, during or after each charging event.

18. The method of claim 16 wherein the aggregated data is used to predict

performance of power consuming device is in a variety of conditions.