CN115167831A - Software integration method and device based on AUTOSAR and use method - Google Patents
Software integration method and device based on AUTOSAR and use method Download PDFInfo
- Publication number
- CN115167831A CN115167831A CN202210849889.5A CN202210849889A CN115167831A CN 115167831 A CN115167831 A CN 115167831A CN 202210849889 A CN202210849889 A CN 202210849889A CN 115167831 A CN115167831 A CN 115167831A
- Authority
- CN
- China
- Prior art keywords
- interface
- file
- document
- software
- ports
- 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
Links
- 238000000034 method Methods 0.000 title claims abstract description 50
- 230000010354 integration Effects 0.000 title claims abstract description 29
- 230000004044 response Effects 0.000 claims description 12
- 238000012545 processing Methods 0.000 claims description 9
- 230000008676 import Effects 0.000 claims description 7
- 238000004891 communication Methods 0.000 claims description 6
- 230000003252 repetitive effect Effects 0.000 abstract description 6
- 230000008569 process Effects 0.000 description 9
- 230000006870 function Effects 0.000 description 6
- 238000004590 computer program Methods 0.000 description 5
- 238000011161 development Methods 0.000 description 4
- 230000004048 modification Effects 0.000 description 4
- 238000012986 modification Methods 0.000 description 4
- 238000010586 diagram Methods 0.000 description 3
- 230000008878 coupling Effects 0.000 description 2
- 238000010168 coupling process Methods 0.000 description 2
- 238000005859 coupling reaction Methods 0.000 description 2
- 238000010276 construction Methods 0.000 description 1
- 230000000694 effects Effects 0.000 description 1
- 238000012423 maintenance Methods 0.000 description 1
- 230000007246 mechanism Effects 0.000 description 1
- 238000013522 software testing Methods 0.000 description 1
- 238000006467 substitution reaction Methods 0.000 description 1
- 238000012360 testing method Methods 0.000 description 1
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/30—Creation or generation of source code
- G06F8/31—Programming languages or programming paradigms
- G06F8/315—Object-oriented languages
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/70—Software maintenance or management
- G06F8/71—Version control; Configuration management
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/44—Arrangements for executing specific programs
- G06F9/451—Execution arrangements for user interfaces
Landscapes
- Engineering & Computer Science (AREA)
- Software Systems (AREA)
- Theoretical Computer Science (AREA)
- General Engineering & Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Computing Systems (AREA)
- Human Computer Interaction (AREA)
- Computer Security & Cryptography (AREA)
- Stored Programmes (AREA)
Abstract
The invention relates to the field of software development, and discloses a software integration method, software integration equipment and a software application method based on AUTOSAR. The method comprises the following steps: acquiring developed application software, bottom layer software, a first interface relation document and a second interface relation document; when the application software is integrated with the bottom layer software, the description file, the DBC file, the first interface relation document and the second interface relation document of the bottom layer software are imported into an auxiliary tool; and responding to the configuration operation of the user on the auxiliary tool, generating new description content through the auxiliary tool, and modifying the description file according to the new description content. The invention reduces the repetitive work in software development and reduces the software development period.
Description
Technical Field
The invention relates to the field of software development, in particular to a software integration method and device based on AUTOSAR and a use method.
Background
With the rapid development of the automobile industry, more and more controllers are installed on automobiles, the scale and cost of software development are getting larger and larger, and an automobile Open System Architecture (Automotive Open System Architecture, AUTOSAR) is developed in order to achieve the standardization of software development and the automation of the development process, so as to reduce the cost of software development and improve the convenience of software development.
However, in the current AUTOSAR toolchain at home and abroad, the "automation" of software development cannot be completely realized, and especially when a large number of interfaces and association relations are required to be added during the realization of new functions, the software development must be completed manually by software developers, so that the process is complicated and time-consuming.
In view of the above, the present invention is particularly proposed.
Disclosure of Invention
In order to solve the technical problem, the invention provides a software integration method, equipment and a use method based on AUTOSAR, which reduce the repetitive work in software development and reduce the software development cycle.
The invention provides a software integration method based on AUTOSAR, which comprises the following steps:
acquiring developed application software, bottom layer software, a first interface relation document and a second interface relation document, wherein the first interface relation document stores the interface description of the application software and the bottom layer software and the incidence relation of message signals in a database DBC (database management center) file of a CAN (controller area network) message, and the second interface relation document stores the incidence relation of the message of the bottom layer software and an executable Entity Runnable Entity of a software component SWC;
when the application software is integrated with the bottom layer software, a description file, a DBC file, a first interface relation document and a second interface relation document of the bottom layer software are imported into an auxiliary tool;
and responding to the configuration operation of the auxiliary tool by a user, searching the information of the first interface relation document, the second interface relation document and the DBC file through the auxiliary tool, generating new description content of the information by adopting the language format of AUTOSAR, and modifying the description file according to the new description content to realize software integration.
The invention provides a using method of an auxiliary tool, wherein the auxiliary tool comprises an interface and a processing unit;
importing a description file, a DBC file, a first interface relation document and a second interface relation document of the bottom layer software in response to the operation of a user on the interface, and determining the configuration content of the description file of the bottom layer software;
and the processing unit searches the information of the first interface relation document, the second interface relation document and the DBC file according to the configuration content, generates new description content of the information by adopting the language format of AUTOSAR, and modifies the description file according to the new description content to realize software integration.
An embodiment of the present invention provides an electronic device, including:
a processor and a memory;
the processor is used for executing the AUTOSAR-based software integration method or the use method of the auxiliary tool according to any embodiment by calling the program or the instruction stored in the memory.
The embodiment of the invention has the following technical effects:
the invention especially develops an auxiliary tool which has the functions of file importing, searching, generating new description content by adopting the language format of AUTOSAR and modifying the description file, developers only need to maintain the first interface relation document and the second interface relation document, and when software is integrated, the auxiliary tool can automatically execute file importing, searching and generating new description content by adopting the language format of AUTOSAR and modify the description file by configuring the auxiliary tool, thereby completing the creation of parameters such as AUTOSAR interfaces and the associated operation among the interfaces, realizing software integration, reducing the repetitive work in software development and reducing the software development period.
Drawings
In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings used in the description of the embodiments or the prior art will be briefly described below, and it is obvious that the drawings in the following description are some embodiments of the present invention, and other drawings can be obtained by those skilled in the art without creative efforts.
FIG. 1 is a flowchart of a AUTOSAR-based software integration method provided by an embodiment of the present invention;
FIG. 2 is a schematic interface diagram of an auxiliary tool provided by an embodiment of the present invention;
FIG. 3 is a flow chart of a method for using an auxiliary tool according to an embodiment of the present invention;
fig. 4 is a schematic structural diagram of an electronic device according to an embodiment of the present invention.
Detailed Description
In order to make the objects, technical solutions and advantages of the present invention more apparent, the technical solutions of the present invention will be clearly and completely described below. It is to be understood that the described embodiments are merely exemplary of the invention, and not restrictive of the full scope of the invention. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present invention.
The AUTOSAR-based software integration method provided by the embodiment of the invention is mainly suitable for the situation of integrating underlying software and application software.
In the existing software development process, firstly, functional requirements and communication matrixes are confirmed, usually by a system engineer and an OEM (automobile host factory), then, development of bottom-layer software is carried out according to the functional requirements, and usually completed by a bottom-layer embedded software engineer; the development of upper-layer application software is required and is completed by application software engineers. After the bottom layer software and the application software are developed, software integration (including interface connection of each SWC, AUTOSAR code generation, software compilation, and the like) is performed, and a large number of interfaces and association relations are added to a description file of the bottom layer software manually by a bottom layer embedded software engineer, so that the operation is complicated. And finally, testing and releasing the software.
Fig. 1 is a flowchart of a method for integrating software based on AUTOSAR according to an embodiment of the present invention. The integration is carried out on the basis of the developed application software and the bottom layer software, and comprises the following operations:
s110, acquiring the developed application software, the bottom layer software, the first interface relation document and the second interface relation document.
The construction and maintenance of the first interface relationship document and the second interface relationship document can be synchronously performed with the software development process and completed by an algorithm engineer.
The first interface relation document stores interface description of application software and bottom layer software and an incidence relation between message signals in a database DBC file of the CAN message. The interface description of the application software and the bottom layer software comprises an SWC used by the bottom layer software for receiving messages, an SWC used for sending messages, an interface type, an interface element, an element type and an initial value of a Port. Referring to table 1, information located in the same row has an association relationship. Therefore, in the software development process, an engineer responsible for application software development only needs to maintain the table, and can automatically complete the creation of ports and interfaces of bottom layer software and related connection operation through a tool during software integration, thereby reducing the repetitive operation of developers and further reducing the software development period.
TABLE 1 first interface relationship document
The second interface relation document stores the association relation between the Message of the bottom layer software and the Runnable entity of the software component SWC. Referring to table 2, information located in the same row has an association relationship. Therefore, in the software development process, an engineer in charge of the bottom layer software development only needs to maintain the table, and the Port and Runnable associated operation in the SWC of the bottom layer software can be automatically completed (needs to be described in detail) through a tool during software integration, so that the repeated operation of developers is reduced, and the software development period is shortened.
TABLE 2 second interface relationship document
And S120, when the application software is integrated with the bottom layer software, importing the description file, the DBC file, the first interface relation document and the second interface relation document of the bottom layer software into an auxiliary tool.
The description file of the bottom layer software comprises: the arxml file configured by the Interface of the SWC of the bottom layer software comprises an arxml file configured by DataType of the SWC of the bottom layer software, an arxml file of the SWC for realizing message receiving by the bottom layer software and an arxml file of the SWC for realizing message sending by the bottom layer software.
The embodiment of the invention particularly develops an auxiliary tool which can load a description file, a DBC file, a first interface relation document and a second interface relation document. Optionally, the interface of the accessibility tool is opened when the application software is integrated with the underlying software, see fig. 2. The interface displays a file import key, and optionally also displays a DBC network node selection key.
Responding to the triggering operation of a user on a DBC network node selection key, and selecting a target node FtNode; and responding to the triggering operation of the user on the file import key, and selecting the description file, the DBC file, the first interface relation document and the second interface relation document of the bottom layer software to be imported into an auxiliary tool so as to modify the description file of the bottom layer software running on the target node.
S130, responding to the configuration operation of the auxiliary tool by a user, searching the information of the first interface relation document, the second interface relation document and the DBC file through the auxiliary tool, generating new description content of the information by adopting the language format of AUTOSAR, and modifying the description file according to the new description content to realize software integration.
Continuing to refer to fig. 2, configuration contents are displayed on the Interface of the assistant tool, including (1) whether to add and associate a corresponding Interface and Port according to the DBC file; (2) Whether to associate the Port with the Runnable Entity according to the DBC file and the second interface relation document; (3) whether to modify the initial value of the corresponding Port according to the DBC file; (4) Whether to add and associate the corresponding Interface and Port according to the first Interface relation document; (5) Whether the ports are associated with the corresponding Runnable Entity according to the first interface relationship document and the second interface relationship document; (6) Whether to modify the initial value of the corresponding Port according to the first interface relation document; (7) Whether a corresponding Port is generated in the AUTOSAR basic software combination BasicSoftWare composition according to the DBC file; (8) Whether to associate ports in the BasicSoftWare composition with ports in the corresponding SWC according to the DBC file and the first interface relationship document; (9) Whether a Port of the BasicSoftWare composition is associated with a system signal SystemSignal in the corresponding electronic control unit communication Network Ecu Network or not according to the DBC file and the first interface relation document; (10) Whether the association relation between all ports in the BasicSoftWare composition and the ports of the SWC is deleted or not; (11) Whether to delete at least one item of the association relationship between ports of all basic software version composition and SystemSignal in the corresponding Ecu Network.
And after the user imports the file, checking the corresponding configuration content to trigger the auxiliary tool to execute the corresponding integrated operation. And responding to the selection operation of the user on the configuration content on the interface, searching the information of the first interface relation document, the second interface relation document and the DBC file according to the selected configuration content through the auxiliary tool, generating new description content of the information by adopting the language format of AUTOSAR, and modifying the description file according to the new description content. The new description content is generated by adopting the language format of AUTOSAR, and the description file generated by adopting the language format of AUTOSAR can be directly inserted or modified.
The integration operation is explained in detail below for each configuration content.
And selecting (1), responding to a selection operation that whether a user adds corresponding interfaces and ports according to the DBC file or not on an Interface and associates, finding the interfaces and ports which are missing in the description file and exist in the DBC file through the auxiliary tool, generating new description contents of creation and association of the interfaces and ports by adopting an AUTOSAR language format, and inserting the new description contents into the description file. The new description includes information such as names and types of interfaces and ports. Specifically, each Interface name existing in the DBC file is used as an index to find whether the Port exists in the description file, and if not, the Interface and the corresponding Port are added.
And selecting (2), responding to the selection operation of a user on an interface whether to associate the ports with the Runnable Entity according to the DBC file and the second interface relation document, searching the ports which are missing in the description file and exist in the DBC file through the auxiliary tool, finding the Runnable Entity associated with the ports in the second interface relation document, generating new description contents associated with the ports and the Runnable Entity by adopting the language format of AUTOSAR, and inserting the new description contents into the description file. The message signal name has uniqueness, and one message signal corresponds to one Interface and a Port under the Interface.
And selecting (3), in response to the selection operation of whether the initial value of the Port is modified according to the DBC file or not by a user on an interface, searching the Port in the DBC file and the initial value of the Port in the first interface relation document through the auxiliary tool, generating the initial value of the Port by adopting the language format of AUTOSAR, and replacing the initial value in the description file with the initial value.
And selecting (4), responding to the selection operation that whether a corresponding Interface and Port are added and associated according to a first Interface relation document by a user on an Interface, finding the Interface and Port which are missing in a description file and exist in the first Interface relation document through the auxiliary tool, generating new description contents of creation and association of the Interface and Port by adopting an AUTOSAR language format, and inserting the new description contents into the description file. Specifically, each Interface name existing in the first Interface relationship document is used as an index to find whether the Port exists in the description file or not, and if not, the Interface and the corresponding Port are added.
And selecting (5), in response to the selection operation of whether the ports are associated with the corresponding Runnable Entity according to the first interface relation document and the second interface relation document or not by the user on the interface, searching the ports in the first interface relation document and the Runnable Entity associated with the ports in the second interface relation document through the auxiliary tool, generating new description contents associated with the ports and the Runnable Entity by adopting the language format of AUTOSAR, and inserting the new description contents into the description file.
And selecting (6), in response to the selection operation of whether the initial value of the corresponding Port is modified according to the first interface relation document or not by the user on the interface, searching the initial value of the Port in the first interface relation document through the auxiliary tool, generating the initial value of the Port by adopting the language format of AUTOSAR, and replacing the initial value in the description file with the initial value.
And selecting (7), responding to the selection operation of whether the corresponding Port is generated in the AUTOSAR basic software combination BasicSoftWare composition according to the DBC file by a user on the interface, finding the Port which is missing in the description file and exists in the DBC file through the auxiliary tool, and adding the new description content of the Port in the BasicSoftWare composition by adopting the language format of AUTOSAR.
And selecting (8) responding to a selection operation of whether the user associates the ports in the BasICSoftWare composition with the ports in the corresponding SWC according to the DBC file and the first interface relation document, finding the ports existing in the DBC file and the BasICSoftWare composition at the same time through the auxiliary tool, finding the ports in the corresponding SWC in the first interface relation document, generating new description contents for proxying the ports in the SWC to the ports in the BasICSoftWare composition by adopting the language format of AUTOSAR, and inserting the new description contents into the description file. SWC here is SWC that exists in both the BasicSoftWare composition and the first interface relationship document
And selecting (9), in response to a selection operation of whether the user associates the Port of the basic software version compatibility with the message signal SystemSignal in the corresponding electronic control unit communication Network Ecu Network according to the DBC file and the first interface relation document on the interface, finding the Port existing in the DBC file and the basic software version compatibility at the same time through the auxiliary tool, generating new description content associated with the Port and the SystemSignal corresponding to the first interface relation document by adopting the language format of AUTOSAR, and inserting the new description content into the description file. Specifically, the Port name is used to index the first interface relationship document, so as to find the corresponding SystemSignal.
And selecting (10) (11), and responding to the configuration operation of the user on the auxiliary tool (10) and/or (11), and searching and deleting the corresponding sentences in the description file according to the selected configuration content through the auxiliary tool. Namely, the statement of the association relationship between all ports in the basicsoftwave composition and the ports of the SWC is deleted, and the statement of the association relationship between all ports in the basicsoftwave composition and the SystemSignal in the corresponding eco Network is associated.
The embodiment can not modify the description file of the application software, only modifies the description file of the bottom layer software, and generates c/h codes through a BSW tool after modification is completed, so that software integration is completed.
After integration, software testing and release is performed.
The invention particularly develops an auxiliary tool which has the functions of file import, search, generation of new description contents by adopting the language format of AUTOSAR and modification of the description files, developers only need to maintain a first interface relation document and a second interface relation document, and when software is integrated, the auxiliary tool can automatically execute the functions of file import, search, generation of new description contents by adopting the language format of AUTOSAR and modification of the description files by configuring the auxiliary tool, thereby completing the creation of parameters such as AUTOSAR interfaces and the associated operation among the interfaces, realizing software integration, reducing the repetitive work in software development and reducing the software development period.
The embodiment of the invention provides a using method of an auxiliary tool, which is applied to an application scene of integrating bottom-layer software and application software. The auxiliary tool includes an interface and a processing unit.
Referring to fig. 3, the method of use includes the following operations:
s210, importing a description file, a DBC file, a first interface relation document and a second interface relation document of the bottom layer software in response to the operation of a user on the interface, and determining the configuration content of the description file of the bottom layer software;
s220, the processing unit searches the information of the first interface relation document, the second interface relation document and the DBC file according to the configuration content, generates new description content of the information by adopting the language format of AUTOSAR, and modifies the description file according to the new description content to realize software integration.
The auxiliary tool can identify the corresponding interface document, automatically generate the needed SWC interface and the like, and complete the association among all the interfaces; and adding, deleting or modifying the imported AUTOSAR description file (in arxml format) according to configuration \ selection so as to reduce the repetitive work of software developers and realize the convenience of software development.
Fig. 4 is a schematic structural diagram of an electronic device according to an embodiment of the present invention. As shown in fig. 4, the electronic device 400 includes one or more processors 401 and memory 402.
The processor 401 may be a Central Processing Unit (CPU) or other form of processing unit having data processing capabilities and/or instruction execution capabilities and may control other components in the electronic device 400 to perform desired functions.
In one example, the electronic device 400 may further include: an input device 403 and an output device 404, which are interconnected by a bus system and/or other form of connection mechanism (not shown). The input device 403 may include, for example, a keyboard, a mouse, and the like. The output device 404 can output various information to the outside, including warning prompt information, braking force, and the like. The output devices 404 may include, for example, a display, speakers, a printer, and a communication network and its connected remote output devices, among others.
Of course, for simplicity, only some of the components of the electronic device 400 relevant to the present invention are shown in fig. 4, and components such as buses, input/output interfaces, and the like are omitted. In addition, electronic device 400 may include any other suitable components depending on the particular application.
In addition to the above methods and apparatuses, embodiments of the present invention may also be a computer program product comprising computer program instructions that, when executed by a processor, cause the processor to perform the steps of the AUTOSAR-based software integration method or the method of using an accessibility aid provided by any of the embodiments of the present invention.
The computer program product may be written in any combination of one or more programming languages, including an object oriented programming language such as Java, C + + or the like and conventional procedural programming languages, such as the "C" programming language or similar programming languages, for carrying out operations according to embodiments of the present invention. The program code may execute entirely on the user's computing device, partly on the user's device, as a stand-alone software package, partly on the user's computing device and partly on a remote computing device, or entirely on the remote computing device or server.
It is to be understood that the terminology used herein is for the purpose of describing particular embodiments only, and is not intended to limit the scope of the present application. As used in the specification and claims of this application, the terms "a," "an," "the," and/or "the" are not intended to be inclusive in the singular, but rather are intended to be inclusive in the plural, unless the context clearly dictates otherwise. The terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, or apparatus. Without further limitation, an element defined by the phrases "comprising one of 8230; \8230;" 8230; "does not exclude the presence of additional like elements in a process, method, or apparatus that comprises the element.
It is further noted that the terms "center," "upper," "lower," "left," "right," "vertical," "horizontal," "inner," "outer," and the like are used in the orientation or positional relationship indicated in the drawings for convenience in describing the invention and for simplicity in description, and do not indicate or imply that the referenced devices or elements must have a particular orientation, be constructed and operated in a particular orientation, and thus should not be construed as limiting the invention. Unless expressly stated or limited otherwise, the terms "mounted," "connected," "coupled," and the like are to be construed broadly and encompass, for example, both fixed and removable coupling or integral coupling; can be mechanically or electrically connected; they may be connected directly or indirectly through intervening media, or they may be interconnected between two elements. The specific meanings of the above terms in the present invention can be understood in a specific case to those of ordinary skill in the art.
Finally, it should be noted that: the above embodiments are only used to illustrate the technical solution of the present invention, and not to limit the same; while the invention has been described in detail and with reference to the foregoing embodiments, it will be understood by those skilled in the art that: the technical solutions described in the foregoing embodiments may still be modified, or some or all of the technical features may be equivalently replaced; and the modifications or the substitutions do not make the essence of the corresponding technical solutions depart from the technical solutions of the embodiments of the present invention.
Claims (10)
1. A software integration method based on AUTOSAR is characterized by comprising the following steps:
acquiring developed application software, bottom layer software, a first interface relation document and a second interface relation document, wherein the first interface relation document stores interface description of the application software and the bottom layer software and an incidence relation between the interface description and a message signal in a database DBC file of a CAN message, and the second interface relation document stores an incidence relation between a message of the bottom layer software and a Runnable Entity of a software component SWC;
when the application software is integrated with the bottom layer software, the description file, the DBC file, the first interface relation document and the second interface relation document of the bottom layer software are imported into an auxiliary tool;
and responding to the configuration operation of the auxiliary tool by a user, searching the information of the first interface relation document, the second interface relation document and the DBC file through the auxiliary tool, generating new description content of the information by adopting the language format of AUTOSAR, and modifying the description file according to the new description content to realize software integration.
2. The method of claim 1, wherein the description file of the underlying software comprises:
the arxml file configured on the Interface of the SWC of the bottom layer software comprises an arxml file configured on the DataType of the SWC of the bottom layer software, an arxml file of the SWC for realizing message receiving by the bottom layer software and an arxml file of the SWC for realizing message sending by the bottom layer software.
3. The method of claim 1, wherein the interface description of the underlying software comprises:
the bottom layer software is used for receiving the SWC of the message, and is used for sending the initial values of the SWC, the interface type, the interface element, the element type and the Port of the message.
4. The method of claim 1, wherein importing the description file, the DBC file, the first interface relationship document and the second interface relationship document of the underlying software into the auxiliary tool when the application software is integrated with the underlying software comprises:
opening an interface of the auxiliary tool when the application software is integrated with the bottom layer software; a file import key and a DBC network node selection key are displayed on the interface;
responding to the triggering operation of a user on a DBC network node selection key, and selecting a target node;
and responding to the triggering operation of the user on the file import key, and selecting the description file, the DBC file, the first interface relation document and the second interface relation document of the bottom layer software to be imported into an auxiliary tool so as to modify the description file of the bottom layer software running on the target node.
5. The method of claim 1, wherein the interface of the accessibility tool has configuration content displayed thereon; the configuration content comprises whether corresponding interfaces and ports are added and associated according to the DBC file; whether the Port is associated with the Runnable Entity according to the DBC file and the second interface relationship document; whether to modify the initial value of the corresponding Port according to the DBC file; whether to add and associate the corresponding Interface and Port according to the first Interface relation document; whether the ports are associated with the corresponding Runnable Entity according to the first interface relationship document and the second interface relationship document; whether to modify the initial value of the corresponding Port according to the first interface relation document; whether a corresponding Port is generated in the AUTOSAR basic software combination BasicSoftWare composition according to the DBC file; whether to associate a Port in the basicsoftwavereconsideration with a Port in the corresponding SWC according to the DBC file and the first interface relationship document; whether to associate a Port of BasicSoftWare composition with at least one item of system signal in the corresponding electronic control unit communication Network Ecu Network according to the DBC file and the first interface relation document;
the step of responding to the configuration operation of the user on the auxiliary tool, searching the information of the first interface relationship document, the second interface relationship document and the DBC file through the auxiliary tool, generating new description content of the information by adopting the language format of AUTOSAR, and modifying the description file according to the new description content includes:
and responding to the selection operation of the user on the configuration content on the interface, searching the information of the first interface relation document, the second interface relation document and the DBC file according to the selected configuration content through the auxiliary tool, generating new description content of the information by adopting the language format of AUTOSAR, and modifying the description file according to the new description content.
6. The method of claim 5, wherein in response to a selection operation of a user on the interface for configuration content, searching, by the assistant tool, for information of the first interface relationship document, the second interface relationship document and the DBC file according to the selected configuration content, generating a new description content of the information in an AUTOSAR language format, and modifying the description file according to the new description content, comprises:
responding to the selection operation that whether a user adds corresponding interfaces and ports according to the DBC file and associates the interfaces and the ports on the Interface, finding the interfaces and the ports which are missing in the description file and exist in the DBC file through the auxiliary tool, generating new description contents of creation and association of the interfaces and the ports by adopting the language format of AUTOSAR, and inserting the new description contents into the description file;
in response to the selection operation of a user on an interface whether to associate ports with Runnable Entity according to a DBC file and a second interface relation document, finding the ports which are missing in a description file and exist in the DBC file through the auxiliary tool and finding the Runnable Entity associated with the ports in the second interface relation document, generating new description contents associated with the ports and the Runnable Entity by adopting the language format of AUTOSAR, and inserting the new description contents into the description file;
responding to a selection operation that whether a user adds corresponding interfaces and ports according to a first Interface relation document or not and associates the interfaces and the ports on an Interface, finding the interfaces and the ports which are missing in a description file and exist in the first Interface relation document through the auxiliary tool, generating new description contents of creation and association of the interfaces and the ports by adopting an AUTOSAR language format, and inserting the new description contents into the description file;
responding to the selection operation of a user on an interface whether to associate ports with corresponding Runnable Entity according to a first interface relation document and a second interface relation document, finding the ports in the first interface relation document and finding the Runnable Entity associated with the ports in the second interface relation document through the auxiliary tool, generating new description contents associated with the ports and the Runnable Entity by adopting the language format of AUTOSAR, and inserting the new description contents into the description file;
responding to the selection operation of a user on an interface whether to generate a corresponding Port in the AUTOSAR basic software combination BasicSoftWare composition according to the DBC file, finding the Port which is absent in the description file and exists in the DBC file through the auxiliary tool, and adding new description content of the Port in the BasicSoftWare composition by adopting the language format of AUTOSAR;
in response to a selection operation of whether a user associates ports in the BasICSoftWare composition with ports in a corresponding SWC according to a DBC file and a first interface relation document or not, finding the ports existing in the DBC file and the BasICSoftWare composition at the same time and finding the ports in the corresponding SWC in the first interface relation document through the auxiliary tool, generating new description contents for proxying the ports in the SWC to the ports in the BasICSoftWare composition by adopting the language format of AUTOSAR, and inserting the new description contents into the description files;
responding to a selection operation of whether a user associates a Port of BasicSoftWare composition with a message signal SystemSignal in a corresponding electronic control unit communication Network Ecu Network according to a DBC file and a first interface relation document on an interface, finding the Port existing in the DBC file and the BasicSoftWare composition at the same time through the auxiliary tool, generating new description contents of the Port and the SystemSignal association corresponding to the first interface relation document by adopting an AUTOSAR language format, and inserting the new description contents into the description files.
7. The method of claim 5, wherein in response to a selection operation of a user on the interface for configuration content, searching, by the assistant tool, for information of the first interface relationship document, the second interface relationship document and the DBC file according to the selected configuration content, generating a new description content of the information in an AUTOSAR language format, and modifying the description file according to the new description content, comprises:
responding to the selection operation of a user on an interface whether the initial value of the Port is modified according to the DBC file, searching the Port in the DBC file and the initial value of the Port in the first interface relation document through the auxiliary tool, generating the initial value of the Port by adopting the language format of AUTOSAR, and replacing the initial value in the description file with the initial value;
and in response to the selection operation of whether the initial value of the corresponding Port is modified according to the first interface relation document or not by a user on an interface, searching the initial value of the Port in the first interface relation document through the auxiliary tool, generating the initial value of the Port by adopting an AUTOSAR language format, and replacing the initial value in the description file with the initial value.
8. The method of claim 5, wherein the configuration content includes whether all ports in BasicSoftWare composition are associated with ports of SWC and/or whether all ports in BasicSoftWare composition are associated with SystemSignal in the corresponding Ecu Network;
the method further comprises the following steps: and responding to the configuration operation of the user on the auxiliary tool, and searching and deleting the corresponding statement in the description file according to the selected configuration content through the auxiliary tool.
9. The use method of the auxiliary tool is characterized in that the auxiliary tool comprises an interface and a processing unit;
importing a description file, a DBC file, a first interface relation document and a second interface relation document of the bottom layer software in response to the operation of a user on the interface, and determining the configuration content of the description file of the bottom layer software;
and the processing unit searches the information of the first interface relation document, the second interface relation document and the DBC file according to the configuration content, generates new description content of the information by adopting the language format of AUTOSAR, and modifies the description file according to the new description content to realize software integration.
10. An electronic device, characterized in that the electronic device comprises:
a processor and a memory;
the processor is used for executing the AUTOSAR-based software integration method according to any one of claims 1 to 8 or the method for using the accessory tool according to claim 9 by calling a program or an instruction stored in the memory.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202210849889.5A CN115167831A (en) | 2022-07-20 | 2022-07-20 | Software integration method and device based on AUTOSAR and use method |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202210849889.5A CN115167831A (en) | 2022-07-20 | 2022-07-20 | Software integration method and device based on AUTOSAR and use method |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN115167831A true CN115167831A (en) | 2022-10-11 |
Family
ID=83495017
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202210849889.5A Pending CN115167831A (en) | 2022-07-20 | 2022-07-20 | Software integration method and device based on AUTOSAR and use method |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN115167831A (en) |
Cited By (5)
| 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 |
| CN116594960A (en) * | 2023-06-08 | 2023-08-15 | 镁佳(北京)科技有限公司 | Descriptive file format conversion method, descriptive file format conversion device, computer equipment and storage medium |
| CN117112019A (en) * | 2023-09-05 | 2023-11-24 | 镁佳(北京)科技有限公司 | Carrier file automatic generation method, device, computer equipment and medium |
| CN117725679A (en) * | 2023-12-21 | 2024-03-19 | 上海烜翊科技有限公司 | AUTOSAR modeling method based on activity scene |
| CN117725679B (en) * | 2023-12-21 | 2024-05-31 | 上海烜翊科技有限公司 | AUTOSAR modeling method based on activity scene |
Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN109002290A (en) * | 2018-10-15 | 2018-12-14 | 昆明理工鼎擎科技股份有限公司 | Integrated ECU embedded target code generator and automatic generation method |
| CN109117121A (en) * | 2018-05-08 | 2019-01-01 | 宁波央腾汽车电子有限公司 | A kind of AUTOSAR software architecture implementation method |
| CN113688026A (en) * | 2021-09-30 | 2021-11-23 | 中汽创智科技有限公司 | Data analog simulation method, device, equipment and storage medium |
| CN114047970A (en) * | 2021-10-14 | 2022-02-15 | 苏州正力芯控电子有限公司 | Configuration method and system of AUTOSAR (automotive open system architecture) architecture software |
| CN114489675A (en) * | 2022-02-07 | 2022-05-13 | 苏州挚途科技有限公司 | Processing method and device of automatic driving system and electronic equipment |
| CN114691132A (en) * | 2022-03-16 | 2022-07-01 | 中汽创智科技有限公司 | ARXML file generation method, device, equipment and storage medium |
-
2022
- 2022-07-20 CN CN202210849889.5A patent/CN115167831A/en active Pending
Patent Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN109117121A (en) * | 2018-05-08 | 2019-01-01 | 宁波央腾汽车电子有限公司 | A kind of AUTOSAR software architecture implementation method |
| CN109002290A (en) * | 2018-10-15 | 2018-12-14 | 昆明理工鼎擎科技股份有限公司 | Integrated ECU embedded target code generator and automatic generation method |
| CN113688026A (en) * | 2021-09-30 | 2021-11-23 | 中汽创智科技有限公司 | Data analog simulation method, device, equipment and storage medium |
| CN114047970A (en) * | 2021-10-14 | 2022-02-15 | 苏州正力芯控电子有限公司 | Configuration method and system of AUTOSAR (automotive open system architecture) architecture software |
| CN114489675A (en) * | 2022-02-07 | 2022-05-13 | 苏州挚途科技有限公司 | Processing method and device of automatic driving system and electronic equipment |
| CN114691132A (en) * | 2022-03-16 | 2022-07-01 | 中汽创智科技有限公司 | ARXML file generation method, device, equipment and storage medium |
Non-Patent Citations (1)
| Title |
|---|
| 郑宜福: ""基于AUTOSAR的纯电动汽车整车控制系统软件开发与功能映射研究"", 《中国优秀硕士学位论文全文数据库工程科技Ⅱ辑》 * |
Cited By (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN116594960A (en) * | 2023-06-08 | 2023-08-15 | 镁佳(北京)科技有限公司 | Descriptive file format conversion method, descriptive file format conversion device, computer equipment and storage medium |
| CN116594960B (en) * | 2023-06-08 | 2024-01-30 | 镁佳(北京)科技有限公司 | Descriptive file format conversion method, descriptive file format conversion device, computer equipment and storage medium |
| 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 |
| CN117112019A (en) * | 2023-09-05 | 2023-11-24 | 镁佳(北京)科技有限公司 | Carrier file automatic generation method, device, computer equipment and medium |
| CN117725679A (en) * | 2023-12-21 | 2024-03-19 | 上海烜翊科技有限公司 | AUTOSAR modeling method based on activity scene |
| CN117725679B (en) * | 2023-12-21 | 2024-05-31 | 上海烜翊科技有限公司 | AUTOSAR modeling method based on activity scene |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN115167831A (en) | Software integration method and device based on AUTOSAR and use method | |
| CN103853535B (en) | The method and apparatus for changing middleware | |
| CN112861501A (en) | Report generation method and device, electronic equipment and computer readable storage medium | |
| CN113127347A (en) | Interface testing method, device, equipment and readable storage medium | |
| CN111818175A (en) | Enterprise service bus configuration file generation method, device, equipment and storage medium | |
| CN113535587B (en) | Target application detection method and device and computer equipment | |
| JPWO2014184896A1 (en) | Program analysis apparatus, program analysis method, and program analysis program | |
| CN114895935A (en) | Method and device for flashing vehicle ECU, electronic equipment and storage medium | |
| CN114461223A (en) | Code generation method and device and terminal equipment | |
| CN114091383A (en) | Test sequence generation method, device and system and related equipment | |
| CN111474923B (en) | Vehicle diagnosis method, device and equipment | |
| CN111078213A (en) | Code generation method and code generation device | |
| CN115525534A (en) | Test case generation method and platform based on swagger interface test | |
| CN115755867A (en) | Vehicle diagnosis method and related device | |
| CN116360887A (en) | Program parameter loading method, device, equipment and storage medium | |
| US11392353B2 (en) | Method for generating source code using service-based communication | |
| CN111722881B (en) | Resource expansion method, system and device of container cloud platform | |
| CN109388400B (en) | Automatic page generation method and device | |
| US7805715B2 (en) | Model publishing framework | |
| CN111026466A (en) | File processing method and device, computer readable storage medium and electronic equipment | |
| CN116521143B (en) | DID read-write service processing method and device for fault diagnosis | |
| JP2014532223A (en) | Method and apparatus for enabling a first computer program to execute application logic of a second computer program, for interfacing the first computer program and the second computer program And apparatus for generating computer program code for the same, a computer program, and a software interface for enabling a first computer program to execute application logic of a second computer program For providing information (computer program interface) | |
| CN117950635A (en) | Application development method and device of platform, electronic equipment and storage medium | |
| CN111782183B (en) | Method and device for judging component dependency, electronic device and medium | |
| CN117061545A (en) | Vehicle-mounted network development system and 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 | ||
| RJ01 | Rejection of invention patent application after publication |
Application publication date: 20221011 |
|
| RJ01 | Rejection of invention patent application after publication |