Virtual environment-based vehicle ECU verification system and method

Abstract

A method performed by a virtual environment-based vehicle ECU verification system comprises the steps of: receiving a control command from a user interface; reading, from a cooperative simulation middleware unit, at least one FMU model corresponding to the control command; performing a simulation on the basis of the read FMU model; transmitting a simulation operation signal, generated by performing the simulation, to an ECU interface via a virtual ECU wrapper (vECU wrapper) on the cooperative simulation middleware unit; and transmitting, via the ECU interface, the simulation operation signal to a virtual ECU corresponding to the simulation, so as to perform testing on the virtual ECU.

Description

Virtual environment-based vehicle ECU verification system and method

[0001] The present invention relates to a virtual environment-based vehicle ECU verification system and method.

[0002] Modern automotive software development environments are becoming increasingly complex to accommodate continuous innovation and diverse technological demands. This growth in the scale and size of vehicle software is also driving up the time and costs required for software and hardware development and validation.

[0003] Figure 1 is a diagram illustrating a V-cycle based methodology in the prior art.

[0004] The traditional approach of the past was the V-cycle development method, in which software (SW) and hardware (HW) were developed sequentially and verified during the integration stage. The V-cycle development method is expressed in a V-shaped manner with the development and testing stages consisting of the user requirement specification writing stage (S11), system requirement specification writing stage (S12), system design stage (S13), unit design stage (S14), code writing stage (S15), unit test stage (S16), integration test stage (S17), system test stage (S18), and acceptance test stage (S19). The V-cycle development method focuses on strengthening verification at each stage and finding and fixing defects early.

[0005] However, this conventional method has the problem that if a problem occurs at the software and hardware integration stage, it is difficult to identify the root cause of the problem, and individual verification between software and hardware is required, which results in more cost and time.

[0006] The problem to be solved by the present invention is to provide a vehicle ECU verification system and method based on a virtual environment, which enables integrated verification with virtual hardware from the software development stage, rather than at the integrated verification stage of software and hardware.

[0007] However, the problems to be solved by the present invention are not limited to the problems described above, and other problems may exist.

[0008] A method performed by a virtual environment-based vehicle ECU verification system according to a first aspect of the present invention for solving the above-described problem includes the steps of: receiving a control command from a user interface; reading out at least one FMU model corresponding to the control command from a cooperative simulation middleware unit; performing a simulation based on the read FMU model; transmitting a simulation operation signal according to the simulation performance to an ECU interface through a virtual ECU wrapper (vECU Wrapper) on the cooperative simulation middleware unit; and performing a test on the virtual ECU by transmitting the simulation operation signal to a virtual ECU corresponding to the simulation through the ECU interface.

[0009] In some embodiments of the present invention, the step of performing a simulation based on the extracted FMU model may include the step of generating a control signal for a predetermined function in a first FMU corresponding to an ECU performing a predetermined function of a vehicle of the cooperative simulation middleware unit; the step of distributing the control signal to a peripheral FMU via a second FMU in charge of a communication function; the step of determining the validity of the control signal in the peripheral FMU; and the step of applying the control signal in the peripheral FMU determined to be valid as a result of the determination.

[0010] In some embodiments of the present invention, the step of transmitting a simulation operation signal according to the simulation performance to an ECU interface through a virtual ECU wrapper (vECU Wrapper) on the cooperative simulation middleware unit may enable the virtual ECU wrapper to transmit the control signal to the ECU interface so that the control signal is transmitted to a valid virtual ECU.

[0011] Some embodiments of the present invention may further include the steps of: receiving development environment setting information from the user interface and storing it in a database; receiving an external commercial tool connection command through the user interface; transmitting the development environment setting information to a third-party tool interface in response to the connection command; and transmitting the development environment setting information to the external commercial tool through the third-party tool interface to establish a connection with the external commercial tool.

[0012] In some embodiments of the present invention, the step of performing a simulation based on the extracted FMU model may further include a step of performing a simulation by linking the FMU model extracted from the cooperative simulation middleware unit and the simulation model built in the external commercial tool, and receiving the test progress results through the virtual ECU reference as the test for the virtual ECU progresses.

[0013] Some embodiments of the present invention may further include a step in which the third-party tool interface receives a simulation operation signal from the external commercial tool; a step in which a third-party wrapper of the cooperative simulation middleware unit transmits the simulation operation signal received through the third-party tool interface to a master simulation unit through an FMI; a step in which the master simulation unit converts the simulation operation signal into a form capable of communicating with a virtual ECU and transmits the converted simulation operation signal to a virtual ECU wrapper; and a step in which the virtual ECU wrapper transmits the converted simulation operation signal to a corresponding virtual ECU through the ECU interface to perform a test on the virtual ECU.

[0014] Some embodiments of the present invention may further include a step of bypassing a simulation operation signal through a simulation model built in the external commercial tool to the ECU interface through the virtual ECU reference of the cooperative simulation middleware unit; a step of receiving a test progress result through the virtual ECU reference of the cooperative simulation middleware unit as a test for the virtual ECU progresses; a step of bypassing the test progress result to the third-party tool interface through the third-party reference of the cooperative simulation middleware unit; and a step of transmitting the test progress result to the external commercial tool through the third-party tool interface.

[0015] Some embodiments of the present invention may include a step of receiving a simulation operation signal through a simulation model built in the external commercial tool through the third-party tool interface; a step of transmitting the simulation operation signal from the third-party tool interface to the ECU interface; and a further step of transmitting the simulation operation signal to a virtual ECU corresponding to the simulation through the ECU interface to perform a test on the virtual ECU.

[0016] In addition, a virtual environment-based vehicle ECU verification system according to a second aspect of the present invention may include a control command receiving unit that receives a control command from a user interface, a cooperative simulation middleware unit that reads out at least one FMU model corresponding to the control command, performs a simulation based on the read FMU model, and then transmits a simulation operation signal according to the simulation performance through a virtual ECU wrapper (vECU Wrapper), and an ECU interface unit that, upon receiving the simulation operation signal, transmits the simulation operation signal to a virtual ECU corresponding to the simulation to perform a test on the virtual ECU.

[0017] In addition, a computer program according to another aspect of the present invention is coupled with a computer as hardware to execute the virtual environment-based vehicle ECU verification system and method, and is stored in a computer-readable recording medium.

[0018] Other specific details of the present invention are included in the detailed description and drawings.

[0019] According to the present invention described above, the new development method enables more efficient integrated verification of software and hardware. This significantly reduces the time and cost of the entire development project, significantly improving productivity compared to existing methods.

[0020] Furthermore, by providing an environment where developers can develop and test software alongside virtual hardware, integrated verification of software and hardware can be performed in stages. This allows for the rapid detection and correction of errors that occur early in development, leading to improved quality.

[0021] Additionally, it can enhance collaboration between software developers and hardware engineers by providing an environment where virtual hardware and software can be handled together, thereby promoting mutual communication and understanding, and enabling efficient team collaboration.

[0022] Additionally, software and hardware developed through an efficient verification process can provide superior quality and stability, improving the quality of the final product and enhancing customer satisfaction.

[0023] Additionally, shortening development and validation times and improving quality can help new products enter the market more quickly and gain a competitive edge.

[0024] The effects of the present invention are not limited to the effects mentioned above, and other effects not mentioned will be clearly understood by those skilled in the art from the description below.

[0025] Figure 1 is a diagram illustrating a V-cycle based methodology in the prior art.

[0026] FIG. 2 is a drawing for explaining the entire system according to one embodiment of the present invention.

[0027] Figure 3 is a drawing for explaining the configuration of a development unit, a simulation unit, a network monitor, and a test unit in one embodiment of the present invention.

[0028] FIG. 4 is a drawing for explaining a vehicle ECU verification system according to one embodiment of the present invention.

[0029] FIG. 5 is a flowchart of a virtual environment-based vehicle ECU verification method according to one embodiment of the present invention.

[0030] Figure 6 is a drawing for explaining the content of verifying a virtual ECU based on the cooperative simulation middleware part.

[0031] Figure 7 is a drawing for explaining the contents of performing a simulation based on an external commercial tool.

[0032] Figure 8 is a drawing for explaining the content of performing a simulation based on an external commercial tool without utilizing the cooperative simulation middleware part.

[0033] The advantages and features of the present invention, and the methods for achieving them, will become clearer with reference to the embodiments described in detail below together with the accompanying drawings. However, the present invention is not limited to the embodiments disclosed below and may be implemented in various different forms. These embodiments are provided solely to ensure that the disclosure of the present invention is complete and to fully inform those skilled in the art of the scope of the present invention, and the present invention is defined solely by the scope of the claims.

[0034] The terminology used herein is for the purpose of describing embodiments only and is not intended to limit the present invention. In this specification, the singular also includes the plural unless specifically stated otherwise. As used herein, the terms "comprises" and / or "comprising" do not exclude the presence or addition of one or more other components in addition to the mentioned components. Like reference numerals refer to like components throughout the specification, and "and / or" includes each and any combination of one or more of the mentioned components. Although "first", "second", etc. are used to describe various components, these components are not limited by these terms. These terms are only used to distinguish one component from another. Therefore, it should be understood that a first component mentioned below may also be a second component within the technical spirit of the present invention.

[0035] Unless otherwise defined, all terms (including technical and scientific terms) used herein may be used in their common sense to those skilled in the art to which the present invention pertains. Furthermore, terms defined in commonly used dictionaries are not to be interpreted ideally or excessively unless explicitly and specifically defined otherwise.

[0036] Fig. 2 is a drawing for explaining the entire system according to one embodiment of the present invention. Fig. 3 is a drawing for explaining the configuration of the development unit (200), simulation unit (300), network monitor, and test unit (400) according to one embodiment of the present invention.

[0037] In one embodiment of the present invention, the entire system includes a development unit (200), a simulation unit (300), a network monitor and test unit (400), an automatic verification unit (100), and a cloud unit (500).

[0038] The development unit (200) provides a configuration tool for effectively configuring and developing software through parameter settings. The configuration tool includes an ASW configuration unit (201) and a BSW configuration unit (202). Additionally, it generates an ECU image (Image, 203) from AUTOSAR-based source code for software development and code generation.

[0039] The simulation unit (300) configures SILS (Software-in-the-Loop Simulation) in the software simulation unit (301) to run and test software applications without actual hardware, thereby verifying the functions, stability, and performance of the software and simulating the interaction between software and hardware.

[0040] In addition, the simulation unit (300) may configure HILS (Hardware-in-the-Loop Simulation) in the hardware simulation unit (302) to test and evaluate the hardware performance of an actual ECU. In addition, the hardware simulation unit (302) may include vHILS (Virtual Hardware-in-the-Loop Simulation) to test and evaluate hardware performance by configuring a virtual ECU (12) identical to an actual ECU without an actual ECU.

[0041] The network monitor and test unit (400) supports various network protocols (vCAN, vLIN, cEthernet) and communication tests, and is used to monitor and test the vehicle's internal communication network. This network monitor and test unit (400) can monitor and observe data exchange and communication between vehicle ECUs to evaluate the stability and efficiency of the network.

[0042] The cloud unit (500) supports OTA (Over-The-Air) updates via the cloud for continuous upgrades and improvements of software.

[0043] The automatic verification unit (100) is intended to ensure the accuracy and stability of software and to identify and correct problems in the early stages of development, and corresponds to a virtual environment-based vehicle ECU verification system according to one embodiment of the present invention.

[0044] One embodiment of the present invention integrates these respective parts to comprehensively support development, simulation, network monitoring, cloud functions, and automatic verification of vehicle software.

[0045] Hereinafter, with reference to FIGS. 4 to 8, an automatic verification unit (100) according to one embodiment of the present invention, i.e., a virtual environment-based vehicle ECU verification system (100), and a method performed through the same will be described in more detail.

[0046] FIG. 4 is a drawing for explaining a vehicle ECU verification system (100) according to one embodiment of the present invention.

[0047] A vehicle ECU verification system (100) according to one embodiment of the present invention includes a control command receiving unit (110), a cooperative simulation middleware unit (COSIM Middleware, 120), and an ECU interface unit (130).

[0048] The control command receiving unit (110) receives a control command from the user interface (11). This control command receiving unit (110) is configured to interpret the input of a developer or user and perform a corresponding operation. It receives signals or file messages transmitted by the user and performs the role of understanding and interpreting the operation desired by the user. In particular, when performing a simulation using the internal cooperative simulation middleware unit (120), the user's command is interpreted and transmitted to the cooperative simulation middleware unit (120) to instruct it to execute a corresponding operation.

[0049] Additionally, the control command receiving unit (110) collects simulation results and provides them as feedback to the user. The information provided to the user may include simulation results, log information, and other information regarding the executed operations.

[0050] The cooperative simulation middleware unit (120) reads out at least one FMU model corresponding to a control command, performs a simulation based on the read out FMU model, and then transmits a simulation operation signal according to the simulation performance through a virtual ECU wrapper (vECU Wrapper).

[0051] Specifically, the cooperative simulation middleware unit (120) may include a master simulation unit (121), a wrapper (122), an FMU (123), and an FMI (124).

[0052] First, the FMU (Functional Mock-up Unit, 123) represents a model that performs a specific operation. For example, a model that simulates a specific system or function, such as a seat heating model, can be expressed as the FMU (123). Through this FMU (123), one embodiment of the present invention enables the operation of the corresponding model to be executed in a simulation environment.

[0053] The FMI (Functional Mock-up Interface, 124) serves to exchange simulation results with the master simulation unit (121), and serves as an interface between the master simulation unit (121) and the FMU (123), and as an interface between the master simulation unit (121) and each reference unit (122). Through this FMI (124), various FMUs (123) can cooperate to perform simulations.

[0054] The master simulation unit (121) is a core component that provides key functions that play a crucial role in the collaborative simulation middleware unit (120). It manages the overall simulation progress and coordinates between each component. Furthermore, the master simulation unit (121) can perform actions such as starting or stopping a simulation, pausing, etc., as needed, and can effectively coordinate the overall simulation by communicating with various FMUs (123) via the FMI (124).

[0055] The wrapper (122) converts data external to the vehicle ECU verification system (or automatic verification unit, 100) into an FMI interface for exchange. That is, the wrapper (122) converts data collected externally to be compatible with the FMI interface and enables it to be exchanged with simulation components within the cooperative simulation middleware unit (120).

[0056] The ECU interface unit (130) transmits the simulation operation signal to the virtual ECU (12) corresponding to the simulation upon receiving the simulation operation signal. The virtual ECU (12) is tested based on the transmitted simulation operation signal, and the test results for the virtual ECU (12) are collected and provided to the user interface (11).

[0057] In addition, in one embodiment of the present invention, the external commercial tool (13) may be primarily commercial software, such as MATLAB's Simulink or CANoe, which can perform various simulation and verification tasks.

[0058] Additionally, the network monitoring tool (14) monitors data received from an external commercial tool (13) and a predetermined operation signal generated from an FMU included in the collaborative simulation middleware unit (120), and provides a function that allows developers to transmit and test desired data. This allows users to easily control and check the vehicle's status.

[0059] For example, the network monitoring tool (14) can monitor in real time the vehicle speed data received from the external commercial tool (13) and the DoorOpen operation signal generated within the cooperative simulation middleware unit (120), and the developer can check the vehicle status and operation in real time through this data. In addition, the developer can directly modify data such as the vehicle speed and DoorOpen status through the network monitoring tool (14).

[0060] For example, if the current vehicle speed is 60 km / h, the developer can change this value to 70 km / h using the tool. Furthermore, the DoorOpen status can be set to a desired state by the developer.

[0061] In addition, the network monitoring tool (14) can provide simpler data signal transmission and manipulation than simulations performed in external commercial tools (13).

[0062] The database (DB, 140) is a repository that effectively manages test cases to be executed with simulation models loaded by users. The database (140) stores a list of simulation models loaded by users. For example, the database (140) may include metadata such as the identifier, version, and description of each model. In addition, the database (140) may store sti files containing test cases to be executed.

[0063] Here, the sti file is a file format structured according to the ASAM-XiL standard, and is an essential element for loading and managing test cases in a simulation environment. Furthermore, ASAM-XiL is a standard defined by ASAM (Association for Standardization of Automation and Measuring Systems), an international standards organization that provides standards for automated testing and simulation environments, and provides a design for standardizing interfaces for data exchange in simulation and test environments.

[0064] In this way, one embodiment of the present invention performs a simulation using a cooperative simulation middleware unit (120) and an external commercial tool (13). This is because the cooperative simulation middleware unit (120) and the external commercial tool (MATLAB / Simulink, Vector / CANoe, 13) have excellent compatibility, making them easy to link, and have good compatibility between each platform.

[0065] In addition, external commercial tools (13), such as MATLAB / Simulink and Vector / CANoe, each provide specialized functions, so efficient verification and simulation can be performed by utilizing the functions of external commercial tools (13).

[0066] As a result, developers can avoid complex and time-consuming new modeling tasks and achieve quick results by leveraging already proven models.

[0067] Meanwhile, examples of simulation models using external commercial tools (13) include vehicle driving speed signal generation and signals output from external sensors that vary by vehicle manufacturer.

[0068] Figure 5 is a flowchart of a virtual environment-based vehicle ECU verification method according to one embodiment of the present invention. While each step illustrated in Figure 5 may be understood to be performed by the aforementioned vehicle ECU verification system (100), the present invention is not necessarily limited thereto.

[0069] A vehicle ECU verification method according to one embodiment of the present invention is performed including a step (S110) of receiving a control command from a user interface (11), a step (S120) of reading out at least one FMU model corresponding to the control command from a cooperative simulation middleware unit (120), a step (S130) of performing a simulation based on the read out FMU model, a step (S140) of transmitting a simulation operation signal according to the simulation performance to an ECU interface through a virtual ECU wrapper (vECU Wrapper) on the cooperative simulation middleware unit (120), and a step (S150) of transmitting the simulation operation signal to a virtual ECU (12) corresponding to the simulation through the ECU interface to perform a test on the virtual ECU (12).

[0070] Before performing each of the above steps, development environment setting information may be received from the developer and stored in a database (140). This is to track and preserve data regarding the environment set by the developer.

[0071] Thereafter, control commands are received from the user interface (11). These control commands are transmitted through a channel for transmission and reception with the cooperative simulation middleware unit (120) responsible for simulation control and data exchange.

[0072] Next, the collaborative simulation middleware unit (120) retrieves at least one FMU model corresponding to the control command. Accordingly, the master simulation unit (121) can perform the entire simulation after connecting the FMUs to each other. This means simulating how each model operates and enabling them to interact with each other.

[0073] Next, the virtual ECU reference (122-1) of the cooperative simulation middleware unit (120) transmits other simulation operation signals to the ECU interface unit (130) for simulation execution.

[0074] Here, the virtual ECU reference (122-1) provides an interface between the virtual ECU (12) and the cooperative simulation middleware (120), and can communicate with the cooperative simulation middleware (120) using FMI and exchange data with the virtual ECU (12) through a communication protocol such as vCAN. Accordingly, data generated in the virtual ECU (12) can be converted so that it can be used in the cooperative simulation middleware (120), and conversely, simulation operation signals in the cooperative simulation middleware (120) can be transmitted to the virtual ECU (12).

[0075] In addition, the collaborative simulation middleware unit (120) may include a third-party referrer (122-2). The third-party referrer (122-2) provides an interface between an external commercial tool (13) and the collaborative simulation middleware unit (120). It can communicate with the external commercial tool (13) via the TCP / IP protocol and exchange data with the collaborative simulation middleware unit (120) via the FMI. Consequently, the third-party referrer (122-2) converts data transmitted from the external commercial tool (13) so that it can be used by the collaborative simulation middleware unit (120).

[0076] Next, the ECU interface unit (130) transmits a simulation operation signal to a virtual ECU (12) corresponding to the simulation to perform a test on the virtual ECU (12). The simulation operation signal may include communication data such as CAN, LIN, etc.

[0077] Figure 6 is a drawing for explaining the contents of verifying a virtual ECU (12) based on the cooperative simulation middleware part (120).

[0078] In one embodiment of the present invention, when a specific simulation model is not provided by an external commercial tool (CANoe, Simulink, 13), an internal simulation can be performed through a cooperative simulation middleware unit (120).

[0079] To this end, the cooperative simulation middleware unit (120) generates a control signal for a given function in the first FMU corresponding to the ECU performing a given function of the vehicle. Then, the control signal is distributed to surrounding FMUs via the second FMU responsible for the communication function.

[0080] Afterwards, the surrounding FMUs can determine the validity of the received control signal, and the surrounding FMUs that determine it to be valid can apply the control signal.

[0081] Referring to the example of Fig. 6, it is assumed that the virtual ECU (12) is a cluster that indicates the vehicle's speed, RPM, and whether the vehicle door is open. In addition, it is assumed that the FMU_1 in charge of the corresponding operation in the cooperative simulation middleware unit (120) when the DoorOpen signal is generated is the DoorOpen sensor ECU.

[0082] Afterwards, when a DoorOpen signal occurs, FMU_1 (123-1) sends a message to the communication FMU, FMU_3 (123-3), for communication, and the communication FMU (123-3) distributes data to surrounding FMUs.

[0083] Each FMU that receives the DoorOpen signal verifies whether the signal is valid for itself using data such as its ID. This allows each FMU to utilize the DoorOpen signal to perform actions as needed.

[0084] In addition, one embodiment of the present invention can transmit a control signal to an ECU interface unit (130) through a virtual ECU reference (122-1) for transmission to a virtual ECU (12) in which the control signal is valid.

[0085] In the above example, the virtual ECU (12) for which the DoorOpen signal is valid can receive the DoorOpen signal through the vECU_Wrapper (122-1) which is FMU_4, and through this, the LED is turned on to indicate DoorOpen in the cluster.

[0086] Next, we will explain how to perform a simulation using an external commercial tool (13).

[0087] First, in order to link with an external commercial tool (13) in one embodiment of the present invention, the control command receiving unit (110) receives development environment setting information from the user interface (11) and stores it in a database (140).

[0088] Next, when the control command receiving unit (110) receives an external commercial tool (13) connection command through the user interface (11), it transmits development environment setting information to the third-party tool interface (150) in response to the connection command.

[0089] Thereafter, the development environment setting information is transmitted to an external commercial tool (13) through a third-party tool interface (150), and thus a connection can be established with the external commercial tool (13).

[0090] Next, a simulation is performed through an external commercial tool (13), and in order to transmit the simulation result data generated from the external commercial tool (13) to the cooperative simulation middleware (120), the data is transmitted to the cooperative simulation middleware (120) that supports the FMI interface through a third-party referrer (122-2) via TCP / IP communication.

[0091] Through this, an effective data flow is established between the external commercial tool (13) and the collaborative simulation middleware unit (120), and the simulation results can be further verified and analyzed in the automatic verification unit (100).

[0092] Figure 7 is a drawing for explaining the contents of performing a simulation based on an external commercial tool (13).

[0093] Meanwhile, Fig. 7 is a case in which the function of the cooperative simulation middleware unit (120) is used together in the process of receiving a simulation operation result signal from an external commercial tool (13).

[0094] Specifically, upon receiving a control command from the user interface (11), the control command is transmitted to the master simulation unit (121) of the cooperative simulation middleware unit (120). The master simulation unit (121) interprets the control command, extracts the necessary FMU model, and loads simulation data for the same.

[0095] Next, upon receiving a simulation execution command through the user interface (11), the master simulation unit (121) can perform a simulation in conjunction with a simulation model built in an external commercial tool (13) and generate a simulation operation signal to be transmitted to the virtual ECU (12).

[0096] Next, a simulation operation signal is transmitted to a virtual ECU (12) corresponding to the simulation through the virtual ECU reference (122-1) and ECU interface (130) of the cooperative simulation middleware (120) to conduct a test on the virtual ECU (12).

[0097] Next, as testing progresses on the virtual ECU (12), the test progress results can be received by the cooperative simulation middleware unit (120) through the virtual ECU reference (122-1).

[0098] In addition, the master simulation unit (121) of the cooperative simulation middleware unit (120) can perform a linked operation by transmitting a simulation operation signal to a virtual ECU (12) or an external commercial tool (13) upon receiving the test progress results or separately therefrom, and can stop the simulation and collect the results as a log when the test case is completed. In addition, the collected results and logs are provided to the user interface (11) for visualization and analysis.

[0099] Referring to the example of FIG. 7, one embodiment of the present invention can use a pre-implemented simulation model from an external commercial tool (13) for a specific simulation model not provided within the cooperative simulation unit middleware (120). For example, a vehicle acceleration model can be imported from an external commercial tool (13) and used.

[0100] Specifically, the speed data resulting from the vehicle acceleration model implemented in the external commercial tool (13) is transmitted from the external commercial tool (13) to the cooperative simulation middleware unit (120), and the FMU_1 third-party reference (122-2) of the cooperative simulation middleware unit (120) converts the speed data received from the external commercial tool (13) into an FMI interface and transmits it to the master simulation unit (121). Then, the FMU_2 vECU reference (122-1) converts the data so that it can communicate with an external virtual ECU (12) by utilizing the FMI interface, and the converted data is transmitted to the virtual ECU (12).

[0101] The virtual ECU (12) that receives the operation result data displays a speed gauge on the cluster, thereby allowing the simulation results for the vehicle's speed to be visually confirmed.

[0102] Figure 8 is a drawing for explaining the content of performing a simulation based on an external commercial tool (13) without utilizing the cooperative simulation middleware part (120).

[0103] Unlike the embodiment of FIG. 7, one embodiment of the present invention can perform simulation based on an external commercial tool (13) without utilizing a cooperative simulation middleware unit (120).

[0104] In one embodiment, the present invention can bypass a simulation operation signal through a simulation model built in an external commercial tool (13) to an ECU interface unit (130) through a virtual ECU reference (122-1) of a cooperative simulation middleware unit (120).

[0105] Next, as the test progresses for the virtual ECU (12), if the test progress result is received by the cooperative simulation middleware unit (120) through the virtual ECU reference (122-1), it can be bypassed to the third-party tool interface (150) through the third-party reference (122-2) of the cooperative simulation middleware unit (120).

[0106] Next, the third-party tool interface (150) can transmit the test progress results to an external commercial tool (13).

[0107] After the simulation is completed, the operation can be stopped and the result logs can be collected, which can then be sent to the user interface (11) for visualization.

[0108] In another embodiment, the present invention can receive a simulation operation signal through a simulation model built in an external commercial tool (13) through a third-party tool interface (150). For example, vehicle speed data generated in an external commercial tool (13) can be directly transmitted to the third-party tool interface (150) without going through the cooperative simulation middleware unit (120).

[0109] Next, the third-party tool interface (150) transmits the simulation operation signal to the ECU interface unit (130), and transmits the simulation operation signal to the virtual ECU (12) corresponding to the simulation through the ECU interface unit (130), so that a test can be performed on the virtual ECU (12). In the above example, the virtual ECU (12) generates a simulation result by utilizing the speed data transmitted from the external commercial tool (13), and accordingly, the virtual ECU (12) can display a speed gauge on the cluster.

[0110] In this embodiment, direct communication is possible without going through the cooperative simulation middleware unit (120), so the verification process can be performed more simply and efficiently.

[0111] Meanwhile, in the above description, steps S110 to S150 may be further divided into additional steps or combined into fewer steps, depending on the implementation of the present invention. Furthermore, some steps may be omitted as needed, and the order of the steps may be changed. Furthermore, even if other details are omitted, the details described in FIGS. 2 to 4 and 5 to 8 are mutually applicable.

[0112] The virtual environment-based vehicle ECU verification system (100) and method in one embodiment of the present invention described above can be implemented as a program (or application) to be executed in combination with a computer as hardware and stored in a medium.

[0113] The above-described program may include codes coded in a computer language, such as C, C++, JAVA, Ruby, or machine language, that can be read by the processor (CPU) of the computer through the device interface of the computer, so that the computer reads the program and executes the methods implemented as a program. Such codes may include functional codes related to functions that define functions necessary to execute the methods, and may include control codes related to execution procedures necessary for the processor of the computer to execute the functions according to a predetermined procedure. In addition, such codes may further include memory reference-related codes regarding which location (address address) of the internal or external memory of the computer should reference additional information or media necessary for the processor of the computer to execute the functions. In addition, if the processor of the computer needs to communicate with any other computer or server located remotely in order to execute the functions, the code may further include communication-related code regarding how to communicate with any other computer or server located remotely using the communication module of the computer, and what information or media to send and receive during communication.

[0114] The above storage medium refers to a medium that stores data semi-permanently and can be read by a device, rather than a medium that stores data for a short period of time, such as a register, cache, or memory. Specifically, examples of the storage medium include, but are not limited to, ROM, RAM, CD-ROM, magnetic tape, floppy disk, and optical data storage device. That is, the program can be stored in various recording media on various servers that the computer can access or in various recording media on the user's computer. In addition, the medium can be distributed across network-connected computer systems, so that computer-readable code can be stored in a distributed manner.

[0115] The foregoing description of the present invention is for illustrative purposes only, and those skilled in the art will readily appreciate that the present invention can be readily modified into other specific forms without altering the technical spirit or essential characteristics of the present invention. Therefore, the embodiments described above should be understood as illustrative in all respects and not restrictive. For example, each component described as a single entity may be implemented in a distributed manner, and similarly, components described as distributed may be implemented in a combined manner.

[0116] The scope of the present invention is indicated by the claims described below rather than the detailed description above, and all changes or modifications derived from the meaning and scope of the claims and their equivalent concepts should be interpreted as being included in the scope of the present invention.

Claims

1. A method performed by a virtual environment-based vehicle ECU verification system, A step of receiving a control command from a user interface; A step of reading out at least one FMU model corresponding to the control command from the cooperative simulation middleware section; A step of performing a simulation based on the above extracted FMU model; A step of transmitting a simulation operation signal according to the above simulation performance to an ECU interface through a virtual ECU wrapper (vECU Wrapper) on the cooperative simulation middleware section; and Including a step of transmitting the simulation operation signal to a virtual ECU corresponding to the simulation through the ECU interface to conduct a test on the virtual ECU. How to verify a vehicle ECU.

2. In paragraph 1, The steps for performing a simulation based on the above extracted FMU model are: A step of generating a control signal for a predetermined function in a first FMU corresponding to an ECU performing a predetermined function of a vehicle in the cooperative simulation middleware section; A step of distributing the above control signal to peripheral FMUs through a second FMU in charge of communication functions; A step of determining the validity of the control signal in the above peripheral FMU; and Including a step of applying the control signal in the peripheral FMU determined to be valid as a result of the above judgment. How to verify a vehicle ECU.

3. In paragraph 2, The step of transmitting the simulation operation signal according to the above simulation performance to the ECU interface through the virtual ECU wrapper (vECU Wrapper) on the cooperative simulation middleware section is as follows. The virtual ECU reference transmits the control signal to the ECU interface so that the control signal is transmitted to a valid virtual ECU. How to verify a vehicle ECU.

4. In paragraph 1, A step of storing development environment setting information received from the user interface in a database; A step of receiving an external commercial tool connection command through the above user interface; A step of transmitting the development environment setting information to a third-party tool interface in response to the above connection command; and Further comprising a step of establishing a connection with an external commercial tool by transmitting the development environment setting information to the external commercial tool through the third-party tool interface. How to verify a vehicle ECU.

5. In paragraph 4, The steps for performing a simulation based on the above extracted FMU model are: The FMU model extracted from the above-mentioned cooperative simulation middleware section and the simulation model built in the above-mentioned external commercial tool are linked to perform the simulation. As the test for the virtual ECU progresses, the cooperative simulation middleware unit further includes a step of receiving the test progress results through the virtual ECU reference. How to verify a vehicle ECU.

6. In paragraph 5, A step in which the third-party tool interface receives a simulation operation signal from the external commercial tool; A step of transmitting a simulation operation signal received through the third-party tool interface from the third-party reference of the cooperative simulation middleware section to the master simulation section through FMI; A step of converting the simulation operation signal in the master simulation unit into a form that can communicate with the virtual ECU and transmitting it to the virtual ECU reference; and The virtual ECU reference further includes a step of transmitting the converted simulation operation signal to a corresponding virtual ECU through the ECU interface to perform a test on the virtual ECU. How to verify a vehicle ECU.

7. In paragraph 4, A step of bypassing a simulation operation signal through a simulation model built in the external commercial tool to the ECU interface through the virtual ECU reference of the cooperative simulation middleware section; A step of receiving the test progress results through the virtual ECU reference by the cooperative simulation middleware unit as the test for the virtual ECU progresses; A step of bypassing to the third-party tool interface through the third-party referrer of the above cooperative simulation middleware section; and Further comprising a step of transmitting the test progress results to the external commercial tool through the third-party tool interface. How to verify a vehicle ECU.

8. In paragraph 4, A step of receiving a simulation operation signal through a simulation model built in the above external commercial tool through the third-party tool interface; A step of transmitting the simulation operation signal from the third-party tool interface to the ECU interface; and Including a further step of transmitting the simulation operation signal to a virtual ECU corresponding to the simulation through the ECU interface to conduct a test on the virtual ECU. How to verify a vehicle ECU.

9. A control command receiving unit that receives control commands from the user interface; A cooperative simulation middleware unit that reads out at least one FMU model corresponding to the above control command, performs a simulation based on the read FMU model, and then transmits a simulation operation signal according to the simulation performance through a virtual ECU wrapper (vECU Wrapper). Including an ECU interface unit that transmits the simulation operation signal to a virtual ECU corresponding to the simulation upon receiving the simulation operation signal, thereby performing a test on the virtual ECU. A virtual environment-based vehicle ECU verification system.

Images