Vehicle software package management method and device, electronic equipment and storage medium

Through the vehicle package management method, the server-side version tree is used to manage on-board software packages, the problem of low efficiency in vehicle package management is solved, and rapid deployment and stable management is achieved, suitable for online and offline deployment.

CN119002958APending Publication Date: 2024-11-22CHINA FAW CO LTD +1
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202411022630.9
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Filing Date
2024-07-29
Publication Date
2024-11-22

AI Technical Summary

Technical Problem

The lack of effective vehicle software package management solutions in the prior art makes it difficult to effectively manage different versions of vehicle software during the development process, affecting development efficiency and deployment time.

Method used

Provides a vehicle software package management method, including generating, uploading, updating and deploying software packages, realizing full management of vehicle software packages through the server-side software package version tree, and supporting online and offline deployment.

Benefits of technology

It realizes packaging, uploading, synchronization and deployment of different versions of vehicle software, improves development efficiency, shortens software deployment time, and provides a stable deployment solution in a network-free environment.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN119002958A_ABST
    Figure CN119002958A_ABST
Patent Text Reader

Abstract

The invention discloses a vehicle software package management method and device, electronic equipment and a storage medium, and the method comprises the steps: responding to a generation request of a first target software package, and if the content of a description file of the first target software package input by a user meets a verification condition, generating the first target software package; uploading the first target software package to a server in response to an uploading request for the first target software package; updating a software package version tree of the server side based on the uploaded first target software package; in response to a downloading request of a second target software package, downloading the second target software package based on the software package version tree of the server side; and deploying the second target software package to the vehicle. By adopting the scheme of the invention, the whole-line management of the vehicle software package can be realized, and developers can be helped to quickly and conveniently manage different versions of vehicle-mounted software generated in the development process.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The present invention relates to the field of vehicles, and in particular to a vehicle software package management method, device, electronic equipment and storage medium. Background Art

[0002] In order to improve the vehicle driving experience, ensure driving safety, optimize vehicle performance and other goals, relevant software is generally deployed on the vehicle. Accordingly, in the process of developing these vehicle-mounted software, developers may develop multiple versions of software, and each software that can be implemented needs to be iterated through multiple versions before it can be finalized. In the face of the different versions of software and corresponding software packages generated in this process, it is very necessary to effectively manage them. However, there is no solution in the prior art to manage these software packages during the development process. Summary of the invention

[0003] The present invention provides a vehicle software package management method, device, electronic device and storage medium, which can realize full-line management of vehicle software packages and help developers quickly and conveniently manage different versions of vehicle-mounted software generated during the development process.

[0004] In a first aspect, the present invention provides a vehicle software package management method, comprising:

[0005] In response to a request for generating a first target software package, if the content of the description file of the first target software package input by the user meets a verification condition, generating the first target software package;

[0006] In response to an upload request for the first target software package, uploading the first target software package to a server;

[0007] Based on the uploaded first target software package, updating the software package version tree on the server side;

[0008] In response to a download request for a second target software package, downloading the second target software package based on the software package version tree on the server side;

[0009] The second target software package is deployed on the vehicle.

[0010] In a second aspect, the present invention further provides a vehicle software package management device, comprising:

[0011] A first target software package generating module, configured to generate the first target software package in response to a generation request of the first target software package if the content of the description file of the first target software package input by the user satisfies a verification condition;

[0012] a first target software package uploading module, configured to upload the first target software package to a server in response to an upload request for the first target software package;

[0013] A server-side version tree update module, used to update the server-side software package version tree based on the uploaded first target software package;

[0014] A second target software package downloading module, configured to respond to a download request for the second target software package and download the second target software package based on the software package version tree on the server side;

[0015] The second target software package deployment module is used to deploy the second target software package on the vehicle.

[0016] In a third aspect, an embodiment of the present invention further provides an electronic device, including:

[0017] one or more processors;

[0018] a storage device for storing one or more programs,

[0019] When the one or more programs are executed by the one or more processors, the one or more processors implement the vehicle software package management method provided in any embodiment of the present invention.

[0020] In a fourth aspect, an embodiment of the present invention further provides a storage medium comprising computer executable instructions, wherein the computer executable instructions, when executed by a computer processor, are used to execute the vehicle software package management method provided in any embodiment of the present invention.

[0021] The technical solution provided by the present invention generates the first target software package in response to a request for generating the first target software package, if the content of the description file of the first target software package input by the user meets the verification condition; uploads the first target software package to the server in response to an upload request for the first target software package; updates the software package version tree on the server side based on the uploaded first target software package; downloads the second target software package based on the software package version tree on the server side in response to a download request for the second target software package; and deploys the second target software package to the vehicle. By adopting the solution of the present invention, the tasks of packaging, uploading, synchronizing and deploying different versions of vehicle-mounted software can be realized in the software development process, thereby realizing the full-line management of the vehicle software package, and can help developers quickly and conveniently manage the different versions of vehicle-mounted software generated in the development process, thereby improving development efficiency and shortening software deployment time.

[0022] The above invention content is only an overview of the technical solution of the present invention. In order to more clearly understand the technical means of the present invention, it can be implemented according to the contents of the specification. In order to make the above and other purposes, features and advantages of the present invention more obvious and easy to understand, the specific implementation methods of the present invention are listed below. BRIEF DESCRIPTION OF THE DRAWINGS

[0023] The above and other features, advantages and aspects of the embodiments of the present invention will become more apparent with reference to the following detailed description in conjunction with the accompanying drawings. Throughout the accompanying drawings, the same or similar reference numerals represent the same or similar elements. It should be understood that the drawings are schematic and the originals and elements are not necessarily drawn to scale.

[0024] Figure 1 It is a flow chart of a vehicle software package management method provided by an embodiment of the present invention;

[0025] Figure 2 is a flow chart of another vehicle software package management method provided by an embodiment of the present invention;

[0026] Figure 3 is a structural schematic diagram of a vehicle software package management device provided by an embodiment of the present invention;

[0027] Figure 4 It is a structural schematic diagram of an electronic device for implementing a vehicle software package management method provided by an embodiment of the present invention. DETAILED DESCRIPTION

[0028] Embodiments of the present invention will be described in more detail below with reference to the accompanying drawings. Although certain embodiments of the present invention are shown in the accompanying drawings, it should be understood that the present invention can be implemented in various forms and should not be construed as being limited to the embodiments described herein, which are instead provided for a more thorough and complete understanding of the present invention. It should be understood that the drawings and embodiments of the present invention are only for exemplary purposes and are not intended to limit the scope of protection of the present invention.

[0029] It should be understood that the various steps described in the method embodiments of the present invention may be performed in different orders and / or in parallel. In addition, the method embodiments may include additional steps and / or omit the steps shown. The scope of the present invention is not limited in this respect.

[0030] The term "including" and its variations used herein are open inclusions, i.e., "including but not limited to". The term "based on" means "based at least in part on". The term "one embodiment" means "at least one embodiment"; the term "another embodiment" means "at least one additional embodiment"; the term "some embodiments" means "at least some embodiments". The relevant definitions of other terms will be given in the following description.

[0031] It should be noted that the concepts such as "first" and "second" mentioned in the present invention are only used to distinguish different devices, modules or units, and are not used to limit the order or interdependence of the functions performed by these devices, modules or units.

[0032] It should be noted that the modifications of "one" and "plurality" mentioned in the present invention are illustrative rather than restrictive, and those skilled in the art should understand that, unless otherwise clearly indicated in the context, it should be understood as "one or more".

[0033] The names of the messages or information exchanged between multiple devices in the embodiments of the present invention are only used for illustrative purposes, and are not used to limit the scope of these messages or information.

[0034] Figure 1 The present invention is a flowchart of a vehicle software package management method provided by an embodiment of the present invention. The present invention is applicable to the case of managing vehicle software packages during the vehicle software development process. The method can be executed by a vehicle software package management device. The vehicle software package management device can be implemented in the form of software and / or hardware and is generally integrated on any electronic device with network communication function. The electronic device can be a mobile terminal, a PC or a server, etc. Figure 1 As shown, the vehicle software package management method of the embodiment of the present invention may include the following process:

[0035] S110 : In response to a request for generating a first target software package, if the content of the description file of the first target software package input by the user meets a verification condition, generating the first target software package.

[0036] In the process of developing vehicle software, developers will continuously develop new vehicle software or new versions of vehicle software. In the face of these multiple different vehicle software, it is very necessary to effectively manage them, especially in the management of the upload, download, and deployment of vehicle software packages formed by the newly developed vehicle software. By managing these vehicle software packages, you can have a clearer understanding of the version iteration of each vehicle software, which can facilitate the deployment and testing of the vehicle software in the later stage.

[0037] After the developer develops new vehicle-mounted software, the vehicle-mounted software needs to be processed to generate a corresponding software package. The software package can be saved locally for subsequent testing and other purposes, or it can be uploaded to the server for archiving and updating. Specifically, the software package contains specific vehicle-mounted software and a description file corresponding to the vehicle-mounted software. Among them, the description file is used to record various types of information related to the vehicle-mounted software. The description file contains the version number information, naming information, checksum information, packaging date, installation path, configuration information and dependencies of the vehicle-mounted software. The first target software package refers to the software package generated for the vehicle-mounted software that needs to be deployed and tested on the vehicle-side system. The vehicle-side system is a system located on the vehicle for debugging and modifying the vehicle-mounted software.

[0038] Specifically, when a user (e.g., a developer) has a software package generation requirement for the developed vehicle software, a first target software package generation request will be triggered, and then the generation request of the first target software package will be responded to, and the corresponding configuration template will be fed back to the user. Among them, the configuration template contains various configuration parameters that need to be filled in to generate the description file of the first target software package, such as: version number information, naming information, startup script, dependency relationship and installation path, etc. The user can fill in the corresponding information based on the configuration template.

[0039] After the user completes inputting various information in the description file of the first target software package, the content of the description file of the first target software package needs to be verified. Only when the verified content meets the verification condition, it indicates that the description file of the first target software package is preliminarily correct, and the first target software package is generated.

[0040] As an optional but non-limiting implementation, the content of the description file of the first target software package input by the user satisfies the verification condition, which may include the following steps A1-A2:

[0041] Step A1: determining whether the version number naming in the description file of the first target software package is correct, so as to perform version number rule verification on the first target software package.

[0042] For the version number information in the description file of the first target software package, it is necessary to determine whether the version number is named correctly, so as to perform version number rule verification on the first target software package. If the version number is named correctly, the iteration information of the vehicle software package can be correctly reflected, which is convenient for managing the vehicle software package. If the version number is named incorrectly, it may directly lead to the inability to upload the vehicle software package, which is not conducive to the unified management of the software package.

[0043] Step A2: Determine whether the configuration information in the description file of the first target software package is correct, so as to perform a high-risk operation check on the first target software package; the configuration information includes the set deployment chip, startup script and software dependency.

[0044] Among them, configuration information refers to the parameter information that can be used to control the operation of vehicle-mounted software. Specifically, the configuration information includes the set deployment chips, startup scripts and software dependencies. Deployment chips refer to the chips required to run vehicle-mounted software, such as the vehicle's main control chip, sensor chip and communication chip. The startup script refers to the program instructions that need to be executed to start the vehicle-mounted software. The startup script includes loading and executing program code and resources, initializing the environment and allocating memory. Software dependencies refer to the dependencies that the vehicle-mounted software needs to form on other software or modules during the compilation and operation process.

[0045] For the configuration information in the description file of the first target software package, it is necessary to determine whether the set configuration information is correct in order to perform a high-risk operation check on the first target software package. If the configuration information is incorrect, high-risk operations will occur when the vehicle-mounted software is running. For example, the configuration information sets the requirement to delete the root directory in the file system or change the firewall settings of the vehicle-side system during the software operation. Once the vehicle-mounted software is run according to such configuration information, it will cause permanent loss of key data and even cause system security vulnerabilities, which will constitute high-risk operations. Therefore, performing a high-risk operation check on the first target software package can ensure the stability of the vehicle-side system during the subsequent actual operation of the vehicle-mounted software and avoid more serious data loss or damage.

[0046] S120 . In response to an upload request for the first target software package, upload the first target software package to a server.

[0047] After determining that the first target software package meets the requirements, the user will initiate an upload request for the generated first target software package to upload the first target software package to the server. Specifically, after successfully generating the first target software package, the user can initiate an upload request for the first target software package on the visual interface, and then respond to the upload request for the first target software package and send the local first target software package to the server to upload the first target software package to the server.

[0048] S130: Based on the uploaded first target software package, update the software package version tree on the server side.

[0049] The software package version tree on the server side records the different versions of the historical changes of each vehicle software. The software package version tree can be graphical information, such as a tree diagram. Through the software package version tree on the server side, the historical changes of different vehicle software can be seen more clearly and macroscopically.

[0050] Specifically, based on the uploaded first target software package, the software package version tree on the server side can be updated. Specifically, it includes adding and replacing nodes in the software package version tree on the server side, wherein replacement refers to deleting and then adding the original nodes in the software package version tree on the server side, thereby updating the software package version tree. By updating the software package version tree on the server side, the continuity and accuracy of the vehicle software during the development process can be ensured.

[0051] S140 . In response to a download request for the second target software package, download the second target software package based on the software package version tree on the server side.

[0052] The second target software package refers to a software package that needs to be downloaded, deployed or tested. It should be noted that the second target software package can be the first target software package or other target software packages, which can be determined according to the actual needs of the user.

[0053] When the user has a download deployment or test requirement for the vehicle software, a download request for the second target software package will be triggered. Since the different version information of each vehicle software is recorded in the software package version tree on the server side, when responding to the download request for the second target software package, the second target software package can be determined and downloaded according to the software package version tree on the server side.

[0054] S150: deploy the second target software package to the vehicle.

[0055] After the second target software package is successfully downloaded, the vehicle-mounted software can be deployed on the vehicle based on the description file in the second target software package.

[0056] The technical solution of the embodiment of the present invention is to generate the first target software package in response to a request for generating the first target software package, if the content of the description file of the first target software package input by the user meets the verification condition; upload the first target software package to the server in response to an upload request for the first target software package; update the software package version tree on the server side based on the uploaded first target software package; download the second target software package based on the software package version tree on the server side in response to a download request for the second target software package; and deploy the second target software package to the vehicle. By adopting the solution of the present invention, the tasks of packaging, uploading, synchronizing and deploying different versions of vehicle-mounted software can be realized in the software development process, thereby realizing the full-line management of the vehicle software package, and can help developers quickly and conveniently manage the different versions of vehicle-mounted software generated in the development process, thereby improving development efficiency and shortening software deployment time.

[0057] Figure 2 This is a flow chart of another vehicle software package management method provided by an embodiment of the present invention. The technical solution of this embodiment further optimizes the process of uploading the first target software package to the server in the above embodiment on the basis of the technical solution of the above embodiment. This embodiment can be combined with various optional solutions in one or more of the above embodiments. Figure 2 As shown, the vehicle software package management method of the embodiment of the present invention may include the following process:

[0058] S210 : In response to a request for generating a first target software package, if the content of the description file of the first target software package input by the user meets a verification condition, generating the first target software package.

[0059] S220 : In response to the upload request for the first target software package, obtain the first target software package based on the address of the first target software package.

[0060] In response to the upload request for the first target software package, the user can manually input the address of the first target software package to obtain the first target software package, or browse and select the first target software package from the local file management to obtain the first target software package.

[0061] During the period from the generation of the first target software package to the uploading of the first target software package to the server, the first target software package may be damaged, for example, internal files may be tampered with. Therefore, during the uploading of the first target software package, a more comprehensive and detailed verification of the first target software package is required to ensure the accuracy and security of the first target software package to be uploaded.

[0062] S230: Determine whether the format of the description file of the first target software package complies with the specification, so as to perform a descriptive check on the first target software package.

[0063] Specifically, it is determined whether the format of the description file of the first target software package complies with the specification, including determining whether the naming information, version number information, packaging date and other information in the description file are correct, so as to perform a descriptive check on the first target software package, thereby ensuring that the first target software package is the software package actually required to be uploaded.

[0064] S240: Determine whether the files in the first target software package have been tampered with, so as to perform a file integrity check on the first target software package.

[0065] The integrity check is to determine whether the files inside the first target software package have been tampered with, and whether the first target software package is correct and complete. The integrity check can be implemented through MD5 check. Specifically, it is determined whether the MD5 value in the vehicle software attribute information is consistent with the MD5 value recorded in the description file. If the MD5 values ​​of the two are consistent, it means that the files inside the first target software package have not been tampered with; if the MD5 values ​​of the two are inconsistent, it means that the files in the first target software package have been tampered with. At this time, the first target software package obtained has errors and does not meet the upload requirements. In the case where the files inside the first target software package have been confirmed to have been tampered with, it is necessary to regenerate the correct first target software package, or re-acquire the first target software package based on the correct path.

[0066] It should be noted that the order of the descriptive check and the file integrity check for the first target software package can be set based on the actual needs of the user. The descriptive check can be performed first, followed by the file integrity check; the file integrity check can be performed first, followed by the descriptive check; or the descriptive check and the file integrity check can be performed simultaneously, which will not be limited in detail here.

[0067] S250: After determining that the first target software package passes the descriptive check and the file integrity check, determine whether the first target software package has overwritten a locally existing historical first target software package, where the historical first target software package is a software package of a previous version corresponding to the first target software package.

[0068] Before uploading the first target software package to the server, it is necessary to ensure that the first target software package uploaded at this time is the software package corresponding to the latest version of the vehicle software. The historical earlier version of the software package has been uploaded to the server. Currently, it is only necessary to ensure that it is the software package corresponding to the latest version of the vehicle software each time it is uploaded. Specifically, it can be determined whether the first target software package to be uploaded is the latest version by judging whether the first target software package has overwritten the historical first target software package that exists locally.

[0069] S260: If the first target software package has overwritten the historical first target software package that exists locally, upload the first target software package to the server.

[0070] If the first target software package has overwritten the existing historical first target software package locally, it means that the first target software package meets the upload requirements and is the latest version of the software package, and the first target software package can be uploaded to the server. If the first target software package cannot overwrite the existing historical first target software package locally, the first target software package needs to be re-determined.

[0071] S270: Based on the uploaded first target software package, update the software package version tree on the server side.

[0072] S280: In response to the download request of the second target software package, download the second target software package based on the software package version tree on the server side.

[0073] As an optional but non-limiting implementation, downloading the second target software package based on the software package version tree on the server side may include the following steps B1-B3:

[0074] Step B1: Obtain the software package version tree on the server side.

[0075] Specifically, the local computer may request the server to download the software package version tree information from the server.

[0076] Optionally, in another implementation, the server may periodically send the software package version tree information of the server to the local.

[0077] Step B2: Compare the software package version tree on the server side with the local software package version tree to determine the second target software package.

[0078] The local software package version tree is also stored locally, but it may be different from the server-side software package version tree because the local software package version tree is not the latest. Based on the comparison result between the server-side software package version tree and the local software package version tree, the software package that has not been updated in time can be determined locally, and the second target software package can be determined.

[0079] Specifically, the comparison result between the two version trees may be determined by a user manually comparing the two versions, and the second target software package may be determined by observing the comparison.

[0080] Optionally, in another implementation, after the server updates the server-side software package version tree, it can send the corresponding version tree update result information to the local, and the version tree update result information includes the version tree node information updated by the server this time. Among them, the version tree update result information specifically includes the updated vehicle software package name information, version number information and update type (such as: new or replaced). The user can also directly use the vehicle software package in the version tree update result information received locally as the second target software package.

[0081] It should be noted that, as an optional but non-limiting implementation, the second target software package in the present application may also be determined by using a software package selected by the user according to actual needs as the second target software package.

[0082] Step B3: Downloading a second target software package based on the remote warehouse list on the server side, wherein the remote warehouse list on the server side stores at least one software package.

[0083] The remote warehouse list on the server side stores at least one software package, and the remote warehouse list stores various software packages corresponding to the software package version tree on the server side. That is, any software package in the software package version tree on the server side can be found based on the remote warehouse list.

[0084] After the second target software package has been determined, the second target software package can be downloaded based on the remote warehouse list of the server. Specifically, a query search can be performed in the remote warehouse list based on key information (e.g., naming information) of the second target software package, and the server can send the searched second target software package to the local according to the query result.

[0085] As an optional but non-limiting implementation, after downloading the second target software package based on the software package version tree on the server, the following steps C1-C3 may also be included:

[0086] Step C1: Determine a first hash value based on a description file of a second target software package.

[0087] During the downloading process of the second target software package, the software package may be incomplete due to data loss or software package damage. Therefore, the downloaded second target software package needs to be verified to ensure that the second target software package is correct and complete.

[0088] Specifically, after receiving the second target software package, the second target software package may be parsed, and a first hash value may be determined based on a description file in the second target software package, wherein the first hash value is a hash value set for the vehicle-mounted software in the second target software package.

[0089] Step C2: Determine a second hash value based on the software information of the second target software package.

[0090] The software information refers to the attribute information of the vehicle-mounted software in the second target software package. During the parsing of the second target software package, the second hash value can be determined according to the parsed attribute information of the vehicle-mounted software.

[0091] Step C3: Determine whether the first Hash value is the same as the second Hash value.

[0092] By determining whether the first hash value is the same as the second hash value, it can be determined whether the second target software package is correct and complete. Specifically, if the determination result is the same, the file of the second target software package has not been tampered with, and subsequent deployment and testing can continue. If the determination result is different, the file of the second target software package has been tampered with, and the second target software package needs to be downloaded again.

[0093] S290: deploy the second target software package to the vehicle.

[0094] As an optional but non-limiting implementation, deploying the second target software package on the vehicle may include the following steps D1-D2:

[0095] Step D1: Install the second target software package in a specified path and execute a startup script; wherein the specified path is determined based on a description file of the second target software package.

[0096] The designated path is determined based on the installation path in the description file of the second target software package, and then the second target software package is installed in the designated path, and the startup script is executed.

[0097] Step D2: Monitor the running status information and resource occupancy information of the second target software package, and record the running status information and resource occupancy information to form monitoring record information; the monitoring record information is used to send to the vehicle-side system so that the vehicle-side system can perform fault detection and performance optimization and adjustment on the vehicle-mounted software based on the monitoring record information.

[0098] Among them, the operating status information includes normal operation and abnormal stop. The source occupancy information includes the resource usage of the vehicle hardware when the vehicle-mounted software is running. After the second target software package is installed on the vehicle, the operating status information and resource occupancy information of the second target software package can be monitored, and the information can be recorded to form monitoring record information. The monitoring record information is used to send to the vehicle-side system, so that the vehicle-side system can perform fault detection on the vehicle-mounted software in the second target software package based on the operating status information in the monitoring record information, and can also enable the vehicle-side system to optimize the performance of the vehicle-mounted software in the second target software package based on the resource occupancy information in the monitoring record information. Among them, the vehicle-side system is a system located on the vehicle for debugging and modifying the vehicle-mounted software.

[0099] As an optional but non-limiting implementation method, after uploading the first target software package to the server, the following may be included: determining whether the local network can access the server; if the server can be accessed normally, performing online deployment based on the software package version tree on the server side; if the server cannot be accessed normally, determining whether the second target software package exists locally, and performing offline deployment based on the second target software package that already exists locally.

[0100] In actual usage scenarios, in addition to normal network conditions, there may also be network anomalies, such as network disconnection or weak network environment. For these possible situations, after uploading the first target software package to the server, it can be determined whether the local network can access the server, so that different measures can be taken for different situations to ensure the efficiency and timeliness of software deployment.

[0101] Specifically, if the server can be accessed normally, online deployment can be performed based on the software package version tree on the server. The specific deployment method can be to determine the software package to be deployed based on the comparison result between the software package version tree on the server and the local, and automatically download and deploy the relevant software packages, thereby improving the efficiency and real-time performance of software deployment.

[0102] If the server cannot be accessed normally, it is necessary to determine whether the required software package already exists in the local warehouse list, and perform offline deployment based on the existing software package in the local warehouse list. The offline deployment method solves the problem of software package deployment in a no network environment or a weak network environment, ensuring the timeliness and reliability of software package deployment.

[0103] The technical solution of the embodiment of the present invention, in response to the generation request of the first target software package, if the content of the description file of the first target software package input by the user meets the verification condition, the first target software package is generated; in response to the upload request for the first target software package, the first target software package is uploaded to the server; based on the uploaded first target software package, the software package version tree on the server is updated; in response to the download request of the second target software package, the second target software package is downloaded based on the software package version tree on the server; and the second target software package is deployed on the vehicle. By adopting the solution of the present invention, the various tasks of packaging, uploading, synchronizing and deploying different versions of vehicle-mounted software can be realized in the software development process, thereby realizing the full-line management of the vehicle software package, which can help developers quickly and conveniently manage the various different versions of vehicle-mounted software generated in the development process, improve the development efficiency and shorten the software deployment time. At the same time, two modes of online deployment and offline deployment are also provided, especially offline deployment can provide a stable and reliable deployment solution for no network environment and weak network environment, effectively improving the efficiency and stability in the vehicle software development process.

[0104] Figure 3 The schematic diagram of the structure of a vehicle software package management device provided by an embodiment of the present invention is applicable to the situation of managing vehicle software packages during the process of vehicle software development. The vehicle software package management device can be implemented in the form of software and / or hardware, and is generally integrated on any electronic device with network communication function, which can be a mobile terminal, PC or server, etc. Figure 3 As shown, the vehicle software package management device of the embodiment of the present invention may include a first target software package generation module 310, a first target software package upload module 320, a server-side version tree update module 330, a second target software package download module 340, and a second target software package deployment module 350. Among them:

[0105] The first target software package generating module 310 is configured to generate the first target software package in response to a request for generating the first target software package if the content of the description file of the first target software package input by the user meets a verification condition.

[0106] The first target software package uploading module 320 is configured to upload the first target software package to the server in response to an upload request for the first target software package.

[0107] The server-side version tree updating module 330 is used to update the server-side software package version tree based on the uploaded first target software package.

[0108] The second target software package downloading module 340 is configured to download the second target software package based on the software package version tree on the server side in response to a download request for the second target software package.

[0109] The second target software package deployment module 350 is used to deploy the second target software package to the vehicle.

[0110] As an optional but non-limiting implementation, the content of the description file of the first target software package input by the user satisfies the verification condition, including:

[0111] Determining whether the version number naming in the description file of the first target software package is correct, so as to perform version number rule verification on the first target software package;

[0112] It is determined whether the configuration information in the description file of the first target software package is correct, so as to perform a high-risk operation check on the first target software package; the configuration information includes a set deployment chip, a startup script, and software dependencies.

[0113] As an optional but non-limiting implementation, uploading the first target software package to the server includes:

[0114] Acquire the first target software package based on the address of the first target software package;

[0115] Determining whether the format of the description file of the first target software package complies with the specification, so as to perform a descriptive check on the first target software package;

[0116] Determining whether a file in the first target software package has been tampered with, so as to perform a file integrity check on the first target software package;

[0117] After determining that the first target software package passes the descriptive check and the file integrity check, determining whether the first target software package has overwritten a locally existing historical first target software package, where the historical first target software package is a software package of a previous version corresponding to the first target software package;

[0118] If the first target software package has overwritten the historical first target software package existing locally, the first target software package is uploaded to the server.

[0119] As an optional but non-limiting implementation, downloading the second target software package based on the software package version tree on the server side includes:

[0120] Get the package version tree on the server side;

[0121] Compare the software package version tree on the server side with the local software package version tree to determine the second target software package;

[0122] The second target software package is downloaded based on the remote warehouse list on the server side, where at least one software package is stored in the remote warehouse list on the server side.

[0123] As an optional but non-limiting implementation, after downloading the second target software package based on the software package version tree on the server, the method further includes:

[0124] Determine a first hash value based on a description file of a second target software package;

[0125] Determine a second hash value based on software information of a second target software package;

[0126] Determine whether the first hash value is the same as the second hash value;

[0127] If the judgment result is the same, the file of the second target software package has not been tampered with;

[0128] If the judgment result is that they are not the same, the file of the second target software package has been tampered with, and the second target software package needs to be downloaded again.

[0129] As an optional but non-limiting implementation, deploying the second target software package to the vehicle includes:

[0130] Install the second target software package in a specified path and execute a startup script; wherein the specified path is determined based on a description file of the second target software package;

[0131] Monitor the running status information and resource occupancy information of the second target software package, and record the running status information and resource occupancy information to form monitoring record information; the monitoring record information is used to send to the vehicle-side system, so that the vehicle-side system can perform fault detection and performance optimization and adjustment on the vehicle-mounted software based on the monitoring record information.

[0132] As an optional but non-limiting implementation, after uploading the first target software package to the server, the method further includes:

[0133] Determine whether the local network can access the server;

[0134] If the server can be accessed normally, online deployment is performed based on the software package version tree on the server;

[0135] If the server cannot be accessed normally, it is determined whether the second target software package exists locally, and offline deployment is performed based on the second target software package that already exists locally.

[0136] The technical solution of the embodiment of the present invention is to generate the first target software package in response to a request for generating the first target software package, if the content of the description file of the first target software package input by the user meets the verification condition; upload the first target software package to the server in response to an upload request for the first target software package; update the software package version tree on the server side based on the uploaded first target software package; download the second target software package based on the software package version tree on the server side in response to a download request for the second target software package; and deploy the second target software package to the vehicle. By adopting the solution of the present invention, the tasks of packaging, uploading, synchronizing and deploying different versions of vehicle-mounted software can be realized in the software development process, thereby realizing the full-line management of the vehicle software package, and can help developers quickly and conveniently manage the different versions of vehicle-mounted software generated in the development process, thereby improving development efficiency and shortening software deployment time.

[0137] The vehicle software package management device provided in the embodiment of the present invention can be used to execute the vehicle software package management method, and has corresponding functional modules and beneficial effects for executing the vehicle software package management method.

[0138] It is worth noting that the various units and modules included in the above-mentioned device are only divided according to functional logic, but are not limited to the above-mentioned division, as long as the corresponding functions can be achieved; in addition, the specific names of the functional units are only for the convenience of distinguishing each other, and are not used to limit the protection scope of the embodiments of the present invention.

[0139] Figure 4 A schematic diagram of the structure of an electronic device for implementing a vehicle software package management method provided by an embodiment of the present invention. Figure 4 , which shows a schematic diagram of the structure of an electronic device 410 suitable for implementing an embodiment of the present invention. The terminal device in the embodiment of the present invention may include but is not limited to mobile terminals such as mobile phones, notebook computers, digital broadcast receivers, PDAs (personal digital assistants), PADs (tablet computers), PMPs (portable multimedia players), vehicle-mounted terminals (such as vehicle-mounted navigation terminals), etc., and fixed terminals such as digital TVs, desktop computers, etc. Figure 4 The electronic device shown is only an example and should not bring any limitation to the functions and scope of use of the embodiments of the present invention.

[0140] like Figure 4As shown, the electronic device 410 includes at least one processor 411, and a memory connected to the at least one processor 411 in communication, such as a read-only memory (ROM) 412, a random access memory (RAM) 413, etc., wherein the memory stores a computer program that can be executed by at least one processor, and the processor 411 can perform various appropriate actions and processes according to the computer program stored in the read-only memory (ROM) 412 or the computer program loaded from the storage unit 418 to the random access memory (RAM) 413. In (RAM) 413, various programs and data required for the operation of the electronic device 410 can also be stored. The processor 411, (ROM) 412 and (RAM) 413 are connected to each other via a bus 414. An input / output (I / O) interface 415 is also connected to the bus 414.

[0141] Multiple components in the electronic device 410 are connected to the I / O interface 415, including: an input unit 416, such as a keyboard, a mouse, etc.; an output unit 417, such as various types of displays, speakers, etc.; a storage unit 418, such as a disk, an optical disk, etc.; and a communication unit 419, such as a network card, a modem, a wireless communication transceiver, etc. The communication unit 419 allows the electronic device 410 to exchange information / data with other devices through a computer network such as the Internet and / or various telecommunication networks.

[0142] The processor 411 may be any general and / or dedicated processing component with processing and computing capabilities. Some examples of the processor 411 include, but are not limited to, a central processing unit (CPU), a graphics processing unit (GPU), various dedicated artificial intelligence (AI) computing chips, various processors running machine learning model algorithms, a digital signal processor (DSP), and any appropriate processor, controller, microcontroller, etc. The processor 411 executes the vehicle software package management method provided in any embodiment of the present invention.

[0143] In particular, according to an embodiment of the present invention, the process described above with reference to the flowchart can be implemented as a computer software program. For example, an embodiment of the present invention includes a computer program product, which includes a computer program carried on a non-transitory computer-readable medium, and the computer program contains program code for executing the vehicle software package management method shown in the flowchart. When the computer program is executed by a processing device, the above functions defined in the vehicle software package management method of the embodiment of the present invention are executed.

[0144] The names of the messages or information exchanged between multiple devices in the embodiments of the present invention are only used for illustrative purposes, and are not used to limit the scope of these messages or information.

[0145] The electronic device provided in the embodiment of the present invention and the vehicle software package management method provided in the above embodiment belong to the same inventive concept. The technical details not fully described in this embodiment can be referred to the above embodiment, and this embodiment has the same beneficial effects as the above embodiment.

[0146] An embodiment of the present invention provides a computer storage medium on which a computer program is stored. When the program is executed by a processor, the vehicle software package management method provided in the above embodiment is implemented.

[0147] It should be noted that the computer-readable medium of the present invention can be a computer-readable signal medium or a computer-readable storage medium or any combination of the above two. The computer-readable storage medium can be, for example, but not limited to, an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, device or device, or any combination of the above. More specific examples of computer-readable storage media can include, but are not limited to: an electrical connection with one or more wires, a portable computer disk, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the above. In the present invention, a computer-readable storage medium can be any tangible medium containing or storing a program that can be used by or in combination with an instruction execution system, device or device. In the present invention, a computer-readable signal medium can include a data signal propagated in a baseband or as part of a carrier wave, which carries a computer-readable program code. This propagated data signal can take a variety of forms, including but not limited to electromagnetic signals, optical signals, or any suitable combination of the above. The computer readable signal medium may also be any computer readable medium other than a computer readable storage medium, which may send, propagate or transmit a program for use by or in conjunction with an instruction execution system, apparatus or device. The program code contained on the computer readable medium may be transmitted using any suitable medium, including but not limited to: wires, optical cables, RF (radio frequency), etc., or any suitable combination of the above.

[0148] In some embodiments, the client and the server may communicate using any currently known or future developed network protocol such as HTTP (HyperText Transfer Protocol), and may be interconnected with any form or medium of digital data communication (e.g., a communication network). Examples of communication networks include a local area network ("LAN"), a wide area network ("WAN"), an internet (e.g., the Internet), and a peer-to-peer network (e.g., an ad hoc peer-to-peer network), as well as any currently known or future developed network.

[0149] The computer-readable medium may be included in the electronic device, or may exist independently without being incorporated into the electronic device.

[0150] Computer program code for performing the operations of the present invention may be written in one or more programming languages ​​or a combination thereof, including but not limited to object-oriented programming languages, such as Java, Smalltalk, C++, and conventional procedural programming languages, such as "C" or similar programming languages. The program code may be executed entirely on the user's computer, partially on the user's computer, as a separate software package, partially on the user's computer and partially on a remote computer, or entirely on a remote computer or server. In the case of a remote computer, the remote computer may be connected to the user's computer via any type of network, including a local area network (LAN) or a wide area network (WAN), or may be connected to an external computer (e.g., via the Internet using an Internet service provider).

[0151] The flow chart and block diagram in the accompanying drawings illustrate the possible architecture, function and operation of the system, method and computer program product according to various embodiments of the present invention. In this regard, each square box in the flow chart or block diagram can represent a module, a program segment or a part of a code, and the module, the program segment or a part of the code contains one or more executable instructions for realizing the specified logical function. It should also be noted that in some alternative implementations, the functions marked in the square box can also occur in a sequence different from that marked in the accompanying drawings. For example, two square boxes represented in succession can actually be executed substantially in parallel, and they can sometimes be executed in the opposite order, depending on the functions involved. It should also be noted that each square box in the block diagram and / or flow chart, and the combination of the square boxes in the block diagram and / or flow chart can be implemented with a dedicated hardware-based system that performs the specified function or operation, or can be implemented with a combination of dedicated hardware and computer instructions.

[0152] The units involved in the embodiments of the present invention may be implemented by software or hardware. The name of a unit does not limit the unit itself in some cases. For example, the first acquisition unit may also be described as a "unit for acquiring at least two Internet Protocol addresses".

[0153] The functions described above herein may be performed at least in part by one or more hardware logic components. For example, without limitation, exemplary types of hardware logic components that may be used include: field programmable gate arrays (FPGAs), application specific integrated circuits (ASICs), application specific standard products (ASSPs), systems on chips (SOCs), complex programmable logic devices (CPLDs), and the like.

[0154] In the context of the present invention, a machine-readable medium may be a tangible medium that may contain or store a program for use by or in conjunction with an instruction execution system, device, or equipment. A machine-readable medium may be a machine-readable signal medium or a machine-readable storage medium. A machine-readable medium may include, but is not limited to, electronic, magnetic, optical, electromagnetic, infrared, or semiconductor systems, devices, or equipment, or any suitable combination of the foregoing. A more specific example of a machine-readable storage medium may include an electrical connection based on one or more lines, a portable computer disk, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing.

[0155] The above description is only a preferred embodiment of the present invention and an explanation of the technical principles used. Those skilled in the art should understand that the disclosure scope involved in the present invention is not limited to the technical solution formed by a specific combination of the above technical features, but should also cover other technical solutions formed by any combination of the above technical features or their equivalent features without departing from the above disclosed concept. For example, the above features are replaced with the technical features with similar functions disclosed in the present invention (but not limited to) by each other.

[0156] In addition, although each operation is described in a specific order, this should not be construed as requiring these operations to be performed in the specific order shown or in a sequential order. Under certain circumstances, multitasking and parallel processing may be advantageous. Similarly, although some specific implementation details are included in the above discussion, these should not be construed as limiting the scope of the present invention. Some features described in the context of a separate embodiment can also be implemented in a single embodiment in combination. On the contrary, the various features described in the context of a single embodiment can also be implemented in multiple embodiments individually or in any suitable sub-combination mode.

[0157] Although the subject matter has been described in language specific to structural features and / or methodological logical actions, it should be understood that the subject matter defined in the appended claims is not necessarily limited to the specific features or actions described above. On the contrary, the specific features and actions described above are merely example forms of implementing the claims.

Claims

1. A vehicle software package management method, characterized in that: The method comprises: In response to a request for generating a first target software package, if the content of the description file of the first target software package input by the user meets a verification condition, generating the first target software package; In response to an upload request for the first target software package, uploading the first target software package to a server; Based on the uploaded first target software package, updating the software package version tree on the server side; In response to a download request for a second target software package, downloading the second target software package based on the software package version tree on the server side; The second target software package is deployed on the vehicle.

2. The method according to claim 1, characterized in that The content of the description file of the first target software package input by the user meets the verification condition, including: Determining whether the version number naming in the description file of the first target software package is correct, so as to perform version number rule verification on the first target software package; It is determined whether configuration information in the description file of the first target software package is correct, so as to perform a high-risk operation check on the first target software package; the configuration information includes a set deployment chip, a startup script, and software dependencies.

3. The method according to claim 1, characterized in that Uploading the first target software package to the server includes: acquiring the first target software package based on the address of the first target software package; Determining whether a format of the description file of the first target software package complies with specifications, so as to perform a descriptive check on the first target software package; Determining whether files within the first target software package have been tampered with, so as to perform a file integrity check on the first target software package; After determining that the first target software package passes the descriptive check and the file integrity check, determining whether the first target software package has overwritten a locally existing historical first target software package, the historical first target software package being a software package of a previous version corresponding to the first target software package; If the first target software package has overwritten the locally existing historical first target software package, the first target software package is uploaded to the server.

4. The method according to claim 1, characterized in that Downloading the second target software package based on the software package version tree on the server side includes: Obtaining a software package version tree on the server side; Comparing the software package version tree on the server with the local software package version tree to determine the second target software package; The second target software package is downloaded based on a remote warehouse list on the server side, where at least one software package is stored in the remote warehouse list on the server side.

5. The method according to claim 4, characterized in that After downloading the second target software package based on the software package version tree on the server, the method further includes: Determine a first hash value based on the description file of the second target software package; Determine a second hash value based on the software information of the second target software package; Determine whether the first Hash value is the same as the second Hash value; If the judgment result is the same, the file of the second target software package has not been tampered with; If the judgment result is that they are not the same, the file of the second target software package has been tampered with, and the second target software package needs to be downloaded again.

6. The method according to claim 1, characterized in that Deploying the second target software package to the vehicle includes: Install the second target software package in a specified path and execute a startup script; wherein the specified path is determined based on a description file of the second target software package; Monitor the running status information and resource occupancy information of the second target software package, and record the running status information and the resource occupancy information to form monitoring record information; the monitoring record information is used to send to the vehicle-side system, so that the vehicle-side system can perform fault detection and performance optimization and adjustment on the vehicle-mounted software based on the monitoring record information.

7. The method according to claim 1, characterized in that After uploading the first target software package to the server, the method further includes: Determine whether the local network can access the server; If the server can be accessed normally, online deployment is performed based on the software package version tree on the server side; If the server cannot be accessed normally, it is determined whether the second target software package exists locally, and offline deployment is performed based on the locally existing second target software package.

8. A vehicle software package management device, characterized in that: The device comprises: A first target software package generating module, configured to generate the first target software package in response to a generation request of the first target software package if the content of the description file of the first target software package input by the user satisfies a verification condition; a first target software package uploading module, configured to upload the first target software package to a server in response to an upload request for the first target software package; A server-side version tree update module, used to update the server-side software package version tree based on the uploaded first target software package; A second target software package downloading module, configured to respond to a download request for the second target software package and download the second target software package based on the software package version tree on the server side; The second target software package deployment module is used to deploy the second target software package on the vehicle.

9. An electronic device, characterized in that: The electronic device comprises: one or more processors; a storage device for storing one or more programs, When the one or more programs are executed by the one or more processors, the one or more processors implement the vehicle software package management method as described in any one of claims 1-7.

10. A storage medium containing computer executable instructions, characterized in that: The computer executable instructions are used to perform the vehicle software package management method as claimed in any one of claims 1 to 7 when executed by a computer processor.