A 5G-based vehicle TBOX protocol testing method, device and medium

Abstract

This invention provides a 5G-based method, device, and medium for testing vehicle-mounted TBOX protocols, relating to the field of vehicle-mounted TBOX testing. The method includes: connecting the TBOX device under test to a switch via a vehicle-mounted Ethernet converter; connecting the switch to a protocol simulation test platform; configuring the TBOX device under test and the protocol simulation test platform to the same network segment; the protocol simulation test platform identifying the vehicle-mounted interaction protocol running on the TBOX device under test to generate a protocol simulation instance; the protocol simulation test platform sending preset test cases corresponding to the protocol simulation instance to the protocol simulation instance; and the protocol simulation instance performing protocol interaction tests on the TBOX device under test according to the test cases to obtain the test results corresponding to the TBOX device under test. This achieves the effect of "write once, cover all protocols," improving the automation and efficiency of vehicle-mounted TBOX testing.

Description

Technical Field

[0001] This invention relates to the field of vehicle-mounted TBOX testing, and in particular to a 5G-based vehicle-mounted TBOX protocol testing method, equipment, and medium. Background Technology

[0002] With the accelerated advancement of intelligentization in new energy vehicles, the collaborative work of TBOX (Telematics Box) and vehicle infotainment systems (such as in-vehicle infotainment systems), as core carriers of intelligent connectivity functions, is becoming increasingly important. Under the current technical architecture, both the TBOX and the vehicle infotainment system access the gateway device via in-vehicle Ethernet, and communication between the TBOX and the vehicle infotainment system is forwarded through the gateway. The TBOX not only provides 4G / 5G network functionality to the vehicle infotainment system but also needs to realize several key service interactions, including vehicle positioning, remote diagnostics, and FOTA firmware upgrades.

[0003] However, the interaction protocol between TBOX and in-vehicle infotainment systems is not unified or standardized within the industry, with different OEMs customizing their own proprietary communication protocols. This situation presents significant engineering challenges for TBOX suppliers. For each new OEM project, they need to specifically adapt to a completely new interaction protocol and collaborate with different in-vehicle infotainment system suppliers. More importantly, during the project development cycle, TBOXes often cannot independently complete sufficient verification of the interaction protocol and must rely on joint debugging with the actual vehicle infotainment system during the vehicle testing phase. This retroactive verification method significantly increases project risk and development costs.

[0004] The current testing method for in-vehicle TBOX vehicle-to-vehicle protocols must rely on the physical connection of the actual vehicle-to-vehicle system for joint testing. The shortcomings of the existing technology are that not only does the development and testing progress of TBOX become completely dependent on the development progress and quality status of the vehicle-to-vehicle system, but it also leads to serious test resource dependency problems on the critical path of the project. Summary of the Invention

[0005] To address the aforementioned technical problems, the technical solution adopted by this invention is as follows:

[0006] According to one aspect of this application, a 5G-based vehicle-mounted TBOX protocol testing method is provided, applied to a vehicle-mounted TBOX testing system. The vehicle-mounted TBOX testing system includes a vehicle-mounted Ethernet converter, a switch, and a protocol simulation testing platform. The vehicle-mounted Ethernet converter is used to convert a dedicated vehicle-mounted Ethernet interface into a standard Ethernet interface. The switch supports access to multiple TBOX devices. The protocol simulation testing platform is used to test the TBOX devices.

[0007] The testing methods for the 5G-based vehicle-mounted TBOX protocol include:

[0008] Connect the TBOX device to be tested to the switch via an onboard Ethernet converter, and connect the switch to the protocol simulation test platform.

[0009] Configure the TBOX device to be tested and the protocol simulation test platform to be on the same network segment;

[0010] The protocol simulation test platform identifies the vehicle-to-everything (V2X) interaction protocol running on the TBOX device under test, and generates a protocol simulation instance corresponding to the V2X interaction protocol running on the TBOX device under test; the protocol simulation instance is used to simulate the vehicle-to-everything (V2X) behavior logic of the corresponding V2X interaction protocol.

[0011] The protocol simulation test platform sends the preset test cases corresponding to the protocol simulation instance to the protocol simulation instance;

[0012] The protocol simulation example performs protocol interaction tests on the TBOX device under test based on the test cases to obtain the test results for the TBOX device under test.

[0013] In one exemplary embodiment of this application, the TBOX device under test is used to perform the following steps:

[0014] In response to being configured on the same network segment as the protocol simulation test platform, a proactive discovery mechanism based on IP multicast is used to periodically broadcast the key identity information of the TBOX device under test to a predefined multicast address and port.

[0015] In one exemplary embodiment of this application, the key identity information of the TBOX device under test includes the vehicle identification code of the TBOX device under test, the protocol type of the vehicle-to-machine interaction protocol running on the TBOX device under test at the current moment, and the protocol service listening port of the TBOX device under test.

[0016] In one exemplary embodiment of this application, the protocol simulation test platform identifies the vehicle-to-everything (V2X) interaction protocol running on the TBOX device under test, and generates a protocol simulation instance corresponding to the V2X interaction protocol running on the TBOX device under test, including:

[0017] When the protocol simulation test platform obtains the broadcast message of the TBOX device under test, establish the mapping relationship between the Internet protocol address of the TBOX device under test, the protocol type of the vehicle-to-machine interaction protocol running on the TBOX device at the current moment, and the protocol service listening port of the TBOX device under test.

[0018] The protocol simulation test platform dynamically loads the protocol stack library corresponding to the identified vehicle-to-everything (V2X) interaction protocol running on the TBOX device under test.

[0019] The protocol simulation test platform creates an independent and isolated protocol simulation instance corresponding to the vehicle-to-everything (V2X) interaction protocol running on the multicast group where the TBOX device under test is located.

[0020] In one exemplary embodiment of this application, the protocol simulation testing platform sends preset test cases corresponding to the protocol simulation instance to the protocol simulation instance, including:

[0021] The protocol simulation test platform determines the test cases corresponding to the protocol simulation instance from a number of preset general test cases based on the type of protocol simulation instance corresponding to the TBOX device under test.

[0022] Send the test cases corresponding to the protocol simulation instance to the protocol simulation instance.

[0023] In one exemplary embodiment of this application, the protocol simulation instance performs protocol interaction testing on the TBOX device under test according to test cases to obtain the test results corresponding to the TBOX device under test, including:

[0024] The test case execution engine is triggered, driving the protocol simulation instance to execute the test steps included in the test case to perform protocol interaction tests on the TBOX device under test;

[0025] The protocol simulation example sends the test logs generated during the protocol interaction test of the TBOX device under test to the protocol simulation test platform.

[0026] The protocol simulation test platform integrates several test information from the test log to obtain the test results for the TBOX device under test.

[0027] In one exemplary embodiment of this application, the test information in the test log includes test instruction information, test response information, test timestamp information, and test status.

[0028] In one exemplary embodiment of this application, the vehicle-mounted TBOX testing system further includes:

[0029] The power supply is connected to the protocol simulation test platform to simulate the power supply environment of the entire vehicle.

[0030] The signal test bench, connected to the protocol simulation test platform, is used to simulate the vehicle wiring harness interface;

[0031] A network positioning antenna, connected to a protocol simulation test platform, is used to provide network connectivity channels and satellite positioning signals.

[0032] According to another aspect of this application, a non-transitory computer-readable storage medium is provided, wherein at least one instruction or at least one program is stored in the storage medium, the at least one instruction or the at least one program being loaded and executed by a processor to implement the aforementioned 5G-based vehicle TBOX protocol testing method.

[0033] According to another aspect of this application, an electronic device is provided, including a processor and the aforementioned non-transitory computer-readable storage medium.

[0034] The present invention has at least the following beneficial effects:

[0035] The 5G-based vehicle-mounted TBOX protocol testing method of this invention is executed by a vehicle-mounted TBOX testing system. The vehicle-mounted TBOX testing system consists of a vehicle-mounted Ethernet converter, a switch, and a protocol simulation testing platform. When testing the TBOX device under test, the TBOX device is connected to the switch via the vehicle-mounted Ethernet converter, and the switch is connected to the protocol simulation testing platform. The TBOX device under test and the protocol simulation testing platform are configured to be on the same network segment to ensure Layer 2 network interoperability. The protocol simulation testing platform identifies the vehicle-mounted interaction protocol running on the TBOX device under test to generate a protocol simulation of the vehicle-mounted terminal behavior logic corresponding to the vehicle-mounted interaction protocol running on the TBOX device under test. For example, the protocol simulation test platform sends the test cases corresponding to the protocol simulation instance to the protocol simulation instance. The protocol simulation instance performs protocol interaction tests on the TBOX device under test according to the test cases to obtain the test results of the TBOX device under test. By building an in-vehicle TBOX test system, the physical dependence of the in-vehicle TBOX on the vehicle system is eliminated. It can simultaneously connect to multiple in-vehicle TBOXes from different manufacturers and with different protocol types for testing, dynamically identify and adapt to multiple protocols, execute general test cases in parallel, and generate test reports based on the test results. It achieves the effect of writing once and covering all protocols, improving the automation and testing efficiency of in-vehicle TBOX testing, while also facilitating the expansion and access of new TBOX in-vehicle interaction protocols. Attached Figure Description

[0036] To more clearly illustrate the technical solutions in the embodiments of the present invention, the accompanying drawings used in the description of the embodiments will be briefly introduced below. Obviously, the accompanying drawings described below are only some embodiments of the present invention. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0037] Figure 1 A flowchart illustrating the 5G-based vehicle TBOX protocol testing method provided in this embodiment of the invention;

[0038] Figure 2 A system structure diagram for testing multiple TBOX devices provided in an embodiment of the present invention;

[0039] Figure 3 This is a schematic diagram illustrating the matching of the protocol adapter and test cases provided in an embodiment of the present invention. Detailed Implementation

[0040] The technical solutions of the embodiments of the present invention will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of the present invention, and not all embodiments. Based on the embodiments of the present invention, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of the present invention.

[0041] This application proposes a 5G-based vehicle-mounted TBOX protocol testing method, which is applied to a vehicle-mounted TBOX testing system. The vehicle-mounted TBOX testing system includes a vehicle-mounted Ethernet converter, a switch, a protocol simulation test platform, a power supply, a signal test bench, and a network positioning antenna combination.

[0042] When testing the vehicle-mounted TBOX, connect the vehicle-mounted TBOX to the vehicle-mounted Ethernet converter, connect the vehicle-mounted Ethernet converter to the switch, connect the switch to the protocol simulation test platform, connect the power supply to the protocol simulation test platform, connect the signal test bench to the protocol simulation test platform, and connect the network positioning antenna combination to the protocol simulation test platform.

[0043] The vehicle-mounted Ethernet converter is used to convert the vehicle-mounted Ethernet-specific interface into a standard Ethernet interface (such as a standard RJ45 Ethernet interface). The switch supports the connection of multiple TBOX devices, which means that multiple TBOX devices can be tested in parallel at the same time. The power supply is used to simulate the vehicle power supply environment. The signal bench is used to simulate the vehicle wiring harness interface. The network positioning antenna combination is used to provide a stable and reliable network connection channel and satellite positioning signal to ensure the effectiveness of communication and positioning function testing.

[0044] The protocol simulation test platform is used to test TBOX devices. The platform has multiple proprietary vehicle infotainment interaction protocols built-in, which can automatically identify the protocol type of the TBOX, create corresponding protocol simulation instances in real time, execute automated test case scripts in parallel, automatically summarize the results of each test instance, and generate detailed and traceable test reports. By building an automated testing host computer platform (protocol simulation test platform) independent of the actual vehicle infotainment system, the platform fully reproduces the interactive behavior of the vehicle infotainment system through protocol simulation technology, so as to achieve the full life cycle autonomous verification effect of the TBOX vehicle infotainment interaction protocol.

[0045] Among them, such as Figure 1As shown, the 5G-based vehicle TBOX protocol testing method of this application includes:

[0046] Step S100: Connect the TBOX device to be tested to the switch via the vehicle-mounted Ethernet converter, and connect the switch to the protocol simulation test platform;

[0047] The TBOX device to be tested is the object being tested.

[0048] like Figure 2 As shown, if there are multiple TBOX devices to be tested, and the manufacturers and protocol types of the multiple TBOX devices to be tested are different, this system can test multiple TBOX devices to be tested simultaneously. Each TBOX device to be tested is connected to the switch through an in-vehicle Ethernet converter, so that each TBOX device to be tested can be tested in parallel through the protocol simulation test platform.

[0049] Step S200: Configure the TBOX device to be tested and the protocol simulation test platform to be on the same network segment;

[0050] Furthermore, in response to being configured on the same network segment as the protocol simulation test platform, the TBOX device under test periodically broadcasts its key identity information to a predefined multicast address and port using an active discovery mechanism based on IP multicast (implemented through the IGMP protocol (Internet Group Management Protocol), whose core function is to dynamically manage the joining and leaving of group members).

[0051] The key identity information of the TBOX device under test includes the Vehicle Identification Number (VIN) of the TBOX device under test, the protocol type of the vehicle-to-machine interaction protocol that the TBOX device is currently running, and the protocol service listening port of the TBOX device under test.

[0052] Step S300: The protocol simulation test platform identifies the vehicle-to-machine interaction protocol running on the TBOX device under test, and generates a protocol simulation instance corresponding to the vehicle-to-machine interaction protocol running on the TBOX device under test.

[0053] The protocol simulation example is used to simulate the vehicle-to-vehicle (V2V) behavior logic of the corresponding V2V interaction protocol.

[0054] Further, in step S300, the protocol simulation test platform identifies the vehicle-to-machine interaction protocol running on the TBOX device under test, and generates a protocol simulation instance corresponding to the vehicle-to-machine interaction protocol running on the TBOX device under test, including steps S310-S330:

[0055] Step S310: When the broadcast message of the TBOX device under test is obtained by the protocol simulation test platform, establish the mapping relationship between the Internet protocol address (IP address) of the TBOX device under test, the protocol type of the vehicle-to-machine interaction protocol running on the TBOX device under test at the current moment, and the protocol service listening port of the TBOX device under test.

[0056] After configuring the protocol simulation test platform to be on the same network segment (same IP subnet address) as the TBOX device under test, the protocol simulation test platform, acting as a listener, joins the same multicast group as the TBOX device under test. Once the protocol simulation test platform receives a broadcast message from the TBOX device under test, it can parse and establish a mapping relationship between the IP address, protocol type, and protocol service listening port of the TBOX device under test in real time. This method realizes the discovery of the TBOX device under test and the automatic identification of the protocol, eliminating the need to manually configure each TBOX device under test, and greatly simplifying the test preparation process.

[0057] Step S320: The protocol simulation test platform dynamically loads the protocol stack library corresponding to the identified vehicle-machine interaction protocol running on the TBOX device under test.

[0058] Step S330: The protocol simulation test platform creates an independent and isolated protocol simulation instance corresponding to the vehicle-to-machine interaction protocol running on the TBOX device to be tested, which is located in the multicast group of the TBOX device to be tested.

[0059] Step S400: The protocol simulation test platform sends the preset test cases corresponding to the protocol simulation instance to the protocol simulation instance;

[0060] Furthermore, in step S400, the protocol simulation test platform sends the preset test cases corresponding to the protocol simulation instance to the protocol simulation instance, including steps S410-S420:

[0061] Step S410: The protocol simulation test platform determines the test cases corresponding to the protocol simulation instance from a number of preset general test cases based on the type of protocol simulation instance corresponding to the TBOX device to be tested.

[0062] Step S420: Send the test cases corresponding to the protocol simulation instance to the protocol simulation instance.

[0063] On the protocol simulation testing platform, select or import a preset general test case set. The general test case set includes several general test cases, such as vehicle status query, location service, remote diagnostics, and FOTA firmware upgrade. The protocol simulation testing platform intelligently distributes the corresponding test cases to the corresponding instances based on the type of each protocol simulation instance. A general test case set can be distributed to all compatible protocol instances simultaneously to ensure parallel testing of multiple TBOX devices under test.

[0064] Step S500: Protocol Simulation Example. Based on the test cases, perform protocol interaction tests on the TBOX device under test to obtain the test results corresponding to the TBOX device under test.

[0065] Further, in step S500, the protocol simulation instance performs protocol interaction tests on the TBOX device under test according to the test cases to obtain the test results corresponding to the TBOX device under test, including steps S510-S530:

[0066] Step S510: Trigger the execution engine of the test case to drive the protocol simulation instance to execute the test steps included in the test case in order to perform protocol interaction testing on the TBOX device under test;

[0067] Each protocol simulation instance independently interacts with the corresponding TBOX device under test, sends commands, receives responses, and verifies results.

[0068] Step S520: The protocol simulation example sends the test logs generated during the protocol interaction test of the TBOX device under test to the protocol simulation test platform.

[0069] Step S530: The protocol simulation test platform integrates several test information from the test log to obtain the test results corresponding to the TBOX device under test.

[0070] The test logs contain test command information, test response information, test timestamp information, and test status. Each protocol simulation instance records detailed logs in real time during execution. After all TBOX devices under test have completed their tests, the protocol simulation test platform will automatically aggregate the test results of each protocol simulation instance, categorize them by device / IP / protocol type, and generate a structured test report. This report clearly displays the test details, pass rate, problem points, and log snapshots for each TBOX device, improving the automation and efficiency of TBOX device testing.

[0071] Furthermore, the TBOX vehicle-to-everything (V2X) interaction protocols defined by different OEMs, and even different vehicle platforms within the same OEM, exhibit significant differences in message structure, command sets, and communication mechanisms (request / response, publish / subscribe). Therefore, to achieve test case universality, a protocol adapter needs to be developed for each supported proprietary protocol. This adapter has two core interfaces: an upper-layer interface that exposes a set of standardized, protocol-independent functional interfaces that abstract the core business functions of the TBOX device; and a lower-layer interface that interfaces with the specific proprietary protocol, handling its unique encoding / decoding, serialization / deserialization, and communication session management functions. Test case scripts are written only for the standardized functional interfaces. Therefore, regardless of the underlying specific protocol, as long as the adapter correctly implements these standard interfaces, the same test case script can run on that protocol, improving test reusability.

[0072] In addition, such as Figure 3 As shown, for a very small number of proprietary protocols with significantly different functional logic or those that cannot be fully mapped to standard interfaces, dedicated protocol adapters can be written. Within these adapters, differences are distinguished by OEM or vehicle model fields, and their unique logic is handled within the test cases. The test cases themselves retain most of their general applicability, only making differentiated calls to specific parts. Through standardized interface design, dynamic multi-protocol adaptation, and parallel testing mechanisms, functional verification of TBOX devices from different manufacturers and with different protocol types can be efficiently supported, significantly improving the automation and execution efficiency of in-vehicle terminal testing.

[0073] The 5G-based vehicle-mounted TBOX protocol testing method of this invention is executed by a vehicle-mounted TBOX testing system. The vehicle-mounted TBOX testing system consists of a vehicle-mounted Ethernet converter, a switch, and a protocol simulation testing platform. When testing the TBOX device under test, the TBOX device is connected to the switch via the vehicle-mounted Ethernet converter, and the switch is connected to the protocol simulation testing platform. The TBOX device under test and the protocol simulation testing platform are configured to be on the same network segment to ensure Layer 2 network interoperability. The protocol simulation testing platform identifies the vehicle-mounted interaction protocol running on the TBOX device under test to generate a protocol simulation of the vehicle-mounted terminal behavior logic corresponding to the vehicle-mounted interaction protocol running on the TBOX device under test. For example, the protocol simulation test platform sends the test cases corresponding to the protocol simulation instance to the protocol simulation instance. The protocol simulation instance performs protocol interaction tests on the TBOX device under test according to the test cases to obtain the test results of the TBOX device under test. By building an in-vehicle TBOX test system, the physical dependence of the in-vehicle TBOX on the vehicle system is eliminated. It can simultaneously connect to multiple in-vehicle TBOXes from different manufacturers and with different protocol types for testing, dynamically identify and adapt to multiple protocols, execute general test cases in parallel, and generate test reports based on the test results. It achieves the effect of writing once and covering all protocols, improving the automation and testing efficiency of in-vehicle TBOX testing, while also facilitating the expansion and access of new TBOX in-vehicle interaction protocols.

[0074] Embodiments of the present invention also provide a computer program product including program code, which, when the program product is run on an electronic device, causes the electronic device to perform the steps of the methods described above in various exemplary embodiments of the present invention.

[0075] Furthermore, although the steps of the method in this disclosure are described in a specific order in the accompanying drawings, this does not require or imply that the steps must be performed in that specific order, or that all the steps shown must be performed to achieve the desired result. Additional or alternative steps may be omitted, multiple steps may be combined into one step, and / or a step may be broken down into multiple steps.

[0076] From the above description of the embodiments, those skilled in the art will readily understand that the exemplary embodiments described herein can be implemented by software or by combining software with necessary hardware. Therefore, the technical solutions according to the embodiments of this disclosure can be embodied in the form of a software product, which can be stored in a non-volatile storage medium (such as a CD-ROM, USB flash drive, external hard drive, etc.) or on a network, including several instructions to cause a computing device (such as a personal computer, server, mobile terminal, or network device, etc.) to execute the methods according to the embodiments of this disclosure.

[0077] In an exemplary embodiment of this disclosure, an electronic device capable of implementing the above-described method is also provided.

[0078] Those skilled in the art will understand that various aspects of the present invention can be implemented as systems, methods, or program products. Therefore, various aspects of the present invention can be specifically implemented in the following forms: entirely in hardware, entirely in software (including firmware, microcode, etc.), or in a combination of hardware and software, collectively referred to herein as “circuit,” “module,” or “system.”

[0079] An electronic device according to this embodiment of the invention. The electronic device is merely an example and should not be construed as limiting the functionality or scope of the embodiments of the invention.

[0080] Electronic devices are manifested in the form of general-purpose computing devices. Components of an electronic device may include, but are not limited to: at least one processor, at least one memory, and buses connecting different system components (including memory and processor).

[0081] The storage device stores program code that can be executed by the processor to perform the steps described in the "Exemplary Methods" section above, according to various exemplary embodiments of the present invention.

[0082] The storage may include readable media in the form of volatile storage, such as random access memory (RAM) and / or cache memory, and may further include read-only memory (ROM).

[0083] The storage may also include programs / utilities having a set (at least one) of program modules, including but not limited to: an operating system, one or more applications, other program modules, and program data, each or some combination of these examples may include an implementation of a network environment.

[0084] A bus can represent one or more of several bus architectures, including a memory bus or memory controller, a peripheral bus, a graphics acceleration port, a processor, or a local bus that uses any of the various bus architectures.

[0085] Electronic devices can also communicate with one or more external devices (such as keyboards, pointing devices, Bluetooth devices, etc.), one or more devices that enable users to interact with the electronic device, and / or any device that enables the electronic device to communicate with one or more other computing devices (such as routers, modems, etc.). This communication can be performed through input / output (I / O) interfaces. Furthermore, electronic devices can also communicate with one or more networks (such as local area networks (LANs), wide area networks (WANs), and / or public networks, such as the Internet) via network adapters.

[0086] In exemplary embodiments of this disclosure, a computer-readable storage medium is also provided, on which a program product capable of implementing the methods described above is stored. In some possible embodiments, various aspects of the invention may also be implemented as a program product comprising program code that, when the program product is run on a terminal device, causes the terminal device to perform the steps of the various exemplary embodiments of the invention described in the "Exemplary Methods" section of this specification.

[0087] The program product may employ any combination of one or more readable media. A readable medium may be a readable signal medium or a readable storage medium. A readable storage medium may be, for example, but not limited to, an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any combination thereof. More specific examples of readable storage media (a non-exhaustive list) include: an electrical connection having one or more wires, a portable disk, a hard disk, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), optical fiber, portable compact disk read-only memory (CD-ROM), optical storage devices, magnetic storage devices, or any suitable combination thereof.

[0088] Computer-readable signal media may include data signals propagated in baseband or as part of a carrier wave, carrying readable program code. Such propagated data signals may take various forms, including but not limited to electromagnetic signals, optical signals, or any suitable combination thereof. A readable signal medium may also be any readable medium other than a readable storage medium, capable of sending, propagating, or transmitting programs for use by or in conjunction with an instruction execution system, apparatus, or device.

[0089] The program code contained on the readable medium may be transmitted using any suitable medium, including but not limited to wireless, wired, optical fiber, RF, etc., or any suitable combination thereof.

[0090] Program code for performing the operations of this invention can be written in any combination of one or more programming languages, including object-oriented programming languages ​​such as Java and C++, and conventional procedural programming languages ​​such as C or similar languages. The program code can execute entirely on the user's computing device, partially on the user's device, as a standalone software package, partially on the user's computing device and partially on a remote computing device, or entirely on a remote computing device or server. In cases involving remote computing devices, the remote computing device can be connected to the user's computing device via any type of network, including a local area network (LAN) or a wide area network (WAN), or it can be connected to an external computing device (e.g., via the Internet using an Internet service provider).

[0091] Furthermore, the above figures are merely illustrative of the processes included in the method according to exemplary embodiments of the present invention, and are not intended to be limiting. It is readily understood that the processes shown in the above figures do not indicate or limit the temporal order of these processes. Additionally, it is readily understood that these processes may be executed synchronously or asynchronously, for example, in multiple modules.

[0092] It should be noted that although several modules or units for the device used to perform actions have been mentioned in the detailed description above, this division is not mandatory. In fact, according to embodiments of this disclosure, the features and functions of two or more modules or units described above can be embodied in one module or unit. Conversely, the features and functions of one module or unit described above can be further divided and embodied by multiple modules or units.

[0093] 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 variations or substitutions that can be easily conceived by those skilled in the art within the technical scope disclosed in the present invention should be included within the scope of protection of the present invention. Therefore, the scope of protection of the present invention should be determined by the scope of the claims.

Claims

1. A 5G-based vehicle-mounted TBOX protocol testing method, characterized in that, This invention relates to an in-vehicle TBOX testing system, which includes an in-vehicle Ethernet converter, a switch, and a protocol simulation testing platform. The in-vehicle Ethernet converter converts a dedicated in-vehicle Ethernet interface into a standard Ethernet interface. The switch supports the connection of multiple TBOX devices. The protocol simulation testing platform is used to test the TBOX devices. The 5G-based vehicle-mounted TBOX protocol testing method includes: The TBOX device to be tested is connected to the switch via the vehicle-mounted Ethernet converter, and the switch is connected to the protocol simulation test platform; Configure the TBOX device to be tested and the protocol simulation test platform to be on the same network segment; The protocol simulation test platform identifies the vehicle-to-machine interaction protocol running on the TBOX device under test, and generates a protocol simulation instance corresponding to the vehicle-to-machine interaction protocol running on the TBOX device under test; the protocol simulation instance is used to simulate the vehicle-to-machine behavior logic of the corresponding vehicle-to-machine interaction protocol. The protocol simulation testing platform sends the preset test cases corresponding to the protocol simulation instance to the protocol simulation instance; The protocol simulation instance performs protocol interaction tests on the TBOX device under test according to the test cases to obtain the test results corresponding to the TBOX device under test. The protocol simulation testing platform identifies the vehicle-to-everything (V2X) interaction protocol running on the TBOX device under test, and generates a protocol simulation instance corresponding to the V2X interaction protocol running on the TBOX device under test, including: When the protocol simulation test platform obtains the broadcast message of the TBOX device under test, a mapping relationship is established between the Internet protocol address of the TBOX device under test, the protocol type of the vehicle-to-machine interaction protocol running on the TBOX device at the current moment, and the protocol service listening port of the TBOX device under test. The protocol simulation test platform dynamically loads the protocol stack library corresponding to the identified vehicle-machine interaction protocol running on the TBOX device under test. The protocol simulation test platform creates an independent and isolated protocol simulation instance for the vehicle-to-machine interaction protocol running on the TBOX device under test within the multicast group where the TBOX device under test is located.

2. The method according to claim 1, characterized in that, The TBOX device under test is used to perform the following steps: In response to being configured on the same network segment as the protocol simulation test platform, the key identity information of the TBOX device under test is periodically broadcast to a predefined multicast address and port using an active discovery mechanism based on IP multicast.

3. The method according to claim 2, characterized in that, The key identity information of the TBOX device under test includes the vehicle identification code of the TBOX device under test, the protocol type of the vehicle-machine interaction protocol running on the TBOX device at the current moment, and the protocol service listening port of the TBOX device under test.

4. The method according to claim 3, characterized in that, The protocol simulation testing platform sends preset test cases corresponding to the protocol simulation instance to the protocol simulation instance, including: The protocol simulation test platform determines the test cases corresponding to the protocol simulation instance from a number of preset general test cases based on the type of the protocol simulation instance corresponding to the TBOX device under test. Send the test cases corresponding to the protocol simulation instance to the protocol simulation instance.

5. The method according to claim 4, characterized in that, The protocol simulation instance performs protocol interaction tests on the TBOX device under test according to the test cases to obtain the test results corresponding to the TBOX device under test, including: The execution engine of the test case is triggered, driving the protocol simulation instance to execute the test steps included in the test case, so as to perform protocol interaction testing on the TBOX device under test; The protocol simulation instance sends the test logs generated during the protocol interaction test of the TBOX device under test to the protocol simulation test platform. The protocol simulation test platform integrates several test information from the test log to obtain the test results corresponding to the TBOX device under test.

6. The method according to claim 5, characterized in that, The test information in the test log includes test instruction information, test response information, test timestamp information, and test status.

7. The method according to claim 6, characterized in that, The vehicle-mounted TBOX testing system also includes: A power supply, connected to the protocol simulation test platform, is used to simulate the power supply environment of the entire vehicle; A signal test bench, connected to the protocol simulation test platform, is used to simulate the vehicle wiring harness interface; A network positioning antenna, connected to the protocol simulation test platform, is used to provide network connection channels and satellite positioning signals.

8. A non-transitory computer-readable storage medium, characterized in that, The storage medium stores at least one instruction or at least one program segment, which is loaded and executed by a processor to implement the method as described in any one of claims 1-7.

9. An electronic device, characterized in that, Includes a processor and the non-transitory computer-readable storage medium as described in claim 8.

Images