AUROSAR application layer architecture generation method, device and electronic device

By dividing the functional submodules in the initial software architecture into software components and generating Arxml files, the problem of large workload when the control system is converted to AUTOSAR architecture under the traditional software framework is solved, and efficient conversion of AUTOSAR architecture and flexibility of software components are achieved. Expand.

CN117608529BActive Publication Date: 2024-11-29DONGFENG COMML VEHICLE CO LTD
View PDF 2 Cites 0 Cited by

Patent Information

Application Number
CN202311525880.X
Authority / Receiving Office
CN · China
Patent Type
Patents(China)
Current Assignee / Owner
Filing Date
2023-11-14
Publication Date
2024-11-29
Estimated Expiration
2043-11-14

AI Technical Summary

Technical Problem

Control systems under the traditional software framework have a large workload when converting to AUTOSAR architecture. It is difficult for existing methods to efficiently realize the reuse, exchange and integration of software components in the development of complex embedded systems.

Method used

By dividing the functional submodules in the initial software architecture into software components, obtaining input and output information, variable data types and scheduling information, generating Arxml files, and importing them into the running environment generation tool to cut off global variable sharing between software components. Generate the AUTOSAR application layer architecture.

Benefits of technology

The transformation of the AUTOSAR architecture is realized, which reduces the workload and allows the traditional development model to be used when adding new functional modules or components to the software components, simplifying the software engineering development of the AUTOSAR architecture.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN117608529B_ABST
    Figure CN117608529B_ABST
Patent Text Reader

Abstract

The present invention provides a method, device and electronic device for generating an AUROSAR application layer architecture, the method comprising: dividing multiple functional submodules in an initial software architecture into corresponding software components to obtain a sub-information table; obtaining a software component interface information table based on the software component sub-information table, input and output information, variable data type and scheduling information; generating an Arxml file based on the software component interface information table and the Mapping information table; importing the Arxml file into an operating environment generation tool to generate an operating environment code; cutting off the global variable sharing between the software components of the initial software architecture, and compiling and integrating in combination with the operating environment code to obtain the AUROSAR application layer architecture. The present invention can solve the technical problem of large workload when the control system under the traditional software framework is converted to the AUTOSAR architecture.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The present invention relates to the field of software information technology, and in particular to a method, device and electronic device for generating an AUROSAR application layer architecture. Background Art

[0002] AUTOSAR (AUTomotive Open System ARchitecture) is a development cooperation alliance of major original equipment manufacturers, suppliers, and tool and software service providers in the global automotive industry. AUTOSAR aims to simplify the joint development of automotive electronic software, reduce costs and accelerate product time to market, improve software quality, and provide the mechanisms required for safety system design. AUTOSAR redefines the way embedded automotive software is written, thereby realizing the reuse, exchange, upgrade and integration of software components. The Run-Time Environment (RTE) is the core of the AUTOSAR architecture. All communications between components in the AUTOSAR system are carried out through component ports, which are defined by AUTOSAR interfaces. The runtime environment can implement communication interfaces and provide communication services between components. Therefore, all communications between components are under the control of the runtime environment.

[0003] The original intention of AUTOSAR is to shield the underlying hardware resource allocation, unify the configuration method, and solve the problem of excessive coupling between modules. Its essence is to facilitate the standardized development of the strategy layer, and ultimately achieve distributed development, improve software development efficiency and reduce maintenance costs. In today's increasingly complex embedded system development, this concept is becoming increasingly important. When the basic software layer (BSW) and the operating environment solution are determined, the application layer is ever-changing. The most important issue that the strategy program needs to consider is how to generate software components (application layer) and the integration of software components and the operating environment. There are two mainstream software component development methods: 1. "Top-down" and 2. "Bottom-up".

[0004] The "top-down" method is to first generate the module arxml file from the operating environment, then generate the software component framework from arxm1, and then combine the software component framework with the model to generate the software component, and then generate the AUTOSAR code from the complete module of the software component, and finally compile it together with the operating environment code; the "bottom-up" method is to start from the simulation module (simulink module), each module is configured according to the AUTOSAR method to generate the software component code and arxml file, and then combine arxml with the operating environment to generate the operating environment code, and finally compile the code generated by the operating environment and the software component together.

[0005] These methods are all suitable for the new development of a system. In fact, complex automotive embedded software has historical inheritance. A large number of control systems under traditional software frameworks need to be converted to the AUTOSAR architecture, which requires a huge workload. Summary of the invention

[0006] In view of this, it is necessary to provide an AUROSAR application layer architecture generation method, device and electronic device to solve the technical problem of heavy workload when the control system under the traditional software framework is converted to the AUTOSAR architecture.

[0007] In order to achieve the above object, the present invention provides an AUROSAR application layer architecture generation method, comprising:

[0008] Divide multiple functional submodules in the initial software architecture into corresponding software components, and obtain a software component belonging information table corresponding to each functional submodule;

[0009] Obtaining input and output information, variable data types and scheduling information corresponding to each functional submodule, and obtaining a software component interface information table based on the software component belonging information table, the input and output information, the variable data types and the scheduling information;

[0010] Obtain the mapping information table of application software layer variables and basic software layer variables;

[0011] Based on the software component interface information table and the Mapping information table, an Arxml file is generated; the Arxml file includes: an application layer software component Arxml file, and an application software layer and basic software layer interface Mapping Arxml file;

[0012] Importing the Arxml file into the operating environment generation tool to generate the operating environment code;

[0013] Cutting off the global variable sharing between the software components of the initial software architecture to obtain a modified software architecture;

[0014] The modified software architecture and the operating environment code are compiled and integrated to obtain the AUROSAR application layer architecture.

[0015] Further, the obtaining of input and output information, variable data types and scheduling information corresponding to each functional submodule, based on the software component belonging information table, the input and output information, the variable data types and the scheduling information, obtains a software component interface information table, including:

[0016] Obtain the input and output information, variable data types and scheduling information corresponding to each sub-function module in the baseline software engineering;

[0017] Based on the software component belonging information table, the input and output information, variable data types and scheduling information corresponding to each sub-functional module in the baseline software engineering are classified to obtain the interface information between the software components corresponding to each sub-functional module in the baseline software engineering, the internal information of the software components, and the interface information between the software components and the bottom layer;

[0018] Obtain the input and output information, variable data types and scheduling information corresponding to the updated functional submodule;

[0019] Based on the software component belonging information table, the input and output information, variable data types and scheduling information corresponding to the updated functional submodules are classified to obtain the interface information between the software components corresponding to the updated functional submodules, the internal information of the software components, and the interface information between the software components and the bottom layer;

[0020] Based on the interface information between software components corresponding to each sub-functional module in the baseline software engineering, the internal information of software components, and the interface information between software components and the underlying layer, as well as the interface information between software components corresponding to the updated functional sub-modules, the internal information of software components, and the interface information between software components and the underlying layer, a software component interface information table is generated.

[0021] Furthermore, the step of obtaining the input and output information, variable data types and scheduling information corresponding to each sub-function module in the baseline software engineering includes:

[0022] Obtaining variable information and function information of each source file in the baseline software project;

[0023] Based on the variable information and function information of each source file in the baseline software project, and the corresponding relationship between the main function of each functional submodule of the baseline software project and the source file, the input and output information of each functional submodule is obtained;

[0024] Obtaining scheduling information corresponding to each functional submodule in the scheduling file in the baseline software project;

[0025] Reverse analysis is performed on the A2L file in the baseline software project to obtain variable data types.

[0026] Furthermore, the input and output information of each functional submodule is obtained based on the variable information and function information of each source file in the baseline software project, and the correspondence between the main function of each functional submodule of the baseline software project and the source file, including:

[0027] Based on the variable information and function information of each source file in the baseline software project, and the correspondence between the main function of each functional sub-module and the source file in the baseline software project, all reference functions of the main function of each functional sub-module are expanded in a recursive manner to obtain the input and output information of each functional sub-module.

[0028] Further, the variable information of each source file includes at least one of a global variable, a static variable and a local variable;

[0029] The function information of each source file includes global functions, local functions, and referenced functions of global functions and referenced functions of local functions.

[0030] Furthermore, the obtaining of input and output information, variable data types and scheduling information corresponding to the updated functional submodules includes:

[0031] In the case where the updated functional sub-module is a functional sub-module that has been developed, compiling the source file of the updated functional sub-module to generate the source file code of the corresponding object file;

[0032] The source file code of the object file is analyzed to obtain input and output information, variable data types and scheduling information corresponding to the updated functional sub-module.

[0033] Furthermore, the obtaining of input and output information, variable data types and scheduling information corresponding to the updated functional submodules includes:

[0034] When the updated functional submodule is an uncompleted functional submodule, a development information table corresponding to the functional submodule is obtained, and information is extracted from the development information table to obtain input and output information, variable data types and scheduling information corresponding to the updated functional submodule.

[0035] The present invention also provides an AUROSAR application layer architecture generation device, comprising:

[0036] The software component allocation module is used to divide multiple functional sub-modules in the initial software architecture into corresponding software components, and obtain a software component belonging information table corresponding to each functional sub-module;

[0037] An interface information extraction module is used to obtain input and output information, variable data types and scheduling information corresponding to each functional submodule, and obtain a software component interface information table based on the software component belonging information table, the input and output information, the variable data type and the scheduling information;

[0038] Mapping information collection module, used to obtain the mapping information table of application software layer variables and basic software layer variables;

[0039] An Arxml file generation module generates an Arxml file based on the software component interface information table and the Mapping information table; the Arxml file includes: an application layer software component Arxml file, and an application software layer and basic software layer interface Mapping Arxml file;

[0040] An operating environment code generation module, used for importing the Arxml file into an operating environment generation tool to generate an operating environment code;

[0041] The original engineering transformation module is used to cut off the global variable sharing between the software components of the initial software architecture to obtain a modified software architecture;

[0042] The compilation and integration module is used to compile and integrate the modified software architecture and the operating environment code to obtain the AUROSAR application layer architecture.

[0043] The present invention also provides an electronic device, comprising a memory and a processor, wherein:

[0044] The memory is used to store programs;

[0045] The processor is coupled to the memory and is used to execute the program stored in the memory to implement the steps in the AUROSAR application layer architecture generation method as described in any one of the above.

[0046] The present invention also provides a non-transitory computer-readable storage medium having a computer program stored thereon, wherein when the computer program is executed by a processor, the method for generating an AUROSAR application layer architecture as described in any one of the above items is implemented.

[0047] The beneficial effect of adopting the above implementation mode is: the AUROSAR application layer architecture generation method, device and electronic device provided by the present invention divide the functional sub-modules of the initial software architecture into software components, and extract the interface information (including input and output information) between software components, the internal information of software components (including scheduling information), the interface information between software components and the underlying layer (including input and output information), and the variable data type, generate the application layer software component Arxml file, and also obtain the interactive variable Mapping information between the application software layer and the basic software layer, generate the corresponding Mapping Arxml file, import the Arxml file into the operating environment generation tool, obtain the operating environment code, and then adaptively modify the software code of the initial software architecture, cut off the global variable sharing between software components, and instead obtain the variable input and output from the operating environment layer and write them into the operating environment layer. Therefore, the application layer software of the initial software architecture completes the AUTOSAR architecture conversion, and the operating environment code and the adaptively modified software code participate in the compilation and integration.

[0048] When a new functional module or a new software component needs to be added to a software component, the functional module developers can continue to use the traditional development model without considering the AUTOSAR factor. After the development of the new functional module or new software component is completed, they only need to update the software component belonging information table and repeat the above conversion process to obtain the AUTOSAR architecture software engineering, thereby solving the technical problem of large workload when the control system under the traditional software framework is converted to the AUTOSAR architecture. BRIEF DESCRIPTION OF THE DRAWINGS

[0049] In order to more clearly illustrate the technical solutions in the embodiments of the present invention, the following briefly introduces the drawings required for use in the description of the embodiments. Obviously, the drawings described below are only some embodiments of the present invention. For those skilled in the art, other drawings can be obtained based on these drawings without creative work.

[0050] Figure 1 A flowchart of an embodiment of the AUROSAR application layer architecture generation method provided by the present invention;

[0051] Figure 2 A principle block diagram of an embodiment of the AUROSAR application layer architecture generation device provided by the present invention;

[0052] Figure 3 A flowchart of an embodiment of the AUROSAR application layer architecture generation device provided by the present invention;

[0053] Figure 4 A schematic structural diagram of an embodiment of an electronic device provided by the present invention. DETAILED DESCRIPTION

[0054] The technical solutions in the embodiments of the present invention will be described clearly and completely below in conjunction with the accompanying drawings in the embodiments of the present invention. Obviously, the described embodiments are only part of the embodiments of the present invention, not all of the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by those skilled in the art without creative work are within the scope of protection of the present invention.

[0055] In the description of the embodiments of the present application, unless otherwise specified, “plurality” means two or more.

[0056] The terms "including" and "having" and any variations thereof in the embodiments of the present invention are intended to cover non-exclusive inclusions. For example, a process, method, apparatus, product or equipment comprising a series of steps or modules is not necessarily limited to those steps or modules clearly listed, but may include other steps or modules not clearly listed or inherent to these processes, methods, products or equipment.

[0057] The naming or numbering of the steps in the embodiments of the present invention does not mean that the steps in the method flow must be executed in the time / logical sequence indicated by the naming or numbering. The execution order of the named or numbered process steps can be changed according to the technical purpose to be achieved, as long as the same or similar technical effects can be achieved.

[0058] Reference to an "embodiment" herein means that a particular feature, structure, or characteristic described in conjunction with the embodiment may be included in at least one embodiment of the present invention. The appearance of the phrase in various places in the specification does not necessarily refer to the same embodiment, nor is it an independent or alternative embodiment that is mutually exclusive with other embodiments. It is explicitly and implicitly understood by those skilled in the art that the embodiments described herein may be combined with other embodiments.

[0059] The present invention provides an AUROSAR application layer architecture generation method, device and electronic device, which are described below respectively.

[0060] like Figure 1 As shown, the present invention provides an AUROSAR (AUTomotive Open System ARchitecture, automotive open system architecture) application layer architecture implementation method, including:

[0061] Divide multiple functional sub-modules in the initial software architecture into corresponding software components (SWCs), and obtain a software component belonging information table corresponding to each functional sub-module;

[0062] Obtaining input and output information, variable data types and scheduling information corresponding to each functional submodule, and obtaining a software component interface information table based on the software component belonging information table, the input and output information, the variable data types and the scheduling information;

[0063] Obtain the mapping information table of the application software layer (Application Software Layer, ASW) variables and the basic software layer (Basic Software Layer, BSW) variables;

[0064] Based on the software component interface information table and the Mapping information table, an Arxml file is generated; the Arxml file includes: an application layer software component Arxml file, and an application software layer and basic software layer interface Mapping Arxml file;

[0065] Importing the Arxml file into a Run-Time Environment (RTE) generation tool to generate a Run-Time Environment code;

[0066] Cutting off the global variable sharing between the software components of the initial software architecture to obtain a modified software architecture;

[0067] The modified software architecture and the operating environment code are compiled and integrated to obtain the AUROSAR application layer architecture.

[0068] It can be understood that AUROSAR is an automotive open system architecture and a development cooperation alliance of major original equipment manufacturers, suppliers and tool and software service providers in the global automotive industry.

[0069] In this embodiment, a software component allocation module is used to divide the software of the original traditional architecture into software components, 1000 functional sub-modules are merged and split, and an information table of the sub-modules on the software components is output. Specifically, the software component allocation module is used to divide the software of the original traditional architecture into software components, and a software component interface information extraction module is used to extract interface information between software components (including output, input information, etc.), internal information of software components (i.e., scheduling information, including runnable name, scheduling cycle, scheduling order, etc.), software component and underlying interface information (including input, output information, etc.), and variable data types, and an Arxml file generation module is used to generate an application layer software component Arxml file based on the above information, and an application software layer and basic software layer interface Mapping information collection module is used to obtain application software layer and basic software layer interactive variable Mapping information, and an Arxml file generation module is used to generate an application software layer and basic software layer interface Mapping Arxml file.

[0070] In another embodiment, an application software layer and basic software layer interface mapping information collection module is used to obtain application software layer and basic software layer interactive variable mapping information, including message transmission and sensor actuator transmission signal, and output application software layer and basic software layer variable mapping information table.

[0071] Furthermore, according to the software component interface information table obtained in the above steps and the output application software layer and basic software layer variable mapping information table, an Arxml file generation module is used to generate an application layer software component Arxml file and an application software layer and basic software layer interface Mapping Arxml file.

[0072] Import the Arxml file into the runtime environment generation tool to obtain the runtime environment code, use the original engineering transformation module to adaptively modify the software code of the original traditional architecture, cut off the global variable sharing between software components, and instead obtain variable input and output from the runtime environment layer and write them into the runtime environment layer.

[0073] In other embodiments, the Arxml file is imported into an operating environment generation tool, such as ISOLAR-A, to obtain the operating environment code.

[0074] As a result, the application layer software of the original traditional architecture completes the AUTOSAR architecture transformation, and the above-mentioned operating environment code and the adaptively modified original engineering code participate in the compilation and integration.

[0075] When a new functional module or a new software component needs to be added to a software component, the functional module developer can continue to use the traditional development model without considering the AUTOSAR factor. After the development of the new module or new software component is completed, the software component allocation module is updated and the above conversion process is repeated to obtain the AUTOSAR architecture software engineering.

[0076] Specifically, the software code of the original traditional architecture (initial software architecture) is adaptively modified using the original engineering transformation module, that is, the global variable sharing between software components is cut off, and the variable input and output are obtained from the operating environment layer and written to the operating environment layer instead. For example, the global variables for interaction between the software components involved are renamed in the unit module code, and the values ​​are read and assigned from the operating environment layer before the runnable is scheduled; or the global variables for interaction between the software components involved in the unit module code are modified to local variables, and the values ​​are read and assigned from the operating environment layer or written to the operating environment layer.

[0077] The application layer software of the original traditional architecture completes the AUTOSAR architecture conversion, and the above-obtained operating environment code and the adaptively modified original engineering code participate in the compilation and integration.

[0078] In some embodiments, the step of obtaining the input and output information, variable data type and scheduling information corresponding to each functional submodule, and obtaining a software component interface information table based on the software component belonging information table, the input and output information, the variable data type and the scheduling information, includes:

[0079] Obtain the input and output information, variable data types and scheduling information corresponding to each sub-function module in the baseline software engineering;

[0080] Based on the software component belonging information table, the input and output information, variable data types and scheduling information corresponding to each sub-functional module in the baseline software engineering are classified to obtain the interface information between the software components corresponding to each sub-functional module in the baseline software engineering, the internal information of the software components, and the interface information between the software components and the bottom layer;

[0081] Obtain the input and output information, variable data types and scheduling information corresponding to the updated functional submodule;

[0082] Based on the software component belonging information table, the input and output information, variable data types and scheduling information corresponding to the updated functional submodules are classified to obtain the interface information between the software components corresponding to the updated functional submodules, the internal information of the software components, and the interface information between the software components and the bottom layer;

[0083] Based on the interface information between software components corresponding to each sub-functional module in the baseline software engineering, the internal information of software components, and the interface information between software components and the underlying layer, as well as the interface information between software components corresponding to the updated functional sub-modules, the internal information of software components, and the interface information between software components and the underlying layer, a software component interface information table is generated.

[0084] It can be understood that the software component interface information extraction module is used to analyze each functional sub-module one by one, that is, the sub-functional modules are first divided into software components, and then the baseline engineering analysis module and the functional update analysis module are used to analyze and process the baseline software engineering and the updated sub-functional module interface information respectively to obtain the input information and output information of each sub-functional module.

[0085] The obtained input and output variables and data types, function scheduling cycle, function scheduling order and other information are classified and sorted according to the sub-module information table of software components, and the interface information between software components (including output information, input information, etc.), internal information of software components (including runnable name, scheduling cycle, scheduling order, etc.), software component and underlying interface information (including input information, output information, etc.) are obtained, and the software component interface information table containing the above information is output.

[0086] In some embodiments, the step of obtaining input and output information, variable data types, and scheduling information corresponding to each sub-function module in the baseline software engineering includes:

[0087] Obtaining variable information and function information of each source file in the baseline software project;

[0088] Based on the variable information and function information of each source file in the baseline software project, and the corresponding relationship between the main function of each functional submodule of the baseline software project and the source file, the input and output information of each functional submodule is obtained;

[0089] Obtaining scheduling information corresponding to each functional submodule in the scheduling file in the baseline software project;

[0090] Reverse analysis is performed on the A2L file in the baseline software project to obtain variable data types.

[0091] Furthermore, the input and output information of each functional submodule is obtained based on the variable information and function information of each source file in the baseline software project, and the correspondence between the main function of each functional submodule of the baseline software project and the source file, including:

[0092] Based on the variable information and function information of each source file in the baseline software project, and the correspondence between the main function of each functional sub-module and the source file in the baseline software project, all reference functions of the main function of each functional sub-module are expanded in a recursive manner to obtain the input and output information of each functional sub-module.

[0093] The variable information of each source file includes at least one of a global variable, a static variable and a local variable;

[0094] The function information of each source file includes global functions, local functions, and referenced functions of global functions and referenced functions of local functions.

[0095] It can be understood that the processing of the baseline software engineering includes using the source code analysis module to obtain (the specific method can be adopted but not limited to automatically analyzing the source file compilation to generate the object file and the code lines of the source file itself) the global variables, static variables, local variables, global function functions, local function function information of each source file, and the input, output variables, and reference function information of each global function and local function itself, and according to the correspondence between the main function of the sub-function module and the source file, all reference functions of the main function are expanded in a layer-by-layer recursive manner to obtain the input and output variable information of the main function of the sub-function module, and use the scheduling analysis module to obtain the scheduling period, scheduling order and other information of the sub-function module in the scheduling file, and then use the A2L file variable data type reverse analysis module to reversely analyze the A2L file in the baseline software engineering to obtain the data type of the variables involved, such as signed, unsigned, data length, dimension and other information.

[0096] Among them, the A2L file defines the information required for communication between the host computer and the vehicle electronic control unit during the calibration process, which can be XCPonCAN, XCPonUSB, XCPonSPI, etc.

[0097] In some embodiments, the obtaining of input and output information, variable data types and scheduling information corresponding to the updated functional submodule includes:

[0098] In the case where the updated functional sub-module is a functional sub-module that has been developed, compiling the source file of the updated functional sub-module to generate the source file code of the corresponding object file;

[0099] The source file code of the object file is analyzed to obtain input and output information, variable data types and scheduling information corresponding to the updated functional sub-module.

[0100] In some embodiments, the obtaining of input and output information, variable data types and scheduling information corresponding to the updated functional submodule includes:

[0101] When the updated functional submodule is an uncompleted functional submodule, a development information table corresponding to the functional submodule is obtained, and information is extracted from the development information table to obtain input and output information, variable data types and scheduling information corresponding to the updated functional submodule.

[0102] It can be understood that the input of the function update analysis module is the function development update information table, which includes the main function name of the newly added sub-function module, scheduling information, data dictionary file and other information, the code, model (no handwritten code), data dictionary file path, and scheduling change information of the upgraded sub-module, and also includes the sub-function module information that needs to be deleted from the baseline project. The newly added sub-function modules are divided into two categories. The first category is the sub-function modules that have been developed, with source code, model (no handwritten code), and data dictionary file. The second category is the sub-function modules that have not been completed but have basic input and output infrastructure design and scheduling presets. For the first category of sub-function modules, the input and output variable information of the newly added sub-function modules can be obtained by, but not limited to, automatically analyzing the object files generated by compiling the source files and the code lines of the source files themselves. The sub-function modules with models also automatically obtain the input and output variable information of the sub-function modules through the model interface information extraction module. For the second category, the pre-development information processing module is used to automatically extract information from the function development update information table with a specific format to obtain the input and output variables, data type information and scheduling information of the sub-function modules.

[0103] In summary, the AUROSAR application layer architecture generation method provided by the present invention includes: dividing multiple functional sub-modules in the initial software architecture into corresponding software components, and obtaining a software component belonging information table corresponding to each functional sub-module; obtaining input and output information, variable data type and scheduling information corresponding to each functional sub-module, and obtaining a software component interface information table based on the software component belonging information table, the input and output information, the variable data type and the scheduling information; obtaining a Mapping information table of application software layer variables and basic software layer variables; generating an Arxml file based on the software component interface information table and the Mapping information table; the Arxml file includes: an application layer software component Arxml file, and an application software layer and basic software layer interface Mapping Arxml file; importing the Arxml file into a running environment generation tool to generate a running environment code; cutting off the global variable sharing between the software components of the initial software architecture to obtain a modified software architecture; compiling and integrating the modified software architecture and the running environment code to obtain the AUROSAR application layer architecture.

[0104] The AUROSAR application layer architecture generation method provided by the present invention divides the functional submodules of the initial software architecture into software components, extracts the interface information (including input and output information) between the software components, the internal information of the software components (including scheduling information), the interface information between the software components and the bottom layer (including input and output information), and the variable data type, generates the application layer software component Arxml file, obtains the interactive variable Mapping information between the application software layer and the basic software layer, generates the corresponding Mapping Arxml file, imports the Arxml file into the operating environment generation tool, obtains the operating environment code, and then adaptively modifies the software code of the initial software architecture, cuts off the global variable sharing between the software components, and instead obtains the variable input and output from the operating environment layer and writes them into the operating environment layer, thereby, the application layer software of the initial software architecture completes the AUTOSAR architecture conversion, and the operating environment code and the adaptively modified software code participate in the compilation and integration.

[0105] When a new functional module or a new software component needs to be added to a software component, the functional module developers can continue to use the traditional development model without considering the AUTOSAR factor. After the development of the new functional module or new software component is completed, they only need to update the software component belonging information table and repeat the above conversion process to obtain the AUTOSAR architecture software engineering, thereby solving the technical problem of large workload when the control system under the traditional software framework is converted to the AUTOSAR architecture.

[0106] like Figure 2 As shown, the present invention also provides an AUROSAR application layer architecture generation device 200, comprising:

[0107] The software component allocation module 210 is used to divide the multiple functional sub-modules in the initial software architecture into corresponding software components, and obtain a software component belonging information table corresponding to each functional sub-module;

[0108] The interface information extraction module 220 is used to obtain the input and output information, variable data type and scheduling information corresponding to each functional submodule, and obtain the software component interface information table based on the software component belonging information table, the input and output information, the variable data type and the scheduling information;

[0109] Mapping information collection module 230, used to obtain a mapping information table of application software layer variables and basic software layer variables;

[0110] Arxml file generation module 240 generates an Arxml file based on the software component interface information table and the Mapping information table; the Arxml file includes: an application layer software component Arxml file, and an application software layer and basic software layer interface Mapping Arxml file;

[0111] An operating environment code generation module 250 is used to import the Arxml file into an operating environment generation tool to generate an operating environment code;

[0112] The original engineering transformation module 260 is used to cut off the global variable sharing between the software components of the initial software architecture to obtain a modified software architecture;

[0113] The compiling and integrating module 270 is used to compile and integrate the modified software architecture and the operating environment code to obtain the AUROSAR application layer architecture.

[0114] In some other embodiments, the working process of the AUROSAR application layer architecture generating device 200 is as follows: Figure 3 As shown, the software component allocation module 210 outputs the software component belonging information table, the interface information extraction module 220 outputs the software component interface information table, the Mapping information collection module 230 outputs the Mapping information table, the Arxml file generation module 240 generates the Mapping Arxml file based on the received information table, and then the operating environment code generation module 250 generates the corresponding operating environment code, and the compilation integration module 270 combines the operating environment code and the modified software architecture output by the original project transformation module 260 to obtain the AUROSAR application layer architecture.

[0115] The AUROSAR application layer architecture generation device provided in the above embodiment can implement the technical solution described in the above AUROSAR application layer architecture generation method embodiment. The specific implementation principles of the above modules or units can refer to the corresponding contents in the above AUROSAR application layer architecture generation method embodiment, which will not be repeated here.

[0116] like Figure 4 As shown, the present invention also provides an electronic device 400. The electronic device 400 includes a processor 401, a memory 402 and a display 403. Figure 4 Only some of the components of the electronic device 400 are shown, but it should be understood that it is not required to implement all of the components shown, and more or fewer components may be implemented instead.

[0117] In some embodiments, the memory 402 may be an internal storage unit of the electronic device 400, such as a hard disk or memory of the electronic device 400. In other embodiments, the memory 402 may also be an external storage device of the electronic device 400, such as a plug-in hard disk, a smart memory card (Smart Media Card, SMC), a secure digital (Secure Digital, SD) card, a flash card (Flash Card), etc. equipped on the electronic device 400.

[0118] Furthermore, the memory 402 may include both an internal storage unit of the electronic device 400 and an external storage device. The memory 402 is used to store application software installed in the electronic device 400 and various data.

[0119] In some embodiments, the processor 401 may be a central processing unit (CPU), a microprocessor or other data processing chip, used to run program codes or process data stored in the memory 402, such as the AUROSAR application layer architecture generation method of the present invention.

[0120] In some embodiments, the display 403 may be an LED display, a liquid crystal display, a touch-sensitive liquid crystal display, an OLED (Organic Light-Emitting Diode) touch device, etc. The display 403 is used to display information on the electronic device 400 and to display a visual user interface. The components 401-403 of the electronic device 400 communicate with each other via a system bus.

[0121] In some embodiments of the present invention, when the processor 401 executes the AUROSAR application layer architecture generation program in the memory 402, the following steps may be implemented:

[0122] Divide multiple functional submodules in the initial software architecture into corresponding software components, and obtain a software component belonging information table corresponding to each functional submodule;

[0123] Obtaining input and output information, variable data types and scheduling information corresponding to each functional submodule, and obtaining a software component interface information table based on the software component belonging information table, the input and output information, the variable data types and the scheduling information;

[0124] Obtain the mapping information table of application software layer variables and basic software layer variables;

[0125] Based on the software component interface information table and the Mapping information table, an Arxml file is generated; the Arxml file includes: an application layer software component Arxml file, and an application software layer and basic software layer interface Mapping Arxml file;

[0126] Importing the Arxml file into the operating environment generation tool to generate the operating environment code;

[0127] Cutting off the global variable sharing between the software components of the initial software architecture to obtain a modified software architecture;

[0128] The modified software architecture and the operating environment code are compiled and integrated to obtain the AUROSAR application layer architecture.

[0129] It should be understood that: when the processor 401 executes the AUROSAR application layer architecture generation program in the memory 402 , in addition to the above functions, other functions may also be implemented, and details may refer to the description of the above corresponding method embodiments.

[0130] Furthermore, the embodiment of the present invention does not specifically limit the type of the electronic device 400 mentioned, and the electronic device 400 may be a portable electronic device such as a mobile phone, a tablet computer, a personal digital assistant (PDA), a wearable device, a laptop computer, etc. Exemplary embodiments of portable electronic devices include but are not limited to portable electronic devices equipped with IOS, Android, Microsoft or other operating systems. The above-mentioned portable electronic device may also be other portable electronic devices, such as a laptop computer with a touch-sensitive surface (e.g., a touch panel). It should also be understood that in some other embodiments of the present invention, the electronic device 400 may not be a portable electronic device, but a desktop computer with a touch-sensitive surface (e.g., a touch panel).

[0131] In another aspect, the present invention further provides a non-transitory computer-readable storage medium having a computer program stored thereon, and when the computer program is executed by a processor, the method for generating an AUROSAR application layer architecture provided by the above methods is implemented, and the method includes:

[0132] Divide multiple functional submodules in the initial software architecture into corresponding software components, and obtain a software component belonging information table corresponding to each functional submodule;

[0133] Obtaining input and output information, variable data types and scheduling information corresponding to each functional submodule, and obtaining a software component interface information table based on the software component belonging information table, the input and output information, the variable data types and the scheduling information;

[0134] Obtain the mapping information table of application software layer variables and basic software layer variables;

[0135] Based on the software component interface information table and the Mapping information table, an Arxml file is generated; the Arxml file includes: an application layer software component Arxml file, and an application software layer and basic software layer interface Mapping Arxml file;

[0136] Importing the Arxml file into the operating environment generation tool to generate the operating environment code;

[0137] Cutting off the global variable sharing between the software components of the initial software architecture to obtain a modified software architecture;

[0138] The modified software architecture and the operating environment code are compiled and integrated to obtain the AUROSAR application layer architecture.

[0139] Those skilled in the art will appreciate that all or part of the processes of the above-mentioned embodiments can be implemented by instructing related hardware through a computer program, and the program can be stored in a computer-readable storage medium, wherein the computer-readable storage medium is a disk, an optical disk, a read-only storage memory, or a random access memory, etc.

[0140] The AUROSAR application layer architecture generation method, device and electronic device provided by the present invention are introduced in detail above. Specific examples are used in this article to illustrate the principles and implementation methods of the present invention. The description of the above embodiments is only used to help understand the method and core idea of ​​the present invention. At the same time, for those skilled in the art, according to the idea of ​​the present invention, there will be changes in the specific implementation method and application scope. In summary, the content of this specification should not be understood as limiting the present invention.

Claims

1. A method for generating an AUROSAR application layer architecture, characterized in that: include: Divide multiple functional submodules in the initial software architecture into corresponding software components, and obtain a software component belonging information table corresponding to each functional submodule; Obtaining input and output information, variable data types and scheduling information corresponding to each functional submodule, and obtaining a software component interface information table based on the software component belonging information table, the input and output information, the variable data types and the scheduling information; Obtain the mapping information table of application software layer variables and basic software layer variables; Generate an Arxml file based on the software component interface information table and the Mapping information table; Importing the Arxml file into the operating environment generation tool to generate the operating environment code; Cutting off the global variable sharing between the software components of the initial software architecture to obtain a modified software architecture; The modified software architecture and the operating environment code are compiled and integrated to obtain the AUROSAR application layer architecture.

2. The AUROSAR application layer architecture generation method according to claim 1, characterized in that: The step of obtaining the input and output information, variable data type and scheduling information corresponding to each functional submodule, and obtaining the software component interface information table based on the software component belonging information table, the input and output information, the variable data type and the scheduling information, includes: Obtain the input and output information, variable data types and scheduling information corresponding to each sub-function module in the baseline software engineering; Based on the software component belonging information table, the input and output information, variable data types and scheduling information corresponding to each sub-functional module in the baseline software engineering are classified to obtain the interface information between the software components corresponding to each sub-functional module in the baseline software engineering, the internal information of the software components, and the interface information between the software components and the bottom layer; Obtain the input and output information, variable data types and scheduling information corresponding to the updated functional submodule; Based on the software component belonging information table, the input and output information, variable data types and scheduling information corresponding to the updated functional submodules are classified to obtain the interface information between the software components corresponding to the updated functional submodules, the internal information of the software components, and the interface information between the software components and the bottom layer; Based on the interface information between software components corresponding to each sub-functional module in the baseline software engineering, the internal information of software components, and the interface information between software components and the underlying layer, as well as the interface information between software components corresponding to the updated functional sub-modules, the internal information of software components, and the interface information between software components and the underlying layer, a software component interface information table is generated.

3. The AUROSAR application layer architecture generation method according to claim 2, characterized in that: The step of obtaining the input and output information, variable data types and scheduling information corresponding to each sub-function module in the baseline software engineering includes: Obtaining variable information and function information of each source file in the baseline software project; Based on the variable information and function information of each source file in the baseline software project, and the corresponding relationship between the main function of each functional submodule of the baseline software project and the source file, the input and output information of each functional submodule is obtained; Obtaining scheduling information corresponding to each functional submodule in the scheduling file in the baseline software project; Reverse analysis is performed on the A2L file in the baseline software project to obtain variable data types.

4. The AUROSAR application layer architecture generation method according to claim 3, characterized in that: The step of obtaining input and output information of each functional submodule based on the variable information and function information of each source file in the baseline software project and the correspondence between the main function of each functional submodule of the baseline software project and the source file includes: Based on the variable information and function information of each source file in the baseline software project, and the correspondence between the main function of each functional sub-module and the source file in the baseline software project, all reference functions of the main function of each functional sub-module are expanded in a recursive manner to obtain the input and output information of each functional sub-module.

5. The AUROSAR application layer architecture generation method according to claim 3, characterized in that: The variable information of each source file includes at least one of a global variable, a static variable and a local variable; The function information of each source file includes global functions, local functions, and referenced functions of global functions and referenced functions of local functions.

6. The AUROSAR application layer architecture generation method according to claim 2, characterized in that: The obtaining of the input and output information, variable data types and scheduling information corresponding to the updated functional submodules includes: In the case where the updated functional sub-module is a functional sub-module that has been developed, compiling the source file of the updated functional sub-module to generate the source file code of the corresponding object file; The source file code of the object file is analyzed to obtain input and output information, variable data types and scheduling information corresponding to the updated functional sub-module.

7. The AUROSAR application layer architecture generation method according to claim 2, characterized in that: The obtaining of the input and output information, variable data types and scheduling information corresponding to the updated functional submodules includes: When the updated functional submodule is an uncompleted functional submodule, a development information table corresponding to the functional submodule is obtained, and information is extracted from the development information table to obtain input and output information, variable data types and scheduling information corresponding to the updated functional submodule.

8. An AUROSAR application layer architecture generation device, characterized in that: include: The software component allocation module is used to divide multiple functional sub-modules in the initial software architecture into corresponding software components, and obtain a software component belonging information table corresponding to each functional sub-module; An interface information extraction module is used to obtain input and output information, variable data types and scheduling information corresponding to each functional submodule, and obtain a software component interface information table based on the software component belonging information table, the input and output information, the variable data type and the scheduling information; Mapping information collection module, used to obtain the mapping information table of application software layer variables and basic software layer variables; An Arxml file generation module generates an Arxml file based on the software component interface information table and the Mapping information table; An operating environment code generation module, used for importing the Arxml file into an operating environment generation tool to generate an operating environment code; The original engineering transformation module is used to cut off the global variable sharing between the software components of the initial software architecture to obtain a modified software architecture; The compilation and integration module is used to compile and integrate the modified software architecture and the operating environment code to obtain the AUROSAR application layer architecture.

9. An electronic device, characterized in that: comprising a memory and a processor, wherein: The memory is used to store programs; The processor is coupled to the memory, and is used to execute the program stored in the memory to implement the steps in the AUROSAR application layer architecture generation method according to any one of claims 1 to 7.

10. A non-transitory computer-readable storage medium having a computer program stored thereon, characterized in that: When the computer program is executed by a processor, the method for generating an AUROSAR application layer architecture according to any one of claims 1 to 7 is implemented.

Citation Information

Patent Citations

  • Model framework and interface file automation realization method based on AUTOSAR architecture

    CN113687814A

  • Automobile software module division system and method and storage medium

    CN116909542A