CN115437659A - Vehicle-end software version remote batch upgrading management method, system and medium - Google Patents
Vehicle-end software version remote batch upgrading management method, system and medium Download PDFInfo
- Publication number
- CN115437659A CN115437659A CN202110613727.7A CN202110613727A CN115437659A CN 115437659 A CN115437659 A CN 115437659A CN 202110613727 A CN202110613727 A CN 202110613727A CN 115437659 A CN115437659 A CN 115437659A
- Authority
- CN
- China
- Prior art keywords
- version
- vehicle
- software
- declarative
- deployment file
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/60—Software deployment
- G06F8/61—Installation
-
- 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/70—Software maintenance or management
- G06F8/71—Version control; Configuration management
Landscapes
- Engineering & Computer Science (AREA)
- Software Systems (AREA)
- General Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Computer Security & Cryptography (AREA)
- Stored Programmes (AREA)
Abstract
The application discloses a method, a system and a medium for remote batch upgrade management of vehicle-end software versions, and belongs to the technical field of automatic driving. The method comprises the following steps: uploading and storing the software codes; continuously compiling the software codes into an integration process; a binary file storage process; an declarative version deployment package storage process; a software new version is uniformly grouped and released; and a software new version grouping automatic batch upgrading process, wherein a plurality of vehicle-end container management units are used for deploying a file package according to a new declarative version when vehicles of the corresponding group are in a starting state, and automatically downloading and operating corresponding binary files from a binary file storage library in a container mode so as to finish batch upgrading of the corresponding software versions on all vehicles of the corresponding group. According to the method for managing the remote batch upgrading of the vehicle-end software version, the software version release efficiency is improved, and the complexity of the release and upgrading of the software version is reduced.
Description
Technical Field
The application relates to the technical field of automatic driving, in particular to a method, a system and a medium for remote batch upgrade management of vehicle-end software versions.
Background
In the prior art of upgrading vehicle end software, it is mainly in a manner consistent with the upgrading of the internet of things OTA (abbreviation of Over-the-air Technology, translated as "Over-the-air Technology", which refers to a Technology for downloading by means of a mobile network or a WIFI network). Figure 1 illustrates a typical prior art manner of upgrading vehicle end software. As shown in fig. 1, after the new version of the car-side application program is developed successfully, the new version is compiled into a full-size version package or an OTA differential package, and is uploaded to a version warehouse and synchronized to an OTA server. After receiving the new version upgrading message, the OTA agent program running on the vehicle displays that the corresponding application program has the new version, and at the moment, the OTA agent program can finish upgrading of the corresponding application software by manually operating on the specific vehicle. The whole upgrading process is similar to the upgrading of the application program on the current mobile phone.
However, as the automated driving technology evolves, particularly during the development of the automated driving technology, a lot of vehicle batch participation is required. Frequent version upgrading is carried out on different vehicles, if the prior art is adopted, the workload of manual operation is very large, and when multiple vehicles need to be upgraded with the same software by multiple persons at the same time, the coordination of the persons becomes a very large problem, and the working efficiency is greatly reduced.
Disclosure of Invention
The application provides a vehicle-end software version remote batch upgrade management method, system and medium, aiming at the technical problem that the prior art cannot be efficiently applied to batch vehicle remote upgrade.
In one technical solution of the present application, a method for managing remote batch upgrade of vehicle-end software versions is provided, including: the software code uploading and storing process is that the code repository stores the software codes uploaded by programmers in a distributed mode; the software code continuous compiling and integrating process is that continuous integration construction service compiles and integrates codes meeting the pre-configured compiling rules in continuously uploaded software codes to generate binary files of different versions which can be run by a vehicle end and a declarative version deployment file package describing the binary files; a binary file storing process of storing a binary file by a binary file repository; a declarative version deployment file package storage process, wherein a declarative version deployment file repository stores declarative version deployment file packages; in the unified grouping release process of the new software version, when the unified release platform automatically monitors in real time or manually selects the vehicle-end software version needing to be upgraded on the unified release platform, the unified release platform checks that a new declarative version deployment file package corresponding to the vehicle-end software version needing to be upgraded is stored in a declarative version deployment file repository, and is compared with the last monitoring result or is manually selected, the new declarative version deployment file package is pulled from the declarative version deployment file repository and is released to all vehicles of a corresponding group in a plurality of vehicle groups; and a software new version grouping automatic batch upgrading process, wherein a plurality of vehicle-end container management units are respectively pre-installed in each vehicle, when the vehicles of the corresponding grouping are in a starting state, the file package is deployed according to the new declarative version, and the corresponding binary file is automatically downloaded from the binary file storage library and operated in a container mode so as to complete batch upgrading of the corresponding software version on all the vehicles of the corresponding grouping.
In another technical solution of the present application, a system for remote batch upgrade management of vehicle-end software versions is provided, including: the code storage bank stores software codes uploaded by programmers in a distributed mode; the continuous integration construction service is used for compiling and integrating codes meeting a preconfigured compiling rule in continuously uploaded software codes to generate binary files of different versions which can be run by a vehicle end and a declarative version deployment file package for describing the binary files; a binary file repository storing binary files; the declarative version deployment file repository stores declarative version deployment file packages; the unified release platform is used for pulling a new declarative version deployment file package from the declarative version deployment file repository and releasing the new declarative version deployment file package to all vehicles in corresponding groups in a plurality of vehicle groups when the vehicle end software version needing to be upgraded is automatically monitored in real time or manually selected on the unified release platform and then is detected, and the new declarative version deployment file package is stored in the declarative version deployment file repository and is compared with the last monitoring result or is manually selected; and a plurality of vehicle-end container management units which are respectively pre-installed in each vehicle, when the vehicles of the corresponding group are in a starting state, deploy the file package according to the new declarative version, automatically download the corresponding binary file from the binary file repository and operate the corresponding binary file in a container form, so as to complete batch upgrading of the corresponding software version on all the vehicles of the corresponding group.
In another aspect of the present application, a computer-readable storage medium is provided, which stores computer instructions, and the computer instructions are operated to execute the method for managing remote batch upgrade of vehicle-end software versions in the foregoing aspects.
Through adopting above-mentioned technical scheme, this application can reach following technological effect: the software versions of the corresponding grouped vehicles can be automatically upgraded remotely without manual intervention at the vehicle end, so that the software version release efficiency is improved; the complexity of software version release and upgrade is reduced by the technical idea of managing containers.
Drawings
In order to more clearly illustrate the detailed description of the present application or the technical solutions in the prior art, the drawings required for the detailed description of the present application or the technical solutions in the prior art will be briefly described below. It is clear that the drawings described below are directed to some specific embodiments of the present application, and that other drawings corresponding to equivalent substitutions or modifications of the specific embodiments can be straightforwardly and unambiguously determined from these drawings by those skilled in the art without inventive effort.
FIG. 1 is a schematic diagram illustrating an exemplary manner of upgrading vehicle-side software in the prior art;
FIG. 2 is a flowchart illustrating an embodiment of a method for remote batch upgrade management of vehicle-end software versions according to the present application;
fig. 3 is a schematic diagram illustrating an embodiment of a vehicle-end software version remote batch upgrade management system according to the present application.
In view of the foregoing drawings, it will be apparent to those skilled in the art that certain embodiments of the present application have been described in detail herein. The drawings and the description are not intended to limit the scope of the inventive concepts of the present application in any way, but rather to enable those skilled in the art to more readily understand the inventive concepts of the present application through a few specific embodiments.
Detailed Description
In order to make the technical solutions of the present application more easily understood by those skilled in the art, some specific embodiments of the technical solutions of the present application will be clearly and completely described with reference to the accompanying drawings. It is obvious that the embodiments described are only a few embodiments of the present invention, not all embodiments. All other embodiments, which can be derived by a person skilled in the art from the description of embodiments already given herein without making any creative effort, shall fall within the protection scope of the present application.
It should be noted that, in the present application, the terms "first", "second", "third", "fourth", etc. (if any), the numbers and/or letter designations of several processes are used for distinguishing similar objects, and are not necessarily to be construed as describing a particular order or sequence. It is to be understood that the numbers may be interchanged where appropriate so that the aspects of the application described herein may be implemented in other sequences than illustrated or described. Furthermore, the terms "comprises" and "comprising," and any variations thereof, are not intended to cover an exclusive inclusion, such that a method that comprises a list of steps or an article or device that comprises a plurality of elements or modules is not necessarily to be construed as limited to the listed steps, elements or modules, but may include other steps, elements or modules not expressly listed or inherent to such method, article or device.
In addition, a plurality of embodiments, a plurality of examples, and the like, which will be described in detail below with respect to different parts of the technical solutions of the present invention, may be combined with each other to form a complete technical solution of the present invention, unless mutually exclusive. For the same or similar concepts, procedures, etc. that have been described in a certain specific embodiment, example, etc., detailed description may not be repeated in other specific embodiments, examples, etc.
Some embodiments, examples, and the like of the present application will be described in detail below with reference to the accompanying drawings.
Fig. 2 is a flowchart illustrating a specific embodiment of a vehicle-end software version remote batch upgrade management method according to the present application.
In the embodiment shown in fig. 2, the method for managing remote batch upgrade of vehicle-end software versions includes: s201, software codes are uploaded and stored, and the code repository stores the software codes uploaded by programmers in a distributed mode.
In the process of uploading and storing the software code represented by S201, the software code uploaded by the programmer in a distributed manner is stored by the code repository.
In the embodiment, the software codes written by programmers distributed at different positions are uploaded and stored in the unified code repository in a unified manner, so that corresponding unified management is performed, software development projects from small to large can be performed effectively at high speed, and the cooperative work capacity of programmers at different positions is improved.
In an embodiment of the present invention, the code repository may be a centralized code repository, and a distributed version control system is pre-installed on the local terminal of each programmer. As one example, the code repository may be one or more computer devices with storage functionality.
In this embodiment, by using a centralized code repository, it is convenient to perform uniform control on the subsequent programming results, i.e. software codes, of all programmers.
As an example, after the local terminal writes the software code of the corresponding software that the local terminal itself is responsible for writing, the programmers distributed at different locations upload the written software code to the centralized code repository through the distributed version control system pre-installed on the local terminal themselves, and store the software code by the code repository.
As an example, the distributed version control system may be an open-source distributed version control system, and may specifically be git. Accordingly, the code repository may be a git repository.
As an example of this embodiment, the programmers may be divided into groups, with one group of programmers working on the task of programming and upgrading the software of the vehicles in a vehicle group that implements one function. Thus, the set of programmers may write code as part of the software for the vehicle for the corresponding functional grouping.
As an example, each group of vehicles grouped by function may perform data collection, autodrive algorithm verification, autodrive commissioning, and the like, respectively.
In the embodiment shown in fig. 2, the method for managing remote batch upgrade of the vehicle-end software version includes: s202, continuously compiling the software codes into an integration process.
In the software code continuous compiling and integrating process represented by S202, the continuous integration construction service compiles and integrates codes that satisfy the preconfigured compiling rules among the continuously uploaded software codes, generates binary files of different versions that the vehicle end can run, and deploys a file package to a declarative version that describes the binary files.
Therefore, different software codes can be compiled and integrated according to corresponding automatic execution flows, so that binary files of different versions which can be run by a vehicle end can be automatically generated, and declarative version deployment file packages for describing the binary files can be automatically generated.
As an example of the present embodiment, the continuous integration construction service is configured such that a corresponding compiling rule is configured in advance for each of software codes uploaded by programmers corresponding to each of a plurality of vehicle groups.
As an example of the present embodiment, the pre-configured compiling rule may implement checking of the compiling normalization of the software code. As an example, writing normalization may include: whether the written format meets the requirements, whether the size of the code is economical compared to the function to be implemented, etc. Thus, when the software code is written out of specification, e.g., the format is not satisfactory, or the code size is not economical enough, the persistent integration build service may return the software code to the appropriate programmer for re-writing.
As an example of the present embodiment, codes meeting a preconfigured compiling rule among continuously uploaded software codes are compiled and integrated, specifically, the codes for the same software may be compiled into a vehicle-executable data format corresponding to the software, and a compiled result is integrated into a binary file of a new version of the software.
As an example of this embodiment, the declarative version deployment package may describe a start command of the corresponding vehicle-end software, a lower limit value and an upper limit value of the occupation of the computational resource, an operation that needs to be executed based on the health check result, the number of copies, and/or a start sequence of the corresponding vehicle-end software.
As an example, the lower limit value of the occupation of the computing resource is an occupied amount of memory and/or CPU that must be allocated to ensure that the new version of the corresponding vehicle-side software can operate normally. The upper limit value of the occupation of computing resources can ensure that the memory and/or CPU occupied by the new version of the corresponding vehicle-end software when in operation can not influence the normal operation of the software and functional components which are necessary to operate when the corresponding vehicle is in normal driving.
As an example, the operations that need to be performed on the health check results may include: in the installation process of the corresponding version of the corresponding vehicle-end software, if the corresponding container cannot normally respond after being continuously arranged for a preset time period, the corresponding container is forcibly stopped to run and then restarted again; and in the running process of the corresponding version of the corresponding vehicle-end software, if the corresponding container is checked to be incapable of responding normally, the corresponding container is restarted after being forcibly stopped to run.
In this way, the operation required to be executed based on the health check result is set in the declarative version deployment package, so that the full life cycle management of the corresponding vehicle-end software can be realized.
As an example of the present embodiment, the number of copies established for the corresponding car-side software is 1. Therefore, when the corresponding vehicle-end software crashes for any reason, a healthy copy is still operated, and the operation robustness of the corresponding vehicle-end software is ensured.
As an example of this embodiment, the start of the corresponding software needs to be premised on the start or stop of other vehicle-end software, and at this time, the start sequence of the corresponding software and the other vehicle-end software is configured in the declarative version deployment package, so that it can be ensured that the corresponding software already has the start condition when being started. For example, the software for image analysis needs to be started before starting the software for controlling the camera installed in the vehicle to capture images.
As an example, the declarative version deployment package may be a declarative deployment package helm chart generated and managed using the lightweight Kubernets' package management tool helm.
In the embodiment shown in fig. 2, the method for managing remote batch upgrade of the vehicle-end software version further includes: s203, binary file storage process.
In the binary file storing process indicated by S203, the binary file is stored by the binary file repository.
In the embodiment shown in fig. 2, the method for managing remote batch upgrade of vehicle-end software versions further includes: and S204, storing the declarative version deployment file package.
In the storing process of the declarative version deployment package represented by S204, the declarative version deployment package is stored by the declarative version deployment file repository.
In an embodiment of the present invention, the declarative deployment file repository may be a plurality of declarative deployment file repositories, and each of the declarative deployment file repositories may be respectively dedicated to store declarative deployment file packages generated by software codes corresponding to software of vehicles in a vehicle group of one function. Thus, the respective declarative version deployment packages stored in the respective declarative version deployment file repositories may be dedicated to respective ones of the plurality of vehicle groups in a one-to-one correspondence.
In this way, in subsequent operations, only according to which declarative version deployment file repository the storage location of declarative version deployment file package is in, it can be determined to which group of vehicles the corresponding declarative version deployment file package needs to be issued.
In one embodiment of this embodiment, the multiple declarative version deployment file repositories may be multiple separate physical storage media or multiple branches within one physical storage medium.
As one example, the declarative version deployment file repository may be a git repository.
In the embodiment shown in fig. 2, the method for managing remote batch upgrade of the vehicle-end software version further includes: s205, the software new version unifies the grouping and releasing process.
In the unified grouping and issuing process of the new software version represented by S205, after the vehicle-end software version to be upgraded is automatically monitored in real time or manually selected on the unified issuing platform, the unified issuing platform checks that a new declarative version deployment file package corresponding to the vehicle-end software version to be upgraded is stored in the declarative version deployment file repository, compared with the last monitoring result or manually selected, and pulls the new declarative version deployment file package from the declarative version deployment file repository and issues the new declarative version deployment file package to all vehicles of a corresponding grouping in the plurality of vehicle groupings.
In the embodiment, if the unified release platform automatically monitors whether a new declarative version deployment file package exists in real time, the uniform release platform releases the new declarative version deployment file package, and the new declarative version deployment file package belongs to monitoring type automatic release; if the vehicle-end software version needing to be upgraded is manually selected on the unified publishing platform and then is published, the vehicle-end software version is actively published.
In an embodiment of the present invention, under the condition of active release, a unified release platform administrator may click a software version to be upgraded on a unified release platform, so that the unified release platform may release a declarative version deployment file package checked and pulled from a corresponding declarative version deployment file repository to all vehicles of a corresponding group served by the software version.
In an embodiment of the present invention, if one or more vehicles in the corresponding group of vehicles that need to release a new version of the software are in an un-started state, the corresponding declarative version deployment package pulled by the unified release platform is cached on the unified release platform. In this way, the automatic upgrade of the respective software can be started upon start-up of the respective vehicle.
As an example, in the case where the declarative version deployment file repository is a git repository, the automatic interception and communication of the declarative version deployment file repository by the unified publishing platform may be accomplished in the form of GitOps.
In the embodiment shown in fig. 2, the method for managing remote batch upgrade of the vehicle-end software version further includes: and S206, grouping the new software version to automatically carry out batch upgrading.
In the automatic batch upgrading process of the software new version grouping represented by S206, a plurality of vehicle-side container management units are respectively pre-installed in each vehicle, and when the vehicle of the corresponding grouping is in a starting state, the file package is deployed according to the new declarative version, and the corresponding binary file is automatically downloaded from the binary file repository and operated in a container form, so as to complete batch upgrading of the corresponding software version on all vehicles of the corresponding grouping.
In one example of this embodiment, the vehicle-end container management unit may be control software. The vehicle-end container management unit can operate the downloaded binary file for software version upgrading in the form of a container, so that the software version upgrading on the corresponding vehicle is completed.
The vehicle-end container management unit can operate the corresponding binary files in the form of containers, and the complexity of release and upgrade of vehicle-end software versions can be reduced in consideration of the characteristics of the containers, such as the capability of overall migration, convenience in copy establishment and the like.
In an embodiment of the present invention, under the management of the vehicle-end container management unit, each vehicle may be represented as an independent cluster under the management of one vehicle-end container management unit. As one example, the independent clusters may be implemented with one or more servers on respective vehicles.
In an embodiment of the present invention, the unified distribution platform may perform group management on independent clusters managed by all vehicle-side container management units, so that vehicles with the same function are grouped in the same group of the vehicle group.
In an embodiment of the present embodiment, the communication between the unified publishing platform and the independent cluster under the management of the vehicle-side container management unit may adopt bidirectional certificate authentication. Therefore, the safety of communication between the two parties can be ensured, and the vehicle is prevented from being hijacked by a third party maliciously in the automatic driving process.
As an example, the vehicle-side container management unit may be a lightweight version k3s of the cluster management tool kubernets. Correspondingly, the independent cluster under the management of the vehicle-end container management unit can be an independent k3s cluster.
Fig. 3 is a schematic diagram illustrating an embodiment of a vehicle-end software version remote batch upgrade management system according to the present application.
In this particular embodiment, it comprises: a code repository 301 for storing software codes uploaded by programmers in a distributed manner; the continuous integration construction service 302 is used for compiling and integrating codes meeting the preconfigured compiling rules in continuously uploaded software codes to generate binary files of different versions which can be run by a vehicle end and a declarative version deployment file package for describing the binary files; a binary file repository 303 that stores binary files; an declarative version deployment file repository 304 storing declarative version deployment file packages; the unified release platform 305 is used for pulling a new declarative version deployment file package from the declarative version deployment file repository and releasing the new declarative version deployment file package to all vehicles in corresponding groups in a plurality of vehicle groups when the fact that a vehicle-end software version needing to be upgraded is stored in the declarative version deployment file repository is detected after real-time automatic monitoring is carried out or a vehicle-end software version needing to be upgraded is manually selected on the unified release platform; and a plurality of vehicle-end container management units 306, which are respectively pre-installed in each vehicle, deploy the file package according to the new declarative version when the vehicles of the corresponding group are in a starting state, automatically download the corresponding binary file from the binary file repository and run the corresponding binary file in a container form, so as to complete batch upgrading of the corresponding software version on all the vehicles of the corresponding group.
In this specific embodiment, the code repository 301, the persistent integration construction server 302, the binary file repository 303, the declarative version deployment file repository 304, the uniform distribution platform 305, and the multiple vehicle-end container management units 306 may specifically execute the software code uploading and storing process 201 and the software code persistent compiling and integrating process 202 of the vehicle-end software version remote batch upgrade management method shown in fig. 2; the corresponding processes described in the above specific embodiments, examples, and the like of the binary file storage process 203, the declarative version deployment package storage process 204, the software new version unified grouping release process 205, and the software new version grouping automatic batch upgrade process 206 can achieve the corresponding technical effects achieved by the corresponding processes described in the above specific embodiments, examples, and the like of the vehicle-end software version remote batch upgrade management method shown in fig. 2.
In one embodiment of the present application, a computer-readable storage medium is provided, which stores computer instructions, where the computer instructions are operated to execute the method for remote batch upgrade management of vehicle-end software versions described in any one of the above embodiments, examples, and the like. The storage medium stores computer instructions that may be stored directly in hardware, in a software module executed by a processor, or in a combination of the two.
A software module may reside in RAM memory, flash memory, ROM memory, EPROM memory, EEPROM memory, registers, hard disk, a removable disk, a CD-ROM, or any other form of storage medium that may be used to store computer instructions. In general, a storage medium may be under the control of a processor such that the processor can read information from, and write information to, the storage medium.
The Processor may be a Central Processing Unit (CPU), other general-purpose Processor, a Digital Signal Processor (DSP), an Application Specific Integrated Circuit (ASIC), a Field Programmable Gate Array (FPGA), other Programmable logic devices, discrete Gate or transistor logic, discrete hardware components, or any combination thereof. A general purpose processor may be a microprocessor, but in the alternative, the processor may be any conventional processor, controller, microcontroller, or state machine. A processor may also be implemented as a combination of computing devices, e.g., a combination of a DSP and a microprocessor, a plurality of microprocessors, one or more microprocessors in conjunction with a DSP core, or any other such configuration. In the alternative, the storage medium may be integral to the processor. The processor and the storage medium may reside in an ASIC. The ASIC may reside in a user terminal. In the alternative, the processor and the storage medium may reside as discrete components in a user terminal.
In the embodiments provided in the present application, it should be understood that the disclosed apparatus may be implemented in other manners. For example, the above-described apparatus embodiments are merely illustrative, and for example, a division of a unit is merely a logical division, and an actual implementation may have another division, for example, a plurality of units or components may be combined or integrated into another system, or some features may be omitted, or not executed. In addition, the shown or discussed mutual coupling or direct coupling or communication connection may be an indirect coupling or communication connection through some interfaces, devices or units, and may be in an electrical, mechanical or other form.
Units described as separate parts may or may not be physically separate, and parts displayed as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. Some or all of the units can be selected according to actual needs to achieve the purpose of the technical solution of the present application.
The above embodiments are merely examples, which are not intended to limit the scope of the present disclosure, and all equivalent structural changes made by using the contents of the specification and the drawings, or any other related technical fields, are also included in the scope of the present disclosure.
Claims (10)
1. A vehicle-end software version remote batch upgrading management method is characterized by comprising the following steps:
the software code uploading and storing process is that the code repository stores the software codes uploaded by programmers in a distributed mode;
a software code continuous compiling and integrating process, wherein codes meeting a preconfigured compiling rule in the continuously uploaded software codes are compiled and integrated by a continuous integrating and constructing service to generate binary files of different versions which can be run by a vehicle end, and a declarative version deployment file package describing the binary files;
a binary file storing process of storing the binary file by a binary file repository;
a declarative version deployment file package storage process, wherein a declarative version deployment file repository stores declarative version deployment file packages;
a unified group release process of a software new version, which is detected by a unified release platform after automatically monitoring in real time or manually selecting a vehicle-end software version to be upgraded on the unified release platform, wherein when a new declarative version deployment file package corresponding to a vehicle-end software version to be upgraded is stored in the declarative version deployment file repository and compared with a previous monitoring result or is manually selected, the new declarative version deployment file package is pulled from the declarative version deployment file repository and is released to all vehicles of a corresponding group in a plurality of vehicle groups; and
and in the automatic batch upgrading process of the software new version grouping, a plurality of vehicle-end container management units are respectively pre-installed in each vehicle, when the vehicles of the corresponding grouping are in a starting state, a file package is deployed according to the new declarative version, and corresponding binary files are automatically downloaded from the binary file storage library and run in a container mode so as to finish batch upgrading of the corresponding software versions on all the vehicles of the corresponding grouping.
2. The vehicle-end software version remote batch upgrade management method according to claim 1, wherein the declarative version deployment file repository is multiple, and the corresponding declarative version deployment file packages stored in each declarative version deployment file repository are respectively dedicated to each of the plurality of vehicle groups in a one-to-one correspondence.
3. The method for remote batch upgrade management of vehicle-end software versions according to claim 1, wherein the declarative version deployment package describes a start command of corresponding vehicle-end software, a lower limit value and an upper limit value of occupation of computational resources, operations to be executed based on health check results, the number of copies, and/or a start sequence of other vehicle-end software.
4. The method for remote batch upgrade management of vehicle-end software versions according to claim 3, wherein the operations required to be performed based on health check results include:
in the installation process of the corresponding version of the corresponding vehicle-end software, if the corresponding container cannot normally respond after being continuously arranged for a preset time period, the corresponding container is forcibly stopped to run and then restarted again; and
and in the running process of the corresponding version of the corresponding vehicle-end software, if the corresponding container cannot respond normally after being checked, forcibly stopping running the corresponding container and restarting the corresponding container again.
5. The vehicle-end software version remote batch upgrade management method according to claim 3, wherein the number of copies established for the corresponding vehicle-end software is 1.
6. The vehicle-end software version remote batch upgrade management method according to claim 1, wherein the continuous integration construction service configures the corresponding compiling rules in advance for the software codes uploaded by programmers respectively corresponding to each of the plurality of vehicle groups.
7. The vehicle-end software version remote batch upgrade management method according to claim 1, wherein on the unified release platform, the vehicle-end container management units are managed in groups, so that vehicles with the same function are grouped in the same group of the vehicle groups.
8. The vehicle-end software version remote batch upgrade management method according to claim 1, characterized in that the communication between the unified issuing platform and the vehicle-end container management unit adopts two-way certificate authentication.
9. The utility model provides a long-range batch upgrade management system of car end software version which characterized in that includes:
the code storage bank stores software codes uploaded by programmers in a distributed mode;
the continuous integration construction service is used for compiling and integrating codes meeting a preconfigured compiling rule in the continuously uploaded software codes to generate binary files of different versions which can be run by a vehicle end, and a declarative version deployment file package for describing the binary files;
a binary file repository storing the binary files;
an declarative version deployment file repository storing the declarative version deployment file package;
the unified release platform is used for pulling a new declarative version deployment file package from the declarative version deployment file repository and releasing the new declarative version deployment file package to all vehicles of corresponding groups in a plurality of vehicle groups when a vehicle end software version needing to be upgraded is automatically monitored in real time or manually selected on the unified release platform and is detected, and the new declarative version deployment file package is stored in the declarative version deployment file repository and is compared with a last monitoring result or is corresponding to the vehicle end software version needing to be upgraded is manually selected; and
and the vehicle-end container management units are respectively pre-installed in each vehicle, when the vehicles of the corresponding group are in a starting state, deploy a file package according to the new declarative version, automatically download the corresponding binary file from the binary file repository and operate the corresponding binary file in a container form, so as to complete batch upgrading of the corresponding software version on all the vehicles of the corresponding group.
10. A computer-readable storage medium storing computer instructions operable to perform the method for remote batch upgrade management of vehicle-end software versions according to any one of claims 1-8.
Priority Applications (2)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110613727.7A CN115437659A (en) | 2021-06-02 | 2021-06-02 | Vehicle-end software version remote batch upgrading management method, system and medium |
| PCT/CN2021/109539 WO2022252381A1 (en) | 2021-06-02 | 2021-07-30 | Management method and system for remotely upgrading vehicle-end software versions in batches, and medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110613727.7A CN115437659A (en) | 2021-06-02 | 2021-06-02 | Vehicle-end software version remote batch upgrading management method, system and medium |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN115437659A true CN115437659A (en) | 2022-12-06 |
Family
ID=84240142
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202110613727.7A Pending CN115437659A (en) | 2021-06-02 | 2021-06-02 | Vehicle-end software version remote batch upgrading management method, system and medium |
Country Status (2)
| Country | Link |
|---|---|
| CN (1) | CN115437659A (en) |
| WO (1) | WO2022252381A1 (en) |
Families Citing this family (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN116707819B (en) * | 2023-06-01 | 2024-03-15 | 红石阳光（北京）科技股份有限公司 | Construction method of vehicle OTA upgrading security mechanism |
Family Cites Families (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103327125A (en) * | 2013-07-15 | 2013-09-25 | 厦门金龙联合汽车工业有限公司 | Code remote upgrading system and file transmission method thereof |
| CN108279919B (en) * | 2018-01-22 | 2021-10-08 | 成都雅骏新能源汽车科技股份有限公司 | Remote program upgrading method for new energy electric vehicle |
| CN110489143B (en) * | 2019-07-18 | 2023-10-13 | 南京依维柯汽车有限公司 | FOTA firmware remote upgrading system and method on new energy automobile |
| CN111343064A (en) * | 2020-02-29 | 2020-06-26 | 东风汽车集团有限公司 | System and method for upgrading software of automobile control system |
-
2021
- 2021-06-02 CN CN202110613727.7A patent/CN115437659A/en active Pending
- 2021-07-30 WO PCT/CN2021/109539 patent/WO2022252381A1/en unknown
Also Published As
| Publication number | Publication date |
|---|---|
| WO2022252381A1 (en) | 2022-12-08 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US11650807B2 (en) | Self-healing learning system for one or more controllers | |
| CN107896162B (en) | Deployment method and device of monitoring system, computer equipment and storage medium | |
| CN110515673A (en) | Plug-in unit system and method | |
| CN104750555A (en) | Management method and device for progresses in Android program | |
| CN115061717A (en) | Application management method, application subscription method and related equipment | |
| CN111679888A (en) | Deployment method and device of agent container | |
| CN115437659A (en) | Vehicle-end software version remote batch upgrading management method, system and medium | |
| CN115328529A (en) | Application management method and related equipment | |
| CN113434180B (en) | Data processing method and device for application, server and storage medium | |
| CN112565416B (en) | Cloud-native-based large-scale edge android equipment nanotube system and nanotube method thereof | |
| CN113296795A (en) | Application deployment method, device, equipment, storage medium and program product | |
| CN113515293B (en) | Method and system for managing DevOps toolchain | |
| CN115421847A (en) | Management method and equipment for research, development, operation and maintenance platform and CICD (common information carrier) assembly line supporting multiple engines | |
| CN113254158B (en) | Deployment method and device of deep learning system | |
| CN114037496A (en) | State machine-based order state management method, device, equipment and medium | |
| CN113326052A (en) | Method and device for upgrading service component, computer equipment and storage medium | |
| CN116933491A (en) | Automatic driving simulation method, system, equipment and storage medium | |
| CN116594632A (en) | Compiling method, compiling device, computer device, storage medium and compiling system | |
| CN113495809A (en) | Application version rollback method, device, equipment and medium | |
| CN116166284A (en) | Memcache cluster deployment method, storage medium and electronic device | |
| CN117369942A (en) | Method and system for arranging and automatically deploying application service resources |
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 |