An exception handling method, vehicle and computer readable storage medium

Abstract

The application provides an exception processing method, a vehicle and a computer readable storage medium, and relates to the technical field of vehicle communication. The method comprises the following steps: in the case that radio technical commission maritime service data received by a telematics terminal is abnormal, determining an exception type of the telematics terminal; determining a target repair strategy corresponding to the exception type, the target repair strategy being at least one of a network repair strategy, a positioning process repair strategy, a chip repair strategy, a service repair strategy and a system repair strategy; and performing exception repair on the telematics terminal based on the target repair strategy. The application solves the problem of abnormal RTCM data received by a T-Box, can avoid unnecessary T-Box system restart, reduces the repair time of the T-Box, realizes the rapid self-healing of the RTCM service, and is beneficial to improving the operation reliability of the T-Box.

Description

Technical Field

[0001] This application relates to the field of vehicle communication technology, and more specifically, to an anomaly handling method, a vehicle, and a computer-readable storage medium in the field of vehicle communication technology. Background Technology

[0002] Currently, high-precision vehicle positioning systems generally rely on the Radio Technical Commission for Maritime Services (RTCM) to correct positioning errors of the Global Navigation Satellite System (GNSS) in real time through a network of ground-based augmentation stations, achieving centimeter-level positioning accuracy. In this architecture, the Telematics Box (T-Box), acting as the vehicle's communication terminal, is responsible for receiving RTCM data from the cloud or a continuously operating reference station network and transmitting the RTCM data to the vehicle's domain controller, thereby achieving high-precision positioning.

[0003] However, in actual operation, the RTCM data received by the T-Box may encounter abnormalities (such as data interruption). Currently, the common solution is to "restart the T-Box system." This method not only has a long recovery period, but also causes multiple vehicle networking functions carried by the T-Box (such as remote vehicle control, emergency call, vehicle diagnostics, etc.) to become temporarily unavailable, seriously affecting the availability of the entire vehicle and the user experience. Summary of the Invention

[0004] This application provides an anomaly handling method, a vehicle, and a computer-readable storage medium. Instead of directly restarting the T-Box to resolve the issue of abnormal RTCM data reception, this application first identifies the type of T-Box anomaly, then locates the corresponding repair strategy based on the anomaly type, and finally repairs the T-Box based on the located repair strategy. This resolves the problem of abnormal RTCM data reception by the T-Box, avoiding unnecessary T-Box system restarts, reducing T-Box repair time, achieving rapid self-healing of the RTCM service, and improving the operational reliability of the T-Box.

[0005] In a first aspect, an anomaly handling method is provided, applied to a remote information processing terminal. The anomaly handling method includes: determining the anomaly type of the remote information processing terminal when the Radio Technical Committee Maritime Service data received by the remote information processing terminal is abnormal; determining a target repair strategy corresponding to the anomaly type, wherein the target repair strategy is at least one of a network repair strategy, a positioning process repair strategy, a chip repair strategy, a service repair strategy, and a system repair strategy; and performing anomaly repair on the remote information processing terminal based on the target repair strategy.

[0006] Based on the aforementioned technical issues, this application, when encountering abnormal RTCM data reception by the T-Box, does not simply resort to directly restarting the T-Box to resolve the problem. Instead, it first performs a precise diagnosis of the T-Box's anomaly to identify the type of anomaly and determine the root cause. Then, based on the anomaly type, it determines a repair strategy to resolve the T-Box anomaly. Finally, based on the determined repair strategy, it precisely repairs the T-Box, restoring it to normal operation and enabling normal RTCM data reception. This not only solves the problem of abnormal RTCM data reception by the T-Box but also avoids unnecessary T-Box system restarts. Because this application does not restart the T-Box system every time an anomaly occurs to restore the T-Box to normal, the time for repairing the T-Box based on the repair strategy determined by the anomaly type is significantly shorter than the time for restarting the T-Box system to repair the anomaly. This reduces the T-Box repair time, enabling rapid self-healing of the RTCM service and reducing the number of times the T-Box system needs to be restarted frequently because the anomaly cannot be resolved after restarting the T-Box system. This is beneficial to improving the operational reliability of the T-Box.

[0007] In one possible implementation, determining the anomaly type of the remote information processing terminal includes: if a first condition is met, determining that the anomaly type includes a network anomaly, wherein the first condition includes at least one of receiving a network disconnection event, access point name dialing failure, and transmission control protocol connection disconnection; determining the target repair strategy corresponding to the anomaly type includes: determining that the target repair strategy corresponding to the network anomaly is a network repair strategy; and performing anomaly repair on the remote information processing terminal based on the target repair strategy includes: if the target repair strategy includes a network repair strategy, controlling the network module in the remote information processing terminal to re-initiate a data connection establishment request to the operator's core network based on the current access point name configuration parameters.

[0008] In one possible implementation, determining the anomaly type of the remote information processing terminal includes: if a second condition is met, determining that the anomaly type includes a process-related anomaly, the second condition including not receiving a heartbeat signal from the positioning process within a preset time period or the positioning process exiting abnormally; determining the target repair strategy corresponding to the anomaly type includes: determining that the target repair strategy corresponding to the process-related anomaly is a positioning process repair strategy; and performing anomaly repair on the remote information processing terminal based on the target repair strategy includes: if the target repair strategy includes a positioning process repair strategy, restarting the positioning process in the remote information processing terminal.

[0009] In one possible implementation, determining the anomaly type of the telematics terminal includes: if a third condition is met, determining that the anomaly type includes a chip-related anomaly, wherein the third condition includes the telematics terminal failing to receive Radio Technical Committee Maritime Service data via the Global Navigation Satellite System (GNSS) chip or the GNSS data received by the telematics terminal via the GNSS chip being invalid data; determining the target repair strategy corresponding to the anomaly type includes: determining that the target repair strategy corresponding to the chip-related anomaly is a chip repair strategy; and performing anomaly repair on the telematics terminal based on the target repair strategy includes: if the target repair strategy includes a chip repair strategy, resetting the GNSS chip.

[0010] In one possible implementation, determining the anomaly type of the telematics terminal includes: if a fourth condition is met, determining that the anomaly type includes a service-related anomaly, where the fourth condition includes at least one of the following: expired license for the Radio Technical Committee Maritime Service, Radio Technical Committee Maritime Service exceeding coverage area, and quota exhaustion for the Radio Technical Committee Maritime Service; determining the target repair strategy corresponding to the anomaly type includes: determining that the target repair strategy corresponding to the service-related anomaly is a service repair strategy; and performing anomaly repair on the telematics terminal based on the target repair strategy includes: if the target repair strategy includes a service repair strategy, re-authenticating the Radio Technical Committee Maritime Service to regain access to the Radio Technical Committee Maritime Service data.

[0011] In one possible implementation, determining the anomaly type of the telematics terminal includes: if the fifth condition is met, determining the anomaly type as a system anomaly, the fifth condition including normal network status, normal positioning process status, normal Global Navigation Satellite System chip status, normal status of Radio Technical Committee Maritime Service, and abnormal Radio Technical Committee Maritime Service data; determining the target repair strategy corresponding to the anomaly type includes: determining the target repair strategy corresponding to the system anomaly as a system repair strategy; and performing anomaly repair on the telematics terminal based on the target repair strategy includes: if the target repair strategy is a system repair strategy, restarting the telematics terminal.

[0012] In one possible implementation, the anomaly handling method further includes: when the Radio Technical Committee Maritime Service data received by the remote information processing terminal is abnormal, sorting the repair times corresponding to the network repair strategy, positioning process repair strategy, chip repair strategy, service repair strategy, and system repair strategy to obtain a first sorting result; executing the repair strategy corresponding to the minimum repair time in the first sorting result; determining whether the Radio Technical Committee Maritime Service data received by the remote information processing terminal is abnormal; when the Radio Technical Committee Maritime Service data received by the remote information processing terminal is abnormal, deleting the minimum repair time in the first sorting result to obtain a second sorting result; using the second sorting result as the first sorting result, and returning to the step of executing the repair strategy corresponding to the minimum repair time in the first sorting result.

[0013] In one possible implementation, the anomaly handling method further includes: simultaneously executing network repair strategy, positioning process repair strategy, chip repair strategy, and service repair strategy when the Radio Technical Committee Maritime Service data received by the remote information processing terminal is abnormal; determining whether the Radio Technical Committee Maritime Service data received by the remote information processing terminal is abnormal; and executing system repair strategy when the Radio Technical Committee Maritime Service data received by the remote information processing terminal is abnormal.

[0014] Secondly, an anomaly handling device is provided for use in a remote information processing terminal. The anomaly handling device includes:

[0015] The type identification module is used to determine the type of anomaly of the remote information processing terminal in the event of anomalies in the Radio Technical Committee Maritime Service data received by the remote information processing terminal. The strategy determination module is used to determine the target repair strategy corresponding to the anomaly type. The target repair strategy is at least one of the following: network repair strategy, process location repair strategy, chip repair strategy, service repair strategy, and system repair strategy. The anomaly repair module is used to repair anomalies in remote information processing terminals based on target repair strategies.

[0016] In one possible implementation, the type identification module is specifically used to determine, under the condition that a first condition is met, that the exception type includes network exceptions, and the first condition includes at least one of receiving a network disconnection event, access point name dialing failure, and transmission control protocol connection disconnection. The strategy determination module is specifically used to determine the target repair strategy corresponding to network-type anomalies as a network repair strategy. The anomaly repair module is specifically used to control the network module in the remote information processing terminal to re-initiate a data connection establishment request to the operator's core network based on the current access point name configuration parameters when the target repair strategy includes a network repair strategy.

[0017] In one possible implementation, the type identification module is specifically used to determine the exception type as a process-related exception when the second condition is met. The second condition includes not receiving a heartbeat signal from the positioning process within a preset time period or the positioning process exiting abnormally. The strategy determination module is specifically used to determine the target repair strategy corresponding to the process-type exception, which is the process repair strategy. The anomaly repair module is specifically used to restart the positioning process in the remote information processing terminal when the target repair strategy includes a positioning process repair strategy.

[0018] In one possible implementation, the type identification module is specifically used to determine the anomaly type as a chip-related anomaly when a third condition is met. The third condition includes the telematics terminal not receiving Radio Technical Committee Maritime Service data through the Global Navigation Satellite System chip or the Radio Technical Committee Maritime Service data received by the telematics terminal through the Global Navigation Satellite System chip being invalid data. The strategy determination module is specifically used to determine the target repair strategy corresponding to the chip-type anomaly as the chip repair strategy. The anomaly repair module is specifically used to reset the global navigation satellite system chip when the target repair strategy includes a chip repair strategy.

[0019] In one possible implementation, the type identification module is specifically used to determine, upon satisfying the fourth condition, that the exception type includes service-related exceptions, and the fourth condition includes at least one of the following: expired license for Radio Technical Committee Maritime Service, Radio Technical Committee Maritime Service outside coverage area, and quota exhaustion for Radio Technical Committee Maritime Service. The strategy determination module is specifically used to determine the target repair strategy corresponding to the service-type exception as the service repair strategy. The anomaly repair module is specifically used to re-authenticate the Radio Technical Committee Maritime Service when the target repair strategy includes a service repair strategy, in order to regain access to the Radio Technical Committee Maritime Service data.

[0020] In one possible implementation, the type identification module is specifically used to determine the anomaly type as a system anomaly when the fifth condition is met. The fifth condition includes the normal network status of the remote information processing terminal, the normal status of the positioning process, the normal status of the global navigation satellite system chip, the normal status of the Radio Technical Committee Maritime Service, and the abnormal data of the Radio Technical Committee Maritime Service. The strategy determination module is specifically used to determine the target repair strategy corresponding to the system-type exception as the system repair strategy. The anomaly repair module is specifically used to restart the remote information processing terminal when the target repair strategy is the system repair strategy.

[0021] In one possible implementation, the anomaly repair module is specifically used to, in the event of anomalies in the Radio Technical Committee Maritime Service data received by the remote information processing terminal, sort the repair times corresponding to the network repair strategy, positioning process repair strategy, chip repair strategy, service repair strategy, and system repair strategy to obtain a first sorting result; execute the repair strategy corresponding to the minimum repair time in the first sorting result; determine whether the Radio Technical Committee Maritime Service data received by the remote information processing terminal is abnormal; if the Radio Technical Committee Maritime Service data received by the remote information processing terminal is abnormal, delete the minimum repair time in the first sorting result to obtain a second sorting result; use the second sorting result as the first sorting result, and return to the step of executing the repair strategy corresponding to the minimum repair time in the first sorting result.

[0022] In one possible implementation, the anomaly repair module is specifically used to simultaneously execute network repair strategy, positioning process repair strategy, chip repair strategy, and service repair strategy when the Radio Technical Committee Maritime Service data received by the remote information processing terminal is abnormal; determine whether the Radio Technical Committee Maritime Service data received by the remote information processing terminal is abnormal; and execute system repair strategy when the Radio Technical Committee Maritime Service data received by the remote information processing terminal is abnormal.

[0023] Thirdly, a vehicle is provided that includes a memory and a processor. The memory is used to store executable program code, and the processor is used to call and run the executable program code from the memory, causing the vehicle to execute the exception handling method in the first aspect or any possible implementation thereof.

[0024] Fourthly, a computer program product is provided, comprising: computer program code, which, when run on a computer, causes the computer to execute the exception handling method in the first aspect or any possible implementation thereof.

[0025] Fifthly, a computer-readable storage medium is provided that stores computer program code, which, when executed on a computer, causes the computer to perform the exception handling method described in the first aspect or any possible implementation thereof. Attached Figure Description

[0026] Figure 1 A schematic flowchart of an exception handling method provided in an embodiment of this application is shown; Figure 2 Another schematic flowchart of an exception handling method provided in an embodiment of this application is shown; Figure 3 This paper shows a schematic diagram of the structure of an exception handling device provided in an embodiment of the present application; Figure 4 A schematic diagram of the structure of a vehicle provided in an embodiment of this application is shown. Detailed Implementation

[0027] The technical solutions in this application will be clearly and thoroughly described below with reference to the accompanying drawings. In the description of the embodiments of this application, unless otherwise stated, " / " means "or," for example, A / B can mean A or B. "And / or" in the text is merely a description of the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent: A existing alone, A and B existing simultaneously, and B existing alone. Furthermore, in the description of the embodiments of this application, "multiple" refers to two or more than two.

[0028] Hereinafter, the terms "first" and "second" are used for descriptive purposes only and should not be construed as implying or suggesting relative importance or implicitly indicating the number of technical features indicated. Thus, a feature defined as "first" or "second" may explicitly or implicitly include one or more of that feature.

[0029] Currently, high-precision vehicle positioning systems generally rely on RTCM services, which use a ground-based augmentation station network to correct GNSS positioning errors in real time to achieve centimeter-level positioning accuracy. In this architecture, the T-Box, as the vehicle-mounted communication terminal, is responsible for receiving RTCM data from the cloud or a continuously operating reference station network and sending the RTCM data to the vehicle's domain controller, thereby achieving high-precision positioning.

[0030] However, in actual operation, the RTCM data received by the T-Box may encounter abnormalities (such as data interruption). Currently, the common solution is to "restart the T-Box system." This method not only has a long recovery period, but also causes multiple vehicle networking functions carried by the T-Box (such as remote vehicle control, emergency call, vehicle diagnostics, etc.) to become temporarily unavailable, seriously affecting the availability of the entire vehicle and the user experience.

[0031] To address the aforementioned issues, this application provides an anomaly handling method, a vehicle, and a computer-readable storage medium. The aim is to avoid unnecessary restarts of the Telecommunications Processing Terminal (T-Box) when anomalies occur in the Radio Technical Committee Maritime Service data (RTCM data) received by the T-Box. Specifically, when the T-Box experiences network, software, hardware, or service anomalies, these anomalies all cause the T-Box to exhibit the same symptoms, such as an interruption in the RTCM data received. Instead of directly restarting the T-Box to resolve the RTCM data reception anomaly, this application first identifies the type of anomaly in the T-Box, then locates the corresponding repair strategy based on the anomaly type, and finally repairs the T-Box based on the located repair strategy. This resolves the issue of abnormal RTCM data reception by the T-Box, avoiding unnecessary T-Box system restarts, reducing T-Box repair time, achieving rapid self-healing of the RTCM service, and improving the operational reliability of the T-Box.

[0032] The following is an embodiment of an exception handling method provided in this application specification.

[0033] Figure 1 A schematic flowchart of an exception handling method provided in an embodiment of this application is shown, such as... Figure 1 As shown in the embodiment of this application, the execution subject of an exception handling method is the vehicle's T-Box, and the exception handling method includes the following scheme: S110: In the event of an anomaly in the Radio Technical Committee Maritime Service data received by the telematics terminal, determine the type of anomaly of the telematics terminal.

[0034] In one exemplary embodiment, when the T-Box experiences network, software, hardware, or service anomalies, these anomalies all cause the T-Box to exhibit the same symptoms, such as interrupted RTCM data reception. Causes of network anomalies include Access Point Name (APN) dialing failure, service provider network problems, and weak network signal; software anomalies include abnormal exit of the positioning process; hardware anomalies include malfunction of the GNSS chip within the T-Box; and service anomalies include expired RTCM service authentication, exceeding coverage area, and quota exhaustion. Therefore, this application does not simply restart the T-Box to restore normal operation when RTCM data reception is abnormal. Instead, it employs different repair methods for different anomaly types. For example, if the problem is a network malfunction, the network of the T-Box will be repaired to restore the T-Box to normal operation; if the problem is a software malfunction, the software of the T-Box will be repaired to restore the T-Box to normal operation, and so on.

[0035] This application pre-configures a multi-dimensional monitoring module for the T-Box, including an RTCM data stream monitoring module, a network connection status monitoring module, a positioning process status monitoring module, a GNSS chip status monitoring module, a service status monitoring module, and a system status monitoring module. Specifically, after the T-Box receives RTCM data, the RTCM data stream monitoring module verifies the data. If the verification passes, the RTCM data is considered valid, thus confirming that the T-Box is functioning normally; if the verification fails, the RTCM data is considered invalid, thus indicating that the T-Box has malfunctioned. To determine the specific type of malfunction, the network connection status monitoring module, the positioning process status monitoring module, the GNSS chip status monitoring module, the service status monitoring module, and the system status monitoring module simultaneously perform anomaly type detection on the T-Box, thereby identifying the specific type of malfunction. The anomaly types can be categorized into network anomalies, process anomalies (also known as software anomalies), chip anomalies (also known as hardware anomalies), service anomalies, and system anomalies. The T-Box is simultaneously monitored by the network connection status monitoring module, the positioning process status monitoring module, the GNSS chip status monitoring module, the service status monitoring module, and the system status monitoring module. The anomaly type of the T-Box may include at least one of the following: network anomaly, process anomaly, chip anomaly, service anomaly, and system anomaly.

[0036] S120: Determine the target repair strategy corresponding to the anomaly type. The target repair strategy is at least one of the following: network repair strategy, process location repair strategy, chip repair strategy, service repair strategy, and system repair strategy.

[0037] Based on the five anomaly types mentioned above, different repair strategies are pre-set for each type of anomaly in the T-Box. These repair strategies are stored in a repair strategy set, which specifically includes network repair strategies, location process repair strategies, chip repair strategies, service repair strategies, and system repair strategies. Among them, the network repair strategy refers to the strategy for repairing the T-Box's network, the location process repair strategy refers to the strategy for repairing the T-Box's location, the chip repair strategy refers to the strategy for repairing the T-Box's GNSS chip, the service repair strategy refers to the strategy for repairing the T-Box's RTCM service, and the system repair strategy refers to the strategy for repairing the entire T-Box system.

[0038] After identifying the anomaly type of the T-Box, the target repair strategy corresponding to the anomaly type is determined from the set of repair strategies. The number of target repair strategies is the same as the number of anomaly types identified for the T-Box. For example, if only one anomaly type is identified for the T-Box, the target repair strategy is one of the following: network repair strategy, process location repair strategy, chip repair strategy, service repair strategy, and system repair strategy. If two anomaly types are identified for the T-Box, the target repair strategy is two of the following: network repair strategy, process location repair strategy, chip repair strategy, service repair strategy, and system repair strategy, and so on. In other words, the determined target repair strategies corresponding to the anomaly types include at least one of the following: network repair strategy, process location repair strategy, chip repair strategy, service repair strategy, and system repair strategy.

[0039] S130: Perform anomaly repair on remote information processing terminals based on target repair strategies.

[0040] After determining the target repair strategy for T-Box based on the anomaly type, the target repair strategy is used to repair the T-Box, restoring it to normal and enabling normal reception of RTCM data. This not only solves the problem of abnormal RTCM data received by T-Box, but also avoids unnecessary T-Box system restarts.

[0041] Based on the technical problems arising from S110 to S130 above, this application, when the RTCM data received by the T-Box is abnormal, does not simply solve the problem by directly restarting the T-Box. Instead, it first performs a precise diagnosis of the abnormality in the T-Box to identify the type of abnormality and the root cause of the abnormality. Then, based on the type of abnormality, it determines a repair strategy to resolve the T-Box abnormality. Finally, based on the determined repair strategy, it precisely repairs the T-Box abnormality, restoring the T-Box to normal and enabling normal reception of RTCM data. This not only solves the problem of abnormal RTCM data received by the T-Box but also avoids unnecessary T-Box system restarts. Because this application does not restart the T-Box system every time an anomaly occurs to restore the T-Box to normal, the time for repairing the T-Box based on the repair strategy determined by the anomaly type is significantly shorter than the time for restarting the T-Box system to repair the anomaly. This reduces the T-Box repair time, enabling rapid self-healing of the RTCM service and reducing the number of times the T-Box system needs to be restarted frequently because the anomaly cannot be resolved after restarting the T-Box system. This is beneficial to improving the operational reliability of the T-Box.

[0042] In one possible implementation, determining the anomaly type of the remote information processing terminal includes at least one of the following steps: (1) If the first condition is met, determine that the anomaly type includes network anomalies; (2) If the second condition is met, the exception type is determined to include process-related exceptions; (3) If the third condition is met, the exception type is determined to include chip-related exceptions; (4) If the fourth condition is met, the exception type is determined to include service-related exceptions; (5) If the fifth condition is met, the exception type is determined to be a system exception.

[0043] The process by which the network connection status monitoring module determines the type of T-Box anomaly involves the module judging whether the T-Box meets a first condition. The first condition includes at least one of the following: receiving a network disconnection event, APN dialing failure, and Transmission Control Protocol (TCP) connection disconnection. If the T-Box does not meet the first condition, it is considered that the network status of the T-Box is normal, meaning that the anomaly of the T-Box is not caused by the network. If the T-Box meets the first condition, it is considered that the network status of the T-Box is abnormal, meaning that the anomaly of the T-Box is caused by an abnormal network status. Therefore, the anomaly type of the T-Box is determined to include network-related anomalies.

[0044] The process by which the positioning process status monitoring module determines the type of T-Box anomaly involves the module judging whether the T-Box meets the second condition. The second condition includes not receiving a heartbeat signal from the positioning process within a preset time (i.e., the positioning process heartbeat timeout) or the positioning process exiting abnormally (i.e., the positioning process crashing). If the T-Box does not meet the second condition, it is considered that the positioning process status of the T-Box is normal, and the anomaly of the T-Box is not caused by the positioning process. If the T-Box meets the second condition, it is considered that the positioning process status of the T-Box is abnormal, and the anomaly of the T-Box is caused by the abnormal positioning process status. Therefore, the anomaly type of the T-Box is determined to include process-related anomalies.

[0045] The process by which the GNSS chip status monitoring module determines the anomaly type of the T-Box involves the GNSS chip status monitoring module judging whether the T-Box meets the third condition. The third condition includes whether the T-Box does not receive RTCM data through the GNSS chip or whether the RTCM data received by the T-Box through the GNSS chip is invalid. If the T-Box does not meet the third condition, the GNSS chip status of the T-Box is considered normal, and the anomaly of the T-Box is not caused by the GNSS chip. If the T-Box meets the third condition, the GNSS chip status of the T-Box is considered abnormal, and the anomaly of the T-Box is caused by the GNSS chip malfunction. Therefore, the anomaly type of the T-Box is determined to include chip-related anomalies.

[0046] The process by which the service status monitoring module determines the anomaly type of the T-Box involves the module judging whether the T-Box meets the fourth condition. The fourth condition includes an expired RTCM service license, RTCM service exceeding coverage, and RTCM service quota exhaustion. If the T-Box does not meet the fourth condition, the RTCM service of the T-Box is considered to be in normal status, and the anomaly is not caused by the RTCM service. If the T-Box meets the fourth condition, the RTCM service of the T-Box is considered to be in abnormal status, and the anomaly is caused by the abnormal status of the RTCM service. Therefore, the anomaly type of the T-Box is determined to include service-related anomalies.

[0047] The process by which the system status monitoring module determines the anomaly type of the T-Box involves checking whether the T-Box meets the fifth condition. This fifth condition includes: the T-Box's network status is normal (i.e., the T-Box meets the first condition); the positioning process status is normal (i.e., the T-Box meets the second condition); the GNSS chip status is normal (i.e., the T-Box meets the third condition); and the RTCM service status is normal (i.e., the T-Box meets the fourth condition), but the RTCM data is abnormal. If the T-Box meets the fourth condition, it is considered that the cause of the T-Box's anomaly is not due to the network, positioning process, GNSS chip, or RTCM service, but rather to other problems within the T-Box's system. Therefore, the anomaly type of the T-Box is determined to be a system-related anomaly.

[0048] By using network connection status monitoring module, positioning process status monitoring module, GNSS chip status monitoring module, service status monitoring module, and system status monitoring module, the abnormality type of the T-Box is identified, enabling accurate diagnosis of abnormal problems in the T-Box. Based on the specific abnormality type, different repair methods can be sampled to repair the T-Box. This reduces the frequency of vehicle networking function interruption caused by simply restarting the T-Box system to solve the abnormality problem, which is conducive to improving the operational reliability of the T-Box.

[0049] In one possible implementation, determining the target repair strategy from the repair strategy set of the remote information processing terminal based on the anomaly type includes the following steps: When the anomaly type includes network anomalies, the network repair strategy is determined as the target repair strategy; When the exception type includes process-related exceptions, the targeted repair strategy is determined by identifying the process to be repaired. When the anomaly type includes chip-related anomalies, the chip repair strategy is determined as the target repair strategy. When the exception type includes service-related exceptions, the service repair strategy is determined as the target repair strategy; When the exception type is a system-level exception, the system repair strategy is determined as the target repair strategy.

[0050] After identifying the anomaly type of the T-Box, if the anomaly type includes a network-related anomaly, the anomaly is considered to be caused by the network, and a network repair strategy is selected as the target repair strategy. If the anomaly type includes a process-related anomaly, the anomaly is considered to be caused by the location process, and a location process repair strategy is selected as the target repair strategy. If the anomaly type includes a chip-related anomaly, the anomaly is considered to be caused by the GNNS chip, and a chip repair strategy is selected as the target repair strategy. If the anomaly type includes a service-related anomaly, the anomaly is considered to be caused by the RTCM service, and a service repair strategy is selected as the target repair strategy. If the anomaly type is a system-related anomaly, the anomaly is considered to be not caused by the network, location process, GNNS chip, or RTCM service, and a system repair strategy is selected as the target repair strategy. Specifically, if the anomaly type is a system-related anomaly, the target repair strategy only includes system repair strategies; if the anomaly type is not a system-related anomaly, the target repair strategy includes at least one of the following: network repair strategy, location process repair strategy, chip repair strategy, and service repair strategy.

[0051] In one possible implementation, performing anomaly repair on a remote information processing terminal based on a target repair strategy includes at least one of the following steps: (1) When the target repair strategy includes a network repair strategy, control the network module in the remote information processing terminal to re-initiate a data connection establishment request to the operator's core network based on the current access point name configuration parameters; (2) If the target repair strategy includes a location process repair strategy, restart the location process in the remote information processing terminal; (3) If the target repair strategy includes a chip repair strategy, reset the global navigation satellite system chip; (4) If the target repair strategy includes a service repair strategy, re-authenticate the Radio Technical Committee Maritime Service in order to regain access to the Radio Technical Committee Maritime Service data. (5) If the target repair strategy is the system repair strategy, restart the remote information processing terminal.

[0052] If the anomaly type includes network anomalies, and the target repair strategy corresponding to the network anomaly is determined to include network repair strategies, and thus the repair object is determined to include the network in the T-Box, then the first repair operation corresponding to the network repair strategy is executed. That is, the network module in the T-Box is controlled to re-initiate a data connection establishment request to the operator's core network based on the current APN configuration parameters in order to repair the network in the T-Box.

[0053] If the exception type includes process-related exceptions, and the target repair strategy corresponding to the process-related exception is determined to include the process location repair strategy, then the repair object is determined to include the location process. In this case, the second repair operation corresponding to the location process repair strategy is executed, that is, the location process is restarted, thereby repairing the location process.

[0054] If the exception type includes chip-related exceptions, and the target repair strategy corresponding to the chip-related exception is determined to include the chip repair strategy, then the repair object is determined to be the GNNS chip. In this case, the third repair operation corresponding to the chip repair strategy is executed, that is, the GNNS chip is reset.

[0055] If the exception type includes service-related exceptions, and the target repair strategy corresponding to the service-related exception is determined to be a service repair strategy, then the repair object is determined to be the RTCM service. In this case, the fourth repair operation corresponding to the service repair strategy is executed, that is, the RTCM service is re-authenticated so that the RTCM service can regain access to RTCM data.

[0056] If the exception type includes system-level exceptions, and the target repair strategy corresponding to the system-level exception is determined to be the system repair strategy, then the repair object is determined to be the T-Box system. In this case, the fifth repair operation corresponding to the system repair strategy is executed, which is to restart the T-Box system.

[0057] It is worth noting that if the target repair strategy includes only one of the network repair strategy, the location process repair strategy, the chip repair strategy, and the service repair strategy, then only the repair operation corresponding to that target repair strategy will be executed; if the target repair strategy includes multiple of the network repair strategy, the location process repair strategy, the chip repair strategy, and the service repair strategy, then the repair operations corresponding to each of the multiple repair strategies included in the target repair strategy will be executed simultaneously, which can reduce the repair time and thus shorten the interruption time of the vehicle networking function.

[0058] In one possible implementation, the above exception handling method further includes the following steps: In the event of anomalies in the maritime service data of the Radio Technical Committee received by the remote information processing terminal, the repair times corresponding to the network repair strategy, positioning process repair strategy, chip repair strategy, service repair strategy and system repair strategy are sorted to obtain the first sorting result. Execute the repair strategy corresponding to the shortest repair time in the first sorting result; Determine whether the maritime service data received by the Radio Technical Committee received by the remote information processing terminal is abnormal; In the event of an anomaly in the maritime service data of the Radio Technical Committee received by the telematics terminal, the minimum repair time in the first sorting result is deleted to obtain the second sorting result; Use the second sorting result as the first sorting result, and return to the step of executing the repair strategy corresponding to the minimum repair time in the first sorting result.

[0059] In addition to distinguishing the anomaly types of T-Boxes and repairing the anomalies of T-Boxes based on the target repair strategies corresponding to the anomaly types, this application can also select a target repair strategy to repair the anomalies of T-Boxes based on the repair time required for each repair strategy to repair the anomalies of T-Boxes.

[0060] Specifically, after an anomaly occurs in the RTCM data received by the T-Box, the repair times corresponding to the network repair strategy, location process repair strategy, chip repair strategy, service repair strategy, and system repair strategy are sorted to obtain a first sorting result. For example, if the repair times corresponding to the network repair strategy, location process repair strategy, chip repair strategy, service repair strategy, and system repair strategy are T1, T2, T3, T4, and T5 respectively, and assuming the first sorting result is T1 < T2 < T3 < T4 < T5, then the network repair strategy is executed. After the network repair strategy is completed, it is checked again whether the RTCM data received by the T-Box is abnormal. If the RTCM data received by the T-Box is normal, the T-Box's anomaly repair process is exited; if the RTCM data received by the T-Box is still abnormal, T1 is removed from the first sorting result to obtain a second sorting result, which is T2 < T3 < T4 < T5. The second sorting result is used as the first sorting result. Then, the repair strategy corresponding to the minimum repair time in the first sorting result is executed, i.e., the location process repair strategy is executed. After the location process repair strategy is completed, the T-Box's received RTCM data is checked again for abnormality. If the received RTCM data is normal, the T-Box's abnormality repair process exits. If the received RTCM data is still abnormal, T2 is removed from the first sorting result, resulting in a second sorting result where T3 < T4 < T5. The repair strategy corresponding to the minimum repair time in the first sorting result is then executed, and so on, until the system repair strategy is completed. After the system repair strategy is completed, if the received RTCM data is normal, the T-Box's abnormality repair process exits. If the received RTCM data is still abnormal, a T-Box abnormality message is output to remind the user to have the T-Box repaired as soon as possible.

[0061] Based on the repair time required to fix T-Box anomalies using various repair strategies, a target repair strategy is selected to fix the T-Box anomalies. This avoids the problem of directly restarting the T-Box system when an anomaly occurs, which would cause multiple vehicle networking functions to be temporarily unavailable. This helps to improve the user experience of vehicle networking functions.

[0062] In one possible implementation, the above exception handling method further includes the following steps: In the event of an anomaly in the Radio Technical Committee Maritime Service data received by the remote information processing terminal, network repair strategy, positioning process repair strategy, chip repair strategy, and service repair strategy are executed simultaneously. Determine whether the maritime service data received by the Radio Technical Committee received by the remote information processing terminal is abnormal; In the event of anomalies in the Radio Technical Committee Maritime Service data received by the remote information processing terminal, a system repair strategy shall be implemented.

[0063] In addition to selecting a target repair strategy based on the repair time required for each repair strategy to fix the T-Box anomaly, this application may also include a third repair method. Specifically, after the RTCM data received by the T-Box becomes abnormal, a network repair strategy, a location process repair strategy, a chip repair strategy, and a service repair strategy are executed simultaneously. After all four repair strategies have been completed, the RTCM data received by the T-Box is checked again to see if it is abnormal. If the RTCM data received by the T-Box is normal, the T-Box anomaly repair process is exited; if the RTCM data received by the T-Box is still abnormal, a system repair strategy is executed. After the system repair strategy is completed, if the RTCM data received by the T-Box is normal, the T-Box anomaly repair process is exited; if the RTCM data received by the T-Box is still abnormal, a T-Box anomaly message is output to remind the user to have the T-Box repaired as soon as possible.

[0064] By simultaneously executing network repair strategies, location process repair strategies, chip repair strategies, and service repair strategies, the problem of multiple vehicle networking functions being temporarily unavailable due to directly restarting the T-Box system when an abnormality occurs can be avoided, which is conducive to improving the user experience of vehicle networking functions.

[0065] The following is another embodiment of an exception handling method provided in this application specification.

[0066] Figure 2 Another schematic flowchart of an exception handling method provided in an embodiment of this application is shown, such as... Figure 2 As shown in the embodiment of this application, the execution subject of an exception handling method is the vehicle's T-Box, and the exception handling method includes the following scheme: S220: In the event of an abnormality in the RTCM data received by the T-Box, determine the type of abnormality of the T-Box; if the type of abnormality of the T-Box includes at least one of network abnormality, process abnormality, chip abnormality, and service abnormality, execute S221; if the type of abnormality of the T-Box is a system abnormality, execute S222. S221: Obtain the target repair operation corresponding to the exception type from the first to fourth repair operations, and execute the target repair operation to repair the T-Box exception; S222: Perform the fifth repair operation to repair the T-Box for anomalies.

[0067] In another exemplary embodiment, if the RTCM data received by the T-Box is abnormal, it is assumed that the T-Box itself is abnormal, and the type of abnormality of the T-Box is then identified. If the abnormality type of the T-Box is a system-level abnormality, the fifth repair operation is performed, that is, the T-Box system is restarted, thereby attempting to repair the abnormality of the T-Box.

[0068] If the T-Box's exception type includes at least one of network exception, process exception, chip exception, and service exception, then the target repair operation corresponding to the exception type is obtained from the first to fourth repair operations, and then the target repair operation is executed to repair the T-Box.

[0069] If the anomaly type is a network anomaly, then the target repair operation is determined to be the first repair operation. The network module in the T-Box is then controlled to re-initiate a data connection establishment request to the operator's core network based on the current APN configuration parameters in order to repair the network of the T-Box and thus perform anomaly repair on the T-Box.

[0070] If the exception type is a process-related exception, and the target repair operation is determined to be the second repair operation, then the location process in the T-Box is restarted to perform exception repair on the T-Box.

[0071] If the exception type is a chip-related exception, and the target repair operation is determined to be the third repair operation, then the GNNS chip in the T-Box is reset, thereby performing exception repair on the T-Box.

[0072] If the exception type is a service-related exception, and the target repair operation is determined to be the fourth repair operation, then the RTCM service in the T-Box is re-authenticated, thereby performing exception repair on the T-Box.

[0073] If the anomaly type includes network anomalies and process anomalies, and the target repair operation is determined to include a first repair operation and a second repair operation, then the network module in the T-Box is controlled to re-initiate a data connection establishment request to the operator's core network based on the current APN configuration parameters, and the positioning process is restarted, thereby performing anomaly repair on the T-Box.

[0074] If the anomaly type includes network anomalies and chip anomalies, and the target repair operation is determined to include a first repair operation and a third repair operation, then the network module in the T-Box is controlled to re-initiate a data connection establishment request to the operator's core network based on the current APN configuration parameters, and the GNNS chip is reset, thereby repairing the anomaly of the T-Box.

[0075] If the anomaly type includes network anomalies and service anomalies, and the target repair operation is determined to include the first repair operation and the fourth repair operation, then the network module in the control T-Box will re-initiate a data connection establishment request to the operator's core network based on the current APN configuration parameters, and re-authenticate the RTCM service, thereby repairing the anomaly of the T-Box.

[0076] If the exception type includes process-related exceptions and chip-related exceptions, and the target repair operation is determined to include a second repair operation and a third repair operation, then the positioning process is restarted and the GNNS chip is reset, thereby performing exception repair on the T-Box.

[0077] If the exception type includes process-related exceptions and service-related exceptions, and the target repair operation is determined to include the second repair operation and the fourth repair operation, then the located process is restarted, and the RTCM service is re-authenticated, thereby performing exception repair on the T-Box.

[0078] If the anomaly type includes chip-related anomalies and service-related anomalies, and the target repair operation is determined to include the third and fourth repair operations, then the GNNS chip is reset and the RTCM service is re-authenticated, thereby performing anomaly repair on the T-Box.

[0079] If the anomaly type includes network anomalies, process anomalies, and chip anomalies, and the target repair operation is determined to include a first repair operation, a second repair operation, and a third repair operation, then the network module in the T-Box is controlled to re-initiate a data connection establishment request to the operator's core network based on the current APN configuration parameters, restart the positioning process, and reset the GNNS chip, thereby performing anomaly repair on the T-Box.

[0080] If the anomaly type includes network anomalies, process anomalies, and service anomalies, and the target repair operations include the first repair operation, the second repair operation, and the fourth repair operation, then the network module in the T-Box is controlled to re-initiate a data connection establishment request to the operator's core network based on the current APN configuration parameters, restart the positioning process, and re-authenticate the RTCM service, thereby repairing the anomaly in the T-Box.

[0081] If the anomaly type includes network anomalies, chip anomalies, and service anomalies, and the target repair operations include the first repair operation, the third repair operation, and the fourth repair operation, then control the network module in the T-Box to re-initiate a data connection establishment request to the operator's core network based on the current APN configuration parameters, reset the GNNS chip, and re-authenticate the RTCM service, thereby repairing the anomaly in the T-Box.

[0082] If the exception type includes process exception, chip exception, and service exception, and the target repair operation is determined to include a second repair operation, a third repair operation, and a fourth repair operation, then the positioning process is restarted, the GNNS chip is reset, and the RTCM service is re-authenticated, thereby repairing the T-Box exception.

[0083] If the anomaly type includes network anomalies, process anomalies, chip anomalies, and service anomalies, and the target repair operations include the first repair operation, the second repair operation, the third repair operation, and the fourth repair operation, then the network module in the T-Box is controlled to re-initiate a data connection establishment request to the operator's core network based on the current APN configuration parameters, restart the positioning process, reset the GNNS chip, and re-authenticate the RTCM service, thereby repairing the anomaly of the T-Box.

[0084] Based on the technical solution formed by S220 to SS222, on the one hand, the T-Box system will only be restarted when the T-Box anomaly type is identified as a system anomaly, thereby repairing the T-Box anomaly; on the other hand, if the T-Box anomaly type is not identified as a system anomaly, but as at least one of network anomalies, process anomalies, chip anomalies, or service anomalies, the target repair operation corresponding to the anomaly type will be obtained from the first to fourth repair operations and executed. This achieves accurate repair of the T-Box anomaly without restarting the T-Box system, thereby reducing the T-Box repair time. This not only enables rapid self-healing of the RTCM service, but also reduces the number of times the T-Box system needs to be restarted frequently because the T-Box anomaly problem cannot be resolved after restarting the T-Box system, which is conducive to improving the operational reliability of the T-Box.

[0085] The following are embodiments of the apparatus described in this application, which can be used to execute the embodiments of the method described in this application. For details not disclosed in the apparatus embodiments of this application, please refer to the embodiments of the method described in this application.

[0086] Figure 3 This application provides a schematic diagram of the structure of an exception handling device according to an embodiment of the present application. Figure 3 As shown, the anomaly handling device 300, applied to a remote information processing terminal, includes: The type identification module 310 is used to determine the anomaly type of the remote information processing terminal in the event of an anomaly in the Radio Technical Committee Maritime Service data received by the remote information processing terminal. The strategy determination module 320 is used to determine the target repair strategy corresponding to the anomaly type. The target repair strategy is at least one of the following: network repair strategy, process location repair strategy, chip repair strategy, service repair strategy, and system repair strategy. The anomaly repair module 330 is used to perform anomaly repair on the remote information processing terminal based on the target repair strategy.

[0087] In one possible implementation, the type identification module 310 is specifically used to determine, when a first condition is met, that the exception type includes network exceptions, and the first condition includes at least one of receiving a network disconnection event, access point name dialing failure, and transmission control protocol connection disconnection. The strategy determination module 320 is specifically used to determine the target repair strategy corresponding to the network anomaly as a network repair strategy. The anomaly repair module 330 is specifically used to control the network module in the remote information processing terminal to re-initiate a data connection establishment request to the operator's core network based on the current access point name configuration parameters when the target repair strategy includes a network repair strategy.

[0088] In one possible implementation, the type identification module 310 is specifically used to determine that the exception type includes process-related exceptions when the second condition is met. The second condition includes not receiving a heartbeat signal sent by the positioning process within a preset time period or the positioning process exiting abnormally. The strategy determination module 320 is specifically used to determine the target repair strategy corresponding to the process-type exception as the process repair strategy. The anomaly repair module 330 is specifically used to restart the positioning process in the remote information processing terminal when the target repair strategy includes a positioning process repair strategy.

[0089] In one possible implementation, the type identification module 310 is specifically used to determine, when the third condition is met, that the anomaly type includes chip-related anomalies. The third condition includes the telematics terminal not receiving Radio Technical Committee Maritime Service data through the Global Navigation Satellite System chip or the Radio Technical Committee Maritime Service data received by the telematics terminal through the Global Navigation Satellite System chip being invalid data. The strategy determination module 320 is specifically used to determine the target repair strategy corresponding to the chip-type anomaly as a chip repair strategy. The anomaly repair module 330 is specifically used to reset the global navigation satellite system chip when the target repair strategy includes a chip repair strategy.

[0090] In one possible implementation, the type identification module 310 is specifically used to determine, when the fourth condition is met, that the exception type includes service-related exceptions, and the fourth condition includes at least one of the following: expired license for Radio Technical Committee Maritime Service, Radio Technical Committee Maritime Service outside coverage area, and quota exhaustion for Radio Technical Committee Maritime Service. The strategy determination module 320 is specifically used to determine the target repair strategy corresponding to the service-type exception as the service repair strategy. The anomaly repair module 330 is specifically used to re-authenticate the Radio Technical Committee Maritime Service when the target repair strategy includes a service repair strategy, so as to regain access to the Radio Technical Committee Maritime Service data.

[0091] In one possible implementation, the type identification module 310 is specifically used to determine the anomaly type as a system anomaly when the fifth condition is met. The fifth condition includes the normal network status of the remote information processing terminal, the normal status of the positioning process, the normal status of the global navigation satellite system chip, the normal status of the Radio Technical Committee Maritime Service, and the abnormal data of the Radio Technical Committee Maritime Service. The strategy determination module 320 is specifically used to determine the target repair strategy corresponding to the system-type exception as the system repair strategy. The anomaly repair module 330 is specifically used to restart the remote information processing terminal when the target repair strategy is the system repair strategy.

[0092] In one possible implementation, the anomaly repair module 330 is specifically used to, in the event of anomalies in the Radio Technical Committee Maritime Service data received by the remote information processing terminal, sort the repair times corresponding to the network repair strategy, positioning process repair strategy, chip repair strategy, service repair strategy, and system repair strategy to obtain a first sorting result; execute the repair strategy corresponding to the minimum repair time in the first sorting result; determine whether the Radio Technical Committee Maritime Service data received by the remote information processing terminal is abnormal; if the Radio Technical Committee Maritime Service data received by the remote information processing terminal is abnormal, delete the minimum repair time in the first sorting result to obtain a second sorting result; use the second sorting result as the first sorting result, and return to the step of executing the repair strategy corresponding to the minimum repair time in the first sorting result.

[0093] In one possible implementation, the anomaly repair module 330 is specifically used to simultaneously execute network repair strategy, positioning process repair strategy, chip repair strategy, and service repair strategy when the Radio Technical Committee Maritime Service data received by the remote information processing terminal is abnormal; determine whether the Radio Technical Committee Maritime Service data received by the remote information processing terminal is abnormal; and execute system repair strategy when the Radio Technical Committee Maritime Service data received by the remote information processing terminal is abnormal.

[0094] The sequence numbers of the embodiments in this application are for descriptive purposes only and do not represent the superiority or inferiority of the embodiments.

[0095] Figure 4 This application provides a schematic diagram of the structure of a vehicle according to an embodiment of the present application. Figure 4 As shown, the vehicle 400 includes a memory 401 and a processor 402. The memory 401 stores executable program code 4011, and the processor 402 is used to call and execute the executable program code 4011 to perform an exception handling method.

[0096] This embodiment can divide the vehicle into functional modules according to the above method example. For example, each function can be assigned to a separate module, or two or more functions can be integrated into one processing module. The integrated module can be implemented in hardware. It should be noted that the module division in this embodiment is illustrative and only represents one logical functional division. In actual implementation, there may be other division methods.

[0097] When each functional module is divided according to its corresponding function, the vehicle may include: a type recognition module, a strategy determination module, an anomaly repair module, etc. It should be noted that all relevant content of each step involved in the above method embodiments can be referenced from the functional description of the corresponding functional module, and will not be repeated here.

[0098] The vehicle provided in this embodiment is used to execute the above-described exception handling method, and thus can achieve the same effect as the above implementation method.

[0099] When using integrated units, the vehicle may include a processing module and a storage module. The processing module is used to control and manage the vehicle's movements. The storage module is used to support the vehicle in executing relevant program code and data.

[0100] The processing module may be a processor or a controller, which can implement or execute the various exemplary logic blocks, modules, and circuits described in conjunction with the disclosure of this application. The processor may also be a combination of functions that implement computing capabilities, such as a combination of one or more microprocessors, a combination of digital signal processing (DSP) and a microprocessor, etc., and the storage module may be a memory.

[0101] This embodiment also provides a computer-readable storage medium storing computer program code. When the computer program code is run on a computer, it causes the computer to execute the above-described related method steps to implement an exception handling method in the above embodiment.

[0102] This embodiment also provides a computer program product that, when run on a computer, causes the computer to perform the aforementioned related steps to implement an exception handling method described in the above embodiment.

[0103] In addition, the vehicle provided in the embodiments of this application may specifically be a chip, component or module. The vehicle may include a connected processor and a memory. The memory is used to store instructions. When the vehicle is running, the processor may call and execute the instructions to make the chip execute an exception handling method in the above embodiments.

[0104] In this embodiment, the vehicle, computer-readable storage medium, computer program product, or chip are all used to execute the corresponding exception handling method provided above. Therefore, the beneficial effects that can be achieved can be referred to the beneficial effects of the corresponding exception handling method provided above, and will not be repeated here.

[0105] Through the above description of the embodiments, those skilled in the art will understand that, for the sake of convenience and brevity, only the division of the above functional modules is used as an example. In actual applications, the above functions can be assigned to different functional modules as needed, that is, the internal structure of the device can be divided into different functional modules to complete all or part of the functions described above.

[0106] In the embodiments provided in this application, it should be understood that the disclosed apparatus and methods can be implemented in other ways. For example, the apparatus embodiments described above are merely illustrative; for instance, the division of modules or units is only a logical functional division, and in actual implementation, there may be other division methods. For example, multiple units or components may be combined or integrated into another device, or some features may be ignored or not executed. Furthermore, the coupling or direct coupling or communication connection shown or discussed may be through some interfaces; the indirect coupling or communication connection between devices or units may be electrical, mechanical, or other forms.

[0107] The above description is merely a specific embodiment of this application, but the scope of protection of this application is not limited thereto. Any variations or substitutions that can be easily conceived by those skilled in the art within the scope of the technology disclosed in this application should be included within the scope of protection of this application. Therefore, the scope of protection of this application should be determined by the scope of the claims.

Claims

1. An exception handling method, characterized in that, The anomaly handling method, applied to remote information processing terminals, includes: In the event of an anomaly in the Radio Technical Committee Maritime Service data received by the remote information processing terminal, the anomaly type of the remote information processing terminal shall be determined. Determine the target repair strategy corresponding to the anomaly type, wherein the target repair strategy is at least one of the following: network repair strategy, location process repair strategy, chip repair strategy, service repair strategy, and system repair strategy; The remote information processing terminal is repaired based on the target repair strategy.

2. The anomaly handling method according to claim 1, characterized in that, The determination of the anomaly type of the remote information processing terminal includes: If the first condition is met, the anomaly type is determined to include network anomalies, wherein the first condition includes at least one of receiving a network disconnection event, access point name dialing failure, and transmission control protocol connection disconnection. Determining the target remediation strategy corresponding to the anomaly type includes: The target repair strategy corresponding to the aforementioned network anomaly is determined as the network repair strategy; The abnormal repair of the remote information processing terminal based on the target repair strategy includes: When the target repair strategy includes the network repair strategy, the network module in the remote information processing terminal is controlled to re-initiate a data connection establishment request to the operator's core network based on the current access point name configuration parameters.

3. The anomaly handling method according to claim 1, characterized in that, The determination of the anomaly type of the remote information processing terminal includes: If the second condition is met, the abnormality type is determined to include process-related abnormalities. The second condition includes not receiving a heartbeat signal from the positioning process within a preset time period or the positioning process exiting abnormally. Determining the target remediation strategy corresponding to the anomaly type includes: The target repair strategy corresponding to the process-type exception is determined to be the location process repair strategy; The abnormal repair of the remote information processing terminal based on the target repair strategy includes: If the target repair strategy includes the positioning process repair strategy, the positioning process in the remote information processing terminal is restarted.

4. The anomaly handling method according to claim 1, characterized in that, The determination of the anomaly type of the remote information processing terminal includes: If the third condition is met, the anomaly type is determined to include chip-related anomalies. The third condition includes the telematics terminal failing to receive the Radio Technical Committee Maritime Service data through the Global Navigation Satellite System chip or the Radio Technical Committee Maritime Service data received by the telematics terminal through the Global Navigation Satellite System chip being invalid data. Determining the target remediation strategy corresponding to the anomaly type includes: The target repair strategy corresponding to the chip-type anomaly is determined as the chip repair strategy; The abnormal repair of the remote information processing terminal based on the target repair strategy includes: If the target repair strategy includes the chip repair strategy, the global navigation satellite system chip is reset.

5. The anomaly handling method according to claim 1, characterized in that, The determination of the anomaly type of the remote information processing terminal includes: If the fourth condition is met, the anomaly type is determined to include a service-related anomaly, and the fourth condition includes at least one of the following: the license for the Radio Technical Committee Maritime Service has expired, the Radio Technical Committee Maritime Service is out of coverage, and the quota for the Radio Technical Committee Maritime Service has been exhausted. Determining the target remediation strategy corresponding to the anomaly type includes: The target repair strategy corresponding to the service-type exception is determined as the service repair strategy; The abnormal repair of the remote information processing terminal based on the target repair strategy includes: If the target repair strategy includes the service repair strategy, the Radio Technical Committee Maritime Service is re-authenticated to regain access to the Radio Technical Committee Maritime Service data.

6. The anomaly handling method according to claim 1, characterized in that, The determination of the anomaly type of the remote information processing terminal includes: If the fifth condition is met, the anomaly type is determined to be a system anomaly. The fifth condition includes the normal network status of the remote information processing terminal, the normal status of the positioning process, the normal status of the global navigation satellite system chip, the normal status of the Radio Technical Committee Maritime Service, and the abnormal data of the Radio Technical Committee Maritime Service. Determining the target remediation strategy corresponding to the anomaly type includes: The target repair strategy corresponding to the system anomaly is determined as the system repair strategy; The abnormal repair of the remote information processing terminal based on the target repair strategy includes: If the target repair strategy is the system repair strategy, restart the remote information processing terminal.

7. The anomaly handling method according to claim 1, characterized in that, The exception handling method further includes: In the event of an anomaly in the Radio Technical Committee Maritime Service data received by the remote information processing terminal, the repair times corresponding to the network repair strategy, the positioning process repair strategy, the chip repair strategy, the service repair strategy, and the system repair strategy are sorted to obtain a first sorting result; Execute the repair strategy corresponding to the minimum repair time in the first sorting result; Determine whether the Radio Technical Committee Maritime Service data received by the remote information processing terminal is abnormal; In the event of an anomaly in the Radio Technical Committee Maritime Service data received by the remote information processing terminal, the minimum repair time in the first sorting result is deleted to obtain the second sorting result; The second sorting result is used as the first sorting result, and the step of executing the repair strategy corresponding to the minimum repair time in the first sorting result is returned.

8. The anomaly handling method according to claim 1, characterized in that, The exception handling method further includes: In the event of an anomaly in the Radio Technical Committee Maritime Service data received by the remote information processing terminal, the network repair strategy, the positioning process repair strategy, the chip repair strategy, and the service repair strategy are executed simultaneously. Determine whether the Radio Technical Committee Maritime Service data received by the remote information processing terminal is abnormal; In the event of an anomaly in the Radio Technical Committee Maritime Service data received by the remote information processing terminal, the system repair strategy shall be executed.

9. A vehicle, characterized in that, The vehicles include: Memory, used to store executable program code; A processor for calling and running the executable program code from the memory, causing the vehicle to perform the exception handling method as described in any one of claims 1 to 8.

10. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores a computer program that, when executed, implements the exception handling method as described in any one of claims 1 to 8.

Images