Vehicle-mounted software integration method and device, electronic equipment and storage medium

Abstract

The invention provides a vehicle-mounted software integration method and device, electronic equipment and a storage medium, and the method comprises the steps: generating a first interface description file of a software component of vehicle-mounted software; verifying the first interface description file to obtain a verification result; adjusting the first interface description file according to the verification result to obtain a second interface description file; compiling environment information is configured; and compiling and integrating the second interface description file according to the configured compiling environment information. By implementing the method and the device, the integration efficiency of the vehicle-mounted software can be improved, the development cycle can be shortened, the stability of the vehicle-mounted software and the vehicle-mounted management system can be improved, the vehicle-mounted software is ensured not to easily break down in the vehicle driving process, and more application requirements can be met.

Description

Technical Field

[0001] The present application relates to the technical field of vehicle-mounted software integration, and in particular to a vehicle-mounted software integration method, device, electronic device and storage medium. Background Art

[0002] The compilation and integration of vehicle-mounted software is a necessary way to develop vehicle-mounted software and vehicle management systems. With the upgrading of vehicles, the requirements for vehicle-mounted software are becoming higher and higher. Most traditional vehicle-mounted software can no longer meet the usage requirements. As the number of vehicle-mounted software developments continues to increase, more requirements are put forward for the compilation and integration of software.

[0003] There are many problems with the existing vehicle software integration methods, such as low integration efficiency, long development cycle, and poor system stability. At the same time, due to the poor stability of the vehicle software, there are likely to be abnormalities or freezes during vehicle operation, which brings many disadvantages to the vehicle's driving and is difficult to meet the current needs of intelligent connected vehicles. Summary of the invention

[0004] The purpose of this application is to provide a vehicle-mounted software integration method, device, electronic device and storage medium, which can improve the integration efficiency of vehicle-mounted software, shorten the development cycle, improve the stability of vehicle-mounted software and vehicle-mounted management system, ensure that the vehicle-mounted software is not prone to failure during vehicle driving, and meet more application needs.

[0005] In a first aspect, an embodiment of the present application provides a method for integrating vehicle-mounted software, the method comprising:

[0006] Generating a first interface description file of a software component of the vehicle-mounted software;

[0007] Verifying the first interface description file to obtain a verification result;

[0008] Adjust the first interface description file according to the verification result to obtain a second interface description file;

[0009] Configure compilation environment information;

[0010] The second interface description file is compiled and integrated according to the configured compilation environment information.

[0011] In the above implementation process, by verifying, adjusting, and updating the first interface description file of the software component, the vehicle-mounted software is adaptively integrated from the source, which can improve the integration efficiency of the vehicle-mounted software, shorten the development cycle, and improve the stability of the vehicle-mounted software and the vehicle-mounted management system. It ensures that the vehicle-mounted software is not prone to failure during vehicle driving and can meet more application requirements.

[0012] Furthermore, the step of generating a first interface description file of a software component of the vehicle-mounted software includes:

[0013] Obtaining interface attribute information of a software component of the vehicle-mounted software;

[0014] A first interface description file of the software component is generated according to the interface attribute information.

[0015] In the above implementation process, the first interface description file is generated according to the interface attribute information, so that the first interface description file contains the real-time access status information of the input interface and output interface of the software component, which can better detect the faults occurring during the integration process.

[0016] Furthermore, the step of verifying the first interface description file to obtain a verification result includes:

[0017] Obtaining demand information of the vehicle-mounted software;

[0018] The first interface description file is modified according to the requirement information of the vehicle-mounted software to obtain a third interface description file;

[0019] The third interface description file is verified to obtain a verification result.

[0020] In the above implementation process, the first interface description file is changed according to the requirement information of the vehicle-mounted software, so that the generated third interface description file is closer to the user's needs and meets more application requirements.

[0021] Furthermore, the step of verifying the third interface description file to obtain a verification result includes:

[0022] Dynamically verifying the third interface description file to obtain a first verification result;

[0023] Performing static verification on the third interface description file to obtain a second verification result;

[0024] The verification result is obtained according to the first verification result and the second verification result.

[0025] In the above implementation process, the third interface description file is dynamically checked and statically checked respectively, so that the interface can be verified from multiple dimensions, thereby improving the stability and compatibility of the interface during the integration process, thereby improving the integration efficiency.

[0026] Further, the step of dynamically verifying the third interface description file to obtain a first verification result includes:

[0027] Extracting the interface name and parameter type from the third interface description file;

[0028] Verify the interface name and the parameter type according to a pre-built verification model to determine whether the interface name and the parameter type conform to specification information;

[0029] If not, determining that the first verification result is verification failure;

[0030] If so, determine that the first verification result is verification passed.

[0031] In the above implementation process, the interface name and parameter type are dynamically checked according to the pre-built verification model to ensure the accuracy of data during the integration process, shorten the verification time, report abnormal or unreasonable parameters in time, and maintain the stability of data access.

[0032] Further, the step of performing static verification on the third interface description file to obtain a second verification result includes:

[0033] Extracting global variables in the third interface description file;

[0034] Performing static verification on the global variables according to a static analysis method to determine whether there are potential anomalies in the global variables;

[0035] If yes, determining that the second verification result is failed;

[0036] If not, determine that the second verification result is verification passed.

[0037] In the above implementation process, static verification is performed on global variables according to static analysis methods, and abnormal information in global variables is checked in time, which can reduce possible errors in the compilation process and improve integration efficiency.

[0038] Furthermore, after the step of compiling and integrating the second interface description file according to the configured compilation environment information, the method further includes:

[0039] Perform integration testing on the compiled and integrated vehicle software to obtain test results;

[0040] The compiled and integrated vehicle software is optimized according to the test results.

[0041] In the above implementation process, the integrated vehicle software is integrated tested and optimized according to the test results, which can improve the stability and compatibility of the integration and enable the vehicle software to adapt to more usage requirements.

[0042] In a second aspect, an embodiment of the present application further provides a vehicle-mounted software integration device, the device comprising:

[0043] A generating module, used for generating a first interface description file of a software component of the vehicle-mounted software;

[0044] A verification module, used to verify the first interface description file and obtain a verification result;

[0045] An adjustment module, configured to adjust the first interface description file according to the verification result to obtain a second interface description file;

[0046] Configuration module, used to configure compilation environment information;

[0047] An integration module is used to compile and integrate the second interface description file according to the configured compilation environment information.

[0048] In the above implementation process, by verifying, adjusting, and updating the first interface description file of the software component, the vehicle-mounted software is adaptively integrated from the source, which can improve the integration efficiency of the vehicle-mounted software, shorten the development cycle, and improve the stability of the vehicle-mounted software and the vehicle-mounted management system. It ensures that the vehicle-mounted software is not prone to failure during vehicle driving and can meet more application requirements.

[0049] In a third aspect, an embodiment of the present application provides an electronic device, comprising: a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor implements the steps of the method described in any one of the first aspects when executing the computer program.

[0050] In a fourth aspect, an embodiment of the present application provides a computer-readable storage medium, on which instructions are stored. When the instructions are executed on a computer, the computer executes the method as described in any one of the first aspects.

[0051] Other features and advantages of the present disclosure will be set forth in the following description, or some features and advantages may be inferred or unambiguously determined from the description, or may be learned by implementing the above-mentioned technology of the present disclosure.

[0052] And it can be implemented according to the contents of the specification. The following is a detailed description of the preferred embodiments of the present application with reference to the accompanying drawings. BRIEF DESCRIPTION OF THE DRAWINGS

[0053] In order to more clearly illustrate the technical solutions of the embodiments of the present application, the drawings required for use in the embodiments of the present application will be briefly introduced below. It should be understood that the following drawings only show certain embodiments of the present application and therefore should not be regarded as limiting the range values. For ordinary technicians in this field, other related drawings can be obtained based on these drawings without paying any creative work.

[0054] Figure 1 A flowchart of a vehicle software integration method provided in an embodiment of the present application;

[0055] Figure 2 A schematic diagram of the structure of the vehicle-mounted software integration device provided in an embodiment of the present application;

[0056] Figure 3 A schematic diagram of the structural composition of an electronic device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0057] The technical solutions in the embodiments of the present application will be described below in conjunction with the drawings in the embodiments of the present application.

[0058] It should be noted that similar reference numerals and letters represent similar items in the following drawings, so once an item is defined in one drawing, it does not need to be further defined and explained in subsequent drawings. At the same time, in the description of this application, the terms "first", "second", etc. are only used to distinguish the description and cannot be understood as indicating or implying relative importance.

[0059] The specific implementation methods of the present application are further described in detail below in conjunction with the accompanying drawings and examples. The following examples are used to illustrate the present application, but are not used to limit the scope of the present application.

[0060] Embodiment 1

[0061] Figure 1 is a flow chart of the vehicle software integration method provided by the embodiment of the present application, such as Figure 1 As shown, the method includes:

[0062] S1, generating a first interface description file of a software component of the vehicle-mounted software;

[0063] S2, verifying the first interface description file to obtain a verification result;

[0064] S3, adjusting the first interface description file according to the verification result to obtain a second interface description file;

[0065] S4, configure compilation environment information;

[0066] S5, compile and integrate the second interface description file according to the configured compilation environment information.

[0067] In the above implementation process, by verifying, adjusting, and updating the first interface description file of the software component, the vehicle-mounted software is adaptively integrated from the source, which can improve the integration efficiency of the vehicle-mounted software, shorten the development cycle, and improve the stability of the vehicle-mounted software and the vehicle-mounted management system. It ensures that the vehicle-mounted software is not prone to failure during vehicle driving and can meet more application requirements.

[0068] Furthermore, S1 includes:

[0069] Obtaining interface attribute information of software components of vehicle-mounted software;

[0070] A first interface description file of the software component is generated according to the interface attribute information.

[0071] In the above implementation process, the first interface description file is generated according to the interface attribute information, so that the first interface description file contains the real-time access status information of the input interface and output interface of the software component, which can better detect the faults occurring during the integration process.

[0072] The interface of the software component includes an input interface and an output interface, each of which has interface attribute information, including real-time runtime environment (RTE) interface attribute information and global variable interface attribute information. According to the interface attribute information, a first interface description file is generated, which includes detailed information such as the name, type, parameters, and return value of the interface.

[0073] The input interface is used to receive data or instructions from other software components or external systems, and the output interface is used to send data or instructions to other software components or external systems.

[0074] RTE interface attribute information is used to describe the behavior of the interface in RTE, including the timing of interface call and parameter transfer method.

[0075] The global variable interface attribute information is used to describe the association between the interface and the global variable, including the naming rules, data types, scopes, etc. of the global variable.

[0076] Furthermore, S2 includes:

[0077] Obtain demand information for in-vehicle software;

[0078] The first interface description file is modified according to the requirement information of the vehicle-mounted software to obtain a third interface description file;

[0079] The third interface description file is verified to obtain a verification result.

[0080] In the above implementation process, the first interface description file is changed according to the requirement information of the vehicle-mounted software, so that the generated third interface description file is closer to the user's needs and meets more application requirements.

[0081] According to actual needs, the interface function is changed, and the first interface description file is updated in real time to ensure the consistency and accuracy of the interface information. The change of this application is a dynamic update mechanism, which can realize the online update of the interface during the software integration process. When the interface changes, there is no need to recompile the entire software component, only the affected interface part needs to be updated.

[0082] Furthermore, the step of verifying the third interface description file to obtain a verification result includes:

[0083] Dynamically verifying the third interface description file to obtain a first verification result;

[0084] Performing static verification on the third interface description file to obtain a second verification result;

[0085] A verification result is obtained according to the first verification result and the second verification result.

[0086] In the above implementation process, the third interface description file is dynamically checked and statically checked respectively, so that the interface can be verified from multiple dimensions, thereby improving the stability and compatibility of the interface during the integration process, thereby improving the integration efficiency.

[0087] The embodiment of the present application introduces a dynamic interface verification mechanism. During the software integration process, the interface is updated online and the interface of the software component is verified, including static verification and dynamic verification.

[0088] The interface is modified and optimized as necessary according to the verification result. For interfaces that fail to pass the verification, the interface definition should be redesigned or adjusted. In the embodiment of the present application, when one of the first verification result and the second verification result is a verification failure, the verification result is a failure.

[0089] Furthermore, the step of dynamically verifying the third interface description file to obtain a first verification result includes:

[0090] Extracting the interface name and parameter type from the third interface description file;

[0091] Verify the interface name and parameter type according to the pre-built verification model to determine whether the interface name and parameter type conform to the specification information;

[0092] If not, determining the first verification result is verification failure;

[0093] If so, determine that the first verification result is verification passed.

[0094] In the above implementation process, the interface name and parameter type are dynamically checked according to the pre-built verification model to ensure the accuracy of data during the integration process, shorten the verification time, report abnormal or unreasonable parameters in time, and maintain the stability of data access.

[0095] Dynamic verification mainly includes RTE interface verification. RTE interface verification checks whether the interface complies with the AUTomotive Open System Architecture (AUTOSAR) specification (specification information), including interface name, parameter type, return value, etc.

[0096] The embodiment of the present application uses an automated verification tool (verification model) to perform RTE interface verification.

[0097] Further, the step of performing static verification on the third interface description file to obtain a second verification result includes:

[0098] Extracting global variables in the third interface description file;

[0099] Perform static verification on global variables according to static analysis methods to determine whether there are potential anomalies in global variables;

[0100] If so, determining that the second verification result is failed;

[0101] If not, determine that the second verification result is verification passed.

[0102] In the above implementation process, static verification is performed on global variables according to static analysis methods, and abnormal information in global variables is checked in time, which can reduce possible errors in the compilation process and improve integration efficiency.

[0103] Static verification is global variable interface verification, which mainly checks whether the interface meets the requirements for the use of global variables, including variable naming rules, data types, scopes, etc. Introduce automated verification tools to improve verification efficiency and accuracy.

[0104] The embodiment of the present application performs code review on global variables based on a static analysis tool (or a static analysis method) to check whether there are potential errors or problems.

[0105] In S4, the compilation environment information includes the information required to provide a virtualized integrated environment and support parallel development and testing of multiple software components. Configuring the compilation environment information in advance can reduce development costs and improve development efficiency.

[0106] The compilation environment information configuration includes the configuration of the compiler version, compilation options, link library, etc.

[0107] The configured compilation environment information needs to ensure that the compilation environment complies with the AUTOSAR specification requirements and can correctly compile and link software components. The embodiment of the present application can compile multiple software components at the same time.

[0108] In S5, after the interface verification is passed, the software components are compiled to generate executable files. This application introduces parallel compilation technology to improve compilation efficiency. The compiled software components are integrated with the AUTOSAR basic software library to generate complete vehicle software.

[0109] During the integration process, the embodiment of the present application optimizes the integration process according to the dependencies and interface information of the software components, thereby reducing unnecessary duplication of work.

[0110] Furthermore, after the step of compiling and integrating the second interface description file according to the configured compilation environment information, the method further includes:

[0111] Perform integration testing on the compiled and integrated vehicle software to obtain test results;

[0112] Optimize the compiled and integrated vehicle software based on the test results.

[0113] In the above implementation process, the integrated vehicle software is integrated tested and optimized according to the test results, which can improve the stability and compatibility of the integration and enable the vehicle software to adapt to more usage requirements.

[0114] Test the integrated vehicle software, including unit testing, integration testing and system testing. According to the test results, optimize the software to improve the stability and performance of the system. Optimization and debugging tools: According to the test results, optimize and debug the software to improve the stability and performance of the system.

[0115] Unit testing is to perform unit testing on each software component to ensure that the internal logic of the component is correct, including boundary testing, exception testing, etc., to verify the behavior of the component in different situations; integration testing verifies whether the interfaces and communications between software components are normal, and should cover all possible scenarios and use cases to ensure the integrity and reliability of the system; system-level testing verifies whether the system of the in-vehicle software meets the design requirements, including performance testing, stability testing, safety testing, etc.

[0116] Optimize based on the test results, including code optimization, memory optimization, performance optimization, etc.

[0117] The embodiments of the present application improve the integration efficiency of vehicle-mounted software and reduce development costs through interface dynamic update technology, parallel compilation technology, and automated verification and testing technology. Through virtualized integration environment and parallel development and testing technology, development costs are reduced, development cycles are shortened, and system stability and reliability are enhanced.

[0118] Embodiment 2

[0119] In order to execute the method corresponding to the above embodiment 1 to achieve the corresponding functions and technical effects, a vehicle-mounted software integration device is provided below, such as Figure 2 As shown, the device comprises:

[0120] A generating module 1, used to generate a first interface description file of a software component of the vehicle-mounted software;

[0121] Verification module 2, used to verify the first interface description file and obtain a verification result;

[0122] An adjustment module 3, used for adjusting the first interface description file according to the verification result to obtain a second interface description file;

[0123] Configuration module 4, used to configure compilation environment information;

[0124] The integration module 5 is used to compile and integrate the second interface description file according to the configured compilation environment information.

[0125] In the above implementation process, by verifying, adjusting, and updating the first interface description file of the software component, the vehicle-mounted software is adaptively integrated from the source, which can improve the integration efficiency of the vehicle-mounted software, shorten the development cycle, and improve the stability of the vehicle-mounted software and the vehicle-mounted management system. It ensures that the vehicle-mounted software is not prone to failure during vehicle driving and can meet more application requirements.

[0126] Furthermore, the generating module 1 is also used for:

[0127] Obtaining interface attribute information of software components of vehicle-mounted software;

[0128] A first interface description file of the software component is generated according to the interface attribute information.

[0129] In the above implementation process, the first interface description file is generated according to the interface attribute information, so that the first interface description file contains the real-time access status information of the input interface and output interface of the software component, which can better detect the faults occurring during the integration process.

[0130] Furthermore, the verification module 2 is also used for:

[0131] Obtain demand information for in-vehicle software;

[0132] The first interface description file is modified according to the requirement information of the vehicle-mounted software to obtain a third interface description file;

[0133] The third interface description file is verified to obtain a verification result.

[0134] In the above implementation process, the first interface description file is changed according to the requirement information of the vehicle-mounted software, so that the generated third interface description file is closer to the user's needs and meets more application requirements.

[0135] Furthermore, the verification module 2 is also used for:

[0136] Dynamically verifying the third interface description file to obtain a first verification result;

[0137] Performing static verification on the third interface description file to obtain a second verification result;

[0138] A verification result is obtained according to the first verification result and the second verification result.

[0139] In the above implementation process, the third interface description file is dynamically checked and statically checked respectively, so that the interface can be verified from multiple dimensions, thereby improving the stability and compatibility of the interface during the integration process, thereby improving the integration efficiency.

[0140] Furthermore, the verification module 2 is also used for:

[0141] Extracting the interface name and parameter type from the third interface description file;

[0142] Verify the interface name and parameter type according to the pre-built verification model to determine whether the interface name and parameter type conform to the specification information;

[0143] If not, determining the first verification result is verification failure;

[0144] If so, determine that the first verification result is verification passed.

[0145] In the above implementation process, the interface name and parameter type are dynamically checked according to the pre-built verification model to ensure the accuracy of data during the integration process, shorten the verification time, report abnormal or unreasonable parameters in time, and maintain the stability of data access.

[0146] Furthermore, the verification module 2 is also used for:

[0147] Extracting global variables in the third interface description file;

[0148] Perform static verification on global variables according to static analysis methods to determine whether there are potential anomalies in global variables;

[0149] If so, determining that the second verification result is failed;

[0150] If not, determine that the second verification result is verification passed.

[0151] In the above implementation process, static verification is performed on global variables according to static analysis methods, and abnormal information in global variables is checked in time, which can reduce possible errors in the compilation process and improve integration efficiency.

[0152] Furthermore, the device also includes an optimization module, which is used to:

[0153] Perform integration testing on the compiled and integrated vehicle software to obtain test results;

[0154] Optimize the compiled and integrated vehicle software based on the test results.

[0155] In the above implementation process, the integrated vehicle software is integrated tested and optimized according to the test results, which can improve the stability and compatibility of the integration and enable the vehicle software to adapt to more usage requirements.

[0156] The above-mentioned vehicle-mounted software integration device can implement the method of the above-mentioned embodiment 1. The options in the above-mentioned embodiment 1 are also applicable to this embodiment and will not be described in detail here.

[0157] The rest of the contents of the embodiments of the present application can refer to the contents of the above-mentioned embodiment 1, and will not be repeated in this embodiment.

[0158] Embodiment 3

[0159] An embodiment of the present application provides an electronic device, including a memory and a processor, wherein the memory is used to store a computer program, and the processor runs the computer program to enable the electronic device to execute the vehicle-mounted software integration method of embodiment one.

[0160] Optionally, the above-mentioned electronic device may be a server.

[0161] See also Figure 3 , Figure 3 The schematic diagram of the structure of the electronic device provided in the embodiment of the present application. The electronic device may include a processor 31, a communication interface 32, a memory 33 and at least one communication bus 34. The communication bus 34 is used to realize direct connection and communication between these components.

[0162] Optionally, the electronic device may further include a storage controller and an input / output unit. The memory 33, the storage controller, the processor 31, the peripheral interface, and the input / output unit are electrically connected to each other directly or indirectly to achieve data transmission or interaction.

[0163] The input and output unit is used to provide users with the task creation and to create an optional time period or preset execution time for the task to enable interaction between the user and the server. The input and output unit can be, but is not limited to, a mouse and a keyboard.

[0164] Understandably, Figure 3 The structure shown is for illustration only. The electronic device may also include Figure 3 More or fewer components as shown, or with Figure 3 Different configurations are shown. Figure 3 The components shown in the figure can be implemented by hardware, vehicle-mounted software or a combination thereof.

[0165] In addition, an embodiment of the present application also provides a computer-readable storage medium, which stores a computer program, and when the computer program is executed by a processor, the vehicle-mounted software integration method of embodiment one is implemented.

[0166] The embodiment of the present application also provides a computer program product, which, when running on a computer, enables the computer to execute the method described in the method embodiment.

[0167] The above description is only an embodiment of the present application and is not intended to limit the protection scope of the present application. For those skilled in the art, the present application may have various changes and variations. Any modifications, equivalent substitutions, improvements, etc. made within the spirit and principles of the present application should be included in the protection scope of the present application. It should be noted that similar numbers and letters represent similar items in the following drawings, so once an item is defined in one drawing, it does not need to be further defined and explained in the subsequent drawings.

[0168] The above is only a specific implementation of the present application, but the protection range of the present application is not limited thereto. Any technician familiar with the technical field can easily think of changes or substitutions within the technical range disclosed in the present application, which should be included in the protection range of the present application. Therefore, the protection range of the present application should be based on the protection range of the claims.

Claims

1. A vehicle software integration method, characterized in that: The method comprises: Generating a first interface description file of a software component of the vehicle-mounted software; Verifying the first interface description file to obtain a verification result; Adjust the first interface description file according to the verification result to obtain a second interface description file; Configure compilation environment information; The second interface description file is compiled and integrated according to the configured compilation environment information.

2. The vehicle software integration method according to claim 1, characterized in that: The step of generating a first interface description file of a software component of the vehicle-mounted software comprises: Obtaining interface attribute information of a software component of the vehicle-mounted software; A first interface description file of the software component is generated according to the interface attribute information.

3. The vehicle software integration method according to claim 1, characterized in that: The step of verifying the first interface description file to obtain a verification result includes: Obtaining demand information of the vehicle-mounted software; The first interface description file is modified according to the requirement information of the vehicle-mounted software to obtain a third interface description file; The third interface description file is verified to obtain a verification result.

4. The vehicle software integration method according to claim 3, characterized in that: The step of verifying the third interface description file to obtain a verification result includes: Dynamically verifying the third interface description file to obtain a first verification result; Performing static verification on the third interface description file to obtain a second verification result; The verification result is obtained according to the first verification result and the second verification result.

5. The vehicle software integration method according to claim 4, characterized in that: The step of dynamically verifying the third interface description file to obtain a first verification result includes: Extracting the interface name and parameter type from the third interface description file; Verify the interface name and the parameter type according to a pre-built verification model to determine whether the interface name and the parameter type conform to specification information; If not, determining that the first verification result is verification failure; If so, determine that the first verification result is verification passed.

6. The vehicle software integration method according to claim 4, characterized in that: The step of performing static verification on the third interface description file to obtain a second verification result includes: Extracting global variables in the third interface description file; Performing static verification on the global variables according to a static analysis method to determine whether there are potential anomalies in the global variables; If yes, determining that the second verification result is failed; If not, determine that the second verification result is verification passed.

7. The vehicle software integration method according to claim 1, characterized in that: After the step of compiling and integrating the second interface description file according to the configured compilation environment information, the method further includes: Perform integration testing on the compiled and integrated vehicle software to obtain test results; The compiled and integrated vehicle software is optimized according to the test results.

8. A vehicle-mounted software integration device, characterized in that: The device comprises: A generating module, used to generate a first interface description file of a software component of the vehicle-mounted software; A verification module, used to verify the first interface description file and obtain a verification result; An adjustment module, configured to adjust the first interface description file according to the verification result to obtain a second interface description file; Configuration module, used to configure compilation environment information; An integration module is used to compile and integrate the second interface description file according to the configured compilation environment information.

9. An electronic device, characterized in that: The electronic device comprises a memory and a processor, wherein the memory is used to store a computer program, and the processor runs the computer program to enable the electronic device to execute the in-vehicle software integration method according to any one of claims 1 to 7.

10. A storage medium, characterized in that: It stores a computer program, which, when executed by a processor, implements the vehicle-mounted software integration method as described in any one of claims 1 to 7.

Images