Automatic Generation Method and Device for Controller Software Routing Information Configuration File Based on Autosar Architecture

Abstract

The present application provides a method and device for automatically generating a controller software routing information configuration file based on the Autosar architecture. By quickly identifying the routing relationships in the CAN matrix, it configures the entire frame routing relationships according to the identified routing relationships, configures the signal routing relationships according to the identified routing relationships, and finally outputs the entire frame routing relationships and signal routing relationships to the arxml file to achieve full-automatic configuration of routing information, improving the time efficiency and configuration quality of AUTOSAR configuration.

Description

Technical Field

[0001] This application relates to the information configuration of Autosar (Automotive Open System Architecture) architecture software, and more particularly to the information configuration of routing-related functions in Autosar architecture software. Background Art

[0002] Currently, the software of vehicle controllers is basically designed based on the Autosar standard architecture, and there are many commercial development software on the market that can support BSW (Basic Software) configuration, RTE (Runtime Environment) configuration, etc. In the Autosar architecture, for the configuration of the PduR (Protocol Data Unit Routing) module and the Com (Communication) module in BSW regarding whole-frame routing and signal routing, it is necessary to identify and configure the mapping relationship between the source and the destination one by one according to the routing relationship in the CAN protocol matrix. Depending on the amount of protocol data, the time required for the configuration of whole-frame routing and signal routing is different. Generally, it takes 1 minute to configure a group of whole-frame routing relationships, and the workload for configuring 1 group of signal routing relationships takes 1 minute.

[0003] Usually, in actual software development work, the number of whole-frame routing relationships and signal routing relationships in a version of the CAN protocol is approximately 200 each. The time required for the configuration of routing relationships is 400 minutes, which is very inefficient, and the quality cannot be guaranteed, affecting the software development efficiency and iteration speed.

[0004] To solve this problem, patent document CN202111289975.7 discloses a configuration method and system for AUTOSAR architecture software, which constructs a PC software module based on C#. This PC software module obtains configuration data from a DBC file or an input window and writes it into an ARXML file; the AUTOSAR configuration tool reads the ARXML file and checks whether the configuration data written by the PC software module is correct; if it is correct, the configuration tool generates code; if it is incorrect, a new ARXML file is generated through the PC software module. The system is divided into an interface part and a code part. The interface part realizes functions such as user input, DBC file import, and ARXML original file import; the code part receives the information input by the interface part, writes the user configuration information into the ARXML original file, and realizes the generation of a new ARMXL file with user configuration information. This method improves the time efficiency of AUTOSAR configuration and enhances the accuracy rate of configuration.

[0005] However, this method mainly imports DBC files to obtain CAN information and signals, automatically realizes communication-related configurations and generates code, mainly for the configuration of the COM layer in the AUTOSAR architecture. This method cannot obtain CAN information and signals by directly reading the CAN protocol matrix, let alone obtain the routing relationships of each network segment, and cannot realize the automatic configuration of routing information. Summary of the Invention

[0006] To solve the problems of low routing relationship configuration efficiency and unreliable configuration quality, the present application proposes a method and device for automatically generating a routing information configuration file for a controller software developed based on the Autosar architecture. Through this method, the routing mapping relationship is automatically identified, the configuration of the entire frame routing information in the PduR module is automatically realized, the configuration of the signal routing in the Com module is automatically realized, and the routing information configuration file is automatically output, improving the time efficiency of AUTOSAR configuration.

[0007] To achieve the above invention purposes, the present application adopts the following technical solutions:

[0008] The present application provides a method for automatically generating a routing information configuration file for a controller software developed based on the Autosar architecture in the first aspect. The method includes the following steps:

[0009] Step 1, load the CAN protocol.

[0010] Step 2, identification of the routing mapping relationship: including parsing the entire frame routing information in the CAN protocol and parsing the signal routing information in the CAN protocol; that is, by identifying the summary table in the CAN protocol, screening out the message IDs of the entire frame routing and their routing mapping relationships, and combining with the identification of the matrix table in the CAN protocol, screening out the specific signals and related information of the signal routing, and parsing out the information for configuring the entire frame routing information and the signal routing information.

[0011] Step 3, configure the entire frame routing information in the PduR module: write the identified entire frame routing information into the arxml file according to the format of the PduR module in autosar.

[0012] Step 4, configure the signal routing information in the Com module: write the identified signal routing information into the arxml file according to the format of the Com module in autosar.

[0013] Step 5, generate the routing information configuration file: create an arxml file with writable file attributes through the matlab tool, and write the entire frame routing configuration information and the signal routing configuration information into the arxml.

[0014] In a second aspect, the present application provides an automatic generation device for a controller software routing information configuration file based on the Autosar architecture, which includes the following functional units:

[0015] A loading unit, configured to load the CAN protocol.

[0016] An identification unit, configured to identify routing mapping relationships, including parsing the frame routing information in the CAN protocol and parsing the signal routing information in the CAN protocol; that is, by identifying the summary table in the CAN protocol, screening out the message IDs of frame routing and their routing mapping relationships, and combining with the identification of the matrix table in the CAN protocol, screening out the specific signals and related information of signal routing, and parsing out the information for frame routing information configuration and signal routing information configuration.

[0017] A first configuration unit, configured to configure the frame routing information in the PduR module, and write the identified frame routing information into the arxml file in the format of the PduR module in autosar.

[0018] A second configuration module, configured to configure the signal routing information in the Com module, and write the identified signal routing information into the arxml file in the format of the Com module in autosar.

[0019] A configuration file generation module, configured to generate a routing information configuration file, create an arxml format file with writable file attributes through a matlab tool, and write the frame routing configuration information and the signal routing configuration information into the arxml.

[0020] Adopting the above technical solutions, the present application has at least the following advantages:

[0021] Through the technical solution provided by the present application, a tool that can automatically generate a routing relationship configuration file according to the CAN matrix is constructed. It quickly identifies the routing relationships in the CAN matrix, realizes the configuration of frame routing relationships according to the identified routing relationships, realizes the configuration of signal routing relationships according to the identified routing relationships, and finally outputs the frame routing relationships and signal routing relationships to the arxml file, realizing the full-automatic configuration of routing information and improving the time efficiency and configuration quality of AUTOSAR configuration. Description of the Drawings

[0022] Figure 1 is a schematic diagram of a tool interface for implementing the present application;

[0023] Figure 2 is a schematic diagram of the overall process of generating gateway configuration information shown in an embodiment of the present application;

[0024] Figure 3 It is a schematic flow chart showing the process of parsing the entire frame routing information in the CAN protocol demonstrated in an embodiment of the present application;

[0025] Figure 4 It is a schematic flow chart showing the process of parsing the signal routing information in the CAN protocol demonstrated in an embodiment of the present application;

[0026] Figure 5 It is a schematic flow chart showing the process of writing the entire frame routing configuration information into the arxml file demonstrated in an embodiment of the present application;

[0027] Figure 6 It is a schematic flow chart showing the process of writing the signal routing configuration information into the arxml file demonstrated in an embodiment of the present application. Detailed implementation manners

[0028] Embodiments of the present application will be described in more detail below with reference to the accompanying drawings. Although some embodiments of the present application are shown in the drawings, it should be understood that the present application can be implemented in various forms and should not be construed as limited to the embodiments set forth herein. On the contrary, these embodiments are provided to more thoroughly and completely understand the present application. It should be understood that the drawings and embodiments of the present application are only for exemplary purposes and are not used to limit the protection scope of the present application.

[0029] It should be understood that the various steps recited in the method embodiments of the present application can be executed in a different order and / or in parallel. In addition, the method embodiments may include additional steps and / or omit the steps shown. The scope of the present application is not limited in this regard.

[0030] The term "including" and its variations used herein are open-ended, that is, "including but not limited to". The term "based on" is "at least partially based on". The term "one embodiment" means "at least one embodiment"; the term "another embodiment" means "at least one additional embodiment"; the term "some embodiments" means "at least some embodiments". The relevant definitions of other terms will be given in the following description. It should be noted that the concepts such as "first" and "second" mentioned in the present application are only used to distinguish different devices, modules or units, and are not used to limit the order of the functions executed by these devices, modules or units or the interdependence relationship.

[0031] It should be noted that the modifications of "one" and "multiple" mentioned in the present application are illustrative rather than restrictive. Those skilled in the art should understand that, unless otherwise clearly stated in the context, it should be understood as "one or more".

[0032] The names of the messages or information exchanged between multiple units in the embodiments of the present application are for illustrative purposes only and are not used to limit the scope of these messages or information.

[0033] AUTOSAR is a standardized open automotive software architecture, a software architecture defined for controllers. This software architecture separates the hardware and software of the device, and puts together the functional model software and software components, which are independent of each other and developed by different manufacturers, and then combined into a specific project through certain automatic configuration processes. The separation between hardware and software and different software components is carried out through the Basic Software Package, which consists of the Microcontroller Abstraction Layer (MCAL) and the ECU and Microcontroller Hardware Abstraction Layer (HAL) of the controller, as well as independent service layers (such as operating systems, communication protocols, and memory management). The work between software components under various driving conditions of the vehicle is carried out through an intermediate layer, namely the AUTOSAR Runtime Environment, which mainly controls data exchange and is sometimes also called the Virtual Function Bus. Its basic idea is that software components should be arbitrarily distributed on different devices without considering the results calculated by other runtime systems and different functions. For the basic software, AUTOSAR sets the basic operating conditions according to OSEK, HIS, ASAM, and ISO, as well as industry-oriented CAN, FlexRay, and LIN. It partly undertakes the definition of concepts and standards for operating systems, hardware drivers, and protocols. In addition to function expansion, AUTOSAR is responsible for coordinating the internal interfaces and communication mechanisms and strives to be fully backward compatible.

[0034] The method for automatically generating a controller software routing information configuration file based on the Autosar architecture proposed in the present application involves the design of a human-machine interface, the identification method of routing mapping relationships, the configuration method of the entire frame routing information in the PduR module, the configuration method of signal routing in the Com module, and the generation method of the routing information configuration file.

[0035] In an embodiment of the present application, the design of the human-machine interface is to design a button for loading the CAN protocol, a button for controlling the operation, and a session box for dynamically displaying operation records through the interface design module of the Matlab tool. As Figure 1As shown, click the "Load File" button, and the tool tip selects the CAN protocol. After correctly selecting the CAN protocol, the path where the CAN protocol is located is displayed in the path box; then click the "Generate GW Configuration" button, and the tool starts to parse the CAN protocol and generate a routing information configuration file. During the process, the tool operation process will be recorded in the operation record box. After the configuration file is successfully generated, a session box of "File generation successful" will pop up.

[0036] In another embodiment of the present application, the method for identifying the routing mapping relationship is to parse the CAN protocol information. First, by identifying the summary table in the CAN protocol, the message IDs of the whole-frame routing and their routing mapping relationships are filtered out. Then, by combining the identification of the matrix table in the CAN protocol, the specific signals and related information of the signal routing are filtered out. Finally, the directly useful information for the whole-frame routing information configuration and the signal routing information configuration is sorted out.

[0037] In a further embodiment of the present application, the method for configuring the whole-frame routing information in the PudR module is to write the identified whole-frame routing information into the arxml file according to the requirements of the autosar architecture.

[0038] In a further embodiment of the present application, the method for configuring the signal routing information in the Com module is to write the identified signal routing information into the arxml file according to the requirements of the autosar architecture.

[0039] In a further embodiment of the present application, the method for generating the routing information configuration file is to create an arxml file with writable file attributes through the matlab tool, and write the whole-frame routing configuration information and the signal routing configuration information into the arxml.

[0040] The following details the process of the automatic generation method of the controller software routing information configuration file based on the Autosar architecture, as Figure 2 shown in the overall process of generating the gateway configuration information:

[0041] First, load the CAN protocol file, and then parse the loaded file, including parsing the information related to the whole-frame routing and part of the information of the signal routing from the summary table, and parsing part of the information of the signal routing from the matrix. Then, combine the signal routing information parsed from the summary table and the matrix table to obtain all the signal routing information. After all the whole-frame routing information and the signal routing information are parsed, start to generate the content of the gateway configuration file according to this information.

[0042] The specific steps of the above process are as follows:

[0043] Step 1, load the CAN protocol.

[0044] In this step, it includes designing a loading button in the human-machine interface, setting the button to the off state before selecting a file, then setting the design prompt message in the pop-up box to "Please select the CAN protocol", and finally setting the loading button to the ON state.

[0045] Step 2: Identification of routing mapping relationships.

[0046] In this step, it includes parsing the entire frame routing information in the CAN protocol and parsing the signal routing information in the CAN protocol. That is, by identifying the summary table in the CAN protocol, filtering out the message IDs of the entire frame routing and their routing mapping relationships, and combining with the identification of the matrix table in the CAN protocol, filtering out the specific signals and related information of the signal routing, and parsing out the information for configuring the entire frame routing information and the signal routing information.

[0047] As Figure 3 shown, parsing the entire frame routing information in the CAN protocol is mainly to extract relevant information from the summary table of the protocol. First, extract the original information in the summary table into the structure ALL_OverView (a structure for storing the original information in the protocol summary table, and the variables it contains are the sending network segment, sending node, period, sending ID, message length, receiving node). The elements of the structure include the network segment, node, period, sending ID, length, and receiving node. Then, remove the spaces from the information in the structure to ensure that all information is accurate. Then, find all the messages sent by the GW (gateway), and store the message information sent by the GW into the structure ALL_GW_Overview (a structure for storing the information of all messages sent by the gateway in the protocol summary table, and the variables it contains are the sending network segment, sending node, period, sending ID, message length, receiving node). Then, for all the messages sent by the found GWs, traverse and query in ALL_OverView according to the ID content. If it is found that the sending node with the same ID content is not a GW, then the message with this ID is considered as an entire frame routing message, and the corresponding information is stored in MsgRouteInfo (a structure for storing the ID corresponding information of the filtered message routing, and the variables it contains are the sending network segment, sending node, period, sending ID, message length, receiving node. The content of this structure is the basis for finally writing the entire frame forwarding configuration information). The information contained in the structure includes the sending network segment, sending node, period, ID, length, and receiving node; otherwise, the message with this ID is an information routing message, and the corresponding information is stored in SigRouteInfo_Overview (a structure for storing the ID corresponding information of the filtered signal routing, and the variables it contains are the sending network segment, sending node, period, sending ID, message length, receiving node). The information contained in the structure includes the sending network segment, sending node, period, ID, length, and receiving node.

[0048] As Figure 4 shown, parsing the signal routing information in the CAN protocol is to further parse the content of the protocol matrix on the basis of the previous step to obtain the information of all information routings. First, extract the original information in the matrix and store it in the structure Tab_Matrix0 (a structure for storing the original information of the protocol matrix, and the variables it contains are the sending network segment, sending node, signal name, sending ID, routing information, receiving node). The elements contained in the structure are the sending network segment, sending node, signal name, sending ID, routing information, and receiving node. In Tab_Matrix0, find the elements with the same ID and the same network segment as those in SigRouteInfo_Overview, and store all the message information that meets the conditions in the structure SigRouteInfo_Temp (a structure for temporarily storing signal forwarding information, and the variables it contains are the sending network segment, sending node, signal name, sending ID, and routing information). The elements contained in this structure are the sending network segment, sending node, signal name, sending ID, and routing information. Finally, remove the invalid routing information in SigRouteInfo_Temp, and store the content after removal in the structure SigRouteInfo (a structure for storing signal forwarding information after removing invalid routing information, and the variables it contains are the sending network segment, sending node, signal name, sending ID, and routing information. The content of this structure is the basis for finally writing the signal forwarding configuration information), including the sending network segment, sending node, signal name, sending ID, and routing information.

[0049] Step 3, configure the frame routing information in the PduR module: Write the recognized frame routing information into the arxml file in the format of the PduR module in autosar.

[0050] The detailed process of this step is as Figure 5As shown, the entire frame routing configuration information is written into the arxml file in accordance with the format of the PduR module in Autosar, including the source information and destination information of the entire frame routing. First, a writable arxml file is created, and the content of the header part is written in the format of the arxml file in Autosar format to ensure the integrity of the file. Then, in the entire frame routing structure MsgRouteInfo, search for the GW message with the sending node. If found, it indicates that the message is the source message, and the information is stored in the structure MsgRouteInfo_Source (a structure for storing the source information of the entire frame routing message, and the structure elements include the sending network segment, sending node, period, sending ID, length, routing information, etc.). The structure elements include the sending network segment, sending node, period, sending ID, length, routing information. Otherwise, it indicates that the message is the destination message, and the information is stored in the structure MsgRouteInfo_Destination (a structure for storing the destination information of the entire frame routing message, and the structure elements include the sending network segment, sending node, period, sending ID, length, routing information, etc.). The structure elements include the sending network segment, sending node, period, sending ID, length, routing information. Then, traverse according to the ID in the structure MsgRouteInfo_Source to obtain the information of the source message required for writing the arxml file, and perform the combination of character segments. Then, write the source information into the arxml file in accordance with the PduR module format in Autosar. Then, search in the structure MsgRouteInfo_Destination for the message with the same ID as the current source structure to obtain the corresponding destination message information, and perform the combination of character segments. Then, write the destination information into the arxml file in accordance with the PduR module format in Autosar. Finally, write the content of the ending part of the arxml file in accordance with the Autosar format at the end of the file.

[0051] Step 4, configure the signal routing information in the Com module: Write the identified signal routing information into the arxml file in accordance with the Com module format in Autosar.

[0052] The detailed process of this step is as Figure 6As shown, the signal routing configuration information is written into the arxml file in the format of the PduR module in Autosar, writing the source and destination information of the signal routing. First, a writable arxml file is created, and then the header content of the file is written in the Autosar format. Then, from the element RouteMark (routing label) in the signal routing structure SigRouteInfo, the source network segment, source sender, and source ID of the signal are obtained and combined in a character segment. Then, the source information and destination information are written into the arxml file in the COM module format in Autosar. Finally, the ending content of the arxml file in the Autosar format is written.

[0053] Step 5, generate a routing information configuration file: Create an arxml-format file with writable file attributes through the Matlab tool, and write the entire frame routing configuration information and signal routing configuration information into the arxml.

[0054] Through the above series of embodiments, an automatic generation method for the controller software routing information configuration file based on the Autosar architecture is demonstrated. Through this method, the routing relationships in the CAN matrix can be quickly identified, the configuration of the entire frame routing relationship can be achieved according to the identified routing relationships, the configuration of the signal routing relationship can be achieved according to the identified routing relationships, and finally the entire frame routing relationship and signal routing relationship are output to the arxml file to realize the automatic configuration of the routing information and improve the time efficiency of AUTOSAR configuration.

[0055] Furthermore, an exemplary embodiment of the present application further provides an automatic generation device for the controller software routing information configuration file based on the Autosar architecture, which includes functional units: a loading unit, an identification unit, a first configuration unit, a second configuration unit, and a configuration file generation module. The specific configuration content of each unit is as follows:

[0056] The loading unit is configured to load the CAN protocol.

[0057] The identification unit is configured to identify the routing mapping relationship, including parsing the entire frame routing information in the CAN protocol and parsing the signal routing information in the CAN protocol.

[0058] In the exemplary embodiment of the present application, the identification unit's parsing of the entire frame routing information in the CAN protocol specifically includes:

[0059] First, extract the original information in the summary table into the structure ALL_OverView. The elements of the structure include network segment, node, period, sending ID, length, and receiving node. Remove the spaces from the information in the structure, and then find all the messages sent by the GW and store them in the structure ALL_GW_Overview. Then, for all the messages sent by the GW found, traverse and query them in ALL_OverView according to the ID content. If a non-GW sending node with the same ID content is found during the query, the message with that ID is considered a full-frame routing message, and the corresponding information is stored in MsgRouteInfo. The information included in the structure is sending network segment, sending node, period, ID, length, and receiving node. Otherwise, the message with that ID is a signal routing message, and the corresponding information is stored in SigRouteInfo_Overview. The information included in the structure is sending network segment, sending node, period, ID, length, and receiving node.

[0060] In an exemplary embodiment of the present application, the specific process of the recognition unit parsing the signal routing information in the CAN protocol includes:

[0061] First, extract the original information in the protocol matrix and store it in the structure Tab_Matrix0. The elements included in the structure are sending network segment, sending node, signal name, sending ID, routing information, and receiving node. In Tab_Matrix0, find the elements with the same ID and the same network segment as those in SigRouteInfo_Overview, and store all the message information that meets the conditions in the structure SigRouteInfo_Temp. The elements included in this structure are sending network segment, sending node, signal name, sending ID, and routing information. Finally, remove the invalid routing information in SigRouteInfo_Temp and store it in the structure SigRouteInfo, including sending network segment, sending node, signal name, sending ID, and routing information.

[0062] The first configuration unit is configured to configure the entire frame routing information in the PduR module, and write the recognized entire frame routing information into the arxml file in the format of the PduR module in autosar. Specifically, it includes: first, create an arxml file, write the content of the header part in the arxml file format specified by autosar, search for the GW message with the sending node in the entire frame routing structure MsgRouteInfo. If it is found, it indicates that the message is the source message, and store the information in the structure MsgRouteInfo_Source. The structure elements include the sending network segment, sending node, period, sending ID, length, and routing information; otherwise, it indicates that the message is the destination message, and store the information in the structure MsgRouteInfo_Destination. The structure elements include the sending network segment, sending node, period, sending ID, length, and routing information; then traverse according to the ID in the structure MsgRouteInfo_Source to obtain the source message information required to write the arxml file, and perform character segment combination, and then write the source information into the arxml file in the format of the PduR module in autosar; then go to the structure MsgRouteInfo_Destination to find the message with the same ID as the current source structure to obtain the corresponding destination message information, and perform character segment combination, and then write the destination information into the arxml file in the format of the PduR module in autosar; finally, write the content of the end part of the arxml file in the autosar format at the end of the file.

[0063] The second configuration module is configured to configure the signal routing information in the Com module, and write the recognized signal routing information into the arxml file in the format of the Com module in autosar. Specifically, it includes: first, create an arxml file, write the content of the header part of the file in the autosar format, then obtain the source network segment, source sender, and source ID of the signal from the element RouteMark in the signal routing structure SigRouteInfo, and perform character segment combination, and then write the source information and destination information into the arxml file in the format of the COM module in autosar, and finally write the content of the end part of the arxml file in the autosar format.

[0064] The configuration file generation module is configured to generate a routing information configuration file, create an arxml format file with writable file attributes through the matlab tool, and write the entire frame routing configuration information and signal routing configuration information into the arxml.

[0065] As can be seen from the detailed description of the present application through the above embodiments, the present application automatically identifies the routing mapping relationship, automatically configures the entire frame routing information in the PduR module, automatically configures the signal routing in the Com module, and automatically outputs the routing information configuration file, which can improve the time efficiency of AUTOSAR configuration and better solve the problems of low routing relationship configuration efficiency and unreliable configuration quality existing in the prior art.

Claims

1. A method for automatically generating a controller software routing information configuration file based on the Autosar architecture, characterized in that The method includes: Step 1, load the CAN protocol; Step 2, identification of routing mapping relationships: including parsing the frame routing information in the CAN protocol and parsing the signal routing information in the CAN protocol; that is, by identifying the overview table in the CAN protocol, filtering out the message IDs of frame routing and their routing mapping relationships, and combining with the identification of the matrix table in the CAN protocol, filtering out the specific signals and related information of signal routing, and parsing out the information for frame routing information configuration and signal routing information configuration; The parsing of the frame routing information in the CAN protocol includes: extracting the original information in the overview table into the structure ALL_OverView; removing spaces from the information in the structure, then finding all the messages sent by the gateway GW, storing them in the structure ALL_GW_Overview, and then traversing and querying all the messages sent by the gateway GW found in ALL_OverView according to the ID content. If a sending node other than the gateway GW is found for the same ID content during the query, the message with this ID is considered a frame routing message, and the corresponding information is stored in the structure MsgRouteInfo; otherwise, the message with this ID is an information routing message, and the corresponding information is stored in the structure SigRouteInfo_Overview; The parsing of the signal routing information in the CAN protocol includes: extracting the original information in the protocol matrix and storing it in the structure Tab_Matrix0; in Tab_Matrix0, finding the elements with the same ID and the same network segment as those in SigRouteInfo_Overview, and storing all the message information that meets the conditions found in the structure SigRouteInfo_Temp, and finally removing the invalid routing information in SigRouteInfo_Temp and storing it in the structure SigRouteInfo; Step 3, configure the frame routing information in the PduR module: write the identified frame routing information into the arxml file in the format of the PduR module in autosar; Step 4, configure the signal routing information in the Com module: write the identified signal routing information into the arxml file in the format of the Com module in autosar; Step 5, generate a routing information configuration file: create a file in the arxml format through the matlab tool, and write the frame routing configuration information and the signal routing configuration information into the arxml.

2. The automatic generation method of the controller software routing information configuration file based on the Autosar architecture according to claim 1, wherein In step 2, the information contained in the structure ALL_OverView, the structure MsgRouteInfo, and the structure SigRouteInfo_Overview all includes the sending network segment, sending node, period, sending ID, length, and receiving node; the elements contained in the structure Tab_Matrix0 are the sending network segment, sending node, signal name, sending ID, routing information, and receiving node; the elements contained in the structures SigRouteInfo_Temp and SigRouteInfo are the sending network segment, sending node, signal name, sending ID, and routing information.

3. The automatic generation method of the controller software routing information configuration file based on the Autosar architecture according to claim 1, characterized in that The specific configuration of the entire frame routing information in the PduR module in step 3 includes: first, create an arxml file, write the content of the header part according to the arxml file format specified by autosar. Search for the message with the sending node as the gateway GW in the entire frame routing structure MsgRouteInfo. If so, it indicates that this message is the source message, and store the information in the structure MsgRouteInfo_Source. The structure elements include the sending network segment, sending node, period, sending ID, length, and routing information; otherwise, it indicates that this message is the destination message, and store the information in the structure MsgRouteInfo_Destination. The structure elements include the sending network segment, sending node, period, sending ID, length, and routing information. Then, traverse according to the ID in the structure MsgRouteInfo_Source to obtain the source message information required for writing the arxml file, and perform character segment combination. Then, write the source information into the arxml file according to the PduR module format in autosar. Then, search for the message with the same ID as the current source structure in the structure MsgRouteInfo_Destination to obtain the corresponding destination message information, and perform character segment combination. Then, write the destination information into the arxml file according to the PduR module format in autosar. Finally, write the content of the end part of the arxml file at the end of the file according to the autosar format.

4. The method for automatically generating a controller software routing information configuration file based on the Autosar architecture according to claim 3, wherein The specific configuration of the signal routing information in the Com module in step 4 includes: first, create an arxml file, write the content of the header part of the file according to the autosar format. Then, obtain the source network segment, source sender, and source ID of the signal from the element RouteMark in the signal routing structure SigRouteInfo, and perform character segment combination. Then, write the source information and destination information into the arxml file according to the COM module format in autosar. Finally, write the content of the end part of the arxml file in the autosar format.

5. An automatic generation device for a controller software routing information configuration file based on the Autosar architecture, characterized in that, Including: A loading unit configured to load the CAN protocol; An identification unit configured to identify the routing mapping relationship, including parsing the entire frame routing information in the CAN protocol and parsing the signal routing information in the CAN protocol; That is, by identifying the summary table in the CAN protocol, the message IDs for the whole-frame routing and their routing mapping relationships are filtered out. Combining with the identification of the matrix table in the CAN protocol, the specific signals and related information for the signal routing are filtered out, and the information for the whole-frame routing information configuration and the signal routing information configuration is parsed; The parsing of the whole-frame routing information in the CAN protocol includes: extracting the original information in the summary table into the structure ALL_OverView; removing the spaces from the information in the structure, then finding all the messages sent by the gateway GW and storing them in the structure ALL_GW_Overview. Then, for all the messages sent by the gateway GW found, traverse and query them in ALL_OverView according to the ID content. If a sending node other than the gateway GW is found for the same ID content during the query, the message with this ID is considered a whole-frame routing message, and the corresponding information is stored in the structure MsgRouteInfo; otherwise, the message with this ID is an information routing message, and the corresponding information is stored in the structure SigRouteInfo_Overview. The parsing of the signal routing information in the CAN protocol includes: extracting the original information in the protocol matrix and storing it in the structure Tab_Matrix0; in Tab_Matrix0, finding the elements with the same ID and the same network segment as those in SigRouteInfo_Overview, and storing all the message information that meets the conditions found in the structure SigRouteInfo_Temp. Finally, after removing the invalid routing information in SigRouteInfo_Temp, it is stored in the structure SigRouteInfo; The first configuration unit is configured to configure the whole-frame routing information in the PduR module, and write the identified whole-frame routing information into the arxml file in the format of the PduR module in autosar; The second configuration module is configured to configure the signal routing information in the Com module, and write the identified signal routing information into the arxml file in the format of the Com module in autosar; The configuration file generation module is configured to generate a routing information configuration file, create an arxml-format file with writable file attributes through the matlab tool, and write the whole-frame routing configuration information and the signal routing configuration information into the arxml; 6. The automatic generation device for the controller software routing information configuration file based on the Autosar architecture according to claim 5, characterized in that, The information contained in the structure ALL_OverView, the structure MsgRouteInfo, and the structure SigRouteInfo_Overview includes the sending network segment, sending node, period, sending ID, length, and receiving node; the elements contained in the structure Tab_Matrix0 are the sending network segment, sending node, signal name, sending ID, routing information, and receiving node; the elements contained in the structure SigRouteInfo_Temp and the structure SigRouteInfo are the sending network segment, sending node, signal name, sending ID, and routing information.

7. The automatic generation device for the controller software routing information configuration file based on the Autosar architecture according to claim 5, characterized in that The specific configuration of the entire frame routing information in the PduR module by the first configuration unit includes: first, create an arxml file, write the content of the header part in accordance with the arxml file format specified by autosar, search for the message with the sending node being the gateway GW in the entire frame routing structure MsgRouteInfo. If so, it indicates that the message is the source message, and store the information in the structure MsgRouteInfo_Source. The structure elements include the sending network segment, sending node, period, sending ID, length, and routing information; otherwise, it indicates that the message is the destination message, and store the information in the structure MsgRouteInfo_Destination. The structure elements include the sending network segment, sending node, period, sending ID, length, and routing information; then traverse according to the ID in the structure MsgRouteInfo_Source to obtain the source message information required for writing the arxml file, and perform the combination of character segments, and then write the source information into the arxml file in accordance with the PduR module format in autosar; then go to the structure MsgRouteInfo_Destination to find the message with the same ID as the current source structure to obtain the corresponding destination message information, and perform the combination of character segments, and then write the destination information into the arxml file in accordance with the PduR module format in autosar; finally, write the content of the ending part of the arxml file at the end of the file in accordance with the autosar format.

8. The automatic generation method of the controller software routing information configuration file based on the Autosar architecture according to claim 7, characterized in that The specific configuration of the signal routing information in the Com module by the second configuration module includes: first, create an arxml file, write the content of the header part of the file in accordance with the autosar format, then obtain the source network segment, source sender, and source ID of the signal from the element RouteMark in the signal routing structure SigRouteInfo, and perform the combination of character segments, and then write the source information and destination information into the arxml file in accordance with the COM module format in autosar, and finally write the content of the ending part of the arxml file in the autosar format.

Images