Application layer information management system and method based on AUTOSAR architecture

Abstract

The present invention relates to an application layer information management system and method based on AUTOSAR architecture, wherein the system comprises: a baseline engineering analysis module, a function update analysis module, a software component information extraction module and an interface information verification module: the baseline engineering analysis module is used to obtain the interface information of each submodule in the baseline software engineering; the function update analysis module is used to obtain the information of the submodules to be updated and to be added in the baseline software engineering stored in the first information table and parse it to obtain the interface information of the submodules to be updated and to be added in the baseline software engineering; the software component information extraction module is used to extract the second information table storing the submodules of the baseline software engineering, the submodule interface information, the application layer and bottom layer interaction variable information table and the interface information of the submodules to be updated in the baseline software engineering to obtain the application layer information; the interface information verification module is used to verify the application layer information to determine the accuracy of the application layer information. The present invention improves work efficiency.

Description

Technical Field

[0001] The present invention relates to the field of embedded software technology, and in particular to an application layer information management system and method based on AUTOSAR 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 enabling the reuse, exchange, upgrade and integration of software components. RTE (Run-Time Environment) 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. RTE can implement communication interfaces and provide communication services between components, so all communications between components are under the control of RTE.

[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 BSW and RTE solutions are determined, the application layer is ever-changing. The most important issue that the strategy program needs to consider is how to generate the application layer SWC and the integration of SWC and RTE. There are two mainstream AUTOSAR application layer SWC development methods: 1. "Top-down" and 2. "Bottom-up".

[0004] The "top-down" method is to generate the module arxml file by RTE first, then generate the SWC framework by arxm1, then combine the SWC framework with the model to generate SWC, then generate AUTOSAR code from the complete SWC module, and finally compile it together with the RTE code. The "bottom-up" method starts from the simulation module (simulink module), each module implements the algorithm function separately, and then configures and generates SWC code and arxml files according to the AUTOSAR method, and then combines arxml with RTE to generate RTE code, and finally compiles the code generated by RTE and SWC together.

[0005] The "bottom-up" method has shortcomings in the actual implementation process: for a continuously iterative development system, the input (inport), output (outport), scheduling and other attributes of each functional module will actually change continuously. The direct input and output mismatch of each SWC will lead to the inability to integrate the system. In a complex control system containing a large number of functional sub-modules, the update of SWC interface information requires a huge amount of work and is difficult to maintain, resulting in low work efficiency. Summary of the invention

[0006] In view of this, it is necessary to provide an application layer information management system and method based on the AUTOSAR architecture to solve the problem that updating SWC interface information requires a huge workload and is difficult to maintain, resulting in low work efficiency.

[0007] In order to solve the above problems, the present invention provides an application layer information management system and method based on the AUTOSAR architecture, including: a baseline engineering analysis module, a function update analysis module, a software component information extraction module and an interface information verification module:

[0008] The baseline engineering analysis module is used to obtain interface information of each submodule in the baseline software engineering;

[0009] The function update analysis module is used to obtain and parse the information of the submodules to be updated and added in the baseline software engineering stored in the first information table to obtain the interface information of the submodules to be updated and added in the baseline software engineering;

[0010] The software component information extraction module is used to extract the second information table storing the submodule of the baseline software engineering, the submodule interface information, the application layer and bottom layer interaction variable information table and the interface information of the submodule to be updated of the baseline software engineering to obtain the application layer information;

[0011] The interface information verification module is used to verify the application layer information to determine the accuracy of the application layer information.

[0012] In some possible implementations, the first information table includes information about sub-modules to be added to the baseline software engineering, information about sub-modules to be modified, information about sub-modules to be deleted, and information about pre-developed sub-modules, and the second information table includes information about the classification and division of software components of the baseline software engineering.

[0013] In some possible implementations, the baseline engineering analysis module includes a first source code analysis module, a scheduling analysis module, and a variable data type reverse analysis module:

[0014] The first source code analysis module is used to obtain the baseline software engineering source file information;

[0015] The scheduling analysis module is used to obtain information of the baseline software engineering scheduling file;

[0016] The variable data type reverse analysis module is used to obtain the baseline software engineering description file information.

[0017] In some possible implementations, the baseline software engineering source file information includes: global variables, static variables, local variables, global function information, and local function information of the baseline software engineering source file.

[0018] In some possible implementations, the information of the baseline software engineering scheduling file includes: the scheduling period and scheduling order of each sub-module of the baseline software engineering.

[0019] In some possible implementations, the function update analysis module includes a second source code analysis module, a scheduling update module, a data type information extraction module, a model interface information extraction module, and a pre-development information processing module:

[0020] The second source code analysis module is used to obtain and parse the source files of the sub-modules to be updated and added in the baseline software engineering through the first information table to obtain the first interface information of the sub-modules;

[0021] The data type information extraction module is used to obtain the updated or newly added sub-module variable data type information of the baseline software engineering from the first information table;

[0022] The model interface information extraction module is used to obtain the updated or newly added sub-module model and data dictionary file based on model development of the baseline software engineering through the first information table and parse them to obtain the sub-module second interface information;

[0023] The pre-development information processing module is used to obtain interface information of the pre-development sub-module based on the baseline software engineering from the first information table;

[0024] The scheduling update module is used to obtain scheduling information from the first information table, and synchronously update the scheduling information to the scheduling information of the application layer of the baseline software engineering.

[0025] In some possible implementations, the information of the updated or newly added submodule based on the baseline software engineering includes the function name, scheduling information, source file path and variable data type of the updated or newly added submodule;

[0026] The information of the updated or newly added model-based development submodule based on the baseline software engineering includes the function name, scheduling information and source file, model, and data dictionary file path of the updated or newly added submodule;

[0027] The information of the pre-developed sub-module of the baseline software engineering includes the function name, scheduling information, input variable name, output variable name and data type of the pre-developed sub-module.

[0028] In some possible implementations, the application layer information includes one or more of information between software components, interface information between software components and underlying interfaces, and execution scheduling information and execution core ID information of functions within software components.

[0029] On the other hand, the present invention also provides an application layer information management method based on the AUTOSAR architecture, comprising:

[0030] Obtain interface information of each submodule in the baseline software project;

[0031] Obtaining and parsing the information of the submodules to be updated and added in the baseline software project stored in the second information table to obtain the interface information of the submodules to be updated in the baseline software project;

[0032] Extracting the second information table storing the submodule of the baseline software engineering, the submodule interface information, the application layer and bottom layer interaction variable information table and the interface information of the submodule to be updated of the baseline software engineering to obtain application layer information;

[0033] The application layer information is verified to determine the accuracy of the application layer information.

[0034] The beneficial effect of adopting the above embodiment is: the application layer information management system based on the AUTOSAR architecture provided by the present invention includes: a baseline engineering analysis module, a function update analysis module, a software component information extraction module and an interface information verification module, the baseline engineering analysis module is used to obtain the interface information of each sub-module in the baseline software engineering, the function update analysis module is used to obtain the information of the sub-modules to be updated and to be added in the baseline software engineering stored in the first information table and parse it to obtain the interface information of the sub-modules to be updated and to be added in the baseline software engineering, the software component information extraction module is used to extract the second information table storing the sub-modules of the baseline software engineering, the sub-module interface information, the application layer and bottom layer interaction variable information table and the interface information of the sub-modules to be updated in the baseline software engineering to obtain the application layer information, and the interface information verification module is used to verify the application layer information to determine the accuracy of the application layer information. The present invention obtains the interface information of the submodules of the baseline software engineering and the interface information of the submodules of the baseline software engineering that need to be updated in the function development update information table, and finally combines the interface information of the submodules of the updated baseline software engineering, the second information table of the software components of the baseline software engineering, and the application layer and bottom layer interaction variable information table to obtain application layer information. The present invention adopts a top-down method to store the information in the table, and then merges the information in the table to obtain the application layer information, so as to realize the management of the software component information and improve the work efficiency. BRIEF DESCRIPTION OF THE DRAWINGS

[0035] Figure 1 A schematic diagram of the structure of an embodiment of an application layer information management system based on AUTOSAR architecture provided by the present invention;

[0036] Figure 2 A schematic diagram of an embodiment of an application layer information management method based on AUTOSAR architecture provided by the present invention;

[0037] Figure 3 A schematic diagram of the structure of an embodiment of an application layer information management device based on AUTOSAR architecture provided by the present invention;

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

[0039] The preferred embodiments of the present invention are described in detail below in conjunction with the accompanying drawings, wherein the accompanying drawings constitute a part of this application and are used together with the embodiments of the present invention to illustrate the principles of the present invention, but are not used to limit the scope of the present invention.

[0040] Figure 1 A schematic diagram of an embodiment of an application layer information management system based on AUTOSAR architecture provided by the present invention is shown in FIG. Figure 1 As shown, an application layer information management system 100 based on the AUTOSAR architecture includes: a baseline engineering analysis module 101, a function update analysis module 102, a software component information extraction module 103 and an interface information verification module 104:

[0041] The baseline engineering analysis module 101 is used to obtain interface information of each submodule in the baseline software engineering;

[0042] The function update analysis module 102 is used to obtain and parse the information of the to-be-updated and to-be-added submodules of the baseline software engineering stored in the first information table to obtain the interface information of the to-be-updated and to-be-added submodules of the baseline software engineering;

[0043] The software component information extraction module 103 is used to extract the second information table storing the submodule of the baseline software engineering, the submodule interface information, the application layer and bottom layer interaction variable information table and the interface information of the submodule to be updated of the baseline software engineering to obtain the application layer information;

[0044] The interface information verification module 104 is used to verify the application layer information to determine the accuracy of the application layer information.

[0045] Compared with the prior art, the present embodiment provides an application layer information management system based on the AUTOSAR architecture, comprising: a baseline engineering analysis module, a function update analysis module, a software component information extraction module and an interface information verification module, wherein the baseline engineering analysis module is used to obtain interface information of each sub-module in the baseline software engineering, the function update analysis module is used to obtain information of sub-modules to be updated and to be added in the baseline software engineering stored in the function development update information table and parse it to obtain interface information of sub-modules to be updated and to be added in the baseline software engineering, the software component information extraction module is used to extract the software component second information table of the sub-modules storing the baseline software engineering, the sub-module interface information, the application layer and bottom layer interaction variable information table and the interface information of the sub-modules to be updated in the baseline software engineering to obtain application layer information, and the interface information verification module is used to verify the application layer information to determine the accuracy of the application layer information. The present invention obtains the submodule interface information of the baseline software engineering and the interface information of the submodule of the baseline software engineering that needs to be updated in the first information table, and finally combines the updated submodule interface information of the baseline software engineering, the second information table of the baseline software engineering, and the application layer and bottom layer interactive variable information table to obtain application layer information. The present invention adopts a top-down method to store information in a table, and then merges the information in the table to obtain application layer information, thereby realizing the management of software component information and improving work efficiency.

[0046] It should be noted that software components (SWC) are generally located in the Application layer of the AUTOSAR architecture.

[0047] In some embodiments of the present invention, the first information table includes information about sub-modules to be added to the baseline software engineering, information about sub-modules to be modified, information about sub-modules to be deleted, and information about pre-developed sub-modules, and the second information table includes information about the classification and division of software components of the baseline software engineering.

[0048] In some embodiments of the present invention, the baseline engineering analysis module 101 includes a first source code analysis module 1010, a scheduling analysis module 1011, and a variable data type reverse analysis module 1012:

[0049] The first source code analysis module 1010 is used to obtain the baseline software engineering source file information;

[0050] The scheduling analysis module 1011 is used to obtain information of the baseline software engineering scheduling file;

[0051] The variable data type reverse analysis module 1012 is used to obtain the baseline software engineering preset description file information.

[0052] In a specific embodiment of the present invention, the preset description file is an A21 file.

[0053] In some embodiments of the present invention, the baseline software engineering source file information includes: global variables, static variables, local variables, global function information and local function information of the baseline software engineering source file.

[0054] In a specific embodiment of the present invention, the global function information includes the input variables of the global function and the output variables of the global function. The local function information includes the input variables of the local function and the output variables of the local function.

[0055] In some embodiments of the present invention, the information of the baseline software engineering scheduling file includes: the scheduling period and scheduling order of each sub-module of the baseline software engineering.

[0056] In a specific embodiment of the present invention, the sub-functional modules of the baseline software engineering are divided into software components, i.e., SWC division, to obtain an information table of SWC division of the sub-modules of the baseline software engineering, i.e., a second information table. The information table of SWC division of the sub-functional modules of the baseline software engineering includes the sub-functional module information of the baseline software engineering and also includes the information of the sub-functional modules to be newly added. For example, a complex control system contains 1000 functional sub-modules, which belong to 6 SWCs. The division information table of these 1000 sub-functional modules is output. Among these 1000 functional sub-modules, 990 exist in the existing baseline software engineering and 10 are newly added sub-functional modules.

[0057] In a specific embodiment of the present invention, the baseline engineering analysis module 101 is used to obtain interface information of each submodule in the baseline software engineering, including:

[0058] The first source code analysis module 1010 compiles the source files of the baseline software project to generate object files and automatically analyzes the code lines of the source files themselves. Each source file of the baseline software project includes the source file's global variables, static variables, local variables, global functions, local functions, and the input and output variables and referenced function information of each global function and local function, and the input and output variables and referenced function information of each global function and local function. The corresponding relationship between the main function of the sub-function module of the baseline software project and the source file is recursively expanded in a layer-by-layer manner to obtain the input and output variable information of the main function of the sub-function module. For example, a software project containing 1000 sub-function modules may contain 3000 source files. The implementation first analyzes and obtains the functions and corresponding inputs and outputs contained in the 3000 source files. For example, 6000 functions are obtained from the 3000 source files. The input and output of these functions are obtained, and then the input and output variable information of the main functions of 1000 sub-function modules are obtained respectively according to the main function name information of the sub-function module obtained in the fourth step. For example, the main function name of the function sub-module A is main_function_A, the input is input_A, the output is output_A, and the internal reference is function_a. The input of function_a is input_a, and the output is output_a. Function_a internally references function_b, and the input of function_b is input_b, and the output is output_b. The following may also be nested function_c..., then after being processed by the source code analysis module, the input of sub-function module A is obtained as input_A, input_a, input_b..., and the output is output_A, output_a, output_b...;

[0059] The scheduling analysis module obtains the main function name of the sub-function module in the baseline software engineering scheduling file, and the corresponding scheduling cycle, scheduling order and other information;

[0060] The A2L file variable data type reverse analysis module 1012 performs reverse analysis on the A2L file in the baseline software project to obtain the data types of the variables involved, such as signed, unsigned, data length, dimension and other information. Among them, the implementation process of the A2l file variable data type reverse analysis module is as follows: according to the ASAP2 standard, the variable name, address, length, calculation formula, precision, maximum and minimum values ​​of the observed variables and calibrated variables are described in a specific paradigm in the A2L file, and the corresponding information is defined in the field blocks marked by keywords, such as: MEASUREMENT is used to define the measurement variable, CHARACTERISTIC is used to define the calibration variable, COMPU_METHOD is used to define the calculation formula, that is, the conversion relationship between the original value and the physical value, COMPU_TAB is generally used for the mapping relationship between the original value and the physical value of the enumeration variable, RECORD_LAYOUT is used to define the physical storage structure of the calibration variable (single variable, two-dimensional table, three-dimensional table, etc.), use the script to match the keyword to search, find the description field related to the specific variable, and extract the symbol, unsigned, data length, dimension and other information.

[0061] In some embodiments of the present invention, the function update analysis module 102 includes a second source code analysis module 1020, a scheduling update module 1021, a data type information extraction module 1022, a model interface information extraction module 1023, and a pre-development information processing module 1024:

[0062] The second source code analysis module 1020 is used to obtain and parse the source files of the submodules to be updated and added in the baseline software project through the first information table to obtain the first interface information of the submodules;

[0063] The data type information extraction module 1021 is used to obtain the updated or newly added sub-module variable data type information of the baseline software engineering from the first information table;

[0064] The model interface information extraction module 1022 is used to obtain the updated or newly added sub-module model and data dictionary file based on model development of the baseline software engineering through the first information table and parse them to obtain the sub-module second interface information;

[0065] The pre-development information processing module 1023 is used to obtain interface information of the pre-development sub-module based on the baseline software engineering from the first information table;

[0066] The scheduling update module 1024 is used to obtain scheduling information from the first information table, and synchronously update the scheduling information to the scheduling information of the application layer of the baseline software engineering.

[0067] In some embodiments of the present invention, the information of the updated or newly added submodule based on the baseline software engineering includes the function name, scheduling information, source file path and variable data type of the updated or newly added submodule;

[0068] The information of the updated or newly added model-based development submodule based on the baseline software engineering includes the function name, scheduling information and source file, model, and data dictionary file path of the newly added submodule;

[0069] The information of the pre-developed sub-module of the baseline software engineering includes the function name, scheduling information, input variable name, output variable name and data type of the pre-developed sub-module.

[0070] It should be noted that the software component is the SWC in AUTOSAR. In some embodiments of the present invention, the application layer information includes one or more of information between software components, interface information between software components and underlying interfaces, and operation scheduling information and operation core ID information of functions in software components.

[0071] In a specific embodiment of the present invention, the first information table, i.e., the function development update information table, includes three categories: the first category is newly added sub-function modules, the second category is updated sub-modules, and the third category is deleted sub-function modules:

[0072] For the first type of newly added sub-function modules, it includes the main function name of the newly added sub-function module, scheduling information, data dictionary file and other information. 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 (handwritten code is not available), data dictionary file, and the second category is the sub-function modules that have not been completed but have basic input and output infrastructure design and scheduling presets.

[0073] For the newly added sub-function modules of the first category that have been developed, the source code analysis module can be used to automatically analyze the object files generated by compiling the source files and the code lines of the source files themselves to obtain the input and output variable information of the newly added sub-function modules. If it is a handwritten code, the data type information extraction module is used to read the function development update information table in a specific format to obtain the data type definition information of the newly added variables. The sub-function modules with models can also read the model and data dictionary files, such as Simulink models, through the model interface information extraction module to automatically obtain the input and output variables and data type information of the sub-function modules;

[0074] For the second type of sub-function modules that only have pre-development information, 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 and data type information of the sub-function module; the scheduling update module is used to obtain the scheduling information from the function development update information table with a specific format, and the scheduling information is synchronously updated to the scheduling period, scheduling order and other information obtained in the baseline engineering analysis module.

[0075] For the second type of updated sub-module, including the updated sub-module code, model, data dictionary file path, and scheduling change information, specifically, the second source code analysis module, data type information extraction module or model interface information extraction module is used to obtain the input and output variable information and data type information of the sub-function module; the scheduling update module is used to obtain the scheduling information from the function development update information table in a specific format, and the scheduling information is synchronously updated to the scheduling period, scheduling order and other information obtained in the baseline engineering analysis module.

[0076] For the third type of deleted sub-function modules, the sub-function module information needs to be deleted from the baseline project, and the scheduling information is synchronously updated to the scheduling cycle, scheduling sequence and other information obtained in the baseline project analysis module, that is, the scheduling information of the sub-module is deleted.

[0077] In a specific embodiment of the present invention, it is also necessary to prepare an application layer and bottom layer interaction variable information table, which includes variable names and transmission direction information.

[0078] In a specific embodiment of the present invention, the sub-function module SWC belonging division information table of the baseline software engineering, i.e., the software component belonging information table, the application layer bottom layer interaction variable information, the sub-module interface information, the application layer and bottom layer interaction variable information table and the updated sub-module interface information are combined, and the sub-function module interface is integrated using the SWC information extraction module to obtain the interface information between SWCs (including output, input information, etc.), the interface information between SWC and the bottom layer (including input, output, etc.), the internal information of SWC (including runnable name, scheduling cycle, scheduling order, SWC interaction variable information involved in the runnable and the interaction information with the bottom layer, etc.), and the variable data type information. For example, if 1000 functional sub-modules are divided into 6 SWCs, a large number of interaction variables between sub-function modules that only exist in the same SWC will be internalized and not used as SWC ports;

[0079] In a specific embodiment of the present invention, an interface information verification module is used to verify the obtained application layer information:

[0080] 1. Check whether the output variables of the sub-function module corresponding to the runnable are repeated. For example, if the variable var_a is the output of runnable 1 and runnable 2, it does not comply with the AUTOSAR specification and needs to be modified.

[0081] 2. Whether the SWC input and output are not closed-loop, for example, whether the input portvar_a of SWC A is the output of other SWCs;

[0082] 3. The application layer and bottom layer interfaces are not enabled. Whether the application layer and bottom layer interface information entered in the third step are all reflected in the application layer information;

[0083] 4. Whether all variables involved in SWC have data type definitions;

[0084] 5. Check whether the data dictionary files provided by each sub-function module are inconsistent with the data types in the source code. The specific implementation method is to extract the data length and type information from the compiled target file or source text file and compare it with the data dictionary file;

[0085] In a specific embodiment of the present invention, the process of the baseline engineering analysis module and the function update analysis module is an automated process implemented by computer scripts. The source of the problem found in the verification is an error in the manually sorted information table or a newly added function module design problem. Therefore, after the automated verification, it is necessary to manually analyze the problems reported in the automated verification, and correct the corresponding initial information or module design according to different problem sources;

[0086] The application layer interface information obtained above supports RTE file generation. Functional module codes and RTE codes jointly participate in AUTOSAR architecture software integration.

[0087] The updated software project can be used as the baseline project for the next application layer interface information update. The basis for each application layer interface information update is the baseline project rather than the previous version of the application layer interface information file. The advantage of this is that the basic information of each version is directly derived from the software project file, which can eliminate the problem of decoupling information file maintenance from software project status and ensure the accuracy of application layer interface information.

[0088] On the other hand, Figure 2 A schematic diagram of an embodiment of an application layer information management method based on the AUTOSAR architecture provided by the present invention, an application layer information management method based on the AUTOSAR architecture, comprising:

[0089] S201, obtaining interface information of each submodule in the baseline software project;

[0090] S202, obtaining and parsing the information of the submodules to be updated and to be added of the baseline software engineering stored in the first information table, and obtaining the interface information of the submodules to be updated and to be added of the baseline software engineering;

[0091] S203, extracting the second information table storing the submodule of the baseline software engineering, the submodule interface information, the application layer and bottom layer interaction variable information table and the interface information of the submodule to be updated of the baseline software engineering to obtain application layer information;

[0092] S204: Verify the application layer information to determine the accuracy of the application layer information.

[0093] In order to better implement an application layer information management method based on the AUTOSAR architecture in an embodiment of the present invention, based on an application layer information management method based on the AUTOSAR architecture, correspondingly, as Figure 3 As shown, the embodiment of the present invention further provides an application layer information management device 300 based on the AUTOSAR architecture, comprising:

[0094] Baseline engineering analysis module 301, used to obtain interface information of each submodule in the baseline software engineering;

[0095] Function update analysis module 302, used to obtain and parse the information of the submodules to be updated and added in the baseline software engineering stored in the first information table, and obtain interface information of the submodules to be updated and added in the baseline software engineering;

[0096] The software component information extraction module 303 is used to extract the second information table storing the submodule of the baseline software engineering, the submodule interface information, the application layer and bottom layer interaction variable information table and the interface information of the submodule to be updated of the baseline software engineering to obtain the application layer information;

[0097] The interface information verification module 304 is used to verify the application layer information to determine the accuracy of the application layer information.

[0098] The application layer information management device 300 based on the AUTOSAR architecture provided in the above embodiment can implement the technical solution described in the above embodiment of an application layer information management method based on the AUTOSAR architecture. The specific implementation principles of the above modules or units can refer to the corresponding contents in the above embodiment of an application layer information management method based on the AUTOSAR architecture, which will not be repeated here.

[0099] 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 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.

[0100] 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 stored in the memory 402 or process data, such as an application layer information management method based on the AUTOSAR architecture in the present invention.

[0101] In some embodiments, the processor 401 may be a single server or a server group. The server group may be centralized or distributed. In some embodiments, the processor 401 may be local or remote. In some embodiments, the processor 401 may be implemented in a cloud platform. In one embodiment, the cloud platform may include a private cloud, a public cloud, a hybrid cloud, a community cloud, a distributed cloud, an internal cloud, a multi-cloud, etc., or any combination thereof.

[0102] 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 media card (SMC), a secure digital (SD) card, a flash card, etc., equipped on the electronic device 400.

[0103] Furthermore, the memory 403 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.

[0104] 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.

[0105] In one embodiment, when the processor 401 executes an application layer information management program based on the AUTOSAR architecture in the memory 402, the following steps may be implemented:

[0106] Obtain interface information of each submodule in the baseline software project;

[0107] Obtaining and parsing the information of the submodules to be updated and added in the baseline software engineering stored in the first information table to obtain the interface information of the submodules to be updated and added in the baseline software engineering;

[0108] Extracting the second information table storing the submodule of the baseline software engineering, the submodule interface information, the application layer and bottom layer interaction variable information table and the interface information of the submodule to be updated of the baseline software engineering to obtain application layer information;

[0109] The application layer information is verified to determine the accuracy of the application layer information.

[0110] It should be understood that: when the processor 401 executes an application layer information management program based on the AUTOSAR architecture in the memory 402 , in addition to the above functions, other functions may also be implemented, for details, see the description of the corresponding method embodiment above.

[0111] 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 devices 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).

[0112] 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.

[0113] The above description is only a preferred specific implementation manner of the present invention, but the protection scope of the present invention is not limited thereto. Any changes or substitutions that can be easily conceived by any technician familiar with the technical field within the technical scope disclosed by the present invention should be covered within the protection scope of the present invention.

Claims

1. An application layer information management system based on AUTOSAR architecture, characterized in that: include: Baseline engineering analysis module, function update analysis module, software component information extraction module and interface information verification module: The baseline engineering analysis module is used to obtain interface information of each submodule in the baseline software engineering; The function update analysis module is used to obtain and parse the information of the submodules to be updated and added of the baseline software engineering stored in the first information table to obtain the interface information of the submodules to be updated and added of the baseline software engineering, wherein the first information table includes the information of the submodules to be added, the information of the submodules to be modified, the information of the submodules to be deleted, and the information of the pre-developed submodules of the baseline software engineering; The software component information extraction module is used to extract the application layer information from the second information table storing the submodules in the baseline software project, the interface information of each submodule in the baseline software project, the application layer and bottom layer interaction variable information table, and the interface information of the submodules to be updated and added in the baseline software project, wherein the second information table includes the software component classification information of the baseline software project; The interface information verification module is used to verify the application layer information to determine the accuracy of the application layer information. The application layer information includes one or more of information between software components, interface information between software components and underlying interfaces, and running scheduling information and running core ID information of functions within software components.

2. The application layer information management system based on AUTOSAR architecture according to claim 1, characterized in that: The baseline engineering analysis module includes a first source code analysis module, a scheduling analysis module, and a variable data type reverse analysis module: The first source code analysis module is used to obtain the baseline software engineering source file information; The scheduling analysis module is used to obtain information of the baseline software engineering scheduling file; The variable data type reverse analysis module is used to obtain the baseline software engineering description file information.

3. The application layer information management system based on AUTOSAR architecture according to claim 2, characterized in that: The baseline software engineering source file information includes: global variables, static variables, local variables, global function information and local function information of the baseline software engineering source file.

4. The application layer information management system based on AUTOSAR architecture according to claim 2, characterized in that: The information of the baseline software engineering scheduling file includes: the scheduling period and scheduling order of each submodule of the baseline software engineering.

5. The application layer information management system based on AUTOSAR architecture according to claim 1, characterized in that: The function update analysis module includes a second source code analysis module, a scheduling update module, a data type information extraction module, a model interface information extraction module, and a pre-development information processing module: The second source code analysis module is used to obtain and parse the source files of the sub-modules to be updated and added in the baseline software engineering through the first information table to obtain the first interface information of the sub-modules; The data type information extraction module is used to obtain variable data type information of submodules to be updated and added in the baseline software engineering from the first information table; The model interface information extraction module is used to obtain the model and data dictionary files of the sub-modules to be updated and newly added based on model development of the baseline software engineering through the first information table and parse them to obtain the second interface information of the sub-modules; The pre-development information processing module is used to obtain interface information of the pre-development sub-module based on the baseline software engineering from the first information table; The scheduling update module is used to obtain scheduling information from the first information table, and synchronously update the scheduling information to the scheduling information of the application layer of the baseline software engineering.

6. The application layer information management system based on AUTOSAR architecture according to claim 5, characterized in that: The information of the submodules to be updated and to be added of the baseline software engineering includes the function names, scheduling information, source file paths and variable data types of the submodules to be updated and to be added; The information of the submodules to be updated and added based on model development of the baseline software engineering includes the function name, scheduling information and source file, model, and data dictionary file path of the submodule to be added; The interface information of the pre-developed sub-module of the baseline software engineering includes the function name, scheduling information, input variable name, output variable name and data type of the pre-developed sub-module.

7. An application layer information management method based on AUTOSAR architecture, characterized in that: include: Obtain interface information of each submodule in the baseline software project; Obtaining and parsing the information of the submodules to be updated and added of the baseline software engineering stored in the first information table to obtain the interface information of the submodules to be updated and added of the baseline software engineering, wherein the first information table includes the information of the submodules to be added, the information of the submodules to be modified, the information of the submodules to be deleted, and the information of the pre-developed submodules of the baseline software engineering; Extracting the second information table of software components of the submodules storing the baseline software project, the interface information of each submodule in the baseline software project, the application layer and bottom layer interaction variable information table, and the interface information of the submodules to be updated and added in the baseline software project to obtain application layer information, wherein the second information table includes the software component classification information of the baseline software project; The application layer information is verified to determine the accuracy of the application layer information, wherein the application layer information includes one or more of information between software components, interface information between software components and underlying interfaces, and operation scheduling information and operation core ID information of functions within software components.

Images