A vehicle-mounted TBox LTE network anomaly monitoring and recovery method

Abstract

The application discloses a vehicle-mounted TBox LTE network anomaly monitoring and recovery method, relates to the technical field of vehicle-mounted telematics, and comprises the following steps: after the vehicle-mounted TBox is powered on, communication parameters are initialized and configured, public APN and private APN parameters are configured, an APN connection state change callback is registered, a network monitoring task is started, and the public APN connection state is periodically acquired; the data connection state is judged according to the public APN connection state; in the data connection opening state, an APN link state callback is registered, a default route, a private APN special route, a network address translation rule and domain name resolution configuration are configured. Through multi-dimensional network detection and four-stage progressive recovery strategies, the application realizes accurate judgment and hierarchical processing of vehicle-mounted TBox LTE network anomalies, optimizes the recovery process in combination with the vehicle state and the recovery number limit, reduces invalid reset operations, reduces power consumption, and improves the stability of vehicle-mounted communication.

Description

Technical Field

[0001] This application relates to the field of vehicle telematics technology, specifically to a method for monitoring and recovering anomalies in a vehicle-mounted TBox LTE network. Background Technology

[0002] With the rapid development of vehicle-to-everything (V2X) technology, the in-vehicle telematics box (TBox) has become a crucial communication device for information exchange between vehicles and cloud platforms. TBoxes typically integrate cellular communication modules, positioning modules, and data processing modules, enabling services such as vehicle status data uploading, remote fault diagnosis, vehicle location, remote control, emergency calls (eCall), and over-the-air (OTA) updates via mobile communication networks like LTE. To ensure the continuous and reliable operation of these V2X services, the TBox needs to maintain long-term data communication connections with the operator's network and cloud servers.

[0003] However, in actual vehicle operating environments, LTE network connectivity is susceptible to various factors, such as changes in operator network load, changes in base station coverage, frequent cell handovers caused by high-speed vehicle movement, weak signal environments such as underground garages or tunnels, communication module malfunctions, incorrect network configuration parameters, and abnormal data link status. These factors can all lead to TBox experiencing network connection interruptions, registration anomalies, data link failures, or "false connections" where the link appears to be connected but data communication is actually impossible.

[0004] Since connected vehicle applications typically involve vehicle safety, remote control, and real-time data interaction, the in-vehicle TBox needs to continuously monitor the LTE network status and automatically perform recovery operations when network anomalies occur, in order to improve the stability and reliability of the vehicle communication system.

[0005] Existing in-vehicle TBox network anomaly detection and recovery solutions typically employ relatively simple network detection and recovery mechanisms. After the vehicle is powered on, the TBox first loads the preset APN (Access Point Name) configuration and executes LTE network registration and data dialing procedures through the communication module to establish a data communication link between the vehicle and the external network. Once the data link is successfully established, the system initiates a periodic network detection task, sending Ping requests to a designated public server address at regular intervals and determining the current network status based on the Ping response results.

[0006] When multiple consecutive ping failures are detected, the system typically assumes an LTE network connection anomaly and further controls the communication module to perform a restart operation, or performs a power-off and power-on process on the communication module, causing it to re-register with the network, reload its configuration, and re-establish a data connection in order to restore normal communication. However, the existing solution still has significant shortcomings: First, network anomaly detection methods are relatively simplistic, typically relying solely on Ping results to determine network status. This fails to combine multi-dimensional information such as APN connection status, data link status, and network registration status to accurately identify the cause of the anomaly, easily leading to simplistic categorization of different types of problems, such as temporary network fluctuations, link anomalies, and module failures. Second, existing recovery methods usually involve directly restarting communication modules or resetting the system, lacking a gradual recovery mechanism from minor to major issues. This causes problems that could be resolved simply by redialing or re-establishing data links to be escalated into module restarts, increasing network recovery time and causing interruptions to real-time services such as remote control and emergency calls. Third, existing technologies typically do not independently monitor and recover multiple APN links. However, in actual vehicle-to-everything (V2X) systems, multiple communication links, including public and private APNs, may exist simultaneously, each handling different services. A single-link detection method cannot accurately pinpoint the specific fault location. Furthermore, existing solutions do not fully consider the impact of different vehicle power states on recovery strategies. Performing high-power module restarts or system resets when the vehicle is off and in low-power sleep mode disrupts the vehicle's power management strategy and increases battery consumption.

[0007] Therefore, existing vehicle-mounted TBox network anomaly recovery technologies still have room for improvement in terms of anomaly detection accuracy, recovery strategy rationality, service continuity assurance, and low power consumption control. A network anomaly monitoring and recovery method that can comprehensively analyze network status, perform graded recovery according to the degree of anomaly, and make intelligent decisions in conjunction with vehicle operating status is needed.

[0008] The information disclosed in the background section is only intended to enhance the understanding of the background of this disclosure, and therefore may include information that does not constitute prior art known to those skilled in the art. Summary of the Invention

[0009] The purpose of this application is to provide a method for detecting and recovering anomalies in an in-vehicle TBox LTE network, in order to solve the problems mentioned in the background art.

[0010] To achieve the above objectives, this application provides the following technical solution: a method for detecting and recovering anomalies in an in-vehicle TBox LTE network, comprising the following steps: After the vehicle-mounted TBox is powered on, it initializes and configures the communication parameters, configures the public APN and private APN parameters, registers APN connection status change callbacks, starts the network monitoring task, and periodically obtains the public APN connection status. The data connection status is determined based on the public APN connection status. When the data connection is enabled, the APN link status callback is registered, the default route, the private APN dedicated route, the network address translation rules and domain name resolution configuration are configured, and the dial-up connection status of the private APN and the public APN is detected. When any APN link is disconnected, the corresponding APN configuration loading and dial-up connection operation are performed. Based on the dial-up connection status of the private APN and the public APN, dual-link reachability detection is performed on the vehicle TBox LTE network. The private network server address is accessed through the private APN link, and the public network server address is accessed through the public APN link. The network anomaly count is updated according to the detection results. When the number of dual-link detection failures reaches a preset threshold, a link recovery operation is performed. Based on the execution result of the link recovery operation, the data connection between the private APN and the public APN is disconnected, the corresponding routing configuration and network connection rules are cleared, and the APN link establishment operation is re-executed. When the number of link recovery operations reaches a preset threshold, the radio frequency recovery operation is executed, and the radio frequency function is turned off and then turned back on by controlling the communication unit. Based on the results of the radio frequency recovery operation and the vehicle's operating status, determine whether to perform a system-level recovery operation. If the vehicle is powered on and the number of system recovery attempts has not reached the preset limit, perform a soft reset operation on the vehicle's TBox operating system. If the number of system recovery attempts reaches the preset limit, stop performing the system-level recovery operation.

[0011] When the network monitoring task acquires the public APN connection status, it simultaneously collects the private APN connection status, data connection switch status, and network registration status, and receives communication link status change information through the connection status change callback function; when a connection change is detected in any APN link, the corresponding APN link status record is updated, and network connection status is judged based on the updated link status.

[0012] Private APNs and public APNs correspond to different data communication paths. Private APNs access the vehicle service server through a dedicated route, while public APNs access the public network server through a default route. During network configuration, routing tables for private APNs and default routing tables for public APNs, as well as corresponding data forwarding rules, are established to ensure that different service data are transmitted according to preset communication paths.

[0013] During the dual-link reachability detection process, the vehicle-mounted TBox sends Ping detection requests to the private network server address through the private APN interface and to the public network server address through the public APN interface, and records the private network link detection results and the public network link detection results respectively. When either link is successfully detected, the continuous network anomaly count is cleared to zero. When both link detections fail, the number of consecutive anomalies is accumulated.

[0014] The link recovery operation includes releasing the current data bearer context, disconnecting the public APN connection, disconnecting the private APN connection, clearing the network routing configuration, deleting firewall rules, and releasing network connection resources. After the network resources are released, the public APN parameters and private APN parameters are reloaded, the dial-up connection request is re-initiated, and the link recovery result is determined based on the APN connection status.

[0015] The radio frequency recovery operation is performed through the AT control interface provided by the communication unit, including sending the radio frequency shutdown command AT+CFUN=0 to shut down the radio frequency function of the communication unit, and sending the radio frequency startup command AT+CFUN=1 to restart the radio frequency function; through the radio frequency status re-initialization process, the LTE network search, network registration and data connection establishment process are re-triggered.

[0016] The system-level recovery operation is controlled according to the vehicle's operating status. The vehicle TBox obtains the vehicle's ignition status information. When the vehicle is detected to be powered on, it reads the system recovery count record and determines whether the system recovery count has reached the preset limit. If the preset limit has not been reached, it sends an operating system soft reset request to reinitialize the communication service program and network management program. When the preset limit is reached, the system-level recovery operation stops.

[0017] The network anomaly detection process adopts a dynamic threshold adjustment method. The vehicle-mounted TBox collects LTE communication quality parameters, including signal strength indicators, signal quality indicators, signal-to-noise ratio indicators, network registration status, and vehicle movement status. Based on the collection results, the thresholds for Ping detection failure times, APN dialing retry times, and link recovery times are adjusted to adapt the network anomaly detection conditions to different communication environments.

[0018] The dynamic threshold adjustment methods include: when the vehicle-mounted TBox detects that the vehicle is in a weak signal coverage area, underground space, tunnel environment, or frequent base station switching state, the network anomaly judgment parameters are adjusted to increase the network recovery waiting time and the number of detection tolerances; when the communication signal status is stable and the network registration status is normal, but Ping detection failure or APN link anomaly persists, the anomaly triggering conditions are adjusted to enter the link recovery processing process in advance.

[0019] The vehicle's operating status includes ignition on state and low-power sleep state. The on-board TBox selects the corresponding recovery strategy according to different vehicle states. When the vehicle is in low-power sleep state, the execution of system-level recovery operations is restricted, and the communication connection is restored by re-establishing the APN link first. When the vehicle is in ignition on state, link recovery, radio frequency recovery, and system recovery operations are performed according to the degree of network anomaly.

[0020] The technical effects and advantages provided by this application in the above technical solution are as follows: This application constructs a multi-dimensional network status detection mechanism and a four-level progressive recovery strategy, enabling the selection of appropriate recovery methods based on the severity of network anomalies in the vehicle-mounted TBox LTE network. In the initial stage of network anomaly, APN reconnection and link reconstruction operations are prioritized. If link restoration fails to resolve the issue, further radio frequency-level and system-level recovery operations are performed, avoiding unnecessary communication interruptions caused by directly executing high-level reset actions. By progressively increasing the recovery strength, the targeting of network anomaly handling is improved, the waiting time during network recovery is shortened, and the impact on the continuity of services such as remote control, vehicle diagnostics, and emergency communications is reduced.

[0021] This application incorporates vehicle operating status, power status, and a recovery count limit mechanism into the network recovery decision-making process, enabling the in-vehicle TBox to adjust its recovery behavior according to different usage scenarios. When the vehicle is in a low-power sleep state, low-power link recovery is prioritized to reduce the impact of high-power recovery operations on the vehicle battery. Simultaneously, by setting a system recovery count limit, the device is prevented from continuously performing repeated reset operations in the event of network anomalies, improving the operational stability of the in-vehicle communication equipment and ensuring power safety during long-term vehicle parking. Attached Figure Description

[0022] To more clearly illustrate the technical solutions in the embodiments of this application or the prior art, the drawings used in the embodiments will be briefly introduced below. Obviously, the drawings described below are only some embodiments recorded in this application. For those skilled in the art, other drawings can be obtained based on these drawings.

[0023] Figure 1 This is a logic diagram of the method in this application. Detailed Implementation

[0024] Exemplary embodiments will now be described more fully with reference to the accompanying drawings. However, these exemplary embodiments can be implemented in many forms and should not be construed as limited to the examples set forth herein; rather, they are provided so that the description of this disclosure will be more complete and fully convey the concept of the exemplary embodiments to those skilled in the art.

[0025] like Figure 1 As shown, this application provides a method for detecting and recovering from LTE network anomalies in a vehicle-mounted TBox, including the following steps: After the vehicle-mounted TBox is powered on, it initializes and configures the communication parameters, configures the public APN and private APN parameters, registers APN connection status change callbacks, starts the network monitoring task, and periodically obtains the public APN connection status. The data connection status is determined based on the public APN connection status. When the data connection is enabled, the APN link status callback is registered, the default route, the private APN dedicated route, the network address translation rules and domain name resolution configuration are configured, and the dial-up connection status of the private APN and the public APN is detected. When any APN link is disconnected, the corresponding APN configuration loading and dial-up connection operation are performed. Based on the dial-up connection status of the private APN and the public APN, dual-link reachability detection is performed on the vehicle TBox LTE network. The private network server address is accessed through the private APN link, and the public network server address is accessed through the public APN link. The network anomaly count is updated according to the detection results. When the number of dual-link detection failures reaches a preset threshold, a link recovery operation is performed. Based on the execution result of the link recovery operation, the data connection between the private APN and the public APN is disconnected, the corresponding routing configuration and network connection rules are cleared, and the APN link establishment operation is re-executed. When the number of link recovery operations reaches a preset threshold, the radio frequency recovery operation is executed, and the radio frequency function is turned off and then turned back on by controlling the communication unit. Based on the results of the radio frequency recovery operation and the vehicle's operating status, determine whether to perform a system-level recovery operation. If the vehicle is powered on and the number of system recovery attempts has not reached the preset limit, perform a soft reset operation on the vehicle's TBox operating system. If the number of system recovery attempts reaches the preset limit, stop performing the system-level recovery operation.

[0026] Specific Implementation Method 1: In one embodiment, this invention provides an LTE network anomaly monitoring and recovery method applied to an in-vehicle TBox. This method is deployed in the communication processing unit inside the in-vehicle TBox and is used to continuously monitor the LTE communication network status, identify anomalies, and perform subsequent recovery processing during vehicle operation. After the vehicle starts and enters the power-on state, the in-vehicle TBox first executes an initialization process to load and configure the basic parameters required for LTE network communication. During initialization, the in-vehicle TBox reads network access parameters pre-stored in the local configuration area, including public APN parameters and private APN parameters, to complete the basic configuration required for mobile communication network access. The public APN is mainly used to access public network resources, enabling data interaction between the vehicle and the external Internet environment; the private APN is mainly used to access the vehicle manufacturer's internal business platform, enabling data communication for vehicle data upload, remote diagnostics, vehicle control, and other vehicle-to-everything (V2X) dedicated services. By configuring the public and private APN parameters separately, the in-vehicle TBox can simultaneously support the data communication needs of different service links.

[0027] After configuring the APN parameters, the vehicle-mounted TBox further calls the network status interface provided by the communication processing unit to register an APN connection status change callback function. Through this callback function, the communication processing unit can proactively obtain status notifications when any APN link status changes, including information such as successful APN connection establishment, APN connection disconnection, network registration anomalies, and changes in data bearer status, thus avoiding the status acquisition delay problem caused by relying solely on periodic queries. Simultaneously, the vehicle-mounted TBox initiates a network monitoring task, establishing a periodic network detection mechanism. The network monitoring task runs cyclically according to a preset detection period T, continuously collecting and judging the LTE network connection status. During the network monitoring task, the vehicle-mounted TBox first reads the current public APN connection status and executes different processing procedures based on it. When a public APN is detected as being in a normal connection state, it indicates that the vehicle-mounted TBox has basic data communication capabilities and enters the subsequent network reachability detection process to further judge the actual communication capability of the current LTE link. When a public APN is detected as being disconnected, the vehicle-mounted TBox further judges the current data connection switch status to confirm whether network connection recovery is allowed.

[0028] When the data connection switch is detected to be on, the in-vehicle TBox continues the network environment configuration process. First, the APN link status callback interface is re-registered through the communication processing unit to ensure that subsequent network connection changes are promptly reported to the network monitoring task. Then, the network communication environment is configured according to the current network connection requirements, including setting a default network route, establishing a dedicated route for the private APN, configuring network address translation rules, and configuring domain name resolution parameters. Specifically, the default route ensures that public APN data traffic can access external networks normally, the private APN dedicated route ensures that vehicle business data accesses the vehicle manufacturer's internal servers along a specified path, network address translation rules maintain the normal forwarding of data packets in different network environments, and domain name resolution parameters support domain name access from the vehicle business platform. Through this network environment configuration process, the in-vehicle TBox's internal network resources can meet the communication requirements of both public and private business links.

[0029] When the data connection switch is detected to be off, the vehicle-mounted TBox further determines whether a data connection has been established previously. If the vehicle-mounted TBox has already established an LTE data link, it indicates that the user may have closed the data connection, the vehicle status may have changed, or the vehicle may have entered a low-power management phase. In this case, the vehicle-mounted TBox actively disconnects the currently established data link, releases communication resources, and clears cached information related to the network connection. Simultaneously, the vehicle-mounted TBox disables the Ethernet physical layer interface (PHY) to reduce unnecessary communication power consumption. When the vehicle control unit sends a sleep request, the vehicle-mounted TBox does not immediately execute the sleep process. Instead, it delays the sleep request based on the current network processing status, waiting for network resources to be released and related status processing completed before proceeding with the subsequent sleep process. This approach avoids the impact of abnormal network recovery on the vehicle's low-power management strategy, reduces vehicle static power consumption, and improves the operational stability of the vehicle's communication equipment.

[0030] After completing the basic network environment configuration, the vehicle-mounted TBox further executes the multi-APN link establishment process. First, the network monitoring task reads the current connection status of the private APN and determines whether a data communication link has been established. When a private APN link is detected to be disconnected, the vehicle-mounted TBox calls the communication processing unit interface, rewrites the network access information according to the pre-saved private APN configuration parameters, and sends a dial-up connection request to the communication processing unit to re-establish the private APN data link. During the private APN dialing process, the vehicle-mounted TBox sets a dialing retry threshold M and accumulates the number of consecutive dialing failures. When the dialing operation has not reached the maximum number of retries, the private APN dialing process continues; when the number of dialing failures reaches the maximum number of retries, the current private APN connection abnormality status is recorded, and the system waits for subsequent network recovery mechanisms to handle the situation.

[0031] After completing the private APN connection status detection, the vehicle-mounted TBox further detects the public APN connection status. When the public APN is disconnected, the vehicle-mounted TBox loads the corresponding public APN configuration parameters and executes a public APN dial-up connection operation to establish a data channel for the vehicle to access public network resources. After both the public and private APNs have established connections, the vehicle-mounted TBox enters the network reachability detection phase. Unlike the traditional method of only detecting the connectivity of a single public network address, this embodiment adopts a dual-link Ping detection mechanism to independently detect different service communication links. Specifically, the vehicle-mounted TBox sends a Ping detection request to a preset private network server address through the private APN communication interface to determine whether the private APN link has normal data transmission capabilities; simultaneously, it sends a Ping detection request to a preset public network server address through the public APN default communication interface to determine whether the public APN link can normally access the external network.

[0032] During the dual-link network reachability detection process, the vehicle-mounted TBox obtains the Ping response results returned by the private network server and the public network server, respectively, and determines the current LTE network status based on the detection results. When any Ping detection is successful, it indicates that at least one valid communication link exists. The vehicle-mounted TBox considers the current network connection status to meet basic communication requirements, resets the continuous network anomaly count to zero, and continues to perform subsequent network status detection according to a preset cycle. When the Ping detection results for both the private APN link and the public APN link fail, the vehicle-mounted TBox considers that there may be an LTE data link anomaly, a network context anomaly, or a communication status anomaly, and accumulates the number of consecutive detection failures. When the number of consecutive failures reaches a preset anomaly judgment threshold, the vehicle-mounted TBox determines that the current LTE network is in an abnormal state and triggers the subsequent link-level recovery processing procedure.

[0033] Through the processing method of this embodiment, the in-vehicle TBox can simultaneously acquire APN connection status, data connection status, network configuration status, and actual dual-link communication status during LTE communication operation, and comprehensively judge the LTE network health status through multi-dimensional network status information. Compared with the traditional solution that relies solely on a single Ping test result to judge network anomalies, this embodiment can distinguish the communication status of different APN links, reducing misjudgments caused by temporary network fluctuations, single-link anomalies, or local communication failures. Furthermore, by completing network status detection and link anomaly judgment before performing high-level recovery operations, subsequent recovery strategies can be matched to the actual degree of anomaly, reducing unnecessary communication module restart operations, improving the network recovery efficiency of the in-vehicle TBox, and reducing the impact on services such as remote control, emergency calls, and vehicle data interaction.

[0034] Specific Implementation Method Two: In another embodiment, this invention addresses situations where an in-vehicle TBox has completed LTE network registration and established a data communication connection, but experiences data link anomalies, network unreachability, APN connection status anomalies, or false communication link connections during actual service operation. It proposes a progressively enhanced recovery strategy based on anomaly level judgment. This recovery strategy gradually increases the intensity of recovery actions according to the number of network anomalies, the type of anomaly, and the recovery execution results. This avoids directly executing high-level recovery operations under minor network anomalies, thereby reducing communication service interruption time and improving the network recovery efficiency of the in-vehicle TBox.

[0035] When the vehicle-mounted TBox continuously detects network anomalies through the dual-link Ping detection mechanism, it first accumulates the network anomaly count. When the Ping detection of the private server address corresponding to the private APN link fails, and the Ping detection of the public server address corresponding to the public APN link also fails, and the number of consecutive failures reaches the preset anomaly judgment threshold, the vehicle-mounted TBox determines that the current LTE data communication link cannot meet the normal service communication requirements and enters the first-level link recovery process. During the link-level recovery process, the vehicle-mounted TBox first disconnects the currently established public APN data connection and private APN data connection, actively releases the data bearer context in the current LTE communication process, and clears the temporary connection state information stored in the communication link. At the same time, the vehicle-mounted TBox cleans up the current network environment resources, including deleting existing network routing configurations, clearing firewall rules, releasing network address translation rules, and clearing network cache information related to data connections, so that the initial configuration can be based on the new network environment when the network connection is re-established.

[0036] After releasing current network resources, the vehicle-mounted TBox waits for a preset recovery time to avoid recovery failure due to temporary fluctuations in the operator's network or immediate reconnection during communication state switching. After the waiting time is reached, the vehicle-mounted TBox re-enters the APN link establishment process, reloading the public and private APN configurations based on pre-saved network configuration parameters, and re-executes the network connection request, dialing operation, routing configuration, and network communication environment initialization process. During the APN link re-establishment process, the vehicle-mounted TBox continuously monitors APN connection status changes and determines whether link recovery was successful based on the connection results. If both the public and private APNs have restored normal connections, and dual-link Ping tests can obtain valid responses again, the current network anomaly is considered to have been resolved, the vehicle-mounted TBox clears the current anomaly status record, and resumes the normal network monitoring process.

[0037] To avoid repeated link recovery operations due to complex network anomalies, which could prevent the restoration of normal communication, this embodiment further includes a link recovery count statistics mechanism. After each link-level recovery operation, the vehicle-mounted TBox accumulates the number of link recovery operations and compares this accumulated count with a preset recovery count threshold. If the link recovery count has not reached the preset threshold, the vehicle-mounted TBox continues to attempt to restore LTE communication using the link-level recovery method. If the link recovery count reaches the preset threshold, it indicates that the current abnormal state may not be a simple data link anomaly, but may involve anomalies in the communication unit's internal state, radio frequency state, or network registration. In this case, the vehicle-mounted TBox stops performing the link reconstruction operation, upgrades the recovery level, and enters the radio frequency level recovery process.

[0038] If link-level recovery fails to restore the LTE communication state, the vehicle-mounted TBox further performs a second-level radio frequency (RF) level recovery operation. RF level recovery primarily addresses abnormal wireless communication states within the communication unit. By re-initializing the RF function of the communication unit, it enables the LTE communication unit to re-execute network search, network registration, and data link establishment processes. In this embodiment, the vehicle-mounted TBox sends RF control commands to the communication unit through the AT control interface provided by the communication unit. First, the vehicle-mounted TBox sends a command to disable RF control (AT+CFUN=0), causing the communication unit to stop its current wireless communication function, disable the LTE RF operating state, and release current wireless communication resources. Subsequently, the vehicle-mounted TBox sends a command to enable RF control (AT+CFUN=1), causing the communication unit to restart its RF function and re-execute the baseband processing flow, operator network search, LTE network registration, and data bearer establishment processes. Through this flight mode switching method, a soft reset of the communication unit's RF section is achieved, eliminating the need for a direct power-off restart operation and thus restoring some data connection failures caused by abnormal RF states, network registration, or communication context.

[0039] After completing the RF-level recovery operation, the vehicle-mounted TBox restarts the network status detection process, reassessing the public APN connection status, private APN connection status, and dual-link network reachability. Simultaneously, the vehicle-mounted TBox resets all link anomaly counts, RF recovery counts, and related status records generated during the recovery process to prevent historical anomalies from affecting subsequent recovery assessments. Once the RF-level recovery operation is successful, the vehicle-mounted TBox re-enters normal network monitoring mode and continues performing network status detection tasks according to the preset cycle.

[0040] If the LTE network still cannot return to normal communication after one or more radio frequency-level recovery operations, the vehicle-mounted TBox further executes a system-level recovery judgment process. This judgment process comprehensively considers the vehicle's current power status and the system's historical recovery count. First, the vehicle-mounted TBox obtains the vehicle's current operating status information to determine whether the vehicle is powered on. When the vehicle is powered on, it indicates that the vehicle is currently allowed to perform higher-level recovery operations. At this time, the system's historical restart count record is further read, and it is determined whether the system recovery count has reached the preset maximum limit. When the system recovery count has not reached the preset upper limit, the vehicle-mounted TBox increments the system recovery count value and sends a soft reset request to the operating system. By restarting the vehicle-mounted TBox operating system, the software operating environment is reinitialized, and the communication service program, network management program, and related business applications are reloaded, thereby attempting to recover from the LTE communication failure caused by the software state abnormality.

[0041] After a system soft reset is complete, the vehicle-mounted TBox re-executes the initialization process, including reloading the APN configuration, establishing an LTE network connection, resuming network monitoring tasks, and re-checking the communication link status. If the system soft reset still fails to resolve the network issue, the system restore count is used to determine whether further system-level restore operations are permissible. Once the preset maximum number of restores is reached, the vehicle-mounted TBox stops performing system reset operations to prevent the device from entering an infinite reboot state due to unrecoverable network failures, hardware malfunctions, or carrier network problems.

[0042] Furthermore, when the vehicle is in a powered-off state or in a low-power sleep management phase, the onboard TBox controls the scope of the recovery strategy based on the vehicle's power state, avoiding high-power system-level recovery operations that could affect the vehicle's static power management. For example, when the vehicle enters a low-power sleep mode, it prioritizes link-level recovery to attempt to restore communication status, only performing higher-level recovery operations when specific conditions are met, thereby reducing battery power consumption and improving communication reliability when the vehicle is parked for extended periods.

[0043] Through the step-by-step enhanced recovery strategy proposed in this embodiment, the vehicle-mounted TBox can select the appropriate recovery method based on the severity of the LTE network anomaly. For minor faults such as data link anomalies, the APN link disconnection and reconstruction method is used for recovery first; for communication unit radio frequency status anomalies, a soft reset is performed by turning the radio frequency off and on; for software operation status anomalies, an operating system soft reset is performed under the condition of meeting the vehicle status and recovery count limits. This recovery process gradually upgrades from low-impact operations to high-intensity recovery operations, avoiding the service interruption problem caused by directly restarting the communication unit or system in traditional solutions, while reducing unnecessary power consumption and improving the stability, reliability, and intelligence of the vehicle-mounted TBox's LTE network anomaly handling.

[0044] Specific Implementation Method 3: In another preferred embodiment, to further improve the accuracy, adaptability, and reliability of the vehicle-mounted TBox LTE network anomaly monitoring and recovery process, this invention introduces a dynamic threshold adjustment mechanism based on the current network environment state, building upon the aforementioned multi-dimensional network status detection system and four-level progressive recovery strategy. In this embodiment, the vehicle-mounted TBox no longer uses fixed network anomaly judgment parameters, but rather adaptively adjusts the network anomaly judgment conditions according to the actual vehicle operating environment, LTE network quality status, and communication link changes, thereby enabling the network detection logic to adapt to complex and ever-changing vehicle usage scenarios. The dynamically adjusted parameters include, but are not limited to, the threshold for consecutive Ping probe failures, the threshold for APN dialing retry counts, the threshold for link-level recovery execution counts, and the radio frequency-level recovery trigger conditions. By adjusting these judgment parameters in real time, the vehicle-mounted TBox can distinguish between temporary communication anomalies caused by changes in the external network environment and persistent network failures caused by internal anomalies in the communication equipment.

[0045] In practice, when the vehicle-mounted TBox performs network status monitoring, in addition to acquiring public APN connection status, private APN connection status, Ping test results, and dial-up connection status, it further collects current LTE communication environment parameters. These parameters include communication signal strength indicators, signal quality indicators, signal-to-noise ratio indicators, network registration status, cell handover status, base station connection stability, and the vehicle's current motion status. Specifically, signal strength indicators reflect the current LTE wireless coverage capability; signal quality indicators determine the degree of interference in the current communication environment; signal-to-noise ratio indicators determine wireless transmission quality; network registration status determines whether the communication unit is normally connected to the operator's network; cell handover status determines whether there are frequent network handovers during vehicle movement; and vehicle motion status helps determine whether the current anomaly is caused by changes in the vehicle's environment.

[0046] When the vehicle-mounted TBox detects that the vehicle is in an area with weak signal coverage, underground parking, tunnel, mountain roads, or other areas with poor wireless communication quality, it will not immediately perform link recovery operations according to a fixed anomaly threshold because such environments are prone to short-term network fluctuations, signal attenuation, and base station handover anomalies. Instead, it will dynamically increase the network anomaly judgment threshold based on the current network quality status. For example, it may increase the threshold for consecutive Ping failures, increase the number of dial-up connection retries, and extend the link recovery waiting time, giving the communication link more opportunities for automatic recovery. In this case, if the LTE signal quality is detected to be gradually recovering, or the network registration status returns to normal, the vehicle-mounted TBox will continue to maintain the current communication status detection process, avoiding frequent APN redialing, link reconstruction, RF reset, or even system-level recovery operations due to short-term network fluctuations.

[0047] For example, during high-speed vehicle travel, the LTE network may experience short-term handover delays as the vehicle continuously passes through different base station coverage areas. This can lead to several consecutive Ping failures, even though the communication unit itself is not faulty. Using a fixed failure threshold for judgment might cause the vehicle's TBox to mistakenly identify a network anomaly and perform link recovery or even radio frequency recovery operations, increasing communication recovery time and potentially causing a brief interruption of vehicle services. This embodiment dynamically adjusts the anomaly judgment threshold by combining signal strength, signal quality, and vehicle motion status. When natural fluctuations in the network environment are confirmed, the anomaly trigger condition is increased, allowing the vehicle's TBox to wait for automatic network recovery, thereby reducing erroneous recovery operations and improving the continuity of vehicle communication services.

[0048] In another scenario, when the vehicle-mounted TBox detects a relatively good network environment but persistent Ping failures, APN dialing failures, or data link anomalies occur, it indicates that the anomaly is more likely caused by an abnormality in the internal state of the communication link, a network connection context, or the communication unit software. In this case, the vehicle-mounted TBox lowers the anomaly detection threshold based on the current favorable network environment, allowing the recovery strategy to enter the corresponding processing stage more quickly. For example, when the LTE signal strength meets communication requirements, network registration is normal, and base station connection is stable, but Ping detection on both the private and public APN links continues to fail, the vehicle-mounted TBox determines that the anomaly is not caused by changes in the wireless environment, but rather by an abnormality in the data bearer state or a network protocol stack. Therefore, it shortens the anomaly confirmation time and quickly triggers link-level recovery operations.

[0049] When link-level recovery fails to restore communication, the vehicle-mounted TBox continues to determine whether to proceed to a higher-level recovery process based on dynamically adjusted recovery conditions. When an abnormal radio frequency (RF) status of the communication unit is detected, and the current network quality meets the recovery conditions, the vehicle-mounted TBox quickly executes an RF-level recovery operation, sending an RF shutdown command AT+CFUN=0 and an RF startup command AT+CFUN=1 via the AT control interface. This causes the communication unit to reinitialize its wireless communication status and re-execute the LTE network search, network registration, and data connection establishment processes. If normal communication still cannot be restored after multiple RF recovery attempts, the vehicle-mounted TBox further determines whether to execute a system-level recovery operation based on the vehicle's operating status and the system's recovery attempt limit.

[0050] Regarding vehicle power status management, this embodiment further incorporates the vehicle's operating status into the dynamic recovery decision-making process. When the onboard TBox detects that the vehicle is in the ignition-on state, the vehicle currently has a high power supply capacity, allowing for high-power recovery actions. Therefore, the recovery level can be gradually increased based on the severity of the network anomaly. When the vehicle is in the off state or in a low-power sleep state, the onboard TBox prioritizes the vehicle's battery protection strategy, limiting the execution of high-power recovery operations. For example, during vehicle sleep, even if a network anomaly is detected, low-power recovery methods such as APN link re-establishment and data connection restoration are prioritized, thereby avoiding direct communication unit restart or TBox operating system soft reset operations. This reduces the impact of the recovery process on the vehicle's static current and ensures power stability during long-term parking.

[0051] Furthermore, this embodiment can further optimize the dynamic threshold adjustment strategy based on historical network anomaly records. The vehicle-mounted TBox can record data such as the number of network anomalies, recovery success rate, and recovery time under different vehicle environments, and adjust subsequent anomaly judgment parameters based on historical operating conditions. For example, when weak coverage exists in a certain area for a long time, the anomaly judgment tolerance for the corresponding area is increased; when a communication area maintains stable network quality for a long time but frequently experiences link anomalies, the anomaly trigger threshold is reduced to improve fault handling response speed. Through the above methods, the vehicle-mounted TBox can continuously optimize the network anomaly judgment logic according to the actual operating environment, improving the adaptability of the network recovery strategy.

[0052] Through the dynamic threshold adjustment mechanism proposed in this embodiment, the vehicle-mounted TBox can comprehensively consider the LTE wireless environment, communication link status, vehicle operating status, and historical anomalies to adaptively adjust the network anomaly judgment conditions and recovery strength. On the one hand, in scenarios with weak signals, network fluctuations, or natural communication changes caused by vehicle movement, it can avoid prematurely triggering recovery actions, reducing unnecessary link reconstruction, RF resets, and system restarts, thereby reducing service interruptions and additional power consumption. On the other hand, in situations where the network environment is good but the communication status is abnormal, it can quickly identify the real fault and improve the recovery level, thereby improving the efficiency of network anomaly handling. Therefore, this embodiment further improves the accuracy, intelligence, and reliability of the vehicle-mounted TBox LTE network anomaly monitoring and recovery method in engineering applications.

[0053] The foregoing has only described certain exemplary embodiments of this application by way of illustration. Undoubtedly, those skilled in the art can modify the described embodiments in various ways without departing from the spirit and scope of this application. Therefore, the foregoing drawings and descriptions are illustrative in nature and should not be construed as limiting the scope of protection of the claims of this application.

Claims

1. A method for detecting and recovering anomalies in an in-vehicle TBox LTE network, characterized in that, Includes the following steps: After the vehicle-mounted TBox is powered on, it initializes and configures the communication parameters, configures the public APN and private APN parameters, registers APN connection status change callbacks, starts the network monitoring task, and periodically obtains the public APN connection status. The data connection status is determined based on the public APN connection status. When the data connection is enabled, the APN link status callback is registered, the default route, the private APN dedicated route, the network address translation rules and domain name resolution configuration are configured, and the dial-up connection status of the private APN and the public APN is detected. When any APN link is disconnected, the corresponding APN configuration loading and dial-up connection operation are performed. Based on the dial-up connection status of the private APN and the public APN, dual-link reachability detection is performed on the vehicle TBox LTE network. The private network server address is accessed through the private APN link, and the public network server address is accessed through the public APN link. The network anomaly count is updated according to the detection results. When the number of dual-link detection failures reaches a preset threshold, a link recovery operation is performed. Based on the execution result of the link recovery operation, the data connection between the private APN and the public APN is disconnected, the corresponding routing configuration and network connection rules are cleared, and the APN link establishment operation is re-executed. When the number of link recovery operations reaches a preset threshold, the radio frequency recovery operation is executed, and the radio frequency function is turned off and then turned back on by controlling the communication unit. Based on the results of the radio frequency recovery operation and the vehicle's operating status, determine whether to perform a system-level recovery operation. If the vehicle is powered on and the number of system recovery attempts has not reached the preset limit, perform a soft reset operation on the vehicle's TBox operating system. If the number of system recovery attempts reaches the preset limit, stop performing the system-level recovery operation.

2. The method for monitoring and recovering anomalies in a vehicle-mounted TBox LTE network according to claim 1, characterized in that, When the network monitoring task acquires the public APN connection status, it simultaneously collects the private APN connection status, data connection switch status, and network registration status, and receives communication link status change information through the connection status change callback function; when a connection change is detected in any APN link, the corresponding APN link status record is updated, and network connection status is judged based on the updated link status.

3. The method for detecting and recovering anomalies in a vehicle-mounted TBox LTE network according to claim 2, characterized in that, Private APNs and public APNs correspond to different data communication paths. Private APNs access the vehicle service server through a dedicated route, while public APNs access the public network server through a default route. During network configuration, routing tables for private APNs, default routing tables for public APNs, and corresponding data forwarding rules are established to ensure that different service data are transmitted according to the preset communication paths.

4. The method for monitoring and recovering anomalies in a vehicle-mounted TBox LTE network according to claim 3, characterized in that, During the dual-link reachability detection process, the vehicle-mounted TBox sends Ping detection requests to the private network server address through the private APN interface and to the public network server address through the public APN interface, and records the private network link detection results and the public network link detection results respectively. When either link is successfully detected, the continuous network anomaly count is cleared to zero. When both link detections fail, the number of consecutive anomalies is accumulated.

5. The method for detecting and recovering anomalies in a vehicle-mounted TBox LTE network according to claim 4, characterized in that, Link recovery operations include releasing the current data bearer context, disconnecting public APN connections, disconnecting private APN connections, clearing network routing configurations, deleting firewall rules, and releasing network connection resources; After releasing network resources, reload the public and private APN parameters, re-initiate the dial-up connection request, and determine the link recovery result based on the APN connection status.

6. The method for monitoring and recovering anomalies in a vehicle-mounted TBox LTE network according to claim 1, characterized in that, The radio frequency recovery operation is performed through the AT control interface provided by the communication unit, including sending the radio frequency shutdown command AT+CFUN=0 to shut down the radio frequency function of the communication unit, and sending the radio frequency startup command AT+CFUN=1 to restart the radio frequency function; through the radio frequency status re-initialization process, the LTE network search, network registration and data connection establishment process are re-triggered.

7. The method for monitoring and recovering anomalies in a vehicle-mounted TBox LTE network according to claim 1, characterized in that, The system-level recovery operation is controlled according to the vehicle's operating status. The vehicle TBox obtains the vehicle's ignition status information. When the vehicle is detected to be powered on, it reads the system recovery count record and determines whether the system recovery count has reached the preset limit. If the preset limit has not been reached, it sends an operating system soft reset request to reinitialize the communication service program and network management program. When the preset limit is reached, the system-level recovery operation stops.

8. The method for monitoring and recovering anomalies in a vehicle-mounted TBox LTE network according to claim 1, characterized in that, The network anomaly detection process adopts a dynamic threshold adjustment method. The vehicle-mounted TBox collects LTE communication quality parameters, including signal strength indicators, signal quality indicators, signal-to-noise ratio indicators, network registration status, and vehicle movement status. Based on the collection results, the thresholds for Ping detection failure times, APN dialing retry times, and link recovery times are adjusted to adapt the network anomaly detection conditions to different communication environments.

9. A method for monitoring and recovering anomalies in a vehicle-mounted TBox LTE network according to claim 8, characterized in that, The dynamic threshold adjustment methods include: when the vehicle-mounted TBox detects that the vehicle is in a weak signal coverage area, underground space, tunnel environment, or frequent base station switching state, the network anomaly judgment parameters are adjusted to increase the network recovery waiting time and the number of detection tolerances; when the communication signal status is stable and the network registration status is normal, but Ping detection failure or APN link anomaly persists, the anomaly triggering conditions are adjusted to enter the link recovery processing process in advance.

10. The method for detecting and recovering anomalies in a vehicle-mounted TBox LTE network according to claim 1, characterized in that, The vehicle's operating status includes ignition on state and low-power sleep state. The on-board TBox selects the corresponding recovery strategy according to different vehicle states. When the vehicle is in low-power sleep state, the execution of system-level recovery operations is restricted, and the communication connection is restored by re-establishing the APN link first. When the vehicle is in ignition on state, link recovery, radio frequency recovery, and system recovery operations are performed according to the degree of network anomaly.

Images