Internet protocol multimedia subsystem service processing method and electronic device

By disabling the IMS function and performing self-healing when IMS service request responses fail, the problem of increased power consumption and service anomalies caused by inconsistent IMS network quality is solved, achieving power optimization and improved user experience.

CN120768879BActive Publication Date: 2026-07-07HONOR DEVICE CO LTD

Patent Information

Authority / Receiving Office
CN · China
Patent Type
Patents(China)
Current Assignee / Owner
HONOR DEVICE CO LTD
Filing Date
2024-03-29
Publication Date
2026-07-07

Smart Images

  • Figure CN120768879B_ABST
    Figure CN120768879B_ABST
Patent Text Reader

Abstract

The application discloses an Internet protocol multimedia subsystem service processing method and electronic equipment, and relates to the technical field of communication, and comprises the following steps: an electronic equipment sends an Internet protocol multimedia subsystem (IMS) service request to a public land mobile network (PLMN) where an IMS in a region where the electronic equipment is located; if the IMS service request is the first IMS service request sent by the electronic equipment to the PLMN in the region where the electronic equipment is located, the electronic equipment closes an IMS function of the electronic equipment when an IMS service request response fails; and the electronic equipment closes the IMS function of the electronic equipment in the case that the IMS service request response fails, and the self-recovery of the IMS function can reduce the power consumption of the electronic equipment and avoid the poor experience caused by the abnormal execution of the IMS service.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] This application relates to the field of communication technology, and in particular to a service processing method and electronic device for the Internet Protocol Multimedia Subsystem. Background Technology

[0002] Before electronic devices leave the factory, the relevant parameters of the Internet-protocol Multimedia Subsystem (IMS) can be configured. This IMS parameter configuration refers to configuring the relevant parameters of IMS provided by multiple operators for different regions within the electronic device. This allows the electronic device to access the corresponding region's IMS based on these parameters and execute IMS services (functions).

[0003] The configuration of the aforementioned IMS-related parameters can include the configuration of IMS-related parameters for multiple regions. If the electronic device is not configured with IMS-related parameters for region 1, the electronic device will not attempt to access IMS (i.e., register with IMS) in region 1, and will also be unable to use IMS services. If the electronic device is configured with IMS-related parameters for region 2, when the electronic device is located in region 2, it can use IMS services in region 2 after accessing IMS (i.e., completing IMS registration). In order for the electronic device to use IMS services in various regions, IMS-related parameters for multiple regions worldwide can be configured on the electronic device.

[0004] However, the network quality of IMS varies across different regions of the world. When electronic devices are located in areas with poor network quality, it can cause problems such as failure or abnormality in the execution of IMS services. Summary of the Invention

[0005] This application provides an Internet Protocol Multimedia Subsystem (IMS) service processing method and an electronic device. When the IMS service request response fails, the electronic device shuts down the IMS function and performs self-healing of the IMS function. This reduces the power consumption of the electronic device and avoids the poor user experience caused by abnormal IMS service execution.

[0006] To achieve the above objectives, the embodiments of this application adopt the following technical solutions:

[0007] Firstly, a method for processing services in the Internet Protocol Multimedia Subsystem is provided, including:

[0008] Electronic devices send IMS service requests to the Public Land Mobile Network (PLMN) where the Internet Protocol Multimedia Subsystem (IMS) is located in their region.

[0009] If the IMS service request is the first IMS service request sent by an electronic device to the PLMN in its local area, the electronic device will disable its IMS function if the IMS service request response fails.

[0010] In this application, if the electronic device confirms that the IMS service request is its first IMS service request sent to the PLMN, and the IMS service request fails to execute, the electronic device disables its IMS function. If the first IMS service request to the PLMN fails, it indicates that the electronic device has not previously sent any IMS-related service requests to the PLMN in its region. This suggests that the region where the electronic device is located does not support IMS services or that the IMS network is highly likely to be faulty. In this case, if the electronic device's IMS service request response fails, it will repeatedly attempt to re-initiate the IMS service request within a certain period. Such frequent initiation of unsuccessful IMS service requests increases the communication response time of the electronic device and causes unnecessary power consumption. Furthermore, executing IMS services in scenarios with poor IMS network quality is also highly likely to encounter anomalies. Therefore, disabling the electronic device's IMS function allows for self-healing of the IMS function, reducing power consumption and preventing a poor user experience caused by IMS service malfunctions.

[0011] In one possible implementation of the first aspect, after the electronic device sends an IMS service request to the Public Land Mobile Network (PLMN) where the Internet Protocol Multimedia Subsystem (IMS) resides in its region, the method further includes:

[0012] The electronic device starts the first timer.

[0013] Therefore, when an IMS service request fails to respond, the electronic device disables its IMS function, including:

[0014] If the electronic device does not receive a response to the IMS service request before the first timer expires, the electronic device disables the IMS function in the first manner, putting the electronic device into the first state.

[0015] In the first state, the electronic device needs to enable the IMS function by restarting the device, toggling airplane mode, or using a hot-swappable card.

[0016] In this application, a first timer can be set to detect whether the electronic device has received a response from the PLMN for the IMS service request before the first timer expires. If the electronic device does not receive a response for the IMS service request before the first timer expires, it indicates that there is an anomaly in the IMS network in the area where the electronic device is located, and the PLMN in the area where the electronic device is located has most likely never successfully responded to the IMS service request. In this case, strict self-healing of the IMS function is performed, and the IMS function of the electronic device is turned off in a first manner to put it in a first state. This can avoid the increased power consumption of the electronic device caused by frequently initiating unsuccessful IMS service requests. While reducing the power consumption of the electronic device, it can also avoid the poor user experience caused by the user using the IMS service but the IMS service is not performing properly.

[0017] In another possible implementation of the first aspect, after the electronic device sends an IMS service request to the Public Land Mobile Network (PLMN) where the Internet Protocol Multimedia Subsystem (IMS) resides in its region, the method further includes:

[0018] The electronic device starts the second timer.

[0019] Therefore, when an IMS service request fails to respond, the electronic device disables its IMS function, including:

[0020] If the electronic device receives a response carrying a failure reason before the second timer expires, and the failure reason indicates an IMS network failure, the electronic device disables the IMS function of the electronic device in a first manner, putting the electronic device into a first state.

[0021] In the first state, the electronic device needs to enable the IMS function by restarting the device, toggling airplane mode, or using a hot-swappable card.

[0022] In this application, when an electronic device receives a request failure response, it can further perform IMS function self-healing based on the failure reason carried in the response. For example, if the failure reason indicates an IMS network failure, strict IMS function self-healing can be performed, disabling the IMS function of the electronic device and placing it in the first state. This avoids the increased power consumption of the electronic device caused by frequently initiating unsuccessful IMS service requests. While reducing the power consumption of the electronic device, it also avoids the poor user experience caused by using IMS services but experiencing abnormal IMS service execution.

[0023] In another possible implementation of the first aspect, when the IMS service request response fails, the electronic device disables the IMS function of the electronic device, further including:

[0024] If the failure is not due to an IMS network malfunction, the electronic device starts a third timer and sends multiple IMS service requests to the PLMN before the third timer expires. If all IMS service requests fail to respond before the third timer expires, the electronic device disables its IMS function in the first manner, placing the electronic device in the first state.

[0025] In this application, if the failure is not due to an IMS network failure, the IMS service request can be re-initiated before the third timer expires. Multiple attempts can increase the probability of a successful IMS service request and avoid situations where IMS services cannot be executed due to accidental abnormalities.

[0026] In another possible implementation of the first aspect, after the electronic device sends an IMS service request to the Public Land Mobile Network (PLMN) where the Internet Protocol Multimedia Subsystem (IMS) resides in its region, the method further includes:

[0027] If the IMS service request electronic device is not sending an IMS service request to the PLMN for the first time, the electronic device starts the fourth timer.

[0028] If all IMS service requests sent by the electronic device fail to respond before the fourth timer expires, and the failure condition is met, the electronic device disables the IMS function in the second manner, putting the electronic device into the second state.

[0029] In this context, the electronic device is in a second state, indicating that the IMS function of the electronic device is turned off when the IMS service request response fails, and the IMS function of the electronic device is turned on after a preset first time period. The failure conditions include the number of IMS service request response failures reaching a preset threshold before the fourth timer expires, or the probability of IMS service request response failure exceeding a preset probability threshold.

[0030] In this application, when the electronic device sending the IMS service request to the PLMN of the current region for the first time, in order to further confirm the IMS capability / network status of the region, the electronic device can start a fourth timer. When the IMS service request response fails, it can further determine whether to perform a certain degree of IMS service processing based on whether the region or the service request meets the failure conditions, thus avoiding the situation where IMS service execution is abnormal due to IMS network abnormality in the region.

[0031] In another possible implementation of the first aspect, the electronic device has a pre-installed IMS configuration list, which includes multiple regions, IMS configuration parameters corresponding to each region, and the network status of the IMS corresponding to each region; wherein, the network status of the IMS includes network normal or network abnormal.

[0032] The method also includes:

[0033] The electronic device will send the operational data of the IMS service requests generated in its local area to the cloud; the operational data includes the operational data corresponding to the failure of the electronic device to send the IMS service request to the PLMN in its local area, or the operational data corresponding to the successful response of the IMS service request.

[0034] Electronic devices receive a target IMS configuration list from the cloud; the target IMS configuration list is a list updated by the cloud based on operational data, showing the IMS configuration parameters corresponding to the region and the network status of the IMS corresponding to the region.

[0035] The electronic device updates the preset number of failures threshold and / or the preset probability threshold in the failure conditions according to the target IMS configuration list.

[0036] In this application, for regions where IMS capability is disabled by default in the target IMS configuration list, electronic devices can still attempt to send IMS service requests upon arriving in that region. In this case, the electronic device can adaptively reduce the number of preset thresholds for determining whether failure conditions are met during IMS service processing in that region, and also reduce the preset probability thresholds for determining whether failure conditions are met during IMS service processing in that region. This reduces the number of IMS service attempts in that region, while minimizing the power consumption of the electronic device during IMS service attempts. In this embodiment, the cloud can update the default IMS function enabled or disabled for each region based on the region's network status, the frequency and number of times users use IMS services in their region, making the IMS configuration list more accurate.

[0037] In another possible implementation of the first aspect, the IMS service request includes an IMS registration request and an IMS call request; the method further includes:

[0038] The electronic device sends an IMS registration request to the PLMN where the IMS is located in its region.

[0039] Once the electronic device receives a successful registration response for the IMS registration request, the electronic device establishes a connection with IMS.

[0040] The electronic device sends an IMS service request to the Public Land Mobile Network (PLMN) where the Internet Protocol Multimedia Subsystem (IMS) is located, including:

[0041] The electronic device sends an IMS call request to the PLMN in its region.

[0042] If the IMS service request is the first IMS service request sent by the electronic device to the PLMN, and the IMS service request response fails, the electronic device disables its IMS function, including:

[0043] If the IMS call request is the first IMS call request sent by the electronic device to the PLMN, when the IMS call request response fails, the electronic device disables the IMS function of the electronic device in the first manner, putting the electronic device into the first state; wherein, the electronic device in the first state needs to enable the IMS function of the electronic device by any one of the following methods: device restart, toggling airplane mode, or hot-swapping card;

[0044] If the IMS call request is not the first IMS call request sent by the electronic device to the PLMN, and the IMS call request response fails and the IMS signal strength is less than the preset signal strength threshold, the electronic device disables the IMS function of the electronic device in a third way, putting the electronic device into a third state.

[0045] In the first state, the electronic device needs to enable its IMS function by restarting the device, switching airplane mode on or off, or hot-swapping the card. In the third state, the electronic device disables its IMS function when the IMS service request response fails, and enables its IMS function after a preset second time interval.

[0046] In this application, after the electronic device completes IMS registration, other IMS services are executed. For example, when making an IMS call request, a determination is made regarding whether to perform IMS self-healing processing upon receiving call failure monitoring information. If the monitoring information indicates a failure of the first IMS call request, strict IMS self-healing is performed, disabling the IMS function of the electronic device and placing it in a first state. If the monitoring information indicates a failure of a non-first IMS call request, and the IMS signal strength is determined to be less than a preset signal strength threshold, low-level IMS self-healing is performed, disabling the IMS function of the electronic device in a third manner and placing it in a third state. By executing different levels of IMS self-healing for call failures in different scenarios, the power consumption of the electronic device is reduced, and the on / off control of the IMS function is more accurately implemented, optimizing the user experience of using IMS services.

[0047] In another possible implementation of the first aspect, after the electronic device sends an IMS service request to the Public Land Mobile Network (PLMN) where the Internet Protocol Multimedia Subsystem (IMS) resides in its region, the method further includes:

[0048] Electronic devices acquire geographical location information.

[0049] If the geographic location information indicates that the electronic device is in the first area it arrives at, the electronic device determines that the IMS service request is the first IMS service request sent to the PLMN.

[0050] In this application, if the IMS service request is the first IMS service request sent by an electronic device to the PLMN in its current location, meaning the electronic device has not previously performed IMS services in that location, a failure in the response to this first IMS service request would highly suggest that the location does not support IMS services or that the IMS network is abnormal. However, if the IMS service request is a subsequent request sent by the electronic device to the PLMN in its current location, meaning the electronic device has previously sent IMS service requests in that location (which may have responded successfully or failed), a failure in the current IMS service request does not necessarily indicate that the location does not support IMS services or that the IMS network is abnormal. Therefore, whether the IMS service request sent by the electronic device is the first IMS service request sent to the local IMS network can serve as an important criterion in this embodiment to indirectly confirm the IMS network status of the current location.

[0051] In a second aspect, an electronic device is provided, comprising a memory, a processor, and a computer program stored in the memory, wherein the processor executes the computer program to implement the steps of the method described in any of the first aspects above.

[0052] Thirdly, a computer-readable storage medium is provided that stores instructions which, when executed by a processor, implement the steps of the method described in any of the first aspects above.

[0053] Fourthly, a computer program product including instructions is provided, comprising a computer program / instructions that, when executed by a processor, implement the steps of the method described in any of the first aspects above.

[0054] Fifthly, embodiments of this application provide a chip, the chip including a processor, the processor being configured to invoke a computer program in memory to perform the method as described in any one of the first aspects.

[0055] It is understood that the beneficial effects of the electronic device described in the second aspect, the computer-readable storage medium described in the third aspect, the computer program product described in the fourth aspect, and the chip described in the fifth aspect can be referred to the beneficial effects of the first aspect and any of its possible design embodiments, which will not be repeated here. Attached Figure Description

[0056] Figure 1 This is a schematic diagram of an application scenario provided by an embodiment of this application;

[0057] Figure 2 This is a schematic diagram of the structure of an electronic device provided in an embodiment of this application;

[0058] Figure 3 A flowchart illustrating an IMS service processing method provided in an embodiment of this application;

[0059] Figure 4 A flowchart illustrating another IMS service processing method provided in this application embodiment;

[0060] Figure 5 A flowchart illustrating another IMS service processing method provided in this application embodiment;

[0061] Figure 6 A flowchart illustrating an IMS service processing method using an IMS registration request as an example, provided for an embodiment of this application;

[0062] Figure 7 A flowchart illustrating another IMS service processing method provided in this application embodiment;

[0063] Figure 8 A flowchart illustrating another IMS service processing method provided in this application embodiment;

[0064] Figure 9 This is a flowchart illustrating a more specific IMS service processing method, taking a VoLTE call as an example, as an embodiment of this application.

[0065] Figure 10 A flowchart illustrating a terminal update IMS configuration list is provided in an embodiment of this application;

[0066] Figure 11 This is a schematic diagram of the structure of another electronic device provided in an embodiment of this application;

[0067] Figure 12 This is a schematic diagram of a chip system provided in an embodiment of this application. Detailed Implementation

[0068] In the description of the embodiments of this application, the terminology used in the following embodiments is for the purpose of describing specific embodiments only and is not intended to be a limitation of this application. As used in the specification and appended claims of this application, the singular expressions "a," "the," "the," "the," and "this" are intended to also include expressions such as "one or more," unless the context clearly indicates otherwise. It should also be understood that in the following embodiments of this application, "at least one" and "one or more" refer to one or more (including two). The term "and / or" is used to describe the relationship between related objects, indicating that three relationships can exist; for example, A and / or B can indicate: A alone, A and B simultaneously, or B alone, where A and B can be singular or plural. The character " / " generally indicates that the preceding and following related objects are in an "or" relationship.

[0069] References to "one embodiment" or "some embodiments" in this specification mean that one or more embodiments of this application include a specific feature, structure, or characteristic described in connection with that embodiment. Therefore, the phrases "in one embodiment," "in some embodiments," "in other embodiments," "in still other embodiments," etc., appearing in different parts of this specification do not necessarily refer to the same embodiment, but rather mean "one or more, but not all, embodiments," unless otherwise specifically emphasized. The terms "comprising," "including," "having," and variations thereof mean "including but not limited to," unless otherwise specifically emphasized. The term "connection" includes direct connections and indirect connections, unless otherwise stated. "First" and "second" are used for descriptive purposes only and should not be construed as indicating or implying relative importance or implicitly specifying the number of technical features indicated.

[0070] In the embodiments of this application, the terms "exemplary" or "for example" are used to indicate that something is an example, illustration, or description. Any embodiment or design that is described as "exemplary" or "for example" in the embodiments of this application should not be construed as being more preferred or advantageous than other embodiments or design. Specifically, the use of the terms "exemplary" or "for example" is intended to present the relevant concepts in a specific manner.

[0071] Before electronic devices leave the factory, the relevant parameters of the Internet-protocol Multimedia Subsystem (IMS) can be configured. This IMS parameter configuration refers to configuring the IMS parameters provided by different regional operators within the electronic device. This allows the electronic device, when IMS is enabled, to access the corresponding regional IMS and perform IMS services based on these parameters.

[0072] The electronic device allows for the configuration of IMS-related parameters for multiple regions. For example, refer to... Figure 1 , Figure 1 A schematic diagram of an application scenario is provided. Figure 1 In (a), if the electronic device is in region 1 and the IMS-related parameters for region 1 are not configured in the electronic device, the electronic device will not attempt to access IMS (i.e., register with IMS) in region 1 and will not be able to use IMS services. Figure 1 In (b), if the electronic device is located in Region 2 and the IMS-related parameters for Region 2 have been configured in the electronic device, then after accessing IMS (i.e., completing IMS registration), the electronic device can use IMS services in Region 2. To provide the electronic device with the possibility of using IMS services in various regions, IMS-related parameters for multiple regions globally can be configured in the electronic device.

[0073] For example, an IMS default enabled list can be pre-configured in an electronic device. This list includes multiple IMS parameter groups from public land mobile networks (PLMNs) of various operators in multiple regions worldwide. Pre-configuring the IMS default enabled list in an electronic device means that if the device is located in a region included in the list, it will, by default, enable the IMS function and send IMS service requests (e.g., IMS registration requests) to the IMS provider in that region.

[0074] However, the network quality of PLMNs varies across different regions globally. After configuring IMS-related parameters for multiple regions on an electronic device, if there are compatibility issues between the IMS in the device's current region and the device's IMS function, or if the IMS in the device's current region has poor network quality, the electronic device may be unable to access IMS. After the initial IMS registration fails, the electronic device will frequently initiate IMS registration requests, causing unnecessary power consumption increases. Furthermore, even if the electronic device successfully registers for IMS, it may experience problems such as failure to execute IMS services or abnormal IMS service execution. For example, when the IMS service is an IMS call, problems such as IMS call initiation failure, IMS call connection abnormalities, and poor IMS call communication quality may occur. This creates a poor user experience where the electronic device has IMS enabled and is providing IMS services, but cannot perform IMS services properly.

[0075] Let's illustrate the problems with existing technologies using a specific scenario. For example, when an electronic device is in Region 1, its first IMS registration request to the PLMN network, if successful, indicates that Region 1 supports IMS, and the electronic device can use IMS services in Region 1. The probability of successful IMS registration after a device reboot in Region 1, or the probability of other electronic devices successfully registering for the first time in Region 1, is extremely high, and therefore the probability of successfully performing IMS services (such as IMS calls) is also extremely high. Conversely, if the electronic device fails to register for IMS on the first attempt or the IMS service is unavailable, it indicates that the IMS network in the current region is very likely poor. To avoid a poor user experience when using IMS services, the IMS function of the electronic device needs to be disabled promptly. This prevents creating the illusion that IMS services are available to users in scenarios where IMS services are not supported, ultimately leading to problems such as users being unable to use IMS services or electronic devices malfunctioning when performing IMS services.

[0076] This application provides a method for processing Internet Protocol Multimedia Subsystem (IMS) services. When an electronic device sends an IMS service request to the IMS in its local area, if this is the first IMS service request sent by the electronic device to the PLMN, the electronic device disables its IMS function if the IMS service request response fails. If the first IMS service request to the PLMN fails to respond, it indicates that the electronic device has not previously sent any IMS service requests to the IMS in its local area. This suggests that the local area may not support IMS services, or that the IMS network in the local area may be faulty. In such cases, if the electronic device's IMS service request response fails, it will repeatedly attempt to re-initiate the IMS service request over a period of time. Such frequent initiation of unsuccessful IMS service requests increases the power consumption of the electronic device. Furthermore, in scenarios with poor IMS network quality, even if the electronic device successfully registers for IMS, the IMS service is highly likely to malfunction. Therefore, disabling the electronic device's IMS function allows for self-healing of the IMS function, reducing power consumption and preventing a poor user experience caused by IMS service malfunctions.

[0077] The IMS service processing method provided in this application can be applied to electronic devices. In this application, the electronic device can be any electronic device capable of communicating with another electronic device via a wireless communication network (e.g., a 5G network) and IMS. The electronic device may have a subscriber identification module (SIM) card interface for inserting a SIM card into the electronic device and communicating with another electronic device via the SIM card. Alternatively, the electronic device can communicate with another electronic device via an embedded SIM (eSIM) card. The electronic device can be a mobile phone, tablet computer, computer with wireless transceiver capabilities, virtual reality device, augmented reality device, wireless device in industrial control, wireless device in autonomous driving, wireless device in telemedicine, wireless device in smart grids, wireless device in transportation safety, wireless device in smart cities, wireless device in smart homes, etc. The following embodiments do not impose special limitations on the specific form of the electronic device.

[0078] Figure 2 A schematic diagram of the structure of an electronic device 100 provided in this embodiment is shown.

[0079] Electronic device 100 may include processor 110, external memory interface 120, internal memory 121, universal serial bus (USB) interface 130, charging management module 140, power management module 141, battery 142, antenna 1, antenna 2, mobile communication module 150, wireless communication module 160, audio module 170, sensor module 180, display screen 194, and subscriber identification module (SIM) card interface 195, etc.

[0080] It is understood that the structures illustrated in the embodiments of the present invention do not constitute a specific limitation on the electronic device 100. In other embodiments of this application, the electronic device 100 may include more or fewer components than illustrated, or combine some components, or split some components, or have different component arrangements. The illustrated components may be implemented in hardware, software, or a combination of software and hardware.

[0081] Processor 110 may include one or more processing units, such as: application processor (AP), modem processor, graphics processing unit (GPU), image signal processor (ISP), controller, memory, video codec, digital signal processor (DSP), baseband processor, and / or neural network processing unit (NPU), etc. Different processing units may be independent devices or integrated into one or more processors.

[0082] The controller can be the nerve center and command center of the electronic device 100. The controller can generate operation control signals according to the instruction opcode and timing signals to complete the control of fetching and executing instructions.

[0083] The processor 110 may also include a memory for storing instructions and data. In some embodiments, the memory in the processor 110 is a cache memory. This memory can store instructions or data that the processor 110 has just used or that are used repeatedly. If the processor 110 needs to use the instruction or data again, it can directly retrieve it from the memory. This avoids repeated accesses, reduces the waiting time of the processor 110, and thus improves the efficiency of the system.

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

[0085] It is understood that the interface connection relationships between the modules illustrated in the embodiments of the present invention are merely illustrative and do not constitute a structural limitation on the electronic device 100. In other embodiments of this application, the electronic device 100 may also employ different interface connection methods or combinations of multiple interface connection methods as described in the above embodiments.

[0086] The charging management module 140 receives charging input from a charger. The charger can be a wireless charger or a wired charger. In some wired charging embodiments, the charging management module 140 receives charging input from the wired charger via the USB interface 130. In some wireless charging embodiments, the charging management module 140 receives wireless charging input via the wireless charging coil of the electronic device 100. While charging the battery 142, the charging management module 140 can also supply power to the electronic device via the power management module 141.

[0087] The power management module 141 connects the battery 142, the charging management module 140, and the processor 110. The power management module 141 receives input from the battery 142 and / or the charging management module 140, providing power to the processor 110, internal memory 121, external memory, display screen 194, camera 193, and wireless communication module 160, etc. The power management module 141 can also monitor parameters such as battery capacity, battery cycle count, and battery health status (leakage current, impedance). In some other embodiments, the power management module 141 may also be located within the processor 110. In other embodiments, the power management module 141 and the charging management module 140 may be located in the same device.

[0088] The wireless communication function of electronic device 100 can be realized through antenna 1, antenna 2, mobile communication module 150, wireless communication module 160, modem processor and baseband processor, etc.

[0089] Antenna 1 and antenna 2 are used to transmit and receive electromagnetic wave signals. Each antenna in electronic device 100 can be used to cover one or more communication frequency bands. Different antennas can also be multiplexed to improve antenna utilization. For example, antenna 1 can be multiplexed as a diversity antenna for a wireless local area network. In some other embodiments, the antennas can be used in conjunction with tuning switches.

[0090] The mobile communication module 150 can provide solutions for wireless communication, including 2G / 3G / 4G / 5G, applied to the electronic device 100. The mobile communication module 150 may include at least one filter, switch, power amplifier, low noise amplifier (LNA), etc. The mobile communication module 150 can receive electromagnetic waves via antenna 1, and perform filtering, amplification, and other processing on the received electromagnetic waves before transmitting them to a modem processor for demodulation. The mobile communication module 150 can also amplify the signal modulated by the modem processor and convert it into electromagnetic waves for radiation via antenna 1. In some embodiments, at least some functional modules of the mobile communication module 150 may be housed in the processor 110. In some embodiments, at least some functional modules of the mobile communication module 150 and at least some modules of the processor 110 may be housed in the same device.

[0091] The modem processor may include a modulator and a demodulator. The modulator modulates the low-frequency baseband signal to be transmitted into a mid-to-high frequency signal. The demodulator demodulates the received electromagnetic wave signal into a low-frequency baseband signal. The demodulator then transmits the demodulated low-frequency baseband signal to the baseband processor for processing. After processing by the baseband processor, the low-frequency baseband signal is transmitted to the application processor. The application processor outputs sound signals through an audio device (not limited to speaker 170A, receiver 170B, etc.) or displays images or videos through the display screen 194. In some embodiments, the modem processor may be a separate device. In other embodiments, the modem processor may be independent of the processor 110 and may be housed in the same device as the mobile communication module 150 or other functional modules.

[0092] The wireless communication module 160 can provide solutions for wireless communication applications on the electronic device 100, including wireless local area networks (WLAN) (such as wireless fidelity (Wi-Fi) networks), Bluetooth (BT), global navigation satellite system (GNSS), frequency modulation (FM), near field communication (NFC), and infrared (IR). The wireless communication module 160 can be one or more devices integrating at least one communication processing module. The wireless communication module 160 receives electromagnetic waves via antenna 2, performs frequency modulation and filtering of the electromagnetic wave signals, and sends the processed signal to processor 110. The wireless communication module 160 can also receive signals to be transmitted from processor 110, perform frequency modulation and amplification, and convert them into electromagnetic waves for radiation via antenna 2.

[0093] In some embodiments, antenna 1 of electronic device 100 is coupled to mobile communication module 150, and antenna 2 is coupled to wireless communication module 160, enabling electronic device 100 to communicate with networks and other devices via wireless communication technology. The wireless communication technology may include Global System for Mobile Communications (GSM), General Packet Radio Service (GPRS), Code Division Multiple Access (CDMA), Wideband Code Division Multiple Access (WCDMA), Time Division Code Division Multiple Access (TD-SCDMA), Long Term Evolution (LTE), BT, GNSS, WLAN, NFC, FM, and / or IR technologies, etc. The GNSS may include the Global Positioning System (GPS), the Global Navigation Satellite System (GLONASS), the BeiDou Navigation Satellite System (BDS), the Quasi-Zenith Satellite System (QZSS), and / or satellite-based augmentation systems (SBAS).

[0094] In this embodiment, the electronic device can establish a communication connection with IMS via a mobile communication module and send IMS service requests to the PLMN, such as IMS registration requests, IMS call requests, IMS roaming requests, etc. The electronic device can also receive responses to IMS service requests via the mobile communication module, such as receiving a registration success response for an IMS registration request, a call success response for an IMS call request, etc.

[0095] Electronic device 100 implements display functions through a GPU, a display screen 194, and an application processor. The GPU is a microprocessor for image processing, connected to the display screen 194 and the application processor. The GPU is used to perform mathematical and geometric calculations and for graphics rendering. Processor 110 may include one or more GPUs, which execute program instructions to generate or modify display information.

[0096] Display screen 194 is used to display images, videos, etc. Display screen 194 includes a display panel. The display panel may be a liquid crystal display (LCD), an organic light-emitting diode (OLED), an active-matrix organic light-emitting diode (AMOLED), a flexible light-emitting diode (FLED), a miniature LED, a microLED, a quantum dot light-emitting diode (QLED), etc. In some embodiments, electronic device 100 may include one or N displays 194, where N is a positive integer greater than 1.

[0097] In some embodiments, when the IMS function of an electronic device is turned off, a prompt message reminding the user that the IMS function has been turned off can be displayed on the screen in the form of a floating window, capsule, pop-up, etc. When the IMS function of an electronic device is turned on, a prompt message reminding the user that the IMS function has been turned on can be displayed on the screen in the form of a floating window, capsule control, pop-up, etc.

[0098] The external storage interface 120 can be used to connect an external memory card, such as a Micro SD card, to expand the storage capacity of the electronic device 100. The external memory card communicates with the processor 110 through the external storage interface 120 to perform data storage functions. For example, music, video, and other files can be saved on the external memory card.

[0099] Internal memory 121 can be used to store computer executable program code, which includes instructions. Processor 110 executes various functional applications and data processing of electronic device 100 by running the instructions stored in internal memory 121. Internal memory 121 may include a program storage area and a data storage area. The program storage area may store the operating system, at least one application program required for a function (such as sound playback, image playback, etc.), etc. The data storage area may store data created during the use of electronic device 100 (such as audio data, phonebook, etc.). Furthermore, internal memory 121 may include high-speed random access memory and may also include non-volatile memory, such as at least one disk storage device, flash memory device, universal flash storage (UFS), etc.

[0100] Electronic device 100 can implement audio functions such as music playback and recording through audio module 170, speaker, receiver, microphone, headphone jack, and application processor.

[0101] The SIM card interface 195 is used to connect a SIM card. The SIM card can be inserted into or removed from the SIM card interface 195 to make contact with and separate from the electronic device 100. The electronic device 100 can support one or N SIM card interfaces, where N is a positive integer greater than 1. The SIM card interface 195 can support Nano SIM cards, Micro SIM cards, SIM cards, etc. Multiple cards can be inserted into the same SIM card interface 195 simultaneously. The multiple cards can be of the same or different types. The SIM card interface 195 is also compatible with different types of SIM cards. The SIM card interface 195 is also compatible with external memory cards. The electronic device 100 interacts with the network through the SIM card to realize functions such as calls and data communication. In some embodiments, the electronic device 100 uses an eSIM, i.e., an embedded SIM card. The eSIM card can be embedded in the electronic device 100 and cannot be separated from the electronic device 100.

[0102] In some embodiments, the electronic device disables its IMS function under certain circumstances, placing the electronic device in a first state. In this case, the IMS function can be enabled by any of the following methods: restarting the electronic device, toggling airplane mode, or hot-swapping the SIM card. This is because the electronic device automatically enables / restarts its IMS function by default after each power-on, restart, toggling airplane mode, or hot-swapping the SIM card.

[0103] In some embodiments, the electronic device triggers the IMS activation / restart function upon detecting events such as power-on, restart, switching airplane mode on / off, or hot-swapping a SIM card. Simultaneously, the electronic device initiates an IMS registration request to the IMS provider of the PLMN in its local area. The region where the electronic device is located may or may not support IMS services. If the region does not support IMS services, or if the region supports IMS services but the IMS network quality is poor, the IMS may be unable to respond to the IMS registration request due to network anomalies, and the electronic device will not receive any response. Alternatively, the IMS may send a request failure response to the electronic device due to network anomalies, which may carry a Session Initiation Protocol (SIP) message. When the SIP message is a network failure message, such as a 403 message, it indicates that the IMS service request response has failed. Whether the electronic device receives no response to the IMS registration request or receives a request failure response, it means that the IMS registration request has failed. In this case, the electronic device can re-initiate the IMS registration request. However, due to network anomalies in IMS, even with multiple IMS registration requests, electronic devices are highly likely to fail to register successfully. Furthermore, existing communication systems do not limit the number of times an electronic device can re-initiate IMS registration requests. Therefore, electronic devices frequently re-initiate IMS registration requests when they fail, increasing power consumption. Alternatively, even if IMS registration is successful, network anomalies during IMS service execution can lead to service failures or malfunctions, resulting in a poor user experience despite being able to use IMS services.

[0104] This embodiment provides an IMS service processing method. In scenarios where electronic devices perform IMS services, the electronic device can promptly disable the IMS function under different circumstances, thus enabling IMS service processing. This avoids the increased response time and unnecessary power consumption caused by the electronic device repeatedly re-initiating IMS service requests when the IMS network is abnormal, and also prevents the electronic device from performing IMS services when the IMS network is abnormal. (See reference...) Figure 3 As shown, it includes:

[0105] S101. The electronic device sends an IMS service request to the PLMN where the IMS is located in the area.

[0106] The "location" refers to the current geographical location of the electronic device. The electronic device can be pre-configured to have IMS enabled by default. When the electronic device reaches a region where IMS is enabled by default, it will trigger the activation / reactivation of IMS upon detecting events such as power-on, restart, switching airplane mode on / off, or hot-swapping a SIM card. This will cause the electronic device to send a service IMS request to the PLMN in the current region.

[0107] For example, IMS service requests may include IMS registration requests, IMS call requests, roaming requests, etc. Among them, IMS call requests include Voice over Wi-Fi (VoWi-Fi) call requests, VoNR (Voice over new radio) call requests, VoLTE (Voice over long-term evolution) call requests, etc.

[0108] In some embodiments, electronic devices need to register with IMS before performing IMS calls. After successful IMS registration, the electronic device can continue to send other IMS service requests to the PLMN to perform the corresponding IMS services.

[0109] S102. The electronic device determines whether the service request is the first IMS service request sent to the PLMN.

[0110] In this embodiment, if the IMS service request is the first IMS service request sent by the electronic device to the PLMN in its current location, meaning the electronic device has not previously performed IMS services in that location, a failure in the response to this first IMS service request would strongly suggest that the location does not support IMS services or that the IMS network is abnormal. However, if the IMS service request is a subsequent request sent by the electronic device to the PLMN in its current location, meaning the electronic device has previously sent IMS service requests in that location (which may have responded successfully or failed), a failure in the current IMS service request does not necessarily indicate that the location does not support IMS services or that the IMS network is abnormal. Therefore, whether the IMS service request sent by the electronic device is the first IMS service request sent to the local IMS network can serve as an important criterion in this embodiment to indirectly confirm the IMS network status of the current location.

[0111] In this embodiment, the electronic device can obtain an IMS not registered identifier corresponding to its location. When the IMS not registered identifier is a first value (e.g., 1 or true), it indicates that the electronic device has not registered with the IMS in the location and has not performed other IMS services. The currently initiated IMS service request is the first IMS service request sent by the electronic device to the PLMN in the location. When the IMS not registered identifier is a second value (e.g., 0 or false), it indicates that the electronic device has registered with the IMS in the location and may have performed other IMS services. The currently initiated IMS service request is a non-first IMS service request sent by the electronic device to the PLMN in the location.

[0112] In some other implementations, electronic devices can also determine whether they are arriving at the location for the first time based on the recorded historical geographical location. If the geographical location of the location is not included in the historical geographical location, it is considered to be arriving at the location for the first time, and the IMS service request sent in the location is the first IMS service request.

[0113] Alternatively, electronic devices can determine whether the PLMN in the current region is the first PLMN to initiate an IMS service request based on the recorded historical PLMN addresses. If the historical PLMN addresses do not include the address of the PLMN in the current region, then the IMS service request sent to the PLMN in the current region is considered to be the first IMS service request.

[0114] In some other implementations, it can be determined whether the service request is the first IMS service request sent to the PLMN, but this is not limited here.

[0115] S103. If the service request is the first IMS service request sent to the PLMN, the electronic device shall disable the IMS function of the electronic device when the IMS service request response fails.

[0116] If the IMS service request is determined to be the first IMS service request sent by the electronic device to the PLMN in its current location, and the IMS service request response fails, it indicates that the area where the electronic device is located does not support IMS services or that the IMS network is highly likely to be abnormal. The electronic device will then disable its own IMS function.

[0117] Electronic devices can confirm IMS service request response failure in several ways. For example, if an electronic device does not receive a response to an IMS service request within a certain period of time, or if it receives a response carrying SIP within a certain period of time, it can confirm that the IMS service request response has failed. Here, SIP refers to messages such as the 403 message indicating network failure.

[0118] After confirming the failure of an IMS service request response, the electronic device disables its IMS function. This can be done by disabling the IMS function for a period of time and then re-enabling it after that period; or by permanently disabling the IMS function, which will only be enabled / reactivated when the electronic device is powered on, restarted, toggled in airplane mode, or hot-swapped. The electronic device can perform different levels of self-healing based on the initiation of the IMS service request and the specific network anomaly, to achieve different effects in IMS service processing under different scenarios. For example, disabling the IMS function in the first method puts it in the first state. In the first state, the IMS function will only be enabled / reactivated when the device is powered on, restarted, toggled in airplane mode, or hot-swapped. Alternatively, disabling the IMS function in the second method puts it in the second state. The second state means that the electronic device disables the IMS function when the IMS service request response fails and reactivates it after a preset first time period. Finally, disabling the IMS function in the third method puts it in the third state. The electronic device being in the third state means that the IMS function is disabled when the IMS service request response fails, and is reactivated after a preset second duration. Specifically, the IMS service processing level of the first method is higher than that of the second method; when the first duration is longer than the second duration, the IMS service processing level of the second method is higher than that of the third-party method; and when the second duration is longer than the first duration, the IMS service processing level of the third-party method is higher than that of the second method. This embodiment does not limit the number of IMS service processing level levels, nor does it limit the preset duration corresponding to different IMS service processing levels; these can be determined according to actual circumstances.

[0119] In this embodiment, if the electronic device confirms that the IMS service request is its first IMS service request sent to the PLMN, and the IMS service request fails to execute, the electronic device disables its IMS function. If the first IMS service request to the PLMN fails, it indicates that the electronic device has not previously sent any IMS-related service requests to the PLMN in its region. This suggests that the region where the electronic device is located does not support IMS services or that the IMS network is highly likely to be faulty. In this case, if the electronic device's IMS service request response fails, it will attempt to re-initiate the IMS service request multiple times over a period of time. Such frequent initiation of unsuccessful IMS service requests increases the communication response time of the electronic device and causes unnecessary power consumption. Furthermore, executing IMS services in scenarios with poor IMS network quality is also highly likely to result in anomalies. Therefore, disabling the electronic device's IMS function allows for self-healing of the IMS function, reducing power consumption and preventing a poor user experience caused by IMS service anomalies.

[0120] In some optional embodiments, different levels of IMS function self-healing can be performed based on the specific circumstances of the IMS service request response failure. (See reference...) Figure 4 As shown, another IMS service processing method is provided, including:

[0121] S201. The electronic device sends an IMS service request to the PLMN where the IMS is located in the area.

[0122] Refer to step S101 above.

[0123] S202, The electronic device starts the first timer.

[0124] In this embodiment, a first timer may be started when the electronic device sends an IMS service request to the PLMN; alternatively, the first timer may be started after the electronic device sends an IMS service request to the PLMN; or, the first timer may be started when the electronic device detects events such as power-on, restart, switching airplane mode on / off, or hot-swappable card events, triggering the electronic device to send an IMS service request. The first timer is used to monitor the response status of the first IMS service request sent.

[0125] S203. The electronic device determines whether the IMS service request is the first IMS service request sent by the electronic device to the PLMN.

[0126] Refer to step S102 above.

[0127] S204. If the IMS service request is the first IMS service request sent by the electronic device to the PLMN, and no response to the IMS service request is received before the first timer expires, the electronic device disables the IMS function of the electronic device in the first manner, so that the electronic device is in the first state.

[0128] In this embodiment, the first timer can also be understood as the maximum response time for the PLMN to IMS service requests. If the PLMN does not respond to the IMS service request before the first timer expires, it is considered that the PLMN's response time to the IMS service request exceeds the maximum response time, and the IMS service request response is considered to have failed.

[0129] If the IMS service request is the first IMS service request, and the electronic device does not receive a response corresponding to the IMS service request before the first timer expires, and the PLMN's response time for the IMS service request exceeds the maximum response time, then the IMS service request response is considered to have failed.

[0130] In this embodiment, the electronic device is in a first state, and the IMS function of the electronic device needs to be enabled by any one of the following methods: device restart, switching airplane mode on and off, or hot-swapping the card.

[0131] In this embodiment, the IMS service request is the first IMS service request, and if no response corresponding to the IMS service request is received within the maximum response time, it means that the region where the electronic device is located has never successfully responded to the IMS service request. In this case, the highest level of IMS self-healing of the electronic device's IMS function is performed. That is, the electronic device disables the IMS function in a first manner, placing it in a first state. The electronic device being in the first state can also be understood as permanently disabling the IMS function. The electronic device will only restart / enable / restore the IMS function when events such as device restart, device power-on, switching airplane mode on / off, or hot-swapping the card occur.

[0132] In some embodiments, in addition to disabling the IMS function, the electronic device may also perform the following:

[0133] S205, The electronic device terminates the first timer.

[0134] In this embodiment, if the current IMS service request response fails, the first timer used to monitor whether the IMS service request response is successful or not will no longer function, so the first timer can be terminated to save power consumption of the electronic device.

[0135] Optionally, after the electronic device disables the IMS function in the first manner, it can also display a message on the screen indicating that the IMS function has been disabled and needs to be re-enabled by restarting the device, powering on the device, toggling airplane mode, or hot-swapping the card. Correspondingly, if the electronic device detects events such as device restart, powering on the device, toggling airplane mode, or hot-swapping the card, it can display a message on the screen indicating that the IMS function has been re-enabled.

[0136] S206. If the electronic device receives a response to an IMS service request before the first timer expires, the first timer shall be terminated.

[0137] After executing S202, if a response corresponding to the IMS service request is received before the first timer expires, it means that the IMS service request has been successfully responded to. For example, if the IMS service request is an IMS registration request, it means that the electronic device has successfully registered for IMS. If the IMS service request is an IMS call request, it means that the electronic device can conduct IMS calls normally. In this case, the first timer used to monitor the success or failure of the IMS service request response no longer functions, so the first timer can be terminated to save power consumption of the electronic device.

[0138] In this embodiment, a first timer can be set to detect whether the electronic device has received a response from the PLMN for the IMS service request before the first timer expires. If the electronic device does not receive a response for the IMS service request before the first timer expires, it indicates that there is an anomaly in the IMS network in the area where the electronic device is located, and the PLMN in the area where the electronic device is located has most likely never successfully responded to the IMS service request. In this case, strict self-healing of the IMS function is performed, and the IMS function of the electronic device is turned off in a first manner to put it in a first state. This can avoid the increased power consumption of the electronic device caused by frequently initiating unsuccessful IMS service requests. While reducing the power consumption of the electronic device, it can also avoid the poor user experience caused by the user using the IMS service but the IMS service is not performing properly.

[0139] In some alternative embodiments, IMS function self-healing can also be performed to varying degrees depending on the specific circumstances of the IMS service request response failure. (See reference...) Figure 5 As shown, another IMS service processing method is provided, including:

[0140] S301. The electronic device sends an IMS service request to the PLMN where the IMS is located in the area.

[0141] Refer to step S101 above.

[0142] S302, The electronic device starts the second timer.

[0143] In this embodiment, a second timer can be started when the electronic device sends an IMS service request to the PLMN; alternatively, the second timer can be started after the electronic device sends an IMS service request to the PLMN; or, the second timer can be started when the electronic device detects events such as power-on, restart, switching airplane mode on / off, or hot-swappable card events, triggering the sending of an IMS service request. The second timer is used to listen for and receive request failure responses after sending the IMS service request.

[0144] The first timer and the second timer have different functions; the duration of the first timer and the duration of the second timer can be the same or different. Specifically, the duration of the first timer and the duration of the second timer are determined according to the actual situation.

[0145] S303. The electronic device determines whether the IMS service request is the first IMS service request sent by the electronic device to the PLMN.

[0146] Refer to step S102 above.

[0147] S304. If the service request is the first IMS service request sent by the electronic device to the PLMN, and a request failure response for the IMS service request is received before the second timer expires, it is determined that the service request response has failed.

[0148] The failure response includes the reason for the failure.

[0149] In this embodiment, the second timer can also be understood as the maximum duration set for the PLMN to return a request failure response to the electronic device for the IMS service request. If the electronic device receives a returned request failure response before the second timer expires, the IMS service request response can be considered to have failed.

[0150] In some embodiments, the request failure response received by the electronic device may be a response carrying SIP. SIP is a Session Initiation Protocol message sent by the IMS to the electronic device. SIP can indicate the reason for failure. For example, SIP 1xx indicates a provisional response; SIP 200 indicates a successful session; and SIP 4xx indicates a failed request. For instance, SIP 401 (unauthorized) indicates unauthorized access, SIP 402 (payment required) indicates payment required, SIP 403 (forbidden) indicates prohibited access, SIP 404 (not found) indicates not found, SIP 405 (method noallowed) indicates the method is not allowed, SIP 406 (not acceptable) indicates unacceptable access, SIP 407 (proxy authentication required) indicates proxy authentication is required, and SIP 408 (request timeout) indicates request timeout, etc.

[0151] If an IMS service request response fails, the electronic device can further determine the degree of self-healing of the IMS function based on the reason for failure carried in the request failure response.

[0152] For example, in some embodiments, after executing S304, the following may also be performed:

[0153] S305. If the failure reason indicates an IMS network failure, the electronic device shall disable the IMS function of the electronic device in the first manner, so that the electronic device is in the first state.

[0154] In the first state, the electronic device needs to enable the IMS function by restarting the device, toggling airplane mode, or using a hot-swappable card.

[0155] In this embodiment, a SIP of 403 or a public data network (PDN) rejection indicating an access point name (APN) error (208027 / 208028) can both indicate an IMS network failure. That is, if the SIP carried in the request failure response is 403, 208027, or 208028, the failure reason in the current request failure response indicates an IMS network failure. A failure reason indicating an IMS network failure means that the IMS network status in the area where the electronic device is located is very poor. In this case, the IMS function of the electronic device can be self-healed to the maximum extent. The electronic device disables its own IMS function in a first manner, placing itself in a first state. The electronic device being in the first state can also be understood as permanently disabling the IMS function; the electronic device will only restart / enable / restore its IMS function when events such as device restart, device power-on, switching airplane mode on / off, or hot-swapping a card occur.

[0156] In some embodiments, the SIM code used to indicate an IMS network failure can be customized. For example, in this embodiment, if the received SIP code is 403, 208027, or 208028, the electronic device's IMS function is triggered to self-heal, and the device disables the electronic device's IMS function in a first manner.

[0157] It is understandable that, in different scenarios such as the first IMS service request, a subsequent IMS service request, an IMS registration request, or other specific IMS service requests executed after successful IMS registration (e.g., VoLTE call requests), the SIP carried in the failure reason of the request failure response received by the electronic device can be flexibly configured according to the actual network status to trigger the electronic device to perform IMS function self-healing to varying degrees. In this embodiment, the specific configuration of the SIP carried in the failure reason, and the degree to which the SIP code corresponds to the electronic device's IMS function self-healing, are not limited.

[0158] S306. If the failure reason does not indicate an IMS network failure, the electronic device starts a third timer and resends the IMS service request multiple times before the third timer expires.

[0159] If the failure reason does not indicate an IMS network failure, it means that the IMS network in the area where the electronic device is located is not experiencing a network failure, but rather other accidental anomalies. In this case, the electronic device can attempt to re-initiate the IMS service request. To prevent the electronic device from continuously re-initiating IMS service requests, a timer can be set. For example, the electronic device can start a third timer to send IMS service requests multiple times before the third timer expires. The third timer is used to monitor the status of re-initiating IMS service requests when the failure reason does not indicate an IMS network failure.

[0160] S307. If all IMS service requests fail to respond before the third timer expires, the electronic device disables its IMS function in the first manner, putting the electronic device into the first state.

[0161] There are several reasons why an IMS service request might fail to respond.

[0162] If the electronic device does not receive a response corresponding to the IMS service request before the third timer expires, or if the electronic device receives a request failure response for the IMS service request before the third timer expires, it means that all IMS service requests have failed to respond. In this case, the electronic device performs maximum self-healing of its IMS function. The electronic device disables its IMS function in the first manner, placing itself in the first state.

[0163] Optionally, in some embodiments, if the IMS service request is successfully responded to before the third timer expires, the corresponding IMS service operation is executed. For example, if the IMS registration request is successfully responded to before the third timer expires, it indicates that the electronic device has successfully registered for IMS and can then execute other IMS services.

[0164] In this embodiment, when the electronic device receives a request failure response, it can further perform IMS function self-healing based on the failure reason carried in the response. For example, if the failure reason indicates an IMS network failure, strict IMS function self-healing can be performed, disabling the IMS function of the electronic device and placing it in the first state. This avoids increased power consumption caused by frequently initiating unsuccessful IMS service requests, and also avoids a poor user experience caused by IMS service execution errors. If the failure reason does not indicate an IMS network failure, the IMS service request can be re-initiated before the third timer expires. Multiple attempts can increase the probability of successful IMS service requests, avoiding situations where IMS services cannot be executed due to accidental abnormalities.

[0165] In some embodiments, Figure 6An IMS service processing method is given, taking the IMS service request as an example of an IMS registration request, including:

[0166] S1, Electronic device monitoring IMS function enabled event.

[0167] For example, monitoring electronic devices for events that could trigger IMS functionality, such as device restart, device power-on, switching airplane mode on / off, or hot-swapping cards.

[0168] S2, Electronic device start timer T1.

[0169] When the electronic device detects an IMS function activation event, it starts timer T1. Timer T1 is the first timer in the above embodiment, used to monitor whether the IMS registration is successful or not.

[0170] S3. The electronic device determines that IMS registration has not been performed. If yes, proceed to S4; otherwise, proceed to S13.

[0171] When an electronic device detects an IMS function activation event, it determines whether IMS registration has been performed in the local area. Refer to step S102 above. If IMS registration has not been performed in the local area, step S4 of the IMS service processing method provided in this embodiment is executed. If IMS registration has been performed in the local area, step S13 is executed.

[0172] S4. Electronic devices monitor IMS registration status.

[0173] If it is determined that the electronic device has not registered with IMS, the electronic device performs self-healing of the IMS function. The electronic device monitors the IMS registration status, which means listening for success or failure of IMS registration before the timer T1 expires.

[0174] S5, Electronic device start timer T2.

[0175] In this context, timer T2 is the second timer in the above embodiment, used to listen for a request failure response received after sending the IMS registration request.

[0176] S6. If the electronic device receives an IMS registration success response before the end of time T1, execute S7.

[0177] S7. The electronic device terminates the monitoring of the IMS registration status; terminates timer T1; and sets the IMS registration status to registered.

[0178] In this embodiment, if the electronic device receives an IMS registration success response, it has successfully registered with IMS and therefore no longer needs to monitor the IMS registration status. Timer T1 is also terminated. Furthermore, the electronic device can update the IMS registration status of its local area from unregistered to registered.

[0179] S8. If the electronic device does not receive an IMS registration success response before the end of time T1, then execute S11.

[0180] Or, in another case:

[0181] S9. The electronic device receives an IMS registration failure response before the end of time T2.

[0182] The IMS registration failure response includes the reason for the failure.

[0183] In this embodiment, when the IMS service is registered with IMS and the IMS registration request is the first IMS service request sent, the electronic device's IMS function self-healing is triggered when the SIP code is configured as 403, 208027 or 208028, and the device shuts down the electronic device's IMS function in a first manner.

[0184] S10. The electronic device determines whether the failure indicates an IMS network fault. If yes, proceed to S11. If no, proceed to S13.

[0185] S11. The electronic device disables the IMS function of the electronic device in a first manner, so that the electronic device is in a first state.

[0186] Refer to step S204 above.

[0187] S12. The electronic device sets the IMS registration status to registered and terminates timers T1 and T2.

[0188] In this embodiment, after the electronic device disables the IMS function, it can no longer register with IMS, therefore there is no need to monitor the IMS registration status, and timers T1 and T2 are terminated. Furthermore, the electronic device can update the IMS registration status of its local area from unregistered to registered.

[0189] S13. No IMS service processing method is required.

[0190] If an electronic device has been registered with IMS in its local area, it means that the IMS registration is successful. The probability of IMS network failure in the local area is relatively small. Therefore, the IMS service processing method provided in this embodiment is not used for IMS service processing.

[0191] In this embodiment, if the electronic device confirms that the IMS registration request is its first IMS registration request and the request fails, the electronic device disables its IMS function. If the first IMS registration request fails, it indicates that the electronic device has not previously sent any IMS-related service requests to the PLMN in its region. This strongly suggests that the region where the electronic device is located does not support IMS services or that the IMS network is malfunctioning. In this case, if the electronic device's IMS registration request fails, it will attempt to re-initiate the IMS registration request multiple times over a period of time. Such frequent initiation of unsuccessful IMS registration requests increases the power consumption of the electronic device. Therefore, disabling the IMS function allows for self-healing and reduces power consumption.

[0192] In some optional embodiments, different levels of IMS service processing can be applied to IMS service requests that are not first-time transmissions by the IMS service requesting electronic device. See reference... Figure 7 As shown, it includes:

[0193] S401. The electronic device sends an IMS service request to the PLMN where the IMS is located in the area.

[0194] Refer to step S101 above.

[0195] S402. The electronic device determines whether the IMS service request is the first IMS service request sent to the PLMN.

[0196] Refer to step S102 above.

[0197] S403. If the IMS service request is the first IMS service request sent by the electronic device to the PLMN, when the IMS service request response fails, the electronic device disables the IMS function of the electronic device in the first manner, so that the electronic device is in the first state.

[0198] Refer to step S204 above.

[0199] S404. If the IMS service request electronic device is not sending an IMS service request to the PLMN for the first time, the electronic device starts the fourth timer.

[0200] In this embodiment, when the electronic device determines that the IMS service request is not the first IMS service request sent by the electronic device, a fourth timer can be started. The fourth timer is used to monitor the response status of the current non-first IMS service request.

[0201] S405. If the IMS service request fails to respond before the fourth timer expires, and the IMS service request meets the failure condition, the electronic device disables the IMS function of the electronic device in the second manner, and puts the electronic device into the second state.

[0202] The second state of the electronic device indicates that the IMS function is turned off when the service request response fails, and the IMS function is turned on again after a preset first duration. For example, the first duration can be 30 minutes, 1 hour, 2 hours, 3 hours, etc. The failure conditions include: the number of IMS service request response failures reaching a preset threshold before the fourth timer expires; or the probability of IMS service request response failures exceeding a preset probability threshold.

[0203] In this embodiment, if the electronic device does not receive a response to the IMS service request before the fourth timer expires, or if the electronic device receives a request failure response for the IMS service request before the fourth timer expires, the IMS service request response is determined to have failed. The electronic device then determines whether the IMS service request meets the failure conditions.

[0204] In this embodiment, if the number of IMS service request response failures reaches a preset threshold before the fourth timer expires, or if the probability of IMS service request response failures is greater than a preset probability threshold, the electronic device disables its IMS function, placing it in a second state. For example, the preset threshold could be 10 times; if the number of IMS service request response failures reaches 10 before the fourth timer expires, the electronic device disables its IMS function, placing it in the second state. The preset probability threshold could be 70%; for example, if the probability of IMS service request response failures in the region where the electronic device is located is greater than 70%, the electronic device disables its IMS function in a second manner, placing it in the second state.

[0205] Optionally, after the electronic device disables the IMS function in the second manner, it may also display a message on the screen indicating that the IMS function has been disabled and will be re-enabled after a preset first duration. Accordingly, at the end of the preset first duration, the electronic device may display a message on the screen indicating that the IMS function has been re-enabled.

[0206] In this embodiment, when the current IMS service request electronic device sends an IMS service request to the PLMN of the region for the first time, in order to further confirm the IMS capability / IMS network status of the region, the electronic device can start a fourth timer. When the IMS service request response fails, it can further determine whether to perform a certain degree of IMS service processing based on whether the region or the service request meets the failure conditions, thus avoiding the situation where IMS service execution is abnormal due to IMS network abnormality in the region.

[0207] In some optional embodiments, IMS services include Voice over Long-Term Evolution (VoLTE) and Voice over Wi-Fi (VoWi-Fi). VoLTE includes IMS registration, IMS SMS, VoNR (Voice over New Radio) calls, VoLTE calls, VoNR roaming, etc.; VoWi-Fi includes VoWi-Fi registration, VoWi-Fi SMS, VoWi-Fi calls, switching between VoWi-Fi and VoLTE, VoWi-Fi roaming, etc.

[0208] For IMS registration failures, please refer to the following: Figure 6 The given embodiment performs corresponding IMS service processing. After successful IMS registration, the electronic device can execute other IMS services. However, while executing these services, it may encounter IMS network failures / anomalies in its local area. Therefore, IMS service processing is also required for IMS services executed after successful registration to reduce the power consumption of the electronic device's IMS service. (Reference) Figure 8 Taking VoLTE calls as an example of IMS service, the explanation includes:

[0209] S501. The electronic device sends an IMS registration request to the PLMN where the IMS is located in the region.

[0210] Electronic devices can be pre-configured to have IMS enabled by default. When an electronic device arrives at a region where IMS is enabled by default, it will trigger the activation / restart of IMS when it detects events such as power-on, restart, switching airplane mode on / off, or hot-swapping cards. This will trigger the electronic device to send a service IMS registration request to the PLMN of the current region.

[0211] S502, The electronic device receives the IMS registration success response returned by the PLMN.

[0212] When an electronic device receives a successful IMS registration response, it means that the electronic device has established a connection with IMS.

[0213] S503, The electronic device sends a VoLTE call request to the PLMN.

[0214] The electronic device sends a VoLTE call request to the PLMN in the current region.

[0215] S504. The electronic device determines whether the VoLTE call request is the first VoLTE call request sent by the electronic device to the PLMN.

[0216] Electronic devices can obtain a "No VoLTE Call" identifier for their current location. When this identifier is true, it indicates that the electronic device has not conducted a VoLTE call within the IMS of that location, and the current VoLTE call request is the first VoLTE call request sent by the electronic device to the PLMN in that location. When the identifier is false, it indicates that the electronic device has conducted a VoLTE call in the location, and the current VoLTE call request is not the first VoLTE call request sent by the electronic device to the PLMN in that location.

[0217] In some other implementations, electronic devices can also determine whether it is the first time they have reached a certain area based on the recorded historical geographical location. If the geographical location of the current area is not included in the historical geographical location, it is considered to be the first time they have reached that area, and the VoLTE call request sent to the PLMN of that area is the first VoLTE call request.

[0218] Alternatively, electronic devices can determine whether the PLMN in the current region is the first PLMN to initiate a VoLTE call request based on the recorded historical PLMN addresses. If the historical PLMN addresses do not include the address of the PLMN in the current region, then the VoLTE call request sent to the PLMN in the current region is considered to be the first VoLTE call request, and so on.

[0219] S505. If the VoLTE call request is the first VoLTE call request sent by the electronic device to the PLMN, and the VoLTE call request response fails, the electronic device disables the VoLTE call function in the first manner, and puts the electronic device in the first state.

[0220] Among them, the failure to respond to a VoLTE call request includes situations where the electronic device does not receive a response to the VoLTE call request or the electronic device receives a failure response to the VoLTE call request.

[0221] After determining that the VoLTE call request is the first VoLTE call request sent by the electronic device to the PLMN in its current location, if the VoLTE call request response fails, it indicates that the area where the electronic device is located does not support IMS services or that the IMS network is highly likely to be abnormal. The electronic device then disables its VoLTE call function in a first manner, placing the electronic device in a first state. In this embodiment, when targeting a specific IMS service, only the specific IMS service can be disabled, rather than the entire IMS function of the electronic device, thus avoiding the impact of disabling the IMS function on other feasible IMS services. With the specific VoLTE call function disabled, the electronic device is in the first state, meaning that the electronic device will only restart / enable / restore its VoLTE call function when events such as device restart, device power-on, switching airplane mode on / off, or hot-swapping the SIM card occur.

[0222] In this embodiment, when the IMS service is a VoLTE call and the VoLTE call request is the first VoLTE call request sent, the SIP code can be configured to be any SIP code other than the SIP code indicating network normality. This triggers the electronic device's IMS function self-healing, and the device disables the electronic device's IMS function in a first manner. For example, the SIP code indicating network normality can be 4, 27, 127, etc. If the SIP code carried in the failure reason is any SIP code other than 4, 27, 127, etc., indicating network normality, then the electronic device's IMS function self-healing is triggered, and the device disables the electronic device's IMS function in the first manner.

[0223] S506. If the VoLTE call request electronic device is not sending a VoLTE call request to the PLMN for the first time, when the VoLTE call request response fails, the electronic device determines whether the signal strength of the IMS is less than a preset signal strength threshold.

[0224] In this embodiment, if the VoLTE call request is not the first VoLTE call request sent to the PLMN, the electronic device can perform IMS self-healing according to the IMS network signal instructions when the VoLTE call request response fails.

[0225] In this embodiment, when the IMS service is a VoLTE call and the VoLTE call request is not the first VoLTE call request sent, the electronic device's IMS function self-healing can be triggered when the SIP code is configured as 503, 500, 580, etc., and the device will determine the signal strength.

[0226] S506. If the IMS signal strength is less than the preset signal strength threshold, the electronic device disables the VoLTE calling function in a third manner, putting the electronic device into a third state.

[0227] The preset signal strength threshold can be understood as a signal strength threshold. If the IMS signal strength is less than the preset signal strength threshold, the self-healing function of the electronic device's IMS is executed, and the IMS function of the electronic device is shut down in a third way, putting the electronic device into a third state. The third-party IMS service processing level is lower than that of the first method.

[0228] For example, the signal strength can be the reference signal receiving power (RSRP). For instance, when RSRP < -120, the self-healing function of the electronic device's IMS is executed, disabling the IMS function and placing the electronic device in a third state. Alternatively, the signal strength can also be the reference signal receiving quality (RSRQ). For instance, when RSRQ <= -3, the self-healing function of the electronic device's IMS is executed, disabling the VoLTE calling function and placing the electronic device in a third state.

[0229] In this context, when a specific VoLTE call function is disabled, the electronic device being in the third state refers to disabling the VoLTE call function when the service request response fails, and then reactivating the VoLTE call function after a preset second duration. For example, the second duration can be 30 minutes, 1 hour, 2 hours, 3 hours, etc. In some embodiments, the first duration for disabling the electronic device's IMS function upon IMS registration failure is longer than the second duration for disabling the electronic device's IMS function upon non-IMS registration services (such as VoLTE calls).

[0230] Optionally, after the electronic device disables the VoLTE call function in a third manner, it can also display a message on the screen indicating that the VoLTE call function has been disabled and will be re-enabled after a preset second duration. Correspondingly, at the end of the preset second duration, the electronic device can display a message on the screen indicating that the VoLTE call function has been re-enabled.

[0231] In this embodiment, if the VoLTE call request is the first request initiated, that is, the VoLTE call is the first call, if the first call fails and the failure reason indicates an IMS network failure, strict self-healing of the IMS function is performed, that is, the IMS function is permanently disabled; if the first call succeeds, the current VoLTE call is not the first request initiated, and the IMS function of the electronic device is only self-healed when the IMS signal strength is lower than the threshold, so as to avoid the poor user experience caused by the VoLTE call being executed abnormally.

[0232] In some embodiments, Figure 9 A more specific IMS service processing method is given, taking the IMS service request as a VoLTE call as an example, including:

[0233] S601. The electronic device received a maintenance report indicating a failed call.

[0234] In this context, "failure monitoring information" refers to the information received by the electronic device when a call request fails. Failure monitoring information can also be understood as the request failure response returned by IMS to the electronic device. This information may include the SIP message indicating the reason for the call failure.

[0235] S602. The electronic device determines whether it is a VoLTE call or a circuit-switched (CS) network replay.

[0236] The electronic device determines whether the maintenance information of the failed call indicates a VoLTE call. If so, it executes S603; or, the electronic device determines whether the maintenance information of the failed call indicates a CS replay call. If so, it executes S603.

[0237] If the call failure information indicates a non-VoLTE call and is not a CS redial call, then the IMS service processing method will not be applied.

[0238] S603. The electronic device determines whether the "no VoLTE call has been made" flag is true.

[0239] In this embodiment, the electronic device determines whether a VoLTE call has been made. If the flag indicating no VoLTE call has been made is true, it means the electronic device has not made a VoLTE call before; if the flag indicating no VoLTE call has been made is false, it means the electronic device has made a VoLTE call before. The specific determination process can be found in step S504 above.

[0240] S604. If so, that is, if the VoLTE call not performed flag is true, the electronic device will update the VoLTE call not performed flag to false.

[0241] In this embodiment, the "no VoLTE call ever performed" flag is set to true, meaning that the electronic device had not performed a VoLTE call before receiving the maintenance information indicating a failed VoLTE call. Since the received maintenance information may be a failure notification of a VoLTE call, the "no VoLTE call ever performed" flag needs to be updated to false.

[0242] S605. Does the electronic device determine whether the reason for the call failure indicates an IMS network failure?

[0243] In this embodiment, the electronic device can obtain the failure reason from the call failure monitoring information and determine whether the failure reason meets the requirements. Whether the failure reason indicates an IMS network failure can be understood as the failure reason including a normal checksum (CHR) reason value. Normal CHR values ​​include 4, 27, etc. If the failure reason includes reason values ​​other than 4 and 27, it indicates that it does not indicate an IMS network failure.

[0244] If the cause of failure does not indicate an IMS network failure, then IMS self-healing will not be performed.

[0245] S606. If so, that is, if the failure reason indicates an IMS network failure, the electronic device disables the VoLTE calling function of the electronic device in a first manner, and puts the electronic device into a first state.

[0246] In this embodiment, the received call failure monitoring information is generated during the first VoLTE call by the electronic device. In the event of a first call failure and the failure reason indicating an IMS network fault, the electronic device performs maximum self-healing of its IMS function. That is, the electronic device disables its VoLTE calling function in a first manner, placing it in a first state. The electronic device being in the first state can also be understood as permanently disabling the VoLTE calling function. The VoLTE calling function will only be restarted / enabled / restored when events such as device restart, device power-on, airplane mode switching, or hot-swapping of the SIM card occur.

[0247] S607. If not, that is, if no VoLTE call has been made, the identifier is false, and the electronic device determines whether it is a normal call or a CS replay.

[0248] The electronic device further confirms whether the maintenance information of the failed call indicates an abnormal VoLTE call. If the VoLTE call is abnormal, that is, the VoLTE call is not a normal call, then S608 is executed; or, if the maintenance information is not generated by CS redialing, then S608 is executed.

[0249] S608. If it is not a normal call, or not a CS replay, the electronic device determines whether the IMS signal strength is less than the preset signal strength threshold.

[0250] In this embodiment, the VoLTE call is an abnormal call, i.e., the VoLTE call fails. In this case, the electronic device further detects the IMS network signal strength. If the IMS signal strength is less than a preset signal strength threshold, the IMS capability performs self-healing processing.

[0251] In some embodiments, if it is a normal call or not a CS replay, the IMS service processing method will not be performed.

[0252] S609. If the IMS signal strength is less than the preset signal strength threshold, the electronic device disables the VoLTE calling capability of the electronic device in a third way, and puts the electronic device into a third state.

[0253] Refer to the above embodiment S506.

[0254] In some other feasible embodiments, the electronic device may disable IMS calling capability (VoLTE calling capability). That is, in the processing of a specific IMS service, IMS function self-healing can be performed on a specific IMS service rather than on the entire IMS capability of the electronic device. This ensures that IMS services that fail to execute will not be executed again, without affecting other unexecuted or successfully executed IMS services.

[0255] In some embodiments, if the IMS signal strength is greater than a preset signal strength threshold, the IMS service processing method will not be performed.

[0256] In this embodiment, after the electronic device completes IMS registration, other IMS services are executed. For example, during a VoLTE call, upon receiving call failure monitoring information, a determination is made regarding whether to perform IMS self-healing processing. If the monitoring information indicates a failure of the first VoLTE call, strict IMS self-healing is performed, disabling the IMS function of the electronic device and placing it in a first state. If the monitoring information indicates a failure of a non-first VoLTE call, and the IMS signal strength is determined to be below a preset signal strength threshold, low-level IMS self-healing is performed, disabling the IMS function of the electronic device in a third manner and placing it in a third state. By performing different levels of IMS self-healing for call failures in different scenarios, the power consumption of the electronic device is reduced, and the on / off control of the IMS function is more accurately implemented, optimizing the user experience of using IMS services.

[0257] It is understood that the above embodiments Figures 3-9The IMS service processing method is applicable to the processing of any IMS service. For different IMS services, parameters involved in the IMS service processing method can be adaptively set, such as corresponding timers, failure conditions, preset signal strength thresholds, and the duration of IMS function shutdown. In some embodiments, priority or independent self-healing control can also be implemented for IMS services of different priorities to achieve more accurate self-healing control of the electronic device for IMS services. While reducing the power consumption generated by the electronic device performing IMS services, it closely matches the actual user experience, achieving self-healing of IMS capabilities to optimize the user experience of using IMS services.

[0258] In some optional embodiments, the electronic device has a pre-configured IMS configuration list, which includes multiple regions, IMS configuration parameters for each region, and the network status of IMS for each region. The IMS network status includes whether the IMS network status is normal or abnormal. The IMS configuration list can also be called the default IMS function enabled list; when the electronic device reaches a region included in this list, the IMS function is required to be enabled by default. The IMS function is enabled when the electronic device detects events that trigger IMS function activation, such as device restart, device power-on, airplane mode switching, or hot-swapping of a SIM card.

[0259] In some embodiments, the electronic device performs the above-described embodiments in a certain region. Figures 3-9 The IMS service processing method generates IMS function corresponding operation data (self-healing data), which can be sent to the cloud for data analysis. The cloud can then update the IMS function status (default enabled or default disabled) and IMS network status (network normal or network abnormal) of each region in the IMS configuration list.

[0260] The operational data corresponding to the IMS function may include the number of IMS service failures, the reasons for IMS service failures, the failure probability of IMS services, etc., generated by each execution of an IMS service request.

[0261] The cloud can periodically obtain operational data for the IMS function corresponding to different regions from the electronic device; or, when the geographical location of the electronic device is updated, it can receive operational data for the IMS function corresponding to the region before the geographical location update sent by the electronic device; or, when the electronic device is powered on, restarted, airplane mode is turned on / off, or a SIM card is hot-swapped, it can receive operational data for the IMS function corresponding to the current region sent by the electronic device.

[0262] The cloud updates the IMS function status of each region based on the received operational data and preset boundary conditions for each region. These preset boundary conditions can include boundary conditions set for the IMS configuration parameters and network status of the corresponding region. For example, preset boundary conditions include the region's IMS network coverage, coverage of 2G / 3G decommissioned areas, IMS capability maturity, IMS network signal status, frequency and number of times users use other IMS services such as CS / VoLTE calls / VoWiFi calls / VoNR calls / VoLTE calls / IMS roaming, and user habits, etc.

[0263] The cloud can set weight ratios for these preset boundary conditions and adaptively adjust the average time T for disabling terminal IMS service capabilities. This allows for the identification of which regions' operator PLMNs do not support IMS registration, IMS calls (such as VoLTE calls), or have poor network signal quality, leading to a high probability of abnormalities in IMS registration and calls for electronic devices in these areas. The cloud can then disable IMS registration and IMS call capabilities for electronic devices in these regions to ensure that the user experience is not compromised.

[0264] In some embodiments, reference Figure 10 The given flowchart illustrates the terminal's IMS configuration list update process. If the cloud does not receive operational data from the electronic device within time period T, it maintains strict self-healing of the IMS service in that region. If the cloud receives operational data from the electronic device within time period T, it determines whether each region meets the conditions for disabling IMS capabilities based on the operational data and preset boundary conditions for each region. If the conditions are met, the IMS capability status of the electronic device in that region is updated to the default disabled state; otherwise, the IMS capability status of the electronic device in that region is updated to the default enabled state.

[0265] The preset boundary conditions for each region include:

[0266] Condition 1: Does the coverage of the 2G / 3G decommissioning area in this region exceed the preset coverage threshold? If yes, item = 1; if no, item = 0. The weight corresponding to condition 1 is A.

[0267] Condition 2: Is the success rate of 2G / 3G services in this region greater than the corresponding preset success rate threshold? If yes, item = 1; if no, item = 0. The weight corresponding to condition 1 is B.

[0268] Condition 3: Is the network signal strength of the IMS in this area greater than the preset signal strength threshold? If yes, item=1; if no, item=0. The weight corresponding to condition 1 is C.

[0269] Condition 4: Is the success rate of IMS services in this region greater than the corresponding preset success rate threshold? If yes, item = 1; if no, item = 0. The weight corresponding to condition 1 is D.

[0270]

[0271] Condition N: ..., the weight corresponding to condition N is N.

[0272] In this embodiment, the cloud calculates the IMS capability value for each region using a weighted summation method based on preset boundary conditions and the weights corresponding to each condition. If the IMS capability value is greater than a preset threshold, the IMS capability of that region is determined to be enabled by default; otherwise, the IMS capability of that region is determined to be disabled by default.

[0273] Alternatively, in some embodiments, the cloud can use the operational data reported by electronic devices as one of the conditions for determining whether each region meets the requirement to disable IMS.

[0274] For example, the preset boundary conditions for each region include:

[0275] Condition 1: Does the region receive self-healing data from multiple IMS registrations reported by electronic devices? If yes, item = 1; if no, item = 0. The weight corresponding to Condition 1 is A.

[0276] Among them, the self-healing data of IMS registration refers to the runtime data generated when the IMS registration request fails during IMS registration in this region.

[0277] Condition 2: Does the region receive self-healing data from multiple IMS calls reported by electronic devices? If yes, item = 1; if no, item = 0. The weight corresponding to condition 1 is B.

[0278] Among them, the self-healing data registered by IMS refers to the operational data generated when an IMS call request fails during an IMS call in the region.

[0279] Condition 3: Does the coverage of the 2G / 3G decommissioning area in this region exceed the preset coverage threshold? If yes, item = 1; if no, item = 0. The weight corresponding to condition 1 is C.

[0280] Condition 4: Is the success rate of 2G / 3G services in this region greater than the corresponding preset success rate threshold? If yes, item = 1; if no, item = 0. The weight corresponding to condition 1 is D.

[0281] Condition 5: Is the network signal strength of the IMS in this area greater than the preset signal strength threshold? If yes, item=1; if no, item=0. The weight corresponding to condition 1 is E.

[0282] Condition 6: Is the success rate of IMS services in this region greater than the corresponding preset success rate threshold? If yes, item = 1; if no, item = 0. The weight corresponding to condition 1 is F.

[0283]

[0284] Condition N: ..., the weight corresponding to condition N is N.

[0285] Similarly, in this embodiment, the cloud calculates the IMS capability value of each region using a weighted summation method based on the preset boundary conditions corresponding to each region and the weights corresponding to each condition. If the IMS capability value is greater than a preset threshold, the IMS capability of that region is determined to be enabled by default; otherwise, the IMS capability of that region is determined to be disabled by default.

[0286] Using the above methods, the cloud can update the status of IMS capabilities in each region of the IMS configuration list to enable or disable them by default, thereby generating a target IMS configuration list and distributing the target IMS configuration list to electronic devices.

[0287] After receiving the target IMS configuration list, the electronic device can perform the default enable or default disable operation of the corresponding IMS capabilities according to the status of the IMS capabilities of each region indicated in the target IMS configuration list.

[0288] In some embodiments, for regions where IMS capability is disabled by default in the target IMS configuration list, electronic devices can still attempt to send IMS service requests upon arriving in that region. In this case, the electronic device can adaptively reduce the number of times a preset threshold for determining whether the failure condition is met during IMS service processing in that region, and reduce the preset probability threshold for determining whether the failure condition is met during IMS service processing in that region, thereby reducing the number of IMS service attempts in that region and minimizing the power consumption of the electronic device while attempting IMS service. In this embodiment, the cloud can adjust the weights of boundary conditions based on the region's network status, the frequency and number of times users use IMS services in their region, and user habits, thereby updating the default IMS function enabled or disabled for each region on the electronic device, making the IMS configuration list more accurate.

[0289] Figure 11 A possible structural schematic diagram of the electronic device involved in the above embodiments is shown. Figure 11 The electronic device 1000 shown includes a processing module 1001, a communication module 1002, and a storage module 1003.

[0290] The processing module 1001 may be a central processing unit (CPU), a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA), or other programmable logic devices, transistor logic devices, hardware components, or any combination thereof. The processor may include an application processor and a baseband processor. It may implement or execute the various exemplary logic blocks, modules, and circuits described in conjunction with the disclosure of this application. The processor may also be a combination that implements computing functions, such as a combination of one or more microprocessors, a combination of a DSP and a microprocessor, etc.

[0291] For example, the processing module 1001 can be as follows: Figure 2 The processor 110 shown; the communication module 1002 can be as follows: Figure 2 The mobile communication module 150 and / or wireless communication module 160 shown; the storage module 1003 can be as follows: Figure 2 The internal memory 121 shown. The electronic device provided in this application embodiment can be Figure 2 The electronic device 100 shown.

[0292] This application also provides a chip system (e.g., a system-on-a-chip (SoC)). Figure 12 As shown, the chip system includes at least one processor 701 and at least one interface circuit 702. The processor 701 and the interface circuit 702 are interconnected via lines. For example, the interface circuit 702 can be used to receive signals from other devices (e.g., the memory of an electronic device). As another example, the interface circuit 702 can be used to send signals to other devices (e.g., the processor 701 or the camera of an electronic device). Exemplarily, the interface circuit 702 can read instructions stored in the memory and send those instructions to the processor 701. When the instructions are executed by the processor 701, the electronic device can perform the steps in the above embodiments. Of course, the chip system may also include other discrete components, which are not specifically limited in this application embodiment.

[0293] This application also provides a computer-readable storage medium including computer instructions that, when executed on the electronic device, cause the electronic device to perform various functions or steps performed by the electronic device 100 in the above method embodiment.

[0294] This application also provides a computer program product that, when run on a computer, causes the computer to perform the various functions or steps performed by the electronic device 100 in the above method embodiments. For example, the computer may be the aforementioned electronic device 100.

[0295] Through the above description of the embodiments, those skilled in the art can clearly understand that, for the sake of convenience and brevity, only the division of the above functional modules is used as an example. In actual applications, the above functions can be assigned to different functional modules as needed, that is, the internal structure of the device can be divided into different functional modules to complete all or part of the functions described above.

[0296] It should be noted that the personal information used in the technical solution of this application is limited to information for which individual consent has been obtained, including but not limited to notifying and reminding users to read the relevant user agreement (notification) and sign the agreement (authorization) which includes authorization of relevant user information before users use the function.

[0297] The technical solutions disclosed in this application involve the collection, storage, use, processing, transmission, provision, and disclosure of users' personal information, all of which comply with relevant laws and regulations and do not violate public order and good morals.

[0298] In the several embodiments provided in this application, it should be understood that the disclosed apparatus and methods can be implemented in other ways. For example, the apparatus embodiments described above are merely illustrative; for instance, the division of modules or units is only a logical functional division, and in actual implementation, there may be other division methods. For example, multiple units or components may be combined or integrated into another device, or some features may be ignored or not executed. Furthermore, the mutual coupling or direct coupling or communication connection shown or discussed may be through some interfaces; the indirect coupling or communication connection between devices or units may be electrical, mechanical, or other forms.

[0299] The units described as separate components may or may not be physically separate. A component shown as a unit can be one or more physical units; that is, it can be located in one place or distributed in multiple different locations. Some or all of the units can be selected to achieve the purpose of this embodiment according to actual needs.

[0300] Furthermore, the functional units in the various embodiments of this application can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit. The integrated unit can be implemented in hardware or as a software functional unit.

[0301] If the integrated unit is implemented as a software functional unit and sold or used as an independent product, it can be stored in a readable storage medium. Based on this understanding, the technical solutions of the embodiments of this application, in essence, or the parts that contribute to the prior art, or all or part of the technical solutions, can be embodied in the form of a software product. This software product is stored in a storage medium and includes several instructions to cause a device (which may be a microcontroller, chip, etc.) or processor to execute all or part of the steps of the methods described in the various embodiments of this application. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, portable hard drives, read-only memory (ROM), random access memory (RAM), magnetic disks, or optical disks.

[0302] The above description is merely a specific embodiment of this application, but the scope of protection of this application is not limited thereto. Any variations or substitutions within the technical scope disclosed in this application should be included within the scope of protection of this application. Therefore, the scope of protection of this application should be determined by the scope of the claims.

Claims

1. A method for processing services in the Internet Protocol Multimedia Subsystem, characterized in that, include: The electronic device sends an IMS service request to the Public Land Mobile Network (PLMN) where the Internet Protocol Multimedia Subsystem (IMS) is located in its region. If the IMS service request is the first IMS service request sent by the electronic device to the PLMN in the current region, the electronic device shall disable its IMS function when the IMS service request response fails. The conditions under which the IMS service request is the first IMS service request sent by the electronic device to the PLMN in the current region include: the IMS in the current region has not registered an identifier of the first value; or, the historical geographical locations recorded by the electronic device do not include the geographical locations of the current region; or, the historical PLMN addresses recorded by the electronic device do not include the PLMN addresses of the current region.

2. The method according to claim 1, characterized in that, After the electronic device sends an IMS service request to the Public Land Mobile Network (PLMN) where the Internet Protocol Multimedia Subsystem (IMS) is located in its region, the method further includes: The electronic device starts a first timer; When the IMS service request response fails, the electronic device disables its IMS function, including: If the electronic device does not receive a response to the IMS service request before the first timer expires, the electronic device disables the IMS function in a first manner, putting the electronic device into a first state. In the first state, the electronic device needs to enable its IMS function by restarting the device, switching the airplane mode on or off, or using a hot-swappable card.

3. The method according to claim 1 or 2, characterized in that, After the electronic device sends an IMS service request to the Public Land Mobile Network (PLMN) where the Internet Protocol Multimedia Subsystem (IMS) is located in its region, the method further includes: The electronic device starts a second timer; When the IMS service request response fails, the electronic device disables its IMS function, including: If the electronic device receives a response carrying a failure reason before the second timer expires, and the failure reason indicates an IMS network failure, the electronic device disables the IMS function of the electronic device in a first manner, so that the electronic device is in the first state; In the first state, the electronic device needs to enable its IMS function by restarting the device, switching the airplane mode on or off, or using a hot-swappable card.

4. The method according to claim 3, characterized in that, The step of disabling the IMS function of the electronic device when the IMS service request response fails also includes: If the cause of failure does not indicate an IMS network failure, the electronic device starts a third timer and sends the IMS service request to the PLMN multiple times before the third timer expires. If multiple IMS service requests fail to respond before the third timer expires, the electronic device disables its IMS function in the first manner, thus placing the electronic device in the first state.

5. The method according to claim 1 or 2, characterized in that, After the electronic device sends an IMS service request to the Public Land Mobile Network (PLMN) where the Internet Protocol Multimedia Subsystem (IMS) is located in its region, the method further includes: If the IMS service request is not the first IMS service request sent by the electronic device to the PLMN, the electronic device starts the fourth timer; If all IMS service requests sent by the electronic device fail to respond before the fourth timer expires, and the failure condition is met, the electronic device disables the IMS function of the electronic device in a second manner, and puts the electronic device into a second state. The electronic device being in the second state indicates that the IMS function of the electronic device is turned off when the IMS service request response fails, and the IMS function of the electronic device is turned on after a preset first time period. The failure conditions include the number of times the IMS service request response fails before the fourth timer expires reaching a preset threshold, or the probability of the IMS service request response failing is greater than a preset probability threshold.

6. The method according to claim 5, characterized in that, The electronic device has a pre-installed IMS configuration list, which includes multiple regions, IMS configuration parameters corresponding to each region, and the network status of the IMS corresponding to each region; wherein, the network status of the IMS includes network normal or network abnormal. The method further includes: The electronic device will send the operation data of the IMS service request generated in the local area to the cloud; the operation data includes the operation data corresponding to the failure of the electronic device to send the IMS service request to the PLMN in the local area, or the operation data corresponding to the successful response of the IMS service request. The electronic device receives the target IMS configuration list sent by the cloud; the target IMS configuration list is a list updated by the cloud based on the running data, after updating the IMS configuration parameters corresponding to the region and the network status of the IMS corresponding to the region. The electronic device updates the preset number threshold and / or the preset probability threshold in the failure condition according to the target IMS configuration list.

7. The method according to claim 1 or 2, characterized in that, The IMS service request includes an IMS registration request and an IMS call request; the method further includes: The electronic device sends the IMS registration request to the PLMN where the IMS is located in the region. Once the electronic device receives a successful registration response for the IMS registration request, the electronic device establishes a connection with the IMS. The electronic device sends an IMS service request to the Public Land Mobile Network (PLMN) where the Internet Protocol Multimedia Subsystem (IMS) is located in the region, including: The electronic device sends the IMS call request to the PLMN in the region where it is located; If the IMS service request is the first IMS service request sent by the electronic device to the PLMN, when the IMS service request response fails, the electronic device disables the IMS function, including: If the IMS call request is the first IMS call request sent by the electronic device to the PLMN, when the IMS call request response fails, the electronic device disables the IMS function of the electronic device in a first manner, so that the electronic device is in a first state; wherein, when the electronic device is in the first state, it needs to enable the IMS function of the electronic device by any one of the following methods: device restart, switching airplane mode on and off, or hot-swapping the card; If the IMS call request is not the first IMS call request sent by the electronic device to the PLMN, and the IMS call request response fails and the IMS signal strength is less than a preset signal strength threshold, the electronic device disables the IMS function in a third manner, placing the electronic device in a third state. The electronic device being in the third state indicates that the IMS function of the electronic device is disabled when the IMS service request response fails, and the IMS function of the electronic device is enabled after a preset second duration.

8. The method according to claim 1 or 2, characterized in that, After the electronic device sends an IMS service request to the Public Land Mobile Network (PLMN) where the Internet Protocol Multimedia Subsystem (IMS) is located in its region, the method further includes: The electronic device acquires the geographical location information of the electronic device; If the geographic location information indicates that the location is the first area the electronic device has arrived in, the electronic device determines that the IMS service request is the first IMS service request sent to the PLMN.

9. A computer device, comprising a memory, a processor, and a computer program stored in the memory, characterized in that, The processor executes the computer program to implement the steps of the method according to any one of claims 1-8.

10. A computer-readable storage medium having a computer program stored thereon, characterized in that, When executed by a processor, the computer program implements the steps of the method according to any one of claims 1-8.

11. A computer program product, comprising a computer program, characterized in that, When executed by a processor, the computer program implements the steps of the method according to any one of claims 1-8.