Network exception processing method, network device, terminal and storage medium

Abstract

The invention provides a network exception processing method, network equipment, a terminal and a storage medium. The method comprises the following steps: acquiring network state information sent by a terminal; the network state information is acquired by the terminal based on the network sensing module under a network abnormal condition; analyzing the network state information to obtain network processing information; the network processing information at least comprises at least one of terminal processing information, a switching target and resource configuration of the switching target; and sending the network processing information to the terminal, so that the terminal executes the network processing information.

Description

Technical Field

[0001] This application relates to the field of communication technology, and in particular to a network anomaly handling method, network device, terminal and storage medium. Background Technology

[0002] In modern communication networks, terminal devices may encounter various abnormal situations during network access and use, such as access failure, connection interruption, or performance fluctuations under multi-network coexistence. These problems can be caused by factors such as network environment complexity, differences in terminal configuration, or unreasonable resource allocation.

[0003] To improve user experience, many related technologies start from the terminal side, responding to anomalies by sensing the current network status and executing switching strategies. These strategies rely on the terminal's own judgment and operation, which alleviates the problem to some extent, but their effectiveness is uncertain because the actual experience of the target network cannot be accurately assessed in advance.

[0004] Optimization methods on the terminal side of related technologies are insufficient to fundamentally solve network anomaly problems. This can lead to service interruptions or poor performance on the terminal after network switching, affecting the overall service quality. Summary of the Invention

[0005] This application provides a network anomaly handling method, network device, terminal, and storage medium, which can combine the real-time perception capability of the terminal side with the global analysis capability of the network side to realize an anomaly handling mechanism of end-to-end network collaboration.

[0006] The technical solution of this application embodiment is implemented as follows: In a first aspect, embodiments of this application provide a network anomaly handling method, applied to a network device; the network anomaly handling method includes: Obtain network status information sent by the terminal; the network status information is collected by the terminal based on the network sensing module in the event of network anomalies. Analyze the network status information to obtain network processing information; the network processing information includes at least one of the following: terminal processing information, handover target, and resource configuration of the handover target; The network processing information is sent to the terminal so that the terminal can execute the network processing information.

[0007] Secondly, embodiments of this application provide a network anomaly handling method, which is applied to a terminal; the network anomaly handling method includes: Anomaly detection is performed based on a network sensing module; Acquire network status information collected by the network sensing module in the event of network anomalies; Send network status information to network devices; In response to network processing information sent by a network device, perform the network processing information; the network processing information includes at least one of terminal processing information, handover target, and resource configuration of the handover target.

[0008] Thirdly, embodiments of this application provide a network device, including: a memory for storing computer-executable instructions or computer programs; and a processor for executing the computer-executable instructions or computer programs stored in the memory to implement the network anomaly handling method provided in embodiments of this application.

[0009] Fourthly, embodiments of this application provide a terminal, including: a memory for storing computer-executable instructions or computer programs; and a processor for executing the computer-executable instructions or computer programs stored in the memory to implement the network anomaly handling method provided in embodiments of this application.

[0010] Fifthly, embodiments of this application provide a computer-readable storage medium storing a computer program or computer-executable instructions for implementing the network anomaly handling method provided in embodiments of this application when executed by a processor.

[0011] Sixthly, embodiments of this application provide a computer program product, including a computer program or computer executable instructions, which, when executed by a processor, implement the network anomaly handling method provided in embodiments of this application.

[0012] This application provides a network anomaly handling method, network device, terminal, and storage medium. It can acquire network status information sent by the terminal. This network status information is collected by the terminal based on a network sensing module under network anomaly conditions. The network status information is analyzed to obtain network processing information. The network processing information includes at least one of the following: terminal processing information, a switching target, and the resource configuration of the switching target. The network processing information is sent to the terminal so that the terminal can execute the network processing information. Thus, through the terminal's built-in network sensing module, detailed network status information is collected when a network anomaly occurs and sent to the network device, enabling the network side to obtain more comprehensive and accurate anomaly context information. The network device performs in-depth analysis of this information, generates network processing information, and feeds it back to the terminal, guiding it to perform corresponding repair or switching operations. On the one hand, it combines the real-time sensing capability of the terminal side with the global analysis capability of the network side, realizing a collaborative processing mechanism where the network side provides network processing information to the terminal through global analysis, and the terminal adjusts based on the network processing information, improving the targeting and efficiency of anomaly handling. On the other hand, by leveraging the global perspective and resource management capabilities of the network side, a better network configuration scheme can be selected for the terminal, thereby improving the terminal user experience and optimizing overall network performance. Attached Figure Description

[0013] Figure 1 This is a schematic diagram of the network device provided in the embodiments of this application; Figure 2 This is an optional flowchart illustrating the network anomaly handling method provided in this application embodiment. Figure 1 ; Figure 3 This is an optional flowchart illustrating the network anomaly handling method provided in this application embodiment. Figure 2 ; Figure 4 This is an optional flowchart illustrating the network anomaly handling method provided in this application embodiment. Figure 3 ; Figure 5 This is a flowchart illustrating the network optimization method provided in the embodiments of this application.

[0014] It should be noted that the terms "first" and "second" mentioned above are only used to distinguish between different options and do not represent the degree of superiority or inferiority of the options or their priority in the implementation process. Detailed Implementation

[0015] To make the objectives, technical solutions, and advantages of this application clearer, the application will be further described in detail below with reference to the accompanying drawings. The described embodiments should not be regarded as limitations on this application. All other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of this application.

[0016] It should be understood that the following description of the embodiments is intended to explain and illustrate the overall concept of the embodiments of this application, and should not be construed as limiting the embodiments of this application. In the specification and drawings, the same or similar reference numerals refer to the same or similar parts or components. For clarity, the drawings are not necessarily drawn to scale, and some well-known parts and structures may be omitted in the drawings.

[0017] In some embodiments, unless otherwise defined, the technical or scientific terms used in the embodiments of this application should have the meaning understood by a person skilled in the art to which the embodiments of this application pertain. The terms "first," "current service," and similar terms used in the embodiments of this application do not indicate any order, quantity, or importance, but are merely used to distinguish different components. The word "a" or "an" does not exclude multiple components. The terms "comprising" or similar terms mean that the element or object preceding the word covers the elements or objects listed after the word and their equivalents, but do not exclude other elements or objects. The terms "connected" or "linked" are not limited to physical or mechanical connections, but can include electrical connections, whether direct or indirect. Terms such as "upper," "lower," "left," "right," "top," or "bottom" are used only to indicate relative positional relationships, and these relative positional relationships may change accordingly when the absolute position of the described object changes. When an element such as a layer, film, region, or substrate is referred to as being "above" or "below" another element, the element may be located "directly" above or below the other element, or there may be intermediate elements present.

[0018] Currently, based on the analysis of numerous live network terminal logs, the main network problems faced by terminals can be categorized into: access anomalies, connection anomalies, and multi-network anomalies. These anomalies occur in different modules, and optimization strategies are also implemented in different modules. However, anomalies between different modules can actually affect each other, which greatly complicates the localization and resolution of problems.

[0019] Terminals may encounter various types of network anomalies during access, connection, and multi-network collaboration, such as protocol signaling access anomalies (e.g., RRC link establishment failure), degraded connection quality (e.g., weak network, high latency), and uneven resource allocation in multi-network coexistence. In related technologies, terminals can rely on their own strategies (e.g., cell switching or SIM card switching) to cope with these anomalies, but they lack an understanding of the overall network state, resulting in a lack of basis for optimization strategies, making it difficult to fundamentally solve network fault problems, and the improvement effect remains uncertain.

[0020] To address the aforementioned technical issues, this application provides a network anomaly handling method. The method utilizes a network sensing module built into the terminal to collect and report network status information to the network device when a network anomaly is detected. The network device analyzes the received information to generate network processing information, including terminal processing information, switching targets, and resource configurations, and feeds this information back to the terminal to guide it in performing appropriate repair or switching operations. By combining the real-time sensing capabilities of the terminal with the global analysis capabilities of the network, a collaborative anomaly handling mechanism between the terminal and the network is achieved. This not only enhances the terminal's adaptability in abnormal situations but also improves the utilization efficiency of network resources and the overall service quality.

[0021] In this way, by combining the real-time perception capabilities of the terminal side with the global analysis capabilities of the network side, an abnormal handling mechanism for terminal-network collaboration is realized, which not only improves the terminal's adaptability in abnormal situations, but also improves the utilization efficiency of network resources and the overall service quality.

[0022] In some embodiments, the network anomaly handling method provided in this application can be executed by a network device, wherein the network device can be a base station, a core network node, or other communication device with data processing capabilities.

[0023] Figure 1 This is a schematic diagram of the network device provided in the embodiments of this application. Figure 1 The network device 10 shown includes at least one processor 110, a memory 150, at least one network interface 120, and a user interface 130. The various components of the network device are coupled together via a bus system 140. It is understood that the bus system 140 is used to implement communication between these components. In addition to a data bus, the bus system 140 also includes a power bus, a control bus, and a status signal bus. However, for clarity, ... Figure 1 The general labeled all buses as Bus System 140.

[0024] The processor 110 can be a computing core component that executes executable instructions stored in memory. The processor can take the form of a microcontroller unit (MCU), a central processing unit (CPU), an application-specific integrated circuit (ASIC), a general-purpose processor, a digital signal processor (DSP), or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. Among them, the general-purpose processor can be a microprocessor or any conventional processor, etc.

[0025] User interface 130 includes one or more output devices 131 that enable the presentation of media content, and one or more input devices 132.

[0026] Memory 150 may be removable, non-removable, or a combination thereof. Exemplary hardware devices include solid-state memory, hard disk drives, optical disk drives, etc. Memory 150 may optionally include one or more storage devices physically located away from processor 110. Memory 150 may include volatile memory or non-volatile memory, or both. Non-volatile memory may be read-only memory (ROM), and volatile memory may be random access memory (RAM). The memory 150 described in this application embodiment is intended to include any suitable type of memory.

[0027] There is a close data interaction relationship between the memory and the processor in network devices. The memory provides the processor with the necessary programs and data, and the processor performs calculations and generates control outputs based on this data.

[0028] In some embodiments, memory 150 is capable of storing data to support various operations, examples of which include AI agents, programs, modules, and data structures or subsets or supersets thereof, as illustrated below.

[0029] Operating system 151 includes system programs for handling various basic system services and performing hardware-related tasks, such as the framework layer, core library layer, driver layer, etc., for implementing various basic business functions and handling hardware-based tasks; The network communication module 152 is used to reach other computing devices via one or more (wired or wireless) network interfaces 120, exemplary network interfaces 120 including: Bluetooth, WiFi, and Universal Serial Bus (USB), etc. The input processing module 153 is used to detect one or more inputs or interactions from one or more input devices 132.

[0030] In some embodiments, the apparatus provided in this application may be implemented in software. Figure 1 A network anomaly handling device 154 stored in memory 150 is shown. This device 154 can be software in the form of programs and plug-ins, and includes the following software modules: an acquisition module 1541, an analysis module 1542, and a sending module 1543. These modules can be logically linked and therefore can be arbitrarily combined or further separated according to the functions they implement. The functions of each module will be described below.

[0031] In other embodiments, the apparatus provided in this application can also be implemented in hardware. As an example, the apparatus provided in this application can be a processor in the form of a hardware decoding processor, which is programmed to execute the network exception handling method provided in this application. For example, the processor in the form of a hardware decoding processor can be one or more application-specific integrated circuits (ASICs), DSPs, programmable logic devices (PLDs), complex programmable logic devices (CPLDs), field-programmable gate arrays (FPGAs), or other electronic components.

[0032] The technical solution of this application will now be described in detail with reference to the accompanying drawings.

[0033] Figure 2 This is an optional flowchart illustrating the network anomaly handling method provided in this application embodiment. Figure 1 ,like Figure 2 As shown, the network anomaly handling method provided in this application embodiment can be implemented through steps S201 to S203: Step S201: Obtain network status information sent by the terminal; the network status information is collected by the terminal based on the network sensing module under abnormal network conditions.

[0034] Here, the network awareness module can be the network anomaly recognition engine in the terminal. The network status information is the data collected and reported by the terminal through the built-in network anomaly recognition engine after the terminal detects a network anomaly.

[0035] In some embodiments, network anomalies may include protocol signaling access anomalies during the access phase, service-mode connection anomalies during the connection process, and multi-network connection anomalies. Protocol signaling access anomalies primarily refer to various signaling interaction problems encountered by the terminal device during its network access attempts, including: access anomalies such as the terminal being in a no-service state, Random Access Channel (RACH) failure, and Radio Resource Control (RRC) / Non-Access Stratum (NAS) compatibility issues. These anomalies directly affect the success rate of the signaling process when the terminal transitions from an idle state to a connected state.

[0036] When a terminal successfully establishes a connection and is in service mode, it may encounter situations such as weak network connection (signal strength or quality is insufficient to support stable data transmission), congested connection (network resource constraints leading to decreased throughput or increased packet loss), or high latency connection (significantly increased end-to-end latency affecting real-time service experience). These anomalies can severely reduce service availability and user experience, requiring network or terminal awareness and optimization.

[0037] In multi-network collaborative scenarios, the scope of anomaly detection extends to fault situations during multi-network parallel operation or handover, mainly including: dual-SIM operator network anomalies, which simultaneously involve the issues described in Category 1 (protocol signaling access anomalies) and Category 2 (service-mode connection anomalies), as well as abnormal SIM card switching, abnormal handover back, and conflicts or failures when dual-SIM cards are used concurrently; mutual anomalies in the coexistence of WiFi and cellular networks, such as WiFi-side anomalies including quality issues like weak network, congestion, and high latency, while the cellular side also covers Category 1 and Category 2 anomalies. Additionally, it includes anomalies during WiFi to cellular and cellular to WiFi handover processes, as well as interference or performance degradation when WiFi and cellular are working concurrently. Multi-network connection anomalies characterize the collaborative failures and handover reliability issues between different access technologies.

[0038] Network status information describes the current connection status and anomalies between the terminal and the network, serving as the basis for subsequent analysis and decision-making by network devices. For example, when a terminal detects anomalies such as signal quality degradation, access failure, or handover failure, it can collect parameters such as the Physical Cell Identity (PCI), Tracking Area Code (TAC), Absolute Radio Frequency Channel Number (ARFCN), Reference Signal Received Power (RSRP), Reference Signal Received Quality (RSRQ), and Block Error Rate (BLER) of the current serving cell, and upload them to the network device through the network interface.

[0039] In some embodiments, network status information may also include de-identified terminal information, such as the International Mobile Equipment Identity (IMEI), to facilitate network devices in analyzing the cause of anomalies by combining the terminal's historical behavior records. For example, if a terminal reports the same anomaly multiple times, it may indicate that the terminal has a specific compatibility issue or hardware defect, causing it to frequently exhibit the same anomaly.

[0040] Step S202: Analyze the network status information to obtain network processing information; the network processing information includes at least one of the following: terminal processing information, handover target, and resource configuration of the handover target.

[0041] In some embodiments, the network device can invoke anomaly analysis algorithms based on received network status information to determine the type of problem the current anomaly belongs to, and generate corresponding network processing information. The network processing information may include multiple sub-items, depending on the anomaly type and its degree of impact.

[0042] In this context, terminal processing information refers to the cause of the anomaly and suggested repair strategies reported by the network device to the terminal when an anomaly occurs in protocol signaling access (such as RRC connection establishment failure). For example, if the terminal reports RRC reject with cause=0, the network device can determine that this is due to a problem with the signaling interaction between the terminal and the network, possibly caused by insufficient resources or configuration errors. In this case, the network device can send specific repair strategies to the terminal, such as changing the cell for reconnection, adjusting the number of retries or the waiting time on the terminal side, etc.

[0043] The handover target refers to the target cell or network that the network device recommends the terminal to switch to when a connection failure or multi-network failure occurs. For connection failures, the handover target can be another cell that the terminal can switch to, such as a neighboring cell with better signal quality and lower network load. For multi-network failures, the handover target might be another network, such as switching from WiFi to a cellular network, or from SIM 1 to SIM 2. The selection of the handover target depends on the network device's assessment of the overall network status, including at least indicators such as signal strength, bandwidth resource utilization, and historical handover success rate.

[0044] Network devices can accurately identify the problems faced by terminals by deeply analyzing network status information and provide targeted solutions. This not only helps improve the terminal's adaptability but also effectively alleviates network congestion, optimizes resource allocation, and thus improves overall network performance and service quality.

[0045] In some embodiments, network devices can also perform long-term optimization of certain cells that frequently experience problems based on the number of times anomaly marking occurs. For example, if a cell is marked as congested or has poor signal quality multiple times, the network device may consider increasing the base station deployment density in the area where the cell is located, or adjusting the resource configuration of the cell, to improve service quality.

[0046] Step S203: Send network processing information to the terminal so that the terminal can execute the network processing information.

[0047] In this embodiment, the network device can send network processing information back to the terminal via an interface. After receiving the network processing information, the terminal can decide whether to perform an operation corresponding to the network processing information based on its service requirements and current state. For example, if the network processing information contains a handover suggestion, the terminal can perform a handover operation if the conditions are met; if the network processing information contains a repair strategy, the terminal can attempt to execute the repair strategy to restore the connection.

[0048] In some embodiments, by combining global information from network devices with real-time sensing information from the terminal, the terminal can make more scientific and rational decisions, thereby effectively responding to various network anomalies. Combining global information from network devices with real-time sensing information from the terminal not only improves the terminal's network adaptability but also enhances the overall robustness and stability of the network.

[0049] This application embodiment utilizes a network awareness module built into the terminal to collect detailed network status information when network anomalies occur and sends it to the network device. This allows the network side to obtain more comprehensive and accurate anomaly context information. The network device then performs in-depth analysis of this information, generating network processing information that is fed back to the terminal, guiding it to perform corresponding repair or switching operations. On one hand, by combining the real-time awareness capabilities of the terminal with the global analysis capabilities of the network side, a collaborative processing mechanism is achieved whereby the network side provides network processing information to the terminal through global analysis, and the terminal adjusts accordingly, improving the targeting and efficiency of anomaly handling. On the other hand, leveraging the global perspective and resource management capabilities of the network side, a better network configuration scheme can be selected for the terminal, thereby improving the terminal user experience and optimizing overall network performance.

[0050] In some embodiments, network anomalies may be protocol signaling access anomalies during the access phase of the terminal. In this case, the network status information includes at least the terminal device identifier, the current serving cell information of the terminal when the protocol signaling access anomaly occurs, and the time of the anomaly.

[0051] Terminal device identifiers can be information used to identify terminal devices, such as the IMEI (Mobile Equipment Identity). Terminal device identifiers can be used to distinguish the behavior of different terminal devices in the network, ensuring the accuracy and relevance of the analysis process. Current serving cell information refers to the relevant parameters of the base station or cell to which the terminal is connected when a protocol signaling access anomaly occurs, such as the Physical Cell Identifier (PCI), Tracking Area Code (TAC), and Frequency Point (ARFCN). Anomaly time point refers to the specific moment when the terminal detects the abnormal event, used to accurately locate the anomaly time point, which helps in backtracking logs and analyzing the context.

[0052] Step S202 can be achieved through steps S1 to S3: Step S1: Based on the terminal device identifier, current serving cell information, and abnormal time point, filter the signaling in the signaling database to obtain the target signaling record.

[0053] Here, the signaling database can be a historical data set that stores control signals (i.e., signaling) exchanged between the terminal and the network. The signaling stored in the signaling database can include key communication processes such as RRC connection requests, NAS registration requests, and handover commands. By using terminal device identifiers, current serving cell information, and abnormal time points as filtering criteria, signaling records related to the terminal device that occurred at specific times and locations can be extracted from the vast signaling database to form target signaling records.

[0054] Step S2: Based on the target signaling record, generate the timing interaction flow between the terminal and the network device.

[0055] In this embodiment of the application, the timing interaction process can be a diagram of the interaction process between the terminal and the network arranged in chronological order according to the target signaling record, reflecting the signaling transmission and reception status reflected in the timing interaction process.

[0056] Step S3: Verify the timing interaction process based on the protocol state machine to obtain terminal processing information.

[0057] A protocol state machine (PVM) is a model that describes the state changes of the communication protocol between a terminal and the network. The PVM defines the possible signaling inputs and corresponding output actions for each state. By comparing the timing interaction process with the PVM, it is possible to verify whether the communication process conforms to the expected protocol logic, discover potential abnormal nodes or state transition errors, and ultimately generate terminal processing information reflecting the terminal's processing behavior. This terminal processing information can be used to determine whether there are protocol compatibility issues, configuration errors, or other root causes of anomalies.

[0058] This application's embodiments, by combining key information such as terminal device identifier, current serving cell information, and abnormal time points, accurately filter relevant signaling records from the signaling database, which helps to construct a complete time-series interaction process between the terminal and the network. Verifying the process based on the protocol state machine can identify issues such as abnormal state transitions and protocol errors, thereby generating clearly directional terminal processing information. This approach not only improves the accuracy of problem localization but also provides a reliable basis for subsequent remediation strategy formulation.

[0059] In some embodiments, step S3 can be implemented by steps S31 to S33: Step S31: Perform anomaly detection on the timing interaction process based on the protocol state machine and obtain the detection results; the anomaly detection includes at least state transition anomaly detection and protocol error detection.

[0060] In this embodiment, the time-series interaction process refers to a series of operations performed by the terminal in a certain time sequence during network connection, data transmission, etc. These operations include at least access requests, signaling interactions, resource allocation, and data sending and receiving. When a step in the process does not occur as expected or is out of order, it indicates an anomaly.

[0061] Anomaly detection can be a process of identifying abnormal behaviors in a timing interaction flow based on a protocol state machine. Anomaly detection mechanisms determine whether there are illegal transitions or protocol errors by tracking the transition paths between states in real time. For example, if a terminal should enter the data transmission state after establishing an RRC connection but instead jumps directly to the disconnected state, this can be considered an abnormal state transition.

[0062] State transition anomaly detection refers to checking whether the transitions between states in a protocol state machine conform to preset rules. If the actual transition path does not conform to the protocol specification, it is considered an anomaly. For example, in wireless communication, a terminal should not transition directly from the idle state to the released state, but should first go through the connection establishment state.

[0063] Protocol error detection refers to checking whether the signaling messages exchanged between the terminal and the network conform to the protocol specifications. For example, incorrect message format, missing necessary fields, or parameter values ​​exceeding the allowed range are all considered protocol errors.

[0064] Step S32: Based on the detection results, determine the cause of the network anomaly and the network repair strategy; wherein, the network repair strategy includes terminal-side repair strategy and network-side repair strategy.

[0065] Network anomalies can refer to the fundamental factors causing communication abnormalities, including weak signal, handover failure, insufficient resource allocation, and signaling interaction failure. For example, when an RRC connection failure is detected and the reason for rejection is "no service," the network anomaly may be caused by poor signal quality or misconfiguration in the current cell.

[0066] Terminal-side repair strategies refer to proactive optimization measures taken by the terminal to address current anomalies and attempt to restore normal communication. Examples include switching cells for reconnection, intelligent dual-SIM switching, switching between Wi-Fi and cellular networks, and retrying failed operations. Terminal-side repair strategies can improve user experience without relying on the network side.

[0067] Network-side repair strategies refer to repair actions initiated by the network side, which can involve global network configuration adjustments or resource scheduling. For example, to address frequent access failures in a particular cell, the power configuration of that specific cell can be adjusted, the handover threshold can be changed, or a new base station can be introduced to alleviate congestion. Network-side repair strategies can resolve cell access failures at their root, thereby improving overall network performance.

[0068] Step S33: Determine the cause of the network anomaly and the terminal-side repair strategy as terminal processing information.

[0069] Terminal processing information is information sent to the terminal by the network device, which includes the cause of the network anomaly and the repair strategies that the terminal can execute. In this way, the terminal can make local optimization decisions quickly through terminal processing information.

[0070] For example, after detecting an RRC connection failure, the terminal records the specific reason for the event (e.g., RRCreject), the time point, and parameters such as the PCI, TAC, and RSRP of the cell it is located in, and uploads them to the network side. The network side then generates terminal processing information containing a suggested handover to a neighboring cell and sends it to the terminal, which then determines whether to execute the plan. Based on similar issues reported by multiple terminals, the network side can determine whether the cell needs capacity expansion or parameter adjustments.

[0071] This application's embodiments introduce a protocol state machine mechanism to perform structured analysis of the interaction process between the terminal and network devices. This enables the identification of common problem types such as abnormal state transitions and protocol errors, obtaining specific network anomaly causes, and formulating repair strategies for both the terminal and network sides. This facilitates multi-dimensional anomaly handling, and the terminal-side repair strategy is returned as part of the terminal's processing information, allowing the terminal to autonomously adjust configuration parameters, thereby improving response speed and repair efficiency.

[0072] In some embodiments, network anomalies can also be terminal service state connection anomalies. In this case, the network status information includes at least the current serving cell information and neighboring cell information when the terminal connection is abnormal.

[0073] The current serving cell refers to the cellular network cell that the terminal is currently connected to and communicating with. Information about the current serving cell may include parameters such as Physical Cell Identifier (PCI), ARFCN, and RSRP, used to describe the basic conditions of the network the terminal is currently in. Neighboring cells are other cells adjacent to or available for handover to the current serving cell. Information about neighboring cells includes measurements, signal quality (RSRQ), and interference ratio (SINR), used to assess whether handover conditions are met. Obtaining information about the current serving cell and neighboring cells provides a foundation for constructing a subsequent candidate cell set.

[0074] Correspondingly, step S202 can also be achieved through steps S4 to S7: Step S4: Based on the current serving cell information and neighboring cell information, determine the candidate cell set. The candidate cell set includes at least the terminal's current serving cell and at least one neighboring cell.

[0075] Here, the candidate cell set consists of the currently serving cell and several neighboring cells of the currently serving cell, serving as the target selection range for possible terminal handover. The currently serving cell itself is included in the set to ensure that it can continue to be used even if there are minor problems with the currently serving cell; the neighboring cells serve as alternative targets to find cells with stronger signals and higher service quality.

[0076] Step S5: Obtain the network service information of each cell in the candidate cell set.

[0077] In some embodiments, network service information may refer to information related to the actual operation and service capabilities of each cell in the candidate cell set obtained by the network side itself, including at least data such as the interface link status, resource availability, and historical handover success rate of each cell.

[0078] Step S6: Based on the current serving cell information, neighboring cell information, and network service information, evaluate the current serving cell and each candidate cell to obtain the network service score of each cell in the candidate cell set.

[0079] Here, the network service score can be a comprehensive evaluation of the service quality of candidate cells. This score can be calculated by weighting multiple indicators from the current serving cell information, neighboring cell information, and network service information. For example, cells with higher signal strength and lower interference can receive higher scores. By scoring each cell, it can be determined which cells are more suitable for the terminal's current network needs, thus enabling the terminal to make the optimal handover decision.

[0080] Step S7: Based on the network service score, determine the handover cell for the terminal from the candidate cell set; the handover target includes at least the handover cell.

[0081] Here, the handover cell can refer to the target cell that is finally selected based on the scoring results for the terminal to perform the handover operation. The cell with the highest score can be selected from multiple candidate cells as the handover target based on the network service score.

[0082] In some embodiments, there can be multiple handover targets. When selecting a handover target, alternative cells other than the primary target cell can be included to provide an alternative if the primary target cell is unavailable.

[0083] This application's embodiments generate a network service score for each cell by comprehensively considering relevant information from the current serving cell and neighboring cells uploaded by the terminal, as well as the obtained network service information, thereby scientifically and rationally determining the optimal handover target. This not only improves the objectivity and accuracy of handover decisions but also effectively avoids user experience degradation caused by blind handovers and enhances the adaptability and flexibility of network anomaly handling.

[0084] In some embodiments, the current serving cell information includes at least one of the following metrics: signal strength, signal quality, signal-to-interference-plus-noise ratio (SINR), and block error rate; the neighboring cell information includes at least one of the following metrics: signal strength, signal quality, SINR, and block error rate; and the network service information includes at least one of the following metrics: interface link status, resource availability, and historical handover success rate.

[0085] Here, Signal Strength (RSRP, Reference Signal Received Power) refers to the power of the wireless signal received by the terminal, used to measure the distance between the terminal and the base station and the signal propagation conditions. A stronger signal indicates higher communication quality. Signal Quality (RSRQ, Reference Signal Received Quality) reflects the degree of channel interference and demodulation capability. Better signal quality means more stable data transmission. Signal-to-Interference-plus-Noise Ratio (SINR) represents the ratio of useful signal to the sum of interference and noise. A higher SINR indicates a clearer signal and higher reliability of the communication system. Block Error Rate (BLER) represents the proportion of data blocks transmitted within a certain time period that contain errors, used to measure the stability of the communication link. A lower BLER indicates higher communication quality. Interface Link Status refers to the operational status of the communication link between the terminal and the network, including whether it is connected, and whether there are issues such as packet loss or delay. Resource Availability refers to the availability of wireless resources on the network side for the terminal, such as spectrum bandwidth, time slot allocation, and channel utilization. Historical handover success rate refers to the percentage of successful cell handovers completed by a terminal within a certain period of time. Historical handover success rate is used to predict the access stability of a target cell.

[0086] Correspondingly, step S6 can be achieved through steps S61 and S62: Step S61: Normalize the indicators in the current serving cell information, neighboring cell information, and network service information to obtain the normalized values ​​of each indicator for each cell.

[0087] In some embodiments, normalization unifies data of different dimensions or ranges to the same scale, facilitating comparison and comprehensive evaluation. For example, signal strength may range from -120dBm to -60dBm, while block error rate is a decimal between 0 and 1. After normalization, all metrics are mapped to the [0,1] interval, making metrics of different dimensions comparable.

[0088] Normalization methods can include min-max normalization, which calculates the minimum and maximum values ​​for each indicator and linearly transforms the original values ​​to the range [0,1]. Alternatively, Z-score normalization can be used, which subtracts the mean from the original value and then divides by the standard deviation to center and standardize the distribution of the original values. There are no restrictions on this method.

[0089] Step S62: Determine the network service score for each cell based on the normalized values ​​of each indicator corresponding to each cell.

[0090] In some embodiments, normalized values ​​can be calculated based on various indicators of each cell, and then weighted and summed to generate a comprehensive score, which is the network service score. The higher the network service score, the better the overall service quality of the cell, and the more suitable it is as a target cell for terminal access.

[0091] In this embodiment, the network service score of each cell is calculated by key indicators reflecting the quality of network service, thereby determining the target cell, which improves the objectivity and rationality of cell handover decision-making and helps to achieve efficient collaboration between the terminal and the network.

[0092] In some embodiments, network anomalies can also be multi-network connection anomalies, in which case the network status information includes at least the signal quality indicators of multiple networks when the multi-network anomaly occurs.

[0093] Multi-network anomaly refers to a situation where a terminal is simultaneously connected to or operating on multiple networks (such as cellular networks and Wi-Fi), and one or more of these networks experience a failure or performance degradation. Signal quality metrics are a set of quantitative parameters used to evaluate the communication quality between a terminal and a network, and at least include reference signal received power, reference signal received quality, signal-to-interference-plus-noise ratio (SINNR), and block error rate (BER).

[0094] The network anomaly handling method provided in this application embodiment may further include step S11: Step S11: Obtain the query request information sent by the terminal. The query request information includes at least a list of query indicators for multiple networks other than the currently connected network.

[0095] Query request information can be a data structure in which a terminal proactively requests other network-related information from the network side when it detects a potential problem with the current network connection. The terminal generates query request information based on its current business needs and network status, and then sends the query request information to the network side.

[0096] The query metric list is part of the query request information and includes other key network performance metrics that the terminal wants to know, such as bandwidth utilization, latency, jitter, and packet loss rate. Through this list, the terminal can clearly express its concerns about other networks, facilitating the network side to return relevant data in a targeted manner.

[0097] Correspondingly, step S202 can also be achieved through steps S8 and S9: Step S8: Based on the query indicator list, perform resource queries on other networks to obtain resource query results; the resource query results shall include at least the bandwidth resource utilization rate of each network.

[0098] Resource query results can be a specific data set returned by the network side based on the terminal's query request, used to assess the availability of other networks. Among these, bandwidth resource utilization reflects the network's load at the current moment. If a network's bandwidth resource utilization is high, it indicates that the network may be close to saturation, and terminals connecting to it may face higher latency or poorer service quality.

[0099] Step S9: Based on the resource query results and the signal quality indicators of multiple networks, determine the switching network and the resource configuration of the switching network in each network so that the terminal switches to the switching network; the switching target includes at least the switching network.

[0100] Network switching can refer to a target network that is considered the optimal choice after comprehensive evaluation. When a terminal receives a network switching notification, it can attempt to switch to the target network to improve communication quality.

[0101] Resource configuration includes at least frequency band allocation, channel settings, and priority adjustment, which are used to ensure that the terminal can obtain the best communication effect after handover.

[0102] By introducing network-side resource query results, the embodiments of this application enable the terminal to obtain more comprehensive network status information before switching, avoiding performance degradation caused by blind switching, improving the ability to handle anomalies in a multi-network environment, and enhancing the terminal's ability to flexibly migrate between networks, thereby significantly improving the user experience.

[0103] In some embodiments, the network anomaly handling method provided in this application may further include steps S21 and S22: Step S21: In response to network status information, mark the current serving cell of the terminal to obtain the number of abnormal markings of the current serving cell.

[0104] Here, when the network side determines that the terminal's network status is abnormal based on the network status information uploaded by the terminal (such as access anomalies, degraded connection quality, or multi-network coordination issues), it can perform an anomaly marking operation on the terminal's current serving cell. Each anomaly marking operation indicates that the current serving cell failed to meet the service quality standard within a specific time period. This situation may be caused by reasons such as resource congestion, signal interference, or protocol compatibility issues, and the cause can also be recorded simultaneously.

[0105] By counting the number of anomaly markers, we can make a preliminary assessment of whether a cell has long-term performance problems, thus providing a basis for subsequent optimization strategies.

[0106] Step S22: In response to any cell among the multiple cells corresponding to the network device having more than a preset threshold number of abnormal markers within a preset time period, analyze the abnormal situation of the cell and obtain a resource adjustment strategy for the cell.

[0107] When the number of anomaly markers accumulated in a cell within a preset time period exceeds a set threshold, the network device will initiate a problem analysis process for that cell. This process includes at least cause identification, metric comparison, resource assessment, and policy generation.

[0108] Indicator comparison can refer to the network side comparing the performance indicators (such as RSRP, SINR, BLER, etc.) of the target cell with those of other neighboring cells to confirm the relative performance of the target cell; resource assessment can consider factors such as the load, coverage, and user distribution of the target cell to assess whether measures such as adding base stations, adjusting spectrum configuration, or optimizing scheduling strategies are needed; strategy generation can generate specific resource adjustment strategies based on the analysis results, such as migrating users to better cells, increasing the capacity of cells, and optimizing handover threshold parameters.

[0109] Through the above process, network devices can formulate targeted optimization solutions based on the abnormal information reported by the terminal. After the network devices execute the optimization solutions, they can solve the current user experience problems. Furthermore, the network devices can take preventive measures to prevent the same type of problem from happening again in the future.

[0110] This application's embodiments, by continuously tracking and recording the number of anomaly markers for each cell, can accumulate sufficient data over a certain period to support the determination of whether a cell has a long-term problem. Once the number of anomaly markers for a cell exceeds a set threshold, the problem analysis process for that cell can be initiated, thereby formulating targeted resource adjustment strategies. This not only helps to promptly detect potential network faults but also provides data support for subsequent network optimization, realizing a shift from short-term repair to long-term prevention.

[0111] In some embodiments, step S201 in the network anomaly handling method provided in this application can be implemented by step S2011: Step S2011: Obtain network status information based on the preset interface.

[0112] In this embodiment of the application, the preset interface can refer to a standardized channel for communication between the terminal and the network side in a pre-agreed manner, which can be implemented using Network API technology.

[0113] The default interface is used to enable the terminal to send data requests to the network and receive feedback information from the network. The communication method used by the default interface can be based on the HTTP protocol or other signaling formats. These communication methods have a unified data structure and transmission standard.

[0114] Correspondingly, step S203 can be achieved through step S2031: Step S2031: Based on the preset interface, send the network processing information to the terminal.

[0115] This application embodiment sends network processing information to the terminal based on a preset interface, which can realize bidirectional information interaction between the terminal and the network side, and enhance the terminal's adaptability and the network side's proactive optimization capability.

[0116] This application embodiment achieves standardized information interaction between the terminal and the network side by defining a unified interface standard, which not only simplifies the information transmission process, but also improves communication efficiency, reduces information transmission delay, and thus speeds up the overall response speed of anomaly handling.

[0117] This application provides a network anomaly handling method for a terminal. The terminal can be implemented as a laptop, tablet, desktop computer, set-top box, mobile terminal (e.g., mobile phone, portable music player, personal digital assistant, dedicated messaging device, portable gaming device), or other user terminal that supports mobile network communication via at least two SIM cards. Exemplarily, the terminal may include smartphones, tablets, laptops, desktop computers, smart speakers, smartwatches, etc., running intelligent operating systems; the specific choice depends on the actual situation, and this application does not limit the choice.

[0118] Figure 3 This is an optional flowchart illustrating the network anomaly handling method provided in this application embodiment. Figure 2 ,like Figure 3 As shown, the network anomaly handling method provided in this application embodiment can be implemented through steps S301 to S304: Step S301: Perform anomaly detection based on the network perception module.

[0119] The network awareness module can include anomaly detection for multiple modules, such as access anomaly detection, connection anomaly detection, and multi-network anomaly detection. Its main function is to identify, classify, and label these anomalies. This is to help find solutions to corresponding problems for subsequent optimization, and to perceive network faults from multiple dimensions, including the communication protocol level and the user experience level.

[0120] Step S302: Obtain network status information collected by the network sensing module when the network is abnormal.

[0121] Network status information can be data collected and reported to the network side by the terminal after detecting a network anomaly.

[0122] Step S303: Send network status information to the network device.

[0123] Step S304: In response to network processing information sent by the network device, execute the network processing information; the network processing information includes at least one of terminal processing information, handover target, and resource configuration of the handover target.

[0124] When a terminal receives network processing information from a network device, it indicates that the network device has evaluated the current connection status and provided optimization suggestions or switching instructions. The terminal responds based on this information, such as adjusting connection parameters, switching cells, or switching networks (e.g., WiFi and cellular).

[0125] This application embodiment makes decisions by using global information provided by the network side, which can avoid misjudgments caused by relying on limited local measurement data. The method of making decisions by using global information provided by the network side can improve network connection quality.

[0126] Figure 4 yes Figure 4 This is an optional flowchart illustrating the network anomaly handling method provided in this application embodiment. Figure 3 , Figure 4 The interaction process between the terminal and the network device is shown. The specific implementation method is as described in the previous embodiments, and will not be repeated here.

[0127] In some embodiments, the terminal processing information includes at least the cause of the network anomaly and the terminal-side repair strategy. Step S304 can be implemented through step S3041: Step S3041: In response to the network anomaly being caused by a local configuration error, adjust the configuration parameters based on the terminal-side repair strategy.

[0128] When a terminal detects a network anomaly and communicates with the network device via the network API, if the network device reports a local configuration error as the cause of the anomaly, it indicates that the problem does not originate from the network infrastructure or external environment, but rather from improper configuration parameters within the terminal, preventing the terminal from connecting or using specific services. Examples include incorrect configuration of certain service parameters, conflicting Quality of Service (QoS) policies, incorrect access point name settings, incorrect IP address allocation, and incorrect DNS server configuration.

[0129] Here, when a terminal receives feedback from a network device regarding a local configuration error, it can adjust relevant configuration parameters according to preset terminal-side repair strategies. For example, if the Access Point Name (APN) is configured incorrectly, the terminal can try switching to the default APN; if there is a QoS policy conflict, the terminal can try reverting to the basic QoS configuration. In this way, the terminal can complete self-repair in a short time, avoiding service interruptions or performance degradation caused by configuration errors. It can quickly restore the terminal's network connectivity without manual intervention, improving the user experience.

[0130] In some embodiments, the handover target includes at least the cell being handed over. Step S304 can also be implemented via step S3042: Step S3042: In response to receiving network processing information including the cell handover information, perform a cell handover operation.

[0131] When a terminal receives network processing information containing cell handover information sent by a network device, the terminal can determine whether a cell handover operation needs to be performed based on the content of the network processing information.

[0132] Cell handover refers to the process by which a terminal, while maintaining connectivity, switches its wireless connection from the current serving cell to a target cell. The purpose of cell handover is to ensure communication continuity, improve service quality, and avoid data interruptions or packet loss due to network anomalies.

[0133] In this embodiment, when the network detects problems such as weak network, high latency, or congestion in the current cell where the terminal is located, the network side can evaluate indicators such as signal quality and load of neighboring cells, select a more suitable handover cell as the target cell, and send network processing information containing the handover cell to the terminal through the Network API. After receiving the network processing information containing the handover cell, the terminal performs the cell handover operation according to the standard protocol process, and completes the connection establishment with the handover cell.

[0134] This application embodiment introduces interaction between the network side and the terminal, which can reduce the disconnection rate of the terminal in the event of network abnormalities, thereby improving the overall availability and reliability of the network, and thus enhancing users' satisfaction and trust in communication services.

[0135] In some embodiments, the handover target includes at least the handover network, and the network processing information also includes the resource configuration of the handover network. In cellular networks, resource configuration may be reflected in base station bandwidth allocation, scheduling policies, congestion status, etc.; in Wi-Fi networks, resource configuration may include signal strength, data transmission rate, channel interference level, etc.

[0136] Step S304 can also be achieved through steps S3043 and S3044: Step S3043: In response to receiving network processing information including the switching network and the resource configuration of the switching network, the resource configuration of the switching network is compared with the resource configuration of the currently connected network to obtain the comparison result.

[0137] The comparison result can be derived by comparing the resource configuration of the target network (i.e., the switching network) with the resource configuration of the currently connected network item by item. The comparison process can be completed by the terminal or network device according to a preset algorithm to determine whether the target network has better communication conditions. For example, if the switching network has a higher signal strength, lower latency, and greater available bandwidth, then the resource configuration of the switching network is considered superior to that of the currently connected network.

[0138] Step S3044: In response to the comparison result indicating that the resource configuration of the switching network is higher than the resource configuration of the currently connected network, perform a network switching operation.

[0139] Network handover refers to a terminal switching from its currently connected network to another network under specific conditions. When the comparison results show that the resource configuration of the switched network is better than that of the currently connected network, it indicates that the switched network has advantages in terms of communication performance and quality of service. In this case, the terminal can perform a network handover operation according to instructions provided by the network device or its own policies to improve the overall communication experience.

[0140] This application embodiment ensures that the terminal is always in the optimal network environment by dynamically evaluating the resource configuration of the switched network and the resource configuration of the currently connected network and triggering reasonable network switching operations, thereby reducing service interruptions or performance degradation caused by network anomalies.

[0141] The following will describe an exemplary application of the embodiments of this application in a real-world application scenario.

[0142] To address the problems existing in related technologies, this application provides a comprehensive optimization method based on a network anomaly identification engine and a network application programming interface (Network API) technology. This comprehensive optimization method can quickly detect and classify network anomalies on the terminal side, and achieve end-to-end collaborative decision-making by synchronizing information with the network side, thereby improving user experience and overall network performance.

[0143] Figure 5 This is a flowchart illustrating the network optimization method provided in an embodiment of this application, as shown below. Figure 5 As shown, the network optimization method includes at least three steps: network anomaly detection engine 501 detects network anomalies, terminal network information synchronization 502, and network and terminal decision-making and optimization 503. The network anomaly detection engine 501 (i.e., the network sensing module) can detect network anomalies including access anomaly detection 5011, connection anomaly detection 5012, and multi-network anomaly detection 5013. Access anomaly detection 5011 includes at least access anomalies, RRC compatibility issues, NAS compatibility issues, and mobility management anomalies; connection anomaly detection 5012 includes at least weak network, congestion, and high latency; and multi-network anomaly detection 5013 includes at least dual-SIM coexistence and WiFi cellular coexistence.

[0144] The 502 error message synchronization between the terminal and the network utilizes Network API technology (i.e., a preset interface, an agreed signaling format, such as HTTP transmission) to achieve synchronization between the network side and the terminal. The network side analyzes the causes and strategies based on the obtained network error information.

[0145] Network and terminal decision-making and optimization 503 can refer to a situation where a terminal senses and marks network anomalies based on its own information, and when different network problems are identified, it sends the information to the network side for joint decision-making. For example, the following situations: The terminal detects an abnormal protocol signaling access, such as an RRC connection failure. If it is not in a connected state (e.g., RRCreject), it will switch cells and reconnect to the network. Once in a connected state, the terminal will synchronize the stored network anomaly details (i.e., network status information) to the network side, such as PCI, Tracking Area Code (TAC), ARFCN, and IMEI, to assist the network side in determining the cause of the anomaly and fixing it, based on the information input by the terminal. For example, the network can assess whether there are areas for optimization based on the protocol signaling interaction log context with the terminal (i.e., target signaling record).

[0146] For example, if a terminal detects an RRC connection establishment failure (a type of access anomaly), its built-in network anomaly detection engine identifies the current network status, determines it to be a protocol signaling access anomaly, and marks it as such. Subsequently, the terminal can attempt to switch cells to re-establish the connection. Simultaneously, the terminal synchronizes relevant anomaly information (such as PCI, Tracking Area Code (TAC), ARFCN, etc.) to the network side via the Network API to assist the network in determining whether there are system configuration or resource allocation problems.

[0147] When a terminal detects a connection anomaly, it synchronizes the anomaly of its current cell (i.e., the information of the current serving cell) and the measured neighboring cell information (such as RSRP, RSRQ, SINR, BLER, etc.) to the network. The network side combines the global data collected by the network itself (i.e., network service information, such as the information of the current cell / neighboring cells obtained by the network side) and the information of the current cell / neighboring cells obtained by the terminal side to decide on a better cell (i.e., the target cell) and switches / redirects the terminal to that cell.

[0148] For example, when a terminal is in a weak network state and reports a measurement report, the network may not respond or trigger a handover operation (a type of connection anomaly). In this case, the terminal uses an anomaly identification engine to determine that the current state is a weak network connection anomaly. The terminal synchronizes key indicators such as the current cell's RSRP, Reference Signal Received Quality (RSRQ), and Signal-to-Interference-plus-Noise Ratio (SINR) to the network side via the Network API. The network combines global network data with the detailed measurement data reported by the terminal to evaluate a better target cell and issues a handover / redirection command to the terminal to improve connection quality.

[0149] In some embodiments, the network side marks the problematic cell. When some cells are marked as abnormal multiple times, the network can be optimized in the long term. For example, if multiple cells on a certain frequency point are continuously congested and network resources do not meet user needs, more communication base stations can be deployed.

[0150] When a terminal detects an anomaly in multiple networks, it synchronizes the information of these networks (i.e., signal quality indicators of multiple networks, such as the signal quality of WiFi and cellular signals that the terminal can measure) and the items it needs to obtain (i.e., a list of query indicators, such as obtaining the bandwidth resource utilization of cellular networks when WiFi quality is poor, to assist the terminal in deciding whether to switch to cellular networks) to the network. After the network queries the resources of different networks (i.e., the resource query results), it synchronizes the network information (i.e., the network switching and the resource configuration of the switching network) to the terminal. The terminal, based on the network information obtained from the terminal and the network information from the network side, jointly decides whether to perform a network switching action, such as switching SIM cards, switching cellular networks, or switching WiFi networks.

[0151] For example, SIM 1 may experience data service congestion from its carrier, while SIM 2 is idle. However, the terminal cannot determine the carrier data status of SIM 2 (a type of multi-network anomaly). In this case, the terminal identifies a dual-SIM carrier network anomaly and sends the current status of SIM 1, along with a request to query the bandwidth utilization and available resources of SIM 2, to the network side via the Network API. The network provides feedback based on its resource information, and the terminal, based on the combined information from both the terminal and the network, decides whether to perform a SIM switching operation to achieve more efficient multi-network coordination.

[0152] The network anomaly detection engine in this application embodiment includes anomaly detection modules, perceiving network faults from multiple dimensions, including communication protocol and user experience levels. Furthermore, by leveraging network API technology to achieve end-to-end network information synchronization, it can obtain more information from the network side to assist both the network and the terminal in optimization. This not only quickly and with low loss improves the terminal experience but also optimizes the network in the medium to long term.

[0153] In this embodiment, the terminal has a built-in network anomaly detection engine. When a network anomaly is detected, it determines whether the problem is an access anomaly, connection anomaly, or multi-network anomaly, and executes different solutions accordingly. The network API technology provides the terminal with a channel to synchronize information with the network. Using this channel, the terminal and network can provide better solutions, more effectively improve the terminal experience, and optimize network configuration.

[0154] In this application embodiment, the accuracy of the network anomaly identification engine can be improved. For example, the threshold can be further expanded and improved. For instance, it is defined that a NAS reject anomaly (a core network signaling event that is rejected by the network side when the terminal (UE) initiates a registration request or session establishment request to the core network) is determined only after a certain number of occurrences. The number of occurrences can be defined based on existing log big data experience values.

[0155] The optimization schemes on the terminal side and the network side can be further expanded. For example, the network API is a powerful channel that, in addition to sharing information between the terminal requiring optimization and the network side, can also reduce the base station load by enabling more terminals to execute optimization strategies through a centralized-to-distributed approach when the network load is too high.

[0156] This application embodiment constructs a network anomaly identification engine with multi-dimensional perception capabilities and utilizes Network API technology to achieve efficient information synchronization and collaborative decision-making between the terminal and the network. This technical solution can quickly respond to network anomalies, improve the user experience on the terminal side, and provide valuable data support for the network side, promoting the long-term optimization and intelligent development of the network.

[0157] It should be noted that the description of the device embodiments in this application is similar to the description of the method embodiments described above, and has similar beneficial effects as the method embodiments; therefore, it will not be repeated. For technical details not disclosed in the device embodiments, please refer to the description of the method embodiments in this application for understanding.

[0158] In other embodiments, the apparatus provided in this application can also be implemented in hardware. As an example, the apparatus provided in this application can be a processor in the form of a hardware decoding processor, which is programmed to execute the network exception handling method provided in this application. For example, the processor in the form of a hardware decoding processor can be one or more application-specific integrated circuits (ASICs), DSPs, programmable logic devices (PLDs), complex programmable logic devices (CPLDs), field-programmable gate arrays (FPGAs), or other electronic components.

[0159] It should be noted that, in the embodiments of this application, if the above-described network anomaly handling method is implemented as a software functional module and sold or used as an independent product, it can also be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the embodiments of this application, or the part that contributes to the related technology, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a terminal to execute all or part of the methods of the various embodiments of this application. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, mobile hard drives, read-only memory (ROM), magnetic disks, or optical disks. Thus, the embodiments of this application are not limited to any specific hardware and software combination.

[0160] This application provides a storage medium storing executable instructions. When the executable instructions are executed by a processor, the processor will execute the network exception handling method provided in this application.

[0161] In some embodiments, the storage medium may be a computer-readable storage medium, such as a ferromagnetic random access memory (FRAM), a read-only memory (ROM), a programmable read-only memory (PROM), an erasable programmable read-only memory (EPROM), an electrically erasable programmable read-only memory (EEPROM), flash memory, magnetic surface memory, optical disc, or a compact disk-read-only memory (CD-ROM); or it may be a device that includes one or any combination of the above-mentioned memories.

[0162] In some embodiments, executable instructions may take the form of a program, software, software module, script, or code, written in any form of programming language (including compiled or interpreted languages, or declarative or procedural languages), and may be deployed in any form, including as a standalone program or as a module, component, subroutine, or other unit suitable for use in a computing environment.

[0163] As an example, executable instructions may, but do not necessarily, correspond to files in a file system. They may be stored as part of a file that holds other programs or data, for example, in one or more scripts within a Hyper Text Markup Language (HTML) document, in a single file dedicated to the program in question, or in multiple co-located files (e.g., files storing one or more modules, subroutines, or code sections). As an example, executable instructions may be deployed to execute on a single computing device, or on multiple computing devices located in one location, or on multiple computing devices distributed across multiple locations and interconnected via a communication network.

[0164] It should be understood that the phrase "one embodiment" or "an embodiment" throughout the specification means that a specific feature, structure, or characteristic related to the embodiment is included in at least one embodiment of this application. Therefore, "in one embodiment" or "in an embodiment" appearing throughout the specification does not necessarily refer to the same embodiment. Furthermore, these specific features, structures, or characteristics can be combined in any suitable manner in one or more embodiments. It should be understood that in the various embodiments of this application, the sequence numbers of the above-described processes do not imply a sequential order of execution; the execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of this application. The sequence numbers of the above-described embodiments are merely descriptive and do not represent the superiority or inferiority of the embodiments.

[0165] It should be noted that, in this document, the terms "comprising," "including," or any other variations thereof are intended to cover a non-exclusive inclusion, such that a process, method, or apparatus that includes a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, or apparatus. Without further limitations, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or apparatus that includes that element. In the several embodiments provided in this application, it should be understood that the disclosed devices and methods can be implemented in other ways. The device embodiments described above are merely illustrative; for example, the division of units is only a logical functional division, and in actual implementation, there may be other division methods, such as: multiple units or components may be combined, or integrated into another system, or some features may be ignored or not performed.

[0166] The above are merely embodiments of this application and are not intended to limit the scope of protection of this application. Any modifications, equivalent substitutions, and improvements made within the spirit and scope of this application are included within the scope of protection of this application.

Claims

1. A network anomaly handling method, applied to network devices; characterized in that, The network anomaly handling method includes: Obtain network status information sent by the terminal; the network status information is collected by the terminal based on the network sensing module under network abnormal conditions; The network status information is analyzed to obtain network processing information; the network processing information includes at least one of terminal processing information, handover target, and resource configuration of the handover target. The network processing information is sent to the terminal so that the terminal executes the network processing information.

2. The network anomaly handling method according to claim 1, characterized in that, The network status information includes at least the terminal device identifier, the current serving cell information of the terminal when the protocol signaling access is abnormal, and the time of the abnormality. The analysis of the network state information to obtain network processing information includes: Based on the terminal device identifier, the current serving cell information, and the abnormal time point, the signaling in the signaling database is filtered to obtain the target signaling record; Based on the target signaling record, a timing interaction flow between the terminal and the network device is generated; The timing interaction process is verified based on the protocol state machine to obtain the terminal processing information.

3. The network anomaly handling method according to claim 2, characterized in that, The verification of the timing interaction process based on the protocol state machine to obtain the terminal processing information includes: Anomaly detection is performed on the timing interaction process based on the protocol state machine to obtain the detection result; the anomaly detection includes at least state transition anomaly detection and protocol error detection. Based on the detection results, the cause of the network anomaly and the network repair strategy are determined; wherein, the network repair strategy includes terminal-side repair strategy and network-side repair strategy; The network anomaly cause and the terminal-side repair strategy are determined as the terminal processing information.

4. The network anomaly handling method according to claim 1, characterized in that, The network status information includes at least the current serving cell information and neighboring cell information when the terminal connection is abnormal; The analysis of the network state information to obtain network processing information includes: Based on the current serving cell information and the neighboring cell information, a candidate cell set is determined, wherein the candidate cell set includes at least the terminal's current serving cell and at least one neighboring cell; Obtain the network service information of each cell in the candidate cell set; Based on the current serving cell information, the neighboring cell information, and the network service information, the current serving cell and each candidate cell are evaluated to obtain the network service score of each cell in the candidate cell set; Based on the network service score, the handover cell for the terminal is determined from the candidate cell set; the handover target includes at least the handover cell.

5. The network anomaly handling method according to claim 4, characterized in that, The current serving cell information includes at least one of the following indicators: signal strength, signal quality, signal-to-interference-plus-noise ratio (SINR), and block error rate; the neighboring cell information includes at least one of the following indicators: signal strength, signal quality, SINR, and block error rate; the network service information includes at least one of the following indicators: interface link status, resource availability, and historical handover success rate. The evaluation of the current serving cell and each candidate cell based on the current serving cell information, the neighboring cell information, and the network service information to obtain the network service score of each cell in the candidate cell set includes: The indicators in the current serving cell information, the neighboring cell information, and the network service information are normalized to obtain the normalized values ​​of each indicator for each cell. The network service score for each cell is determined based on the normalized values ​​of each indicator corresponding to each cell.

6. The network anomaly handling method according to claim 1, characterized in that, The network status information includes at least the signal quality indicators of multiple networks when multiple networks are experiencing anomalies; the network anomaly handling method further includes: Obtain the query request information sent by the terminal, wherein the query request information includes at least a list of query indicators for other networks besides the currently connected network among the plurality of networks; Correspondingly, the analysis of the network state information to obtain network processing information includes: Based on the list of query indicators, resource queries are performed on the other networks to obtain resource query results; the resource query results include at least the bandwidth resource utilization rate of each network. Based on the resource query results and the signal quality indicators of the multiple networks, a switching network and its resource configuration are determined in each network so that the terminal switches to the switching network; the switching target includes at least the switching network.

7. The network anomaly handling method according to any one of claims 1 to 6, characterized in that, The network anomaly handling method further includes: In response to the network status information, the current serving cell of the terminal is marked to obtain the number of abnormal markings of the current serving cell; In response to any cell among the multiple cells corresponding to the network device having more than a preset threshold number of abnormal markers within a preset time period, the abnormal situation of the cell is analyzed to obtain a resource adjustment strategy for the cell.

8. The network anomaly handling method according to any one of claims 1 to 6, characterized in that, The acquisition of network status information sent by the terminal includes: The network status information is obtained based on a preset interface; Correspondingly, sending the network processing information to the terminal includes: Based on a preset interface, the network processing information is sent to the terminal.

9. A network anomaly handling method, applied to a terminal; characterized in that, The network anomaly handling method includes: Anomaly detection is performed based on a network sensing module; The network status information collected by the network sensing module in the event of a network anomaly is obtained; Send the network status information to the network device; In response to network processing information sent by the network device, the network processing information is executed; the network processing information includes at least one of terminal processing information, handover target, and resource configuration of the handover target.

10. The network anomaly handling method according to claim 9, characterized in that, The terminal processing information includes at least the cause of the network anomaly and the terminal-side repair strategy; the execution of the network processing information in response to the network device includes: In response to the network anomaly being caused by a local configuration error, configuration parameters are adjusted based on the terminal-side repair strategy.

11. The network anomaly handling method according to claim 9, characterized in that, The handover target includes at least the cell to be handed over; the step of executing the network processing information in response to the network processing information sent by the network device includes: In response to receiving network processing information including the cell to be switched, a cell handover operation is performed.

12. The network anomaly handling method according to claim 9, characterized in that, The handover target includes at least the handover network, and the network processing information further includes the resource configuration of the handover network; the step of executing the network processing information in response to the network device includes: In response to receiving network processing information including the switched network and the resource configuration of the switched network, the resource configuration of the switched network is compared with the resource configuration of the currently connected network to obtain a comparison result; In response to the comparison result indicating that the resource configuration of the network to be switched is higher than the resource configuration of the currently connected network, a network switching operation is performed.

13. A network device, characterized in that, include: Memory is used to store executable instructions or computer programs. A processor, when executing computer-executable instructions or computer programs stored in memory, implements the network anomaly handling method as described in any one of claims 1 to 8.

14. A terminal, characterized in that, include: Memory is used to store executable instructions or computer programs. A processor, when executing computer-executable instructions or computer programs stored in memory, implements the network anomaly handling method as described in any one of claims 9 to 12.

15. A computer-readable storage medium, characterized in that, The readable storage medium stores a program or instructions that, when executed by a processor, implement the steps of the network anomaly handling method as described in any one of claims 1 to 12, or implement the steps of the network anomaly handling method as described in any one of claims 9 to 12.

Images