METHOD AND APPARATUS FOR PROCESSING CALL INITIATION ANOMALY

Abstract

A method and apparatus for processing a call initiation anomaly are disclosed in this application. The method includes: sending a first call request message through a first PS domain; performing a first operation in a case that a first call initiation anomaly occurs, where the first operation includes any one of the following: sending the first call request message through a second PS domain; disabling a VoLTE function, and sending the first call request message through a CS domain; registering in the second PS domain again, and sending the first call request message through the second PS domain; and sending a second call request message to a first account through a target application program, where the first account corresponds to an account indicated by the first call request message.

Claims

1. A method for processing a call initiation anomaly, comprising: sending a first call request message through a first packet switch PS domain; and performing a first operation in a case that a first call initiation anomaly occurs, wherein the first operation comprises any one of the following: sending the first call request message through a second PS domain; disabling a voice over long term evolution VoLTE function, and sending the first call request message through a circuit switch CS domain; registering in the second PS domain again, and sending the first call request message through the second PS domain; and sending a second call request message to a first account through a target application program, wherein the first account corresponds to an account indicated by the first call request message.

2. The method according to claim 1, wherein the first PS domain and the second PS domain are different; and before the performing a first operation, the method further comprises: falling back to a second access network device from a first access network device, wherein the first access network device is an access network device corresponding to the first PS domain, and the second access network device is an access network device corresponding to the second PS domain.

3. The method according to claim 1, wherein after the sending a first call request message through a first PS domain, before the first call initiation anomaly occurs, the method further comprises: in a case that a second call initiation anomaly occurs, falling back to a second core network from a first core network device, and sending the first call request message through the second PS domain, wherein the first core network device is a core network device corresponding to the first PS domain, and the second core network device is a core network device corresponding to the second PS domain.

4. The method according to claim 1, wherein the first operation is to send the first call request message through the second PS domain; and after the performing a first operation, the method further comprises: performing a second operation in a case that a third call initiation anomaly occurs, wherein the second operation comprises any one of the following: disabling the VoLTE function, and sending the first call request message through the CS domain; registering in the second PS domain again, and sending the first call request message through the second PS domain; and sending the second call request message to the first account through the target application program.

5. The method according to claim 4, wherein the second operation is to disable the VoLTE function and send the first call request message through the CS domain; and after the performing a second operation, the method further comprises: performing a third operation in a case that a fourth call initiation anomaly occurs, wherein the third operation comprises any one of the following: registering in the second PS domain again, and sending the first call request message through the second PS domain; and sending the second call request message to the first account through the target application program.

6. The method according to claim 1, wherein the sending a second call request message to a first account through a target application program comprises: determining the first account from the target application program according to the first call request message; and sending the second call request message to the first account through the target application program.

7. An electronic device, comprising a processor, a memory, and a program or instruction stored on the memory and runnable on the processor, wherein the program or instruction, when executed by the processor, implements the following steps: sending a first call request message through a first packet switch PS domain; and performing a first operation in a case that a first call initiation anomaly occurs, wherein the first operation comprises any one of the following: sending the first call request message through a second PS domain; disabling a voice over long term evolution VoLTE function, and sending the first call request message through a circuit switch CS domain; registering in the second PS domain again, and sending the first call request message through the second PS domain; and sending a second call request message to a first account through a target application program, wherein the first account corresponds to an account indicated by the first call request message.

8. The electronic device according to claim 7, wherein the first PS domain and the second PS domain are different; and before the performing a first operation, the program or instruction, when executed by the processor, further implements: falling back to a second access network device from a first access network device, wherein the first access network device is an access network device corresponding to the first PS domain, and the second access network device is an access network device corresponding to the second PS domain.

9. The electronic device according to claim 7, wherein after the sending a first call request message through a first PS domain, before the first call initiation anomaly occurs, the program or instruction, when executed by the processor, further implements: in a case that a second call initiation anomaly occurs, falling back to a second core network from a first core network device, and sending the first call request message through the second PS domain, wherein the first core network device is a core network device corresponding to the first PS domain, and the second core network device is a core network device corresponding to the second PS domain.

10. The electronic device according to claim 7, wherein the first operation is to send the first call request message through the second PS domain; and after the performing a first operation, the program or instruction, when executed by the processor, further implements: performing a second operation in a case that a third call initiation anomaly occurs, wherein the second operation comprises any one of the following: disabling the VoLTE function, and sending the first call request message through the CS domain; registering in the second PS domain again, and sending the first call request message through the second PS domain; and sending the second call request message to the first account through the target application program.

11. The electronic device according to claim 10, wherein the second operation is to disable the VoLTE function and send the first call request message through the CS domain; and after the performing a second operation, the program or instruction, when executed by the processor, further implements: performing a third operation in a case that a fourth call initiation anomaly occurs, wherein the third operation comprises any one of the following: registering in the second PS domain again, and sending the first call request message through the second PS domain; and sending the second call request message to the first account through the target application program.

12. The electronic device according to claim 7, wherein the program or instruction, when executed by the processor, further implements: determining the first account from the target application program according to the first call request message; and sending the second call request message to the first account through the target application program.

13. A non-transitory readable storage medium, storing a program or instruction, wherein the program or instruction, when executed by a processor, implements the following steps: sending a first call request message through a first packet switch PS domain; and performing a first operation in a case that a first call initiation anomaly occurs, wherein the first operation comprises any one of the following: sending the first call request message through a second PS domain; disabling a voice over long term evolution VoLTE function, and sending the first call request message through a circuit switch CS domain; registering in the second PS domain again, and sending the first call request message through the second PS domain; and sending a second call request message to a first account through a target application program, wherein the first account corresponds to an account indicated by the first call request message.

14. The non-transitory readable storage medium according to claim 13, wherein the first PS domain and the second PS domain are different; and before the performing a first operation, the program or instruction, when executed by a processor, further implements: falling back to a second access network device from a first access network device, wherein the first access network device is an access network device corresponding to the first PS domain, and the second access network device is an access network device corresponding to the second PS domain.

15. The non-transitory readable storage medium according to claim 13, wherein after the sending a first call request message through a first PS domain, before the first call initiation anomaly occurs, the program or instruction, when executed by a processor, further implements: in a case that a second call initiation anomaly occurs, falling back to a second core network from a first core network device, and sending the first call request message through the second PS domain, wherein the first core network device is a core network device corresponding to the first PS domain, and the second core network device is a core network device corresponding to the second PS domain.

16. The non-transitory readable storage medium according to claim 13, wherein the first operation is to send the first call request message through the second PS domain; and after the performing a first operation, the program or instruction, when executed by a processor, further implements: performing a second operation in a case that a third call initiation anomaly occurs, wherein the second operation comprises any one of the following: disabling the VoLTE function, and sending the first call request message through the CS domain; registering in the second PS domain again, and sending the first call request message through the second PS domain; and sending the second call request message to the first account through the target application program.

17. The non-transitory readable storage medium according to claim 16, wherein the second operation is to disable the VoLTE function and send the first call request message through the CS domain; and after the performing a second operation, the program or instruction, when executed by a processor, further implements: performing a third operation in a case that a fourth call initiation anomaly occurs, wherein the third operation comprises any one of the following: registering in the second PS domain again, and sending the first call request message through the second PS domain; and sending the second call request message to the first account through the target application program.

18. The non-transitory readable storage medium according to claim 13, wherein the program or instruction, when executed by a processor, further implements: determining the first account from the target application program according to the first call request message; and sending the second call request message to the first account through the target application program.

Description

BRIEF DESCRIPTION OF THE DRAWINGS

[0011] FIG. 1 is a first schematic flowchart of a method for processing a call initiation anomaly according to an embodiment of this application;

[0012] FIG. 2 is a second schematic flowchart of a method for processing a call initiation anomaly according to an embodiment of this application;

[0013] FIG. 3 is a third schematic flowchart of a method for processing a call initiation anomaly according to an embodiment of this application;

[0014] FIG. 4 is a fourth schematic flowchart of a method for processing a call initiation anomaly according to an embodiment of this application;

[0015] FIG. 5 is a schematic structural diagram of an apparatus for processing a call initiation anomaly according to an embodiment of this application;

[0016] FIG. 6 is a schematic structural diagram of an electronic device according to an embodiment of this application; and

[0017] FIG. 7 is a schematic diagram of a hardware structure of an electronic device according to an embodiment of this application.

DETAILED DESCRIPTION

[0018] The following clearly describes the technical solutions in embodiments of this application with reference to the accompanying drawings in the embodiments of this application. Apparently, the described embodiments are some of the embodiments of this application rather than all of the embodiments. All other embodiments derived by a person of ordinary skill in the art based on the embodiments of this application without creative efforts shall fall within the protection scope of this application.

[0019] In the specification and claims of this application, the terms “first”, “second”, and the like are used to distinguish similar objects, but are not used to describe a specific sequence or order. It may be understood that the data used in such a way is interchangeable in proper circumstances, so that the embodiments of this application described herein can be implemented in other sequences than the sequence illustrated or described herein, and the objects distinguished through “first”, “second”, and the like are generally of a same type and the number of the objects are not limited, for example, a first object may be one or more than one. In addition, “and/or” in this specification and the claims represents at least one of the connected objects, and a character “/” used herein generally indicates an “or” relationship between associated objects.

[0020] In the embodiments of this application, the terms such as “exemplary” and “for example” are used to represent giving an example, an illustration, or a description. Any embodiment or design scheme described as “exemplary” or “for example” in the embodiments of this application should not be construed as being preferred or superior to other embodiments or design schemes. To be specific, the use of the word such as “exemplary” or “for example” is intended to present a related concept in a specific manner.

[0021] Some terms involved in the embodiments of this application are first explained and described below.

[0022] Call initiation anomaly: a call initiation anomaly refers to an anomaly occurs before receiving a ring response message after sending a first call request message. For example, a network temporary anomaly, a network call parameter anomaly, and the like.

[0023] It is to be noted that, a method for processing a call initiation anomaly according to the embodiments of this application may be performed by an apparatus for processing a call initiation anomaly or a control module configured to perform the method for processing a call initiation anomaly in the apparatus for processing a call initiation anomaly, or may be performed by an electronic device (the electronic device may include the apparatus for processing a call initiation anomaly in the embodiments of this application, or an independent apparatus for processing a call initiation anomaly). The method for processing a call initiation anomaly according to the embodiments of this application is exemplarily described in the embodiments of this application by using an electronic device as an example.

[0024] The method for processing a call initiation anomaly according to the embodiments of this application is described in detail below with reference to the accompany drawings through specific embodiments and application scenarios thereof.

[0025] As shown in FIG. 1, an embodiment of this application provides a method for processing a call initiation anomaly, and the method may include the following S201 and S202.

[0026] S201: An electronic device sends a first call request message through a first PS domain.

[0027] In this embodiment of this application, the first call request message may be used for requesting a call connection establishment with a certain account, for example, establishing call connection with a certain subscriber identity module (SIM) card.

[0028] S202: The electronic device performs a first operation in a case that a first call initiation anomaly occurs.

[0029] The first operation may include any one of the following: [0030] sending the first call request message through a second PS domain; [0031] disabling a VoLTE function, and sending the first call request message through a CS domain; [0032] registering in the second PS domain again, and sending the first call request message through the second PS domain; and [0033] sending a second call request message to a first account through a target application program, where the first account corresponds to an account indicated by the first call request message.

[0034] It may be understood that the electronic device may improve a call success rate of the electronic device through a method of calling out again.

[0035] In this embodiment of this application, after the electronic device sends the first call request message through the first PS domain (that is, sending in the first PS domain), if the first call initiation anomaly occurs, the electronic device may resend the first call request message through the first operation, or send the second call request message corresponding to the first call request message through the target application program, so as to avoid a call failure caused by the call initiation anomaly, thereby improving a call success rate.

[0036] Optionally, in this embodiment of this application, when the electronic device receives the call request input of a user, the electronic device may generate, according to a session initiation protocol (SIP), a SIP invite message, that is, the first call request message, and then send the first call request message to an IMS network through the first PS domain.

[0037] Optionally, in this embodiment of this application, the first call initiation anomaly may be any possible call initiation anomaly, such as a network temporary anomaly, a network call parameter anomaly, or an electronic device call parameter anomaly. Details may be determined according to an actual use requirement, which is not limited in this embodiment of this application.

[0038] Optionally, in this embodiment of this application, the first PS domain and the second PS domain may be the same PS domain or may be different PS domains. Details may be determined according to an actual use requirement, which is not limited in this embodiment of this application.

[0039] Optionally, in this embodiment of this application, the first PS domain may be a 5G-PS domain or may be a 4G-PS domain. Details may be determined according to an actual use requirement, which is not limited in this embodiment of this application.

[0040] It is to be noted that, in this embodiment of this application, when the electronic device is registered on a 4G network and a voice service is registered on the VoLTE, the first PS domain may be the 4G-PS domain; and when the electronic device is registered on a 5G network and the voice service is registered on a voice over new radio ( VoNR), the first PS domain may be the 5G-PS domain.

[0041] In this embodiment of this application, the second PS domain may be the 4G-PS domain.

[0042] In this embodiment of this application, when the first PS domain and the second PS domain are the same PS domain, the sending the first call request message through a second PS domain may be understood as: the electronic device calls out (sends) the first call request message again in the first PS domain, so as to avoid a call initiation failure caused by the network temporary anomaly, thereby improving a call initiation success rate.

[0043] It is to be noted that, in this embodiment of this application, generally the network temporary anomaly lasts for a short time and is accidental, so that when the electronic device calls out the first call request message again in the first PS domain, a success rate of this calling out is relatively large.

[0044] In this embodiment of this application, after the electronic device calls out the first call request message again in the first PS domain, if the call initiation anomaly still occurs, the electronic device may call out the first call request message again in the first PS domain, so as to further avoid the call initiation failure caused by the network temporary anomaly, thereby further improving the call initiation success rate.

[0045] Optionally, in this embodiment of this application, a quantity of times of calling out the first call request message through the first PS domain by the electronic device may be N (N is an integer greater than 1). Details may be determined according to an actual use requirement, which is not limited in this embodiment of this application.

[0046] N may be a value of a threshold set by a manufacturer of the electronic device in the electronic device.

[0047] In this embodiment of this application, for the disabling a VoLTE function, and sending the first call request message through a CS domain, the electronic device may fall back to the CS domain through disabling the VoLTE function, so as to avoid a situation that the electronic device cannot fall back to the CS domain and cannot call out a call request message again because the electronic device is in an LTE ONLY mode, so as to ensure that the electronic device can call out again when the call initiation anomaly occurs, thereby improving the call success rate of the electronic device.

[0048] In this embodiment of this application, for the registering in the second PS domain again, and sending the first call request message through the second PS domain, the electronic device may re-access the network (that is, refresh the registration) by means of detaching (detach) and attaching (attach) in the second PS domain, so as to register in the second PS domain again and refresh an electronic device call parameter and a network call parameter. In this way, after the electronic device registers in the second PS domain again, when the electronic device sends the first call request message again through the second PS domain, the call initiation failure caused by the electronic device call parameter and/or the network call parameter may be avoided, so as to improve the call initiation success rate of the electronic device.

[0049] In this embodiment of this application, the target application program may be an application program with a communication function in the electronic device. Specifically, the target application program may be an OTT (over-the-top) voice application program.

[0050] The target application program may store an account corresponding to the account indicated by the first call request message.

[0051] Optionally, in this embodiment of this application, the second call request message may be a video call request message, or may be a voice call request message. Details may be determined according to an actual use requirement, which is not limited in this embodiment of this application.

[0052] In this embodiment of this application, the second call request message may be a call request message called out through a data network. In this way, when the call initiation anomaly occurs in the electronic device, the electronic device may directly call out the second call request message through the data network, so as to further improve the call initiation success rate of the electronic device, thereby improving the call experience of the user.

[0053] Through the processing method for the call initiation anomaly according to the embodiments of this application, when the call initiation anomaly occurs, the first call request message may be resent (that is, the first call request message may be called out again) through the first operation, or the second call request message may be sent to the account corresponding to the account indicated by the first call request message through the target application program, so that when the call initiation anomaly occurs, the call initiation anomaly can be directly dealt with, thereby avoiding a call failure caused by the call initiation anomaly and improving the call success rate.

[0054] Optionally, in this embodiment of this application, in a case that the first PS domain and the second PS domain are different, before the electronic device performs the first operation, the electronic device may first fall back to an access network device corresponding to the second PS domain from an access network device corresponding to the first PS domain, and then perform the first operation.

[0055] In this embodiment of this application, the foregoing S202 may be specifically implemented through the following S202a and S202b.

[0056] S202a: The electronic device falls back to a second access network device from a first access network device in a case that the first call initiation anomaly occurs.

[0057] The first access network device may be the access network device corresponding to the first PS domain, and the second access network device may be the access network device corresponding to the second PS domain.

[0058] S202b: The electronic device performs the first operation.

[0059] In this embodiment of this application, in a case that the first call initiation anomaly occurs, the electronic device may fall back to the second access network device from the first access network device, and then perform the first operation.

[0060] Optionally, in this embodiment of this application, the first access network device may be a 5G access network device (for example, an NR device, or the like), and the second access network device may be a 4G access network device (for example, an eNB, or the like).

[0061] Certainly, during an actual implementation, the first access network device and the second access network device may further be any other possible access network device. Details may be determined according to an actual use requirement, which is not limited in this embodiment of this application.

[0062] In this embodiment of this application, when the first access network device is a 5G access network device, and the second access network device is a 4G access network device, the first PS domain may be the 5G-PS domain, and the second PS domain may be the 4G-PS domain.

[0063] In this embodiment of this application, that the electronic device falls back to the second access network device from the first access network device may be implemented through a radio access network (RAN) fallback. Specifically, the electronic device may fall back to accessing a 5G core network device through a 4G RAN from accessing the 5G core network device through the NR device. In this way, the electronic device falls back to a 4G access network from an access network to which the electronic device is connected, so that the electronic device may call out the call request message (the first call request message or the second call request message) again in a 4G network, thereby avoiding the call initiation anomaly caused by a 5G network anomaly and improving the call initiation success rate of the electronic device.

[0064] Optionally, in this embodiment of this application, after the electronic device sends the first call request message through the first PS domain, before the first call initiation anomaly occurs, if a call initiation anomaly occurs (for example, a second call initiation anomaly in this embodiment of this application), the electronic device may fall back to a core network device corresponding to the second PS domain from a core network device corresponding to the first PS domain, and send the first call request message through the second PS domain.

[0065] With reference to FIG. 1, as shown in FIG. 2, after S201 and before S202, the method for processing a call initiation anomaly according to this embodiment of this application may further include the following S203.

[0066] S203: In a case that the second call initiation anomaly occurs, the electronic device falls back to a second core network from a first core network device, and sends the first call request message through the second PS domain.

[0067] The first core network device may be the core network device corresponding to the first PS domain, and the second core network device may be the core network device corresponding to the second PS domain.

[0068] In this embodiment of this application, after the electronic device sends the first call request message through the first PS domain, before the first call initiation anomaly occurs, if the second call initiation anomaly occurs, the electronic device may fall back to the second core network device from the first core network device, and send the first call request message through the second PS domain.

[0069] Optionally, in this embodiment of this application, the second call initiation anomaly may be a call initiation anomaly the same as or different from the first call initiation anomaly. Details may be determined according to an actual use requirement, which is not limited in this embodiment of this application.

[0070] Optionally, in this embodiment of this application, the first core network device may be the 5G core network device, and the second core network device may be a 4G core network device.

[0071] Certainly, during an actual implementation, the first core network device and the second core network device may further be any other possible core network device. Details may be determined according to an actual use requirement, which is not limited in this embodiment of this application.

[0072] In this embodiment of this application, when the first core network device is the 5G core network device, and the second core network device is the 4G core network device, the first PS domain may be the 5G-PS domain, and the second PS domain may be the 4G-PS domain.

[0073] In this embodiment of this application, that the electronic device falls back to the second access network device from the first access network device may be implemented through an evolved packet system (EPS) fallback. Specifically, the electronic device may fall back to accessing the IMS network through the 4G core network device from accessing the IMS network through the 5G core network device, to implement falling back to the second core network device from the first core network device, which causes a fallback to a 4G voice from a 5G voice, so that the electronic device may call out the first call request message again in the 4G-PS domain.

[0074] Optionally, in this embodiment of this application, in a case that the first operation is to send the first call request message through the second PS domain, after the electronic device performs the first operation, if a call initiation anomaly occurs (for example, a third call initiation anomaly in this embodiment of this application) again, the electronic device may perform another operation (for example, a second operation in this embodiment of this application) in the first operation other than sending the first call request message through the second PS domain, and deal with the call initiation anomaly again.

[0075] With reference to FIG. 1, as shown in FIG. 3, after S202, the method for processing a call initiation anomaly according to this embodiment of this application may further include the following S204.

[0076] S204: The electronic device performs the second operation in a case that the third call initiation anomaly occurs.

[0077] The second operation may include any one of the following: [0078] disabling the VoLTE function, and sending the first call request message through the CS domain; [0079] registering in the second PS domain again, and sending the first call request message through the second PS domain; and [0080] sending the second call request message to the first account through the target application program.

[0081] In this embodiment of this application, after the electronic device performs the first operation (sending the first call request message through the second PS domain), if the third call initiation anomaly occurs again, the electronic device may perform the second operation, and deal with the call initiation anomaly again, thereby further improving the call initiation success rate.

[0082] Optionally, in this embodiment of this application, the third call initiation anomaly may be a call initiation anomaly the same as or different from the second call initiation anomaly. Details may be determined according to an actual use requirement, which is not limited in this embodiment of this application.

[0083] It is to be noted that, in this embodiment of this application, for the related description of “disabling the VoLTE function, and sending the first call request message through the CS domain”, “registering in the second PS domain again, and sending the first call request message through the second PS domain”, and “sending the second call request message to the first account through the target application program”, reference may be made to the detailed description in the foregoing embodiments for details, and the details will not be described herein again to avoid repetition.

[0084] In this embodiment of this application, after the electronic device deals with the call initiation anomaly, if the call initiation anomaly further occurs, the electronic device may deal with the call initiation anomaly in other processing manners, so as to deal with the call initiation anomalies caused by different reasons, thereby further improving the call initiation success rate.

[0085] Optionally, in this embodiment of this application, in a case that the second operation is to disable the VoLTE function, and send the first call request message through the CS domain, after the electronic device performs the second operation, if a call initiation anomaly occurs (for example, a fourth call initiation anomaly in this embodiment of this application) again, the electronic device may perform a third operation, and deal with the call initiation anomaly again.

[0086] With reference to FIG. 3, as shown in FIG. 4, after S204, the method for processing a call initiation anomaly according to this embodiment of this application may further include the following S205.

[0087] S205: The electronic device performs the third operation in a case that the fourth call initiation anomaly occurs.

[0088] The third operation may include any one of the following: [0089] registering in the second PS domain again, and sending the first call request message through the second PS domain; and [0090] sending the second call request message to the first account through the target application program.

[0091] It is to be noted that, in this embodiment of this application, for the related description of “registering in the second PS domain again, and sending the first call request message through the second PS domain”, and “sending the second call request message to the first account through the target application program”, reference may be made to the detailed description in the foregoing embodiments for details, and the details will not be described herein again to avoid repetition.

[0092] In this embodiment of this application, after the electronic device deals with the call initiation anomaly through the second operation, if the call initiation anomaly still occurs, the electronic device may deal with the call initiation anomaly in other processing manners, so as to deal with the call initiation anomalies caused by different reasons, thereby further improving the call initiation success rate.

[0093] Optionally, in this embodiment of this application, the step that the electronic device sends the second call request message to the first account through the target application program may be implemented through the following step A and step B.

[0094] Step A: The electronic device determines the first account from the target application program according to the first call request message.

[0095] Step B: The electronic device sends the second call request message to the first account through the target application program.

[0096] In this embodiment of this application, when the electronic device sends the second call request message to the first account through the target application program, the electronic device may first determine the first account from the target application program according to the first call request message, and then send the second call request message to the first account through the target application program.

[0097] It is to be noted that, in this embodiment of this application, the electronic device may send the second call request message to the first account through the data network, so as to avoid the call initiation failure caused by the network call parameter anomaly and the electronic device call parameter anomaly.

[0098] The apparatus for processing a call initiation anomaly according to the embodiments of this application is described by using an example in which the apparatus for processing a call initiation anomaly performs the method for processing a call initiation anomaly in the embodiments of this application.

[0099] As shown in FIG. 5, the embodiments of this application provide an apparatus 300 for processing a call initiation anomaly, including a sending module 301 and an execution module 302. The sending module 301 is configured to send a first call request message through a first PS domain; and the execution module 302 is configured to perform a first operation in a case that a first call initiation anomaly occurs, where the first operation includes any one of the following: sending the first call request message through a second PS domain; disabling a VoLTE function, and sending the first call request message through a CS domain; registering in the second PS domain again, and sending the first call request message through the second PS domain; and sending a second call request message to a first account through a target application program, where the first account corresponds to an account indicated by the first call request message.

[0100] Through the apparatus for processing a call initiation anomaly according to the embodiments of this application, when the call initiation anomaly occurs, the first call request message may be resent (that is, the first call request message may be called out again) through the first operation, or the second call request message may be sent to the account corresponding to the account indicated by the first call request message through the target application program, so that when the call initiation anomaly occurs, the call initiation anomaly can be directly dealt with, thereby avoiding a call failure caused by the call initiation anomaly and improving the call success rate.

[0101] Optionally, in this embodiment of this application, the first PS domain and the second PS domain are different; and the execution module 302 is further configured to fall back to a second access network device from a first access network device before performing the first operation, where the first access network device is an access network device corresponding to the first PS domain, and the second access network device is an access network device corresponding to the second PS domain.

[0102] Optionally, in this embodiment of this application, the execution module 302 is further configured to, after the sending module 301 sends the first call request message through the first PS domain, before the first call initiation anomaly occurs, in a case that a second call initiation anomaly occurs, fall back to a second core network from a first core network device; and the sending module 301 is configured to send the first call request message through the second PS domain, where the first core network device is a core network device corresponding to the first PS domain, and the second core network device is a core network device corresponding to the second PS domain.

[0103] Optionally, in this embodiment of this application, the first operation is to send the first call request message through the second PS domain; and the execution module 302 is further configured to, after performing the first operation, perform a second operation in a case that a third call initiation anomaly occurs, where the second operation includes any one of the following: disabling the VoLTE function, and sending the first call request message through the CS domain; registering in the second PS domain again, and sending the first call request message through the second PS domain; and sending the second call request message to the first account through the target application program.

[0104] Through the apparatus for processing a call initiation anomaly according to this embodiment of this application, after the apparatus for processing a call initiation anomaly deals with the call initiation anomaly, if the call initiation anomaly further occurs, the apparatus for processing a call initiation anomaly may deal with the call initiation anomaly in other processing manners, so as to deal with the call initiation anomalies caused by different reasons, thereby further improving the call initiation success rate.

[0105] Optionally, in this embodiment of this application, the second operation is to disable the VoLTE function and send the first call request message through the CS domain; and the execution module 302 is further configured to, after performing the second operation, perform a third operation in a case that a fourth call initiation anomaly occurs, where the third operation includes any one of the following: registering in the second PS domain again, and sending the first call request message through the second PS domain; and sending the second call request message to the first account through the target application program.

[0106] Through the apparatus for processing a call initiation anomaly according to this embodiment of this application, after the apparatus for processing a call initiation anomaly deals with the call initiation anomaly through the second operation, if the call initiation anomaly still occurs, the apparatus for processing a call initiation anomaly may deal with the call initiation anomaly in other processing manners, so as to deal with the call initiation anomalies caused by different reasons, thereby further improving the call initiation success rate.

[0107] Optionally, in this embodiment of this application, the sending module includes a determining submodule and a sending submodule; the determining submodule is configured to determine the first account from the target application program according to the first call request message; and the sending submodule is configured to send the second call request message to the first account through the target application program.

[0108] The apparatus for processing a call initiation anomaly in this embodiment of this application may be an apparatus, or may be a component, an integrated circuit, or a chip in an electronic device. The apparatus may be a mobile electronic device or may be a non-mobile electronic device. For example, the mobile electronic device may be a mobile phone, a tablet computer, a notebook computer, a palm computer, an in-vehicle electronic device, a wearable device, an ultra-mobile personal computer (UMPC), a netbook, or a personal digital assistant (PDA); and the non-mobile electronic device may be a personal computer (PC), a television (TV), a teller machine, or an automated machine, which are not specifically limited in this embodiment of this application.

[0109] The apparatus for processing a call initiation anomaly in this embodiment of this application may be an apparatus with an operating system. The operating system may be an Android operating system, an iOS operating system, or another possible operating system, which is not specifically limited in this embodiment of this application.

[0110] The apparatus for processing a call initiation anomaly according to this embodiment of this application can implement all processes implemented by the method embodiments shown in FIG. 1 to FIG. 4, and details are not described herein again to avoid repetition.

[0111] Optionally, as shown in FIG. 6, the embodiments of this application further provide an electronic device 600, including a processor 601, a memory 602, and a program or instruction stored in the memory 602 and runnable on the processor 601, where the program or instruction, when executed by the processor 601, implements each process of the foregoing method embodiments for a call initiation anomaly, and the same technical effects can be achieved. To avoid repetition, details are not described herein again.

[0112] It is to be noted that, the electronic device in this embodiment of this application includes the mobile electronic device and the non-mobile electronic device.

[0113] FIG. 7 is a schematic diagram of a hardware structure of an electronic device according to an embodiment of this application.

[0114] The electronic device 100 includes, but is not limited to, components such as a radio frequency unit 101, a network module 102, an audio output unit 103, an input unit 104, a sensor 105, a display unit 106, a user input unit 107, an interface unit 108, a memory 109, and a processor 110.

[0115] A person skilled in the art may understand that the electronic device 100 may further include a power supply 111 (such as a battery) for supplying power to the components. The power supply may be logically connected to the processor 110 by using a power management system, thereby implementing functions such as charging, discharging, and power consumption management by using the power management system. The structure of the electronic device shown in FIG. 7 constitutes no limitation on the electronic device, and the electronic device may include more or fewer components than those shown in the figure, or some components may be combined, or a different component deployment may be used, which are not described herein again.

[0116] The radio frequency unit 101 is configured to send a first call request message through a first PS domain; and the processor 110 is configured to perform a first operation in a case that a first call initiation anomaly occurs, where the first operation includes any one of the following: sending the first call request message through a second PS domain; disabling a VoLTE function, and sending the first call request message through a CS domain; registering in the second PS domain again, and sending the first call request message through the second PS domain; and sending a second call request message to a first account through a target application program, where the first account corresponds to an account indicated by the first call request message.

[0117] Through the apparatus for processing a call initiation anomaly according to the embodiments of this application, when the call initiation anomaly occurs, the first call request message may be resent (that is, the first call request message may be called out again) through the first operation, or the second call request message may be sent to the account corresponding to the account indicated by the first call request message through the target application program, so that when the call initiation anomaly occurs, the call initiation anomaly can be directly dealt with, thereby avoiding a call failure caused by the call initiation anomaly and improving the call success rate.

[0118] Optionally, in this embodiment of this application, the first PS domain and the second PS domain are different; and the processor 110 is further configured to fall back to a second access network device from a first access network device before performing the first operation, where the first access network device is an access network device corresponding to the first PS domain, and the second access network device is an access network device corresponding to the second PS domain.

[0119] Optionally, in this embodiment of this application, the processor 110 is further configured to, after the radio frequency unit 101 sends the first call request message through the first PS domain, before the first call initiation anomaly occurs, in a case that a second call initiation anomaly occurs, fall back to a second core network from a first core network device; and the radio frequency unit 101 is configured to send the first call request message through the second PS domain, where the first core network device is a core network device corresponding to the first PS domain, and the second core network device is a core network device corresponding to the second PS domain.

[0120] Optionally, in this embodiment of this application, the first operation is to send the first call request message through the second PS domain; and the processor 110 is further configured to, after performing the first operation, perform a second operation in a case that a third call initiation anomaly occurs, where the second operation includes any one of the following: disabling the VoLTE function, and sending the first call request message through the CS domain; registering in the second PS domain again, and sending the first call request message through the second PS domain; and sending the second call request message to the first account through the target application program.

[0121] Through the apparatus for processing a call initiation anomaly according to this embodiment of this application, after the electronic device deals with the call initiation anomaly, if the call initiation anomaly further occurs, the electronic device may deal with the call initiation anomaly in other processing manners, so as to deal with the call initiation anomalies caused by different reasons, thereby further improving the call initiation success rate.

[0122] Optionally, in this embodiment of this application, the second operation is to disable the VoLTE function and send the first call request message through the CS domain; and the processor 110 is further configured to, after performing the second operation, perform a third operation in a case that a fourth call initiation anomaly occurs, where the third operation includes any one of the following: registering in the second PS domain again, and sending the first call request message through the second PS domain; and sending the second call request message to the first account through the target application program.

[0123] Through the apparatus for processing a call initiation anomaly according to this embodiment of this application, after the electronic device deals with the call initiation anomaly through the second operation, if the call initiation anomaly still occurs, the electronic device may deal with the call initiation anomaly in other processing manners, so as to deal with the call initiation anomalies caused by different reasons, thereby further improving the call initiation success rate.

[0124] Optionally, in this embodiment of this application, the radio frequency unit 101 is configured to determine the first account from the target application program according to the first call request message, and send the second call request message to the first account through the target application program.

[0125] It is to be noted that, in this embodiment of this application, the sending module 301 in the schematic structural diagram (for example, FIG. 5 above) of the foregoing apparatus for processing a call initiation anomaly may be implemented by using the foregoing radio frequency unit 101; and the execution module 302 in the schematic structural diagram of the foregoing apparatus for processing a call initiation anomaly may be implemented by using the foregoing processor 110.

[0126] It is to be understood that, in this embodiment of this application, the input unit 104 may include a graphics processing unit (GPU) 1041 and a microphone 1042, and the graphics processing unit 1041 processes static pictures or video image data obtained by an image capturing device (such as a camera) in a video capturing mode or an image capturing mode. The display unit 106 may include a display panel 1061, and the display panel 1061 may be configured by using a liquid crystal display, an organic light-emitting diode, or the like. The user input unit 107 includes a touch panel 1071 and another input device 1072. The touch panel 1071 is also referred to as a touch screen. The touch panel 1071 may include two parts: a touch detection apparatus and a touch controller. The another input device 1072 may include, but is not limited to, a physical keyboard, a functional key (such as a volume control key or a switch key), a track ball, a mouse, and a joystick, which are not described herein again. The memory 109 may be configured to store a software program and various data, including, but not limited to an application program and an operating system. The processor 110 may integrate an application processor and a modem processor, where the application processor mainly processes an operating system, a user interface, an application program, and the like, and the modem processor mainly processes wireless communication. It may be understood that the foregoing modem may not be integrated into the processor 110.

[0127] The embodiments of this application further provide a readable storage medium, storing a program or instruction, where the program or instruction, when executed by a processor, implements each process of the foregoing method embodiments for a call initiation anomaly, and the same technical effects can be achieved. To avoid repetition, details are not described herein again.

[0128] The foregoing processor is the processor in the electronic device described in the foregoing embodiment. The readable storage medium may include a computer-readable storage medium, such as, a read-only memory (ROM), a random access memory (RAM), a magnetic disk, or an optical disk.

[0129] The embodiments of this application further provide a chip, including a processor and a communication interface, where the communication interface is coupled to the processor, and the processor is configured to run a program or instructions to implement each process of the foregoing method embodiments for a call initiation anomaly and can achieve the same technical effects. To avoid repetition, details are not described herein again.

[0130] It is to be understood that the chip mentioned in this embodiment of this application may also be referred to as a system-level chip, a system chip, a chip system, a system chip on a chip, or the like.

[0131] It is to be noted that, the term “comprise”, “include” or any other variation thereof in this specification is intended to cover a non-exclusive inclusion, which specifies the presence of stated processes, methods, objects, or apparatuses, but does not preclude the presence or addition of one or more other processes, methods, objects, or apparatuses. Without more limitations, elements defined by a sentence “including one” does not exclude that there are still other same elements in the process, method, object, or apparatus. In addition, it is to be noted that, the scope of the method and apparatus in the embodiments of this application is not limited to performing the functions in the order shown or discussed, but may also include performing the functions in a substantially simultaneous manner or in a reverse order according to the functions involved, for example, the described method may be performed in a sequence different from the described order, and various steps may also be added, omitted, or combined. In addition, features described with reference to certain examples may be combined in other examples.

[0132] Through the descriptions of the foregoing implementations, a person skilled in the art may clearly understand that the method according to the foregoing embodiments may be implemented by means of software and a necessary general hardware platform, and certainly, may also be implemented by hardware, but in many cases, the former manner is a better implementation. Based on such an understanding, the technical solutions of this application essentially or the part contributing to the prior art may be implemented in a form of a software product. The computer software product is stored in a storage medium (such as a ROM/RAM, a magnetic disk, or an optical disk) and includes several instructions for instructing an electronic device (which may be a mobile phone, a computer, a server, an air conditioner, a network device, or the like) to perform the methods of the embodiments of this application.

[0133] The embodiments of this application are described above with reference to the accompanying drawings, but this application is not limited to the foregoing specific embodiments, which are merely illustrative rather than limited. Under the inspiration of this application, a person of ordinary skill in the art can make many forms without departing from the scope of this application and the protection of the claims, all of which fall within the protection of this application.