Notice of Pre-AIA or AIA Status
The present application, filed on or after March 16, 2013, is being examined under the first inventor to file provisions of the AIA .
This is in response to Amendment/Request for Reconsideration filed 07/01/26 Claims 1, 3– 12 have been amended and are pending.
Claim Rejections - 35 USC § 102
The following is a quotation of the appropriate paragraphs of 35 U.S.C. 102 that form the basis for the rejections under this section made in this Office action:
A person shall be entitled to a patent unless –
(a)(2) the claimed invention was described in a patent issued under section 151, or in an application for patent published or deemed published under section 122(b), in which the patent or application, as the case may be, names another inventor and was effectively filed before the effective filing date of the claimed invention.
Claim(s)1 – 12 is/are rejected under 35 U.S.C. 102(a)(2) as being anticipated by Huggins US 20190393706.
Regarding claims 1, and 12, Huggins anticipates a firmware updating method, executed by a charger, and comprising:
sending first data to a terminal, wherein the first data comprises charging state information of the charger during charging [0026, see monitor charge status];
the charging state information comprises at least one of a number of times of protection events, a charging current, a charging voltage, a device temperature. a charging efficiency, an adopted charging protocol, a charging power, a working state of a key device, a charging voltage requested by the terminal and a charging current requested by the terminal [0026, see battery pack current output, voltage across the battery cells, and charge status, note: claim calls for at least one of these capabilities];
receiving second data sent by the terminal, wherein the second data comprises program data determined based on the first data and configured for updating firmware of the charger;
and updating the firmware of the charger based on the second data [0035 shows receiver firmware];
wherein the charger is monitored to acquire the first data of the charger, in response to that the charger is connected with a power supply and the terminal [0026, see “…The communication module 124 monitors charge status, controls charging of the battery pack 150 by the charger 120…”].
Regarding claim 3, the method according to claim 1, further comprising:
storing the first data; and deleting the stored first data after a first time [0026 – 0035, shows stored data and updating the firmware which implies deleting and overwriting].
Regarding claim 4, the method according to claim 1, wherein the sending the first data to the terminal comprises: sending the first data to the terminal in response to being in a charging completion state [0036, see “…The communication module 124 receives data including status information…”].
Regarding claim 5, the method according to claim 1, further comprising:
sending update information to the terminal, wherein the update information indicates a progress of updating the firmware of the charger by the terminal [0026, see monitor charge status, i.e. completion or uncompletion].
Regarding claim 6, Huggins anticipates firmware updating method, is executed by a terminal, and comprising:
receiving first data sent by a charger, wherein the first data comprises charging state information of the charger during charging; sending the first data to a cloud [0026, see monitor charge status also 0020 – 0027 shows both cloud and server implementation];
receiving second data from the cloud in response to that firmware of the cloud is different from firmware of the charger, wherein the second data comprises program data determined based on the first data and configured for updating the firmware of the charger; and sending the second data to the charger [0026 – 0035. See updates and firmware].
Regarding claim 7, the method according to claim 6, wherein the sending the first data to the cloud comprises:
sending the first data to the cloud in response to that a state indicated by the charging state information is a first state, wherein the first state is determined based on the number of times of protection events that have occurred in the terminal [0037, shows receiving charging status information from devices].
Regarding claim 8, the method according to claim 6, wherein the sending the second data to the charger comprises: sending the second data to the charger in response to that the terminal is in a charging completion state [0026 - 0035].
Regarding claim 9, the method according to claim 6, wherein the sending the second data to the charger comprises: sending the second data to the charger in response to detecting a first operation instruction of a user [0035 shows receiver firmware].
Regarding claim 10, the method according to claim 6, wherein the sending the second data to the charger comprises: sending the second data to the charger in response to that the terminal is in a charging completion state ; and sending the second data to the charger in response to detecting a first operation instruction of a user [0026 – 0035].
Regarding claim 11, the method according to claim 6, further comprising:
receiving update information sent by the charger, wherein the update information indicates a progress of updating the firmware of the charger by the terminal [0026 – 0035].
Regarding claim 12, a firmware updating system, comprising a charger, a terminal and a cloud, wherein the charger is configured to send first data to the terminal, wherein the first data comprises charging state information of the charger during charging [0026 – 0035];
the terminal is configured to send the first data to the cloud [0026 - 0035];
the cloud is configured to acquire second data and send the second data to the terminal, wherein the second data comprises program data determined based on the first data and configured for updating firmware of the charger; and the terminal is configured to update the firmware of the charger based on the second data [0026 - 0041].
Response to Arguments
Applicant’s arguments with respect to claim(s) 1, and 3 – 12 have been considered but are moot because the new ground of rejection does not rely on any reference applied in the prior rejection of record for any teaching or matter specifically challenged in the argument.
Correspondence Information
Any inquiry concerning this communication or earlier communications from the examiner should be directed to Chuck Kendall whose telephone number is 571-272-3698. The examiner can normally be reached on 10:00 am - 6:30pm.
If attempts to reach the examiner by telephone are unsuccessful, the examiner’s supervisor, Hyung Sough can be reached on 571-272-6799. The fax phone number for the organization where this application or proceeding is assigned is 571-273-8300.
Information regarding the status of an application may be obtained from the Patent Application Information Retrieval (PAIR) system. Status information for published applications may be obtained from either Private PAIR or Public PAIR. Status information for unpublished applications is available through Private PAIR only [0060 – 0080].
For more information about the PAIR system, see http://pair-direct.uspto.gov. Should you have questions on access to the Private PAIR system, contact the Electronic Business Center (EBC) at 866-217-9197 (toll-free).
/CHUCK O KENDALL/
Primary Examiner, Art Unit 2192
Prosecution Insights