CN115878212A - Automatic generation method and device for controller software routing information configuration file based on Autosar architecture - Google Patents

Automatic generation method and device for controller software routing information configuration file based on Autosar architecture Download PDF

Info

Publication number
CN115878212A
CN115878212A CN202211343088.8A CN202211343088A CN115878212A CN 115878212 A CN115878212 A CN 115878212A CN 202211343088 A CN202211343088 A CN 202211343088A CN 115878212 A CN115878212 A CN 115878212A
Authority
CN
China
Prior art keywords
information
routing
sending
routing information
message
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Pending
Application number
CN202211343088.8A
Other languages
Chinese (zh)
Inventor
廖娇
顾远芳
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Chongqing Changan New Energy Automobile Technology Co Ltd
Original Assignee
Chongqing Changan New Energy Automobile Technology Co Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Chongqing Changan New Energy Automobile Technology Co Ltd filed Critical Chongqing Changan New Energy Automobile Technology Co Ltd
Priority to CN202211343088.8A priority Critical patent/CN115878212A/en
Publication of CN115878212A publication Critical patent/CN115878212A/en
Pending legal-status Critical Current

Links

Images

Classifications

    • YGENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
    • Y02TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
    • Y02PCLIMATE CHANGE MITIGATION TECHNOLOGIES IN THE PRODUCTION OR PROCESSING OF GOODS
    • Y02P90/00Enabling technologies with a potential contribution to greenhouse gas [GHG] emissions mitigation
    • Y02P90/02Total factory control, e.g. smart factories, flexible manufacturing systems [FMS] or integrated manufacturing systems [IMS]

Landscapes

  • Data Exchanges In Wide-Area Networks (AREA)

Abstract

The method and the device realize the configuration of the whole frame routing relation according to the identified routing relation, realize the configuration of the signal routing relation according to the identified routing relation, and finally output the whole frame routing relation and the signal routing relation to an arxml file, thereby realizing the full automatic configuration of the routing information and improving the time efficiency and the configuration quality of AUTOSAR configuration.

Description

Automatic generation method and device for controller software routing information configuration file based on Autosar architecture
Technical Field
The present application relates to information configuration of Autosar (open system architecture) architecture software, and more particularly, to information configuration of routing related functions in Autosar architecture software.
Background
At present, software of the vehicle control unit is basically designed based on an Autosar standard architecture, and many commercially developed software are available on the market, which can support BSW (basic software) configuration, RTE (runtime environment) configuration, and the like. In the Autosar architecture, the PduR (protocol data unit routing) module and the Com (communication) module in the BSW need 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, and the configuration of the whole frame routing and the signal routing needs to consume different time according to the amount of data of the protocol, generally, the configuration of one group of whole frame routing relationship needs to consume 1 minute, and the configuration workload of 1 group of signal routing relationship needs to consume 1 minute.
Generally, in actual software development work, the amount of the whole frame routing relationship and the signal routing relationship in a single-version CAN protocol is about 200 groups, the configuration of the routing relationship needs 400 minutes, the efficiency is very low, the quality cannot be guaranteed, and the software development efficiency and the iteration speed are affected.
In order to solve the problem, the patent document CN202111289975.7 discloses a configuration method and system of AUTOSAR architecture software, a PC software module is constructed based on C #, and the PC software module acquires configuration data from a DBC file or an input window and writes the configuration data 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 or not; if the code is correct, the configuration tool generates a code; if the file is wrong, a new ARXML file is generated through the PC software module. The system is divided into an interface part and a code part, wherein the interface part realizes the functions of user input, DBC file import and ARXML original file import; the code part receives the information input by the interface part and writes the user configuration information into the ARXML original file to realize the generation of the ARMXL new file with the user configuration information. The method improves the time efficiency of AUTOSAR configuration and enhances the accuracy of the configuration.
However, the method mainly includes acquiring information and signals of the CAN by importing a DBC file, and automatically implementing configuration and code generation related to communication, mainly including configuration of a COM layer in an AUTOSAR architecture.
Disclosure of Invention
In order to solve the problems of low routing relation configuration efficiency and unreliable configuration quality, the application provides a method and a device for automatically generating a routing information configuration file of controller software developed based on an Autosar framework.
In order to achieve the above purpose, the following technical scheme is adopted in the application:
in a first aspect, the present application provides a method for automatically generating a routing information configuration file of controller software developed based on an Autosar architecture, where the method includes the following steps:
step 1, loading a CAN protocol.
Step 2, identifying the route mapping relation: analyzing the whole frame of routing information in the CAN protocol and analyzing the signal routing information in the CAN protocol; the message ID of the whole frame routing and the routing mapping relation thereof are screened out by identifying a summary table in the CAN protocol, and the specific signal and the related information of the signal routing are screened out by combining with the matrix table in the CAN protocol, so that the information for the whole frame routing information configuration and the signal routing information configuration is analyzed.
Step 3, configuring the whole frame of routing information in the Pdu module: and writing the identified whole-frame routing information into an arxml file according to the format of a PduR module in the autosar.
Step 4, configuring signal routing information in the Com module: and writing the identified signal routing information into an arxml file according to the format of the Com module in the autosar.
Step 5, generating a routing information configuration file: and creating a file with writable arxml format file attribute through a matlab tool, and writing the whole frame routing configuration information and the signal routing configuration information into the arxml.
In a second aspect of the present application, an automatic generation apparatus for a controller software routing information configuration file based on an Autosar architecture is provided, which includes the following functional units:
a loading unit configured to load a CAN protocol.
The identifying unit is configured to identify a routing mapping relation, and comprises the steps of analyzing the whole frame of routing information in the CAN protocol and analyzing the signal routing information in the CAN protocol; the message ID of the whole frame routing and the routing mapping relation thereof are screened out by identifying a summary table in the CAN protocol, and the specific signal and the related information of the signal routing are screened out by combining with the matrix table in the CAN protocol, so that the information for the whole frame routing information configuration and the signal routing information configuration is analyzed.
And the first configuration unit is configured to configure the whole frame of routing information in the PdauR module, and write the identified whole frame of routing information into an arxml file according to the format of the PdauR module in the autosar.
And the second configuration module is configured to configure the signal routing information in the Com module, and write the identified signal routing information into an arxml file according to the format of the Com module in the autosar.
The configuration file generation module is configured to generate a routing information configuration file, create a file with a writable arxml format file attribute through a matlab tool, and write the whole frame of routing configuration information and the signal routing configuration information into the arxml.
By adopting the technical scheme, the method has at least the following advantages: .
According to the technical scheme, a tool capable of automatically generating the routing relation configuration file according to the CAN matrix is constructed, the routing relation in the CAN matrix is quickly identified, the configuration of the routing relation of the whole frame is realized according to the identified routing relation, the configuration of the routing relation of the signal is realized according to the identified routing relation, and finally the routing relation of the whole frame and the routing relation of the signal are output to the arxml file, so that the full-automatic configuration of routing information is realized, and the time efficiency and the configuration quality of AUTOSAR configuration are improved.
Drawings
FIG. 1 is a schematic view of a tool interface embodying the present application;
fig. 2 is a schematic general flow chart illustrating generation of gateway configuration information according to an embodiment of the present application;
fig. 3 is a schematic flow chart illustrating parsing of an entire frame of routing information in a CAN protocol according to an embodiment of the present application;
fig. 4 is a schematic flow chart illustrating a process of analyzing signal routing information in a CAN protocol according to an embodiment of the present application;
fig. 5 is a schematic flowchart illustrating a process of writing the routing configuration information of the entire frame into an arxml file according to an embodiment of the present application;
fig. 6 is a schematic flow chart illustrating writing of signal routing configuration information into an arxml file according to an embodiment of the present application.
Detailed Description
Embodiments of the present application will be described in more detail below with reference to the accompanying drawings. While certain embodiments of the present application are shown in the drawings, it should be understood that the present application may be embodied in various forms and should not be construed as limited to the embodiments set forth herein, but rather are provided for a more thorough and complete understanding of the present application. It should be understood that the drawings and embodiments of the present application are for illustration purposes only and are not intended to limit the scope of the present application.
It should be understood that the various steps recited in the method embodiments of the present application may be performed in a different order, and/or performed in parallel. Moreover, method embodiments may include additional steps and/or omit performing the illustrated steps. The scope of the present application is not limited in this respect.
The term "including" and variations thereof as used herein is intended to be open-ended, i.e., "including but not limited to". The term "based on" is "based, at least in part, 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". Relevant definitions for other terms will be given in the following description. It should be noted that the terms "first", "second", and the like in the present application are only used for distinguishing different devices, modules or units, and are not used for limiting the order or interdependence relationship of the functions performed by the devices, modules or units.
It is noted that references to "a", "an", and "the" modifications in this application are intended to be illustrative rather than limiting, and that those skilled in the art will recognize that reference to "one or more" unless the context clearly dictates otherwise.
The names of messages or information exchanged between the units in the embodiments of the present application are for illustrative purposes only, and are not intended to limit the scope of the messages or information.
The automotive open software architecture is a standardized open automobile software architecture, which is a software architecture defined for a controller, and the software architecture separates hardware and software of equipment, puts functional model software and software components together, is independent of each other and is developed by different manufacturers, and is combined into a specific project through some automatic configuration processes. The separation between hardware and software and the different software components is performed by a Basic software package (Basic software-ware) consisting of a microcontroller abstraction layer MCAL and an abstraction layer of the controller (ECU and microcontroller hardware abstraction layer HAL) and mutually independent service layers (such as operating system, communication protocol and memory management). The software components of the vehicle operating in different operating modes work with each other via an intermediate layer, i.e. the AUTOSAR runtime environment, which is primarily an exchange of control data, sometimes referred to as Virtual Function Bus (Virtual Function Bus). The basic idea is that the software components should be distributed arbitrarily over the different devices, without having to take into account the results calculated by other runtime systems, different functions. For the base software, AUTOSAR sets basic operating conditions according to OSEK, HIS, ASAM and ISO and industry-oriented CAN, flexRay and LIN. It bears partly the definition of concepts and standards for operating systems, hardware drivers and protocols, and in addition to functional extensions, the coordination between internal interfaces and communication mechanisms is taken care of by AUTOSAR in striving for full backward compatibility.
The application provides an automatic generation method of a controller software routing information configuration file based on an Autosar framework, and relates to a design of a human-computer interface, a recognition method of a routing mapping relation, a configuration method of whole-frame routing information in a Pdu module, a configuration method of a signal route in a Com module, and a generation method of a routing information configuration file.
In an embodiment of the application, the human-computer interface is designed to design a button for loading a CAN protocol, a button for controlling operation and a session box for dynamically displaying an operation record through an interface design module of a Matlab tool. As shown in fig. 1, clicking a button of loading a file, prompting a tool to select a CAN protocol, and displaying a path of the CAN protocol in a path frame after the CAN protocol is correctly selected; and then clicking a button for generating GW configuration, starting analyzing the CAN protocol by the tool and generating a routing information configuration file, recording the operation process of the tool in an operation recording frame in the process, and popping up a session frame of 'successful file generation' after the configuration file is successfully generated.
In another embodiment of the present application, the method for identifying a routing mapping relationship includes analyzing CAN protocol information, first screening message IDs of an entire frame of routing and their routing mapping relationships by identifying a summary table in the CAN protocol, then screening specific signals and related information of a signal routing by combining with an identification matrix table in the CAN protocol, and finally sorting out direct useful information for configuration of the entire frame of routing information and configuration of the signal routing information.
In a further embodiment of the present application, the configuration method of the whole-frame routing information in the PudR module is to write the identified whole-frame routing information into an arxml file according to the requirement of the autosar architecture.
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 an arxml file according to the requirements of the autosar architecture.
In a further embodiment of the present application, the method for generating the routing information configuration file is to create a file with a writable arxml format file attribute through a matlab tool, and write the whole frame of routing configuration information and the signal routing configuration information into the arxml.
The following describes in detail a flow of a method for automatically generating a controller software routing information configuration file based on an Autosar architecture, such as a general flow of gateway configuration information generation shown in fig. 2:
the CAN protocol file is loaded firstly, then the loaded file is analyzed, the information related to the routing of the whole frame and the partial information of the signal routing are analyzed from the summary table, the partial information of the signal routing is analyzed from the matrix, and then all the signal routing information is obtained by combining the signal routing information analyzed from the summary table and the matrix table. And after all the routing information of the whole frame and the signal routing information are analyzed, generating the content of the gateway configuration file according to the information.
The specific steps of the above process are as follows:
step 1, loading a CAN protocol.
In the step, a loading button is designed in a human-computer interface, the button is set to be in an off state before a file is selected, then a prompt language of 'please select a CAN protocol' is designed in a pop-up box, and finally the loading button is set to be in an ON state.
And 2, identifying the routing mapping relation.
In this step, the whole frame of routing information in the CAN protocol is analyzed, and the signal routing information in the CAN protocol is analyzed. The message ID of the whole frame routing and the routing mapping relation thereof are screened out by identifying a summary table in the CAN protocol, and the specific signal and the related information of the signal routing are screened out by combining with the matrix table in the CAN protocol, so that the information for the whole frame routing information configuration and the signal routing information configuration is analyzed.
As shown in fig. 3, the analysis of the whole frame of routing information in the CAN protocol mainly extracts relevant information from the summary table of the protocol. Firstly, extracting original information in a summary table to a structure ALL _ OverView (a structure storing the original information in a protocol summary table, wherein variables comprise a sending network segment, a sending node, a period, a sending ID, a message length and a receiving node), structure elements comprise a network segment, a node, a period, a sending ID, a length and a receiving node, then performing blank processing on the information in the structure to ensure that ALL the information is accurate, then finding out messages sent by ALL GW (gateways), storing the message information sent by the GW to the structure ALL _ GW _ Overview (a structure storing the information of ALL the messages sent by the gateways in the protocol summary table, wherein the structure comprises variables comprising a sending network segment, a sending node, a period, a sending ID, a message length and a receiving node), traversing and inquiring the found messages sent by ALL GWs in ALL _ OverView according to ID contents, if inquiring that the same ID contents have sending nodes which are not GW, considering that the messages of the ID are whole-frame routing messages, and storing corresponding information in MsgrouteInfo (a structural body storing ID corresponding information of the screened message routing, and containing variables including a sending network segment, a sending node, a period, a sending ID, a message length and a receiving node, wherein the structural body content is a basis for finally writing whole-frame forwarding configuration information), and the structural body contains information including a sending network segment, a sending node, a period, an ID, a length and a receiving node; otherwise, the ID message is an information routing message, and corresponding information is stored in SigRouteInfo _ Overview (a structure storing information corresponding to the ID of the screened signal route, including variables such as a sending segment, a sending node, a period, a sending ID, a message length, and a receiving node), and the structure includes information such as a sending segment, a sending node, a period, an ID, a length, and a receiving node.
As shown in fig. 4, analyzing the signal routing information in the CAN protocol is to further analyze the content of the protocol matrix on the basis of the previous step to obtain information of all information routes. The method comprises the steps of firstly extracting original information in a Matrix, storing the original information in a structure Tab _ Matrix0 (the structure storing the original information of a protocol Matrix comprises a transmitting network segment, a transmitting node, a signal name, a transmitting ID, routing information and a receiving node), wherein elements contained in the structure comprise the transmitting network segment, the transmitting node, the signal name, the transmitting ID, the routing information and the receiving node, in the Tab _ Matrix0, finding elements with the same ID and the same network segment as those in SigRouteInfo _ Overview, storing all found message information meeting conditions in a structure SigRouteInfo _ Temp (the structure temporarily storing signal forwarding information comprises the transmitting network segment, the transmitting node, the signal name, the transmitting ID and the routing information), removing invalid routing information in the SigRouteInfo _ Temp, storing the removed content in the structure, and finally storing the structure (the content of the SigRouteInfo, the signal name, the transmitting ID and the routing information comprise the transmitting information, the routing information and the routing information, wherein the structure is used for removing the invalid routing information stored in the structure.
Step 3, configuring the whole frame of routing information in the Pdu module: and writing the identified whole-frame routing information into an arxml file according to the format of a PduR module in the autosar.
The detailed process of this step is as shown in fig. 5, the writing of the whole frame of routing configuration information into the arxml file is to write the source information and the destination information of the whole frame of routing according to the format of the PduR module in the autosar. Firstly, establishing a writable arxml file, writing the content of a header part according to the arxml file format of an autosar format, ensuring the integrity of the file, then searching a sending node in an overall frame routing structure MsgrouteInfo as a GW message, if the message is a Source message, storing the message into a structure MsgrouteInfo _ Source (a structure for storing the Source information of the overall frame routing message information, wherein structural elements comprise a sending network segment, a sending node, a period, a sending ID, a length and routing information), and comprise a sending network segment, a sending node, a period, a sending ID, a length and routing information; otherwise, indicating that the message is a target message, storing the message into a structure MsgrouteInfo _ Destination (a structure storing target information of the whole frame of routing message information, wherein structure elements comprise a sending network segment, a sending node, a period, a sending ID, a length and routing information), and the structure elements comprise a sending network segment, a sending node, a period, a sending ID, a length and routing information; traversing the MsgrouteInfo _ Source in the structure according to the ID to obtain the information of the Source message required by writing the arxml file, combining character segments, and writing the Source information into the arxml file according to a PduR module format in the autosar; and then searching a message with the same ID as that in the current source structure body in the MsgrouteInfo _ Destination of the structure body to obtain the information of the corresponding target message, combining character segments, and then writing the target information into an arxml file according to a Pdu module format in autosar. And finally, writing the content of the tail part of the arxml file at the end of the file according to the autosar format.
Step 4, configuring signal routing information in the Com module: and writing the identified signal routing information into an arxml file according to the format of the Com module in the autosar.
The detailed flow of this step is as shown in fig. 6, the writing of the signal routing configuration information into the arxml file is to write the source and destination information of the signal routing according to the PduR module format in the autosar. Firstly, a writable arxml file is created, then the header content of the file is written in according to the autosar format, then the source network segment, the source sender and the source ID of the signal are obtained from the element RouteMark (routing label) in the signal routing structure Sigrouteinfo, the combination of the character segments is carried out, then the source information and the destination information are written in the arxml file according to the COM module format in the autosar, and finally the end part content of the arxml file in the autosar format is written in.
Step 5, generating a routing information configuration file: and creating a file with writable arxml format file attribute through a matlab tool, and writing the whole frame routing configuration information and the signal routing configuration information into the arxml.
The method CAN quickly identify the routing relation in the CAN matrix, realize the configuration of the routing relation of the whole frame according to the identified routing relation, realize the configuration of the routing relation of the signal according to the identified routing relation, and finally output the routing relation of the whole frame and the routing relation of the signal to the arxml file, thereby realizing the automatic configuration of the routing information and improving the time efficiency of AUTOSAR configuration.
Further, an exemplary embodiment of the present application further provides an automatic generation apparatus for a controller software routing information configuration file based on an Autosar architecture, which includes functional units: the device comprises 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:
a loading unit configured to load a CAN protocol.
And the identifying unit is configured to identify the routing mapping relation, and comprises the steps of analyzing the whole frame of routing information in the CAN protocol and analyzing the signal routing information in the CAN protocol.
In an exemplary embodiment of the present application, the analyzing, by the identification unit, the whole frame of routing information in the CAN protocol specifically includes:
extracting original information in a summary table to a structure ALL _ OverView, wherein structure elements comprise network segments, nodes, periods, sending IDs, lengths and receiving nodes; the method comprises the steps of carrying out space removal processing on information in a structure, finding out messages sent by ALL GWs, storing the messages into the structure ALL _ GW _ Overview, then carrying out traversal query on the found messages sent by ALL GWs in the ALL _ Overview according to ID content, if a sending node with the same ID content and a non-GW is queried, considering the messages of the ID as a whole-frame routing message, storing corresponding information into MsgrouteInfo, wherein the structure comprises information including a sending network segment, a sending node, a period, an ID, a length and a receiving node; otherwise, the message of the ID is an information routing message, corresponding information is stored in SigRouteInfo _ Overview, and the structure body comprises information including a sending network segment, a sending node, a period, an ID, a length and a receiving node.
In an exemplary embodiment of the present application, the analyzing, by the identification unit, the signal routing information in the CAN protocol specifically includes:
firstly, extracting original information in a protocol Matrix and storing the original information in a structural body Tab _ Matrix0, wherein elements contained in the structural body comprise a sending network segment, a sending node, a signal name, a sending ID, routing information and a receiving node; in Tab _ Matrix0, finding out elements with the same ID and the same network segment as those in SigRouteInfo _ Overview, storing all found message information meeting the conditions into a structure SigRouteInfo _ Temp, wherein the elements contained in the structure comprise a sending network segment, a sending node, a signal name, a sending ID and routing information, and finally removing invalid routing information in the SigRouteInfo _ Temp and storing the invalid routing information in the structure SigRouteInfo, wherein the elements comprise the sending network segment, the sending node, the signal name, the sending ID and the routing information.
And the first configuration unit is configured to configure the whole frame of routing information in the PdauR module, and write the identified whole frame of routing information into an arxml file according to the format of the PdauR module in the autosar. The method specifically comprises the following steps: firstly, creating an arxml file, writing the contents of a header part according to an arxml file format specified by autosar, searching a sending node in a whole frame routing structure MsgrouteInfo as a GW message, if yes, indicating that the message is a Source message, and storing the information into a structure MsgrouteInfo _ Source, wherein structural elements comprise a sending network segment, a sending node, a period, a sending ID, a length and routing information; otherwise, indicating that the message is a target message, and storing the information into a structure MsgrouteInfo _ Destination, wherein the structure elements comprise a sending network segment, a sending node, a period, a sending ID, a length and routing information; traversing the MsgrouteInfo _ Source in the structure according to the ID to obtain Source message information required by writing an arxml file, combining character segments, and writing the Source message information into the arxml file according to a Pdu module format in autosar; then, searching a message with the same ID as that in the current source structure body in the MsgrouteInfo _ Destination of the structure body to obtain the information of a corresponding target message, combining character segments, and writing the target information into an arxml file according to a Pdu module format in autosar; and finally, writing the content of the tail part of the arxml file at the end of the file according to the autosar format.
And 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 according to the format of the Com module in the autosar. The method specifically comprises the following steps: firstly, creating an arxml file, writing the head part content of the file according to an autosar format, then obtaining a source network segment, a source sender and a source ID of a signal from an element RouteMark in a signal routing structure Sigrouteinfo, combining character segments, then writing source information and target information into the arxml file according to a COM module format in the autosar, and finally writing the tail part content of the arxml file in the autosar format.
The configuration file generation module is configured to generate a routing information configuration file, create a file with a writable arxml format file attribute through a matlab tool, and write the whole frame of routing configuration information and the signal routing configuration information into the arxml.
As can be seen from the detailed explanation of the above embodiment, the present application automatically identifies the route mapping relationship, automatically implements configuration of the entire frame of route information in the PduR module, automatically implements configuration of the signal route in the Com module, and automatically outputs the route information configuration file, which can improve the time efficiency of AUTOSAR configuration, and better solve the problems of low efficiency of route relationship configuration and unreliable configuration quality in the prior art.

Claims (10)

1. A method for automatically generating a routing information configuration file of controller software based on an Autosar architecture is characterized by comprising the following steps:
step 1, loading a CAN protocol;
step 2, identifying the route mapping relation: analyzing the whole frame of routing information in the CAN protocol and analyzing the signal routing information in the CAN protocol; the method comprises the steps of screening message IDs of whole-frame routing and routing mapping relations of the message IDs and the routing mapping relations through identifying a summary table in a CAN protocol, screening specific signals and related information of signal routing by combining identifying a matrix table in the CAN protocol, and analyzing information for whole-frame routing information configuration and signal routing information configuration;
step 3, configuring the whole frame of routing information in the Pdu module: writing the identified whole-frame routing information into an arxml file according to the format of a Pdu module in the autosar;
step 4, configuring signal routing information in the Com module: writing the identified signal routing information into an arxml file according to the format of the Com module in the autosar;
step 5, generating a routing information configuration file: and creating a file in an arxml format through a matlab tool, and writing the routing configuration information of the whole frame and the signal routing configuration information into the arxml.
2. The method of claim 1, wherein in step 2, analyzing the entire frame of routing information in the CAN protocol comprises: firstly, extracting original information in a summary table to a structure ALL _ OverView, wherein structure elements comprise network segments, nodes, periods, sending IDs (identities), lengths and receiving nodes; the method comprises the steps of carrying out space removal processing on information in a structure, finding out messages sent by ALL GWs, storing the messages into the structure ALL _ GW _ Overview, then carrying out traversal query on the found messages sent by ALL GWs in the ALL _ Overview according to ID content, if a sending node with the same ID content and a non-GW is queried, considering the messages of the ID as a whole-frame routing message, storing corresponding information into MsgrouteInfo, wherein the structure comprises information including a sending network segment, a sending node, a period, an ID, a length and a receiving node; otherwise, the ID message is an information routing message, corresponding information is stored in SigRouteInfo _ Overview, and the structure comprises information including a sending network segment, a sending node, a period, an ID, a length and a receiving node.
3. The method according to claim 2, wherein the analyzing the signal routing information in the CAN protocol in step 2 includes: extracting original information in a protocol Matrix and storing the original information in a structural body Tab _ Matrix0, wherein elements contained in the structural body comprise a sending network segment, a sending node, a signal name, a sending ID, routing information and a receiving node; in Tab _ Matrix0, finding out elements with the same ID and the same network segment as those in SigRouteInfo _ Overview, storing all found message information meeting the conditions into a structure SigRouteInfo _ Temp, wherein the elements contained in the structure comprise a sending network segment, a sending node, a signal name, a sending ID and routing information, and finally removing invalid routing information in the SigRouteInfo _ Temp and storing the invalid routing information in the structure SigRouteInfo, wherein the elements comprise the sending network segment, the sending node, the signal name, the sending ID and the routing information.
4. The method for automatically generating the controller software routing information configuration file based on the Autosar architecture according to claim 2 or 3, wherein the configuring of the entire frame of routing information in the PduR module in step 3 specifically includes: firstly, creating an arxml file, writing the contents of a header part according to an arxml file format specified by autosar, searching a sending node in a whole frame routing structure MsgrouteInfo as a GW message, if yes, indicating that the message is a Source message, and storing the information into a structure MsgrouteInfo _ Source, wherein structural elements comprise a sending network segment, a sending node, a period, a sending ID, a length and routing information; otherwise, indicating that the message is a target message, and storing the information into a structure MsgrouteInfo _ Destination, wherein the structure elements comprise a sending network segment, a sending node, a period, a sending ID, a length and routing information; traversing the MsgrouteInfo _ Source in the structure according to the ID to obtain Source message information required by writing an arxml file, combining character segments, and writing the Source message information into the arxml file according to a Pdu module format in autosar; then, searching a message with the same ID as that in the current source structure body in the MsgrouteInfo _ Destination of the structure body to obtain the information of a corresponding target message, combining character segments, and writing the target information into an arxml file according to a Pdu module format in autosar; and finally, writing the content of the tail part of the arxml file at the end of the file according to the autosar format.
5. The automatic generation method of the controller software routing information configuration file based on the Autosar architecture according to claim 4, wherein the configuring of the signal routing information in the Com module in step 4 specifically includes: firstly, creating an arxml file, writing the head part content of the file according to an autosar format, then obtaining a source network segment, a source sender and a source ID of a signal from an element RouteMark in a signal routing structure SigrouteInfo, combining character segments, then writing source information and target information into an arxml file according to a COM module format in the autosar, and finally writing the tail part content of the arxml file in the autosar format.
6. An automatic generation device for controller software routing information configuration files based on an Autosar architecture is characterized by comprising the following components:
a loading unit configured to load a CAN protocol;
the identifying unit is configured to identify a routing mapping relation, and comprises the steps of analyzing the whole frame of routing information in the CAN protocol and analyzing the signal routing information in the CAN protocol; the message ID of the whole frame route and the route mapping relation thereof are screened out by identifying a summary table in the CAN protocol, and the specific signal and the related information of the signal route are screened out by combining the matrix table in the CAN protocol, so that the information for the whole frame route information configuration and the signal route information configuration is analyzed;
the first configuration unit is configured to configure the whole-frame routing information in the Pdu module, and write the identified whole-frame routing information into an arxml file according to the format of the Pdu module in the 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 according to the format of the Com module in the autosar;
the configuration file generation module is configured to generate a routing information configuration file, create a file with a writable arxml format file attribute through a matlab tool, and write the whole frame of routing configuration information and the signal routing configuration information into the arxml.
7. The automatic generation device of the controller software routing information configuration file based on the Autosar architecture as claimed in claim 6, wherein the parsing, by the identification unit, of the entire frame of routing information in the CAN protocol specifically includes: extracting original information in a summary table to a structure ALL _ OverView, wherein structure elements comprise network segments, nodes, periods, sending IDs, lengths and receiving nodes; carrying out de-spaceization processing on information in a structure, finding out messages sent by ALL GWs, storing the messages into a structure ALL _ GW _ Overview, then carrying out traversal query on the messages sent by ALL the found GWs in the ALL _ Overview according to ID content, if a sending node with the same ID content and non-GW is queried, considering the message with the ID as a whole-frame routing message, and storing corresponding information in MsgrouteInfo, wherein the structure comprises information including a sending network segment, a sending node, a period, an ID, a length and a receiving node; otherwise, the ID message is an information routing message, corresponding information is stored in SigRouteInfo _ Overview, and the structure comprises information including a sending network segment, a sending node, a period, an ID, a length and a receiving node.
8. The automatic generation method for the controller software routing information configuration file based on the Autosar architecture as claimed in claim 7, wherein the analyzing the signal routing information in the CAN protocol by the identification unit specifically includes: extracting original information in a protocol Matrix and storing the original information in a structural body Tab _ Matrix0, wherein elements contained in the structural body comprise a sending network segment, a sending node, a signal name, a sending ID, routing information and a receiving node; in Tab _ Matrix0, finding out elements with the same ID and the same network segment as those in SigRouteInfo _ Overview, storing all found message information meeting the conditions into a structure SigRouteInfo _ Temp, wherein the elements contained in the structure comprise a sending network segment, a sending node, a signal name, a sending ID and routing information, and finally removing invalid routing information in the SigRouteInfo _ Temp and storing the invalid routing information in the structure SigRouteInfo, wherein the elements comprise the sending network segment, the sending node, the signal name, the sending ID and the routing information.
9. The automatic generation device of the controller software routing information configuration file based on the Autosar architecture according to claim 7 or 8, wherein the configuring, by the first configuration unit, of the entire frame of routing information in the PduR module specifically includes: firstly, creating an arxml file, writing the contents of a header part according to an arxml file format specified by autosar, searching a sending node in a whole frame routing structure MsgrouteInfo as a GW message, if yes, indicating that the message is a Source message, and storing the information into a structure MsgrouteInfo _ Source, wherein structural elements comprise a sending network segment, a sending node, a period, a sending ID, a length and routing information; otherwise, indicating that the message is a target message, and storing the information into a structure MsgrouteInfo _ Destination, wherein the structure elements comprise a sending network segment, a sending node, a period, a sending ID, a length and routing information; traversing the MsgrouteInfo _ Source in the structure according to the ID to obtain Source message information required by writing an arxml file, combining character segments, and writing the Source message information into the arxml file according to a Pdu module format in autosar; then, searching a message with the same ID as that in the current source structure body in the MsgrouteInfo _ Destination of the structure body to obtain the information of a corresponding target message, combining character segments, and writing the target information into an arxml file according to a Pdu module format in autosar; and finally, writing the content of the tail part of the arxml file at the end of the file according to the autosar format.
10. The method according to claim 9, wherein the configuring, by the second configuring unit, the signal routing information in the Com module specifically includes: firstly, creating an arxml file, writing the head part content of the file according to an autosar format, then obtaining a source network segment, a source sender and a source ID of a signal from an element RouteMark in a signal routing structure Sigrouteinfo, combining character segments, then writing source information and target information into the arxml file according to a COM module format in the autosar, and finally writing the tail part content of the arxml file in the autosar format.
CN202211343088.8A 2022-10-31 2022-10-31 Automatic generation method and device for controller software routing information configuration file based on Autosar architecture Pending CN115878212A (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN202211343088.8A CN115878212A (en) 2022-10-31 2022-10-31 Automatic generation method and device for controller software routing information configuration file based on Autosar architecture

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN202211343088.8A CN115878212A (en) 2022-10-31 2022-10-31 Automatic generation method and device for controller software routing information configuration file based on Autosar architecture

Publications (1)

Publication Number Publication Date
CN115878212A true CN115878212A (en) 2023-03-31

Family

ID=85759162

Family Applications (1)

Application Number Title Priority Date Filing Date
CN202211343088.8A Pending CN115878212A (en) 2022-10-31 2022-10-31 Automatic generation method and device for controller software routing information configuration file based on Autosar architecture

Country Status (1)

Country Link
CN (1) CN115878212A (en)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN116431119A (en) * 2023-06-12 2023-07-14 上海鉴智其迹科技有限公司 Software component port creation method and device, electronic equipment and storage medium

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN116431119A (en) * 2023-06-12 2023-07-14 上海鉴智其迹科技有限公司 Software component port creation method and device, electronic equipment and storage medium
CN116431119B (en) * 2023-06-12 2023-08-29 上海鉴智其迹科技有限公司 Software component port creation method and device, electronic equipment and storage medium

Similar Documents

Publication Publication Date Title
US11188400B2 (en) System, method and computer program product for sharing information in a distributed framework
Grzemba MOST: the automotive multimedia network
CN115878212A (en) Automatic generation method and device for controller software routing information configuration file based on Autosar architecture
CN113596017B (en) Protocol analysis method and device, soft gateway and storage medium
CN108804100B (en) Method and device for creating interface element, storage medium and mobile terminal
CN114047970A (en) Configuration method and system of AUTOSAR (automotive open system architecture) architecture software
CN112565194A (en) Transaction link tracking method, electronic device and storage medium
CN114995878A (en) Method for automatically generating network data forwarding plane driver code
CN108093028B (en) Method and apparatus for reproducing content based on presentation time in vehicle network
CN114422624B (en) Data receiving method
CN116450109A (en) Modbus communication library adaptation method under MATLAB and CCS combined development mode
US7457881B2 (en) Method and apparatus for sending data from one protocol layer to another
CN109254774A (en) The management method and device of code in software development system
CN112054955B (en) Gateway-based device communication method
CN112866294B (en) Multi-protocol adaptation method, device and readable storage medium
CN113342426A (en) Application layer software component integration method and system
CN118101494B (en) Network control plane protocol simulation method and device, electronic equipment and storage medium
CN117112048B (en) UDS Clinet Implementation Method Based on XML File
CN115277886B (en) Vehicle data acquisition method based on data distribution service
US20240275706A1 (en) Information processing method
CN114461422A (en) Vehicle application communication method, device, equipment and medium
CN117812171A (en) Vehicle data analysis method and device, computer equipment, storage medium and vehicle
Bishop et al. The TCP specification: A quick introduction
CN117032754A (en) OTA (over the air) refreshing method and device, readable storage medium and electronic equipment
CN117527938A (en) Automatic configuration method, device and equipment for communication protocol stack applied to vehicle

Legal Events

Date Code Title Description
PB01 Publication
PB01 Publication
SE01 Entry into force of request for substantive examination
SE01 Entry into force of request for substantive examination