A method and apparatus for link status monitoring and self-recovery in 4G wireless communication modules
By jointly analyzing indicators from the physical layer, network access layer, and application layer, the link status of 4G modules is identified and hierarchical recovery operations are performed. This solves the problems of high false alarm rate and long recovery time in existing technologies, and achieves accurate identification and rapid recovery of link failure.
Patent Information
- Application Number
- CN202611211432.6
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2026-08-11
- Publication Date
- 2026-11-10
AI Technical Summary
Existing technologies have a high false alarm rate when monitoring and recovering 4G module link anomalies. They cannot distinguish between true weak signals and false dead signals, cannot detect silent false dead signals, and lack a joint judgment mechanism that integrates multiple indicators, resulting in unnecessary restarts and recovery processes that take a long time.
By acquiring multiple judgment indicators from the physical layer, network access layer, and application layer in real time and performing joint analysis, the link status is identified as instantaneous network fluctuation or link dead. Based on the cause of the anomaly, graded recovery operations are performed, including heartbeat retransmission, network re-registration, radio frequency restart, and hardware reset.
It enables accurate identification and rapid recovery of link freezes, reduces false alarms and unnecessary restarts, and improves communication stability and efficiency.
Smart Images

Figure CN123075504A_ABST
Abstract
Description
Technical Field
[0001] This invention relates to the field of 4G communication technology, and more specifically, to a method and apparatus for link status monitoring and self-recovery of 4G wireless communication modules. Background Technology
[0002] In applications such as the Internet of Things (IoT), industrial automation, vehicle communication, and remote data acquisition, the stability and reliability of 4G modules, as core communication units, are crucial. However, in complex real-world wireless network environments, 4G modules frequently experience an abnormal state known as "pseudo-dead" or "network hang." This state manifests as follows: the module's firmware and hardware appear to be functioning normally; the power and network indicator lights flash normally; and the network signal appears normal. However, the data transmission channel (PDP context) between the module and the operator's core network is actually interrupted, preventing the device from sending or receiving uplink data. In this situation, upper-layer application software, unaware of the module's hardware failure, often continues to assume the link is intact, resulting in continuous data loss and prolonged communication outages.
[0003] In particular, taking the development of "smart power sockets" as an example, the sockets integrate a 4G wireless module. This type of module typically requires a direct connection to the main station's energy management system server. The smart sockets within its jurisdiction constantly need to transmit large amounts of data to the main station, either passively or actively. In real-world environments, various issues arise, such as signal interference, poor channel quality, and network access problems. These combined factors can all impact data retrieval and proactive reporting.
[0004] In existing technical solutions, the following two methods are commonly used to monitor and recover from such link anomalies: The first is the single-index threshold judgment method. This method uses the MCU (microcontroller unit) to periodically send AT commands to the 4G module and only reads the return value of the signal quality indicator AT+CSQ. When this return value is consistently lower than a certain preset fixed threshold (for example, +CSQ: return value less than 5, corresponding to a reference signal received power RSRP lower than -109dBm), the system determines that the signal quality is too poor and then performs a module reset or power-off restart operation; The second is the independent heartbeat packet monitoring method. This method is independent of the module's RF status and relies only on the mechanism of application layer protocols (such as MQTT, TCP Keepalive). The device sends a very small "heartbeat" data packet to the server at fixed time intervals (such as 30 seconds or 60 seconds) and waits for the server's response. If no response is received for multiple consecutive (such as 3) heartbeat requests, the system determines that the network connection has failed and then triggers AT commands to restart the PPP (point-to-point protocol) stack or perform a complete module reset.
[0005] The two traditional methods mentioned above have a high false positive rate, leading to unnecessary restarts.
[0006] In the first approach, relying solely on AT+CSQ signal strength cannot distinguish between "truly weak signals" and "false deadness." In areas near signal coverage edges (such as basements or remote rural areas), insufficient signal strength is normal; data communication may be slow but a connection may still be maintained. Existing technology frequently identifies these as false deadnesses and executes module restarts in such situations, failing to restore communication and instead prolonging the actual communication interruption time due to repeated network registration (Attach / Detach), while also increasing module power consumption and base station signaling load. In the second approach, "silent false deadness" cannot be detected: while independent heartbeat monitoring can detect communication failures, it cannot pinpoint the root cause. A more common false deadness scenario is: the AT+CSQ return value is good (e.g., above 20), but the network attachment state AT+CGATT or the EPS registration state AT+CEREG has quietly changed to an unregistered state (e.g., from +CEREG: 0,1 to +CEREG: 0,2 or 0,3). This is usually caused by NAT (Network Address Translation) timeouts on the operator side, inactive context on the base station side, or abnormal module protocol stack logic, and is unrelated to RF signal strength. In this "silent dead" state, although a simple heartbeat timeout in the existing technology will trigger a reset, the lack of pre-diagnosis of the network registration status makes it impossible to implement a precise and tiered recovery strategy (e.g., prioritizing "airplane mode" RF reset instead of a complete power-off restart), resulting in a crude and time-consuming recovery method.
[0007] Meanwhile, existing technologies lack a joint decision-making mechanism that integrates multiple indicators: existing technical solutions view each monitoring indicator in isolation, failing to correlate and analyze the radio frequency physical layer (signal strength), network access layer (attachment / registration status), and application layer (heartbeat response). For example, when a module simultaneously experiences a sudden drop in signal strength and changes its registration status to "roaming prohibited" or "registration refused," existing technologies cannot comprehensively determine whether this is a momentary network fluctuation or a permanent dead state requiring intervention, often either missing the recovery opportunity or making an incorrect reset decision. Summary of the Invention
[0008] To address the aforementioned issues, this application provides a method and apparatus for link status monitoring and self-recovery of a 4G wireless communication module.
[0009] In a first aspect, this application provides a real-time example of a link status monitoring and self-recovery method for a 4G wireless communication module, comprising the following steps:
[0010] S1: Acquire the data corresponding to the physical layer judgment indicators, network access layer judgment indicators and application layer judgment indicators respectively within the first preset time period;
[0011] S2: Based on the data of the physical layer judgment indicators, judge whether the physical layer is abnormal and obtain the corresponding current layer abnormality characteristics when the physical layer is judged to be abnormal. Based on the data of the network access layer judgment indicators, judge whether the network access layer is abnormal and obtain the corresponding current layer abnormality characteristics when the network access layer is judged to be abnormal. Based on the data of the application layer judgment indicators, judge whether the application layer is abnormal and obtain the corresponding current layer abnormality characteristics when the application layer is judged to be abnormal.
[0012] S3: If at least one of the physical layer, network access layer and application layer is determined to be abnormal, the abnormal duration corresponding to the abnormal layer is obtained respectively. If only one of the physical layer, network access layer and application layer is abnormal and the abnormal duration corresponding to the abnormal layer is less than the second preset duration, the link state is determined to be instantaneous network fluctuation and the process returns to step S1. If at least one of the physical layer, network access layer and application layer is abnormal and the abnormal duration corresponding to the abnormal layer is greater than or equal to the third preset duration, the link state is determined to be link dead.
[0013] S4: Based on the abnormal layers in the physical layer, network access layer, and application layer, and the current abnormal characteristics of the abnormal layers, perform combined analysis on the physical layer, network access layer, and application layer to determine the current dead link cause as one of network-side abnormality, radio frequency hardware dead link, protocol stack software dead link, and deep integration dead link.
[0014] S5: Based on the current cause of the apparent failure, perform the corresponding graded recovery operation on the link to restore the link to normal status.
[0015] Preferably, the anomaly characteristics of the physical layer include signal strength anomaly, signal quality anomaly, and module hardware anomaly; the anomaly characteristics of the network access layer include 4G core network attachment anomaly, registration result anomaly, and data bearer channel anomaly; and the anomaly characteristics of the application layer include server communication anomaly, transport layer connectivity anomaly, and service data anomaly. The current anomaly characteristics of the physical layer include at least one of signal strength anomaly, signal quality anomaly, and module hardware anomaly; the current anomaly characteristics of the network access layer include at least one of 4G core network attachment anomaly, registration result anomaly, and data bearer channel anomaly; and the current anomaly characteristics of the application layer include at least one of server communication anomaly, transport layer connectivity anomaly, and service data anomaly.
[0016] Preferably, the physical layer judgment indicators include reference signal received power, signal-to-interference-plus-noise ratio (SINNR), RF transmission status, and RF reception status. Step S2, which judges whether the physical layer is abnormal based on the data from the physical layer judgment indicators and obtains the corresponding current layer abnormality feature when the physical layer is determined to be abnormal, specifically includes: if the reference signal received power meets a first preset condition, it is determined that the physical layer has a signal strength abnormality; if the SINNR meets a second preset condition, it is determined that the physical layer has a signal quality abnormality; if the RF transmission status meets a third preset condition and / or the RF reception status meets a fourth preset condition, it is determined that the physical layer has a module hardware abnormality; if the physical layer has at least one of signal strength abnormality, signal quality abnormality, and module hardware abnormality, it is determined that the physical layer is abnormal and this is used as the corresponding current layer abnormality feature.
[0017] Preferably, the network access layer judgment indicators include EPS attachment status, network registration status, and PDN connection status; step S2, judging whether the network access layer is abnormal based on the data of the network access layer judgment indicators, specifically includes: if the EPS attachment status meets the fifth preset condition, it is determined that the network access layer has an abnormal attachment to the 4G core network; if the network registration status meets the sixth preset condition, it is determined that the network access layer has an abnormal registration result; if the PDN connection status meets the seventh preset condition, it is determined that the network access layer has an abnormal data bearer channel; if the network access layer has at least one of the abnormal attachment to the 4G core network, abnormal registration result, and abnormal data bearer channel, it is determined that the network access layer is abnormal and is used as the current layer abnormality feature of the network access layer.
[0018] Preferably, the application layer judgment indicators include heartbeat response delay, heartbeat packets, TCP connection status, and upload data transmission success rate. Step S2, which judges whether the application layer is abnormal based on the data from the application layer judgment indicators, specifically includes: if the heartbeat response delay meets the eighth preset condition and / or the heartbeat packet meets the ninth preset condition, then the application layer is determined to have communication anomalies with the server; if the TCP connection status meets the tenth preset condition, then the application layer is determined to have transport layer connectivity anomalies; if the uplink data transmission success rate meets the eleventh preset condition, then the application layer has business data anomalies; if the application layer has at least one of the following: communication anomalies with the server, transport layer connectivity anomalies, and business data anomalies, then the application layer is determined to be abnormal and this is taken as the current layer anomaly characteristic of the application layer.
[0019] Preferably, the graded recovery operation includes multiple recovery actions in ascending order of level; step S4 includes: when the physical layer is normal, the current layer anomaly of the network access layer is registration anomaly, and the current layer anomaly of the application layer is communication anomaly with the server, determining that the current cause of the link freeze is a network-side anomaly; when the current layer anomaly of the network access layer is registration result anomaly, the current layer anomaly of the application layer is communication anomaly with the server, and the current layer anomaly of the physical layer includes signal strength anomaly and / or module hardware anomaly, determining that the current cause of the link freeze is a radio frequency hardware freeze; when the physical layer is normal, the network access layer is normal, and the current layer anomaly of the physical layer includes signal strength anomaly and / or module hardware anomaly, determining that the current cause of the link freeze is a radio frequency hardware freeze; when the physical layer is normal, the current layer anomaly of the application layer is communication anomaly with the server ..., and the current layer anomaly of the application layer includes signal strength anomaly and / or module hardware anomaly, determining that the current cause of the link freeze is a radio frequency hardware freeze; when the physical layer is normal, the current layer anomaly of the application layer is communication anoma When the current layer anomaly characteristics of the application layer include abnormal communication with the server and / or abnormal connectivity of the transport layer, the current dead link is determined to be caused by a protocol stack software dead link. When the physical layer, network access layer, and application layer are abnormal, the current layer anomaly characteristics of the network access layer (registration result abnormality), the current layer anomaly characteristics of the application layer (interaction with the server abnormality), and the current layer anomaly characteristics of the physical layer (signal strength abnormality and / or module hardware abnormality) are determined to be true. If they are not true, a recovery action of any level except the highest level is performed on the link. If the link cannot be restored to normal, the current dead link is determined to be caused by a deep integrated dead link.
[0020] Preferably, step S5 includes: when the current apparent death is caused by one of network-side anomalies, radio frequency hardware death, and protocol stack software death, performing corresponding recovery actions on the link in sequence from the lowest level recovery action to the highest level recovery action; if the link status returns to normal after performing the first recovery action of the first preset level, then the subsequent actions are stopped; if the link status is abnormal after performing the first recovery action of the first preset level, then performing a second recovery action of the second preset level, which is one level higher than the first recovery action of the first preset level, on the link.
[0021] Preferably, the fourth recovery action of the fourth preset level in the graded recovery operation is one level higher than the third recovery action of the third preset level. Step S5 further includes: when the current cause of the apparent death is a deep composite apparent death, and the link cannot be restored to normal after the third recovery action of the third preset level has been performed on the link, the corresponding recovery actions are sequentially performed on the link in the order from the fourth recovery action of the fourth preset level to the highest level recovery action. If the state of the link is restored to normal after the fourth recovery action of the fourth preset level is performed, the subsequent actions are stopped. If the state of the link is abnormal after the fourth recovery action of the fourth preset level is performed, the fifth recovery action of the fifth preset level, which is one level higher than the fourth recovery action of the fourth preset level, is performed on the link.
[0022] Preferably, the recovery action is one of heartbeat retransmission, network re-registration, radio frequency restart, module soft reset, and hardware reset, with the levels of heartbeat retransmission, network re-registration, radio frequency restart, module soft reset, and hardware reset increasing sequentially.
[0023] Secondly, embodiments of this application provide a link status monitoring and self-recovery device for a 4G wireless communication module, including a data acquisition module, an anomaly judgment module, a false death judgment module, a cause acquisition module, and a link status recovery module;
[0024] The data acquisition module is used to acquire data corresponding to the physical layer judgment index, the network access layer judgment index and the application layer judgment index within a first preset time period.
[0025] The anomaly detection module is used to determine whether the physical layer is abnormal based on the data of the physical layer detection index and to obtain the corresponding current layer anomaly characteristics when the physical layer is determined to be abnormal; to determine whether the network access layer is abnormal based on the data of the network access layer detection index and to obtain the corresponding current layer anomaly characteristics when the network access layer is determined to be abnormal; and to determine whether the application layer is abnormal based on the data of the application layer detection index and to obtain the corresponding current layer anomaly characteristics when the application layer is determined to be abnormal.
[0026] The dead link determination module is used to determine the link status as instantaneous network fluctuation if at least one of the physical layer, network access layer and application layer is abnormal, and to obtain the abnormal duration corresponding to the abnormal layer. If only one of the physical layer, network access layer and application layer is abnormal and the abnormal duration corresponding to the abnormal layer is less than a second preset duration, the link status is determined to be a dead link.
[0027] The data acquisition module is used to acquire data corresponding to the physical layer judgment indicator, the network access layer judgment indicator and the application layer judgment indicator within a fourth preset time period when the fake dead judgment module determines that the current link state is an instantaneous network fluctuation.
[0028] The cause acquisition module is used to perform combined analysis on the physical layer, network access layer and application layer based on the abnormal layer in the physical layer, network access layer and application layer and the current abnormal characteristics of the abnormal layer to determine that the current dead link is caused by one of the following: network side abnormality, radio frequency hardware dead link, protocol stack software dead link and deep integration dead link.
[0029] The link state recovery module is used to perform corresponding hierarchical recovery operations on the link based on the current cause of the apparent failure in order to restore the link state to normal.
[0030] The beneficial effects of this invention are as follows: instead of looking at indicators in isolation, it performs joint analysis of the physical layer, network access layer, and application layer to obtain the number of abnormal layers in the physical layer, network access layer, and application layer. Based on the number of abnormal layers and the duration of the abnormality corresponding to the abnormal layer, it determines whether the link status is instantaneous network fluctuation or link dead. It performs combined analysis of the physical layer, network access layer, and application layer to determine the current cause of the link dead. Based on the current cause of the dead, it performs corresponding hierarchical recovery operations on the link to restore the link status to normal, thereby realizing the execution of corresponding hierarchical recovery operations according to the specific cause of the dead. Attached Figure Description
[0031] To more clearly illustrate the technical solutions in the embodiments of this application, the accompanying drawings used in the embodiments will be briefly introduced below. Obviously, the drawings described below are only some embodiments of this application. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.
[0032] Figure 1 A flowchart illustrating a link status monitoring and self-recovery method for a 4G wireless communication module provided in an embodiment of this application;
[0033] Figure 2 This is a schematic diagram of a link status monitoring and self-recovery device for a 4G wireless communication module provided in an embodiment of this application. Detailed Implementation
[0034] The technical solutions in the embodiments of this application will be clearly and completely described below with reference to the accompanying drawings.
[0035] In the following description, the terms "first" and "second" are used for descriptive purposes only and should not be construed as indicating or implying relative importance. The following description provides multiple embodiments of this application, which can be substituted or combined with each other. Therefore, this application can also be considered to include all possible combinations of the same and / or different embodiments described. Thus, if one embodiment includes features A, B, and C, and another embodiment includes features B and D, then this application should also be considered to include embodiments containing one or more other possible combinations of A, B, C, and D, even if such embodiments are not explicitly described in the following text.
[0036] The following description provides examples and does not limit the scope, applicability, or examples set forth in the claims. Changes may be made to the function and arrangement of the described elements without departing from the scope of this application. Various processes or components may be appropriately omitted, substituted, or added to the examples. For example, the described methods may be performed in a different order than described, and various steps may be added, omitted, or combined. Furthermore, features described with respect to some examples may be combined into other examples.
[0037] Please see Figure 1 . Figure 1 This is a flowchart illustrating a link status monitoring and self-recovery method for a 4G wireless communication module provided in an embodiment of this application. In this embodiment, the method includes the following steps:
[0038] S1: Acquire the data corresponding to the physical layer judgment indicators, network access layer judgment indicators and application layer judgment indicators respectively within the first preset time period;
[0039] S2: Based on the data of the physical layer judgment indicators, judge whether the physical layer is abnormal and obtain the corresponding current layer abnormality characteristics when the physical layer is judged to be abnormal. Based on the data of the network access layer judgment indicators, judge whether the network access layer is abnormal and obtain the corresponding current layer abnormality characteristics when the network access layer is judged to be abnormal. Based on the data of the application layer judgment indicators, judge whether the application layer is abnormal and obtain the corresponding current layer abnormality characteristics when the application layer is judged to be abnormal.
[0040] S3: If at least one of the physical layer, network access layer and application layer is determined to be abnormal, the abnormal duration corresponding to the abnormal layer is obtained respectively. If only one of the physical layer, network access layer and application layer is abnormal and the abnormal duration corresponding to the abnormal layer is less than the second preset duration, the link state is determined to be instantaneous network fluctuation and the process returns to step S1. If at least one of the physical layer, network access layer and application layer is abnormal and the abnormal duration corresponding to the abnormal layer is greater than or equal to the third preset duration, the link state is determined to be link dead.
[0041] S4: Based on the abnormal layers in the physical layer, network access layer, and application layer, and the current abnormal characteristics of the abnormal layers, perform combined analysis on the physical layer, network access layer, and application layer to determine the current dead link cause as one of network-side abnormality, radio frequency hardware dead link, protocol stack software dead link, and deep integration dead link.
[0042] S5: Based on the current cause of the apparent failure, perform the corresponding graded recovery operation on the link to restore the link to normal status.
[0043] In this embodiment, instead of considering individual indicators in isolation, the system assesses whether the physical layer is abnormal based on physical layer indicators, network access layer indicators, and application layer indicators. The system then jointly determines the number of abnormal layers across the physical, network access, and application layers. Based on the number of abnormal layers and their corresponding duration, the system identifies whether the link status is transient network fluctuation or a link freeze, thus distinguishing between the two. Furthermore, the system performs combined analysis of the abnormal layers and their current abnormal characteristics to determine if the link freeze is caused by one of the following: network-side anomaly, RF hardware freeze, protocol stack software freeze, or deep integration freeze. This allows for accurate and rapid identification of the current cause of the link freeze. Based on the current cause, the system performs corresponding tiered recovery operations to restore the link status to normal, achieving precise link status recovery in a short time.
[0044] In this embodiment, if only one of the physical layer, network access layer, and application layer is abnormal, and the duration of the abnormality is short (e.g., 30 seconds), the link state is determined to be a momentary network fluctuation. In this case, the indicators corresponding to the abnormal layer in the physical layer, network access layer, and application layer can recover automatically. If at least one of the physical layer, network access layer, and application layer is abnormal, and the duration of the abnormality is long (e.g., 90 seconds), the link state is determined to be a link freeze. In this case, the indicators corresponding to the abnormal layer in the physical layer, network access layer, and application layer cannot recover automatically.
[0045] In one possible implementation, the physical layer's layer anomaly characteristics include signal strength anomaly, signal quality anomaly, and module hardware anomaly; the network access layer's layer anomaly characteristics include 4G core network attachment anomaly, registration result anomaly, and data bearer channel anomaly; the application layer's layer anomaly characteristics include server communication anomaly, transport layer connectivity anomaly, and service data anomaly; the physical layer's current layer anomaly characteristics include at least one of signal strength anomaly, signal quality anomaly, and module hardware anomaly; the network access layer's current layer anomaly characteristics include at least one of 4G core network attachment anomaly, registration result anomaly, and data bearer channel anomaly; and the application layer's current layer anomaly characteristics include at least one of server communication anomaly, transport layer connectivity anomaly, and service data anomaly.
[0046] In one possible implementation, the physical layer judgment indicators include reference signal received power, signal-to-interference-plus-noise ratio (SIR), RF transmission status, and RF reception status. Step S2, which involves judging whether the physical layer is abnormal based on the data from the physical layer judgment indicators and obtaining the corresponding current layer abnormality feature when the physical layer is determined to be abnormal, specifically includes: if the reference signal received power meets a first preset condition, then the physical layer is determined to have a signal strength abnormality; if the SIR meets a second preset condition, then the physical layer is determined to have a signal quality abnormality; if the RF transmission status meets a third preset condition and / or the RF reception status meets a fourth preset condition, then the physical layer is determined to have a module hardware abnormality; if the physical layer has at least one of signal strength abnormality, signal quality abnormality, and module hardware abnormality, then the physical layer is determined to be abnormal and this is used as the corresponding current layer abnormality feature.
[0047] In this embodiment of the application, the signal strength, signal quality and hardware status of the physical layer are judged according to the physical layer judgment index.
[0048] In this embodiment, if the decrease in reference signal received power within a fifth preset time period is greater than a first preset value, i.e., the reference signal received power drops sharply, then the reference signal received power is determined to meet the first preset condition. If the reference signal received power within a sixth preset time period is lower than a second preset value and greater than 0, i.e., the reference signal received power remains below a threshold, then the reference signal received power is determined to meet the first preset condition. If the change in reference signal received power within a seventh preset time period is greater than a third preset value, i.e., the reference signal received power fluctuates drastically, then the reference signal received power is determined to meet the first preset condition. If the reference signal received power is 0 within an eighth preset time period, i.e., there is no signal, then the reference signal received power is determined to meet the first preset condition. Reference signal received power is RSRP, or Reference Signal Receiving Power.
[0049] In this embodiment, if the signal-to-interference-plus-noise ratio (SINR) is less than 0 for a ninth preset time period (i.e., the SINR is consistently negative), then the SINR is determined to meet the second preset condition. If the change in SINR within a tenth preset time period is greater than the fourth preset value (i.e., the SINR fluctuates drastically), then the SINR is determined to meet the second preset condition. SINR is the ratio of signal to interference plus noise.
[0050] In this embodiment, if the radio frequency transmission state is no transmission or no uplink power, the radio frequency transmission state is determined to meet the third preset condition. If the radio frequency reception state is reception stuck, the radio frequency reception state meets the fourth preset condition.
[0051] In one possible implementation, the network access layer judgment indicators include EPS attachment status, network registration status, and PDN connection status. Step S2, which determines whether the network access layer is abnormal based on the data from the network access layer judgment indicators, specifically includes: if the EPS attachment status meets a fifth preset condition, it is determined that the network access layer has an abnormal attachment to the 4G core network; if the network registration status meets a sixth preset condition, it is determined that the network access layer has an abnormal registration result; if the PDN connection status meets a seventh preset condition, it is determined that the network access layer has an abnormal data bearer channel; if the network access layer exhibits at least one of the following abnormalities: abnormal attachment to the 4G core network, abnormal registration result, and abnormal data bearer channel, it is determined that the network access layer is abnormal and this is used as the current layer abnormality characteristic of the network access layer.
[0052] In this embodiment of the application, the network access layer's attached 4G core network, registration results, and data bearer channels are judged as abnormal based on network access layer judgment indicators.
[0053] In this embodiment, if the EPS attachment status is not attached or attachment failed, the EPS attachment status is determined to meet the fifth preset condition. The EPS attachment status refers to the state in which the mobile terminal (UE) successfully completes registration in the Evolved Packet System (4G / LTE network), is recognized by the core network and establishes a logical connection, corresponding to the EMM-REGISTERED identifier, and is a prerequisite for conducting data / voice services.
[0054] In this embodiment of the application, if the network registration status is registration refused, roaming prohibited, PLMN prohibited, or TAI prohibited, then the network registration status is determined to meet the sixth preset condition.
[0055] In this embodiment of the application, if the PDN connection status is no PDN, or the bearer is disconnected or dead, then the PDN connection status is determined to meet the seventh preset condition. The PDN connection status refers to the activation status and lifecycle stage of the logical IP channel between the terminal (UE) and the external packet data network (such as the Internet, IMS), which is mainly reflected in "not established, activating, activated (connected), deactivating, disconnected".
[0056] In one possible implementation, the application layer judgment indicators include heartbeat response latency, heartbeat packets, TCP connection status, and upload data transmission success rate. Step S2, which determines whether the application layer is abnormal based on the data from the application layer judgment indicators, specifically includes: if the heartbeat response latency meets an eighth preset condition and / or the heartbeat packet meets a ninth preset condition, then the application layer is determined to have an abnormal communication with the server; if the TCP connection status meets a tenth preset condition, then the application layer is determined to have a transport layer connectivity abnormality; if the uplink data transmission success rate meets an eleventh preset condition, then the application layer has a business data abnormality; if the application layer has at least one of the following: abnormal communication with the server, transport layer connectivity abnormality, and business data abnormality, then the application layer is determined to be abnormal and this is taken as the current layer abnormality characteristic of the application layer.
[0057] In this embodiment, if the heartbeat response delay times out, the heartbeat response delay is determined to meet the eighth preset condition. If the heartbeat connection fails to respond after N attempts, the heartbeat is determined to meet the ninth preset condition. If the TCP connection status is a dead link, a broken connection, or an inability to establish a connection, the TCP connection status is determined to meet the tenth preset condition. If the uplink data transmission success rate is a continuous transmission failure, the uplink data transmission success rate is determined to meet the eleventh preset condition.
[0058] In one possible implementation, the graded recovery operation includes multiple recovery actions of progressively higher levels; step S4 includes: when the physical layer is normal, the current layer anomaly of the network access layer is registration anomaly, and the current layer anomaly of the application layer is communication anomaly with the server, determining that the current cause of the link freeze is a network-side anomaly; when the current layer anomaly of the network access layer is registration result anomaly, the current layer anomaly of the application layer is communication anomaly with the server, and the current layer anomaly of the physical layer includes signal strength anomaly and / or module hardware anomaly, determining that the current cause of the link freeze is a radio frequency hardware freeze; when the physical layer is normal, the network access layer is normal, and the current layer anomaly of the application layer includes signal strength anomaly and / or module hardware anomaly, determining that the current cause of the link freeze is a radio frequency hardware freeze; when the physical layer is normal, the network access layer is normal, and the current layer anomaly of the application layer includes signal strength anomaly and / or module hardware anomaly, determining that the current cause of the link freeze is a radio frequency hardware freeze; when the physical layer is normal, the current layer anomaly of the application layer is registration result anomaly, the current layer anomaly of the application layer is communication anomaly with the server, and the current layer anomaly of the physical layer includes signal strength anomaly and / or module hardware anomaly, determining that the current cause of the link freeze is a radio frequency hardware freeze; when the physical layer is normal, the current layer anomaly of the application layer is registration result anomaly, the current layer anomaly of the application layer is communication anomaly ... When the current layer anomaly characteristics of the application layer include abnormal communication with the server and / or abnormal connectivity of the transport layer, the cause of the link freeze is determined to be a protocol stack software freeze. When the physical layer, network access layer, and application layer are abnormal, the current layer anomaly characteristics of the network access layer (registration result abnormality), the current layer anomaly characteristics of the application layer (interaction with the server abnormality), and the current layer anomaly characteristics of the physical layer (signal strength abnormality and / or module hardware abnormality) are determined to be true. If they are not true, a recovery action of any level except the highest level is performed on the link. If the link cannot be restored to normal, the cause of the current freeze is determined to be a deep integrated freeze.
[0059] In this embodiment, by combining the physical layer, network access layer, and application layer, precise location is achieved to directly determine the root cause of the apparent deadlock, thereby obtaining the current cause of the link's apparent deadlock and avoiding blind resets. The system checks whether the current abnormal characteristics of the network access layer (registration result abnormality), the application layer (communication abnormality with the server), and the physical layer (signal strength abnormality and / or module hardware abnormality) are true. If not, all three layers are considered NOT true (i.e., the current abnormal characteristics of the network access layer (registration result abnormality), the application layer (communication abnormality with the server), and the physical layer (signal strength abnormality and / or module hardware abnormality) are true.
[0060] In this embodiment, the cause of the apparent death is determined through a three-layer combined analysis, as follows: Type 1: Network-side anomaly (operator / cell problem): The physical layer is normal, but the network access layer exhibits at least one of the following: registration refusal, roaming ban, or PLMN ban. This indicates that the current layer anomaly of the network access layer is registration anomaly. The application layer exhibits at least one of the following: N consecutive heartbeats without response, or heartbeat response delay timeout. This indicates that the current layer anomaly of the application layer is communication anomaly with the server. Type 2: RF hardware apparent death: The physical layer exhibits at least one of the following: a sudden drop in reference signal received power, no reference signal received power, no RF transmission status, or RF reception status is reception dead. This indicates that the current layer anomaly of the physical layer includes at least one of module hardware anomaly or reference signal received power anomaly. The network access layer exhibits registration refusal. This indicates that the current layer anomaly of the network access layer is registration result anomaly. The application layer exhibits at least one of the following: N consecutive heartbeats without response, or heartbeat response delay timeout. This indicates that the current layer anomaly of the application layer is communication anomaly with the server. The symptoms are as follows: Type 3: Protocol stack software dead (software dead): The physical layer is normal, the access layer is normal, the application layer has N consecutive heartbeat packets without response and the TCP connection status is dead, that is, the current layer abnormality characteristics of the application layer include abnormal communication with the server and abnormal connectivity of the transport layer; Type 4: The physical layer, network access layer and application layer are all abnormal, the abnormality duration exceeds the eleventh preset time, and the current layer abnormality characteristics of the network access layer are abnormal registration results, the current layer abnormality characteristics of the application layer are abnormal communication with the server, and the current layer abnormality characteristics of the physical layer, including abnormal signal strength and / or module hardware abnormality, are not met. Perform any recovery action of any level except the highest level on the link and if the link cannot be restored to normal, the current deadness of the link is determined to be a deep comprehensive dead.
[0061] In one possible implementation, step S5 includes: when the current apparent death is caused by one of network-side anomalies, radio frequency hardware death, and protocol stack software death, performing corresponding recovery actions on the link sequentially in order from the lowest level recovery action to the highest level recovery action; if the link status returns to normal after performing the first recovery action of the first preset level, then stopping the subsequent actions; if the link status is abnormal after performing the first recovery action of the first preset level, then performing a second recovery action of the second preset level, which is one level higher than the first recovery action of the first preset level, on the link.
[0062] In one possible implementation, the fourth recovery action of the fourth preset level in the graded recovery operation is one level higher than the third recovery action of the third preset level. Step S5 further includes: when the current cause of the apparent death is a deep composite apparent death, and the link cannot return to normal after the third recovery action of the third preset level has been performed on the link, the corresponding recovery actions are sequentially performed on the link in the order from the fourth recovery action of the fourth preset level to the highest level recovery action. If the state of the link returns to normal after the fourth recovery action of the fourth preset level is performed, the subsequent actions are stopped. If the state of the link is abnormal after the fourth recovery action of the fourth preset level is performed, the fifth recovery action of the fifth preset level, which is one level higher than the fourth recovery action of the fourth preset level, is performed on the link.
[0063] In one possible implementation, the recovery action is one of heartbeat retransmission, network re-registration, RF restart, module soft reset, and hardware reset, with the order of priority from low to high. When the apparent deadlock is caused by a network-side anomaly, RF hardware deadlock, or protocol stack software deadlock, a heartbeat retransmission is first performed on the link. If the link remains abnormal after heartbeat retransmission, network re-registration is then performed. If the link remains abnormal after network re-registration, RF restart is then performed. If the link remains abnormal after RF restart, module soft reset is then performed. If the link remains abnormal after module soft reset, a hardware reset is finally performed. If the current apparent death is caused by deep integration apparent death, and the link cannot recover after heartbeat retransmission, then first perform network re-registration on the link. If the link is still abnormal after network re-registration, then perform RF restart on the link. If the link is still abnormal after RF restart, then perform module soft reset on the link. If the link is still abnormal after module soft reset, then finally perform hardware reset on the link.
[0064] In this embodiment, the graded recovery operation includes multiple recovery actions, namely heartbeat retransmission, network re-registration, radio frequency restart, module soft reset, and hardware reset. The levels of heartbeat retransmission, network re-registration, radio frequency restart, module soft reset, and hardware reset are from low to high. The lower the level of the recovery action, the lower the cost and the shorter the time. The lower level recovery action is performed on the link first, so as to realize the priority of performing low-cost and low-time-consuming means on the link.
[0065] The following will be combined with the appendix Figure 2 This application provides a detailed description of a link status monitoring and self-recovery device for a 4G wireless communication module, based on embodiments of the present application. It should be noted that the appendix... Figure 2 The illustrated device is a link status monitoring and self-recovery apparatus for a 4G wireless communication module, used to perform the functions described in this application. Figure 1 The methods shown in the embodiments are for illustrative purposes only, illustrating the parts relevant to the embodiments of this application. For specific technical details not disclosed, please refer to this application. Figure 1 The example shown.
[0066] Please see Figure 2 , Figure 2 This is a schematic diagram of a link status monitoring and self-recovery device for a 4G wireless communication module provided in an embodiment of this application. Figure 2 As shown, the device includes a data acquisition module 201, an anomaly judgment module 202, a false death judgment module 203, a cause acquisition module 204, and a link status recovery module 205;
[0067] The data acquisition module 201 is used to acquire data corresponding to the physical layer judgment index, the network access layer judgment index and the application layer judgment index respectively within a first preset time period.
[0068] The anomaly judgment module 202 is used to judge whether the physical layer is abnormal based on the data of the physical layer judgment index and obtain the corresponding current layer anomaly characteristics when the physical layer is judged to be abnormal; to judge whether the network access layer is abnormal based on the data of the network access layer judgment index and obtain the corresponding current layer anomaly characteristics when the network access layer is judged to be abnormal; and to judge whether the application layer is abnormal based on the data of the application layer judgment index and obtain the corresponding current layer anomaly characteristics when the application layer is judged to be abnormal.
[0069] The dead link determination module 203 is used to determine the link status as instantaneous network fluctuation if at least one of the physical layer, network access layer and application layer is abnormal, and to obtain the abnormal duration corresponding to the abnormal layer. If only one of the physical layer, network access layer and application layer is abnormal and the abnormal duration corresponding to the abnormal layer is less than the second preset duration, the link status is determined to be a dead link.
[0070] The data acquisition module 201 is used to acquire data corresponding to the physical layer judgment index, the network access layer judgment index and the application layer judgment index respectively within a fourth preset time period when the false death judgment module 203 determines that the current link state is an instantaneous network fluctuation.
[0071] The cause acquisition module 204 is used to perform combined analysis on the physical layer, network access layer and application layer based on the abnormal layer in the physical layer, network access layer and application layer and the current abnormal characteristics of the abnormal layer to determine that the current dead link is caused by one of the following: network side abnormality, radio frequency hardware dead link, protocol stack software dead link and deep integration dead link.
[0072] The link state recovery module 205 is used to perform corresponding hierarchical recovery operations on the link based on the current cause of the apparent failure in order to restore the link state to normal.
[0073] In this embodiment, instead of considering a single indicator in isolation, the system judges whether the physical layer is abnormal based on physical layer indicators, network access layer indicators, and application layer indicators. The system jointly determines the number of abnormal layers among the physical, network access, and application layers. Based on the number of abnormal layers and the duration of the corresponding abnormality, the system determines whether the link status is transient network fluctuation or link deadlock, thus distinguishing between the two. Based on the abnormal layers in the physical, network access, and application layers and their current abnormality characteristics, the system performs combined analysis to determine if the current deadlock is caused by one of the following: network-side anomaly, radio frequency hardware deadlock, protocol stack software deadlock, or deep integration deadlock. This allows for accurate and rapid identification of the current deadlock cause. Based on the current deadlock cause, the system performs corresponding graded recovery operations to restore the link status to normal, achieving precise link status recovery in a short time.
[0074] Those skilled in the art will clearly understand that the technical solutions of the embodiments of this application can be implemented by means of software and / or hardware. In this specification, "unit", "module" and "part" refer to software and / or hardware that can independently complete or cooperate with other components to complete a specific function, wherein the hardware may be, for example, a field-programmable gate array (FPGA), an integrated circuit (IC), etc.
[0075] Each processing unit and / or module in the embodiments of this application can be implemented by an analog circuit that implements the functions described in the embodiments of this application, or by software that executes the functions described in the embodiments of this application.
[0076] It should be noted that, for the sake of simplicity, the foregoing method embodiments are all described as a series of actions. However, those skilled in the art should understand that this application is not limited to the described order of actions, as some steps may be performed in other orders or simultaneously according to this application. Furthermore, those skilled in the art should also understand that the embodiments described in the specification are preferred embodiments, and the actions and modules involved are not necessarily essential to this application.
[0077] In the above embodiments, the descriptions of each embodiment have different focuses. For parts not described in detail in a certain embodiment, please refer to the relevant descriptions in other embodiments.
[0078] In the several embodiments provided in this application, it should be understood that the disclosed apparatus 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 system, or some features may be ignored or not executed. Furthermore, the displayed or discussed mutual couplings, direct couplings, or communication connections may be through some service interfaces; indirect couplings or communication connections between apparatuses or units may be electrical or other forms.
[0079] The units described as separate components may or may not be physically separate. The components shown as units may or may not be physical units; that is, they may be located in one place or distributed across multiple network units. Some or all of the units can be selected to achieve the purpose of this embodiment according to actual needs.
[0080] Furthermore, the functional units in the various embodiments of this application can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit. The integrated unit can be implemented in hardware or as a software functional unit.
[0081] If the integrated unit is implemented as a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage device (CMD). Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the prior art, or all or part of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a memory 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 described in the various embodiments of this application. The aforementioned memory includes various media capable of storing program code, such as USB flash drives, read-only memory (ROM), random access memory (RAM), portable hard drives, magnetic disks, or optical disks.
[0082] Those skilled in the art will understand that all or part of the steps in the various methods of the above embodiments can be implemented by a program instructing related hardware. The program can be stored in a computer-readable storage medium, which may include: a flash drive, a read-only memory (ROM), a random access memory (RAM), a magnetic disk, or an optical disk, etc.
[0083] The foregoing description is merely an exemplary embodiment of this disclosure and should not be construed as limiting the scope of this disclosure. Any equivalent changes and modifications made in accordance with the teachings of this disclosure shall still fall within the scope of this disclosure. Other embodiments of this disclosure will be readily apparent to those skilled in the art upon consideration of the specification and practice of the disclosure herein. This application is intended to cover any variations, uses, or adaptations of this disclosure that follow the general principles of this disclosure and include common knowledge or customary techniques in the art not described herein. The specification and embodiments are to be considered exemplary only, and the scope and spirit of this disclosure are defined by the claims.
Claims
1. A link status monitoring and self-recovery method for a 4G wireless communication module, characterized in that, Includes the following steps: S1: Acquire the data corresponding to the physical layer judgment indicators, network access layer judgment indicators and application layer judgment indicators respectively within the first preset time period; S2: Based on the data of the physical layer judgment indicators, judge whether the physical layer is abnormal and obtain the corresponding current layer abnormality characteristics when the physical layer is judged to be abnormal. Based on the data of the network access layer judgment indicators, judge whether the network access layer is abnormal and obtain the corresponding current layer abnormality characteristics when the network access layer is judged to be abnormal. Based on the data of the application layer judgment indicators, judge whether the application layer is abnormal and obtain the corresponding current layer abnormality characteristics when the application layer is judged to be abnormal. S3: If at least one of the physical layer, network access layer and application layer is determined to be abnormal, the abnormal duration corresponding to the abnormal layer is obtained respectively. If only one of the physical layer, network access layer and application layer is abnormal and the abnormal duration corresponding to the abnormal layer is less than the second preset duration, the link state is determined to be instantaneous network fluctuation and the process returns to step S1. If at least one of the physical layer, network access layer and application layer is abnormal and the abnormal duration corresponding to the abnormal layer is greater than or equal to the third preset duration, the link state is determined to be link dead. S4: Based on the abnormal layers in the physical layer, network access layer, and application layer, and the current abnormal characteristics of the abnormal layers, perform combined analysis on the physical layer, network access layer, and application layer to determine the current dead link cause as one of network-side abnormality, radio frequency hardware dead link, protocol stack software dead link, and deep integration dead link. S5: Based on the current cause of the apparent failure, perform the corresponding graded recovery operation on the link to restore the link to normal status.
2. The link status monitoring and self-recovery method for a 4G wireless communication module as described in claim 1, characterized in that, The physical layer anomaly characteristics include signal strength anomaly, signal quality anomaly, and module hardware anomaly. The network access layer anomaly characteristics include 4G core network attachment anomaly, registration result anomaly, and data bearer channel anomaly. The application layer anomaly characteristics include server communication anomaly, transport layer connectivity anomaly, and service data anomaly. The current layer anomaly characteristics of the physical layer include at least one of signal strength anomaly, signal quality anomaly, and module hardware anomaly. The current layer anomaly characteristics of the network access layer include at least one of 4G core network attachment anomaly, registration result anomaly, and data bearer channel anomaly. The current layer anomaly characteristics of the application layer include at least one of server communication anomaly, transport layer connectivity anomaly, and service data anomaly.
3. The link status monitoring and self-recovery method for a 4G wireless communication module as described in claim 2, characterized in that, The physical layer judgment indicators include reference signal received power, signal-to-interference-plus-noise ratio (SIR), RF transmission status, and RF reception status. Step S2, which judges whether the physical layer is abnormal based on the data from the physical layer judgment indicators and obtains the corresponding current layer abnormality feature when the physical layer is determined to be abnormal, specifically includes: if the reference signal received power meets a first preset condition, the physical layer is determined to have a signal strength abnormality; if the SIR meets a second preset condition, the physical layer is determined to have a signal quality abnormality; if the RF transmission status meets a third preset condition and / or the RF reception status meets a fourth preset condition, the physical layer is determined to have a module hardware abnormality; if the physical layer has at least one of signal strength abnormality, signal quality abnormality, and module hardware abnormality, the physical layer is determined to be abnormal and this is used as the corresponding current layer abnormality feature.
4. A link status monitoring and self-recovery method for a 4G wireless communication module as described in claim 2 or 3, characterized in that, The network access layer judgment indicators include EPS attachment status, network registration status, and PDN connection status. Step S2, based on the data from these indicators, specifically determines whether the network access layer is abnormal, including: if the EPS attachment status meets the fifth preset condition, the network access layer is determined to have an abnormal attachment to the 4G core network; if the network registration status meets the sixth preset condition, the network access layer is determined to have an abnormal registration result; if the PDN connection status meets the seventh preset condition, the network access layer is determined to have an abnormal data bearer channel; if the network access layer exhibits at least one of the following abnormalities: abnormal attachment to the 4G core network, abnormal registration result, or abnormal data bearer channel, the network access layer is determined to be abnormal and this is used as the current layer abnormality characteristic of the network access layer.
5. A link status monitoring and self-recovery method for a 4G wireless communication module as described in claim 2 or 3, characterized in that, The application layer judgment indicators include heartbeat response latency, heartbeat packets, TCP connection status, and data upload success rate. Step S2, which determines whether the application layer is abnormal based on the data of the application layer judgment indicators, specifically includes: if the heartbeat packet response delay meets the eighth preset condition and / or the heartbeat packet meets the ninth preset condition, then it is determined that the application layer has an abnormal communication with the server; if the TCP connection status meets the tenth preset condition, then it is determined that the application layer has an abnormal transport layer connectivity; if the uplink data success rate meets the eleventh preset condition, then it is determined that the application layer has an abnormal business data; if the application layer has at least one of the following: abnormal communication with the server, abnormal transport layer connectivity, and abnormal business data, then it is determined that the application layer is abnormal and this is taken as the current layer abnormality feature of the application layer.
6. A link status monitoring and self-recovery method for a 4G wireless communication module as described in claim 2 or 3, characterized in that, The graded recovery operation includes multiple recovery actions in ascending order of level; step S4 includes: when the physical layer is normal, the current layer anomaly of the network access layer is registration anomaly, and the current layer anomaly of the application layer is communication anomaly with the server, the cause of the link freeze is determined to be a network-side anomaly; when the current layer anomaly of the network access layer is registration result anomaly, the current layer anomaly of the application layer is communication anomaly with the server, and the current layer anomaly of the physical layer includes signal strength anomaly and / or module hardware anomaly, the cause of the link freeze is determined to be a radio frequency hardware freeze; when the physical layer is normal, the network access layer is normal, and the application layer anomaly .... When the current layer anomaly characteristics of the application layer include abnormal communication with the server and / or abnormal transport layer connectivity, the current dead link is determined to be caused by a protocol stack software dead link. When the physical layer, network access layer, and application layer are abnormal, the current layer anomaly characteristics of the network access layer (registration result abnormality), the current layer anomaly characteristics of the application layer (interaction with the server abnormality), and the current layer anomaly characteristics of the physical layer (signal strength abnormality and / or module hardware abnormality) are determined to be true. If they are not true, a recovery action of any level except the highest level is performed on the link. If the link cannot be restored to normal, the current dead link is determined to be caused by a deep integrated dead link.
7. The link status monitoring and self-recovery method for a 4G wireless communication module as described in claim 6, characterized in that, Step S5 includes: when the current apparent death is caused by one of the following: network-side anomaly, radio frequency hardware death, and protocol stack software death, the corresponding recovery actions are executed sequentially on the link in order from the lowest level recovery action to the highest level recovery action. If the link status returns to normal after executing the first recovery action of the first preset level, the subsequent actions are stopped. If the link status is abnormal after executing the first recovery action of the first preset level, a second recovery action of the second preset level, which is one level higher than the first recovery action of the first preset level, is executed on the link.
8. The link status monitoring and self-recovery method for a 4G wireless communication module as described in claim 6, characterized in that, The fourth recovery action of the fourth preset level in the graded recovery operation is one level higher than the third recovery action of the third preset level. Step S5 also includes: when the current cause of the apparent death is a deep composite apparent death, and the link cannot be restored to normal after the third recovery action of the third preset level has been performed on the link, the corresponding recovery actions are sequentially performed on the link in the order from the fourth recovery action of the fourth preset level to the highest level recovery action. If the state of the link is restored to normal after the fourth recovery action of the fourth preset level is performed, the subsequent actions are stopped. If the state of the link is abnormal after the fourth recovery action of the fourth preset level is performed, the fifth recovery action of the fifth preset level, which is one level higher than the fourth recovery action of the fourth preset level, is performed on the link.
9. A link status monitoring and self-recovery method for a 4G wireless communication module as described in claim 6, characterized in that, The recovery action is one of the following: heartbeat retransmission, network re-registration, radio frequency restart, module soft reset, and hardware reset. The levels of heartbeat retransmission, network re-registration, radio frequency restart, module soft reset, and hardware reset are from low to high in sequence.
10. A link status monitoring and self-recovery device for a 4G wireless communication module, characterized in that: It includes a data acquisition module, an anomaly detection module, a false dead detection module, a cause acquisition module, and a link status recovery module; The data acquisition module is used to acquire data corresponding to the physical layer judgment index, the network access layer judgment index and the application layer judgment index within a first preset time period. The anomaly detection module is used to determine whether the physical layer is abnormal based on the data of the physical layer detection index and to obtain the corresponding current layer anomaly characteristics when the physical layer is determined to be abnormal; to determine whether the network access layer is abnormal based on the data of the network access layer detection index and to obtain the corresponding current layer anomaly characteristics when the network access layer is determined to be abnormal; and to determine whether the application layer is abnormal based on the data of the application layer detection index and to obtain the corresponding current layer anomaly characteristics when the application layer is determined to be abnormal. The dead link determination module is used to determine the link status as instantaneous network fluctuation if at least one of the physical layer, network access layer and application layer is abnormal, and to obtain the abnormal duration corresponding to the abnormal layer. If only one of the physical layer, network access layer and application layer is abnormal and the abnormal duration corresponding to the abnormal layer is less than a second preset duration, the link status is determined to be a dead link. The data acquisition module is used to acquire data corresponding to the physical layer judgment indicator, the network access layer judgment indicator and the application layer judgment indicator within a fourth preset time period when the fake dead judgment module determines that the current link state is an instantaneous network fluctuation. The cause acquisition module is used to perform combined analysis on the physical layer, network access layer and application layer based on the abnormal layer in the physical layer, network access layer and application layer and the current abnormal characteristics of the abnormal layer to determine that the current dead link is caused by one of the following: network side abnormality, radio frequency hardware dead link, protocol stack software dead link and deep integration dead link. The link state recovery module is used to perform corresponding hierarchical recovery operations on the link based on the current cause of the apparent failure in order to restore the link state to normal.
