Network service icon display control method and device, terminal and medium

Abstract

The invention discloses a network service icon display control method and device, a terminal and a medium, and belongs to the technical field of communication, and the network service icon display control method comprises the steps that the terminal obtains reason information of network registration failure when monitoring that registration to a target network fails; the terminal determines whether the network registration failure belongs to a recoverable network registration failure according to the reason information; and under the condition that the terminal determines that the network registration failure belongs to the recoverable network registration failure, maintaining that a service icon of the target network is displayed on a user interface.

Description

TECHNICAL FIELD

[0001] The present application belongs to the technical field of communication, and particularly relates to a network service icon display control method and device, a terminal and a medium. BACKGROUND

[0002] In the existing mobile communication technology, when a mobile terminal such as a mobile phone successfully registers to a network, a corresponding network service icon is usually displayed on the front-end status bar of a user interface (UI) to indicate to the user that the current network supports high-quality call service. For example, when registering to an IP Multimedia Subsystem (IMS), a high-definition voice or video call icon, such as an "HD" icon, is displayed to indicate that the current network supports high-quality call service. The display state of the icon is directly bound to the IMS registration state of the terminal, that is, the icon is displayed when the registration is successful, and the icon disappears when the registration fails or is deregistered.

[0003] In actual application, the network may experience a short-term, self-recoverable registration failure due to reasons such as wireless environment fluctuation, network signaling congestion, and temporary core network device restart for maintenance. At this time, the terminal receives a registration failure response with a specific cause value. The existing processing flow is that the terminal updates its network state to "unregistered" and hides or removes the corresponding network service icon in the UI front-end status bar as soon as it receives any registration failure response, even if the network registration failure is temporary and can be quickly recovered by the re-registration mechanism.

[0004] The disappearance and reappearance of the network service icon will obviously affect the user's perception, and frequent icon flickering not only interferes with the user and distracts the user's attention, but also easily causes the user to have a poor experience of network stability. SUMMARY

[0005] The embodiments of the present application provide a network service icon display control method and device, a terminal and a medium, which can solve the problem of user interference caused by frequent flickering of the network service icon.

[0006] In a first aspect, a network service icon display control method is provided, which includes: The terminal acquires cause information of network registration failure when it is detected that the registration to the target network fails; The terminal determines whether the network registration failure belongs to a recoverable network registration failure according to the cause information; The terminal maintains the service icon of the target network in the user interface display when it is determined that the network registration failure belongs to a recoverable network registration failure.

[0007] In a second aspect, a network service icon display control apparatus is provided, applied to a terminal, and comprising: a first obtaining module configured to, in a case where it is monitored that registration to a target network fails, obtain cause information of the network registration failure; a determining module configured to determine, according to the cause information, whether the network registration failure belongs to a recoverable network registration failure; a first control module configured to, in a case where it is determined that the network registration failure belongs to a recoverable network registration failure, maintain a service icon of the target network to be displayed on a user interface.

[0008] In a third aspect, a terminal is provided, comprising a processor and a memory, the memory storing programs or instructions executable on the processor, and the programs or instructions, when executed by the processor, implement steps of the method according to the first aspect.

[0009] In a fourth aspect, a terminal is provided, comprising a processor and a communication interface, wherein the processor is configured to: in a case where it is monitored that registration to a target network fails, obtain cause information of the network registration failure; determine, according to the cause information, whether the network registration failure belongs to a recoverable network registration failure; in a case where it is determined that the network registration failure belongs to a recoverable network registration failure, maintain a service icon of the target network to be displayed on a user interface.

[0010] In a fifth aspect, a readable storage medium is provided, storing programs or instructions, and the programs or instructions, when executed by a processor, implement steps of the method according to the first aspect.

[0011] In a sixth aspect, a chip is provided, comprising a processor and a communication interface, the communication interface and the processor being coupled, and the processor being configured to run programs or instructions to implement steps of the method according to the first aspect.

[0012] In a seventh aspect, a computer program / program product is provided, stored in a storage medium, and executed by at least one processor to implement steps of the method according to the first aspect.

[0013] In the embodiment of the present application, the terminal acquires the cause information of network registration failure in the case of monitoring the failure of registration to the target network; the terminal determines whether the network registration failure belongs to the recoverable network registration failure according to the cause information; and the terminal maintains the service icon of the target network displayed on the user interface in the case of determining that the network registration failure belongs to the recoverable network registration failure. In this way, when the terminal fails to register to the target network, it is determined whether the current network registration failure belongs to the recoverable network registration failure by analyzing the cause of registration failure, and if it is determined that it belongs to the recoverable network registration failure, the service icon of the target network is maintained displayed on the user interface, which can avoid the frequent flickering of the service icon of the target network caused by the temporary network registration failure, thereby reducing the interference to the user and avoiding the poor experience of the user caused by the poor network stability. BRIEF DESCRIPTION OF DRAWINGS

[0014] Figure 1 is a block diagram of a wireless communication system to which the embodiment of the present application can be applied; Figure 2 is one of flowcharts of the network service icon display control method provided by the embodiment of the present application; Figure 3 is a system module flowchart of the overall technical solution of the network service icon display control method provided by the embodiment of the present application; Figure 4 is the second flowchart of the network service icon display control method provided by the embodiment of the present application; Figure 5 is the third flowchart of the network service icon display control method provided by the embodiment of the present application; Figure 6 is a structural diagram of the network service icon display control apparatus provided by the embodiment of the present application; Figure 7 is a structural diagram of the terminal provided by the embodiment of the present application; Figure 8 is a hardware structural diagram of the terminal provided by the embodiment of the present application. DETAILED DESCRIPTION

[0015] The technical solutions in the embodiments of the present application will be described clearly below with reference to the drawings in the embodiments of the present application. Obviously, the described embodiments are only some of the embodiments of the present application, but not all the embodiments of the present application. Based on the embodiments in the present application, all other embodiments obtained by those of ordinary skill in the art belong to the scope of protection of the present application.

[0016] The terms "first", "second", and the like in the specification are used to distinguish between similar objects, and are not used to describe a particular sequential or chronological order. It is to be understood that such terms are used interchangeably, where appropriate, to refer to similar objects in order to illustrate embodiments of the present application by way of non-limiting example, and that the terms "first", "second", and the like are not intended to limit the number of objects to which the terms refer. For example, the first object can be one or more. Furthermore, the term "or" as used in the specification is intended to mean at least one of the connected objects. For example, the protection scope of "A or B" at least covers three schemes, namely, scheme one: including A and not including B; scheme two: including B and not including A; and scheme three: including both A and B. In addition, the terms "A and / or B", "at least one of A and B", and "at least one of A or B" also at least cover the above three schemes, respectively. The character " / " generally represents an "or" relationship between the associated objects before and after it.

[0017] The term "indicate" in the specification can be a direct indication (or explicit indication) or an indirect indication (or implicit indication). The direct indication can be understood as the sender explicitly informing the receiver of the specific information, the operation to be performed, or the result of the request, etc. in the sent indication. The indirect indication can be understood as the receiver determining the corresponding information according to the indication sent by the sender, or making a judgment and determining the operation to be performed or the result of the request according to the judgment result.

[0018] It is worth noting that the technology described in the embodiments of the present application is not limited to Long Term Evolution (LTE) / LTE-Advanced (LTE-A) systems, but can also be used in other wireless communication systems, such as Code Division Multiple Access (CDMA), Time Division Multiple Access (TDMA), Frequency Division Multiple Access (FDMA), Orthogonal Frequency Division Multiple Access (OFDMA), Single-carrier Frequency-Division Multiple Access (SC-FDMA) or other systems. The terms "system" and "network" in the embodiments of the present application are often used interchangeably, and the described technology can be used in the above-mentioned systems and radio technologies, as well as in other systems and radio technologies. The following description describes a New Radio (NR) system for example purposes, and NR terminology is used in most of the following description, but these technologies can also be applied to systems other than NR systems, such as 6th Generation (6G) communication systems. th

[0019] Figure 1 ​A block diagram of a wireless communication system to which embodiments of the present application can be applied is shown. The wireless communication system includes a terminal 11 and a network side device 12. The terminal 11 can also be referred to as a user equipment (UE). The terminal 11 can be a terminal side device such as a mobile phone, a tablet personal computer, a laptop computer, a notebook computer, a personal digital assistant (PDA), a palmtop computer, a netbook, an ultra-mobile personal computer (UMPC), a mobile Internet device (MID), an augmented reality (AR) device, a virtual reality (VR) device, a robot, a wearable device, a flight vehicle, a vehicle user equipment (VUE), a shipboard device, a pedestrian user equipment (PUE), a smart home (a home device with a wireless communication function such as a refrigerator, a television, a washing machine, or furniture), a game console, a personal computer (PC), a kiosk, or a self-service machine. The wearable device includes a smart watch, a smart bracelet, a smart earphone, smart glasses, smart jewelry (a smart bracelet, a smart necklace, a smart ring, a smart necklace, a smart anklet, a smart necklace, etc.), a smart wristband, and smart clothing. The vehicle-mounted device can also be referred to as a vehicle-mounted terminal, a vehicle-mounted controller, a vehicle-mounted module, a vehicle-mounted component, a vehicle-mounted chip, or a vehicle-mounted unit. In addition, the terminal 11 can be a chip in a terminal, such as a modem chip or a system on chip (SoC). It should be noted that the specific type of the terminal 11 is not limited in the embodiments of the present application. The network side device 12 can include an access network device or a core network device. The access network device can also be referred to as a radio access network (RAN) device, a radio access network function, or a radio access network unit. The access network device can include a base station, a wireless local area network (WLAN) access point (AP), or a wireless fidelity (WiFi) node.The base station can be referred to as a Node B (NB), an evolved Node B (eNB), a next generation Node B (gNB), a New Radio Node B (NR Node B), an access point, a relay base station (RBS), a serving base station (SBS), a base transceiver station (BTS), a radio base station, a radio transceiver, a basic service set (BSS), an extended service set (ESS), a home Node B (HNB), a home evolved Node B, a transmit / receive point (TRP), a Non-Terrestrial Network (NTN) device (such as a satellite or a high altitude platform station, etc.), or some other suitable terminology in the art, and is not limited to a particular technical terminology, provided that the same technical effect is achieved. It should be noted that in the embodiments of the present application, only the base station in the NR system is taken as an example for introduction, and the specific type of the base station is not limited.

[0020] The core network device can also be referred to as a core network node, a core network function, or a core network network element, etc., which includes but is not limited to at least one of the following: a mobility management entity (MME), an access and mobility management function (AMF), a session management function (SMF), a user plane function (UPF), a policy control function (PCF), a policy and charging rules function (PCRF), an edge application server discovery function (EASDF), a unified data management (UDM), a unified data repository (UDR), a home subscriber server (HSS), a centralized network configuration (CNC), a network repository function (NRF), a network exposure function (NEF), a local NEF (L-NEF), a binding support function (BSF), an application function (AF), a location management function (LMF), a gateway mobile location center (GMLC), a network data analytics function (NWDAF), a non-terrestrial network (NTN) device (such as a satellite or a high altitude platform station, etc.), and the like.It should be noted that the embodiments of this application only use the core network equipment in the NR system as an example for introduction, and do not limit the specific type of core network equipment. If the name of the core network equipment mentioned in the embodiments of this application changes in subsequent protocol versions (such as 6G), it is also within the scope of protection of this application.

[0021] Optionally, the core network equipment can be implemented by one or more functional modules in a single device, or by multiple devices working together; this application does not specifically limit this. It is understood that the aforementioned functional modules can be network elements in hardware devices, software functional modules running on dedicated hardware, or virtualized functional modules instantiated on a platform (e.g., a cloud platform).

[0022] The network service icon display control method provided in this application will be described in detail below with reference to the accompanying drawings and through some embodiments and application scenarios.

[0023] Please see Figure 2 , Figure 2 A flowchart of the network service icon display control method provided in the embodiments of this application is shown below. Figure 2 As shown, the method includes the following steps: Step 201: When the terminal detects that the registration with the target network has failed, it obtains the reason information for the network registration failure.

[0024] When a terminal needs to access a target network to perform related services, it must first initiate a registration request to the target network and periodically re-register to ensure the availability of the target network. During the terminal's access to the target network, the registration status can be monitored in real time. When a registration failure is detected, the cause of the failure can be analyzed to determine whether the failure is temporary or recoverable. Specifically, the cause information of the network registration failure can be obtained, such as obtaining the failure cause value from the registration failure response message returned by the network side, checking the network connection status to determine whether the registration failure was caused by a network disconnection, or obtaining the terminal's network status. By obtaining the registration failure cause information, the specific reason for the current network registration failure can be determined.

[0025] In this embodiment of the application, the target network can be any network that supports terminal access and is used to provide a specific service, such as an IMS network used to provide key services such as high-quality voice (VoLTE, VoNR) and video calls (ViLTE, ViNR).

[0026] Step 202: The terminal determines, based on the cause information, whether the network registration failure is a recoverable network registration failure.

[0027] In this step, the terminal can determine whether the current network registration failure is a recoverable failure based on the obtained registration failure reason information. Specifically, it can determine whether the current registration failure is recoverable by analyzing the registration failure reason information and combining it with historical registration failure information and successful registration recovery information. Alternatively, it can pre-store a list of recoverable network registration failure reason information and determine whether the current network registration failure is a recoverable failure by judging whether the current failure reason information is in the stored reason information list.

[0028] For example, when common registration failure reasons include Internal Server Error or Service Unavailable, indicating temporary server-side issues, it can be directly determined that the current network registration failure is a recoverable failure. Conversely, when the registration failure reason is 403 Forbidden or 404 Not Found, it can be determined that the current network registration failure is not a recoverable failure.

[0029] Optionally, obtaining the reason information for this network registration failure includes: Obtain the network registration failure response message returned by the network-side device; Step 202 includes: Extract the failure reason value from the network registration failure response message; The failure reason value is matched with the network registration failure whitelist, which stores a list of reason values ​​for recoverable network registration failures. If the failure reason value is included in the reason value list, the network registration failure is determined to be a recoverable network registration failure.

[0030] In some embodiments, when the terminal fails to register with the target network and the access network, such as cellular network or WIFI, is disconnected, the network-side device will carry the corresponding failure reason value in the network registration failure response message and return it to the terminal. The terminal will then receive the network registration failure response message returned by the network-side device and extract the failure reason value from it, such as the failure reason value 408 indicating a request timeout, or the failure reason value 500 indicating an internal server error.

[0031] In this embodiment, the terminal can use a network registration failure whitelist to summarize the cause values ​​of recoverable network registration failures. By matching the whitelist, it can quickly determine whether the current network registration failure is recoverable. Specifically, all recoverable network registration failure cause values ​​are stored in the whitelist. After retrieving a failure cause value, the terminal can match it with the whitelist, such as checking if the cause value exists in the whitelist or checking if the whitelist contains the cause value. If found, the match is successful, indicating that the current network registration failure is recoverable; otherwise, it is determined that the current network registration failure is not recoverable.

[0032] It should be noted that the network registration failure whitelist can be updated via cloud synchronization. For example, when the list of recoverable network registration failure reasons is updated, the cloud server pushes it to the terminal to update the local network registration failure whitelist, or the terminal can periodically request the cloud server to update it.

[0033] In this way, by implementing this method, it is possible to quickly and accurately determine whether a current network registration failure is a recoverable failure by matching the network registration failure whitelist.

[0034] Optionally, the network registration failure whitelist also stores network status information corresponding to each reason value in the reason value list; The method further includes: Obtain the network status information of the terminal; The step of matching the failure reason value with the network registration failure whitelist includes: The failure reason value and the network status information of the terminal are matched with the network registration failure whitelist; When the failure reason value is included in the reason value list, determining that the network registration failure is a recoverable network registration failure includes: If the failure reason value matches the first reason value in the reason value list, and the network status information of the terminal matches the first network status information, it is determined that the network registration failure is a recoverable network registration failure, and the first network status information is the network status information corresponding to the first reason value stored in the network registration failure whitelist.

[0035] In some embodiments, the network registration failure type can be determined by combining the registration failure reason value and the terminal's network status information. Specifically, when obtaining the failure reason value, the terminal's current network status information, such as the Public Data Network (PDN) establishment status, network service status, network standard, etc., can also be obtained. Furthermore, the network registration failure whitelist also stores the reason values ​​and corresponding network status information included in recoverable network registration failures.

[0036] When determining the cause of registration failure, the obtained failure cause value and the network status information of the terminal can be matched with the network registration failure whitelist. The system checks whether the failure cause value exists in the network registration failure whitelist and whether the corresponding network status information is consistent with the network status information of the terminal. If both match successfully, the current network registration failure is determined to be a recoverable network registration failure. If either the failure cause value or the network status information does not match, the current network registration failure is determined to be an unrecoverable network registration failure.

[0037] In this way, by combining the failure reason value with network status information to determine whether the network registration failure is recoverable, the accuracy and reliability of the judgment results can be better ensured.

[0038] Optionally, the network status information includes at least one of the following: network type, Public Land Mobile Network (PLMN) information, Public Data Network (PDN) connection establishment status, framework service status, current network cell information, and geographic location information.

[0039] The network status information of the terminal obtained and the network status information stored in the network registration failure whitelist can both include one or more of the following: network standard, PLMN information, PDN connection establishment status, framework service status, current network cell information (such as Tracking Area Code (TAC), Cell ID), and geographical location information. For example, the network status information stored in the network registration failure whitelist includes PDN establishment is normal, network service is normal, and the network standard is 4G / 5G.

[0040] Step 203: If the terminal determines that the network registration failure is a recoverable network registration failure, it maintains the service icon of the target network displayed on the user interface.

[0041] If it is determined that the current network registration failure is a recoverable network registration failure, the original control logic of canceling the display of the target network's service icon on the front-end user interface can be changed to keep the display of the target network's service icon on the front-end user interface unchanged, so as not to make users aware of the current temporary failure of the target network and to avoid the interference and bad experience caused by the frequent flashing of the service icon.

[0042] Optionally, step 203 includes: Intercept the event of the target network registration failure to prevent the sending of network registration status update notifications to the user interface (UI) module, so as to maintain the display of the target network's service icon in the user interface.

[0043] In other words, if it is determined that the current network registration failure is a recoverable network registration failure, the event of this failure to register with the target network can be intercepted to prevent the network registration status update notification from being sent to the UI module. This ensures that the service icon of the target network is still displayed on the front end, avoiding the network service icon from flashing on the front end due to temporary registration failure.

[0044] Optionally, the method further includes: The terminal initiates a re-registration with the target network.

[0045] In some embodiments, while maintaining the service icon of the target network displayed on the user interface, the original re-registration process of the terminal to the target network can be triggered or continued. For example, the re-registration to the target network can be initiated after a timer expires, thus ensuring a faster restoration of the registration status to the target network.

[0046] Optionally, the method further includes: If it is determined that the network registration failure is not a recoverable network registration failure, a network registration status update notification is sent to the UI module. The network registration status update notification is used to indicate that the current registration with the target network has failed. The service icon controlling the target network is not displayed in the user interface.

[0047] In some embodiments, if it is determined that the network registration failure is not a recoverable network registration failure, it indicates that the current network registration failure cannot be recovered in the short term. Therefore, it is necessary to hide or cancel the display of the service icon on the front-end user interface until the network registration is successful. Thus, the standard procedure can be followed, that is, to send a registration status update notification to the UI module, indicating that the current registration with the target network has failed, and to control the service icon of the target network not to be displayed on the front end, such as controlling the HD icon corresponding to the IMS network service to disappear or hide.

[0048] In this way, when a terminal experiences a prolonged and unrecoverable network registration failure, the user can be informed that there is a problem with the current network registration and that the target service is temporarily unavailable by canceling the display of the corresponding network service icon, thus clearly informing the user of the availability status of the target network service.

[0049] Optionally, the target network includes an IP Multimedia Subsystem (IMS) network.

[0050] As an application scenario, the embodiments of this application can be applied to the scenario of a terminal registering with the IMS network. When the terminal fails to register with the IMS network and the reason for the failure is a recoverable type, the HD icon displayed on the terminal's front-end user interface can be maintained to avoid unnecessary interference to the user caused by the icon disappearing briefly and then re-displaying.

[0051] The following example uses an IMS network as the target network. Figure 3 The implementation methods of the embodiments of this application are illustrated by examples: Step 1, Status Monitoring and Event Triggering: Monitor the IMS registration status of the terminal. When an IMS registration failure event is detected, obtain the IMS registration failure response message returned by the network side, as well as the current corresponding network status value of the terminal.

[0052] Step 2, Reason Extraction and Judgment: Extract the failure reason value from the obtained IMS registration failure response message, and combine it with the terminal's network status value. Match the summarized failure reason value and network status value with the network registration failure whitelist pre-stored in the terminal.

[0053] The network registration failure whitelist includes one or more reason values ​​indicating that the registration failure is temporary and can be automatically recovered, along with corresponding network status values, such as, but not limited to: 408 (Request Timeout), 500 (Internal Server Error), 503 (Service Unavailable), 504 (Server Timeout), etc.; at the same time, IMS PDN is established normally, the network service is normal, and the resident standard is 4G / 5G, etc.

[0054] Step 3: Differentiation processing of control modules: If the match is successful, meaning the failure reason value exists in the whitelist, then this registration failure is determined to be a recoverable registration failure. The registration failure event is intercepted, and no "IMS not registered" status update notification is sent to the application layer or framework layer module responsible for updating the UI icon display, such as the UI module. The display state of the front-end HD icon remains unchanged, and the original IMS re-registration process of the terminal is triggered or continued. For example, re-registration is initiated after a timer expires.

[0055] If the match fails, i.e. the failure reason value is not in the whitelist or the reason is unknown, the registration failure is determined to be an unrecoverable registration failure. For example, the current failure reason value is 403 (Forbidden) or 404 (Not Found), the network status is IMS PDN establishment rejected, the network status is roaming, and it is handled according to the standard procedure, i.e., a registration status update notification is sent to the UI module, and the front-end HD icon is controlled to disappear or hide.

[0056] Step 4: UI Status Display Synchronization: Continuously attempt IMS re-registration on the backend. When re-registration is successful, the UI status remains in the "Registered" state, thus requiring no UI operations and achieving seamless status synchronization.

[0057] The existing solution is to hide the HD icon in the UI module after receiving the IMS registration failure message, and then show the HD icon again after successful re-registration (which may only take 2 seconds). This causes the UI icon display status to update too frequently, resulting in a "flickering" effect, which affects the user experience.

[0058] Compared to existing solutions, this application's solution monitors and parses IMS registration failure messages to obtain the terminal's current network status value. If it is determined that the registration failure can be recovered, the UI status update event is intercepted to maintain the display of the HD icon and avoid frequent icon flickering, thereby improving the user experience.

[0059] like Figure 4 As shown, this application embodiment provides a method for maintaining the display of the IMS service icon on a mobile terminal. The overall process of this embodiment includes the following steps: Step 41: The mobile terminal has successfully registered with IMS; Step 42: The UI interface displays the HD icon; Step 43: Detected an IMS registration failure event; Step 44: Extract the failure reason, including the IMS registration failure reason value Cause and the terminal's current corresponding network status value. Determine whether the reason is in the "network registration failure whitelist". If yes, proceed to step 45; otherwise, proceed to step 48. Step 45: Intercept the abnormal event and do not send a status update notification to the UI; Step 46: Maintain HD icon display; Step 47: Trigger the IMS re-registration process; Step 48: Follow the standard procedure: Notify the UI to update the status and hide the HD icon.

[0060] Optionally, step 201 includes: If a terminal registers with the target network via a wireless network, and a disconnection from the wireless network is detected, the reason for the disconnection is analyzed, and the historical connection information of the wireless network is obtained. Step 202 includes: Based on the cause information and the historical connection information, determine whether the network registration failure is a recoverable network registration failure.

[0061] In some application scenarios, a terminal can register with the target network via a wireless network as an access network. In this case, if the connection with the wireless network is lost, the registration with the target network will fail, and the terminal needs to re-initiate the registration with the target network. The wireless network can be cellular or Wi-Fi (Wireless Fidelity).

[0062] Taking high-definition Wi-Fi voice calling (VoWiFi) as an example, it registers with the operator's IMS through a Wi-Fi network as the access network and enables the making and receiving of voice / video calls. When the terminal enables this function, the terminal's status bar will usually display a specific icon, such as "Wi-Fi Calling," "VoWiFi," or a similar label, to indicate to the user that the service is currently in use.

[0063] According to the standard procedure of existing technology, once the terminal operating system detects a Wi-Fi connection loss, such as a link layer disconnection, it immediately updates the network connection status and notifies the UI module to hide or remove the "Wi-Fi Calling" icon. Even if the Wi-Fi connection is quickly and automatically restored within seconds, the terminal needs to re-initiate IMS registration and display the icon again after successful registration. This process causes the "Wi-Fi Calling" icon to flash frequently, causing unnecessary anxiety for the user.

[0064] Wi-Fi networks in home or office environments may experience brief interruptions due to factors such as router restarts, momentary radio frequency interference between devices, or channel congestion. These interruptions usually resolve automatically within a few seconds.

[0065] In this embodiment, to avoid frequent flashing of the corresponding service icon due to a brief disconnection from the wireless network, the cause of the disconnection can be analyzed when a disconnection is detected. This includes determining if it's due to a brief router restart, momentary radio frequency interference between the terminal and the router, or channel congestion. Historical connection information of the wireless network can also be obtained, such as confirming that the wireless network is a frequently used home or work network with a stable historical connection. Then, based on the obtained cause and historical connection information, it can be determined whether the current network registration failure is a recoverable failure. For example, if the cause of the wireless network disconnection is a link layer loss, and the current wireless network is a home network with a stable historical connection, then the current network registration failure is considered recoverable, and the network will re-register successfully after the wireless network is restored. Conversely, if the terminal moved a long distance when the wireless network disconnected, and the signal strength gradually decreased during this process, and the current wireless network is a temporary connection, then the current network registration failure is not considered recoverable.

[0066] In this way, when registering to a target network via wireless network access, if the wireless network is disconnected, by analyzing the reason for the disconnection and the historical connection information of the wireless network, it is possible to identify recoverable network registration failure scenarios. In such scenarios, the flashing of the service icon on the front end can be reduced, minimizing disturbance to the user.

[0067] The specific implementation methods of this application will be illustrated below using two specific application scenarios: Scenario 1: During large gatherings, such as sporting events or concerts, the high density of users in certain areas causes temporary overload of IMS core network equipment in those areas, such as the Serving Call Session Control Function (S-CSCF), due to reaching its processing capacity limit (because server overload is usually temporary and expected to be alleviated within seconds or minutes). In this situation, the server cannot process all registration requests in a timely manner and will return a 503 (Service Unavailable) error response to the terminal.

[0068] like Figure 5 As shown, the method for controlling the display of the IMS network service icon in this scenario includes the following steps: Step 51, Initial state: The terminal has successfully registered with IMS, and the HD icon is displayed in the UI status bar.

[0069] Step 52, Event Trigger: Due to a momentary overload of the network-side server, the periodic re-registration request initiated by the terminal failed, and the terminal received a registration failure response message from the network side. The IMS registration failure reason value is 503 (ServiceUnavailable).

[0070] Step 53, Cause Analysis and Judgment: The terminal's parsing and judgment module immediately extracts the failure cause value "503" and the terminal's current network status value, queries the preset network registration failure whitelist, and finds that the current cause (IMS error 503 and the corresponding terminal status value) exists in the whitelist. Therefore, this failure is determined to be a recoverable registration failure.

[0071] Step 54, Intelligent Interception and UI Maintenance: The control module then activates the interception mechanism to prevent the "503" failure reason from being transmitted to the upper-level UI module. Therefore, the UI module responsible for the status bar display is unaware of this registration failure, the HD icon remains displayed, and the user is completely unaware of the network fluctuations occurring in the background.

[0072] Step 55, Silent Background Retry: While the network is being blocked, the terminal's re-registration management module silently initiates a re-registration attempt in the background according to standard protocols, such as the timer mechanism in RFC 3261, or the time suggested by the Retry-After header field that may be carried in the network response. Since the server overload is temporary, after several retries, for example, after 30 seconds, the terminal successfully re-registers with the IMS network.

[0073] Step 56, Seamless Recovery: After successful IMS registration, the IMS protocol stack updates its internal state to "Registered". Since the UI state is never interrupted, no additional icon refresh is required, and the entire process is seamless for the user.

[0074] Scenario 2: A user has registered with their carrier's IMS via Wi-Fi at home, and a specific icon, such as "Wi-Fi Calling," is displayed in the device's status bar to indicate that the service is currently in use. However, the home's wireless router suddenly restarts automatically due to power fluctuations, a process that lasts approximately 15 seconds.

[0075] The method for controlling the display of IMS network service icons in this scenario includes the following steps: Step 61, Status Monitoring and Event Triggering: The terminal detects that the connection to the home Wi-Fi network (a saved, highly trusted network) has suddenly been lost.

[0076] Step 62, Cause Extraction and Judgment: The analysis and judgment module immediately performs anomaly analysis on the event and finds that the disconnection is caused by a link layer loss, and the network is a "home network" with a stable historical connection. Sensor data shows that the terminal has not moved. Therefore, this is determined to be a recoverable disconnection.

[0077] It should be noted that the terminal does not apply the same handling strategy to all Wi-Fi disconnection events. The system immediately analyzes the cause of the disconnection and assesses its recoverability. The judgment logic is based on a predefined whitelist of recoverable network registration failures, which may include, but is not limited to: 1) The link layer cause value indicates that the signal disappears momentarily, but historical records show that the network signal is strong and stable.

[0078] 2) Dynamic Host Configuration Protocol (DHCP) lease renewal failed (can be quickly retried successfully).

[0079] 3) Disconnect from known, trusted Wi-Fi networks (such as saved home / office Wi-Fi networks).

[0080] 4) No physical location movement was detected (this can be combined with any of the above criteria for judgment).

[0081] If a match is found, the fault is considered to be recoverable; otherwise, the anomaly is considered to be an unrecoverable failure, such as when the user manually turns off Wi-Fi or connects to an unavailable new network.

[0082] Step 63, control module decision: When the fault is determined to be recoverable quickly, the disconnection event is intercepted and the UI module is not notified; the "Wi-Fi Calling" icon on the status bar remains displayed; after the router restarts, the terminal automatically reconnects to the Wi-Fi network and quickly rebinds the IMS session.

[0083] Step 64, UI icon display synchronization: Throughout the process, the UI icons do not flicker at all, and the continuity of user experience is protected to the greatest extent.

[0084] In summary, the purpose of this application is to provide a method for maintaining the display of a terminal network service icon, used to maintain the display of the network service icon when a recoverable network registration failure occurs, avoiding frequent icon flickering, thereby improving user experience and perceived network stability. The improvements of this application are as follows: 1) Intelligent cause analysis mechanism: Not all registration failures are handled with the same strategy. This application parses the cause value and the terminal's current network status value in the network registration failure response and compares them with a predefined "recoverable network registration failure whitelist". 2) State interception and maintenance mechanism: When the failure cause is determined to be recoverable, the system will intercept the abnormal event, preventing it from triggering the UI update process (i.e., not hiding the service icon), while silently attempting re-registration in the backend. 3) Since the UI display is not interrupted, after successful re-registration, there is no need to display the icon again, thus achieving user-unobtrusive fault self-healing and recovery.

[0085] The embodiments of this application bring the following significant benefits: 1) Significantly improved user experience: It eliminates the flickering of UI service icons caused by brief network fluctuations, giving users the perception that network services are "always stable and continuously online," enhancing user confidence in the device and the operator. 2) Intelligent differentiation of fault types: Through a whitelist mechanism for failure reasons, it can intelligently distinguish between temporary and permanent faults, ensuring user experience without misleading users when real faults occur. For example, when the SIM card is invalid, the network service icon will not be displayed correctly. 3) Strong compatibility: This solution is fully compatible with existing IMS standard protocols and terminal re-registration mechanisms. It adds an intelligent decision-making layer on top of the existing process and does not affect the operation of other normal functions. 4) Low implementation cost: This application mainly consists of software algorithms, which can be implemented in the existing IMS protocol stack and UI design of the terminal through software upgrades or configuration updates without hardware modifications, making it easy to deploy and promote.

[0086] The network service icon display control method in this embodiment involves a terminal detecting a registration failure to a target network and obtaining information about the reason for the failure. Based on this information, the terminal determines whether the registration failure is a recoverable failure. If the failure is recoverable, the terminal maintains the target network's service icon displayed on the user interface. This method, by analyzing the reason for the registration failure to determine if it is a recoverable failure and maintaining the target network's service icon on the user interface, avoids frequent flashing of the target network's service icon due to brief registration failures, thus reducing user interference and preventing a poor user experience due to network instability.

[0087] The network service icon display control method provided in this application can be executed by a network service icon display control device. This application uses the execution of the network service icon display control method by a network service icon display control device as an example to illustrate the network service icon display control device provided in this application.

[0088] This application provides a network service icon display control device. As an example, the network service icon display control device can be a communication device or a component within a communication device, such as a chip. The communication device can be a terminal. Exemplarily, the terminal can include, but is not limited to, the types of terminals 11 listed above; this application does not impose specific limitations.

[0089] The network service icon display control device includes a receiving module, a transmitting module, and a processing module. These modules can be implemented in software or hardware. When implemented in hardware, the processing module can be implemented by a processor. For example, the processor can include general-purpose processors, special-purpose processors, etc., such as central processing units (CPUs), microprocessors, digital signal processors (DSPs), artificial intelligence (AI) processors, graphics processing units (GPUs), application-specific integrated circuits (ASICs), network processors (NPs), field-programmable gate arrays (FPGAs), or other programmable logic devices, gate circuits, transistors, discrete hardware components, etc. The receiving and transmitting modules can be implemented by a communication interface, which can include one or more of the following: transceivers, pins, circuits, buses, radio frequency units, etc.

[0090] For details, see Figure 6 When the network service icon display control device is a terminal or a component within a terminal, the network service icon display control device 600 includes: The first acquisition module 601 is used to acquire the reason information for the failure of network registration when it is detected that the registration with the target network has failed. The determining module 602 is used to determine, based on the cause information, whether the network registration failure is a recoverable network registration failure. The first control module 603 is used to maintain the service icon of the target network displayed on the user interface when it is determined that the network registration failure is a recoverable network registration failure.

[0091] Optionally, the first acquisition module 601 is used to acquire the network registration failure response message returned by the network-side device; The determination module 602 includes: The extraction unit is used to extract the failure reason value from the network registration failure response message; A matching unit is used to match the failure reason value with a network registration failure whitelist, which stores a list of reason values ​​for recoverable network registration failures. The determining unit is configured to determine, when the failure reason value is included in the reason value list, that the network registration failure is a recoverable network registration failure.

[0092] Optionally, the network registration failure whitelist also stores network status information corresponding to each reason value in the reason value list; The network service icon display control device 600 also includes: The second acquisition module is used to acquire the network status information of the terminal; The matching unit is used to match the failure reason value, the network status information of the terminal, and the network registration failure whitelist. The determining unit is used to determine that the network registration failure is a recoverable network registration failure when the failure reason value matches the first reason value in the reason value list and the network status information of the terminal matches the first network status information. The first network status information is the network status information corresponding to the first reason value stored in the network registration failure whitelist.

[0093] Optionally, the network status information includes at least one of the following: network type, Public Land Mobile Network (PLMN) information, Public Data Network (PDN) connection establishment status, framework service status, current network cell information, and geographic location information.

[0094] Optionally, the first control module 603 is used to intercept the event of the target network registration failure to prevent the sending of network registration status update notifications to the user interface (UI) module, so as to maintain the display of the target network's service icon on the user interface.

[0095] Optionally, the network service icon display control device 600 includes: The sending module is used to send a network registration status update notification to the UI module when it is determined that the network registration failure is not a recoverable network registration failure. The network registration status update notification is used to indicate that the current registration with the target network has failed. The second control module is used to prevent the service icon of the target network from being displayed in the user interface.

[0096] Optionally, the acquisition module 601 is used to analyze the reason information of the disconnection from the wireless network and acquire the historical connection information of the wireless network if it is detected that the terminal has registered with the target network through the wireless network. The determining module 602 is used to determine whether the network registration failure is a recoverable network registration failure based on the cause information and the historical connection information.

[0097] Optionally, the target network includes an IP Multimedia Subsystem (IMS) network.

[0098] The network service icon display control device 600 in this embodiment of the application, upon detecting a registration failure to a target network, acquires the reason information for the network registration failure; based on the reason information, determines whether the network registration failure is a recoverable failure; and if it is determined to be a recoverable failure, maintains the display of the target network's service icon on the user interface. In this way, when a terminal fails to register to a target network, by analyzing the reason for the registration failure to determine whether it is a recoverable failure, and if so, maintaining the display of the target network's service icon on the user interface, it avoids frequent flashing of the target network service icon due to brief network registration failures, thereby reducing interference to the user and preventing a poor user experience due to poor network stability.

[0099] The network service icon display control device provided in this application embodiment can achieve... Figures 2 to 5 The various processes implemented in the method embodiments achieve the same technical effect, and will not be described again here to avoid repetition.

[0100] like Figure 7 As shown, this application embodiment also provides a terminal 700, including a processor 701 and a memory 702. The memory 702 stores a program or instructions that can run on the processor 701. When the program or instructions are executed by the processor 701, they implement the various steps of the above-described network service icon display control method embodiment and can achieve the same technical effect.

[0101] This application embodiment also provides a terminal, including a processor and a communication interface, wherein the communication interface is coupled to the processor, and the processor is used to run programs or instructions to implement, for example... Figure 2 The steps in the method embodiment shown are illustrated. This terminal embodiment corresponds to the above-described terminal-side method embodiment. All implementation processes and methods of the above-described method embodiments can be applied to this terminal embodiment and achieve the same technical effect. The terminal can be... Figure 6 The network service icon shown indicates the control device. Specifically, Figure 8 A schematic diagram of the hardware structure of a terminal to implement an embodiment of this application.

[0102] The terminal 800 includes, but is not limited to, at least some of the following components: radio frequency unit 801, network module 802, audio output unit 803, input unit 804, sensor 805, display unit 806, user input unit 807, interface unit 808, memory 809, and processor 810.

[0103] Those skilled in the art will understand that the terminal 800 may also include a power supply (such as a battery) for supplying power to various components. The power supply can be logically connected to the processor 810 through a power management system, thereby enabling functions such as managing charging, discharging, and power consumption through the power management system. Figure 8 The terminal structure shown does not constitute a limitation on the terminal. The terminal may include more or fewer components than shown, or combine certain components, or have different component arrangements, which will not be elaborated here.

[0104] It should be understood that, in this embodiment, the input unit 804 may include a graphics processor 8041 and a microphone 8042. The graphics processor 8041 processes image data of still images or videos obtained by an image capture device (such as a camera) in video capture mode or image capture mode. The display unit 806 may include a display panel 8061, which may be configured in the form of a liquid crystal display, an organic light-emitting diode, or the like. The user input unit 807 includes at least one of a touch panel 8071 and other input devices 8072. The touch panel 8071 is also called a touch screen. The touch panel 8071 may include two parts: a touch detection device and a touch controller. Other input devices 8072 may include, but are not limited to, physical keyboards, function keys (such as volume control buttons, power buttons, etc.), trackballs, mice, and joysticks, which will not be described in detail here.

[0105] In this embodiment, after receiving downlink data from the network-side device, the radio frequency unit 801 can transmit it to the processor 810 for processing; in addition, the radio frequency unit 801 can send uplink data to the network-side device. Typically, the radio frequency unit 801 includes, but is not limited to, antennas, amplifiers, transceivers, couplers, low-noise amplifiers, duplexers, etc.

[0106] The memory 809 can be used to store software programs or instructions, as well as various data. The memory 809 may primarily include a first storage area for storing programs or instructions and a second storage area for storing data. The first storage area may store the operating system, application programs or instructions required for at least one function (such as sound playback, image playback, etc.). Furthermore, the memory 809 may include volatile memory or non-volatile memory. The non-volatile memory may be read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), or flash memory. Volatile memory can be random access memory (RAM), static random access memory (SRAM), dynamic random access memory (DRAM), synchronous dynamic random access memory (SDRAM), double data rate synchronous dynamic random access memory (DDRSDRAM), enhanced synchronous dynamic random access memory (ESDRAM), synchronous link dynamic random access memory (SLDRAM), and direct memory bus RAM (DRRAM). The memory 809 in the embodiments of this application includes, but is not limited to, these and any other suitable types of memory.

[0107] Processor 810 may include one or more processing units; optionally, processor 810 integrates an application processor and a modem processor, wherein the application processor mainly handles operations involving the operating system, user interface, and applications, and the modem processor mainly handles wireless communication signals, such as a baseband processor. It is understood that the aforementioned modem processor may also not be integrated into processor 810.

[0108] The processor 810 is used for: If registration with the target network fails, obtain information about the reason for the failure. Based on the aforementioned cause information, determine whether the network registration failure is a recoverable network registration failure; If it is determined that the network registration failure is a recoverable network registration failure, the service icon of the target network will be maintained in the user interface.

[0109] Optionally, the processor 810 is also used for: Obtain the network registration failure response message returned by the network-side device; Extract the failure reason value from the network registration failure response message; The failure reason value is matched with the network registration failure whitelist, which stores a list of reason values ​​for recoverable network registration failures. If the failure reason value is included in the reason value list, the network registration failure is determined to be a recoverable network registration failure.

[0110] Optionally, the network registration failure whitelist also stores network status information corresponding to each reason value in the reason value list; The 810 processor is also used for: Obtain the network status information of the terminal; The failure reason value and the network status information of the terminal are matched with the network registration failure whitelist; If the failure reason value matches the first reason value in the reason value list, and the network status information of the terminal matches the first network status information, it is determined that the network registration failure is a recoverable network registration failure, and the first network status information is the network status information corresponding to the first reason value stored in the network registration failure whitelist.

[0111] Optionally, the network status information includes at least one of the following: network type, Public Land Mobile Network (PLMN) information, Public Data Network (PDN) connection establishment status, framework service status, current network cell information, and geographic location information.

[0112] Optionally, the processor 810 is also used for: Intercept the event of the target network registration failure to prevent the sending of network registration status update notifications to the user interface (UI) module, so as to maintain the display of the target network's service icon on the user interface.

[0113] Optionally, the processor 810 is also used for: If it is determined that the network registration failure is not a recoverable network registration failure, a network registration status update notification is sent to the UI module. The network registration status update notification is used to indicate that the current registration with the target network has failed. The service icon controlling the target network is not displayed in the user interface.

[0114] Optionally, the processor 810 is also used for: If a terminal registers with the target network via a wireless network, and a disconnection from the wireless network is detected, the reason for the disconnection is analyzed, and the historical connection information of the wireless network is obtained. Based on the cause information and the historical connection information, determine whether the network registration failure is a recoverable network registration failure.

[0115] Optionally, the target network includes an IP Multimedia Subsystem (IMS) network.

[0116] It is understood that the implementation process of each implementation method mentioned in this embodiment can refer to the relevant description of the method embodiment and achieve the same or corresponding technical effect. To avoid repetition, it will not be described again here.

[0117] This application also provides a readable storage medium storing a program or instructions. When the program or instructions are executed by a processor, they implement the various processes of the above-described network service icon display control method embodiment and achieve the same technical effect. To avoid repetition, they will not be described again here.

[0118] The processor mentioned above is either the processor in the terminal described in the above embodiments or the processor in the network-side device. The readable storage medium includes computer-readable storage media, such as computer read-only memory (ROM), random access memory (RAM), magnetic disk, or optical disk. In some examples, the readable storage medium may be a non-transient readable storage medium.

[0119] This application embodiment also provides a chip, which includes a processor and a communication interface. The communication interface is coupled to the processor. The processor is used to run programs or instructions to implement the various processes of the above-described network service icon display control method embodiment, and can achieve the same technical effect. To avoid repetition, it will not be described again here.

[0120] It should be understood that the chip mentioned in the embodiments of this application may also be referred to as a system-on-a-chip, system chip, chip system, or system-on-a-chip, etc.

[0121] This application also provides a computer program / program product, which is stored in a storage medium and executed by at least one processor to implement the various processes of the above-described network service icon display control method embodiment, and can achieve the same technical effect. To avoid repetition, it will not be described again here.

[0122] It should be noted that, in this document, the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or apparatus. Without further limitations, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or apparatus that includes that element. Furthermore, it should be noted that the scope of the methods and apparatuses in the embodiments of this application is not limited to performing functions in the order shown or discussed, but may also include performing functions substantially simultaneously or in the reverse order, depending on the functions involved. For example, the described methods may be performed in a different order than described, and various steps may be added, omitted, or combined. Additionally, features described with reference to certain examples may be combined in other examples.

[0123] From the above description of the embodiments, those skilled in the art can clearly understand that the methods of the above embodiments can be implemented by means of computer software products plus necessary general-purpose hardware platforms, and of course, they can also be implemented by hardware. The computer software product is stored in a storage medium (such as ROM, RAM, magnetic disk, optical disk, etc.), and the computer software product includes several instructions to cause the terminal or network-side device to execute the methods described in the various embodiments of this application.

[0124] The embodiments of this application have been described above with reference to the accompanying drawings. However, this application is not limited to the specific embodiments described above. The specific embodiments described above are merely illustrative and not restrictive. Those skilled in the art can make many other implementations under the guidance of this application without departing from the spirit and scope of the claims. All of these implementations are within the protection scope of this application.

Claims

1. A network service icon display control method characterized by comprising: The method comprises the following steps: In the case that the terminal monitors the failure of registration to a target network, the terminal acquires the cause information of the network registration failure; The terminal determines whether the network registration failure belongs to a recoverable network registration failure according to the cause information; In the case that the terminal determines that the network registration failure belongs to a recoverable network registration failure, the terminal maintains the service icon of the target network in the display of the user interface.

2. The method of claim 1, wherein, The acquisition of the cause information of the network registration failure comprises the following steps: The terminal acquires the network registration failure response message returned by the network side device; The determination of whether the network registration failure belongs to a recoverable network registration failure according to the cause information comprises the following steps: The terminal extracts the failure cause value from the network registration failure response message; The terminal matches the failure cause value with a network registration failure white list, wherein the network registration failure white list stores a list of cause values of recoverable network registration failures; In the case that the list of cause values contains the failure cause value, the terminal determines that the network registration failure belongs to a recoverable network registration failure.

3. The method of claim 2, wherein, The network registration failure white list further stores network state information corresponding to each cause value in the list of cause values; The method further comprises the following steps: The terminal acquires the network state information of the terminal; The matching of the failure cause value with the network registration failure white list comprises the following steps: The terminal matches the failure cause value, the network state information of the terminal and the network registration failure white list; In the case that the failure cause value matches a first cause value in the list of cause values and the network state information of the terminal matches a first network state information, the terminal determines that the network registration failure belongs to a recoverable network registration failure, wherein the first network state information is the network state information corresponding to the first cause value stored in the network registration failure white list. The network state information comprises at least one of the following: network type, public land mobile network (PLMN) information, public data network (PDN) connection establishment state, framework service state, current network cell information and geographical location information.

4. The method of claim 3, wherein, The maintenance of the service icon of the target network in the display of the user interface comprises the following steps:

5. The method according to any one of claims 1 to 4, characterized in that, The terminal intercepts the event of the failure of registration to the target network, so as to prevent the network registration state update notification from being sent to the user interface (UI) module, thereby maintaining the service icon of the target network in the display of the user interface. The method further comprises the following steps:

6. The method according to any one of claims 1 to 4, characterized in that, In the case that the terminal determines that the network registration failure does not belong to a recoverable network registration failure, the terminal sends a network registration state update notification to the UI module, wherein the network registration state update notification is used to indicate the failure of registration to the target network; The terminal controls the service icon of the target network not to be displayed in the user interface. The acquisition of the cause information of the network registration failure in the case that the terminal monitors the failure of registration to a target network comprises the following steps:

7. The method according to any one of claims 1 to 4, characterized in that, ​ In a case that the terminal registers to the target network through a wireless network, if disconnection from the wireless network is monitored, reason information of the disconnection from the wireless network is analyzed, and historical connection information of the wireless network is acquired; The determining, according to the reason information, whether the network registration failure belongs to a recoverable network registration failure comprises: The determining, according to the reason information and the historical connection information, whether the network registration failure belongs to a recoverable network registration failure.

8. The method according to any one of claims 1 to 4, characterized in that, The target network comprises an IP Multimedia Subsystem (IMS) network.

9. A network service icon display control apparatus applied to a terminal, characterized by comprising: The network service icon display control apparatus comprises: A first acquiring module, configured to acquire reason information of a network registration failure in a case that registration to a target network is monitored to fail; A determining module, configured to determine, according to the reason information, whether the network registration failure belongs to a recoverable network registration failure; A first control module, configured to maintain a service icon of the target network to be displayed on a user interface in a case that the network registration failure is determined to belong to a recoverable network registration failure.

10. The network service icon display control apparatus according to claim 9, wherein The first acquiring module is configured to acquire a network registration failure response message returned by a network side device; The determining module comprises: An extracting unit, configured to extract a failure reason value from the network registration failure response message; A matching unit, configured to match the failure reason value with a network registration failure white list, wherein the network registration failure white list stores a reason value list of recoverable network registration failures; A determining unit, configured to determine that the network registration failure belongs to a recoverable network registration failure in a case that the failure reason value is contained in the reason value list.

11. The network service icon display control apparatus according to claim 10, wherein The network registration failure white list further stores network state information corresponding to each reason value in the reason value list; The network service icon display control apparatus further comprises: A second acquiring module, configured to acquire network state information of the terminal; The matching unit is configured to match the failure reason value, the network state information of the terminal, and the network registration failure white list; The determining unit is configured to determine that the network registration failure belongs to a recoverable network registration failure in a case that the failure reason value matches a first reason value in the reason value list, and the network state information of the terminal matches first network state information, wherein the first network state information is network state information corresponding to the first reason value stored in the network registration failure white list.

12. The network service icon display control apparatus according to claim 11, wherein The network state information comprises at least one of the following: a network type, Public Land Mobile Network (PLMN) information, Public Data Network (PDN) connection establishment state, framework service state, current network camping cell information, and geographical position information.

13. The network service icon display control apparatus according to any one of claims 9 to 12, characterized in that, The first control module is configured to intercept an event of the registration to the target network failing, to prevent a network registration state update notification from being sent to a User Interface (UI) module, and to maintain the service icon of the target network to be displayed on the user interface.

14. A terminal, characterized by A computer-readable storage medium storing a program or instructions, which, when executed by a processor, implement the steps of the network service icon display control method according to any one of claims 1 to 8.

15. A readable storage medium, characterized by, A computer-readable storage medium storing a program or instructions, which, when executed by a processor, implement the steps of the network service icon display control method according to any one of claims 1 to 8.

Images