Autosar software component development method, device, equipment and storage medium

Abstract

The application provides a Matlab / Simulink-based AUTOSAR software component development method and device, equipment and a computer readable storage medium. The Matlab / Simulink-based AUTOSAR software component development method comprises the following steps: placing Simulink models of all function modules of a controller application layer into a function call subsystem to establish a software component; finding input signals of all Simulink models and taking the input signals of all Simulink models as input signals of the software component; finding output signals of all Simulink models and taking the output signals of all Simulink models as output signals of the software component; and establishing a function call as an RTE event of the software component. According to the embodiment of the application, the workload can be reduced, the work efficiency is improved, and the work content is simplified.

Description

Technical Field

[0001] The present invention relates to the field of software component development, and in particular to a Matlab / Simulink-based AUTOSAR software component development method, apparatus, device, and computer-readable storage medium. Background Art

[0002] In the bottom-up workflow of the AUTomotive Open System Architecture (AUTOSAR) system solution, it is necessary to establish an application layer software component (SWC) based on the existing Simulink model and configure the generated code and arxml description file.

[0003] Currently, when constructing software components in Simulink, different software components can be constructed according to different users. In the vehicle control unit (VCU), multiple software components can be constructed according to different functions. However, constructing multiple software components increases the corresponding configuration and variable connections between software components, which greatly increases the workload.

[0004] Therefore, how to reduce workload, thereby improving work efficiency and simplifying work content is a technical problem that technical personnel in this field urgently need to solve. Summary of the Invention

[0005] The embodiments of the present application provide a Matlab / Simulink-based AUTOSAR software component development method, apparatus, device, and computer-readable storage medium, which can reduce workload, thereby improving work efficiency and simplifying work content.

[0006] In a first aspect, an embodiment of the present application provides an AUTOSAR software component development method based on Matlab / Simulink, comprising:

[0007] Place the Simulink models of all functional modules of the controller application layer into a function call subsystem to create a software component;

[0008] Find the input signals of all Simulink models and use the system input signals of all Simulink models as the input signals of software components;

[0009] Find the system output signals of all Simulink models and use the output signals of all Simulink models as the output signals of software components;

[0010] A function call is established as an RTE event of the software component.

[0011] Optionally, all input signals of the Simulink model are found, including:

[0012] All system signals input from the outside of the Simulink model are found, including at least can signals and LIN signals.

[0013] Optionally, all output signals of the Simulink model are found, including:

[0014] All system signals output to the outside of the Simulink model are found, including at least can signals and LIN signals.

[0015] Optionally, the method further comprises:

[0016] In the case that there is a change in the Simulink model, the code and the arxml description file can be regenerated without reconfiguring the software component SWC, wherein the change in the Simulink model includes a change in internal interfaces.

[0017] The code is only used for program development, and the arxml description file is imported into ISOLAR-A / B to perform AUTOSAR development; wherein, because the change is realized through a SWC, the SWC signal matching does not need to be performed again.

[0018] In a second aspect, an embodiment of the present application provides an AUTOSAR software component development device based on Matlab / Simulink, comprising:

[0019] The software component establishing module is configured to place Simulink models of all function modules of the controller application layer into a function call subsystem, and establish a software component.

[0020] The input signal finding module is configured to find all input signals of the Simulink model, and take system input signals of all Simulink models as input signals of the software component.

[0021] The output signal finding module is configured to find all output signals of the Simulink model, and take system output signals of all Simulink models as output signals of the software component.

[0022] The RTE event establishing module is configured to establish a function call as an RTE event of the software component.

[0023] Optionally, the input signal finding module is configured to find all system signals input from the outside of the Simulink model, including at least can signals and LIN signals.

[0024] Optionally, an output signal searching module is configured to search for at least system signals including can signals and LIN signals output by all Simulink models to the outside.

[0025] Optionally, the device further comprises:

[0026] The generating module is configured to regenerate the code and the arxml description file without reconfiguring the software component SWC in the case that there is a change in the Simulink model; wherein the change in the Simulink model includes a change in internal interfaces.

[0027] The importing module is configured to import the code and the arxml description file into ISOLAR-A / B for program development and AUTOSAR development; wherein, because the implementation is realized by one SWC, it is not necessary to re-perform SWC signal matching.

[0028] In a third aspect, an electronic device is provided, and the electronic device comprises a processor and a memory storing computer program instructions.

[0029] The processor executes the computer program instructions to implement the Matlab / Simulink-based AUTOSAR software component development method according to the first aspect.

[0030] In a fourth aspect, a computer readable storage medium is provided, and the computer readable storage medium stores computer program instructions, and the computer program instructions are executed by a processor to implement the Matlab / Simulink-based AUTOSAR software component development method according to the first aspect.

[0031] The Matlab / Simulink-based AUTOSAR software component development method, device, electronic device and computer readable storage medium provided in the embodiments of the present application can reduce workload, thereby improving work efficiency and simplifying work content.

[0032] The Matlab / Simulink-based AUTOSAR software component development method comprises the following steps: placing Simulink models of all function modules of a controller application layer into a function call subsystem to establish a software component; searching for system input signals of all Simulink models and taking the input signals of all Simulink models as input signals of the software component; searching for system output signals of all Simulink models and taking the output signals of all Simulink models as output signals of the software component; and establishing a function call as an RTE event of the software component.

[0033] It can be seen that the method only needs to establish one software component, greatly reduces the workload, and does not need to change the configuration of AUTOSAR when the system signal input port is unchanged during subsequent Simulink model modification, which is very convenient; reduces the workload of AUTOSAR development, improves work efficiency, simplifies work content, makes Simulink model modification have no influence on subsequent AUTOSAR configuration; improves the work efficiency of AUTOSAR development; reduces the human cost of software development; makes the application layer Simulink model modification have no influence on subsequent AUTOSAR configuration; and makes the developer not need to understand the internal application layer Simulink model to develop the SWC software component. BRIEF DESCRIPTION OF DRAWINGS

[0034] In order to more clearly illustrate the specific embodiments of the present application or the technical solutions in the prior art, the drawings needed to be used in the specific embodiments or the prior art description will be briefly introduced. Obviously, the drawings in the following description are some embodiments of the present application, and other drawings can be obtained by those skilled in the art without creative labor on the basis of these drawings.

[0035] Figure 1 is a flowchart of the prior art controller application layer software component development method;

[0036] Figure 2 is a flowchart of the Matlab / Simulink-based AUTOSAR software component development method provided by an embodiment of the present application;

[0037] Figure 3 is a schematic diagram of the prior controller application layer software component provided by an embodiment of the present application;

[0038] Figure 4 is a structural schematic diagram of the Matlab / Simulink-based AUTOSAR software component development device provided by an embodiment of the present application;

[0039] Figure 5 is a structural schematic diagram of an electronic device provided by an embodiment of the present application. DETAILED DESCRIPTION

[0040] The features and exemplary embodiments of various aspects of the present application will be described below in detail, in order to make the purposes, technical solutions and advantages of the present application more clear and apparent, the present application will be further described in detail below in combination with the drawings and specific embodiments. It should be understood that the specific embodiments described herein are only intended to explain the present application, but not to limit the present application. For those skilled in the art, the present application can be implemented without some of these specific details. The following description of the embodiments is only to provide a better understanding of the present application by showing examples of the present application.

[0041] It should be noted that, in this paper, relational terms such as first and second are only used to distinguish one entity or operation from another entity or operation, and do not necessarily require or imply that there is any such actual relationship or order between these entities or operations. Moreover, the terms "include", "contain" or any other variants thereof are intended to cover non-exclusive inclusion, so that the process, method, article or device including a series of elements not only includes those elements, but also includes other elements not explicitly listed or inherent to such process, method, article or device. Without more limitations, the elements defined by the statement "include" do not exclude the presence of other identical elements in the process, method, article or device including the elements.

[0042] In the "bottom-up" workflow of the AUTomotive Open System Architecture (AUTOSAR) system solution, application layer software components (SWC) need to be established based on existing Simulink models, and code and arxml description files are configured and generated.

[0043] As shown in Figure 1 At present, software components can be constructed in Simulink, different software components can be constructed according to different users, and multiple software components can be constructed according to different functions in a vehicle control unit (VCU), but constructing multiple software components increases the corresponding configuration and variable connection between software components, which increases a lot of workload.

[0044] In order to solve the problems in the prior art, the embodiments of the present application provide an AUTOSAR software component development method, device and equipment based on Matlab / Simulink and a computer readable storage medium. First, the AUTOSAR software component development method based on Matlab / Simulink provided by the embodiments of the present application will be introduced.

[0045] Figure 2 A flowchart of a Matlab / Simulink-based AUTOSAR software component development method provided by an embodiment of the present application is shown. As shown in Figure 2 the Matlab / Simulink-based AUTOSAR software component development method includes:

[0046] S201, placing Simulink models of all function modules of a controller application layer into a function call subsystem to establish a software component.

[0047] The present application uses the SWC software component establishment technology of AUTOSAR and the Simulink technology to realize establishment of the SWC software component of the controller application layer software.

[0048] First, all Simulink models of the controller application layer are placed into a Function Call Subsystem, which is equivalent to establishing a running entity, and there is no need to establish multiple SWC software components and running entities. For details, see Figure 3 , Figure 3 is a schematic diagram of the present controller application layer software component provided by an embodiment of the present application.

[0049] As shown in Figure 3 , for the Simulink model of the existing application layer function of the controller, only an AUTOSAR software component and a running entity need to be established. Only the external input and output signals of the Simulink model need to be determined, and there is no need to analyze the internal signals and logic. When designing in ISOLAR-A / B, only external ports need to be established, and there is no need for internal ports. Modification of the internal model of the application layer Simulink has no influence on subsequent AUTOSAR configuration.

[0050] S202, finding all input signals of the Simulink models, and taking all system input signals of the Simulink models as input signals of the software component.

[0051] In an embodiment, finding all input signals of the Simulink models includes: finding all system signals including at least can signals and LIN signals input from the outside of the Simulink models.

[0052] Specifically, all external input signals in the controller application layer Simulink model that have not been preprocessed by the application layer are found, including system signals such as can signals and LIN signals, and these signals are taken as input signals of the Function Call Subsystem. Only external input signals need to be found, and there is no need to analyze internal signals and implement logic.

[0053] S203, find all output signals of the Simulink models, and take all system output signals of the Simulink models as the output signals of the software component.

[0054] In one embodiment, the finding of all output signals of the Simulink models comprises: finding all system signals including at least can signals and LIN signals outputted by the Simulink models to the outside.

[0055] Specifically, all signals outputted by the controller application layer Simulink models to the outside including can signals, LIN signals and other system signals are found, and these signals are taken as the output signals of the Function Call Subsystem, without the need of analyzing the output signals inside the models.

[0056] S204, establishing a function call as an RTE event of the software component.

[0057] Specifically, a function call Function Call is established as the RTE event of the running entity, without the need of establishing multiple function calls.

[0058] In one embodiment, the method further comprises: in the case of changes inside the Simulink models, without the need of reconfiguring the software component SWC, the code and the arxml description file can be regenerated; wherein the changes inside the Simulink models include changes of internal interfaces.

[0059] Only the code is used for program development, and the arxml description file is imported into ISOLAR-A / B to perform AUTOSAR development; wherein, because of the implementation by one SWC, the SWC signal matching does not need to be performed again.

[0060] Specifically, in the case of changes inside the application layer Simulink models, without the need of changing the established SWC software configuration, the code is directly regenerated for program development, and the arxml description file is imported into ISOLAR-A / B to perform AUTOSAR development, without the need of making other changes such as port changes.

[0061] Based on the above embodiments, the method only needs to establish one software component, greatly reduces the workload, and if the system signal input port is unchanged when the subsequent Simulink model is changed, the configuration of AUTOSAR does not need to be changed, which is very convenient; reduces the workload of AUTOSAR development, improves work efficiency, simplifies work content, makes the Simulink model modification have no influence on the subsequent AUTOSAR configuration; improves the work efficiency of AUTOSAR development; reduces the human cost of software development; makes the application layer Simulink model modification have no influence on the subsequent AUTOSAR configuration; makes the developer not need to understand the internal of the application layer Simulink model, and can develop the SWC software component. The single controller application layer Simulink model establishes the SWC software component of AUTOSAR to realize quickly, reduces the workload, and improves the flexibility of Simulink model modification.

[0062] Figure 4 is a structural schematic diagram of an apparatus for developing an AUTOSAR software component based on Matlab / Simulink provided in an embodiment of the present application, as shown in the figure, the apparatus for developing an AUTOSAR software component based on Matlab / Simulink comprises: Figure 4

[0063] The software component establishing module 401 is configured to place the Simulink model of all functional modules of the controller application layer into a function call subsystem, and establish a software component.

[0064] The input signal searching module 402 is configured to search for the system input signals of all Simulink models, and take the system input signals of all Simulink models as the input signals of the software component.

[0065] The output signal searching module 403 is configured to search for the system output signals of all Simulink models, and take the system output signals of all Simulink models as the output signals of the software component.

[0066] The RTE event establishing module 404 is configured to establish a function call as the RTE event of the software component.

[0067] In an embodiment, the input signal searching module 402 is configured to search for at least the system signals including can signals and LIN signals input from the outside of all Simulink models.

[0068] In an embodiment, the output signal searching module 403 is configured to search for at least the system signals including can signals and LIN signals output to the outside of all Simulink models.

[0069] ​In one embodiment, the apparatus further comprises:

[0070] The generating module is configured to regenerate the code and the arxml description file without reconfiguring the software component SWC in the case that there is a change in the Simulink model; wherein the change in the Simulink model includes a change in the internal interface.

[0071] The importing module is configured to import the code for program development and the arxml description file into ISOLAR-A / B to perform AUTOSAR development; wherein the SWC signal matching is not required to be performed again because the implementation is realized through one SWC.

[0072] Figure 4 Each module / unit in the apparatus has the function of implementing each step in the method and can achieve the corresponding technical effects, and for brevity, will not be described here. Figure 2

[0073] Figure 5 FIG. 1 shows a structural schematic diagram of an electronic device according to an embodiment of the present application.

[0074] The electronic device can include a processor 501 and a memory 502 having stored computer program instructions.

[0075] Specifically, the processor 501 can include a central processing unit (CPU), or an application specific integrated circuit (ASIC), or one or more integrated circuits configured to implement one or more embodiments of the present application.

[0076] The memory 502 can include a mass storage for data or instructions. By way of example and not limitation, the memory 502 can include a hard disk drive (HDD), a floppy disk drive, a flash memory, an optical disk, a magneto-optical disk, a magnetic tape, or a universal serial bus (USB) drive or a combination of two or more of these. The memory 502 can include removable or non-removable (or fixed) media, where appropriate. The memory 502 can be internal or external to the electronic device, where appropriate. In certain embodiments, the memory 502 can be a non-volatile solid-state memory.

[0077] ​In one embodiment, the memory 502 can be a Read Only Memory (ROM). In one embodiment, the ROM can be a mask programmed ROM, a Programmable ROM (PROM), an Erasable PROM (EPROM), an Electrically Erasable PROM (EEPROM), an Electrically Alterable ROM (EAROM), or a flash memory, or a combination of two or more of these.

[0078] The processor 501 implements any one of the above-described embodiments of the Matlab / Simulink-based AUTOSAR software component development method by reading and executing computer program instructions stored in the memory 502.

[0079] In one example, the electronic device can further include a communication interface 503 and a bus 510. As shown, the processor 501, the memory 502, and the communication interface 503 are connected through the bus 510 and complete communication therebetween. Figure 5

[0080] The communication interface 503 is mainly used to realize the communication between the modules, devices, units, and / or equipment in the embodiments of the present application.

[0081] The bus 510 includes hardware, software, or both, which couples the components of the electronic device to each other. By way of example, and not limitation, the bus can include an Accelerated Graphics Port (AGP) or other graphics bus, an Enhanced Industry Standard Architecture (EISA) bus, a Front Side Bus (FSB), a HyperTransport (HT) interconnect, an Industry Standard Architecture (ISA) bus, an InfiniBand interconnect, a Low Pin Count (LPC) bus, a memory bus, a Micro Channel Architecture (MCA) bus, a Peripheral Component Interconnect (PCI) bus, a PCI-Express (PCI-X) bus, a Serial Advanced Technology Attachment (SATA) bus, a Video Electronics Standards Association Local (VLB) bus, or another suitable bus or interconnect, or a combination of two or more of these. Where appropriate, the bus 510 can include one or more buses. Although the present application describes and illustrates a particular bus, the present application contemplates any suitable bus or interconnect.

[0082] In addition, in combination with the Matlab / Simulink-based AUTOSAR software component development method in the above-described embodiments, the embodiments of the present application can provide a computer-readable storage medium to implement. The computer-readable storage medium has computer program instructions stored thereon; the computer program instructions are executed by a processor to implement any one of the above-described embodiments of the Matlab / Simulink-based AUTOSAR software component development method.

[0083] ​It should be understood that the present application is not limited to the specific configurations and processes described above and illustrated in the figures. For the sake of brevity, a detailed description of known methods is omitted here. In the above embodiments, several specific steps are described and illustrated as examples. However, the method process of the present application is not limited to the specific steps described and illustrated. Those skilled in the art can make various changes, modifications, and additions, or change the order of the steps after understanding the spirit of the present application.

[0084] The functional modules shown in the above-described block diagram can be implemented as hardware, software, firmware or a combination thereof. When implemented in hardware, it can be, for example, an electronic circuit, an application specific integrated circuit (ASIC), appropriate firmware, a plug-in unit, a function card or the like. When implemented in software, the elements of the present application are programs or code segments that are used to perform the required tasks. The program or code segment can be stored in a machine-readable medium, or transmitted on a transmission medium or a communication link by a data signal carried in a carrier wave. "Machine-readable medium" can include any medium that can store or transmit information. Examples of machine-readable media include electronic circuits, semiconductor memory devices, ROMs, flash memories, erasable ROMs (EROMs), floppy disks, CD-ROMs, optical disks, hard disks, optical fiber media, radio frequency (RF) links, etc. The code segment can be downloaded via a computer network such as the Internet, an intranet, etc.

[0085] It should also be noted that the exemplary embodiments mentioned in this application describe some methods or systems based on a series of steps or devices. However, this application is not limited to the order of the above steps. In other words, the steps can be performed in the order mentioned in the embodiments, or in a different order, or several steps can be performed simultaneously.

[0086] Aspects of the present application have been described above with reference to the flowcharts and / or block diagrams of the methods, devices (systems) and computer program products according to the embodiments of the present application. It should be understood that each box in the flowchart and / or block diagram and the combination of each box in the flowchart and / or block diagram can be implemented by computer program instructions. These computer program instructions can be provided to the processor of a general-purpose computer, a special-purpose computer or other programmable data processing device to produce a machine so that these instructions executed via the processor of the computer or other programmable data processing device enable the implementation of the function / action specified in one or more boxes of the flowchart and / or block diagram. This processor can be, but is not limited to, a general-purpose processor, a special-purpose processor, a special application processor or a field programmable logic circuit. It is also understood that each box in the block diagram and / or the flowchart and the combination of the boxes in the block diagram and / or the flowchart can also be implemented by the dedicated hardware that performs the specified function or action, or can be implemented by the combination of dedicated hardware and computer instructions.

[0087] The above merely describes a specific implementation of the present application. Those skilled in the art can clearly understand the specific working processes of the system, modules and units described above for the convenience and brevity of description, and the corresponding processes in the foregoing method embodiments can be referred to, which will not be described herein again. It should be understood that the protection scope of the present application is not limited in this way, and any person skilled in the art can easily think of various equivalent modifications or replacements within the technical range disclosed in the present application, and these modifications or replacements should be covered in the protection scope of the present application.

Claims

1. A Matlab / Simulink-based AUTOSAR software component development method, characterized in that: include: Put the Simulink models of all functional modules of the controller application layer into a function call subsystem to establish a software component and a running entity; Finding input signals of all Simulink models and using the input signals of all Simulink models as input signals of the software component; Finding output signals of all Simulink models, and using the output signals of all Simulink models as output signals of the software component; A function call is established as an RTE event of the software component.

2. The AUTOSAR software component development method based on Matlab / Simulink according to claim 1, characterized in that: The search for all Simulink model input signals includes: Find all system signals that are input from the outside to all Simulink models, including at least CAN signals and LIN signals.

3. The AUTOSAR software component development method based on Matlab / Simulink according to claim 1, characterized in that: The output signals of all Simulink models are found, including: Find all system signals output to the outside by Simulink models, including at least CAN signals and LIN signals.

4. The AUTOSAR software component development method based on Matlab / Simulink according to claim 1, characterized in that: The method further comprises: If there are changes within the Simulink model, the code and arxml description files can be regenerated without reconfiguring the software component SWC; changes within the Simulink model include changes to the internal interfaces; It is only necessary to use the code for program development and import the arxml description file into ISOLAR-A / B for AUTOSAR development. Since it is implemented through a SWC, there is no need to re-match the SWC signals.

5. A Matlab / Simulink-based AUTOSAR software component development device, characterized in that: include: The software component creation module is used to place the Simulink models of all functional modules of the controller application layer into a function call subsystem to create a software component and a running entity; An input signal search module is used to search for input signals of all Simulink models and use the input signals of all Simulink models as input signals of the software component; An output signal search module is used to search for output signals of all Simulink models and use the output signals of all Simulink models as output signals of the software component; The RTE event creation module is used to create a function call as the RTE event of the software component.

6. The Matlab / Simulink-based AUTOSAR software component development device according to claim 5, characterized in that: The input signal search module is used to search for system signals including at least CAN signals and LIN signals input from the outside to all Simulink models.

7. The AUTOSAR software component development device based on Matlab / Simulink according to claim 5, characterized in that: The output signal search module is used to search for system signals output to the outside by all Simulink models, including at least CAN signals and LIN signals.

8. The Matlab / Simulink-based AUTOSAR software component development device according to claim 5, characterized in that: The device further comprises: The generation module is used to regenerate code and arxml description files when there are changes within the Simulink model without reconfiguring the software component SWC; changes within the Simulink model include changes to internal interfaces; The import module is used to import the code for program development and the arxml description file into ISOLAR-A / B for AUTOSAR development; since it is implemented through a SWC, there is no need to re-match the SWC signals.

9. An electronic device, characterized in that: The electronic device includes: a processor and a memory storing computer program instructions; When the processor executes the computer program instructions, the Matlab / Simulink-based AUTOSAR software component development method according to any one of claims 1 to 4 is implemented.

10. A computer-readable storage medium, characterized in that The computer-readable storage medium stores computer program instructions, and when the computer program instructions are executed by a processor, the Matlab / Simulink-based AUTOSAR software component development method according to any one of claims 1 to 4 is implemented.

Images