Integrated interface system of AUTOSAR model editing tool

Abstract

The invention relates to the technical field of embedded systems, in particular to an integrated interface system of an AUTOSAR model editing tool, and the system comprises a component storage module which collects and stores prefabricated component information; the configuration module responds to an externally input editing instruction to configure the prefabricated component information to obtain system service elements; the debugging operation module is used for performing operation and debugging according to the system service elements; and the output module is used for packaging and outputting the debugged system service elements. In order to solve the problems that in the prior art, an AUTOSAR editing system is relatively single in function and relatively split in development process, the editing system is introduced in the scheme, a graphical editing interface is provided, so that a user can configure the information of the prefabricated component through the configuration module, then the debugging operation module operates the debugging process, and the debugging efficiency is improved. And finally, packaging and outputting are performed, so that integration of a plurality of development links is realized, and the user experience is improved.

Description

Technical Field

[0001] The present invention relates to the technical field of embedded systems, and in particular to an integrated interface system of an AUTOSAR model editing tool. Background Art

[0002] AUTOSAR (Automotive Open System ARchitecture) is an automotive open system architecture jointly established and designed by global automobile manufacturers, component suppliers and other electronic, semiconductor and software system companies. This software architecture separates the hardware and software of the device, puts the functional model software and software components together, and is independent of each other and developed by different manufacturers, and then combines them into a specific project through some automatic configuration processes. The separation between hardware and software and different software components is carried out through the basic software package (Basic Software-ware), which is composed of the microcontroller abstraction layer and the controller abstraction layer (ECU and microcontroller hardware abstraction layer HAL) and independent service layers (such as operating system, communication protocol and memory management).

[0003] In the prior art, in order to enable the vehicle system to operate normally and realize the expected functions, it is usually necessary to edit, modify and adjust the mutual relationship between the components provided by the AUTOSAR model during the development process. For example, Chinese patent CN201811194297.4 discloses an integrated ECU embedded target code automatic generator and automatic generation method, which belongs to the field of diesel engine ECU software special development platform. The target code automatic generator consists of Simulink underlying interface module, underlying driver library file, main process control script, calibration measurement file generation script, report generation script, Simulink code generation plug-in, model calibration measurement definition file, model configuration and operation script. It can realize the one-click integration of control strategy model and underlying basic software in the engine electronic control unit ECU software development process and the automatic generation and compilation of embedded product code, simplify the generation process of ECU execution software, save the time of human participation in software integration and product code generation, and the control strategy model and basic software are developed in parallel and divided into work and cooperated, which can shorten the development cycle of ECU software products and improve development efficiency.

[0004] However, in the actual implementation process, the inventors found that the above development software usually focuses on editing and generating the code part, and lacks the ability to integrate model editing, code generation, breakpoint debugging, running status monitoring, and packaging deployment into a unified integrated development environment. This has led to the fragmentation of the development process, increased the development cycle, and reduced efficiency. Summary of the invention

[0005] In view of the above problems existing in the prior art, an integrated interface system of an AUTOSAR model editing tool is now provided.

[0006] The specific technical solutions are as follows:

[0007] An integrated interface system for AUTOSAR model editing tools, comprising:

[0008] A component storage module, in which prefabricated component information is collected and stored;

[0009] A configuration module, the configuration module is connected to the component storage module, and the configuration module configures the prefabricated component information in response to an externally input editing instruction to obtain a system service element;

[0010] A debugging and running module, the debugging and running module is connected to the configuration module, and the debugging and running module runs and debugs according to the system service element;

[0011] An output module, wherein the output module is connected to the debugging and running module, and the output module packages and outputs the debugged system service elements.

[0012] On the other hand, the component storage module includes:

[0013] A component entry module, wherein the component entry module obtains prefabricated system components;

[0014] A component marking module, the component marking module is connected to the component entry module, and the component marking module respectively records the structural information between the prefabricated system components and adds component identification;

[0015] An index building module, the index building module is connected to the component marking module, and the index building module builds an index according to the component identification and the structural information and adds it to the prefabricated component information.

[0016] On the other hand, the configuration module includes:

[0017] A model finder, wherein the model finder obtains the corresponding prefabricated system component according to the editing instruction;

[0018] A model editor is connected to the model finder, and the model editor edits a plurality of the prefabricated system components according to the editing instructions to form the system service element.

[0019] On the other hand, the configuration module also includes:

[0020] A setting interface, wherein the setting interface is respectively connected to the model finder and the model editor;

[0021] The setting interface obtains the interface operation instruction input from the outside, and generates the editing instruction according to the interface operation instruction and inputs it into the model finder and the model editor;

[0022] The setting interface receives and displays the output results of the model finder and the model editor;

[0023] The first output result of the model finder is the found prefabricated system component, the structural information associated with the prefabricated system component, and the component identifier;

[0024] The second output result of the model editor is the editing result of the prefabricated system components and the structural information.

[0025] In another aspect, the model finder comprises:

[0026] A search parameter determination module, wherein the search parameter determination module determines the search parameters currently used for searching the prefabricated system components according to the editing command;

[0027] The search parameters include scope, type, and FQN;

[0028] A field selection module, the field selection module is connected to the search parameter determination module, and the field selection module determines a corresponding component field in the component storage module according to the search parameter;

[0029] A matching module, the matching module is connected to the field selection module, and the matching module matches the component field according to the editing command to obtain the corresponding prefabricated system component.

[0030] In another aspect, the model editor comprises:

[0031] A proxy model generation module, wherein the proxy model generation module generates a proxy model according to the prefabricated system components;

[0032] a proxy model editing module, the proxy model editing module being connected to the proxy model generating module, and the proxy model editing module modifying the configuration information of the proxy model according to the editing command;

[0033] The configuration information includes model configuration information of the proxy model, the structural information of other proxy models associated with the proxy model, and the model configuration information of other proxy models associated with the proxy model.

[0034] On the other hand, the debug run module includes:

[0035] A device proxy configuration module, wherein the device proxy configuration module creates a device process for each input system service element;

[0036] An instance running module, wherein the instance configuration module is connected to the device proxy configuration module, and the instance configuration module creates a machine instance according to the device process and runs the machine instance;

[0037] A monitoring module, the monitoring module is connected to the instance running module, the monitoring module obtains the running status of the machine instance and generates debugging information;

[0038] A display module is connected to the monitoring module, and the display module obtains and displays the debugging information.

[0039] On the other hand, the output module comprises:

[0040] A cutting module, which cuts the debugged system service elements and creates an export task;

[0041] A task queue module, the task queue module is connected to the cutting module, and the task queue module obtains and stores the export task;

[0042] An export thread creation module is connected to the task queue module, and the export thread creation module obtains the export task and creates a corresponding execution thread to run.

[0043] The above technical solution has the following advantages or beneficial effects:

[0044] In view of the problem that the AUTOSAR editing system in the prior art has relatively single functions and relatively fragmented development processes, this solution introduces the above-mentioned editing system. By providing a graphical editing interface, users can configure the prefabricated component information through the configuration module, and then switch to the debugging and running module to perform the running and debugging process, and finally package and output it, thereby realizing the integration of multiple development links and improving the user experience. BRIEF DESCRIPTION OF THE DRAWINGS

[0045] The embodiments of the present invention will be described more fully with reference to the attached drawings, which are provided for illustration and description only and are not intended to limit the scope of the present invention.

[0046] Figure 1 It is an overall schematic diagram of an embodiment of the present invention;

[0047] Figure 2 This is a schematic diagram of a component storage module in an embodiment of the present invention;

[0048] Figure 3 A schematic diagram of a configuration module in an embodiment of the present invention;

[0049] Figure 4 A schematic diagram of setting an interface in an embodiment of the present invention;

[0050] Figure 5 A schematic diagram of a model finder in an embodiment of the present invention;

[0051] Figure 6 A schematic diagram of a model editor in an embodiment of the present invention;

[0052] Figure 7 This is a schematic diagram of a debugging operation module in an embodiment of the present invention;

[0053] Figure 8 Schematic diagram of an output module in an embodiment of the present invention. DETAILED DESCRIPTION

[0054] The following will be combined with the drawings in the embodiments of the present invention to clearly and completely describe the technical solutions 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 ordinary technicians in this field without creative work are within the scope of protection of the present invention.

[0055] It should be noted that, in the absence of conflict, the embodiments of the present invention and the features in the embodiments may be combined with each other.

[0056] The present invention will be further described below in conjunction with the accompanying drawings and specific embodiments, but they are not intended to limit the present invention.

[0057] The present invention comprises:

[0058] An integrated interface system for AUTOSAR model editing tools, such as Figure 1 As shown, including:

[0059] Component storage module 1, in which prefabricated component information is collected and stored;

[0060] Configuration module 2, configuration module 2 is connected to component storage module 2, configuration module 3 is connected to component storage module 1, and configuration module 2 configures the prefabricated component information in response to the external input editing instruction to obtain the system service element;

[0061] The debugging and running module 3 is connected to the configuration module 2, and the debugging and running module 3 runs and debugs according to the system service elements;

[0062] Output module 4, output module 4 is connected to debugging and running module 3, and output module 4 packages and outputs the debugged system service elements.

[0063] Specifically, in response to the problem that the AUTOSAR editing system in the prior art has relatively single functions and relatively fragmented development processes, this solution introduces the above-mentioned integrated interface system, integrates multiple links in the development process, and provides a graphical editing interface to improve development efficiency. Specifically, the component storage module 1 pre-collects and stores the prefabricated component information of the AUTOSAR system architecture. Users can configure the prefabricated component information through the configuration module 2, including modifying the configuration, specifying the scope, adjusting the structural relationship between components, etc., so as to form a system service element that meets the requirements. Then the debugging and running module 3 is turned to run the debugging process, and finally the output module 4 is packaged and output, which realizes the integration of multiple development links and improves the user experience.

[0064] In one embodiment, Figure 2 As shown, the component storage module 1 includes:

[0065] A component input module 11, the component input module 11 obtains prefabricated system components;

[0066] A component marking module 12, the component marking module 12 is connected to the component input module 11, and the component marking module 12 respectively records the structural information between the prefabricated system components and adds component identification;

[0067] The index building module 13 is connected to the component marking module 12. The index building module 13 builds an index according to the component identification and structure information and adds it to the prefabricated component information.

[0068] Specifically, in order to achieve a better input process of prefabricated system components, in this embodiment, two configuration files are first set in the component storage module 1, including components.json and .isoftap. Among them, the components.json file defines the structural information between prefabricated components and marks a unique identification id for each group of prefabricated components. The .isoftap file is stored in the project directory, and the id of the prefabricated components that the project depends on is recorded in the file, which is used as an index file.

[0069] Based on the above two files, the component entry module 11 first obtains the prefabricated system component. The extraction process includes loading the arxml file of the prefabricated system component into the memory model, and then judging whether the currently loaded prefabricated system component has been entered into the index file .isoftap through the model scope. If it has been entered, it will be removed.

[0070] The component marking module 12 records the structural information between the prefabricated system components and adds the component identification. The above two sets of information are recorded in the components.json file. Then, the index construction module 13 constructs an index according to the component identification and structural information and adds it to the prefabricated component information, which is saved in the .isoftap file.

[0071] Correspondingly, a corresponding resource tab of component storage module 1 will be created in the front-end display interface. The data displayed in the resource tab is the structural data defined in the components.json file. The model scope of the project can be dynamically adjusted by modifying the prefabricated component id recorded in the .isoftap file under the project.

[0072] In one embodiment, Figure 3 As shown, the configuration module 2 includes:

[0073] A model finder 21, the model finder 21 obtains the corresponding prefabricated system component according to the editing instruction;

[0074] The model editor 22 is connected to the model finder 21. The model editor 22 edits a plurality of prefabricated system components according to editing instructions to form system service elements.

[0075] Specifically, to achieve a better model configuration process, in this embodiment, the model finder 21 first obtains the corresponding prefabricated system components according to the editing instructions, and then the model editor 22 edits multiple prefabricated system components according to the editing instructions to form system service elements.

[0076] At the same time, in order to achieve a better operation process, such as Figure 4 As shown, the configuration module 2 also includes:

[0077] A setting interface 23, the setting interface 23 is connected to the model finder 21 and the model editor 22 respectively;

[0078] The setting interface 23 obtains the interface operation instruction input from the outside, and generates the editing instruction according to the interface operation instruction and inputs it into the model finder 21 and the model editor 22;

[0079] The setting interface 23 receives and displays the output results of the model finder 21 and the model editor 22;

[0080] The first output result of the model finder 21 is the found prefabricated system component, the structural information associated with the prefabricated system component, and the component identification;

[0081] The second output result of the model editor 22 is the editing result of the prefabricated system components and structure information.

[0082] Specifically, in order to achieve a better display effect, a setting interface 23 is set for the configuration module in this embodiment, which is embodied as the configurator interface UI part, including a navigation area and an operation area, which are respectively used to display the results of model search and editing, and to input interface operation instructions. The setting interface 23 generates editing instructions according to the interface operation instructions and inputs them into the model finder 21 and the model editor 22 for search and editing.

[0083] In one embodiment, Figure 5 As shown, the model finder 21 includes:

[0084] A search parameter determination module 211, which determines the search parameters currently used for searching the prefabricated system components according to the editing command;

[0085] Search parameters include scope, type, and FQN;

[0086] A field selection module 212, the field selection module 212 is connected to the search parameter determination module 211, and the field selection module 212 determines the corresponding component field in the component storage module according to the search parameter;

[0087] The matching module 213 is connected to the field selection module 212. The matching module 213 matches the component field according to the editing command to obtain the corresponding prefabricated system component.

[0088] Specifically, in order to achieve a better search effect, in this embodiment, multiple search methods are set in the model finder 21, including the scope, type, FQN, etc. of the model. In the search process, first, the search parameter determination module 211 determines the search parameters used for the current search of the prefabricated system components according to the editing command. Then, the field selection module 212 determines the corresponding component field in the component storage module according to the search parameters, and finally the matching module 213 matches the component field according to the editing command to obtain the corresponding prefabricated system component.

[0089] In one embodiment, Figure 6 As shown, the model editor 22 includes:

[0090] The proxy model generation module 221 generates a proxy model according to the prefabricated system components;

[0091] The proxy model editing module 222 is connected to the proxy model generating module 221, and the proxy model editing module 222 modifies the configuration information of the proxy model according to the editing command;

[0092] The configuration information includes model configuration information of the proxy model, structural information of other proxy models associated with the proxy model, and model configuration information of other proxy models associated with the proxy model.

[0093] Specifically, in order to edit a complex model architecture, in this embodiment, the proxy model is first generated according to the prefabricated system components by the proxy model generation module 221, and then the configuration information of the proxy model is modified according to the editing command by the proxy model editing module 222. The modification content includes adjusting the model configuration information of the proxy model to form a component that meets the requirements, adjusting the structural information between multiple proxy models to change the model architecture, etc., and also provides a linkage modification function and a real-time saving function between the model and the parent model.

[0094] In one embodiment, Figure 7 As shown, the debugging and running module 3 includes:

[0095] A device proxy configuration module 31, the device proxy configuration module 31 creates a device process for each input system service element;

[0096] The instance running module 32, the instance configuration module 32 is connected to the device agent configuration module 31, and the instance configuration module 32 creates a machine instance according to the device process and runs it;

[0097] A monitoring module 33, the monitoring module 33 is connected to the instance running module 32, and the monitoring module 33 obtains the running status of the machine instance and generates debugging information;

[0098] The display module 34 is connected to the monitoring module 33 , and the display module 34 obtains and displays the debugging information.

[0099] Specifically, in order to achieve a better debugging process, in this embodiment, the above-mentioned debugging and running module 3 is constructed. Specifically, after receiving the configured system service element, the device agent configuration module 31 will create a device process runtime agent. The main functions of the device process include managing the life cycle of the machine agent, monitoring the changes in the model scope under the project, and the modification of the model.

[0100] Then, the instance configuration module 32 creates a machine instance in the device process and runs it.

[0101] First, the machine agent is responsible for managing the life cycle of the machine instance agent and creating and initializing the function group manager.

[0102] After creating the corresponding machine instance and machine instance agent, the machine instance agent is used to control the start, stop, connection, upload, and management process debug modules of the machine instance.

[0103] The function group manager is responsible for managing the life cycle of state machine agents and the life cycle of function group agents that are not taken over by the state machine.

[0104] The state machine agent is responsible for managing the life cycle of the function group agent it takes over, changing the state machine state, and monitoring changes in the state machine state.

[0105] Function group management function group agent is responsible for managing the life cycle of the process agent, changing the function group state, and monitoring changes in the function group state.

[0106] The above combination is used to realize the operation process of the system service element in the machine instance. Accordingly, in order to realize the control in the machine instance, a monitoring module 33 is also set. The monitoring module 33 first creates a monitoring thread for the machine instance, and then monitors the status, debug mark changes, manages debug marks, and starts debugging through the process agent.

[0107] On this basis, the debugging information is also acquired and displayed through the display module 34 .

[0108] Also, during the debugging process, the created machine instance will be recorded in the .instance file under the project, and the recorded information includes instance name, IP address, address type (IPV4 / IPV6), connection type (Local / Remote), port, user name, password, and connection status. When the machine instance is initialized or updated, the IP address in the instance will be synchronized to the NetworkEndpoint model corresponding to the current machine.

[0109] Script encapsulation realizes the integration process of local and remote scripts, and selects different scripts to execute according to the connection type recorded in the machine instance. It also realizes the integration of script execution and log output modules.

[0110] The local script is machine_cli, and the script parameters are start-machine (start the machine), update-machine (update the machine), stop-machine (stop the machine), change-state (switch the function group state), machine-sm-state (get the state machine state), and change-sm-state (switch the state machine state).

[0111] The remote script is are-cmd, and the script parameters are -r (start the machine), -s (stop the machine), -c (switch the function group status), -m / +# (get the state machine status / switch the state machine status)

[0112] After starting the machine, you need to use the TCP receiver TCPReceiver to monitor the machine's operating status, function group status, and process status in real time.

[0113] The implementation process of the TCP receiver includes adding the -d parameter when calling the startup machine script, passing the port number to be monitored, then establishing a connection through Sckut, sending the function group status message to be monitored, and then waiting to receive the function group status and the process status it supervises. In addition, it also supports monitoring the network status through heartbeats to achieve the function of reconnecting after disconnection.

[0114] In one embodiment, Figure 8 As shown, the output module 4 includes:

[0115] A cutting module 41, which cuts the debugged system service elements and creates an export task;

[0116] A task queue module 42, the task queue module 42 is connected to the cutting module 41, and the task queue module 42 obtains and stores the export tasks;

[0117] The export thread creation module 43 is connected to the task queue module 42, and the export thread creation module 43 obtains the export task and creates a corresponding execution thread to run.

[0118] Specifically, in order to achieve a better export effect, in this embodiment, during the debugging process, a log recording module is also configured, which can record the detailed information of the export operation into the .deliveryLog file through JSON serialization. This information includes timestamp, compression package type, compression status, file name, clipping level and location, etc. During the export process, the debugged system service element is firstly clipped by the clipping module 41 and an export task is created and input into the task queue module 42. The task queue module 42 will store multiple export tasks through the task queue and schedule them in a first-in-first-out manner. The export thread creation module 43 obtains the export task and creates the corresponding execution thread to run. In the process of creating the execution thread, the export task is managed by the thread pool, which can reduce the number of times the package guide thread is created and destroyed.

[0119] The above are only preferred embodiments of the present invention, and are not intended to limit the implementation methods and protection scope of the present invention. Those skilled in the art should be aware that all solutions obtained by equivalent substitutions and obvious changes made using the description and illustrations of the present invention should be included in the protection scope of the present invention.

Claims

1. An integrated interface system for AUTOSAR model editing tools, characterized in that: include: A component storage module, in which prefabricated component information is collected and stored; A configuration module, the configuration module is connected to the component storage module, and the configuration module configures the prefabricated component information in response to an externally input editing instruction to obtain a system service element; A debugging and running module, the debugging and running module is connected to the configuration module, and the debugging and running module runs and debugs according to the system service element; An output module, wherein the output module is connected to the debugging and running module, and the output module packages and outputs the debugged system service elements.

2. The integrated interface system according to claim 1, characterized in that: The component storage module includes: A component entry module, wherein the component entry module obtains prefabricated system components; A component marking module, the component marking module is connected to the component entry module, and the component marking module respectively records the structural information between the prefabricated system components and adds component identification; An index building module, the index building module is connected to the component marking module, and the index building module builds an index according to the component identification and the structural information and adds it to the prefabricated component information.

3. The integrated interface system according to claim 2, characterized in that: The configuration module includes: A model finder, wherein the model finder obtains the corresponding prefabricated system component according to the editing instruction; A model editor is connected to the model finder, and the model editor edits a plurality of the prefabricated system components according to the editing instructions to form the system service element.

4. The integrated interface system according to claim 3, characterized in that: The configuration module also includes: A setting interface, wherein the setting interface is respectively connected to the model finder and the model editor; The setting interface obtains the interface operation instruction input from the outside, and generates the editing instruction according to the interface operation instruction and inputs it into the model finder and the model editor; The setting interface receives and displays the output results of the model finder and the model editor; The first output result of the model finder is the found prefabricated system component, the structural information associated with the prefabricated system component, and the component identifier; The second output result of the model editor is the editing result of the prefabricated system components and the structural information.

5. The integrated interface system according to claim 3, characterized in that: The model finder includes: A search parameter determination module, wherein the search parameter determination module determines the search parameters currently used for searching the prefabricated system components according to the editing command; The search parameters include scope, type, and FQN; A field selection module, the field selection module is connected to the search parameter determination module, and the field selection module determines a corresponding component field in the component storage module according to the search parameter; A matching module, the matching module is connected to the field selection module, and the matching module matches the component field according to the editing command to obtain the corresponding prefabricated system component.

6. The integrated interface system according to claim 3, characterized in that: The model editor includes: A proxy model generation module, wherein the proxy model generation module generates a proxy model according to the prefabricated system components; a proxy model editing module, the proxy model editing module being connected to the proxy model generating module, and the proxy model editing module modifying the configuration information of the proxy model according to the editing command; The configuration information includes model configuration information of the proxy model, the structural information of other proxy models associated with the proxy model, and the model configuration information of other proxy models associated with the proxy model.

7. The integrated interface system according to claim 1, characterized in that: The debugging and running modules include: A device proxy configuration module, wherein the device proxy configuration module creates a device process for each input system service element; An instance running module, wherein the instance configuration module is connected to the device proxy configuration module, and the instance configuration module creates a machine instance according to the device process and runs the machine instance; A monitoring module, the monitoring module is connected to the instance running module, the monitoring module obtains the running status of the machine instance and generates debugging information; A display module is connected to the monitoring module, and the display module obtains and displays the debugging information.

8. The integrated interface system according to claim 1, characterized in that: The output module comprises: A cutting module, which cuts the debugged system service elements and creates an export task; A task queue module, the task queue module is connected to the cutting module, and the task queue module obtains and stores the export task; An export thread creation module is connected to the task queue module, and the export thread creation module obtains the export task and creates a corresponding execution thread to run.

Images