Updating method and device, firmware updating system, electronic equipment and storage medium

Abstract

The embodiment of the invention discloses a firmware updating method and device, a firmware updating system, electronic equipment and a storage medium. The method comprises the following steps: sending first data to a terminal, wherein the first data comprises charging state information of a charger end in a charging process; receiving second data sent by the terminal, wherein the second data comprises program data which is determined based on the first data and is used for updating firmware of the charger end; and updating firmware of the charger end based on the second data. In the embodiment of the invention, compared with a mode that the program of the firmware cannot be updated, the firmware of the charger end can be updated, on one hand, when the charger end fails, the program of the firmware can be updated in time, and on the other hand, the program of the firmware can adapt to the charging state information. Therefore, the charging process of the charger end is more reliable, and the situation of potential safety hazards caused by charging failures and charging faults is reduced.

Description

Technical Field

[0001] The present disclosure relates to the field of charging technology, and in particular to a firmware update method, device, firmware update system, electronic device and storage medium. Background Art

[0002] With the continuous development of terminal (e.g. mobile phone) charging technology, the charging power is getting higher and higher, and the performance and safety of the charger are becoming more and more important. During the charging process, if the firmware of the charger is damaged or the hardware is not running properly, charging may fail, and in high-power charging scenarios, it may even cause safety hazards. Summary of the invention

[0003] The present disclosure provides a firmware update method, device, firmware update system, electronic device and storage medium.

[0004] According to a first aspect of the present disclosure, a firmware update method is provided, the method being executed by a charger end, the method comprising:

[0005] Sending first data to a terminal, wherein the first data includes charging status information of the charger during the charging process;

[0006] receiving second data sent by the terminal, wherein the second data includes program data for updating the firmware of the charger end determined based on the first data;

[0007] The firmware of the charger terminal is updated based on the second data.

[0008] In one embodiment, the charging status information includes at least one of the following:

[0009] The number of over-protection events, charging current, charging voltage, device temperature, charging efficiency, charging protocol used, charging power, working status of key devices, charging voltage requested by the terminal, and charging current requested by the terminal.

[0010] In one embodiment, the method further comprises:

[0011] storing the first data;

[0012] The first stored data is deleted after a first time.

[0013] In one embodiment, sending the first data to the terminal includes:

[0014] In response to being in a charging completion state, sending the first data to the terminal.

[0015] In one embodiment, the method further comprises:

[0016] Sending update information to the terminal;

[0017] The update information indicates the progress of the terminal updating the program data of the firmware of the charger end.

[0018] According to a second aspect of the present disclosure, a firmware update method is provided, the method being executed by a terminal, the method comprising:

[0019] receiving first data sent by a charger end, wherein the first data includes charging status information of the charger end during a charging process;

[0020] Sending the first data to the cloud;

[0021] In response to the firmware on the cloud being different from the firmware on the charger, receiving second data from the cloud, the second data including program data of updated firmware determined based on the first data;

[0022] The second data is sent to the charger end.

[0023] In one embodiment, sending the first data to the cloud includes:

[0024] In response to the state indicated by the charging state information being a first state, sending the first data to the cloud;

[0025] The first state is determined based on the number of over-protection events that occur at the terminal.

[0026] In one embodiment, sending the second data to the charger terminal includes:

[0027] In response to the terminal being in a charging completion state, sending the second data to the charger end;

[0028] and / or,

[0029] In response to detecting a first operation instruction from a user, the second data is sent to the charger end.

[0030] In one embodiment, the method further comprises:

[0031] Receiving update information sent by the charger end;

[0032] The update information indicates the progress of the terminal updating the program data of the firmware of the charger end.

[0033] According to a third aspect of the present disclosure, a firmware update method is provided, the method being executed by a cloud, and the method comprising:

[0034] receiving first data sent by a terminal, wherein the first data includes charging status information of the charger terminal during the charging process;

[0035] acquiring second data, the second data comprising program data of updated firmware determined based on the first data;

[0036] The second data is sent to the terminal.

[0037] According to a fourth aspect of the present disclosure, a firmware update method is provided, the method being executed by a firmware update system, the method comprising:

[0038] The charger end sends the first data to the terminal, where the first data includes charging status information of the charger end during the charging process;

[0039] The terminal sends the first data to the cloud;

[0040] The cloud acquires second data, wherein the second data includes program data for updating the firmware of the charger end determined based on the first data;

[0041] The cloud sends the second data to the terminal;

[0042] The terminal updates the firmware of the charger end based on the second data.

[0043] According to a fifth aspect of the present disclosure, a firmware update device is provided, the device comprising:

[0044] A first sending module is configured to send first data to a terminal, wherein the first data includes charging status information of the charger terminal during the charging process;

[0045] a first receiving module configured to receive second data sent by the terminal, wherein the second data includes program data for updating the firmware of the charger terminal determined based on the first data;

[0046] The first update module is configured to update the firmware of the charger end based on the second data.

[0047] In one embodiment, the first sending module is further configured to: the charging status information includes at least one of the following:

[0048] The number of over-protection events, charging current, charging voltage, device temperature, charging efficiency, charging protocol used, charging power, working status of key devices, charging voltage requested by the terminal, and charging current requested by the terminal.

[0049] In one embodiment, the apparatus further comprises:

[0050] A storage module, configured to store the first data;

[0051] The deletion module is configured to delete the first stored data after a first time.

[0052] In one embodiment, the first sending module is further configured to:

[0053] In response to being in a charging completion state, sending the first data to the terminal.

[0054] In one embodiment, the first sending module is further configured to:

[0055] Sending update information to the terminal;

[0056] The update information indicates the progress of the terminal updating the program data of the firmware of the charger end.

[0057] According to a sixth aspect of the present disclosure, a firmware update device is provided, the device comprising:

[0058] A second receiving module is configured to receive first data sent by the charger end, wherein the first data includes charging state information of the charger end during the charging process;

[0059] A second sending module is configured to send the first data to the cloud;

[0060] The second receiving module is further configured to: in response to the firmware on the cloud being different from the firmware on the charger, receive second data from the cloud, wherein the second data includes program data of the updated firmware determined based on the first data;

[0061] The second sending module is further configured to: send the second data to the charger end.

[0062] In one embodiment, the second sending module is further configured to:

[0063] In response to the state indicated by the charging state information being a first state, sending the first data to the cloud;

[0064] The first state is determined based on the number of over-protection events that occur at the terminal.

[0065] In one embodiment, the second sending module is further configured to:

[0066] In response to the terminal being in a charging completion state, sending the second data to the charger end;

[0067] and / or,

[0068] In response to detecting a first operation instruction from a user, the second data is sent to the charger end.

[0069] In one embodiment, the second receiving module is further configured to:

[0070] Receiving update information sent by the charger end;

[0071] The update information indicates the progress of the terminal updating the program data of the firmware of the charger end.

[0072] According to a seventh aspect of the present disclosure, a firmware update device is provided, the device comprising:

[0073] A third receiving module is configured to receive first data sent by the terminal, wherein the first data includes charging status information of the charger during the charging process;

[0074] A second acquisition module is configured to acquire second data, wherein the second data includes program data of the updated firmware determined based on the first data;

[0075] The third sending module is configured to send the second data to the terminal.

[0076] According to an eighth aspect of an embodiment of the present disclosure, a firmware update system is provided, which includes a charger end, a terminal and a cloud; wherein the charger end is used to execute any method executed by the charger end described in the present disclosure, the terminal is used to execute any method executed by the terminal, and the cloud is used to execute the method executed by the cloud.

[0077] According to a ninth aspect of the embodiments of the present disclosure, there is further provided an electronic device, including:

[0078] Memory;

[0079] The processor is connected to the memory and is configured to execute computer executable instructions stored in the memory and is capable of performing the steps of the method provided by any of the aforementioned technical solutions.

[0080] According to the tenth aspect of an embodiment of the present disclosure, a non-temporary computer-readable storage medium is also provided, wherein the non-temporary computer-readable storage medium stores an executable program, wherein the executable program, when executed by a processor, implements the steps of the method provided by any of the aforementioned technical solutions.

[0081] The technical solution provided by the embodiments of the present disclosure may have the following beneficial effects:

[0082] In the embodiment of the present disclosure, first data is sent to the terminal, the first data including the charging status information of the charger end during the charging process; second data sent by the terminal is received, the second data including program data for updating the firmware of the charger end determined based on the first data; and the firmware of the charger end is updated based on the second data. Here, the charger end sends the first data of the charger end including the charging status information of the charger end during the charging process to the terminal, and can receive the second data from the terminal. Since the second data includes the program data for updating the firmware of the charger end determined based on the first data, after receiving the second data, the firmware program can be updated based on the second data. Compared with the method in which the firmware program cannot be updated, the firmware of the charger end can be updated. On the one hand, when a fault occurs at the charger end, the firmware program can be updated in time, and on the other hand, the firmware program can be adapted to the charging status information. In this way, the charging process of the charger end will be more reliable, reducing the situation of safety hazards caused by charging failure and charging failure.

[0083] It is to be understood that the foregoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of the present disclosure. BRIEF DESCRIPTION OF THE DRAWINGS

[0084] The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the invention and, together with the description, serve to explain the principles of the invention.

[0085] Figure 1 The figure is a flowchart of a firmware update method according to an exemplary embodiment.

[0086] Figure 2 The figure is a flowchart of a firmware update method according to an exemplary embodiment.

[0087] Figure 3 The figure is a flowchart of a firmware update method according to an exemplary embodiment.

[0088] Figure 4 The figure is a flowchart of a firmware update method according to an exemplary embodiment.

[0089] Figure 5 The figure is a flowchart of a firmware update method according to an exemplary embodiment.

[0090] Figure 6 The figure is a flowchart of a firmware update method according to an exemplary embodiment.

[0091] Figure 7The figure is a schematic diagram showing the structure of a firmware update device according to an exemplary embodiment.

[0092] Figure 8 The figure is a schematic diagram showing the structure of a firmware update device according to an exemplary embodiment.

[0093] Fig. 9 The figure is a schematic diagram showing the structure of a firmware update device according to an exemplary embodiment.

[0094] Fig.10 It is a block diagram of an electronic device according to an exemplary embodiment. DETAILED DESCRIPTION

[0095] Exemplary embodiments will be described in detail herein, examples of which are shown in the accompanying drawings. When the following description refers to the drawings, the same numbers in different drawings represent the same or similar elements unless otherwise indicated. The embodiments described in the following exemplary embodiments do not represent all embodiments consistent with the present invention. Instead, they are merely examples of devices and methods consistent with some aspects of the present invention as detailed in the appended claims.

[0096] In order to facilitate the understanding of any embodiment of the present disclosure, first, the relevant scenarios are described:

[0097] In one embodiment, the charger that provides power for charging the mobile phone interacts with the mobile phone according to a specific protocol (for example, the power transmission (PD) protocol or each manufacturer's own private protocol, etc.), and provides the mobile phone with the voltage and / or current requested by the mobile phone. However, in long-term use, the charger cannot be upgraded for firmware and charging status detection, and there is no charger management data for developers to analyze. If there is a problem with the charger itself, even if it is a firmware problem, the charger firmware cannot be repaired and upgraded.

[0098] like Figure 1 As shown, an embodiment of the present disclosure provides a method for updating firmware, which is executed by a charger end and includes:

[0099] Step 11: Sending first data to the terminal, wherein the first data includes charging status information of the charger during the charging process;

[0100] Step 12: receiving second data sent by the terminal, wherein the second data includes program data for updating the firmware of the charger end determined based on the first data;

[0101] Step 13: Update the firmware of the charger based on the second data.

[0102] In one embodiment, first data of a charger end is acquired, the first data including charging status information of the charger end during charging. The first data is sent to a terminal. Second data sent by the terminal is received, the second data including program data for updating firmware of the charger end determined based on the first data. The firmware of the charger end is updated based on the second data.

[0103] In one embodiment, the terminal may actively acquire the first data of the charger end. For example, the terminal may periodically acquire the first data according to a first cycle. For example, in response to a change in the first data, the terminal actively acquires the first data of the charger end.

[0104] It should be noted that in the present disclosure, the firmware version rollback also belongs to a method of updating the program data of the firmware of the charger end in the present disclosure. That is, updating the program data of the firmware of the charger end may include performing a version rollback operation on the firmware.

[0105] In one embodiment, the charger end may be a charger with data processing and data transmission functions. After connecting the power supply end and the terminal, the charger end may charge the terminal, send data to the terminal, and receive data sent by the terminal.

[0106] In one embodiment, each of the charger terminals corresponds to a unique identifier for representing the charger terminal.

[0107] In one embodiment, the charger end is provided with a programmable memory, the programmable memory stores a firmware program, and the programmable memory can be repeatedly written and erased (for example, 1000 times). Here, the firmware program can be a control program related to controlling charging and / or communication of the charger end.

[0108] In one embodiment, the charger end is provided with a predetermined storage space (e.g., 32M). The predetermined storage space is used to store key data obtained during the operation of a fixed program, such as date, number of times over-temperature protection (OTP) occurs, number of times over-current protection (OCP) occurs, number of times over-voltage protection (OVP) occurs, number of times under-voltage protection (UVP) occurs, charger negative temperature coefficient (NTC) temperature, number of overheating, charger output current, charger output voltage, charging efficiency, protocol used, and other data. It should be noted that the key data can be retained for a predetermined period of time (e.g., 1 month), and if the predetermined period of time is exceeded, the saved key data can be automatically deleted.

[0109] In one embodiment, the terminal may be various types of mobile devices or fixed devices. For example, the electronic device may be a mobile phone, a computer, a smart wearable terminal, a smart home terminal, an industrial sensor device and / or a medical device.

[0110] In one embodiment, the cloud may be a cloud server. The charger may perform data exchange with the cloud through the terminal.

[0111] In some embodiments, "first data" and "point-marking data" and "point-burying data" can be interchangeable in certain scenarios, and can all refer to data associated with the charging status obtained by monitoring the charger end.

[0112] In one embodiment, the charging status information includes at least one of the following:

[0113] The number of over-protection events, charging current, charging voltage, device temperature, charging efficiency, charging protocol used, charging power, working status of key devices, charging voltage requested by the terminal, and charging current requested by the terminal.

[0114] Here, the number of times the over-protection occurs may be the number of times the OTP occurs, the number of times the OCP occurs, the number of times the OVP occurs, and / or the number of times the UVP occurs.

[0115] In one embodiment, in response to the charger end being connected to a power source and a terminal, the charger end is monitored and first data of the charger end is acquired, wherein the first data includes charging status information of the charger end during the charging process. Exemplarily, the first data of the charger end may be acquired periodically. In response to acquiring the first data, the first data is sent to the terminal. Second data sent by the terminal is received, wherein the second data includes program data for updating the firmware of the charger end determined based on the first data. The firmware of the charger end is updated based on the second data.

[0116] In one embodiment, first data of a charger end is acquired, the first data including charging status information of the charger end during charging. The first data is sent to a terminal. Second data sent by the terminal is received, the second data including program data for updating firmware of the charger end determined based on the first data. The firmware of the charger end is updated based on the second data. The first data is stored. The stored first data is deleted after a first time.

[0117] In one embodiment, a request message for triggering acquisition of first data sent by a terminal is received, the first data including charging status information of the charger end during charging. In response to acquiring the request message, the first data of the charger end is acquired. A request message for requesting the first data sent by the terminal is received. In response to receiving the request message, the first data is sent to the terminal. Second data sent by the terminal is received, the second data including program data for updating the firmware of the charger end determined based on the first data. The firmware of the charger end is updated based on the second data.

[0118] In one embodiment, first data of a charger end is acquired, the first data including charging status information of the charger end during charging. The first data is periodically sent to a terminal. Second data sent by the terminal is received, the second data including program data for updating firmware of the charger end determined based on the first data. The firmware of the charger end is updated based on the second data.

[0119] In one embodiment, first data of a charger end is acquired, the first data including charging status information of the charger end during charging. Request information for the first data sent by the terminal is received. In response to receiving the request information, the first data is sent to the terminal. Second data sent by the terminal is received, the second data including program data for updating the firmware of the charger end determined based on the first data. The firmware of the charger end is updated based on the second data.

[0120] In one embodiment, first data of a charger end is acquired, the first data including charging status information of the charger end during charging. In response to being in a charging completion state, the first data is sent to the terminal. Second data sent by the terminal is received, the second data including program data for updating firmware of the charger end determined based on the first data. The firmware of the charger end is updated based on the second data.

[0121] In one embodiment, first data of a charger terminal is acquired, the first data including charging status information of the charger terminal during charging. In response to being in a charging fault state, the first data is sent to the terminal. Second data sent by the terminal is received, the second data including program data for updating firmware of the charger terminal determined based on the first data. The firmware of the charger terminal is updated based on the second data.

[0122] In one embodiment, first data of a charger end is acquired, the first data including charging status information of the charger end during charging. The first data is sent to a terminal. Second data sent by the terminal is received, the second data including program data for updating firmware of the charger end determined based on the first data. Trigger information for updating firmware sent by the terminal is received. In response to receiving the trigger information, the firmware of the charger end is updated based on the second data.

[0123] In one embodiment, first data of a charger terminal is acquired, the first data including charging status information of the charger terminal during charging. The first data is sent to a terminal. Second data sent by the terminal is received, the second data including program data for updating firmware of the charger terminal determined based on the first data. In response to being in a charging completion state, the firmware of the charger terminal is updated based on the second data.

[0124] In one embodiment, first data is sent to a terminal, wherein the first data includes charging status information of the charger end during the charging process. Second data sent by the terminal is received, wherein the second data includes program data for updating the firmware of the charger end determined based on the first data. The firmware of the charger end is updated based on the second data. Update information is sent to the terminal; wherein the update information indicates the progress of the terminal updating the program data of the firmware of the charger end. Here, the progress can be a percentage, for example, 50% or 80%. It should be noted that after receiving the update information, the terminal can display the progress. In this way, the user can intuitively see the displayed progress information.

[0125] In the embodiment of the present disclosure, first data of the charger end is obtained, the first data includes the charging status information of the charger end during the charging process; the first data is sent to the terminal; the second data sent by the terminal is received, the second data includes the program data of the updated firmware determined based on the first data; the firmware of the charger end is updated based on the second data. Here, the charger end will obtain the first data of the charger end including the charging status information of the charger end during the charging process and send the first data to the terminal, and the second data can be received from the terminal. Since the second data includes the program data of the updated firmware determined based on the first data, after receiving the second data, the firmware program can be updated based on the second data. Compared with the method in which the firmware cannot be updated, the firmware of the charger end can be updated. On the one hand, when a fault occurs at the charger end, the firmware program can be updated in time, and on the other hand, the firmware program can be adapted to the charging status information. In this way, the charging process of the charger end will be more reliable, reducing the situation of safety hazards caused by charging failure and charging failure.

[0126] It should be noted that those skilled in the art can understand that the method provided in the embodiments of the present disclosure can be executed alone or together with some methods in the embodiments of the present disclosure or some methods in related technologies.

[0127] like Figure 2 As shown, an embodiment of the present disclosure provides a method for updating firmware, which is executed by a terminal and includes:

[0128] Step 21, receiving first data sent by the charger end, wherein the first data includes charging status information of the charger end during the charging process;

[0129] Step 22: Send the first data to the cloud;

[0130] Step 23: In response to the firmware on the cloud being different from the firmware on the charger, receiving second data from the cloud, wherein the second data includes program data for updating the firmware on the charger determined based on the first data;

[0131] Step 24: Send the second data to the charger end.

[0132] In one embodiment, first data sent by a charger end is received, the first data including charging status information of the charger end during charging. The first data is sent to a cloud. The firmware on the cloud and the firmware on the charger end are compared. In response to the firmware on the cloud being different from the firmware on the charger end, second data is received from the cloud, the second data including program data for updating the firmware on the charger end determined based on the first data. The second data is sent to the charger end.

[0133] In one embodiment, first data sent by a charger end is received, the first data including charging status information of the charger end during charging. The first data is sent to a cloud. Comparison information sent by the cloud is received, wherein the comparison information indicates a comparison result obtained by the cloud comparing the firmware on the cloud with the firmware on the charger end. In response to the firmware on the cloud being different from the firmware on the charger end, second data is received from the cloud, the second data including program data for updating the firmware on the charger end determined based on the first data. The second data is sent to the charger end.

[0134] In one embodiment, the charger end may be a charger with data processing and data transmission functions. After connecting the power supply end and the terminal, the charger end may charge the terminal, send data to the terminal, and receive data sent by the terminal.

[0135] In one embodiment, each of the charger terminals corresponds to a unique identifier for representing the charger terminal.

[0136] In one embodiment, the charger end is provided with a programmable memory, the programmable memory stores a firmware program, and the programmable memory can be repeatedly written and erased (for example, 1000 times). Here, the firmware program can be a control program related to controlling charging and / or communication of the charger end.

[0137] In one embodiment, the charger end is provided with a predetermined storage space (e.g., 32M). The predetermined storage space is used to store key data obtained during the operation of a fixed program, such as date, number of OTP occurrences, number of OCP occurrences, number of OVP occurrences, number of UVP occurrences, charger NTC temperature, number of overheating, charger output current, charger output voltage, charging efficiency, protocol used, and other data. It should be noted that the key data can be retained for a predetermined period of time (e.g., 1 month), and if the predetermined period is exceeded, the saved key data can be automatically deleted.

[0138] In one embodiment, the terminal may be various types of mobile devices or fixed devices. For example, the electronic device may be a mobile phone, a computer, a smart wearable terminal, a smart home terminal, an industrial sensor device and / or a medical device.

[0139] In one embodiment, the cloud may be a cloud server. The charger may perform data exchange with the cloud through the terminal.

[0140] In some embodiments, "first data" and "point-marking data" and "point-burying data" can be interchangeable in certain scenarios, and can all refer to data associated with the charging status obtained by monitoring the charger end.

[0141] In one embodiment, the charging status information includes at least one of the following:

[0142] The number of over-protection events, charging current, charging voltage, device temperature, charging efficiency, charging protocol used, charging power, working status of key devices, charging voltage requested by the terminal, and charging current requested by the terminal.

[0143] Here, the number of times the over-protection occurs may be the number of times the OTP occurs, the number of times the OCP occurs, the number of times the OVP occurs, and / or the number of times the UVP occurs.

[0144] In one embodiment, first data sent by a charger end is periodically received, the first data including charging status information of the charger end during charging. The first data is sent to a cloud. The firmware on the cloud and the firmware on the charger end are compared. In response to the firmware on the cloud being different from the firmware on the charger end, second data is received from the cloud, the second data including program data for updating the firmware on the charger end determined based on the first data. The second data is sent to the charger end.

[0145] In one embodiment, before comparing the firmware on the cloud and the firmware on the charger end, first firmware information of the firmware on the cloud is obtained from the cloud, and second firmware information of the firmware on the charger end is obtained from the charger end, wherein the first firmware information is used to indicate characteristics of the firmware on the cloud, and the second firmware information is used to indicate characteristics of the firmware on the charger end; the first firmware information and the second firmware information are compared; if the first firmware information and the second firmware information are the same, it is determined that the firmware on the cloud is the same as the firmware on the charger end; if the first firmware information and the second firmware information are different, it is determined that the firmware on the cloud is different from the firmware on the charger end.

[0146] In one embodiment, a request message for obtaining first data is sent to the charger end, the first data including charging status information of the charger end during charging; the first data sent by the charger end is received; the first data is sent to the cloud; the firmware on the cloud is compared with the firmware on the charger end; in response to the firmware on the cloud being different from the firmware on the charger end, second data is received from the cloud, the second data including program data for updating the firmware on the charger end determined based on the first data; and the second data is sent to the charger end.

[0147] In one embodiment, in response to being in a charging completion state, receiving first data sent by the charger end, the first data including charging state information of the charger end during the charging process. Sending the first data to the cloud. Comparing the firmware on the cloud with the firmware on the charger end. In response to the firmware on the cloud being different from the firmware on the charger end, receiving second data from the cloud, the second data including program data for updating the firmware on the charger end determined based on the first data. Sending the second data to the charger end.

[0148] In one embodiment, in response to being in a state of charging failure, first data sent by the charger end is received, the first data including charging status information of the charger end during charging. The first data is sent to the cloud. The firmware of the cloud and the firmware of the charger end are compared. In response to the firmware of the cloud and the firmware of the charger end being different, second data is received from the cloud, the second data including program data for updating the firmware of the charger end determined based on the first data. The second data is sent to the charger end.

[0149] In one embodiment, first data sent by a charger end is received, the first data including charging status information of the charger end during charging. The first data is sent to a cloud. In response to being in a charging fault state, the firmware on the cloud and the firmware on the charger end are compared. In response to the firmware on the cloud being different from the firmware on the charger end, second data is received from the cloud, the second data including program data for updating the firmware on the charger end determined based on the first data. The second data is sent to the charger end.

[0150] In one embodiment, first data sent by a charger end is received, the first data including charging status information of the charger end during charging. Request information for requesting the first data is received from a cloud. In response to receiving the request information, the first data is sent to the cloud. The firmware of the cloud and the firmware of the charger end are compared. In response to the firmware of the cloud and the firmware of the charger end being different, second data is received from the cloud, the second data including program data for updating the firmware of the charger end determined based on the first data. The second data is sent to the charger end.

[0151] In one embodiment, receiving the second data from the cloud may be by starting a download program to download the second data.

[0152] In one embodiment, first data sent by a charger end is received, the first data including charging status information of the charger end during charging. In response to the state indicated by the charging status information being a first state, the first data is sent to the cloud; wherein the first state is determined based on the number of over-protection events that occur at the terminal. The firmware on the cloud and the firmware on the charger end are compared. In response to the firmware on the cloud being different from the firmware on the charger end, second data is received from the cloud, the second data including program data for updating the firmware on the charger end determined based on the first data. The second data is sent to the charger end.

[0153] In one embodiment, the over-protection event may be an event of OTP occurrence, OCP occurrence, OVP occurrence, and / or UVP occurrence.

[0154] In one embodiment, first data sent by a charger end is received, the first data including charging status information of the charger end during the charging process. The first data is sent to the cloud. The firmware on the cloud and the firmware on the charger end are compared. In response to the firmware on the cloud being different from the firmware on the charger end, second data is received from the cloud, the second data including program data for updating the firmware on the charger end determined based on the first data. In response to the terminal being in a charging completion state, the second data is sent to the charger end. In this way, the interference of the sending data to the charging process can be reduced.

[0155] In one embodiment, first data sent by a charger end is received, the first data including charging status information of the charger end during the charging process. The first data is sent to the cloud. The firmware on the cloud and the firmware on the charger end are compared. In response to the firmware on the cloud being different from the firmware on the charger end, second data is received from the cloud, the second data including program data for updating the firmware on the charger end determined based on the first data. In response to detecting a first operation instruction from a user, the charging process is paused, and the second data is sent to the charger end. In this way, the second data can be sent to the charger end according to the needs of the user. Here, the first operation instruction can be an instruction input by the user through the input control of the display interface of the terminal.

[0156] In one embodiment, first data sent by a charger end is received, the first data including charging status information of the charger end during the charging process. The first data is sent to a cloud. The firmware on the cloud and the firmware on the charger end are compared. In response to the firmware on the cloud being different from the firmware on the charger end, second data is received from the cloud, the second data including program data for updating the firmware on the charger end determined based on the first data. In response to receiving a request message sent by the charger end for obtaining the second data, the charging process is suspended, and the second data is sent to the charger end.

[0157] It should be noted that after the second data is sent, the charging process will be restarted.

[0158] In one embodiment, first data sent by a charger end is received, the first data including charging status information of the charger end during charging. The first data is sent to a cloud. In response to the firmware on the cloud being different from the firmware on the charger end, second data is received from the cloud, the second data including program data for updating the firmware on the charger end determined based on the first data. The second data is sent to the charger end. Update information sent by the charger end is received; wherein the update information indicates the progress of the program data of the firmware on the charger end being updated by the terminal.

[0159] It should be noted that those skilled in the art can understand that the method provided in the embodiments of the present disclosure can be executed alone or together with some methods in the embodiments of the present disclosure or some methods in related technologies.

[0160] like Figure 3 As shown, an embodiment of the present disclosure provides a firmware update method, which is executed by the cloud and includes:

[0161] Step 31, receiving first data sent by a terminal, wherein the first data includes charging status information of the charger during the charging process;

[0162] Step 32: Acquire second data, where the second data includes program data of the updated firmware determined based on the first data;

[0163] Step 33: Send the second data to the terminal.

[0164] In one embodiment, the charger end may be a charger with data processing and data transmission functions. After connecting the power supply end and the terminal, the charger end may charge the terminal, send data to the terminal, and receive data sent by the terminal.

[0165] In one embodiment, each of the charger terminals corresponds to a unique identifier for representing the charger terminal.

[0166] In one embodiment, the charger end is provided with a programmable memory, the programmable memory stores a firmware program, and the programmable memory can be repeatedly written and erased (for example, 1000 times). Here, the firmware program can be a control program related to controlling charging and / or communication of the charger end.

[0167] In one embodiment, the charger end is provided with a predetermined storage space (e.g., 32M). The predetermined storage space is used to store key data obtained during the operation of a fixed program, such as date, number of OTP occurrences, number of OCP occurrences, number of OVP occurrences, number of UVP occurrences, charger NTC temperature, number of overheating, charger output current, charger output voltage, charging efficiency, protocol used, and other data. It should be noted that the key data can be retained for a predetermined period of time (e.g., 1 month), and if the predetermined period is exceeded, the saved key data can be automatically deleted.

[0168] In one embodiment, the terminal may be various types of mobile devices or fixed devices. For example, the electronic device may be a mobile phone, a computer, a smart wearable terminal, a smart home terminal, an industrial sensor device and / or a medical device.

[0169] In one embodiment, the cloud may be a cloud server. The charger may perform data exchange with the cloud through the terminal.

[0170] In some embodiments, "first data" and "point-marking data" and "point-burying data" can be interchangeable in certain scenarios, and can all refer to data associated with the charging status obtained by monitoring the charger end.

[0171] In one embodiment, the charging status information includes at least one of the following:

[0172] The number of over-protection events, charging current, charging voltage, device temperature, charging efficiency, charging protocol used, charging power, working status of key devices, charging voltage requested by the terminal, and charging current requested by the terminal.

[0173] Here, the number of times the over-protection occurs may be the number of times the OTP occurs, the number of times the OCP occurs, the number of times the OVP occurs, and / or the number of times the UVP occurs.

[0174] In one embodiment, the firmware of different charger models is different.

[0175] In one embodiment, the cloud may store data of firmware of different chargers.

[0176] In one embodiment, the second data includes program data for updating the firmware of the charger end determined by the user based on the first data. Alternatively, the second data includes program data for updating the firmware of the charger end determined by the cloud based on the first data.

[0177] In one embodiment, first data sent by a terminal is received, the first data including charging status information of the charger terminal during charging, second data is determined based on the first data, the second data including program data for updating firmware of the charger terminal determined based on the first data, and the second data is sent to the terminal.

[0178] In one embodiment, a request message for obtaining first data is sent to a terminal, wherein the first data includes charging status information of the charger terminal during charging. In response to receiving the request message, the first data sent by the terminal is received. Second data is obtained, wherein the second data includes program data for updating the firmware of the charger terminal determined based on the first data. The second data is sent to the terminal.

[0179] In one embodiment, first data sent by a terminal is received, the first data including charging status information of the charger terminal during charging. Second data is acquired, the second data including program data for updating firmware of the charger terminal determined based on the first data. Request information for acquiring the second data is received from the terminal. In response to acquiring the request information, the second data is sent to the terminal.

[0180] In one embodiment, the cloud may send comparison information to the terminal, wherein the comparison information indicates a comparison result obtained by the cloud by comparing the firmware on the cloud with the firmware on the charger.

[0181] It should be noted that those skilled in the art can understand that the method provided in the embodiments of the present disclosure can be executed alone or together with some methods in the embodiments of the present disclosure or some methods in related technologies.

[0182] See also Figure 4 The present disclosure provides a firmware update method, which is executed by a firmware update system. The firmware update system includes a charger, a cloud, and a terminal. The terminal may be, but is not limited to, a mobile phone, a computer, a tablet, and the like. The method includes:

[0183] Step 41: The charger sends the first data to the terminal, where the first data includes charging status information of the charger during the charging process;

[0184] Step 42: The terminal sends the first data to the cloud;

[0185] Step 43: The cloud obtains second data, where the second data includes program data for updating the firmware of the charger end determined based on the first data;

[0186] Step 44: The cloud sends the second data to the terminal;

[0187] Step 45: The terminal updates the firmware of the charger based on the second data.

[0188] It should be noted that those skilled in the art can understand that the method provided in the embodiments of the present disclosure can be executed alone or together with some methods in the embodiments of the present disclosure or some methods in related technologies.

[0189] In order to better understand the embodiments of the present disclosure, the technical solution of the present disclosure is further described below through two exemplary embodiments:

[0190] Example 1:

[0191] See also Figure 5 The firmware update system may include a remote cloud and a local user end, and the local user end may include: a mobile phone end and a charger.

[0192] Among them, the mobile phone and the charger can realize the transmission of firmware and dot data (corresponding to the first data). The cloud and the mobile phone can realize the mobile phone pulling firmware (corresponding to the second data) from the cloud, and the mobile phone can upload data to the cloud.

[0193] Example 2:

[0194] See also Figure 6The present disclosure provides a method for updating firmware, the method comprising:

[0195] Step 61: When the user is charging or in response to plugging in a charger, the user actively clicks a button on the mobile phone user interface to monitor the charger end and trigger a firmware upgrade process of the charger. Meanwhile, during the charging process of the mobile phone, the charger will record historical charging data (corresponding to the first data in the present disclosure);

[0196] Step 62: The mobile phone detects the charger model, compares the charger firmware with the cloud firmware, and receives the historical charging management data uploaded and saved by the charger. When the mobile phone analyzes the charger historical management data, at least one of the following three situations occurs:

[0197] Case 1: The charger has experienced OTP overheat protection events for more than 3 days in the past 2 weeks;

[0198] Case 2: The charger has experienced over-temperature warning events for more than 7 days in the past 2 weeks;

[0199] Case 3: The charger has experienced OCP overcurrent protection events for more than 3 days in the past 2 weeks;

[0200] The mobile phone uploads historical charging management data to the cloud, downloads the latest firmware and pushes it to the charger;

[0201] Step 63: The charger receives the firmware and upgrades it. At the same time, the cloud receives the ID charger's dot data uploaded by the mobile phone and stores the data for the manufacturer to analyze and optimize the product. At the same time, the hardware status of the ID charger can also be monitored;

[0202] Step 64: Repeat the process from step 61 to step 63 to achieve the functions of uploading dot data and updating firmware.

[0203] It should be noted that the time for firmware upgrade is not limited to the time of full charge and the time of user clicking. According to different control logics, the upgrade can be triggered during charging, before charging, etc. The dot data can also be stored in the mobile phone at the same time and displayed in the mobile phone. After being processed by the mobile phone, the full or partial status of the charger can be displayed to the user.

[0204] It should be noted that those skilled in the art can understand that the method provided in the embodiments of the present disclosure can be executed alone or together with some methods in the embodiments of the present disclosure or some methods in related technologies.

[0205] Figure 7 An exemplary embodiment is provided to show a firmware update device, the device comprising:

[0206] A first sending module 71 is configured to send first data to a terminal, wherein the first data includes charging status information of the charger during the charging process;

[0207] A first receiving module 72 is configured to receive second data sent by the terminal, wherein the second data includes program data for updating the firmware of the charger terminal determined based on the first data;

[0208] The first updating module 73 is configured to update the firmware of the charger end based on the second data.

[0209] In one embodiment, the first sending module 71 is further configured to: the charging status information includes at least one of the following:

[0210] The number of over-protection events, charging current, charging voltage, device temperature, charging efficiency, charging protocol used, charging power, working status of key devices, charging voltage requested by the terminal, and charging current requested by the terminal.

[0211] In one embodiment, the apparatus further comprises:

[0212] A storage module 74, configured to store the first data;

[0213] The deleting module 75 is configured to delete the first stored data after a first time.

[0214] In one embodiment, the first sending module 71 is further configured to:

[0215] In response to being in a charging completion state, sending the first data to the terminal.

[0216] In one embodiment, the first sending module 71 is further configured to:

[0217] Sending update information to the terminal;

[0218] The update information indicates the progress of the terminal updating the program data of the firmware of the charger end.

[0219] It should be noted that those skilled in the art can understand that the method provided in the embodiments of the present disclosure can be executed alone or together with some methods in the embodiments of the present disclosure or some methods in related technologies.

[0220] Figure 8 An exemplary embodiment is provided to show a firmware update device, the device comprising:

[0221] The second receiving module 81 is configured to receive first data sent by the charger end, wherein the first data includes charging state information of the charger end during the charging process;

[0222] A second sending module 82, configured to send the first data to the cloud;

[0223] The second receiving module 81 is further configured to: in response to the firmware of the cloud being different from the firmware of the charger end, receive second data from the cloud, wherein the second data includes program data for updating the firmware of the charger end determined based on the first data;

[0224] The second sending module 82 is further configured to send the second data to the charger end.

[0225] In one embodiment, the second sending module 82 is further configured to:

[0226] In response to the state indicated by the charging state information being a first state, sending the first data to the cloud;

[0227] The first state is determined based on the number of over-protection events that occur at the terminal.

[0228] In one embodiment, the second sending module 82 is further configured to:

[0229] In response to the terminal being in a charging completion state, sending the second data to the charger end;

[0230] and / or,

[0231] In response to detecting a first operation instruction from a user, the second data is sent to the charger end.

[0232] In one embodiment, the second receiving module 81 is further configured to:

[0233] Receiving update information sent by the charger end;

[0234] The update information indicates the progress of the terminal updating the program data of the firmware of the charger end.

[0235] It should be noted that those skilled in the art can understand that the method provided in the embodiments of the present disclosure can be executed alone or together with some methods in the embodiments of the present disclosure or some methods in related technologies.

[0236] Fig. 9 An exemplary embodiment is provided to show a firmware update device, the device comprising:

[0237] A third receiving module 91 is configured to receive first data sent by the terminal, wherein the first data includes charging status information of the charger during the charging process;

[0238] A second acquisition module 92 is configured to acquire second data, wherein the second data includes program data for updating the firmware of the charger terminal determined based on the first data;

[0239] The third sending module 93 is configured to send the second data to the terminal.

[0240] It should be noted that those skilled in the art can understand that the method provided in the embodiments of the present disclosure can be executed alone or together with some methods in the embodiments of the present disclosure or some methods in related technologies.

[0241] An embodiment of the present disclosure provides a firmware update system, which includes a charger end, a terminal and a cloud; wherein the charger end is used to execute any method executed by the charger end described in the present disclosure, the terminal is used to execute any method executed by the terminal, and the cloud is used to execute the method executed by the cloud.

[0242] An embodiment of the present disclosure further provides a computer-readable storage medium, wherein the computer-readable storage medium stores an executable program, wherein when the executable program is executed by a processor, the method described in any embodiment of the present disclosure is implemented.

[0243] Regarding the device in the above embodiment, the specific manner in which each module performs operations has been described in detail in the embodiment of the method, and will not be elaborated here.

[0244] An embodiment of the present disclosure further provides an electronic device, including:

[0245] processor;

[0246] a memory for storing processor-executable instructions;

[0247] The processor is configured to implement the method described in any embodiment of the present disclosure when running the executable instructions.

[0248] The memory may include various types of storage media, which are non-transitory computer storage media that can continue to memorize information stored thereon after the communication device loses power.

[0249] The processor may be connected to the memory via a bus or the like, and is used to read the executable program stored in the memory.

[0250] Fig.101 is a block diagram of an electronic device 600 according to an exemplary embodiment, and the electronic device 600 can execute the method disclosed in any embodiment of the present disclosure. For example, the electronic device 600 can be a mobile phone, a computer, a digital broadcast terminal, a messaging device, a game console, a tablet device, a medical device, a fitness device, a personal digital assistant, etc.

[0251] Reference Fig.10 , the electronic device 600 may include one or more of the following components: a processing component 602 , a memory 604 , a power component 606 , a multimedia component 608 , an audio component 610 , an input / output (I / O) interface 612 , a sensor component 614 , and a communication component 616 .

[0252] The processing component 602 generally controls the overall operation of the electronic device 600, such as operations associated with display, phone calls, data communications, camera operations, and recording operations. The processing component 602 may include one or more processors 820 to execute instructions to complete all or part of the steps of the above-mentioned method. In addition, the processing component 602 may include one or more modules to facilitate the interaction between the processing component 602 and other components. For example, the processing component 602 may include a multimedia module to facilitate the interaction between the multimedia component 608 and the processing component 602.

[0253] The memory 604 is configured to store various types of data to support operations on the device 600. Examples of such data include instructions for any application or method operating on the electronic device 600, contact data, phone book data, messages, pictures, videos, etc. The memory 604 can be implemented by any type of volatile or non-volatile storage device or a combination thereof, such as static random access memory (SRAM), electrically erasable programmable read-only memory (EEPROM), erasable programmable read-only memory (EPROM), programmable read-only memory (PROM), read-only memory (ROM), magnetic memory, flash memory, magnetic disk or optical disk.

[0254] The power supply component 606 provides power to the various components of the electronic device 600. The power supply component 606 may include a power management system, one or more power supplies, and other components associated with generating, managing, and distributing power to the electronic device 600.

[0255] The multimedia component 608 includes a screen that provides an output interface between the electronic device 600 and the user. In some embodiments, the screen may include a liquid crystal display (LCD) and a touch panel (TP). If the screen includes a touch panel, the screen may be implemented as a touch screen to receive input signals from the user. The touch panel includes one or more touch sensors to sense touch, slide, and gestures on the touch panel. The touch sensor may not only sense the boundaries of the touch or slide action, but also detect the duration and pressure associated with the touch or slide operation. In some embodiments, the multimedia component 608 includes a front camera and / or a rear camera. When the device 600 is in an operating mode, such as a shooting mode or a video mode, the front camera and / or the rear camera may receive external multimedia data. Each front camera and the rear camera may be a fixed optical lens system or have a focal length and optical zoom capability.

[0256] The audio component 610 is configured to output and / or input audio signals. For example, the audio component 610 includes a microphone (MIC), and when the electronic device 600 is in an operating mode, such as a call mode, a recording mode, and a voice recognition mode, the microphone is configured to receive an external audio signal. The received audio signal can be further stored in the memory 604 or sent via the communication component 616. In some embodiments, the audio component 610 also includes a speaker for outputting audio signals.

[0257] I / O interface 612 provides an interface between processing component 602 and peripheral interface modules, such as keyboards, click wheels, buttons, etc. These buttons may include but are not limited to: a home button, a volume button, a start button, and a lock button.

[0258] The sensor assembly 614 includes one or more sensors for providing various aspects of status assessment for the electronic device 600. For example, the sensor assembly 614 can detect the open / closed state of the device 600, the relative positioning of components, such as the display and keypad of the electronic device 600, and the sensor assembly 614 can also detect the position change of the electronic device 600 or a component of the electronic device 600, the presence or absence of contact between the user and the electronic device 600, the orientation or acceleration / deceleration of the electronic device 600, and the temperature change of the electronic device 600. The sensor assembly 614 may include a proximity sensor configured to detect the presence of nearby objects without any physical contact. The sensor assembly 614 may also include an optical sensor, such as a CMOS or CCD image sensor, for use in imaging applications. In some embodiments, the sensor assembly 614 may also include an acceleration sensor, a gyroscope sensor, a magnetic sensor, a pressure sensor, or a temperature sensor.

[0259] The communication component 616 is configured to facilitate wired or wireless communication between the electronic device 600 and other devices. The electronic device 600 can access a wireless network based on a communication standard, such as WiFi, 2G or 3G, or a combination thereof. In an exemplary embodiment, the communication component 616 receives a broadcast signal or broadcast-related information from an external broadcast management system via a broadcast channel. In an exemplary embodiment, the communication component 616 also includes a near field communication (NFC) module to facilitate short-range communication. For example, the NFC module can be implemented based on radio frequency identification (RFID) technology, infrared data association (IrDA) technology, ultra-wideband (UWB) technology, Bluetooth (BT) technology and other technologies.

[0260] In an exemplary embodiment, the electronic device 600 may be implemented by one or more application-specific integrated circuits (ASICs), digital signal processors (DSPs), digital signal processing devices (DSPDs), programmable logic devices (PLDs), field programmable gate arrays (FPGAs), controllers, microcontrollers, microprocessors, or other electronic components to perform the above methods.

[0261] In an exemplary embodiment, a non-transitory computer-readable storage medium including instructions is also provided, such as a memory 604 including instructions, and the instructions can be executed by the processor 820 of the electronic device 600 to perform the above method. For example, the non-transitory computer-readable storage medium can be a ROM, a random access memory (RAM), a CD-ROM, a magnetic tape, a floppy disk, an optical data storage device, etc.

[0262] Those skilled in the art will readily appreciate other embodiments of the present invention after considering the specification and practicing the invention disclosed herein. This application is intended to cover any variations, uses or adaptations of the present invention that follow the general principles of the present invention and include common knowledge or customary techniques in the art that are not disclosed in this disclosure. The specification and examples are to be considered exemplary only, and the true scope and spirit of the present invention are indicated by the following claims.

[0263] It should be understood that the present invention is not limited to the exact construction that has been described above and shown in the drawings and that various modifications and changes may be made without departing from the scope thereof. The scope of the present invention is limited only by the appended claims.

Claims

1. A firmware update method, characterized in that: The method is performed by a charger end, and the method includes: Sending first data to a terminal, wherein the first data includes charging status information of the charger during the charging process; receiving second data sent by the terminal, wherein the second data includes program data for updating the firmware of the charger end determined based on the first data; The firmware of the charger terminal is updated based on the second data.

2. The method according to claim 1, characterized in that The charging status information includes at least one of the following: The number of over-protection events, charging current, charging voltage, device temperature, charging efficiency, charging protocol used, charging power, working status of key devices, charging voltage requested by the terminal, and charging current requested by the terminal.

3. The method according to claim 1, characterized in that The method further comprises: storing the first data; The first stored data is deleted after a first time.

4. The method according to claim 1, characterized in that: The sending the first data to the terminal includes: In response to being in a charging completion state, sending the first data to the terminal.

5. The method according to claim 1, characterized in that The method further comprises: Sending update information to the terminal; The update information indicates the progress of the terminal updating the program data of the firmware of the charger end.

6. A firmware update method, characterized in that: The method is executed by a terminal, and includes: receiving first data sent by a charger end, wherein the first data includes charging status information of the charger end during a charging process; Sending the first data to the cloud; In response to the firmware on the cloud being different from the firmware on the charger, receiving second data from the cloud, the second data including program data for updating the firmware on the charger determined based on the first data; The second data is sent to the charger end.

7. The method according to claim 6, characterized in that The sending the first data to the cloud includes: In response to the state indicated by the charging state information being a first state, sending the first data to the cloud; The first state is determined based on the number of over-protection events that occur at the terminal.

8. The method according to claim 6, characterized in that The sending the second data to the charger end includes: In response to the terminal being in a charging completion state, sending the second data to the charger end; and / or, In response to detecting a first operation instruction from a user, the second data is sent to the charger end.

9. The method according to claim 6, characterized in that The method further comprises: Receiving update information sent by the charger end; The update information indicates the progress of the terminal updating the program data of the firmware of the charger end.

10. A firmware update method, characterized in that: The method is executed by the cloud, and the method includes: receiving first data sent by a terminal, wherein the first data includes charging status information of the charger terminal during the charging process; acquiring second data, wherein the second data includes program data for updating firmware of the charger terminal determined based on the first data; The second data is sent to the terminal.

11. A firmware update device, characterized in that: The device comprises: A first sending module is configured to send first data to a terminal, wherein the first data includes charging status information of the charger terminal during the charging process; a first receiving module configured to receive second data sent by the terminal, wherein the second data includes program data for updating the firmware of the charger terminal determined based on the first data; The first update module is configured to update the firmware of the charger end based on the second data.

12. A firmware update device, characterized in that: The device comprises: A second receiving module is configured to receive first data sent by the charger end, wherein the first data includes charging state information of the charger end during the charging process; A second sending module is configured to send the first data to the cloud; The second receiving module is further configured to: in response to the firmware of the cloud being different from the firmware of the charger end, receive second data from the cloud, wherein the second data includes program data for updating the firmware of the charger end determined based on the first data; The second sending module is further configured to: send the second data to the charger end.

13. A firmware update device, characterized in that: The device comprises: A third receiving module is configured to receive first data sent by the terminal, wherein the first data includes charging status information of the charger during the charging process; A second acquisition module is configured to acquire second data, wherein the second data includes program data for updating the firmware of the charger terminal determined based on the first data; The third sending module is configured to send the second data to the terminal.

14. A firmware update system, characterized in that: The firmware update system includes a charger end, a terminal and a cloud; wherein the charger end is used to execute the method executed by the charger end as described in any one of claims 1 to 5, the terminal is used to execute the method executed by the terminal as described in any one of claims 6 to 9, and the cloud is used to execute the method executed by the cloud as described in claim 10.

15. An electronic device, wherein: include: Memory; The processor is connected to the memory and is configured to execute computer executable instructions stored on the memory and can implement the method provided in any one of claims 1 to 5, 6 to 9 or 10.

16. A computer storage medium storing computer executable instructions, wherein the computer executable instructions can implement the method provided in any one of claims 1 to 5, 6 to 9 or 10 after being executed by a processor.

Images