A system and method for whole vehicle OTA automatic test in a production line environment

Abstract

The application relates to a system and method for automatically testing OTA of a whole vehicle in a production line environment, and belongs to the technical field of vehicle OTA testing. The system solves the problems of no automatic OTA testing system for a whole vehicle in a production line environment and low efficiency in a complex testing process. The system comprises a client, an edge device, an OBD wireless switching device, an OTA testing server and a production line OTA server. The edge device is used for scheduling a testing task, sending the testing task for the production line OTA server to the production line OTA server, and sending the testing task for testing a vehicle end to the OBD wireless switching device. The OBD wireless switching device is used for sending the testing task for testing the vehicle end to a testing vehicle, receiving a testing result fed back by the testing vehicle, and sending the testing result fed back by the testing vehicle to the edge device. The edge device sends the testing result fed back by the testing vehicle to the OTA testing server. The application is suitable for automatically testing OTA of a whole vehicle in a production line environment.

Description

TECHNICAL FIELD

[0001] The present application relates to the technical field of vehicle OTA test, in particular to a system and method for automatically testing a whole vehicle in a production line environment. BACKGROUND

[0002] With the development of the automobile industry towards standardization, intelligentization and software, the combination of automobiles and the Internet has become a mainstream trend, and automobile OTA technology is also widely used by various vehicle manufacturers. In order to ensure the stability and safety of OTA functions, it is urgent to automatically test the whole vehicle upgraded in the production line environment.

[0003] At present, in the automobile OTA test industry, there are tools for OTA testing, and these tools are usually realized in the form of customization. These tools can test certain functions of specific vehicle models to varying degrees.

[0004] The biggest drawback of the prior art is that the current technology mainly focuses on the OTA development stage, and the test range is concentrated in the laboratory scene of the vehicle. The test environment in the laboratory scene is ideal and complete. However, after the assembly is completed, the vehicle is a finished vehicle, and after the vehicle OTA upgrade is completed, the upgrade result needs to be tested. The existing technology has certain limitations.

[0005] The existing problems in the prior art are:

[0006] 1. Only component testing can be completed, and whole vehicle testing in a production line environment is not possible;

[0007] 2. Testing can only be performed in a laboratory bench environment, and a large cabinet and server need to be independently deployed, which has strong site limitations;

[0008] 3. The instruments used in the test process are large in size and the number reaches more than ten, such as control units, switches, program-controlled power supplies, bus monitoring devices, cellular communication testers, LTE testers, channel simulators, and ECU drawer panels, which are not convenient to carry;

[0009] 4. The test software excessively relies on foreign technology, such as the DiVa tool of the German Vector company, and lacks independent innovation. SUMMARY

[0010] The present application aims to solve the problem of the lack of a whole vehicle OTA automatic test system in a production line environment and the low efficiency of the test process in the prior art, and provides a system and method for automatically testing a whole vehicle in a production line environment.

[0011] The application is realized by the following technical scheme, and the application provides a vehicle OTA automatic test system for a vehicle in a production line environment, which comprises a client, an edge device, an OBD wireless switching device, an OTA test server and a production line OTA server;

[0012] The client is used for accessing OTA test platform software on the OTA test server and checking test reports;

[0013] The OTA test server is used for creating a test vehicle model, parsing a DBC file of the test vehicle model, editing a test task according to the DBC file, sending the test task to the edge device through the OTA test server, and generating a test report according to test results fed back by the test vehicle and test results of the production line OTA server and sending the test report to the client.

[0014] The edge device is used for scheduling the test task, and specifically comprises:

[0015] The test task for the production line OTA server is sent to the production line OTA server, and the test task for the test vehicle end is sent to the OBD wireless switching device.

[0016] The production line OTA server is used for sending upgrade information of a test case in the test task for the production line OTA server to the test vehicle, and sending test results of the production line OTA server to the edge device, and the edge device sends the test results of the production line OTA server to the OTA test server.

[0017] The OBD wireless switching device is used for sending the test task for the test vehicle end to the test vehicle, receiving test results fed back by the test vehicle, and sending the test results fed back by the test vehicle to the edge device, and the edge device sends the test results fed back by the test vehicle to the OTA test server.

[0018] Further, the test task is edited according to the DBC file, and specifically comprises configuring a test script for testing the production line OTA server, a test script for testing the test vehicle end and CAN signals according to the DBC file.

[0019] Test cases are edited according to the test script for testing the production line OTA server, the test script for testing the test vehicle end and the CAN signals.

[0020] The test task is edited according to the test cases.

[0021] Further, the test case includes API interface instructions, CAN scripts and UDS diagnostic messages.

[0022] Further, the test task for the OTA server in the production line includes API interface instructions, and the test task for testing the vehicle end includes CAN scripts and UDS diagnostic messages.

[0023] Further, the test script for testing the OTA server in the production line includes server load testing, fault injection testing, server stress testing and server network security testing.

[0024] The test script for testing the vehicle end includes testing of upgrade strategy mechanism, security anti-theft mechanism, parallel upgrade mechanism and upgrade guarantee mechanism.

[0025] In another aspect, the present application provides an OTA automatic testing method for a whole vehicle in a production line environment, the method comprising:

[0026] Step 1, configure an edge device, which has the functions of data communication, local calculation and AI inference, and cloud configuration synchronization;

[0027] Step 2, configure an OBD wireless switching device, which can realize the communication function between the measuring vehicle and the edge device;

[0028] Step 3, create a test vehicle model by using the OTA test platform software on the OTA test server, and parse the DBC file of the test vehicle model, edit test tasks according to the DBC file, the test tasks including test tasks for the OTA server in the production line and test tasks for testing the vehicle end;

[0029] Step 4, the OTA test server sends the test tasks to the edge device;

[0030] Step 5, the edge device schedules the test tasks, specifically including:

[0031] sending the test tasks for the OTA server in the production line to the OTA server in the production line, and sending the test tasks for testing the vehicle end to the OBD wireless switching device;

[0032] Step 6, the OTA server in the production line sends the upgrade information in the test tasks for the OTA server in the production line to the test vehicle;

[0033] The OBD wireless switching device sends the test tasks for testing the vehicle end to the test vehicle;

[0034] Step 7, the test vehicle performs OTA test according to the upgrade information and the test task for the test vehicle end, and obtains test results of the production line OTA server and test results fed back by the vehicle;

[0035] Step 8, the production line OTA server sends the test results of the production line OTA server to the edge device;

[0036] The test vehicle sends the test results fed back by the vehicle to the OBD wireless switching device, and the OBD wireless switching device sends the test results fed back by the vehicle to the edge device;

[0037] Step 9, the edge device sends the test results of the production line OTA server and the test results fed back by the vehicle to the OTA test server, and the OTA test server generates a test report according to the test results of the production line OTA server and the test results fed back by the vehicle, and sends the test report to the client.

[0038] Further, the test task is edited according to the DBC file, and specifically includes: configuring a test script of a test production line OTA server, a test script of a test vehicle end and CAN signals according to the DBC file;

[0039] According to the test script of the test production line OTA server, the test script of the test vehicle end and the CAN signals, a test case is edited;

[0040] According to the test case, a test task is edited.

[0041] Further, the test case includes API interface instructions, CAN scripts and UDS diagnostic messages.

[0042] Further, the test task for the production line OTA server includes API interface instructions, and the test task for the test vehicle end includes CAN scripts and UDS diagnostic messages.

[0043] Further, the test script of the test production line OTA server includes server load test, fault injection test, server stress test and server network security test.

[0044] The test script of the test vehicle end includes test of upgrade strategy mechanism, security anti-theft mechanism, parallel upgrade mechanism and upgrade guarantee mechanism.

[0045] The beneficial effects of the application are as follows:

[0046] The application provides a vehicle OTA automatic testing system and method in a production line environment, and an OBD wireless switching device can be pre-configured after logging in a Web platform.

[0047] Compared with the disclosed patent literature, the application patent has the advantages of high integrity, good portability and strong timeliness in the vehicle OTA automatic testing method and system in the production line environment.

[0048] Firstly, the application realizes the OTA test for the vehicle; secondly, the application can meet the OTA test for the vehicle completed by the host factory, instead of the partial component test result under the development condition of the component or test bench, and solves the defect factors caused by human or machine in the process from the development to the offline of the vehicle OTA, and the test cases cover the test and evaluation of the OTA function of the vehicle, and the test and evaluation of the API interface of the OTA cloud platform in the production line, so that the OTA automatic testing range in the production line environment is more complete; thirdly, the test hardware adopts the edge device and the OBD wireless switching device, and compared with the other test schemes which need dozens of test devices, the application has the excellent portability; finally, the application can perform the OTA test in the OTA upgrading process in the production line environment, and the implementation manner is that the OTA cloud platform continuously calls the system API interface in the OTA upgrading process, the OTA test platform software records the API log of the OTA cloud platform, and the OTA test platform software can judge which ECU parts are upgraded in the OTA upgrading process of the OTA cloud platform by acquiring the UDS diagnostic message of the vehicle, the OTA test process and the OTA upgrading process are completely coincident, and there is no need to test for testing, so that the application has the high timeliness; the application guarantees the stability and safety of the OTA cloud platform and the vehicle, greatly improves the test speed, effectively saves the manpower and material resources, and fills the OTA automatic testing technology gap in the production line environment.

[0049] The edge device and the OBD wireless switching device of the application can realize the fast OTA automatic testing in the production line environment in the most portable way, and do not need to use too many instruments by improving the test direction and test content.

[0050] The OTA test environment in the application is to take a complete vehicle as a test condition, and the test equipment is composed of edge equipment and OBD wireless switching equipment as system equipment, and the data flow of the test task is from the test server to the edge equipment, and the test task is distributed to the production line OTA server and the OBD wireless switching equipment by the edge equipment, thereby solving the problems of long OTA test period and low overall test efficiency

[0051] The application is suitable for the OTA automatic test of the whole vehicle in the production line environment. BRIEF DESCRIPTION OF DRAWINGS

[0052] In order to more clearly illustrate the technical solutions of the present application, the drawings needed in the embodiments will be briefly introduced as follows, and obviously, other drawings can also be obtained by those skilled in the art without creative labor on the premise of not paying creative labor.

[0053] Figure 1 It is a test flow architecture diagram based on the system of the application.

[0054] Figure 2 It is a flowchart of the method of the application.

[0055] Figure 3 It is the principle of the edge equipment of the application Figure 1 ;

[0056] Figure 4 It is the principle of the edge equipment of the application Figure 2 ;

[0057] Figure 5 It is the principle diagram of the OBD wireless switching equipment of the application. DETAILED DESCRIPTION

[0058] The embodiments of the application will be described in detail below, and examples of the embodiments are shown in the drawings, wherein the same or similar reference signs represent the same or similar elements or elements with the same or similar functions throughout. The embodiments described below by referring to the drawings are exemplary and are intended to explain the application, and cannot be understood as a limitation of the application.

[0059] Embodiment one, a system for OTA automatic test of the whole vehicle in the production line environment, the system comprises: a client, an edge equipment, an OBD wireless switching equipment, an OTA test server and a production line OTA server.

[0060] The client is used for accessing the OTA test platform software on the OTA test server and viewing the test report.

[0061] The OTA test server is configured to create a test vehicle, parse a DBC file of the test vehicle, edit a test task according to the DBC file, the test task including a test task for the line OTA server and a test task for the test vehicle end, and send the test task to the edge device through the OTA test server; and is further configured to generate a test report according to a test result fed back by the test vehicle and a test result of the line OTA server, and send the test report to the client.

[0062] The edge device is configured to schedule the test task, and specifically includes:

[0063] The test task for the line OTA server is sent to the line OTA server, and the test task for the test vehicle end is sent to the OBD wireless switching device.

[0064] The line OTA server is configured to send upgrade information of a test case in the test task for the line OTA server to the test vehicle, and further configured to send a test result of the line OTA server to the edge device, and the edge device further sends the test result of the line OTA server to the OTA test server.

[0065] The OBD wireless switching device is configured to send the test task for the test vehicle end to the test vehicle, and further configured to receive a test result fed back by the test vehicle, and send the test result fed back by the test vehicle to the edge device, and the edge device further sends the test result fed back by the test vehicle to the OTA test server.

[0066] In this embodiment, an OTA automatic test system for a whole vehicle in a line environment is provided, as shown in Figure 1 As shown in the figure, the OBD wireless switching device can be pre-configured after logging in to the Web platform. The purpose of configuring the OBD device is to establish an association and pairing relationship between the platform and the OBD device. A new configuration is created, and a vehicle to be tested is selected. The main medium for testing is a test case. The test case is selected, and a rule strategy is specified to generate a task. The task is sent from the test server to the edge device. The edge device schedules and distributes different test cases.

[0067] One aspect is to test the API interface instruction of the OTA production line server, mainly test the API instruction issued by the production line OTA server to the vehicle, check whether the API instruction issued by the OTA cloud platform is returned according to the API request parameter and the expected response parameter input in the production line OTA test platform software, and the response parameter result includes the API status code and the response code; verify whether the API does not return a result or returns an abnormal result, no return result is judged according to the response status code 500, and abnormal result is judged according to the response status code other than 200, other status codes such as 403, 404, 405, 502, etc.; verify whether the API correctly triggers other events or correctly calls other APIs; verify whether the API correctly updates the data, and return these test result logs to the test system for analysis and statistics, the importance of testing the API interface instruction of the production line OTA cloud platform lies in that it can check the instability and incorrectness that may occur in the system of the production line OTA cloud platform, so the purpose of the test is to find the possible faults of the system API interface.

[0068] It should be noted that the API instruction is implemented by the OTA test platform software on the OTA cloud platform system deployed on the production line OTA server, and finally the API response result code is returned by the OTA cloud platform to the OTA test platform software, and the OTA test platform software compares the consistency of the response code parameter and the expected response code parameter, such as consistency, which achieves the purpose of passing the test, otherwise, which does not pass; the implementation of the instruction belongs to the data interaction between the OTA cloud platform deployed in the production line and the OTA test platform software.

[0069] The other aspect is to test the real vehicle. The OBD wireless switching device is inserted into the OBD interface of the vehicle, communicates with the TBOX of the whole vehicle through the CAN protocol, the TBOX issues the test case in the form of CAN signal to the ECU and IVI to be tested through the CGW, and the test log obtained after the test script program runs on the ECU and IVI to be tested is returned to the OBD wireless switching device through the CGW and the TBOX and stored, when the OBD wireless switching device executes all test cases, the structured data test result log is returned to the test server through the edge device, and finally the operator can view the test result and analysis report in the OTA test platform software.

[0070] The embodiment can realize OTA automatic testing of the whole vehicle in the production line environment, has the advantages of convenience, speed and efficiency compared with the traditional technical solution, that is, ensures the stability and safety of the OTA function, and also effectively saves manpower and material resources, fills the blank of OTA automatic testing technology of the whole vehicle in the production line environment.

[0071] The purpose of the embodiment is to provide an OTA automatic test system for a whole vehicle in a production line environment, which can realize user operation system platform access to a server, the server transmits data through an OBD device connection and a vehicle, including functions such as editing test cases, issuing test tasks, test result board, test defect analysis, and test report output, so as to realize OTA upgrade test of the whole vehicle in the production line environment.

[0072] It should be noted that 1. The OTA test environment of the embodiment is to take the whole vehicle of the completed assembly automobile as the test condition, that is, the measured vehicle is the off-line vehicle of the production line, wherein the whole vehicle part should include an OBD interface, a TBOX, a CGW, an ECU, and an IVI;

[0073] 2. The edge device is connected to a 24V power supply, and simultaneously accesses a network in the same local area network segment as the OTA test server and the production line OTA server;

[0074] 3. The OBD wireless switching device is powered by the OBD interface pin of the real vehicle, and is connected to the edge device through WIFI networking;

[0075] 4. The OBD wireless switching device communicates with the real vehicle ECU through CAN channel instructions;

[0076] 5. Since the OTA technology is to update the program stored in the Flash of each ECU of the vehicle to realize upgrade, and the UDS diagnostic message issued by the OTA test platform software is ultimately to the ECU, the response is given by the ECU, so the measured unit is the ECU;

[0077] 6. The system of the embodiment has functions such as vehicle model management, OBD device management, test case management, test task management, test result board, test defect analysis, and test report output.

[0078] Embodiment two, the embodiment is a further limitation of the OTA automatic test system for a whole vehicle in a production line environment according to the first embodiment, and in the embodiment, the test task is further limited according to the DBC file, specifically including:

[0079] According to the DBC file, the test script of the test production line OTA server, the test script of the test vehicle end, and the CAN signal are configured;

[0080] According to the test script of the test production line OTA server, the test script of the test vehicle end, and the CAN signal, the test case is edited;

[0081] According to the test case, the test task is edited.

[0082] The embodiment provides an editing method of a test task, so that the test task can be divided into a test task for testing an OTA server of a production line and a test task for testing a vehicle end, and problems of a long OTA test period and low overall test efficiency are solved.

[0083] In the third embodiment, the test case is further limited, and specifically includes:

[0084] The test case includes API interface instructions, CAN scripts and UDS diagnostic messages.

[0085] It should be noted that the API interface instructions are to be sent to the OTA server of the production line, and the CAN scripts and the UDS diagnostic messages are to be sent to the OBD wireless switching device and then to the measured vehicle, so that the problems of a long OTA test period and low overall test efficiency are solved.

[0086] It should be noted that the OBD wireless switching device can receive the UDS diagnostic messages and the structured OBD test logs returned by the OBD interface of the real vehicle, the edge device can receive the UDS diagnostic messages and the structured OBD test logs returned by the OBD wireless switching device, and the OTA test server can receive the UDS diagnostic messages, the structured OBD test logs and the API test logs returned by the edge device. Based on the above design scheme, the OTA test case task can be implemented by the upstream and downstream level communication message flow of the production line OTA server, the OTA test server, the edge device and the OBD wireless switching device.

[0087] In the fourth embodiment, the test task for the OTA server of the production line and the test task for the vehicle end are further limited, and specifically include:

[0088] The test task for the OTA server of the production line includes API interface instructions, and the test task for the vehicle end includes CAN scripts and UDS diagnostic messages.

[0089] In the fifth embodiment, the test script for testing the OTA server of the production line and the test script for testing the vehicle end are further limited, and specifically include:

[0090] The test script for testing the OTA server of the production line includes server load testing, fault injection testing, server stress testing, and server network security testing.

[0091] The test script for testing the vehicle end includes testing of upgrade strategy mechanism, security anti-theft mechanism, parallel upgrade mechanism, and upgrade guarantee mechanism.

[0092] It should be noted that the server stress testing (such as 7x24 hours continuous upgrade); the server network security testing includes penetration testing and attack testing; the test script for testing the OTA server of the production line adopts Web (HTTP / HTML) protocol; and the instructions of the script and API interface (message pushing, log receiving and saving, vehicle model version collection, and upgrade package generation strategy) to be tested are recorded in the OTA test platform software in sequence.

[0093] The test script for testing the vehicle end adopts CANBUS protocol, and the steps and script content of each function to be tested are edited in the OTA platform software.

[0094] Embodiment six is an automatic testing method for a vehicle in a production line environment, which comprises the following steps:

[0095] Step 1: configuring an edge device, which has the functions of data communication, local calculation and AI inference, and cloud configuration synchronization;

[0096] Step 2: configuring an OBD wireless switching device, which can realize the communication function between the vehicle and the edge device;

[0097] Step 3: creating a test vehicle by using the OTA test platform software on the OTA test server, and parsing the DBC file of the test vehicle, and editing a test task according to the DBC file, which includes a test task for the OTA server of the production line and a test task for the vehicle end;

[0098] Step 4: the OTA test server sends the test task to the edge device;

[0099] Step 5: the edge device schedules the test task, specifically including:

[0100] sending the test task for the OTA server of the production line to the OTA server of the production line; and sending the test task for the vehicle end to the OBD wireless switching device;

[0101] Step 6: the OTA server of the production line sends the upgrade information in the test task for the OTA server of the production line to the test vehicle;

[0102] The OBD wireless switching device sends the test task for testing the vehicle end to the test vehicle;

[0103] Step 7, the test vehicle performs OTA testing according to the upgrade information and the test task for testing the vehicle end, and obtains the test result of the production line OTA server and the test result fed back by the vehicle;

[0104] It should be noted that when the test vehicle performs OTA testing, the generated message record is uploaded to the OTA test server through the edge device and fed back to the test task interface of the OTA test platform software.

[0105] Step 8, the production line OTA server sends the test result of the production line OTA server to the edge device;

[0106] The test vehicle sends the test result fed back by the vehicle to the OBD wireless switching device, and the OBD wireless switching device sends the test result fed back by the vehicle to the edge device;

[0107] Step 9, the edge device sends the test result of the production line OTA server and the test result fed back by the vehicle to the OTA test server, the OTA test server generates a test report according to the test result of the production line OTA server and the test result fed back by the vehicle, and sends the test report to the client.

[0108] Embodiment seven, this embodiment is a specific embodiment of a method for performing OTA automatic testing on a whole vehicle in a production line environment, specifically:

[0109] As shown in Figure 2 , step 1:

[0110] The edge device (i.e. industrial intelligent edge device) has the capabilities of data communication, local calculation and AI inference, cloud configuration synchronization, etc.; the platform cloud management suite provides massive edge management capabilities, and interfaces different application production ecologies to provide powerful application integration, testing, management and distribution capabilities.

[0111] In this embodiment, it has two functions: first, it communicates with the production line OTA cloud server, the OTA test server and the OBD wireless switching device; second, it can receive and send data generated by test case tasks.

[0112] The device has the advantages of ultra-high efficiency, high performance, rich interfaces, etc. It is internally integrated with CAN, USB, Ethernet port, 4G, WIFI, HDMI, audio function interface and module to meet the needs of different occasions. The principle diagram of the industrial edge device is as Figure 3 ,Figure 4 as shown.

[0113] Step 2:

[0114] The OBD wireless adapter is connected with the OBD interface of the vehicle. The ECU data of the vehicle can be collected through CAN signals and UDS diagnostic messages. The ECU data is transmitted back to the edge device through the wireless network, and the edge device is uploaded to the OTA test software platform through the wireless network. The encryption chip built-in OBD wireless adapter can perform batch authorization function through OBD port and built-in protocol communication SDK and security authentication SDK. It has UDS diagnostic protocol. The device information diagram is as shown in Figure 5 as shown.

[0115] Step 3:

[0116] After the edge device in step 1 and the OBD wireless adapter in step 2 are configured, they are connected and paired through WIFI to ensure that the authentication is successful and communication is realized, and data can be uploaded and downloaded. Before performing the test task, the OBD wireless adapter should be inserted into the OBD interface of the real vehicle to establish a communication connection with the vehicle. The communication connection process is as follows: the real vehicle and the built-in certificate of the OBD wireless adapter pass TCP handshake identity authentication, the vehicle state is switched from user mode to factory mode, and OTA Session is stopped (i.e. stop the communication between the vehicle and the R&D OTA server). At this time, the real vehicle will be in factory mode and handshake identity authentication with the production line OTA server TCP.

[0117] Step 4:

[0118] Verify in advance that the production line OTA server can establish communication with the real vehicle TBOX (smart vehicle terminal in the Internet of Vehicles system) in step 3 through the 4G network;

[0119] Check the OTA test system communication link, log in to the OTA test platform software, and check that the OBD wireless adapter is in online state in the software. It can be judged that the OBD wireless adapter in step 3 has established a communication connection with the OTA test server through the edge device;

[0120] Check the communication between the edge device and the production line OTA server. Since they are in the same LAN segment, the edge device will send a PING packet to the production line OTA server after the service is started to verify the communication status;

[0121] Step 5:

[0122] In the OTA test platform software creates a test vehicle, and in the creation of the test vehicle page attachment module item upload the vehicle's DBC file, DBC database file is used to describe the CAN network nodes data communication file, contains the CAN bus protocol in the protocol data and its specific meaning, OTA test platform software can automatically parse the DBC file. OTA test platform software will automatically parse the uploaded DBC file, identify the CANID, network nodes, message, signal and environmental variables defined in the DBC file, for the CAN signal in step 7 configuration to the corresponding ECU system module, after the configuration of CAN signal in step 8 test case configuration edit and generate the corresponding test preconditions and step description of the test script.

[0123] Step 6:

[0124] Configuration test script, need to configure the test line OTA server test script and OTA vehicle end script, wherein

[0125] Line OTA server test script is mainly for server load testing, fault injection testing, server stress testing (such as 7x24 hours continuous upgrade), server network security testing (penetration testing, attack testing); test script using Web (HTTP / HTML) protocol, in the OTA test platform software in turn according to the steps to save each step to test the script and API interface (message push, log receiving and saving, vehicle version collection, upgrade package generation strategy) instruction.

[0126] It should be noted that the preset test order, the first step test call instruction, the second step test call instruction… After the configuration is completed, the OTA test platform software will execute the test according to the preset test script order step by step.

[0127] Vehicle end script includes the test of upgrade strategy mechanism, security anti-theft mechanism, parallel upgrade mechanism, upgrade guarantee mechanism; test script using CANBUS protocol, editing the steps and script content of each function to be tested in the OTA platform software.

[0128] Step 7:

[0129] Configuration CAN signal, according to the CANID parsed out in step 5 DBC file, select the CANID function in the OTA test platform software according to the CANID enumeration class parsed out in the DBC file, select the specified CANID, the system will automatically identify the CAN signal, maximum value, minimum value and other key information of the CANID added to each ECU system module under the vehicle, finally the CAN signal of each ECU module is connected to each ECU of the automobile through the 6th and 14th pins of the OBD wireless adapter device by CAN bus protocol.

[0130] Step 8:

[0131] Edit the test case, edit the corresponding preconditions and step descriptions in the use case, and insert the script in step 6 and the CANID in step 7 in the corresponding conditions and steps in the OTA test platform use case management function module in sequence to generate the test case.

[0132] Step 9:

[0133] Edit the test task and select the use case configured in step 8 in the test task module of the OTA test platform software. The task can contain multiple use cases, which include API interface instructions, CAN scripts and UDS diagnostic messages. Configure the strategy for the test task, which includes the priority of the test task and the number of test case executions. After the configuration is completed, it is necessary to confirm that the prerequisite OBD wireless adapter has been inserted into the OBD interface of the actual vehicle before executing the task. At this time, the OTA test platform software displays the task execution progress and the status results of each step.

[0134] The OTA test server's functions include running the service program of the OTA test platform software and establishing a network connection with the edge device;

[0135] The role of the OTA test platform software is that it is deployed on the OTA test server. All visual function interactions are edited, configured and viewed on this software, which can reflect the activities of the entire production line OTA automated test system.

[0136] Step 10:

[0137] The OTA test server executes and sends the test task message. In step 9, the OTA test platform software sends the test task message from the OTA test server to the edge device via Ethernet.

[0138] Step 11:

[0139] The edge device sends and receives scheduling test task messages. The edge device receives messages from the OTA test server in step 10. It is responsible for the distribution and scheduling of messages, and assigns the test tasks (API interface instructions) belonging to the back-end of the production line OTA cloud platform deployed on the production line OTA server to the production line OTA server, and assigns the test tasks (CAN scripts and UDS diagnostic messages) belonging to the vehicle side to the OBD wireless adapter.

[0140] Step 12:

[0141] The production line OTA server transmits and receives test task messages. After the production line OTA server receives the task assigned by the edge device in step 11, the production line OTA server checks the test case information contained in the task and the information in the server database for conditional matching. The API interface instruction test case information includes the VIN code of the test vehicle, the engine model, the transmission model, the vehicle model, the production date, the stop production date, the TBOX serial number, the ECU information, the last update status of the ECU, the last upgrade time of the ECU, and the upgrade package (full package, differential package). If the corresponding is successful, the production line OTA server sends the upgrade package version information to the corresponding vehicle TBOX through the cellular network.

[0142] Step 13:

[0143] The OBD wireless switching device transmits and receives test task messages. After the OBD wireless switching device receives the task assigned by the edge device in step 11 through WIFI communication in step 3, the test case task (CAN, UDS) messages belonging to the vehicle end test task are connected to each ECU of the automobile through the CAN bus protocol by the 6th and 14th pins of the OBD wireless switching device through the CAN signal of each ECU module in step 7.

[0144] The function of the CAN signal is that after the ECU receives a certain instruction, it will convert the instruction into a CAN bus signal, and then transmit it through the CAN bus. The CAN bus transmits the signal to a specific sensor.

[0145] Step 14:

[0146] The real vehicle executes the OTA test task. The real vehicle establishes a communication connection with the production line OTA server in the factory mode in step 3. The production line OTA server sends the OTA upgrade package version information to the measured real vehicle TBOX in step 12. The vehicle end starts the update process in the factory mode:

[0147] The production line OTA server sends the OTA upgrade message to the TBOX. The OTA test server receives the log of the test message transmission and reception of the production line OTA server and the OBD wireless switching device, generates a message record, and uploads it to the OTA test server to feedback to the test task interface of the OTA test platform software. It should be noted that this feedback is to record each step of the OTA execution process. The OTA test (API, CAN, UDS) case task is also included in each step, so the OBD wireless switching device and the production line OTA server need to feedback the message log to the edge device to the OTA test platform software.

[0148] The TBOX sends an upgrade consent message to the production line OTA server, the OTA test server receives logs of test message transmission of the production line OTA server and the OBD wireless switching device, generates a message record uploaded to the OTA test server through the edge device and fed back to the test task interface of the OTA test platform software;

[0149] The production line OTA server sends updated ECU information to the TBOX, the OTA test server receives logs of test message transmission of the production line OTA server and the OBD wireless switching device, generates a message record uploaded to the OTA test server through the edge device and fed back to the test task interface of the OTA test platform software;

[0150] The real vehicle TBOX recognizes and confirms the ECU information and the internal storage space check result, the OTA test server receives logs of test message transmission of the OBD wireless switching device, generates a message record uploaded to the OTA test server through the edge device and fed back to the test task interface of the OTA test platform software;

[0151] The ECU returns the current version information and the internal storage space to the TBOX, the OTA test server receives logs of test message transmission of the OBD wireless switching device, generates a message record uploaded to the OTA test server through the edge device and fed back to the test task interface of the OTA test platform software;

[0152] The TBOX returns the current version information of the ECU to the production line OTA server, the OTA test server receives logs of test message transmission of the production line OTA server and the OBD wireless switching device, generates a message record uploaded to the OTA test server through the edge device and fed back to the test task interface of the OTA test platform software;

[0153] The production line OTA server performs version information verification, the OTA test server receives logs of test message transmission of the production line OTA server, generates a message record uploaded to the OTA test server through the edge device and fed back to the test task interface of the OTA test platform software;

[0154] The production line OTA server sends an upgrade package (full package or differential package) to the tested real vehicle TBOX, the OTA test server receives logs of test message transmission of the production line OTA server and the OBD wireless switching device, generates a message record uploaded to the OTA test server through the edge device and fed back to the test task interface of the OTA test platform software;

[0155] The TBOX receives the upgrade package sent by the production line OTA server, and in the downloading process, the test script configured in step 6 is executed step by step to perform fault injection: TBOX short-time network interruption and long-time network interruption, and low battery power script, to test the OTA download strategy and the breakpoint continuation capability in the update downloading process. The OTA test server receives the log of the test message transmission of the OBD wireless switching device, generates a message record, uploads it to the OTA test server through the edge device, and feeds back to the test task interface of the OTA test platform software.

[0156] The OTA Manager in the TBOX performs integrity verification and decryption signature on the upgrade package. The OTA test server receives the log of the test message transmission of the OBD wireless switching device, generates a message record, uploads it to the OTA test server through the edge device, and feeds back to the test task interface of the OTA test platform software.

[0157] The OTA Manager in the TBOX performs reconstruction on the upgrade package and guides it to be downloaded to each ECU through the CGW by the Boot Loader for parallel upgrade, and the spare Flash of the ECU performs mirror making of the upgrade package. The OTA test server receives the log of the test message transmission of the OBD wireless switching device, generates a message record, uploads it to the OTA test server through the edge device, and feeds back to the test task interface of the OTA test platform software.

[0158] During the upgrade process, the test script configured in step 6 is executed step by step to perform fault injection: functional interaction test (power mode switching test, four-door two-cover opening and closing interaction test, anti-theft alarm state switching interaction test, power mode switching interaction test, and drive unit switching interaction test) and abnormal working condition test (OTA master power supply abnormality, OTA upgraded ECU power supply abnormality, battery power abnormality, vehicle speed abnormality, engine speed abnormality, voltage abnormality, remaining power abnormality, parking brake switching, gear shifting, starting system running state switching, charging state switching, motor running state switching). The above test contents are downloaded to the vehicle in the form of scripts to cause interference signals to test the OTA upgrade strategy.

[0159] After the above process is completed, the TBOX and the ECU perform consistency check on the upgrade information. If the check is passed, the upgrade process is completed, and the log is generated and sent to the production line OTA server by the TBOX. If the check is not passed, the mirror file made in the spare Flash of the ECU is rolled back to the previous version, and the log is generated and sent to the production line OTA server by the TBOX. The OTA test server receives the logs of the test message transmission of the production line OTA server and the OBD wireless switching device, generates a message record, uploads it to the OTA test server through the edge device, and feeds back to the test task interface of the OTA test platform software.

[0160] Step 15:

[0161] The test report module of the OTA test platform software generates an OTA test report. The test report is generated by comparing the API response of the OTA cloud platform and the CAN and UDS response message logs of the vehicle side obtained after the above steps 1 to 14 are completed, the expected response results of each precondition and step included in the test case are set in the OTA test platform software, and it is judged whether they are consistent. If consistent, it is judged as passed, otherwise, it is not passed. The results are summarized to generate a test report. In the OTA test platform software, task reports (use case test pass rate, use case test result statistics, task information), defect reports (defect module, defect state, defect quantity, defect level, defect priority, defect handler) charts and reports can be selected and viewed, and the reports can be downloaded to the local.

[0162] Step 16:

[0163] Check the test defects. After the above steps 1 to 15 are completed, the test task can be created in the OTA test platform software, and the test defects with the result of not passing in the test task can be created. The name, priority, level, creator, handler, state, creation time of the test defect can be filled according to the selected test task, and the processing state and message notes of a single test defect can be modified, which is used for tracking and collaborative processing of defects.

[0164] Step 17

[0165] Test board defect adjustment. After the above steps 1 to 14 are completed, the test task can be selected to view the test board in the OTA test platform software. In the test board, my test defects and recently updated test defects can be viewed. There are six states of test defects, which are: pending defects, defects under repair, defects under test, closed defects, rejected defects, and delayed processing defects.

[0166] The test defects are displayed in the form of cards in the six states of the swim lane. Different defects correspond to different modification state rules. The pending defect swim lane card can be moved to the defect under repair swim lane. The defect under repair swim lane card can be moved to the defect under test swim lane. The defect under test swim lane card can be moved to the closed defect, rejected defect, and delayed processing defect swim lane. The closed defect, rejected defect, and delayed processing defect swim lane card can be moved to the pending defect.

[0167] In order to help understand the technology of the present application, Table 1: Glossary is provided.

[0168] Table 1: Glossary

[0169]

[0170]

[0171] The application discloses a kind of methods and systems for whole vehicle in line environment carries out OTA automatic test.The principle is: user pre-configures edge device and OBD wireless switching device, and check the OTA test platform software deployed on OTA test server and the line OTA cloud platform deployed on line OTA server between normal communication, test case (including API interface instruction, CAN script and UDS diagnostic message) is issued to edge device in OTA test platform software, and edge device is distributed to test case Data, test API interface instruction case distribution is given to line OTA cloud platform, test CAN script and UDS diagnostic message case is issued to OBD wireless switching device, OBD wireless switching device is connected with the OBD interface of measured vehicle, executes OTA test procedure, and test result is returned to OTA test platform software from line OTA cloud platform server and OBD wireless switching device with data through edge device, and test result is viewed and analyzed in test board, test defect, test report module, to realize whole vehicle in line environment OTA upgrade test.

[0172] The application can realize whole vehicle in line environment carries out OTA automatic test, compared with traditional technical scheme has the advantages of convenient, fast, efficient, that is, guarantee the stability and safety of OTA function, while also effectively saving manpower and material resources, fill the whole vehicle in line environment OTA automatic test technology blank.

Claims

1. A system for performing OTA automated testing on a vehicle in a production line environment, characterized in that: The system includes: a client, an edge device, an OBD wireless adapter, an OTA test server, and a production line OTA server; The client is used to access the OTA test platform software on the OTA test server and view the test report; The OTA test server is used to create a test vehicle model, parse the DBC file of the test vehicle model, edit the test task according to the DBC file, and send the test task to the edge device through the OTA test server. It is also used to generate a test report based on the test results fed back by the test vehicle and the test results of the production line OTA server, and send the test report to the client. The edge device is used to schedule the test task, specifically including: Sending the test task for the production line OTA server to the production line OTA server; sending the test task for testing the vehicle end to the OBD wireless switching device; The production line OTA server is used to send the upgrade information of the test case in the test task for the production line OTA server to the test vehicle; it is also used to send the test result of the production line OTA server to the edge device, and the edge device then sends the test result of the production line OTA server to the OTA test server; The OBD wireless switching device is used to send the test task for the test vehicle side to the test vehicle; it is also used to receive the test results fed back by the test vehicle and send the test results fed back by the test vehicle to the edge device, and the edge device then sends the test results fed back by the test vehicle to the OTA test server.

2. The OTA automated testing system for a vehicle in a production line environment according to claim 1, characterized in that: The editing of the test task according to the DBC file specifically includes: configuring a test script for the test production line OTA server, a test script for the test vehicle side, and a CAN signal according to the DBC file; Edit test cases based on the test scripts of the test production line OTA server, the test scripts of the test vehicle, and the CAN signals; Edit the test task according to the test case.

3. The OTA automated testing system for a vehicle in a production line environment according to claim 2, characterized in that: The test cases include API interface instructions, CAN scripts and UDS diagnostic messages.

4. The OTA automated testing system for a vehicle in a production line environment according to claim 1, characterized in that: The test tasks for the production line OTA server include API interface instructions, and the test tasks for testing the vehicle side include CAN scripts and UDS diagnostic messages.

5. The OTA automated testing system for a vehicle in a production line environment according to claim 2, characterized in that: The test scripts for the production line OTA server include server load testing, fault injection testing, server stress testing, and server network security testing; The test script of the test vehicle side includes tests on the upgrade strategy mechanism, security and anti-theft mechanism, parallel upgrade mechanism, and upgrade guarantee mechanism.

6. A method for performing OTA automated testing on a complete vehicle in a production line environment, characterized in that: The method comprises: Step 1: Configure edge devices, which have the functions of data communication, local computing and AI inference, and cloud configuration synchronization; Step 2: Configure an OBD wireless adapter, which can realize the communication function between the measurement vehicle and the edge device; Step 3: Use the OTA test platform software on the OTA test server to create a test vehicle model, parse the DBC file of the test vehicle model, and edit the test tasks according to the DBC file. The test tasks include test tasks for the production line OTA server and test tasks for the test vehicle side; Step 4: The OTA test server sends the test task to the edge device; Step 5: The edge device schedules the test task, specifically including: Sending the test task for the production line OTA server to the production line OTA server; sending the test task for testing the vehicle end to the OBD wireless switching device; Step 6: The production line OTA server sends the upgrade information in the test task for the production line OTA server to the test vehicle; The OBD wireless switching device sends the test task for the test vehicle to the test vehicle; Step 7: The test vehicle performs OTA testing based on the upgrade information and the test task for the test vehicle, and obtains the test results of the production line OTA server and the test results fed back by the vehicle; Step 8: The production line OTA server sends the test result of the production line OTA server to the edge device; The test vehicle sends the test result fed back by the vehicle to the OBD wireless switching device, and the OBD wireless switching device then sends the test result fed back by the vehicle to the edge device; Step 9. The edge device sends the test results of the production line OTA server and the test results fed back by the vehicle to the OTA test server. The OTA test server generates a test report based on the test results of the production line OTA server and the test results fed back by the vehicle, and sends the test report to the client.

7. The method for performing OTA automated testing on a vehicle in a production line environment according to claim 6, characterized in that: The editing of the test task according to the DBC file specifically includes: configuring a test script for the test production line OTA server, a test script for the test vehicle side, and a CAN signal according to the DBC file; Edit test cases based on the test scripts of the test production line OTA server, the test scripts of the test vehicle, and the CAN signals; Edit the test task according to the test case.

8. The method for performing OTA automated testing on a vehicle in a production line environment according to claim 7, characterized in that: The test cases include API interface instructions, CAN scripts and UDS diagnostic messages.

9. The method for performing OTA automated testing on a vehicle in a production line environment according to claim 6, characterized in that: The test tasks for the production line OTA server include API interface instructions, and the test tasks for testing the vehicle side include CAN scripts and UDS diagnostic messages.

10. The method for performing OTA automated testing on a vehicle in a production line environment according to claim 7, characterized in that: The test scripts for the production line OTA server include server load testing, fault injection testing, server stress testing, and server network security testing; The test script of the test vehicle side includes tests on the upgrade strategy mechanism, security and anti-theft mechanism, parallel upgrade mechanism, and upgrade guarantee mechanism.

Images