A CANFD controller software remote upgrade test method and system based on L3 vehicle architecture
Through multi-step testing methods and a collaborative working system, the problem of missing remote upgrade test of CANFD controller software in the L3 vehicle architecture is solved, ensuring the reliability and stability of the remote upgrade software, and realizing the L3 vehicle architecture Effective test of remote upgrade of CANFD controller software.
Patent Information
- Application Number
- CN202111611077.9
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- Filing Date
- 2021-12-27
- Publication Date
- 2024-11-26
- Estimated Expiration
- 2041-12-27
AI Technical Summary
The existing technology lacks the remote upgrade testing technology of CANFD controller software based on the L3 vehicle architecture, and it is impossible to effectively verify the software reliability and stability of remote upgrades.
A test method including multiple steps is adopted to ensure the transmission and flashing reliability from TSP to ECUS, including FBL flashing specifications by verifying the flashing reliability, transmission reliability, and closed-loop testing of ECUS, GW and THU. Testing, OTA-master flash verification, THU to GW transmission verification, TSP to THU, THU to GW and GW to ECUS closed-loop testing, using ECU-test, Dspace, System-bench, EGGplant, THU and OTAsystem working together .
The reliability and stability test of remote upgrade of CANFD controller software based on L3 vehicle architecture is realized, ensuring the reliability of remote upgrade software and filling the test gap.
Smart Images

Figure CN114356760B_ABST
Abstract
Description
Technical Field
[0001] The present invention belongs to the field of automotive electrical technology, and specifically relates to a CANFD controller software remote upgrade test technology based on an L3 vehicle architecture. Background Art
[0002] With the rapid development of intelligent and networked automobiles, the demand for embedded software has shown a blowout growth, and "software-defined cars" has become a trend. However, the traditional software upgrade method (users need to go to 4S stores to upgrade the software through special equipment) can no longer meet the current software iteration needs. It is necessary to develop a software for remote upgrades to meet the needs of software upgrades anytime and anywhere, but the software itself must be reliable and stable. Therefore, in order to ensure that the software quality meets the standards, the software needs to be tested. However, there is currently no upgrade test technology for CANFD controller software based on L3 vehicle architecture in related technologies. Therefore, this test technology is a difficult problem that needs to be overcome by R&D personnel.
[0003] The Chinese patent document with publication number "CN110727255A" discloses a technology named "A vehicle controller software upgrade test system and vehicle", and the Chinese patent document with publication number "CN106959926A" discloses a technology named "A software testing module and method for software upgrade". Both of the above technologies do not involve the remote upgrade test technology of CANFD controller software based on L3 vehicle architecture. Summary of the invention
[0004] The purpose of the present invention is to provide a CANFD controller software remote upgrade test method and system based on L3 vehicle architecture, and to solve the technical problem that there is no CANFD controller software remote upgrade test technology based on L3 vehicle architecture in the related technology for testing the remote upgraded software, and it is impossible to know whether the software to be used for remote upgrade is reliable and stable.
[0005] In order to solve the above technical problems, the present invention adopts the following technical solution, a CANFD controller software remote upgrade test method based on L3 vehicle architecture, comprising the following steps:
[0006] Step A: Verify the ECUS and regression test issues according to the FBL flash specification test. If all tests are qualified, proceed to step B;
[0007] Step B: The host computer virtual THU node stores the software package in the local hard disk, and transmits the software package to the GW, and triggers the GW to flash the ECUS to verify the flash reliability of the OTA-master. If the test passes, execute step C;
[0008] Step C: THU transmits the software package to GW to verify the transmission reliability from THU to GW. If the test passes, execute step D;
[0009] Step D: The host computer virtual TSP node stores the software package in the local hard disk, transfers the software package to the THU, and triggers the installation of the software package in the THU to verify the flash reliability from the THU to the GW and from the GW to the ECUS. If the test passes, execute step E;
[0010] Step E: Perform closed-loop tests from TSP to THU, THU to GW, and GW to ECUS to verify the transmission reliability and flash reliability from TSP to ECUS.
[0011] Preferably,
[0012] The test method is to carry out testing according to the test cases designed in advance, and the test steps of the test cases include:
[0013] Test step a: Test general functions, test FOTA-APK general functions and interactions;
[0014] Test step b: Test the download prompt, the download prompt is in multiple prompt scenarios, the prompt scenario includes pop-up prompt, background prompt and icon special prompt, and the download prompt is also divided into 4G network and WIFI network;
[0015] Test step c: testing the download process, which is an interactive scenario or abnormal interruption. The interactive scenario includes dialing BCALL, ECALL, Bluetooth phone, downloading offline maps, and restarting the vehicle.
[0016] Test step d: testing the data transmission process, wherein the data transmission process is performed under an interruption test scenario, wherein the test scenario includes frequent switching of power levels, frequent sleep and wake-up, frequent restart of the vehicle computer, and activation of the vehicle computer's big data collection configuration;
[0017] Test step e: Test installation prompts;
[0018] Test step f: test installation condition judgment, the conditions include power, parking state, handbrake state, engine state;
[0019] Test step g: test installation methods, including terminal immediate installation, terminal vehicle installation, terminal scheduled installation, remote immediate installation, and remote scheduled installation;
[0020] Test step h: test the installation process;
[0021] Test step i: Test the interaction between the vehicle and the vehicle control. The interaction between the vehicle and the vehicle control is under different upgrade tasks, including cockpit upgrade only, CANFD-ECU upgrade only, both cockpit upgrade and CANFD-ECU upgrade, and the combination of cockpit and CANFD-ECU upgrade types transferred to you.
[0022] Test step j: Test abnormal interruption, test abnormal recovery under common interruption scenarios, the interruption scenarios include vehicle hibernation, manual restart of the vehicle computer, and manual disconnection of the battery.
[0023] Preferably,
[0024] In the step B, during the test, the GW flashes the ECUS using the diagnostic FBL specification.
[0025] Preferably,
[0026] In step D, during the test, the GW reads the software component number and the current software version number of the ECUS through a diagnostic command, and the GW feeds back the software component number and the current software version number to the THU through a private protocol with the THU, and the THU feeds back the software component number and the current software version number to FOTA-APK through an internal serial port.
[0027] Preferably, the screen and instrument feed back the software information to the THU via LVDS, USB protocol and virtual Ethernet protocol, and the THU feeds back the software information to the FOTA-APK via an internal serial port.
[0028] Preferably, in the step E, during the test, FOTA-APK feeds back the software part number and the current software version number to OTA-service via WIFI or TBOX's 4G network, the OTA-service feeds back the list of upgradeable objects to the THU, and the THU downloads the software package of the upgradeable object from the TSP via WIFI or 4G network.
[0029] Preferably, if the THU does not store the rollback package of the upgradeable object, the rollback package is downloaded.
[0030] The present invention also provides a CANFD controller software remote upgrade test system based on L3 vehicle architecture, which executes the CANFD controller software remote upgrade test method based on L3 vehicle architecture according to any one of claims 1 to 7 through ECU-test, Dspace, System-bench, EGGplant, THU and OTAsystem working in collaboration with each other; the ECU-test communicates with the Dspace, the Dspace communicates with the System-bench, the ECU-test communicates with the EGGplant, the EGGplant communicates with the THU, and the ECU-test communicates with the OTAsystem.
[0031] Preferably, the Dspace is connected to the System-bench via a CAN or CANFD board to achieve communication.
[0032] Preferably, the EGGplant is connected to the THU via an ADB debugging interface to achieve communication.
[0033] By adopting the above-mentioned technical scheme, the beneficial technical effects that can be achieved by the present invention are stated as follows: The present invention is a CANFD controller software remote upgrade test technology based on the L3 vehicle architecture, which can ensure that the software to be used for remote upgrade is reliable and stable, making the test of remote upgrade of CANFD controller software based on the L3 vehicle architecture possible, filling the testing gap. BRIEF DESCRIPTION OF THE DRAWINGS
[0034] Figure 1 A diagram of the physical architecture of the system applicable to the upgrade of the present invention;
[0035] Figure 2 It is the upgrade flow chart of the present invention;
[0036] Figure 3 Design a mind map for the use cases of the present invention;
[0037] Figure 4 It is a test flow chart of the present invention;
[0038] Figure 5 This is a diagram of the automated testing framework of the present invention. DETAILED DESCRIPTION
[0039] The present invention will be further described below in conjunction with the accompanying drawings.
[0040] TSP: Telematics Service Provider;
[0041] PKI: Public Key Infrastructure;
[0042] Screen: display screen;
[0043] instrument: instrument;
[0044] LVDS: audio and video transmission line;
[0045] BCALL: Roadside Assistance;
[0046] ECALL: Emergency assistance.
[0047] With the rapid development of L3 autonomous driving technology, L3 technology itself has become a watershed and a label for major OEMs to demonstrate their technical strength. At the same time, L3 technology itself has put forward higher requirements on the electronic and electrical architecture of the whole vehicle, and also put forward higher requirements on the remote upgrade technology of the software. Of course, it also puts forward higher requirements on the remote upgrade testing technology, such as the upgrade speed, the compatibility of the upgrade protocol, etc. Based on the L3 technical architecture, the present invention proposes a CANFD controller software remote upgrade test method and system based on the L3 vehicle architecture.
[0048] From the perspective of test categories, the entire testing activity can be divided into four sections: functional testing, stress testing, performance testing, and stability testing. Functional testing and stability testing are mainly based on the partial analysis method defined in ISTQB to design test cases and execute tests accordingly. Stress testing and performance testing are mainly carried out with the help of automated testing tools. Performance testing refers to simulating multiple terminals to initiate upgrade requests to the server at the same time, which is a routine test.
[0049] Automated test development is to solve stress testing needs, and mainly focuses on setting up an automated test environment and developing automated scripts.
[0050] The automation script is a script for executing the test task, and the automated test environment construction is to build a system for executing the automated test task. Because the present invention is based on the L3 vehicle architecture, it is necessary to first describe the remote upgrade based on the L3 architecture.
[0051] like Figure 1 The figure shows the physical architecture diagram of the system applicable to the upgrade of the present invention. The present invention is an upgrade test method based on this architecture. The GW is connected to the THU via ICAN and Data CANFD. ICAN is used to send and receive regular event messages, and DataCANFD is used for software package data transmission between the THU and the GW. The CANFD-ECUS is connected to the GW via CANFD, and the GW upgrades and flashes the ECU via CANFD.
[0052] Since the traditional vehicle architecture uses CAN bus as the main data communication medium, there are two major shortcomings in the controller software upgrade process. One is that the data transmission speed from THU to GW is too slow, and the other is that the flashing speed from GW to ECUS is too slow. These two shortcomings will lead to a greater possibility of upgrade failure and limit the size of the software package.
[0053] The L3 vehicle architecture specifically referred to in the present invention uses the CANFD bus as the data communication medium during the controller software upgrade process to improve data transmission and flashing speeds, thereby improving the reliability of the upgrade from the design end itself.
[0054] like Figure 2 As shown, it is the upgrade flow chart of the present invention, and the object under test implements the successful flashing process from pulling the package from the cloud to the CANFD-ECU according to this process step.
[0055] The software package of CANFD-ECU is encrypted and signed through the PKI (Public Key Infrastructure) system, and the software package is mounted to the OTA-service of the TSP (Automotive Remote Service Provider) background according to the software part number of the corresponding ECU. When mounting the software package, the type of upgrade needs to be indicated, such as silent upgrade, regular upgrade, and some upgrade parameters of the upgrade object need to be clarified, such as upgrade sequence, diagnostic ID number, etc. The upgrade task is released according to the mounted software package. The task information needs to include the TUID number of the device that executes the upgrade task and the time when the task takes effect. Note that all upgrade objects need to mount the relevant rollback package at the same time.
[0056] After the vehicle is powered on, GW will read the software part number and current software version number of CANFD-ECU through diagnostic commands. After GW successfully obtains the software information of ECU, it will feed back the relevant information to the vehicle through the private protocol with the vehicle computer, and the vehicle computer will then feed back the information to FOTA\APK through the internal serial port. The screen (display) and instrument (instrument) feed back the relevant software information to the vehicle computer through LVDS, USB protocol, and virtual Ethernet protocol, and the vehicle computer will then feed back the information to FOTA-APK through the internal serial port.
[0057] After FOTA-APK collects the software information of all objects related to CANFD-ECU and cockpit, it transmits it to OTA-service through WIFI hotspot network or TBOX's 4G network. After OTA-SERVICE receives the software information fed back by the terminal device, it calculates the list of objects that can be upgraded based on the software part number and version number. OTA-service feeds back the list of upgradeable objects to the vehicle computer. Based on this list, the vehicle computer downloads the software package of the upgrade object from TSP to the terminal through WIFI hotspot or 4G network. If the terminal does not store the rollback package of the upgrade object, the rollback package will also be downloaded at the same time.
[0058] After the vehicle computer downloads all the upgrade object software packages, it prompts the user to click to install immediately, install off-vehicle, or schedule installation. After the user clicks to install, the vehicle computer line notifies the GW to flash the CANFD-ECU. The GW flashes the CANFD-ECU through the diagnostic FBL specification. The vehicle computer then flashes the cockpit-related software through LVDS (audio and video transmission line) and USB. After all objects are upgraded, the vehicle computer automatically restarts to prompt that the installation is successful.
[0059] From the above, it can be seen that the remote upgrade based on the L3 vehicle architecture is different from the traditional upgrade technology, so the test method is also improved accordingly to obtain the test method of the present invention, such as Figure 4 As shown, it is a test flow chart of the present invention. The test flow of the present invention is divided into five stages and carried out in sequence.
[0060] Step A: Verify the ECUS and regression test issues according to the FBL flash specification test. If all tests are qualified, proceed to step B. Step A is the basis for the execution of subsequent steps, and step A must be tested to pass.
[0061] Step B: The host computer virtual THU vehicle node stores the software package on the local hard disk and transfers the software package to the GW, triggering the GW to flash the ECUS to verify the flash reliability of the OTA-master. If the test passes, execute step C. Step B must also be tested before the subsequent steps can be continued. During the test, the GW flashes the ECUS according to the diagnostic FBL specification.
[0062] Step C: THU transmits the software package to GW to verify the transmission reliability from THU to GW. If the test passes, execute step D.
[0063] Step D: The host computer virtual TSP node stores the software package on the local hard disk, transfers the software package to THU, triggers the installation of the software package in THU to verify the reliability of flashing from THU to GW and GW to ECUS. If the test passes, execute step E. During the test, GW will read the software part number and current software version number of ECUS through diagnostic commands. GW will feedback the software part number and current software version number to THU through a private protocol with THU. THU will feedback the software part number and current software version number to FOTA-APK through the internal serial port. Screen and instrument feedback software information to THU through LVDS, USB protocol and virtual Ethernet protocol, and THU will feedback software information to FOTA-APK through the internal serial port.
[0064] Step E: Conduct closed-loop tests from TSP to THU, THU to GW, and GW to ECUS to verify the transmission reliability and flash reliability from TSP to ECUS. During the test, FOTA-APK feeds back the software part number and current software version number to OTA-service via WIFI or TBOX's 4G network, and OTA-service feeds back the list of upgradeable objects to THU. THU downloads the software package of the upgradeable object from TSP via WIFI or 4G network. If THU does not store the rollback package of the upgradeable object, download the rollback package.
[0065] The above test method is tested according to the test cases developed in advance. The design idea diagram of the test cases is described below.
[0066] like Figure 3 As shown, this is a test case design idea diagram of the present invention, and the development and design of the entire test case is carried out according to this idea.
[0067] In the general functions, it is necessary to focus on testing the various theme application scenarios of FOTA-APK in the car computer, the Chinese-English switching scenarios, the four-corner public components in the FOTA interface, the interaction of the upgrade description, etc. The general functions mainly examine the general functions and interactions of FOTA-APK.
[0068] Download prompts need to consider a variety of prompt scenarios, such as pop-up prompts, background prompts, special icon prompts, etc. At the same time, it is necessary to distinguish the different prompt logics of 4G networks and WIFI networks. The download process focuses on the interactive scenarios and abnormal interruptions during the download process, such as calling BCALL (road rescue), ECALL (emergency rescue)\Bluetooth phone, downloading offline maps, and transferring them to the car computer during the download process. The test points of the data transmission process and the download process are similar. It should be noted that the data transmission process should also increase the interruption test scenarios, such as frequent switching of power gears, frequent sleep wake-up, frequent restart of the car computer, and opening the big data collection configuration of the car computer. The test points of the installation prompt and the download prompt are similar, and the difference lies in the different option tests in the installation prompt interface. The installation condition judgment and the installation prompt can be tested together. The condition judgment needs to traverse all conditions such as power, registration status, handbrake status, and engine status. The installation method needs to consider the activation and exit of several different installations, such as terminal immediate installation, terminal car installation, terminal appointment installation, remote immediate installation, and remote appointment installation. The installation process focuses on the success rate of the installation and the interaction of the installation process, such as the logical processing mechanism of the diagnostic message.
[0069] The tests of cockpit software upgrade and CANFD-ECU upgrade should consider different combinations of upgrade tasks, such as: only cockpit upgrade, only CANFD-ECU upgrade, both types of upgrades, and different combinations of upgrade objects in each upgrade type (such as the upgrade combination of IBCM and GW, the combination of vehicle OS and vehicle MCU), etc. The abnormal interruption category mainly examines the abnormal recovery situation under common interruption scenarios, such as the vehicle is in sleep mode, the vehicle is manually restarted, and the battery is manually disconnected.
[0070] According to the design idea of the test case, the test steps of the test method of the present invention include the following test steps:
[0071] Test step a: Test general functions, test FOTA-APK general functions and interactions;
[0072] Test step b: Test the download prompt. The download prompt is in multiple prompt scenarios, including pop-up prompt, background prompt and icon special prompt. The download prompt is also divided into 4G network and WIFI network.
[0073] Test step c: Test the download process. The download process is in interactive scenarios and abnormal interruptions. The interactive scenarios include calling BCALL, ECALL, Bluetooth phone, downloading offline maps, and restarting the vehicle.
[0074] Test step d: Test the data transmission process. The data transmission process is under the interruption test scenario. The test scenario includes frequent switching of power gears, frequent sleep and wake-up, frequent restart of the vehicle computer, and opening of the vehicle computer's big data collection configuration;
[0075] Test step e: Test installation prompts;
[0076] Test step f: Test installation condition judgment, the conditions include power, parking status, handbrake status, engine status;
[0077] Test step g: Test installation methods, including terminal immediate installation, terminal vehicle installation, terminal scheduled installation, remote immediate installation and remote scheduled installation;
[0078] Test step h: test the installation process;
[0079] Test step i: Test the interaction between the vehicle and the vehicle control. The interaction between the vehicle and the vehicle control is under different upgrade tasks. The upgrade tasks include cockpit upgrade only, CANFD-ECU upgrade only, both cockpit upgrade and CANFD-ECU upgrade, and the combination of cockpit and CANFD-ECU upgrade types transferred to your different upgrade objects;
[0080] Test step j: Test abnormal interruption and abnormal recovery under common interruption scenarios. Interruption scenarios include vehicle hibernation, manual restart of the vehicle computer, and manual disconnection of the battery.
[0081] The CAN controller software remote upgrade test is tested according to the originally written test cases according to the following system, which is the CANFD controller software remote upgrade test system based on the L3 vehicle architecture. The system executes the above-mentioned CANFD controller software remote upgrade test method based on the L3 vehicle architecture through the collaborative work of ECU-test, Dspace (a host computer software), System-bench, EGGplant (software), THU and OTAsystem; ECU-test communicates with Dspace (a host computer software), Dspace communicates with System-bench through CAN and CANFD boards, ECU-test communicates with EGGplant, EGGplant communicates with THU through the ADB debugging interface, and ECU-test communicates with OTAsystem.
[0082] ECU-test is the control center of the entire automated test project. ECU-test communicates with Dspace software through internal software interfaces. Dspace software is connected to the physical test bench through CAN and CANFD boards to achieve data communication. ECU-test can monitor the network data of the bench and control the power-on and power-off of the test bench, including simulating the sending of message data.
[0083] ECU-test communicates with EGGplant software through the internal software interface. EGGplant connects to the vehicle computer through the vehicle computer's ADB debugging interface to take screenshots of all FOTA UI interfaces and compare information. ECU-test can monitor each work process of the FOTA software and determine the expected results.
[0084] ECU-test uses Python scripts to achieve mutual communication with OTAsystem, and ECU-test can control the status of upgrade tasks released by TSP cloud at any time. Finally, ECU-test automatically outputs the test report after the test is completed.
Claims
1. A CANFD controller software remote upgrade test method based on L3 vehicle architecture, characterized in that: The following steps are involved: Step A: Verify the ECUS and regression test issues according to the FBL flash specification test. If all tests are qualified, proceed to step B; Step B: The host computer virtual THU node stores the software package in the local hard disk, and transmits the software package to the GW, and triggers the GW to flash the ECUS to verify the flash reliability of the OTA-master. If the test passes, execute step C; Step C: THU transmits the software package to GW to verify the transmission reliability from THU to GW. If the test passes, execute step D; Step D: The host computer virtual TSP node stores the software package in the local hard disk, transfers the software package to the THU, and triggers the installation of the software package in the THU to verify the flash reliability from the THU to the GW and from the GW to the ECUS. If the test passes, execute step E; Step E: Perform closed-loop tests from TSP to THU, THU to GW, and GW to ECUS to verify the transmission reliability and flashing reliability from TSP to ECUS; The system for executing the method includes ECU-test, host computer software Dspace, System-bench, EGGplant software, THU and OTAsystem, wherein the ECU-test communicates with the host computer software Dspace, the host computer software Dspace communicates with the System-bench, the ECU-test communicates with the EGGplant, the EGGplant communicates with the THU, and the ECU-test communicates with the OTAsystem; ECU-test is the control center of the entire automated test project. ECU-test communicates with Dspace software through internal software interfaces. Dspace software is connected to the physical test bench through CAN and CANFD boards to achieve data communication. ECU-test can monitor the network data of the bench and control the power-on and power-off of the test bench, including simulating the sending of message data. ECU-test communicates with EGGplant software through the internal software interface. EGGplant connects to the vehicle computer through the vehicle computer's ADB debugging interface to take screenshots of all FOTA UI interfaces and compare information. ECU-test can monitor each workflow of the FOTA software and determine expected results. ECU-test communicates with OTAsystem through Python scripts, controls the status of upgrade tasks released by TSP cloud at any time, and automatically outputs the test report after the ECU-test test is completed.
2. The CANFD controller software remote upgrade test method based on L3 vehicle architecture according to claim 1 is characterized in that: The test method is to carry out the test according to the test case designed in advance, and the test steps of the test case include: Test step a: Test general functions, test FOTA-APK general functions and interactions; Test step b: testing the download prompt, the download prompt is in multiple prompt scenarios, the prompt scenarios include pop-up prompt, background prompt and icon prompt, and the download prompt is also divided into 4G network and WIFI network; Test step c: testing the download process, which is an interactive scenario or abnormal interruption. The interactive scenario includes dialing BCALL, ECALL, Bluetooth phone, downloading offline maps, and restarting the vehicle. Test step d: testing the data transmission process, wherein the data transmission process is performed under an interruption test scenario, wherein the test scenario includes frequent switching of power levels, frequent sleep and wake-up, frequent restart of the vehicle computer, and activation of the vehicle computer's big data collection configuration; Test step e: Test installation prompts; Test step f: test installation condition judgment, the conditions include power, parking state, handbrake state, engine state; Test step g: test installation methods, including terminal immediate installation, terminal vehicle installation, terminal scheduled installation, remote immediate installation, and remote scheduled installation; Test step h: test the installation process; Test step i: Test the interaction between the vehicle and the vehicle control, where the interaction between the vehicle and the vehicle control is under different upgrade tasks, including cockpit upgrade only, CANFD-ECU upgrade only, both cockpit upgrade and CANFD-ECU upgrade, and a combination of different upgrade objects of cockpit and CANFD-ECU upgrade types; Test step j: Test abnormal interruption, test abnormal recovery under common interruption scenarios, the interruption scenarios include vehicle hibernation, manual restart of the vehicle computer, and manual disconnection of the battery.
3. The CANFD controller software remote upgrade test method based on L3 vehicle architecture according to claim 1 is characterized in that: In the step B, during the test, the GW flashes the ECUS using the diagnostic FBL specification.
4. The CANFD controller software remote upgrade test method based on L3 vehicle architecture according to claim 1 is characterized in that: In step D, during the test, the GW reads the software component number and the current software version number of the ECUS through a diagnostic command, and the GW feeds back the software component number and the current software version number to the THU through a private protocol with the THU, and the THU feeds back the software component number and the current software version number to FOTA-APK through an internal serial port.
5. The CANFD controller software remote upgrade test method based on L3 vehicle architecture according to claim 4 is characterized in that: The screen and instrument feed back software information to the THU via LVDS, USB protocol and virtual Ethernet protocol, and the THU feeds back the software information to the FOTA-APK via an internal serial port.
6. The CANFD controller software remote upgrade test method based on L3 vehicle architecture according to claim 1 is characterized in that: In step E, during the test, FOTA-APK feeds back the software part number and the current software version number to OTA-service via WIFI or TBOX's 4G network, and the OTA-service feeds back the list of upgradeable objects to the THU, and the THU downloads the software package of the upgradeable object from the TSP via WIFI or 4G network.
7. The CANFD controller software remote upgrade test method based on L3 vehicle architecture according to claim 6 is characterized in that: If the THU does not store the rollback package of the upgradeable object, the rollback package is downloaded.
8. A CANFD controller software remote upgrade test system based on L3 vehicle architecture, characterized in that: The system executes the CANFD controller software remote upgrade test method based on L3 vehicle architecture as described in any one of claims 1 to 7 through ECU-test, Dspace, System-bench, EGGplant, THU and OTAsystem working in coordination with each other; the ECU-test communicates with the Dspace, the Dspace communicates with the System-bench, the ECU-test communicates with the EGGplant, the EGGplant communicates with the THU, and the ECU-test communicates with the OTAsystem.
9. The CANFD controller software remote upgrade test system based on L3 vehicle architecture according to claim 8 is characterized in that: The Dspace is connected to the System-bench via CAN and CANFD boards to achieve communication.
10. The CANFD controller software remote upgrade test system based on L3 vehicle architecture according to claim 8 is characterized in that: The EGGplant is connected to the THU via the ADB debugging interface to achieve communication.
