Voice call method, user equipment and storage medium

Abstract

The invention provides a voice call method, user equipment and a storage medium, relates to the technical field of terminals, and can solve the problem of poor user experience caused by call retry failure. The method comprises: in response to a failure of initiating a voice call in an IMS domain, determining a registration type identifier of a registration request of a UE in a current region, the registration request being a registration request sent to a core network when the UE performs network registration in the current region; if the registration type identifier shows that the registration request is a PS domain registration request, the voice call is ended, and the PS domain registration request is used for requesting network registration of a PS domain. According to the embodiment of the invention, when the call in the IMS domain fails, whether the call retry of the CS domain is carried out is determined in combination with the type of the registration request, and when the registration request is a PS domain registration request, it can be determined that the current area does not cover the CS domain network and the call retry of the CS domain is not carried out any more, so that the problem that UE display has no signal due to network search failure in the CS domain is solved, and the display experience of a user is optimized.

Description

TECHNICAL FIELD

[0001] The present application relates to the technical field of terminal, and in particular, to a voice call method, a user equipment and a storage medium. BACKGROUND

[0002] Voice call is a communication connection between user equipments established through a communication network. The communication connection can be established through the 2nd Generation Mobile Communication Technology (2G), the 3rd Generation Mobile Communication Technology (3G), the 4th Generation Mobile Communication Technology (4G) or the 5th Generation Mobile Communication Technology (5G). Among them, when the voice call connection is established through the 2G or 3G technology, it is generally implemented in the Circuit Switched (CS) domain; when the voice call connection is established through the 4G or 5G technology, it is generally implemented in the Internet Protocol (IP) Multimedia Subsystem (IMS) domain.

[0003] Due to the different development levels of network communication in different regions, the voice calls using the CS domain and the IMS domain coexist. Generally, when the user equipment initiates a call in the IMS domain fails, it will try to search for the CS domain, and when the search is successful, it will retry the call in the CS domain. At this time, the User Interface (UI) is not aware of the call retry process.

[0004] However, with the development of network technology, the 2G and 3G networks are gradually being replaced by more advanced 4G and 5G networks. Therefore, the CS domain is gradually covered by the IMS domain, and in some regions, there is no CS domain network coverage. In this case, if the search for the CS domain for retry is continued after the call in the IMS domain fails, the result of the search for the network will fail, the call retry cannot be successful, and accordingly, the UI will display a signal anomaly, resulting in poor user experience. SUMMARY

[0005] The application provides a voice call method, a user equipment and a storage medium, which can solve the problem of poor user display experience caused by CS domain network search failure when IMS domain call fails in related scenarios. The technical solution is as follows:

[0006] In a first aspect, a voice call method is provided, the method comprising:

[0007] In response to a failure of initiating a voice call in an Internet Protocol Multimedia Subsystem (IMS) domain, determining a registration type identifier of a registration request of a user equipment (UE) in a current area, the registration request being a registration request sent by the UE to a core network when performing network registration in the current area;

[0008] If the registration type identifier indicates that the registration request is a packet switched (PS) domain registration request, ending the voice call and not performing a CS domain call retry, the PS domain registration request being used for requesting network registration in a PS domain.

[0009] When the IMS domain call fails, whether to perform the CS domain call retry is determined in combination with the type of the registration request. Only when the registration request is a joint request and the registration result is that the PS domain network and the CS domain network are both successfully registered, the CS domain call retry is performed when the IMS domain call fails, thereby reducing the problem of UE display of no signal caused by CS domain network search failure and optimizing the display experience of the user.

[0010] In some embodiments, the method further comprises:

[0011] If the registration type identifier indicates that the registration request is a joint registration request, obtaining a registration result identifier;

[0012] If the registration result identifier indicates that the UE is successfully registered in the PS domain network and the CS domain network in the current area, continuing to perform the call retry based on the CS domain.

[0013] When the IMS domain call fails, whether to perform the CS domain call retry is determined in combination with the type of the registration request and the type of the registration result. Only when the registration request is a joint request and the registration result is that the PS domain network and the CS domain network are both successfully registered, the CS domain call retry is performed when the IMS domain call fails, thereby reducing the problem of UE display of no signal caused by CS domain network search failure and optimizing the display experience of the user.

[0014] In some embodiments, the method further comprises:

[0015] If the registration result identifier indicates that the UE is successfully registered in the PS domain network in the current area, obtaining a number of the voice call, and the joint registration request is used for requesting registration of the PS domain network and a circuit switched (CS) domain network.

[0016] if the number of the current voice call is not the preset target number, ending the voice call without CS domain call retry;

[0017] if the number of the current voice call is the preset target number, continuing the call retry based on the CS domain.

[0018] When the registration request is a joint registration request and the registration response indicates that the UE is successfully registered in the PS domain in the current area, it cannot be completely excluded that the current area is covered by the CS domain network, therefore, the CS domain network search can be attempted to attempt the call retry of the CS domain, and when the number of the call is the target number, the call retry of the CS domain is attempted, which improves the call success rate for the target number, and when the number is not the target number, the call retry of the CS domain is not performed, thereby reducing the probability of network search failure in the call retry of the CS domain, and further optimizing the user experience.

[0019] In some embodiments, the method further comprises:

[0020] if the registration result identifier indicates that the UE is successfully registered in the PS domain network in the current area, obtaining the current screen state of the UE;

[0021] if the screen state is the screen-on state, ending the voice call without CS domain call retry;

[0022] if the screen state is the screen-off state, continuing the call retry based on the CS domain.

[0023] When the registration request is a joint registration request and the registration response indicates that the UE is successfully registered in the PS domain in the current area, it cannot be completely excluded that the current area is covered by the CS domain network, therefore, the CS domain network search can be attempted to attempt the call retry of the CS domain, and when the UE is in the screen-off state, even if the call retry of the CS domain is started, but the network search fails, the UE will not display the network search failure page, which does not affect the user experience, therefore, when the UE is in the screen-off state, the call retry of the CS domain is initiated, and when the UE is in the screen-on state, the call retry of the CS domain is not initiated, which improves the call success rate and does not affect the user experience.

[0024] In some embodiments, the method further comprises:

[0025] if the registration result identifier indicates that the UE is successfully registered in the PS domain network in the current area, obtaining historical call data of the current area, the historical call data comprising a success rate of the call retry of the CS domain in the current area;

[0026] if the success rate is not greater than a preset value, ending the voice call without CS domain call retry;

[0027] If the success rate is greater than the preset value, the call retry is continued based on the CS domain.

[0028] The success rate of the CS domain call retry in the current area is determined to determine whether to perform the call retry, thereby preventing the problem of low success rate of the call retry caused by the low success rate of the CS domain call, and the call retry is performed when the success rate of the CS domain call is greater than a preset value, thereby improving the probability of the success of the call retry, reducing the probability of the display of no signal caused by the failure of the call retry, and optimizing the user experience.

[0029] In some embodiments, the method further comprises:

[0030] The registration request sent by the UE is obtained from the local storage unit.

[0031] In the registration request, a target field of the user marked registration type is obtained.

[0032] The registration type identifier is determined from the content of the target field.

[0033] The UE adds the registration type identifier in the registration request when performing network registration, and the core network adds the result type identifier in the registration response when feeding back the registration response to the UE, the registration type identifier of the network requested to be registered in this network registration is recorded through the registration type identifier, and the type of the network successfully registered in this network registration is recorded through the registration result identifier. In this way, the registration type identifier and the registration result identifier of the network registration are stored respectively, so that the UE can determine whether the CS domain network is successfully registered currently according to the stored registration type identifier and the registration result identifier, and then determine whether to initiate the call retry in the CS domain when the call in the IMS domain fails, thereby avoiding the problem of search failure and display of no signal caused by blindly initiating the call retry in the CS domain when the CS is not successfully registered, ensuring the call experience of the user, considering the network display experience, and thereby optimizing the user experience.

[0034] In some embodiments, the method further comprises:

[0035] The voice call process is ended, and the voice call interface is exited.

[0036] After the call in the IMS domain fails, the voice call interface is directly exited, so that no signal and other information are displayed, thereby optimizing the user experience.

[0037] In some embodiments, the method further comprises:

[0038] The preset registration type identifier is obtained based on the public land mobile network (PLMN) information of the user identification card used by the UE.

[0039] generating a registration request based on the registration type identifier;

[0040] sending the registration request to a core network, the core network being a network element device corresponding to an operator of the current region;

[0041] receiving a registration response fed back by the core network, the registration response including a registration result identifier;

[0042] storing the registration request and the registration response.

[0043] In a second aspect, a voice call apparatus is provided, and the apparatus includes:

[0044] a determining module configured to determine a registration type identifier of a registration request of a user equipment (UE) in a current region in response to a failure of initiating a voice call in an Internet Protocol Multimedia Subsystem (IMS) domain, the registration request being a registration request sent to a core network when the UE performs network registration in the current region;

[0045] a control module configured to end the voice call and not perform a circuit switched (CS) domain call retry if the registration type identifier indicates that the registration request is a packet switched (PS) domain registration request, the PS domain registration request being used to request network registration in a PS domain.

[0046] In some embodiments, the apparatus further includes:

[0047] a first obtaining module configured to obtain a registration result identifier if the registration type identifier indicates that the registration request is a joint registration request.

[0048] The control module is further configured to continue the call retry based on the CS domain if the registration result identifier indicates that the UE is successfully registered in the current region in a PS domain network and a CS domain network.

[0049] In some embodiments, the apparatus further includes:

[0050] a second obtaining module configured to obtain a number of the current voice call if the registration result identifier indicates that the UE is successfully registered in the current region in a PS domain network, the joint registration request being used to request registration in the PS domain network and a circuit switched (CS) domain network.

[0051] The control module is further configured to end the voice call and not perform the CS domain call retry if the number of the current voice call is not a preset target number, and continue the call retry based on the CS domain if the number of the current voice call is the preset target number.

[0052] In some embodiments, the apparatus further includes:

[0053] a third obtaining module, configured to obtain a current screen state of the UE if the registration result identifier indicates that the UE is successfully registered in a PS domain network in a current region;

[0054] The control module is further configured to end the voice call and not to perform CS domain call retry if the screen state is a screen-on state, and to continue to perform call retry based on the CS domain if the screen state is a screen-off state.

[0055] In some embodiments, the apparatus further includes:

[0056] a fourth obtaining module, configured to obtain historical call data of the current region if the registration result identifier indicates that the UE is successfully registered in a PS domain network in the current region, the historical call data including a success rate of CS domain call retry in the current region;

[0057] The control module is further configured to end the voice call and not to perform CS domain call retry if the success rate is not greater than a preset value, and to continue to perform call retry based on the CS domain if the success rate is greater than the preset value.

[0058] In some embodiments, the determining module includes:

[0059] a first obtaining unit, configured to obtain the registration request sent by the UE from a local storage unit;

[0060] a second obtaining unit, configured to obtain a target field of a user-labeled registration type in the registration request;

[0061] a determining unit, configured to determine the registration type identifier from content of the target field.

[0062] In some embodiments, the control module includes:

[0063] a display unit, configured to end a voice call process and exit a voice call interface.

[0064] In some embodiments, the apparatus further includes:

[0065] a fifth obtaining module, configured to obtain a preset registration type identifier based on public land mobile network (PLMN) information of a user identification card used by the UE;

[0066] a generating module, configured to generate a registration request based on the registration type identifier;

[0067] a sending module, configured to send the registration request to a core network, the core network being a network element device corresponding to an operator of the current region;

[0068] receiving a registration response fed back by the core network, the registration response comprising a registration result identifier;

[0069] storing the registration request and the registration response.

[0070] In a third aspect, a user equipment is provided, which comprises a processor and a memory in its structure, the memory is configured to store a program supporting the user equipment to execute the method provided in the first aspect above, and store data involved in the method provided in the first aspect above. The processor is configured to execute the program stored in the memory.

[0071] In a fourth aspect, a computer readable storage medium is provided, which stores instructions, when running on a computer, causes the computer to execute the method provided in the first aspect above.

[0072] In a fifth aspect, a computer program product is provided, which comprises instructions, when running on a computer, causes the computer to execute the method provided in the first aspect above.

[0073] The technical effects obtained by the second aspect, the third aspect, the fourth aspect and the fifth aspect above are similar to the technical effects obtained by the corresponding technical means in the first aspect above, and will not be repeated here. BRIEF DESCRIPTION OF DRAWINGS

[0074] Figure 1 is a structural schematic diagram of a user equipment according to an exemplary embodiment;

[0075] Figure 2 is an interface schematic diagram of displaying no signal when a call fails according to an exemplary embodiment;

[0076] Figure 3 is a timing diagram of a user equipment performing network registration with a core network according to an exemplary embodiment;

[0077] Figure 4 is a flowchart of a user equipment performing network registration with a core network according to an exemplary embodiment;

[0078] Figure 5 is a flowchart of a method for determining whether to perform call retry in a voice call process according to an exemplary embodiment;

[0079] Figure 6 is a flowchart of a method for determining whether to perform call retry in a voice call process in combination with multiple preset conditions according to an exemplary embodiment;

[0080] Figure 7is a flow diagram of a voice call method according to an example embodiment;

[0081] Figure 8 is a structural diagram of a voice call device according to an example embodiment. DETAILED DESCRIPTION

[0082] In the following description, specific details are set forth in order to provide a thorough understanding of embodiments of the application. However, persons having ordinary skill in the art will appreciate that embodiments of the application can be practiced without the specific details, which are for illustration only.

[0083] It should be understood that the term "comprising" when used in this specification and the appended claims, specifies the presence of stated features, integers, steps, operations, elements, and / or components, but does not preclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and / or groups thereof.

[0084] It should also be understood that "one or more" of an element or aspect means that one, two, or more elements or aspects are present; "and / or" as used herein refers to and encompasses any and all possible combinations of one or more of the associated items, as well as the lack of an item; and that the singular forms "a", "an" and "the" include one or more of the referenced item or items unless the context clearly indicates otherwise.

[0085] In addition, the terms "first", "second", "third", "fourth", and the like in the description and the appended claims of the present specification are used for distinguishing between similar elements and not necessarily for describing a sequential or chronological order. It is to be understood that the terms so used are interchangeable under appropriate circumstances such that the descriptive terms used herein are to be interpreted in the context as a special embodiment.

[0086] The terms "comprising", "containing", "including", "having" and their conjugates herein are used in their broadest sense to mean that the stated features, integers, steps, operations, elements, components, and / or combinations thereof are present, but not excluding the presence of one or more other features, integers, steps, operations, elements, components, and / or combinations thereof.

[0087] The voice call method provided by the embodiments of the present application can be applied to a user equipment. The user equipment can be a wearable device, a mobile phone, or other electronic devices. The embodiments of the present application do not limit the specific type of the user equipment.

[0088] Figure 1 is a structural schematic diagram of a user equipment provided by an embodiment of the present application. is a structural schematic diagram of a user equipment provided by an embodiment of the present application. Referring to Figure 1 The user equipment 100 can include a processor 110, an external memory interface 120, an internal memory 121, a universal serial bus (USB) interface 130, a charging management module 140, a power management module 141, a battery 142, an antenna 1, an antenna 2, a mobile communication module 150, a wireless communication module 160, an audio module 170, a loudspeaker 170A, a receiver 170B, a microphone 170C, an earphone interface 170D, a sensor module 180, a key 190, a motor 191, an indicator 192, a camera 193, a display screen 194, and a subscriber identification module (SIM) card interface 195, etc. The sensor module 180 can include a pressure sensor 180A, a gyroscope sensor 180B, a barometric pressure sensor 180C, a magnetic sensor 180D, an acceleration sensor 180E, a distance sensor 180F, a proximity light sensor 180G, a fingerprint sensor 180H, a temperature sensor 180J, a touch sensor 180K, an ambient light sensor 180L, a bone conduction sensor 180M, etc.

[0089] It can be understood that the structure illustrated in the embodiments of the present application does not constitute a specific limitation on the user equipment 100. In some other embodiments of the present application, the user equipment 100 can include more or fewer components than the illustration, or combine certain components, or split certain components, or different component arrangements. The illustrated components can be implemented in hardware, software, or a combination of software and hardware.

[0090] The processor 110 can include one or more processing units, such as: the processor 110 can include an application processor (AP), a modem processor, a graphics processing unit (GPU), an image signal processor (ISP), a controller, a memory, a video codec, a digital signal processor (DSP), a baseband processor, and / or a neural-network processing unit (NPU), etc. Different processing units can be independent devices, or can be integrated in one or more processors.

[0091] The controller can be the nerve center and command center of the user device 100. The controller can generate operation control signals according to the instruction operation code and the timing signal, and complete the control of fetching and executing instructions.

[0092] The processor 110 can also be provided with a memory for storing instructions and data. In some embodiments, the memory in the processor 110 is a cache memory. The memory can store instructions or data that the processor 110 has just used or recycled. If the processor 110 needs to use the instructions or data again, it can be directly called from the memory. This avoids repeated access and reduces the waiting time of the processor 110, thereby improving the efficiency of the system.

[0093] In some embodiments, the processor 110 can include one or more interfaces, such as an inter-integrated circuit (I2C) interface, an inter-integrated circuit sound (I2S) interface, a pulse code modulation (PCM) interface, a universal asynchronous receiver / transmitter (UART) interface, a mobile industry processor interface (MIPI), a general-purpose input / output (GPIO) interface, a subscriber identity module (SIM) interface, and / or a universal serial bus (USB) interface, etc.

[0094] The charging management module 140 is configured to receive charging input from a charger. The charger can be a wireless charger or a wired charger. In some wired charging embodiments, the charging management module 140 can receive charging input from a wired charger through the USB interface 130. In some wireless charging embodiments, the charging management module 140 can receive wireless charging input through the wireless charging coil of the user device 100. The charging management module 140 can charge the battery 142 while also providing power to the user device 100 through the power management module 141.

[0095] The power management module 141 is configured to connect the battery 142 and the charging management module 140 to the processor 110. The power management module 141 receives input from the battery 142 and / or the charging management module 140 to power the processor 110, the internal memory 121, the external memory, the display 194, the camera 193, the wireless communication module 160, and the like. The power management module 141 can also be configured to monitor parameters such as the battery capacity, the number of battery cycles, the state of health of the battery (leakage, impedance), and the like. In some embodiments, the power management module 141 can also be disposed in the processor 110. In some other embodiments, the power management module 141 and the charging management module 140 can be disposed in the same device.

[0096] The wireless communication function of the user device 100 can be implemented by the antenna 1, the antenna 2, the mobile communication module 150, the wireless communication module 160, the modem processor, and the baseband processor, and the like.

[0097] The mobile communication module 150 can provide a solution for wireless communication including 2G / 3G / 4G / 5G, and the like, applied to the user device 100. The mobile communication module 150 can include at least one filter, a switch, a power amplifier, a low noise amplifier (LNA), and the like. The mobile communication module 150 can receive electromagnetic waves from the antenna 1, filter, amplify, and the like, the received electromagnetic waves, and transmit the processed signals to the modem processor for demodulation. The mobile communication module 150 can also amplify signals modulated by the modem processor and radiate the signals as electromagnetic waves through the antenna 1. In some embodiments, at least part of the function modules of the mobile communication module 150 can be disposed in the processor 110. In some embodiments, at least part of the function modules of the mobile communication module 150 and at least part of the modules of the processor 110 can be disposed in the same device.

[0098] In some embodiments, antenna 1 and mobile communication module 150 of user equipment 100 are coupled, and antenna 2 and wireless communication module 160 are coupled, so that user equipment 100 can communicate with a network and other devices through wireless communication technology. The wireless communication technology can include global system for mobile communications (GSM), general packet radio service (GPRS), code division multiple access (CDMA), wideband code division multiple access (WCDMA), time-division code division multiple access (TD-SCDMA), long term evolution (LTE), BT, GNSS, WLAN, NFC, FM, and / or IR technology, etc. The GNSS can include global positioning system (GPS), global navigation satellite system (GLONASS), beidu navigation satellite system (BDS), quasi-zenith satellite system (QZSS), and / or satellite based augmentation systems (SBAS).

[0099] User equipment 100 implements display functions through a GPU, display screen 194, and an application processor, etc. The GPU is a microprocessor for image processing, connected to the display screen 194 and the application processor. The GPU is used to perform mathematical and geometric calculations for graphics rendering. Processor 110 can include one or more GPUs that execute program instructions to generate or change display information.

[0100] The display screen 194 is configured to display images, videos, and the like. The display screen 194 includes a display panel. The display panel can be a liquid crystal display (LCD), an organic light-emitting diode (OLED), an active-matrix organic light-emitting diode (AMOLED), a flex light-emitting diode (FLED), a Miniled, a MicroLed, a Micro-OLED, a quantum dot light emitting diode (QLED), or the like. In some embodiments, the user device 100 can include one or N display screens 194, where N is an integer greater than 1.

[0101] The user device 100 can implement a photographing function through an ISP, the camera 193, a video codec, a GPU, the display screen 194, and an application processor.

[0102] The internal memory 121 can be configured to store computer-executable program codes including instructions. The processor 110 executes various functional applications and data processing of the user device 100 by running the instructions stored in the internal memory 121. The internal memory 121 can include a program storage area and a data storage area. The program storage area can store an operating system, at least one application program required by a function (such as a sound playing function, an image playing function, and the like), and the like. The data storage area can store data (such as audio data, a phone book, and the like) created during use of the user device 100, and the like. In addition, the internal memory 121 can include a high-speed random access memory, and can further include a non-volatile memory such as at least one of a magnetic disk storage device, a flash memory device, a universal flash storage (UFS), and the like.

[0103] The user device 100 can implement an audio function such as music playing, voice recording, and the like through an audio module 170, a speaker 170A, a receiver 170B, a microphone 170C, an earphone interface 170D, and an application processor.

[0104] The audio module 170 is configured to convert digital audio information into analog audio signals for output, and to convert analog audio input into digital audio signals. The audio module 170 can also be configured to encode and decode audio signals. In some embodiments, the audio module 170 can be disposed in the processor 110, or some of the functions of the audio module 170 can be disposed in the processor 110.

[0105] The temperature sensor 180J is configured to detect temperature. In some embodiments, the user device 100 uses the temperature detected by the temperature sensor 180J to implement temperature handling strategies. For example, when the temperature reported by the temperature sensor 180J exceeds a threshold, the user device 100 reduces the performance of the processor located near the temperature sensor 180J to reduce power consumption and implement thermal protection. In other embodiments, when the temperature is lower than another threshold, the user device 100 heats the battery 142 to avoid abnormal shutdown of the user device 100 caused by low temperature. In other embodiments, when the temperature is lower than yet another threshold, the user device 100 boosts the output voltage of the battery 142 to avoid abnormal shutdown caused by low temperature.

[0106] The touch sensor 180K, also referred to as a "touch panel". The touch sensor 180K can be disposed on the display screen 194, and the touch sensor 180K and the display screen 194 together form a touch screen, also referred to as a "touch panel". The touch sensor 180K is configured to detect touch operations acting on or near the touch sensor 180K. The touch sensor 180K can transmit the detected touch operation to the application processor to determine the type of touch event. Visual output related to the touch operation can be provided through the display screen 194. In other embodiments, the touch sensor 180K can also be disposed on the surface of the user device 100, which is different from the position where the display screen 194 is located.

[0107] The keys 190 include a power key, a volume key, and the like. The keys 190 can be mechanical keys or touch keys. The user device 100 can receive key inputs and generate key signal inputs related to user settings and function control of the user device 100.

[0108] The SIM card interface 195 is configured to connect a SIM card. The SIM card can be inserted into or removed from the SIM card interface 195 to achieve contact and separation with the user equipment 100. The user equipment 100 can support one or N SIM card interfaces, where N is an integer greater than 1. The SIM card interface 195 can support Nano SIM cards, Micro SIM cards, SIM cards, and the like. The same SIM card interface 195 can simultaneously insert multiple cards. The types of the multiple cards can be the same or different. The SIM card interface 195 can also be compatible with different types of SIM cards. The SIM card interface 195 can also be compatible with external storage cards. The user equipment 100 interacts with the network through the SIM card to achieve functions such as call and data communication. In some embodiments, the user equipment 100 uses an eSIM, i.e., an embedded SIM card. The eSIM card can be embedded in the user equipment 100 and cannot be separated from the user equipment 100.

[0109] Voice call is a communication connection between user equipment established through a communication network. The communication connection can be established through the 2nd Generation Mobile Communication Technology (2G), the 3rd Generation Mobile Communication Technology (3G), the 4th Generation Mobile Communication Technology (4G), or the 5th Generation Mobile Communication Technology (5G). Among them, when the communication connection is established through the 2G or 3G technology, it is generally implemented in the Circuit Switched (CS) domain; when the communication connection is established through the 4G or 5G technology, it is generally implemented in the Internet Protocol (IP) Multimedia Subsystem (IMS) domain.

[0110] Due to different development levels of network communication in different regions, voice calls using CS domain and IMS domain coexist. In order to improve the call success rate of voice call service, a user equipment (UE) generally sets a CS call redial mechanism. Under the CS redial mechanism, if the UE fails to call in the IMS domain, the UE attempts to search for a CS domain network, and when the search is successful, the UE performs call redial on the CS domain, that is, continues to call through the CS domain. At this time, the user interface (UI) is not aware of the call redial, and therefore, the user only perceives a call process.

[0111] However, with the development of network technology, 2G and 3G networks are gradually being replaced by more advanced 4G and 5G networks. Therefore, the CS domain is gradually being replaced by the IMS domain, and in some regions, there is no CS domain network coverage. In this case, if call redial is continued by searching for the CS domain after a call in the IMS domain fails, the search for the network fails, the call redial cannot be successful, and accordingly, the UI displays a signal anomaly, resulting in poor user experience. For example, refer to Figure 2 which shows a UI interface display when call redial fails to search for a network. The UI interface displays a signal symbol 10, which indicates that there is currently no signal. The UI interface can also optionally display a dialing failure prompt box 20, which displays prompt information such as "dialing failure, do you want to redial" and the like. The dialing failure prompt box 20 can also display a cancel button and a retry button. When a triggering operation on the cancel button is detected, dialing is canceled and the dialing interface is exited. When a triggering operation on the retry button is detected, dialing is reattempted, and in this reattempted dialing, the call is initiated from the IMS domain.

[0112] To optimize user experience, the present application provides a call method that can take into account both user call experience and network display experience. That is, call redial is performed as much as possible when CS call redial is needed, to ensure user call success, and when it is predicted that call redial is ineffective, CS domain call redial is not performed, thereby avoiding the abnormal situation of displaying no signal when call redial is performed due to the inability to search for a 2G or 3G network.

[0113] Specifically, in the process of network registration, the type of network registered by the UE in the current network environment is recorded, and when a call in the IMS domain fails, it is determined whether to initiate call redial according to the registered network type. When the UE successfully registers in the CS domain, call redial is initiated, and when the UE fails to register in the CS domain, call redial is not initiated, thereby avoiding the user interface displaying a signal anomaly when call redial is performed due to the inability to search for a CS domain network, and further optimizing the user's network display experience.

[0114] When a voice call is made, whether the voice call is made in an IMS domain or a CS domain, the UE needs to be successfully registered in the corresponding network. For the CS domain, the user equipment can be registered in the network corresponding to the CS domain. For the IMS domain, since the IMS domain is based on IP bearer, which is superimposed on the packet domain (PS), registration in the network corresponding to the PS domain is required.

[0115] Referring to Figure 3 , which shows the interaction process between the UE and the core network in a network registration process. When the UE triggers network registration, a registration request (attach request) is sent to the core network. The core network performs authentication on the registration request. When the authentication is passed, the core network sends a registration response (attach accept) to the UE. After receiving the registration response sent by the core network, the UE sends a registration completion notification (attach complete) to the core network, and the registration is completed.

[0116] In actual application, the UE can record some parameter information generated in the registration process. Referring to Figure 4 , which shows a process of network registration of the UE provided in an embodiment of the present application.

[0117] A1. When the UE performs initial network registration in a network environment, a registration request is sent to the core network. The registration request carries a registration type identifier. The value of the registration type identifier is used to indicate the network type requested to be registered in this network registration.

[0118] For some regions where CS domain network is completely withdrawn, the operator generally requires that the UE sends a PS domain registration request for registering the PS domain network only, i.e., the value of the registration type identifier in the registration request indicates that the type of the network requested to be registered in this network registration is the PS domain. For some regions where CS domain network has not been withdrawn or partially withdrawn, the operator generally requires that the UE sends a combined registration request for registering the PS domain network and the CS domain network, i.e., the value of the registration type identifier in the registration request indicates that the type of the network requested to be registered in this network registration is the PS domain and the CS domain. Correspondingly, in some embodiments, when the UE needs to perform network registration, the UE acquires a preset registration type identifier based on the Public Land Mobile Network (PLMN) information of a subscriber identity card used by the UE; and generates a registration request based on the registration type identifier. The subscriber identity card is a card provided by an operator and matched with the number of a user. For example, the subscriber identity card is an Integrated Circuit Card (IC) card held by a user of a Global System for Mobile Communications (SIM), such as a Subscriber Identity Module (SIM) card.

[0119] For example, when the operator of the region where the UE is located requires only PS domain network registration, it is determined that the value of the registration type identifier is 1; and when the operator of the region where the UE is located requires PS domain and CS domain network registration, it is determined that the value of the registration type identifier is 2. When the value of the registration type identifier is 1, it indicates that the registration request is a PS domain registration request (eps attach), i.e., the UE requests to perform network registration in the PS domain; and when the value of the registration type identifier is 2, it indicates that the registration request is a combined registration request (combined attach), i.e., the UE requests to perform network registration in both the CS domain and the PS domain. Moreover, the registration type identifier is marked in a corresponding field of the registration request, for example, the registration type identifier can be in the EPSattach type information element field of the registration request.

[0120] It should be noted that the timing of network registration of the UE can be determined by various factors such as the network type of the region where the UE is located, device configuration, user behavior, etc. For example, the UE performs network registration when it is initially powered on. Or, the UE needs to perform network registration when network switching occurs, such as switching from 3G to 4G, switching from one operator to another, etc. Or, the UE can need to perform network registration again when it becomes out of service. In the embodiments of the present application, the timing of network registration of the UE is not limited.

[0121] The core network can be a network element device provided by an operator, for example, a network element device based on Long Term Evolution (LTE) technology provided by an operator, which is not specifically limited in the embodiments of the present application.

[0122] A2, the UE records the registration type identification in the registration request locally.

[0123] The UE can store the complete content of the registration request in the local storage space, or the UE stores the registration type identification corresponding field in the registration request in the local storage space. In the embodiments of the present application, this is not specifically limited.

[0124] A3, the core network receives the registration request.

[0125] The core network receives the registration request sent by the UE.

[0126] A4, the core network authenticates the UE based on the registration request.

[0127] In network registration, authentication of the UE can verify whether the UE has legal access rights, prevent illegal UEs from accessing the network, and provide secure communication connection for legal UEs. The authentication method can be set as needed, and in the embodiments of the present application, the authentication method is not specifically limited.

[0128] Through authentication, the core network can confirm the identity of the UE, and decide whether to allow the UE to access the network according to the authentication result. This helps to prevent illegal intrusion and abuse of network resources, and protects the integrity and reliability of the network.

[0129] If the authentication fails, the UE registration fails; if the authentication succeeds, the core network registers the UE, for example, allocates a temporary identifier to the UE, updates user information, generates a permanent identifier, etc., and then the core network performs step A5.

[0130] A5, the core network sends a registration response to the UE, the registration response carries a registration result identification, and the value of the registration result identification represents the network type of this network registration.

[0131] The core network registers the UE according to the type of the network requested to be registered in the registration request and the type of the network covered by the current network environment. After the registration is completed, a registration response is sent to the UE, which carries a registration result identifier. The value of the registration result identifier indicates the type of the network registered in this network registration. For example, when the value of the registration result identifier is 1, it indicates that only the PS domain network is successfully registered; when the value of the registration result identifier is 2, it indicates that both the CS domain network and the PS domain network are successfully registered. The registration result identifier is marked in the corresponding field of the registration response, for example, in the EPS attach result information element field of the registration response.

[0132] As described above, the types of the registration request include the PS domain registration request and the joint registration request. The types of the networks covered in different network environments can also be different. For example, only the PS domain network is covered, or both the PS domain network and the CS domain network are covered. Therefore, different registration requests combined with the types of the networks covered in different network environments can result in different registration results. The registration results are described below in combination with different registration requests and the types of the networks covered in different network environments.

[0133] In the case of the PS domain registration request:

[0134] In the first case, the environment network only covers the PS domain network, and after the registration is successful, the registration result indicates that the PS domain registration is successful, i.e., the value of the registration result identifier is 1.

[0135] In the case of the joint registration request:

[0136] In the second case, the environment network covers both the PS domain network and the CS domain network, but only the PS domain network is successfully registered, and the registration result indicates that the PS domain registration is successful, i.e., the value of the registration result identifier is 1.

[0137] In the third case, the environment network covers both the PS domain network and the CS domain network, and both the PS domain network and the CS domain network are successfully registered, and the registration result indicates that both the PS domain network and the CS domain network are successfully registered, i.e., the value of the registration result identifier is 2.

[0138] A6. The UE receives the registration response sent by the core network.

[0139] A7. The UE stores the registration result identifier in the registration response.

[0140] In some embodiments, after receiving the registration response sent by the core network, the UE stores the registration response. In other embodiments, after receiving the registration response sent by the core network, the UE reads the registration result identifier from the result field of the registration response and stores the registration result identifier. In the embodiments of the present application, the way in which the UE stores the registration result identifier is not limited.

[0141] In the implementation, the UE adds a registration type identifier in a registration request when performing network registration, and the core network adds a result type identifier in a registration response when feeding back the registration response to the UE. The registration type identifier records the type of the network for which registration is requested in the current network registration, and the registration result identifier records the type of the network for which registration is successfully performed in the current network registration. In this way, the registration type identifier and the registration result identifier of the current network registration are stored respectively, so that the UE can determine whether the CS domain network is successfully registered currently according to the stored registration type identifier and registration result identifier when call retry is performed, and further determine whether to initiate call retry in the CS domain when call initiation in the IMS domain fails, thereby avoiding the problem of signal display failure due to blind call retry in the CS domain when the CS is not successfully registered, ensuring the call experience of the user, considering the network display experience, and thereby optimizing the user experience.

[0142] As described above, for some regions where the CS domain network is completely retired, the operator generally requires that the UE sends a PS domain registration request for registering only the PS domain network. For some regions where the CS domain has not been retired or has been partially retired, the operator generally requires that the UE sends a joint registration request for registering the PS domain network and the CS domain network. The core network determines the registration result of the UE according to the registration request and the current network coverage, and then feeds back a registration response to the UE. Therefore, when the registration response shows that the PS domain registration is successful, the network environment may cover only the PS domain network, or may cover both the PS domain network and the CS domain network.

[0143] Therefore, for the third case described above, when the UE is successfully registered in both the PS domain and the CS domain, it indicates that the UE can successfully establish a connection with the PS domain network and the CS domain network. Therefore, when call initiation in the IMS domain fails, the call retry mechanism in the CS domain can be started. When the UE is successfully registered in the PS domain only, the following two cases may occur:

[0144] For the first case described above, only the PS domain network exists in the current network environment. Therefore, when call initiation in the IMS domain fails, the call retry mechanism in the CS domain is not started.

[0145] For the second case, when the registration result indicates that the UE is successfully registered in the PS domain network, the current area cannot exclude the coverage of the CS network. The CS domain registration fails due to different reasons, for example, the CS domain network failure causes the registration failure. Therefore, even if the UE fails to register in the CS domain initially, it can be successfully registered again after the subsequent CS domain network recovers. In order to reduce the number of times of initiating the CS call retry and reduce the risk of the UE displaying no signal as much as possible, the application determines whether to initiate the CS call retry by combining more preset conditions when the CS domain registration fails.

[0146] In summary, the application provides a voice call method for determining whether to initiate the CS call retry by combining the registration request and the registration result when the call initiated in the IMS domain fails. Referring to Figure 5 which shows a flowchart of the voice call method provided by the embodiment of the application. The voice call method is applied to the case where the UE fails to initiate the call in the IMS domain. Referring to Figure 5 After the UE completes the initial network registration, when the call initiated in the IMS domain fails, it is determined whether the registration request is the PS domain registration request (eps attach). If the registration request is the PS domain registration request, the CS call retry is not initiated. If the registration request is the joint registration request, it is further determined whether the registration result in the registration response corresponding to the registration request indicates that the UE is successfully registered in both the PS domain and the CS domain. If the registration response indicates that the UE is successfully registered in both the PS domain and the CS domain, the CS call retry is initiated. If the registration response indicates that the UE is successfully registered in the PS domain only, it is further determined whether to initiate the CS call retry by combining more preset conditions.

[0147] The preset conditions can be set as required, and the content of the preset conditions is not limited in the embodiment of the application. For example, in some embodiments, the preset condition is that the number of the current call is the target number. Accordingly, when the registration request is the joint registration request and the registration response indicates that the UE is successfully registered in the PS domain only, the UE determines whether the number of the current call is the target number. If the number is the target number, the CS call retry is initiated. If the number is not the target number, the CS call retry is not initiated.

[0148] The target number is a number defined by a user. For example, the target number is a number with high priority, such as a number collected by the user, a public service number, or the like, that is, for the target number, call connection is preferentially ensured. In the embodiments of the present application, the target number is not limited. When the registration request is a joint registration request and the registration response indicates that the UE is successfully registered in the PS domain only, it cannot be excluded that the local area is covered by the CS domain network, and therefore, the CS domain network search can be attempted to attempt the call retry of the CS domain. When the number of the call is the target number, the call retry of the CS domain is attempted, the call success rate for the target number is improved, and when the number is not the target number, the call retry of the CS domain is not performed, the probability of network search failure in the call retry of the CS domain is reduced, and therefore, the user experience is optimized.

[0149] In some other embodiments, the preset condition is that the UE is in a screen-off state. Accordingly, when the registration request is a joint registration request and the registration response indicates that the UE is successfully registered in the PS domain only, it cannot be completely excluded that the local area is covered by the CS domain network, the UE determines whether the UE is currently in the screen-off state, if the UE is currently in the screen-off state, the call retry of the CS domain is initiated, and if the UE is not currently in the screen-off state, the call retry of the CS domain is not initiated. When the UE is in the screen-off state, even if the call retry of the CS domain is initiated, the network search fails, the UE does not display the network search failure page, and the user experience is not affected. Therefore, when the UE is in the screen-off state, the call retry of the CS domain is initiated, and when the UE is in the screen-on state, the call retry of the CS domain is not initiated, the call success rate is improved, and the user experience is not affected.

[0150] In some other embodiments, the preset condition is that the current area CS domain call retry success rate is greater than a preset value. Accordingly, when the registration request is a joint registration request and the registration response indicates that the UE is successfully registered in the PS domain only, the UE acquires the historical call data pushed by the cloud, the historical call data includes the success rate of the call retry of the CS domain in the current area, if the success rate is greater than the preset value, the call retry of the CS domain is initiated, and if the success rate is not greater than the preset value, the call retry of the CS domain is not initiated.

[0151] The cloud can be a big data server of a vendor of the UE. The historical call data pushed by the cloud includes call retry results of a plurality of UEs developed by the vendor in the current area in the CS domain. The call retry result is success or failure of a call in the CS domain. The UE determines a success rate of call retry in the current area in the CS domain according to the historical call result, and determines whether to initiate call retry in the CS domain based on whether the success rate is greater than a preset value. The preset value can be set as needed, and in the embodiments of the present application, the preset value is not specifically limited. For example, the preset value can be 80%, 85%, or 90%, etc. In this way, the success rate of call retry in the current area in the CS domain is used to determine whether to perform call retry, thereby preventing call retry in the CS domain when the success rate of call retry is low, resulting in a low success rate of call retry and thus a no-signal display problem. When the success rate of call retry in the CS domain is greater than the preset value, call retry is performed, thereby improving the probability of call retry success and reducing the probability of a no-signal display problem due to call retry failure, and optimizing user experience.

[0152] In some other embodiments, the preset condition is that the number of times of calling the current number in a preset time period is greater than a preset number of times. Accordingly, when the registration request is a joint registration request and the registration response indicates that the UE is successfully registered in the PS domain only, the UE determines the number of times of calling the current number in a preset time period, and initiates call retry in the CS domain when the number of times of calling the number in the preset time period is greater than the preset number of times, and does not initiate call retry in the CS domain when the number of times of calling the number in the preset time period is not greater than the preset number of times.

[0153] If the number of times of calling the current number in a preset time period reaches the preset number of times, the user has a greater expectation of successfully establishing voice communication with the number, and therefore, when the UE fails to call the number in the IMS, in order to meet the demand, call retry is continued in the CS domain. In this way, the probability of a no-signal display problem due to call retry failure is reduced, user experience is optimized, and the probability of call success for a number that is called more than the preset number of times is improved.

[0154] The preset time period and the preset number of times can be set as needed, and in the embodiments of the present application, the preset time period and the preset number of times are not specifically limited. For example, the preset time period can be 1 hour, 2 hours, etc. The preset number of times can be 10 times, 15 times, etc.

[0155] It should be noted that the above embodiments of the plurality of preset conditions are exemplary embodiments provided by the present application, and in actual application, the UE can determine more or fewer conditions, which are not specifically limited in the embodiments of the present application. Moreover, the UE can select at least one of the plurality of preset conditions to determine. When the UE selects a plurality of preset conditions to determine, the UE can simultaneously determine whether each preset condition is satisfied, and when at least one preset condition is satisfied, the UE performs the call retry in the CS domain, and when none of the preset conditions is satisfied, the UE does not perform the call retry in the CS domain.

[0156] When the UE selects a plurality of preset conditions to determine, the UE can also determine whether the UE satisfies the preset conditions in sequence according to a preset order. Referring to Figure 6 FIG. 1 shows a flowchart of a voice call method according to an exemplary embodiment of the present application. In the present implementation, when the registration request is a joint registration request and the registration response indicates that the UE is successfully registered in the PS domain only, the UE first determines whether the current number is the target number, and if the number is the target number, the UE performs the call retry in the CS domain, and if the number is not the target number, the UE continues to determine whether the UE is currently in the screen-off state, and when the UE is in the screen-off state, the UE performs the call retry in the CS domain, and when the UE is in the screen-on state, the UE acquires historical call data, and when the success rate of the UE performing the call retry in the CS domain in the current area in the historical call data is greater than a preset value, the UE performs the call retry in the CS domain, and otherwise, the UE does not perform the call retry in the CS domain.

[0157] It should be noted that in the process of determining whether to perform the call retry in the CS domain based on the plurality of preset conditions, the number of preset conditions and the order of determination can be set as needed, which are not specifically limited in the embodiments of the present application.

[0158] In the present implementation, the plurality of preset conditions are used to determine whether to perform the call retry in the CS domain, so that when the IMS domain call fails, the UE does not directly attempt the call retry in the CS domain, and the UE performs the call retry in the CS domain only when the conditions are satisfied, thereby meeting the requirement of improving the call success rate by the call retry in the CS domain when the IMS domain call fails, and effectively preventing the problem of no signal display caused by the failure of searching for the CS domain network due to the network withdrawal of the CS domain, thereby optimizing the user experience.

[0159] The voice call process of the UE is described below in combination with a specific flow. Referring to Figure 7 FIG. 1 shows a flowchart of a voice call method according to an exemplary embodiment of the present application.

[0160] B1, the UE initiates a call in the IMS domain.

[0161] In response to the UE receiving the voice call instruction, a voice call is initiated to other UEs. It should be noted that the call initiated by the UE in the IMS domain can be a call between an IMS domain user and an IMS domain user, or a call between an IMS domain user and a CS domain user, which is not limited in the embodiments of the present application.

[0162] B2. When the UE fails to initiate a call in the IMS domain, the UE acquires the registration type identifier of the registration request.

[0163] After the UE completes the registration, the registration type identifier of the registration request is stored locally, and in this step, the UE acquires the registration type identifier stored locally.

[0164] B3. When the registration type identifier indicates that the registration request is a PS domain registration request, the UE does not perform call retry in the CS domain.

[0165] Based on the requirements of the operator, in general, when the registration request is a PS domain only registration request, the current region only covers a PS domain network, and therefore, the UE does not perform call retry in the CS domain. In this way, when a voice call fails in a region that only covers a PS domain network, the search for a CS domain network fails due to the continued attempt of call retry in the CS domain, and the UE displays no signal, thereby optimizing the user experience.

[0166] B4. When the registration type identifier indicates that the registration request is a joint registration request, the UE acquires the registration result identifier.

[0167] When the registration type identifier indicates that the registration request is a joint registration request, it means that the CS and PS networks are both covered for the entire operator, but different regions can be different. Then, whether to perform call retry in the CS domain can be determined according to the registration result of the UE this time.

[0168] B5. When the registration result identifier indicates that the UE successfully registers the PS domain network and the CS domain network, the UE performs call retry in the CS domain.

[0169] When the registration result identifier indicates that the UE successfully registers the PS domain network and the CS domain network, it is determined that the current region covers the PS domain network and the CS domain network, and the UE registers successfully in the CS domain, and the success rate of call retry in the CS domain is greatly improved. Therefore, the success rate of call retry in the CS domain is improved, the risk of the UE displaying no signal due to the failure of the CS domain is reduced, and the user experience is further optimized.

[0170] B6. When the registration result identifier indicates that the UE successfully registers the PS domain network, the UE acquires the number of the current call.

[0171] In some embodiments, after the UE initiates a call event, the UE records information related to the current voice call during the process of establishing the voice call, the information including the number of the current call. Accordingly, the UE acquires the information related to the current voice call, and acquires the number of the current call from the information.

[0172] After the UE acquires the number of the current call, the UE determines whether the number is a target number. If the number is the target number, the UE proceeds to step B7. If the number is not the target number, the UE proceeds to step B8. The target number is a number defined by the user. For example, the target number is a number saved by the user, a public service number, etc. In the embodiments of the present application, the target number is not limited.

[0173] B7, if the number is the target number, the UE performs call retry in the CS domain.

[0174] When the number of the call is the target number, the UE attempts to perform call retry in the CS domain, thereby improving the call success rate for the target number.

[0175] In the case where the registration result identifier indicates that the UE successfully registers the PS domain network, since the UE fails to register the initial network in the CS domain, before the UE performs call retry in the CS domain, the UE needs to attempt to register the network in the CS domain, and only when the registration is successful, the UE initiates call retry in the CS domain.

[0176] B8, if the number is not the target number, the UE determines the current screen state.

[0177] When the number is not the target number, the UE continues to determine the current screen state of the UE. When the screen state is the screen-off state, the UE proceeds to step B9. When the screen state is the screen-on state, the UE proceeds to step B10.

[0178] B9, if the UE is in the screen-off state, the UE performs call retry in the CS domain.

[0179] In this step, the principle of performing call retry in the CS domain by the UE is the same as that in step B7, and thus is not described herein.

[0180] When the UE is in the screen-off state, the UE initiates call retry in the CS domain, but does not display a page indicating network search failure even if the UE fails to search for the network, thereby not affecting the user experience. Therefore, when the UE is in the screen-off state, the UE initiates call retry in the CS domain, and when the UE is in the screen-on state, the UE does not initiate call retry in the CS domain, thereby improving the call success rate and not affecting the user experience.

[0181] B10, if the UE is in the screen-on state, the UE acquires historical call data.

[0182] When the UE is in the bright screen state, the UE continues to acquire the historical call data of the CS domain of the current area. The historical call data includes the call retry results of a plurality of UEs in the CS domain of the current area. The call retry result is a call success or failure in the CS domain.

[0183] The UE determines the success rate of the UE performing the CS call retry in the current area according to the historical call retry result. When the success rate is greater than a preset value, the UE performs step B11. When the success rate is not greater than the preset value, the UE performs step B12.

[0184] The preset value can be set as needed, and in the embodiments of the present application, the preset value is not specifically limited. For example, the preset value can be 80%, 85%, or 90%, etc.

[0185] B11, if the call success rate of the CS domain in the historical call data is greater than the preset value, the UE performs the call retry in the CS domain.

[0186] The principle of the UE performing the call retry in the CS domain in this step is the same as that of the UE performing the call retry in the CS domain in step B7, and will not be described here.

[0187] B12, if the call success rate of the CS domain in the historical call data is not greater than the preset value, the UE does not perform the call retry in the CS domain.

[0188] The success rate of the CS domain call in the current area is determined to determine whether to perform the call retry, thereby preventing the problem of low success rate of the call retry caused by the low success rate of the CS domain call, and thereby preventing the problem of abnormal display. When the success rate of the CS domain call is greater than the preset value, the call retry is performed, thereby improving the probability of the call retry success and reducing the probability of the display of no signal caused by the failure of the call retry, and optimizing the user experience.

[0189] In summary, in the embodiments of the present application, the type of the registration request and the type of the registration result are recorded in the network registration process. When the IMS domain call fails, whether to perform the call retry in the CS domain is determined according to the type of the registration request and the type of the registration result. Only when the registration request is a joint request and the registration result is that the PS domain network and the CS domain network are successfully registered, the call retry in the CS domain is performed when the IMS domain call fails, thereby reducing the problem of the UE displaying no signal caused by the failure of the CS domain search network, and optimizing the display experience of the user.

[0190] Further, when the registration request is a joint registration request and the registration result is only a PS domain registration success, whether to continue to attempt the call retry of the CS domain is determined by preset conditions when the call in the IMS domain fails, so as to guarantee the requirement of the call retry as much as possible, and to reduce the problem of UE display signal loss caused by the CS domain search failure to a certain extent, thereby guaranteeing the call experience of the user and the display experience of the user.

[0191] Figure 8 is a structural schematic diagram of a voice call device provided by an embodiment of the present application. The device can be realized by software, hardware or a combination of both to become part or all of a computer device. The computer device can be a user equipment as shown in Figure 1 . Referring to Figure 8 , the device comprises:

[0192] A determining module 810 is configured to determine a registration type identifier of a registration request of a user equipment (UE) in a current area in response to a failure of initiating a voice call in an Internet Protocol Multimedia Subsystem (IMS) domain, the registration request being a registration request sent to a core network when the UE performs network registration in the current area.

[0193] A control module 820 is configured to end the voice call and not perform a call retry in a CS domain if the registration type identifier indicates that the registration request is a PS domain registration request, the PS domain registration request being used to request network registration in a PS domain.

[0194] In some embodiments, the device further comprises:

[0195] A first obtaining module is configured to obtain a registration result identifier if the registration type identifier indicates that the registration request is a joint registration request.

[0196] The control module 820 is further configured to continue to perform the voice call based on the CS domain if the registration result identifier indicates that the UE has successfully registered the PS domain network and the CS domain network in the current area.

[0197] In some embodiments, the device further comprises:

[0198] A second obtaining module is configured to obtain a number of the current voice call if the registration result identifier indicates that the UE has successfully registered the PS domain network in the current area, the joint registration request being used to request registration of the PS domain network and a CS domain network.

[0199] The control module 820 is further configured to end the voice call and not perform the call retry in the CS domain if the number of the current voice call is not a preset target number, and to continue to perform the call retry based on the CS domain if the number of the current voice call is the preset target number.

[0200] In some embodiments, the apparatus further includes:

[0201] a third obtaining module, configured to obtain a current screen state of the UE if the registration result identifier indicates that the UE has successfully registered the PS domain network in the current region;

[0202] The control module 820 is further configured to end the voice call and not perform the CS domain call retry if the screen state is the screen-on state, and continue the call retry based on the CS domain if the screen state is the screen-off state.

[0203] In some embodiments, the apparatus further includes:

[0204] a fourth obtaining module, configured to obtain historical call data of the current region if the registration result identifier indicates that the UE has successfully registered the PS domain network in the current region, the historical call data including a success rate of the CS domain call retry in the current region;

[0205] The control module 820 is further configured to end the voice call and not perform the CS domain call retry if the success rate is not greater than a preset value, and continue the call retry based on the CS domain if the success rate is greater than the preset value.

[0206] In some embodiments, the determining module 810 includes:

[0207] a first obtaining unit, configured to obtain the registration request sent by the UE from a local storage unit;

[0208] a second obtaining unit, configured to obtain a target field of a user-annotated registration type in the registration request;

[0209] a determining unit, configured to determine the registration type identifier from content of the target field.

[0210] In some embodiments, the control module 820 includes:

[0211] a display unit, configured to end the voice call process and exit a voice call interface.

[0212] In some embodiments, the apparatus further includes:

[0213] a fifth obtaining module, configured to obtain a preset registration type identifier based on public land mobile network (PLMN) information of a user identification card used by the UE;

[0214] a generating module, configured to generate a registration request based on the registration type identifier;

[0215] a sending module, configured to send the registration request to a core network, the core network being a network element device corresponding to an operator of the current region;

[0216] receive the registration response fed back by the core network, the registration response comprising a registration result identifier;

[0217] a storage module configured to store the registration request and the registration response.

[0218] In the embodiments of the present application, when the call in the IMS domain fails, whether to perform the call retry in the CS domain is determined in combination with the type of the registration request and the type of the registration result. Only when the registration request is a joint request and the registration result is that the UE is successfully registered in both the PS domain network and the CS domain network, the call retry in the CS domain is performed when the call in the IMS domain fails. Thus, the problem of the UE displaying no signal caused by the failure of searching for the network in the CS domain is reduced, and the display experience of the user is optimized.

[0219] Further, when the registration request is a joint registration request and the registration result is that only the registration in the PS domain is successful, whether to continue to attempt the call retry in the CS domain is determined by a preset condition when the call in the IMS domain fails. In this way, the demand for the call retry is ensured as much as possible, and the problem of the UE displaying no signal caused by the failure of searching for the network in the CS domain is reduced to a certain extent. Thus, the call experience of the user is ensured, and the display experience of the user is ensured.

[0220] It should be noted that: when the voice call device provided in the above embodiments performs voice calling, only the division of the above functional modules is taken as an example for illustration. In actual application, the above functions can be completed by different functional modules according to needs, that is, the internal structure of the device is divided into different functional modules to complete all or part of the functions described above.

[0221] Each functional unit and module in the above embodiments can be integrated in one processing unit, or each unit can exist physically, or two or more units can be integrated in one unit. The integrated unit can be realized in the form of hardware or in the form of a software functional unit. In addition, the specific names of the functional units and modules are only used for mutual distinction, and do not serve to limit the protection scope of the embodiments of the present application.

[0222] The boot device of the electronic device and the boot method of the electronic device provided in the above embodiments belong to the same concept. The specific working process of the units and modules in the above embodiments and the resulting technical effects can be referred to the method embodiment part, which will not be repeated here.

[0223] In the above embodiments, all or part of the embodiments can be implemented by software, hardware, firmware or any combination thereof. When implemented by software, all or part of the embodiments can be implemented in the form of a computer program product. The computer program product includes one or more computer instructions. When the computer instructions are loaded and executed on a computer, all or part of the processes or functions described in the embodiments of the present application are generated. The computer can be a general purpose computer, a special purpose computer, a computer network or other programmable apparatus. The computer instructions can be stored in a computer readable storage medium or transmitted from one computer readable storage medium to another computer readable storage medium, such as the computer instructions can be transmitted from one website site, computer, server or data center to another website site, computer, server or data center through wired (such as coaxial cable, optical fiber, digital subscriber line (DSL)) or wireless (such as infrared, wireless, microwave, etc.) mode. The computer readable storage medium can be any available medium accessible by a computer, or a data storage device such as a server, data center, etc. integrated with one or more available media. The available media can be magnetic media (such as floppy disk, hard disk, magnetic tape), optical media (such as digital versatile disc (DVD)) or semiconductor media (such as solid state disk (SSD)) and the like.

[0224] The above is an optional embodiment provided by the present application, and is not used to limit the present application. Any modification, equivalent replacement, improvement, etc. made within the technical scope disclosed by the present application shall be included in the protection scope of the present application.

Claims

1. A voice call method, characterized by, The method comprises: In response to a voice call initiation failure in an Internet Protocol Multimedia Subsystem (IMS) domain, determining a registration type identifier of a registration request of a user equipment (UE) in a current area, the registration request being a registration request sent by the UE to a core network when performing network registration in the current area; If the registration type identifier indicates that the registration request is a packet switched (PS) domain registration request, ending the voice call and not performing a circuit switched (CS) domain call retry, the PS domain registration request being used to request network registration in a PS domain.

2. The method of claim 1, wherein, The method further comprises: If the registration type identifier indicates that the registration request is a joint registration request, obtaining a registration result identifier, the joint registration request being used to request registration in a PS domain network and a CS domain network; If the registration result identifier indicates that the UE has successfully registered in the PS domain network and the CS domain network in the current area, continuing the call retry based on the CS domain.

3. The method of claim 2, wherein, The method further comprises: If the registration result identifier indicates that the UE has successfully registered in the PS domain network in the current area, obtaining a number of the current voice call; If the number of the current voice call is not a preset target number, ending the voice call and not performing the CS domain call retry; If the number of the current voice call is the preset target number, continuing the call retry based on the CS domain.

4. The method of claim 2, wherein, The method further comprises: If the registration result identifier indicates that the UE has successfully registered in the PS domain network in the current area, obtaining a current screen state of the UE; If the screen state is a screen-on state, ending the voice call and not performing the CS domain call retry; If the screen state is a screen-off state, continuing the call retry based on the CS domain.

5. The method of claim 2, wherein, The method further comprises: If the registration result identifier indicates that the UE has successfully registered in the PS domain network in the current area, obtaining historical call data of the current area, the historical call data comprising a success rate of the CS domain call retry in the current area; If the success rate is not greater than a preset value, ending the voice call and not performing the CS domain call retry; If the success rate is greater than the preset value, continuing the call retry based on the CS domain.

6. The method according to any one of claims 1 to 5, wherein, The determination of the registration type identifier of the registration request of the UE in the current area comprises: Obtaining the registration request sent by the UE from a local storage unit; Obtaining a target field of a user marked registration type in the registration request; Determining the registration type identifier from content of the target field.

7. The method according to any one of claims 1 to 5, wherein The ending of the voice call comprises: Ending a voice call process and exiting a voice call interface.

8. The method of any one of claims 1-5, wherein, The method further comprises: Obtaining a preset registration type identifier based on public land mobile network (PLMN) information of a user identification card used by the UE; Generating a registration request based on the registration type identifier; Sending the registration request to a core network, the core network being a network element device corresponding to an operator of the current area; Receiving a registration response fed back by the core network, the registration response comprising a registration result identifier; Storing the registration request and the registration response. 9.A user equipment, comprising: The user equipment comprises a processor coupled with a memory, the processor being configured to run a computer program stored in the memory to cause the user equipment to implement the method of any one of claims 1 to 8.

10. A computer-readable storage medium, characterized in that, The computer program is stored in the computer readable storage medium and, when run on the processor, implements the method of any one of claims 1 to 8.

Images