Software assembly method and device, vehicle, storage medium and program product

Abstract

The invention relates to the technical field of vehicles, in particular to a software assembly method and device, a vehicle, a storage medium and a program product.The method comprises the steps that the vehicle type of a target vehicle is obtained; determining a target configuration file of the target vehicle according to the vehicle type; and assembling the electronic control unit software of the target vehicle based on the target configuration file which is a configuration file related to the vehicle type. Therefore, the problems that part of software cannot adapt to different vehicle types due to the difference of the vehicle types, the software needs to be recompiled to adapt to the vehicle, the software development and maintenance cost is high and the like in the related technology are solved.

Description

Technical Field

[0001] The present application relates to the field of vehicle technology, and in particular to a software assembly method, device, vehicle, storage medium and program product. Background Art

[0002] Existing solutions generally use the AUTOSAR (Automotive Open System ARchitecture) tool chain configuration to generate the underlying software on the ECU (Electronic Control Unit) and recompile the overall software to achieve adaptation to different vehicle EEAs (Electronic Electric Architecture).

[0003] However, there are the following problems: the underlying software related to communication diagnosis is not decoupled from the overall software, and the overall software needs to be recompiled and flashed to the ECU. This means that for different models, ECU suppliers need to maintain different software versions and software part numbers, which will cause additional development, maintenance and production-related workloads for Tier 1 (first-tier suppliers) and OEMs (Original Equipment Manufacturers). Summary of the invention

[0004] The present application provides a software assembly method, device, vehicle, storage medium and program product to solve the problems in the related art that some software cannot be adapted to different vehicle models due to the differences in vehicle models, and the software development and maintenance costs are high.

[0005] The first aspect of the present application provides a software assembly method, comprising the following steps: obtaining a model of a target vehicle; determining a target configuration file of the target vehicle according to the model; and assembling the electronic control unit software of the target vehicle based on the target configuration file, wherein the target configuration file is a configuration file related to the model.

[0006] Optionally, in an embodiment of the present application, determining a target configuration file of a target vehicle according to a vehicle model includes: acquiring a correspondence between the vehicle model and the target configuration file; and determining the target configuration file by searching for the correspondence according to the vehicle model.

[0007] Optionally, in one embodiment of the present application, obtaining the correspondence between the vehicle model and the target configuration file includes: obtaining software content related to the vehicle and the vehicle model; compiling the software content based on a preset format, and integrating the compiled software content with the calibration configuration file to obtain the target configuration file of the vehicle.

[0008] Optionally, in an embodiment of the present application, after determining the target configuration file of the target vehicle according to the vehicle model, the method further includes: obtaining a unified basic configuration file of the vehicle; and fusing the basic configuration file and the target configuration file to obtain a complete configuration file of the target vehicle.

[0009] Optionally, in one embodiment of the present application, assembling the electronic control unit software of the target vehicle based on the target configuration file includes: assembling the electronic control unit software of the target vehicle based on the complete configuration file.

[0010] Optionally, in one embodiment of the present application, the target configuration file also includes standardized configuration information of the underlying software northbound interface, wherein the north interface is used to provide a standardized communication interface between the electronic control unit of the target vehicle and the application layer.

[0011] The second aspect of the present application provides a software assembly device, including: an acquisition module, used to obtain the model of a target vehicle; a determination module, used to determine a target configuration file of the target vehicle according to the model; an assembly module, used to assemble the target vehicle electronic control unit software based on the target configuration file, wherein the target configuration file is a configuration file related to the model.

[0012] Optionally, in one embodiment of the present application, the determination module is further used to: obtain a correspondence between a vehicle model and a target configuration file; and determine the target configuration file by searching for the correspondence according to the vehicle model.

[0013] Optionally, in one embodiment of the present application, the determination module is further used to: obtain software content related to the vehicle and vehicle model; compile the software content based on a preset format, and merge the compiled software content with the calibration configuration file to obtain a target configuration file for the vehicle.

[0014] Optionally, in one embodiment of the present application, it further includes: a fusion module, which is used to obtain a unified basic configuration file of the vehicle after determining the target configuration file of the target vehicle according to the vehicle model; and fuse the basic configuration file and the target configuration file to obtain a complete configuration file of the target vehicle.

[0015] Optionally, in one embodiment of the present application, the assembly module is further used to: assemble the electronic control unit software of the target vehicle based on the complete configuration file.

[0016] Optionally, in one embodiment of the present application, the target configuration file also includes standardized configuration information of the underlying software northbound interface, wherein the northbound interface is used to provide a standardized communication interface between the electronic control unit of the target vehicle and the application layer.

[0017] A third aspect of the present application provides a vehicle, comprising: a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor executes the program to perform the software assembly method as described in the above embodiment.

[0018] The fourth aspect of the present application provides a computer-readable storage medium on which a computer program or instructions are stored. The computer program or instructions are executed by a processor to perform a software assembly method as shown.

[0019] The fifth aspect of the present application provides a computer program product, including a computer program or instructions. When the computer program or instructions are executed, the software assembly method as described in the above embodiment is implemented.

[0020] Therefore, this application has at least the following beneficial effects:

[0021] The embodiment of the present application can determine the target configuration file by the vehicle model, assemble the ECU software based on the target configuration file, ensure that the ECU software can adapt to the differences of different vehicle models, and because the target configuration file is only related to the vehicle model, the other parts of the software are unified content, so that the software version can be unified, and the needs of different vehicle models can be met at the same time, thereby reducing the subsequent software development cost and maintenance cost. Therefore, the technical problems in the related technology that some software cannot adapt to different vehicle models due to the differences in vehicle models, the software needs to be recompiled to adapt to the vehicle, and the software development and maintenance costs are high are solved.

[0022] Additional aspects and advantages of the present application will be given in part in the description below, and in part will become apparent from the description below, or will be learned through the practice of the present application. BRIEF DESCRIPTION OF THE DRAWINGS

[0023] The above and / or additional aspects and advantages of the present application will become apparent and easily understood from the following description of the embodiments in conjunction with the accompanying drawings, in which:

[0024] Figure 1 A flowchart of a software assembly method provided according to an embodiment of the present application;

[0025] Figure 2 A schematic diagram of an application scenario of software assembly provided according to an embodiment of the present application;

[0026] Figure 3 A schematic diagram of a unified software version provided according to an embodiment of the present application;

[0027] Figure 4 A schematic diagram of a northbound interface in a complete configuration file provided according to an embodiment of the present application;

[0028] Figure 5A schematic diagram of a northbound standard interface provided according to an embodiment of the present application;

[0029] Figure 6 Schematic diagram of automatic adaptation of SOC (System on Chip) to vehicle model according to an embodiment of the present application

[0030] Figure 7 This is an example diagram of a software assembly device provided according to an embodiment of the present application;

[0031] Figure 8 It is a schematic diagram of the structure of a vehicle provided according to an embodiment of the present application. DETAILED DESCRIPTION

[0032] Embodiments of the present application are described in detail below, and examples of the embodiments are shown in the accompanying drawings, wherein the same or similar reference numerals throughout represent the same or similar elements or elements having the same or similar functions. The embodiments described below with reference to the accompanying drawings are exemplary and are intended to be used to explain the present application, and should not be construed as limiting the present application.

[0033] The software assembly method, device, vehicle, storage medium and program product of the embodiment of the present application are described below with reference to the accompanying drawings. In view of the problem mentioned in the above background technology that for different vehicle models, ECU suppliers need to maintain different software versions and software part numbers, which will cause additional development and maintenance and production-related workload for Tier 1 and OEM, the present application provides a software update method, in which the target configuration file is determined by the vehicle model, and the ECU software is assembled based on the target configuration file to ensure that the ECU software can adapt to the differences between different vehicle models, and can achieve the unification of software versions, while meeting the needs of different vehicle models. As a result, the problems in the related technology that some software cannot be adapted to different vehicle models due to the differences in vehicle models, the software needs to be recompiled to adapt to the vehicle, and the software development and maintenance costs are high are solved.

[0034] Specifically, Figure 1 A flowchart of a software assembly method provided in an embodiment of the present application.

[0035] like Figure 1 As shown, the software assembly method includes the following steps:

[0036] In step S101, the model of the target vehicle is obtained.

[0037] The target vehicle may be a vehicle that needs to be updated or installed with software.

[0038] In step S102 , a target configuration file of the target vehicle is determined according to the vehicle model.

[0039] The target configuration file is a configuration file related to the vehicle model.

[0040] It is understandable that the embodiment of the present application can determine the target configuration file of the target vehicle according to the model of the target vehicle, so as to subsequently assemble the software based on the target configuration file.

[0041] In an embodiment of the present application, determining a target configuration file of a target vehicle according to a vehicle model includes: acquiring a correspondence between the vehicle model and the target configuration file; and determining the target configuration file by searching the correspondence according to the vehicle model.

[0042] The correspondence stores the relationship between the vehicle model and the configuration file.

[0043] It can be understood that the embodiment of the present application can determine the target configuration file of the target vehicle by searching the corresponding relationship based on the model of the target vehicle.

[0044] In an embodiment of the present application, obtaining the correspondence between the vehicle model and the target configuration file includes: obtaining software content related to the vehicle model; compiling the software content based on a preset format, and integrating the compiled software content with the calibration configuration file to obtain the target configuration file of the vehicle.

[0045] Among them, the preset format can be set according to the specific situation. For example, it can be compiled separately in the form of SoftwareCluster (a new feature released by AUTOSAR CP R20); the calibration configuration file is the original CAL.hex file related to the vehicle model.

[0046] It can be understood that the embodiment of the present application can obtain software content related to the vehicle model, and compile the part related to the vehicle model separately according to a preset format, and merge the compiled software content with the calibration configuration file to obtain the target configuration file of the vehicle.

[0047] In the embodiment of the present application, after determining the target configuration file of the target vehicle according to the vehicle model, the method further includes: obtaining a unified basic configuration file of the vehicle; and merging the basic configuration file and the target configuration file to obtain a complete configuration file of the target vehicle.

[0048] It can be understood that the embodiment of the present application can obtain a unified basic configuration file for the vehicle, merge the basic configuration file and the target configuration file to obtain a complete configuration file for the target vehicle, so as to achieve the uniformity of software versions between different vehicle models, but the configuration files for the vehicle models are different, ensuring that the complete configuration file contains both common parts and vehicle-specific parts.

[0049] In an embodiment of the present application, the target configuration file also includes standardized configuration information of the underlying software northbound interface, wherein the northbound interface is used to provide a standardized communication interface between the electronic control unit of the target vehicle and the application layer.

[0050] It can be understood that the target configuration file of the embodiment of the present application also includes standardized configuration information of the underlying software northbound interface. Through standardized northbound interface configuration information, the standardization of the communication interface between the ECU and the application layer is ensured, thereby achieving software interoperability and maintainability.

[0051] In step S103 , the electronic control unit software of the target vehicle is assembled based on the target configuration file.

[0052] It can be understood that the embodiments of the present application can assemble the ECU software of the target vehicle based on the target configuration file, thereby achieving the unification of the software version and meeting the needs of different vehicle models at the same time.

[0053] In an embodiment of the present application, assembling the electronic control unit software of the target vehicle based on the target configuration file includes: assembling the electronic control unit software of the target vehicle based on the complete configuration file.

[0054] It can be understood that the embodiment of the present application assembles the ECU software of the target vehicle based on a complete configuration file, which can not only ensure the uniformity of the current software version, but also meet the needs of different vehicle models.

[0055] The software assembly method of the present application is explained below through a specific embodiment, that is, it can adapt to the EEA difference of the whole vehicle, that is, the difference in vehicle models, taking the ECU of the vehicle AUTOSAR CP (AUTOSAR Classic Platform, which is part of the automotive open system architecture) and posix OS (operating system based on the POSIX (Portable Operating System Interface) standard) as an example.

[0056] Specific application scenarios such as Figure 2 As shown, Figure 2 The gray box in the middle is the part of the vehicle related to EEA. Each time a new model is adapted, the corresponding base software needs to be reconfigured and the overall software version needs to be recompiled. Some models only have CAN (Controller area network) bus, some have CAN and ETH (Ethernet) at the same time, or the specific signals may be different. For this reason, the embodiment of the present application uses a software assembly method to achieve the same set of main software, one version number, but different EEA configuration files, while meeting the needs of different models. The principle is as follows:

[0057] MCU (Microcontroller Unit) side: compile the EEA / model-related parts separately in the form of SoftwareCluster, and merge them with the original model-related calibration file CAL.hex into a hex file. When the production line is off, different CAL.hex files are flashed according to different models to achieve the unification of the main software version (the same APP.hex).

[0058] SOC side: The POSIX-based OS generally runs in the SOC, which can dynamically load processes. It only needs to load the corresponding vehicle configuration file through the EM (Execution Management) at startup and run the corresponding process in the communication protocol stack.

[0059] Specifically:

[0060] MCU side: Figure 3 As shown, assuming there are two versions of EEA V1 and V2 (different EEA architectures for two car models), under normal circumstances, due to the difference in the underlying software, two software versions Software V1 and V2 need to be maintained. The solution here is to compile the EEA / car model related parts separately in the form of SoftwareCluster (a new feature released by AUTOSAR CP R20), and merge them with the original car model related CAL.hex (calibration configuration file) into a hex file. When the production is off the line, different CAL.hex files are flashed according to different car models to achieve the unification of software versions (the same APP.hex).

[0061] It should be noted that the underlying software northbound interface needs to be platform-based. No matter how the underlying signal changes, the northbound interface can be kept stable through abstraction. Combined with the SoftwareCluster concept of AUTOSAR, this layer of interface is made into a binary connection and integrated into CAL.hex, such as Figure 4 shown.

[0062] Examples of northbound standard interfaces include Figure 5 As shown in the figure, different signals of EEA V1 and V2 need to be mapped to the same standardized northbound interface and provided to the application layer. This mapping relationship needs to be implemented in the underlying software.

[0063] SOC side: Figure 6As shown, the POSIX-based OS generally running in the SOC can dynamically load processes. It only needs to load the corresponding vehicle configuration file (.json file or other file format) through EM (Execution Management) when the system starts, and run the corresponding process in the communication protocol stack.

[0064] In summary, this application decouples the main software version from the vehicle model EEA by splitting the application layer and the bottom software into two binary files (MCU side) and by configuring adaptively (SOC side), saving the development and maintenance workload of Tier1 and OEM. The abstraction of the MCU bottom software northbound interface is combined with the concept of SoftwareCluster as a stable binary interface implementation method. The SOC side realizes automatic adaptation to different EEAs through pre-embedded codes and configuration files.

[0065] The premise here is that the underlying software northbound interface needs to be platform-based. No matter how the underlying signal changes, the northbound interface can be kept stable through abstraction. Combined with the SoftwareCluster concept of AUTOSAR, this layer of interface is made into a binary connection and integrated into CAL.hex.

[0066] According to the software assembly method proposed in the embodiment of the present application, the target configuration file can be determined by the vehicle model, and the ECU software can be assembled based on the target configuration file to ensure that the ECU software can adapt to the differences between different vehicle models. Since the target configuration file is only content related to the vehicle model, the other parts of the software are unified content, thereby achieving the unification of software versions and meeting the needs of different vehicle models, thereby reducing the subsequent software development cost and maintenance cost.

[0067] Next, the software assembly device proposed according to the embodiment of the present application is described with reference to the accompanying drawings.

[0068] Figure 7 It is a block diagram of a software assembly device according to an embodiment of the present application.

[0069] like Figure 7 As shown, the software assembly device 10 includes: an acquisition module 100 , a determination module 200 and an assembly module 300 .

[0070] Among them, the acquisition module 100 is used to obtain the model of the target vehicle; the determination module 200 is used to determine the target configuration file of the target vehicle according to the model; the assembly module 300 is used to assemble the target vehicle electronic control unit software based on the target configuration file, wherein the target configuration file is a configuration file related to the model.

[0071] In the embodiment of the present application, the determination module 200 is further used to: obtain the correspondence between the vehicle model and the target configuration file; and determine the target configuration file by searching the correspondence according to the vehicle model.

[0072] In the embodiment of the present application, the determination module 200 is further used to: obtain software content related to the vehicle and the vehicle model; compile the software content based on a preset format, and merge the compiled software content with the calibration configuration file to obtain a target configuration file for the vehicle.

[0073] In the embodiment of the present application, the device 10 of the embodiment of the present application further includes: a fusion module.

[0074] The fusion module is used to obtain a unified basic configuration file of the vehicle after determining the target configuration file of the target vehicle according to the vehicle model; and fuse the basic configuration file and the target configuration file to obtain a complete configuration file of the target vehicle.

[0075] In the embodiment of the present application, the assembly module 300 is further used to: assemble the electronic control unit software of the target vehicle based on the complete configuration file.

[0076] In an embodiment of the present application, the target configuration file also includes standardized configuration information of the underlying software northbound interface, wherein the northbound interface is used to provide a standardized communication interface between the electronic control unit of the target vehicle and the application layer.

[0077] It should be noted that the above explanations of the software assembly method embodiment are also applicable to the software assembly device of this embodiment, and will not be repeated here.

[0078] According to the software assembly device proposed in the embodiment of the present application, the target configuration file can be determined according to the vehicle model, and the ECU software can be assembled based on the target configuration file to ensure that the ECU software can adapt to the differences between different vehicle models. Moreover, since the target configuration file is only content related to the vehicle model, the other parts of the software are unified content, thereby achieving the unification of software versions and meeting the needs of different vehicle models at the same time, thereby reducing the subsequent software development cost and maintenance cost.

[0079] Figure 8 A schematic diagram of the structure of a vehicle provided in an embodiment of the present application. The vehicle may include:

[0080] A memory 801 , a processor 802 , and a computer program stored in the memory 801 and executable on the processor 802 .

[0081] When the processor 802 executes the program, the software assembly method provided in the above embodiment is implemented.

[0082] Furthermore, the vehicle also includes:

[0083] The communication interface 803 is used for communication between the memory 801 and the processor 802 .

[0084] The memory 801 is used to store computer programs that can be executed on the processor 802 .

[0085] The memory 801 may include a high-speed RAM memory, and may also include a non-volatile memory (non-volatile memory), such as at least one disk memory.

[0086] If the memory 801, the processor 802 and the communication interface 803 are implemented independently, the communication interface 803, the memory 801 and the processor 802 can be connected to each other through a bus and communicate with each other. The bus can be an Industry Standard Architecture (ISA) bus, a Peripheral Component Interconnect (PCI) bus or an Extended Industry Standard Architecture (EISA) bus. The bus can be divided into an address bus, a data bus, a control bus, etc. For ease of representation, Figure 8 Only one thick line is used in the diagram, but this does not mean that there is only one bus or only one type of bus.

[0087] Optionally, in a specific implementation, if the memory 801, the processor 802 and the communication interface 803 are integrated on a chip, the memory 801, the processor 802 and the communication interface 803 can communicate with each other through an internal interface.

[0088] The processor 802 may be a central processing unit (CPU), or an application specific integrated circuit (ASIC), or one or more integrated circuits configured to implement the embodiments of the present application.

[0089] An embodiment of the present application also provides a computer-readable storage medium on which a computer program or instruction is stored. When the computer program or instruction is executed by a processor, the above software assembly method is implemented.

[0090] The embodiment of the present application also provides a computer program product, including a computer program or instructions, which, when executed, implements the above software assembly method.

[0091] In the description of this specification, the description with reference to the terms "one embodiment", "some embodiments", "example", "specific example", or "some examples" etc. means that the specific features, structures, materials or characteristics described in conjunction with the embodiment or example are included in at least one embodiment or example of the present application. In this specification, the schematic representations of the above terms do not necessarily refer to the same embodiment or example. Moreover, the specific features, structures, materials or characteristics described may be combined in any one or N embodiments or examples in a suitable manner. In addition, those skilled in the art may combine and combine the different embodiments or examples described in this specification and the features of the different embodiments or examples, without contradiction.

[0092] In addition, the terms "first" and "second" are used for descriptive purposes only and should not be understood as indicating or implying relative importance or implicitly indicating the number of technical features indicated. Therefore, a feature defined as "first" or "second" may explicitly or implicitly include at least one of the features. In the description of this application, "N" means at least two, such as two, three, etc., unless otherwise clearly and specifically defined.

[0093] Any process or method description in a flowchart or otherwise described herein may be understood to represent a module, fragment or portion of code comprising one or N executable instructions for implementing the steps of a custom logical function or process, and the scope of the preferred embodiments of the present application includes alternative implementations in which functions may not be performed in the order shown or discussed, including performing functions in a substantially simultaneous manner or in reverse order depending on the functions involved, which should be understood by technicians in the technical field to which the embodiments of the present application belong.

[0094] It should be understood that the various parts of the present application can be implemented by hardware, software, firmware or a combination thereof. In the above embodiment, the N steps or methods can be implemented by software or firmware stored in a memory and executed by a suitable instruction execution system. For example, if implemented by hardware, as in another embodiment, it can be implemented by any one or a combination of multiple of the following technologies known in the art: a discrete logic circuit having a logic gate circuit for implementing a logic function for a data signal, a dedicated integrated circuit having a suitable combination of logic gate circuits, a programmable gate array (PGA), a field programmable gate array (FPGA), etc.

[0095] A person skilled in the art may understand that all or part of the steps in the method for implementing the above-mentioned embodiment may be completed by instructing related hardware through a program, and the program may be stored in a computer-readable storage medium, which, when executed, includes one or a combination of the steps of the method embodiment.

Claims

1. A software assembly method, characterized in that: The following steps are involved: Get the model of the target vehicle; determining a target configuration file of the target vehicle according to the vehicle model; The electronic control unit software of the target vehicle is assembled based on the target configuration file, wherein the target configuration file is a configuration file related to the vehicle model.

2. The software assembly method according to claim 1, characterized in that: The step of determining the target configuration file of the target vehicle according to the vehicle model includes: Obtaining a correspondence between the vehicle type and the target configuration file; The target configuration file is determined by searching the corresponding relationship according to the vehicle type.

3. The software assembly method according to claim 2, characterized in that: The obtaining of the correspondence between the vehicle type and the target configuration file includes: Obtain vehicle and model-related software content; The software content is compiled based on a preset format, and the compiled software content is merged with the calibration configuration file to obtain a target configuration file for the vehicle.

4. The software assembly method according to claim 1, characterized in that: After determining the target configuration file of the target vehicle according to the vehicle model, the method further includes: Obtaining a unified basic configuration file for the vehicle; The basic configuration file and the target configuration file are merged to obtain a complete configuration file of the target vehicle.

5. The software assembly method according to claim 4, characterized in that: The electronic control unit software of the target vehicle is assembled based on the target configuration file, comprising: The electronic control unit software of the target vehicle is assembled based on the complete configuration file.

6. The software assembly method according to any one of claims 1 to 5, characterized in that: The target configuration file also includes standardized configuration information of the underlying software northbound interface, wherein the northbound interface is used to provide a standardized communication interface between the electronic control unit of the target vehicle and the application layer.

7. A software assembly device, characterized in that: include: An acquisition module is used to acquire the model of the target vehicle; A determination module, used to determine a target configuration file of the target vehicle according to the vehicle model; An assembly module is used to assemble the target vehicle electronic control unit software based on the target configuration file, wherein the target configuration file is a configuration file related to the vehicle model.

8. A vehicle, characterized in that: include: A memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor executes the program to implement the software assembly method according to any one of claims 1 to 6.

9. A computer-readable storage medium having a computer program or instruction stored thereon, characterized in that: The computer program or instruction is executed by a processor to implement the software assembly method according to any one of claims 1 to 6.

10. A computer program product comprising a computer program or instructions, characterized in that When the computer program or instruction is executed, the software assembly method according to any one of claims 1 to 6 is implemented.

Images