IMS registration method and device

Abstract

The invention provides an IMS registration method and device, and the method comprises the steps: transmitting IMS registration request information to network side equipment, determining whether an operator of the network side equipment deploys a circuit domain network or not based on a pre-configured network list in response to the received PDN request failure information transmitted by the network side equipment, and transmitting the IMS registration request information to the network side equipment under the condition that the operator does not deploy the circuit domain network. And based on a pre-configured re-registration operation corresponding to the PDN request failure information, re-initiating IMS registration until a first preset condition is satisfied. In the embodiment of the invention, under the condition that the PDN connection between the terminal equipment and the network side equipment fails, the circuit domain network deployment condition of an operator and PDN failure reason analysis are combined, the re-registration operation with higher pertinence is determined, the PDN connection success rate is improved, the IMS registration success rate and the resident network rate are further improved, the risk that a user cannot use a voice service is reduced, and the user experience is improved. And user experience is ensured.

Description

Technical Field

[0001] The present disclosure relates to the field of wireless communication technology, and in particular to an IMS registration method and device. Background Art

[0002] VoLTE (Voice over Long-Term Evolution) is a data transmission technology based on the Internet Protocol (IP) Multimedia Subsystem (IMS). This technology does not require 2G / 3G networks, and all VoLTE services are carried on the 4G LTE+IMS network.

[0003] Before using VoLTE services, terminals need to register with IMS. If IMS registration fails, VoLTE services on the IMS network cannot be used. With the general trend of 2G / 3G networks being phased out, telephone services based on 2G / 3G networks will inevitably shift completely to VoLTE services in the future. Therefore, improving the IMS registration success rate is an important means to increase the IMS network online rate. Summary of the invention

[0004] In order to improve the IMS registration success rate and thus improve the connection rate of VoLTE services based on the IMS network, the embodiments of the present disclosure provide an IMS registration method and apparatus, a terminal device, and a storage medium.

[0005] In a first aspect, an embodiment of the present disclosure provides an Internet Protocol Multimedia Subsystem IMS registration method, the method comprising:

[0006] Sending an IMS registration request message to a network side device, wherein the IMS registration request message includes a packet data network PDN connection request;

[0007] In response to receiving the PDN request failure information sent by the network side device, determining whether the operator of the network side device deploys a circuit domain network based on a pre-configured network list;

[0008] In the case that the operator has not deployed a circuit domain network, based on a pre-configured re-registration operation corresponding to the PDN request failure information, IMS registration is re-initiated until a first preset condition is met, wherein the first preset condition is used to indicate that the IMS registration is successful or multiple consecutive IMS registration failures.

[0009] In some implementations, determining whether the operator of the network side device deploys a circuit domain network based on a preconfigured network list includes:

[0010] Obtain the target operator of the network side device currently registered by the terminal device;

[0011] Based on the network list, determining network deployment information corresponding to the target operator;

[0012] Determine whether the target operator deploys a circuit domain network according to the network deployment information.

[0013] In some implementations, the IMS registration method described in the present disclosure further includes:

[0014] Receive the current network deployment information of each operator sent by the server;

[0015] The historically stored network list is updated according to the current network deployment information of each operator.

[0016] In some implementations, the re-initiating IMS registration based on a pre-configured re-registration operation corresponding to the PDN request failure information includes:

[0017] Determine a PDN failure type based on a protocol status code carried by the PDN request failure information;

[0018] Re-initiating IMS registration based on a pre-configured re-registration operation corresponding to the PDN failure type.

[0019] In some implementations, the re-initiating IMS registration based on a pre-configured re-registration operation corresponding to the PDN request failure information includes:

[0020] In a case where the PDN failure type corresponding to the PDN request failure information is response timeout, the cell identifier included in the IMS registration request information is replaced with another cell identifier, and the IMS registration request information is resent to the network side device.

[0021] In some implementations, the re-initiating IMS registration based on a pre-configured re-registration operation corresponding to the PDN request failure information includes:

[0022] In the case that the PDN failure type corresponding to the PDN request failure information is an IP type exception, the PDN IP type information included in the IMS registration request information is replaced with other IP type information, and the IMS registration request information is resent to the network side device.

[0023] In some implementations, the re-initiating IMS registration based on a pre-configured re-registration operation corresponding to the PDN request failure information includes:

[0024] In a case where the PDN failure type corresponding to the PDN request failure information is user authentication failure, the IMS registration request information is resent to the network side device after a preset time interval.

[0025] In some implementations, the first preset condition is that the IMS registration is successful, and the IMS registration method of the example of the present disclosure further includes:

[0026] Sending a VoLTE service request to a network-side device, wherein the VoLTE service request is used to request to establish a VoLTE call connection with a called device that has registered with the IMS;

[0027] In response to receiving a network error code sent by the network side device, determining whether an operator of the network side device deploys a circuit domain network based on a pre-configured network list;

[0028] In the case that the operator has not deployed a circuit domain network, based on a pre-configured target operation corresponding to the network error code, the VoLTE call connection with the called device is re-initiated until a second preset condition is met, wherein the second preset condition is used to indicate that the VoLTE call connection is successful or that the VoLTE call connection fails for multiple consecutive times.

[0029] In some implementations, the re-initiating the VoLTE call connection with the called device based on a pre-configured target operation corresponding to the network error code includes:

[0030] When the network error code indicates that the current network side device does not support the VoLTE service, the VoLTE service roaming request is sent to other network side devices.

[0031] In some implementations, the re-initiating the VoLTE call connection with the called device based on a pre-configured target operation corresponding to the network error code includes:

[0032] When the network error code indicates that the IMS network of the current terminal device is disconnected, an IMS registration request message is sent to the network side device, and after the IMS registration is successful, the VoLTE service request is resent to the network side device.

[0033] In some implementations, the re-initiating the VoLTE call connection with the called device based on a pre-configured target operation corresponding to the network error code includes:

[0034] In a case where the network error code indicates a temporary network error, the VoLTE service request is resent to the network side device after a preset time interval.

[0035] In a second aspect, an embodiment of the present disclosure provides an Internet Protocol Multimedia Subsystem IMS registration device, the device comprising:

[0036] A registration request module, configured to send an IMS registration request message to a network side device, wherein the IMS registration request message includes a packet data network PDN connection request;

[0037] A first network determination module is configured to determine, in response to receiving PDN request failure information sent by the network side device, whether the operator of the network side device deploys a circuit domain network based on a pre-configured network list;

[0038] The re-registration module is configured to re-initiate IMS registration based on a pre-configured re-registration operation corresponding to the PDN request failure information when the operator has not deployed a circuit domain network, until a first preset condition is met, wherein the first preset condition is used to indicate that the IMS registration is successful or multiple consecutive IMS registration failures.

[0039] In a third aspect, an embodiment of the present disclosure provides a terminal device, including:

[0040] Processor; and

[0041] A memory storing computer instructions, wherein the computer instructions are used to enable a processor to execute the method according to any embodiment of the first aspect.

[0042] In a fourth aspect, an embodiment of the present disclosure provides a storage medium storing computer instructions, wherein the computer instructions are used to enable the computer instructions to perform the method described in any embodiment of the first aspect.

[0043] The IMS registration method of the disclosed embodiment includes sending an IMS registration request message to a network side device, and in response to receiving a PDN request failure message sent by the network side device, determining whether the operator of the network side device has deployed a circuit domain network based on a pre-configured network list, and in the case where the operator has not deployed a circuit domain network, re-initiating the IMS registration based on a pre-configured re-registration operation corresponding to the PDN request failure message until a first preset condition is met. In the disclosed embodiment, in the case where the PDN connection between the terminal device and the network side device fails, a more targeted re-registration operation is determined in combination with the operator's circuit domain network deployment and the analysis of the cause of the PDN failure, thereby improving the PDN connection success rate, thereby improving the IMS registration success rate and the network resident rate, reducing the risk of users being unable to use voice services, and ensuring user experience. BRIEF DESCRIPTION OF THE DRAWINGS

[0044] In order to more clearly illustrate the specific embodiments of the present disclosure or the technical solutions in the prior art, the drawings required for use in the specific embodiments or the description of the prior art will be briefly introduced below. Obviously, the drawings described below are some embodiments of the present disclosure. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying any creative work.

[0045] Figure 1 It is a schematic diagram of a network architecture according to some implementation modes of the present disclosure.

[0046] Figure 2 FIG. 4 is a flowchart of an IMS registration method according to some implementations of the present disclosure.

[0047] Figure 3 FIG. 4 is a flowchart of an IMS registration method according to some implementations of the present disclosure.

[0048] Figure 4 It is a schematic diagram of a network architecture according to some implementation modes of the present disclosure.

[0049] Figure 5 FIG. 4 is a flowchart of an IMS registration method according to some implementations of the present disclosure.

[0050] Figure 6 FIG. 4 is a flowchart of an IMS registration method according to some implementations of the present disclosure.

[0051] Figure 7 It is a flowchart of a VoLTE service processing method according to some implementation modes of the present disclosure.

[0052] Figure 8 It is a structural block diagram of an IMS registration device in some implementation modes of the present disclosure.

[0053] Fig. 9 It is a structural block diagram of a VoLTE service processing device in some implementation modes of the present disclosure.

[0054] Fig.10 It is a structural block diagram of a terminal device in some implementation modes of the present disclosure. DETAILED DESCRIPTION

[0055] The technical solution of the present disclosure will be described clearly and completely below in conjunction with the accompanying drawings. Obviously, the described implementation is a part of the implementation of the present disclosure, rather than all the implementations. Based on the implementation in the present disclosure, all other implementations obtained by ordinary technicians in the field without creative work are within the scope of protection of the present disclosure. In addition, the technical features involved in the different implementations of the present disclosure described below can be combined with each other as long as they do not conflict with each other.

[0056] IMS (Internet Protocol Multimedia Subsystem) is an IP data transmission technology built on the 4G LTE (Long-Term Evolution) network. VoLTE (Voice over Long-Term Evolution) is a voice call technology based on the IMS network.

[0057] In traditional voice solutions, terminal devices use 4G / 5G networks to access the Internet. When they want to make a voice call with the called device, they need to use CSFB (Circuit Switched Fall Back) to fall back to 2G / 3G to make a phone call.

[0058] With the development of 4G / 5G technology, various mobile network operators have gradually begun to abandon 2G / 3G networks. The gradual withdrawal of 2G / 3G networks has become a general trend. The VoLTE service based on the IMS network is a new voice solution in this context. VoLTE does not require 2G / 3G networks. All its services are carried on the 4G LTE+IMS network, realizing the unification of data and voice services under the same network. VoLTE can not only provide voice calls, but also video calls.

[0059] In order to establish VoLTE services based on IMS networks, it is necessary to ensure that both the initiator and receiver of the voice call are registered with IMS services. If either terminal device is not registered with IMS, or the IMS registration fails, the VoLTE service cannot be used. Therefore, in the current transition stage where voice services are gradually shifting from 2G / 3G networks to IMS networks, how to improve the IMS registration success rate is an important research direction to ensure the IMS network occupancy rate and VoLTE service connection rate.

[0060] Based on this, the embodiments of the present disclosure provide an IMS registration method and apparatus, a VoLTE service processing method and apparatus, a terminal device, and a storage medium, aiming to improve the IMS registration success rate of the terminal device, thereby ensuring the connection rate of the voice service of the terminal device.

[0061] In some implementations, the present disclosure provides an Internet Protocol Multimedia Subsystem (IMS) registration method.

[0062] The IMS registration method disclosed in the present invention can be applied to various communication systems, for example, a 4G LTE communication system, a 5G communication system, a communication system with a hybrid architecture of LTE and 5G, a 5G New Radio (NR) system, and new communication systems that will emerge in future communication developments. It can be understood that as long as the IMS is used as a voice solution in the communication system, the IMS registration method provided in the embodiments of the present invention can be used.

[0063] Figure 1 A schematic diagram of a network architecture to which the present disclosure is applicable is shown, wherein the network architecture includes one or more terminal devices, one or more access network devices, a core network device, and an IMS system.

[0064] like Figure 1 As shown, the terminal device refers to an electronic device used to connect to a wireless network. The terminal device described in the present disclosure can be any type of device suitable for implementation, such as a mobile phone, a tablet computer, a wearable device, a vehicle-mounted device, etc., and the present disclosure does not impose any restrictions on this.

[0065] The access network equipment includes a base station (eNodeB), and the base station may include a base station that provides a 2G / 3G network for a terminal device, a base station that provides an LTE network for a terminal device, a base station that provides an NR network for a terminal device, etc., and the present disclosure does not limit this. It is worth noting that the embodiments of the present disclosure are also applicable to a communication system in which a 2G / 3G network is decommissioned, that is, the communication system does not include a 2G / 3G base station.

[0066] Core network equipment refers to the core network servers of 2G / 3G, LTE, 5G and other communication systems. The IMS system is a multimedia subsystem grafted onto the LTE or 5G network. The VoLTE voice solution provided by the IMS system can achieve the unification of data and voice services on the same network.

[0067] Based on the above network architecture, an embodiment of the present disclosure provides an IMS registration method, which can be applied to the aforementioned terminal device to implement IMS registration of the terminal device in the network side device.

[0068] like Figure 2 As shown, in some implementations, the IMS registration method of the present disclosure example includes:

[0069] S210: Send IMS registration request information to the network side device.

[0070] In the embodiments of the present disclosure, the network side device may include the aforementioned access network device (base station), core network device and IMS system. When the terminal device performs IMS registration, a registration request is generated on the terminal device side, and the registration request is the IMS registration request information described in the present disclosure.

[0071] After generating the IMS registration request information, the terminal device can send the IMS registration request information to the network side device. Specifically, the terminal device sends the IMS registration request information to the Proxy Call Session Control Function (P-CSCF) entity in the IMS system through the access network and the core network.

[0072] The P-CSCF entity is the first connection point between the access network device and the IMS system. All information initiated from and terminated at terminal devices that support IMS must be forwarded through the P-CSCF entity. The P-CSCF entity can be used to forward the IMS registration request information from the terminal device to the Serving Call Session Control Function (S-CSCF) entity of the IMS system. The S-CSCF entity is the core of the IMS system, and it performs session control and registration requests for terminal devices. The S-CSCF entity can generate corresponding response information based on the IMS registration request information from the terminal device, and forward it to the terminal device through the P-CSCF entity.

[0073] Of course, the IMS system will also include other related functional network elements, such as I-CSCF (Interrogating Call Session Control Function) entity, BGCF (Breakout Gateway Control Function) entity, MGCF (Media Gateway Control Function) entity, etc. Those skilled in the art can undoubtedly understand this by referring to the relevant technology, and this disclosure will not go into details.

[0074] It can be understood that when the terminal device performs IMS registration, it first needs to establish an IMS PDN (Packet Data Network) connection with the network side device. PDN is an external data network relative to the LTE network. Since the LTE network is a network with only a PS (Packet Switch) domain and no CS (Circuit Switch) domain, the terminal device must be connected to at least one PDN to perform IMS registration.

[0075] Therefore, in the embodiments of the present disclosure, the IMS registration request information sent by the terminal device includes a PDN connection request. In some embodiments, the PDN connection request may generally include an APN (Access Point Name) type and a PDN IP type. The APN type refers to the name of the IMS system accessed, and the PDN IP type refers to the IP type for establishing a PDN connection, generally including IPv4, IPv6, and IPv4v6.

[0076] In the disclosed embodiments, the terminal device may perform the IMS registration process when the 4G / 5G network is successfully attached and the IMS is not registered.

[0077] For example, in one example, after the terminal device is turned on or switched out of flight mode, the terminal device will automatically send an attachment request (Attach Request) to the network side device. If the core network of the network side device allows the terminal device to attach, the terminal device can be established in the 4G / 5G network. After that, the terminal device can start the IMS registration process, that is, send IMS registration request information to the IMS system of the network side device.

[0078] S220 : In response to receiving the PDN request failure information sent by the network side device, determine whether the operator of the network side device deploys a circuit domain network based on a pre-configured network list.

[0079] It can be understood that data transmission includes two domains, namely the CS domain and the PS domain. The CS domain refers to the circuit switching domain. The CS domain network is usually used for voice calls. Currently, basic telephone services based on 2G / 3G are all implemented through the CS domain network. The PS domain refers to the packet switching domain. The PS domain network is usually used for data services, including streaming media services. Currently, data services based on 4G / 5G are all implemented through the PS domain network.

[0080] The PS domain network cannot directly provide voice services, so at this stage, the circuit domain fallback (CSFB) method is usually used to establish voice services. That is, users can realize data services through the 4G / 5G network. When they need to make a call, the network will fall back to the 2G / 3G network for telephone services.

[0081] Combined with the above, we can see that with the general trend of 2G / 3G networks being gradually withdrawn from the network, voice services will be in the transition stage from 2G / 3G networks to IMS networks at present and in the future. During this transition stage, some mobile network operators will completely abandon 2G / 3G networks, while some operators will continue to maintain the operation of 2G / 3G networks.

[0082] For users of operators who maintain 2G / 3G network deployment, if IMS registration fails, even if VoLTE voice services based on the IMS network are unavailable, they can still fall back to the CS domain network to make calls through the circuit domain fallback CSFB method. However, for users of operators who no longer deploy 2G / 3G networks, if IMS registration fails, they cannot fall back to the CS domain to make calls, and VoLTE voice services are also unavailable, which will seriously affect the use of user voice services.

[0083] Therefore, in the embodiment of the present disclosure, the terminal device needs to pre-configure and maintain a network list, which is used to record the current network deployment of each operator, that is, to record whether each operator currently still has a circuit domain (CS domain) network deployed. It can be understood that as the network deployment of each operator changes, the network list is a dynamically updated list.

[0084] In some implementations, the circuit domain network includes a 2G / 3G network. When the operator deploys the circuit domain network, the terminal device can fall back to the circuit domain network to implement telephone services. When the operator does not deploy the circuit domain network, the terminal device can only implement VoLTE voice services through the IMS network and cannot fall back to the circuit domain network to make calls.

[0085] For example, in an example, the network list on the terminal device side may be as shown in Table 1 below:

[0086] Table 1

[0087]

[0088]

[0089] For example, in the example in Table 1, the circuit domain network of operator A is in the "non-deployed" state, that is, operator A does not support the basic telephone service of circuit domain fallback, and only supports the VoLTE voice service of IMS network. The circuit domain networks of operator B and operator C are in the "deployed" state, that is, operator B and operator C support both the basic telephone service of circuit domain fallback and the VoLTE voice service based on IMS network.

[0090] In some implementations, the terminal device may autonomously configure and maintain the network list, that is, the terminal device periodically obtains the current circuit domain network deployment status of each operator and updates the historically stored network list.

[0091] In other implementations, the terminal device can configure and maintain the network list together with the server, and the server refers to a cloud platform that provides relevant services for the terminal device. Thus, the server can send the configured network list to the terminal device, and the terminal device stores the received network list. Then, the server can periodically obtain the current circuit domain network deployment status of each operator and send the circuit domain network deployment status to the terminal device, so that the terminal device updates the historically stored network list. This is explained in the following implementation of the present disclosure and will not be described in detail here.

[0092] In an embodiment of the present disclosure, after the terminal device sends IMS registration request information to the network side device, the network side device processes the IMS registration request information through relevant network elements. If the PDN connection request sent by the terminal device fails to be established, the network side device can return corresponding PDN request failure information to the terminal device.

[0093] When the terminal device receives the PDN request failure information returned by the network side device, it means that the terminal device fails to establish a PDN connection with the network side device, and thus the IMS registration of the terminal device fails. In the case of IMS registration failure, the terminal device can determine from the pre-configured network list whether the operator of the network side device currently performing IMS registration has deployed a circuit domain network.

[0094] For example, in one example, it is assumed that the operator of the network side device with which the terminal device is currently performing IMS registration is "operator X".

[0095] If operator X deploys a circuit domain network, even if the current IMS registration fails, the mobile terminal can still fall back to the circuit domain network to make calls through CSFB. At this time, the priority of IMS re-registration is not high. For example, the re-registration logic of the traditional solution can be used to retry registration after a certain interval, or keep the registration failure status.

[0096] If operator X has not deployed a circuit domain network, it means that the mobile terminal cannot fall back to the circuit domain network to make calls, and can only make calls through the VoLTE voice service. At this time, the mobile terminal fails to register with the IMS and cannot use the VoLTE service, so the priority of IMS re-registration is very high. Therefore, in the embodiment of the present disclosure, the PDN request failure information returned by the network side device can be combined to analyze the cause of the PDN failure, and adopt corresponding re-registration measures to maximize the IMS registration success rate.

[0097] S230: In the case where the operator has not deployed a circuit domain network, re-initiate IMS registration based on a pre-configured re-registration operation corresponding to the PDN request failure information until a first preset condition is met.

[0098] In combination with the foregoing, it can be known that the circuit domain network deployment of the current operator can be determined based on the network list shown in Table 1. For example, if the operator has not deployed a circuit domain network, it is necessary to analyze the cause of the PDN failure and select the corresponding re-registration operation to re-register the IMS to maximize the IMS registration success rate.

[0099] In the embodiments of the present disclosure, corresponding re-registration operations can be pre-configured for different PDN failure types, that is, a more targeted solution can be set for each PDN failure type, so as to improve the PDN connection success rate between the terminal device and the network side device, thereby improving the IMS registration success rate.

[0100] In some embodiments, when a PDN connection cannot be established based on a PDN connection request sent by a terminal device, a network-side device returns a PDN request failure message to the terminal device. The PDN request failure message includes a corresponding protocol status code. The protocol status code may be, for example, a 5xx status code, where 5xx refers to a code indicating a request error. The terminal device can thereby determine the corresponding PDN failure type based on the 5xx status code.

[0101] There may be many reasons for PDN request failure, such as response timeout, IP type abnormality, user authentication failure, etc. Therefore, targeted re-registration operations can be pre-configured for each failure reason, and a correspondence between PDN failure type and re-registration operation can be established.

[0102] In an embodiment of the present disclosure, after determining the corresponding PDN failure type according to the PDN request failure information, the re-registration operation corresponding to the PDN failure type can be determined based on a pre-established correspondence relationship, and then the IMS registration is re-initiated according to the re-registration operation until the first preset condition is met.

[0103] In some implementations, the first preset condition may include successful IMS registration, that is, after the terminal device performs one or more IMS re-registrations, the re-registration process is stopped until the IMS registration succeeds. In other implementations, the first preset condition may include n consecutive IMS re-registration failures, that is, after the terminal device performs n re-registrations, it still fails, indicating that the current IMS registration of the terminal device cannot be restored. In order to avoid repeated re-registration operations, the re-registration operation may also be stopped.

[0104] It is worth noting that in the traditional IMS registration solution, when the PDN connection fails, the terminal device generally initiates re-registration after an interval of 30 seconds, and abandons the re-registration operation when the re-registration fails for 2 or 3 consecutive times.

[0105] In the disclosed embodiment, during the IMS registration process of the terminal device, if the PDN connection fails, it is first determined whether the current operator has deployed a circuit domain network. If the circuit domain network is not deployed, the cause of the failure can be analyzed to select a targeted re-registration operation.

[0106] On the one hand, the IMS registration priority is classified based on the deployment of the circuit domain network. For lower priority situations such as being able to fall back to the circuit domain network to make calls, traditional re-registration logic can be used to avoid the sudden increase in power consumption and heat generation of electronic devices caused by the execution of complex logic, which affects the user experience. On the other hand, for higher priority situations such as being unable to fall back to the circuit domain network to make calls, by analyzing the specific reasons for PDN failure, a more targeted IMS registration solution is selected for re-registration, which greatly improves the PDN connection success rate, thereby improving the IMS registration success rate and reducing the risk of users being unable to use voice services.

[0107] From the above, it can be seen that in the embodiments of the present disclosure, when the PDN connection between the terminal device and the network side device fails, combined with the operator's circuit domain network deployment and PDN failure cause analysis, a more targeted re-registration operation is determined to improve the PDN connection success rate, thereby improving the IMS registration success rate and network resident rate, reducing the risk of users being unable to use voice services, and ensuring user experience.

[0108] like Figure 3 As shown, in some implementations, the IMS registration method of the present disclosure example, the process of pre-configuring the network list includes:

[0109] S310: Receive current network deployment information of each operator sent by the server.

[0110] S320: Update the historically stored network list according to the current network deployment information of each operator.

[0111] In the embodiment of the present disclosure, the terminal device and the server device can jointly maintain a network list such as shown in Table 1. Figure 4 As shown, the server can regularly obtain the current network deployment information of each operator, including the deployment status of the circuit domain network of each operator. The server can then send the network deployment information to the terminal device, and the terminal device can update the historically stored network list according to the network deployment information.

[0112] For example, in one example, the network list historically stored in the mobile terminal may be as shown in Table 1 above. The server may detect the network deployment information of each operator once every 7 days, 15 days, 30 days, etc., and the network deployment information is the current network deployment information described in the present disclosure. For example, the current network deployment information detected by the server is shown in Table 2 below:

[0113] Table 2

[0114] Operator Name Network deployment information Operator A 2G / 3G network is not deployed, 4G / 5G network is deployed Operator B 2G / 3G network is not deployed, 4G / 5G network is deployed Operator C 2G / 3G networks have been deployed, and 4G / 5G networks have been deployed …… ……

[0115] Thus, the server can determine the current deployment status of each operator's circuit domain network based on the current network deployment information. For example, in the example in Table 2, the circuit domain networks of operators A and B are not deployed, and the circuit domain network of operator C is deployed. Then, the server can send the current network deployment information to the terminal device.

[0116] After receiving the current network deployment information sent by the server, the terminal device can update the information in the historically stored network list based on the current network deployment information. For example, in this implementation example, the terminal device updates the historically stored network list described in Table 1 according to the current network deployment information shown in Table 2, and the updated network list can be shown in Table 3 below:

[0117] Table 3

[0118] Operator Name Circuit Domain Network Operator A No deployment Operator B No deployment Operator C deploy …… ……

[0119] By comparing Table 1 and Table 3, it can be seen that in the time period between the historical network list and the current network list, the CS network of operator B was de-deployed, so the deployment status of the CS network in the network list is updated to "no deployment".

[0120] The above only illustrates one network list update process. In the specific implementation process, the above network list update process can be performed once every preset time period. The preset time period can be, for example, 7 days, 15 days, 30 days, 60 days, etc., and the present disclosure does not limit this.

[0121] From the above, it can be seen that in the embodiments of the present disclosure, the terminal device and the server can dynamically maintain the network list, so that during the transition period of gradual withdrawal of 2G / 3G networks, the deployment status of the circuit domain network recorded in the network list can always be kept up to date, providing an accurate data basis for subsequent IMS registration.

[0122] like Figure 5 As shown, in some implementations, the IMS registration method of the present disclosure example, the process of determining whether the operator deploys a circuit domain network based on the network list, includes:

[0123] S221. Obtain the target operator of the network side device currently registered by the terminal device.

[0124] S222: Determine network deployment information corresponding to the target operator based on the network list.

[0125] S223: Determine whether the target operator deploys a circuit domain network according to the network deployment information.

[0126] In an embodiment of the present disclosure, after the terminal device receives the PDN request failure information returned by the network side device, the terminal device can obtain the operator of the SIM (Subscriber Identity Module) card currently registered with the IMS, which is also the operator of the network side device, and is also the target operator described in the present disclosure.

[0127] After determining the target operator, the current network deployment information of the target operator can be determined according to the aforementioned pre-stored network list. For example, in one example, the network list currently stored in the terminal device is shown in Table 3. Taking "Operator B" as an example, according to the network list shown, the network deployment information corresponding to the target operator "Operator B" can be determined, and then according to the network deployment information, it can be determined that the target operator "Operator B" has not deployed a circuit domain network.

[0128] In the implementation manner of the present disclosure, the IMS registration method of the present disclosure example, when it is determined that the target operator has not deployed a circuit domain network, the corresponding re-registration operation can be determined based on the PDN request failure information returned by the network side device, and the IMS registration is re-performed. Figure 6 Provide explanation.

[0129] like Figure 6 As shown, in some implementations, the IMS registration method of the example of the present disclosure, the process of re-registering the IMS according to the re-registration operation corresponding to the PDN request failure information, includes:

[0130] S610: Determine a PDN failure type based on a protocol status code carried in the PDN request failure information.

[0131] S620: Re-initiate IMS registration based on a pre-configured re-registration operation corresponding to the PDN failure type.

[0132] It can be understood that for different reasons for PDN connection failure, the PDN request failure information returned by the network side device includes different protocol status codes. Therefore, after receiving the PDN request failure information, the terminal device can parse the information to obtain the carried protocol status code, and then analyze the protocol status code to determine the corresponding PDN failure type.

[0133] In some examples, the protocol status code may be represented as rejrect_esm_cause=29, rejrect_esm_cause=50, etc., which may be understood by those skilled in the art and will not be elaborated in the present disclosure.

[0134] After determining the PDN failure type, it is necessary to determine the corresponding re-registration operation according to the PDN failure type. Therefore, in the embodiments of the present disclosure, it is necessary to pre-configure the corresponding re-registration operation for each PDN failure type.

[0135] For example, in some implementations, when the PDN failure type is response timeout, it is likely that an abnormal condition occurs in the cell where the current terminal device performs IMS registration. It is understandable that for a cellular network system, there may always be some cells in the network with poor VoLTE quality and cannot be optimized. When the terminal device performs IMS registration in these cells, a PDN connection failure may occur.

[0136] Therefore, in the embodiment of the present disclosure, when the PDN failure type is response timeout, the corresponding re-registration operation is: replacing the cell identifier included in the IMS registration request information with another cell identifier, and re-sending the IMS registration request information to the network side device.

[0137] In other words, the cell currently being registered with IMS can be changed by cell reselection, and the cell ID in the IMS registration request information of the terminal device can be replaced with the cell ID of the reselected new cell. Then, the IMS registration request information after the cell ID is changed can be resent to the network side device to try IMS registration again.

[0138] For example, in some implementations, when the PDN failure type is an IP type exception, it is likely that the PDN IP type currently configured by the terminal device does not match the PDN IP type supported by the network device side. For example, in the IMS registration request information sent by the terminal device, the PDN IP type is IPv6, while the PDN IP type supported by the network side device is IPv4, so that the PDN connection fails to be established.

[0139] Therefore, in the embodiment of the present disclosure, when the PDN failure type is an IP type exception, the corresponding re-registration operation is: replacing the PDN IP type information included in the IMS registration request information with other IP type information, and re-sending the IMS registration information to the network side device.

[0140] In other words, the PDN IP type information in the IMS registration request information of the terminal device can be replaced with new type information by changing the PDN IP type. For example, in one example, the PDN failure information returned by the network side device includes the PDN IP type supported by itself, so that the terminal device can replace the original PDN IP type information "IPv6" with "IPv4" or "IPv6v4" supported by the network side device. Then, the IMS registration request information after the PDN IP type information is changed can be resent to the network side device to try IMS registration again.

[0141] For example, in some implementations, when the PDN failure type is user authentication failure, it is likely that an identity anomaly occurs on the current terminal device side, such as an anomaly in the encryption process of the terminal device, which causes the network device to be unable to decrypt normally, resulting in user identity authentication failure.

[0142] Therefore, in the embodiment of the present disclosure, when the PDN failure type is user authentication failure, the corresponding re-registration operation is: re-sending IMS registration request information to the network side device after a preset time interval.

[0143] In other words, the PDN connection failure caused by occasional abnormality can be eliminated by retrying to register the IMS after waiting for a preset time interval. The preset time interval can be set according to the specific situation, such as 30s, 60s, 120s, etc., and the present disclosure does not limit this.

[0144] Of course, those skilled in the art can understand that the reasons for the PDN connection failure during the IMS registration process may also include other reasons, so the PDN failure type is not limited to the above example. Those skilled in the art can make corresponding extensions based on the above disclosure, and the present disclosure is not limited to this.

[0145] In the implementation manner of the present disclosure, after the PDN failure type is determined, the re-registration operation corresponding to the current PDN failure type can be determined according to the aforementioned pre-configured re-registration operation, and IMS registration is performed based on the re-registration operation.

[0146] It is worth noting that in some embodiments of the present disclosure, two consecutive re-registrations of the terminal device can be performed at an interval of a preset time. For example, after the first IMS registration, the second IMS registration can be performed after an interval of a preset time, and the preset time can increase with the increase in the number of registrations, that is, the more registration failures, the longer the preset interval time. In addition, the corresponding number of re-registrations can be preset, and if the IMS registration is still not successful after reaching the preset number of re-registrations, the re-registration operation can be stopped.

[0147] From the above, it can be seen that in the embodiments of the present disclosure, when the PDN connection between the terminal device and the network side device fails, combined with the operator's circuit domain network deployment and PDN failure cause analysis, a more targeted re-registration operation is determined to improve the PDN connection success rate, thereby improving the IMS registration success rate and network resident rate, reducing the risk of users being unable to use voice services, and ensuring user experience.

[0148] As mentioned above, after the terminal device successfully registers with IMS, the terminal device can use the VoLTE service based on the IMS network, and can establish voice and video call services without falling back to the 2G / 3G network. However, since the reliability of the PS domain network is lower than that of the CS domain network, even after the terminal device successfully registers with IMS, as the terminal device stays in the network for a long time, the terminal device often fails to connect to the VoLTE call service normally.

[0149] Based on this, the embodiments of the present disclosure provide a method for processing long term evolution voice bearer VoLTE services, which aims to optimize abnormal scenarios in which terminal devices use VoLTE voice call services, improve the connection rate of VoLTE voice services, reduce the risk of users being unable to use voice services, and improve user experience.

[0150] like Figure 7 As shown, in some implementations, the VoLTE service processing method of the present disclosure example includes:

[0151] S710: When the terminal device has registered with the IMS, the terminal device sends a VoLTE service request to the network side device.

[0152] In the implementation manner of the present disclosure, the terminal device can implement IMS registration in the network side device through the aforementioned method process. Those skilled in the art may refer to the aforementioned, and the present disclosure will not elaborate on this.

[0153] After completing the IMS registration, it means that the terminal device can use the VoLTE voice service based on the IMS network. By clicking the VoLTE voice call icon on the terminal device, the user can establish a VoLTE voice call or video call with any called device that has also registered with IMS.

[0154] In the implementation manner of the present disclosure, the terminal device refers to the initiator of the VoLTE call service, and the called device refers to the receiver of the VoLTE call service.

[0155] When a terminal device initiates a VoLTE call service, the terminal device needs to send a VoLTE service request to a network-side device, thereby requesting the network-side device to initiate a call to the called device according to the service request.

[0156] S720: In response to receiving a network error code sent by the network side device, determine whether the operator of the network side device deploys a circuit domain network based on a pre-configured network list.

[0157] It can be understood that after the terminal device sends a VoLTE service request to the network side device, the network side device processes the VoLTE service request and returns a corresponding network error code to the terminal device if the VoLTE service connection fails.

[0158] In some implementations, the network error code may be, for example, a 5xx status code, where 5xx refers to a code indicating a request error, and different error causes correspond to different 5xx status codes, such as 501, 502, 503, and the like.

[0159] In the embodiment of the present disclosure, when the terminal device receives a network error code returned by the network side device, it indicates that the VoLTE service request of the terminal device has failed and the VoLTE call cannot be made. At this time, it is necessary to determine whether the currently used operator has deployed a circuit domain network based on the network list pre-configured in the above embodiment.

[0160] As mentioned above, for users of operators who maintain 2G / 3G network deployment, if IMS registration fails, even if the VoLTE voice service based on the IMS network is unavailable, they can still fall back to the CS domain network to make calls through the circuit domain fallback CSFB method. However, for users of operators who no longer deploy 2G / 3G networks, if IMS registration fails, they cannot fall back to the CS domain to make calls, and the VoLTE voice service is also unavailable, which will seriously affect the use of user voice services.

[0161] For example, in one example, it is assumed that the operator of the network-side device for which the terminal device currently requests the VoLTE call service is "operator X".

[0162] If operator X deploys a circuit domain network, even if the current VoLTE call service request fails, the mobile terminal can still fall back to the circuit domain network to make a call through CSFB. At this time, the priority of VoLTE reconnection is not high. For example, the circuit domain fallback logic of the traditional solution can be used to fall back to the CS domain and switch to the basic telephone service for the called device.

[0163] If operator X has not deployed a circuit domain network, it means that the mobile terminal cannot fall back to the circuit domain network to make a call, and can only make a call through the VoLTE call service. At this time, the mobile terminal fails to request the VoLTE call service and cannot use the VoLTE service, so the priority of reconnecting to VoLTE is very high. Therefore, in the embodiment of the present disclosure, the reason for the failure of the VoLTE request can be analyzed in combination with the network error code returned by the network side device, and corresponding reconnection measures can be adopted to maximize the connection rate of the VoLTE call service.

[0164] Therefore, in the embodiments of the present disclosure, after receiving the network error code sent by the network side device, the terminal device can determine whether the current operator deploys a circuit domain network based on the currently used operator and the network list pre-stored in the above embodiments.

[0165] In the implementation manner of the present disclosure, for the configuration and update process of the network list stored in the terminal device, those skilled in the art may refer to the aforementioned implementation, and the present disclosure will not elaborate on this.

[0166] S730: In the case where the operator has not deployed a circuit domain network, based on a pre-configured target operation corresponding to the network error code, re-initiate a VoLTE call connection with the called device until a second preset condition is met.

[0167] In combination with the above, it can be known that based on the above network list, the circuit domain network deployment status of the current operator can be determined. For example, if the operator has not deployed a circuit domain network, it is necessary to analyze the reason for the failure of the VoLTE request and select the corresponding reconnection operation to re-initiate the VoLTE call connection to maximize the connection rate of the VoLTE call.

[0168] In the embodiments of the present disclosure, corresponding reconnection operations can be pre-configured for different network error codes, that is, a more targeted solution can be set for each network error code of VoLTE request failure, thereby improving the success rate of VoLTE call connection between the terminal device and the network side device, and then improving the connection rate of VoLTE calls.

[0169] There may be many reasons for the failure of VoLTE requests, such as the network side equipment not supporting VoLTE services, the IMS network interruption of the terminal equipment, occasional network errors, etc. Therefore, targeted VoLTE reconnection operations can be pre-configured for each request failure reason, and a corresponding relationship between the network error code and the reconnection operation can be established.

[0170] In an implementation manner of the present disclosure, after receiving a network error code, the VoLTE reconnection operation corresponding to the network error code can be determined based on a pre-established correspondence relationship. The VoLTE reconnection operation is the target operation described in the present disclosure. Then, the VoLTE call connection with the called device is re-initiated according to the target operation until the second preset condition is met.

[0171] In some implementations, the second preset condition may include a successful VoLTE call connection, that is, after the terminal device performs one or more reconnection operations, the reconnection process is stopped until the VoLTE call is successfully connected. In other implementations, the second preset condition may include n consecutive VoLTE reconnection failures, that is, after the terminal device performs n reconnections, it still fails, indicating that the VoLTE service of the current terminal device cannot be restored. In order to avoid repeated reconnection operations, the reconnection operation can be stopped.

[0172] It is worth noting that in the traditional VoLTE service processing solution, when the VoLTE connection fails, the terminal device generally falls back to the circuit domain network to make a regular call. However, during the network architecture transition phase, once the 2G / 3G network is decommissioned, this solution will no longer be feasible.

[0173] Therefore, in the embodiments of the present disclosure, when the terminal device makes a VoLTE call request, if the VoLTE request fails, it is first determined whether the current operator has deployed a circuit domain network. If the circuit domain network is not deployed, the cause of the failure can be analyzed to select a targeted reconnection operation.

[0174] On the one hand, the priority of VoLTE call services is classified based on the deployment of the circuit domain network. For lower priority situations such as those that can fall back to the circuit domain network to make calls, the traditional circuit domain fallback solution can be used for voice call services to avoid the sudden increase in power consumption and heat generation of electronic devices caused by the execution of complex logic, which affects the user experience. On the other hand, for higher priority situations such as those that cannot fall back to the circuit domain network to make calls, by analyzing the specific reasons for the failure of the VoLTE request, a more targeted target operation is selected for VoLTE reconnection, which greatly improves the success rate of VoLTE connection, thereby improving the connection rate of VoLTE calls and reducing the risk of users being unable to use voice services.

[0175] It can be understood that for different VoLTE request failure reasons, the network side device will return different network error codes. Therefore, after receiving the network error code, the terminal device can determine the corresponding failure cause by analyzing the network error code.

[0176] For example, in one example, the network error code can be expressed as: not-support-QCI-value, radio-connection-with-ue-lost, tx2relocoverall-expiry, Temporary failure, etc. Those skilled in the art can understand this and will not be elaborated in this disclosure.

[0177] After the network error code is determined, it is necessary to determine the corresponding target operation according to the network error code. Therefore, in the embodiment of the present disclosure, it is necessary to pre-configure the corresponding VoLTE reconnection target operation for each network error code.

[0178] For example, in some implementations, when the network error code indicates that the current network side device does not support the VoLTE service, the terminal device cannot establish a VoLTE connection with the network side device. Therefore, in the implementation of the present disclosure, in this case, the corresponding target operation is: sending a VoLTE service roaming request to other network side devices.

[0179] It is understandable that the current network-side equipment does not support VoLTE services. This may be because the operator of the network-side equipment itself does not provide VoLTE services. Even if the terminal device repeatedly reconnects, it is impossible to successfully establish a VoLTE connection.

[0180] Therefore, in the embodiments of the present disclosure, a VoLTE service request can be sent to other network side devices that have a roaming agreement with the current network side device, and an attempt can be made to establish a VoLTE connection with the operator device that supports the VoLTE service through roaming, thereby establishing a VoLTE call with the called device.

[0181] For example, in some implementations, when the network error code indicates that the current terminal device's IMS network is disconnected, possible reasons include that the network side device believes that the terminal device is disconnected, or the terminal device times out during cell switching, resulting in an IMS network interruption. Since the terminal device is disconnected from the IMS network of the network side device, the VoLTE service cannot establish a connection.

[0182] Therefore, in the embodiment of the present disclosure, when the network error code indicates that the IMS network of the current terminal device is disconnected, the corresponding target operation is: sending an IMS registration request message to the network side device, and after the IMS registration is successful, re-sending the VoLTE service request to the network side device.

[0183] It can be understood that since the IMS network connection is disconnected, the terminal device cannot establish a VoLTE service connection. Therefore, it can re-register with the IMS according to the aforementioned method process, thereby re-registering with the IMS, and after the re-registration is successful, re-initiate a VoLTE service request with the called device.

[0184] For example, in some implementations, when the network error code indicates a temporary network error, it is likely that an occasional abnormality occurs in the network connection between the terminal device and the network-side device, such as network fluctuations.

[0185] Therefore, in the embodiments of the present disclosure, when the network error code indicates a temporary network error, the corresponding target operation is: resending the VoLTE service request to the network side device after a preset time interval.

[0186] It is understood that the VoLTE connection failure caused by occasional abnormalities can be eliminated by retrying VoLTE after waiting for a preset time interval. The preset time interval can be set according to the specific situation, such as 1s, 3s, 5s, etc., and the present disclosure does not limit this.

[0187] Of course, those skilled in the art can understand that the reasons for the failure of the VoLTE request may also include other reasons, so the reconnection operation for the VoLTE service is not limited to the above example. Those skilled in the art can make corresponding expansions based on the above disclosure, and the present disclosure does not limit this.

[0188] In the disclosed embodiment, after the network error code is determined, the target operation corresponding to the current network error code can be determined according to the aforementioned pre-configured target operation, and VoLTE reconnection is performed based on the target operation.

[0189] It is worth noting that in some embodiments of the present disclosure, two consecutive reconnections of the terminal device can be performed at an interval of a preset time. For example, after the first VoLTE reconnection, the second VoLTE reconnection can be performed after an interval of a preset time, and the preset time can increase with the increase in the number of reconnection times, that is, the more the number of reconnection failures, the longer the preset time interval. In addition, the corresponding number of reconnection times can be pre-set, and if the connection is still not successful after reaching the preset number of reconnection times, the VoLTE reconnection operation can be stopped.

[0190] From the above, it can be seen that in the embodiments of the present disclosure, when the VoLTE connection between the terminal device and the network side device fails, combined with the operator's circuit domain network deployment and the analysis of the cause of the VoLTE connection failure, a more targeted target operation is determined to improve the VoLTE connection success rate, reduce the risk of users being unable to use voice services, and ensure user experience.

[0191] Based on the aforementioned network architecture, an embodiment of the present disclosure provides an IMS registration device, and the method can be applied to the aforementioned terminal device to implement IMS registration of the terminal device in the network side device.

[0192] like Figure 8 As shown, in some implementations, the IMS registration device of the example of the present disclosure includes:

[0193] The registration request module 10 is configured to send an IMS registration request message to a network side device, wherein the IMS registration request message includes a packet data network PDN connection request;

[0194] The first network determination module 20 is configured to determine whether the operator of the network side device deploys a circuit domain network based on a pre-configured network list in response to receiving the PDN request failure information sent by the network side device;

[0195] The re-registration module 30 is configured to re-initiate IMS registration based on a pre-configured re-registration operation corresponding to the PDN request failure information when the operator has not deployed a circuit domain network, until a first preset condition is met, wherein the first preset condition is used to indicate that the IMS registration is successful or multiple consecutive IMS registration failures.

[0196] From the above, it can be seen that in the embodiments of the present disclosure, when the PDN connection between the terminal device and the network side device fails, combined with the operator's circuit domain network deployment and PDN failure cause analysis, a more targeted re-registration operation is determined to improve the PDN connection success rate, thereby improving the IMS registration success rate and network resident rate, reducing the risk of users being unable to use voice services, and ensuring user experience.

[0197] Based on the aforementioned network architecture, an embodiment of the present disclosure provides a VoLTE service processing device, and the method can be applied to the aforementioned terminal device to realize the VoLTE connection of the terminal device on the network side device.

[0198] like Fig. 9 As shown, in some implementations, the Long Term Evolution Voice Bearer VoLTE service processing device of the example of the present disclosure includes:

[0199] The voice request module 40 is configured to, when the IMS is registered, send a VoLTE service request to the network side device by the terminal device, wherein the VoLTE service request is used to request to establish a VoLTE call connection with the called device that has registered the IMS; the terminal device registers with the IMS by the method of any of the aforementioned implementation modes;

[0200] A second network determination module 50 is configured to determine whether the operator of the network side device deploys a circuit domain network based on a pre-configured network list in response to receiving a network error code sent by the network side device;

[0201] The voice reconnection module 60 is configured to, when the operator has not deployed a circuit domain network, re-initiate a VoLTE call connection with the called device based on a pre-configured target operation corresponding to the network error code until a second preset condition is met, wherein the second preset condition is used to indicate that the VoLTE call connection is successful or that the VoLTE call connection fails for multiple consecutive times.

[0202] From the above, it can be seen that in the embodiments of the present disclosure, when the VoLTE connection between the terminal device and the network side device fails, combined with the operator's circuit domain network deployment and the analysis of the cause of the VoLTE connection failure, a more targeted target operation is determined to improve the VoLTE connection success rate, reduce the risk of users being unable to use voice services, and ensure user experience.

[0203] In some embodiments, the present disclosure provides a terminal device, which may be the terminal device of any of the foregoing embodiments, and includes:

[0204] Processor; and

[0205] A memory stores computer instructions, wherein the computer instructions are used to enable a processor to execute the method described in any of the above embodiments.

[0206] In some embodiments, the present disclosure provides a storage medium storing computer instructions, wherein the computer instructions are used to enable a computer to execute the method described in any of the aforementioned embodiments.

[0207] Fig.10 The terminal device structure in some embodiments of the present disclosure is shown in FIG. Fig.10 The terminal devices of some embodiments of the present disclosure are described.

[0208] Reference Fig.10The terminal device 1800 may include one or more of the following components: a processing component 1802 , a memory 1804 , a power component 1806 , a multimedia component 1808 , an audio component 1810 , an input / output (I / O) interface 1812 , a sensor component 1816 , and a communication component 1818 .

[0209] The processing component 1802 generally controls the overall operation of the terminal device 1800, such as operations associated with display, phone calls, data communications, camera operations, and recording operations. The processing component 1802 may include one or more processors 1820 to execute instructions. In addition, the processing component 1802 may include one or more modules to facilitate the interaction between the processing component 1802 and other components. For example, the processing component 1802 may include a multimedia module to facilitate the interaction between the multimedia component 1808 and the processing component 1802. For another example, the processing component 1802 can read executable instructions from a memory to implement terminal device related functions.

[0210] The memory 1804 is configured to store various types of data to support operations on the terminal device 1800. Examples of such data include instructions for any application or method operating on the terminal device 1800, contact data, phone book data, messages, pictures, videos, etc. The memory 1804 can be implemented by any type of volatile or non-volatile storage device or a combination thereof, such as static random access memory (SRAM), electrically erasable programmable read-only memory (EEPROM), erasable programmable read-only memory (EPROM), programmable read-only memory (PROM), read-only memory (ROM), magnetic memory, flash memory, magnetic disk or optical disk.

[0211] The power supply component 1806 provides power to various components of the terminal device 1800. The power supply component 1806 may include a power management system, one or more power supplies, and other components associated with generating, managing, and distributing power to the terminal device 1800.

[0212] The multimedia component 1808 includes a display screen that provides an output interface between the terminal device 1800 and the user. In some embodiments, the multimedia component 1808 includes a front camera and / or a rear camera. When the terminal device 1800 is in an operating mode, such as a shooting mode or a video mode, the front camera and / or the rear camera can receive external multimedia data. Each front camera and the rear camera can be a fixed optical lens system or have a focal length and optical zoom capability.

[0213] The audio component 1810 is configured to output and / or input audio signals. For example, the audio component 1810 includes a microphone (MIC), and when the terminal device 1800 is in an operation mode, such as a call mode, a recording mode, and a speech recognition mode, the microphone is configured to receive an external audio signal. The received audio signal can be further stored in the memory 1804 or sent via the communication component 1818. In some embodiments, the audio component 1810 also includes a speaker for outputting audio signals.

[0214] I / O interface 1812 provides an interface between processing component 1802 and peripheral interface modules, such as keyboards, click wheels, buttons, etc. These buttons may include but are not limited to: home button, volume button, start button, and lock button.

[0215] The sensor assembly 1816 includes one or more sensors for providing various aspects of status assessment for the terminal device 1800. For example, the sensor assembly 1816 can detect the open / closed state of the terminal device 1800, the relative positioning of the components, such as the display and keypad of the terminal device 1800, and the sensor assembly 1816 can also detect the position change of the terminal device 1800 or a component of the terminal device 1800, the presence or absence of contact between the user and the terminal device 1800, the orientation or acceleration / deceleration of the terminal device 1800, and the temperature change of the terminal device 1800. The sensor assembly 1816 may include a proximity sensor configured to detect the presence of a nearby object without any physical contact. The sensor assembly 1816 may also include an optical sensor, such as a CMOS or CCD image sensor, for use in imaging applications. In some embodiments, the sensor assembly 1816 may also include an acceleration sensor, a gyroscope sensor, a magnetic sensor, a pressure sensor, or a temperature sensor.

[0216] The communication component 1818 is configured to facilitate wired or wireless communication between the terminal device 1800 and other devices. The terminal device 1800 can access a wireless network based on a communication standard, such as Wi-Fi, 2G, 3G, 4G, 5G or 6G, or a combination thereof. In an exemplary embodiment, the communication component 1818 receives a broadcast signal or broadcast-related information from an external broadcast management system via a broadcast channel. In an exemplary embodiment, the communication component 1818 also includes a near field communication (NFC) module to facilitate short-range communication. For example, the NFC module can be implemented based on radio frequency identification (RFID) technology, infrared data association (IrDA) technology, ultra-wideband (UWB) technology, Bluetooth (BT) technology and other technologies.

[0217] In an exemplary embodiment, the terminal device 1800 may be implemented by one or more application-specific integrated circuits (ASICs), digital signal processors (DSPs), digital signal processing devices (DSPDs), programmable logic devices (PLDs), field programmable gate arrays (FPGAs), controllers, microcontrollers, microprocessors, or other electronic components.

[0218] Obviously, the above embodiments are merely examples for the purpose of clear explanation, and are not intended to limit the embodiments. For those skilled in the art, other different forms of changes or modifications can be made based on the above description. It is not necessary and impossible to list all the embodiments here. The obvious changes or modifications derived therefrom are still within the scope of protection of the present invention.

Claims

1. An Internet Protocol Multimedia Subsystem IMS registration method, characterized in that: The method comprises: Sending an IMS registration request message to a network side device, wherein the IMS registration request message includes a packet data network PDN connection request; In response to receiving the PDN request failure information sent by the network side device, determining whether the operator of the network side device deploys a circuit domain network based on a pre-configured network list; In the case that the operator has not deployed a circuit domain network, based on a pre-configured re-registration operation corresponding to the PDN request failure information, IMS registration is re-initiated until a first preset condition is met, wherein the first preset condition is used to indicate that the IMS registration is successful or multiple consecutive IMS registration failures.

2. The method according to claim 1, characterized in that The determining, based on the pre-configured network list, whether the operator of the network side device deploys a circuit domain network includes: Get the target operator of the currently registered network-side device; Based on the network list, determining network deployment information corresponding to the target operator; Determine whether the target operator deploys a circuit domain network according to the network deployment information.

3. The method according to claim 2, characterized in that Also includes: Receive the current network deployment information of each operator sent by the server; The historically stored network list is updated according to the current network deployment information of each operator.

4. The method according to claim 1, characterized in that: The re-initiating IMS registration based on the pre-configured re-registration operation corresponding to the PDN request failure information includes: Determine a PDN failure type based on a protocol status code carried by the PDN request failure information; Re-initiating IMS registration based on a pre-configured re-registration operation corresponding to the PDN failure type.

5. The method according to any one of claims 1 to 4, characterized in that: The re-initiating IMS registration based on the pre-configured re-registration operation corresponding to the PDN request failure information includes: In a case where the PDN failure type corresponding to the PDN request failure information is response timeout, the cell identifier included in the IMS registration request information is replaced with another cell identifier, and the IMS registration request information is resent to the network side device.

6. The method according to any one of claims 1 to 4, characterized in that: The re-initiating IMS registration based on the pre-configured re-registration operation corresponding to the PDN request failure information includes: In the case that the PDN failure type corresponding to the PDN request failure information is an IP type exception, the PDN IP type information included in the IMS registration request information is replaced with other IP type information, and the IMS registration request information is resent to the network side device.

7. The method according to any one of claims 1 to 4, characterized in that: The re-initiating IMS registration based on the pre-configured re-registration operation corresponding to the PDN request failure information includes: In a case where the PDN failure type corresponding to the PDN request failure information is user authentication failure, the IMS registration request information is resent to the network side device after a preset time interval.

8. The method according to claim 1, characterized in that The first preset condition is that the IMS registration is successful, and the method further includes: Sending a VoLTE service request to a network-side device, wherein the VoLTE service request is used to request to establish a VoLTE call connection with a called device that has registered with the IMS; In response to receiving a network error code sent by the network side device, determining whether an operator of the network side device deploys a circuit domain network based on a pre-configured network list; In the case that the operator has not deployed a circuit domain network, based on a pre-configured target operation corresponding to the network error code, the VoLTE call connection with the called device is re-initiated until a second preset condition is met, wherein the second preset condition is used to indicate that the VoLTE call connection is successful or that the VoLTE call connection fails for multiple consecutive times.

9. The method according to claim 8, characterized in that The re-initiating the VoLTE call connection with the called device based on a pre-configured target operation corresponding to the network error code includes: When the network error code indicates that the current network side device does not support the VoLTE service, the VoLTE service roaming request is sent to other network side devices.

10. The method according to claim 8, characterized in that The re-initiating the VoLTE call connection with the called device based on a pre-configured target operation corresponding to the network error code includes: When the network error code indicates that the IMS network of the current terminal device is disconnected, an IMS registration request message is sent to the network side device, and after the IMS registration is successful, the VoLTE service request is resent to the network side device.

11. The method according to claim 8, characterized in that The re-initiating the VoLTE call connection with the called device based on a pre-configured target operation corresponding to the network error code includes: In a case where the network error code indicates a temporary network error, the VoLTE service request is resent to the network side device after a preset time interval.

12. An Internet Protocol Multimedia Subsystem IMS registration device, characterized in that: The device comprises: A registration request module, configured to send an IMS registration request message to a network side device, wherein the IMS registration request message includes a packet data network PDN connection request; A first network determination module is configured to determine, in response to receiving PDN request failure information sent by the network side device, whether the operator of the network side device deploys a circuit domain network based on a pre-configured network list; The re-registration module is configured to re-initiate IMS registration based on a pre-configured re-registration operation corresponding to the PDN request failure information when the operator has not deployed a circuit domain network, until a first preset condition is met, wherein the first preset condition is used to indicate that the IMS registration is successful or multiple consecutive IMS registration failures.

13. A terminal device, characterized in that: include: processor; as well as A memory storing computer instructions, wherein the computer instructions are used to enable a processor to execute the method according to any one of claims 1 to 11.

14. A storage medium, characterized in that: Computer instructions are stored, and the computer instructions are used to make a computer execute the method according to any one of claims 1 to 11.

Images