CN113672256A - Processing method and server of executable file, software upgrading method and client - Google Patents
Processing method and server of executable file, software upgrading method and client Download PDFInfo
- Publication number
- CN113672256A CN113672256A CN202110886692.4A CN202110886692A CN113672256A CN 113672256 A CN113672256 A CN 113672256A CN 202110886692 A CN202110886692 A CN 202110886692A CN 113672256 A CN113672256 A CN 113672256A
- Authority
- CN
- China
- Prior art keywords
- file
- upgrade
- software
- client
- upgrading
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
- 238000000034 method Methods 0.000 title claims abstract description 59
- 238000003672 processing method Methods 0.000 title abstract description 13
- 238000012545 processing Methods 0.000 claims description 16
- 238000012423 maintenance Methods 0.000 abstract description 11
- 238000010586 diagram Methods 0.000 description 14
- 230000008901 benefit Effects 0.000 description 7
- 230000008569 process Effects 0.000 description 5
- 230000015572 biosynthetic process Effects 0.000 description 3
- 238000004146 energy storage Methods 0.000 description 3
- 230000006870 function Effects 0.000 description 3
- 230000003993 interaction Effects 0.000 description 3
- 238000003786 synthesis reaction Methods 0.000 description 3
- 230000009286 beneficial effect Effects 0.000 description 2
- 238000006243 chemical reaction Methods 0.000 description 2
- 239000002131 composite material Substances 0.000 description 2
- 238000007599 discharging Methods 0.000 description 2
- 238000005516 engineering process Methods 0.000 description 2
- 238000012986 modification Methods 0.000 description 2
- 230000004048 modification Effects 0.000 description 2
- 238000004891 communication Methods 0.000 description 1
- 238000004590 computer program Methods 0.000 description 1
- 230000000694 effects Effects 0.000 description 1
- 230000008676 import Effects 0.000 description 1
- 238000004519 manufacturing process Methods 0.000 description 1
- 230000003446 memory effect Effects 0.000 description 1
- 238000010295 mobile communication Methods 0.000 description 1
- 230000003287 optical effect Effects 0.000 description 1
- 239000007787 solid Substances 0.000 description 1
- 238000006467 substitution reaction Methods 0.000 description 1
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/60—Software deployment
- G06F8/65—Updates
Abstract
The embodiment of the application relates to a processing method and a server side of an executable file, a software upgrading method and a client side, wherein the processing method of the executable file comprises the following steps: receiving an executable file of the BMS software; obtaining an upgrade file according to a file header of the executable file and a fool-proof information code, wherein the fool-proof information code comprises a software upgrade validity period; and sending the upgrade file to a client, wherein the client is used for determining whether to carry out upgrade operation according to the software upgrade validity period after receiving the upgrade file. The embodiment of the application can realize management and control on the BMS software upgrading of the client, avoids the situation that the version is returned disorderly and the BMS software of the client cannot work normally due to the fact that the version exceeds the valid period and is easy to cause due to direct upgrading of the client, and accordingly effectively reduces the after-sale maintenance cost of the client.
Description
Technical Field
The present application relates to the field of battery technologies, and in particular, to a method and a server for processing an executable file, a method for upgrading software, and a client.
Background
At present, a BATTERY pack is widely applied to the fields of new energy vehicles and energy storage, and a BMS (BATTERY management system) system of the BATTERY pack monitors and controls charging and discharging of a BATTERY in real time. In the battery pack production and assembly process, program flashing needs to be carried out on BMS system software of the battery pack, and after a supplier carries out version updating on the BMS system software, the client can also upgrade the BMS system software.
Disclosure of Invention
In the process of implementing the embodiment of the present application, the inventors of the present application find that: at present, when BMS software of a battery management system of a client is upgraded, a server cannot control the version of an upgrade file used by the client, and the BMS software cannot normally work after the version of the BMS software is disordered and the version of the BMS software is returned.
The technical problem mainly solved by the embodiments of the present application is to provide a processing method of an executable file, a service end, a software upgrading method and a client, where the processing method of the executable file can manage and control the upgrade of BMS software of the client, and avoid the situation that the version rollback is disordered and the BMS software of the client cannot normally work due to the fact that the version exceeds the validity period easily caused by the direct upgrade of the client, thereby effectively reducing the after-sale maintenance cost of the client.
In order to solve the above technical problem, in a first aspect, an embodiment of the present application provides a method for processing an executable file, where the method includes: receiving an executable file of the BMS software; obtaining an upgrade file according to a file header of the executable file and a fool-proof information code, wherein the fool-proof information code comprises a software upgrade validity period; and sending the upgrade file to a client. And the client is used for determining whether to carry out upgrading operation according to the software upgrading validity period after receiving the upgrading file.
In some embodiments, the obtaining an upgrade file according to the header and the fool-proof information code of the executable file includes: outputting a fool-proof code setting interface; receiving a setting operation aiming at the fool-proof code setting interface to obtain a fool-proof information code; and obtaining an upgrade file according to the fool-proof information code and the file header of the executable file.
In some embodiments, the fool-proof setting interface comprises a validity period setting interface, the method further comprising: outputting a validity period setting interface; and receiving the setting operation aiming at the valid period setting interface to obtain the software upgrading valid period.
In some embodiments, the fool-proof code setting interface further includes one or more of company name information, project information, schema information, hardware version information.
In order to solve the foregoing technical problem, in a second aspect, an embodiment of the present application provides a software upgrading method, where the method includes: receiving an upgrade file with a fool-proof information code, wherein the fool-proof information code comprises a software upgrade validity period; when software is upgraded, comparing the time information of the software upgrading validity period with the real-time clock information of the client to obtain a comparison result; and judging whether the upgrade file executes the upgrade operation or not according to the comparison result.
In some embodiments, the determining, according to the comparison result, whether the upgrade file performs an upgrade operation includes: if the comparison result is that the time information of the software upgrading validity period is larger than the real-time clock information of the client, executing upgrading operation according to the upgrading file; and if the comparison result is that the time information of the software upgrading validity period is not less than the real-time clock information of the client, stopping executing upgrading operation according to the upgrading file.
In some embodiments, after the stopping of the execution of the upgrade operation according to the upgrade file, the method further comprises: when the execution of the upgrading operation is stopped, generating feedback information of upgrading failure; and reporting the feedback information to a server.
In order to solve the foregoing technical problem, in a third aspect, an embodiment of the present application provides an apparatus for processing an executable file, where the apparatus includes: the executable file receiving module is used for receiving the executable file of the BMS software; the upgrading file obtaining module is used for obtaining an upgrading file according to a file header of the executable file and a fool-proof information code, wherein the fool-proof information code comprises a software upgrading validity period; and the sending module is used for sending the upgrade file to a client, wherein the client determines whether to perform upgrade operation according to the software upgrade validity period after receiving the upgrade file.
In order to solve the foregoing technical problem, in a fourth aspect, an embodiment of the present application provides a software upgrading apparatus, where the apparatus includes: the system comprises an upgrade file receiving module, a software upgrading module and a software upgrading module, wherein the upgrade file receiving module is used for receiving an upgrade file with a foolproof information code, and the foolproof information code comprises a software upgrading validity period; the comparison module is used for comparing the time information of the software upgrading validity period with the real-time clock information of the client to obtain a comparison result when software upgrading is carried out; and the judging module is used for judging whether the upgrading file executes upgrading operation or not according to the comparison result.
In order to solve the foregoing technical problem, in a fifth aspect, an embodiment of the present application provides a server, where the server includes: at least one first processor, and a first memory communicatively coupled to the first processor, the first memory storing instructions executable by the at least one first processor to enable the at least one processor to perform the method of any of the first aspects.
In order to solve the foregoing technical problem, in a sixth aspect, an embodiment of the present application provides a client, where the client includes: at least one second processor, and a second memory communicatively coupled to the second processor, the second memory storing instructions executable by the at least one second processor to enable the at least one second processor to perform the method of any of the second aspects.
In order to solve the above technical problem, in a seventh aspect, an embodiment of the present application provides a non-transitory computer-readable storage medium, which stores computer-executable instructions, and when the computer-executable instructions are executed by a server or a client, the server is caused to perform the method according to the first aspect, or the client is caused to perform the method according to the second aspect.
Benefits of one or more embodiments of the present application include: different from the situation of the prior art, in the method for processing the executable file provided in one or more embodiments of the present application, the server receives the executable file of the BMS software, then obtains the upgrade file according to the file header of the executable file and the fool-proof information code, where the fool-proof information code includes a software upgrade validity period, sends the upgrade file to the client, and the client determines whether to perform an upgrade operation according to the software upgrade validity period after receiving the upgrade file. The BMS software upgrading of the client is managed and controlled through the set software upgrading validity period, the situation that version backspacing is disordered and BMS software of the client cannot work normally due to the fact that the version exceeds the validity period easily caused by direct upgrading of the client is avoided, and therefore after-sale maintenance cost of the client is effectively reduced.
According to the software upgrading method provided by one or more embodiments of the application, the upgrading file received by the client side is provided with the fool-proof information code, the fool-proof information code comprises the software upgrading validity period, when the client side carries out software upgrading, time information of the software upgrading validity period and real-time clock information of the client side are compared firstly, a comparison result is obtained, whether upgrading operation is executed on the upgrading file is judged according to the comparison result, and therefore version confusion caused by direct upgrading is avoided when upgrading fails, the risk that BMS software cannot be used continuously due to version rollback is reduced, after-sale maintenance cost of a supplier on the client side is reduced, and better economic benefits are brought to enterprises.
Drawings
One or more embodiments are illustrated by way of example in the accompanying drawings which correspond to figures in the drawings and not by way of limitation, in which elements having the same reference numeral designations represent like elements and the figures are not to scale unless otherwise specified.
FIG. 1 is a schematic diagram of a scenario in which a server interacts with a client according to the present application; (ii) a
FIG. 2 is a schematic flow chart illustrating interaction between a server and a client according to the present application;
FIG. 3 is a schematic flow chart diagram illustrating one embodiment of a method for processing an executable file of the present application;
FIG. 4 is a schematic diagram of a fool-proof code setup interface of an embodiment of a method of processing an executable file of the present application;
FIG. 5 is a diagram of a fool-proof information code according to an embodiment of the executable file processing method of the present application;
FIG. 6 is a schematic diagram of an upgrade file for one embodiment of a method for processing an executable file of the present application;
FIG. 7 is a schematic flow chart diagram illustrating one embodiment of a software upgrade method of the present application;
FIG. 8 is a schematic diagram of a client feedback interface according to an embodiment of the software upgrade method of the present application;
FIG. 9 is a block diagram of an embodiment of an executable file processing apparatus;
FIG. 10 is a schematic block diagram of an embodiment of a software upgrade apparatus of the present application;
FIG. 11 is a diagram illustrating a hardware configuration of a first controller in an embodiment of a server of the present application;
fig. 12 is a schematic hardware configuration diagram of a second controller in an embodiment of the client.
Detailed Description
The present application is described in detail below with reference to specific examples, which will assist those skilled in the art in further understanding the present application, but are not intended to limit the present application in any way. It should be noted that various changes and modifications can be made by one skilled in the art without departing from the spirit of the application. All falling within the scope of protection of the present application.
In order to make the objects, technical solutions and advantages of the present application more apparent, the present application is described in further detail below with reference to the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are merely illustrative of the present application and are not intended to limit the present application.
It should be noted that, if not conflicted, the various features of the embodiments of the present application may be combined with each other within the scope of protection of the present application. Additionally, while functional block divisions are performed in apparatus schematics, with logical sequences shown in flowcharts, in some cases, steps shown or described may be performed in sequences other than block divisions in apparatus or flowcharts. Further, the terms "first," "second," "third," and the like, as used herein, do not limit the data and the execution order, but merely distinguish the same items or similar items having substantially the same function and effect.
Unless defined otherwise, all technical and scientific terms used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this application belongs. The terminology used in the description of the present application is for the purpose of describing particular embodiments only and is not intended to be limiting of the present application. As used in this specification, the term "and/or" includes any and all combinations of one or more of the associated listed items.
In addition, the technical features mentioned in the embodiments of the present application described below may be combined with each other as long as they do not conflict with each other.
In recent years, more and more electronic devices such as portable computers, digital cameras, mobile phones, portable audio devices, bluetooth devices, or large industrial modules employ a battery pack as a main power source, and the battery pack has the advantages of small size, high energy density, no memory effect, long cycle life, high-voltage battery, low self-discharge rate, and the like.
The battery pack includes a battery module and a battery management system BMS.
As shown in fig. 1, fig. 1 is a scene schematic diagram of interaction between a server and a client, a synthesis upper computer is installed in the server, synthesis of a foolproof information code including a software upgrading validity period is performed on an executable file of BMS software, the client installs the BMS software after installing a battery pack, and when version upgrading of the BMS software is required, the executable file of the BMS software sent by the server is received to perform upgrading operation.
As shown in fig. 2, fig. 2 is an exemplary interaction flowchart between a server and a client, where the server receives an executable file of BMS software, obtains an upgrade file according to a file header of the executable file and a fool-proof information code, where the fool-proof information code includes a software upgrade validity period, and sends the upgrade file to the client. The client receives an upgrade file with a foolproof information code, compares time information of the software upgrade validity period with real-time clock information of the client to obtain a comparison result when software upgrade is performed, and judges whether the upgrade file executes upgrade operation or not according to the comparison result.
The BMS software upgrading of the client is managed and controlled through the software upgrading validity period set by the server, the situation that the version rollback confusion is caused easily because the version exceeds the validity period due to the direct upgrading of the client, and the BMS software of the client cannot normally work is avoided, and therefore the after-sales maintenance cost of the client is effectively reduced.
The method and the device for processing the executable file can be applied to a server.
It can be understood that, in the server, the first controller is arranged as a main control center, and the valid period of the software upgrade is set, so that the BMS software upgrade of the client is managed and controlled, the situation that the BMS software of the client cannot normally work due to the fact that the version exceeds the valid period and the version rollback confusion is caused easily because the client is directly upgraded is avoided, and the after-sale maintenance cost of the client is effectively reduced.
Referring to fig. 3, fig. 3 is a schematic flowchart illustrating a processing method of an executable file according to an embodiment of the present application, where the method may be executed by a first controller of a server, and as shown in fig. 3, the method includes:
301: an executable file of the BMS software is received.
An executable file refers to a file that can be loaded for execution by the operating system.
In this embodiment, the executable file is a file that the BMS system software can load for execution.
When generating the update file related to the BMS, the server first receives an executable file of BMS software, and the executable file may be derived from an update upper computer or a Power Conversion System (PCS).
The energy storage converter PCS can control the charging and discharging processes of the storage battery to perform alternating current and direct current conversion, and can directly supply power to alternating current loads under the condition of no power grid. The controller of energy storage converter PCS passes through CAN interface and battery management system BMS communication, acquires group battery state information, CAN realize the protectiveness charge-discharge to the battery, ensures battery operation safety.
When receiving the executable file, the server user may select an import path of the executable file on the foolproof code setting interface, as shown in fig. 3, so that the executable file obtained by the server is LV _ ESS _ gen1. bin.
302: and obtaining an upgrade file according to the file header of the executable file and the fool-proof information code, wherein the fool-proof information code comprises the software upgrade validity period.
In some embodiments, after obtaining the executable file, the server obtains the upgrade file according to the file header and the fool-proof information code of the executable file, which may include: outputting a fool-proof code setting interface; receiving a setting operation aiming at the fool-proof code setting interface to obtain a fool-proof information code; and obtaining an upgrade file according to the fool-proof information code and the file header of the executable file.
Specifically, when the upgrade file is obtained, the server outputs a fool-proof code setting interface, as shown in fig. 4, the fool-proof code setting interface includes one or more of company name information, project information, mode information, and hardware version information, and the server user inputs one or more of the company name, the project name, the mode information, and the hardware version information on the fool-proof code setting interface.
Then, the server user sets information on the fool-proof code setting interface, and the server receives setting operation aiming at the fool-proof code setting interface, so that the fool-proof information code is obtained.
Further, the fool-proof setting interface comprises an expiration date setting interface, and the method further comprises: outputting a valid period setting interface; and receiving the setting operation aiming at the valid period setting interface to obtain the valid period of the software upgrading.
The server is internally provided with an upper computer specially used for file synthesis, and a user of the server uses the upper computer to synthesize the foolproof information code containing the software upgrading validity period for the executable file. Specifically, as shown in fig. 4, the server user selects a file path of the executable file of the BMS software on the fool-proof code setting interface to receive the executable file of the BMS software, the inputted Company name Company is PTL, the Item information Item Number is C3S9CDEA09, the Master-Slave mode information Master/Slave is selected as Master, the Hardware version information Hardware Ver is version 1.1, the software upgrade validity period is 2021 year and 3 months, which is abbreviated as 213, so as to obtain setting operations of the user for the fool-proof code setting interface and the validity period setting interface, and after the server user clicks a Composite button, the server obtains the fool-proof information code according to information set by the server user.
The fool-proof information code is shown in fig. 5, the setting operation of the service end user on the fool-proof code setting interface is performed, the obtained fool-proof information code is represented by a 16-ary system, and is composed of a plurality of bytes, for example, a company name occupies three bytes, and is B0/B1/B2, project information occupies 12 bytes, and is B3-B12, software upgrade validity period information occupies 3 bytes, and is B19-B21, B19 corresponds to YearH, corresponding year, for example, the decade in 2021 is "2", B20 corresponds to YearL, corresponding year, for example, the unit in 2021 is "1", B21 corresponds to Month, and corresponding Month is 3 months.
And after the server side obtains the fool-proof information code, obtaining an upgrade file according to the fool-proof information code and the file header of the executable file.
In this embodiment, the executable file is a bin file, and then the header of the executable file is the first byte of LV _ ESS _ gen1. bin. After the server user clicks the Composite button, the server synthesizes the fool-proof information code with the file header of the executable file to obtain an upgrade file, which is understood to be an executable file containing the software upgrade validity period, as shown in fig. 6, and 213 in the block is the software upgrade validity period.
203: and sending the upgrade file to a client, wherein the client is used for determining whether to carry out upgrade operation according to the software upgrade validity period after receiving the upgrade file.
After the server side obtains the upgrade file, the server side sends the upgrade file to the client side, the client side receives the upgrade file, and whether the upgrade operation is carried out or not is determined according to the software upgrade valid period in the upgrade file.
According to the embodiment of the application, the server receives the executable file of the BMS software, then the upgrading file is obtained according to the file header of the executable file and the fool-proof information code, the fool-proof information code comprises the software upgrading validity period, the server sends the upgrading file to the client, and the client determines whether to carry out upgrading operation according to the software upgrading validity period after receiving the upgrading file. Through the set software upgrading validity period, the BMS software upgrading of the client is managed and controlled, the situation that the version is returned to be disordered and the BMS software of the client cannot work normally due to the fact that the version exceeds the validity period easily caused by the fact that the client is directly upgraded is avoided, and therefore the after-sale maintenance cost of the client is effectively reduced.
The software upgrading method and device provided by the embodiment of the application can be applied to a client.
It can be understood that, in the client, the second controller is arranged as a main control center, and whether the upgrade file is subjected to upgrade operation is judged according to the comparison result, so that version confusion caused by upgrade failure due to direct upgrade is avoided, the risk that BMS software cannot be used continuously due to version rollback is reduced, the after-sales maintenance cost of a supplier on the client is reduced, and better economic benefit is brought to an enterprise.
Referring to fig. 7, fig. 7 is a flowchart illustrating a software upgrading method according to an embodiment of the present application, where the method may be executed by a second controller of a client, and as shown in fig. 7, the method includes:
701: and receiving an upgrade file with a fool-proof information code, wherein the fool-proof information code comprises a software upgrade valid period.
And after the version of the BMS software installed on the client is updated, the client automatically downloads an upgrade file sent by the server, wherein the upgrade file contains the fool-proof information code, and the fool-proof information code comprises the software upgrading validity period.
For example, the current version of the BMS software of the client is 1.0 version, when the version of the BMS software updated by the server is 1.1 version, the upgrade file with the fool-proof information code is sent to the client, and the software upgrade validity period in the fool-proof information code is 2021 year and 3 month.
702: and when the software is upgraded, comparing the time information of the software upgrading effective period with the real-time clock information of the client to obtain a comparison result.
After the client obtains the upgrade file, the upgrade file is analyzed to obtain the software upgrade validity period, and at the moment, the software upgrade validity period and the real-time clock information of the client are compared to obtain a comparison structure. The comparison result comprises that the time information of the software upgrading validity period is larger than the real-time clock information of the client, and the time information of the software upgrading validity period is not larger than the real-time clock information of the client.
For example, the time information of the software upgrading validity period is 2021 year 3 month, and when the real-time clock information of the client is 2021 year 2 month, the comparison result that the time information of the software upgrading validity period is greater than the real-time clock information of the client is obtained; and when the real-time clock information of the client is 2021 year 4 month, obtaining a comparison result that the time information of the software upgrading validity period is not larger than the real-time clock information of the client.
703: and judging whether the upgrade file executes the upgrade operation or not according to the comparison result.
After obtaining the comparison result, the client determines whether the upgrade file executes the upgrade operation according to the comparison result, which may include: if the comparison result is that the time information of the software upgrading validity period is larger than the real-time clock information of the client, executing upgrading operation according to the upgrading file; and if the comparison result is that the time information of the software upgrading validity period is not less than the real-time clock information of the client, stopping executing upgrading operation according to the upgrading file.
Specifically, if the comparison result indicates that the time information of the software upgrading validity period is greater than the real-time clock information of the client, it indicates that the upgradable time limit of the BMS software of the client is within the software upgrading validity period, and the client executes the upgrading operation according to the upgrading file.
And if the comparison result is that the time information of the software upgrading validity period is not greater than the real-time clock information of the client, the upgrading cannot be performed if the upgrading validity period of the BMS software of the client exceeds the software upgrading validity period, and the upgrading operation is stopped according to the upgrading file, so that the phenomenon that the BMS software of the client cannot normally work due to version confusion and version rollback caused by upgrading operation when the upgrading validity period of the software is exceeded is avoided.
In some embodiments, after the client stops performing the upgrade operation according to the upgrade file, in order to make the user of the client know that the upgrade cannot be performed, the method further includes: when the execution of the upgrading operation is stopped, generating feedback information of upgrading failure; and reporting the feedback information to a server.
Specifically, when the client stops executing the upgrade operation, feedback information of upgrade failure is generated, as shown in fig. 8, which prompts that the software versions of the client are mismatched and cannot be upgraded, and the client reports the feedback information of upgrade failure to the server, so as to inform the server that the client cannot use the software version for upgrade at this time.
According to the embodiment of the application, the upgrading file received by the client side is provided with the fool-proof information code, the fool-proof information code comprises the software upgrading validity period, when the client side carries out software upgrading, time information of the software upgrading validity period and real-time clock information of the client side are firstly compared to obtain a comparison result, whether the upgrading operation is executed on the upgrading file is judged according to the comparison result, and therefore version confusion caused by direct upgrading is avoided when upgrading fails, the risk that BMS software cannot be used continuously due to version rollback is reduced, after-sale maintenance cost of a supplier on the client side is reduced, and better economic benefits are brought to enterprises.
Correspondingly, as shown in fig. 9, an embodiment of the present application further provides an executable file processing apparatus, which may be used in a server, where the executable file processing apparatus 900 includes:
an executable file receiving module 901 for receiving an executable file of the BMS software;
an upgrade file obtaining module 902, configured to obtain an upgrade file according to a file header of the executable file and a fool-proof information code, where the fool-proof information code includes a software upgrade validity period;
a sending module 903, configured to send the upgrade file to a client, where the client determines whether to perform an upgrade operation according to the software upgrade validity period after receiving the upgrade file.
According to the embodiment of the application, the server receives the executable file of the BMS software, then the upgrading file is obtained according to the file header of the executable file and the fool-proof information code, the fool-proof information code comprises the software upgrading validity period, the server sends the upgrading file to the client, and the client determines whether to carry out upgrading operation according to the software upgrading validity period after receiving the upgrading file. Through the set software upgrading validity period, the BMS software upgrading of the client is managed and controlled, the situation that the version is returned to be disordered and the BMS software of the client cannot work normally due to the fact that the version exceeds the validity period easily caused by the fact that the client is directly upgraded is avoided, and therefore the after-sale maintenance cost of the client is effectively reduced.
In other embodiments, the upgrade file obtaining module 902 is further configured to:
outputting a fool-proof code setting interface; receiving a setting operation aiming at the fool-proof code setting interface to obtain a fool-proof information code; and obtaining an upgrade file according to the fool-proof information code and the file header of the executable file.
In other embodiments, the upgrade file obtaining module 902 is further configured to:
outputting a validity period setting interface; and receiving the setting operation aiming at the valid period setting interface to obtain the software upgrading valid period.
Correspondingly, as shown in fig. 10, an embodiment of the present application further provides a software upgrading apparatus, which may be used for a client, where the software upgrading apparatus 1000 includes:
an upgrade file receiving module 1001 configured to receive an upgrade file with a fool-proof information code, where the fool-proof information code includes a software upgrade validity period;
the comparison module 1002 is configured to compare, when software is upgraded, time information of the software upgrade validity period and real-time clock information of the client to obtain a comparison result;
a judging module 1003, configured to judge whether the upgrade file executes an upgrade operation according to the comparison result.
According to the embodiment of the application, the upgrading file received by the client side is provided with the fool-proof information code, the fool-proof information code comprises the software upgrading validity period, when the client side carries out software upgrading, time information of the software upgrading validity period and real-time clock information of the client side are firstly compared to obtain a comparison result, whether the upgrading operation is executed on the upgrading file is judged according to the comparison result, and therefore version confusion caused by direct upgrading is avoided when upgrading fails, the risk that BMS software cannot be used continuously due to version rollback is reduced, after-sale maintenance cost of a supplier on the client side is reduced, and better economic benefits are brought to enterprises.
In other embodiments, the determining module 1003 is further configured to:
if the comparison result is that the time information of the software upgrading validity period is larger than the real-time clock information of the client, executing upgrading operation according to the upgrading file;
and if the comparison result is that the time information of the software upgrading effective period is not less than the real-time clock information of the client, stopping executing upgrading operation according to the upgrading file.
In other embodiments, the software upgrade apparatus 1000 further comprises a feedback module 1004 for:
when the execution of the upgrading operation is stopped, generating feedback information of upgrading failure; and reporting the feedback information to a server.
The device can execute the processing method of the executable file provided by the embodiment of the application, and has the corresponding functional modules and beneficial effects of the processing method of the executable file. For technical details that are not described in detail in the device embodiments, reference may be made to the processing method of the executable file provided in the embodiments of the present application.
Fig. 11 is a schematic hardware structure diagram of a first controller in an embodiment of a server, as shown in fig. 11, the first controller includes:
one or more first processors 1101, a memory 1102. In fig. 11, a first processor 1101 and a first memory 1102 are taken as an example.
The first processor 1101 and the first memory 1102 may be connected by a bus or other means, and fig. 11 illustrates an example of connection by a bus.
The first memory 1102, which is a non-volatile computer-readable storage medium, may be used to store non-volatile software programs, non-volatile computer-executable programs, and modules, such as program instructions/modules corresponding to the executable file processing method in the embodiment of the present application (for example, the executable file receiving module 801, the upgrade file obtaining module 802, and the sending module 803 shown in fig. 8). The first processor 1101 executes various functional applications and data processing of the first controller, that is, a processing method of an executable file implementing the above-described method embodiment, by running a nonvolatile software program, instructions, and modules stored in the first memory 1102.
The first memory 1102 may include a storage program area and a storage data area, wherein the storage program area may store an operating system, an application program required for at least one function; the storage data area may store data created according to use of a processing device that can execute a file, and the like. In addition, the first memory 1102 may include high speed random access memory, and may also include non-volatile memory, such as at least one magnetic disk storage device, flash memory device, or other non-volatile solid state storage device. In some embodiments, the first memory 1102 may optionally include memory located remotely from the first processor 1101, which may be connected to a server over a network. Examples of such networks include, but are not limited to, the internet, intranets, local area networks, mobile communication networks, and combinations thereof.
The one or more modules are stored in the first memory 1102, and when executed by the one or more first processors 1101, perform the method of processing an executable file in any of the method embodiments described above, e.g., performing method steps 301 to 303 of fig. 3 described above; the functions of the modules 901 and 903 in fig. 9 are realized.
Fig. 12 is a schematic diagram of a hardware structure of a second controller in an embodiment of the client, where as shown in fig. 12, the second controller includes:
one or more second processors 1201, a second memory 1202. Fig. 12 illustrates an example of one second processor 1201 and one second memory 1202.
The second processor 1201 and the second memory 1202 may be connected by a bus or other means, and the bus connection is exemplified in fig. 12.
It is understood that the second processor 1201 is similar to the first processor 1101 described above, and the second memory 1202 is similar to the first memory 1102 described above, and therefore will not be described herein again.
The product can execute the software upgrading method provided by the embodiment of the application, and has the corresponding functional modules and beneficial effects of the execution method. For details of the technology that are not described in detail in this embodiment, reference may be made to the software upgrading method provided in the embodiments of the present application.
The above-described embodiments of the apparatus are merely illustrative, and the units described as separate parts may or may not be physically separate, and parts displayed as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. Some or all of the modules may be selected according to actual needs to achieve the purpose of the solution of the present embodiment.
Through the above description of the embodiments, those skilled in the art will clearly understand that the embodiments may be implemented by software plus a general hardware platform, and may also be implemented by hardware. It will be understood by those skilled in the art that all or part of the processes of the methods of the embodiments described above can be implemented by hardware instructions of a computer program, which can be stored in a computer-readable storage medium, and when the program is executed, the processes of the embodiments of the methods described above can be included. The storage medium may be a magnetic disk, an optical disk, a Read-Only Memory (ROM), a Random Access Memory (RAM), or the like.
Finally, it should be noted that: the above embodiments are only used to illustrate the technical solutions of the present application, and are not limited thereto; within the context of the present application, where technical features in the above embodiments or in different embodiments can also be combined, the steps can be implemented in any order and there are many other variations of the different aspects of the present application as described above, which are not provided in detail for the sake of brevity; although the present application has been described in detail with reference to the foregoing embodiments, it should be understood by those of ordinary skill in the art that: the technical solutions described in the foregoing embodiments may still be modified, or some technical features may be equivalently replaced; and the modifications or the substitutions do not make the essence of the corresponding technical solutions depart from the scope of the technical solutions of the embodiments of the present application.
Claims (11)
1. A method for processing an executable file, the method comprising:
receiving an executable file of the BMS software;
obtaining an upgrade file according to a file header of the executable file and a fool-proof information code, wherein the fool-proof information code comprises a software upgrade validity period;
and sending the upgrade file to a client, wherein the client is used for determining whether to carry out upgrade operation according to the software upgrade validity period after receiving the upgrade file.
2. The method of claim 1, wherein obtaining an upgrade file according to a header and a fool-proof information code of the executable file comprises:
outputting a fool-proof code setting interface;
receiving a setting operation aiming at the fool-proof code setting interface to obtain a fool-proof information code;
and obtaining an upgrade file according to the fool-proof information code and the file header of the executable file.
3. The method of claim 2, wherein the fool-proof setting interface comprises a validity period setting interface, the method further comprising:
outputting a validity period setting interface;
and receiving the setting operation aiming at the valid period setting interface to obtain the valid period of the software upgrading.
4. The method of claim 2, wherein the fool-proof code setup interface further comprises one or more of company name information, project information, schema information, hardware version information.
5. A method of upgrading software, the method comprising:
receiving an upgrade file with a fool-proof information code, wherein the fool-proof information code comprises a software upgrade validity period;
when software is upgraded, comparing the time information of the software upgrading validity period with the real-time clock information of the client to obtain a comparison result;
and judging whether the upgrade file executes the upgrade operation or not according to the comparison result.
6. The method according to claim 5, wherein the determining whether the upgrade file performs an upgrade operation according to the comparison result includes:
if the comparison result is that the time information of the software upgrading validity period is larger than the real-time clock information of the client, executing upgrading operation according to the upgrading file;
and if the comparison result is that the time information of the software upgrading validity period is not less than the real-time clock information of the client, stopping executing upgrading operation according to the upgrading file.
7. The method of claim 6, wherein after the ceasing to perform the upgrade operation according to the upgrade file, the method further comprises:
when the execution of the upgrading operation is stopped, generating feedback information of upgrading failure;
and reporting the feedback information to a server.
8. An apparatus for processing an executable file, the apparatus comprising:
the executable file receiving module is used for receiving the executable file of the BMS software;
the upgrading file obtaining module is used for obtaining an upgrading file according to a file header of the executable file and a fool-proof information code, wherein the fool-proof information code comprises a software upgrading validity period;
and the sending module is used for sending the upgrade file to a client, wherein the client determines whether to perform upgrade operation according to the software upgrade validity period after receiving the upgrade file.
9. A software upgrading apparatus, characterized in that the apparatus comprises:
the system comprises an upgrade file receiving module, a software upgrading module and a control module, wherein the upgrade file receiving module is used for receiving an upgrade file with a foolproof information code, and the foolproof information code comprises a software upgrading validity period;
the comparison module is used for comparing the time information of the software upgrading validity period with the real-time clock information of the client to obtain a comparison result when software upgrading is carried out;
and the judging module is used for judging whether the upgrading file executes upgrading operation or not according to the comparison result.
10. A server, characterized in that the server comprises:
at least one first processor, and
a first memory communicatively coupled to the first processor, the first memory storing instructions executable by the at least one first processor to enable the at least one processor to perform the method of any of claims 1-4.
11. A client, the client comprising:
at least one second processor, and
a second memory communicatively coupled to the second processor, the second memory storing instructions executable by the at least one second processor to enable the at least one processor to perform the method of any of claims 5-7.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110886692.4A CN113672256A (en) | 2021-08-03 | 2021-08-03 | Processing method and server of executable file, software upgrading method and client |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110886692.4A CN113672256A (en) | 2021-08-03 | 2021-08-03 | Processing method and server of executable file, software upgrading method and client |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN113672256A true CN113672256A (en) | 2021-11-19 |
Family
ID=78541218
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202110886692.4A Pending CN113672256A (en) | 2021-08-03 | 2021-08-03 | Processing method and server of executable file, software upgrading method and client |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN113672256A (en) |
Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101557308A (en) * | 2009-05-06 | 2009-10-14 | 成都市华为赛门铁克科技有限公司 | File upgrading method and terminal device |
| CN105491161A (en) * | 2016-01-19 | 2016-04-13 | 深圳市沃特玛电池有限公司 | Battery management system software remote upgrading system and remote upgrading method thereof |
| CN106358083A (en) * | 2016-09-05 | 2017-01-25 | 深圳Tcl数字技术有限公司 | Method and system for updating television application |
| CN108270806A (en) * | 2016-12-30 | 2018-07-10 | 航天信息股份有限公司 | A kind of more application upgrade method and systems |
| CN111694579A (en) * | 2019-03-11 | 2020-09-22 | 宁德时代新能源科技股份有限公司 | Remote upgrading method of energy storage system, energy management system and battery management system |
-
2021
- 2021-08-03 CN CN202110886692.4A patent/CN113672256A/en active Pending
Patent Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101557308A (en) * | 2009-05-06 | 2009-10-14 | 成都市华为赛门铁克科技有限公司 | File upgrading method and terminal device |
| CN105491161A (en) * | 2016-01-19 | 2016-04-13 | 深圳市沃特玛电池有限公司 | Battery management system software remote upgrading system and remote upgrading method thereof |
| CN106358083A (en) * | 2016-09-05 | 2017-01-25 | 深圳Tcl数字技术有限公司 | Method and system for updating television application |
| CN108270806A (en) * | 2016-12-30 | 2018-07-10 | 航天信息股份有限公司 | A kind of more application upgrade method and systems |
| CN111694579A (en) * | 2019-03-11 | 2020-09-22 | 宁德时代新能源科技股份有限公司 | Remote upgrading method of energy storage system, energy management system and battery management system |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US9160171B2 (en) | Pre-processing of data for automatic generation control | |
| CN105872123B (en) | Address coding method, battery monitoring unit, battery management unit and system | |
| EP3016237A1 (en) | Method for controlling charging power, system for controlling charging power, and program | |
| CN109359031B (en) | Multi-device application program testing method and device, server and storage medium | |
| EP3635547B1 (en) | Systems and methods for preventing service disruption during software updates | |
| CN104932912A (en) | Software updating method and system and mobile device | |
| EP3024115A1 (en) | Rapid charging method for storage cell, rapid charging system, and program | |
| CN112394957A (en) | Server upgrading method and device, server and storage medium | |
| CN109941149A (en) | Multi-source battery pack charging/discharging thereof, device, electronic equipment, storage medium | |
| CN104953707A (en) | Intelligent error prevention method and system for monitoring operation order | |
| CN113157297B (en) | Remote upgrading method and system for charging station equipment | |
| CN113672256A (en) | Processing method and server of executable file, software upgrading method and client | |
| CN101685144B (en) | Mine lamp service life monitoring device and implement method | |
| CN111984287A (en) | Equipment upgrading method and system | |
| CN111816939A (en) | Battery pack maintenance method and device, electronic equipment and storage medium | |
| US9239720B2 (en) | Device and method for generating application model based on layered structure | |
| CN114633652B (en) | Charging system, method and device for dynamic power distribution, main charging pile and medium | |
| CN112306534A (en) | Firmware upgrading method and device, electronic equipment and storage medium | |
| CN103914339A (en) | Server management system and server management method | |
| CN111082964B (en) | Distribution method and device of configuration information | |
| CN113721938A (en) | Edge-edge cooperative task processing method, device and system suitable for power Internet of things | |
| CN116737208B (en) | Software maintenance upgrade management method and device and electronic equipment | |
| CN110518611B (en) | Charging and discharging autonomous control method and device of energy storage module and energy storage equipment | |
| US20230382260A1 (en) | Charging location selection of an incoming electric vehicle for large ev depot infrastructure | |
| CN115520155A (en) | Mobile battery replacement method, system, device, electronic equipment and storage medium |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination |