Vehicle baseline version determination method and device, equipment, medium and program product
By comparing the vehicle's component software version set with the preset baseline version set, the target baseline version of the vehicle is determined, which solves the problem of not being able to obtain the baseline version correctly, and achieves the guarantee of rapid and accurate calibration of the vehicle and subsequent development and upgrading.
Patent Information
- Application Number
- CN202510170713.0
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2025-02-17
- Publication Date
- 2025-06-10
AI Technical Summary
The baseline version of the vehicle cannot be correctly obtained in the prior art, making it difficult to ensure the subsequent development and upgrading of the vehicle.
By obtaining the component software version set of the target vehicle and comparing it with the preset baseline version set until the comparison end condition is met, the target baseline version of the target vehicle is determined.
The baseline version of the vehicle is quickly and accurately determined, ensuring that the vehicle can undergo subsequent development and upgrades smoothly.
Smart Images
Figure CN120122978A_ABST
Abstract
Description
Technical Field
[0001] This application relates to the technical field of intelligent vehicles, and in particular, to a method, device, equipment, medium, and program product for determining the baseline version of a vehicle. Background Art
[0002] At the software development level, the baseline version of a vehicle is the starting point for the overall vehicle software development. It contains all the requirements, settings, and specifications required for the subsequent software version development. The baseline version determines the core technologies and basic configurations of the vehicle, including key elements such as the engine, transmission system, suspension system, and safety configuration. The selection of these technologies and configurations has a direct impact on the driving experience and safety of the vehicle.
[0003] If the baseline version of the vehicle cannot be obtained, or the obtained baseline version is incorrect, it is difficult to provide guidance and guarantee for the subsequent development and upgrade of the vehicle. Therefore, there is an urgent need to provide a method for determining the baseline version of a vehicle. Summary of the Invention
[0004] This application provides a method, device, equipment, medium, and program product for determining the baseline version of a vehicle, which is used to solve the defect in the prior art that it is difficult to ensure the subsequent development and upgrade of the vehicle when the baseline version of the vehicle cannot be correctly obtained, and realizes fast and accurate baseline version calibration to ensure the smooth progress of the subsequent development and upgrade of the vehicle.
[0005] In a first aspect, this application provides a method for determining the baseline version of a vehicle, including:
[0006] Obtain a set of component software versions of the target vehicle; the set of component software versions includes a first component and the software version corresponding to the first component;
[0007] Based on the preset baseline version set of the target vehicle and the set of component software versions, perform at least one comparison operation until the comparison end condition is met, and use the first baseline version that meets the comparison end condition as the target baseline version of the target vehicle; the baseline version set includes multiple baseline versions, and for each baseline version, a second component and the software version corresponding to the second component.
[0008] In one embodiment, the comparison operation includes:
[0009] Determine the first baseline version corresponding to the current comparison operation from the baseline version set; among them, the first baseline version corresponding to the first comparison operation is the highest baseline version in the baseline version set;
[0010] If there are identical components between the first component in the component software version set and the second component corresponding to the first baseline version, and the software version of the identical component in the component software version set is lower than the software version of the identical component corresponding to the first baseline version, determine a second baseline version based on the first baseline version, and use the second baseline version as the first baseline version for the next comparison operation.
[0011] In one embodiment, the determining the second baseline version based on the first baseline version includes:
[0012] Screen out a target baseline version set with versions lower than the first baseline version from the baseline version set;
[0013] Use the highest baseline version in the target baseline version set as the second baseline version.
[0014] In one embodiment, the comparison end condition is that there are identical components between the first component and the second component, and the software versions of all identical components in the component software version set are not lower than the software versions of the identical components corresponding to the first baseline version.
[0015] In one embodiment, the vehicle baseline version determination method further includes:
[0016] If there are no identical components between the first component and the second component, re-obtain the component software version set.
[0017] In one embodiment, the vehicle baseline version determination method further includes:
[0018] If it is determined that the target vehicle is a vehicle to be upgraded based on the target baseline version, upgrade the target vehicle based on the baseline version to be upgraded.
[0019] In a second aspect, the present application further provides a vehicle baseline version determination device, including:
[0020] An acquisition module, configured to acquire a component software version set of a target vehicle; the component software version set includes a first component and the software version corresponding to the first component;
[0021] A determination module, configured to perform at least one comparison operation based on the baseline version set preset for the target vehicle and the component software version set until the comparison end condition is met, and use the first baseline version that meets the comparison end condition as the target baseline version of the target vehicle; the baseline version set includes multiple baseline versions, and a second component corresponding to each baseline version and the software version corresponding to the second component.
[0022] In one embodiment, the comparison operation includes:
[0023] Determine a first baseline version corresponding to the current comparison operation from the set of baseline versions; wherein, the first baseline version corresponding to the first comparison operation is the highest baseline version in the set of baseline versions;
[0024] If there are identical components between the first component in the component software version set and the second component corresponding to the first baseline version, and the software version of the identical component in the component software version set is lower than the software version of the identical component corresponding to the first baseline version, determine a second baseline version based on the first baseline version, and use the second baseline version as the first baseline version corresponding to the next comparison operation.
[0025] In one embodiment, the determining module is specifically configured to:
[0026] Screen out a set of target baseline versions with versions lower than the first baseline version from the set of baseline versions;
[0027] Use the highest baseline version in the set of target baseline versions as the second baseline version.
[0028] In one embodiment, the comparison end condition is that there are the identical components between the first component and the second component, and the software versions of all the identical components in the component software version set are not lower than the software versions of the identical components corresponding to the first baseline version.
[0029] In one embodiment, the obtaining module is further configured to:
[0030] If there are no such identical components between the first component and the second component, re-obtain the component software version set.
[0031] In one embodiment, the determining module is further configured to:
[0032] If it is determined that the target vehicle is a vehicle to be upgraded based on the target baseline version, upgrade the target vehicle based on the baseline version to be upgraded.
[0033] In a third aspect, the present application further provides an electronic device, including a memory, a processor, and a computer program stored on the memory and executable on the processor, where when the processor executes the computer program, the method described in the first aspect is implemented.
[0034] In a fourth aspect, the present application further provides a non-transitory computer-readable storage medium, on which a computer program is stored, and when the computer program is executed by a processor, the method described in the first aspect is implemented.
[0035] In a fifth aspect, the present application further provides a computer program product, including a computer program which, when executed by a processor, implements the method described in the first aspect.
[0036] The vehicle baseline version determination method, device, equipment, medium and program product provided by the present application can, by comparing a preset baseline version set of a target vehicle with a component software version set, match the most suitable baseline version corresponding to the component software version set as the target baseline version of the target vehicle, and can quickly, conveniently and accurately determine the target baseline version of the target vehicle, thereby ensuring the smooth progress of subsequent development and upgrade of the target vehicle. BRIEF DESCRIPTION OF THE DRAWINGS
[0037] To more clearly illustrate the technical solutions in the present application or the prior art, the following briefly introduces the drawings required for use in the description of the embodiments or the prior art. Obviously, the drawings in the following description are some embodiments of the present application, and those of ordinary skill in the art can also obtain other drawings based on these drawings without creative efforts.
[0038] Figure 1 It is a flowchart of the vehicle baseline version determination method provided by an embodiment of the present application;
[0039] Figure 2 It is a schematic structural diagram of the vehicle baseline version determination device provided by an embodiment of the present application;
[0040] Figure 3 It is a schematic structural diagram of an electronic device provided by an embodiment of the present application. DETAILED DESCRIPTION OF THE EMBODIMENTS
[0041] To make the objectives, technical solutions and advantages of the present application clearer, the following clearly and completely describes the technical solutions in the present application with reference to the drawings in the present application. Obviously, the described embodiments are some, but not all, of the embodiments of the present application. All other embodiments obtained by those of ordinary skill in the art without creative efforts based on the embodiments in the present application belong to the scope of protection of the present application.
[0042] Figure 1 It is a flowchart of the vehicle baseline version determination method provided by an embodiment of the present application. Referring to Figure 1 , an embodiment of the present application provides a vehicle baseline version determination method, and its execution subject can be the cloud. The following takes the execution subject of this method being the cloud as an example for description. This method may include:
[0043] Step 110: Obtain the component software version set of the target vehicle; the component software version set includes the first component and the software version corresponding to the first component.
[0044] Step 120: Based on the preset baseline version set and the component software version set of the target vehicle, perform at least one comparison operation until the comparison end condition is met, and use the first baseline version that meets the comparison end condition as the target baseline version of the target vehicle; the baseline version set includes multiple baseline versions, as well as the second component corresponding to each baseline version and the software version corresponding to the second component.
[0045] In Step 110, when there is no baseline version when the target vehicle rolls off the production line or the obtained baseline version is incorrect, the cloud can obtain the component software version set of the target vehicle. Specifically, the component software version set includes the first component and the software version corresponding to the first component.
[0046] In Step 120, the cloud can perform at least one comparison operation based on the preset baseline version set and the component software version set of the target vehicle. Specifically, it compares the same components and the software versions of the same components in the two sets until the comparison end condition is met. The cloud can use the first baseline version that meets the comparison end condition as the target baseline version of the target vehicle. Specifically, the baseline version set can include multiple baseline versions, as well as the second component corresponding to each baseline version and the software version corresponding to the second component. After determining the target baseline version of the vehicle, the cloud can return the target baseline version to the target vehicle, and the target vehicle writes the target baseline version into the in-vehicle computer.
[0047] The vehicle baseline version determination method provided by the embodiments of the present application can match the most suitable baseline version corresponding to the component software version set by comparing the preset baseline version set of the target vehicle with the component software version set, and use it as the target baseline version of the target vehicle, so as to quickly, conveniently and accurately determine the target baseline version of the target vehicle, thereby ensuring the smooth progress of subsequent development and upgrade of the target vehicle.
[0048] In one embodiment, the comparison operation includes: determining the first baseline version corresponding to the current comparison operation from the baseline version set; among them, the first baseline version corresponding to the first comparison operation is the highest baseline version in the baseline version set; if there are the same components between the first component in the component software version set and the second component corresponding to the first baseline version, and the software version of the same component in the component software version set is lower than the software version of the same component corresponding to the first baseline version, determine the second baseline version based on the first baseline version, and use the second baseline version as the first baseline version corresponding to the next comparison operation.
[0049] Further, in one embodiment, the comparison end condition is that there are identical components between the first component and the second component, and the software versions of all the identical components in the component software version set are not lower than the software versions of the corresponding identical components of the first baseline version.
[0050] The cloud can determine the first baseline version corresponding to the current comparison operation from the baseline version set. Specifically, the first baseline version corresponding to the first comparison operation is the highest baseline version in the baseline version set. The cloud can compare the first component in the component software version set with the second component corresponding to the first baseline version, and when there are identical components between the first component and the second component, compare the software versions of the identical components in the component software version set with the software versions of the corresponding identical components of the first baseline version. If the software versions of all the identical components in the component software version set are not lower than the software versions of the corresponding identical components of the first baseline version, the first baseline version corresponding to the current comparison operation is used as the target baseline version. If there are software versions of identical components in the component software version set that are lower than the software versions of the corresponding identical components of the first baseline version, the second baseline version is determined based on the first baseline version, and the second baseline version is used as the first baseline version for the next comparison operation. Then, the comparison operation is repeated until there are the identical components between the first component and the second component in a certain comparison operation, and the software versions of all the identical components in the component software version set are not lower than the software versions of the corresponding identical components of the first baseline version, and the first baseline version corresponding to this comparison operation is used as the target baseline version.
[0051] The vehicle baseline version determination method provided by the embodiments of the present application can determine the target baseline version of the target vehicle quickly, conveniently and accurately by comparing the same components and the versions of the same components in the preset baseline version set of the target vehicle with the component software version set, so as to ensure the smooth progress of the subsequent development and upgrade of the target vehicle.
[0052] In one embodiment, determining the second baseline version based on the first baseline version includes: screening out a target baseline version set with versions lower than the first baseline version from the baseline version set; using the highest baseline version in the target baseline version set as the second baseline version.
[0053] The cloud can screen out all the baseline versions with versions lower than the first baseline version from the baseline version set as the target baseline version set. Then, the highest baseline version is screened out from the target baseline version set as the second baseline version.
[0054] The vehicle baseline version determination method provided by the embodiments of the present application screens out a target baseline version set with versions lower than the first baseline version from the baseline version set, and then uses the highest baseline version in the target baseline version set as the second baseline version, so as to be able to determine the comparison order of each baseline version in the baseline version set with the component software version set, which is beneficial to improving the comparison efficiency and quickly, conveniently and accurately determining the target baseline version of the target vehicle, thereby ensuring the smooth progress of subsequent development and upgrade of the target vehicle.
[0055] In one embodiment, the vehicle baseline version determination method further includes: if there are no identical components between the first component and the second component, re-obtain the component software version set.
[0056] Normally, there are identical components between the first component in the component software version set and the second component corresponding to the first baseline version determined based on the baseline version set. If there are no identical components between the first component in the component software version set and the second component corresponding to the first baseline version determined based on the baseline version set, it may be that the component software version set is obtained incorrectly, and the component software version set can be re-obtained.
[0057] The vehicle baseline version determination method provided by the embodiments of the present application can quickly, conveniently and accurately determine the target baseline version of the target vehicle by re-obtaining the component software version set when there are no identical components between the first component in the component software version set and the second component corresponding to the first baseline version determined based on the baseline version set, thereby ensuring the smooth progress of subsequent development and upgrade of the target vehicle.
[0058] In one embodiment, the vehicle baseline version determination method further includes: if the target vehicle is determined to be a vehicle to be upgraded based on the target baseline version, upgrade the target vehicle based on the baseline version to be upgraded.
[0059] In-vehicle software is an indispensable part of new energy vehicles, and the Over-the-Air (OTA) technology upgrade is the most important means for in-vehicle software update. OTA upgrade means that the operator deploys an upgrade task in the cloud, sends the task to the vehicle, and the vehicle automatically upgrades after receiving the task instruction. In this process, it is a very critical step for the operator to determine which vehicles to upgrade. Vehicle manufacturers all have a Manufacturing Execution System (MES) similar to that of manufacturing enterprises, which mainly records the software version information of vehicle components. Currently, vehicle OTA upgrades generally determine the scope of vehicles to be upgraded by retrieving the software versions of components. Since there are too many components on the vehicle, it will cause the determination process to be cumbersome and error-prone each time.
[0060] Through comparison operations, the cloud end of this application can determine the target baseline version of the target vehicle. Then, based on the target baseline version, it is determined whether the target vehicle is a vehicle to be upgraded. If the target vehicle is a vehicle to be upgraded, an OTA task is deployed based on the baseline version to be upgraded. After receiving the OTA task, the target vehicle is upgraded, and the target baseline version is updated to the in-vehicle computer.
[0061] For the vehicle baseline version determination method provided in the embodiments of this application, when it is determined that the target vehicle is a vehicle to be upgraded based on the target baseline version, the target vehicle is upgraded based on the baseline version to be upgraded. The target baseline version can be determined based on the component software version set of the target vehicle, and then the target vehicle can be upgraded based on the target baseline version. It can accurately determine whether the target vehicle is a vehicle to be upgraded and quickly upgrade the target vehicle.
[0062] Based on the descriptions of the above embodiments, this application provides a specific example of the application of a vehicle baseline version determination method.
[0063] When Vehicle A is offline, it has no baseline. After the vehicle reads the component software version set, it reports it to the cloud end. The cloud end can obtain the baseline version set of Vehicle A, and this baseline version set can include three baseline versions: Baseline 1.0.0, Baseline 1.0.1, and Baseline 1.0.2. Each baseline version corresponds to a component and the software version of the component. The cloud end uses the highest baseline version 1.0.2 as the first baseline version corresponding to the first comparison operation. Select a component from the component software version set. If it does not exist in the first baseline version, continue to select the next component from the component software version set. If the component exists in the first baseline version, compare the software version of the component in the first baseline version with the software version of the component in the component software version set. If the version of the component in the first baseline version is higher than the software version of the component in the component software version set, it indicates that the component software version set cannot match the first baseline version. Screen out the target baseline version set with versions lower than the first baseline version from the baseline version set: Baseline 1.0.0 and Baseline 1.0.1. Use the highest baseline version in the target baseline version set: Baseline 1.0.1, as the second baseline version, and use the second baseline version as the first baseline version corresponding to the next comparison operation, and continue the comparison operation. If there are the same components in the component software version set and the software versions of all the same components in the component software version set are not lower than the software versions of the corresponding same components in the first baseline version, use Baseline 1.0.1 as the target baseline version.
[0064] The vehicle baseline version determination method provided by this application defines the corresponding relationship between the baseline version and the component software version set. Each vehicle has its own baseline, and the baseline calibration algorithm is simpler. Through the initial baseline calibration when the vehicle rolls off the production line, and then after the cloud selects vehicles for upgrade based on the baseline, the vehicle baseline is updated to form the synchronization and unification of the cloud and vehicle-end baselines.
[0065] The vehicle baseline version determination device provided by this application will be described below. The vehicle baseline version determination device described below can be correspondingly referred to the vehicle baseline version determination method described above.
[0066] Figure 2 It is a schematic structural diagram of the vehicle baseline version determination device provided by an embodiment of this application. Refer to Figure 2 , the vehicle baseline version determination device provided by an embodiment of this application may include:
[0067] An acquisition module 210, configured to acquire the component software version set of the target vehicle; the component software version set includes a first component and the software version corresponding to the first component;
[0068] A determination module 220, configured to perform at least one comparison operation based on the preset baseline version set of the target vehicle and the component software version set until a comparison end condition is met, and use the first baseline version that meets the comparison end condition as the target baseline version of the target vehicle; the baseline version set includes multiple baseline versions, and a second component corresponding to each baseline version and the software version corresponding to the second component.
[0069] The vehicle baseline version determination device provided by an embodiment of this application can match the most suitable baseline version corresponding to the component software version set by comparing the preset baseline version set of the target vehicle with the component software version set, and use it as the target baseline version of the target vehicle, so as to quickly, conveniently and accurately determine the target baseline version of the target vehicle, thereby ensuring the smooth subsequent development and upgrade of the target vehicle.
[0070] In one embodiment, the comparison operation includes:
[0071] Determine the first baseline version corresponding to the current comparison operation from the baseline version set; among them, the first baseline version corresponding to the first comparison operation is the highest baseline version in the baseline version set;
[0072] If there are identical components between the first component in the component software version set and the second component corresponding to the first baseline version, and the software version of the identical component in the component software version set is lower than the software version of the identical component corresponding to the first baseline version, determine a second baseline version based on the first baseline version, and use the second baseline version as the first baseline version for the next comparison operation.
[0073] In one embodiment, the determining module is specifically configured to:
[0074] Screen out a target baseline version set with versions lower than the first baseline version from the baseline version set;
[0075] Use the highest baseline version in the target baseline version set as the second baseline version.
[0076] In one embodiment, the comparison end condition is that there are the identical components between the first component and the second component, and the software versions of all the identical components in the component software version set are not lower than the software versions of the identical components corresponding to the first baseline version.
[0077] In one embodiment, the obtaining module is further configured to:
[0078] If there are no such identical components between the first component and the second component, re-obtain the component software version set.
[0079] In one embodiment, the determining module is further configured to:
[0080] If it is determined that the target vehicle is a vehicle to be upgraded based on the target baseline version, upgrade the target vehicle based on the baseline version to be upgraded.
[0081] Specifically, the vehicle baseline version determining device provided in the embodiments of the present application can implement all the method steps implemented by the method embodiments with the execution subject being the cloud, and can achieve the same technical effects. The same parts and beneficial effects as those in the method embodiments will not be specifically described in this embodiment.
[0082] Figure 3 It is a schematic structural diagram of an electronic device provided in the embodiments of the present application. As Figure 3As shown in the figure, the electronic device may include: a processor 310, a communication interface 320, a memory 330, and a communication bus 340. Among them, the processor 310, the communication interface 320, and the memory 330 communicate with each other through the communication bus 340. The processor 310 can call the logical instructions in the memory 330 to execute the vehicle baseline version determination method, for example, including:
[0083] Obtain the component software version set of the target vehicle; the component software version set includes a first component and the software version corresponding to the first component;
[0084] Based on the preset baseline version set of the target vehicle and the component software version set, perform at least one comparison operation until the comparison end condition is met, and use the first baseline version that meets the comparison end condition as the target baseline version of the target vehicle; the baseline version set includes multiple baseline versions, and the second component corresponding to each baseline version and the software version corresponding to the second component.
[0085] In addition, when the logical instructions in the above-mentioned memory 330 are implemented in the form of software functional units and sold or used as independent products, they can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present application, in essence, or the part that contributes to the prior art, or a part of this technical solution, can be embodied in the form of a software product. The computer software product is stored in a storage medium and includes several instructions for causing a computer device (which may be a personal computer, a server, or a network device, etc.) to execute all or part of the steps of the methods described in various embodiments of the present application. The foregoing storage medium includes: various media such as USB flash drives, mobile hard disks, read-only memory (ROM), random access memory (RAM), magnetic disks, or optical discs that can store program codes.
[0086] On the other hand, the present application also provides a non-transitory computer-readable storage medium, on which a computer program is stored. When the computer program is executed by a processor, it is implemented to execute the steps of the vehicle baseline version determination method provided by the above-mentioned methods, for example, including:
[0087] Obtain the component software version set of the target vehicle; the component software version set includes a first component and the software version corresponding to the first component;
[0088] Perform at least one comparison operation based on the preset baseline version set of the target vehicle and the component software version set until the comparison end condition is met, and use the first baseline version that meets the comparison end condition as the target baseline version of the target vehicle; the baseline version set includes multiple baseline versions, as well as the second components corresponding to each baseline version and the software versions corresponding to the second components.
[0089] In another aspect, the present application also provides a computer program product. The computer program product includes a computer program that can be stored on a non-transitory computer-readable storage medium. When the computer program is executed by a processor, the computer can execute the steps of the vehicle baseline version determination method provided by the above-mentioned various methods, for example, including:
[0090] Obtain the component software version set of the target vehicle; the component software version set includes the first components and the software versions corresponding to the first components;
[0091] Perform at least one comparison operation based on the preset baseline version set of the target vehicle and the component software version set until the comparison end condition is met, and use the first baseline version that meets the comparison end condition as the target baseline version of the target vehicle; the baseline version set includes multiple baseline versions, as well as the second components corresponding to each baseline version and the software versions corresponding to the second components.
[0092] The device embodiments described above are merely illustrative. The units described as separate components may or may not be physically separated, and the components shown as units may or may not be physical units, that is, they may be located in one place or distributed to multiple network units. Some or all of the modules can be selected according to actual needs to achieve the purpose of the solution of this embodiment. Those of ordinary skill in the art can understand and implement it without creative labor.
[0093] Through the description of the above embodiments, those skilled in the art can clearly understand that each embodiment can be implemented by means of software plus a necessary general hardware platform, and of course, it can also be implemented by hardware. Based on such an understanding, the above technical solution, in essence, or the part that contributes to the prior art, can be embodied in the form of a software product. The computer software product can be stored in a computer-readable storage medium, such as ROM / RAM, magnetic disk, optical disk, etc., and includes several instructions for causing a computer device (which can be a personal computer, a server, or a network device, etc.) to execute the methods described in each embodiment or some parts of the embodiments.
[0094] In addition, it should be noted that in the embodiments of the present application, the terms "first", "second", etc. are used to distinguish similar objects, rather than to describe a specific order or sequence. It should be understood that such terms can be interchanged under appropriate circumstances, so that the embodiments of the present application can be implemented in an order other than those illustrated or described herein, and the objects distinguished by "first" and "second" are generally of the same category, and the number of objects is not limited. For example, the first object can be one or more.
[0095] In the embodiments of the present application, the term "and / or" describes the association relationship of associated objects, indicating that three relationships can exist. For example, A and / or B can represent three situations: A exists alone, A and B exist simultaneously, and B exists alone. The character " / " generally represents an "or" relationship between the associated objects before and after.
[0096] "Determining B based on A" in the embodiments of the present application means that the factor A should be considered when determining B. It is not limited to "determining B only based on A", but should also include: "determining B based on A and C", "determining B based on A, C, and E", "determining C based on A, and further determining B based on C", etc. In addition, it can also include using A as a condition for determining B. For example, "when A meets the first condition, use the first method to determine B"; for another example, "when A meets the second condition, determine B"; for another example, "when A meets the third condition, determine B based on the first parameter", etc. Of course, it can also be a condition for using A as a factor for determining B. For example, "when A meets the first condition, use the first method to determine C, and further determine B based on C", etc.
[0097] In the embodiments of the present application, the term "a plurality of" means two or more, and other quantifiers are similar.
[0098] In the embodiments of the present application, the orientation or positional relationship indicated by the terms "center", "longitudinal", "lateral", "upper", "lower", "front", "rear", "left", "right", "vertical", "horizontal", "top", "bottom", "inner", "outer", etc. is based on the orientation or positional relationship shown in the drawings. It is only for the convenience of describing the embodiments of the present application and simplifying the description, rather than indicating or implying that the device or element referred to must have a specific orientation, be constructed and operated in a specific orientation, and therefore cannot be understood as a limitation to the embodiments of the present application.
[0099] In the embodiments of the present application, unless otherwise clearly specified and limited, the terms "connected" and "coupled" should be understood in a broad sense. For example, it can be a fixed connection, a detachable connection, or an integral connection; it can be a mechanical connection or an electrical connection; it can be directly connected or indirectly connected through an intermediate medium. For those of ordinary skill in the art, the specific meanings of the above terms in the embodiments of the present application can be understood according to specific circumstances.
[0100] In the embodiments of the present application, unless otherwise clearly specified or limited, the first feature being "on" or "under" the second feature may be that the first and second features are in direct contact, or the first and second features are indirectly in contact through an intermediate medium. Moreover, the first feature being "above", "over" and "on top of" the second feature may be that the first feature is directly above or obliquely above the second feature, or merely indicates that the horizontal height of the first feature is higher than that of the second feature. The first feature being "under", "below" and "beneath" the second feature may be that the first feature is directly below or obliquely below the second feature, or merely indicates that the horizontal height of the first feature is less than that of the second feature.
[0101] In the embodiments of the present application, the description with reference to terms such as "an embodiment", "some embodiments", "example", "specific example", or "some examples", etc. means that the specific features, structures, materials, or characteristics described in connection with the embodiment or example are included in at least one embodiment or example of the embodiments of the present application. In the embodiments of the present application, the schematic representation of the above terms does not necessarily refer to the same embodiment or example. Moreover, the specific features, structures, materials, or characteristics described may be combined in a suitable manner in any one or more embodiments or examples. In addition, without contradiction, those skilled in the art may combine and combine the different embodiments or examples described in this specification and the features of different embodiments or examples.
[0102] Finally, it should be noted that the above embodiments are only used to illustrate the technical solutions of the present application, rather than to limit them; although the present application has been described in detail with reference to the foregoing embodiments, those of ordinary skill in the art should understand that they can still modify the technical solutions recorded in the foregoing embodiments, or perform equivalent replacements on some of the technical features; and these modifications or replacements do not make the essence of the corresponding technical solutions deviate from the spirit and scope of the technical solutions of the embodiments of the present application.
Claims
1. A method for determining a vehicle baseline version, characterized in that: include: Obtaining a component software version set of a target vehicle; the component software version set includes a first component and a software version corresponding to the first component; Based on the preset baseline version set of the target vehicle and the component software version set, at least one comparison operation is performed until a comparison end condition is met, and the first baseline version that meets the comparison end condition is used as the target baseline version of the target vehicle; the baseline version set includes multiple baseline versions, and a second component corresponding to each baseline version and a software version corresponding to the second component.
2. The vehicle baseline version determination method according to claim 1, characterized in that: The comparison operation includes: Determine a first baseline version corresponding to the current comparison operation from the baseline version set; wherein the first baseline version corresponding to the first comparison operation is the highest baseline version in the baseline version set; If the first component in the component software version set is the same as the second component corresponding to the first baseline version, and the software version of the same component in the component software version set is lower than the software version of the same component corresponding to the first baseline version, a second baseline version is determined based on the first baseline version, and the second baseline version is used as the first baseline version corresponding to the next comparison operation.
3. The vehicle baseline version determination method according to claim 2, characterized in that: The determining a second baseline version based on the first baseline version includes: Filtering out a target baseline version set whose version is lower than the first baseline version from the baseline version set; The highest baseline version in the target baseline version set is used as the second baseline version.
4. The vehicle baseline version determination method according to claim 2, characterized in that: The comparison end condition is that the first component and the second component have the same component, and the software versions of all the same components in the component software version set are not lower than the software version of the same component corresponding to the first baseline version.
5. The vehicle baseline version determination method according to claim 4, characterized in that: Also includes: If the first component and the second component do not have the same component, the component software version set is acquired again.
6. The vehicle baseline version determination method according to any one of claims 1 to 5, characterized in that: Also includes: If the target vehicle is determined to be a vehicle to be upgraded based on the target baseline version, the target vehicle is upgraded based on the baseline version to be upgraded.
7. A vehicle baseline version determination device, characterized in that: include: An acquisition module, used to acquire a component software version set of a target vehicle; the component software version set includes a first component and a software version corresponding to the first component; A determination module is used to perform at least one comparison operation based on the preset baseline version set of the target vehicle and the component software version set until a comparison end condition is met, and use the first baseline version that meets the comparison end condition as the target baseline version of the target vehicle; the baseline version set includes multiple baseline versions, and a second component corresponding to each baseline version and a software version corresponding to the second component.
8. An electronic device comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein: When the processor executes the computer program, the vehicle baseline version determination method according to any one of claims 1 to 6 is implemented.
9. A non-transitory computer-readable storage medium having a computer program stored thereon, characterized in that: When the computer program is executed by a processor, the vehicle baseline version determination method according to any one of claims 1 to 6 is implemented.
10. A computer program product, comprising a computer program, characterized in that When the computer program is executed by a processor, the vehicle baseline version determination method according to any one of claims 1 to 6 is implemented.