Methods for generating programs, related equipment, and storage media for implementing vehicle software.

Abstract

This invention provides a method for generating vehicle software programs, related equipment, and a storage medium, relating to the field of software configuration technology. The method includes: obtaining a preset target node configuration file; parsing the target node configuration file to generate target node configuration class information for each configurable functional node based on its node attribute information and node hierarchy; obtaining preset basic function source code and node configuration resource files to determine the target node entity class information for each configurable functional node; and combining the target node configuration class information with the target node entity class information to obtain the configured functional node. Extracting node configuration information improves development efficiency, reduces repetitive code in node creation and association during tool development, effectively improves program running efficiency, and accelerates program execution speed.

Description

Technical Field

[0001] This invention relates to the field of software configuration technology, and specifically to a method for generating program for implementing vehicle software, related equipment, and storage medium. Background Technology

[0002] The Adaptive Platform AUTOSAR (AP AUTOSAR) is an open system architecture platform for adaptive vehicles, designed to effectively manage vehicle software development and improve its efficiency. Developing vehicle software using a unified configuration tool can improve efficiency and accuracy. However, in typical configuration tool programming, AP AUTOSAR provides numerous nodes, some containing a large number of attributes. Creating and associating these nodes requires extensive coding, leading to code redundancy in the configuration tool. Furthermore, the configuration tool's interface is closely tied to AP AUTOSAR node information, requiring the development of corresponding interface functions for each node, thus failing to reduce the coupling of the configuration tool software. Summary of the Invention

[0003] To address the aforementioned technical problems, the present invention provides a method, apparatus, electronic device, and storage medium for generating vehicle software, the solution of which is as follows:

[0004] Firstly, a method for generating a program to implement vehicle software is provided, comprising:

[0005] Obtain a preset target node configuration file; the target node configuration file includes node attribute information and node hierarchy relationship of each of the at least one configurable functional nodes; the program for implementing vehicle software includes the at least one configurable functional node;

[0006] The target node configuration file is parsed, and target node configuration class information for each functional node to be configured is generated based on the node attribute information and node hierarchy relationship of each functional node to be configured.

[0007] Obtain the preset basic function source code and node configuration resource file, and determine the target node entity class information of each functional node to be configured based on the preset basic function source code, the node configuration resource file and the target node configuration class information of each functional node to be configured;

[0008] The target node configuration class information and target node entity class information of each configurable functional node are combined to obtain the at least one configurable functional node; the at least one configurable functional node is used to be displayed in response to the first node display instruction.

[0009] Optionally, the step of parsing the target node configuration file and generating target node configuration class information for each functional node to be configured based on the node attribute information and node hierarchy relationship of each functional node to be configured includes:

[0010] The target node configuration file is parsed to obtain the node attribute information and node hierarchy relationship of each functional node to be configured;

[0011] Obtain a predefined node configuration class, and based on the predefined node configuration class, map the attribute information and node hierarchy relationship of each functional node to be configured into the target node configuration class information of each functional node to be configured.

[0012] Optionally, determining the target node entity class information for each functional node to be configured based on the preset basic function source code, the node configuration resource file, and the target node configuration class information for each functional node to be configured includes:

[0013] Based on the data model framework corresponding to the preset basic function source code, load the target node data corresponding to the target node configuration class information of each function node to be configured in the node configuration resource file;

[0014] The target node data is reflected to generate target node entity class information for each functional node to be configured; the target node entity class information corresponds to the entity information of the target node data.

[0015] Optionally, combining the target node configuration class information and the target node entity class information of each functional node to be configured to obtain the at least one functional node to be configured includes:

[0016] The target node configuration class information and target node entity class information of each functional node to be configured are combined using a first combination pattern to obtain first node information; the first node information is used to determine the entity information of each functional node to be configured.

[0017] The target node configuration class information and target node entity class information of each functional node to be configured are combined using a second combination pattern to obtain second node information; the second node information is used to determine the configuration information of each functional node to be configured.

[0018] The at least one functional node to be configured is obtained based on the first node information and the second node information.

[0019] Optionally, the method further includes:

[0020] In response to a node operation command for the target interface, an update request for the at least one functional node to be configured is obtained; the update request includes adding or deleting the at least one functional node to be configured.

[0021] Based on the update request, the at least one functional node to be configured is updated, and the updated at least one functional node to be configured is determined.

[0022] Upon receiving a user-triggered save command, the node data corresponding to at least one updated functional node to be configured is stored in the node configuration resource file.

[0023] In response to the second node display instruction, the updated at least one configurable functional node is displayed in the target interface based on the preset display method.

[0024] Optionally, the method further includes:

[0025] In response to the configuration command of the vehicle software module to be developed, the configuration data of the vehicle software module to be developed is obtained;

[0026] When the data to be configured corresponds to the target node configuration class information, copy the target node configuration class information corresponding to the data to be configured in the target node rule file to generate the vehicle software module configuration file to be developed.

[0027] The vehicle software module to be developed is generated based on the configuration file of the vehicle software module to be developed.

[0028] Secondly, a program generation apparatus for implementing vehicle software is provided, comprising:

[0029] The target node configuration file acquisition module is used to acquire a preset target node configuration file; the target node configuration file includes node attribute information and node hierarchy relationship of each of the at least one configurable functional nodes; the program for implementing vehicle software includes the at least one configurable functional node.

[0030] The parsing module is used to parse the target node configuration file and generate target node configuration class information for each functional node to be configured based on the node attribute information and node hierarchy relationship of each functional node to be configured.

[0031] The node entity class information determination module is used to obtain the preset basic function source code and node configuration resource file, and determine the target node entity class information of each functional node to be configured based on the preset basic function source code, the node configuration resource file and the target node configuration class information of each functional node to be configured.

[0032] The node combination module is used to combine the target node configuration class information and the target node entity class information of each functional node to be configured to obtain the at least one functional node to be configured; the at least one functional node to be configured is used to be displayed in response to the first node display instruction.

[0033] Optionally, the parsing module includes:

[0034] The parsing unit is used to parse the target node configuration file to obtain the node attribute information and node hierarchy relationship of each functional node to be configured;

[0035] The target node configuration class information determination unit is used to obtain a predefined node configuration class and, based on the predefined node configuration class, map the attribute information and node hierarchy relationship of each functional node to be configured into the target node configuration class information of each functional node to be configured.

[0036] Optionally, the node entity class information determination module includes:

[0037] The target node data acquisition unit is used to load the target node data corresponding to the target node configuration class information of each functional node to be configured in the node configuration resource file, based on the data model framework corresponding to the preset basic function source code.

[0038] The data reflection unit is used to reflect the target node data to generate target node entity class information for each functional node to be configured; the target node entity class information corresponds to the entity information of the target node data.

[0039] Optionally, the node combination module includes:

[0040] The first node information generation unit is used to combine the target node configuration class information and the target node entity class information of each functional node to be configured through a first combination mode to obtain the first node information; the first node information is used to determine the entity information of each functional node to be configured.

[0041] The second node information generation unit is used to combine the target node configuration class information and the target node entity class information of each functional node to be configured through a second combination mode to obtain the second node information; the second node information is used to determine the configuration information of each functional node to be configured.

[0042] The configuration node generation unit is used to obtain the at least one configuration node based on the first node information and the second node information.

[0043] Optionally, the device further includes:

[0044] The first display module is used to respond to the first node display instruction and display the at least one functional node to be configured in the target interface based on a preset display method; the preset display method includes a tree node structure and a tree table node structure.

[0045] Optionally, the device further includes:

[0046] The node update request acquisition module is used to acquire update requests for the at least one functional node to be configured in response to a node operation instruction for the target interface; the update request includes adding or deleting the at least one functional node to be configured.

[0047] The node update module is used to update the at least one functional node to be configured based on the update request, and determine the at least one functional node to be configured after the update.

[0048] The storage module is used to receive a save command triggered by the user and store the updated node data corresponding to at least one functional node to be configured in the node configuration resource file.

[0049] The second display module is used to respond to the second node display instruction and display the updated at least one configurable functional node in the target interface based on the preset display method.

[0050] Optionally, the device further includes:

[0051] The configuration data acquisition module is used to acquire the configuration data of the vehicle software module to be developed in response to the configuration command of the vehicle software module to be developed.

[0052] The software module configuration file generation module is used to copy the target node configuration class information corresponding to the data to be configured in the target node rule file when the data to be configured corresponds to the target node configuration class information, and generate the vehicle software module configuration file to be developed.

[0053] A software development module is used to generate the software module to be developed based on the configuration file of the software module to be developed.

[0054] Thirdly, an electronic device is provided, including a processor and a memory, wherein the memory stores at least one instruction or at least one program segment, the at least one instruction or the at least one program segment being loaded and executed by the processor to implement the above-described program generation method for implementing vehicle software.

[0055] Fourthly, a computer-readable storage medium is provided, wherein at least one instruction or at least one program is stored therein, the at least one instruction or the at least one program being loaded and executed by a processor to implement the above-described program generation method for implementing vehicle software.

[0056] Fifthly, a computer program product or computer program is provided, comprising computer instructions stored in a computer-readable storage medium, wherein a processor of a computer device reads the computer instructions from the computer-readable storage medium and executes the computer instructions, causing the computer device to perform the aforementioned program generation method for implementing vehicle software.

[0057] By adopting the above technical solution, the present invention has the following beneficial effects:

[0058] This invention pre-configures target node configuration files and writes the node configuration information (node ​​attribute information and node hierarchy relationship) of the functional nodes to be configured. Extracting the node configuration information improves development efficiency and reduces repetitive code creation and association of nodes during tool development. Utilizing ATUOSAR's pre-set basic function source code and node configuration resource files, it determines the target node entity class information for each functional node to be configured. Through design patterns, it combines the target node configuration class information and the target node entity class information to obtain the functional node to be configured, completing the configuration tool software program development. It only needs to be reloaded when the user clicks to refresh the page, effectively improving program efficiency and speed. With ATUOSAR version upgrades, only the node configuration information in the XML rule file needs to be changed for the configuration tool to be extended and upgraded.

[0059] Other features and advantages of the present invention will be described in detail in the following detailed description section. Attached Figure Description

[0060] To more clearly illustrate the technical solutions in the embodiments of the present invention, the accompanying drawings used in the description of the embodiments will be briefly introduced below. Obviously, the drawings described below are only some embodiments of the present invention, and the same reference numerals usually represent the same parts. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0061] Figure 1 A schematic diagram illustrating the working process of configuration tool software programs for existing adaptive vehicle open system architecture platforms.

[0062] Figure 2 A flowchart illustrating a method for generating vehicle software according to an embodiment of the present invention;

[0063] Figure 3 This is a schematic flowchart of an optional method for implementing a program generation method for vehicle software, provided in an embodiment of the present invention.

[0064] Figure 4 This is a schematic flowchart of an optional method for implementing a program generation method for vehicle software, provided in an embodiment of the present invention.

[0065] Figure 5 A schematic diagram of the structure of a program device for implementing vehicle software provided in an embodiment of the present invention;

[0066] Figure 6 A schematic diagram of a terminal structure for implementing a program generation method for vehicle software, provided for the implementation of this invention. Detailed Implementation

[0067] The technical solutions of the embodiments of the present invention will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of the present invention, and not all embodiments. All other embodiments obtained by those skilled in the art based on the embodiments of the present invention without creative effort are within the scope of protection of the present invention.

[0068] The term "an embodiment" or "embodiment" as used herein refers to a specific feature, structure, or characteristic that may be included in at least one implementation of the invention. In the description of the invention, it should be understood that the terms "upper," "lower," "top," "bottom," etc., indicating orientation or positional relationships based on the orientation or positional relationships shown in the accompanying drawings, are used only for the convenience of describing the invention and for simplifying the description, and do not indicate or imply that the device or element referred to must have a specific orientation, or be constructed and operated in a specific orientation, and therefore should not be construed as a limitation of the invention. Furthermore, the terms "first" and "second" are used for descriptive purposes only and should not be construed as indicating or implying relative importance or implicitly specifying the number of indicated technical features. Thus, a feature defined with "first" and "second" may explicitly or implicitly include one or more of that feature. Moreover, the terms "first," "second," etc., are used to distinguish similar objects and are not necessarily used to describe a specific order or sequence. It should be understood that such data can be interchanged where appropriate so that the embodiments of the invention described herein can be implemented in orders other than those illustrated or described herein.

[0069] With the rapid development of the automotive electronics industry, especially the application of intelligent connected vehicle technology, the scale and complexity of automotive control software development have increased rapidly. While some automotive companies have adopted their own defined methods or standards in the development of automotive electronic software, these cannot be universally applied across the automotive industry. The ever-evolving development of automotive control software necessitates a set of universal standards and development processes.

[0070] AUTOSAR (Automotive Open System Architecture) is a platform jointly established by major global automakers, automotive parts suppliers, and automotive electronics software companies. Its aim is to more effectively manage and improve the development efficiency of automotive electronic software. Currently, AUTOSAR is divided into ClassicPlatform AUTOSAR (CP AUTOSAR) and Adaptive Platform AUTOSAR (AP AUTOSAR). CP AUTOSAR has been widely used in traditional embedded automotive electronic software development, such as engine controllers, transmission controllers, and vehicle controllers. It focuses on automotive electronic software development with strict real-time and safety requirements, but cannot meet the development requirements of more complex and computationally demanding automotive electronic software. AP AUTOSAR addresses the shortcomings of CP AUTOSAR, focusing more on providing high-performance computing and intelligent connectivity functions.

[0071] AP AUTOSAR's functional modules include Service Communication Management (CM), Diagnostic Management (DM), Platform Health Management (PHM), and Platform Lifecycle Management (EM). The development of each module must adhere to the standards defined by AP AUTOSAR. However, developers are prone to errors when manually writing service interfaces, making it difficult to guarantee the accuracy and standardization of the code. Therefore, configuration tools for AP AUTOSAR have emerged. Developers can use these tools to generate code templates and target code files, enabling efficient implementation of each AUTOSAR functional module. (See reference...) Figure 1 The diagram illustrates the working process of the AP AUTOSAR configuration tool software.

[0072] In the typical design of AP AUTOSAR configuration tool software architecture, there are generally two approaches: The first approach is to develop independently of Artotop provided by ATUOSAR. Artotop is a foundational platform that provides common basic functions for configuration tools and can be used for the design and configuration of AUTOSAR-compliant systems and ECUs. The advantage of this approach is the ability to choose a development language, not being limited to Eclipse's RCP development. However, its disadvantage is the inability to utilize the node class information and modeling framework provided by AP ATUOSAR. A modeling framework must be built manually according to AP ATUOSAR's rules, a process that is often time-consuming and labor-intensive. Furthermore, with each AP ATUOSAR version upgrade, the modeling framework needs to be manually updated and supplemented, resulting in low efficiency. The second approach is to develop based on Artotop provided by ATUOSAR. While this saves time in building a modeling framework, existing configuration tool software frameworks lack proper utilization of the methods provided by Artotop. The design process involves a large number of repetitive node creations and associations. Some element nodes contain numerous attributes, requiring extensive coding to create and associate these nodes, resulting in redundant configuration tool software code. Furthermore, writing code for each node to implement corresponding interface functions leads to high code duplication, increased coupling, and difficulty in updating and expanding. When loading data, the configuration tool interface loads the entire dataset, often causing frequent lag and significantly reducing performance.

[0073] Therefore, this invention provides a low-redundancy, low-coupling configuration tool software program generation method, which maintains code simplicity and significantly improves the scalability and maintainability of the configuration tool, enabling efficient development of vehicle software. This method separates the user interface display from the AP AUTOSAR node data module, generating functional nodes through custom configuration. This greatly reduces the redundancy and coupling of the configuration tool software architecture, and allows for rapid tool upgrades and iterations with only minor changes to the configuration file during maintenance and upgrades, reducing development costs and improving overall work efficiency.

[0074] refer to Figure 2 The diagram illustrates a flowchart of a method for generating vehicle software according to an embodiment of the present invention. It should be noted that while this specification provides the operational steps described in the embodiments or flowcharts, more or fewer operational steps may be included based on conventional or non-inventive methods. The order of steps listed in the embodiments is merely one possible execution order among many and does not represent the only possible execution order. In actual system devices or products, the methods shown in the embodiments or drawings can be executed sequentially or in parallel (e.g., using parallel processors or multi-threaded processing environments). The method for generating vehicle software provided in this embodiment of the present invention includes:

[0075] S201, Obtain the preset target node configuration file; the target node configuration file includes node attribute information and node hierarchy relationship of each of the at least one configurable functional nodes; the program for implementing vehicle software includes the at least one configurable functional node, and vehicle software refers to software developed based on the AP ATUOSAR platform for controlling vehicles or realizing vehicle-to-everything (V2X) intelligent interconnection functions, such as traditional engine controllers, transmission controllers and vehicle controllers, as well as vehicle entertainment software, remote intelligent vehicle control software, etc.

[0076] Specifically, in this embodiment of the invention, the target node configuration file is an XML rule file. Developers write the target node configuration file based on the nodes of APATUOSAR. The target node configuration file is used to define the functional nodes to be configured. The functional nodes to be configured can also be modified by modifying the target node configuration file. In this embodiment of the invention, the target node configuration file contains the node attribute information and node hierarchy of the functional nodes to be configured. The node attribute information includes row attributes and column attributes. Row attributes include, but are not limited to, node name, node type, node description, number of columns to display, whether to display, maximum number of nodes to create, parent node name, List attribute of associated parent node, and associated parent node attribute, etc. Column attributes include, but are not limited to, icon, column name, data type, editing type, type validation rules, whether it can be nullable, associated data type, associated attribute, and associated List attribute, etc. The node hierarchy includes parent-child-sibling node relationships. The parent node, child node, and sibling node of a functional node to be configured can be determined based on the node hierarchy. For a node, its parent node is its superior node, its child node is its subordinate node, and its sibling node is its peer node. Sibling nodes share the same parent node. The functional nodes to be configured are used to implement the AP ATUOSAR configuration tool software architecture. This implementation extracts the configuration information of the functional nodes to be configured and writes target node configuration files to improve development efficiency and reduce repetitive code in node creation and association during tool development.

[0077] S202, the target node configuration file is parsed, and target node configuration class information for each functional node to be configured is generated based on the node attribute information and node hierarchy relationship of each functional node to be configured.

[0078] Specifically, based on the node information defined in the target node configuration file (node ​​attribute information and node hierarchy relationship of the functional nodes to be configured), the target node configuration class information is determined for subsequent node creation and display. The target node configuration class information includes the parent node configuration relationship for each functional node to be configured and the node's own attribute information; it also includes node operation and verification information, etc. The parent node configuration relationship includes the parent node name, the List attribute associated with the parent node, and the attributes associated with the parent node, etc. Node operations include adding and deleting functional nodes to be configured in subsequent processes; node verification refers to the process where, when a node needs to send data to another node, verification information needs to be sent to a buffer register for verification to confirm whether the data can be sent from one node to another. In one possible implementation, step S202 includes:

[0079] The target node configuration file is parsed to obtain the node attribute information and node hierarchy relationship of each functional node to be configured;

[0080] Obtain a predefined node configuration class, and based on the predefined node configuration class, map the attribute information and node hierarchy relationship of each functional node to be configured into the target node configuration class information of each functional node to be configured.

[0081] Specifically, a node configuration class is predefined. This class contains the configuration relationships of parent nodes and the node's own attribute information, as well as node operation and validation information. In other embodiments, the node configuration class can be further defined based on the node attribute information of the functional node to be configured, such as node name, node type, node description, number of columns to display, whether to display, maximum number of nodes to create, parent node name, List attribute associated with the parent node, associated parent node attribute, node icon, column name, data type, editing type, type validation rules, whether it can be nullable, associated data type, associated attribute, associated List attribute, etc. C++ code is written to parse the target node configuration file and generate a Document Object Model (DOM). The DOM is a platform- and language-independent application programming interface (API) that allows dynamic access to programs and scripts, updating their content, structure, and style of WWW documents (HTML and XML documents are defined through the specification section). Code is then written to complete the mapping between the DOM and attribute information. The C++ code is packaged into a callable C++ library. The main Java project uses an open-source local interface to call the C++ library file to generate the target node configuration class information for each functional node to be configured. This implementation method takes advantage of the difficulty in decompiling C++ code to achieve confidentiality of the core code and prevent it from being decompiled and cracked.

[0082] S203, obtain the preset basic function source code and node configuration resource file, and determine the target node entity class information of each functional node to be configured based on the preset basic function source code, the node configuration resource file and the target node configuration class information of each functional node to be configured.

[0083] In one possible implementation, step S203 includes:

[0084] Based on the data model framework corresponding to the preset basic function source code, load the target node data corresponding to the target node configuration class information of each function node to be configured in the node configuration resource file;

[0085] The target node data is reflected to generate target node entity class information for each functional node to be configured; the target node entity class information corresponds to the entity information of the target node data.

[0086] Specifically, the data framework model mentioned in this embodiment of the invention refers to the Artotop modeling framework. This embodiment of the invention is developed based on Artotop provided by ATUOSAR, and introduces the basic function source code of Artotop to provide common basic functions for configuration tool software, such as version control, change management, configuration status statistics, access control and security control, etc. Through the data model framework of Artotop and its loading mechanism, the node data resource information in the node configuration resource file is loaded and cached in memory. In this embodiment of the invention, the node configuration resource file is an ARXML file. The ARXML file is a configuration file saved in AUTOSAR XML format. As a general configuration file or database file, it plays a key role in data transmission and storage. ARXML mode is a special definition of XML data language. The ARXML in AUTOSAR stores the signal types, components and input / output port information in AUTOSAR. The node data resource information in the ARXML file, which is loaded as a node configuration resource file, is loaded on demand according to the custom XML rule file in the embodiment of step S201. That is, the target node data corresponding to the target node configuration class information of each functional node to be configured is loaded in the ARXML file. The target node data includes the node name abbreviation, ID, and other attributes of the functional node to be configured. The target node data in the obtained ARXML is used to generate the target node entity class information of each functional node to be configured through the Java reflection mechanism according to the XML rule file. The entity class corresponds one-to-one with the entity information of the target node data in the ARXML. The Java reflection mechanism means that for any class, all attributes and methods of the class can be known during program execution; for any object, any method and attribute of the object can be called. This ability to dynamically obtain information and dynamically call the methods of objects is called the reflection mechanism of the Java language. The above implementation method loads the target node data corresponding to the target node configuration class information of each functional node to be configured in the ARXML file on demand. The ARXML node data resource information only needs to be reloaded when the interface is refreshed, which can effectively improve the program running efficiency and speed up the program running speed. This is because after the node data resource information in the node configuration resource file is cached in memory at once, the target node data corresponding to the target node configuration class information of each functional node to be configured is maintained in memory when the user performs node update operations on the interface, such as adding a node. The node data resource information is only reloaded when the user refreshes the entire interface.

[0087] S204, combine the target node configuration class information and the target node entity class information of each functional node to be configured to obtain the at least one functional node to be configured; the at least one functional node to be configured is used to be displayed in response to the first node display instruction.

[0088] Specifically, in the process of combining target node configuration class information and target node entity class information, the entity information of the functional nodes to be configured in the tree node structure is constructed by combining the target node configuration class information with the composite pattern. For example, the parent-child node relationship in the tree node structure is represented. For node operations such as adding or deleting byte points, the content in the target node entity class information is loaded and displayed. The configuration information of the functional nodes to be configured in the tree table node structure is generated by combining the target node configuration class information with the factory method pattern. For example, the node attribute information defined in the node configuration corresponds to the number of columns in the table. In one possible implementation, step S204 includes:

[0089] The target node configuration class information and target node entity class information of each functional node to be configured are combined using a first combination pattern to obtain first node information; the first node information is used to determine the entity information of each functional node to be configured.

[0090] The target node configuration class information and target node entity class information of each functional node to be configured are combined using a second combination pattern to obtain second node information; the second node information is used to determine the configuration information of each functional node to be configured.

[0091] The at least one functional node to be configured is obtained based on the first node information and the second node information.

[0092] Specifically, in this embodiment of the invention, the first combination pattern is the Composite pattern, and the second combination pattern is the Factory Method pattern. The Composite pattern and the Factory Method pattern combine the target node configuration class information and the target node entity class information of each configurable functional node, corresponding to the first and second combination patterns. The Composite pattern composes objects into a tree structure to represent a part-whole hierarchical structure. It constructs the entity information of nodes in the tree node structure, including attributes such as the node's abbreviation and ID, the node's column attributes, and get and set methods for its child nodes. The Factory Method pattern provides an interface for creating objects in the parent class but allows subclasses to change the type of the object to be created. It combines the target node configuration class information with the Factory Method pattern to generate the configuration information of the configurable functional nodes in the tree table node structure. For example, the node attribute information defined in the node configuration corresponds to a certain number of columns in the table, which is used to match the node configuration class corresponding to the node when switching target interface nodes (described later). When different software modules contain the same nodes, the above implementation method only requires copying the node configuration information from the custom target node configuration file to complete the node configuration and page loading in the new software module without adding any code. This is because the variables in the generation and combination of target node configuration class information and target node entity class information are the node attribute information and node hierarchy relationship in the target node configuration file, as well as the node data resource information imported from the ARXML node configuration resource file. The subsequent display of the functional nodes to be configured only involves the node attribute information and node hierarchy relationship in the target node configuration file. Therefore, copying the node attribute information and node hierarchy relationship from the target node configuration file and placing them in different software modules can still display the same node effect. Furthermore, as the AP AUTOSAR version is upgraded, only the node configuration information in the target node configuration file needs to be changed for the tool to complete the expansion and upgrade.

[0093] refer to Figure 3 In one possible implementation, steps S301 to S304 are consistent with the aforementioned steps S201 to S204, wherein step S305 may include: in response to the first node display instruction, displaying the at least one functional node to be configured in the target interface based on a preset display method; the preset display method includes a tree node structure and a tree table node structure.

[0094] Specifically, the functional nodes to be configured obtained in the above steps are displayed and operated using the SWT model in Eclipse. Eclipse is an open-source, Java-based, extensible development platform. While Eclipse itself is just a framework platform, the support of numerous plugins makes it flexible. SWT (Standard Widget Toolkit) is a Java-based window component designed to provide access to efficient and portable user interface facilities, and to implement an operating system on top of them. In this embodiment, the display of the functional nodes to be configured includes two methods: a packageable tree node structure displayed on the left side of the interface, and an element tree table node structure displayed on the right side of the interface. Packageable nodes require information such as newly added child nodes and the maximum number of nodes created to be read from the tree node structure for right-click operations; element node information requires information such as newly added child nodes, its own node attributes, and column editing information to be read from the tree table node structure. The above implementation displays the functional nodes to be configured in two ways, allowing for intuitive operation on the target interface and providing an efficient way to create and display nodes. This is beneficial for the use and maintenance of the configuration tool software.

[0095] refer to Figure 4 In one possible implementation, the method further includes:

[0096] S401, in response to a node operation instruction for the target interface, obtain an update request for the at least one functional node to be configured; the update request includes adding or deleting the at least one functional node to be configured;

[0097] S402, based on the update request, update the at least one functional node to be configured, and determine the updated at least one functional node to be configured;

[0098] S403, receive the user-triggered save command, and store the node data corresponding to the updated at least one functional node to be configured into the node configuration resource file.

[0099] S404, in response to the second node display instruction, the updated at least one functional node to be configured is displayed in the target interface based on the preset display method.

[0100] Specifically, after the configuration tool software program is generated, the target interface displays the functional nodes to be configured. Users can update these nodes on the target interface, including adding or deleting nodes. Node entity class information is also updated synchronously. When a user performs a save operation, the system receives the user-triggered save command and saves the updated node data of the functional nodes to be configured to the node configuration resource file. In this embodiment, this is synchronized to an ARXML file, and the updated functional nodes are dynamically displayed on the target interface. This implementation reduces the coupling of the configuration tool software, effectively improves program efficiency, and speeds up program execution.

[0101] In one possible implementation, the method further includes:

[0102] In response to the configuration command of the vehicle software module to be developed, the configuration data of the vehicle software module to be developed is obtained;

[0103] When the data to be configured corresponds to the target node configuration class information, copy the target node configuration class information corresponding to the data to be configured in the target node rule file to generate the vehicle software module configuration file to be developed.

[0104] The vehicle software module to be developed is generated based on the configuration file of the vehicle software module to be developed.

[0105] This invention, through the above implementation methods, defines a custom XML rule file and writes the node configuration information (node ​​attribute information and node hierarchy relationship) for the functional nodes to be configured. This extracts the node configuration information to improve development efficiency and reduce repetitive code in node creation and association during tool development. It utilizes Artop provided by ATUOSAR to load ARXML node data resources on demand and combines target node configuration class information and target node entity class information using design patterns. This only requires reloading when the user refreshes the page, effectively improving program efficiency and speed. When different vehicle software modules contain the same nodes, only the node information in the XML rule file needs to be copied to complete the configuration and page loading of the nodes in the new module, without adding any program code. Furthermore, as the AP AUTOSAR version is upgraded, only the node configuration information in the XML rule file needs to be changed for the configuration tool to be extended and upgraded.

[0106] Corresponding to the above-described method for generating vehicle software, this embodiment of the invention also provides a device for generating vehicle software. Since the device for generating vehicle software provided in this embodiment corresponds to the method for generating vehicle software provided in the above-described embodiments, the implementation methods of the aforementioned method for generating vehicle software are also applicable to the device for generating vehicle software provided in this embodiment, and will not be repeated in this embodiment.

[0107] refer to Figure 5 The diagram shows a schematic representation of a program generation device for implementing vehicle software according to an embodiment of the present invention. This device has the function of implementing the program generation method for implementing vehicle software described in the above-described method embodiments. This function can be implemented by hardware or by hardware executing corresponding software. The device may include:

[0108] The target node configuration file acquisition module 510 is used to acquire a preset target node configuration file; the target node configuration file includes node attribute information and node hierarchy relationship of each of the at least one configurable functional nodes; the program for implementing vehicle software includes the at least one configurable functional node.

[0109] The parsing module 520 is used to parse the target node configuration file and generate target node configuration class information for each functional node to be configured based on the node attribute information and node hierarchy relationship of each functional node to be configured.

[0110] The node entity class information determination module 530 is used to obtain the preset basic function source code and node configuration resource file, and determine the target node entity class information of each functional node to be configured based on the preset basic function source code, the node configuration resource file and the target node configuration class information of each functional node to be configured.

[0111] The node combination module 540 is used to combine the target node configuration class information and the target node entity class information of each functional node to be configured to obtain the at least one functional node to be configured; the at least one functional node to be configured is used to be displayed in response to the first node display instruction.

[0112] Optionally, the parsing module 520 includes:

[0113] The parsing unit is used to parse the target node configuration file to obtain the node attribute information and node hierarchy relationship of each functional node to be configured;

[0114] The target node configuration class information determination unit is used to obtain a predefined node configuration class and, based on the predefined node configuration class, map the attribute information and node hierarchy relationship of each functional node to be configured into the target node configuration class information of each functional node to be configured.

[0115] Optionally, the node entity class information determination module 530 includes:

[0116] The target node data acquisition unit is used to load the target node data corresponding to the target node configuration class information of each functional node to be configured in the node configuration resource file, based on the data model framework corresponding to the preset basic function source code.

[0117] The data reflection unit is used to reflect the target node data to generate target node entity class information for each functional node to be configured; the target node entity class information corresponds to the entity information of the target node data.

[0118] Optionally, the node combination module 540 includes:

[0119] The first node information generation unit is used to combine the target node configuration class information and the target node entity class information of each functional node to be configured through a first combination mode to obtain the first node information; the first node information is used to determine the entity information of each functional node to be configured.

[0120] The second node information generation unit is used to combine the target node configuration class information and the target node entity class information of each functional node to be configured through a second combination mode to obtain the second node information; the second node information is used to determine the configuration information of each functional node to be configured.

[0121] The configuration node generation unit is used to obtain the at least one configuration node based on the first node information and the second node information.

[0122] Optionally, the device further includes:

[0123] The first display module is used to respond to the first node display instruction and display the at least one functional node to be configured in the target interface based on a preset display method; the preset display method includes a tree node structure and a tree table node structure.

[0124] Optionally, the device further includes:

[0125] The node update request acquisition module is used to acquire update requests for the at least one functional node to be configured in response to a node operation instruction for the target interface; the update request includes adding or deleting the at least one functional node to be configured.

[0126] The node update module is used to update the at least one functional node to be configured based on the update request, and determine the at least one functional node to be configured after the update.

[0127] The storage module is used to receive a save command triggered by the user and store the updated node data corresponding to at least one functional node to be configured in the node configuration resource file.

[0128] The second display module is used to respond to the second node display instruction and display the updated at least one configurable functional node in the target interface based on the preset display method.

[0129] Optionally, the device further includes:

[0130] The configuration data acquisition module is used to acquire the configuration data of the vehicle software module to be developed in response to the configuration command of the vehicle software module to be developed.

[0131] The software module configuration file generation module is used to copy the target node configuration class information corresponding to the data to be configured in the target node rule file when the data to be configured corresponds to the target node configuration class information, and generate the vehicle software module configuration file to be developed.

[0132] A software development module is used to generate the software module to be developed based on the configuration file of the software module to be developed.

[0133] It should be noted that the apparatus provided in the above embodiments is only illustrated by the division of the above functional modules when implementing its functions. In actual applications, the above functions can be assigned to different functional modules as needed, that is, the internal structure of the device can be divided into different functional modules to complete all or part of the functions described above. In addition, the apparatus and method embodiments provided in the above embodiments belong to the same concept, and the specific implementation process can be found in the method embodiments, which will not be repeated here.

[0134] This invention also provides an electronic device, including a processor and a memory, wherein the memory stores at least one instruction or at least one program segment, the at least one instruction or the at least one program segment being loaded and executed by the processor to implement the steps of the program generation method for implementing vehicle software as described above.

[0135] Memory can be used to store software programs and modules. The processor executes various functional applications by running the software programs and modules stored in the memory. Memory can mainly include a program storage area and a data storage area. The program storage area can store the operating system, application programs required for functions, etc.; the data storage area can store data created based on the use of the device, etc. Furthermore, memory can include high-speed random access memory, and can also include non-volatile memory, such as at least one disk storage device, flash memory device, or other volatile solid-state storage device. Accordingly, memory can also include a memory controller to provide the processor with access to the memory. The processor can be a central processing unit, or other general-purpose processors, digital signal processors, application-specific integrated circuits (ASICs) or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. A general-purpose processor can be a microprocessor or any conventional processor.

[0136] The methods and embodiments provided in this invention can be executed on a computer terminal, server, or similar computing device. Taking execution on a terminal as an example, refer to... Figure 6 The diagram shown is a hardware structure schematic of a terminal that runs a program generation method for implementing vehicle software, according to an embodiment of the present invention.

[0137] Specifically, the terminal may include an RF (Radio Frequency) circuit 610, a memory 620 including one or more computer-readable storage media, an input unit 630, a display unit 640, a sensor 650, an audio circuit 660, a WiFi (Wireless Fidelity) module 670, a processor 680 including one or more processing cores, and a power supply 690, among other components. Those skilled in the art will understand that... Figure 6 The terminal structure shown does not constitute a limitation on the terminal and may include more or fewer components than shown, or combine certain components, or have different component arrangements. Wherein:

[0138] The RF circuit 610 can be used for receiving and transmitting signals during information transmission or calls. Specifically, it receives downlink information from the base station and hands it over to one or more processors 680 for processing; additionally, it transmits uplink data to the base station. Typically, the RF circuit 610 includes, but is not limited to, an antenna, at least one amplifier, a tuner, one or more oscillators, a Subscriber Identity Module (SIM) card, a transceiver, a coupler, an LNA (Low Noise Amplifier), a duplexer, etc. Furthermore, the RF circuit 610 can also communicate wirelessly with networks and other terminals. The wireless communication can use any communication standard or protocol, including but not limited to GSM (Global System for Mobile communication), GPRS (General Packet Radio Service), CDMA (Code Division Multiple Access), WCDMA (Wideband Code Division Multiple Access), LTE (Long Term Evolution), email, SMS (Short Messaging Service), etc.

[0139] The memory 620 can be used to store software programs and modules. The processor 680 executes various functional applications and data processing by running the software programs and modules stored in the memory 620. The memory 620 may mainly include a program storage area and a data storage area. The program storage area may store the operating system, application programs required for the functions, etc.; the data storage area may store data created according to the use of the terminal, etc. In addition, the memory 620 may include high-speed random access memory, and may also include non-volatile memory, such as at least one disk storage device, flash memory device, or other volatile solid-state storage device. Accordingly, the memory 620 may also include a memory controller to provide access to the memory 620 for the processor 680 and the input unit 630.

[0140] The input unit 630 can be used to receive input digital or character information, and to generate keyboard, mouse, joystick, optical, or trackball signal inputs related to user settings and function control. Specifically, the input unit 630 may include a touch-sensitive surface 631 and other input devices 632. The touch-sensitive surface 631, also known as a touch display screen or touchpad, can collect touch operations performed by the user on or near it (such as operations performed by the user using a finger, stylus, or any suitable object or accessory on or near the touch-sensitive surface 631), and drive the corresponding connection device according to a pre-set program. Optionally, the touch-sensitive surface 631 may include two parts: a touch detection device and a touch controller. The touch detection device detects the user's touch position and the signal generated by the touch operation, and transmits the signal to the touch controller; the touch controller receives touch information from the touch detection device, converts it into touch point coordinates, sends it to the processor 680, and can receive and execute commands sent by the processor 680. In addition, the touch-sensitive surface 631 can be implemented using various types such as resistive, capacitive, infrared, and surface acoustic wave. In addition to the touch-sensitive surface 631, the input unit 630 may also include other input devices 632. Specifically, other input devices 632 may include, but are not limited to, one or more of the following: physical keyboard, function keys (such as volume control buttons, power buttons, etc.), trackball, mouse, joystick, etc.

[0141] The display unit 640 can be used to display information input by the user or information provided to the user, as well as various graphical user interfaces of the terminal. These graphical user interfaces can be composed of graphics, text, icons, videos, and any combination thereof. The display unit 640 may include a display panel 641, which may optionally be configured as an LCD (Liquid Crystal Display), OLED (Organic Light-Emitting Diode), or similar display panel 641. Further, a touch-sensitive surface 631 may cover the display panel 641. When the touch-sensitive surface 631 detects a touch operation on or near it, it transmits the information to the processor 680 to determine the type of touch event. Subsequently, the processor 680 provides corresponding visual output on the display panel 641 according to the type of touch event. The touch-sensitive surface 631 and the display panel 641 can be two independent components to implement input and output functions. However, in some embodiments, the touch-sensitive surface 631 and the display panel 641 can be integrated to achieve both input and output functions.

[0142] The terminal may also include at least one sensor 650, such as a light sensor, a motion sensor, and other sensors. Specifically, the light sensor may include an ambient light sensor and a proximity sensor. The ambient light sensor can adjust the brightness of the display panel 641 according to the ambient light level, and the proximity sensor can turn off the display panel 641 and / or backlight when the terminal is moved to the ear. As a type of motion sensor, a gravity acceleration sensor can detect the magnitude of acceleration in various directions (generally three axes). When stationary, it can detect the magnitude and direction of gravity and can be used for applications that identify the terminal's posture (such as landscape / portrait switching, related games, magnetometer posture calibration), vibration recognition-related functions (such as pedometer, tapping), etc. Other sensors that may be configured on the terminal, such as gyroscopes, barometers, hygrometers, thermometers, and infrared sensors, will not be described in detail here.

[0143] Audio circuitry 660, speaker 661, and microphone 662 provide an audio interface between the user and the terminal. Audio circuitry 660 converts received audio data into electrical signals, which are then transmitted to speaker 661, where they are converted into sound signals for output. Conversely, microphone 662 converts collected sound signals into electrical signals, which are received by audio circuitry 660, converted back into audio data, and then processed by processor 680 before being transmitted via RF circuitry 610 to, for example, another terminal, or output to memory 620 for further processing. Audio circuitry 660 may also include an earphone jack to facilitate communication between a peripheral headset and the terminal.

[0144] WiFi is a short-range wireless transmission technology. The terminal, through the WiFi module 670, can help users send and receive emails, browse web pages, and access streaming media, providing users with wireless broadband internet access. Although Figure 6 WiFi module 670 is shown, but it is understood that it is not a necessary component of the terminal and can be omitted as needed without changing the nature of the invention.

[0145] The processor 680 is the control center of the terminal, connecting various parts of the terminal via various interfaces and lines. It executes software programs and / or modules stored in the memory 620, and calls data stored in the memory 620 to perform various functions and process data, thereby providing overall monitoring of the terminal. Optionally, the processor 680 may include one or more processing cores; preferably, the processor 680 may integrate an application processor and a modem processor, wherein the application processor mainly handles the operating system, user interface, and applications, and the modem processor mainly handles wireless communication. It is understood that the modem processor may not be integrated into the processor 680.

[0146] The terminal also includes a power supply 690 (such as a battery) to power various components. Preferably, the power supply can be logically connected to the processor 680 through a power management system, thereby enabling functions such as charging, discharging, and power consumption management through the power management system. The power supply 690 may also include one or more DC or AC power supplies, recharging systems, power fault detection circuits, power converters or inverters, power status indicators, and other arbitrary components.

[0147] Although not shown, the terminal may also include a camera, Bluetooth module, etc., which will not be described in detail here. Specifically, in this embodiment, the terminal also includes a memory and one or more programs, wherein one or more programs are stored in the memory and configured to be executed by one or more processors.

[0148] This invention also provides a computer-readable storage medium storing at least one instruction or at least one program segment, which is loaded and executed by a processor to implement the steps of the program generation method for implementing vehicle software as described above. In this invention, the computer program includes computer program code, which may be in the form of source code, object code, executable file, or some intermediate form. The computer-readable storage medium may include any entity or device capable of carrying the computer program code, a recording medium, a USB flash drive, a portable hard drive, a magnetic disk, an optical disk, a computer memory, a read-only memory, a random access memory, an electrical carrier signal, a telecommunication signal, and a software distribution medium, etc.

[0149] This invention also provides a computer storage medium storing at least one instruction or at least one program segment, which is loaded and executed by a processor to implement the above-described method. In this invention, the computer program includes computer program code, which may be in the form of source code, object code, executable file, or some intermediate form. The computer-readable storage medium may include any entity or device capable of carrying the computer program code, a recording medium, a USB flash drive, a portable hard drive, a magnetic disk, an optical disk, a computer memory, a read-only memory, a random access memory, an electrical carrier signal, a telecommunication signal, and a software distribution medium, etc.

[0150] This invention also provides a computer program product or computer program, which includes computer instructions stored in a computer-readable storage medium. A processor of a computer device reads the computer instructions from the computer-readable storage medium and executes the computer instructions, causing the computer device to perform the program generation method for implementing vehicle software provided in the various optional implementations described above.

[0151] The above description is only a preferred embodiment of the present invention and is not intended to limit the present invention. Any modifications, equivalent substitutions, improvements, etc., made within the spirit and principles of the present invention should be included within the protection scope of the present invention.

Claims

1. A method for generating a program to implement vehicle software, characterized in that, include: Obtain the preset target node configuration file; The target node configuration file includes node attribute information and node hierarchy relationship for each of the at least one configurable functional nodes; the program for implementing the vehicle software includes the at least one configurable functional node; the vehicle software is software developed based on the adaptive vehicle open system architecture platform for controlling the vehicle or realizing vehicle-to-everything (V2X) intelligent interconnection functions; The target node configuration file is parsed, and target node configuration class information for each functional node to be configured is generated based on the node attribute information and node hierarchy relationship of each functional node to be configured. Obtain the source code of the preset basic functions and the node configuration resource file. Based on the data model framework corresponding to the source code of the preset basic functions, load the target node data corresponding to the target node configuration class information of each functional node to be configured in the node configuration resource file. The target node data is reflected to generate target node entity class information for each functional node to be configured; the target node entity class information corresponds to the entity information of the target node data; the data model framework is the Artop modeling framework; the node configuration resource file is a configuration file saved in AUTOSAR XML format; Based on the Composite pattern and the Factory Method pattern, the target node configuration class information and the target node entity class information of each functional node to be configured are combined to obtain the at least one functional node to be configured. The at least one configurable functional node is used to display in response to the display instruction of the first node.

2. The method for generating a program to implement vehicle software according to claim 1, characterized in that, The step of parsing the target node configuration file and generating target node configuration class information for each functional node to be configured based on the node attribute information and node hierarchy relationship of each functional node to be configured includes: The target node configuration file is parsed to obtain the node attribute information and node hierarchy relationship of each functional node to be configured; Obtain a predefined node configuration class, and based on the predefined node configuration class, map the attribute information and node hierarchy relationship of each functional node to be configured into the target node configuration class information of each functional node to be configured.

3. The method for generating program for implementing vehicle software according to claim 1, characterized in that, The step of combining the target node configuration class information and the target node entity class information of each functional node to be configured to obtain the at least one functional node to be configured includes: The target node configuration class information and target node entity class information of each functional node to be configured are combined using a first combination pattern to obtain first node information; the first node information is used to determine the entity information of each functional node to be configured. The target node configuration class information and target node entity class information of each functional node to be configured are combined using a second combination pattern to obtain second node information; the second node information is used to determine the configuration information of each functional node to be configured. The at least one functional node to be configured is obtained based on the first node information and the second node information.

4. The method for generating a program to implement vehicle software according to claim 1, characterized in that, Also includes: In response to the first node display instruction, the at least one functional node to be configured is displayed in the target interface based on a preset display method; The preset display methods include tree node structure and tree table node structure.

5. The method for generating a program to implement vehicle software according to claim 4, characterized in that, Also includes: In response to a node operation command for the target interface, an update request for the at least one functional node to be configured is obtained; The update request includes adding or deleting at least one of the functional nodes to be configured; Based on the update request, the at least one functional node to be configured is updated, and the updated at least one functional node to be configured is determined. Upon receiving a user-triggered save command, store the updated node data corresponding to at least one configurable functional node in the node configuration resource file; In response to the second node display instruction, the updated at least one configurable functional node is displayed in the target interface based on the preset display method.

6. The method for generating a program to implement vehicle software according to any one of claims 1 to 5, characterized in that, Also includes: In response to the configuration command of the vehicle software module to be developed, the configuration data of the vehicle software module to be developed is obtained; When the data to be configured corresponds to the target node configuration class information, copy the target node configuration class information that corresponds to the data to be configured in the target node configuration class information to generate the vehicle software module configuration file to be developed. The vehicle software module to be developed is generated based on the configuration file of the vehicle software module to be developed.

7. A program generation apparatus for implementing vehicle software, characterized in that, include: The target node configuration file acquisition module is used to acquire the preset target node configuration file; The target node configuration file includes node attribute information and node hierarchy relationship for each of the at least one configurable functional nodes; the program for implementing the vehicle software includes the at least one configurable functional node; the vehicle software is software developed based on the adaptive vehicle open system architecture platform for controlling the vehicle or realizing vehicle-to-everything (V2X) intelligent interconnection functions; The parsing module is used to parse the target node configuration file and generate target node configuration class information for each functional node to be configured based on the node attribute information and node hierarchy relationship of each functional node to be configured. The node entity class information determination module is used to obtain the preset basic function source code and node configuration resource file, and based on the data model framework corresponding to the preset basic function source code, load the target node data corresponding to the target node configuration class information of each function node to be configured in the node configuration resource file. The target node data is reflected to generate target node entity class information for each functional node to be configured; the target node entity class information corresponds to the entity information of the target node data; the data model framework is the Artop modeling framework; the node configuration resource file is a configuration file saved in AUTOSAR XML format; The node combination module is used to combine the target node configuration class information and the target node entity class information of each functional node to be configured based on the composition pattern and the factory method pattern to obtain the at least one functional node to be configured. The at least one configurable functional node is used to display in response to the display instruction of the first node.

8. An electronic device, characterized in that, The system includes a processor and a memory, wherein the memory stores at least one instruction or at least one program segment, the at least one instruction or the at least one program segment being loaded and executed by the processor to implement the program generation method for implementing vehicle software as described in any one of claims 1 to 6.

9. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores at least one instruction or at least one program segment, which is loaded and executed by a processor to implement the program generation method for implementing vehicle software as described in any one of claims 1 to 6.

Images