Automatic test method and system for communication between vehicle-mounted terminal and vehicle networking platform

Abstract

The invention provides an automatic test method and system for communication between a vehicle-mounted terminal and an Internet of Vehicles platform. The method comprises the following steps: (1) converting the content of a vehicle-mounted terminal message field input by a user into a hexadecimal original vehicle-mounted terminal message; (2) automatically executing a TCP (Transmission Control Protocol) connection establishment process between the Internet of Vehicles platform and the vehicle-mounted terminal, and sending the hexadecimal original vehicle-mounted terminal message to the Internet of Vehicles platform; (3) automatically logging in an Internet of Vehicles platform, and acquiring a message associated with the vehicle based on a vehicle unique identification code VIN of the vehicle; and (4) automatically executing two comparison processes: (a) comparing the obtained message with the hexadecimal original vehicle-mounted terminal message written in the step (1); (b) calling an analysis tool of the vehicle networking platform to analyze the obtained message, extracting field content in the analyzed message, and comparing the extracted field content with the field content of the vehicle-mounted terminal message input by the user.

Description

Technical Field

[0001] The present invention relates to testing the communication between an in-vehicle terminal and a vehicle networking platform. More specifically, the present invention relates to an automatic testing method and system for the communication between an in-vehicle terminal and a vehicle networking platform. Background Art

[0002] With the development of vehicle networking technology, the stability and reliability of the communication between an in-vehicle terminal (or referred to as a car machine terminal, a vehicle center console system, etc.) and a vehicle networking platform deserve attention. During development, testers need to test the accuracy of the communication between an in-vehicle terminal and a vehicle networking platform. Generally speaking, this accuracy test mainly involves testing whether the in-vehicle terminal and the vehicle networking platform can correctly parse the messages sent by each other.

[0003] For example, generally speaking, the main methods for testing the software module of the communication protocol (China National Standard GB / T 32960.1 - 2016) of the current in-vehicle terminal (such as a T-BOX or a smart antenna) may include: (1) simulating the in-vehicle terminal to write a message; converting the message into a hexadecimal message and sending the hexadecimal message to the vehicle networking platform; (2) logging in to the vehicle networking platform to check whether the hexadecimal message received by the vehicle networking platform is consistent with the hexadecimal message converted in process (1); using the parsing tool of the vehicle networking platform to parse the received hexadecimal message; and verifying whether the fields and field values derived from the parsed hexadecimal conversion message are consistent with the fields and field values written by the tester in process (1).

[0004] However, the above processes (1) and (2) generally adopt manual methods, which involve many calculation items, a cumbersome calculation process, are prone to errors, and have low test efficiency. In addition, when there are many similar fields, it is easy to overlook inspections, resulting in the omission of software defects. Summary of the Invention

[0005] The Summary of the Invention is provided to introduce in a simplified form some concepts that will be further described in the following Detailed Description. The Summary of the Invention is not intended to identify the key features or essential features of the claimed subject matter, nor is it intended to be used to help determine the scope of the claimed subject matter.

[0006] According to an embodiment of the present invention, a method for automatically testing the communication between a vehicle-mounted terminal and a vehicle networking platform is provided, including: (1) converting the content of the vehicle-mounted terminal message field input by the user into a hexadecimal original vehicle-mounted terminal message, where the hexadecimal original vehicle-mounted terminal message is associated with a vehicle; (2) automatically executing the TCP connection establishment process between the vehicle networking platform and the vehicle-mounted terminal, and sending the hexadecimal original vehicle-mounted terminal message to the vehicle networking platform via the TCP connection; (3) automatically logging in to the vehicle networking platform, and obtaining the message associated with the vehicle based on the vehicle identification number VIN of the vehicle; and (4) automatically performing two comparison processes: (a) comparing the obtained message with the hexadecimal original vehicle-mounted terminal message compiled in step (1) to determine whether they are consistent; (b) invoking the parsing tool of the vehicle networking platform to parse the obtained message, extracting the field content in the parsed message, and comparing the extracted field content with the content of the vehicle-mounted terminal message field input by the user to determine whether they are consistent.

[0007] According to another embodiment of the present invention, a system for automatically testing the communication between a vehicle-mounted terminal and a vehicle networking platform is provided, including: an original message compilation module configured to convert the content of the vehicle-mounted terminal message field input by the user into a hexadecimal original vehicle-mounted terminal message, where the hexadecimal original vehicle-mounted terminal message is associated with a vehicle; a communication module configured to execute the TCP connection establishment process between the vehicle networking platform and the vehicle-mounted terminal, and send the hexadecimal original vehicle-mounted terminal message to the vehicle networking platform via the TCP connection; a sent message acquisition module configured to log in to the vehicle networking platform and obtain the message associated with the vehicle based on the vehicle identification number VIN of the vehicle; and a message comparison module configured to perform two comparison processes: (a) comparing the obtained message with the hexadecimal original vehicle-mounted terminal message compiled by the original message compilation module to determine whether they are consistent; (b) invoking the parsing tool of the vehicle networking platform to parse the obtained message, extracting the field content in the parsed message, and comparing the extracted field content with the content of the vehicle-mounted terminal message field input by the user to determine whether they are consistent.

[0008] These and other features and advantages will become apparent by reading the following detailed description and referring to the associated drawings. It should be understood that the foregoing general description and the following detailed description are illustrative only and do not limit the various aspects claimed. Brief Description of the Drawings

[0009] To understand the manner in which the above-described features of the present invention can be used in detail, the above briefly summarized content can be described more specifically with reference to the various embodiments, some aspects of which are shown in the accompanying drawings. It should be noted, however, that the drawings only show some typical aspects of the present invention and should not be considered as limiting its scope, as the description may allow other equally effective aspects.

[0010] Figure 1 FIG. 4 shows a block diagram of a system 100 for automatically testing communication between an in-vehicle terminal and a vehicle networking platform according to an embodiment of the present invention;

[0011] Figure 2 FIG. 8 shows a flowchart of a method 200 for automatically testing communication between an in-vehicle terminal and a vehicle networking platform according to an embodiment of the present invention; and

[0012] Figure 3 FIG. 12 shows a block diagram of an exemplary computing device according to an embodiment of the present invention. DETAILED DESCRIPTION OF THE INVENTION

[0013] The present invention will be described in detail below with reference to the accompanying drawings, and the features of the present invention will be further manifested in the following detailed description.

[0014] The following detailed description refers to the accompanying drawings showing exemplary embodiments of the present invention. However, the scope of the present invention is not limited to these embodiments, but is defined by the appended claims. Thus, embodiments other than those shown in the drawings, such as modified versions of the shown embodiments, are still encompassed by the present invention.

[0015] References in this specification to "an embodiment", "embodiment", "exemplary embodiment", etc. mean that the embodiment may include a particular feature, structure, or characteristic, but every embodiment may not necessarily include the particular feature, structure, or characteristic. Moreover, these phrases do not necessarily refer to the same embodiment. Further, when a particular feature, structure, or characteristic is described in connection with an embodiment, it should be understood that the particular feature, structure, or characteristic can be implemented in combination with other embodiments within the knowledge of those skilled in the relevant art, whether or not explicitly described.

[0016] For ease of explanation, only embodiments of applying the technical solution of the present invention to "vehicles" are described in detail herein. However, those skilled in the art can fully understand that the technical solution of the present invention can be applied to any means of transportation such as trains, subways, ships, etc. where there may be passing situations. Unless otherwise specified, the term "A or B" used in this specification refers to "A and B" and "A or B", rather than meaning that A and B are exclusive.

[0017] Term Introduction:

[0018] GB / T 32960.1-2016 National Standard: Technical Specification for Electric Vehicle Remote Service and Management System, Release Date: August 29, 2016, Implementation Date: October 1, 2016.

[0019] In view of the cumbersome manual testing in the prior art, the testing method of the present invention uses automated code writing to achieve the following functions: configuring the data packet structure of in-vehicle terminal messages and each field of data units using a yaml configuration file; reading message fields from the configuration file and performing calculations to convert types such as strings, dates, WORDs, and BYTEs of data units into hexadecimal strings; establishing a TCP connection process between the vehicle networking platform and the in-vehicle terminal; simulating the in-vehicle terminal to send the written simulated messages to the vehicle networking platform; simulating manual login to the vehicle networking platform, entering the corresponding web page menu, querying the messages corresponding to the VIN, clicking to obtain the original message and the parsed message; automatically comparing whether the original message and the original hexadecimal message are consistent; automatically checking whether the parsed message is consistent with the fields configured by the tester in the yaml file. If both are consistent, a conclusion of passing the test is given; if either is inconsistent, a conclusion of failing the test is given.

[0020] Figure 1 A block diagram of a system 100 for automatically testing communication between an in-vehicle terminal and a vehicle networking platform according to an embodiment of the present invention is shown.

[0021] The system 100 may include an original message writing module 101, a communication module 102, a transmitted message acquisition module 103, and a message comparison module 104. Those skilled in the art can fully understand that the above module division is only for the purpose of clear explanation. The functions of one or more of the above modules can be combined into a single module or split into more modules. Moreover, one or more of the above modules can be implemented in the form of software, hardware, or a combination thereof. In addition, the data transfer method between the modules can adopt the methods known in the art, which is not within the scope of discussion of the present invention. In addition, the system 100 can be implemented in any computing system that can communicate with the in-vehicle terminal and the vehicle networking platform to perform tests between the in-vehicle terminal 105 and the vehicle networking platform 106.

[0022] According to an embodiment of the present invention, the original message writing module 101 may be configured to convert the content of the vehicle terminal message fields input by a user (such as a tester, a system administrator, etc.) into a hexadecimal original vehicle terminal message. Specifically, the original message writing module 101 may be configured to provide a vehicle terminal message configuration file, receive the field content input by the user for one or more fields of the vehicle terminal message configuration file, perform hexadecimal conversion on the field content of the one or more fields, and splice the converted hexadecimal strings of each field to obtain a hexadecimal original vehicle terminal message.

[0023] According to an embodiment of the present invention, the vehicle terminal message configuration file is at least predefined based on general message fields and fields varying according to the message type. In the context of the present invention, the configuration file may be a yaml configuration file. For example, for different types of messages, a vehicle terminal message configuration file may be predefined.

[0024] For example, according to the national standard GB / T 32960.1-2016, a complete data packet / message should consist of a start symbol, a command unit, an identification code, a data encryption method, a data unit length, a data unit, and a check code. The data packet structure and definition are shown in Table 1.

[0025]

[0026] Table 1

[0027] For a specific message type, for example, the vehicle login message, according to the national standard GB / T 32960.1-2016, its data format and definition are shown in Table 2.

[0028]

[0029] Table 2

[0030] Beijing time should be used for time, and the time definition is shown in Table 3.

[0031] Data representation content Length / byte Data type Valid value range Year 1 BYTE 0～99 Month 1 BYTE 1～12 Day 1 BYTE 1～31 Hour 1 BYTE 0～23 Minute 1 BYTE 0～59 Second 1 BYTE 0～59

[0032] Table 3

[0033] Based at least on the above Tables 1-3, the configuration file (such as a yaml configuration file) for the vehicle login message may be predefined in the following form, see Tables 4 and 5:

[0034]

[0035] Table 4 Vehicle Login Data Format and Definition

[0036]

[0037] Table 5 (Data Unit for Vehicle Login Message)

[0038] As mentioned above, the content of Table 5 is only for vehicle login messages, and different data units can be configured for other types of messages. In practice, testers only need to input the content of each field according to this configuration file, and the original message writing module 101 will automatically convert the content of each field input by the tester into the corresponding hexadecimal string based on the type of the field, and then splice the corresponding hexadecimal strings to form a hexadecimal message. For example, the content input by the tester above is converted into a hexadecimal string as follows: 232301FE4845563231424431365046303030373138010036170C0F0628390002383 93836303443383132323339303033343038390118304548504230313833313231303244394330313030303034F2. In order, first is the hexadecimal string of the content of some general message fields. For example, "2323" is the hexadecimal string of the content of the "start character" field, "01" is the hexadecimal string of the content of the "command identifier of the command unit" field, "FE" is the hexadecimal string of the content of the "response flag of the command unit" field, "4845563231424431365046303030373138" is the hexadecimal string of the content of the "unique identification code" field, "01" is the hexadecimal string of the content of the "data unit encryption method" field, and "0036" is the hexadecimal string of the content of the "data unit length" field. After that, follow the hexadecimal strings of the content of fields of a specific type of message (such as a vehicle login message). For example, "170C0F062839" is the hexadecimal string of the content of the "data collection time" field, "0002" is the hexadecimal string of the content of the "login serial number" field, "3839383630344338313232333930303334303839" is the hexadecimal string of the content of the "ICCID" field, "01" is the hexadecimal string of the content of the "number of rechargeable energy storage subsystems" field, "18" is the hexadecimal string of the content of the "coding length of the rechargeable energy storage subsystem" field, and "304548504230313833313231303244394330313030303034" is the hexadecimal string of the content of the "coding of the number of rechargeable energy storage systems" field. The last string is the content "F2" of the "check code" field of the general message field. Among them, F2 is the BCC check code calculated by the original message writing module 101 and does not need to be filled in by the tester.

[0039] According to an embodiment of the present invention, the communication module 102 may be configured to execute the TCP connection establishment process between the vehicle networking platform and the vehicle-mounted terminal, and send the hexadecimal original vehicle-mounted terminal message compiled by the original message compilation module 101 to the vehicle networking platform via the TCP connection.

[0040] According to an embodiment of the present invention, the received message acquisition module 103 may be configured to log in to the vehicle networking platform and obtain the messages associated with the vehicle based on the vehicle's VIN. Specifically, the received message acquisition module 103 may be configured to search for the messages sent by the vehicle in the vehicle networking platform based on the vehicle VIN indicated in the "unique identification code" field.

[0041] According to an embodiment of the present invention, the message comparison module 104 may be configured to perform two comparison processes: (1) compare the message obtained by the received message acquisition module 103 with the hexadecimal original vehicle-mounted terminal message compiled by the original message compilation module 101 to determine whether they are consistent; (2) call the parsing tool of the vehicle networking platform to parse the message obtained by the received message acquisition module 103, extract the field content in the parsed message, and compare the extracted field content with multiple fields of the vehicle-mounted terminal message configuration file to determine whether they are consistent. The message comparison module 104 may be further configured to provide a test failure result when the result of any one of the comparison processes (1) and (2) is inconsistent, and provide a test pass result when the results of both comparison processes (1) and (2) are consistent.

[0042] According to an embodiment of the present invention, the parsing tool of the vehicle networking platform parses the hexadecimal message using the same standard as the vehicle-mounted terminal (e.g., the national standard GB / T 32960.1-2016).

[0043] The above Figure 1 The example describes simulating the vehicle-mounted terminal sending messages to the vehicle networking platform to test whether the communication module and / or parsing tool on the vehicle networking platform side is working properly. The present invention can also be applied to simulating the vehicle networking platform sending messages to the vehicle-mounted terminal to test whether the communication module and / or parsing tool on the vehicle-mounted terminal side is working properly.

[0044] For example, the original message writing module 101 can be configured to convert the content of the vehicle networking platform message fields input by a user (such as a tester, a system administrator, etc.) into a hexadecimal original vehicle networking platform message. Specifically, the original message writing module 101 can be configured to provide a vehicle networking platform message configuration file, receive the field content input by the user for one or more fields among the multiple fields of the vehicle networking platform message configuration file, perform hexadecimal conversion on the field content of the one or more fields, and splice the converted hexadecimal strings of each field to obtain a hexadecimal original vehicle networking platform message.

[0045] The communication module 102 can be configured to execute the TCP connection establishment process between the vehicle networking platform and the in-vehicle terminal, and send the hexadecimal original vehicle networking platform message written by the original message writing module 101 to the in-vehicle terminal via the TCP connection. The received message acquisition module 103 can be configured to log in to the in-vehicle terminal and obtain the latest received message. The message comparison module 104 can be configured to execute two comparison processes: (1) compare the message obtained by the received message acquisition module 103 with the hexadecimal original vehicle networking platform message written by the original message writing module 101 to determine whether they are consistent; (2) call the parsing tool of the in-vehicle terminal to parse the message obtained by the received message acquisition module 103, extract the field content in the parsed message, and compare the extracted field content with the multiple fields of the vehicle networking platform message configuration file to determine whether they are consistent. The message comparison module 104 can be further configured to provide a test failure result in the case where the result of either of the comparison process (1) and the comparison process (2) is inconsistent, and provide a test pass result in the case where the results of both the comparison process (1) and the comparison process (2) are consistent.

[0046] Figure 2 The flowchart of a method 200 for automatically testing the communication between an in-vehicle terminal and a vehicle networking platform according to an embodiment of the present invention is shown.

[0047] At 205, the content of the in-vehicle terminal message fields input by the user is converted into a hexadecimal original in-vehicle terminal message, and the hexadecimal original in-vehicle terminal message is associated with a vehicle. Specifically, step 205 may further include providing an in-vehicle terminal message configuration file, receiving the field content input by the user for one or more fields among the multiple fields of the in-vehicle terminal message configuration file, automatically performing hexadecimal conversion on the field content of the one or more fields, and automatically splicing the converted hexadecimal strings of each field to obtain a hexadecimal original in-vehicle terminal message.

[0048] At 210, the TCP connection establishment process between the vehicle networking platform and the in-vehicle terminal is automatically executed, and the original in-vehicle terminal message in hexadecimal format written in step 205 is sent to the vehicle networking platform via this TCP connection.

[0049] At 215, the vehicle networking platform is automatically logged in, and the messages associated with the vehicle are obtained based on the VIN of the vehicle.

[0050] At 220, two comparison processes are automatically executed: (1) comparing the message obtained in step 215 with the original in-vehicle terminal message in hexadecimal format written in step 205 to determine whether they are consistent; (2) calling the parsing tool of the vehicle networking platform to parse the message obtained in step 215, extracting the field content in the parsed message, and comparing the extracted field content with the in-vehicle terminal message field content input by the user to determine whether they are consistent.

[0051] At 225, the comparison result is provided. Specifically, in the case where the result of any one of comparison process (1) and comparison process (2) is inconsistent, a comparison result of "test failed" is provided, and in the case where the results of both comparison process (1) and comparison process (2) are consistent, a comparison result of "test passed" is provided.

[0052] Figure 3 The block diagram of an exemplary computing device according to an embodiment of the present invention is shown, and this computing device is an example of a hardware device applicable to various aspects of the present invention.

[0053] Reference Figure 3 , a computing device 300 will now be described. This computing device is an example of a hardware device applicable to various aspects of the present invention. The computing device 300 can be any machine configured to perform processing and / or computing, and can be, but is not limited to, a workstation, a server, a desktop computer, a laptop computer, a tablet computer, a personal digital assistant, a smart phone, an in-vehicle computer, or any combination thereof. The foregoing various methods / devices / servers / client devices can be implemented in whole or at least in part by the computing device 300 or a similar device or system.

[0054] The computing device 300 may include components that can be connected or communicate via one or more interfaces and a bus 302. For example, the computing device 300 may include a bus 302, one or more processors 304, one or more input devices 306, and one or more output devices 308. The one or more processors 304 can be any type of processor and may include, but are not limited to, one or more general-purpose processors and / or one or more dedicated processors (e.g., specialized processing chips). The input device 306 can be any type of device capable of inputting information into the computing device and may include, but are not limited to, a mouse, a keyboard, a touch screen, a microphone, and / or a remote controller. The output device 308 can be any type of device capable of presenting information and may include, but are not limited to, a display, a speaker, a video / audio output terminal, a vibrator, and / or a printer. The computing device 300 may also include a non-transitory storage device 310 or be connected to the non-transitory storage device. The non-transitory storage device can be any storage device that is non-transitory and capable of implementing data storage, and the non-transitory storage device may include, but are not limited to, a disk drive, an optical storage device, a solid-state memory, a floppy disk, a flexible disk, a hard disk, a magnetic tape, or any other magnetic medium, an optical disk, or any other optical medium, a ROM (read-only memory), a RAM (random access memory), a cache memory, and / or any storage chip or cartridge, and / or any other medium from which a computer can read data, instructions, and / or code. The non-transitory storage device 310 can be separated from the interface. The non-transitory storage device 310 may have data / instructions / code for implementing the above methods and steps. The computing device 300 may also include a communication device 312. The communication device 312 can be any type of device or system capable of implementing communication with internal devices and / or communication with a network and may include, but are not limited to, a modem, a network card, an infrared communication device, a wireless communication device, and / or a chipset, such as a Bluetooth device, an IEEE 1302.11 device, a WiFi device, a WiMax device, a cellular communication device, and / or a similar device.

[0055] When the computing device 300 is used as an in-vehicle device, it can also be connected to external devices (e.g., a GPS receiver, sensors for sensing different environmental data (such as an acceleration sensor, a wheel speed sensor, a gyroscope, etc.)). In this way, for example, the computing device 300 can receive positioning data and sensor data indicating the vehicle condition. When the computing device 300 is used as an in-vehicle device, it can also be connected to other devices for controlling the driving and operation of the vehicle (e.g., an engine system, a windshield wiper, an anti-lock braking system, an electronic control unit, etc.).

[0056] In addition, the non-transitory storage device 310 may have map information and software components, so that the processor 304 can implement route guidance processing. In addition, the output device 308 may include a display for displaying maps, displaying positioning markers of the vehicle, and displaying images indicating the driving status of the vehicle. The output device 308 may also include a speaker or a headphone jack for audio guidance.

[0057] The bus 302 may include, but is not limited to, an Industry Standard Architecture (ISA) bus, a Micro Channel Architecture (MCA) bus, an Enhanced ISA (EISA) bus, a Video Electronics Standards Association (VESA) local bus, and a Peripheral Component Interconnect (PCI) bus. In particular, for in-vehicle devices, the bus 302 may also include a Controller Area Network (CAN) bus or other architectures designed for automotive applications.

[0058] The computing device 300 may further include a working memory 314, which may be any type of working memory capable of storing instructions and / or data beneficial to the operation of the processor 304 and may include, but is not limited to, random access memory and / or read-only storage devices.

[0059] The software components may be located in the working memory 314, and these software components include, but are not limited to, an operating system 316, one or more application programs 318, drivers, and / or other data and code. The instructions for implementing the above methods and steps may be included in the one or more application programs 318, and the modules / units / components of the foregoing various devices / servers / client devices may be implemented by the processor 304 reading and executing the instructions of the one or more application programs 318.

[0060] It should also be recognized that changes can be made according to specific requirements. For example, custom hardware may also be used, and / or specific components may be implemented in hardware, software, firmware, middleware, microcode, hardware description language, or any combination thereof. In addition, connections to other computing devices, such as network input / output devices, etc., may be employed. For example, part or all of the disclosed methods and devices may be implemented by programming hardware (e.g., programmable logic circuits including Field Programmable Gate Arrays (FPGAs) and / or Programmable Logic Arrays (PLAs)) with assembly language or hardware programming languages (e.g., VERILOG, VHDL, C++) using the logic and algorithms according to the present invention.

[0061] Although aspects of the present invention have been described so far with reference to the accompanying drawings, the above methods, systems, and devices are merely examples, and the scope of the present invention is not limited to these aspects, but is defined only by the appended claims and their equivalents. Various components may be omitted or may also be replaced by equivalent components. Additionally, the steps may be implemented in an order different from the order described in the present invention. Furthermore, the various components may be combined in various ways. It is also important that, as technology develops, many of the components described may be replaced by equivalent components that emerge later.

Claims

1. A method for automatically testing the communication between a vehicle-mounted terminal and a vehicle networking platform, comprising: (1) Converting the content of the vehicle-mounted terminal message field input by the user into a hexadecimal original vehicle-mounted terminal message, where the hexadecimal original vehicle-mounted terminal message is associated with a vehicle; (2) Automatically performing the TCP connection establishment process between the vehicle networking platform and the vehicle-mounted terminal, and sending the hexadecimal original vehicle-mounted terminal message to the vehicle networking platform via the TCP connection; (3) Automatically logging in to the vehicle networking platform, and obtaining the message associated with the vehicle based on the vehicle identification number VIN of the vehicle; And (4) Automatically performing two comparison processes: (a) Comparing the obtained message with the hexadecimal original vehicle-mounted terminal message compiled in step (1) to determine whether they are the same; (b) Invoking the parsing tool of the vehicle networking platform to parse the obtained message, extracting the field content in the parsed message, and comparing the extracted field content with the content of the vehicle-mounted terminal message field input by the user to determine whether they are the same.

2. The method according to claim 1, wherein Step (1) further includes: Providing a vehicle-mounted terminal message configuration file; Receiving the field content input by the user for one or more fields in the vehicle-mounted terminal message configuration file; Automatically converting the field content of the one or more fields into hexadecimal; and Automatically concatenating the converted hexadecimal strings of each field in the one or more fields to obtain the hexadecimal original vehicle-mounted terminal message.

3. The method according to claim 2, characterized in that, The vehicle-mounted terminal message configuration file is predefined at least based on general message fields and fields varying with message types.

4. The method according to claim 2, characterized in that The vehicle-mounted terminal message configuration file varies with message types.

5. The method according to claim 2, wherein Automatically converting the field content of the one or more fields into hexadecimal further includes: Performing hexadecimal conversion based on the field type of each field in the one or more fields.

6. The method according to claim 1, further comprising providing a comparison result, wherein: In the case where the result of either comparison process (a) or comparison process (b) is inconsistent, providing a comparison result of test failure; or In the case where the results of both comparison process (a) and comparison process (b) are consistent, providing a comparison result of test pass.

7. A system for automatically testing the communication between a vehicle-mounted terminal and a vehicle networking platform, comprising: An original message compilation module configured to convert the content of the vehicle-mounted terminal message field input by the user into a hexadecimal original vehicle-mounted terminal message, where the hexadecimal original vehicle-mounted terminal message is associated with a vehicle; A communication module configured to perform the TCP connection establishment process between the vehicle networking platform and the vehicle-mounted terminal, and send the hexadecimal original vehicle-mounted terminal message to the vehicle networking platform via the TCP connection; A transmitted message acquisition module configured to log in to the vehicle networking platform and obtain the message associated with the vehicle based on the vehicle identification number VIN of the vehicle; And A message comparison module, which is configured to perform two comparison processes: (a) compare the obtained message with the hexadecimal original vehicle terminal message written by the original message writing module to determine whether the two are consistent; (b) Call the parsing tool of the vehicle networking platform to parse the obtained message, extract the field content in the parsed message, and compare the extracted field content with the vehicle terminal message field content input by the user to determine whether the two are consistent.

8. The system according to claim 7, wherein The original message writing module is further configured to: Provide a vehicle terminal message configuration file; Receive the field content input by the user for one or more fields in the vehicle terminal message configuration file; Convert the field content of the one or more fields into hexadecimal; And Concatenate the converted hexadecimal strings of each field in the one or more fields to obtain the hexadecimal original vehicle terminal message.

9. The system according to claim 8, wherein The vehicle terminal message configuration file is predefined at least based on general message fields and fields that vary according to message types.

10. The system according to claim 7, wherein The message comparison module is further configured to: Provide a comparison result of failed test in the case where the result of either comparison process (a) or comparison process (b) is inconsistent; And Provide a comparison result of passed test in the case where the results of both comparison process (a) and comparison process (b) are consistent.

Images