Software integration method and software management system of power domain controller

Abstract

The invention provides a software integration method and a software management system of a power domain controller, and belongs to the field of automobiles, the method comprises the following steps: generating an ARXML file based on a variable data type and a system transfer function interface defined in a software architecture; based on the ARXML file, generating a code file of the basic software; based on the ARXML file, a code file of the application software is generated, and the code file of the application software is matched with the software interface described by the ARXML file; based on the ARXML file, a code file of a middle layer is generated, the middle layer is used for connecting the basic software and the application software, and the code file of the middle layer is matched with the software interface described by the ARXML file; and performing integrated compiling on the code file of the basic software, the code file of the middle layer and the code file of the application software to obtain an executable file. The software integration method and device can be compatible with various modes for software development, rapid integration of the software is facilitated, and the software integration efficiency is improved.

Description

Technical Field

[0001] The present application relates to the automotive field, and in particular to a software integration method and a software management system for a power domain controller. Background Art

[0002] The power domain controller is an important component of the automotive electronic and electrical architecture, and is responsible for unified control of the vehicle's power system.

[0003] In the related technology, the basic software and application software in the power domain controller are directly connected, and the basic software and application software are strongly coupled and not portable. Therefore, it is difficult for the development of application software to be compatible with multiple methods, resulting in a long R&D cycle, high R&D cost and low efficiency in the software integration process of the power domain controller. Summary of the invention

[0004] The embodiment of the present application provides a software integration method and software management system for a power domain controller, which is compatible with multiple ways of software development, is conducive to rapid software integration, and improves the efficiency of software integration. The technical solution is as follows:

[0005] In one aspect, a software integration method for a power domain controller is provided, the method comprising:

[0006] Generate an ARXML file based on variable data types and system transfer function interfaces defined in the software architecture, wherein the ARXML file is used to describe the software interface;

[0007] Based on the ARXML file, a code file of basic software is generated, wherein the code file of the basic software is adapted to the software interface described in the ARXML file;

[0008] Based on the ARXML file, a code file of the application software is generated, wherein the code file of the application software is adapted to the software interface described in the ARXML file;

[0009] Based on the ARXML file, a code file of an intermediate layer is generated, wherein the intermediate layer is used to connect the basic software and the application software, and the code file of the intermediate layer is adapted to the software interface described in the ARXML file;

[0010] The code files of the basic software, the code files of the intermediate layer and the code files of the application software are integrated and compiled to obtain an executable file, and the executable file is used to be executed by the power domain controller.

[0011] In a possible implementation, generating a code file of basic software based on the ARXML file includes:

[0012] Based on the ARXML file and the hardware interface information of the power domain controller, a code file of the basic software is generated, and the code file of the basic software is adapted to the software interface described by the ARXML file and to the hardware interface described by the hardware interface information.

[0013] In a possible implementation, the application software includes a plurality of software components; and generating a code file of the application software based on the ARXML file includes:

[0014] Sending the ARXML file to multiple terminals, the terminals are used to use any software development tool to generate a code file of at least one software component of the application software based on the ARXML file, and return the generated code file of the at least one software component, and different terminals are used to generate code files of different software components;

[0015] Receive code files of different software components sent by multiple terminals.

[0016] In one possible implementation, the application software includes at least one of a vehicle control system software component, an electric drive control system software component, a battery management system software component, a charging system software component, a DC conversion system software component, a thermal management control system software component, or a charging conversion system software component.

[0017] On the other hand, a software integration device for a power domain controller is provided, the device comprising:

[0018] A first generating module is used to generate an ARXML file based on the variable data type and the system transfer function interface defined in the software architecture, wherein the ARXML file is used to describe the software interface;

[0019] A second generating module is used to generate a code file of basic software based on the ARXML file, wherein the code file of the basic software is adapted to the software interface described in the ARXML file;

[0020] A third generating module is used to generate a code file of the application software based on the ARXML file, wherein the code file of the application software is adapted to the software interface described in the ARXML file;

[0021] A fourth generating module, configured to generate a code file of an intermediate layer based on the ARXML file, wherein the intermediate layer is used to connect the basic software and the application software, and the code file of the intermediate layer is adapted to the software interface described in the ARXML file;

[0022] The compiling module is used to integrate and compile the code files of the basic software, the code files of the intermediate layer and the code files of the application software to obtain an executable file, and the executable file is used to be executed by the power domain controller.

[0023] In a possible implementation, the second generating module is used to:

[0024] Based on the ARXML file and the hardware interface information of the power domain controller, a code file of the basic software is generated, and the code file of the basic software is adapted to the software interface described by the ARXML file and to the hardware interface described by the hardware interface information.

[0025] In a possible implementation, the application software includes multiple software components; the third generating module is used to:

[0026] Sending the ARXML file to multiple terminals, the terminals are used to use any software development tool to generate a code file of at least one software component of the application software based on the ARXML file, and return the generated code file of the at least one software component, and different terminals are used to generate code files of different software components;

[0027] Receive code files of different software components sent by multiple terminals.

[0028] In one possible implementation, the application software includes at least one of a vehicle control system software component, an electric drive control system software component, a battery management system software component, a charging system software component, a DC conversion system software component, a thermal management control system software component, or a charging conversion system software component.

[0029] On the other hand, a software management system is provided, the software management system comprising an integrated compilation management module, a code management module, a calibration data management module and a software version management module;

[0030] The code management module is used to store code files of basic software, code files of application software and code files of intermediate layers, wherein the code files of basic software, code files of application software and intermediate layers are generated based on the same ARXML file and are all adapted to the software interface described in the ARXML file;

[0031] The integrated compilation management module is used to integrate and compile the code files of the basic software, the code files of the intermediate layer and the code files of the application software to obtain an executable file;

[0032] The calibration data management module is used to manage the calibration data of the basic software and the calibration data of the application software;

[0033] The software version management module is used to manage the version of the basic software, the version of the intermediate layer and the version of the application software.

[0034] On the other hand, an electronic device is provided, characterized in that the electronic device includes a processor and a memory, the memory stores at least one computer program, and the at least one computer program is loaded and executed by the processor to implement the operations performed by the software integration method of the power domain controller as described in the above aspects.

[0035] The beneficial effects of the technical solution provided by the embodiments of the present application include at least:

[0036] The embodiment of the present application provides a software integration method and software management system for a power domain controller, which adds an intermediate layer between the basic software and the application software of the power domain controller, and adopts an ARXML file as a descriptive file of the software interface of the intermediate layer. Therefore, the code file of the application software and the code file of the basic software are generated based on the same ARXML file, so that the application software and the basic software can call the software interface of the intermediate layer, so that it can be compatible with multiple ways of software development, and it is only necessary to ensure that the software is compatible with the ARXML file. This is conducive to the use of different development tools to develop different software separately, and the software is quickly integrated, which improves the efficiency of software integration. BRIEF DESCRIPTION OF THE DRAWINGS

[0037] In order to more clearly illustrate the technical solutions in the embodiments of the present application, the drawings required for use in the description of the embodiments will be briefly introduced below. Obviously, the drawings described below are only some embodiments of the present application. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying any creative work.

[0038] Figure 1 It is a schematic diagram of an implementation environment provided by an embodiment of the present application;

[0039] Figure 2 It is a flow chart of a software integration method of a power domain controller provided in an embodiment of the present application;

[0040] Figure 3 It is a schematic diagram of a software layered architecture of a power domain controller provided in an embodiment of the present application;

[0041] Figure 4 is a schematic diagram of a multi-core control chip integrating multiple application software provided in an embodiment of the present application;

[0042] Figure 5It is a structural diagram of a software integration device of a power domain controller provided in an embodiment of the present application;

[0043] Figure 6 It is a structural diagram of a software integration system provided in an embodiment of the present application;

[0044] Figure 7 It is a structural schematic diagram of an electronic device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0045] In order to make the objectives, technical solutions and advantages of the present application clearer, the implementation methods of the present application will be further described in detail below with reference to the accompanying drawings.

[0046] The terms "first", "second", "third" and "fourth" etc. in the specification and claims of the present application and the drawings are used to distinguish different objects, rather than to describe a specific order. In addition, the terms "including" and "having" and any variations thereof are intended to cover non-exclusive inclusions. For example, a process, method, system, product or device that includes a series of steps or units is not limited to the listed steps or units, but optionally includes steps or units that are not listed, or optionally includes other steps or units inherent to these processes, methods, products or devices.

[0047] The software integration method of the power domain controller provided in the embodiment of the present application is executed by an electronic device. Optionally, the electronic device is a server, which can be an independent physical server, or a server cluster or distributed system composed of multiple physical servers, or a cloud server that provides basic cloud computing services such as cloud services, cloud databases, cloud computing, cloud functions, cloud storage, network services, cloud communications, middleware services, domain name services, security services, CDN (Content Delivery Network), and big data and artificial intelligence platforms. Server. Optionally, the electronic device is a terminal, which can be a smart phone, a tablet computer, a laptop computer, a desktop computer, a vehicle-mounted terminal, etc., but is not limited to this. The terminal and the server can be directly or indirectly connected via wired or wireless communication, and this application is not limited here.

[0048] Figure 1 is a schematic diagram of an implementation environment provided by an embodiment of the present application. Figure 1, the implementation environment includes a terminal 101 and a server 102. The terminal 101 and the server 102 are connected via a wireless or wired network. In the embodiment of the present application, the server 102 sends an ARXML file to the terminal 101, and the terminal 101 can generate a code file of the basic software, a code file of the application software, or a code file of the intermediate layer based on the ARXML file, and upload the generated code file to the server 102. The server 102 integrates and compiles the code file of the basic software, the code file of the intermediate layer, and the code file of the application software to obtain an executable file executed by the power domain controller.

[0049] Figure 2 is a flowchart of a software integration method for a power domain controller provided in an embodiment of the present application, see Figure 2 , the method comprising:

[0050] 201. Generate an ARXML file based on the variable data type and system transfer function interface defined in the software architecture. The ARXML file is used to describe the software interface.

[0051] The software architecture may be AUTOSAR (Automotive Open System Architecture). AUTOSAR is a general architecture for automotive controller software. The AUTOSAR architecture can be divided from the bottom layer to the application layer into: Microcontroller Abstraction Layer, Basic Software Layer, Runtime Environment (RTE) and Application Software Layer.

[0052] The software architecture defines a unified variable data type and a system transfer function interface. According to the variable data type and the system transfer function interface defined in the software architecture, a standard ARXML file can be generated.

[0053] Among them, ARXML file refers to AUTOSAR XML, which is an XML format file defined in AUTOSAR. ARXML file is used to describe the software and hardware architecture of automotive electronic systems, and contains various information of automotive electronic systems, such as ECU (Electronic Control Unit) definition and configuration, signal and parameter definition, software component and interface definition, etc. ARXML file provides a unified and scalable way to describe automotive electronic systems so that system information can be shared and processed in different development environments.

[0054] 202. Generate a code file of the basic software based on the ARXML file, and the code file of the basic software is adapted to the software interface described in the ARXML file.

[0055] After the ARXML file is generated, the software interface function in the ARXML file is identified by software or script, and the code file of the basic software adapted to the ARXML file is generated based on the identified software interface function, so that the code file of the basic software is adapted to the software interface described in the ARXML file.

[0056] In the embodiment of the present application, the basic software is the basic software of the power domain controller. The basic software is a standard software layer defined in AUTOSAR, and the basic software is used to provide services for application software. The basic software does not actually complete specific functions such as ACC (Adaptive Cruise Control) and EBA (Electronic BrakeAssist), but is responsible for managing the underlying functions such as hardware drivers, memory management, and communications.

[0057] In one possible implementation, a code file of basic software is generated based on the ARXML file and the hardware interface information of the power domain controller, and the code file of the basic software is adapted to the software interface described in the ARXML file and to the hardware interface described in the hardware interface information.

[0058] Among them, the hardware interface information of the power domain controller is obtained based on the hardware electrical schematic diagram, and the code file of the basic software is adapted not only to the software interface described by the ARXML file, but also to the hardware interface described by the hardware interface information of the power domain controller.

[0059] In one possible implementation, the executor of the software integration method of the power domain controller is a server. The server sends an ARXML file to a terminal. The terminal uses any software development tool to generate a code file of the basic software based on the ARXML file and returns the generated code file of the basic software. The server receives the code file of the basic software sent by the terminal.

[0060] 203. Generate a code file of the application software based on the ARXML file, and the code file of the application software is adapted to the software interface described in the ARXML file.

[0061] After the ARXML file is generated, the software interface function in the ARXML file is identified by software or script, and a code file of the application software adapted to the ARXML file is generated based on the identified software interface function, so that the code file of the application software is adapted to the software interface described in the ARXML file.

[0062] In the embodiment of the present application, the application software is the application software of the power domain controller. The application software is composed of multiple interactive software components (SWC), which are modules that encapsulate some automotive electronic functions and are the basis for realizing various specific functions, such as power control, driving assistance system and other functions.

[0063] The power domain controller is an important part of the automotive electrical and electronic architecture, responsible for unified control of the vehicle's power system. The power domain controller is used to coordinate and optimize the functions of various subsystems related to the vehicle's powertrain, including the engine, gearbox, motor, battery management system, and braking system.

[0064] In a possible implementation, the execution subject of the software integration method of the power domain controller is a server, and the application software includes multiple software components. The server sends an ARXML file to multiple terminals, and the terminals are used to use any software development tool to generate a code file of at least one software component of the application software based on the ARXML file, and return the generated code file of the at least one software component, and different terminals are used to generate code files of different software components.

[0065] In the embodiment of the present application, the software integration process of the power domain controller adopts centralized online compilation and management by the server. Different terminals can be responsible for generating code files of some software components in the application software. All terminals upload the code files of the software components they generate to the server. The server then centrally manages and compiles multiple software components, which is beneficial to improving the efficiency of software compilation and integration and the security of software code files.

[0066] In one possible implementation, the application software includes at least one of a vehicle control system software component, an electric drive control system software component, a battery management system software component, a charging system software component, a DC conversion system software component, a thermal management control system software component, or a charging conversion system software component.

[0067] Among them, the vehicle control unit (VCU) software component is used to realize the functions of high-voltage power management, portable start, vehicle fault management, gear management, charging management, driving mode, energy recovery, etc. Portable start includes keyless entry start, keyless start, remote start, etc. Driving modes include normal mode, economic mode, sports mode, snow mode, off-road mode, comfort mode, custom mode, etc.

[0068] Among them, the electric drive control system (MCU, Microcontroller Unit) software component is used to realize high-voltage power management, fault diagnosis, drive management and other functions.

[0069] Among them, the battery management system (BMU, Battery Management Unit) software component is used to implement power management, energy management, thermal management, remote control and other functions.

[0070] Among them, the charging system (OBC, On-Board Charger) software component is used to implement functions such as charging management, discharging management, and power on and off management.

[0071] Among them, the DC-DC (DC-to-DC converter) software component is used to implement functions such as power on and off management, remote control management, and discharge management.

[0072] Among them, the thermal management control system (ECC, Energy Control Center) software component is used to realize functions such as vehicle cooling needs management, vehicle energy management, cooling pump, expansion valve, fan, water pump and other accessory drive management.

[0073] Among them, the charging conversion system (EVCC, Electric Vehicle Communication Controller) software component is used to realize functions such as conversion between European and American standard charging protocols.

[0074] In the embodiment of the present application, the power domain controller can deeply integrate the software functions of each distributed controller of the power system, including but not limited to the above-mentioned vehicle control system software components, electric drive control system software components, battery management system software components, charging system software components, DC conversion system software components, thermal management control system software components and charging conversion system software components, replacing the distributed control design architecture, realizing the integrated architecture of the power domain controller, and reducing the vehicle production cost and software development cost.

[0075] In addition, the above-mentioned power domain controller includes software functions of multiple distributed controllers, and the corresponding software functions are developed according to the software interface defined in the AEXML file. The development tools and software versions of each software function can be the same or different, which solves the compatibility problem and improves the convenience of software integration.

[0076] 204. Based on the ARXML file, generate a middle layer code file, the middle layer is used to connect the basic software and the application software, and the middle layer code file is adapted to the software interface described in the ARXML file.

[0077] In the embodiment of the present application, an intermediate layer code file is generated according to the ARXML file, and the intermediate layer may be a Run Time Environment (RTE). RTE is set as an intermediate layer between the application software and the basic software, and the application software and the basic software communicate and exchange data through RTE.

[0078] Among them, RTE is a specific implementation of the AUTOSAR virtual function bus (VFB) of the ECU (Electronic Control Unit). It encapsulates the communication and services of the basic software and provides a standardized interface for the application software components, so that the application software can call the services of the basic software through the interface to achieve seamless communication between software components.

[0079] 205. Integrate and compile the code files of the basic software, the code files of the intermediate layer, and the code files of the application software to obtain an executable file, and the executable file is used to be executed by the power domain controller.

[0080] By building a software integration environment, the code files of the basic software, the middle-layer code files and the application software are integrated and compiled with the help of a software compiler to finally generate an executable file.

[0081] In the embodiment of the present application, the ARXML file is a unified standard file of the AUTOSAR architecture. The intermediate layer generated by the ARXML file is used to connect the application software and the basic software, thereby realizing the decoupling of the application software and the basic software. The modifications between the application software and the basic software will not directly affect each other. Therefore, when the basic software or the application software needs to be modified later, only the intermediate layer needs to be maintained.

[0082] Figure 3 is a schematic diagram of a software layered architecture of a power domain controller provided in an embodiment of the present application, such as Figure 3 As shown in the figure, the software architecture of the power domain controller of new energy electric vehicles includes application software (ASW), middle layer (such as RTE) and basic software (BSW). The middle layer connects the application layer and the basic software, and the middle layer is used to adapt each software component in the application software. Among them, the ARXML file is used as a descriptive file of all interfaces of the middle layer for interface description.

[0083] like Figure 3 As shown, the application software is divided into multiple software components (SWC, Application Software) according to the functional modules that need to be implemented. Figure 3Only four are taken as examples. Each software component belongs to the functional software code of the distributed architecture controller. Therefore, during development, the application software can use different development tools to develop different software components.

[0084] like Figure 3 As shown, the middle layer develops and releases ARXML files to match software components of different development tools, and identifies the interface functions in the ARXML files to develop the code files of each software component. This ensures that the code files of each software component and the ARXML files released by the middle layer are always synchronized, preventing software redevelopment and repeated testing due to software incompatibility and mismatch.

[0085] Figure 4 is a schematic diagram of a multi-core control chip integrating multiple application software provided by an embodiment of the present application. The power domain controller allocates software functions according to the cores of the multi-core control chip. For example, the multi-core control chip is a six-core control chip. Figure 4 As shown, the distribution of different software functions is as follows.

[0086] Core 0 is mainly used to implement the VCU control algorithm module and the basic software module of the entire system, including signal acquisition, drive control, communication module, diagnosis module, complex drive module, calibration module, VCU application software algorithm module, etc. Among them, Core 0 is divided into two OS-Applications (system applications), namely trusted OS applications (Trusted OSApplication) and untrusted OS applications (Non-Trusted OS Application). Untrusted OS applications are used for non-functional safety-related task management, and trusted OS applications are used for functional safety-related task management.

[0087] Core1 is mainly used to implement the BMU control algorithm module, complex drivers related to BMU control, and related basic software modules. Core1 is divided into two OS applications, namely trusted OS applications and untrusted OS applications. Untrusted OS applications are used for non-functional safety-related task management, and trusted OS applications are used for functional safety-related task management.

[0088] Core 2 is mainly used to implement the MCU's motor control algorithm module, complex drivers related to MCU control, and related basic software modules. Core 2 is divided into two OS applications, namely trusted OS applications and untrusted OS applications. Untrusted OS applications are used for non-functional safety-related task management, and trusted OS applications are used for functional safety-related task management.

[0089] Core 3 is mainly used to implement the control algorithm modules of OBC and DCDC, complex drivers related to OBC and DCDC control, and related basic software modules. Core 3 will be divided into two OS applications, namely trusted OS applications and untrusted OS applications. Untrusted OS applications are used for non-functional safety-related task management, and trusted OS applications are used for functional safety-related task management.

[0090] Core 4 is mainly used to implement the ECC control algorithm module, complex drivers related to ECC control, and related basic software modules.

[0091] Core 5 is mainly used to implement the EVCC control algorithm module, complex drivers related to EVCC control, and related basic software modules.

[0092] The embodiment of the present application provides a software integration method for a power domain controller, which adds an intermediate layer between the basic software and the application software of the power domain controller, and adopts an ARXML file as a descriptive file of the software interface of the intermediate layer. Therefore, the code file of the application software and the code file of the basic software are generated based on the same ARXML file, so that the application software and the basic software can call the software interface of the intermediate layer, so that it can be compatible with multiple ways of software development, and it is only necessary to ensure that the software is compatible with the ARXML file. This is conducive to the use of different development tools to develop different software separately, and the software is quickly integrated, which improves the efficiency of software integration.

[0093] Furthermore, since the embodiment of the present application connects the basic software and the application software through an intermediate layer, the basic software and the application software are not directly connected, thereby reducing the coupling between the basic software and the application software, and realizing the separation of the basic software and the application software. Modifications to each other will not directly affect the other. Therefore, when the basic software or the application software needs to be modified at a later stage, only the intermediate layer needs to be maintained.

[0094] Furthermore, the functional software codes of each application layer are adapted through the intermediate layer. Therefore, the integrated distribution of the power domain controller software provided by the present invention can be compatible with multiple application layer software codes developed by multiple people through various development forms, effectively solving the problem that application layer software developed by multiple people and across platforms is difficult to quickly integrate, and can also effectively reduce the company's investment in application layer software development tool costs. At the same time, it can also provide utilization of existing mature functional software, realize software and hardware separation, reduce the risk of re-development of core software modules, and improve software development efficiency.

[0095] In addition, by standardizing the software interfaces of embedded software, application developers can develop software based on unified software interfaces, avoiding the problem of unclear software function implementation links, achieving software and hardware separation, reducing software coupling, and reducing software development costs, which is conducive to improving the utilization rate of software modular design and improving software development efficiency.

[0096] Figure 5 Schematic diagram of the structure of a software integration device of a power domain controller provided by an embodiment of the present application. Figure 5 , the device comprises:

[0097] The first generating module 501 is used to generate an ARXML file based on the variable data type and the system transfer function interface defined in the software architecture, and the ARXML file is used to describe the software interface;

[0098] The second generating module 502 is used to generate a code file of the basic software based on the ARXML file, and the code file of the basic software is adapted to the software interface described in the ARXML file;

[0099] The third generating module 503 is used to generate a code file of the application software based on the ARXML file, and the code file of the application software is adapted to the software interface described in the ARXML file;

[0100] A fourth generating module 504 is used to generate a code file of an intermediate layer based on the ARXML file, where the intermediate layer is used to connect the basic software and the application software, and the code file of the intermediate layer is adapted to the software interface described in the ARXML file;

[0101] The compiling module 505 is used to integrate and compile the code files of the basic software, the code files of the intermediate layer and the code files of the application software to obtain an executable file, and the executable file is used to be executed by the power domain controller.

[0102] The software integration device of the power domain controller provided in the embodiment of the present application adds an intermediate layer between the basic software and the application software of the power domain controller, and adopts an ARXML file as a descriptive file of the software interface of the intermediate layer. Therefore, by generating the code file of the application software and the code file of the basic software based on the same ARXML file, it can be ensured that the application software and the basic software can call the software interface of the intermediate layer, so that it can be compatible with multiple ways of software development, and it is only necessary to ensure that the software is adapted to the ARXML file. This is conducive to the use of different development tools to develop different software separately, and the software can be quickly integrated, thereby improving the efficiency of software integration.

[0103] Optionally, the second generating module 502 is used to:

[0104] Based on the ARXML file and the hardware interface information of the power domain controller, a code file of the basic software is generated. The code file of the basic software is adapted to the software interface described in the ARXML file and to the hardware interface described in the hardware interface information.

[0105] Optionally, the application software includes multiple software components; the third generation module 503 is used to:

[0106] Sending an ARXML file to multiple terminals, the terminals are used to use any software development tool to generate a code file of at least one software component of the application software based on the ARXML file, and return the generated code file of the at least one software component, and different terminals are used to generate code files of different software components;

[0107] Receive code files of different software components sent by multiple terminals.

[0108] Optionally, the application software includes at least one of a vehicle control system software component, an electric drive control system software component, a battery management system software component, a charging system software component, a DC conversion system software component, a thermal management control system software component or a charging conversion system software component.

[0109] It should be noted that the software integration device of the power domain controller provided in the above embodiment is only illustrated by the division of the above functional modules. In actual applications, the above functions can be assigned to different functional modules as needed, that is, the internal structure of the electronic device is divided into different functional modules to complete all or part of the functions described above. In addition, the software integration device of the power domain controller provided in the above embodiment and the software integration method embodiment of the power domain controller belong to the same concept. The specific implementation process is detailed in the method embodiment and will not be repeated here.

[0110] In some embodiments, the present application also provides a software management system. Figure 6 is a schematic diagram of a software management system provided in an embodiment of the present application, such as Figure 6 As shown, the software management system includes an integrated compilation management module, a code management module, a calibration data management module and a software version management module;

[0111] A code management module is used to store code files of basic software, code files of application software and code files of intermediate layers. The code files of basic software, code files of application software and intermediate layers are generated based on the same ARXML file and are all adapted to the software interface described in the ARXML file.

[0112] The integrated compilation management module is used to integrate and compile the code files of the basic software, the code files of the intermediate layer and the code files of the application software to obtain an executable file;

[0113] Calibration data management module, used to manage the calibration data of basic software and application software;

[0114] The software version management module is used to manage the versions of the basic software, the middle layer and the application software.

[0115] For example, Figure 6 As shown, the software integration compilation module includes functions such as Makefile file management and software compilation task management. The software integration compilation module performs software integration compilation according to the calibration data defined in the Makefile file. Optionally, the software integration compilation module includes a software compilation client and a software compilation server.

[0116] For example, Figure 6 As shown, the code management module stores code files of basic software, code files of application software and code files of the intermediate layer. The code files of the application software include code files of multiple software components in the application software, such as code files of software components such as vehicle control system software components, electric drive control system software components, battery management system software components, charging system software components, DC conversion system software components, thermal management control system software components or charging conversion system software components.

[0117] Optionally, the code management module creates a software management project for each vehicle model project, which includes the management of code files for the basic software, the middle-layer code files, and the application software code files. Since the update frequency of the basic software and the middle-layer is low, the code files of the basic software and the middle-layer are managed in a high-authority, small-scale manner, which makes the logic clearer and makes it easier to protect data security. Since the application software is updated frequently and has a large development scope, the application software is managed in a large-scale, multi-audit manner to more effectively improve development efficiency.

[0118] Optionally, accounts involved in software development have different permissions, and permissions on code files include read-only, read-write, read-write-delete, etc.

[0119] For example, Figure 6 As shown, the calibration data management module stores the calibration data of the basic software and the calibration data of the application software.

[0120] For example, Figure 6 As shown, the software version management module includes basic software version, middle-layer software version, application software version, software integration version and software release version.

[0121] For example, Figure 6As shown, the software management system includes a terminal and a server, and manages the software of the power domain controller in a combined manner of the terminal and the server.

[0122] The terminal establishes a communication connection with the server. In order to meet the data transmission between the terminal and the server, the terminal is installed with application software for realizing data transmission, such as SVN, GitLab, Jenkins, etc. The terminal is used to generate the code files of the basic software, the code files of the application software and the code files of the middle layer based on the ARXML file, upload the generated code files of the basic software, the code files of the application software and the code files of the middle layer to the server, and the code management module deployed in the server stores the code files of the basic software, the code files of the application software and the code files of the middle layer.

[0123] exist Figure 6 On this basis, the process of managing software based on the software management system is described below.

[0124] 1. The terminal downloads the initial code file of the software to be developed from the server through application software such as SVN, GitLab, Jenkins, etc. The initial code file refers to the code file of the initial version of the software. Among them, the software can be basic software, application software or middle layer.

[0125] 2. Based on the ARXML file, the terminal changes, adjusts and optimizes the initial code file to obtain the target code file, and uploads the tested target code file and the corresponding Makefile file to the server. The code management module deployed in the server stores the target code file of the software, and the software integrated compilation module deployed in the server stores the Makefile file.

[0126] 3. The software integration compilation module deployed in the server identifies the code files that need to be integrated and compiled according to the uploaded Makefile file, and integrates and compiles the code files that need to be integrated and compiled to obtain executable files.

[0127] 4. After the integrated compilation is completed, the server will feed back the integrated compilation results to the terminal. If the integrated compilation fails, the failure reason will be saved. If the integrated compilation is successful, the obtained executable file will be stored in the storage path specified in the Makefile file.

[0128] 5. If the integrated compilation is successful, the software integrated compilation module sends the executable file to the terminal within the software release range according to the software release range.

[0129] The software management system provided in the embodiment of the present application integrates functions such as compilation management, code management, calibration data management and software version management into the same software management system. Compared with distributed independent management of multiple software management systems, the embodiment of the present application is conducive to improving the software iteration efficiency and quality of the power domain controller.

[0130] In addition, since the software management system can manage the code files for developing full-link software, it can implement integrated management based on the account permissions and groups of developers. It has the function of software code file traceability. By viewing the update logs and integrated compilation logs of the code files, it can grasp the software development progress and software maturity in real time, greatly improving the software development efficiency.

[0131] In some embodiments, an electronic device is also provided, characterized in that the electronic device includes a processor and a memory, at least one computer program is stored in the memory, and the at least one computer program is loaded and executed by the processor to implement the operations performed by the software integration method of the power domain controller in the above-mentioned embodiment.

[0132] Figure 7 The electronic device includes a processor 701 and a memory 702 .

[0133] The processor 701 may include one or more processing cores, such as a 4-core processor, an 8-core processor, etc. The processor 701 may be implemented in at least one hardware form of DSP (Digital Signal Processing), FPGA (Field Programmable Gate Array), and PLA (Programmable Logic Array). The processor 701 may also include a main processor and a coprocessor. The main processor is a processor for processing data in an awake state, also known as a CPU (Central Processing Unit); the coprocessor is a low-power processor for processing data in a standby state. In some embodiments, the processor 701 may be integrated with a GPU (Graphics Processing Unit), which is responsible for rendering and drawing the content to be displayed on the display screen. In some embodiments, the processor 701 may also include an AI (Artificial Intelligence) processor, which is used to process computing operations related to machine learning.

[0134] The memory 702 may include one or more computer-readable storage media, which may be non-transitory. The memory 702 may also include a high-speed random access memory, and a non-volatile memory, such as one or more disk storage devices, flash memory storage devices. In some embodiments, the non-transitory computer-readable storage medium in the memory 702 is used to store at least one computer program, which is used to be possessed by the processor 701 to implement the software integration method of the power domain controller provided in the method embodiment of the present application.

[0135] Those skilled in the art will understand that Figure 7 The structure shown in the figure does not constitute a limitation on the electronic device, and may include more or less components than shown in the figure, or combine certain components, or adopt a different component arrangement.

[0136] An embodiment of the present application also provides a computer-readable storage medium, in which at least one program code is stored. The at least one program code is loaded and executed by a processor to implement the software integration method of the power domain controller as described in any of the above implementation methods.

[0137] It should be understood that all or part of the steps to implement the above embodiments can be implemented by software, hardware, firmware or any combination thereof. When implemented using software, it can be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions. The computer instructions can be stored in the above-mentioned computer readable storage medium.

[0138] That is, in some embodiments, a computer program product comprising instructions is also provided, which, when executed on a computer, enables the computer to execute the steps of the software integration method of the power domain controller described above.

[0139] It should be noted that the information (including but not limited to user device information, user personal information, etc.), data (including but not limited to data used for analysis, stored data, displayed data, etc.) and signals involved in the embodiments of the present application are all authorized by the user or fully authorized by all parties, and the collection, use and processing of relevant data need to comply with relevant laws, regulations and standards of relevant countries and regions.

[0140] The above are only optional embodiments of the present application and are not intended to limit the present application. 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.

Claims

1. A software integration method for a power domain controller, characterized in that: The method comprises: Generate an ARXML file based on variable data types and system transfer function interfaces defined in the software architecture, wherein the ARXML file is used to describe the software interface; Based on the ARXML file, a code file of basic software is generated, wherein the code file of the basic software is adapted to the software interface described in the ARXML file; Based on the ARXML file, a code file of the application software is generated, wherein the code file of the application software is adapted to the software interface described in the ARXML file; Based on the ARXML file, a code file of an intermediate layer is generated, wherein the intermediate layer is used to connect the basic software and the application software, and the code file of the intermediate layer is adapted to the software interface described in the ARXML file; The code files of the basic software, the code files of the intermediate layer and the code files of the application software are integrated and compiled to obtain an executable file, and the executable file is used to be executed by the power domain controller.

2. The software integration method according to claim 1, characterized in that: The generating of the code file of the basic software based on the ARXML file comprises: Based on the ARXML file and the hardware interface information of the power domain controller, a code file of the basic software is generated, and the code file of the basic software is adapted to the software interface described by the ARXML file and to the hardware interface described by the hardware interface information.

3. The software integration method according to claim 1, characterized in that: The application software includes a plurality of software components; the code file of the application software is generated based on the ARXML file, including: Sending the ARXML file to multiple terminals, the terminals are used to use any software development tool to generate a code file of at least one software component of the application software based on the ARXML file, and return the generated code file of the at least one software component, and different terminals are used to generate code files of different software components; Receive code files of different software components sent by multiple terminals.

4. The software integration method according to claim 1, characterized in that: The application software includes at least one of a vehicle control system software component, an electric drive control system software component, a battery management system software component, a charging system software component, a DC conversion system software component, a thermal management control system software component or a charging conversion system software component.

5. A software integration device for a power domain controller, characterized in that: The device comprises: A first generating module is used to generate an ARXML file based on the variable data type and the system transfer function interface defined in the software architecture, wherein the ARXML file is used to describe the software interface; A second generating module is used to generate a code file of basic software based on the ARXML file, wherein the code file of the basic software is adapted to the software interface described in the ARXML file; A third generating module is used to generate a code file of the application software based on the ARXML file, wherein the code file of the application software is adapted to the software interface described in the ARXML file; A fourth generating module, configured to generate a code file of an intermediate layer based on the ARXML file, wherein the intermediate layer is used to connect the basic software and the application software, and the code file of the intermediate layer is adapted to the software interface described in the ARXML file; The compiling module is used to integrate and compile the code files of the basic software, the code files of the intermediate layer and the code files of the application software to obtain an executable file, and the executable file is used to be executed by the power domain controller.

6. The software integration device according to claim 5, characterized in that: The second generating module is used for: Based on the ARXML file and the hardware interface information of the power domain controller, a code file of the basic software is generated, and the code file of the basic software is adapted to the software interface described by the ARXML file and to the hardware interface described by the hardware interface information.

7. The software integration device according to claim 5, characterized in that: The application software includes a plurality of software components; the third generating module is used to: Sending the ARXML file to multiple terminals, the terminals are used to use any software development tool to generate a code file of at least one software component of the application software based on the ARXML file, and return the generated code file of the at least one software component, and different terminals are used to generate code files of different software components; Receive code files of different software components sent by multiple terminals.

8. The software integration device according to claim 5, characterized in that: The application software includes at least one of a vehicle control system software component, an electric drive control system software component, a battery management system software component, a charging system software component, a DC conversion system software component, a thermal management control system software component or a charging conversion system software component.

9. A software management system, characterized in that: The software management system includes an integrated compilation management module, a code management module, a calibration data management module and a software version management module; The code management module is used to store code files of basic software, code files of application software and code files of intermediate layers, wherein the code files of basic software, code files of application software and intermediate layers are generated based on the same ARXML file and are all adapted to the software interface described in the ARXML file; The integrated compilation management module is used to integrate and compile the code files of the basic software, the code files of the intermediate layer and the code files of the application software to obtain an executable file; The calibration data management module is used to manage the calibration data of the basic software and the calibration data of the application software; The software version management module is used to manage the version of the basic software, the version of the intermediate layer and the version of the application software.

10. An electronic device, characterized in that: The electronic device includes a processor and a memory, wherein the memory stores at least one computer program, and the at least one computer program is loaded and executed by the processor to implement the operations performed by the software integration method for the power domain controller as described in any one of claims 1 to 4.

Images