Vehicle communication connection management method and system

Abstract

The application provides a vehicle-mounted communication connection management method and system, and relates to the technical field of network-connected vehicle communication. The method comprises the following steps: establishing a network connection between a vehicle machine and a vehicle-mounted communication terminal; when the network connection is abnormally disconnected, the vehicle machine performs first abnormality detection and executes a first recovery operation to reestablish the network connection when a first type of abnormality is detected; the vehicle-mounted communication terminal performs second abnormality detection and executes a second recovery operation to reestablish the network connection when a second type of abnormality is detected. The application can timely and reliably recover the connection when the universal serial bus network connection is abnormally disconnected, and significantly improves the self-healing ability and robustness of the vehicle-mounted communication link.

Description

Technical Field

[0001] This invention relates to the field of connected vehicle communication technology, and in particular to a method and system for managing vehicle communication connections. Background Technology

[0002] Currently, in intelligent connected vehicles, the in-vehicle infotainment system typically needs to establish a network connection with the vehicle's communication terminal to enable internet access via the terminal's mobile communication module. However, in actual use, the network connection between the in-vehicle infotainment system and the communication terminal is prone to unexpected disconnection due to various abnormal factors (such as power fluctuations, signal interference, system sleep / wake-up). Once the network connection is lost, the vehicle will be unable to access the network normally, causing network-dependent in-vehicle functions such as navigation, online music, and remote control to malfunction.

[0003] In existing technologies, when the network connection is abnormally disconnected, the system lacks an effective automatic recovery mechanism, often requiring users to manually restart the vehicle or wait for a long time to re-establish the network connection, which seriously affects the user experience.

[0004] Therefore, how to promptly detect and restore the abnormally disconnected network connection between the vehicle's infotainment system and the communication terminal has become an urgent technical problem to be solved. Summary of the Invention

[0005] In view of this, the purpose of the present invention is to provide a vehicle communication connection management method and system to solve the technical problem of frequent abnormal disconnection of network connection between the vehicle unit and the vehicle communication terminal.

[0006] In a first aspect, embodiments of the present invention provide a method for managing vehicle-mounted communication connections, the method comprising: A network connection is established between the vehicle's infotainment system and the in-vehicle communication terminal; When the network connection is abnormally disconnected, the vehicle system performs a first anomaly detection, and performs a first recovery operation when a first type of anomaly is detected, in order to re-establish the network connection; When the network connection is abnormally disconnected, the vehicle-mounted communication terminal performs a second anomaly detection, and when a second type of anomaly is detected, it performs a second recovery operation to re-establish the network connection.

[0007] In one implementation, the network connection is a Universal Serial Bus (USB) network connection.

[0008] In one embodiment, establishing a network connection between the vehicle-mounted infotainment system and the vehicle-mounted communication terminal includes: During vehicle initialization, the vehicle system provides bus voltage to the vehicle communication terminal. The vehicle communication terminal responds to the bus voltage being at an effective level by feeding back a positive differential data signal to the vehicle system. After detecting the positive differential data signal, the vehicle's infotainment system initiates a Universal Serial Bus (USB) enumeration to complete the USB network connection with the vehicle communication terminal.

[0009] In one implementation, the vehicle system performs a first anomaly detection, including: The vehicle-mounted system monitors the connection status of the network interface between itself and the vehicle-mounted communication terminal; If the network interface fails to mount, it is determined that the first type of anomaly exists.

[0010] In one implementation, the vehicle system performs a first recovery operation, including: The vehicle's infotainment system cuts off and restores power to the network interface to re-establish the network connection.

[0011] In one embodiment, the vehicle-mounted communication terminal performs a second anomaly detection, including: The vehicle-mounted communication terminal monitors the bus voltage and the application layer connection status with the vehicle's infotainment system. If the bus voltage is high and the application layer connection between the vehicle communication terminal and the vehicle system is abnormal, then the second type of abnormality is determined to exist.

[0012] In one embodiment, the vehicle-mounted communication terminal performs a second recovery operation, including: The vehicle-mounted communication terminal re-initiates a physical layer handshake signal to the vehicle's infotainment system to trigger the system to re-establish the network connection.

[0013] In one embodiment, the vehicle communication terminal monitors the bus voltage and the application layer connection status with the vehicle's infotainment system, including: If the vehicle-mounted communication terminal detects that the application layer heartbeat packet is lost and fails to re-establish the connection for more than a first preset time, it determines that the application layer connection is abnormal. The application layer heartbeat packet is a status detection signal sent by the vehicle-mounted system or the vehicle-mounted communication terminal to the other party at a preset period when the application layer connection status is detected between the vehicle-mounted system and the vehicle-mounted communication terminal.

[0014] In one embodiment, the method further includes: When the network connection is normal but the vehicle-mounted system cannot access the public network, in response to an automatically triggered event or a user-triggered event, the vehicle-mounted system and the vehicle-mounted communication terminal cooperate to execute a network reset process to restore public network access.

[0015] In one implementation, the automatically triggered event includes events that simultaneously satisfy the following conditions: The application layer service between the vehicle infotainment system and the vehicle communication terminal is normal. The network standard provided by the vehicle-mounted communication terminal meets the preset requirements; The mobile communication network signal strength provided by the vehicle-mounted communication terminal is within a preset range.

[0016] In one implementation, in response to the automatically triggered event, the vehicle infotainment system and the in-vehicle communication terminal cooperate to execute a network reset procedure to restore public network access, including: The vehicle-mounted system sends a probe packet to the primary public network address. If sending the probe packet to the primary public network address fails, it sends probe packets to multiple backup public network addresses or multiple public domain name servers one by one. If sending probe packets to all multiple backup public network addresses or multiple public domain name servers fails, it is determined that the public network cannot be accessed, and the vehicle-mounted system generates a reset command and sends it to the vehicle communication terminal.

[0017] In one implementation, in response to the user-triggered event, the vehicle-mounted system and the in-vehicle communication terminal cooperate to execute a network reset procedure to restore public network access, including: In response to an active triggering operation on its user interface, the vehicle system sends a reset command to the vehicle communication terminal. The number of times the vehicle-mounted communication terminal executes the reset command within the same ignition cycle shall not exceed a preset maximum number of times, and the interval between two adjacent reset commands shall not be less than a second preset duration.

[0018] In one implementation, the vehicle-mounted system and the in-vehicle communication terminal cooperate to perform a network reset procedure to restore public network access, including: The vehicle-mounted system captures communication data packets, routing tables, and domain name resolution logs, and performs a network reset on the vehicle-mounted system. The vehicle-mounted communication terminal captures communication data packets, routing tables, and domain name resolution logs, performs public network redial, and reinitializes the network configuration.

[0019] Secondly, embodiments of the present invention also provide a vehicle communication connection management method, comprising: Establish a network connection with the vehicle-mounted communication terminal; When the network connection is abnormally disconnected, a first anomaly detection is performed, and a first recovery operation is performed when a first type of anomaly is detected to re-establish the network connection; the vehicle-mounted communication terminal is used to perform a second anomaly detection when the network connection is abnormally disconnected, and to perform a second recovery operation when a second type of anomaly is detected to re-establish the network connection.

[0020] Thirdly, embodiments of the present invention also provide a vehicle communication connection management method, comprising: Establish a network connection with the vehicle's infotainment system; When the network connection is abnormally disconnected, a second anomaly detection is performed, and a second recovery operation is performed when a second type of anomaly is detected to re-establish the network connection; the vehicle system is used to perform a first anomaly detection when the network connection is abnormally disconnected, and to perform a first recovery operation when a first type of anomaly is detected to re-establish the network connection.

[0021] Fourthly, embodiments of the present invention also provide a vehicle communication connection management system, the system including a vehicle-mounted unit and a vehicle-mounted communication terminal, wherein a network connection is established between the vehicle-mounted unit and the vehicle-mounted communication terminal; The vehicle system is configured such that when the network connection is abnormally disconnected, the vehicle system performs a first anomaly detection, and when a first type of anomaly is detected, it performs a first recovery operation to re-establish the network connection. The vehicle-mounted communication terminal is configured to perform a second anomaly detection when the network connection is abnormally disconnected, and to perform a second recovery operation when a second type of anomaly is detected, so as to re-establish the network connection.

[0022] The present invention provides a vehicle communication connection management method and system, which performs a first anomaly detection on the vehicle-mounted unit side and performs a first recovery operation when a first type of anomaly is detected, and performs a second anomaly detection on the vehicle-mounted communication terminal side and performs a second recovery operation when a second type of anomaly is detected. This achieves the effect of independent detection and complementary recovery by both sides when the network connection between the vehicle-mounted unit and the vehicle-mounted communication terminal is abnormally disconnected, thereby improving the self-healing capability and robustness of the vehicle communication link in abnormal scenarios.

[0023] Other features and advantages of the invention will be set forth in the description which follows, and will be apparent in part from the description, or may be learned by practicing the invention. The objects and other advantages of the invention are realized and obtained in accordance with the structures particularly pointed out in the description, claims and drawings.

[0024] To make the above-mentioned objects, features and advantages of the present invention more apparent and understandable, preferred embodiments are described below in detail with reference to the accompanying drawings. Attached Figure Description

[0025] To more clearly illustrate the specific embodiments of the present invention or the technical solutions in the prior art, the drawings used in the description of the specific embodiments or the prior art will be briefly introduced below. Obviously, the drawings described below are some embodiments of the present invention. For those skilled in the art, other drawings can be obtained from these drawings without creative effort.

[0026] Figure 1 A flowchart illustrating a vehicle communication connection management method provided in an embodiment of the present invention; Figure 2 A structural block diagram of an in-vehicle communication connection management system provided in an embodiment of the present invention; Figure 3 This is a schematic diagram of the structure of an electronic device provided in an embodiment of the present invention. Detailed Implementation

[0027] To make the objectives, technical solutions, and advantages of the embodiments of the present invention clearer, the technical solutions of the present invention will be clearly and completely described below in conjunction with the embodiments. Obviously, the described embodiments are only some embodiments of the present invention, not all embodiments. Based on the embodiments of the present invention, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of the present invention.

[0028] Currently, in intelligent connected vehicles, the in-vehicle infotainment system typically needs to establish a network connection with the vehicle's communication terminal to enable internet access via the terminal's mobile communication module. However, in actual use, the network connection between the in-vehicle infotainment system and the communication terminal is prone to unexpected disconnection due to various abnormal factors (such as power fluctuations, signal interference, system sleep / wake-up). Once the network connection is lost, the vehicle will be unable to access the network normally, causing network-dependent in-vehicle functions such as navigation, online music, and remote control to malfunction.

[0029] In existing technologies, when the network connection is abnormally disconnected, the system lacks an effective automatic recovery mechanism, often requiring users to manually restart the vehicle or wait for a long time to re-establish the network connection, which seriously affects the user experience.

[0030] Based on this, the present invention provides a vehicle communication connection management method and system, which performs a first anomaly detection on the vehicle-mounted unit side and performs a first recovery operation when a first type of anomaly is detected, and performs a second anomaly detection on the vehicle-mounted communication terminal side and performs a second recovery operation when a second type of anomaly is detected. This achieves the effect of independent detection and complementary recovery by both sides when the network connection between the vehicle-mounted unit and the vehicle-mounted communication terminal is abnormally disconnected, thereby improving the self-healing capability and robustness of the vehicle communication link in abnormal scenarios.

[0031] To facilitate understanding of this embodiment, a detailed description of the vehicle communication connection management method disclosed in this embodiment of the invention will be provided first, see [link to relevant documentation]. Figure 1 The diagram shows a flowchart of a vehicle communication connection management method, which may include the following steps: S102, a network connection is established between the vehicle infotainment system and the vehicle communication terminal.

[0032] Network connection refers to the communication link established between the vehicle's infotainment system and the in-vehicle communication terminal based on the Universal Serial Bus (USB) protocol for data transmission. The vehicle's infotainment system (HU) is integrated into the vehicle and provides infotainment, navigation, vehicle settings, and network communication functions. The in-vehicle communication terminal (T-BOX) is a remote information processing control unit installed in the vehicle, with a built-in mobile communication module (such as a 4G / 5G module) for data interaction between the vehicle and external networks. It connects to the vehicle's infotainment system via a USB interface to provide internet access.

[0033] In one implementation, the network connection is a Universal Serial Bus (USB) network connection.

[0034] In one implementation, establishing a network connection between the vehicle infotainment system and the vehicle communication terminal includes: the vehicle infotainment system providing a bus voltage to the vehicle communication terminal during initialization; the vehicle communication terminal responding to the bus voltage being at an effective level by feeding back a positive differential data signal to the vehicle infotainment system; and the vehicle infotainment system initiating a Universal Serial Bus (USB) enumeration after detecting the positive differential data signal to complete the USB network connection with the vehicle communication terminal.

[0035] For example, after the vehicle is powered on, the in-vehicle infotainment system initializes its Universal Serial Bus (USB) host controller and provides bus voltage to the in-vehicle communication terminal via the Vbus (USB Voltage Bus) pin of the USB interface. Upon detecting that the Vbus voltage is at a valid level, the in-vehicle communication terminal sends a positive differential data signal back to the in-vehicle infotainment system via the D+ (Data PositiveSignal) pin of its USB interface to indicate that a device is connected. After detecting this D+ signal, the in-vehicle infotainment system initiates a USB enumeration process, including obtaining information such as the device descriptor, configuration descriptor, and interface descriptor of the in-vehicle communication terminal, and assigning a USB address to the in-vehicle communication terminal and loading the corresponding USB network card driver. After the USB network card driver is successfully loaded, the in-vehicle operating system generates a virtual network interface (such as usb0 or ethX), which forms a point-to-point data transmission link with the USB network card on the in-vehicle communication terminal side. At this time, the in-vehicle infotainment system configures an IP address through this virtual network interface and completes a network layer handshake with the in-vehicle communication terminal, thus establishing a network connection between the in-vehicle infotainment system and the in-vehicle communication terminal.

[0036] For example, in one embodiment, after the vehicle's infotainment system (VBS) is powered on, its USB host controller initializes and pulls the Vbus pin level high to 5V. After the T-BOX detects that Vbus is 5V, it outputs a high-level pulse lasting approximately 10ms on the D+ pin. After detecting this pulse, the VBS obtains the device descriptor of the T-BOX through control transmission, then performs address allocation and configuration selection, loads the USB CDC ECM (Ethernet Control Model) class driver, and generates a virtual network card interface usb0. The VBS assigns an IP address (e.g., 192.168.1.1 / 24) to the usb0 interface via DHCP (Dynamic Host Configuration Protocol) or static configuration, and configures the corresponding USB network card interface on the T-BOX side with an IP (Internet Protocol) address (e.g., 192.168.1.2 / 24). The two then establish a network connection that allows them to communicate with each other, and the VBS can access the public network through the T-BOX's mobile communication module.

[0037] It should be noted that other equivalent USB device class protocols (such as RNDIS (Remote Network Driver Interface Specification), NCM (Network Control Model), etc.) or different IP address configuration methods can be used to establish a network connection.

[0038] S104, when the network connection is abnormally disconnected, the vehicle system performs the first anomaly detection, and performs the first recovery operation when the first type of anomaly is detected, in order to re-establish the network connection.

[0039] Among them, abnormal network connection disconnection refers to the interruption of the established network connection between the vehicle-mounted infotainment system and the vehicle-mounted communication terminal due to abnormal reasons, such as power fluctuations, signal interference, system sleep-wake conflicts, etc., which prevents the vehicle-mounted infotainment system from exchanging data with the vehicle-mounted communication terminal through the connection.

[0040] For example, the vehicle's infotainment system monitors the mounting status of the USB network card in its operating system in real time to determine whether the network connection with the vehicle communication terminal is normal. If the infotainment system detects that the USB network card has not been successfully mounted, for example, by reading whether the corresponding network card interface exists in the system's / sys / class / net / directory, or by confirming that the network card does not exist through the error code returned by the network card binding operation, it determines that the network connection has been abnormally disconnected, and a first type of anomaly exists.

[0041] When the vehicle's infotainment system detects a Type I anomaly, it executes the first recovery operation. For example, the system sends a power reset signal to the USB port connected to the vehicle communication terminal via the power management interface of the Universal Serial Bus (USB) host controller. This essentially performs a power-off and power-back operation on the USB port, forcibly resetting the physical layer state of the USB link. After the power reset is complete, the system re-initiates the USB enumeration process to re-establish a connection with the vehicle communication terminal.

[0042] It's important to note that the vehicle's infotainment system performs the first recovery operation not just once, but multiple times according to a preset retry strategy. For example, the system repeatedly performs a power reset at increasing time intervals to address connection anomalies caused by various reasons, while avoiding excessively frequent resets that could burden the system. If the network connection is restored within a certain interval, subsequent retries cease. Furthermore, the system monitors the vehicle's power status; when the vehicle is in standby or sleep mode, the first recovery operation is prohibited to prevent unnecessary hardware operations in the system's low-power mode.

[0043] S106, when the network connection is abnormally disconnected, the vehicle-mounted communication terminal performs a second anomaly detection, and when a second type of anomaly is detected, it performs a second recovery operation to re-establish the network connection.

[0044] For example, firstly, the vehicle communication terminal determines whether it is in a non-prepared sleep state, that is, whether an abnormal recovery operation is currently allowed. If allowed, it checks whether the voltage of the Vbus pin is at a valid level. If Vbus is at a valid level, it indicates that the vehicle's infotainment system still considers the USB link to exist; at this time, the vehicle communication terminal further checks the application layer connection status with the vehicle's infotainment system, for example, by checking whether it periodically receives application layer heartbeat packets from the vehicle's infotainment system to determine whether the application layer connection is alive.

[0045] If the vehicle communication terminal detects that the application layer heartbeat packet is lost and fails to re-establish the application layer connection for more than the first preset time (e.g., 30 seconds), it is determined that the current USB network connection has a second type of anomaly, that is, the physical layer connection is still there but the application layer data channel is abnormal.

[0046] Upon detecting a Type II anomaly, the vehicle communication terminal performs a second recovery operation. For example, the vehicle communication terminal re-triggers the positive differential data signal through the D+ pin of its USB interface, simulating the handshake signal for device re-insertion, thereby forcing the vehicle's infotainment system to re-initiate the USB enumeration process and re-establish the USB network connection.

[0047] It should be noted that, to avoid frequent reconnections leading to wasted system resources or a loop, the vehicle communication terminal limits the frequency of the second recovery operation. For example, the vehicle communication terminal only allows the second recovery operation to be executed if the number of times the positive differential data signal is retried within the current ignition cycle has not reached a first preset limit (e.g., 3 times). If the limit has been reached, reconnection will not be triggered, and the system will wait for the next ignition cycle or user intervention.

[0048] This invention achieves dual-end self-healing for network connection anomalies by deploying independent and complementary anomaly detection and recovery mechanisms on the vehicle-mounted system side and the vehicle-mounted communication terminal side respectively: the vehicle-mounted system side detects the network interface mounting status and performs a first recovery operation when an anomaly occurs, while the communication terminal side detects the bus voltage and application layer connection status and performs a second recovery operation when an anomaly occurs. The detection logic of the two is different and the recovery actions are complementary. Even if the recovery on one side fails, the connection on the other side can still be rebuilt, thereby significantly improving the robustness and self-healing capability of the vehicle communication link under various fault scenarios such as physical layer disconnection, link layer anomaly, and application layer inactivation.

[0049] Meanwhile, by introducing multiple safeguards such as incremental retry intervals, upper limit on the number of reconnections within the ignition cycle, suppression of sleep state, and public network connectivity detection and automatic reset, the system effectively avoids waste of resources, ensures the stability and reliability of the network recovery process, and ultimately achieves the beneficial effects of timely network connection restoration without user intervention, improving the availability of intelligent connected functions, and enhancing user satisfaction.

[0050] In one implementation, the vehicle-mounted infotainment system performs a first anomaly detection, including: monitoring the mounting status of the network interface between the system and the vehicle-mounted communication terminal; if the network interface fails to mount successfully, a first type of anomaly is determined to exist. Here, the network interface refers to a virtual network device created in the vehicle-mounted infotainment system kernel for data communication with the vehicle-mounted communication terminal. Once a normal Universal Serial Bus (USB) network connection is established between the vehicle-mounted infotainment system and the vehicle-mounted communication terminal, the vehicle-mounted infotainment system loads the corresponding USB network card driver and generates a virtual network interface, such as usb0, ethX, or wwan0.

[0051] The mounting status refers to whether the network interface has been successfully recognized, loaded, and is available in the vehicle's operating system. Successful mounting means the operating system has allocated the necessary system resources to the interface, completed device registration, and enabled it to send and receive data packets. Conversely, if the network interface fails to mount, it indicates that the data link layer between the vehicle's infotainment system and the in-vehicle communication terminal has not been established, and the two cannot interact. Unsuccessful mounting includes, but is not limited to, the following situations: the network interface device file does not exist in the system, interface registration fails, driver loading is abnormal, or the interface is inactive.

[0052] For example, the vehicle's infotainment system monitors the network interface connection status with the in-vehicle communication terminal in real time through the network device management interface provided by the operating system. The system runs a network status monitoring thread that periodically (e.g., every 5 seconds) checks if the network interface name corresponding to the in-vehicle communication terminal exists in the system's / sys / class / net / directory. If the network interface exists, it further confirms whether the interface is in the UP state by reading its operstate or flags file. If the interface does not exist or its status is abnormal, it is determined that the network interface has not been successfully connected.

[0053] In one implementation, the vehicle's infotainment system binds the network interface via an application. If the binding operation fails, the system returns an error code indicating that the device does not exist (such as ENODEV), based on which the infotainment system determines that the network interface has not been successfully attached.

[0054] In one implementation, the vehicle-mounted system performs a first recovery operation, including: disconnecting and restoring power to the network interface to re-establish the network connection.

[0055] For example, when the vehicle's infotainment system determines that the network interface has not been successfully connected, it confirms the existence of a first type of anomaly. At this time, the vehicle's infotainment system triggers a first recovery operation, such as resetting the power of the USB port or re-initiating USB enumeration, to re-establish the network connection with the vehicle communication terminal.

[0056] In one embodiment, the vehicle communication terminal performs a second anomaly detection, including: the vehicle communication terminal monitors the bus voltage and the application layer connection status between the vehicle communication terminal and the vehicle unit; if the bus voltage is high and the application layer connection between the vehicle communication terminal and the vehicle unit is abnormal, then it is determined that a second type of anomaly exists.

[0057] The bus voltage refers to the power supply voltage provided by the vehicle's infotainment system to the vehicle communication terminal through the Vbus pin of the Universal Serial Bus interface. When the vehicle's infotainment system is in normal operation and the USB interface is powered normally, there is a valid level on the Vbus pin (usually 5V, or other voltage values ​​that conform to the USB standard), indicating that the vehicle's infotainment system is still maintaining the physical layer power supply of the USB link; when the vehicle's infotainment system is powered down, in sleep mode, or the USB interface is closed, this voltage disappears.

[0058] Application layer connection status refers to whether the vehicle-mounted infotainment system and the vehicle-mounted communication terminal maintain communicable status at the application layer protocol. This status is usually maintained through an application layer heartbeat mechanism: the vehicle-mounted infotainment system and the vehicle-mounted communication terminal send heartbeat packets to each other at a preset period. If one party does not receive a heartbeat packet response from the other party for a continuous period of time, it can be determined that the application layer connection has been interrupted.

[0059] For example, the application layer connection state is the socket connection state between the vehicle's infotainment system and the vehicle communication terminal.

[0060] In this embodiment, the vehicle communication terminal first monitors the voltage level of the Vbus pin through the voltage detection circuit of its USB interface. If the Vbus voltage is detected to be at a valid level, for example, according to the USB specification, a Vbus voltage between 4.75V and 5.25V is considered a valid level, then it is confirmed that the vehicle unit is still providing bus power, that is, the physical layer USB connection has not been completely disconnected.

[0061] After confirming the bus voltage is valid, the vehicle communication terminal further detects the application layer connection status with the vehicle's infotainment system. The vehicle communication terminal monitors whether it periodically receives application layer heartbeat packets from the vehicle's infotainment system. If the vehicle communication terminal detects that the application layer heartbeat packet is lost and fails to re-establish the application layer connection with the vehicle's infotainment system for more than a first preset time (e.g., 30 seconds), it determines that the application layer connection is abnormal.

[0062] When the vehicle communication terminal simultaneously meets two conditions—a valid bus voltage and an application layer connection anomaly—it determines that a second type of anomaly exists. This determination indicates that the USB physical connection still exists (the vehicle's infotainment system is not powered off, and the USB cable is not physically disconnected), but the application layer data channel is interrupted, and the network connection is in a false connection state. That is, the vehicle communication terminal believes the physical layer is still connected, but the vehicle's infotainment system may be unable to communicate normally due to driver anomalies, system lag, or other reasons. After determining the existence of a second type of anomaly, the vehicle communication terminal triggers a second recovery operation, such as re-triggering the D+ signal to force the vehicle's infotainment system to re-initiate USB enumeration, thereby restoring the application layer connection.

[0063] In one implementation, before determining the second type of anomaly, the vehicle communication terminal further confirms that the number of times the D+ signal is retried within the current ignition cycle has not reached the first preset limit (e.g., 3 times) to avoid wasting system resources due to frequent reconnections.

[0064] In one implementation, the vehicle communication terminal performs a second recovery operation, including: the vehicle communication terminal re-initiating a physical layer handshake signal to the vehicle's infotainment system to trigger the vehicle's infotainment system to re-establish a network connection.

[0065] In one embodiment, the vehicle communication terminal monitors the bus voltage and the application layer connection status with the vehicle unit, including: if the vehicle communication terminal detects that the application layer heartbeat packet is lost and fails to re-establish the connection for more than a first preset time, it determines that the application layer connection is abnormal; wherein, the application layer heartbeat packet is: a status detection signal sent by the vehicle unit or the vehicle communication terminal to the other party at a preset period when the application layer connection status is detected between the vehicle unit and the vehicle communication terminal.

[0066] In one implementation, the method further includes: when the network connection is normal but the vehicle-mounted unit cannot access the public network, in response to an automatically triggered event or a user-triggered event, the vehicle-mounted unit and the in-vehicle communication terminal cooperate to execute a network reset procedure to restore public network access. This strategy will restore the network when the HU and TBOX USB connection are normal, but the HU cannot access the public network. Network reset is divided into two methods: automatic vehicle-mounted unit-triggered restart and user-initiated network restart, each corresponding to a different execution method.

[0067] In one implementation, the automatically triggered event includes simultaneously meeting the following conditions: the application layer service between the vehicle-mounted unit and the vehicle-mounted communication terminal is normal; the network standard provided by the vehicle-mounted communication terminal meets the preset requirements; and the mobile communication network signal strength provided by the vehicle-mounted communication terminal is within the preset range.

[0068] It should be noted that the pre-verification conditions for automatically triggering the public network recovery process are as follows: Normal application layer service is used to confirm that the application layer communication channel between the vehicle's infotainment system and the in-vehicle communication terminal is unobstructed, avoiding accidental triggering of a public network reset when the USB connection itself is faulty; the network standard meets preset requirements to confirm that the mobile communication network type (such as 4G or 5G) currently registered to the in-vehicle communication terminal has the basic capability to access the public network; and the signal strength is within a preset range to confirm that the mobile communication signal quality at the current location meets the standards, excluding scenarios where internet access is impossible due to no signal or a weak signal. These three conditions are progressively assessed, from application layer connectivity to network type availability and then to signal quality compliance, comprehensively evaluating the objective conditions for recoverable public network access. This ensures that the network reset process is triggered only in reasonable and recoverable scenarios, thereby avoiding the waste of system resources from invalid reset operations and improving the success rate and response efficiency of public network recovery.

[0069] In one implementation, in response to an automatically triggered event, the vehicle-mounted unit and the vehicle-mounted communication terminal collaborate to execute a network reset process to restore public network access, including: the vehicle-mounted unit sending a probe packet to the primary public network address; if sending the probe packet to the primary public network address fails, then sending probe packets to multiple backup public network addresses or multiple public domain name servers one by one; if sending probe packets to all multiple backup public network addresses or multiple public domain name servers fails, it is determined that the public network is inaccessible, and the vehicle-mounted unit generates a reset command and sends it to the vehicle-mounted communication terminal.

[0070] For example, when the vehicle's infotainment system determines that the preconditions for automatic triggering are met, it does not directly execute a reset. Instead, it first confirms whether the public network is indeed inaccessible by sending network probe packets. Specifically, the vehicle's infotainment system probes sequentially according to a preset priority order, that is, it first sends probe packets to a primary public network address (such as a server address). If a response is successfully received, it indicates that the public network is connected normally and there is no need to execute the reset process. If sending probe packets to the primary public network address fails (such as timeout without response), it indicates that the address may be temporarily unreachable. In this case, the vehicle's infotainment system does not immediately determine that the public network is faulty, but instead sends probe packets to multiple backup public network addresses (such as the server addresses of some websites) or public domain name servers (DNS servers) one by one to avoid misjudgment due to a single server failure or local network fluctuations.

[0071] If all probe packets sent to the aforementioned backup addresses or DNS servers fail, it confirms that there is indeed a failure in public network access. The vehicle's infotainment system then determines that public network access is unavailable, generates a reset command, and sends it to the in-vehicle communication terminal to trigger recovery operations such as public network redialing and network configuration reinitialization. This multi-level progressive probe mechanism effectively reduces the probability of false positives, ensuring that the reset process is only triggered when absolutely necessary, avoiding unnecessary reset operations that could negatively impact system resources and user experience.

[0072] For example, the vehicle system can determine whether the current SOCKET connection service with the TBOX is normal; whether the network standard provided by the TBOX is equal to 4G; and whether the CSQ is not equal to 99 or 0. If all the above conditions are met, the vehicle system will execute a public network detection procedure, prioritizing pinging the first URL. If the first URL cannot be pinged, it can ping the second URL, the third URL, and the public DNS. If all pings fail, the vehicle system can automatically trigger a network reset command. The HU will determine the conditions based on the preconditions, and will send a reset command immediately on the first attempt, followed by reset commands at 3-minute intervals thereafter. If the network recovers, the HU will stop resetting the network and clear the retransmission interval.

[0073] After receiving the network reset request automatically triggered by the vehicle's infotainment system, the TBOX will execute the reset command according to the network reset frequency control (the network frequency control count is reset every ignition cycle, with intervals of 3min, 5min, 10min, 15min... with a maximum interval of 15min). (The network reset command can be executed as long as the vehicle's infotainment system and the TBOX maintain a USB connection).

[0074] If the network frequency control reset is satisfied, TBOX will immediately respond with a success command.

[0075] At this point, the vehicle's infotainment system immediately captures 15 seconds of TCPDump packets, routing configuration tables, DNS logs, and PING logs for the public DNS network. After completing the capture, the system executes the functions related to resetting the vehicle's network and returns key interaction logs and execution results to the platform.

[0076] The TBOX adds TCPDump packets, dynamically allocating space based on the remaining memory in the project, and saves the three most recent TCPDump packets, routing configuration tables, and DNS logs. After TBOX completes data capture, it performs a public network redial and reinitializes network-related configurations.

[0077] In one implementation, in response to a user-triggered event, the vehicle infotainment system and the vehicle communication terminal cooperate to execute a network reset process to restore public network access, including: the vehicle infotainment system responding to an active triggering operation for its user interface by sending a reset command to the vehicle communication terminal; the number of times the vehicle communication terminal executes the reset command within the same ignition cycle does not exceed a preset maximum number of times, and the interval between two adjacent reset commands is not less than a second preset duration.

[0078] For example, firstly, when a user finds that the vehicle displays a network signal but cannot actually access the internet, they can perform an active trigger operation through the human-machine interface provided by the vehicle's infotainment system, such as the reset network button on the central control screen. After the vehicle's infotainment system responds to the operation, it sends a reset command to the vehicle's communication terminal according to the interaction protocol between the vehicle's infotainment system and the vehicle's communication terminal. At the same time, the vehicle's communication terminal maintains a reset command execution counter within the same ignition cycle to ensure that the total number of times the user actively triggers the reset command within the current ignition cycle does not exceed a preset limit (e.g., 5 times), thus avoiding excessive consumption of system resources due to the user's anxiety leading to unlimited reset triggers.

[0079] Furthermore, the vehicle-mounted communication terminal records the time of each reset command execution, ensuring that the time interval between two adjacent user-triggered reset commands is no less than a second preset duration (e.g., 60 seconds). This prevents network registration storms and system overload caused by continuous resets within a short period. The aforementioned upper limit for the number of resets and the lower limit for the time interval constitute a two-dimensional constraint mechanism. While providing users with the ability to actively intervene, this effectively ensures a reasonable frequency of reset operations and the stability of system operation, guaranteeing sufficient time for each reset to complete the full network re-registration and configuration process, thereby improving the reset success rate.

[0080] For example, a user actively triggers a network reset command: When a user selects to reset the network through the vehicle's infotainment system, the system sends the command to the TBOX via the system-to-TBOX (V2B) communication protocol. Upon receiving the user's network reset request, the TBOX executes it immediately; identical commands will only be received after the TBOX has completed its network reset. A maximum of five reset commands can be executed within a single ignition cycle, with an interval of more than 60 seconds between identical commands. If the execution conditions are met, the TBOX immediately responds with a successful execution command. At this time, the vehicle's infotainment system immediately captures a 15-second TCPDump packet, routing configuration table, and DNS logs. After capturing the data, the system completes the network reset function and returns key interaction logs and execution results to the platform. The TBOX adds TCPDump packets, dynamically allocating space according to the remaining project space, and saves the three most recent TCPDump packets, routing configuration table, and DNS logs. After completing data capture, the TBOX performs a public network redial and reinitializes the network-related configurations.

[0081] In one implementation, the vehicle-mounted infotainment system and the vehicle-mounted communication terminal collaborate to perform a network reset process to restore public network access, including: the vehicle-mounted infotainment system capturing communication data packets, routing tables, and domain name resolution logs, and performing a network reset on the vehicle-mounted system; and the vehicle-mounted communication terminal capturing communication data packets, routing tables, and domain name resolution logs, performing a public network redial, and re-initializing the network configuration.

[0082] For example, after the vehicle-mounted system determines that the public network cannot be accessed, it sends a reset command to the vehicle communication terminal. Based on this, the vehicle-mounted system first captures the current communication data packets, routing table and domain name resolution logs to record the network status before the reset, providing data support for subsequent fault diagnosis and log tracing. Then, the vehicle-mounted system performs local network reset operations (such as clearing the routing table cache, refreshing the DNS resolution cache, etc.) to eliminate any possible network configuration anomalies on the vehicle-mounted system.

[0083] Simultaneously, upon receiving the reset command, the vehicle-mounted communication terminal also captures communication data packets, routing tables, and domain name resolution logs to preserve the fault scene on the terminal side. It then performs a public network redial operation (i.e., disconnecting the current mobile network connection and re-initiating dial-up registration), and reinitializes network-related configurations (including IP address acquisition, routing table settings, DNS configuration, etc.) after successful dial-up to restore the complete network protocol stack. The capture actions on the vehicle-mounted device side and the vehicle-mounted communication terminal side are independent and executed in parallel, ensuring that the fault scene is completely preserved from both sides. The reset actions on both sides act on the network protocol stack of the vehicle-mounted device and the mobile network access layer of the communication terminal, respectively, forming a full-link reset from the vehicle-mounted device application layer to the mobile communication network access layer, thereby achieving a comprehensive repair of public network anomalies.

[0084] For example, a user actively triggers a network reset command: When a user selects to reset the network through the vehicle's infotainment system, the system sends the command to the TBOX via the system-to-TBOX (V2B) communication protocol. Upon receiving the user's network reset request, the TBOX executes it immediately; identical commands will only be received after the TBOX has completed its network reset. A maximum of five reset commands can be executed within a single ignition cycle, with an interval of more than 60 seconds between identical commands. If the execution conditions are met, the TBOX immediately responds with a successful execution command. At this time, the vehicle's infotainment system immediately captures a 15-second TCPDump packet, routing configuration table, and DNS logs. After capturing the data, the system completes the network reset function and returns key interaction logs and execution results to the platform. The TBOX adds TCPDump packets, dynamically allocating space according to the remaining project space, and saves the three most recent TCPDump packets, routing configuration table, and DNS logs. After completing data capture, the TBOX performs a public network redial and reinitializes the network-related configurations.

[0085] In one embodiment, this invention also provides another method for managing vehicle communication connections, including: Establish a network connection with the vehicle-mounted communication terminal; When the network connection is abnormally disconnected, a first anomaly detection is performed, and a first recovery operation is performed when a first type of anomaly is detected to re-establish the network connection; the vehicle-mounted communication terminal is used to perform a second anomaly detection when the network connection is abnormally disconnected, and a second recovery operation is performed when a second type of anomaly is detected to re-establish the network connection.

[0086] In one embodiment, this invention also provides another method for managing vehicle communication connections, including: Establish a network connection with the vehicle's infotainment system; When the network connection is abnormally disconnected, a second anomaly detection is performed, and a second recovery operation is performed when a second type of anomaly is detected to re-establish the network connection; the vehicle-mounted system is used to perform a first anomaly detection when the network connection is abnormally disconnected, and to perform a first recovery operation when a first type of anomaly is detected to re-establish the network connection.

[0087] The specific implementation methods and effects can be referred to in the above embodiments, and will not be repeated here.

[0088] Based on the same concept, embodiments of the present invention provide an in-vehicle communication connection management system, such as... Figure 2 The diagram shown is a structural block diagram of an in-vehicle communication connection management system. The in-vehicle communication connection management system may include an in-vehicle unit 210 and an in-vehicle communication terminal 220, and a network connection is established between the in-vehicle unit 210 and the in-vehicle communication terminal 220. The vehicle infotainment system 210 is configured to perform a first anomaly detection when the network connection is abnormally disconnected, and perform a first recovery operation when a first type of anomaly is detected to re-establish the network connection. The vehicle-mounted communication terminal 220 is configured to perform a second anomaly detection when the network connection is abnormally disconnected, and perform a second recovery operation when a second type of anomaly is detected to re-establish the network connection.

[0089] The system provided in this embodiment of the invention has the same implementation principle and technical effects as the aforementioned method embodiment. For the sake of brevity, any parts not mentioned in the system embodiment can be referred to the corresponding content in the aforementioned method embodiment.

[0090] This invention also provides an electronic device, such as... Figure 3 The diagram shows the structure of the electronic device, which includes a processor 31 and a memory 30. The memory 30 stores computer-executable instructions that can be executed by the processor 31. The processor 31 executes the computer-executable instructions to implement the above-mentioned vehicle communication connection management method.

[0091] exist Figure 3 In the illustrated embodiment, the electronic device further includes a bus 32 and a communication interface 33, wherein the processor 31, the communication interface 33, and the memory 30 are connected via the bus 32.

[0092] The memory 30 may include high-speed random access memory (RAM) or non-volatile memory, such as at least one disk storage device. Communication between this system network element and at least one other network element is achieved through at least one communication interface 33 (which can be wired or wireless), such as the Internet, wide area network, local area network, metropolitan area network, etc. The bus 32 may be an ISA (Industry Standard Architecture) bus, a PCI (Peripheral Component Interconnect) bus, or an EISA (Extended Industry Standard Architecture) bus, etc. The bus 32 can be divided into address bus, data bus, control bus, etc. For ease of representation, Figure 3 The symbol is represented by a single double-headed arrow, but this does not mean that there is only one bus or one type of bus.

[0093] Processor 31 may be an integrated circuit chip with signal processing capabilities. In implementation, each step of the above method can be completed by the integrated logic circuitry in the hardware of processor 31 or by software instructions. Processor 31 can be a general-purpose processor, including a Central Processing Unit (CPU), a Network Processor (NP), etc.; it can also be a Digital Signal Processor (DSP), an Application Specific Integrated Circuit (ASIC), a Field-Programmable Gate Array (FPGA), or other programmable logic devices, discrete gate or transistor logic devices, or discrete hardware components. The general-purpose processor can be a microprocessor or any conventional processor. The steps of the method disclosed in the embodiments of this invention can be directly implemented by a hardware decoding processor, or implemented by a combination of hardware and software modules in the decoding processor. The software modules can reside in random access memory, flash memory, read-only memory, programmable read-only memory, electrically erasable programmable memory, registers, or other mature storage media in the art. The storage medium is located in the memory. The processor 31 reads the information in the memory and, in conjunction with its hardware, completes the steps of the vehicle communication connection management method of the aforementioned embodiment.

[0094] This invention also provides a computer-readable storage medium storing computer-executable instructions. When these computer-executable instructions are called and executed by a processor, they cause the processor to implement the above-described vehicle communication connection management method. For specific implementation details, please refer to the foregoing method embodiments, which will not be repeated here.

[0095] The computer program products of the vehicle communication connection management method, device and electronic device provided in the embodiments of the present invention include a computer-readable storage medium storing program code. The instructions included in the program code can be used to execute the methods in the preceding method embodiments. For specific implementation, please refer to the method embodiments, which will not be repeated here.

[0096] Unless otherwise specifically stated, the relative steps, numerical expressions, and values ​​of the components and steps described in these embodiments do not limit the scope of the invention.

[0097] If the functionality is implemented as a software functional unit and sold or used as an independent product, it can be stored in a processor-executable, non-volatile, computer-readable storage medium. Based on this understanding, the technical solution of this invention, or the part that contributes to the prior art, or a portion of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute all or part of the steps of the methods of the various embodiments of this invention. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, portable hard drives, read-only memory (ROM), random access memory (RAM), magnetic disks, or optical disks.

[0098] In the description of this invention, it should be noted that the terms "center," "upper," "lower," "left," "right," "vertical," "horizontal," "inner," and "outer," etc., indicate the orientation or positional relationship based on the orientation or positional relationship shown in the accompanying drawings. They are used only for the convenience of describing the invention and for simplifying the description, and do not indicate or imply that the device or element referred to must have a specific orientation, or be constructed and operated in a specific orientation. Therefore, they should not be construed as limitations on the invention. Furthermore, the terms "first," "second," and "third" are used for descriptive purposes only and should not be construed as indicating or implying relative importance.

[0099] Finally, it should be noted that the above embodiments are merely specific implementations of the present invention, used to illustrate the technical solutions of the present invention, and not to limit it. The scope of protection of the present invention is not limited thereto. Although the present invention has been described in detail with reference to the foregoing embodiments, those skilled in the art should understand that any person skilled in the art can still modify or easily conceive of changes to the technical solutions described in the foregoing embodiments within the technical scope disclosed in the present invention, or make equivalent substitutions for some of the technical features; and these modifications, changes, or substitutions do not cause the essence of the corresponding technical solutions to deviate from the spirit and scope of the technical solutions of the embodiments of the present invention, and should all be covered within the scope of protection of the present invention. Therefore, the scope of protection of the present invention should be determined by the scope of the claims.

Claims

1. A method for managing vehicle-mounted communication connections, characterized in that, The method includes: A network connection is established between the vehicle's infotainment system and the in-vehicle communication terminal; When the network connection is abnormally disconnected, the vehicle system performs a first anomaly detection, and performs a first recovery operation when a first type of anomaly is detected, in order to re-establish the network connection; When the network connection is abnormally disconnected, the vehicle-mounted communication terminal performs a second anomaly detection, and when a second type of anomaly is detected, it performs a second recovery operation to re-establish the network connection.

2. The method according to claim 1, characterized in that, The network connection is a Universal Serial Bus (USB) network connection.

3. The method according to claim 2, characterized in that, The establishment of a network connection between the vehicle infotainment system and the vehicle-mounted communication terminal includes: During vehicle initialization, the vehicle system provides bus voltage to the vehicle communication terminal. The vehicle communication terminal responds to the bus voltage being at an effective level by feeding back a positive differential data signal to the vehicle system. After detecting the positive differential data signal, the vehicle's infotainment system initiates a Universal Serial Bus (USB) enumeration to complete the USB network connection with the vehicle communication terminal.

4. The method according to claim 1, characterized in that, The vehicle system performs a first anomaly detection, including: The vehicle-mounted system monitors the connection status of the network interface between itself and the vehicle-mounted communication terminal; If the network interface fails to mount, it is determined that the first type of anomaly exists.

5. The method according to claim 4, characterized in that, The vehicle system performs a first recovery operation, including: The vehicle's infotainment system cuts off and restores power to the network interface to re-establish the network connection.

6. The method according to claim 1, characterized in that, The vehicle-mounted communication terminal performs a second anomaly detection, including: The vehicle-mounted communication terminal monitors the bus voltage and the application layer connection status with the vehicle's infotainment system. If the bus voltage is high and the application layer connection between the vehicle communication terminal and the vehicle system is abnormal, then the second type of abnormality is determined to exist.

7. The method according to claim 6, characterized in that, The vehicle-mounted communication terminal performs a second recovery operation, including: The vehicle-mounted communication terminal re-initiates a physical layer handshake signal to the vehicle's infotainment system to trigger the system to re-establish the network connection.

8. The method according to claim 6, characterized in that, The vehicle-mounted communication terminal monitors the bus voltage and the application layer connection status with the vehicle's infotainment system, including: If the vehicle-mounted communication terminal detects that the application layer heartbeat packet is lost and fails to re-establish the connection for more than a first preset time, it determines that the application layer connection is abnormal. The application layer heartbeat packet is a status detection signal sent by the vehicle-mounted system or the vehicle-mounted communication terminal to the other party at a preset period when the application layer connection status is detected between the vehicle-mounted system and the vehicle-mounted communication terminal.

9. The method according to claim 1, characterized in that, The method further includes: When the network connection is normal but the vehicle-mounted system cannot access the public network, in response to an automatically triggered event or a user-triggered event, the vehicle-mounted system and the vehicle-mounted communication terminal cooperate to execute a network reset process to restore public network access.

10. The method according to claim 9, characterized in that, The automatically triggered event includes events that simultaneously meet the following conditions: The application layer service between the vehicle infotainment system and the vehicle communication terminal is normal. The network standard provided by the vehicle-mounted communication terminal meets the preset requirements; The mobile communication network signal strength provided by the vehicle-mounted communication terminal is within a preset range.

11. The method according to claim 10, characterized in that, In response to the automatically triggered event, the vehicle infotainment system and the in-vehicle communication terminal cooperate to execute a network reset procedure to restore public network access, including: The vehicle-mounted system sends a probe packet to the primary public network address. If sending the probe packet to the primary public network address fails, it sends probe packets to multiple backup public network addresses or multiple public domain name servers one by one. If sending probe packets to all multiple backup public network addresses or multiple public domain name servers fails, it is determined that the public network cannot be accessed, and the vehicle-mounted system generates a reset command and sends it to the vehicle communication terminal.

12. The method according to claim 9, characterized in that, In response to the user-triggered event, the vehicle infotainment system and the in-vehicle communication terminal cooperate to execute a network reset procedure to restore public network access, including: In response to an active triggering operation on its user interface, the vehicle system sends a reset command to the vehicle communication terminal. The number of times the vehicle-mounted communication terminal executes the reset command within the same ignition cycle shall not exceed a preset maximum number of times, and the interval between two adjacent reset commands shall not be less than a second preset duration.

13. The method according to claim 9, characterized in that, The vehicle-mounted system and the vehicle-mounted communication terminal cooperate to perform a network reset process to restore public network access, including: The vehicle-mounted system captures communication data packets, routing tables, and domain name resolution logs, and performs a network reset on the vehicle-mounted system. The vehicle-mounted communication terminal captures communication data packets, routing tables, and domain name resolution logs, performs public network redial, and reinitializes the network configuration.

14. A method for managing vehicle-mounted communication connections, characterized in that, include: Establish a network connection with the vehicle-mounted communication terminal; When the network connection is abnormally disconnected, a first anomaly detection is performed, and a first recovery operation is performed when a first type of anomaly is detected to re-establish the network connection; the vehicle-mounted communication terminal is used to perform a second anomaly detection when the network connection is abnormally disconnected, and to perform a second recovery operation when a second type of anomaly is detected to re-establish the network connection.

15. A method for managing vehicle-mounted communication connections, characterized in that, include: Establish a network connection with the vehicle's infotainment system; When the network connection is abnormally disconnected, a second anomaly detection is performed, and a second recovery operation is performed when a second type of anomaly is detected to re-establish the network connection; the vehicle system is used to perform a first anomaly detection when the network connection is abnormally disconnected, and to perform a first recovery operation when a first type of anomaly is detected to re-establish the network connection.

16. A vehicle-mounted communication connection management system, characterized in that, The system includes a vehicle-mounted infotainment system and an in-vehicle communication terminal, and a network connection is established between the vehicle-mounted infotainment system and the in-vehicle communication terminal. The vehicle system is configured such that when the network connection is abnormally disconnected, the vehicle system performs a first anomaly detection, and when a first type of anomaly is detected, it performs a first recovery operation to re-establish the network connection. The vehicle-mounted communication terminal is configured to perform a second anomaly detection when the network connection is abnormally disconnected, and to perform a second recovery operation when a second type of anomaly is detected, so as to re-establish the network connection.

Images