A method and apparatus for testing the reliability of TBOX communication

Abstract

This application provides a method and apparatus for testing the communication reliability of a TBOX (Telematics Toy Box), relating to the field of vehicle testing. The method includes: determining multiple target areas within a preset area range, and generating at least one test scenario based on the multiple target areas; obtaining the total number of tests corresponding to each of the at least one test scenario; performing multiple communication reliability tests on the TBOX in each test scenario, recording the current number of tests at each test, and including the failure in the total number of failures when the test results indicate a TBOX failure; and ending the test in each test scenario when the current number of tests in each test scenario reaches the corresponding total number of tests. This application can generate all scenarios covering the testing needs, providing more comprehensive and targeted testing, shortening the testing mileage and time, and reducing testing costs. Furthermore, the total number of tests obtained after the TBOX version update is the minimum number of tests, and testing is performed based on this minimum number of tests, further reducing testing costs.

Description

Technical Field

[0001] This application relates to the field of vehicle testing technology, and in particular to a TBOX communication reliability testing method and apparatus. Background Technology

[0002] The TBOX (Telematics Box) is the core controller for vehicle information systems. It is used to collect vehicle bus signals in real time and connect to the TSP (Telematics Service Provider) backend via 4G to realize functions such as vehicle status uploading, remote upgrades, remote diagnostics, remote control, and fault reporting. At the same time, users can remotely control the vehicle and remotely diagnose vehicle health through a mobile APP, bringing great convenience to users.

[0003] Due to weather and road conditions, cars often need to travel through areas with inconsistent communication signal strength (such as 4G signal) while driving on the road. Therefore, it is necessary to conduct communication reliability tests on the TBOX to avoid the danger caused by TBOX communication failure when the car is on the road.

[0004] Currently, TBOX's communication reliability testing is all done on actual roads. However, due to the influence of weather and roads, communication signals can change even in the same area, which often results in road tests being unable to test all scenarios. In order to test as many scenarios as possible, long-distance (e.g., 10,000 kilometers) and long-term (usually a test cycle of about one month) tests are required, which is inefficient and costly. After the TBOX version is updated, long-distance and long-term road tests need to be carried out again, which further increases the testing cost. Summary of the Invention

[0005] In view of this, this application provides a TBOX communication reliability testing method and apparatus to solve the above-mentioned technical problems, and the technical solution is as follows:

[0006] A TBOX communication reliability testing method includes:

[0007] Multiple target areas are identified within a preset area, and at least one test scenario is generated based on the multiple target areas. The GPS signal and / or communication signal strength of any two target areas are different. At least one test scenario includes a scenario where the communication signal strength switches when there is a GPS signal and / or a scenario where the communication signal strength switches when there is no GPS signal.

[0008] Obtain the total number of tests corresponding to at least one test scenario. When the remote information processor TBOX being tested is version 1, the total number of tests is a preset number. When the TBOX being tested is version 2, the total number of tests is a predetermined minimum number of tests required for at least one TBOX failure to occur. Version 2 refers to versions updated after version 1.

[0009] In each test scenario, the TBOX is subjected to multiple communication reliability tests. The current number of tests is recorded at each test. When the test results indicate that the TBOX is faulty, the fault is included in the total number of faults. The test for each test scenario ends when the current number of tests in each test scenario reaches the corresponding total number of tests.

[0010] Optionally, the multiple target regions include: a first target region, a second target region, a third target region, a fourth target region, a fifth target region, and a sixth target region;

[0011] GPS signals are present in the first, second, and third target areas, while GPS signals are absent in the fourth, fifth, and sixth target areas. The presence of a GPS signal in one area indicates that a GPS signal can be detected in that area, while the absence of a GPS signal in one area indicates that a GPS signal cannot be detected in that area.

[0012] The communication signal strength of the first target area and the fourth target area is the first strength, the communication signal strength of the second target area and the fifth target area is the second strength, and the communication signal strength of the third target area and the sixth target area is the third strength;

[0013] The first intensity is greater than or equal to a preset first threshold, the second intensity is less than the first threshold but greater than or equal to a preset second threshold, and the third intensity is less than the second threshold.

[0014] Optionally, multiple target areas within a preset area range can be defined, including:

[0015] When the vehicle with the TBOX installed is within a preset area, retrieve the TBOX log data;

[0016] Based on the first field in the log data, determine the areas with GPS signals and the areas without GPS signals within the preset area;

[0017] Based on the second field in the log data, the first target area, the second target area, and the third target area are determined from the areas with GPS signals, and the fourth target area, the fifth target area, and the sixth target area are determined from the areas without GPS signals.

[0018] Optionally, at least one test scenario includes:

[0019] The test scenario involves a vehicle equipped with a TBOX moving from the first target area to the second target area and then back to the first target area.

[0020] A test scenario in which a vehicle enters a third target area from a first target area and then returns to the first target area;

[0021] The test scenario involves vehicles sequentially entering the second and third target areas from the first target area, and then sequentially returning to the second and first target areas.

[0022] The test scenario where the vehicle enters the fifth target area from the fourth target area and then returns to the fourth target area;

[0023] The test scenario where the vehicle enters the sixth target area from the fourth target area and then returns to the fourth target area;

[0024] The test scenario involves the vehicle moving sequentially from the fourth target area to the fifth and sixth target areas, and then returning sequentially to the fifth and fourth target areas.

[0025] Optionally, communication reliability testing is performed on the TBOX in each test scenario, including:

[0026] When a vehicle moves from the first target area to the second target area, or from the fourth target area to the fifth target area, the vehicle is kept idling for a first duration. If communication between the TBOX and the backend server is abnormal during the first duration, the system determines whether the current fault is a TBOX fault based on the TBOX log data and the vehicle's controller area network CAN message data.

[0027] When a vehicle enters the third target area from the first or second target area, or enters the sixth target area from the fourth or fifth target area, the vehicle is kept idling for a first duration. During the first duration, it is determined whether the TBOX and the backend server are unable to communicate.

[0028] When a vehicle enters the first target area from the second or third target area, or enters the fourth target area from the fifth or sixth target area, or enters the second target area from the third target area, or enters the fifth target area from the sixth target area, if the TBOX fails to recover to the corresponding communication signal strength within the second time period, or if the communication between the TBOX and the backend server is abnormal during the first time period when the vehicle is idling, the current fault is determined to be a TBOX fault based on the TBOX log data and CAN message data.

[0029] Optionally, communication reliability testing is performed on the TBOX in each test scenario, including:

[0030] When the vehicle moves from the first target area to the second target area, or from the fourth target area to the fifth target area, the vehicle is put into sleep mode for a third period of time and then powered on again. After powering on, the vehicle idles for a first period of time. If communication between the TBOX and the backend server is abnormal during the first period of time, the system determines whether the current fault is a TBOX fault based on the TBOX log data and the vehicle's controller area network CAN message data.

[0031] When a vehicle enters the third target area from the first or second target area, or enters the sixth target area from the fourth or fifth target area, the vehicle is put into sleep mode for a third period of time and then powered on again. After powering on, the vehicle idles for a first period of time. During the first period of time, it is determined whether the TBOX and the backend server are unable to communicate.

[0032] When a vehicle enters the first target area from the second or third target area, or the fourth target area from the fifth or sixth target area, or the second target area from the third target area, or the fifth target area from the sixth target area, the vehicle is put into sleep mode for a third period and then powered on again. If the TBOX fails to recover to the corresponding communication signal strength within the second period after power-on, or if the communication between the TBOX and the backend server is abnormal within the first period of idling after power-on, the current fault is determined to be a TBOX fault based on the TBOX log data and CAN message data.

[0033] Optionally, if the TBOX fails to periodically report vehicle status information or the backend server fails to successfully issue a vehicle status query command within the first time period, it is determined that there is an abnormality in the communication between the TBOX and the backend server.

[0034] Optionally, when the TBOX being tested is version 1, the method also includes:

[0035] Based on the total number of tests, the total number of failures after the test, and the preset confidence level for each of the at least one test scenario, determine the confidence intervals for each of the at least one test scenario.

[0036] Based on the confidence interval and total number of tests corresponding to at least one test scenario, determine the minimum number of tests corresponding to each of the at least one test scenario.

[0037] Optionally, based on the total number of tests corresponding to at least one test scenario, the total number of failures after the test, and a preset confidence level, determine the confidence intervals corresponding to at least one test scenario, including:

[0038] Calculate the sample proportion corresponding to each of the at least one test scenario based on the total number of tests and the total number of failures after the test.

[0039] Calculate the confidence intervals for each of the at least one test scenario based on the sample proportion, total number of tests, and confidence level.

[0040] A TBOX communication reliability testing device, comprising:

[0041] The test scenario generation module is used to determine multiple target areas within a preset area range and generate at least one test scenario based on the multiple target areas. The GPS signal and / or communication signal strength of any two target areas are different. At least one test scenario includes a scenario where the communication signal strength switches when there is a GPS signal and / or a scenario where the communication signal strength switches when there is no GPS signal.

[0042] The total number of tests acquisition module is used to acquire the total number of tests corresponding to at least one test scenario. When the remote information processor TBOX being tested is version 1, the total number of tests is a preset number. When the TBOX being tested is version 2, the total number of tests is the minimum number of tests required for at least one TBOX failure to occur. Version 2 refers to versions updated after version 1.

[0043] The communication reliability testing module is used to perform multiple communication reliability tests on the TBOX in each test scenario. It records the current number of tests during each test and includes the failure in the total number of failures when the test results indicate a failure of the TBOX. The test for each test scenario ends when the current number of tests in each test scenario reaches the corresponding total number of tests.

[0044] As can be seen from the above technical solution, the TBOX communication reliability testing method provided in this application takes into account that roads and weather mainly affect communication signals and GPS signals. Therefore, this application first determines multiple target areas within a preset area based on GPS signal and communication signal strength, and generates at least one test scenario required for testing based on multiple target areas, covering all scenarios required for testing, making the test more comprehensive. This application can also obtain the total number of tests corresponding to at least one test scenario. After the TBOX version is updated, the total number of tests is the minimum number of tests required for at least one TBOX failure to occur, which can greatly shorten the test mileage and test time, reduce test costs, and at the same time, pre-generate test scenarios, allowing this application to conduct TBOX communication reliability tests in targeted test scenarios, greatly shortening the test mileage and test time, and further reducing test costs. Attached Figure Description

[0045] To more clearly illustrate the technical solutions in the embodiments of this application or the prior art, the drawings used in the description of the embodiments or the prior art will be briefly introduced below. Obviously, the drawings described below are only embodiments of this application. For those skilled in the art, other drawings can be obtained based on the provided drawings without creative effort.

[0046] Figure 1 A flowchart illustrating a TBOX communication reliability testing method provided in an embodiment of this application;

[0047] Figure 2 A schematic diagram illustrating the 4G communication reliability testing process of an automotive TBOX provided in this application embodiment;

[0048] Figure 3 A schematic diagram of the structure of a TBOX communication reliability testing device provided in an embodiment of this application;

[0049] Figure 4 This is a hardware structure block diagram of a TBOX communication reliability testing device provided in an embodiment of this application. Detailed Implementation

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

[0051] This application provides a TBOX communication reliability testing method, which will be described in detail below through the following embodiments.

[0052] Please see Figure 1 The diagram illustrates a flowchart of a TBOX communication reliability testing method provided in an embodiment of this application. This TBOX communication reliability testing method may include:

[0053] Step S101: Determine multiple target areas within the preset area range, and generate at least one test scenario based on the multiple target areas.

[0054] Here, the preset area range refers to the area range to be studied in this application. For example, the preset area range can be the country, province, city, or other area range where the vehicle containing the TBOX to be tested is currently located.

[0055] Considering the impact of roads and weather on TBOX communication, which can lead to unstable communication signals or Global Positioning System (GPS) signals on roads (the influencing factors for communication road testing can be summarized as weather and road conditions; weather conditions include cloudy days, rainy days, heavy fog, etc.; roads can be tunnels, tall buildings on both sides that block the view, overpasses, suspension bridges, etc.; these are specifically reflected on the TBOX as strong, weak, or no 4G signal and the presence or absence of GPS signal), we need to find areas with unstable communication signals and unstable GPS signals within a preset area, and then conduct tests based on these areas, which makes the test more targeted and efficient.

[0056] To conduct communication reliability testing on TBOX, it is necessary to ensure that the GPS signal is the same in each test scenario. That is, in any test scenario, either all target areas have GPS signals, or none of the target areas have GPS signals.

[0057] Meanwhile, in order to conduct communication reliability testing on TBOX in a test scenario, it is necessary to ensure that the communication signal in the test scenario is unstable, that is, the communication signal strength of the test scenario needs to switch, and the communication signal strength of each target area included in the test scenario is different.

[0058] Therefore, in order to generate at least one test scenario capable of performing communication reliability testing on TBOX, this application first determines multiple target areas within a preset area range, wherein the GPS signal and / or communication signal strengths of any two target areas are different.

[0059] For example, optionally, multiple target regions include: a first target region, a second target region, a third target region, a fourth target region, a fifth target region, and a sixth target region.

[0060] The target areas are categorized based on the presence or absence of GPS signals: GPS signals are present in the first, second, and third target areas, while GPS signals are absent in the fourth, fifth, and sixth target areas. Here, the presence of a GPS signal indicates that a GPS signal can be detected within that area, while the absence of a GPS signal indicates that a GPS signal cannot be detected within that area.

[0061] The communication signal strength within a given area is categorized as follows: the communication signal strength of the first and fourth target areas is defined as the first strength; the communication signal strength of the second and fifth target areas is defined as the second strength; and the communication signal strength of the third and sixth target areas is defined as the third strength. Here, the first strength is greater than or equal to a preset first threshold, the second strength is less than the first threshold but greater than or equal to a preset second threshold, and the third strength is less than the second threshold.

[0062] It should be noted that the first and second thresholds mentioned above can be set according to actual conditions, and this application does not limit them. For example, in an optional embodiment, the first threshold is -95 and the second threshold is -115.

[0063] For ease of subsequent description, this application defines the first target area as an area with GPS signal and strong communication signal; the second target area as an area with GPS signal and weak communication signal; the third target area as an area with GPS signal and no communication signal; the fourth target area as an area without GPS signal and strong communication signal; the fifth target area as an area without GPS signal and weak communication signal; and the sixth target area as an area without GPS signal and no communication signal.

[0064] This application allows for the arrangement and combination of multiple target areas based on actual testing needs to generate at least one test scenario. Here, each test scenario includes at least two target areas; at least one test scenario includes a scenario where communication signal strength switches when GPS signal is available, and / or a scenario where communication signal strength switches when GPS signal is unavailable.

[0065] For example, optionally, taking the above six target areas as an example, at least one test scenario includes: a test scenario in which a vehicle with a TBOX installed enters a second target area from a first target area and then returns to the first target area; a test scenario in which a vehicle with a TBOX installed enters a third target area from a first target area and then returns to the first target area; a test scenario in which a vehicle with a TBOX installed enters a second and a third target area sequentially from a first target area and then returns to a second and a first target area sequentially; a test scenario in which a vehicle with a TBOX installed enters a fifth target area from a fourth target area and then returns to a fourth target area; a test scenario in which a vehicle with a TBOX installed enters a sixth target area from a fourth target area and then returns to a fourth target area; and a test scenario in which a vehicle with a TBOX installed enters a fifth and a sixth target area sequentially from a fourth target area and then returns to a fifth and a fourth target area sequentially.

[0066] That is, at least one test scenario includes: with GPS signal, a first target area with strong communication signal → a second target area with weak communication signal → a first target area with strong communication signal; with GPS signal, a first target area with strong communication signal → a third target area without communication signal → a first target area with strong communication signal; with GPS signal, a first target area with strong communication signal → a second target area with weak communication signal → a third target area without communication signal → a second target area with weak communication signal → a first target area with strong communication signal.

[0067] At least one test scenario also includes: without GPS signal, the fourth target area with strong communication signal → the fifth target area with weak communication signal → the fourth target area with strong communication signal; without GPS signal, the fourth target area with strong communication signal → the sixth target area with no communication signal → the fourth target area with strong communication signal; without GPS signal, the fourth target area with strong communication signal → the fifth target area with weak communication signal → the sixth target area with no communication signal → the fifth target area with weak communication signal → the fourth target area with strong communication signal.

[0068] Optionally, the aforementioned communication signal can be a 4G signal.

[0069] Step S102: Obtain the total number of tests corresponding to at least one test scenario.

[0070] Specifically, the total number of tests varies depending on the version of the TBOX being tested. Specifically, when the TBOX being tested is version 1, the total number of tests is a preset number, for example, 82 tests. When the TBOX being tested is version 2, the total number of tests is a predetermined minimum number of tests required for at least one TBOX failure to occur.

[0071] The aforementioned second version refers to the first version of TBOX, and the second version is an updated version after the first version.

[0072] Step S103: Perform multiple communication reliability tests on the TBOX in each test scenario. Record the current number of tests during each test. When the test results indicate a TBOX failure, include the failure in the total number of failures. When the current number of tests in each test scenario reaches the corresponding total number of tests, end the test for each test scenario.

[0073] As described in the preceding steps, each test scenario includes at least two target areas. This application allows vehicles equipped with TBOX to shuttle back and forth between at least two target areas to test the TBOX communication reliability in each test scenario.

[0074] In this application, for each test scenario, a corresponding total number of tests can be performed, and the total number of TBOX failures in these tests can be recorded in order to determine the communication reliability of the TBOX.

[0075] Specifically, in each test scenario, the current test count is incremented by 1 each time a communication reliability test is performed on the TBOX. After the test is completed, if a failure is detected, the failure is either a TBOX failure or a backend server failure. This application can include the failure in the total failure count if the test result indicates a TBOX failure, i.e., increment the current total failure count by 1. For each test scenario, the initial current test count and the initial total failure count are both 0.

[0076] For each test scenario, after each test, this application will compare the current number of tests with the total number of tests corresponding to that test scenario. If the current number of tests is less than the total number of tests corresponding to that test scenario, the communication reliability test will continue to be performed on the TBOX. If the current number of tests is equal to the total number of tests corresponding to that test scenario, the test for that test scenario will end.

[0077] The TBOX communication reliability testing method provided in this application takes into account that roads and weather mainly affect communication and GPS signals. Therefore, this application first determines multiple target areas within a preset area based on GPS and communication signal strength, and generates at least one test scenario based on these target areas, covering all necessary testing scenarios and making the testing more comprehensive. This application can also obtain the total number of tests corresponding to each of the at least one test scenario. After the TBOX version is updated, the total number of tests is the pre-determined minimum number of tests required for at least one TBOX failure. This significantly shortens the testing mileage and time, reducing testing costs. Furthermore, the pre-generated test scenarios allow for targeted TBOX communication reliability testing within these scenarios, further reducing testing mileage and time and lowering testing costs.

[0078] One embodiment of this application describes the process of determining multiple target areas within a preset area range in step S101.

[0079] Those skilled in the art should understand that the log data of the TBOX has a dedicated field for recording the GPS signal and communication signal of the area where the vehicle is located. In this embodiment, the field for recording the GPS signal is defined as the first field, and the field for recording the communication signal is defined as the second field. Then, the process of "determining multiple target areas within a preset area range" may include: when the vehicle with the TBOX installed is within a preset area range, acquiring the log data of the TBOX; determining the area with GPS signal and the area without GPS signal within the preset area range based on the first field in the log data; determining the first target area, the second target area, and the third target area from the area with GPS signal based on the second field in the log data; and determining the fourth target area, the fifth target area, and the sixth target area from the area without GPS signal.

[0080] For example, taking a 4G communication signal as an example, the first and second fields in the TBOX log printout are shown in Table 1.

[0081] Table 1 shows the first and second fields in the TBOX log print.

[0082]

[0083] As shown in Table 1 above, the first field refers to the "gps status" field. A value of "GPS_FUNCTION_INVALID" indicates no GPS signal, while a value of "GPS_FUNCTION_VALID" indicates a GPS signal. The second field refers to the "rsrp" field. A value greater than or equal to -95 (i.e., the first strength threshold) indicates a strong signal, a value between -115 and 95 indicates a weak signal, and a value less than -115 (i.e., the second strength threshold) indicates no signal.

[0084] Of course, Table 1 above is only an example and is not intended to limit this application.

[0085] This application can identify areas with GPS signals and areas without GPS signals within a preset area based on the first field of the TBOX log data when the vehicle is within that area. Optionally, areas with GPS signals can typically be found on mountain roads or near areas without 4G base stations, while areas without GPS signals can be found in underground parking garages. Next, based on the second field of the TBOX log data, three target areas are identified: areas with strong communication signals, areas with weak communication signals, and areas with no communication signals when there is no GPS signal. Similarly, three target areas are identified: areas with strong communication signals, areas with weak communication signals, and areas with no communication signals when there is GPS signal. This yields the six target areas required by this application.

[0086] Optionally, after finding the target area required for this application, multiple target areas can be recorded by positioning or taking pictures as a reference for the next communication reliability test.

[0087] This application considers the impact of roads and weather on TBOX communication, summarizes multiple target areas with varying communication signal strength and the presence or absence of GPS signals, and generates at least one test scenario that may be involved in the actual vehicle driving process based on multiple target areas. This allows for dedicated communication reliability testing under the generated test scenario, without limitations on total mileage and time, greatly reducing time and monetary costs.

[0088] The following embodiment illustrates the process of performing communication reliability testing on the TBOX in each test scenario in step S103.

[0089] In one possible implementation, when the vehicle enters an area where the communication signal strength changes, the vehicle can be allowed to idle for a period of time. During this period, a communication reliability test of the TBOX can be performed to determine whether the TBOX can communicate normally with the backend server.

[0090] Specifically, the process of conducting communication reliability testing on the TBOX in each test scenario in this application may include:

[0091] When a vehicle moves from the first target area to the second target area, or from the fourth target area to the fifth target area, the vehicle is kept idling for a first duration. If communication between the TBOX and the backend server is abnormal during the first duration, the system determines whether the current fault is a TBOX fault based on the TBOX log data and the vehicle's controller area network CAN message data.

[0092] When a vehicle enters the third target area from the first or second target area, or enters the sixth target area from the fourth or fifth target area, the vehicle is kept idling for a first duration. During the first duration, it is determined whether the TBOX and the backend server are unable to communicate.

[0093] When a vehicle enters the first target area from the second or third target area, or enters the fourth target area from the fifth or sixth target area, or enters the second target area from the third target area, or enters the fifth target area from the sixth target area, if the TBOX fails to recover to the corresponding communication signal strength within the second time period, or if the communication between the TBOX and the backend server is abnormal during the first time period when the vehicle is idling, the current fault is determined to be a TBOX fault based on the TBOX log data and CAN message data.

[0094] Specifically, for the test scenario where the vehicle moves from the first target area to the second target area and back to the first target area (i.e., with GPS signal available, the test scenario involves the first target area with strong communication signal -> the second target area with weak communication signal -> the first target area with strong communication signal), when the vehicle enters the second target area, the idle speed is started for the first duration. During the first duration, the communication between the TBOX and the backend server is monitored. If an anomaly occurs in the communication between the two, the TBOX log data and the vehicle's controller area network CAN message data are used to determine whether the current fault occurs in the TBOX or the backend server through a comprehensive analysis of TBOX log printing and CAN data messages.

[0095] Within the second time period after the vehicle moves from the second target area to the first target area after the first time period, the communication signal of the TBOX changes from the second communication signal strength to the first communication signal strength, as observed by the TBOX log printout. Furthermore, if there are no abnormalities in the communication between the backend server and the TBOX during the first time period of vehicle idling, it indicates that there is currently no fault. Conversely, if the TBOX communication signal does not recover to the first communication signal strength within the second time period, or if there are abnormalities in the communication between the TBOX and the backend server during the first time period of vehicle idling, it indicates that a fault exists. Therefore, based on the TBOX log data and CAN message data, a comprehensive analysis method combining TBOX log printouts and CAN data messages is used to determine whether the current fault occurs in the TBOX or the backend server.

[0096] In this application, if either of the two processes determines that the TBOX is faulty, the total number of TBOX faults is incremented by 1; otherwise, if neither process determines that the TBOX is faulty, the total number of TBOX faults is not counted.

[0097] Similarly, for the test scenario where the vehicle enters the third target area from the first target area and then returns to the first target area, that is, in the case of GPS signal, the test scenario is: first target area with strong communication signal -> third target area with no communication signal -> first target area with strong communication signal. When the vehicle enters the third target area, the idle speed starts to time the first duration. During the first duration, the communication between the TBOX and the backend server is monitored. Since there is no communication signal in the third target area, theoretically, the TBOX and the backend server cannot communicate during the first duration.

[0098] Within the second time period before the vehicle enters the first target area from the third target area after the first time period, the communication signal of the TBOX changes to the first communication signal strength as observed by the TBOX log printout. Furthermore, if there are no abnormalities in the communication between the backend server and the TBOX during the first time period of vehicle idling, it indicates that there is currently no fault. Conversely, if the TBOX communication signal does not recover to the first communication signal strength within the second time period, or if there are abnormalities in the communication between the TBOX and the backend server during the first time period of vehicle idling, it indicates that a fault exists. Therefore, based on the TBOX log data and CAN message data, a comprehensive analysis method combining TBOX log printouts and CAN data messages is used to determine whether the current fault occurs in the TBOX or the backend server.

[0099] In this test scenario, if a TBOX failure is confirmed, the total number of TBOX failures is incremented by 1; otherwise, if a TBOX failure is not confirmed, no action is taken on the total number of TBOX failures.

[0100] Similarly, for the test scenario where the vehicle sequentially enters the second and third target areas from the first target area, and then returns to the second and first target areas in sequence (i.e., with GPS signal available, the test scenario is: first target area with strong communication signal -> second target area with weak communication signal -> third target area with no communication signal -> second target area with weak communication signal -> first target area with strong communication signal), when the vehicle enters the second target area, the idle speed is started for the first duration. During the first duration, the communication between the TBOX and the backend server is monitored. If an anomaly occurs in the communication between the two, the TBOX log data and the vehicle's controller area network CAN message data are used to determine whether the current fault occurs in the TBOX or the backend server, based on the TBOX log data and the vehicle's controller area network CAN message data.

[0101] After the first time interval, the vehicle moves from the second target area to the third target area, and the idle timer starts for the first time interval. During the first time interval, the communication between the TBOX and the backend server is monitored. Since there is no communication signal in the third target area, theoretically, the TBOX and the backend server cannot communicate during the first time interval.

[0102] After entering the third target area for the first period, and before the vehicle enters the second target area, the communication signal of the TBOX changes to the second communication signal strength during the second period, as observed by the TBOX log printout. If the communication between the backend server and the TBOX remains normal during the first period of vehicle idling, it indicates no fault. Conversely, if the TBOX communication signal fails to recover to the second communication signal strength during the second period, or if the communication between the TBOX and the backend server becomes abnormal during the first period of vehicle idling, it indicates a fault. Therefore, based on the TBOX log data and CAN message data, a comprehensive analysis method combining TBOX log printouts and CAN data messages is used to determine whether the fault originates in the TBOX or the backend server.

[0103] After the vehicle enters the second target area for a first period of time, and then travels from the second target area to the first target area for a second period of time, the communication signal of the TBOX changes to the first communication signal strength according to the log printout of the TBOX. If the communication between the backend server and the TBOX remains normal during the first period of vehicle idling, it indicates that there is no fault. Conversely, if the TBOX communication signal does not recover to the first communication signal strength within the second period of time, or if the communication between the TBOX and the backend server becomes abnormal during the first period of vehicle idling, it indicates that a fault exists. Therefore, based on the TBOX log data and CAN message data, a comprehensive analysis method combining TBOX log printing and CAN data message analysis is used to determine whether the fault originates in the TBOX or the backend server.

[0104] In this test scenario, if a TBOX failure is determined in any process, the total number of TBOX failures is incremented by 1; otherwise, if a TBOX failure is not determined, no action is taken on the total number of TBOX failures.

[0105] For the three test scenarios without GPS signal, the specific test procedures correspond one-to-one with the three test scenarios with GPS signal. For details, please refer to the test procedures for the three test scenarios with GPS signal mentioned above, which will not be repeated here.

[0106] In an optional embodiment, the process of whether the TBOX and the backend server are communicating abnormally can be determined by whether the TBOX periodically reports vehicle condition information and whether the backend server successfully issues a vehicle condition query command.

[0107] Specifically, if the TBOX fails to periodically report vehicle status information or the backend server fails to successfully issue a vehicle status query command within the first time period, it is determined that there is an abnormality in the communication between the TBOX and the backend server. If the TBOX can periodically report vehicle status information and the backend server can successfully issue a vehicle status query command within the first time period, it is determined that the communication between the TBOX and the backend server is normal.

[0108] In another possible implementation, when the vehicle enters an area where the communication signal strength changes, it can be put into hibernation for a period of time and then powered on again. After powering on, it can be idled for a period of time, and during this period, the communication reliability test of the TBOX can be performed to determine whether the TBOX can communicate normally with the backend server.

[0109] Specifically, the process of conducting communication reliability testing on the TBOX in each test scenario in this application may include:

[0110] When the vehicle moves from the first target area to the second target area, or from the fourth target area to the fifth target area, the vehicle is put into sleep mode for a third period of time and then powered on again. After powering on, the vehicle idles for a first period of time. If communication between the TBOX and the backend server is abnormal during the first period of time, the system determines whether the current fault is a TBOX fault based on the TBOX log data and the vehicle's controller area network CAN message data.

[0111] When a vehicle enters the third target area from the first or second target area, or enters the sixth target area from the fourth or fifth target area, the vehicle is put into sleep mode for a third period of time and then powered on again. After powering on, the vehicle idles for a first period of time. During the first period of time, it is determined whether the TBOX and the backend server are unable to communicate.

[0112] When a vehicle enters the first target area from the second or third target area, or the fourth target area from the fifth or sixth target area, or the second target area from the third target area, or the fifth target area from the sixth target area, the vehicle is put into sleep mode for a third period and then powered on again. If the TBOX fails to recover to the corresponding communication signal strength within the second period after power-on, or if the communication between the TBOX and the backend server is abnormal within the first period of idling after power-on, the current fault is determined to be a TBOX fault based on the TBOX log data and CAN message data.

[0113] Optionally, the first duration is 15 minutes, the second duration is 30 seconds, and the third duration is 15 minutes. Of course, in this application, the first, second, and third durations can also be other, and no specific limitation is made here.

[0114] The process in this embodiment is similar to the test process for the first idling time of the vehicle described above. For details, please refer to the above description, which will not be repeated here.

[0115] The following specific example is provided to help those skilled in the art better understand this application.

[0116] Taking 4G communication signals as an example, see Figure 2 The diagram illustrates the 4G communication reliability testing process of the automotive TBOX provided in this embodiment of the application.

[0117] Step S201: Generate 6 test scenarios with permutations and combinations of 4G signal strength, weakness, and absence, and GPS signal presence or absence.

[0118] The process of this step corresponds to the aforementioned step S101. Please refer to the description in the aforementioned step S101 for details, which will not be repeated here.

[0119] Step S202: Drive the vehicle into one of the six test scenarios.

[0120] For each test scenario, follow these steps.

[0121] Step S203: Monitor the 4G communication data between the backend server and TBOX and issue vehicle status query commands to determine if there is a communication abnormality.

[0122] In case of an abnormal situation, proceed to step S204; otherwise, proceed to step S206.

[0123] Step S204: Analyze the CAN messages and TBOX logs to determine whether the current fault belongs to the TBOX or the backend server.

[0124] If the current fault occurs in the TBOX, proceed to step S205. If the current fault does not occur in the TBOX, i.e., if the current fault occurs in the backend server, proceed to step S206.

[0125] Step S205: Increment the total number of failures by 1, and increment the current number of tests by 1.

[0126] The initial total number of failures is 0, and the initial number of current tests is 0.

[0127] Step S206: Increment the current number of tests by 1.

[0128] Step S207: Determine whether the current number of tests is equal to the total number of tests corresponding to the current test scenario.

[0129] If the current number of tests equals the total number of tests for the current test scenario, end the test in the current test scenario and move the vehicle to the next test scenario, until all test scenarios have been completed.

[0130] If the current number of tests is not equal to the total number of tests corresponding to the current test scenario, proceed to step S208.

[0131] Step S208: Proceed to the next test in the current test scenario.

[0132] Specifically, if the current number of tests is not equal to the total number of tests corresponding to the current test scenario, this application will proceed to the next test under the current test scenario and return to step S203.

[0133] For details not described in this embodiment, please refer to the descriptions in the foregoing embodiments.

[0134] In some embodiments of this application, when the TBOX being tested is version 1, the process of determining the minimum number of tests required for at least one TBOX failure to occur in each of the at least one test scenarios after a version update is described.

[0135] Specifically, the process may include:

[0136] Step S301: Based on the total number of tests, the total number of failures after the test, and the preset confidence level corresponding to at least one test scenario, determine the confidence interval corresponding to at least one test scenario.

[0137] Optionally, the process of "determining the confidence intervals corresponding to at least one test scenario based on the total number of tests, the total number of failures after the test, and the preset confidence level for each test scenario" may include: calculating the sample proportions corresponding to at least one test scenario based on the total number of tests and the total number of failures after the test; and calculating the confidence intervals corresponding to at least one test scenario based on the sample proportions, the total number of tests, and the confidence level for each test scenario.

[0138] Optionally, this application can calculate the sample proportion according to the formula p = x / n, where x represents the total number of failures after the test, n represents the total number of tests, and p represents the sample proportion.

[0139] Optionally, this application can be based on the formula To calculate the confidence interval, we use the formula where 1.96 is the key value corresponding to a 95% confidence level.

[0140] Referring to Table 2 below, the total number of failures corresponding to the six test scenarios provided in this application are 7, 9, 6, 8, 12 and 5 respectively. Taking the total number of tests corresponding to the six test scenarios as 82 and the confidence level as 95% as an example, the confidence intervals calculated by this application are as follows: [0.025, 0.146], [0.041, 0.178], [0.016, 0.13], [0.032, 0.162], [0.07, 0.223] and [0.009, 0.113].

[0141] Table 26 Fault Records for Test Scenarios

[0142]

[0143] Step S302: Determine the minimum number of tests corresponding to at least one test scenario based on the confidence interval and total number of tests corresponding to each of the at least one test scenario.

[0144] Taking Table 2 above as an example, the minimum number of tests required for at least one TBOX failure to occur under the six test scenarios obtained in this application are 7, 6, 8, 8, 5 and 9, respectively.

[0145] In this embodiment of the application, after testing at least one test scenario generated above, the total number of faults belonging to TBOX and the total number of tests are recorded to obtain the fault probability. Then, the confidence interval for each test scenario is calculated using the confidence level, thereby obtaining the minimum number of tests required for one fault to occur, in order to guide the 4G reliability communication testing of subsequent TBOX version iterations.

[0146] This application sets up six test scenarios to conduct communication reliability tests on the TBOX, which can basically cover all possible scenarios during vehicle operation on roads. This application has at least the following beneficial effects:

[0147] First, it shortens the testing time and distance, reducing time and financial costs. This application covers the impact of road weather and roads on 4G communication by designing six scenarios, eliminating the need for long-duration and long-distance road tests, and allowing for more targeted testing of the reliability of 4G communication.

[0148] Secondly, it improved the 4G communication fault detection rate of TBOX. Through the initial testing of six scenarios, the minimum number of tests required for a single fault can be calculated based on the fault rate and confidence level, thereby reducing unnecessary tests. This guides the 4G reliability testing of TBOX iterations and significantly improves the fault detection rate in the six scenarios.

[0149] This application also provides a TBOX communication reliability testing device. The TBOX communication reliability testing device provided in this application is described below. The TBOX communication reliability testing device described below can be referred to in correspondence with the TBOX communication reliability testing method described above.

[0150] Please see Figure 3 This document illustrates a schematic diagram of the TBOX communication reliability testing device provided in an embodiment of this application. Figure 3 As shown, the TBOX communication reliability testing device may include: a test scenario generation module 301, a total number of tests acquisition module 302, and a communication reliability testing module 303.

[0151] The test scenario generation module 301 is used to determine multiple target areas within a preset area range and generate at least one test scenario based on the multiple target areas. The GPS signal and / or communication signal strength of any two target areas are different. At least one test scenario includes a scenario where the communication signal strength switches when there is a GPS signal and / or a scenario where the communication signal strength switches when there is no GPS signal.

[0152] The test total number acquisition module 302 is used to acquire the total number of tests corresponding to at least one test scenario. When the remote information processor TBOX being tested is version 1, the total number of tests is a preset number. When the TBOX being tested is version 2, the total number of tests is a predetermined minimum number of tests required for at least one TBOX failure to occur. Version 2 is a version updated after version 1.

[0153] The communication reliability test module 303 is used to perform multiple communication reliability tests on the TBOX in each test scenario. It records the current number of tests during each test and includes the failure in the total number of failures when the test results indicate a failure of the TBOX. The test in each test scenario ends when the current number of tests in each test scenario reaches the corresponding total number of tests.

[0154] In one possible implementation, the aforementioned multiple target regions may include: a first target region, a second target region, a third target region, a fourth target region, a fifth target region, and a sixth target region;

[0155] GPS signals are present in the first, second, and third target areas, while GPS signals are absent in the fourth, fifth, and sixth target areas. The presence of a GPS signal in one area indicates that a GPS signal can be detected in that area, while the absence of a GPS signal in one area indicates that a GPS signal cannot be detected in that area.

[0156] The communication signal strength of the first target area and the fourth target area is the first strength, the communication signal strength of the second target area and the fifth target area is the second strength, and the communication signal strength of the third target area and the sixth target area is the third strength;

[0157] The first intensity is greater than or equal to a preset first threshold, the second intensity is less than the first threshold but greater than or equal to a preset second threshold, and the third intensity is less than the second threshold.

[0158] In one possible implementation, the process by which the test scenario generation module determines multiple target regions within a preset area may include:

[0159] When the vehicle with the TBOX installed is within a preset area, retrieve the TBOX log data;

[0160] Based on the first field in the log data, determine the areas with GPS signals and the areas without GPS signals within the preset area;

[0161] Based on the second field in the log data, the first, second, and third target areas are determined from the areas with GPS signals, and the fourth, fifth, and sixth target areas are determined from the areas without GPS signals.

[0162] In one possible implementation, at least one of the above test scenarios may include:

[0163] The test scenario involves a vehicle equipped with a TBOX moving from the first target area to the second target area and then back to the first target area.

[0164] The test scenario in which a vehicle equipped with a TBOX enters the third target area from the first target area and then returns to the first target area;

[0165] The test scenario involves vehicles equipped with TBOX sequentially entering the second and third target areas from the first target area, and then sequentially returning to the second and first target areas.

[0166] The test scenario in which a vehicle equipped with a TBOX enters the fifth target area from the fourth target area and then returns to the fourth target area;

[0167] The test scenario involves a vehicle equipped with a TBOX entering the sixth target area from the fourth target area and then returning to the fourth target area.

[0168] The test scenario involves a vehicle equipped with a TBOX moving sequentially from the fourth target area to the fifth and sixth target areas, and then returning sequentially to the fifth and fourth target areas.

[0169] In one possible implementation, the communication reliability testing module described above, in each test scenario, performs communication reliability testing on the TBOX, which may include:

[0170] When a vehicle moves from the first target area to the second target area, or from the fourth target area to the fifth target area, the vehicle is kept idling for a first duration. If communication between the TBOX and the backend server is abnormal during the first duration, the system determines whether the current fault is a TBOX fault based on the TBOX log data and the vehicle's controller area network CAN message data.

[0171] When a vehicle enters the third target area from the first or second target area, or enters the sixth target area from the fourth or fifth target area, the vehicle is kept idling for a first duration. During the first duration, it is determined whether the TBOX and the backend server are unable to communicate.

[0172] When a vehicle enters the first target area from the second or third target area, or enters the fourth target area from the fifth or sixth target area, or enters the second target area from the third target area, or enters the fifth target area from the sixth target area, if the TBOX fails to recover to the corresponding communication signal strength within the second time period, or if the communication between the TBOX and the backend server is abnormal during the first time period when the vehicle is idling, the current fault is determined to be a TBOX fault based on the TBOX log data and CAN message data.

[0173] In one possible implementation, the communication reliability testing module described above, in each test scenario, performs communication reliability testing on the TBOX, which may include:

[0174] When the vehicle moves from the first target area to the second target area, or from the fourth target area to the fifth target area, the vehicle is put into sleep mode for a third period of time and then powered on again. After powering on, the vehicle idles for a first period of time. If communication between the TBOX and the backend server is abnormal during the first period of time, the system determines whether the current fault is a TBOX fault based on the TBOX log data and the vehicle's controller area network CAN message data.

[0175] When a vehicle enters the third target area from the first or second target area, or enters the sixth target area from the fourth or fifth target area, the vehicle is put into sleep mode for a third period of time and then powered on again. After powering on, the vehicle idles for a first period of time. During the first period of time, it is determined whether the TBOX and the backend server are unable to communicate.

[0176] When a vehicle enters the first target area from the second or third target area, or the fourth target area from the fifth or sixth target area, or the second target area from the third target area, or the fifth target area from the sixth target area, the vehicle is put into sleep mode for a third period and then powered on again. If the TBOX fails to recover to the corresponding communication signal strength within the second period after power-on, or if the communication between the TBOX and the backend server is abnormal within the first period of idling after power-on, the current fault is determined to be a TBOX fault based on the TBOX log data and CAN message data.

[0177] In one possible implementation, if the TBOX fails to periodically report vehicle status information or the backend server fails to successfully issue a vehicle status query command within the first time period, it is determined that there is an abnormality in the communication between the TBOX and the backend server.

[0178] In one possible implementation, when the TBOX being tested is a first version, the TBOX communication reliability testing device provided in this application may further include: a confidence interval determination module and a minimum number of tests determination module.

[0179] The confidence interval determination module is used to determine the confidence intervals corresponding to at least one test scenario based on the total number of tests, the total number of failures after the test, and the preset confidence level.

[0180] The minimum number of tests determination module is used to determine the minimum number of tests corresponding to at least one test scenario based on the confidence interval and the total number of tests corresponding to at least one test scenario.

[0181] In one possible implementation, the process by which the confidence interval determination module determines the confidence intervals corresponding to at least one test scenario based on the total number of tests corresponding to at least one test scenario, the total number of failures after the test, and a preset confidence level may include:

[0182] Calculate the sample proportion corresponding to each of the at least one test scenario based on the total number of tests and the total number of failures after the test.

[0183] Calculate the confidence intervals for each of the at least one test scenario based on the sample proportion, total number of tests, and confidence level.

[0184] This application also provides a TBOX communication reliability testing device. Optionally, Figure 4 The hardware structure block diagram of the TBOX communication reliability testing equipment is shown below. Figure 4The hardware structure of the TBOX communication reliability testing device may include: at least one processor 1, at least one communication interface 2, at least one memory 3, and at least one communication bus 4;

[0185] In this embodiment of the application, the number of processor 1, communication interface 2, memory 3, and communication bus 4 is at least one, and processor 1, communication interface 2, and memory 3 communicate with each other through communication bus 4;

[0186] Processor 1 may be a central processing unit (CPU), an application-specific integrated circuit (ASIC), or one or more integrated circuits configured to implement embodiments of the present invention.

[0187] Memory 3 may include high-speed RAM, and may also include non-volatile memory, such as at least one disk storage device;

[0188] The memory 3 stores a program, and the processor 1 can call the program stored in the memory 3. The program is used for:

[0189] Multiple target areas are identified within a preset area, and at least one test scenario is generated based on the multiple target areas. The GPS signal and / or communication signal strength of any two target areas are different. At least one test scenario includes a scenario where the communication signal strength switches when there is a GPS signal and / or a scenario where the communication signal strength switches when there is no GPS signal.

[0190] Obtain the total number of tests corresponding to at least one test scenario. When the remote information processor TBOX being tested is version 1, the total number of tests is a preset number. When the TBOX being tested is version 2, the total number of tests is a predetermined minimum number of tests required for at least one TBOX failure to occur. Version 2 refers to versions updated after version 1.

[0191] In each test scenario, the TBOX is subjected to multiple communication reliability tests. The current number of tests is recorded at each test. When the test results indicate that the TBOX is faulty, the fault is included in the total number of faults. The test for each test scenario ends when the current number of tests in each test scenario reaches the corresponding total number of tests.

[0192] Optionally, the refined and extended functions of the program can be found in the description above.

[0193] This application also provides a readable storage medium storing a computer program thereon, which, when executed by a processor, implements the TBOX communication reliability testing method described above.

[0194] Optionally, the refined and extended functions of the program can be found in the description above.

[0195] Finally, it should be noted that in this document, relational terms such as "second" and "etc." are used merely 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 a process, method, article, or apparatus. Without further limitations, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or apparatus that includes said element.

[0196] The various embodiments in this specification are described in a progressive manner, with each embodiment focusing on the differences from other embodiments. The same or similar parts between the various embodiments can be referred to each other.

[0197] The above description of the disclosed embodiments enables those skilled in the art to make or use this application. Various modifications to these embodiments will be readily apparent to those skilled in the art, and the general principles defined herein may be implemented in other embodiments without departing from the spirit or scope of this application. Therefore, this application is not to be limited to the embodiments shown herein, but is to be accorded the widest scope consistent with the principles and novel features disclosed herein.

Claims

1. A TBOX communication reliability test method, characterized in that, The method comprises the following steps: determining a plurality of target areas within a preset area range, and generating at least one test scene according to the plurality of target areas, wherein the global positioning system (GPS) signal and / or the communication signal strength of any two target areas are different, the at least one test scene comprises a scene of communication signal strength switching in the presence of a GPS signal and / or a scene of communication signal strength switching in the absence of a GPS signal; obtaining a total test number corresponding to each test scene, wherein when a current test remote information processor (TBOX) is a first version, the total test number is a preset number, and when the current test TBOX is a second version, the total test number is a minimum test number in which at least one TBOX failure occurs, and the second version is a version updated after the first version; performing a plurality of communication reliability tests on the TBOX under each test scene, recording a current test number at each test, and counting a total failure number when a test result represents a TBOX failure, and ending the test under each test scene when the current test number under each test scene reaches the corresponding total test number; performing a communication reliability test on the TBOX under each test scene, comprising: when a vehicle enters an area in which the communication signal strength switches, making the vehicle idle for a period of time, and in the case that the communication between the TBOX and the background server is abnormal in the period of time, determining whether the current failure is a TBOX failure according to log data of the TBOX and controller area network (CAN) message data of the vehicle.

2. The TBOX communication reliability test method according to claim 1, wherein, The plurality of target areas comprises a first target area, a second target area, a third target area, a fourth target area, a fifth target area, and a sixth target area; the first target area, the second target area, and the third target area have GPS signals, and the fourth target area, the fifth target area, and the sixth target area have no GPS signals, wherein the presence of a GPS signal in an area indicates that the GPS signal can be detected in the area, and the absence of a GPS signal in an area indicates that the GPS signal cannot be detected in the area; the communication signal strength of the first target area and the fourth target area is a first strength, the communication signal strength of the second target area and the fifth target area is a second strength, and the communication signal strength of the third target area and the sixth target area is a third strength; the first strength is greater than or equal to a preset first threshold value, the second strength is less than the first threshold value and greater than or equal to a preset second threshold value, and the third strength is less than the second threshold value.

3. The TBOX communication reliability test method according to claim 2, characterized in that, The determination of the plurality of target areas within the preset area range comprises: obtaining log data of the TBOX when the vehicle in which the TBOX is installed is in the preset area range; determining areas in which there are GPS signals and areas in which there are no GPS signals within the preset area range according to a first field in the log data; The first target area, the second target area and the third target area are determined from the GPS signal area according to the second field in the log data, and the fourth target area, the fifth target area and the sixth target area are determined from the GPS signal-free area.

4. The TBOX communication reliability test method according to claim 2, characterized in that, The at least one test scenario includes: a test scenario in which a vehicle in which the TBOX is installed enters the second target area from the first target area and returns to the first target area; a test scenario in which the vehicle enters the third target area from the first target area and returns to the first target area; a test scenario in which the vehicle enters the second target area and the third target area from the first target area in sequence and returns to the second target area and the first target area in sequence; a test scenario in which the vehicle enters the fifth target area from the fourth target area and returns to the fourth target area; a test scenario in which the vehicle enters the sixth target area from the fourth target area and returns to the fourth target area; a test scenario in which the vehicle enters the fifth target area and the sixth target area from the fourth target area in sequence and returns to the fifth target area and the fourth target area in sequence.

5. The TBOX communication reliability test method according to claim 4, characterized in that, When the vehicle enters an area in which communication signal strength switches, the vehicle is caused to idle for a period of time, and in the case of an abnormality in communication between the TBOX and a background server in the period of time, whether the current fault is a TBOX fault is determined according to log data of the TBOX and controller area network (CAN) message data of the vehicle, including: When the vehicle enters the second target area from the first target area or enters the fifth target area from the fourth target area, the vehicle is caused to idle for a first time period, and in the case of an abnormality in communication between the TBOX and a background server in the first time period, whether the current fault is a TBOX fault is determined according to log data of the TBOX and controller area network (CAN) message data of the vehicle; When the vehicle enters the third target area from the first target area or the second target area or enters the sixth target area from the fourth target area or the fifth target area, the vehicle is caused to idle for the first time period, and whether the TBOX and the background server cannot communicate is determined in the first time period. In a case that the vehicle enters the first target area from the second target area or the third target area, or enters the fourth target area from the fifth target area or the sixth target area, or enters the second target area from the third target area, or enters the fifth target area from the sixth target area, and in a case that the TBOX does not recover to a corresponding communication signal strength within a second time length or the communication between the TBOX and the background server is abnormal within the first time length during which the vehicle is idling, it is determined whether the current fault is the TBOX fault according to the log data of the TBOX and the CAN message data.

6. The TBOX communication reliability test method according to claim 4, characterized in that, In a case that the vehicle enters a region in which the communication signal strength is switched, the vehicle is idled for a period of time, and in a case that the communication between the TBOX and the background server is abnormal within the period of time, it is determined whether the current fault is the TBOX fault according to the log data of the TBOX and the controller area network (CAN) message data of the vehicle, and the method comprises the following steps of: In a case that the vehicle enters the first target area from the second target area or the third target area, or enters the fourth target area from the fifth target area or the sixth target area, or enters the second target area from the third target area, or enters the fifth target area from the sixth target area, the vehicle is put into sleep for a third time length and then powered on, and in a case that the communication between the TBOX and the background server is abnormal within a first time length during which the vehicle is idling after being powered on, it is determined whether the current fault is the TBOX fault according to the log data of the TBOX and the controller area network (CAN) message data of the vehicle. In a case that the vehicle enters the first target area from the second target area or the third target area, or enters the fourth target area from the fifth target area or the sixth target area, or enters the second target area from the third target area, or enters the fifth target area from the sixth target area, the vehicle is put into sleep for a third time length and then powered on, and in a case that the communication between the TBOX and the background server is abnormal within a first time length during which the vehicle is idling after being powered on, it is determined whether the current fault is the TBOX fault according to the log data of the TBOX and the controller area network (CAN) message data of the vehicle. In a case that the vehicle enters the first target area from the second target area or the third target area, or enters the fourth target area from the fifth target area or the sixth target area, or enters the second target area from the third target area, or enters the fifth target area from the sixth target area, the vehicle is put into sleep for a third time length and then powered on, and in a case that the communication between the TBOX and the background server is abnormal within a first time length during which the vehicle is idling after being powered on, it is determined whether the current fault is the TBOX fault according to the log data of the TBOX and the controller area network (CAN) message data of the vehicle.

7. The TBOX communication reliability test method according to claim 5 or 6, characterized in that, In a case that the TBOX does not periodically report vehicle condition information within the first time length or the background server does not successfully issue a vehicle condition query command, it is determined that the communication between the TBOX and the background server is abnormal.

8. The TBOX communication reliability test method according to claim 1, wherein, In a case that the TBOX of the current test is the first version, the method further comprises: According to the total number of tests, the total number of faults after the test ends, and the preset confidence level corresponding to each of the at least one test scene, a confidence interval corresponding to each of the at least one test scene is determined; According to the confidence interval and the total number of tests corresponding to each of the at least one test scene, the minimum number of tests corresponding to each of the at least one test scene is determined.

9. The TBOX communication reliability test method according to claim 8, characterized in that, The method according to the total number of tests, the total number of faults after the test ends, and the preset confidence level corresponding to each of the at least one test scene, a confidence interval corresponding to each of the at least one test scene is determined, comprising: According to the total number of tests and the total number of faults after the test ends corresponding to each of the at least one test scene, a sample proportion corresponding to each of the at least one test scene is calculated; According to the sample proportion, the total number of tests, and the confidence level corresponding to each of the at least one test scene, a confidence interval corresponding to each of the at least one test scene is calculated.

10. A TBOX communication reliability test device, characterized by, Comprising: A test scene generation module is configured to determine a plurality of target regions within a preset area range, and generate at least one test scene according to the plurality of target regions, wherein the global positioning system (GPS) signal and / or the communication signal strength of any two target regions are different, the at least one test scene includes a scene of communication signal strength switching in the presence of a GPS signal and / or a scene of communication signal strength switching in the absence of a GPS signal; A total number of tests acquisition module is configured to acquire the total number of tests corresponding to each of the at least one test scene, wherein when a remote information processing unit (TBOX) currently being tested is a first version, the total number of tests is a preset number, and when the TBOX currently being tested is a second version, the total number of tests is a minimum number of tests for at least one TBOX fault, and the second version is an updated version after the first version; A communication reliability test module is configured to perform a plurality of communication reliability tests on the TBOX under each test scene, record the current number of tests at each test, and count the total number of faults when the test result represents a TBOX fault, and end the test under each test scene when the current number of tests under each test scene reaches the corresponding total number of tests; The communication reliability test module performs a communication reliability test on the TBOX under each test scene, comprising: When the vehicle enters a region with communication signal strength switching, the communication reliability test module makes the vehicle idle for a period of time, and according to the log data of the TBOX and the controller area network (CAN) message data of the vehicle, determines whether the current fault is a TBOX fault when the communication between the TBOX and the background server is abnormal during the period of time.

Images