System and method for verifying whole vehicle OTA upgrade result by using ADB instruction in preparation environment

Abstract

The application relates to a system and method for verifying whole vehicle OTA upgrading results by using ADB instructions in a preparation environment, which comprises an edge box, an OBD switching device and an OTA test platform. In the preparation environment, the whole vehicle is opened to ADB authority, and data can be obtained by executing ADB instructions. A test ADB script is edited on the OTA test platform, the ADB script is sent to the OBD switching device, test script data is transmitted to the whole vehicle CGW by using the OBD switching device to connect a vehicle end OBD interface, the CWG gateway log is obtained from the whole vehicle CGW, the log content is read, the whole vehicle data stream information is known, and the whole vehicle OTA automatic upgrading result is verified. The application can quickly obtain the whole vehicle OTA automatic upgrading result in the preparation environment by using the OBD switching device. The application does not need secondary data processing operation, can enable users to more quickly, efficiently and intuitively see the upgrading result, saves manpower and material resources, and improves the efficiency of correcting the whole vehicle data stream information before the automobile is put into operation.

Description

Technical Field

[0001] This invention belongs to the field of vehicle OTA testing technology, and relates to a system and method for verifying vehicle OTA upgrade results using ADB commands in a vehicle preparation environment. Background Technology

[0002] With the automotive industry moving towards intelligentization in recent years, the integration of automobiles and the internet has become a mainstream trend, and OTA (Over-The-Air) technology is being widely adopted by major automakers. Given the increasingly complex structure and control algorithms of vehicle ECUs, the proper use of OTA technology, under proper maintenance conditions, allows for efficient monitoring of vehicle ECU data, ensuring that the ECU version information is standardized and consistent when the vehicle leaves the factory.

[0003] The vehicle's ECU can monitor various data information of the entire vehicle in real time. In the preparation environment, this invention establishes communication with the vehicle's CGW (Control Gateway) using an OBD adapter to obtain the vehicle's CGW gateway logs, ensuring the accuracy and consistency of the data stream before the vehicle leaves the factory, thereby achieving efficient automobile production.

[0004] The existing implementation involves pre-configuring communication parameters such as pins, communication methods, and baud rates in the diagnostic system's data stream configuration table, which serve as data stream identification commands. These pre-configured data stream identification commands are then sent line by line to the vehicle's ECU, and the vehicle's data stream is read based on the feedback from the ECU.

[0005] The shortcomings and problems of existing technologies:

[0006] 1. Data stream identification instructions need to be prepared in advance, and the data preparation phase takes a long time;

[0007] 2. It requires each vehicle ECU to run and identify the commands and provide feedback, which is difficult to control and takes a long time;

[0008] Patent document CN112068531A discloses a method for reading vehicle data streams, including: responding to a user-inputted data stream reading command, filtering out general data stream instructions and address-type data stream instructions matching the ECU version information corresponding to the current diagnostic system from the data stream configuration table; data stream pre-reading: sending each filtered data stream instruction to the ECU, and hiding data stream instructions that the ECU does not respond to or does not respond negatively; responding to a user-inputted data stream category, sending the filtered data stream instructions that correspond to the data stream category and are not hidden to the ECU; matching the data stream returned by the ECU with the corresponding reasonable value range, and filtering out the data streams that meet the corresponding reasonable value range for display. This invention ensures that the data stream finally displayed to the user is a data stream that is responded to by the ECU and has reasonable values, avoiding interference with the user's repair judgment.

[0009] The process of obtaining upgrade result data in this invention does not require pre-setting data flow instructions, which significantly improves timeliness.

[0010] Patent document CN112991578A applies to the field of vehicle diagnostic technology, providing a method, apparatus, electronic device, and electronic control unit for processing vehicle data streams. The method includes: establishing a communication connection with the vehicle's electronic control unit (ECU); sending a data stream acquisition command to the ECU; the data stream acquisition command including a data stream identifier; receiving response data from the ECU based on the data stream acquisition command; the response data including target data stream information and target reference information corresponding to the data stream identifier; parsing the target data stream information and target reference information to obtain a target data stream value and a target reference value; comparing the target data stream value and the target reference value to obtain a comparison result; and displaying the comparison result. By receiving the target data stream value and target reference value returned by the vehicle's electronic control unit, a comparison result indicating whether the current target data stream value is normal is obtained, shortening the detection time and improving the efficiency of vehicle diagnostics.

[0011] This invention does not require the addition of a complex physical device. It only requires the built-in Ethernet module in the OBD adapter to use ADB commands to compare whether the target data stream is normal, making it easier to control costs.

[0012] Patent document CN106993056A discloses a method, system, and computer-readable storage medium for acquiring automotive data streams. The method includes: receiving a data stream selection instruction and packaging the instruction into a first data packet; sending the first data packet to a lower-level machine, which then parses the packet and sends it to the vehicle's OBD interface, and obtains response data corresponding to the data stream selection instruction returned by the OBD interface; receiving a second data packet generated by the lower-level machine from the response data, and parsing the second data packet to obtain the data stream corresponding to the data stream selection instruction. This solution packages multiple data stream selection instructions and sends them to the lower-level machine, allowing the lower-level machine to parse them and interact with the vehicle's OBD interface to obtain the response data returned by the OBD interface. The response data is then processed to obtain the data stream corresponding to the data stream selection instruction, thus avoiding the need to send and display multiple data streams sequentially, and accelerating the data stream refresh rate.

[0013] This invention does not require data compression and sorting to improve data stream flushing speed. By properly configuring test ADB commands on the OTA test platform, the required data stream information can be quickly and accurately located directly. Summary of the Invention

[0014] The purpose of this invention is to provide a system and method for verifying the results of vehicle OTA upgrades using ADB commands in a preparation environment, addressing the obstacles and problems existing in the prior art. This system enables users to operate a test platform, issue test script ADB commands to an OBD adapter, use the OBD adapter to connect to the vehicle's OBD interface to transmit test script data to the vehicle's CGW, obtain CWG gateway logs from the vehicle's CGW, read the log content to obtain vehicle data flow information, and thus verify the results of the vehicle's OTA automated upgrade.

[0015] It should be noted that, in this document, relational terms such as "first" and "second" are used only to distinguish one entity or operation from another, and do not necessarily require or imply any such actual relationship or order between these entities or operations. Furthermore, the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such process, method, article, or apparatus.

[0016] To solve the above-mentioned technical problems, the present invention is implemented using the following technical solution:

[0017] A system for verifying the results of vehicle OTA upgrades using ADB commands in a preparation environment includes an edge box, an OBD adapter, and an OTA test platform;

[0018] The edge box processes test ADB command data and sends and receives data to the OTA test platform and OBD adapter through the SDK service;

[0019] The OBD adapter device achieves communication with the vehicle's CGW by adding an Ethernet module;

[0020] The OBD adapter sends ADB commands to be executed within the vehicle's CGW, and can obtain the execution results;

[0021] Compile and issue ADB script commands on the OTA testing platform;

[0022] The OTA testing platform sends test task information to the edge box via Ethernet DOIP protocol communication.

[0023] Furthermore, the OBD adapter has a built-in Ethernet module, which establishes a communication link between the OBD adapter and the vehicle's CGW, enabling the OBD adapter to send ADB commands to the vehicle's CGW via the OBD pin connection to the vehicle's OBD interface.

[0024] Furthermore, the vehicle CGW returns upgrade result data to the OBD adapter via the OBD interface.

[0025] Furthermore, after receiving the instruction information, the vehicle CGW executes the ADB instruction to obtain the vehicle CGW gateway log data; the obtained gateway log contains historical vehicle ECU version upgrade information, and the test script contains the standard version ECU version information after OTA automated upgrade and comparison instructions.

[0026] A method for verifying the results of a vehicle OTA upgrade using ADB commands in a preparation environment includes:

[0027] Data preparation phase: The OTA testing platform is configured with ADB script command information to generate test cases, and then generates test tasks that need to be sent to the vehicle.

[0028] Data transmission phase: The edge box distributes ADB script commands to the OBD adapter device through the SDK service; the OBD adapter device receives the ADB script commands through WIFI communication and sends the ADB script commands to the vehicle CGW through the direct connection to the vehicle's OBD interface;

[0029] Obtaining Log Information: After obtaining the test information, the vehicle CGW executes ADB script commands one by one to obtain the vehicle CGW gateway log information. This information is then compared with the returned gateway log information to verify the results of the vehicle OTA automated upgrade.

[0030] A method for verifying the results of a vehicle OTA upgrade using ADB commands in a preparation environment, specifically including the following steps:

[0031] Step 1: Configure the edge box. The edge box provides SDK services to handle sending and receiving ADB script commands.

[0032] Step 2: Configure the OBD adapter. The OBD adapter has a built-in Ethernet module. Through the built-in Ethernet module, a communication link between the OBD adapter and the vehicle's CGW can be established, enabling the OBD adapter to send ADB script commands to the vehicle's CGW through the OBD pin connection to the vehicle's OBD interface.

[0033] Step 3: After completing the configuration in Steps 1 and 2, ensure that the edge box and the OBD adapter are connected and paired on the same local area network so that they can send and receive data normally.

[0034] Step 4: Compile ADB script instructions on the OTA testing platform, combine and store the compiled ADB script instructions as test tasks, and issue the test tasks.

[0035] Step 5: After the test task is issued in Step 4, the edge box obtains the instruction information and sends the ADB script instruction information to the OBD adapter through the communication connection established in Step 3 using the SDK service.

[0036] Step 6: The OBD adapter receives the instruction information transmitted in Step 6, connects directly to the vehicle through the OBD port, and sends ADB instruction information to the vehicle's CGW;

[0037] Step 7: After receiving the instruction information in Step 6, the vehicle CGW executes the ADB instruction to obtain the vehicle CGW gateway log data. The obtained gateway log contains historical vehicle ECU version upgrade information. The test script contains the standard version ECU version information after OTA automated upgrade and the comparison instruction. Execute the comparison instruction to compare whether the vehicle ECU version upgrade information and the standard version ECU version information in the gateway log are consistent. If they are consistent, the upgrade result is successful; if they are inconsistent, the upgrade result is unsuccessful.

[0038] Furthermore, before obtaining the upgrade results, it is necessary to connect the OBD converter to the vehicle through the OBD interface and establish communication with the vehicle; by connecting the OBD pin of the OBD converter to the OBD interface and then to the vehicle, it is possible to directly connect to the vehicle's CGW to issue ADB commands.

[0039] A method for verifying the results of a vehicle OTA upgrade using ADB commands in a preparation environment, further includes step 8:

[0040] After step 7 is completed, the upgrade result is obtained. The vehicle CGW returns the upgrade result data to the OBD adapter via the OBD interface.

[0041] A method for verifying the results of a vehicle OTA upgrade using ADB commands in a preparation environment, further includes step 9:

[0042] The upgrade results received by the OBD adapter in step 8 are fed back to the edge box via the communication link established in step 3.

[0043] A method for verifying the results of a vehicle OTA upgrade using ADB commands in a preparation environment, further includes step 10:

[0044] The edge box receives the data processed in step 9 and uses the SDK service to transmit the upgrade results to the OTA test platform. Users can view the OTA automated upgrade results of the whole vehicle on the OTA test platform.

[0045] Compared with the prior art, the beneficial effects of the present invention are:

[0046] This invention enables rapid verification of OTA (Over-The-Air) upgrade results for the entire vehicle in a pre-installed environment via an OBD adapter. Traditional methods involve pre-programming vehicle data stream identification commands through a diagnostic system, comparing these commands line by line, and reading the vehicle data stream based on feedback from the vehicle's ECU. In contrast, this invention eliminates the need for secondary data processing, allowing users to see upgrade results more quickly, efficiently, and intuitively, saving manpower and resources, and improving the efficiency of verifying vehicle data stream information before vehicle deployment. Attached Figure Description

[0047] The invention will now be further described with reference to the accompanying drawings:

[0048] Figure 1 The present invention provides a system workflow diagram for verifying the OTA upgrade results of a vehicle using ADB commands in a preparation environment.

[0049] Figure 2 The flowchart of the method for verifying the OTA upgrade results of a vehicle using ADB commands in a preparation environment as described in this invention;

[0050] Figure 3 This is a schematic diagram of the pinout for an OBD adapter.

[0051] Figure 4 This is a schematic diagram of an OBD adapter. Detailed Implementation

[0052] To make the objectives, technical solutions, and advantages of this invention clearer, the technical solutions of the embodiments of this invention will be described in more detail below with reference to the accompanying drawings. In the drawings, the same or similar reference numerals denote the same or similar elements or elements having the same or similar functions throughout. The described embodiments are some, but not all, embodiments of this invention. The embodiments described below with reference to the accompanying drawings are exemplary and intended to explain this invention, and should not be construed as limiting the invention. All other embodiments obtained by those skilled in the art based on the embodiments of this invention without creative effort are within the scope of protection of this invention. The embodiments of this invention will be described in detail below with reference to the accompanying drawings.

[0053] In the description of this invention, it should be understood that the terms "center", "longitudinal", "lateral", "front", "rear", "left", "right", "vertical", "horizontal", "top", "bottom", "inner", "outer", etc., indicate the orientation or positional relationship based on the orientation or positional relationship shown in the accompanying drawings. They are only for the convenience of describing this invention and simplifying the description, and do not indicate or imply that the device or element referred to must have a specific orientation, or be constructed and operated in a specific orientation. Therefore, they should not be construed as limiting the scope of protection of this invention.

[0054] The present invention will now be described in detail with reference to the accompanying drawings:

[0055] The invention discloses a vehicle OTA upgrade verification system using ADB commands, comprising an OTA testing platform, an edge box, an OBD adapter, and a complete vehicle. The vehicle component should include an OBD interface and a CGW (Continuous Vehicle Gateway). Figure 1 As shown.

[0056] Under the prepared condition, the vehicle has ADB permissions enabled, and data can be obtained by executing ADB commands;

[0057] When the vehicle is in the preparation environment, ADB permissions are enabled. After the vehicle leaves the factory, ADB permissions will be disabled.

[0058] Given that the vehicle is in a maintenance environment, after logging into the OTA test platform, users can edit the script command to retrieve upgrade logs and issue ADB script commands (command format: adb [-d|-e|-s<device number>]). <command> The system retrieves the vehicle's CWG gateway logs from the vehicle's CGW and compares the log information to obtain the vehicle's OTA automated upgrade results.

[0059] Data preparation phase: Configure script information on the OTA testing platform, generate test cases, and then generate test tasks that need to be distributed to the entire vehicle;

[0060] Data transmission phase: The edge box sends and receives ADB script commands and, through the SDK service, assigns test tasks to the OBD adapter. The OBD adapter receives the test tasks via Wi-Fi communication and sends the test information to the vehicle CGW through the vehicle's OBD interface.

[0061] The OBD adapter enables communication with the vehicle's CGW by adding an Ethernet module.

[0062] OBD adapters can issue ADB commands to be executed within the vehicle's CGW and can obtain the execution results;

[0063] Obtaining Log Information: After obtaining the test information, the vehicle's Control Gateway (CGW) executes the ADB commands of the test script one by one to obtain the CGW gateway log information. By combining the test script with the returned gateway log information, the vehicle's OTA automated upgrade result is determined. The upgrade result can be sent back to the OTA test platform via the command path.

[0064] The edge box processes test ADB command data and sends and receives data to the OTA test platform and OBD adapter through the SDK service;

[0065] The OBD adapter enables communication with the vehicle's CGW by adding an Ethernet module;

[0066] The OBD adapter sends ADB commands to be executed within the vehicle's CGW, and can obtain the execution results;

[0067] Compile and issue ADB script commands on the OTA testing platform;

[0068] The OTA testing platform sends test task information to the edge box via Ethernet DOIP protocol communication.

[0069] The OTA testing platform is an existing technology, an automated testing system involved in patent document CN115373981A.

[0070] The OBD adapter has a built-in Ethernet module, which establishes a communication link between the OBD adapter and the vehicle's CGW, enabling the OBD adapter to send ADB commands to the vehicle's CGW via the OBD pin connection to the vehicle's OBD interface.

[0071] The vehicle's CGW returns upgrade result data to the OBD adapter via the OBD interface.

[0072] After receiving the instruction information, the vehicle CGW executes the ADB instruction to obtain the vehicle CGW gateway log data; the obtained gateway log contains historical vehicle ECU version upgrade information, and the test script contains the standard version ECU version information after OTA automated upgrade and comparison instructions.

[0073] A method for verifying the results of vehicle OTA upgrades using ADB commands in a preparation environment; see the detailed implementation method below. Figure 2 It is divided into the following ten steps:

[0074] Step 1:

[0075] Configure the edge box, which provides SDK services to handle sending and receiving test task information. Properly utilizing the edge box can effectively reduce data latency and ensure timely data transmission.

[0076] Edge box description:

[0077] The edge box is designed using an 8th Gen. Intel Core i7-8665UE / i5-8365UE Quad Core processor, offering advantages such as high efficiency, high performance, and rich interfaces. Internally, it integrates CAN, USB, Ethernet, 4G, WiFi, HDMI, and audio interfaces and modules. It supports Linux systems, and the hard drive can be expanded to 2TB.

[0078] The hardware parameters of the edge box are shown in Table 1:

[0079] Table 1

[0080]

[0081]

[0082]

[0083] Step 2:

[0084] Configure an OBD adapter device with a built-in Ethernet module. This module establishes a communication link between the OBD adapter and the vehicle's CGW, allowing the OBD adapter to send ADB commands to the CGW via its OBD pin connection to the vehicle's OBD interface. The OBD adapter also includes a built-in encryption chip to prevent ARM processors from being cracked.

[0085] The software within the chip is existing technology.

[0086] OBD adapter module specifications are shown in Table 2:

[0087] Table 2

[0088] 1 OBD module Used for connecting to the OBD port on the vehicle side for power supply and data communication. 2 ARM Development based on embedded Linux system 3 Encryption chip Used to prevent ARM from being cracked. 4 Voltage regulator circuit Protect equipment load 5 Ethernet module Supports ADB command execution 6 WIFI module Used for communication with edge devices, with uplink and downlink speeds >10MB / s, and a standard ≥WIFI5.

[0089] The hardware parameters of the OBD adapter are shown in Table 3:

[0090] Table 3

[0091]

[0092] OBD adapter pinout descriptions are as follows: Figure 3 As shown in Table 4;

[0093] Table 4

[0094]

[0095] OBD adapter information diagram as follows: Figure 4 As shown;

[0096] Step 3:

[0097] After completing steps 1 and 2, ensure that the edge box and OBD adapter are connected and paired on the same local area network to send and receive data normally. Before obtaining the upgrade results, the OBD adapter needs to be connected to the vehicle via the OBD interface to establish communication. Connecting the OBD adapter to the vehicle via the OBD pin of the OBD adapter allows direct connection to the vehicle's CGW to issue ADB commands.

[0098] Step 4:

[0099] On the OTA testing platform, ADB script commands are compiled and issued. The compiled ADB script commands are combined and stored as test tasks, and then the test tasks are issued.

[0100] Commands such as: vehicle model version collection and upgrade package generation strategies.

[0101] After logging into the OTA cloud platform and completing step 3, you can see that the OBD adapter has become online, indicating that the connection in step 3 has been successfully established.

[0102] Step 5:

[0103] By issuing the test task in step 4, the edge box receives the instruction information, and through the communication connection established in step 3, uses the SDK service to send...

[0104] Send ADB script instructions to the OBD adapter.

[0105] Step 6:

[0106] The OBD adapter receives the instruction information transmitted in step 5 and sends the ADB script instruction information to the vehicle CGW.

[0107] Step 7:

[0108] Step 6: After receiving the instruction information, the vehicle CGW executes the ADB script to obtain the vehicle CGW gateway log data. The obtained gateway log contains historical vehicle ECU version upgrade information. The test script contains the standard ECU version information after OTA automated upgrade and a comparison command. The comparison command is executed to compare whether the vehicle ECU version upgrade information and the standard ECU version information in the gateway log are consistent. If they are consistent, the upgrade result is successful; if they are inconsistent, the upgrade result is unsuccessful.

[0109] Compare the 'vehicle ECU version upgrade information in the gateway log' with the 'standard ECU version information' to see if they match. For example, if the gateway log records that ECU-A version has been upgraded from V1.0 to V2.0, and the data collected shows that the standard ECU-A version is V2.0, then the upgrade was successful.

[0110] Step 8:

[0111] After step 7 is completed, the upgrade result is obtained. The vehicle CGW returns the upgrade result data to the OBD adapter via the OBD interface.

[0112] Step 9:

[0113] The upgrade results received by the OBD adapter in step 8 are fed back to the edge box via the communication link established in step 3.

[0114] Step 10:

[0115] The edge box receives the data processed in step 9 and uses the SDK service to transmit the upgrade results to the OTA test platform. Users can view the vehicle's OTA automated upgrade results on the OTA test platform.

[0116] For a definition of the terms, see Table 5.

[0117] Table 5

[0118] OTA Over-the-air download technology OBD Onboard self-diagnostic system ADB Andxoid debug bridge CGW Central Gateway ECU Electronic control unit SDK Software Development Kit CAN Controller Area Network USB Universal Serial Bus WIFI Wireless network communication technology Web Global Wide Area Network HTTP Response Protocol HTML Hypertext Markup Language ARM processor API Application Programming Interface

[0119] The above description is merely a specific embodiment of the present invention, but the scope of protection of the present invention is not limited thereto. Any modifications, equivalent substitutions, and improvements made by those skilled in the art within the scope of the technology disclosed in the present invention, and within the spirit and principles of the present invention, should be included within the scope of protection of the present invention. Furthermore, all content not described in detail in this specification is prior art known to those skilled in the art.

Claims

1. A system for verifying vehicle OTA upgrade results using ADB commands in a preparation environment, characterized in that: This includes edge boxes, OBD adapters, and OTA testing platforms; The edge box processes test ADB command data and sends and receives data to the OTA test platform and OBD adapter through the SDK service; The OBD adapter device achieves communication with the vehicle's CGW by adding an Ethernet module; The OBD adapter sends ADB commands to be executed within the vehicle's CGW, and can obtain the execution results; Compile and issue ADB script commands on the OTA testing platform; The OTA testing platform sends test task information to the edge box via Ethernet DOIP protocol communication.

2. The system for verifying vehicle OTA upgrade results using ADB commands in a preparation environment according to claim 1, characterized in that: The OBD adapter has a built-in Ethernet module. Through the built-in Ethernet module, a communication link is established between the OBD adapter and the vehicle's CGW, enabling the OBD adapter to send ADB commands to the vehicle's CGW via the OBD pin connection to the vehicle's OBD interface.

3. The system for verifying vehicle OTA upgrade results using ADB commands in a preparation environment according to claim 2, characterized in that: The vehicle CGW returns upgrade result data to the OBD adapter via the OBD interface.

4. The system for verifying vehicle OTA upgrade results using ADB commands in a preparation environment according to claim 1, characterized in that: After receiving the instruction information, the vehicle CGW executes the ADB instruction to obtain the vehicle CGW gateway log data; the obtained gateway log contains historical vehicle ECU version upgrade information, and the test script contains the standard version ECU version information after OTA automated upgrade and comparison instructions.

5. A method for verifying the results of a vehicle OTA upgrade using ADB commands in a preparation environment, characterized in that, include: Data preparation phase: The OTA testing platform is configured with ADB script command information to generate test cases, and then generates test tasks that need to be sent to the vehicle. During the data transmission phase: The edge box distributes ADB script instructions to the OBD adapter via the SDK service; The OBD adapter receives ADB script commands via WIFI communication and sends ADB script commands to the vehicle's CGW via the direct connection to the vehicle's OBD interface. Obtaining Log Information: After obtaining the test information, the vehicle CGW executes ADB script commands one by one to obtain the vehicle CGW gateway log information. It then compares the log information with the returned gateway log information to verify the results of the vehicle OTA automated upgrade.

6. The method for verifying the OTA upgrade results of a vehicle using ADB commands in a preparation environment, as described in claim 5, is characterized in that... Specifically, the following steps are included: Step 1: Configure the edge box. The edge box provides SDK services to handle sending and receiving ADB script commands. Step 2: Configure the OBD adapter. The OBD adapter has a built-in Ethernet module. Through the built-in Ethernet module, a communication link between the OBD adapter and the vehicle's CGW can be established, enabling the OBD adapter to send ADB script commands to the vehicle's CGW through the OBD pin connection to the vehicle's OBD interface. Step 3: After completing the configuration in Steps 1 and 2, ensure that the edge box and the OBD adapter are connected and paired on the same local area network so that they can send and receive data normally. Step 4: Compile ADB script instructions on the OTA testing platform, combine and store the compiled ADB script instructions as test tasks, and issue the test tasks. Step 5: After the test task is issued in Step 4, the edge box obtains the instruction information and sends the ADB script instruction information to the OBD adapter through the communication connection established in Step 3 using the SDK service. Step 6: The OBD adapter receives the instruction information transmitted in Step 6, connects directly to the vehicle through the OBD port, and sends ADB instruction information to the vehicle's CGW; Step 7: After receiving the instruction information in Step 6, the vehicle CGW executes the ADB instruction to obtain the vehicle CGW gateway log data. The obtained gateway log contains historical vehicle ECU version upgrade information. The test script contains the standard version ECU version information after OTA automated upgrade and the comparison instruction. Execute the comparison instruction to compare whether the vehicle ECU version upgrade information and the standard version ECU version information in the gateway log are consistent. If they are consistent, the upgrade result is successful; if they are inconsistent, the upgrade result is unsuccessful.

7. The method for verifying the OTA upgrade results of a vehicle using ADB commands in a preparation environment, as described in claim 6, is characterized in that: Before obtaining the upgrade results, the OBD converter device needs to be connected to the vehicle through the OBD interface to establish communication with the vehicle. By connecting the OBD pin of the OBD converter device to the OBD interface and then connecting to the vehicle, it can directly connect to the vehicle's CGW to issue ADB commands.

8. The method for verifying the OTA upgrade results of a vehicle using ADB commands in a preparation environment according to claim 7, characterized in that, It also includes step 8: After step 7 is completed, the upgrade result is obtained. The vehicle CGW returns the upgrade result data to the OBD adapter via the OBD interface.

9. A method for verifying the results of a vehicle OTA upgrade using ADB commands in a preparation environment, as described in claim 8, is characterized in that... It also includes step 9: The upgrade results received by the OBD adapter in step 8 are fed back to the edge box via the communication link established in step 3.

10. A method for verifying the results of a vehicle OTA upgrade using ADB commands in a preparation environment, as described in claim 9, characterized in that, It also includes step 10: The edge box receives the data processed in step 9 and uses the SDK service to transmit the upgrade results to the OTA test platform. Users can view the OTA automated upgrade results of the whole vehicle on the OTA test platform.

Images