Automotive software version management methods, devices, equipment and readable storage media
By determining the function code and version number based on the software code segment in automotive products, and generating function values and function expressions, the correlation problem of software version management in the prior art is solved, realizing the correlation management and update reminder of software versions, and ensuring the normal operation of the whole vehicle functions.
Patent Information
- Application Number
- CN202310669516.4
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- Filing Date
- 2023-06-07
- Publication Date
- 2026-11-17
- Estimated Expiration
- 2043-06-07
AI Technical Summary
Existing automotive software version management methods make it difficult to establish relationships between software versions, resulting in an inability to intuitively identify the software that needs to be changed when a software version changes, which can easily lead to abnormal vehicle functions.
By determining the function code based on the software code segment on the automotive product, obtaining the associated function code and its version number from the automotive software function library, generating function values and function expressions, updating the version number in the function expression after updating the code segment, establishing the software version association relationship, and outputting update reminders.
It enables the management of the relationships between different versions of the same software and between different versions of different software, ensuring the normal operation of the vehicle's functions when the software version is updated.
Smart Images

Figure CN116804931B_ABST
Abstract
Description
Technical Field
[0001] This invention relates to the field of automotive software management technology, and in particular to an automotive software version management method, apparatus, device, and readable storage medium. Background Technology
[0002] As the automotive industry evolves towards electrification, connectivity, and intelligence, the types of software used in vehicles are increasing, and their interrelationships are becoming increasingly complex. Effective management, transmission, and identification of the types of software used in vehicles and their corresponding version information are crucial in design, development, manufacturing, and after-sales service. Current automotive software version management methods lack established relationships between different versions of the same software and between different versions of different software, making it difficult to manage software version dependencies. For example, when a software version changes, it's not readily apparent which software versions need to be changed accordingly, potentially leading to malfunctions in the entire vehicle. Summary of the Invention
[0003] The main objective of this invention is to provide a method, apparatus, device, and readable storage medium for automotive software version management, aiming to solve the technical problem that existing automotive software version management methods are difficult to perform associated management of software versions.
[0004] In a first aspect, the present invention provides a method for managing automotive software versions, the method comprising:
[0005] In automotive products, software functions are determined based on software code segments and associated function codes are obtained from the automotive software function library. The version number of each associated function code is determined, wherein each software function in the automotive software function library corresponds to a unique function code.
[0006] The software's associated function codes and version numbers are combined to generate the software's function values, and all the software's function values are combined to generate the software's function formula.
[0007] If the software's code segment is updated, the version number of the corresponding function code in the updated function expression will be used to form a new function value.
[0008] Optionally, after the steps of combining the function codes associated with the software and their version numbers to generate the function values of the software, and combining all the function values of the software to generate the function formula of the software, the method further includes:
[0009] If the version numbers corresponding to the same function codes in the function formulas of different software in an automotive product are all the same, then a function set for the automotive product is generated based on the function formulas of all software. This function set stores the different function values involved in all software in the automotive product, as well as the association information between each software and each function value.
[0010] Optionally, after the step of updating the version number of the corresponding function code in the function expression according to the updated code segment to form a new function value if the software code segment is updated, the method further includes:
[0011] Update the corresponding function values in the function set according to the new function values;
[0012] Based on the association information in the function set, identify the software to be updated that has the same function code but a different version number as the new function value and output an update reminder.
[0013] Optionally, the step of determining the version number of each function code associated with the software includes:
[0014] Does the vehicle product containing the detection software have a functional library?
[0015] If the automotive product does not have a function library, then the version number of each function code associated with the software is determined to be the initial version number.
[0016] Optionally, after the step of detecting whether the vehicle product containing the detection software has a function library, the method further includes:
[0017] If the automotive product has a function library, then select the function code with an undetermined version number from the function codes associated with the software as the target function code;
[0018] Does the target function code exist in the detection function library?
[0019] If the target function code does not exist in the function library, then the version number of the target function code is determined to be the initial version number;
[0020] If the target function code exists in the function library, then obtain the current version number of the target function code in the function library, and determine the version number of the target function code as the progressive version number of the current version number.
[0021] Optionally, after the step of generating a function set for the automotive product based on the function expressions of all software in the automotive product, where the version numbers corresponding to the same function codes in the function expressions of different software are all the same, and storing the different function values involved in all software in the automotive product, as well as the association information between each software and each function value through the function set, the following further step is included:
[0022] Based on all the function values in the function set and the associated information, determine the functional formulas of all software on a single automotive product;
[0023] Get the software version numbers of all software on a single automotive product;
[0024] Construct software version BOM data for a single vehicle product based on the software name, software function, and software version number.
[0025] Optionally, after the step of constructing the software version BOM data for a single vehicle product based on the software name, software function, and software version number, the method further includes:
[0026] For multiple automotive products, the function set version number of each automotive product is determined based on all function values in each function set and the associated information.
[0027] From the software version BOM data of each automotive product, obtain the corresponding software version number based on the software name;
[0028] Construct software version BOM data for multiple automotive products based on software name, vehicle product name, feature set version number, and software version number.
[0029] Secondly, the present invention also provides an automotive software version management device, the automotive software version management device comprising:
[0030] The association module is used to determine the software function based on the software code segment and obtain the associated function code from the automotive software function library in the automotive product, and determine the version number of each associated function code. Each software function in the automotive software function library corresponds to a unique function code.
[0031] The first generation module is used to combine the function codes associated with the software and their version numbers to generate the function values of the software, and to combine all the function values of the software to generate the function formula of the software.
[0032] The update module is used to update the version number of the corresponding function code in the function expression according to the updated code segment if the software code segment is updated, so as to form a new function value.
[0033] Thirdly, the present invention also provides an automotive software version management device, the automotive software version management device including a processor, a memory, and an automotive software version management program stored in the memory and executable by the processor, wherein when the automotive software version management program is executed by the processor, it implements the steps of the above-described automotive software version management method.
[0034] Fourthly, the present invention also provides a readable storage medium storing an automotive software version management program, wherein when the automotive software version management program is executed by a processor, it implements the steps of the above-described automotive software version management method.
[0035] In this invention, the software in automotive products represents the functions it can perform through function codes in its function expressions. Different versions of the same software differ in the function values within their function expressions, indicating functional changes corresponding to version updates. By comparing whether different software programs have the same function codes, the invention determines whether these programs are functionally related. Furthermore, by comparing whether the version numbers of the same function codes in the function expressions of different software programs are the same, the invention determines whether the software versions are compatible. Therefore, this invention establishes software version associations between different versions of the same software and between different versions of different software, facilitating the management of software version associations. Attached Figure Description
[0036] Figure 1 This is a flowchart illustrating an automotive software version management method according to an embodiment of the present invention.
[0037] Figure 2 This is a flowchart illustrating the automotive software version management method in another embodiment of the present invention;
[0038] Figure 3 This is a flowchart illustrating the process of determining the version number of each function code associated with the software in one embodiment of the present invention.
[0039] Figure 4 This is a schematic diagram of the hardware structure of an automotive software version management device in one embodiment of the present invention;
[0040] Figure 5 This is a schematic diagram of the hardware structure of an automotive software version management device in one embodiment of the present invention.
[0041] The realization of the objective, functional features and advantages of the present invention will be further explained in conjunction with the embodiments and with reference to the accompanying drawings. Detailed Implementation
[0042] It should be understood that the specific embodiments described herein are merely illustrative of the invention and are not intended to limit the invention.
[0043] In a first aspect, embodiments of the present invention provide a method for managing automotive software versions.
[0044] Figure 1 A flowchart illustrating an embodiment of the automotive software version management method of the present invention is shown.
[0045] Reference Figure 1 In one embodiment, the automotive software version management method includes the following steps:
[0046] S11. In automotive products, the software functions are determined based on the software code segments and the associated function codes are obtained from the automotive software function library. The version number of each associated function code is determined. Each software function in the automotive software function library corresponds to a unique function code.
[0047] In this embodiment, an automotive software function library is constructed, containing all software functions that can be implemented in a vehicle. Each software function defines a unique and identifiable function code. An example is shown below:
[0048]
[0049]
[0050] Table 1
[0051] Optionally, function codes can be defined according to function categories for different software functions. For example, in Table 1, both automatic parking and autonomous parking are parking-related functions and belong to the same function category. Therefore, both are categorized using the "C" class when defining their function codes. This helps to define function codes in an orderly manner and facilitates the construction of an automotive software function library.
[0052] The software functions involved are determined by analyzing the software's code segments. Then, the corresponding function codes are retrieved from the vehicle's software function library. These function codes are the software-associated function codes. For example, if the software involves cruise control and tire pressure monitoring, Table 1 shows that the associated function codes are A01 and B01. The version number of the function code indicates the version of the software function. When the code segments related to a software function are adjusted, the function code undergoes version iteration, and the version number of the function code changes.
[0053] S12. Combine the function codes associated with the software and their version numbers to generate the function values of the software, and combine all the function values of the software to generate the function formula of the software.
[0054] In this embodiment, the function value represents a software function and its version, while the function expression represents all the functions the software can implement and their corresponding versions. It can be understood that when the software version changes, it may involve changes to one or more software functions, each corresponding to a uniquely determined function expression and software version number. An example is as follows:
[0055]
[0056] Table 2
[0057] Referring to Table 2, the function expression for Software 1 is A0100 B0101, corresponding to software version number V4001; the function expression for Software 2 is B0101 C0102, corresponding to software version number V3100. Combining this with Table 1, we can see that Software 1 involves cruise control and tire pressure monitoring, while Software 2 involves tire pressure monitoring and automatic parking. Software 1 and Software 2 share the same function code B01, indicating a functional relationship between them. The version number of B01 in both Software 1 and Software 2 is 01, indicating that version V4001 of Software 1 and version V3100 of Software 2 are version-matched.
[0058] S13. If the software code segment is updated, the version number of the corresponding function code in the updated function expression is updated according to the updated code segment to form a new function value.
[0059] In this embodiment, software version updates involve updating the software's code segments. After the code segments are updated, the version number of the corresponding function code needs to be updated to form a new function value. After the function value is updated, the software's function expression will also be updated synchronously, so that the new software version number corresponds to the new software function expression. Based on the changes in the two function expressions before and after the update, it can be seen what software functions are specifically involved in this update. For example, assuming that the function expression of software 1 in version V5001 is A0100 B0102, and the function expression of software 1 in version V4001 is A0100 B0101, referring to Table 1, the version update of software 1 from V4001 to V5001 involves the update of the tire pressure monitoring function.
[0060] In summary, in this embodiment, the software in automotive products represents the functions it can perform through function codes in its function expressions. Different versions of the same software differ in the function values within their function expressions, indicating functional changes corresponding to version updates. By comparing whether different software programs have the same function codes, the system determines whether these programs are functionally related. Furthermore, by comparing whether the version numbers of the same function codes in the function expressions of different software programs are the same, the system determines whether the software versions are compatible. Therefore, this embodiment establishes software version associations between different versions of the same software and between different versions of different software, facilitating the management of software version associations.
[0061] Figure 2 A flowchart illustrating an automotive software version management method according to another embodiment of the present invention is shown.
[0062] Reference Figure 2 In one embodiment, the automotive software version management method includes the following steps:
[0063] S21. In automotive products, the software functions are determined based on the software code segments and the associated function codes are obtained from the automotive software function library. The version number of each associated function code is determined, wherein each software function in the automotive software function library corresponds to a unique function code.
[0064] S22. Combine the function codes associated with the software and their version numbers to generate the function values of the software, and combine all the function values of the software to generate the function formula of the software.
[0065] S23. If the version numbers corresponding to the same function codes in the function formulas of different software in the automotive product are all the same, then generate a function set of the automotive product based on the function formulas of all software, so as to store the different function values involved in all software in the automotive product, as well as the association information between each software and each function value through the function set.
[0066] In this embodiment, all software in the automotive product is defined through steps S21 and S22, possessing function values and function expressions. The version numbers corresponding to the same function codes in the function expressions of different software are identical, indicating that the versions of different software in the automotive product are compatible and the vehicle functions normally. Based on this, the function expressions of all software are further integrated to generate a function set for the automotive product, enabling orderly management of all software function expressions and facilitating the storage and retrieval of software functions and version information for each software in the automotive product. An example is shown below:
[0067]
[0068] Table 3
[0069] Referring to Table 3, the automotive product contains Software 1, Software 2, and Software 3. Their functional codes include A01, B01, C01, and C02. A01 has a unique version number 00, B01 has a unique version number 01, C01 has a unique version number 02, and C02 has a unique version number 00. Correspondingly, the function set stores four function values: A0100, B0101, C0102, and C0200. The function set also stores the association information between Software 1, Software 2, and Software 3 and these four function values. Specifically, Software 1 is associated with A0100 and B0101, Software 2 is associated with B0101 and C0102, and Software 3 is associated with C0200.
[0070] S24. If the software code segment is updated, the version number of the corresponding function code in the updated function expression is updated according to the updated code segment to form a new function value.
[0071] S25. Update the corresponding function value in the function set according to the new function value; based on the association information in the function set, identify the software to be updated that has the same function code but a different version number as the new function value and output an update reminder.
[0072] In this embodiment, software version updates involve updating the software's code segments. The function set can quickly identify the software that is functionally related to the software version update and needs to be updated synchronously, and output update reminders until all functionally related software has been updated, ensuring the normal functioning of the entire vehicle.
[0073] Referring to Table 3, let's assume Software 1 is upgraded from version V4001 to V5001, and the tire pressure monitoring function is upgraded. The relevant code segments are updated, and the version number of B01 in the function expression progresses from 01 to 02, forming a new function value B0102. Based on B0102, B0101 in the function set is updated to B0102. According to the association information, B0102 is also associated with Software 2. The version number corresponding to B01 in Software 2's function expression is 01, which is inconsistent with the updated function value B0102. Therefore, Software 2 is determined to be the software to be updated, and an update reminder is output to Software 2. After Software 2 is updated, a new function value B0102 is formed in Software 2's function expression, consistent with the function value in the function set, indicating that all related software has been updated.
[0074] Figure 3 A flowchart illustrating the process of determining the version number of each function code associated with the software is shown in one embodiment of the present invention.
[0075] Reference Figure 3 In one embodiment, the step of determining the version number of each function code associated with the software includes:
[0076] Does the vehicle product containing the detection software have a functional library?
[0077] If the automotive product does not have a function library, then the version number of each function code associated with the software is determined to be the initial version number.
[0078] In this embodiment, for the initial implementation of the automotive software version management method of the present invention on an automotive product, all software on the automotive product is undefined and the automotive product does not have a function library. At this time, it is necessary to set a unified initial version number for all function codes as the basis for version number progression during subsequent version upgrades. Specifically, 00 in Table 2 is the initial version number.
[0079] Continue to refer to Figure 3 In one embodiment, after the step of detecting whether the vehicle product containing the software has a function library, the method further includes:
[0080] If the automotive product has a function library, then select the function code with an undetermined version number from the function codes associated with the software as the target function code;
[0081] Check if the target function code exists in the function library;
[0082] If the target function code does not exist in the function library, then the version number of the target function code is determined to be the initial version number;
[0083] If the target function code exists in the function library, obtain the current version number of the target function code in the function library, and determine the version number of the target function code as the progressive version number of the current version number.
[0084] In this embodiment, the automotive software version management method of the present invention is further implemented in automotive products, for example, by improving an existing automotive product, adding new software to the automotive product, or adding new functions to existing software in the automotive product. Since the automotive product before improvement already has a function library, and each function code in the function library has a corresponding version number, this embodiment specifies a method for determining the function code version number for different situations: for function codes not defined in the function library, the version number is set to the initial version number; for function codes already defined in the function library, the version number is set to the progressive version number of the current version number. For example, the current version number is 00, and the progressive version number is 01.
[0085] Optionally, to differentiate function sets for different automotive products, a function set version number is defined. This version number changes when the function values and / or relationships within the function set change. For example, assuming the function set version in Table 3 is 03, and during automotive product improvements, B0101 in the function set is updated to B0102, then the function set version number increments to 04. The updated function set is represented as follows:
[0086]
[0087] Table 4
[0088] Furthermore, in one embodiment, the method further includes the following after step S23:
[0089] Based on all the function values and associated information in the function set, determine the functional formulas of all software on a single automotive product;
[0090] Get the software version numbers of all software on a single automotive product;
[0091] Construct software version BOM data for a single vehicle product based on the software name, software function, and software version number.
[0092] In this embodiment, software version BOM data for a single vehicle product is quickly constructed using a set of functions. This software version BOM data allows for the identification of the applicable software version for each vehicle product and its associated software versions, thus achieving systematic and visual management of software versions. For example, the left-hand side of the function sets in Tables 3 and 4 represents the software version BOM data for a single vehicle product.
[0093] Furthermore, in one embodiment, after the step of constructing the software version BOM data for a single vehicle product based on the software name, software function, and software version number, the method further includes:
[0094] For multiple automotive products, the function set version number of each automotive product is determined based on all function values and associated information in each function set;
[0095] From the software version BOM data of each automotive product, obtain the corresponding software version number based on the software name;
[0096] Construct software version BOM data for multiple automotive products based on software name, vehicle product name, feature set version number, and software version number.
[0097] In this embodiment, the analysis of function set version numbers is as described above. By using the function sets and corresponding function set version numbers of multiple automotive products, software version BOM data for multiple automotive products can be quickly constructed, enabling the management of software version differences for the same software across different automotive products. An example is shown below:
[0098]
[0099] The feature set for version 03 is shown in Table 3, and the feature set for version 04 is shown in Table 4. The same software version is the same across different automotive products with the same feature set. The same software version may be either the same or different across different automotive products with different feature set versions.
[0100] Secondly, embodiments of the present invention also provide an automotive software version management device.
[0101] Figure 4 A schematic diagram of the hardware structure of an automotive software version management device according to an embodiment of the present invention is shown.
[0102] Reference Figure 4 In one embodiment, the vehicle software version management device includes:
[0103] The association module 10 is used to determine the software function based on the software code segment and obtain the associated function code from the automotive software function library in the automotive product, and determine the version number of each associated function code of the software. Each software function in the automotive software function library corresponds to a unique function code.
[0104] The first generation module 20 is used to combine the function codes associated with the software and their version numbers to generate the function values of the software, and to combine all the function values of the software to generate the function formula of the software.
[0105] The update module 30 is used to update the version number of the corresponding function code in the function expression according to the updated code segment if the software code segment is updated, so as to form a new function value.
[0106] Furthermore, in one embodiment, the automotive software version management device further includes a second generation module 40, which is used to generate a function set of the automotive product based on the function formulas of all software if the version numbers corresponding to the same function codes in the function formulas of different software in the automotive product are all the same, so as to store the different function values involved in all software in the automotive product, as well as the association information between each software and each function value through the function set.
[0107] Furthermore, in one embodiment, the update module 30 is also used to:
[0108] Update the corresponding function values in the function set according to the new function values;
[0109] Based on the association information in the function set, identify the software to be updated that has the same function code as the new function value but a different version number, and output an update reminder.
[0110] Furthermore, in one embodiment, the first generation module 20 is used to:
[0111] Does the vehicle product containing the detection software have a functional library?
[0112] If the automotive product does not have a function library, then the version number of each function code associated with the software is determined to be the initial version number.
[0113] Furthermore, in one embodiment, the first generation module 20 is also used for:
[0114] If the automotive product has a function library, then select the function code with an undetermined version number from the function codes associated with the software as the target function code;
[0115] Check if the target function code exists in the function library;
[0116] If the target function code does not exist in the function library, then the version number of the target function code is determined to be the initial version number;
[0117] If the target function code exists in the function library, obtain the current version number of the target function code in the function library, and determine the version number of the target function code as the progressive version number of the current version number.
[0118] Furthermore, in one embodiment, the automotive software version management device further includes a third generation module 50, used for:
[0119] Based on all the function values and associated information in the function set, determine the functional formulas of all software on a single automotive product;
[0120] Get the software version numbers of all software on a single automotive product;
[0121] Construct software version BOM data for a single vehicle product based on the software name, software function, and software version number.
[0122] Furthermore, in one embodiment, the third generation module 50 is also used for:
[0123] For multiple automotive products, the function set version number of each automotive product is determined based on all function values and associated information in each function set;
[0124] From the software version BOM data of each automotive product, obtain the corresponding software version number based on the software name;
[0125] Construct software version BOM data for multiple automotive products based on software name, vehicle product name, feature set version number, and software version number.
[0126] The functions of each module in the aforementioned automotive software version management device correspond to the steps in the aforementioned automotive software version management method embodiment, and their functions and implementation processes will not be described in detail here.
[0127] Thirdly, embodiments of the present invention provide an automotive software version management device, which can be a personal computer (PC), a laptop computer, a server, or other device with data processing capabilities.
[0128] Figure 5 A schematic diagram of the hardware structure of an automotive software version management device according to an embodiment of the present invention is shown.
[0129] Reference Figure 5In this embodiment of the invention, the automotive software version management device may include a processor 1001 (e.g., a Central Processing Unit, CPU), a communication bus 1002, a user interface 1003, a network interface 1004, and a memory 1005. The communication bus 1002 is used to enable communication between these components; the user interface 1003 may include a display screen or an input unit such as a keyboard; the network interface 1004 may optionally include a standard wired interface or a wireless interface (e.g., Wireless Fidelity, Wi-Fi); the memory 1005 may be high-speed random access memory (RAM) or stable memory (non-volatile memory), such as a disk storage device. Alternatively, the memory 1005 may also be a storage device independent of the aforementioned processor 1001. Those skilled in the art will understand that… Figure 5 The hardware structure shown does not constitute a limitation of the invention and may include more or fewer components than shown, or combine certain components, or have different component arrangements.
[0130] Continue to refer to Figure 5 , Figure 5 The memory 1005, serving as a computer storage medium, may include an operating system, a network communication module, a user interface module, and an automotive software version management program. The processor 1001 can call the automotive software version management program stored in the memory 1005 and execute the automotive software version management method provided in this embodiment of the invention.
[0131] Fourthly, embodiments of the present invention also provide a readable storage medium.
[0132] The present invention provides a readable storage medium storing an automotive software version management program, wherein when the automotive software version management program is executed by a processor, it implements the steps of the automotive software version management method described above.
[0133] The method implemented when the automotive software version management program is executed can be referred to in various embodiments of the automotive software version management method of the present invention, and will not be repeated here.
[0134] It should be noted that, in this document, the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or system that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or system. 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 system that includes that element.
[0135] The sequence numbers of the above embodiments of the present invention are for descriptive purposes only and do not represent the superiority or inferiority of the embodiments.
[0136] Through the above description of the embodiments, those skilled in the art can clearly understand that the methods of the above embodiments can be implemented by means of software plus necessary general-purpose hardware platforms. Of course, they can also be implemented by hardware, but in many cases the former is a better implementation method. Based on this understanding, the technical solution of the present invention, in essence, or the part that contributes to the prior art, can be embodied in the form of a software product. This computer software product is stored in a storage medium (such as ROM / RAM, magnetic disk, optical disk) as described above, and includes several instructions to cause a terminal device to execute the methods described in the various embodiments of the present invention.
[0137] The above are merely preferred embodiments of the present invention and do not limit the scope of the patent. Any equivalent structural or procedural transformations made based on the description and drawings of the present invention, or direct or indirect applications in other related technical fields, are similarly included within the scope of patent protection of the present invention.
Claims
1. A method for managing automotive software versions, characterized in that, The automotive software version management method includes: In automotive products, software functions are determined based on software code segments and associated function codes are obtained from the automotive software function library. The version number of each associated function code is determined, wherein each software function in the automotive software function library corresponds to a unique function code. The software's associated function codes and version numbers are combined to generate the software's function values, and all the software's function values are combined to generate the software's function formula. If the version numbers corresponding to the same function codes in the function formulas of different software in an automotive product are all the same, then a function set of the automotive product is generated based on the function formulas of all software. The function set stores the different function values involved in all software in the automotive product, as well as the association information between each software and each function value. Based on all the function values in the function set and the associated information, determine the functional formulas of all software on a single automotive product; Get the software version numbers of all software on a single automotive product; Construct software version BOM data for a single vehicle product based on the software name, software function, and software version number; If the software's code segment is updated, the version number of the corresponding function code in the updated function expression will be used to form a new function value.
2. The automotive software version management method as described in claim 1, characterized in that, Following the step of updating the version number of the corresponding function code in the function expression according to the updated code segment to form a new function value if the software code segment is updated, the method further includes: Update the corresponding function values in the function set according to the new function values; Based on the association information in the function set, identify the software to be updated that has the same function code but a different version number as the new function value and output an update reminder.
3. The automotive software version management method as described in claim 1, characterized in that, The step of determining the version number of each function code associated with the software includes: Does the vehicle product containing the detection software have a functional library? If the automotive product does not have a function library, then the version number of each function code associated with the software is determined to be the initial version number.
4. The automotive software version management method as described in claim 3, characterized in that, Following the step of determining whether the automotive product containing the detection software has a function library, the following is also included: If the automotive product has a function library, then select the function code with an undetermined version number from the function codes associated with the software as the target function code; Does the target function code exist in the detection function library? If the target function code does not exist in the function library, then the version number of the target function code is determined to be the initial version number; If the target function code exists in the function library, then obtain the current version number of the target function code in the function library, and determine the version number of the target function code as the progressive version number of the current version number.
5. The automotive software version management method as described in claim 1, characterized in that, Following the step of constructing the software version BOM data for a single vehicle product based on the software name, software function, and software version number, the method further includes: For multiple automotive products, the function set version number of each automotive product is determined based on all function values in each function set and the associated information. From the software version BOM data of each automotive product, obtain the corresponding software version number based on the software name; Construct software version BOM data for multiple automotive products based on software name, vehicle product name, feature set version number, and software version number.
6. A vehicle software version management device, characterized in that, The vehicle software version management device includes: The association module is used to determine the software function based on the software code segment and obtain the associated function code from the automotive software function library in the automotive product, and determine the version number of each associated function code. Each software function in the automotive software function library corresponds to a unique function code. The first generation module is used to combine the function codes associated with the software and their version numbers to generate the function values of the software, and to combine all the function values of the software to generate the function formula of the software. The second generation module is used to generate a function set of the automotive product based on the function formulas of all software if the version numbers corresponding to the same function codes in the function formulas of different software in the automotive product are all the same. The function set stores the different function values involved in all software in the automotive product, as well as the association information between each software and each function value. The third generation module is used to determine the functional formulas of all software on a single vehicle product based on all functional values and associated information in the functional set; obtain the software version numbers of all software on a single vehicle product; and construct the software version BOM data of a single vehicle product based on the software name, software functional formula, and software version number. The update module is used to update the version number of the corresponding function code in the function expression according to the updated code segment if the software code segment is updated, so as to form a new function value.
7. A vehicle software version management device, characterized in that, The automotive software version management device includes a processor, a memory, and an automotive software version management program stored in the memory and executable by the processor, wherein when the automotive software version management program is executed by the processor, it implements the steps of the automotive software version management method as described in any one of claims 1 to 5.
8. A readable storage medium, characterized in that, The readable storage medium stores an automotive software version management program, wherein when the automotive software version management program is executed by a processor, it implements the steps of the automotive software version management method as described in any one of claims 1 to 5.
Citation Information
Patent Citations
Software version control method
CN103500112A
Method and system for updating a software program installed in an electronic device
CN110069275A
