Vehicle management method and device based on vehicle software baseline and storage medium

Abstract

The application provides a vehicle management method and device based on a vehicle software baseline and related equipment. A complete vehicle software super baseline is configured, hardware and corresponding software are connected based on the complete vehicle software super baseline to determine complete information of the complete vehicle software super baseline, configuration table information of the vehicle is collected, the single vehicle software baseline of the vehicle is determined according to the complete information of the complete vehicle software super baseline and the configuration table information, and software baseline management is performed on the corresponding vehicle according to the single vehicle software baseline of the vehicle. The vehicle management method based on the vehicle software baseline provided by the application can quickly and accurately determine the single vehicle software baseline of each vehicle type by configuring a super baseline that covers all software required by the vehicle type, and combining the configuration table information of different vehicle types, so as to effectively manage the software and hardware. The configuration and management complexity of the software baseline is reduced, and the method is simple, reliable and easy to implement. The error probability of the configuration process is small, the required time is short, and the efficiency is high.

Description

TECHNICAL FIELD

[0001] The present application relates to the technical field of automobiles, and in particular to a vehicle management method and device based on a vehicle software baseline and a storage medium. BACKGROUND

[0002] With the development of vehicle intelligence, a wave of software-defined vehicles has also emerged. The concept of vehicle management based on a vehicle software baseline has been born from the previous management of single-controller software and hardware versions. However, in the existing automobile topology system, due to the existence of different configuration differences in software and hardware for the same vehicle model, in order to meet the different requirements of software for each configuration difference in software and hardware of the vehicle during the OTA upgrade process, a corresponding software baseline needs to be defined for each functional configuration of the configuration difference in software and hardware of the vehicle. For the same vehicle model, there may be hundreds of functional configurations, which requires the definition of hundreds of software baselines. The process of configuring a single-vehicle software baseline for different vehicles to achieve vehicle management in the prior art is very complex and tedious, which affects the management effect of software baselines and the associated software and hardware of functional configurations. SUMMARY

[0003] Therefore, the embodiments of the present application provide a vehicle management method and device based on a vehicle software baseline and a storage medium to at least or partially solve the above problems.

[0004] In a first aspect, the embodiments of the present application provide a vehicle management method based on a vehicle software baseline, comprising:

[0005] configuring a super baseline of vehicle software;

[0006] based on the super baseline of vehicle software, concatenating hardware and corresponding software under the super baseline of vehicle software to determine complete information of the super baseline of vehicle software;

[0007] collecting configuration table information of a vehicle;

[0008] determining a single-vehicle software baseline of the vehicle according to the complete information of the super baseline of vehicle software and the configuration table information;

[0009] performing software baseline management on a corresponding vehicle according to the single-vehicle software baseline of the vehicle.

[0010] Optionally, in an embodiment of the present application, the complete information includes controllers carried by the vehicle, software versions configured for each controller, and vehicle models applicable to different software versions.

[0011] Optionally, in one embodiment of this application, the step of connecting the hardware and corresponding software under the vehicle software super baseline to determine the complete information of the vehicle software super baseline includes:

[0012] Based on a tree-like topology, the controllers configured under the vehicle super software baseline are associated;

[0013] Within the tree-like topology, the software version of the control software used by the controller is determined;

[0014] Based on the software version, determine the compatible vehicle models;

[0015] The complete information is determined based on the associated controllers, software versions, and compatible vehicle models in the tree-like topology.

[0016] Optionally, in one embodiment of this application, determining the vehicle's individual software baseline based on the complete information of the vehicle software super baseline and the configuration table information includes:

[0017] Use the baseline complete information and the configuration table information as input data;

[0018] The input data is processed using a single-vehicle software baseline algorithm configured in the server to determine the single-vehicle software baseline of the vehicle.

[0019] Optionally, in one embodiment of this application, the configuration table information includes at least one of the vehicle's drive information, gear information, and displacement information.

[0020] Optionally, in one embodiment of this application, the method further includes: naming the vehicle software super baseline of the corresponding vehicle based on the user's needs.

[0021] Secondly, based on the vehicle management method based on vehicle software baseline provided in the first aspect of this application, embodiments of this application also provide a vehicle management device based on vehicle software baseline, comprising:

[0022] The configuration module is used to configure a super baseline for the entire vehicle software;

[0023] The serialization module is used to connect the hardware and corresponding software under the vehicle software super baseline based on the vehicle software super baseline, so as to determine the complete information of the vehicle software super baseline.

[0024] The collection module is used to collect vehicle configuration information;

[0025] The determination module is used to determine the vehicle's individual software baseline based on the complete information of the vehicle software super baseline and the configuration table information;

[0026] The management module is used to manage the software baseline of the corresponding vehicle based on the vehicle's individual software baseline.

[0027] Optionally, in one embodiment of this application, the serial module is further configured to:

[0028] Based on a tree-like topology, the controllers configured under the vehicle super software baseline are associated;

[0029] Within the tree-like topology, the software version of the control software used by the controller is determined;

[0030] Based on the software version, determine the compatible vehicle models;

[0031] The complete information is determined based on the associated controllers, software versions, and compatible vehicle models in the tree-like topology.

[0032] The generation module is used to determine the enhanced display interface based on the information from the control terminal;

[0033] Thirdly, embodiments of this application also provide a storage medium storing computer-executable instructions, which, when executed, perform any of the vehicle management methods based on a vehicle software baseline as described in the first aspect of this application.

[0034] Fourthly, embodiments of this application also provide an electronic device, the electronic device comprising: a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor executes the computer program to implement any of the vehicle management methods based on a vehicle software baseline as described in the first aspect of this application.

[0035] This application provides a vehicle management method, apparatus, and related equipment based on vehicle software baselines. The method involves configuring a super baseline for the entire vehicle's software; connecting the hardware and corresponding software under the super baseline to determine its complete information; collecting vehicle configuration table information; determining the individual vehicle software baselines based on the complete super baseline information and the configuration table information; and managing the software baselines of the corresponding vehicles based on these individual vehicle software baselines. This vehicle management method, based on vehicle software baselines, first configures a super baseline encompassing the software required for all vehicle models, then combines this with configuration table information for different models to quickly and accurately determine the individual vehicle software baselines for each model, and finally manages the vehicle's hardware and software effectively based on these individual vehicle software baselines. This implementation avoids the pain point of traditional methods that require creating multiple vehicle software baselines for different models, reducing the complexity of vehicle software baseline management, and is simple and easy to implement. The configuration process has a low error probability, requires little time to configure baselines, and is highly efficient. Attached Figure Description

[0036] To more clearly illustrate the technical solutions in the embodiments of this application or the prior art, the drawings used in the description of the embodiments or the prior art will be briefly introduced below. Obviously, the drawings described below are only some embodiments recorded in the embodiments of this application. For those skilled in the art, other drawings can be obtained based on these drawings.

[0037] Figure 1 A schematic diagram illustrating the workflow of a vehicle management method based on a vehicle software baseline, provided for embodiments of this application;

[0038] Figure 2 A schematic diagram illustrating an example of a super baseline tree topology structure for vehicle software provided in this application embodiment;

[0039] Figure 3 An exemplary schematic diagram illustrating a single-vehicle software baseline for different vehicle models provided in an embodiment of this application;

[0040] Figure 4 This is a schematic diagram of the structure of a vehicle management device based on a vehicle software baseline, provided as an embodiment of this application. Detailed Implementation

[0041] To enable those skilled in the art to better understand the technical solutions in the embodiments of this application, the technical solutions in the embodiments of this application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of this application, and not all embodiments. Based on the embodiments of this application, all other embodiments obtained by those skilled in the art should fall within the protection scope of the embodiments of this application.

[0042] It should be understood that the steps described in the method embodiments of this application may be performed in different orders and / or in parallel. Furthermore, the method embodiments may include additional steps and / or omit the steps shown. The scope of this application is not limited in this respect.

[0043] Example 1

[0044] This application provides a vehicle management method based on a vehicle software baseline, such as... Figure 1 As shown, Figure 1 A schematic diagram of the workflow of a vehicle management method based on a vehicle software baseline provided in this application embodiment includes:

[0045] Step S101: Configure a vehicle software super baseline. Specifically, in this embodiment, the vehicle software super baseline is a baseline that encompasses and associates the software required by all configuration models. By using this main baseline to encompass and associate the software required by all configuration models, the process of creating multiple common software baselines for different models is avoided, thereby reducing the cumbersome configuration and management complexity of vehicle software baselines.

[0046] Step S102: Based on the vehicle software super baseline, connect the hardware and corresponding software under the vehicle software super baseline to determine the complete information of the vehicle software super baseline. This facilitates the effective management of more vehicle models through the vehicle management method based on the vehicle software baseline provided in this application embodiment.

[0047] Optionally, in one implementation of this application, the complete information of the vehicle software super baseline includes: the controller installed in the vehicle, the software version configured for each controller, and the vehicle models applicable to different software versions. This allows for more efficient management of different vehicle models through the vehicle management method based on the vehicle software baseline provided in this application, by leveraging the compatibility between hardware and different software versions, thereby simplifying the complexity of management.

[0048] Optionally, in one implementation of this application, the step of connecting the hardware and corresponding software under the vehicle software super baseline to determine the complete information of the vehicle software super baseline includes: based on a tree topology, associating the controllers configured under the vehicle software super baseline using the vehicle software super baseline; determining the software version of the control software used by the controller in the tree topology; determining the compatible vehicle model based on the software version; and determining the complete information based on the associated controller, the software version, and the compatible vehicle model in the tree topology. The tree topology allows for a visually intuitive and orderly organization of the software and hardware of different vehicle models.

[0049] Step S103: Collect vehicle configuration table information. In this embodiment, the vehicle configuration table information includes comprehensive vehicle parameter information, such as the vehicle's length, width, height, wheelbase, and front and rear wheel information. By collecting the vehicle configuration table information as the basis for configuring the single-vehicle baseline, it is possible to more quickly configure the single-vehicle software baseline corresponding to various vehicle models through the whole vehicle software super baseline, and ensure the comprehensiveness and accuracy of the configured single-vehicle software baseline.

[0050] Optionally, in one implementation of this application embodiment, the configuration table information includes at least one of the vehicle's drive information, gear information, and engine displacement information. By using one or more of the vehicle's drive information, gear information, and engine displacement information as the main information in the configuration table, it is possible to provide users with an orderly single-vehicle software baseline corresponding to different vehicle models and the vehicle management functions they can achieve in a more intuitive way that conforms to users' habits of understanding vehicle functional parameters.

[0051] Step S104: Determine the vehicle's individual software baseline based on the complete information of the vehicle software super baseline and the configuration table information.

[0052] Specifically, this application provides an example implementation for illustration, such as... Figure 2 As shown, Figure 2This is a schematic diagram illustrating an example of a tree-like topology structure for vehicle software superbaseline provided in this application embodiment. A configured vehicle software superbaseline 20 serves as the trunk of the tree-like topology. Different controllers are configured for different vehicle models, including controller A, controller B, and controller C. Each controller is configured with different control software versions for different vehicle models. For example, controller A is configured with software versions A1 and A2, where software version A1 is suitable for four-wheel drive vehicles 201, and software version A2 is suitable for two-wheel drive vehicles 202. Controller B is configured with software versions B1 and B2, where software version B1 is suitable for automatic transmission vehicles 211, and software version B2 is suitable for manual transmission vehicles 212. Controller C is configured with software versions C1 and C2, where software version C1 is suitable for 2.0T vehicles 221, and software version C2 is suitable for 1.5T vehicles 222. At this time, as... Figure 2 As shown, each different controller is used as the main leaf node on the trunk of the tree-structured topology, and the different software versions of the corresponding controllers are used as the next-level secondary leaf nodes of the main leaf nodes. Corresponding leaf nodes are connected to the corresponding different software versions, and these leaf nodes indicate the vehicle models used by the different software versions, thereby generating a super software baseline tree topology for the entire vehicle that can cover various vehicle models.

[0053] Furthermore, such as Figure 3 As shown, Figure 3 This is an exemplary schematic diagram illustrating a single-vehicle software baseline for different vehicle models provided in an embodiment of this application. This embodiment will continue to use the aforementioned example. Figure 2 The established vehicle super software baseline tree structure includes vehicle models 31 and 32. The configuration table for vehicle model 31 indicates that it is a four-wheel drive, automatic transmission, and 2.0T vehicle. Correspondingly, the single-vehicle software baseline for vehicle model 31 includes controllers A, B, and C. Controller A in vehicle model 31 is compatible with software version A1, controller B with software version B1, and controller C with software version C1. The configuration table for vehicle model 32 indicates that it is a two-wheel drive, manual transmission, and 1.5T vehicle. Correspondingly, the single-vehicle software baseline for vehicle model 32 is associated with controllers A, B, and C. Controller A in vehicle model 32 is compatible with software version A2, controller B with software version B2, and controller C with software version C2.

[0054] Optionally, in one implementation of this application embodiment, determining the vehicle's individual software baseline based on baseline complete information and configuration table information includes: using the baseline complete information and configuration table information as input data, and processing the input data using a vehicle software baseline algorithm configured in the server to determine the vehicle's individual software baseline. This method allows for faster and more accurate determination of individual software baselines for different vehicles or vehicle models. It also reduces the computationally intensive and repetitive work by implementing it through a computer, decreasing the probability of errors and saving time in calculating software baselines for different vehicles or vehicle models.

[0055] Step S105: Based on the vehicle's single-vehicle software baseline, perform software baseline management on the corresponding vehicle.

[0056] Optionally, in one embodiment of this application, the method further includes: naming the vehicle software super baseline of the corresponding vehicle based on user needs. This facilitates quick identification of the vehicle software super baseline by the user through naming, and also facilitates rapid configuration and storage of the determined single-vehicle super limits in the computer.

[0057] This application provides a vehicle management method based on vehicle software baselines. It configures a super baseline for the entire vehicle software, connects the hardware and corresponding software under this super baseline to determine its complete information, collects vehicle configuration table information, and determines the individual vehicle software baselines based on the complete super baseline information and configuration table information. Software baseline management is then performed on the corresponding vehicles based on these individual vehicle software baselines. This vehicle management method, based on vehicle software baselines, quickly and accurately determines the individual vehicle software baselines for each vehicle model by configuring a super baseline encompassing the software required by all vehicle configurations and combining it with configuration table information for different models. This enables effective management of both hardware and software. It reduces the complexity of software baseline configuration and management, is simple, reliable, and easy to implement. The configuration process has a low error probability, requires little time, and is highly efficient.

[0058] Example 2

[0059] Based on the vehicle management method based on vehicle software baseline described in Embodiment 1 of this application, this embodiment also provides a vehicle management device based on vehicle software baseline, such as... Figure 4 As shown, Figure 4 A schematic diagram of a vehicle management device 40 based on a vehicle software baseline provided in this application embodiment. The vehicle management device 40 based on a vehicle software baseline includes:

[0060] Configuration module 401 is used to configure a super baseline for vehicle software;

[0061] The serialization module 402 is used to connect the hardware and corresponding software under the vehicle software super baseline based on the vehicle software super baseline, so as to determine the complete information of the vehicle software super baseline.

[0062] Collection module 403 is used to collect vehicle configuration table information;

[0063] The determination module 404 is used to determine the vehicle software baseline based on the complete information of the vehicle software super baseline and the configuration table information;

[0064] The management module 405 is used to manage the software baseline of the corresponding vehicle based on the vehicle's single-vehicle software baseline.

[0065] Optionally, in one implementation of this application embodiment, the serial module 402 is further configured to: associate controllers configured under the vehicle super software baseline based on a tree topology; determine the software version of the control software used by the controller in the tree topology; determine the compatible vehicle model based on the software version; and determine the complete information based on the associated controller, the software version, and the compatible vehicle model in the tree topology.

[0066] Optionally, in one implementation of this application embodiment, the complete information includes: the controller installed in the vehicle, the software version configured for each controller, and the vehicle models to which different software versions are applicable.

[0067] Optionally, in one implementation of this application embodiment, the determining module 404 is further configured to use the baseline complete information and the configuration table information as input data; and to process the input data using a single-vehicle software baseline algorithm configured in the server to determine the single-vehicle software baseline of the vehicle.

[0068] Optionally, in one implementation of this application embodiment, the configuration table information includes at least one of the vehicle's drive information, gear information, and displacement information.

[0069] Optionally, in one implementation of this application embodiment, the vehicle management device 40 based on the vehicle software baseline further includes a naming module (not shown in the figures), which is used to name the super baseline of the vehicle software of the corresponding vehicle based on the user's needs.

[0070] This application provides a vehicle software baseline device and related equipment. A configuration module configures a vehicle software super baseline; a serialization module serializes the hardware and corresponding software under the vehicle software super baseline to determine its complete information; a mobile module collects vehicle configuration table information; a determination module determines the vehicle's individual software baseline based on the complete super baseline information and configuration table information; and a management module manages the software baselines of corresponding vehicles based on their individual software baselines. This vehicle management device based on vehicle software baselines, by configuring a super baseline encompassing the software required by all vehicle models and combining it with configuration table information for different models, quickly and accurately determines the individual software baselines for each model, enabling effective management of hardware and software. It reduces the complexity of software baseline configuration and management, is simple, reliable, and easy to implement. The configuration process has a low error probability, requires little time, and is highly efficient.

[0071] Example 3

[0072] This application also provides a storage medium storing a computer program thereon. When executed by a processor, the program implements any of the vehicle management methods based on a vehicle software baseline as described in Embodiment 1 of this application. These vehicle management methods based on a vehicle software baseline include, but are not limited to:

[0073] Configure a super baseline for the entire vehicle software;

[0074] Based on the vehicle software super baseline, the hardware and corresponding software under the vehicle software super baseline are connected in series to determine the complete information of the vehicle software super baseline;

[0075] Collect vehicle configuration information;

[0076] Based on the complete information of the vehicle software super baseline and the configuration table information, the vehicle software baseline is determined.

[0077] Based on the vehicle's individual software baseline, software baseline management is performed on the corresponding vehicle.

[0078] Example 4

[0079] This application also provides an electronic device, including: a memory, a processor, and a computer program stored in the memory and executable on the processor. When the processor executes the computer program, it implements any of the vehicle management methods based on a vehicle software baseline as described in Embodiment 1 of this application. The vehicle management method based on a vehicle software baseline includes, but is not limited to:

[0080] Configure a super baseline for the entire vehicle software;

[0081] Based on the vehicle software super baseline, the hardware and corresponding software under the vehicle software super baseline are connected in series to determine the complete information of the vehicle software super baseline;

[0082] Collect vehicle configuration information;

[0083] Based on the complete information of the vehicle software super baseline and the configuration table information, the vehicle software baseline is determined.

[0084] Based on the vehicle's individual software baseline, software baseline management is performed on the corresponding vehicle.

[0085] This application has now described specific embodiments of the subject matter. Other embodiments are within the scope of the appended claims. In some cases, the actions recited in the claims can be performed in a different order and still achieve the desired result. Furthermore, the processes depicted in the drawings do not necessarily require a specific or sequential order to achieve the desired result. In some embodiments, multitasking and parallel processing can be advantageous.

[0086] In the 1990s, improvements to a technology could be clearly distinguished as either hardware improvements (e.g., improvements to the circuit structure of diodes, transistors, switches, etc.) or software improvements (improvements to methodology). However, with technological advancements, many methodological improvements today can be considered direct improvements to hardware circuit structures. Designers almost always obtain the corresponding hardware circuit structure by programming the improved methodology into the hardware circuit. Therefore, it cannot be said that a methodological improvement cannot be implemented using hardware physical modules. For example, a Programmable Logic Device (PLD) (e.g., a Field Programmable Gate Array (FPGA)) is such an integrated circuit whose logic function is determined by the user programming the device. Designers can program and "integrate" a digital system layer onto a PLD themselves, without needing chip manufacturers to design and manufacture dedicated integrated circuit chips. Furthermore, nowadays, instead of manually manufacturing integrated circuit chips, this programming is mostly implemented using "logic compiler" software. Similar to the software compiler used in program development, the original code before compilation must be written in a specific programming language, called a Hardware Description Language (HDL). There are many HDLs, such as ABEL (Advanced Boolean Expression Language), AHDL (Altera Hardware Description Language), Confluence, CUPL (Cornell University Programming Language), HDCal, JHDL (Java Hardware Description Language), Lava, Lola, MyHDL, PALASM, and RHDL (Ruby Hardware Description Language). Currently, the most commonly used are VHDL (Very-High-Speed ​​Integrated Circuit Hardware Description Language) and Verilog. Those skilled in the art should understand that by simply performing some logic programming on the method flow using one of these hardware description languages ​​and programming it into an integrated circuit, the hardware circuit implementing the logical method flow can be easily obtained.

[0087] The controller can be implemented in any suitable manner. For example, it can take the form of a microprocessor or processor and a computer-readable medium storing computer-readable program code (e.g., software or firmware) executable by the (micro)processor, logic gates, switches, application-specific integrated circuits (ASICs), programmable logic controllers, and embedded microcontrollers. Examples of controllers include, but are not limited to, the following microcontrollers: ARC 625D, Atmel AT91SAM, Microchip PIC18F26K20, and Silicon Labs C8051F320. A memory controller can also be implemented as part of the control logic of the memory. Those skilled in the art will also recognize that, in addition to implementing the controller in purely computer-readable program code form, the same functionality can be achieved by logically programming the method steps to make the controller take the form of logic gates, switches, application-specific integrated circuits, programmable logic controllers, and embedded microcontrollers. Therefore, such a controller can be considered a hardware component, and the means included therein for implementing various functions can also be considered as structures within the hardware component. Alternatively, the means for implementing various functions can be considered as both software modules implementing the method and structures within the hardware component.

[0088] The system layers, devices, modules, or units described in the above embodiments can be implemented by computer chips or entities, or by products with certain functions. A typical implementation device is a computer. Specifically, a computer can be, for example, a personal computer, laptop computer, cellular phone, camera phone, smartphone, personal digital assistant, media player, navigation device, email device, game console, tablet computer, wearable device, or any combination of these devices.

[0089] For ease of description, the above devices are described separately by function as various units. Of course, in implementing this application, the functions of each unit can be implemented in one or more software and / or hardware.

[0090] Those skilled in the art will understand that embodiments of this application can be provided as methods, system-level, or computer program products. Therefore, this application can take the form of a completely hardware embodiment, a completely software embodiment, or an embodiment combining software and hardware aspects. Furthermore, this application can take the form of a computer program product embodied on one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) containing computer-usable program code.

[0091] It should also be noted that the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such process, method, article, or apparatus. Unless otherwise specified, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or apparatus that includes that element.

[0092] This application can be described in the general context of computer-executable instructions that are executed by a computer, such as program modules. Generally, program modules include routines, programs, objects, components, data structures, etc., that perform specific transactions or implement specific abstract data types. This application can also be practiced in distributed computing environments where transactions are performed by remote processing devices connected via a communication network. In distributed computing environments, program modules can reside in local and remote computer storage media, including storage devices.

[0093] The various embodiments in this specification are described in a progressive manner. Similar or identical parts between embodiments can be referred to interchangeably. Each embodiment focuses on describing the differences from other embodiments. In particular, the system-level embodiments are basically similar to the method embodiments, so the description is relatively simple; relevant parts can be referred to the descriptions in the method embodiments.

[0094] The above are merely embodiments of this application and are not intended to limit the scope of this application. Various modifications and variations can be made to this application by those skilled in the art. Any modifications, equivalent substitutions, improvements, etc., made within the spirit and principles of this application should be included within the scope of the claims of this application.

Claims

1. A vehicle management method based on a vehicle software baseline, characterized in that, include: Configure a super baseline for the entire vehicle software; A configured vehicle software super baseline is used as the trunk of a tree-like topology, and the controllers configured under the vehicle software super baseline are associated with it. Each of the controllers configured under the vehicle software super baseline is used as the main leaf node on the trunk of the tree-like topology. Determine the software version of the control software used by the controller, and use the different software versions corresponding to each controller as the next level sub-leaf nodes of the primary leaf node; Based on the software version, the compatible vehicle models are determined, and leaf nodes of the same level are connected for the corresponding different software versions. The leaf nodes of the same level contain the driving information, gear information and displacement information of the vehicle models adapted to different software versions, so as to generate a super baseline tree topology structure for the whole vehicle software. Based on the associated controllers, software versions, and compatible vehicle models in the tree-like topology of the vehicle software super baseline, the complete information of the vehicle software super baseline is determined. Collect vehicle configuration information, which includes the vehicle's drive information, gear information, and engine displacement information; Based on the complete information of the vehicle software super baseline and the configuration table information, the vehicle software baseline is determined. The vehicle software baseline includes a controller adapted to the vehicle's drive information and its corresponding software version, a controller adapted to the vehicle's gear information and its corresponding software version, and a controller adapted to the vehicle's displacement information and its corresponding software version. Based on the vehicle's individual software baseline, software baseline management is performed on the corresponding vehicle.

2. The vehicle management method based on vehicle software baseline according to claim 1, characterized in that, The complete information includes: the controller installed in the vehicle, the software version configured for each controller, and the vehicle models to which different software versions are applicable.

3. The vehicle management method based on vehicle software baseline according to claim 1, characterized in that, The step of determining the vehicle's individual software baseline based on the complete information of the vehicle software super baseline and the configuration table information includes: Use the complete information and the configuration table information as input data; The input data is processed using a single-vehicle software baseline algorithm configured in the server to determine the single-vehicle software baseline of the vehicle.

4. The vehicle management method based on vehicle software baseline according to claim 1, characterized in that, The method further includes: naming the corresponding vehicle software super baseline based on user needs.

5. A vehicle management device based on a vehicle software baseline, characterized in that, include: The configuration module is used to configure a super baseline for the entire vehicle software; The serial module is used to use a configured vehicle software super baseline as the trunk of a tree-like topology, associate controllers configured under the vehicle software super baseline, and use each controller configured under the vehicle software super baseline as a primary leaf node on the trunk of the tree-like topology. It determines the software version of the control software used by each controller, and uses different software versions corresponding to each controller as the next-level secondary leaf nodes of the primary leaf nodes. Based on the software version, it determines the compatible vehicle model and connects the corresponding leaf nodes of different software versions to the same level. The same-level leaf nodes contain the drive information, gear information, and displacement information of the vehicle models adapted to different software versions, thereby generating a tree-like topology for the vehicle software super baseline. Based on the associated controllers, the software versions, and the adapted vehicle models in the tree-like topology of the vehicle software super baseline, it determines the complete information of the vehicle software super baseline. The collection module is used to collect vehicle configuration information, which includes the vehicle's drive information, gear information, and engine displacement information. The determination module is used to determine the vehicle software baseline based on the complete information of the vehicle software super baseline and the configuration table information. The vehicle software baseline includes a controller adapted to the vehicle's drive information and its corresponding software version, a controller adapted to the vehicle's gear information and its corresponding software version, and a controller adapted to the vehicle's displacement information and its corresponding software version. The management module is used to manage the software baseline of the corresponding vehicle based on the vehicle's individual software baseline.

6. A computer storage medium, characterized in that, The computer storage medium stores computer-executable instructions, which, when executed, perform the vehicle management method based on a vehicle software baseline as described in any one of claims 1-4.

7. An electronic device, characterized in that, include: The memory, the processor, and the computer program stored in the memory and executable on the processor, wherein the processor, when executing the computer program, implements the vehicle management method based on any one of claims 1-4.

Images