Communication anomaly recovery method, apparatus, medium, and device

Abstract

Embodiments of the present application provide a communication exception recovery method, device, medium and equipment, the method comprising: when detecting that a terminal device currently located in a second network is abnormal and initiating a first network switching request, listening to whether network switching failure prompt information fed back by an IP multimedia subsystem (IMS) is currently received; if the network switching failure prompt information is received, suspending the terminal device from sending an IMS registration request to the IP multimedia subsystem (IMS), and listening to whether network registration failure prompt information fed back by the IP multimedia subsystem (IMS) is currently received; if the network registration failure prompt information is received, resuming the terminal device to send the IMS registration request to the IP multimedia subsystem (IMS) to recover voice service based on the first network. The present application can avoid the IMS registration request interruption caused by the network registration failure prompt information sent by the IP multimedia subsystem (IMS) and the network switching failure prompt information.

Description

Technical Field

[0001] This application relates to the field of electronic communication technology, and more particularly to the field of communication anomaly recovery technology, and especially to a communication anomaly recovery method, apparatus, medium and equipment. Background Technology

[0002] Under normal circumstances, when a terminal device's call settings are set to Wi-Fi-preferred, after the phone registers with the LTE network and connects to Wi-Fi simultaneously, if the Wi-Fi signal is strong, calls will be made primarily via Wi-Fi. During the call, as the terminal device moves further away from the Wi-Fi access point and the Wi-Fi signal weakens, reaching the operator's required handover threshold (i.e., the Wi-Fi signal RSSI is less than a certain threshold, while the LTE signal is greater than a certain threshold), the terminal device will trigger a handover from VoWi-Fi to VoLTE. At this point, the terminal initiates a PDN Connectivity Request (Request type: Handover) to the network. Subsequently, the network activates the corresponding IMS signaling bearer ACTIVATE_DEFAULT_EPS_BEARER_CONTEXT_REQUEST (QCI:5) and voice bearer ACTIVATE_DEFAULT_EPS_BEARER_CONTEXT_REQUEST (QCI:1) to complete the network handover process.

[0003] However, in practical applications, when a terminal device initiates a network handover request to the IP Multimedia Subsystem (IMS), due to network anomalies, the IMS replies with a network handover failure message, causing the handover to fail and the call to drop. Subsequently, the terminal device will re-initiate an IMS registration request to the IMS. Simultaneously, after the network handover failure, the IMS will send a network registration failure message to the terminal device, interrupting the IMS registration process. Ultimately, due to the prolonged failure to successfully register with IMS, the terminal device cannot make calls. The root cause of this problem is that after the network handover failure, both the terminal device and the IMS trigger two processes simultaneously: Process 1: The terminal device initiates IMS registration with the IMS; Process 2: The IMS sends a network registration failure message to the terminal device to inform it of its IMS registration status. If the terminal device receives the network registration failure message after triggering the IMS registration process, the IMS registration process will be interrupted, resulting in a prolonged inability to make calls due to unsuccessful IMS registration. Summary of the Invention

[0004] This application provides a communication anomaly recovery method, apparatus, medium, and device. The communication anomaly recovery method provided by this application can monitor whether a network switching failure prompt message from the IP Multimedia Subsystem (IMS) is received when a terminal device initiates a request to switch to another network due to a network anomaly. Upon receiving the network switching failure message, the terminal device can suspend the IMS registration request, thereby avoiding the interruption of the IMS registration request caused by concurrent network registration failure prompt messages sent by the IP Multimedia Subsystem (IMS).

[0005] This application provides a communication anomaly recovery method, applied to a terminal device. The terminal device is connected to an IP Multimedia Subsystem (IMS) and performs voice services through a first network or a second network provided by the IMS. When both the first network and the second network exist simultaneously, the access priority of the second network is greater than that of the first network. The method includes:

[0006] When the terminal device detects an anomaly in the second network it is currently in and initiates a first network switching request, it listens to whether it receives a network switching failure message from the IP Multimedia Subsystem (IMS).

[0007] If the network switching failure message is received, the terminal device is suspended from sending the IMS registration request to the IP Multimedia Subsystem (IMS), and the system listens for whether a network registration failure message is received from the IP Multimedia Subsystem (IMS).

[0008] If the network registration failure message is received, the terminal device resumes sending an IMS registration request to the IP Multimedia Subsystem (IMS) to resume voice services based on the first network.

[0009] In the communication anomaly recovery method described in this application embodiment, the step of monitoring whether a network registration failure message has been received from the IP Multimedia Subsystem (IMS) includes:

[0010] A timer with a preset runtime is started, and during the runtime of the timer, it is monitored whether a network registration failure prompt message is received from the IP Multimedia Subsystem (IMS). The preset runtime is the waiting time for the terminal device from receiving the network switching failure prompt message to receiving the network registration failure prompt message under normal circumstances.

[0011] In the communication anomaly recovery method described in this application embodiment, after monitoring whether a network registration failure message has been received from the IP Multimedia Subsystem (IMS), the method further includes:

[0012] If the timer duration exceeds the preset duration and no network registration failure message is received, the terminal device resumes sending an IMS registration request to the IP Multimedia Subsystem (IMS) to resume voice services.

[0013] In the communication anomaly recovery method described in this application embodiment, after restoring the voice service based on the first network, the method further includes:

[0014] Real-time detection of the distance between the terminal device and the signal source of the second network, as well as the current signal strength of the second network on the terminal device;

[0015] Determine whether the distance between the terminal device and the signal source is less than a preset distance threshold. If so, determine whether the second network signal strength of the terminal device is greater than a preset signal strength threshold. If so, the terminal device initiates a second network switching request to switch the first network to the second network.

[0016] In the communication anomaly recovery method described in this application embodiment, after determining whether the distance between the terminal device and the signal source is less than a preset distance threshold, the method further includes:

[0017] If the distance between the terminal device and the signal source is not less than a preset distance threshold, then voice services will continue to be performed based on the first network.

[0018] In the communication anomaly recovery method described in this application embodiment, the first network is an LTE network and the second network is a WiFi network.

[0019] Accordingly, another aspect of this application embodiment also provides a communication anomaly recovery device, the communication anomaly recovery device comprising:

[0020] The first monitoring module is used to monitor whether a network switching failure message is received from the IP Multimedia Subsystem (IMS) when the terminal device detects an abnormality in the second network it is currently in and initiates a first network switching request.

[0021] The second monitoring module is used to pause the terminal device from sending an IMS registration request to the IP Multimedia Subsystem (IMS) if it receives the network switching failure prompt message, and to monitor whether it has received a network registration failure prompt message from the IP Multimedia Subsystem (IMS).

[0022] The request recovery module is used to, if it receives the network registration failure prompt information, restore the terminal device to send an IMS registration request to the IP Multimedia Subsystem (IMS) to restore voice services based on the first network.

[0023] In the communication anomaly recovery device described in this application embodiment, the second monitoring module is used to start a timer with a preset runtime, and during the runtime of the timer, monitor whether a network registration failure prompt message is received from the IP Multimedia Subsystem (IMS). The preset runtime is the waiting time for the terminal device from receiving the network switching failure prompt message to receiving the network registration failure prompt message under normal circumstances.

[0024] Accordingly, another aspect of this application embodiment also provides a storage medium storing a plurality of instructions adapted for loading by a processor to execute the communication anomaly recovery method described above.

[0025] Accordingly, another aspect of this application embodiment also provides a terminal device, including a processor and a memory, wherein the memory stores a plurality of instructions, and the processor loads the instructions to execute the communication anomaly recovery method as described above.

[0026] This application provides a communication anomaly recovery method, apparatus, medium, and device. The method is applied to a terminal device connected to an IP Multimedia Subsystem (IMS) and using a first or second network provided by the IMS for voice services. When both the first and second networks exist simultaneously, the access priority of the second network is higher than that of the first network. When an anomaly is detected in the second network and a first network switching request is initiated, the method monitors whether a network switching failure message is received from the IMS. If the network switching failure message is received, the method suspends the terminal device from sending IMS registration requests to the IMS and monitors whether a network registration failure message is received from the IMS. If the network registration failure message is received, the method resumes the terminal device from sending IMS registration requests to the IMS to restore voice services based on the first network. The communication anomaly recovery method provided in this application can avoid interrupting the IMS registration request by concurrently sending network registration failure messages with the network registration failure message sent by the IP Multimedia Subsystem (IMS) when the terminal device initiates a request to switch to another network due to network anomaly. Attached Figure Description

[0027] To more clearly illustrate the technical solutions in the embodiments of this application, the accompanying drawings used in the description of 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.

[0028] Figure 1 This is a flowchart illustrating the communication anomaly recovery method provided in an embodiment of this application.

[0029] Figure 2 This is a schematic diagram of the communication anomaly recovery device provided in an embodiment of this application.

[0030] Figure 3 This is another structural schematic diagram of the communication anomaly recovery device provided in the embodiments of this application.

[0031] Figure 4 This is a schematic diagram of the structure of a terminal device provided in an embodiment of this application. Detailed Implementation

[0032] The technical solutions of the embodiments of this application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only a part of the embodiments of this application, and not all of them. All other embodiments obtained by those skilled in the art based on the embodiments of this application without creative effort are within the protection scope of this application.

[0033] It should be noted that the following is a brief introduction to the background of this solution:

[0034] This solution mainly addresses the technical issue of "how to prevent the IMS registration request from being interrupted due to the concurrent execution of the IMS registration failure message sent by the IP Multimedia Subsystem (IMS) and ultimately affecting the operation of voice services". Under normal circumstances, when a terminal device's call settings are set to Wi-Fi-preferred, after the phone registers with the LTE network and connects to Wi-Fi, if the Wi-Fi signal is strong, calls will be made primarily via Wi-Fi. During the call, as the terminal device moves further away from the Wi-Fi access point and the Wi-Fi signal weakens, reaching the operator's required handover threshold (i.e., the Wi-Fi signal RSSI is below a certain threshold, while the LTE signal is above a certain threshold), the terminal device will trigger a handover from VoWi-Fi to VoLTE. At this point, the terminal initiates a PDN Connectivity Request (Request type: Handover) to the network. Subsequently, the network activates the corresponding IMS signaling bearer ACTIVATE_DEFAULT_EPS_BEARER_CONTEXT_REQUEST (QCI:5) and voice bearer ACTIVATE_DEFAULT_EPS_BEARER_CONTEXT_REQUEST (QCI:1) to complete the network handover process.

[0035] However, in practical applications, when a terminal device initiates a network handover request to the IP Multimedia Subsystem (IMS), due to network anomalies, the IMS replies with a network handover failure message, causing the handover to fail and the call to drop. Subsequently, the terminal device will re-initiate an IMS registration request to the IMS. Simultaneously, after the network handover failure, the IMS will send a network registration failure message to the terminal device, interrupting the IMS registration process. Ultimately, due to the prolonged failure to successfully register with IMS, the terminal device cannot make calls. The root cause of this problem is that after the network handover failure, both the terminal device and the IMS trigger two processes simultaneously: Process 1: The terminal device initiates IMS registration with the IMS; Process 2: The IMS sends a network registration failure message to the terminal device to inform it of its IMS registration status. If the terminal device receives the network registration failure message after triggering the IMS registration process, the IMS registration process will be interrupted, resulting in a prolonged inability to make calls due to unsuccessful IMS registration.

[0036] To address the aforementioned technical problems, this application provides a communication anomaly recovery method. Using the communication anomaly recovery method provided in this application, when a terminal device initiates a request to switch to another network due to a network anomaly, the method listens for whether a network switching failure message from the IP Multimedia Subsystem (IMS) is received. Upon receiving the network switching failure message, the method suspends the terminal device's IMS registration request, thereby preventing concurrent execution of the network registration failure message sent by the IMS and avoiding interruption of the IMS registration request.

[0037] Please see Figure 1 , Figure 1 This is a flowchart illustrating the communication anomaly recovery method provided in an embodiment of this application. The communication anomaly recovery method is applied to a terminal device. Optionally, the terminal device is a terminal or a server. Optionally, the server is an independent physical server, a server cluster or distributed system composed of multiple physical servers, or a cloud server providing basic cloud computing services such as cloud services, cloud databases, cloud computing, cloud functions, cloud storage, network services, cloud communication, middleware services, domain name services, security services, CDN (Content Delivery Network), and big data and artificial intelligence platforms. Optionally, the terminal is a smartphone, tablet computer, laptop computer, desktop computer, smart speaker, smartwatch, smart voice interaction device, smart home appliance, or in-vehicle terminal, but is not limited to these.

[0038] The following is an explanation of the terms that appear in this article:

[0039] IMS stands for IP Multimedia Subsystem. It is a network architecture that provides voice and multimedia services over an IP network. Designed by the 3GPP (3G Standardization Partnership) as part of its vision for future mobile networks after GSM, the initial version of IMS (3GPP Release 5) primarily outlined a method for implementing IP multimedia services based on GPRS. Building upon this version, 3GPP, 3GPP2, and TISPAN have made further updates to support other access networks besides GPRS (such as WLAN, CDMA2000, and fixed connections). The IP multimedia core network system consists of all core network functional entities capable of providing multimedia services, including a set of functional entities related to signaling and bearers. IP multimedia services are implemented using the PS domain and multimedia bearers, based on session control capabilities defined by the IETF.

[0040] In one embodiment, the method is applied to a terminal device that connects to an IP Multimedia Subsystem (IMS) and performs voice services through a first network or a second network provided by the IMS. When both the first network and the second network exist simultaneously, the access priority of the second network is greater than that of the first network. The method may include the following steps:

[0041] Step 101: When the terminal device detects an anomaly in the second network it is currently in and initiates a first network switching request, listen for whether a network switching failure message is received from the IP Multimedia Subsystem (IMS).

[0042] It should be noted that this solution is primarily applicable to scenarios where voice services are conducted via a connection to the IP Multimedia Subsystem (IMS) and based on a first or second network provided by the IMS. The first network specifically refers to an LTE network, and the second network specifically refers to a WiFi network.

[0043] Under normal circumstances, after a terminal device such as a mobile phone registers on the LTE network and connects to WiFi, if the WiFi signal is good, voice calls will be made primarily through WiFi. During the call, as the mobile phone moves further away from the WiFi network access point, the WiFi signal weakens. Once the handover threshold required by the operator is reached (i.e., the WiFi signal RSSI is less than a certain threshold, while the LTE signal is greater than a certain threshold), the terminal device will trigger a handover from the WiFi network (i.e., the second network) to the LTE network (i.e., the first network). At this point, the terminal device initiates a first network handover request to the IP Multimedia Subsystem (IMS). Subsequently, the IMS will activate the corresponding IMS signaling bearer and voice bearer to complete the network handover process.

[0044] However, in practical applications, when a terminal device initiates a network handover request to the IP Multimedia Subsystem (IMS), anomalies in the LTE network (i.e., the first network) may cause the IMS to fail, resulting in a dropped call. Subsequently, the terminal device will re-initiate an IMS registration request to the IMS. Simultaneously, after the network handover failure, the IMS will send a network registration failure message to the terminal device, interrupting the IMS registration process. Ultimately, due to the prolonged failure to successfully register with IMS, the terminal device cannot make calls. The root cause of this problem is that after the network handover failure, both the terminal device and the IMS simultaneously trigger two processes: Process 1: The terminal device initiates IMS registration with the IMS; Process 2: The IMS sends a network registration failure message to the terminal device to inform it of its IMS registration status. If the terminal device receives the network registration failure message after triggering the IMS registration process, the IMS registration process will be interrupted, resulting in a prolonged inability to make calls due to unsuccessful IMS registration.

[0045] Therefore, in order to solve the above problems, it is necessary to ensure that the IMS registration request sent by the terminal device and the network registration failure prompt message sent by the IP Multimedia Subsystem IMS are carried out concurrently to prevent the IMS registration request from being interrupted. The first step is to determine the network handover failure prompt message sent by the IP Multimedia Subsystem IMS in order to prepare for receiving the network registration failure prompt message sent by the IP Multimedia Subsystem IMS.

[0046] In this embodiment, when an anomaly is detected in the second network currently in which the terminal device is located and a first network switching request is initiated, a first listener set on the terminal device is used to listen for events to see whether a network switching failure prompt message is received from the IP Multimedia Subsystem (IMS).

[0047] Step 102: If the network switching failure message is received, the terminal device is paused from sending the IMS registration request to the IP Multimedia Subsystem (IMS), and the system listens for whether a network registration failure message is received from the IP Multimedia Subsystem (IMS).

[0048] In this embodiment, when the terminal device receives a network handover failure message from the IP Multimedia Subsystem (IMS), it suspends sending IMS registration requests to the IMS and listens for events related to whether it has received network registration failure messages from the IMS via a second listener set on the terminal device. This prevents the IMS registration request sent by the terminal device from being interrupted by the network registration failure message sent by the IMS.

[0049] In some embodiments, a timer with a preset runtime can be set on the terminal device and started when the terminal device pauses sending IMS registration requests to the IP Multimedia Subsystem (IMS). During the timer's runtime, it listens for network registration failure messages from the IMS. The preset runtime is the waiting time, for example, 1 second, between receiving the network handover failure message and receiving the network registration failure message under normal circumstances. By setting the timer, the IMS registration request can be paused within a reasonable timeframe, ensuring that it does not occur concurrently with network registration failure messages, and preventing disruption to voice services due to prolonged pauses in IMS registration request transmission.

[0050] It should be noted that if the timer runs for longer than the preset duration and no network registration failure message is received, the terminal device will send an IMS registration request to the IP Multimedia Subsystem (IMS) to restore voice services.

[0051] Step 103: If the network registration failure message is received, the terminal device resumes sending an IMS registration request to the IP Multimedia Subsystem (IMS) to resume voice services based on the first network.

[0052] In the case where IMS registration request transmission is suspended, if the terminal device receives a network registration failure message from the IP Multimedia Subsystem (IMS), it indicates that the network registration failure message will not occur after the IMS registration request is sent. At this time, the terminal device can resume sending the IMS registration request to the IP Multimedia Subsystem (IMS) to restore voice services based on the first network.

[0053] In some embodiments, after resuming voice service based on the first network, the method further detects in real time the distance between the terminal device and the signal source of the second network, as well as the current signal strength of the second network on the terminal device; determines whether the distance between the terminal device and the signal source is less than a preset distance threshold; if so, determines whether the signal strength of the second network on the terminal device is greater than a preset signal strength threshold; if so, the terminal device initiates a second network switching request to switch from the first network to the second network, enabling the terminal device to prioritize voice service on the WiFi network. If the distance between the terminal device and the signal source is not less than the preset distance threshold, voice service based on the first network continues.

[0054] All of the above-mentioned optional technical solutions can be combined in any way to form the optional embodiments of this application, and will not be described in detail here.

[0055] In practice, this application is not limited by the execution order of the described steps. Without causing conflicts, some steps may be performed in other orders or simultaneously.

[0056] As can be seen from the above, the communication anomaly recovery method provided in this application, when detecting an anomaly in the second network currently in which the terminal device is located and initiating a first network switching request, listens for whether a network switching failure prompt message is received from the IP Multimedia Subsystem (IMS). If the network switching failure prompt message is received, the terminal device suspends sending an IMS registration request to the IMS and listens for whether a network registration failure prompt message is received from the IMS. If the network registration failure prompt message is received, the terminal device resumes sending an IMS registration request to the IMS, thereby restoring voice services based on the first network. By utilizing the communication anomaly recovery method provided in this application, when detecting a request from the terminal device to switch to another network due to a network anomaly, listening for whether a network switching failure prompt message is received from the IMS, and suspending the terminal device's IMS registration request upon receiving the network switching failure message, it is possible to avoid concurrent transmission of the network registration failure prompt message sent by the IMS, thus preventing the IMS registration request from being interrupted.

[0057] This application also provides a communication anomaly recovery device, which can be integrated into a terminal device.

[0058] Please see Figure 2 , Figure 2 This is a schematic diagram of the communication anomaly recovery device provided in an embodiment of this application. The communication anomaly recovery device 30 may include:

[0059] The first monitoring module 31 is used to monitor whether it receives network switching failure prompt information from the IP Multimedia Subsystem (IMS) when it detects that the second network where the terminal device is currently located is abnormal and initiates a first network switching request.

[0060] The second monitoring module 32 is used to pause the terminal device from sending an IMS registration request to the IP Multimedia Subsystem (IMS) if it receives the network switching failure prompt information, and to monitor whether it has received a network registration failure prompt information from the IP Multimedia Subsystem (IMS).

[0061] The request recovery module 33 is used to, if it receives the network registration failure prompt information, restore the terminal device to send an IMS registration request to the IP Multimedia Subsystem (IMS) to restore voice services based on the first network.

[0062] In some embodiments, the second monitoring module 32 is used to start a timer with a preset runtime, and during the runtime of the timer, monitor whether a network registration failure prompt message is received from the IP Multimedia Subsystem (IMS). The preset runtime is the waiting time for the terminal device from receiving the network switching failure prompt message to receiving the network registration failure prompt message under normal circumstances.

[0063] In some embodiments, the device further includes a first determination module, configured to, if the timer runtime exceeds the preset runtime and no network registration failure message is received, restore the terminal device to send an IMS registration request to the IP Multimedia Subsystem (IMS) to restore voice services.

[0064] In some embodiments, the device further includes a second judgment module, configured to detect in real time the distance between the terminal device and the signal source of the second network, and the current signal strength of the second network of the terminal device; determine whether the distance between the terminal device and the signal source is less than a preset distance threshold; if so, determine whether the signal strength of the second network of the terminal device is greater than a preset signal strength threshold; if so, the terminal device initiates a second network switching request to switch the first network to the second network.

[0065] In some embodiments, the device further includes a third determination module, configured to continue performing voice services based on the first network if the distance between the terminal device and the signal source is not less than a preset distance threshold.

[0066] In some embodiments, the first network is an LTE network and the second network is a WiFi network.

[0067] In practice, the above modules can be implemented as independent entities or combined in any way to be implemented as the same or several entities.

[0068] As can be seen from the above, the communication anomaly recovery device 30 provided in this application embodiment includes a first monitoring module 31 used to monitor whether a network switching failure prompt message is received from the IP Multimedia Subsystem (IMS) when the terminal device detects an anomaly in the second network it is currently in and initiates a first network switching request; a second monitoring module 32 used to suspend the terminal device from sending an IMS registration request to the IMS if the network switching failure prompt message is received, and to monitor whether a network registration failure prompt message is received from the IMS; and a request recovery module 33 used to resume the terminal device from sending an IMS registration request to the IMS if the network registration failure prompt message is received, so as to restore voice services based on the first network.

[0069] Please see Figure 3 , Figure 3 This is another schematic diagram of the communication anomaly recovery device provided in this application embodiment. The communication anomaly recovery device 30 includes a memory 120, one or more processors 180, and one or more application programs, wherein the one or more application programs are stored in the memory 120 and configured to be executed by the processors 180; the processors 180 may include a first monitoring module 31, a second monitoring module 32, and a request recovery module 33. For example, the structure and connection relationship of the above components can be as follows:

[0070] Memory 120 can be used to store applications and data. The applications stored in memory 120 contain executable code. Applications can be composed of various functional modules. Processor 180 executes various functional applications and data processing by running the applications stored in memory 120. Furthermore, memory 120 may include high-speed random access memory and may also include non-volatile memory, such as at least one disk storage device, flash memory device, or other volatile solid-state storage device. Accordingly, memory 120 may also include a memory controller to provide processor 180 with access to memory 120.

[0071] The processor 180 is the control center of the device, connecting various parts of the terminal through various interfaces and lines. It performs various functions and processes data by running or executing applications stored in the memory 120 and calling data stored in the memory 120, thereby providing overall monitoring of the device. Optionally, the processor 180 may include one or more processing cores; preferably, the processor 180 may integrate an application processor and a modem processor, wherein the application processor mainly handles the operating system, user interface, and applications.

[0072] Specifically, in this embodiment, the processor 180 loads the executable code corresponding to the processes of one or more applications into the memory 120 according to the following instructions, and the processor 180 runs the applications stored in the memory 120 to achieve various functions:

[0073] The first listening instruction is used to listen for whether a network switching failure prompt message is received from the IP Multimedia Subsystem (IMS) when the terminal device detects an abnormality in the second network it is currently in and initiates a first network switching request.

[0074] The second monitoring instruction is used to pause the terminal device from sending an IMS registration request to the IP Multimedia Subsystem (IMS) if the network switching failure message is received, and to monitor whether a network registration failure message is currently received from the IP Multimedia Subsystem (IMS).

[0075] The request recovery instruction is used to, if the network registration failure prompt message is received, restore the terminal device to send an IMS registration request to the IP Multimedia Subsystem (IMS) to restore voice services based on the first network.

[0076] In some embodiments, the second monitoring instruction is used to start a timer with a preset runtime, and during the runtime of the timer, monitor whether a network registration failure message is received from the IP Multimedia Subsystem (IMS). The preset runtime is the waiting time for the terminal device from receiving the network switching failure message to receiving the network registration failure message under normal circumstances.

[0077] In some embodiments, the program further includes a first judgment instruction, configured to, if the timer runtime exceeds the preset runtime and no network registration failure message is received, restore the terminal device to send an IMS registration request to the IP Multimedia Subsystem (IMS) to restore voice services.

[0078] In some embodiments, the program further includes a second judgment instruction, used to detect in real time the distance between the terminal device and the signal source of the second network, and the current signal strength of the second network of the terminal device; to determine whether the distance between the terminal device and the signal source is less than a preset distance threshold; if so, to determine whether the signal strength of the second network of the terminal device is greater than a preset signal strength threshold; if so, the terminal device initiates a second network switching request to switch the first network to the second network.

[0079] In some embodiments, the program further includes a third judgment instruction, used to continue voice service based on the first network if the distance between the terminal device and the signal source is not less than a preset distance threshold.

[0080] In some embodiments, the first network is an LTE network and the second network is a WiFi network.

[0081] This application also provides a terminal device. The terminal device may be a server, smartphone, computer, tablet computer, or other similar device.

[0082] Please see Figure 4 , Figure 4 A schematic diagram of a terminal device provided in an embodiment of this application is shown. This terminal device can be used to implement the communication anomaly recovery method provided in the above embodiments. The terminal device 1200 can be a television set, a smartphone, or a tablet computer.

[0083] like Figure 4 As shown, the terminal device 1200 may include an RF (Radio Frequency) circuit 110, a memory 120 including one or more (only one is shown in the figure) computer-readable storage media, an input unit 130, a display unit 140, a sensor 150, an audio circuit 160, a transmission module 170, a processor 180 including one or more (only one is shown in the figure) processing cores, and a power supply 190, etc. Those skilled in the art will understand that... Figure 4 The structure of the terminal device 1200 shown does not constitute a limitation on the terminal device 1200, and may include more or fewer components than shown, or combine certain components, or have different component arrangements. Wherein:

[0084] RF circuit 110 is used to receive and transmit electromagnetic waves, realizing the mutual conversion between electromagnetic waves and electrical signals, thereby enabling communication with communication networks or other devices. RF circuit 110 may include various existing circuit elements used to perform these functions, such as antennas, radio frequency transceivers, digital signal processors, encryption / decryption chips, Subscriber Identity Module (SIM) cards, memory, etc. RF circuit 110 can communicate with various networks such as the Internet, corporate intranets, and wireless networks, or communicate with other devices via wireless networks.

[0085] The memory 120 can be used to store software programs and modules, such as the program instructions / modules corresponding to the communication anomaly recovery method in the above embodiment. The processor 180 executes various functional applications and data processing by running the software programs and modules stored in the memory 120. It can automatically select a vibration alert mode to recover from communication anomalies based on the current scenario of the terminal device, ensuring that scenarios such as meetings are not disturbed while still allowing users to sense incoming calls, thus improving the intelligence of the terminal device. The memory 120 may include high-speed random access memory and non-volatile memory, such as one or more magnetic storage devices, flash memory, or other non-volatile solid-state memories. In some instances, the memory 120 may further include memory remotely located relative to the processor 180, which can be connected to the terminal device 1200 via a network. Examples of such networks include, but are not limited to, the Internet, corporate intranets, local area networks, mobile communication networks, and combinations thereof.

[0086] Input unit 130 can be used to receive input numerical or character information, and to generate keyboard, mouse, joystick, optical, or trackball signal inputs related to user settings and function control. Specifically, input unit 130 may include touch-sensitive surface 131 and other input devices 132. Touch-sensitive surface 131, also known as a touch display screen or touchpad, can collect user touch operations on or near it (such as user operations using fingers, styluses, or any suitable object or accessory on or near touch-sensitive surface 131), and drive corresponding connection devices according to a pre-set program. Optionally, touch-sensitive surface 131 may include two parts: a touch detection device and a touch controller. The touch detection device detects the user's touch position and the signal generated by the touch operation, and transmits the signal to the touch controller; the touch controller receives touch information from the touch detection device, converts it into touch point coordinates, sends it to processor 180, and can receive and execute commands from processor 180. In addition, the touch-sensitive surface 131 can be implemented using various types such as resistive, capacitive, infrared, and surface acoustic wave. Besides the touch-sensitive surface 131, the input unit 130 may also include other input devices 132. Specifically, other input devices 132 may include, but are not limited to, one or more of the following: a physical keyboard, function keys (such as volume control buttons, power buttons, etc.), a trackball, a mouse, and a joystick.

[0087] Display unit 140 can be used to display information input by the user or information provided to the user, as well as various graphical user interfaces of terminal device 1200. These graphical user interfaces can be composed of graphics, text, icons, video, and any combination thereof. Display unit 140 may include display panel 141, optionally configured as LCD (Liquid Crystal Display), OLED (Organic Light-Emitting Diode), etc. Further, touch-sensitive surface 131 may cover display panel 141. When touch-sensitive surface 131 detects a touch operation on or near it, it transmits the information to processor 180 to determine the type of touch event. Subsequently, processor 180 provides corresponding visual output on display panel 141 according to the type of touch event. Although in Figure 4 In this embodiment, the touch-sensitive surface 131 and the display panel 141 are implemented as two separate components to realize input and output functions. However, in some embodiments, the touch-sensitive surface 131 and the display panel 141 can be integrated to realize input and output functions.

[0088] The terminal device 1200 may also include at least one sensor 150, such as a light sensor, a motion sensor, and other sensors. Specifically, the light sensor may include an ambient light sensor and a proximity sensor. The ambient light sensor can adjust the brightness of the display panel 141 according to the ambient light level, and the proximity sensor can turn off the display panel 141 and / or backlight when the terminal device 1200 is moved to the ear. As a type of motion sensor, a gravity acceleration sensor can detect the magnitude of acceleration in various directions (generally three axes). When stationary, it can detect the magnitude and direction of gravity and can be used for applications that recognize the phone's posture (such as landscape / portrait switching, related games, magnetometer posture calibration), vibration recognition-related functions (such as pedometer, tapping), etc. Other sensors that the terminal device 1200 may also be configured with, such as a gyroscope, barometer, hygrometer, thermometer, and infrared sensor, will not be described in detail here.

[0089] Audio circuitry 160, speaker 161, and microphone 162 provide an audio interface between the user and terminal device 1200. Audio circuitry 160 converts received audio data into electrical signals, which are then transmitted to speaker 161, where they are converted into sound signals for output. Conversely, microphone 162 converts collected sound signals into electrical signals, which are received by audio circuitry 160, converted back into audio data, and then processed by processor 180 before being transmitted via RF circuitry 110 to, for example, another terminal, or output to memory 120 for further processing. Audio circuitry 160 may also include an earphone jack to facilitate communication between peripheral headphones and terminal device 1200.

[0090] Terminal device 1200, through transmission module 170 (e.g., Wi-Fi module), can help users send and receive emails, browse web pages, and access streaming media, providing users with wireless broadband internet access. Although Figure 4 The transmission module 170 is shown, but it is understood that it is not a necessary component of the terminal device 1200 and can be omitted as needed without changing the nature of the invention.

[0091] The processor 180 is the control center of the terminal device 1200. It connects to various parts of the mobile phone via various interfaces and lines. By running or executing software programs and / or modules stored in the memory 120, and by calling data stored in the memory 120, it performs various functions of the terminal device 1200 and processes data, thereby providing overall monitoring of the mobile phone. Optionally, the processor 180 may include one or more processing cores; in some embodiments, the processor 180 may integrate an application processor and a modem processor, wherein the application processor mainly handles the operating system, user interface, and applications, and the modem processor mainly handles wireless communication. It is understood that the modem processor may also not be integrated into the processor 180.

[0092] The terminal device 1200 also includes a power supply 190 that supplies power to the various components. In some embodiments, the power supply can be logically connected to the processor 180 through a power management system, thereby enabling functions such as discharge management and power consumption management through the power management system. The power supply 190 may also include one or more DC or AC power supplies, recharging systems, power fault detection circuits, power converters or inverters, power status indicators, and other arbitrary components.

[0093] Although not shown, the terminal device 1200 may also include a camera (such as a front-facing camera and a rear-facing camera), a Bluetooth module, etc., which will not be described in detail here. Specifically, in this embodiment, the display unit 140 of the terminal device 1200 is a touch screen display, and the terminal device 1200 also includes a memory 120 and one or more programs, one or more of which are stored in the memory 120 and configured to be executed by one or more processors 180. One or more programs contain instructions for performing the following operations:

[0094] The first listening instruction is used to listen for whether a network switching failure prompt message is received from the IP Multimedia Subsystem (IMS) when the terminal device detects an abnormality in the second network it is currently in and initiates a first network switching request.

[0095] The second monitoring instruction is used to pause the terminal device from sending an IMS registration request to the IP Multimedia Subsystem (IMS) if the network switching failure message is received, and to monitor whether a network registration failure message is currently received from the IP Multimedia Subsystem (IMS).

[0096] A request for recovery instruction is used to, if the network registration failure message is received, restore the terminal device to send an IMS registration request to the IP Multimedia Subsystem (IMS) to restore voice services based on the first network.

[0097] In some embodiments, the second monitoring instruction is used to start a timer with a preset runtime, and during the runtime of the timer, monitor whether a network registration failure message is received from the IP Multimedia Subsystem (IMS). The preset runtime is the waiting time for the terminal device from receiving the network switching failure message to receiving the network registration failure message under normal circumstances.

[0098] In some embodiments, the program further includes a first judgment instruction, configured to, if the timer runtime exceeds the preset runtime and no network registration failure message is received, restore the terminal device to send an IMS registration request to the IP Multimedia Subsystem (IMS) to restore voice services.

[0099] In some embodiments, the program further includes a second judgment instruction, used to detect in real time the distance between the terminal device and the signal source of the second network, and the current signal strength of the second network of the terminal device; to determine whether the distance between the terminal device and the signal source is less than a preset distance threshold; if so, to determine whether the signal strength of the second network of the terminal device is greater than a preset signal strength threshold; if so, the terminal device initiates a second network switching request to switch the first network to the second network.

[0100] In some embodiments, the program further includes a third judgment instruction, used to continue voice service based on the first network if the distance between the terminal device and the signal source is not less than a preset distance threshold.

[0101] In some embodiments, the first network is an LTE network and the second network is a WiFi network.

[0102] This application also provides a terminal device. The terminal device may be a smartphone, computer, or other similar device.

[0103] As can be seen from the above, this application embodiment provides a terminal device 1200, which performs the following steps:

[0104] When the terminal device detects an anomaly in the second network it is currently in and initiates a first network switching request, it listens to whether it receives a network switching failure message from the IP Multimedia Subsystem (IMS).

[0105] If the network switching failure message is received, the terminal device is suspended from sending the IMS registration request to the IP Multimedia Subsystem (IMS), and the system listens for whether a network registration failure message is received from the IP Multimedia Subsystem (IMS).

[0106] If the network registration failure message is received, the terminal device resumes sending an IMS registration request to the IP Multimedia Subsystem (IMS) to resume voice services based on the first network.

[0107] This application also provides a storage medium storing a computer program. When the computer program is run on a computer, the computer executes the communication anomaly recovery method described in any of the above embodiments.

[0108] It should be noted that, for the communication anomaly recovery method described in this application, those skilled in the art will understand that all or part of the process of the communication anomaly recovery method described in the embodiments of this application can be implemented by a computer program controlling the relevant hardware. The computer program can be stored in a computer-readable storage medium, such as in the memory of a terminal device, and executed by at least one processor within the terminal device. During execution, it can include the process of the embodiments of the communication anomaly recovery method described. The storage medium can be a magnetic disk, optical disk, read-only memory (ROM), random access memory (RAM), etc.

[0109] For the communication anomaly recovery device described in this application embodiment, its functional modules can be integrated into a single processing chip, or each module can exist physically separately, or two or more modules can be integrated into one module. The integrated module can be implemented in hardware or as a software functional module. If the integrated module 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, such as a read-only memory, a disk, or an optical disk.

[0110] The communication anomaly recovery method, apparatus, medium, and device provided in the embodiments of this application have been described in detail above. Specific examples have been used to illustrate the principles and implementation methods of this application. The descriptions of the embodiments above are only for the purpose of helping to understand the methods and core ideas of this application; at the same time, those skilled in the art will recognize that, based on the ideas of this application, there will be changes in the specific implementation methods and application scope. Therefore, the content of this specification should not be construed as a limitation of this application.

Claims

1. A communication anomaly recovery method, applied to a terminal device, wherein the terminal device is connected to an IP Multimedia Subsystem (IMS) and performs voice services through a first network or a second network provided by the IMS, wherein when both the first network and the second network exist simultaneously, the access priority of the second network is greater than the access priority of the first network, characterized in that... include: When the terminal device detects an anomaly in the second network it is currently in and initiates a first network switching request, it listens to whether it receives a network switching failure message from the IP Multimedia Subsystem (IMS). If the network switching failure message is received, the terminal device will pause sending the IMS registration request to the IP Multimedia Subsystem (IMS) and monitor whether the network registration failure message is received from the IP Multimedia Subsystem (IMS) to avoid the IMS registration request sent by the terminal device and the network registration failure message sent by the IP Multimedia Subsystem (IMS) occurring concurrently. If the network registration failure message is received, the terminal device resumes sending an IMS registration request to the IP Multimedia Subsystem (IMS) to resume voice services based on the first network.

2. The communication anomaly recovery method as described in claim 1, characterized in that, The monitoring of whether a network registration failure message has been received from the IP Multimedia Subsystem (IMS) includes: A timer with a preset runtime is started, and during the runtime of the timer, it is monitored whether a network registration failure prompt message is received from the IP Multimedia Subsystem (IMS). The preset runtime is the waiting time for the terminal device from receiving the network switching failure prompt message to receiving the network registration failure prompt message under normal circumstances.

3. The communication anomaly recovery method as described in claim 2, characterized in that, After monitoring whether a network registration failure message has been received from the IP Multimedia Subsystem (IMS), the method further includes: If the timer duration exceeds the preset duration and no network registration failure message is received, the terminal device resumes sending an IMS registration request to the IP Multimedia Subsystem (IMS) to resume voice services.

4. The communication anomaly recovery method as described in claim 1, characterized in that, After restoring voice services based on the first network, the method further includes: Real-time detection of the distance between the terminal device and the signal source of the second network, as well as the current signal strength of the second network on the terminal device; Determine whether the distance between the terminal device and the signal source is less than a preset distance threshold. If so, determine whether the second network signal strength of the terminal device is greater than a preset signal strength threshold. If so, the terminal device initiates a second network switching request to switch the first network to the second network.

5. The communication anomaly recovery method as described in claim 4, characterized in that, After determining whether the distance between the terminal device and the signal source is less than a preset distance threshold, the method further includes: If the distance between the terminal device and the signal source is not less than a preset distance threshold, then voice services will continue to be performed based on the first network.

6. The communication anomaly recovery method as described in claim 1, characterized in that, The first network is an LTE network, and the second network is a WiFi network.

7. A communication anomaly recovery device, characterized in that, include: The first monitoring module is used to monitor whether a network switching failure message is received from the IP Multimedia Subsystem (IMS) when the terminal device detects an abnormality in the second network it is currently in and initiates a first network switching request. The second monitoring module is used to pause the terminal device from sending an IMS registration request to the IP Multimedia Subsystem (IMS) if it receives the network switching failure prompt information, and to monitor whether it receives a network registration failure prompt information from the IP Multimedia Subsystem (IMS) to avoid the IMS registration request sent by the terminal device and the network registration failure prompt information sent by the IP Multimedia Subsystem (IMS) being processed concurrently. The request recovery module is used to, if it receives the network registration failure prompt information, restore the terminal device to send an IMS registration request to the IP Multimedia Subsystem (IMS) to restore voice services based on the first network.

8. The communication anomaly recovery device as described in claim 7, characterized in that, The second monitoring module is used to start a timer with a preset runtime, and during the runtime of the timer, it monitors whether a network registration failure prompt message is received from the IP Multimedia Subsystem (IMS). The preset runtime is the waiting time for the terminal device from receiving the network switching failure prompt message to receiving the network registration failure prompt message under normal circumstances.

9. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores a plurality of instructions adapted for loading by a processor to execute the communication anomaly recovery method according to any one of claims 1-6.

10. A terminal device, characterized in that, The method includes a processor and a memory, the memory storing multiple instructions, and the processor loading the instructions to execute the communication anomaly recovery method according to any one of claims 1-6.

Images