CN113094073B - Vehicle remote upgrading method, device and server - Google Patents
Vehicle remote upgrading method, device and server Download PDFInfo
- Publication number
- CN113094073B CN113094073B CN202110472386.6A CN202110472386A CN113094073B CN 113094073 B CN113094073 B CN 113094073B CN 202110472386 A CN202110472386 A CN 202110472386A CN 113094073 B CN113094073 B CN 113094073B
- Authority
- CN
- China
- Prior art keywords
- upgrading
- software
- vehicle
- rollback
- package
- 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 35
- 238000009434 installation Methods 0.000 claims abstract description 44
- 230000002159 abnormal effect Effects 0.000 claims description 8
- 238000012800 visualization Methods 0.000 claims description 4
- 238000005516 engineering process Methods 0.000 abstract description 7
- 238000007726 management method Methods 0.000 description 7
- 238000012360 testing method Methods 0.000 description 6
- 238000010586 diagram Methods 0.000 description 4
- 230000006870 function Effects 0.000 description 4
- 230000008569 process Effects 0.000 description 4
- 238000012550 audit Methods 0.000 description 3
- 239000003795 chemical substances by application Substances 0.000 description 3
- 230000009467 reduction Effects 0.000 description 3
- 230000000007 visual effect Effects 0.000 description 3
- 238000003491 array Methods 0.000 description 2
- 239000000463 material Substances 0.000 description 2
- 230000005856 abnormality Effects 0.000 description 1
- 125000002015 acyclic group Chemical group 0.000 description 1
- 230000006399 behavior Effects 0.000 description 1
- 238000006243 chemical reaction Methods 0.000 description 1
- 230000004069 differentiation Effects 0.000 description 1
- 230000005059 dormancy Effects 0.000 description 1
- 238000012423 maintenance Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 238000012544 monitoring process Methods 0.000 description 1
- 238000002360 preparation method Methods 0.000 description 1
- 230000002618 waking effect Effects 0.000 description 1
- XLYOFNOQVPJJNP-UHFFFAOYSA-N water Substances O XLYOFNOQVPJJNP-UHFFFAOYSA-N 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
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/60—Software deployment
- G06F8/61—Installation
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/70—Software maintenance or management
- G06F8/71—Version control; Configuration management
Abstract
The application discloses a vehicle remote upgrading method, device and server, wherein the method comprises the following steps: determining application software definition of one or more control domains of a vehicle to be upgraded according to a plurality of control domain software definitions based on the whole vehicle type division; determining an installation package, a differential package and/or a rollback package according to the release version identification of the application software definition; and upgrading the software corresponding to the upgrading instruction according to the installation package, the differential package and/or the rollback package. Therefore, the problems that the remote upgrading scheme in the related technology cannot accurately determine all software versions and the dependency relationship among the software, upgrading configuration errors are easy to occur, upgrading cannot be performed, upgrading reliability and efficiency are reduced, user experience is poor and the like are solved.
Description
Technical Field
The present disclosure relates to the field of vehicle technologies, and in particular, to a method, an apparatus, and a server for remote upgrade of a vehicle.
Background
Along with the continuous upgrading of vehicle technology, the architecture of the existing automobile electronic and electric appliance is upgraded, the upgrading and updating of related domain controllers and ECU application software are more frequent, and the dependency relationship among the software is tighter.
In the related art, the remote upgrade scheme is as follows: the upgrade operations of the single and multiple ECU (Electronic Control Unit ) software are managed in an upgrade task manner.
However, the remote upgrade scheme in the related art cannot accurately determine all software versions and dependency relationships among the software, and is prone to configuration errors during upgrade, so that upgrade cannot be completed, reliability and efficiency of remote upgrade are reduced, user experience is poor, and the problem needs to be solved.
Content of the application
The application provides a vehicle remote upgrading method, device and server, which are used for solving the problems that a remote upgrading scheme in the related technology cannot accurately determine all software versions and dependency relations among software, upgrading configuration errors are easy to occur, upgrading cannot be performed, upgrading reliability and efficiency are reduced, user experience is poor and the like.
An embodiment of a first aspect of the present application provides a vehicle remote upgrade method, including the following steps: determining application software definition of one or more control domains of a vehicle to be upgraded according to a plurality of control domain software definitions based on the whole vehicle type division; determining an installation package, a differential package and/or a rollback package according to the release version identification of the application software definition; and upgrading the software corresponding to the upgrading instruction according to the installation package, the differential package and/or the rollback package.
Further, the upgrading the software corresponding to the upgrade instruction according to the installation package, the differential package and/or the rollback package includes: generating a whole vehicle software upgrading strategy of the vehicle to be upgraded according to the upgrading instruction; configuring at least one piece of software to be upgraded according to the whole vehicle software upgrading strategy, and configuring version identification, upgrading operation and the installation package of each piece of software to be upgraded; configuring the upgrading sequence and the rollback sequence of each piece of software to be upgraded according to the differential packet and the rollback packet, calculating the storage size occupied by all pieces of software upgrading packet, and generating an upgrading instruction message and a rollback instruction message to form upgrading data; and sending the upgrade data to the vehicle to be upgraded so as to execute upgrade operation based on the upgrade data.
Further, the method of the embodiment of the application further comprises the following steps: generating a directed acyclic graph according to the upgrading sequence and the rollback sequence, and converting the directed acyclic graph into a tree structure so as to visualize the upgrading sequence and the rollback sequence.
Further, the method of the embodiment of the application further comprises the following steps: receiving a current upgrading flow and an upgrading result fed back by the vehicle to be upgraded; and determining a final upgrading result of the vehicle to be upgraded according to the current upgrading flow and the upgrading result.
Further, the method of the embodiment of the application further comprises the following steps: detecting whether the vehicle to be upgraded is abnormal or not, and executing the installation operation of the rollback software package according to the rollback message; and if the installation operation is not executed, carrying out fault reminding while carrying out upgrading failure reminding.
An embodiment of a second aspect of the present application provides a vehicle remote upgrade apparatus, including: the dividing module is used for determining one or more control domain affiliated application software definitions of the vehicle to be upgraded according to a plurality of control domain software definitions divided based on the whole vehicle type; the determining module is used for determining an installation package, a differential package and/or a rollback package according to the release version identification of the application software definition; and the upgrading module is used for upgrading the software corresponding to the upgrading instruction according to the installation package, the differential package and/or the rollback package.
Further, the upgrade module includes: the generation unit is used for generating an entire vehicle software upgrading strategy of the vehicle to be upgraded according to the upgrading instruction; the first configuration unit is used for configuring at least one piece of software to be upgraded according to the whole vehicle software upgrading strategy, and configuring the version identification, upgrading operation and the installation package of each piece of software to be upgraded; the second configuration unit is used for configuring the upgrading sequence and the rollback sequence of each piece of software to be upgraded according to the difference packet and the rollback packet, calculating the storage size occupied by all pieces of software upgrading packet, and generating an upgrading instruction message and a rollback instruction message to form upgrading data; and the upgrading unit is used for sending the upgrading data to the vehicle to be upgraded so as to execute upgrading operation based on the upgrading data.
Further, the device of the embodiment of the application further comprises: and the visualization module is used for generating a directed acyclic graph according to the upgrading sequence and the rollback sequence, and converting the directed acyclic graph into a tree structure so as to visualize the upgrading sequence and the rollback sequence.
Further, the device of the embodiment of the application further comprises: the receiving module is used for receiving the current upgrading flow and the upgrading result fed back by the vehicle to be upgraded and determining the final upgrading result of the vehicle to be upgraded according to the current upgrading flow and the upgrading result; and the reminding module is used for detecting whether the vehicle to be upgraded is abnormal or not, executing the installation operation of the rollback software package according to the rollback message, and carrying out fault reminding while carrying out upgrading failure reminding if the installation operation is not executed.
An embodiment of a third aspect of the present application provides a server, which includes the vehicle remote upgrade device described above.
The unified upgrade management of the whole vehicle software is realized in a software definition mode, the direct dependence relationship of all software versions of the vehicle and the software can be accurately determined, the problem of configuration errors caused by unclear dependence relationship when a plurality of software is upgraded simultaneously is avoided, a plurality of software can be upgraded reliably and remotely at the same time, the reliability and the efficiency of remote upgrade are effectively improved, and the use experience of a user is improved. Therefore, the problems that the remote upgrading scheme in the related technology cannot accurately determine all software versions and the dependency relationship among the software, upgrading configuration errors are easy to occur, upgrading cannot be performed, upgrading reliability and efficiency are reduced, user experience is poor and the like are solved.
Additional aspects and advantages of the application will be set forth in part in the description which follows and, in part, will be obvious from the description, or may be learned by practice of the application.
Drawings
The foregoing and/or additional aspects and advantages of the present application will become apparent and readily appreciated from the following description of the embodiments, taken in conjunction with the accompanying drawings, in which:
fig. 1 is a schematic structural diagram of a vehicle remote upgrade system provided according to an embodiment of the present application;
FIG. 2 is a flow chart of a method for remote upgrade of a vehicle according to an embodiment of the present application;
FIG. 3 is a diagram illustrating conversion of a DAG graph into an upgrade order according to embodiments of the present application;
FIG. 4 is a flow chart of a method for remote upgrade of a vehicle according to one embodiment of the present application;
FIG. 5 is a flowchart of a vehicle-side download upgrade package policy according to one embodiment of the present application;
FIG. 6 is a flow chart of a vehicle side performing upgrade policies according to one embodiment of the present application;
fig. 7 is a block schematic diagram of a vehicle remote upgrade apparatus according to an embodiment of the present application.
Detailed Description
Embodiments of the present application are described in detail below, examples of which are illustrated in the accompanying drawings, wherein the same or similar reference numerals refer to the same or similar elements or elements having the same or similar functions throughout. The embodiments described below by referring to the drawings are exemplary and intended for the purpose of explaining the present application and are not to be construed as limiting the present application.
Before introducing the vehicle remote upgrading method, device and server of the embodiment of the application, the upgrading system of the embodiment of the application is described, as shown in fig. 1, the upgrading system comprises a server side and a vehicle side upgrading management client side, wherein the server side consists of an application server, a database, a service gateway and a file server; the vehicle end consists of a software package download agent, a package restoration unit, an upgrade management unit, an upgrade instruction execution unit and a data embedding unit.
The service gateway is a server which directly provides a service interface to the outside; the application server provides actual program and logic implementation of the service interface and provides timing execution program implementation; storing vehicle types, vehicle information, upgrade application version information, vehicle version information, upgrade strategy configuration information, application upgrade real vehicle test records, vehicle upgrade session log running water information, various data reports and the like; the file server stores software package files such as application atom software packages, differential packages, rollback packages and the like. The software package download agent is responsible for downloading all atomic software packages or differential packages which need to be downloaded in the upgrade instruction; the packet reduction unit is responsible for merging the differential packet and the old atomic packet into a new atomic packet according to a differential algorithm.
The following describes a vehicle remote upgrading method, device and server according to the embodiments of the present application with reference to the accompanying drawings. Aiming at the problems that the remote upgrading scheme in the related technology mentioned in the background technology center cannot accurately determine all software versions and the dependency relationship between the software, the problem that the upgrading configuration errors cannot be upgraded easily occurs, the upgrading reliability and efficiency are reduced, and the user experience is poor, the application provides a vehicle remote upgrading method. Therefore, the problems that the remote upgrading scheme in the related technology cannot accurately determine all software versions and the dependency relationship among the software, upgrading configuration errors are easy to occur, upgrading cannot be performed, upgrading reliability and efficiency are reduced, user experience is poor and the like are solved.
Specifically, fig. 2 is a schematic flow chart of a vehicle remote upgrade method according to an embodiment of the present application.
As shown in fig. 2, the vehicle remote upgrade method includes the steps of:
in step S101, an application software definition to which one or more control domains of a vehicle to be upgraded belong is determined according to a plurality of control domain software definitions based on the vehicle model overall division.
The vehicle to be upgraded can be understood as a specified vehicle type to be upgraded in the embodiment of the application.
In this embodiment, in the software upgrade application service platform, the whole vehicle to be upgraded is divided into a plurality of control domain software definitions, and application software to which each control domain belongs is defined as an application. Specifically: defining a software application, namely defining whole vehicle software or local domain controller software through software application identification information; and the association relation between the software application and the vehicle type is configured, so that the range of the upgradeable software application package of the vehicle type is defined.
In step S102, an installation package, a differential package, and/or a rollback package is determined according to the release version identification of the belonging application software definition.
The release version identifier can be a release version number, the release version number defined by each application is maintained after the application is defined, and each application version corresponds to a group of software atom installation packages, software differentiation packages and software rollback packages.
In this embodiment, when upgrading the whole vehicle software of a specified vehicle type, firstly, generating a whole vehicle software upgrading policy number, and configuring an ECU application software list included in the upgrade according to the policy number; and then configuring version numbers of the application software, whether forced upgrading is carried out or not, a software package file, and generating a version differential package and a rollback package.
In step S103, the software corresponding to the upgrade instruction is upgraded according to the installation package, the differential package and/or the rollback package.
In this embodiment, upgrading software corresponding to an upgrade instruction according to an installation package, a differential package and/or a rollback package includes: generating a whole vehicle software upgrading strategy of the vehicle to be upgraded according to the upgrading instruction; configuring at least one piece of software to be upgraded according to a whole vehicle software upgrading strategy, and configuring a version identifier, upgrading operation and an installation package of each piece of software to be upgraded; configuring an upgrading sequence and a rollback sequence of each piece of software to be upgraded according to the differential packets and the rollback packets, calculating the storage size occupied by all the software upgrading packets, and generating an upgrading instruction message and a rollback instruction message to form upgrading data; and sending the upgrade data to the vehicle to be upgraded so as to execute upgrade operation based on the upgrade data.
Wherein, the configuration upgrade policy is: and generating a directed acyclic graph according to the upgrading sequence and the rollback sequence, and converting the directed acyclic graph into a tree structure so as to visualize the upgrading sequence and the rollback sequence. For example, the order of converting the graphically configured DAG graph into the executable upgrade policy in the embodiments of the present application may be as shown in fig. 3, where the S4-1 DAG graph is converted into the S4-2 tree data structure by a deep traversal algorithm, and the S4-2 tree data structure is obtained by a layer sequence traversal algorithm to obtain the upgrade task execution policy list S4-3.
It can be understood that, in the embodiment of the present application, DAG graphs (directed acyclic graphs) of the software upgrade order and the rollback order are configured, the storage size occupied by all the software upgrade packages is calculated, an upgrade instruction message is generated, a rollback instruction message is generated, an upgrade vehicle list is set, and a message is pushed to an OTA upgrade proxy service of a vehicle to be upgraded through a push pipeline of the MQTT protocol service.
Specifically, (1) configuring an upgrade strategy, managing upgrade execution sequences of a plurality of software packages in a graphical mode, automatically converting a DAG graph into a tree structure by a system, converting the DAG graph into the software package upgrade sequences in a layer sequence tree node traversing mode, and obtaining a rollback sequence in a queue convenient mode;
(2) Configuring a vehicle to be upgraded, and triggering the vehicle to be upgraded to verify an upgrade strategy in a mode of pushing an upgrade notice to the vehicle to be upgraded;
(3) Configuring a gray level release strategy, and releasing a new software version in a certain range by designating an upgrade vehicle, an upgrade area and the like;
(4) Configuring an upgrade timing task, and pushing an upgrade notification message to a vehicle to be upgraded at fixed time so as to trigger and start an upgrade session of the vehicle end.
In some embodiments, the method of embodiments of the present application further comprises: receiving a current upgrading flow and an upgrading result fed back by a vehicle to be upgraded; and determining the final upgrading result of the vehicle to be upgraded according to the current upgrading flow and the upgrading result.
The vehicle end downloads the upgrade instruction message and the rollback instruction message, judges whether the execution instruction can be executed according to the upgrade instruction message, and executes the instructions of software package downloading, software package merging, software package installing and the like to determine the final upgrade result.
Specifically, after the vehicle side receives the upgrade notification, firstly, the upgrade management unit requests the server side gateway to obtain a target version of the vehicle application to be upgraded, and the server side gateway is requested to obtain an upgrade strategy file and a rollback strategy file according to the local version and the target version, and the upgrade session record and the execution state of the current vehicle are sent to the service gateway through the data embedding unit; then, the vehicle-end software package download agent circularly downloads the differential package according to the upgrade strategy file, the package reduction unit combines the differential package and the local old atomic package into a new atomic package according to the differential package, the validity of the differential package is checked, and the validity of the new atomic package is checked; finally, after the vehicle end completes the preparation of the software package required by all the upgrading tasks, the vehicle end sequentially executes the upgrading installation instructions according to the definition of the upgrading strategy file, and the vehicle end sequentially displays the software installation flow and the result when installing the upgrading instructions.
In some embodiments, the method of embodiments of the present application further comprises: detecting whether the vehicle to be upgraded is abnormal or not, and executing the installation operation of the rollback software package according to the rollback message; if the installation operation is not executed, carrying out fault reminding while carrying out upgrading failure reminding.
After the vehicle end is abnormal in the upgrade instruction execution message, the rollback software package installation operation is sequentially executed according to the rollback instructions, and the vehicle end sends the execution log of the upgrade task to the service gateway through the data embedding point unit in the entering and exiting steps of the upgrade instruction execution step.
In summary, the embodiment of the application can use the whole vehicle software or local domain controller software as a distributed system to perform unified application software management, configure and track the vehicle software upgrading strategy and the related strategy execution state in a visual graphic mode, and facilitate operation and maintenance personnel, technicians and testers to realize remote upgrading operation of the whole vehicle software.
The vehicle remote upgrade method will be described by a specific embodiment, as shown in fig. 4, including the following steps:
s1-1, configuring a software application, and defining information such as a software part number, an application code, an application name, a description and the like which can be remotely upgraded.
S1-2, configuring the vehicle type code, the vehicle type name, the vehicle type year money, the belonged brand and other information.
S1-3, configuring the association relation between the vehicle type and the software application, and configuring a software application list which can be allowed to be remotely upgraded according to the vehicle type.
S1-4, defining an application version/upgrading strategy of a vehicle type, increasing the software version number of the whole vehicle of the vehicle type according to the vehicle type, configuring the part number to be upgraded according to the whole vehicle version number, and configuring upgrading conditions, such as upgrading program starting information of a vehicle gear, an ignition state and the like, according to the application configuration.
S1-5, uploading an upgrade atomic packet, a differential packet, a rollback packet, upgrade description information and the like of the part application software to be upgraded according to the vehicle type application version.
S1-6, configuring the upgrading sequence of the part application software to be upgraded according to the configured vehicle type application version number, and marking the upgrading sequence by an arrow in a DAG visual mode.
S1-7, the server automatically generates an upgrade instruction list according to the configured DAG graph, and writes the upgrade instruction into an upgrade strategy configuration file according to the format specification.
S1-8, the server automatically sorts the upgrading and downgrading instruction list according to the upgrading instruction list, and writes the downgrading instruction list into the downgrading vehicle configuration file according to the format.
S1-9, pushing the upgrade message to the test vehicle, and enabling the appointed test vehicle to acquire and download the upgrade strategy file of the appointed whole vehicle application version.
S1-10, whether the execution of the upgrade strategy of the test vehicle reaches the expectation or not is verified manually, and if the execution reaches the expectation, S1-11 is executed; if the expectation is not reached, S1-5 is performed.
S1-11, uploading a test report aiming at a specified whole vehicle application version.
S1-12, auditing personnel audit a test report of the whole vehicle application version.
S1-13, if the auditor passes, S1-14 is executed, and if the auditor does not pass, S1-5 is executed.
S1-14, generating an upgrade task aiming at the whole vehicle application version which passes the audit, and defining a vehicle range which allows upgrade.
S1-15, auditing personnel audit the upgrade tasks to be released, and pass and fail can be executed.
S1-16, if the auditor selects to pass the execution of S1-17 and does not pass the execution, the state of the whole vehicle upgrading task is modified to be an initial state, and the process returns to S1-14 for modification.
S1-17, the system judges whether the upgrading task is executed at the appointed time, if the upgrading task is the timing task, S1-18 is executed, and if the upgrading task is not the timing task, S1-20 is executed.
S1-18, the task execution system records a new timed task record.
S1-19, the task execution system regularly checks whether the timed task to be executed exists, the execution time is met, S1-20 is executed, the execution time is not met, and the dormancy waits for awakening.
S1-20, acquiring a vehicle list to be upgraded according to an upgrading range designated by the upgrading task, and calling a message pushing interface to push the upgrading task to the executing vehicle according to the vehicle list.
S1-21, downloading and upgrading the steamed stuffed bun flow by the vehicle end.
S1-22, the vehicle end executes an upgrade strategy sub-flow.
In this embodiment, the flow of downloading and upgrading the steamed stuffed bun at the vehicle end is shown in fig. 5, and includes the following steps:
s2-1, a vehicle end requests a server end upgrade checking interface to check whether a vehicle application package of the vehicle needs to be updated exists or not, and the upgrade strategy information of the vehicle application package of the vehicle needs to be updated is obtained.
S2-2, if the whole vehicle application packet needing to be updated exists, executing S-3, otherwise ending the flow.
S2-3, checking whether the local available capacity meets the size of the upgrade package to be downloaded.
S2-4, if enough download task execution is stored, S2-5 is executed, otherwise S2-7 is executed.
S2-5, generating an upgrade task record ID locally, and recording and identifying the execution behavior of the upgrade task.
S2-6, circularly checking the downloaded software package according to the upgrade strategy list
S2-7, generating alarm prompt information, displaying the alarm prompt information through a visual screen, and sending the alarm prompt information to a server side.
S2-8, if the software package corresponding to the current cycle has a difference package, executing S2-9, otherwise executing S2-11.
S2-9, downloading the appointed software differential packet according to the differential packet downloading link defined in the upgrading strategy list.
S2-10, generating an upgrade target package through local atomic inclusion and differential package by using a package reduction unit.
S2-11, downloading the appointed software atomic package according to the original software package downloading link defined in the upgrading strategy list.
S2-12, recording an upgrade execution log according to the upgrade task ID.
S2-13, judging whether a download task to be executed exists, if so, executing S2-6, and if not, ending the flow.
In this embodiment, the sub-flow of the upgrade policy executed by the vehicle end is shown in fig. 6, and includes the following steps:
s3-1, circularly executing the software package installation instruction according to the upgrade strategy list.
S3-2, judging whether an upgrading condition is met, if yes, executing S3-3, and if not, executing S3-9.
S3-3, recording an upgrade execution log according to the upgrade task ID, and updating the upgrade state of the whole vehicle.
S3-4, executing a software package installation instruction according to the software package installation requirement, and starting the daemon.
S3-5, monitoring whether the software installation is abnormal or not through the daemon, if the daemon judges that the abnormality occurs, interrupting the installation instruction, executing S3-11, and if the installation is completed, executing S3-6.
S3-6, recording an upgrade task execution log according to the upgrade task ID, and updating the whole vehicle upgrade state.
S3-7, judging whether the upgrade strategy list is completely executed, if not, executing S3-1, and if so, completely executing.
S3-8, waking up the upgrade master execution task through timing or other specific events.
S3-9, suspending the upgrade master task process for waiting.
S3-10, judging whether the rollback condition of the whole vehicle software is met, if the rollback condition is met, executing S3-14, and if the rollback condition is not met, executing S3-9.
S3-11, recording an upgrade task exception log according to the upgrade task ID.
S3-12, displaying an upgrade success prompt through a vehicle screen.
S3-13, the system judges whether the maximum retry number is exceeded, if the maximum retry number is not exceeded, the system executes S3-8, and if the maximum retry number is exceeded, the system executes S3-21.
S3-14, requesting server-side interface service, acquiring a rollback execution policy list, and circularly executing rollback operation according to the rollback execution policy list.
S3-15, recording an upgrade task rollback log according to the upgrade task ID.
S3-16, executing a software rollback installation instruction according to the rollback policy list.
S3-17, recording an upgrade task rollback log according to the upgrade task ID.
S3-18, judging whether the next rollback operation task exists, if so, executing S3-14, and if not, executing S3-19.
S3-19, deleting new software atomic packages of the upgrading task according to the upgrading task strategy list, and deleting downloaded differential packages of the upgrading task.
S3-20, deleting the old software atomic package according to the upgrade task strategy list, and deleting the differential package downloaded by the upgrade task.
S3-21, updating the current upgrade task state to be upgrade success according to the upgrade task ID.
According to the vehicle remote upgrading method, unified upgrading management of the whole vehicle software is achieved through a software definition mode, direct dependence of all software versions of the vehicle and the software can be accurately determined, the problem of configuration errors caused by unclear dependence when a plurality of software are simultaneously upgraded is avoided, the plurality of software can be reliably upgraded remotely at the same time, reliability and efficiency of remote upgrading are effectively improved, and user experience is improved.
A vehicle remote upgrade apparatus according to an embodiment of the present application will be described next with reference to the accompanying drawings.
Fig. 7 is a block schematic diagram of a vehicle remote upgrade apparatus according to an embodiment of the present application.
As shown in fig. 7, the vehicle remote upgrade apparatus 10 includes: the module 100 is divided, the module 200 is determined and the module 300 is upgraded.
The dividing module 100 is configured to determine an application software definition to which one or more control domains of a vehicle to be upgraded belong according to a plurality of control domain software definitions divided based on a whole vehicle type; the determining module 200 is configured to determine an installation package, a differential package and/or a rollback package according to the release version identifier of the application software definition; the upgrade module 300 is configured to upgrade software corresponding to the upgrade instruction according to the installation package, the differential package, and/or the rollback package.
Further, the upgrade module 300 includes: the device comprises a generating unit, a first configuration unit, a second configuration unit and an upgrading unit. The generating unit is used for generating a whole vehicle software upgrading strategy of the vehicle to be upgraded according to the upgrading instruction; the first configuration unit is used for configuring at least one piece of software to be upgraded according to the whole vehicle software upgrading strategy, and configuring version identification, upgrading operation and installation package of each piece of software to be upgraded; the second configuration unit is used for configuring the upgrading sequence and the rollback sequence of each piece of software to be upgraded according to the difference packet and the rollback packet, calculating the storage size occupied by all pieces of software upgrading packet, and generating an upgrading instruction message and a rollback instruction message to form upgrading data; and the upgrading unit is used for sending the upgrading data to the vehicle to be upgraded so as to execute upgrading operation based on the upgrading data.
Further, the apparatus 10 of the embodiment of the present application further includes: and a visualization module. The visualization module is used for generating a directed acyclic graph according to the upgrading sequence and the rollback sequence, and converting the directed acyclic graph into a tree structure so as to visualize the upgrading sequence and the rollback sequence.
Further, the apparatus 10 of the embodiment of the present application further includes: the device comprises a receiving module and a reminding module. The receiving module is used for receiving a current upgrading flow and an upgrading result fed back by the vehicle to be upgraded, and determining a final upgrading result of the vehicle to be upgraded according to the current upgrading flow and the upgrading result; and the reminding module is used for detecting whether the vehicle to be upgraded is abnormal or not, executing the installation operation of the rollback software package according to the rollback message, and carrying out fault reminding while carrying out upgrade failure reminding if the installation operation is not executed.
It should be noted that the foregoing explanation of the embodiment of the vehicle remote upgrade method is also applicable to the vehicle remote upgrade apparatus of this embodiment, and will not be repeated here.
According to the vehicle remote upgrading device, unified upgrading management of the whole vehicle software is achieved through a software definition mode, direct dependence of all software versions of the vehicle and the software can be accurately determined, the problem of configuration errors caused by unclear dependence when a plurality of software are simultaneously upgraded is avoided, the plurality of software can be reliably upgraded remotely at the same time, reliability and efficiency of remote upgrading are effectively improved, and use experience of a user is improved.
In addition, the embodiment of the application also provides a server, and the server comprises the vehicle remote upgrading device. The server can realize unified upgrade management of the whole vehicle software in a software definition mode, can accurately determine all software versions of the vehicle and direct dependence of the software, avoid the problem of configuration errors caused by unclear dependence when simultaneously upgrading a plurality of software, can simultaneously and reliably remotely upgrade the plurality of software, effectively improve the reliability and efficiency of remote upgrade, and improve the use experience of users.
In the description of the present specification, a description referring to terms "one embodiment," "some embodiments," "examples," "specific examples," or "some examples," etc., means that a particular feature, structure, material, or characteristic described in connection with the embodiment or example is included in at least one embodiment or example of the present application. In this specification, schematic representations of the above terms are not necessarily directed to the same embodiment or example. Furthermore, the particular features, structures, materials, or characteristics described may be combined in any suitable manner in any one or N embodiments or examples. Furthermore, the different embodiments or examples described in this specification and the features of the different embodiments or examples may be combined and combined by those skilled in the art without contradiction.
Furthermore, the terms "first," "second," and the like, are used for descriptive purposes only and are not to be construed as indicating or implying a relative importance or implicitly indicating the number of technical features indicated. Thus, a feature defining "a first" or "a second" may explicitly or implicitly include at least one such feature. In the description of the present application, the meaning of "N" is at least two, such as two, three, etc., unless explicitly defined otherwise.
Any process or method descriptions in flow charts or otherwise described herein may be understood as representing modules, segments, or portions of code which include one or more N executable instructions for implementing specific logical functions or steps of the process, and further implementations are included within the scope of the preferred embodiment of the present application in which functions may be executed out of order from that shown or discussed, including substantially concurrently or in reverse order, depending on the functionality involved, as would be understood by those reasonably skilled in the art of the embodiments of the present application.
It is to be understood that portions of the present application may be implemented in hardware, software, firmware, or a combination thereof. In the above-described embodiments, the N steps or methods may be implemented in software or firmware stored in a memory and executed by a suitable instruction execution system. As with the other embodiments, if implemented in hardware, may be implemented using any one or combination of the following techniques, as is well known in the art: discrete logic circuits having logic gates for implementing logic functions on data signals, application specific integrated circuits having suitable combinational logic gates, programmable Gate Arrays (PGAs), field Programmable Gate Arrays (FPGAs), and the like.
Those of ordinary skill in the art will appreciate that all or a portion of the steps carried out in the method of the above-described embodiments may be implemented by a program to instruct related hardware, where the program may be stored in a computer readable storage medium, and where the program, when executed, includes one or a combination of the steps of the method embodiments.
Claims (8)
1. A method for remotely upgrading a vehicle, comprising the steps of:
determining application software definition of one or more control domains of a vehicle to be upgraded according to a plurality of control domain software definitions based on the whole vehicle type division;
determining an installation package, a differential package and a rollback package according to the release version identification of the application software definition;
upgrading the software corresponding to the upgrading instruction according to the installation package, the differential package and the rollback package;
configuring an upgrading sequence and a rollback sequence of each piece of software to be upgraded according to the differential packet and the rollback packet;
generating a directed acyclic graph according to the upgrading sequence and the rollback sequence, converting the directed acyclic graph into a tree structure, converting the directed acyclic graph into a software package upgrading sequence in a layer sequence traversing tree node mode, and obtaining the rollback sequence in a queue traversing mode to visualize the upgrading sequence and the rollback sequence.
2. The method of claim 1, wherein the upgrading software corresponding to the upgrade instruction according to the installation package, the differential package, and the rollback package comprises:
generating a whole vehicle software upgrading strategy of the vehicle to be upgraded according to the upgrading instruction;
configuring at least one piece of software to be upgraded according to the whole vehicle software upgrading strategy, and configuring version identification, upgrading operation and the installation package of each piece of software to be upgraded;
calculating the storage size occupied by all the software upgrade packages, and generating an upgrade instruction message and a rollback instruction message to form upgrade data;
and sending the upgrade data to the vehicle to be upgraded so as to execute upgrade operation based on the upgrade data.
3. The method as recited in claim 1, further comprising:
receiving a current upgrading flow and an upgrading result fed back by the vehicle to be upgraded;
and determining a final upgrading result of the vehicle to be upgraded according to the current upgrading flow and the upgrading result.
4. The method as recited in claim 2, further comprising:
detecting whether the vehicle to be upgraded is abnormal or not, and executing the installation operation of the rollback software package according to the rollback instruction message;
and if the installation operation is not executed, carrying out fault reminding while carrying out upgrading failure reminding.
5. A vehicle remote upgrade apparatus, comprising:
the dividing module is used for determining one or more control domain affiliated application software definitions of the vehicle to be upgraded according to a plurality of control domain software definitions divided based on the whole vehicle type;
the determining module is used for determining an installation package, a differential package and a rollback package according to the release version identification of the application software definition;
the upgrading module is used for upgrading the software corresponding to the upgrading instruction according to the installation package, the differential package and the rollback package, and is used for configuring the upgrading sequence and the rollback sequence of each piece of software to be upgraded according to the differential package and the rollback package;
and the visualization module is used for generating a directed acyclic graph according to the upgrading sequence and the rollback sequence, converting the directed acyclic graph into a tree structure, converting the directed acyclic graph into a software package upgrading sequence in a layer sequence traversal tree node mode, and obtaining the rollback sequence in a queue traversal mode so as to visualize the upgrading sequence and the rollback sequence.
6. The apparatus of claim 5, wherein the upgrade module comprises:
the generation unit is used for generating an entire vehicle software upgrading strategy of the vehicle to be upgraded according to the upgrading instruction;
the first configuration unit is used for configuring at least one piece of software to be upgraded according to the whole vehicle software upgrading strategy, and configuring the version identification, upgrading operation and the installation package of each piece of software to be upgraded;
the second configuration unit is used for configuring the upgrading sequence and the rollback sequence of each piece of software to be upgraded according to the difference packet and the rollback packet, calculating the storage size occupied by all pieces of software upgrading packet, and generating an upgrading instruction message and a rollback instruction message to form upgrading data;
and the upgrading unit is used for sending the upgrading data to the vehicle to be upgraded so as to execute upgrading operation based on the upgrading data.
7. The apparatus as recited in claim 5, further comprising:
the receiving module is used for receiving the current upgrading flow and the upgrading result fed back by the vehicle to be upgraded and determining the final upgrading result of the vehicle to be upgraded according to the current upgrading flow and the upgrading result;
and the reminding module is used for detecting whether the vehicle to be upgraded is abnormal or not, executing the installation operation of the rollback software package according to the rollback instruction message, and carrying out fault reminding while carrying out upgrading failure reminding if the installation operation is not executed.
8. A server comprising a vehicle remote upgrade apparatus according to any one of claims 5-7.
Priority Applications (2)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110472386.6A CN113094073B (en) | 2021-04-29 | 2021-04-29 | Vehicle remote upgrading method, device and server |
| PCT/CN2022/074733 WO2022227755A1 (en) | 2021-04-29 | 2022-01-28 | Remote upgrade method and apparatus for vehicle, and server |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110472386.6A CN113094073B (en) | 2021-04-29 | 2021-04-29 | Vehicle remote upgrading method, device and server |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN113094073A CN113094073A (en) | 2021-07-09 |
| CN113094073B true CN113094073B (en) | 2024-03-12 |
Family
ID=76681457
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202110472386.6A Active CN113094073B (en) | 2021-04-29 | 2021-04-29 | Vehicle remote upgrading method, device and server |
Country Status (2)
| Country | Link |
|---|---|
| CN (1) | CN113094073B (en) |
| WO (1) | WO2022227755A1 (en) |
Families Citing this family (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113094073B (en) * | 2021-04-29 | 2024-03-12 | 芜湖雄狮汽车科技有限公司 | Vehicle remote upgrading method, device and server |
| CN114189442A (en) * | 2021-11-30 | 2022-03-15 | 深圳市国电科技通信有限公司 | Remote upgrading of edge equipment and electronic equipment |
| CN114466098B (en) * | 2022-01-19 | 2023-12-26 | 上海黑眸智能科技有限责任公司 | OTA upgrading method, system, equipment end and APP end based on APP interaction |
| CN114979297B (en) * | 2022-05-26 | 2023-06-27 | 重庆长安汽车股份有限公司 | Vehicle software version large-span OTA upgrading method |
| CN114980073A (en) * | 2022-05-26 | 2022-08-30 | 重庆长安汽车股份有限公司 | Vehicle OTA state intelligent analysis processing method, system and storage medium |
| CN115242633B (en) * | 2022-06-23 | 2024-04-09 | 惠州华阳通用电子有限公司 | Vehicle-mounted equipment upgrading method and device based on USB Ethernet |
| CN115396309A (en) * | 2022-08-23 | 2022-11-25 | 浙江吉智新能源汽车科技有限公司 | Software upgrading method, OTA function purchasing method and information interaction system |
Citations (11)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2013178048A1 (en) * | 2012-05-28 | 2013-12-05 | 华为终端有限公司 | Method and device for generating firmware over-the-air upgrade package |
| CN106325892A (en) * | 2015-06-15 | 2017-01-11 | 中兴通讯股份有限公司 | Method and device for difference backspacing upgrade |
| CN107493186A (en) * | 2016-12-23 | 2017-12-19 | 宝沃汽车（中国）有限公司 | The remote update system and its control method of vehicle |
| CN109189422A (en) * | 2018-08-13 | 2019-01-11 | 北京新能源汽车股份有限公司 | A kind of remote upgrade method and device of electronic control unit |
| CN111090445A (en) * | 2019-12-18 | 2020-05-01 | 广东中兴新支点技术有限公司 | Vehicle service upgrading method, device and system |
| CN111399884A (en) * | 2020-04-09 | 2020-07-10 | 东风小康汽车有限公司重庆分公司 | Vehicle component upgrading method and device and electronic equipment |
| CN112104736A (en) * | 2020-09-17 | 2020-12-18 | 广州汽车集团股份有限公司 | OTA-based multi-ECU upgrading method |
| WO2021008184A1 (en) * | 2019-07-18 | 2021-01-21 | 南京依维柯汽车有限公司 | Remote upgrading system and upgrading method for fota firmware on new energy automobile |
| CN112256315A (en) * | 2020-10-16 | 2021-01-22 | 中国第一汽车股份有限公司 | Upgrading method, device, equipment and storage medium |
| CN112328294A (en) * | 2020-11-12 | 2021-02-05 | 杭州创想智联科技有限公司 | OTA (over the air) upgrading method and system for vehicle ECU (electronic control Unit) |
| CN112514354A (en) * | 2020-03-19 | 2021-03-16 | 华为技术有限公司 | Vehicle software upgrading method and related system |
Family Cites Families (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US7366589B2 (en) * | 2004-05-13 | 2008-04-29 | General Motors Corporation | Method and system for remote reflash |
| US9836300B2 (en) * | 2015-06-16 | 2017-12-05 | Lear Corporation | Method for updating vehicle ECUs using differential update packages |
| CN111108472A (en) * | 2017-09-25 | 2020-05-05 | 蒂森克虏伯普利斯坦股份公司 | Method for remote online software updating in a motor vehicle |
| 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 |
| US11449327B2 (en) * | 2018-11-30 | 2022-09-20 | Paccar Inc | Error-resilient over-the-air software updates for vehicles |
| CN113094073B (en) * | 2021-04-29 | 2024-03-12 | 芜湖雄狮汽车科技有限公司 | Vehicle remote upgrading method, device and server |
| CN113434169B (en) * | 2021-06-22 | 2023-03-28 | 重庆长安汽车股份有限公司 | Method and system for generating air upgrading parallel task group based on dependency relationship |
-
2021
- 2021-04-29 CN CN202110472386.6A patent/CN113094073B/en active Active
-
2022
- 2022-01-28 WO PCT/CN2022/074733 patent/WO2022227755A1/en unknown
Patent Citations (11)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2013178048A1 (en) * | 2012-05-28 | 2013-12-05 | 华为终端有限公司 | Method and device for generating firmware over-the-air upgrade package |
| CN106325892A (en) * | 2015-06-15 | 2017-01-11 | 中兴通讯股份有限公司 | Method and device for difference backspacing upgrade |
| CN107493186A (en) * | 2016-12-23 | 2017-12-19 | 宝沃汽车（中国）有限公司 | The remote update system and its control method of vehicle |
| CN109189422A (en) * | 2018-08-13 | 2019-01-11 | 北京新能源汽车股份有限公司 | A kind of remote upgrade method and device of electronic control unit |
| WO2021008184A1 (en) * | 2019-07-18 | 2021-01-21 | 南京依维柯汽车有限公司 | Remote upgrading system and upgrading method for fota firmware on new energy automobile |
| CN111090445A (en) * | 2019-12-18 | 2020-05-01 | 广东中兴新支点技术有限公司 | Vehicle service upgrading method, device and system |
| CN112514354A (en) * | 2020-03-19 | 2021-03-16 | 华为技术有限公司 | Vehicle software upgrading method and related system |
| CN111399884A (en) * | 2020-04-09 | 2020-07-10 | 东风小康汽车有限公司重庆分公司 | Vehicle component upgrading method and device and electronic equipment |
| CN112104736A (en) * | 2020-09-17 | 2020-12-18 | 广州汽车集团股份有限公司 | OTA-based multi-ECU upgrading method |
| CN112256315A (en) * | 2020-10-16 | 2021-01-22 | 中国第一汽车股份有限公司 | Upgrading method, device, equipment and storage medium |
| CN112328294A (en) * | 2020-11-12 | 2021-02-05 | 杭州创想智联科技有限公司 | OTA (over the air) upgrading method and system for vehicle ECU (electronic control Unit) |
Also Published As
| Publication number | Publication date |
|---|---|
| CN113094073A (en) | 2021-07-09 |
| WO2022227755A1 (en) | 2022-11-03 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN113094073B (en) | Vehicle remote upgrading method, device and server | |
| CN106293811A (en) | A kind of packing and issuing method and device automatically | |
| ES2879869T3 (en) | Method and system to perform a software diagnosis or maintenance for a vehicle | |
| CA2472854C (en) | Distributed expert diagnostic service and system | |
| CN101718992B (en) | Vehicle diagnosis system and method based on internet C/S mode | |
| CN110673576B (en) | Automatic test method and device, vehicle and storage medium | |
| CN103902542A (en) | Operating and maintaining method and system of database in testing environment | |
| CN112286171A (en) | Remote diagnosis method, device, vehicle and storage medium | |
| CN111752850B (en) | Method and related equipment for testing block chain system | |
| CN111737207B (en) | Method and device for showing and collecting logs of service nodes in distributed system | |
| JP2004532445A (en) | System and method for monitoring service provider performance | |
| CN108364242A (en) | The copyright for preserving intermediate file really weighs method and device | |
| CN110602209A (en) | Firmware over-the-air upgrading method and system based on DMP | |
| CN109558147A (en) | A kind of continuous integrating platform construction method based on Jenkins and Gitlab | |
| CN107506194A (en) | Application version, which retracts, determines method and device | |
| Naslavsky et al. | Using scenarios to support traceability | |
| CN114880220A (en) | Development system and method for vehicle automatic driving software | |
| CN110908955B (en) | Management system of IO device description file | |
| CN112202647A (en) | Test method, device and test equipment in block chain network | |
| CN111913974A (en) | Method and server for measuring point configuration of rail transit passenger information system | |
| CN109375946A (en) | A kind of method and system of the component packet of management node package manager | |
| CN114285840A (en) | Vehicle data acquisition method, intelligent terminal and storage medium | |
| CN112102107A (en) | Method, device and equipment for generating report of power supply system | |
| CN115118577A (en) | Method and device for determining remote upgrade abnormal reason, electronic equipment and storage medium | |
| CN114915643A (en) | Configuration method, device, equipment and medium of railway signal centralized monitoring system |
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 |