IMS registration processing method and device and storage medium

Abstract

The invention relates to an IMS registration processing method and device and a storage medium. The method comprises the steps of determining whether the terminal equipment is in a target use scene or not under the condition that IMS registration failure is monitored; under the condition that the terminal equipment is in the target use scene, determining a target recovery strategy based on a current error code of IMS registration failure; and restarting IMS registration under the condition that the target recovery strategy is successfully executed. According to the technical scheme, the target recovery strategy can be automatically executed based on the specific IMS registration failure reason by integrating the use scene of the terminal equipment, the IMS registration success rate is improved to the maximum extent, and the network use experience of a user is greatly improved.

Description

Technical Field

[0001] The present disclosure relates to the field of mobile communications, and in particular to an IMS registration processing method, device and storage medium. Background Art

[0002] At present, the 4th generation mobile networks (4G) and the 5th generation mobile networks (5G) have become mainstream networks, and the 2nd generation mobile networks (2G) and the 3rd generation mobile networks (3G) are gradually withdrawing from the market. In the 4G / 5G network environment, terminal devices need to register with the Internet Protocol (IP) Multimedia Subsystem (IMS) to make calls and send text messages normally. Among them, IMS is a network system based on IP network for providing multimedia services. IMS can provide voice solutions for 4G and 5G.

[0003] After the terminal device completes the 4G or 5G network attachment process, the IMS registration process can be carried out. However, if an abnormality occurs in the IMS registration, it will often lead to IMS registration failure, which in turn will lead to user communication failure, resulting in a poor user experience. Summary of the invention

[0004] In order to overcome the problems existing in the related art, the present disclosure provides a method, device and storage medium for processing IMS registration, so as to overcome the problem that IMS registration failure will reduce the online rate of IMS and affect the user experience.

[0005] According to a first aspect of an embodiment of the present disclosure, a method for processing IMS registration is provided, including:

[0006] In the case of detecting an IMS registration failure, determining whether the terminal device is in a target usage scenario;

[0007] When the terminal device is in the target usage scenario, determining a target recovery strategy based on a current error code of the IMS registration failure, wherein the target recovery strategy is used to indicate automatic recovery of the IMS registration failure;

[0008] In case the target recovery strategy is successfully executed, the IMS registration is restarted.

[0009] In some embodiments, when an IMS registration failure is detected, determining whether the terminal device is in a target usage scenario includes:

[0010] When an IMS registration failure is detected, starting a first timer;

[0011] When the timing duration of the first timer reaches a first preset duration, determining whether a message of successful IMS registration is monitored;

[0012] If no IMS registration success message is detected, it is determined whether the terminal device is in a target usage scenario.

[0013] In some embodiments, if the IMS registration success message is not monitored, determining whether the terminal device is in a target usage scenario includes:

[0014] If no IMS registration success message is detected, determining the network data demand and / or application running status of the terminal device;

[0015] When the network data demand is less than a preset demand and / or the application running state meets a preset running condition, it is determined that the terminal device is in the target usage scenario.

[0016] In some embodiments, when the terminal device is in the target usage scenario, determining the target recovery strategy based on the current error code of the IMS registration failure includes:

[0017] When the terminal device is in the target usage scenario, the current error code is compared with each preset error code in a preset database; wherein the preset error code and the preset recovery strategy are stored in the preset database, and the preset error code and the corresponding preset recovery strategy satisfy a preset mapping relationship;

[0018] The preset recovery strategy corresponding to the preset error code identical to the current error code in the preset database is determined as the target recovery strategy.

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

[0020] When there is no preset error code identical to the current error code in the preset database, the current error code is updated to the preset database.

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

[0022] The cause value of the last IMS registration failure during the period from the time when the IMS registration failure is first detected to the current time is determined as the current cause value;

[0023] The current reason value is converted into the current error code.

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

[0025] Determining whether the reason for the IMS registration failure exists in a filtering reason database;

[0026] In the case where the reason for the IMS registration failure exists in the filtering reason database, the reporting of the IMS registration failure is ignored.

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

[0028] After restarting the IMS registration, starting a second timer;

[0029] When the timing duration of the second timer reaches a second preset duration, the registration status of the IMS registration is obtained.

[0030] According to a second aspect of an embodiment of the present disclosure, a processing device for IMS registration is provided, including:

[0031] A first determination module is configured to determine whether the terminal device is in a target usage scenario when an IMS registration failure is detected;

[0032] A second determination module is configured to determine a target recovery strategy based on a current error code of the IMS registration failure when the terminal device is in the target usage scenario, wherein the target recovery strategy is used to indicate automatic recovery of the IMS registration failure;

[0033] The execution module is configured to restart the IMS registration when the target recovery strategy is successfully executed.

[0034] In some embodiments, the first determining module is configured to:

[0035] When an IMS registration failure is detected, starting a first timer;

[0036] When the timing duration of the first timer reaches a first preset duration, determining whether a message of successful IMS registration is monitored;

[0037] If no IMS registration success message is detected, it is determined whether the terminal device is in a target usage scenario.

[0038] In some embodiments, the first determining module is configured to:

[0039] If no IMS registration success message is detected, determining the network data demand and / or application running status of the terminal device;

[0040] When the network data demand is less than a preset demand and / or the application running state meets a preset running condition, it is determined that the terminal device is in the target usage scenario.

[0041] In some embodiments, the second determining module is configured to:

[0042] When the terminal device is in the target usage scenario, the current error code is compared with each preset error code in a preset database; wherein the preset error code and the preset recovery strategy are stored in the preset database, and the preset error code and the corresponding preset recovery strategy satisfy a preset mapping relationship;

[0043] The preset recovery strategy corresponding to the preset error code identical to the current error code in the preset database is determined as the target recovery strategy.

[0044] In some embodiments, the apparatus further comprises:

[0045] The updating module is configured to update the current error code to the preset database when there is no preset error code identical to the current error code in the preset database.

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

[0047] A third determination module is configured to determine the cause value of the last IMS registration failure within the time period from the moment when the IMS registration failure is first monitored to the current moment as the current cause value;

[0048] The conversion module is configured to convert the current cause value into the current error code.

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

[0050] A fourth determination module is configured to determine whether the reason for the IMS registration failure exists in a filtering reason database;

[0051] The determination module is configured to ignore the reporting of the IMS registration failure when the reason for the IMS registration failure exists in the filtering reason database.

[0052] In some embodiments, the execution module is configured to:

[0053] After restarting the IMS registration, starting a second timer;

[0054] When the timing duration of the second timer reaches a second preset duration, the registration status of the IMS registration is obtained.

[0055] The technical solution provided by the embodiments of the present disclosure may have the following beneficial effects:

[0056] In the embodiment of the present disclosure, when an IMS registration failure is monitored, it is determined whether the terminal device is in a target usage scenario; when the terminal device is in the target usage scenario, a target recovery strategy is determined based on the current error code of the IMS registration failure; when the target recovery strategy is successfully executed, the IMS registration is restarted.

[0057] The technical solution disclosed in the present invention can integrate the usage scenarios of terminal devices, automatically execute the target recovery strategy based on the specific reasons for IMS registration failure, maximize the IMS registration success rate, and greatly improve the user's network usage experience.

[0058] It is to be understood that the foregoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of the present disclosure. BRIEF DESCRIPTION OF THE DRAWINGS

[0059] The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the present disclosure and, together with the description, serve to explain the principles of the present disclosure.

[0060] Figure 1 The following is a flow chart of a method for processing IMS registration according to an exemplary embodiment. Figure 1 .

[0061] Figure 2 The figure is a schematic diagram of a system architecture of IMS registration according to an exemplary embodiment.

[0062] Figure 3 The following is a flow chart of a method for processing IMS registration according to an exemplary embodiment. Figure 2 .

[0063] Figure 4 The invention is a block diagram of a processing device for IMS registration according to an exemplary embodiment.

[0064] Figure 5 It is a block diagram of an IMS registration processing device 800 according to an exemplary embodiment. DETAILED DESCRIPTION

[0065] Exemplary embodiments will be described in detail herein, examples of which are shown in the accompanying drawings. When the following description refers to the drawings, the same numbers in different drawings represent the same or similar elements unless otherwise indicated. The embodiments described in the following exemplary embodiments do not represent all embodiments consistent with the present disclosure. Instead, they are merely examples of devices and methods consistent with some aspects of the present disclosure as detailed in the appended claims.

[0066] Figure 1 The following is a flow chart of a method for processing IMS registration according to an exemplary embodiment. Figure 1 ,like Figure 1 As shown, the IMS registration processing method can be applied to a terminal device, comprising the following steps:

[0067] In step 101, when an IMS registration failure is detected, determining whether the terminal device is in a target usage scenario;

[0068] In step 102, when the terminal device is in the target usage scenario, a target recovery strategy is determined based on a current error code of the IMS registration failure, wherein the target recovery strategy is used to indicate automatic recovery of the IMS registration failure;

[0069] In step 103, when the target recovery strategy is successfully executed, the IMS registration is restarted.

[0070] It should be noted that the IMS registration processing method proposed in the present disclosure can be applied to a terminal device that has a wireless transceiver function. Here, the terminal device may include: a mobile terminal or a fixed terminal. Among them, the mobile terminal may include: a mobile phone, a tablet computer, a laptop computer, a wearable terminal device, etc. The fixed terminal may include: a desktop computer, a smart TV, a vehicle-mounted device, etc.

[0071] The IMS registration processing method provided in this application can be applied to various communication systems, for example, it can be a long term evolution (LTE) or a 5G communication system, it can also be a LTE and 5G hybrid architecture, it can also be a 5G new radio (NR) system, and new communication systems that will emerge in future communication developments. As long as IMS is used as a voice solution in a communication system, the IMS registration processing method provided in the embodiment of this application can be used.

[0072] In some embodiments, the terminal device may generate an IMS registration request, send the generated IMS registration request to the network side, and receive a registration response message returned by the network side. Since IMS registration may be affected by many factors, registration failure may occur. For example, IMS registration may fail due to network connection problems; IMS registration may fail due to incorrect username or password; IMS registration may fail due to server failure; IMS registration may fail due to database errors; IMS registration may fail due to registration information conflicts, etc. IMS registration failure will reduce the online rate of IMS and affect the user experience.

[0073] In some embodiments, an IMS registration may be initiated through a modem side of a terminal device, and an IMS registration status may be updated, wherein the IMS registration status may include: a status of successful IMS registration and a status of failed IMS registration. After updating the IMS registration status, the modem side may report the IMS registration status to an IMS server. After receiving the IMS registration status, the IMS server may report the IMS registration status to an IMS status listener.

[0074] In the embodiment of the present disclosure, when an IMS registration failure is detected, it can be determined whether the terminal device is in a target usage scenario, and when the terminal device is in the target usage scenario, the current error code of the IMS registration failure can be obtained. Here, the target usage scenario may include: a low traffic demand scenario, a low power consumption scenario, etc., which can be determined according to user needs and characteristics of the terminal device, and is not specifically limited here.

[0075] In some embodiments, when an IMS registration failure is detected, determining whether the electronic device is in a target usage scenario includes:

[0076] When an IMS registration failure is detected, starting a first timer;

[0077] When the timing duration of the first timer reaches a first preset duration, determining whether a message of successful IMS registration is monitored;

[0078] If no IMS registration success message is detected, it is determined whether the terminal device is in a target usage scenario.

[0079] Here, the first timer may be an IMS timer, a custom timer, or a timer in a protocol. The first preset duration may be set as required, for example, may be set to 10 seconds (s), etc., and is not specifically limited here.

[0080] When the first timer is in the on state, the timing can be started, and when the timing duration of the first timer reaches the first preset duration, the IMS registration status is obtained to determine whether the IMS registration is successful when the timing duration reaches the first preset duration. If the IMS registration is successful, there is no need to judge the usage scenario of the terminal device. If the IMS registration fails, the usage scenario of the terminal device is further judged.

[0081] In the embodiment of the present disclosure, when an IMS registration failure is detected, the usage scenario is not immediately determined. Instead, a first timer is started first, and the IMS registration status is continuously monitored within a first preset duration. When the timing duration of the first timer reaches the first preset duration, if no IMS registration success message is detected, it is then determined whether the terminal device is in the target usage scenario.

[0082] In the embodiment of the present disclosure, when an IMS registration failure is detected, the IMS registration can be continued to be attempted, and the IMS registration status can be monitored. When the registration is still not successful when the first preset time is reached, the use scenario is judged. Since the probability of successful IMS registration is already very low when the timing time of the first timer reaches the first preset time, the possibility of misjudgment can be reduced compared to immediately judging the use scenario when the IMS registration fails.

[0083] In some embodiments, if the IMS registration success message is not monitored, determining whether the electronic device is in a target usage scenario includes:

[0084] If no IMS registration success message is detected, determining the network data demand and / or application running status of the electronic device;

[0085] When the network data demand is less than a preset demand and / or the application running state meets a preset running condition, it is determined that the electronic device is in the target usage scenario.

[0086] It should be noted that the network data demand may include: the network traffic demand of the terminal device. The network data demand may be determined according to the working mode of the terminal device, or according to the mobile network data used by the terminal device. For example, if the terminal device works in a game mode, it can be determined that the network data demand of the terminal device is greater than or equal to the preset demand, and at this time, it can be determined that the terminal device is in a non-target usage scenario.

[0087] For another example, if the terminal device is using mobile network data, the data traffic rate (uplink and downlink rates) of the mobile network data can be determined. If the data traffic rate of the mobile network data is greater than or equal to the preset rate, it is determined that the network data demand of the terminal device is greater than or equal to the preset demand, and it can be directly determined that the electronic device is in a non-target usage scenario.

[0088] In some embodiments, in the process of determining the data flow rate of mobile network data, multiple tests can be performed and the data flow rate can be calculated. For example, if the data flow rate of mobile network data of the terminal device within a preset time period is greater than the preset rate, it can be determined that the network data demand of the terminal device is greater than or equal to the preset demand. For another example, 5 tests can be performed within 10s. If the data flow rate obtained each time is greater than or equal to the preset rate, it can be determined that the network data demand of the terminal device is greater than or equal to the preset demand, and it can be directly determined that the electronic device is in a non-target usage scenario. Among them, the preset rate can be determined as needed, for example, it can be 1kb / s.

[0089] The application running status may include: the running status of the application installed on the terminal device. For example, the number of applications in running state on the terminal device, or the number of applications in use on the terminal device, etc. For another example, when the terminal device is in the screen-on state, and there is no foreground application in running state, it can be determined that the application running state meets the preset running conditions. For another example, when the call application of the terminal device is in running state, that is, the terminal device is in a call state, it can be determined that the application running state does not meet the preset running conditions and the terminal device is in a non-target usage scenario.

[0090] In some embodiments, when the network data demand is less than the preset demand, it can be determined that the electronic device is in the target usage scenario. For example, if the terminal device is operating in a non-gaming mode, it can be determined that the network data demand of the terminal device is less than the preset demand, and at this time, it can be determined that the terminal device is in the target usage scenario.

[0091] In other embodiments, when the application running state meets the preset running condition, it is determined that the electronic device is in the target usage scenario. For example, when the terminal device has no foreground application in the running state, it can be determined that the application running state meets the preset running condition, and at this time, it can be determined that the terminal device is in the target usage scenario.

[0092] In other embodiments, when the network data demand is less than the preset demand and the application running state meets the preset running condition, it is determined that the electronic device is in the target usage scenario. For example, if the terminal device is operating in a non-gaming mode, it can be determined that the network data demand of the terminal device is less than the preset demand, and when the terminal device has no foreground application in operation, it can be determined that the application running state meets the preset running condition. At this time, it can be determined that the network data demand is less than the preset demand and the application running state meets the preset running condition, and the terminal device is in the target usage scenario.

[0093] In some embodiments, when it is determined that the terminal device is in the target usage scenario, the reason value of the IMS registration failure can be obtained, and the reason value of the IMS registration failure can be converted into an error code, thereby obtaining the current error code of the IMS registration failure. Here, if the IMS registration fails, the IMS server can obtain the reason value of the IMS registration failure, convert the reason value of the IMS registration failure into an error code, and report the error code of the IMS registration failure to the IMS status listener.

[0094] In some embodiments, the error code may include: a general error code and a custom error code. Among them, the general error code may be an error code specified by the protocol, and the custom error code may be an error code customized by the user, which may be set according to the requirements and is not specifically limited here. For example, the general error code may be 0, and the corresponding recovery strategy may be to send the VoLTE switch value to the IMS configuration management module, wherein the VoLTE switch value is used to turn on or off the IMS registration of the terminal device. The custom error code may be 403, which is used to indicate an authentication failure, and the corresponding recovery strategy may be to set the configuration parameters in the Modem and restart the Modem.

[0095] In other embodiments, if it is determined that the terminal device is in a non-target usage scenario, it can be detected again whether the terminal device enters the target usage scenario after a preset waiting time. For example, if it is determined that the terminal device is in a non-target usage scenario, it can be detected again after one hour whether the terminal device enters the target usage scenario.

[0096] By setting a preset waiting time and performing another detection after the preset waiting time is reached, after determining that the terminal device has entered the target usage scenario, the target recovery strategy corresponding to the IMS registration failure can be immediately determined, thereby maximizing the IMS registration success rate.

[0097] In some embodiments, when the electronic device is in the target usage scenario, determining the target recovery strategy based on the current error code of the IMS registration failure includes:

[0098] When the electronic device is in the target usage scenario, the current error code is compared with each preset error code in a preset database; wherein the preset error code and the preset recovery strategy are stored in the preset database, and the preset error code and the corresponding preset recovery strategy satisfy a preset mapping relationship;

[0099] The preset recovery strategy corresponding to the preset error code identical to the current error code in the preset database is determined as the target recovery strategy.

[0100] It should be noted that, when the electronic device is in the target usage scenario, the current error code can be compared with each preset error code in the preset database, and the preset recovery strategy corresponding to the preset error code in the preset database that is the same as the current error code is determined as the target recovery strategy. It can be understood that the preset database in the present disclosure stores preset error codes and preset recovery strategies, and the preset error codes and the corresponding preset recovery strategies satisfy the preset mapping relationship.

[0101] It should be noted that in the process of historical IMS registration, after obtaining the error code of IMS registration failure, the error code of IMS registration failure and the operator network registered by the terminal device when the IMS registration fails can be recorded in the preset database and uploaded to the fixed server at the set frequency. For example, a mapping relationship between the error code of IMS registration failure and the operator network can be established, and the error code of IMS registration failure, the operator network and the mapping relationship can be stored in the preset database. Among them, uploading according to the set frequency can be understood as regular uploading, for example, uploading once a week, once a day, etc.

[0102] In some embodiments, after the error code of the IMS registration failure is stored in a preset database, a corresponding recovery strategy can be formulated based on the error code of the IMS registration failure, that is, a preset error code and a corresponding preset recovery strategy can be obtained and stored in the preset database. In this way, after the current error code is obtained, the corresponding target recovery strategy can be obtained from the preset database based on the current error code, thereby realizing automatic recovery for the IMS registration failure.

[0103] For example, if the current error code is 0, the corresponding target recovery strategy can be to send the VoLTE switch value to the IMS configuration management module, where the VoLTE switch value is used to turn on or off the IMS registration of the terminal device. The current error code is 403, which is used to indicate authentication failure, and the corresponding target recovery strategy can be to set the configuration parameters in the modem and restart the modem.

[0104] In the embodiment of the present disclosure, when an IMS registration failure is monitored, it can be determined whether the terminal device is in the target usage scenario. When the terminal device is in the target usage scenario, a target recovery strategy is determined based on the current error code of the IMS registration failure; when the target recovery strategy is successfully executed, the IMS registration is restarted.

[0105] The technical solution disclosed in the present invention can integrate the usage scenarios of terminal devices, automatically execute the target recovery strategy based on the specific reasons for IMS registration failure, maximize the IMS registration success rate, and greatly improve the user's network usage experience.

[0106] In other embodiments, the recovery strategy corresponding to the user instruction can also be executed based on the detected user instruction. For example, the terminal device can be controlled to switch to flight mode based on the user instruction, for example, the Radio status can be reset, or the VoLTE function can be switched based on user-specified switches, etc. In some embodiments, the priority of the recovery strategy corresponding to the instruction is higher than the priority of the target recovery strategy. When the user instruction is detected, the target recovery strategy may not be executed. Since the user will perform the corresponding operation according to his or her needs during the execution of the target recovery strategy, the priority of the operation performed by the user can be placed at the highest level at this time, which is more in line with the user's needs for using the terminal device and can improve the user's experience of using the terminal device.

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

[0108] When there is no preset error code identical to the current error code in the preset database, the current error code is updated to the preset database.

[0109] It can be understood that, if there is no preset error code identical to the current error code in the preset database, it can be determined that there is no same error in the historical IMS registration, and at this time, the current error code can be updated to the preset database. In other embodiments, a corresponding recovery strategy can be formulated based on the current error code, and the current error code and the recovery strategy corresponding to the current error code can be updated to the preset database, thereby ensuring the real-time performance of the preset database and preparing for the automatic recovery of subsequent IMS registrations.

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

[0111] The cause value of the last IMS registration failure during the period from the time when the IMS registration failure is first detected to the current time is determined as the current cause value;

[0112] The current reason value is converted into the current error code.

[0113] It should be noted that the reason value of the IMS registration failure can represent the reason for the IMS failure, and can be a number, a letter, or a serial number, etc., which is not specifically limited here. For example, if the reason value is 1, it can be represented that the reason for the IMS registration failure is a network connection problem, and the error code is a general code that can represent the reason.

[0114] In some embodiments, when the IMS registration status is monitored, multiple IMS registration failures may occur within a period of time. In this case, if each IMS registration failure is processed, system resources of the terminal device may be wasted.

[0115] In the disclosed embodiment, the cause value of the last IMS registration failure in the time period from the time when the IMS registration failure is first detected to the current time can be determined as the current cause value, and the current cause value can be converted into the current error code. In this way, not only the accuracy of the determined current error code can be improved, but also the possibility of wasting system resources of the terminal device can be reduced.

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

[0117] Determining whether the reason for the IMS registration failure exists in a filtering reason database;

[0118] In the case where the reason for the IMS registration failure exists in the filtering reason database, the reporting of the IMS registration failure is ignored.

[0119] In some embodiments, the cause of the IMS registration failure that does not need or cannot be automatically recovered can be pre-stored in a filtering cause database. After the cause of the IMS registration failure is determined, the cause of the IMS registration failure can be compared with the cause pre-stored in the filtering cause database. If the cause of the IMS registration failure exists in the filtering cause database, the reporting of the IMS registration failure can be ignored, that is, the automatic recovery process will not be executed.

[0120] The reasons pre-stored in the filtering reason database may be unnecessary or unable to be automatically restored, for example, they may include: the operator does not support IMS, the terminal device is in a call state, the failure reason value is wrong, or a user-defined reason.

[0121] In the embodiment of the present disclosure, before executing the recovery strategy for the IMS registration, it can be determined whether the cause of the IMS registration failure exists in the filtering cause database. When the cause of the IMS registration failure exists in the filtering cause database, the report of the IMS registration failure is ignored, thereby saving system resources of the terminal device.

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

[0123] After restarting the IMS registration, starting a second timer;

[0124] When the timing duration of the second timer reaches a second preset duration, the registration status of the IMS registration is obtained.

[0125] It should be noted that the registration status of the IMS registration can be used to indicate whether the target recovery strategy is effective.

[0126] In the disclosed embodiment, after the IMS registration is restarted, a second timer may be started, and when the timing duration of the second timer reaches a second preset duration, the registration status of the IMS registration is obtained. The registration status of the IMS registration includes: a state of successful IMS registration and a state of failed IMS registration. If the IMS registration is successful, it indicates that the target recovery strategy is effective, and if the IMS registration fails, it indicates that the target recovery strategy is not effective.

[0127] Since IMS registration takes time, the registration status of IMS registration obtained immediately after restarting IMS registration may be inaccurate. In the embodiment of the present disclosure, after restarting IMS registration, a second timer can be started, and when the timing duration of the second timer reaches a second preset duration, the registration status of IMS registration is obtained. In this way, the possibility of misjudgment due to inaccurate registration obtained during the process of restarting IMS registration can be reduced. Among them, the second preset duration can be set as needed, for example, it can be 15s.

[0128] In other embodiments, after the target recovery strategy is successfully executed, the IMS registration may be restarted by detecting a restart instruction, wherein the restart instruction may be manually triggered by a user or automatically triggered by a terminal device, which is not specifically limited here.

[0129] Figure 2 FIG. 1 is a schematic diagram of a system architecture of IMS registration according to an exemplary embodiment. Figure 2 As shown, the IMS registration can be initiated through the modem 201 (Modem) of the terminal device, and the IMS registration status can be updated, wherein the IMS registration status can include: the status of successful IMS registration and the status of failed IMS registration. After updating the IMS registration status, the modem 201 can report the IMS registration status to the IMS server 202.

[0130] After receiving the IMS registration status, if the IMS registration fails, the IMS server 202 may obtain the reason value of the IMS registration failure, convert the reason value of the IMS registration failure into an error code, and report the error code of the IMS registration failure to the IMS status listener 203.

[0131] After receiving the IMS registration status, the IMS status listener 203 may update the IMS registration status to the IMS registration status manager 204. If the IMS registration is successful, the IMS registration success status is directly updated to the IMS registration status manager 204; if the IMS registration fails, the IMS registration failure status is updated to the IMS registration status manager 204, and the error code of the IMS registration failure is updated to the error code statistics module 205.

[0132] After obtaining the error code of the IMS registration failure, the error code statistics module 205 can record the error code of the IMS registration failure and the operator network to which the terminal device is registered when the IMS registration fails in a preset database, and upload it to a fixed server at a set frequency. For example, a mapping relationship between the error code of the IMS registration failure and the operator network can be established, and the error code of the IMS registration failure, the operator network, and the mapping relationship can be stored in the preset database. Among them, uploading according to the set frequency can be understood as regular uploading, for example, uploading once a week, once a day, etc. In some embodiments, after the error code of the IMS registration failure is stored in the preset database, a corresponding recovery strategy can be formulated based on the error code of the IMS registration failure.

[0133] After receiving the IMS status listener 203, the IMS status manager may record the error code (current error code) of the IMS registration failure, start the first timer, and when the timing duration of the first timer reaches the first preset duration, if the IMS registration success message is not detected, the scene control module 206 is started to be entered, and whether the terminal device is in the target usage scenario is determined based on the scene control module 206. For example, when the timing duration reaches 10s, if the IMS registration success message reported by the IMS status listener 203 is not received, the scene control module 206 is started to be entered. If the IMS registration success message is detected during this period, the IMS status manager is updated to the initial state, and the scene control module 206 and the recovery measure module 207 are reset.

[0134] Under the scenario control module 206, the network data demand and / or application running state of the electronic device can be determined; when the network data demand is less than the preset demand and / or the application running state meets the preset running condition, it is determined that the electronic device is in the target usage scenario. For example, if the terminal device is working in a non-game mode, it can be determined that the network data demand of the terminal device is less than the preset demand, and when the terminal device has no foreground application in running state, it can be determined that the application running state meets the preset running condition. At this time, it can be determined that the network data demand is less than the preset demand, and the application running state meets the preset running condition, and the terminal device is in the target usage scenario.

[0135] When it is determined that the terminal device is in the target usage scenario, the recovery measure module 207 can select a corresponding recovery measure (recovery strategy) according to the failure error code recorded by the IMS state manager. For example, the current error code can be compared with each preset error code in the preset database; the preset recovery strategy corresponding to the preset error code in the preset database that is the same as the current error code is determined as the target recovery strategy.

[0136] Figure 3 The following is a flow chart of a method for processing IMS registration according to an exemplary embodiment. Figure 2 ,like Figure 3 As shown, the IMS registration processing method mainly includes the following steps:

[0137] In step 301, when an IMS registration failure is detected, a first timer is started;

[0138] In step 302, when the timing duration of the first timer reaches a first preset duration, it is determined whether a message of successful IMS registration is monitored;

[0139] In step 303, if no message indicating successful IMS registration is detected, determining the network data demand and / or application running status of the terminal device;

[0140] In step 304, when the network data demand is less than a preset demand and / or the application running state meets a preset running condition, it is determined that the terminal device is in the target usage scenario;

[0141] In step 305, when the terminal device is in the target usage scenario, the current error code is compared with each preset error code in a preset database;

[0142] The preset database stores the preset error code and the preset recovery strategy, and the preset error code and the corresponding preset recovery strategy satisfy a preset mapping relationship.

[0143] In step 306, a preset recovery strategy corresponding to a preset error code identical to the current error code in the preset database is determined as the target recovery strategy;

[0144] In step 307, if there is no preset error code identical to the current error code in the preset database, the current error code is updated to the preset database;

[0145] In step 308, if the target recovery strategy is successfully executed, IMS registration is restarted.

[0146] In the embodiment of the present disclosure, when an IMS registration failure is monitored, it is determined whether the terminal device is in a target usage scenario; when the terminal device is in the target usage scenario, a target recovery strategy is determined based on the current error code of the IMS registration failure; when the target recovery strategy is successfully executed, the IMS registration is restarted.

[0147] The technical solution disclosed in the present invention can integrate the usage scenarios of terminal devices, automatically execute the target recovery strategy based on the specific reasons for IMS registration failure, maximize the IMS registration success rate, and greatly improve the user's network usage experience.

[0148] Figure 4 FIG. 1 is a block diagram of a processing device for IMS registration according to an exemplary embodiment. Figure 4 As shown, the IMS registration processing device 400 can be applied to a terminal device, and mainly includes:

[0149] The first determination module 401 is configured to determine whether the terminal device is in a target usage scenario when an IMS registration failure is detected;

[0150] The second determination module 402 is configured to determine a target recovery strategy based on a current error code of the IMS registration failure when the terminal device is in the target usage scenario, wherein the target recovery strategy is used to indicate automatic recovery of the IMS registration failure;

[0151] The execution module 403 is configured to restart the IMS registration if the target recovery strategy is successfully executed.

[0152] In some embodiments, the first determining module 401 is configured to:

[0153] When an IMS registration failure is detected, starting a first timer;

[0154] When the timing duration of the first timer reaches a first preset duration, determining whether a message of successful IMS registration is monitored;

[0155] If no IMS registration success message is detected, it is determined whether the terminal device is in a target usage scenario.

[0156] In some embodiments, the first determining module 401 is configured to:

[0157] If no IMS registration success message is detected, determining the network data demand and / or application running status of the terminal device;

[0158] When the network data demand is less than a preset demand and / or the application running state meets a preset running condition, it is determined that the terminal device is in the target usage scenario.

[0159] In some embodiments, the second determining module 402 is configured to:

[0160] When the terminal device is in the target usage scenario, the current error code is compared with each preset error code in a preset database; wherein the preset error code and the preset recovery strategy are stored in the preset database, and the preset error code and the corresponding preset recovery strategy satisfy a preset mapping relationship;

[0161] The preset recovery strategy corresponding to the preset error code identical to the current error code in the preset database is determined as the target recovery strategy.

[0162] In some embodiments, the apparatus 400 further includes:

[0163] The updating module is configured to update the current error code to the preset database when there is no preset error code identical to the current error code in the preset database.

[0164] In some embodiments, the apparatus 400 further includes:

[0165] A third determination module is configured to determine the cause value of the last IMS registration failure within the time period from the moment when the IMS registration failure is first monitored to the current moment as the current cause value;

[0166] The conversion module is configured to convert the current cause value into the current error code.

[0167] In some embodiments, the apparatus 400 further includes:

[0168] A fourth determination module is configured to determine whether the reason for the IMS registration failure exists in a filtering reason database;

[0169] The determination module is configured to ignore the reporting of the IMS registration failure when the reason for the IMS registration failure exists in the filtering reason database.

[0170] In some embodiments, the execution module 403 is configured to:

[0171] In case the target recovery strategy is successfully executed, starting a second timer;

[0172] When the timing duration of the second timer reaches a second preset duration, the IMS registration is restarted.

[0173] Regarding the device in the above embodiment, the specific manner in which each module performs operations has been described in detail in the embodiment of the method, and will not be elaborated here.

[0174] Figure 5 8 is a block diagram of an IMS registration processing device 800 according to an exemplary embodiment. For example, the device 800 may be a mobile phone, a mobile computer, etc.

[0175] Reference Figure 5 , the device 800 may include one or more of the following components: a processing component 802 , a memory 804 , a power component 806 , a multimedia component 808 , an audio component 810 , an input / output (I / O) interface 812 , a sensor component 814 , and a communication component 816 .

[0176] The processing component 802 generally controls the overall operation of the device 800, such as operations associated with display, phone calls, data communications, camera operations, and recording operations. The processing component 802 may include one or more processors 820 to execute instructions to complete all or part of the steps of the above-mentioned method. In addition, the processing component 802 may include one or more modules to facilitate the interaction between the processing component 802 and other components. For example, the processing component 802 may include a multimedia module to facilitate the interaction between the multimedia component 808 and the processing component 802.

[0177] The memory 804 is configured to store various types of data to support operations on the device 800. Examples of such data include instructions for any application or method operating on the device 800, contact data, phone book data, messages, pictures, videos, etc. The memory 804 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.

[0178] The power supply component 806 provides power to the various components of the device 800. The power supply component 806 may include a power management system, one or more power supplies, and other components associated with generating, managing, and distributing power for the device 800.

[0179] The multimedia component 808 includes a screen that provides an output interface between the device 800 and the user. In some embodiments, the screen may include a liquid crystal display (LCD) and a touch panel (TP). If the screen includes a touch panel, the screen may be implemented as a touch screen to receive input signals from the user. The touch panel includes one or more touch sensors to sense touch, slide, and gestures on the touch panel. The touch sensor may not only sense the boundaries of the touch or slide action, but also detect the duration and pressure associated with the touch or slide operation. In some embodiments, the multimedia component 808 includes a front camera and / or a rear camera. When the device 800 is in an operating mode, such as a shooting mode or a video mode, the front camera and / or the rear camera may receive external multimedia data. Each front camera and rear camera may be a fixed optical lens system or have a focal length and optical zoom capability.

[0180] The audio component 810 is configured to output and / or input audio signals. For example, the audio component 810 includes a microphone (MIC), and when the device 800 is in an operating 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 804 or sent via the communication component 816. In some embodiments, the audio component 810 also includes a speaker for outputting audio signals.

[0181] I / O interface 812 provides an interface between processing component 802 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.

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

[0183] The communication component 816 is configured to facilitate wired or wireless communication between the device 800 and other devices. The device 800 can access a wireless network based on a communication standard, such as Wi-Fi, 4G or 5G, or a combination thereof. In an exemplary embodiment, the communication component 816 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 816 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.

[0184] In an exemplary embodiment, the apparatus 800 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 to perform the above method.

[0185] In an exemplary embodiment, a non-transitory computer-readable storage medium including instructions is also provided, such as a memory 804 including instructions, and the instructions can be executed by the processor 820 of the device 800 to perform the above method. For example, the non-transitory computer-readable storage medium can be a ROM, a random access memory (RAM), a CD-ROM, a magnetic tape, a floppy disk, an optical data storage device, etc.

[0186] A non-transitory computer-readable storage medium, when the instructions in the storage medium are executed by a processor of an IMS registration processing device, enables the IMS registration processing device to perform an IMS registration processing method, the method comprising:

[0187] In the case of monitoring an IMS registration failure, determining whether the terminal device is in a target usage scenario;

[0188] When the terminal device is in the target usage scenario, determining a target recovery strategy based on a current error code of the IMS registration failure, wherein the target recovery strategy is used to indicate automatic recovery of the IMS registration failure;

[0189] In case the target recovery strategy is successfully executed, the IMS registration is restarted.

[0190] It should be understood that "one embodiment" or "an embodiment" mentioned throughout the specification means that specific features, structures or characteristics related to the embodiment are included in at least one embodiment of the present disclosure. Therefore, "in one embodiment" or "in an embodiment" appearing throughout the specification does not necessarily refer to the same embodiment. In addition, these specific features, structures or characteristics can be combined in one or more embodiments in any suitable manner. It should be understood that in the various embodiments of the present disclosure, the size of the serial number of the above-mentioned processes does not mean the order of execution. The execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of the present disclosure. The serial numbers of the embodiments of the present disclosure are for description only and do not represent the advantages and disadvantages of the embodiments.

[0191] It should be noted that, in this article, the terms "include", "comprises" or any other variations thereof are intended to cover non-exclusive inclusion, so that a process, method, article or device including a series of elements includes not only those elements, but also other elements not explicitly listed, or also includes elements inherent to such process, method, article or device. In the absence of further restrictions, an element defined by the sentence "comprises a ..." does not exclude the existence of other identical elements in the process, method, article or device including the element.

[0192] In the several embodiments provided in the present disclosure, it should be understood that the disclosed devices and methods can be implemented in other ways. The device embodiments described above are only schematic. For example, the division of the units is only a logical function division. There may be other division methods in actual implementation, such as: multiple units or components can be combined, or can be integrated into another system, or some features can be ignored, or not executed. In addition, the coupling, direct coupling, or communication connection between the components shown or discussed can be through some interfaces, and the indirect coupling or communication connection of the devices or units can be electrical, mechanical or other forms.

[0193] The units described above as separate components may or may not be physically separated, and the components displayed as units may or may not be physical units; they may be located in one place or distributed on multiple network units; some or all of the units may be selected according to actual needs to achieve the purpose of the present embodiment.

[0194] In addition, all functional units in the embodiments of the present disclosure may be integrated into one processing unit, or each unit may be separately configured as a unit, or two or more units may be integrated into one unit; the above-mentioned integrated units may be implemented in the form of hardware or in the form of hardware plus software functional units.

[0195] Those skilled in the art will readily appreciate other embodiments of the present disclosure after considering the specification and practicing the invention disclosed herein. The present disclosure is intended to cover any variations, uses or adaptations of the present disclosure that follow the general principles of the present disclosure and include common knowledge or customary techniques in the art that are not disclosed in the present disclosure. The description and examples are to be considered exemplary only, and the true scope and spirit of the present disclosure are indicated by the following claims.

[0196] It should be understood that the present disclosure is not limited to the exact structures that have been described above and shown in the drawings, and that various modifications and changes may be made without departing from the scope thereof. The scope of the present disclosure is limited only by the appended claims.

Claims

1. A method for processing IMS registration, characterized in that: include: In the case of detecting an IMS registration failure, determining whether the terminal device is in a target usage scenario; When the terminal device is in the target usage scenario, determining a target recovery strategy based on a current error code of the IMS registration failure, wherein the target recovery strategy is used to indicate automatic recovery of the IMS registration failure; In case the target recovery strategy is successfully executed, the IMS registration is restarted.

2. The method according to claim 1, characterized in that The determining whether the terminal device is in a target usage scenario when an IMS registration failure is detected includes: When an IMS registration failure is detected, starting a first timer; When the timing duration of the first timer reaches a first preset duration, determining whether a message of successful IMS registration is monitored; If no IMS registration success message is detected, it is determined whether the terminal device is in a target usage scenario.

3. The method according to claim 2, characterized in that If the IMS registration success message is not detected, determining whether the terminal device is in the target usage scenario includes: If no IMS registration success message is detected, determining the network data demand and / or application running status of the terminal device; When the network data demand is less than a preset demand and / or the application running state meets a preset running condition, it is determined that the terminal device is in the target usage scenario.

4. The method according to claim 1, characterized in that: The determining of a target recovery strategy based on a current error code of an IMS registration failure when the terminal device is in the target usage scenario includes: When the terminal device is in the target usage scenario, the current error code is compared with each preset error code in a preset database; wherein the preset error code and the preset recovery strategy are stored in the preset database, and the preset error code and the corresponding preset recovery strategy satisfy a preset mapping relationship; The preset recovery strategy corresponding to the preset error code identical to the current error code in the preset database is determined as the target recovery strategy.

5. The method according to claim 4, characterized in that The method further comprises: When there is no preset error code identical to the current error code in the preset database, the current error code is updated to the preset database.

6. The method according to claim 1, characterized in that The method further comprises: The cause value of the last IMS registration failure during the period from the time when the IMS registration failure is first detected to the current time is determined as the current cause value; The current reason value is converted into the current error code.

7. The method according to claim 1, characterized in that The method further comprises: Determining whether the reason for the IMS registration failure exists in a filtering reason database; In the case where the reason for the IMS registration failure exists in the filtering reason database, the reporting of the IMS registration failure is ignored.

8. The method according to any one of claims 1 to 7, characterized in that: The method further comprises: After restarting the IMS registration, starting a second timer; When the timing duration of the second timer reaches a second preset duration, the registration status of the IMS registration is obtained.

9. An IMS registration processing device, characterized in that: include: A first determination module is configured to determine whether the terminal device is in a target usage scenario when an IMS registration failure is detected; A second determination module is configured to determine a target recovery strategy based on a current error code of the IMS registration failure when the terminal device is in the target usage scenario, wherein the target recovery strategy is used to indicate automatic recovery of the IMS registration failure; The execution module is configured to restart the IMS registration when the target recovery strategy is successfully executed.

10. An IMS registration processing device, characterized in that: include: processor; a memory for storing processor-executable instructions; The processor is configured to: implement the steps in any one of the IMS registration processing methods in claims 1 to 8 when executing.

11. A non-transitory computer-readable storage medium, when the instructions in the storage medium are executed by a processor of an IMS registration processing device, the device is enabled to perform the steps in any one of the IMS registration processing methods of claims 1 to 8.

Images