CN111722860B - OTA upgrading method and device based on finite state machine - Google Patents
OTA upgrading method and device based on finite state machine Download PDFInfo
- Publication number
- CN111722860B CN111722860B CN202010552191.8A CN202010552191A CN111722860B CN 111722860 B CN111722860 B CN 111722860B CN 202010552191 A CN202010552191 A CN 202010552191A CN 111722860 B CN111722860 B CN 111722860B
- Authority
- CN
- China
- Prior art keywords
- upgrade
- upgrading
- state
- node
- downloading
- 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.)
- Active
Links
- 238000000034 method Methods 0.000 title claims abstract description 91
- 230000008569 process Effects 0.000 claims abstract description 40
- 238000004891 communication Methods 0.000 claims abstract description 16
- 230000004044 response Effects 0.000 claims description 7
- 238000004590 computer program Methods 0.000 claims description 6
- 238000006243 chemical reaction Methods 0.000 claims description 4
- 230000003993 interaction Effects 0.000 description 7
- 230000007246 mechanism Effects 0.000 description 6
- 238000010586 diagram Methods 0.000 description 5
- 238000011161 development Methods 0.000 description 4
- 238000012545 processing Methods 0.000 description 4
- 230000003044 adaptive effect Effects 0.000 description 3
- 230000008859 change Effects 0.000 description 3
- 230000003287 optical effect Effects 0.000 description 3
- 230000000977 initiatory effect Effects 0.000 description 2
- 238000006467 substitution reaction Methods 0.000 description 2
- 238000012546 transfer Methods 0.000 description 2
- 230000007704 transition Effects 0.000 description 2
- 102100034112 Alkyldihydroxyacetonephosphate synthase, peroxisomal Human genes 0.000 description 1
- 101000799143 Homo sapiens Alkyldihydroxyacetonephosphate synthase, peroxisomal Proteins 0.000 description 1
- 238000000848 angular dependent Auger electron spectroscopy Methods 0.000 description 1
- 230000005540 biological transmission Effects 0.000 description 1
- 230000001680 brushing effect Effects 0.000 description 1
- 230000001419 dependent effect Effects 0.000 description 1
- 238000005516 engineering process Methods 0.000 description 1
- 238000010295 mobile communication Methods 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 238000012795 verification Methods 0.000 description 1
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
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/50—Network services
- H04L67/56—Provisioning of proxy services
Landscapes
- Engineering & Computer Science (AREA)
- Software Systems (AREA)
- General Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Computer Security & Cryptography (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Stored Programmes (AREA)
Abstract
The invention provides an OTA upgrading method and device based on a finite state machine, which are applied to upgrading nodes of an OTA upgrading agent process deployed on a vehicle-end finite state machine, wherein the method comprises the steps that if the upgrading nodes are in an idle state and query information sent by an upgrading end is received, communication connection is established with a cloud server, and the query information is sent to the cloud server, so that the cloud server determines upgrading information according to the query information; responding to a download driving instruction sent by the upgrading end, completing the downloading operation of the upgrading package according to the upgrading information, transferring the state of the upgrading node to a downloading completion state, and feeding back the downloading completion result to the upgrading end so that the upgrading end upgrades the ECU based on the upgrading package; and responding to an upgrade completion driving instruction sent by an upgrade terminal, if the ECUs corresponding to the upgrade package are all upgraded, transferring the state of the upgrade node to an idle state, and adapting to different upgrade requirements through the deployment of an OTA upgrade agent process of a finite state machine.
Description
Technical Field
The invention relates to the technical field of OTA (over the air) upgrading, in particular to an OTA upgrading method and device based on a finite state machine.
Background
With the development of the automotive industry and the increasing number of car software bugs, OTA (Over-the-Air Technology Over-the-Air, also known as online upgrades) is being sought by numerous host factories. And the cloud server pushes the updated version to the vehicle end according to the version information and the vehicle information reported by the vehicle end, and the vehicle end downloads the updated version and carries out version updating.
In the development process of the whole vehicle OTA upgrade, for OTA suppliers, the number of electronic control units (ECU, electronic Control Unit) to be refreshed and the refreshing priority of different host factories are different, so that the development of the vehicle end of the OTA is difficult to adapt to the requirements of all host factories at one time. In addition, the current whole car OTA upgrading mode and the off-line refreshing mode cannot coexist, and various upgrading scenes cannot be met.
Disclosure of Invention
Therefore, the present invention aims to provide an OTA upgrading method and device based on a finite state machine, which can adapt to different upgrading requirements through deployment of an OTA upgrading agent process of the finite state machine.
In a first aspect, an embodiment provides an OTA upgrade method based on a finite state machine, applied to an upgrade node of a vehicle-end finite state machine, where the upgrade node is deployed with an OTA upgrade proxy process, the method includes:
If the upgrade node is in an idle state and receives query information sent by an upgrade end, communication connection is established with a cloud server, the query information is sent to the cloud server, so that the cloud server determines upgrade information according to the query information, wherein the query information comprises vehicle information, ECU version information, ECU types and the number of ECUs, and the cloud server configures upgrade information corresponding to each type of ECUs in advance;
responding to a download driving instruction sent by the upgrading end, completing the downloading operation of an upgrading packet according to the upgrading information, transferring the state of the upgrading node to a downloading completion state, and feeding back the downloading completion result to the upgrading end so that the upgrading end upgrades the ECU based on the upgrading packet;
and responding to an upgrade completion driving instruction sent by the upgrade terminal, and if the ECUs corresponding to the upgrade package are all upgraded, transferring the state of the upgrade node to an idle state, wherein the upgrade completion driving instruction is sent by the upgrade terminal under the condition of completing the upgrade operation of the ECUs.
In an alternative embodiment, the method further comprises:
the method comprises the steps of connecting with an upper computer to obtain an offline upgrade package in the upper computer;
And sending the offline upgrade package to the upgrade terminal so that the upgrade terminal performs upgrade based on the offline upgrade package.
In an optional embodiment, the upgrade package corresponds to one or more ECU upgrade tasks, and if the upgrade package corresponds to one ECU upgrade task, the upgrade information includes a task ID generated by the cloud server according to the query information.
In an alternative embodiment, before the step of responding to the download driving instruction sent by the upgrade end, the method further includes:
and receiving the upgrade information sent by the cloud server, feeding the upgrade information back to an upgrade end, and transferring the state of the upgrade node to a state ready for upgrade.
In an optional embodiment, responding to a download driving instruction sent by the upgrade end, completing the downloading operation of the upgrade package according to the upgrade information, transferring the state of the upgrade node to a download completion state, and feeding back the download completion result to the upgrade end, where the method includes the steps of:
receiving a start downloading driving instruction sent by the upgrading end, downloading an upgrading packet according to a downloading address in the upgrading information, and transferring the state of the upgrading node to a downloading state;
Receiving a downloading progress acquisition instruction sent by the upgrading end, and feeding back the downloading progress of the upgrading packet to the upgrading end;
if the upgrade package is downloaded and the upgrade package after the download is checked, feeding back the downloaded result to the upgrade terminal, and transferring the state of the upgrade node to a download completion state.
In an optional embodiment, in response to an upgrade completion driving instruction sent by the upgrade end, if all the ECUs corresponding to the upgrade package are upgraded, the step of transferring the state of the upgrade node to an idle state includes:
receiving an upgrade driving instruction sent by the upgrade end, uploading upgrade starting information to the cloud server, and transferring the state of the upgrade node to upgrade;
when the upgrade terminal completes the upgrade operation of the ECU based on the upgrade package, receiving an upgrade completion driving instruction sent by the upgrade terminal, uploading an upgrade completion message to the cloud server, and transferring the state of the upgrade node to an upgrade completion state;
and if each ECU corresponding to the upgrade package is upgraded, transferring the state of the upgrade node to an idle state.
In an alternative embodiment, the method further comprises:
And responding to a termination driving instruction sent by the upgrading end, and transferring the state of the upgrading node to an upgrading completion state.
In a second aspect, an embodiment provides an OTA upgrade apparatus based on a finite state machine, applied to an upgrade node of a vehicle-end finite state machine, where the upgrade node is deployed with an OTA upgrade proxy process, the apparatus includes:
the query module is used for establishing communication connection with a cloud server if the upgrade node is in an idle state and receives query information sent by an upgrade end, and is used for sending the query information to the cloud server so that the cloud server can determine upgrade information according to the query information, wherein the query information comprises vehicle information, ECU version information, ECU types and ECU quantity, and the cloud server is pre-configured with upgrade information corresponding to each ECU;
the downloading module is used for responding to a downloading driving instruction sent by the upgrading end, completing the downloading operation of the upgrading package according to the upgrading information, transferring the state of the upgrading node to a downloading completed state, and feeding back the downloading completed result to the upgrading end so that the upgrading end upgrades the ECU based on the upgrading package;
And the upgrade module is used for responding to an upgrade completion driving instruction sent by the upgrade terminal, and if the ECUs corresponding to the upgrade package are all upgraded, the state of the upgrade node is transferred to an idle state, wherein the upgrade completion driving instruction is sent by the upgrade terminal under the condition of completing the upgrade operation of the ECUs.
In a third aspect, an embodiment provides an electronic device, including a memory, a processor, where the memory stores a computer program executable on the processor, and where the processor implements the steps of the method according to any of the foregoing embodiments when the computer program is executed.
In a fourth aspect, embodiments provide a machine-readable storage medium storing machine-executable instructions that, when invoked and executed by a processor, cause the processor to implement the steps of the method of any of the preceding embodiments.
According to the OTA upgrading method and device based on the finite state machine, the finite state machine is applied to the vehicle end, an OTA upgrading agent process is deployed at an upgrading node of the finite state machine, interaction is respectively carried out on the upgrading end of the vehicle end and a cloud server, and corresponding operation is automatically completed through state conversion of the upgrading node. If the current node state is idle, the upgrading node establishes communication with a cloud server according to the query information of the upgrading end, and the cloud server determines corresponding upgrading information based on the query information so as to meet upgrading requirements of various different host factories; the upgrade node finishes the upgrade package downloading operation based on the upgrade information according to the download driving instruction of the upgrade terminal, the node state is set to be that the downloading is finished, and the result after the downloading is fed back to the upgrade terminal, so that the upgrade terminal performs ECU upgrade according to the upgrade package; when the ECU in the upgrade package is upgraded, an upgrade completion driving instruction sent by an upgrade end is received, the node state is set to be upgrade completed, and after all the ECUs in the upgrade package are upgraded, the upgrade node state is set to be idle, so that different upgrade requirements can be met.
Additional features and advantages of the disclosure will be set forth in the description which follows, or in part will be obvious from the description, or may be learned by practice of the techniques of the disclosure.
The foregoing objects, features and advantages of the disclosure will be more readily apparent from the following detailed description of the preferred embodiments taken in conjunction with the accompanying drawings.
Drawings
In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings that are needed in the description of the embodiments or the prior art will be briefly described, and it is obvious that the drawings in the description below are some embodiments of the present invention, and other drawings can be obtained according to the drawings without inventive effort for a person skilled in the art.
Fig. 1 is a flowchart of an OTA upgrading method based on a finite state machine according to an embodiment of the present invention;
FIG. 2 is a schematic diagram of an upgrade state transition diagram based on a finite state machine according to an embodiment of the present invention;
fig. 3 is a multi-terminal interaction schematic diagram of an OTA upgrade adaptive method based on a finite state machine according to an embodiment of the present invention;
Fig. 4 is a functional block diagram of an OTA upgrading device based on a finite state machine according to an embodiment of the present invention;
fig. 5 is a schematic diagram of a hardware architecture of an electronic device according to an embodiment of the present invention.
Detailed Description
For the purpose of making the objects, technical solutions and advantages of the embodiments of the present invention more apparent, the technical solutions of the present invention will be clearly and completely described below with reference to the accompanying drawings, and it is apparent that the described embodiments are some embodiments of the present invention, but not all embodiments. All other embodiments, which can be made by those skilled in the art based on the embodiments of the invention without making any inventive effort, are intended to be within the scope of the invention.
At present, aiming at different requirements of host factories, each OTA provider provides a scheme for upgrading the whole vehicle, the large diameter of the whole vehicle is the same in the processing flow, and the whole vehicle is processed from three aspects of cloud end-pipe end-vehicle end, and the general flow is as follows:
1) The OTA provider uploads the upgrade package to a cloud OTA server;
2) The vehicle end and the OTA server establish safe connection through the pipe end;
3) The vehicle end reports version information and vehicle information;
4) The server pushes updated version information to the vehicle end;
5) Man-machine interaction (interaction between a user and a vehicle end) confirms downloading of the upgrade package;
6) The vehicle end establishes a safe connection with the server and downloads an upgrade package;
7) Man-machine interaction confirms upgrading;
8) The vehicle end starts to upgrade;
9) And finishing the upgrading of the vehicle end.
Because each host factory has different upgrading requirements for different types of vehicles, different types and numbers of ECUs, suppliers need to execute the upgrading process once for the upgrading requirements of each host factory, and the upgrading process is complex.
In addition, some host factories may have developed offline refreshing programs, and if the ECU is updated in an OTA manner, the original offline refreshing updating program cannot be basically adapted. If the current vehicle end adopts an OTA upgrade mode, the developed offline refreshing program cannot be applied to upgrade, or if the current vehicle end applies the developed offline refreshing program to upgrade, the ECU cannot be upgraded in the OTA mode. The OTA upgrading mode redeveloped by the vehicle end and the original off-line refreshing upgrading mode are mutually independent and cannot be applied together, and cannot be suitable for the current diversified upgrading application scenes of the vehicle end.
Based on the above, the method and the device for OTA upgrading based on the finite state machine provided by the embodiment of the invention can adapt to different upgrading requirements through the deployment of the OTA upgrading agent process of the finite state machine.
For the convenience of understanding the present embodiment, an OTA upgrading method based on a finite state machine disclosed in the present embodiment is first described in detail, where an agent program of an OTA driver may be deployed on an upgrade master node of the finite state machine, so that the method can adapt to writing in various languages and running in various environments.
Fig. 1 is a flowchart of an OTA upgrading method based on a finite state machine according to an embodiment of the present invention.
As shown in fig. 1, the method for upgrading OTA based on finite state machine is applied to upgrade nodes of finite state machine at vehicle end, the upgrade nodes are deployed with (OTA Agent) upgrade Agent process, and accept business process processing of vehicle end and OTA service end, and includes the following steps:
step S102, if the upgrade node is in an idle state and receives the query information sent by the upgrade end, communication connection is established with the cloud server, the query information is sent to the cloud server, so that the cloud server determines upgrade information according to the query information, wherein the query information comprises vehicle information, ECU version information, ECU types and ECU quantity, and the cloud server configures upgrade information corresponding to each type of ECU in advance.
Step S104, responding to the download driving instruction sent by the upgrade terminal, completing the download operation of the upgrade package according to the upgrade information, transferring the state of the upgrade node to the download completion state, and feeding back the download completion result to the upgrade terminal, so that the upgrade terminal upgrades the ECU based on the upgrade package.
Step S106, responding to an upgrade completion driving instruction sent by the upgrade terminal, and if the ECUs corresponding to the upgrade package are all upgraded, transferring the state of the upgrade node to an idle state, wherein the upgrade completion driving instruction is sent by the upgrade terminal under the condition of completing the upgrade operation of the ECUs.
In a preferred embodiment of practical application, an OTA upgrade agent process is deployed on an upgrade node of a finite state machine by applying the finite state machine on a vehicle end, and the OTA upgrade agent process is interacted with an upgrade end and a cloud server of the vehicle end respectively, and corresponding operation is automatically completed through state conversion of the upgrade node. If the current node state is idle, the upgrading node establishes communication with a cloud server according to the query information of the upgrading end, and the cloud server determines corresponding upgrading information based on the query information so as to meet upgrading requirements of various different host factories; the upgrade node finishes the upgrade package downloading operation based on the upgrade information according to the download driving instruction of the upgrade terminal, the node state is set to be that the downloading is finished, and the result after the downloading is fed back to the upgrade terminal, so that the upgrade terminal performs ECU upgrade according to the upgrade package; when the ECU in the upgrade package is upgraded, an upgrade completion driving instruction sent by an upgrade end is received, the node state is set to be upgrade completed, and after all the ECUs in the upgrade package are upgraded, the upgrade node state is set to be idle, so that different upgrade requirements can be met.
The agent process of the OTA vehicle end adopts a self-adaptive mode of a finite state machine, and fully displays various active states in the OTA upgrading process. But are not limited to the several states described in the present invention, and other states may be extended without departing from the spirit of the present invention.
In an alternative implementation manner, the method in the embodiment of the present invention further includes the following steps:
step 1.1), connecting with an upper computer to obtain an offline upgrade package in the upper computer;
here, the upper computer may include a diagnostic apparatus, an intelligent device, a PC end, etc., and may enable the OTA upgrade node to be connected with the upper computer through a communication manner such as wireless communication, a USB interface, bluetooth, etc., and obtain an offline upgrade package.
Step 1.2), the offline upgrade package is sent to the upgrade terminal, so that the upgrade terminal performs upgrade based on the offline upgrade package.
According to the embodiment of the invention, the OTA proxy process is introduced, so that the upgrading end of the vehicle end is decoupled from the OTA Server, the OTA proxy process is used for completing the safe interaction with the cloud Server, the OTA is upgraded more safely and reliably, the original offline refreshing program of a host factory can be adapted at the same time, the cost of redevelopment of the upgrading program is saved, or the secondary development cost of offline refreshing is saved. The vehicle end of the embodiment of the invention can be connected with the cloud server through the upgrading node of the OTA proxy process to realize a remote OTA upgrading mode, and can also be connected with the upper computer through the upgrading node of the OTA proxy process to upgrade the ECU according to the original offline refreshing program so as to adapt to diversified vehicle end upgrading scenes.
In an alternative embodiment, the upgrade package corresponds to one or more ECU upgrade tasks, and if the upgrade package corresponds to one ECU upgrade task, the upgrade information includes a task ID generated by the cloud server according to the query information.
Here, for the case where the upgrade package corresponds to one or more ECU upgrade tasks, two upgrade mechanisms are respectively corresponding: the mechanism of the upgrade package corresponding to a plurality of ECU upgrade tasks is all in one, and the mechanism of the upgrade package corresponding to one ECU upgrade task is one by one. Here, the cloud server may determine the current upgrade information and upgrade mechanism according to the vehicle model or the number and type of the upgrade ECU corresponding to the upgrade of the host factory in the query information. The cloud server may pre-configure upgrade information corresponding to each ECU, upgrade order of each ECU, or upgrade mechanism that should be selected when upgrading a plurality of ECUs with strong/weak dependencies.
It should be noted that the ECU types may include electronic control systems, intelligent vehicle-mounted systems, and infotainment systems, where the electronic control systems may include a vehicle body control system, a battery management system, a power control system, a chassis control system, a safety control system, and a vehicle-mounted bluetooth system; the intelligent vehicle may include intelligent cabins, display designs, meters, autopilot control units ((ADAS Domain Controller UnitADCU), the internet of vehicles TBOX (Telematics BOX); infotainment systems may include in-vehicle entertainment services, GPS navigation, mobile communication services.
The upgrade order of each ECU is not fixed because the whole vehicle architecture of each vehicle factory is different, and the upgrade order of each ECU can be set according to the requirements of the host computer factory.
In order to more clearly describe the embodiments of the present invention, the node status and the event type corresponding to the node will be explained separately, as shown in fig. 2. Wherein the node state includes:
idle: the OTA Agent process is in a silent state;
preparing for upgrading: after the upgrading task issued by the OTA server is processed, the OTA server enters a state of preparing for upgrading;
in the downloading process: the current upgrade task is downloading an upgrade package;
and (3) finishing downloading: the current upgrade task finishes the downloading of an upgrade package;
in the updating: the current upgrade task is in the refreshing process;
and (3) upgrading completion: the current upgrade task has been completed.
Here, all message events (driving instructions) are driven by the upgrade end of the vehicle end, i.e. there is an upgrade node that the upgrade end sends to the OTA Agent process. Finally, the upgrading terminal completes final updating by brushing according to the legal upgrading package downloaded to the local and the decision of the user. Event types may include:
query information RequestTask: the request upgrade task inquiry can customize reporting OTA vehicle information, ECU version information and the like according to different requirements of a vehicle end;
The download of DownloadStart is started: requesting to start downloading;
cancel download DownloadCancel: cancel/terminal download;
percentage of progress percentage: requesting to read the percentage of downloads;
starting to upgrade: notifying to start updating;
cancel the upgrade: canceling updating;
and (3) upgrading completion: and the updating is completed at the same time.
Based on the node states and event types, the state transition of the upgrade node of the vehicle terminal based on the finite state machine will be described with reference to fig. 2. In a finite state machine, the OTA Agent processes upgrade various node states of the nodes, and upgrade interaction with the OTA Server cloud Server is completed under the condition of receiving corresponding event drives of correct types. The method mainly comprises the steps of establishing a secure connection with an OTA Server cloud Server, completing secure communication, completing secure downloading, supporting breakpoint continuous transmission, completing downloading results, reporting upgrading results and the like. The method and the system have the advantages that the upgrading end of the vehicle end is decoupled from the OTA Server cloud Server, and the vehicle end can be adapted no matter how the quantity of the vehicle end upgrading ECUs and the upgrading sequence of the ECUs are different. Meanwhile, when the node state of the OTA Agent is driven by an error event, the OTA Agent prompts the error to the upgrading end, and the upgrading end can perform self-adjustment according to the upgrading flow.
Here, the upgrade process of all in one mode is described first, and the refresh version of each ECU is packaged into an upgrade package with a certain preset policy and security mechanism, which is called all in one mode. The upgrade package of the mode can realize the purpose of upgrading a plurality of ECUs through one-time downloading, and a state machine of the OTA Agent only needs to be adapted to one-time task driving. If the dependency relationship between the ECUs is not strong, the all in one mode may be adopted for upgrading in order to save the number of downloads.
When the initial state of the OTAAgent upgrade node is idle, the upgrade end waits for initiating a query message.
In an alternative embodiment, prior to step S104, the method further comprises:
step 2.1), receiving upgrading information sent by the cloud server, feeding the upgrading information back to the upgrading end, and transferring the state of the upgrading node to a state ready for upgrading.
The upgrade node of the OTA Agent process is driven by the query information request task, establishes connection with the OTA Server cloud Server, reports all ECU information and necessary vehicle information in the query information, returns the upgrade information to the upgrade end after receiving the upgrade information of correct response of the cloud Server OTA Server, and at the moment, the upgrade node of the OTA Agent process automatically shifts to a 'ready to upgrade' state.
In an alternative embodiment, step S104 includes:
step 3.1), receiving a downloading starting driving instruction sent by an upgrading end, downloading an upgrading packet according to a downloading address in upgrading information, and transferring the state of an upgrading node to a downloading state;
here, the upgrade node of the OTA Agent process is driven by the start download instruction, and starts downloading the upgrade package according to the download address in the upgrade information responded by the server, and the state of the upgrade node is transferred into "downloading";
step 3.2), receiving a downloading progress acquisition instruction sent by the upgrading end, and feeding back the downloading progress of the upgrading packet to the upgrading end;
step 3.3), if the downloading of the upgrade package is completed and the upgrade package after the downloading is verified, feeding back the downloading result to the upgrade end, and transferring the state of the upgrade node to the downloading completion state.
Here, in the downloading process of the OTA Agent upgrade package, the upgrade end sends the progress percentage to obtain the downloading progress, and the OTA Agent process upgrades the node to feed back the downloading progress. When the downloading of the upgrade package of the OTA Agent upgrade node is finished, checking the local upgrade package; when the upgrade end sends the progress percentage again, the OTA Agent upgrade node feeds the downloading completion result back to the upgrade end, and the state is transferred to 'downloading completion'.
In an alternative embodiment, step S106 may be further implemented by the following steps, including:
step 4.1), receiving an upgrade driving instruction sent by an upgrade terminal, uploading upgrade starting information to a cloud server, and transferring the state of an upgrade node to upgrade;
here, the OTA Agent upgrade node is driven by an upgrade start instruction, and the message of "the vehicle end starts to upgrade" is transmitted safely through the pipe end, reported to the cloud Server OTA Server, and the state is transferred into "update".
Step 4.2), when the upgrade terminal completes the upgrade operation of the ECU based on the upgrade package, receiving a complete upgrade driving instruction sent by the upgrade terminal, uploading a complete upgrade message to the cloud server, and transferring the state of the upgrade node to an upgrade completion state;
the OTA Agent upgrading node is driven by an upgrading end command, and the message of 'vehicle end finishing upgrading' is transmitted safely through the end of the pipe and reported to the cloud Server OTA Server, and the state of the upgrading node is transferred into 'upgrading finishing';
step 4.3), if each ECU corresponding to the upgrade package is upgraded, the state of the upgrade node is transferred to an idle state.
Here, if no other upgrade task is currently performed (i.e., all ECU's in the upgrade package are upgraded), the upgrade node state is restored to "idle", and the OTA Agent upgrade node is silent, and waits for the next upgrade task.
As an alternative embodiment, the one by one mode may be used for upgrading, where the ECUs to be upgraded have strong mutual dependence and may cause interference. The upgrade process of each ECU is in different upgrade tasks in the cloud Server OTA Server. The upgrade of each ECU is sequential, the version is dependent, and in order to avoid the occurrence of the situation, the upgrade is performed by adopting a one by one mode. Each ECU of the mode corresponds to different upgrade packages respectively, a state machine of the OTA Agent at the vehicle end is distinguished by task IDs except for an idle state, and multiple task driving is adapted, wherein the specific processing flow is as follows:
step 5.1), the initial state of the OTA Agent upgrading node is idle, and an upgrading end waits for initiating query information;
step 5.2), the OTA Agent upgrading node is driven by query information, establishes connection with the cloud Server OTA Server, and reports the ECU to be upgraded, related ECU information and necessary vehicle information in the query information message. After receiving upgrade information of correct response of the cloud Server OTA Server, feeding the upgrade information back to an upgrade end, and marking the state of each task as a 'ready to upgrade' state by an OTA Agent upgrade node according to the task ID;
And 5.3), the upgrading terminal transmits a downloading start instruction to drive the OTA Agent upgrading node according to the task ID. The OTA Agent upgrading node searches an upgrading task downloading address issued from the server according to the task ID, and starts to download an upgrading packet and shifts the corresponding task ID state into downloading;
step 5.4), in the downloading process of the OTA Agent upgrading packet, the upgrading end obtains the upgrading progress according to the task ID sending progress percentage instruction, and the OTA Agent upgrading node feeds back the downloading progress. After the downloading of the upgrade package of the OTA Agent upgrade node is finished, the local upgrade package verification is finished, and when the upgrade end sends the progress percentage again, the OTA Agent upgrade node feeds back the downloading result to the upgrade end, and the upgrade node state is transferred into 'downloading finished';
step 5.5), the OTA Agent upgrading node is driven by an upgrade starting instruction, and the message of 'vehicle end upgrade starting' is transmitted safely through the pipe end and reported to the cloud Server OTA Server, and the state of the upgrading node is transferred into 'upgrade';
step 5.6), the OTA Agent upgrading node is driven by an upgrading end command, and the message of 'the vehicle end finishing upgrading' is transmitted safely through the pipe end and reported to the cloud Server OTA Server, and the state of the upgrading node is transferred into 'upgrading finishing';
Step 5.7), the OTA Agent upgrading node judges whether other upgrading tasks exist at present, if so, the step 5.3 is shifted to, if not, the state is restored to be idle, the OTA Agent is silent, and the next updating task is waited.
The task ID is generated by the cloud server based on the query information, and the cloud server records the task ID as a unique identifier corresponding to the updated ECU. As an optional embodiment, the upgrade node sends a request for obtaining the recorded content of the task ID1 to the cloud server, and the cloud server determines the target content based on the task ID 1.
In an alternative implementation manner, the method in the embodiment of the present invention further includes:
step 6.1), responding to a termination driving instruction sent by the upgrading end, and transferring the state of the upgrading node to an upgrading completion state.
For example, the upgrade node of the OTA Agent state machine is in a state of 'ready for upgrade', the upgrade end interacts with a user, or other reasons cancel and terminate downloading, a download canceling downlink command is notified to the OTA Agent upgrade node, the OTA Agent upgrade node is driven, the upgrade node enters into a state of 'upgrade completion', and it is judged that no other upgrade task exists, and the state is switched to 'idle';
For another example, the upgrade node of the OTA Agent state machine is in a "downloading" state, the upgrade end interacts with the user, or the upgrade end interrupts the downloading for other reasons, the download canceling download is notified to the OTA Agent upgrade node, the OTA Agent upgrade node is driven, the upgrade node state enters into an "upgrade completion", it is judged that no other upgrade task exists, and the upgrade node state is transferred to an "idle" state;
for another example, the upgrade node of the OTA Agent state machine is in a "download complete" state, the upgrade end interacts with the user, or other reasons cancel the upgrade, notify the OTA Agent of canceling the download of the upgrade, the OTA Agent is driven, the state enters into the "upgrade complete" state, and it is determined that no other upgrade task exists, and the upgrade node state is transferred to "idle".
Aiming at the difference of the OTA at the vehicle end, the embodiment of the invention is based on a finite state machine and supports different vehicle end upgrading processes, thereby realizing a self-adaptive OTA vehicle end upgrading mode and meeting the OTA whole vehicle upgrading requirements of different host factories. Meanwhile, the embodiment of the invention decouples the upgrading end of the vehicle end from the processing flow of the OTA cloud server, so that the offline refreshing program originally developed by the host factory can be reused to a great extent on the basis of adopting an OTA upgrading mode.
As shown in fig. 3, the embodiment of the present invention further provides an OTA upgrade adaptive method of a finite state machine, which is applied to a cloud side, a vehicle side and a user side, wherein the cloud side includes a cloud Server OTA Server, the vehicle side includes an OTA Agent, the finite state machine configures an upgrade node and an Update app upgrade end of an OTA Agent process, the user side may include an intelligent terminal, and the user may also directly interact with the upgrade end in the vehicle side, and specifically includes the following steps:
step S201, preparing an upgrade package by a cloud server;
step S202, upgrading node is powered on and started, waiting for inquiry information;
step S203, the upgrade terminal sends a query message to the upgrade node, queries the upgrade version, and waits for a query result;
step S204, the upgrade node establishes connection with a cloud server, and inquires about an upgrade task;
step S205, the cloud server returns upgrade information to the upgrade node;
step S206, the upgrade node returns upgrade information to the upgrade terminal;
step S207, the upgrading terminal initiates a query to the intelligent terminal at the user side, and whether to download or not;
step S2071, if the user side sends a command for canceling downloading to the upgrading end;
step S20711, the upgrade end sends a cancel download instruction to the upgrade node;
Step S20712, the upgrade node reports a cancel download instruction to the cloud server;
step S20713, the cloud server displays a cancel download instruction through the web;
step S208, if the user side sends a downloading starting instruction to the upgrading end;
step S209, the upgrade end sends a download starting instruction to the upgrade node;
step S210, the upgrade node starts downloading based on the instruction;
step S211, the upgrade node reports a downloading start instruction to the cloud server;
step S212, the cloud server displays a downloading start instruction through the web;
step S213, the upgrade node returns the download status to the upgrade terminal;
step S214, the upgrade terminal obtains the downloading progress;
step S215, the upgrade node returns the download progress to the upgrade terminal;
step S216, the upgrade terminal displays the downloading progress to the user side;
step S2161, if the user side sends a command for canceling the download to the upgrading end;
step S2162, the upgrade terminal sends a cancel download instruction to the upgrade node;
step S2163, the upgrade node reports a cancel download instruction to the cloud server;
step S2164, the cloud server displays a cancel download instruction through the web;
step S217, if the downloading is completed at this time, the upgrading node informs the upgrading end of the completion of the downloading;
Step S218, if the downloading is completed at this time, the upgrade node reports the completion of the downloading of the cloud server;
step S219, the cloud server displays a downloading completion instruction through the web;
step S220, the upgrade end processes the downloading operation;
step S221, the upgrading terminal initiates a query to the user side, and whether to upgrade or not;
step S2211, if the user side sends to cancel the upgrade to the upgrade side;
step S2212, the upgrade terminal sends an upgrade canceling instruction to the upgrade node;
step S2213, the upgrade node reports an upgrade canceling instruction to the cloud server;
step S2214, the cloud server displays a cancel upgrade instruction through the web;
step S222, if the user side sends to start upgrading to the upgrading end;
step S223, the upgrading end processes the upgrade;
step S224, the upgrade end sends an upgrade starting instruction to the upgrade node;
step S225, the upgrade node reports an upgrade starting instruction to the cloud server;
step S226, the cloud server displays an upgrade starting instruction through the web;
step S227, the upgrade terminal displays the upgrade progress to the user;
step S228, the upgrade end sends an upgrade end instruction to the upgrade node;
step S229, the upgrade node reports an upgrade end result to the cloud server;
step S230, the cloud server displays an upgrade ending result through the web;
Step S231, the cloud server returns a cloud response result to the upgrade node;
step S232, the upgrade node returns a cloud response result to the upgrade terminal.
As shown in fig. 4, an embodiment provides an OTA upgrade apparatus 400 based on a finite state machine, applied to an upgrade node of a vehicle-end finite state machine, where the upgrade node is deployed with an OTA upgrade proxy process, the apparatus includes:
the query module 401 establishes communication connection with a cloud server if the upgrade node is in an idle state and receives query information sent by an upgrade end, and is used for sending the query information to the cloud server so that the cloud server determines upgrade information according to the query information, wherein the query information comprises vehicle information, ECU version information, ECU types and ECU quantity, and the cloud server configures upgrade information corresponding to each type of ECU in advance;
the downloading module 402 is configured to respond to a downloading driving instruction sent by the upgrade terminal, complete a downloading operation of an upgrade package according to the upgrade information, change a state of the upgrade node to a downloading completion state, and feed back a downloading completion result to the upgrade terminal, so that the upgrade terminal upgrades the ECU based on the upgrade package;
And the upgrade module 403 is configured to respond to an upgrade completion driving instruction sent by the upgrade terminal, and if all the ECUs corresponding to the upgrade package are upgraded, switch the state of the upgrade node to an idle state, where the upgrade completion driving instruction is sent by the upgrade terminal under the condition that the upgrade operation of the ECU is completed.
In an optional embodiment, the upgrade module is further specifically configured to connect with an upper computer, and obtain an offline upgrade package in the upper computer; and sending the offline upgrade package to the upgrade terminal so that the upgrade terminal performs upgrade based on the offline upgrade package.
In an optional embodiment, the upgrade package corresponds to one or more ECU upgrade tasks, and if the upgrade package corresponds to one ECU upgrade task, the upgrade information includes a task ID generated by the cloud server according to the query information.
In an optional embodiment, the system further includes a preparation module, configured to receive the upgrade information sent by the cloud server, feed back the upgrade information to an upgrade end, and change the state of the upgrade node to a state of preparing for upgrade.
In an optional implementation manner, the downloading module is further specifically configured to receive a start downloading driving instruction sent by the upgrade end, download an upgrade package according to a download address in the upgrade information, and transfer the state of the upgrade node to a downloading state; receiving a downloading progress acquisition instruction sent by the upgrading end, and feeding back the downloading progress of the upgrading packet to the upgrading end; if the upgrade package is downloaded and the upgrade package after the download is checked, feeding back the downloaded result to the upgrade terminal, and transferring the state of the upgrade node to a download completion state.
In an optional embodiment, the upgrade module is further specifically configured to receive an upgrade driving instruction sent by the upgrade end, upload upgrade start information to the cloud server, and transfer the state of the upgrade node to upgrade; when the upgrade terminal completes the upgrade operation of the ECU based on the upgrade package, receiving an upgrade completion driving instruction sent by the upgrade terminal, uploading an upgrade completion message to the cloud server, and transferring the state of the upgrade node to an upgrade completion state; and if each ECU corresponding to the upgrade package is upgraded, transferring the state of the upgrade node to an idle state.
In an optional embodiment, the upgrade module is further specifically configured to respond to a termination driving instruction sent by the upgrade end, and change the state of the upgrade node to an upgrade completion state.
Fig. 5 is a schematic hardware architecture of an electronic device 500 according to an embodiment of the present invention. Referring to fig. 5, the electronic device 500 includes: a machine-readable storage medium 501 and a processor 502, and may also include a non-volatile storage medium 503, a communication interface 504, and a bus 505; wherein the machine-readable storage medium 501, the processor 502, the non-volatile storage medium 503, and the communication interface 504 accomplish communication with each other via the bus 505. The processor 502 may perform the finite state machine based OTA upgrade method described in the above embodiments by reading and executing the finite state machine based OTA upgrade adaptive machine executable instructions in the machine readable storage medium 501.
The machine-readable storage medium referred to herein may be any electronic, magnetic, optical, or other physical storage device that can contain or store information, such as executable instructions, data, or the like. For example, a machine-readable storage medium may be: RAM (Radom Access Memory, random access memory), volatile memory, non-volatile memory, flash memory, a storage drive (e.g., hard drive), any type of storage disk (e.g., optical disk, dvd, etc.), or a similar storage medium, or a combination thereof.
The non-volatile medium may be a non-volatile memory, a flash memory, a storage drive (e.g., hard drive), any type of storage disk (e.g., optical disk, dvd, etc.), or a similar non-volatile storage medium, or a combination thereof.
It can be understood that the specific operation method of each functional module in this embodiment may refer to the detailed description of the corresponding steps in the above method embodiment, and the detailed description is not repeated here.
The computer readable storage medium provided by the embodiments of the present invention stores a computer program, and when the computer program code is executed, the method for upgrading an OTA based on a finite state machine according to any one of the embodiments of the present invention may be implemented, and detailed implementation of the method embodiment will not be repeated herein.
It will be clear to those skilled in the art that, for convenience and brevity of description, specific working procedures of the above-described system and apparatus may refer to corresponding procedures in the foregoing method embodiments, which are not described herein again.
In addition, in the description of embodiments of the present invention, unless explicitly stated and limited otherwise, the terms "mounted," "connected," and "connected" are to be construed broadly, and may be, for example, fixedly connected, detachably connected, or integrally connected; can be mechanically or electrically connected; can be directly connected or indirectly connected through an intermediate medium, and can be communication between two elements. The specific meaning of the above terms in the present invention will be understood in specific cases by those of ordinary skill in the art.
In the description of the present invention, it should be noted that the directions or positional relationships indicated by the terms "center", "upper", "lower", "left", "right", "vertical", "horizontal", "inner", "outer", etc. are based on the directions or positional relationships shown in the drawings, are merely for convenience of describing the present invention and simplifying the description, and do not indicate or imply that the devices or elements referred to must have a specific orientation, be configured and operated in a specific orientation, and thus should not be construed as limiting the present invention. Furthermore, the terms "first," "second," and "third" are used for descriptive purposes only and are not to be construed as indicating or implying relative importance.
Finally, it should be noted that: the above examples are only specific embodiments of the present invention, and are not intended to limit the scope of the present invention, but it should be understood by those skilled in the art that the present invention is not limited thereto, and that the present invention is described in detail with reference to the foregoing examples: any person skilled in the art may modify or easily conceive of the technical solution described in the foregoing embodiments, or perform equivalent substitution of some of the technical features, while remaining within the technical scope of the present disclosure; such modifications, changes or substitutions do not depart from the spirit and scope of the technical solutions of the embodiments of the present invention, and are intended to be included in the scope of the present invention.
Claims (9)
1. An OTA upgrading method based on a finite state machine is characterized by being applied to upgrading nodes of the finite state machine at a vehicle end, wherein the upgrading nodes are deployed with OTA upgrading agent processes, the upgrading nodes respectively interact with upgrading ends and cloud servers at the vehicle end, and corresponding upgrading operations are automatically completed through state conversion of the upgrading nodes, and the method comprises the following steps:
If the upgrade node is in an idle state and receives query information sent by an upgrade end, communication connection is established with a cloud server, the query information is sent to the cloud server, so that the cloud server determines upgrade information according to the query information, wherein the query information comprises vehicle information, ECU version information, ECU types and the number of ECUs, and the cloud server configures upgrade information corresponding to each type of ECUs in advance;
responding to a download driving instruction sent by the upgrading end, completing the downloading operation of an upgrading packet according to the upgrading information, transferring the state of the upgrading node to a downloading completion state, and feeding back the downloading completion result to the upgrading end so that the upgrading end upgrades the ECU based on the upgrading packet;
responding to an upgrade completion driving instruction sent by the upgrade terminal, and if the ECUs corresponding to the upgrade package are all upgraded, transferring the state of the upgrade node to an idle state, wherein the upgrade completion driving instruction is sent by the upgrade terminal under the condition of completing the upgrade operation of the ECUs;
the method further comprises the steps of:
the method comprises the steps of connecting with an upper computer to obtain an offline upgrade package in the upper computer;
And sending the offline upgrade package to the upgrade terminal so that the upgrade terminal performs upgrade based on the offline upgrade package.
2. The method of claim 1, wherein the upgrade package corresponds to one or more ECU upgrade tasks, and if the upgrade package corresponds to one ECU upgrade task, the upgrade information includes a task ID generated by the cloud server according to the query information.
3. The method of claim 1, wherein prior to the step of responding to the download driver instructions sent by the upgrade side, the method further comprises:
and receiving the upgrade information sent by the cloud server, feeding the upgrade information back to an upgrade end, and transferring the state of the upgrade node to a state ready for upgrade.
4. The method according to claim 2, wherein the step of completing the downloading operation of the upgrade package according to the upgrade information in response to the download driving instruction sent by the upgrade terminal, transferring the state of the upgrade node to a download completed state, and feeding back the result of the completion of the downloading to the upgrade terminal includes:
receiving a start downloading driving instruction sent by the upgrading end, downloading an upgrading packet according to a downloading address in the upgrading information, and transferring the state of the upgrading node to a downloading state;
Receiving a downloading progress acquisition instruction sent by the upgrading end, and feeding back the downloading progress of the upgrading packet to the upgrading end;
if the upgrade package is downloaded and the upgrade package after the download is checked, feeding back the downloaded result to the upgrade terminal, and transferring the state of the upgrade node to a download completion state.
5. The method according to claim 2, wherein the step of transferring the state of the upgrade node to the idle state if the ECU corresponding to the upgrade package is upgraded in response to the upgrade completion driving instruction sent by the upgrade terminal, includes:
receiving an upgrade driving instruction sent by the upgrade end, uploading upgrade starting information to the cloud server, and transferring the state of the upgrade node to upgrade;
when the upgrade terminal completes the upgrade operation of the ECU based on the upgrade package, receiving an upgrade completion driving instruction sent by the upgrade terminal, uploading an upgrade completion message to the cloud server, and transferring the state of the upgrade node to an upgrade completion state;
and if each ECU corresponding to the upgrade package is upgraded, transferring the state of the upgrade node to an idle state.
6. The method according to claim 2, wherein the method further comprises:
and responding to a termination driving instruction sent by the upgrading end, and transferring the state of the upgrading node to an upgrading completion state.
7. An OTA upgrading device based on a finite state machine is characterized by being applied to an upgrading node of a finite state machine at a vehicle end, wherein an OTA upgrading proxy process is deployed on the upgrading node, the upgrading node respectively interacts with an upgrading end and a cloud server at the vehicle end, and corresponding upgrading operation is automatically completed through state conversion of the upgrading node, and the device comprises:
the query module is used for establishing communication connection with a cloud server if the upgrade node is in an idle state and receives query information sent by an upgrade end, and is used for sending the query information to the cloud server so that the cloud server can determine upgrade information according to the query information, wherein the query information comprises vehicle information, ECU version information, ECU types and ECU quantity, and the cloud server is pre-configured with upgrade information corresponding to each ECU;
the downloading module is used for responding to a downloading driving instruction sent by the upgrading end, completing the downloading operation of the upgrading package according to the upgrading information, transferring the state of the upgrading node to a downloading completed state, and feeding back the downloading completed result to the upgrading end so that the upgrading end upgrades the ECU based on the upgrading package;
The upgrade module is used for responding to an upgrade completion driving instruction sent by the upgrade terminal, and if the ECUs corresponding to the upgrade package are all upgraded, the state of the upgrade node is transferred to an idle state, wherein the upgrade completion driving instruction is sent by the upgrade terminal under the condition of completing upgrade operation of the ECUs;
the device is also used for connecting with an upper computer to obtain an offline upgrade package in the upper computer; and sending the offline upgrade package to the upgrade terminal so that the upgrade terminal performs upgrade based on the offline upgrade package.
8. An electronic device comprising a memory, a processor, the memory having stored therein a computer program executable on the processor, characterized in that the processor, when executing the computer program, implements the steps of the method of any of the preceding claims 1 to 6.
9. A machine-readable storage medium storing machine-executable instructions which, when invoked and executed by a processor, cause the processor to perform the steps of the method of any one of claims 1 to 6.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010552191.8A CN111722860B (en) | 2020-06-16 | 2020-06-16 | OTA upgrading method and device based on finite state machine |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010552191.8A CN111722860B (en) | 2020-06-16 | 2020-06-16 | OTA upgrading method and device based on finite state machine |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN111722860A CN111722860A (en) | 2020-09-29 |
| CN111722860B true CN111722860B (en) | 2024-02-02 |
Family
ID=72566955
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202010552191.8A Active CN111722860B (en) | 2020-06-16 | 2020-06-16 | OTA upgrading method and device based on finite state machine |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN111722860B (en) |
Families Citing this family (9)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN112286556A (en) * | 2020-10-30 | 2021-01-29 | 芯讯通无线科技（上海）有限公司 | Communication equipment and remote upgrading method of MCU thereof |
| CN112256310A (en) * | 2020-11-13 | 2021-01-22 | 上海伟世通汽车电子系统有限公司 | Vehicle instrument OTA upgrading system and method |
| CN112764780A (en) * | 2021-01-25 | 2021-05-07 | 北京华顺信安信息技术有限公司 | Application batch automatic upgrading method suitable for DCC multi-node server |
| CN113094075A (en) * | 2021-03-02 | 2021-07-09 | 厦门亿联网络技术股份有限公司 | Firmware upgrading method and device, terminal equipment and computer readable storage medium |
| CN113190250A (en) * | 2021-04-30 | 2021-07-30 | 延锋汽车饰件系统有限公司 | Cabin software upgrading method, electronic equipment and readable storage medium |
| CN113905061A (en) * | 2021-07-30 | 2022-01-07 | 联合汽车电子有限公司 | Information processing method, device, chip, diagnostic instrument, equipment and vehicle |
| CN113656061B (en) * | 2021-08-20 | 2023-12-15 | 成都亨通光通信有限公司 | 5G communication power supply firmware updating method and updating device |
| CN114003262A (en) * | 2021-11-11 | 2022-02-01 | 镁佳(北京)科技有限公司 | Online upgrade control method, device and equipment based on finite-state machine |
| CN115051919B (en) * | 2022-06-30 | 2024-07-12 | 深圳市云洲创新科技有限公司 | OTA upgrading system and OTA upgrading method |
Citations (15)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| DE102016210676A1 (en) * | 2015-06-16 | 2016-12-22 | Lear Corporation | A method of updating ECUs using differential update packages |
| CN106325947A (en) * | 2016-09-18 | 2017-01-11 | 北京方研矩行科技有限公司 | Method for upgrading OTA (over-the-air technology) firmware based on state machine |
| CN106385420A (en) * | 2016-09-29 | 2017-02-08 | 中国联合网络通信集团有限公司 | ECU software download method and device |
| CN108769226A (en) * | 2018-06-05 | 2018-11-06 | 北京智行者科技有限公司 | The OAT upgrade methods and car-mounted terminal of vehicle |
| CN108810082A (en) * | 2018-04-24 | 2018-11-13 | 江苏金坛长荡湖新能源科技有限公司 | A kind of new-energy automobile control module remotely writes with a brush dipped in Chinese ink method |
| CN110032382A (en) * | 2019-03-25 | 2019-07-19 | 深圳猛犸电动科技有限公司 | A kind of vehicle electronic control unit upgrade method, system and terminal device |
| CN110224907A (en) * | 2018-03-01 | 2019-09-10 | 上海汽车集团股份有限公司 | A kind of updating system of vehicle-mounted ECU, method and terminal |
| CN110365510A (en) * | 2018-04-10 | 2019-10-22 | 上海仪电（集团）有限公司中央研究院 | It is a kind of can to network node batch OTA upgrade things-internet gateway and OTA upgrade method |
| CN110928567A (en) * | 2019-11-27 | 2020-03-27 | 安徽江淮汽车集团股份有限公司 | Vehicle system upgrading method, terminal device and computer-readable storage medium |
| CN110955444A (en) * | 2019-12-04 | 2020-04-03 | 福尔达车联网（深圳）有限公司 | Vehicle ECU upgrading method, system, terminal and storage medium |
| CN111031115A (en) * | 2019-11-28 | 2020-04-17 | 安徽江淮汽车集团股份有限公司 | Electronic controller version updating system and method based on Internet of vehicles |
| CN111061499A (en) * | 2019-12-31 | 2020-04-24 | 上海赫千电子科技有限公司 | ECU updating method and system based on file system |
| CN111158718A (en) * | 2019-12-26 | 2020-05-15 | 智车优行科技（北京）有限公司 | Local communication server, OTA (over the air) upgrading method thereof and cloud server |
| CN111190633A (en) * | 2020-01-03 | 2020-05-22 | 东风汽车集团有限公司 | OTA (over the air) upgrading system and method for whole electric control unit |
| CN111258611A (en) * | 2020-01-22 | 2020-06-09 | 重庆长安汽车股份有限公司 | Method for upgrading firmware of whole vehicle in air |
Family Cites Families (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| JP6722198B2 (en) * | 2015-05-14 | 2020-07-15 | エアビクティ インコーポレイテッド | Centralized management system for mobile-assisted vehicle software updates and vehicle data analysis |
| US11204750B2 (en) * | 2018-03-30 | 2021-12-21 | Intel Corporation | Systems, methods and apparatus for distributed software/firmware update and software versioning system for automated vehicles |
| US11528330B2 (en) * | 2018-12-06 | 2022-12-13 | Ford Global Technologies, Llc | Upgradeable vehicle |
-
2020
- 2020-06-16 CN CN202010552191.8A patent/CN111722860B/en active Active
Patent Citations (15)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| DE102016210676A1 (en) * | 2015-06-16 | 2016-12-22 | Lear Corporation | A method of updating ECUs using differential update packages |
| CN106325947A (en) * | 2016-09-18 | 2017-01-11 | 北京方研矩行科技有限公司 | Method for upgrading OTA (over-the-air technology) firmware based on state machine |
| CN106385420A (en) * | 2016-09-29 | 2017-02-08 | 中国联合网络通信集团有限公司 | ECU software download method and device |
| CN110224907A (en) * | 2018-03-01 | 2019-09-10 | 上海汽车集团股份有限公司 | A kind of updating system of vehicle-mounted ECU, method and terminal |
| CN110365510A (en) * | 2018-04-10 | 2019-10-22 | 上海仪电（集团）有限公司中央研究院 | It is a kind of can to network node batch OTA upgrade things-internet gateway and OTA upgrade method |
| CN108810082A (en) * | 2018-04-24 | 2018-11-13 | 江苏金坛长荡湖新能源科技有限公司 | A kind of new-energy automobile control module remotely writes with a brush dipped in Chinese ink method |
| CN108769226A (en) * | 2018-06-05 | 2018-11-06 | 北京智行者科技有限公司 | The OAT upgrade methods and car-mounted terminal of vehicle |
| CN110032382A (en) * | 2019-03-25 | 2019-07-19 | 深圳猛犸电动科技有限公司 | A kind of vehicle electronic control unit upgrade method, system and terminal device |
| CN110928567A (en) * | 2019-11-27 | 2020-03-27 | 安徽江淮汽车集团股份有限公司 | Vehicle system upgrading method, terminal device and computer-readable storage medium |
| CN111031115A (en) * | 2019-11-28 | 2020-04-17 | 安徽江淮汽车集团股份有限公司 | Electronic controller version updating system and method based on Internet of vehicles |
| CN110955444A (en) * | 2019-12-04 | 2020-04-03 | 福尔达车联网（深圳）有限公司 | Vehicle ECU upgrading method, system, terminal and storage medium |
| CN111158718A (en) * | 2019-12-26 | 2020-05-15 | 智车优行科技（北京）有限公司 | Local communication server, OTA (over the air) upgrading method thereof and cloud server |
| CN111061499A (en) * | 2019-12-31 | 2020-04-24 | 上海赫千电子科技有限公司 | ECU updating method and system based on file system |
| CN111190633A (en) * | 2020-01-03 | 2020-05-22 | 东风汽车集团有限公司 | OTA (over the air) upgrading system and method for whole electric control unit |
| CN111258611A (en) * | 2020-01-22 | 2020-06-09 | 重庆长安汽车股份有限公司 | Method for upgrading firmware of whole vehicle in air |
Non-Patent Citations (3)
| Title |
|---|
| ECU Software Updating Scenario Using OTA Technology through Mobile Communication Network;B. Kim等;《2018 IEEE 3rd International Conference on Communication and Information Systems (ICCIS)》;67-72 * |
| 整车OTA系统中的车身动力域ECU升级与软件匹配;冯万军等;《2019中国汽车工程学会年会论文集》;259-263 * |
| 智能网联汽车整车OTA功能设计研究;王栋梁等;《汽车技术》(第10期);29-33 * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN111722860A (en) | 2020-09-29 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN111722860B (en) | OTA upgrading method and device based on finite state machine | |
| CN110377307A (en) | A kind of car body controller firmware upgrade method, terminal, system | |
| US20050090942A1 (en) | System and method to load vehicle operation software and calibration data in general assembly and service environment | |
| CN111061499A (en) | ECU updating method and system based on file system | |
| CN110442363B (en) | Vehicle ECU upgrading control method | |
| US20200110406A1 (en) | Vehicle software check | |
| CN111610993A (en) | Firmware upgrading method, server and system | |
| CN113497819A (en) | Remote upgrade security guarantee method and system and vehicle-mounted Tbox equipment | |
| CN213303011U (en) | OTA-based vehicle ECU upgrading system | |
| US20240069906A1 (en) | Server, software update system, distribution method, and non-transitory storage medium | |
| CN114363385B (en) | Method, system, equipment and storage medium for updating automobile end software by cloud | |
| CN115291907A (en) | Vehicle upgrading method, device and system | |
| US20220066768A1 (en) | Software update device, update control method, and non-transitory storage medium | |
| KR20180086907A (en) | System and method for updating firmware of blackbox for vehicle | |
| CN113791800A (en) | Automatic parking control module remote upgrading method and system and automobile | |
| CN113630437A (en) | Vehicle control unit upgrading method and device and vehicle | |
| US20240118886A1 (en) | Mobile equipment and software distribution system | |
| US20240103839A1 (en) | Mobile terminal and software distribution system | |
| US20240118885A1 (en) | User equipment, software update system, control method, and non-transitory storage medium | |
| WO2022249846A1 (en) | Vehicular electronic control device and update program | |
| US20220391193A1 (en) | Ota master, system, method, non-transitory storage medium, and vehicle | |
| US11972248B2 (en) | Controlling software update of electronic control units mounted on a vehicle | |
| CN116450172A (en) | Vehicle OTA upgrading method and system, vehicle network terminal, HMI terminal and storage medium | |
| US20230033832A1 (en) | System, center, method, and non-transitory storage medium | |
| US20240069893A1 (en) | Server, software update system, software update method, and non-transitory 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 | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |