Software version management method of intelligent driving system, electronic equipment and storage medium

Abstract

The invention discloses a software version management method of an intelligent driving system, electronic equipment and a storage medium. The method comprises the following steps: receiving at least one module version selection operation, wherein the module version selection operation is triggered after a user completes edition of a version number of a software template in a module version updating window; displaying the version number of each software module; receiving a software version package generation operation, wherein the software version package generation operation is triggering a generation button of the software version package; generating a software version package; displaying the information of the software version package; receiving a software version package release operation, wherein the software version package release operation is triggering a release button of the software version package; the software version package is released, the problem that software version management of the intelligent driving system is difficult and disordered is solved, module version numbers in the software version updating process are selected through visual operation, the software version package is generated, and the software version management process is simple and convenient to operate; and the condition of disordered software version management is avoided.

Description

Technical Field

[0001] The present invention relates to the field of computer technology, and in particular to a software version management method, electronic device and storage medium for an intelligent driving system. Background Art

[0002] The software architecture of self-driving cars usually includes multiple modules and is a relatively complex software system. The modularization of the software clarifies the layered architecture of the software, improves the efficiency of development, and reduces the difficulty of problem repair, but also increases the difficulty of system version integration. At present, there are no systematic version management specifications and mature version management methods, and the version management of intelligent driving software is difficult and the management process is chaotic. Due to the modular characteristics of automobile intelligent driving software, system version integration management is difficult, which easily causes version confusion. Summary of the invention

[0003] The present invention provides a software version management method, electronic device and storage medium of an intelligent driving system, so as to solve the problem that software version management of the intelligent driving system is difficult and confusing.

[0004] According to one aspect of the present invention, a software version management method for an intelligent driving system is provided, comprising:

[0005] receiving at least one module version selection operation, wherein the module version selection operation is triggered after the user completes editing of the version number of the software template in the module version update window;

[0006] Display the version number of each software module;

[0007] Receiving a software version package generation operation, wherein the software version package generation operation is triggering a generation button of the software version package;

[0008] Generate software version package;

[0009] Display information about the software version package;

[0010] Receiving a software version package publishing operation, wherein the software version package publishing operation is triggering a publishing button of the software version package;

[0011] Release the software version package.

[0012] According to another aspect of the present invention, an electronic device is provided, the electronic device comprising:

[0013] at least one processor, and a memory communicatively coupled to the at least one processor;

[0014] In which, the memory stores a computer program that can be executed by the at least one processor, and the computer program is executed by the at least one processor so that the at least one processor can execute the software version management method of the intelligent driving system described in any embodiment of the present invention.

[0015] According to another aspect of the present invention, a computer-readable storage medium is provided, wherein the computer-readable storage medium stores computer instructions, and the computer instructions are used to enable a processor to implement the software version management method of the intelligent driving system described in any embodiment of the present invention when executed.

[0016] The technical solution of the embodiment of the present invention solves the problem of difficult and chaotic software version management of the intelligent driving system by receiving at least one module version selection operation, the module version selection operation is triggered after the user completes editing the version number of the software template in the module version update window; displaying the version number of each software module; receiving a software version package generation operation, the software version package generation operation is the triggering of a software version package generation button; generating a software version package; displaying the information of the software version package; receiving a software version package publishing operation, the software version package publishing operation is the triggering of a software version package publishing button; publishing the software version package, and selecting the module version number in the software version update process through a visual operation, generating a software version package based on the user's software version package generation operation and the version number of the selected software module, receiving a software version package publishing operation, and publishing the software version package in response to this operation. The entire software version management process is simple and easy to operate; the user can perform visual management of complex software versions through simple operations, the management process is clear and easy to understand, and the chaotic software version management is avoided.

[0017] It should be understood that the contents described in this section are not intended to identify the key or important features of the embodiments of the present invention, nor are they intended to limit the scope of the present invention. Other features of the present invention will become easily understood through the following description. BRIEF DESCRIPTION OF THE DRAWINGS

[0018] In order to more clearly illustrate the technical solutions in the embodiments of the present invention, the following briefly introduces the drawings required for use in the description of the embodiments. Obviously, the drawings described below are only some embodiments of the present invention. For ordinary technicians in this field, other drawings can be obtained based on these drawings without creative work.

[0019] Figure 1 is a flowchart of a software version management method for an intelligent driving system provided according to Embodiment 1 of the present invention;

[0020] Figure 2This is a display example diagram of a module version update window and a version number of a software module provided according to Embodiment 1 of the present invention;

[0021] Figure 3 is a flowchart of a software version management method for an intelligent driving system provided according to a second embodiment of the present invention;

[0022] Figure 4 This is an example diagram showing information of a software version package provided according to Embodiment 2 of the present invention;

[0023] Figure 5 This is a display example diagram of a software version publishing interface provided according to Embodiment 2 of the present invention;

[0024] Figure 6 This is a display example diagram of a module version update interface provided according to Embodiment 2 of the present invention;

[0025] Figure 7 This is a display example diagram of a configuration version update interface provided according to Embodiment 2 of the present invention;

[0026] Figure 8 This is an example diagram of a display interface of software package information provided according to Embodiment 2 of the present invention;

[0027] Fig. 9 This is an example diagram of a display interface for all information of a software package provided in Embodiment 2 of the present invention;

[0028] Fig.10 is a structural diagram of a software version management device for an intelligent driving system provided according to a third embodiment of the present invention;

[0029] Fig.11 It is a structural diagram of an electronic device that implements the software version management method of the intelligent driving system according to an embodiment of the present invention. DETAILED DESCRIPTION

[0030] In order to enable those skilled in the art to better understand the scheme of the present invention, the technical scheme in the embodiments of the present invention will be clearly and completely described below in conjunction with the drawings in the embodiments of the present invention. Obviously, the described embodiments are only part of the embodiments of the present invention, not all of the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by ordinary technicians in this field without creative work should fall within the scope of protection of the present invention.

[0031] It should be noted that the terms "first", "second", etc. in the specification and claims of the present invention and the above-mentioned drawings are used to distinguish similar objects, and are not necessarily used to describe a specific order or sequence. It should be understood that the data used in this way can be interchanged where appropriate, so that the embodiments of the present invention described herein can be implemented in an order other than those illustrated or described herein. In addition, the terms "including" and "having" and any variations thereof are intended to cover non-exclusive inclusions, for example, a process, method, system, product or device that includes a series of steps or units is not necessarily limited to those steps or units that are clearly listed, but may include other steps or units that are not clearly listed or inherent to these processes, methods, products or devices.

[0032] Embodiment 1

[0033] Figure 1 This is a flowchart of a software version management method for an intelligent driving system provided in Embodiment 1 of the present invention. This embodiment can be applied to the situation of standardized management of software versions of intelligent driving systems. The method can be executed by a software version management device for an intelligent driving system. The software version management device for an intelligent driving system can be implemented in the form of hardware and / or software. The software version management device for an intelligent driving system can be configured in an electronic device.

[0034] It should be noted that the method provided in this embodiment can be integrated as an application client on an electronic device, or can be presented as an application webpage on an electronic device. The electronic device can manage the version of the software in the intelligent driving system through the method provided in this embodiment. The embodiment of this application can implement operations such as updating and viewing the software version in the system.

[0035] like Figure 1 As shown, the method includes:

[0036] S101. Receive at least one module version selection operation, where the module version selection operation is triggered after a user completes editing of a version number of a software template in a module version update window.

[0037] In this embodiment, the module version selection operation can be understood as an operation of selecting the version of a module in the intelligent driving system software. The software module can be understood as a module in the intelligent driving system software, such as a perception module, a positioning module, a planning module, a control module, and a drive module. The module version update window can be understood as a window for updating the version of the software module, such as a sliding window that provides data options, a window that can edit and input data, and so on.

[0038] It should be noted that this step can be considered as the execution logic after the user enters the management interface of the software version in the corresponding application or web page through operation. This execution subject can present a corresponding interface after entering the management application of the corresponding software version, and the interface includes at least one module version update window, each module version update window corresponds to a software module to realize the version update of this software module, and the user can manually enter the new version number (or updated version number) of the software module in the module version update window, or the module version update window is a sliding window, and the user can click the operation, and the corresponding user's click operation is that the user selects the selectable version number of the software module, and the user manually selects one of the version numbers as the new version number. After completing the input or selection of the version number of the software module, the module version selection operation is triggered. Since multiple module version update windows may be displayed on the interface, the user can edit the version number of the software template in multiple module version update windows respectively.

[0039] This execution subject receives at least one module version selection operation through this step.

[0040] Developers can develop software modules in advance and then name the version numbers of the software modules. There are certain rules for the iteration of version numbers. For the xyz-rc version number, x represents the major version number, y is the minor version number, z is the revision number, and rc is the candidate version number. x, y, and z must be non-negative integers, and each version number must increase numerically. There are many version requirement specifications. In the present invention, when one or some modules undergo minor modifications or functional additions, the major version number and the minor version number remain unchanged, and the revision number increases; when the architecture or function of a module undergoes major changes, the minor version number increases; when the software architecture of the entire intelligent driving system changes, or the algorithms or software architectures of multiple modules undergo major changes, or the minor version number increases to a certain requirement, the major version number changes.

[0041] S102: Display the version number of each software module.

[0042] Displays the version number of each edited software module, which is the updated version number.

[0043] For example, Figure 2Provided is a module version update window and a display example diagram of the version number of a software module. The rectangular box in the figure is a module version update window. Each module version update window corresponds to a software module. The user can manually enter the version number of the software module in the module version update window, or display all the version numbers corresponding to the software module in a drop-down box. The user can select one of them through operation. The figure only shows 4 module version update windows and the version number of one of the software modules. The downward small label in the rectangular box in the figure can realize the drop-down box function, that is, the user can click this label, and the execution subject will display all the version numbers corresponding to this software module after receiving the user's click operation.

[0044] S103: Receive a software version package generation operation, where the software version package generation operation is triggering a generation button for the software version package.

[0045] In this embodiment, the software version package generation operation can be understood as the operation of the user instructing to generate the software version package; the generation button can be understood as an operable button for generating the software version package, for example, a button of any shape is displayed in the interface, and the user can trigger the generation button by single-clicking, double-clicking, etc. The user can trigger the generation button after selecting the version number of each software module. This execution subject receives the software version package generation operation through this step.

[0046] S104: Generate a software version package.

[0047] According to the version number of each software module, a corresponding file, that is, a data package of each developed software module is obtained, and a software version package is generated based on the data package of each software module.

[0048] S105: Display software version package information.

[0049] In this embodiment, the information of the software version package can be understood as information describing the software version package, for example, the version number of the software version package, the generation time of the software version package, the software modules included in the software version package, the software modules updated in the software version package, the user who generated the software version package, etc. The information of the software version package may include one or more of the above information.

[0050] S106: Receive a software version package publishing operation, where the software version package publishing operation is triggering a publishing button of the software version package.

[0051] In this embodiment, the software version package publishing operation can be understood as the operation of the user instructing to publish the software version package; the publishing button can be understood as an operable button for publishing the software version package, for example, a button of any shape is displayed in the interface, and the user can trigger the publishing button by single-clicking, double-clicking, etc. The user can trigger the publishing button after confirming that the information of the software version package is correct. This execution subject receives the software version package publishing operation through this step.

[0052] S107. Release the software version package.

[0053] Release the software version package. The released software version package can be displayed in the management interface for users to view and download. Users can view the released software version package, download the software version package, run the new version of the software module, and implement software function updates.

[0054] An embodiment of the present invention provides a software version management method for an intelligent driving system, which receives at least one module version selection operation, wherein the module version selection operation is triggered after a user completes editing of a version number of a software template in a module version update window; displays the version number of each software module; receives a software version package generation operation, wherein the software version package generation operation is the triggering of a software version package generation button; generates a software version package; displays information of the software version package; receives a software version package publishing operation, wherein the software version package publishing operation is the triggering of a software version package publishing button; and publishes the software version package, thereby solving the problem of difficult and chaotic software version management of the intelligent driving system. The module version number in the software version update process is selected through a visual operation, a software version package is generated based on the user's software version package generation operation and the version number of the selected software module, a software version package is received, and a software version package is published in response to the operation. The entire software version management process is simple and easy to operate. The user can perform visual management of complex software versions through simple operations, and the management process is clear and easy to understand, thereby avoiding the situation of chaotic software version management.

[0055] Embodiment 2

[0056] Figure 3 This is a flowchart of a software version management method for an intelligent driving system provided in Embodiment 2 of the present invention. This embodiment is refined on the basis of the above embodiment. Figure 3 As shown, the method includes:

[0057] S201. Receive at least one module version selection operation, where the module version selection operation is triggered after the user completes editing of the version number of the software template in the module version update window.

[0058] S202: Display the version number of each software module.

[0059] S203: Receive a software update writing trigger operation, where the software update writing trigger operation is triggering a software update writing function button.

[0060] In this embodiment, the software update writing trigger operation can be understood as an operation in which the user instructs to edit the relevant information of the software update; the software update writing function button can be understood as an operable button for writing the software update information, for example, a button of any shape is displayed in the interface, and the user can trigger the software update writing function button by single-clicking, double-clicking, etc. The user can trigger the software update writing function button after confirming that the version number of the software module is correct. This execution subject receives the software update writing trigger operation through this step.

[0061] S204: Display a software update writing interface, where the software update writing interface includes at least one software update writing window.

[0062] In this embodiment, the software update writing interface can be understood as an interface for writing information in the software update process. The software update writing window can be understood as an editable window for inputting software update information, and the software update information can be understood as information describing the software update.

[0063] The software update editing interface is displayed, and the software update editing interface includes at least one software update editing window. Each software update editing window is used to edit different types of information, for example, to edit the time of this software update, to edit the user who performs the software update, to summarize and edit the releasenote, to edit the added, deleted, and modified content, etc.

[0064] S205: Receive at least one software update writing operation, where the software update writing operation is triggered after the user completes editing of software update information in each software update writing window.

[0065] In this embodiment, the software update writing operation can be understood as an operation for editing the relevant information of the software update. At least one software update writing window is displayed in the software update writing interface, and each window is used to write different types of information. The user edits the corresponding software update information in the software update writing window, and triggers the software update writing operation after editing. The user can edit the corresponding software update information in one or more software update writing windows, and trigger the software update writing operation after editing; the embodiment of the present application can also set mandatory items and optional items when the number of software update writing windows is multiple. For mandatory items, the user is required to edit the software update information in the software update writing window. For optional items, the user can choose whether to edit the software update information in this software update writing window as needed. The present execution subject receives at least one software update writing operation through this step.

[0066] S206: Display the compiled software update information.

[0067] S207: Receive a software version package generation operation, where the software version package generation operation is triggering a generation button for the software version package.

[0068] S208: Obtain the installation package of each software module according to the version number of each software module.

[0069] The installation packages corresponding to the different version numbers of each software module are stored in advance. After completing the update of the software module, the R&D personnel store the installation package in the corresponding space according to the pre-set path. After determining the version number of each software module selected by the user, the corresponding installation package is read according to the set storage path.

[0070] S209: Generate a software version package according to each installation package and each software update information.

[0071] The installation packages are stored randomly or in accordance with a set rule, sequence, etc. in the same folder, and the software update message is used as information describing the software version package to form a software version package.

[0072] S210: Display software version package information.

[0073] For example, Figure 4 An example diagram for displaying information of a software version package is provided, which exemplarily displays different types of information of a software version package.

[0074] S211: Receive a software version package publishing operation, where the software version package publishing operation is triggering a publishing button of the software version package.

[0075] S212. Release the software version package.

[0076] As an optional embodiment of this embodiment, this optional embodiment is further optimized, and before receiving at least one module version selection operation, it also includes:

[0077] A1. Receive a software version update operation, where the software version update operation is triggering a software version update button.

[0078] In this embodiment, the software version update operation can be understood as a user operation for triggering a software update. The software version update button can be understood as an operable button for triggering software version update information. For example, a button of any shape is displayed in the interface, and the user can trigger the software version update button by single-clicking, double-clicking, etc. The software version update button can be displayed in the application interface of the software version management. After the user enters the application interface of the software version management, the user can see the displayed software version update button. When the user determines that a software update is required, the software version update button is triggered. This execution subject receives the software version update operation through this step.

[0079] A2. Display a software version release interface, where the software version release interface includes at least one software version basic information update window.

[0080] In this embodiment, the software version release interface can be understood as the interface displayed when the software version is released, that is, the interface presented to the user. The software version basic information update window can be understood as an editable window for inputting basic information of the software version. Each window of the software version basic information update window can input different types of data.

[0081] The software version release interface is displayed, and the software version release interface includes at least one software version basic information update window. Each software version basic information update window can be sorted according to preset rules and displayed in the software version release interface.

[0082] A3. Receive a software basic information update operation, where the software basic information update operation is triggered after the user completes editing of the software version basic information in the software version basic information update window.

[0083] In this embodiment, the software basic information update operation can be understood as a user operation for triggering the software basic information update. The user edits and inputs the software version basic information in the software version basic information update window, and after completing the editing of the software version basic information, the software basic information update operation is triggered.

[0084] A4. Display the basic information of the updated software version.

[0085] The updated software version basic information is displayed. Users can check the displayed software version basic information and proceed to the next step after confirming that it is correct.

[0086] For example, Figure 5 A software version release interface is provided, which includes multiple software version basic information update windows, such as Figure 5The rectangular box shown in the figure; the user can edit the basic information of the software version in the software version basic information update window; the light gray text in the rectangular box in the figure is the information to prompt the user, and it can disappear automatically after the user edits the corresponding information, for example, "Please select a warehouse", "Please select a product type", etc.; the rectangular box in the lower right corner of the figure can be used as a button, and the user can enter the previous operation, the next operation, cancel, etc. after triggering this button.

[0087] The method provided in the embodiment of the present application can execute steps B1-B2 after executing steps A1-A4.

[0088] As an optional embodiment of this embodiment, this optional embodiment is further optimized, and before receiving at least one module version selection operation, it also includes:

[0089] B1. Receive a module and configuration version update operation, where the module and configuration version update operation is a triggering of a generation button for the module and configuration version.

[0090] In this embodiment, the module and configuration version update operation can be understood as a user operation for triggering the module and configuration version update. A module and configuration version generation button is displayed in the display interface, and the user can trigger this button by single-clicking, double-clicking, etc. The user triggers the module and configuration version generation button by operating to generate the module and configuration version update operation. This execution subject receives the module and configuration version update operation through this step.

[0091] B2. Display a module version update interface, where the module version update interface includes at least one module version update window.

[0092] In this embodiment, the module version update interface can be understood as a display interface for updating the module version. The module version update interface includes at least one module version update window, and each module version update window is sorted according to certain rules and displayed in this interface. The module version update window can set the display position, size, etc. according to the type and priority of the corresponding software module. After the module version update interface is displayed, the user can complete the editing of the version number of the software template in the module version update window to trigger the module version selection operation.

[0093] Optionally, the module version update interface further includes a switch button, and the method further includes:

[0094] C1. Receive a switching operation, where the switching operation is the user triggering a switching button.

[0095] In this embodiment, the switching operation can be understood as a user operation for switching software updates. The switching button can be understood as an operable button for switching the software display interface. For example, a button of any shape is displayed in the interface, and the user can trigger the switching button by single-clicking, double-clicking, etc. The switching button is displayed in the module version update interface, and the user triggers the switching button if he needs to switch the operation interface. This execution subject receives the switching operation through this step.

[0096] C2. Displaying a configuration version update interface, where the configuration version update interface includes at least one configuration version update window.

[0097] In this embodiment, the configuration version update interface can be understood as an interface for updating the configuration version. The configuration version update window can be understood as an editable window for updating the version of the configuration information. The configuration version update interface is displayed, and at least one configuration version update window is displayed in the configuration version update interface, and each configuration version update window is displayed in this interface according to certain rules.

[0098] Optionally, the method further includes: receiving at least one configuration version selection operation, the configuration version selection operation being triggered after the user completes editing of the version number of the configuration version in the configuration version update window; and displaying the version number of each configuration version.

[0099] In this embodiment, the configuration version selection operation can be understood as an operation for selecting the version of the configuration information in the intelligent driving system software. The user can manually enter the new version number (or updated version number) of the configuration version in the configuration version update window, or the configuration version update window is a sliding window, and the user can perform a click operation, and the corresponding user's click operation is that the user selects the selectable version number of the configuration version, and the user manually selects one of the version numbers as the new version number. After completing the input or selection of the version number of the configuration version, the configuration version selection operation is triggered. Since multiple configuration version update windows may be displayed on the interface, the user can edit the version number of the configuration information in multiple configuration version update windows respectively. This execution subject receives at least one configuration version selection operation through this step.

[0100] The configuration version update interface also includes a switch button. When the configuration version update interface is displayed, the user can also switch the display interface from the configuration version update interface to the module version update interface through the switch operation.

[0101] For example, Figure 6 An example diagram of a module version update interface is provided, wherein a user can click a switch button 11 to switch the displayed module version update interface to a configuration version update interface.

[0102] For example, Figure 7 An example diagram for displaying a configuration version update interface is provided, wherein a user can click a switch button 12 to switch the displayed configuration version update interface to a module version update interface.

[0103] As an optional embodiment of this embodiment, this optional embodiment is further optimized to include:

[0104] D1. Receive a software package display operation, where the software package display operation is triggering a display button of the software package.

[0105] In this embodiment, the software package display operation can be understood as an operation of displaying a software package, and the software package that has been released can be displayed. The display button can be understood as an operable button for selecting and displaying a software package. For example, a button of any shape is displayed in the interface, and the user can trigger the display button by single-clicking, double-clicking, etc. When the user needs to view the specific information of the software package, the display button of the software package can be triggered. This execution subject receives the software package display operation through this step.

[0106] D2. Display at least one software package information, where the software package information includes software package type and / or version type.

[0107] In this embodiment, the software package type may be music playback, air conditioning control, seat adjustment, etc.; the version type may be a pre-release version, a released version, a version to be tested, etc. The corresponding information of each software package is displayed. Each software package includes at least one information. The software package information may also include test results, creation user, creation time, creation branch, source branch, version number, etc. At least one software package information is displayed on the display interface. Each software package information briefly describes the information of a software.

[0108] For example, Figure 8 An example diagram of a display interface for software package information is provided, wherein the information in the first row is the type of content displayed in each column, for example, different information types and operations, and each line from the second row to the last row is software package information corresponding to a software package and an operation that can be performed on the software package. A user can click to trigger an operation, and the operation can be view, download, etc., and the corresponding operation button is displayed in the interface accordingly, wherein: Figure 8 The downward arrow in the last column is the download button, and the triangle is the view button.

[0109] D3. Receive a software package viewing operation, where the software package viewing operation is triggering a view button of the software package.

[0110] In this embodiment, the software package viewing operation can be understood as a user operation for viewing the specific information of the software package. The view button can be understood as an operable button for viewing the specific information of the software package. A button of any shape is displayed in the interface, and the user can trigger this view button by single-clicking, double-clicking, etc. The user determines the software package to be viewed according to the needs and clicks the corresponding display button. Multiple software packages can be displayed in the display interface, and the display button of each software package is displayed accordingly. The user can trigger the viewing operation of the specific information of this software package by clicking the view button of each software package. This execution subject receives the software package viewing operation through this step.

[0111] D4. Display all information of the software package.

[0112] For example, Fig. 9 An example diagram of a display interface of all information of a software package is provided, in which only several software modules and configurations are exemplarily displayed, and the number of software modules and configurations can be the same or different.

[0113] The embodiment of the present invention provides a software version management method for an intelligent driving system, which solves the problem of difficult and chaotic software version management of the intelligent driving system. The module version number in the software version update process is selected through visual operation, a software version package is generated based on the user's software version package generation operation and the version number of the selected software module, a software version package is received, and a software version package is released in response to this operation. The entire software version management process is simple and easy to operate; users can visually manage complex software versions through simple operations, and the management process is clear and easy to understand, avoiding the situation of chaotic software version management. When managing software version packages, the management method provided by the present application reduces the risk of generating product packages through code cloud instruction operations and reduces the difficulty of operation.

[0114] Embodiment 3

[0115] Fig.10 This is a schematic diagram of the structure of a software version management device for an intelligent driving system provided by Embodiment 3 of the present invention. Fig.10 As shown, the device includes: a module version selection operation receiving module 31, a module version number display module 32, a software package generation operation receiving module 33, a software version package generation module 34, a software package information display module 35, a software package publishing operation receiving module 36 and a software package publishing module 37.

[0116] The module version selection operation receiving module is used to receive at least one module version selection operation, wherein the module version selection operation is triggered after the user completes editing the version number of the software template in the module version update window;

[0117] Module version number display module, used to display the version number of each software module;

[0118] A software package generation operation receiving module, used to receive a software version package generation operation, wherein the software version package generation operation is a triggering of a generation button of the software version package;

[0119] A software version package generation module, used to generate a software version package;

[0120] A software package information display module, used to display the information of the software version package;

[0121] A software package publishing operation receiving module, used to receive a software version package publishing operation, wherein the software version package publishing operation is the triggering of a publishing button of the software version package;

[0122] The software package publishing module is used to publish the software version package.

[0123] An embodiment of the present invention provides a software version management device for an intelligent driving system, which solves the problem of difficult and chaotic software version management of the intelligent driving system. The device selects the module version number in the software version update process through visual operation, generates a software version package based on the user's software version package generation operation and the version number of the selected software module, receives a software version package publishing operation, and publishes the software version package in response to the operation. The entire software version management process is simple and easy to operate. The user can perform visual management of complex software versions through simple operations, and the management process is clear and easy to understand, avoiding chaotic software version management.

[0124] Optionally, the device further comprises:

[0125] A writing trigger operation receiving module, used to receive a software update writing trigger operation, wherein the software update writing trigger operation is a trigger of a software update writing function button;

[0126] An update writing interface display module, used to display a software update writing interface, wherein the software update writing interface includes at least one software update writing window;

[0127] An update writing operation receiving module, used to receive at least one software update writing operation, wherein the software update writing operation is triggered after the user completes editing of the software update information in each of the software update writing windows;

[0128] The editing information display module is used to display the edited software update information.

[0129] Optionally, the software version package generating module 34 is specifically used to: obtain the installation package of the software module according to the version number of each software module; and generate a software version package according to each installation package and each software update information.

[0130] Optionally, the device further comprises:

[0131] A first update operation receiving module, configured to receive a software version update operation before receiving at least one module version selection operation, wherein the software version update operation is a triggering of a software version update button;

[0132] A release interface display module, used to display a software version release interface, wherein the software version release interface includes at least one software version basic information update window;

[0133] A basic information update operation receiving module, used for receiving a software basic information update operation, wherein the software basic information update operation is triggered after the user completes editing of the software version basic information in the software version basic information update window;

[0134] The basic information display module is used to display the basic information of the updated software version.

[0135] Optionally, the device further comprises:

[0136] A second update operation receiving module, used for receiving a module and configuration version update operation before receiving at least one module version selection operation, wherein the module and configuration version update operation is a triggering of a generation button for a module and configuration version;

[0137] The update interface display module is used to display a module version update interface, wherein the module version update interface includes at least one module version update window.

[0138] Optionally, the module version update interface further includes a switch button, and the device further includes:

[0139] A switching operation receiving module, used to receive a switching operation, wherein the switching operation is a triggering of the switching button by a user;

[0140] The version update interface display operation is used to display a configuration version update interface, wherein the configuration version update interface includes at least one configuration version update window.

[0141] Optionally, the device further comprises:

[0142] A configuration version selection operation receiving module, used to receive at least one configuration version selection operation, where the configuration version selection operation is triggered after the user completes editing the version number of the configuration version in the configuration version update window;

[0143] The configuration version number display module is used to display the version number of each configuration version.

[0144] Optionally, the device further comprises:

[0145] A software package display operation receiving module, used to receive a software package display operation, wherein the software package display operation is the triggering of a display button of the software package;

[0146] A first software package information display module, used to display at least one software package information, wherein the software package information includes a software package type and / or a version type;

[0147] A software package viewing operation receiving module, used to receive a software package viewing operation, wherein the software package viewing operation is the triggering of a view button of a software package;

[0148] The second software package information display module is used to display all information of the software package.

[0149] The software version management device of the intelligent driving system provided in the embodiment of the present invention can execute the software version management method of the intelligent driving system provided in any embodiment of the present invention, and has the corresponding functional modules and beneficial effects of the execution method.

[0150] Embodiment 4

[0151] Fig.11 A schematic diagram of the structure of an electronic device 40 that can be used to implement an embodiment of the present invention is shown. The electronic device is intended to represent various forms of digital computers, such as laptop computers, desktop computers, workstations, personal digital assistants, servers, blade servers, mainframe computers, and other suitable computers. The electronic device can also represent various forms of mobile devices, such as personal digital assistants, cellular phones, smart phones, wearable devices (such as helmets, glasses, watches, etc.) and other similar computing devices. The components shown herein, their connections and relationships, and their functions are merely examples and are not intended to limit the implementation of the present invention described and / or required herein.

[0152] like Fig.11 As shown, the electronic device 40 includes at least one processor 41, and a memory connected to the at least one processor 41, such as a read-only memory (ROM) 42, a random access memory (RAM) 43, etc., wherein the memory stores a computer program that can be executed by at least one processor, and the processor 41 can perform various appropriate actions and processes according to the computer program stored in the read-only memory (ROM) 42 or the computer program loaded from the storage unit 48 to the random access memory (RAM) 43. In the RAM 43, various programs and data required for the operation of the electronic device 40 can also be stored. The processor 41, the ROM 42, and the RAM 43 are connected to each other through a bus 44. An input / output (I / O) interface 45 is also connected to the bus 44.

[0153] A number of components in the electronic device 40 are connected to the I / O interface 45, including: an input unit 46, such as a keyboard, a mouse, etc.; an output unit 47, such as various types of displays, speakers, etc.; a storage unit 48, such as a disk, an optical disk, etc.; and a communication unit 49, such as a network card, a modem, a wireless communication transceiver, etc. The communication unit 49 allows the electronic device 40 to exchange information / data with other devices through a computer network such as the Internet and / or various telecommunication networks.

[0154] The processor 41 may be a variety of general and / or special processing components with processing and computing capabilities. Some examples of the processor 41 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, digital signal processors (DSPs), and any appropriate processors, controllers, microcontrollers, etc. The processor 41 executes the various methods and processes described above, such as the software version management method of the intelligent driving system.

[0155] In some embodiments, the software version management method of the intelligent driving system may be implemented as a computer program, which is tangibly contained in a computer-readable storage medium, such as a storage unit 48. In some embodiments, part or all of the computer program may be loaded and / or installed on the electronic device 40 via the ROM 42 and / or the communication unit 49. When the computer program is loaded into the RAM 43 and executed by the processor 41, one or more steps of the software version management method of the intelligent driving system described above may be performed. Alternatively, in other embodiments, the processor 41 may be configured to execute the software version management method of the intelligent driving system in any other appropriate manner (e.g., by means of firmware).

[0156] Various implementations of the systems and techniques described above herein can be implemented in digital electronic circuit systems, integrated circuit systems, field programmable gate arrays (FPGAs), application specific integrated circuits (ASICs), application specific standard products (ASSPs), systems on chips (SOCs), load programmable logic devices (CPLDs), computer hardware, firmware, software, and / or combinations thereof. These various implementations can include: being implemented in one or more computer programs that can be executed and / or interpreted on a programmable system including at least one programmable processor, which can be a special purpose or general purpose programmable processor that can receive data and instructions from a storage system, at least one input device, and at least one output device, and transmit data and instructions to the storage system, the at least one input device, and the at least one output device.

[0157] Computer programs for implementing the methods of the present invention may be written in any combination of one or more programming languages. These computer programs may be provided to a processor of a general-purpose computer, a special-purpose computer, or other programmable data processing device, so that when the computer program is executed by the processor, the functions / operations specified in the flow chart and / or block diagram are implemented. The computer program may be executed entirely on the machine, partially on the machine, partially on the machine and partially on a remote machine as a stand-alone software package, or entirely on a remote machine or server.

[0158] An embodiment of the present invention provides a computer program product, which includes a computer program. When the computer program is executed by a processor, it implements the software version management method of the intelligent driving system described in any embodiment of the present invention.

[0159] In the context of the present invention, a computer-readable storage medium may be a tangible medium that may contain or store a computer program for use by or in combination with an instruction execution system, device or equipment. A computer-readable storage 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. Alternatively, a computer-readable storage medium may be a machine-readable signal medium. 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.

[0160] To provide interaction with a user, the systems and techniques described herein may be implemented on an electronic device having: a display device (e.g., a CRT (cathode ray tube) or LCD (liquid crystal display) monitor) for displaying information to the user; and a keyboard and a pointing device (e.g., a mouse or trackball) through which the user can provide input to the electronic device. Other types of devices may also be used to provide interaction with the user; for example, the feedback provided to the user may be any form of sensory feedback (e.g., visual feedback, auditory feedback, or tactile feedback); and input from the user may be received in any form (including acoustic input, voice input, or tactile input).

[0161] The systems and techniques described herein may be implemented in a computing system that includes backend components (e.g., as a data server), or a computing system that includes middleware components (e.g., an application server), or a computing system that includes frontend components (e.g., a user computer with a graphical user interface or a web browser through which a user can interact with implementations of the systems and techniques described herein), or a computing system that includes any combination of such backend components, middleware components, or frontend components. The components of the system may be interconnected by 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), a blockchain network, and the Internet.

[0162] A computing system may include a client and a server. The client and the server are generally remote from each other and usually interact through a communication network. The client and server relationship is generated by computer programs running on the corresponding computers and having a client-server relationship with each other. The server may be a cloud server, also known as a cloud computing server or cloud host, which is a host product in the cloud computing service system to solve the defects of difficult management and weak business scalability in traditional physical hosts and VPS services.

[0163] It should be understood that the various forms of processes shown above can be used to reorder, add or delete steps. For example, the steps described in the present invention can be executed in parallel, sequentially or in different orders, as long as the desired results of the technical solution of the present invention can be achieved, and this document does not limit this.

[0164] The above specific implementations do not constitute a limitation on the protection scope of the present invention. It should be understood by those skilled in the art that various modifications, combinations, sub-combinations and substitutions can be made according to design requirements and other factors. Any modification, equivalent substitution and improvement made within the spirit and principle of the present invention should be included in the protection scope of the present invention.

Claims

1. A software version management method for an intelligent driving system, characterized in that: include: receiving at least one module version selection operation, wherein the module version selection operation is triggered after a user completes editing of a version number of a software template in a module version update window; Display the version number of each software module; Receiving a software version package generation operation, wherein the software version package generation operation is triggering a generation button of the software version package; Generate software version package; Display information about the software version package; Receiving a software version package publishing operation, wherein the software version package publishing operation is triggering a publishing button of the software version package; Release the software version package.

2. The method according to claim 1, characterized in that: Before the receiving software version package generation operation, the method further includes: Receiving a software update writing trigger operation, wherein the software update writing trigger operation is triggering a software update writing function button; Displaying a software update writing interface, wherein the software update writing interface includes at least one software update writing window; receiving at least one software update writing operation, wherein the software update writing operation is triggered after the user completes editing of software update information in each of the software update writing windows; Displays software update information after it is written.

3. The method according to claim 2, characterized in that The generated software version package includes: Obtaining the installation package of the software module according to the version number of each software module; A software version package is generated according to each of the installation packages and each of the software update information.

4. The method according to claim 1, characterized in that: Before receiving at least one module version selection operation, the method further includes: Receiving a software version update operation, wherein the software version update operation is triggering a software version update button; Displaying a software version release interface, wherein the software version release interface includes at least one software version basic information update window; Receiving a software basic information update operation, wherein the software basic information update operation is triggered after the user completes editing of the software version basic information in the software version basic information update window; Displays basic information about the updated software version.

5. The method according to claim 1, characterized in that Before receiving at least one module version selection operation, the method further includes: Receive a module and configuration version update operation, where the module and configuration version update operation is a triggering of a generation button for the module and configuration version; A module version update interface is displayed, wherein the module version update interface includes at least one module version update window.

6. The method according to claim 5, characterized in that The module version update interface also includes a switch button, and the method further includes: Receiving a switching operation, wherein the switching operation is a user triggering the switching button; A configuration version update interface is displayed, wherein the configuration version update interface includes at least one configuration version update window.

7. The method according to claim 6, characterized in that Also includes: Receive at least one configuration version selection operation, where the configuration version selection operation is triggered after the user completes editing the version number of the configuration version in the configuration version update window; Displays the version number of each configuration version.

8. The method according to any one of claims 1 to 7, characterized in that: Also includes: receiving a software package display operation, wherein the software package display operation is triggering a display button of the software package; Display at least one software package information, wherein the software package information includes a software package type and / or a version type; receiving a software package viewing operation, wherein the software package viewing operation is triggering a view button of the software package; Displays all information about the package in question.

9. An electronic device, characterized in that: The electronic device comprises: at least one processor, and a memory communicatively coupled to the at least one processor; In which, the memory stores a computer program that can be executed by the at least one processor, and the computer program is executed by the at least one processor so that the at least one processor can execute the software version management method of the intelligent driving system described in any one of claims 1-8.

10. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores computer instructions, and the computer instructions are used to enable a processor to implement the software version management method of the intelligent driving system according to any one of claims 1 to 8 when executed.

Images