Call control method, terminal, computer program product and readable storage medium

Abstract

The application provides a call control method, a terminal, a computer program product and a readable storage medium, and relates to the technical field of terminals. When a call failure occurs in the process of performing a target type of call function, the terminal establishes an electronic fence for a cell in which the call failure has occurred under the condition that the establishment condition of the electronic fence is met, and the terminal monitors whether the electronic fence is entered. The terminal judges whether it is located in the electronic fence, and performs a first operation under the condition that it is located in the electronic fence. The first operation is used for controlling the terminal to not support the target type of call function in the electronic fence. The call control method provided in the application embodiment performs the first operation for the case that the cell accessed by the terminal is located in the electronic fence, so as to control the terminal to not support the target type of call function in the electronic fence. In this way, the call failure of the terminal in the cell can be prevented in advance, and the call experience of a user is improved.

Description

Technical Field

[0001] This application relates to the field of terminal technology, and in particular to a call control method, a terminal, a computer program product, and a readable storage medium. Background Technology

[0002] After a mobile phone connects to a cell network, it can make calls, such as voice or video calls, based on the cellular network. However, some cell networks may experience call problems, such as failed calls, failed incoming calls, dropped calls, and poor voice quality, affecting the user's call experience.

[0003] The existing call solution involves establishing a call after the mobile phone connects to the cell. If a call failure occurs, a self-healing action is executed. This self-healing action could include, for example, disabling call functionality during a call failure, to resolve the issue of call failures occurring within the current cell.

[0004] The phone performs a self-healing action after each call failure, resulting in poor call quality and affecting the user's call experience. Summary of the Invention

[0005] This application provides a call control method, a terminal, a computer program product, and a readable storage medium to solve the technical problem of poor mobile phone call quality affecting the call experience.

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

[0007] Firstly, a call control method is provided, which is applied to a terminal.

[0008] After a terminal connects to the first cell, if a call failure occurs during a call of the target type, the terminal establishes an electronic fence, which includes the first cell. After establishing the electronic fence, the terminal monitors whether it enters or exits the electronic fence.

[0009] When the terminal determines that it is within an electronic fence, it performs a first operation. This first operation controls the terminal to not support the target type of call function within the electronic fence.

[0010] In one example, the way a terminal determines whether it is within an electronic fence may include: when the terminal accesses a cell, it determines whether the cell it is accessing is within an electronic fence.

[0011] The first operation performed by the terminal may include disabling VoNR calling functionality, disabling SA networking functionality, and adding the first cell where the calling failure occurred to a blacklist. By disabling the target type of calling functionality or suppressing access to the cell, the terminal controls the electronic fence to prevent the target type of calling functionality from being supported.

[0012] In one example, after the terminal performs the first operation, the unsupported target type of call function may include VoNR call function. This allows for call control of the main call functions under common 5G network communication standards, improving the call experience.

[0013] The call control method provided in this application allows a terminal to perform a first operation when located within an electronic fence, controlling the terminal to not support the target type of call function within that electronic fence. This can proactively prevent call failures within the cell and improve the user's call experience.

[0014] In one possible implementation of the first aspect, a scheme for establishing an electronic fence by a terminal is provided.

[0015] If a call failure occurs during a call of the target type, the terminal determines whether the conditions for establishing an electronic fence are met. If the conditions are met, the terminal establishes the electronic fence.

[0016] The terminal experiences a call failure when accessing the first cell, and establishes an electronic fence when the establishment conditions are met.

[0017] In one example, the electronic fence may only include the first cell.

[0018] In another example, the geofence also includes a second cell; the second cell is a neighboring cell of the first cell, or a cell that the terminal registered with before accessing the first cell. The terminal determines that the geofence includes the first cell and its neighboring cells, thus enabling the terminal to begin preventing call failures before accessing the first cell, further improving the effectiveness of call failure prevention.

[0019] In one example, the electronic fence is associated with a cell, and the terminal stores the identifier of the cell within the electronic fence.

[0020] The specific implementation method for a terminal to establish an electronic fence can be that the terminal stores the identifiers of the cells within the electronic fence. The specific implementation method for a terminal to monitor whether it has entered the electronic fence is that the terminal monitors whether the cell it has accessed is within the electronic fence.

[0021] In other examples, the electronic fence can also draw a circle with a certain radius, centered on the first cell, to identify cells that overlap with the area within that circle. The terminal can store the identifiers of both the first cell and the cells that overlap with the area within the circle, as the cells associated with the electronic fence.

[0022] A terminal can use a registered cell change event as a trigger event to determine whether it has entered or exited the geofence. For example, when a terminal receives a registered cell change event, it triggers a detection process to determine whether it has entered or exited the geofence. If the identifier of the cell the terminal accesses is within the identifier set, it can be determined that the terminal has entered the geofence. Conversely, if the identifier of the cell the terminal accesses is not within the identifier set, it can be determined that the terminal has not entered the geofence. Furthermore, if the terminal is already within the geofence, and the identifier of a newly accessed cell is not within the identifier set, it can be determined that the terminal has exited the geofence.

[0023] In other embodiments, the electronic fence is associated with a geographic area, and the terminal stores the location data of that geographic area. For example, when a call fails, if the establishment conditions are met, the terminal can draw a circle with a certain radius centered on the real-time location where the call failed occurred, and the area within the circle can be used as the target area. The terminal stores the location data set of this target area.

[0024] In one example, the conditions for establishing an electronic fence may include at least one of the following:

[0025] Within a first time period, the first data point of the same type of call failure occurring in the same cell reaches a first threshold; the first data point includes the number of occurrences and / or the failure rate.

[0026] During the second time period, the second data on different types of call failures occurring within the same cell reaches the second threshold; the second data includes the number of occurrences and / or the failure rate.

[0027] The type of call failure that occurred belongs to a type set; the type set is pre-configured or pre-determined;

[0028] The time when the call failure occurred did not fall within the target time period; the target time period is the period during which the geofence is disabled.

[0029] Specifically, when the same type of call failure occurs within the same cell, "same cell" can refer to the first cell the terminal accesses when the call failure occurs, and "same type" can refer to the type of call failure currently occurring to the terminal. In other words, when the terminal experiences a first type of call failure in the first cell, the establishment conditions may include, within a first time period, the first data of a first type of call failure occurring within the first cell reaching a first threshold.

[0030] Specifically, this involves issuing different types of call faults within the same cell. When a terminal experiences a first type of call fault in the first cell, the establishment condition may include, within a first time period, a second threshold being reached for second data regarding the occurrence of both first and other types of call faults within the first cell. The second data may be the total number of first-type and other-type call faults, or the fault rate corresponding to the total number of faults.

[0031] In this example, the conditions for the terminal to establish an electronic fence are related to first data showing the occurrence of the same type of call failure within the same cell. This allows the terminal to promptly detect anomalies where a certain type of call failure occurs frequently within the same cell. Furthermore, the conditions for the terminal to establish an electronic fence are related to second data showing the occurrence of multiple types of call failures within the same cell. This allows the terminal to promptly detect anomalies where multiple types of call failures occur frequently within the same cell.

[0032] Specifically, the type of call failure that occurs belongs to a pre-defined set of call failure types. When a terminal experiences a first type of call failure, the terminal can determine whether this first type belongs to the set of types, or the terminal can also determine whether the types of other call failures that have occurred previously belong to the set of types.

[0033] In this example, the conditions for the terminal to establish an electronic fence are related to the type of call failure that occurs. This allows the terminal to promptly detect certain types of call failures occurring within the cell.

[0034] Specifically, the timing of the call failure must fall outside the target time period. When a call failure occurs, the terminal determines whether the establishment conditions are met. These conditions may refer to whether the time of the call failure falls outside the target time period.

[0035] In this example, the conditions for the terminal to establish an electronic fence are related to whether the time of the call failure falls within the target time period for disabling the electronic fence. In this way, the terminal can promptly establish an electronic fence for call failures occurring in other time periods that do not fall within the target time period, or in other words, the terminal can avoid establishing an electronic fence for the first cell again within the target time period.

[0036] The four conditions mentioned above can be used individually or in combination. Using multiple conditions in combination means that at least two of the above conditions are used together to determine whether the conditions for establishing an electronic fence are met. For example, all four conditions can be used as conditions for establishing an electronic fence.

[0037] When the terminal uses at least two of the above conditions together to determine whether the conditions for establishing an electronic fence are met, the terminal can determine that the conditions for establishing an electronic fence are met if both of the conditions involved in the judgment are satisfied. Furthermore, when the terminal performs the judgment action on at least two conditions, the order in which the two conditions are judged is not limited. For example, the terminal can judge whether the at least two conditions are satisfied sequentially, or the terminal can judge whether the at least two conditions are satisfied simultaneously.

[0038] One specific example is that when a terminal experiences a call failure, the cell the terminal is currently accessing is the first cell, and the type of call failure is the first type.

[0039] The terminal first determines whether the type of the current call failure belongs to a pre-defined set of call failure types. If the type of the current call failure belongs to that set, the terminal then determines whether the time of the current call failure belongs to the target time period.

[0040] If the current call failure does not occur within the target time period, the terminal further determines whether the first data on accumulated first-type call failures in the first cell has reached a first threshold. If the first data reaches the first threshold, the conditions for establishing an electronic fence are met, and the terminal can establish an electronic fence. If the first data does not reach the first threshold, the terminal then determines whether the first data has reached a second threshold. If the second data reaches the second threshold, the terminal establishes an electronic fence.

[0041] In one possible implementation of the first aspect, an assessment and control scheme is provided for the establishment of an electronic fence.

[0042] After establishing an electronic fence, the terminal determines whether the conditions for disabling the electronic fence are met. The conditions for disabling the electronic fence are related to certain situations that require its deactivation, such as poor call failure prevention or special time periods.

[0043] When the terminal determines that the deactivation conditions are met, it deactivates the geofence. Specifically, when the terminal deactivates the geofence, it may cease monitoring whether other terminals enter or exit the geofence, or, if the terminal enters the geofence, it may cease performing the first operation.

[0044] In addition, in some cases, after the electronic fence is deactivated, the terminal performs a second operation to restore the terminal's target type of call functionality.

[0045] In one example, the terminal may determine whether the deactivation conditions of the geofence are met by acquiring third data on call failures occurring within the geofence and determining whether the third data reaches a third threshold. The third data includes the number of calls and / or the failure rate.

[0046] If the third data reaches the third threshold, the terminal determines that the electronic fence deactivation conditions are met, and the terminal deactivates the electronic fence. If the third data does not reach the third threshold, the terminal determines that the electronic fence deactivation conditions are not met, and the terminal may choose not to deactivate the electronic fence.

[0047] The acquisition period for the third data can be the time period from when the terminal enters the electronic fence to when it exits the electronic fence, or it can be the time period during which the terminal is inside the electronic fence during multiple entries and exits.

[0048] When the conditions for disabling the electronic fence are met, the terminal can perform a second operation. This second operation controls the terminal's support for the target type of call functionality. For example, if the first operation is to disable VoNR call functionality, the second operation can be to enable VoNR call functionality. As another example, if the first operation is to disable SA networking functionality, the second operation can be to enable SA networking functionality. Yet another example, if the first operation is to add the first cell experiencing call failure to the blacklist, the second operation can be to remove the first cell from the blacklist.

[0049] The call control method provided in this application allows the terminal to disable the electronic fence after establishing it, provided that the disabling conditions are met. This allows the terminal to both prevent call failures by establishing the electronic fence and disable it when the fence's effectiveness in preventing call failures is poor, thus avoiding continuous restrictions on the terminal's call functionality.

[0050] In one possible implementation of the first aspect, a solution for handling terminal exiting the electronic fence is provided.

[0051] After the terminal is located within the electronic fence in the first cell and performs the first operation, if the terminal exits the electronic fence, it performs the second operation; the second operation is used to control the terminal to support the target type of call function within the electronic fence.

[0052] The call control method provided in this application involves a first operation performed by the terminal when entering an electronic fence, controlling the terminal to not support the target type of call function within the electronic fence. After exiting the electronic fence, the target type of call function continues to be supported. This approach prevents call failures within the electronic fence while ensuring a good call experience outside the electronic fence.

[0053] In one possible implementation of the first aspect, the possible implementation schemes for the first operation are further limited.

[0054] For example, the first operation includes at least one of the following: disabling VoNR call function, disabling SA networking function, and adding the first cell to the blacklist.

[0055] If the terminal disables VoNR calling, it cannot initiate a VoNR call. If the terminal disables SA networking, it also cannot initiate a VoNR call. If the terminal adds the first cell where a call failure has occurred to a blacklist, the terminal will suppress access to the first cell on that blacklist. The blacklist can be a list of unlisted cells.

[0056] In one example, for signaling plane faults, such as call failures including calling failure, called failure, or dropped calls, the first operation includes disabling VoNR call functionality and / or disabling SA networking functionality. For media plane faults, such as call failures involving voice calls, the first operation includes adding the first cell where the call failure occurred to a blacklist.

[0057] In this way, the terminal can implement corresponding call control schemes to prevent call failures for different types of call failures, thereby improving the terminal's call experience.

[0058] Secondly, this application provides a terminal, which includes a transceiver, a memory, and a processor, wherein the transceiver and the memory are both coupled to the processor;

[0059] The memory stores instructions that the computer executes;

[0060] The processor executes computer execution instructions stored in memory, causing the terminal to perform a call control method as described in any of the first aspects.

[0061] Thirdly, this application provides a computer-readable storage medium storing a computer program that, when run on a computer, causes the computer to perform the call control method as described in any of the first aspects.

[0062] Fourthly, this application provides a computer program product, including a computer program that, when executed by a processor, implements the call control method as described in any of the first aspects.

[0063] The technical effects of any of the design methods in the second to fourth aspects can be found in the technical effects of different design methods in the first aspect, and will not be repeated here. Attached Figure Description

[0064] Figure 1 A flowchart illustrating a call control method provided in an embodiment of this application;

[0065] Figure 2 This is a schematic diagram of a portion of the process involved in the call control method provided in the embodiments of this application;

[0066] Figure 3 A schematic diagram illustrating the inclusion relationship between an electronic fence and a residential community, provided in an embodiment of this application;

[0067] Figure 4 A schematic diagram illustrating an evaluation scheme for signaling plane faults involved in the call control method provided in this application embodiment;

[0068] Figure 5 A schematic diagram of an evaluation scheme for media plane faults involved in the call control method provided in the embodiments of this application;

[0069] Figure 6 A hardware and software architecture diagram of the terminal involved in the call control method provided in the embodiments of this application;

[0070] Figure 7 A timing diagram of the call control method provided in the embodiments of this application;

[0071] Figure 8 This is a hardware structure diagram of the terminal provided in an embodiment of this application. Detailed Implementation

[0072] The following description, in conjunction with the accompanying drawings, illustrates exemplary embodiments of this application, including various details to aid understanding. These embodiments should be considered merely exemplary. Therefore, those skilled in the art will recognize that various changes and modifications can be made to the embodiments described herein without departing from the scope of this application. Similarly, for clarity and brevity, descriptions of well-known functions and structures are omitted in the following description.

[0073] To facilitate understanding, some technical common sense involved in the embodiments of this application will be introduced first.

[0074] Mobile phone calls include subscriber identity module (SIM) card calls and internet calls. SIM card calls refer to a mobile phone establishing voice or video calls with other terminals through the cellular network provided by the operator corresponding to the SIM card. Internet calls refer to a mobile phone establishing voice or video calls with other terminals through internet protocols. This embodiment mainly relates to SIM card calls.

[0075] As mentioned above, SIM card calls are based on cellular networks, and different cellular networks correspond to different call types. For example, calls based on fourth-generation (4G) cellular networks are VoLTE (voice over long-term evolution) calls, while calls based on fifth-generation (5G) cellular networks are VoNR (voice over new radio) calls.

[0076] Take VoNR calls as an example. VoNR calls, also known as VONR calls, are calls made using the 5G new radio access (NR) network. A VoNR call means that the phone directly carries voice services through the 5G network, without falling back to the 4G network. The process of a phone making a VoNR call through a 5G network is as follows:

[0077] 1. The mobile phone connects to the network.

[0078] When a mobile phone detects a 5G NR cell (hereinafter referred to as the cell), it establishes a connection with the base station to which the cell belongs through a radio resource control (RRC) connection request.

[0079] The mobile phone registers with the 5G core network (CN) through the base station to complete identity authentication and network access.

[0080] Mobile phones establish Protocol Data Unit (PDU) sessions through base stations. PDU sessions can be used for data transmission and registration with the Internet Protocol Multimedia Subsystem (IMS).

[0081] The mobile phone uses a PDU session to register with the 5G core network for IMS via the Session Initiation Protocol (SIP).

[0082] During the registration process with the 5G core network, the mobile phone synchronizes its VoNR call support capability with the core network.

[0083] 2. The phone establishes a call.

[0084] A mobile phone establishes a call service based on user confirmation (voice control or touch control). The call service is a service where the mobile phone initiates a call to another terminal. The other terminal called by the mobile phone can be the called terminal. The mobile phone sends a call request to the core network via the SIP protocol, carrying media session parameters (such as codec information) and the identification information of the called terminal.

[0085] After receiving a call request from a mobile phone, the core network performs authentication, authorization, and billing processing, and sends a call notification to the called terminal. Once a call is established between the mobile phone and the called terminal, the core network creates a dedicated Quality of Service (QoS) flow for voice data, used to carry the voice data stream of Real-Time Transport Protocol (RTP). After the called terminal answers the call, it begins transmitting voice data.

[0086] 3. The phone maintains the call and releases.

[0087] During a call between a mobile phone and the called terminal, the SIP protocol is responsible for maintaining the session state, while the RTP protocol is responsible for the real-time transmission of voice data.

[0088] After the mobile phone ends the call with the called terminal, the mobile phone terminates the session via a SIP BYE message, and the network releases the relevant resources.

[0089] The calls mentioned in points 2 and 3 above are VoNR calls. When a mobile phone makes a VoNR call, it leverages the low latency and high bandwidth of the 5G cellular network to provide clearer voice calls and shorter call setup times. VoNR is the ultimate voice solution under the 5G Standalone (SA) architecture. Compared to VoLTE calls, VoNR calls operate entirely within the 5G cellular network and do not require falling back to the 4G cellular network, thus resulting in lower latency and higher voice quality.

[0090] As the foregoing analysis shows, a mobile phone needs to connect to a cell before it can make a call. After connecting to the cell and initiating a call, the phone may experience call failures due to factors such as poor cell signal quality or access anomalies. These failures may include caller failure, receiver failure, dropped calls, and poor voice quality. Current solutions for call failures involve temporarily disabling currently supported calling functions if a call failure occurs after initiating a call, to prevent further failures in that cell. However, this approach cannot prevent potential call failures in advance, resulting in a poor user experience.

[0091] Based on this, this application provides a call control method applied to a terminal. The terminal establishes an electronic fence for a first cell where a call failure occurs, specifically during a call of the target type. When the terminal is within the electronic fence, it performs a first operation to control the terminal to not support the target type of call function within that electronic fence. This allows for proactive prevention of call failures within the cell, improving the user's call experience.

[0092] The terminal involved in the embodiments of this application can be an electronic device that supports SIM card calling function, such as a mobile phone. In some other cases, personal computers (PCs), tablet computers, laptops, portable computers (such as mobile phones), wearable terminals (such as smartwatches), augmented reality (AR) / virtual reality (VR) devices, in-vehicle computers, and other devices that support SIM card calling function can also execute the call control method provided in the embodiments of this application, without limitation.

[0093] See Figure 1 This is a flowchart illustrating a call control method provided in an embodiment of this application. The execution of the call control method by the terminal can be divided into three main parts: S1 the terminal establishes an electronic fence, S2 the terminal uses the electronic fence, and S3 the terminal deactivates the electronic fence. These three main parts will be described in detail below.

[0094] S1. The terminal establishes an electronic fence.

[0095] The terminal determines whether the conditions for establishing an electronic fence are met. If the conditions are met, the terminal establishes the electronic fence.

[0096] There can be various triggering conditions for the terminal to perform the above-mentioned judgment action. For example, the terminal can perform the judgment action when it accesses a certain cell and a call failure occurs. Alternatively, the terminal can perform the judgment action after each power-on. Of course, the terminal can also perform the judgment action in response to other triggering conditions, and this embodiment of the application does not impose specific limitations on this.

[0097] In some embodiments, the triggering condition for the terminal to perform a judgment action is that the terminal accesses a certain cell and a call failure occurs. For example... Figure 1 As shown in (1), the above S1 may include the following steps: S101-S102.

[0098] S101: When a call failure occurs during a call of the target type, the terminal determines whether the conditions for establishing an electronic fence are met.

[0099] Terminal call failures include failures that occur when the terminal establishes a call and failures that occur during the call. Terminal call failures can lead to abnormal call termination or poor audio quality. Types of call failures can include: calling failure, called party failure, dropped calls, and poor voice quality. Poor voice quality can also be referred to as a call voice failure, which can include voice problems such as silence or intermittent sound.

[0100] In some embodiments, call failures can be categorized into signaling plane (or control plane) failures and media plane failures, depending on the cause. Signaling plane failures may include primary failures, called party failures, and dropped calls. Media plane failures may include voice call failures. Signaling plane failures may be related to the call functions or network standards supported by the terminal. Media plane failures may be related to the cell the terminal is accessing.

[0101] The terminal includes functional modules that perform different services, such as a fault detection module that detects call failures. When a call failure occurs, the terminal's fault detection module reports the fault information. This fault information can indicate the type of call failure, among other things. Different types of call failures will result in different fault information reported by the fault detection module.

[0102] It should be understood that the fault perception module reporting fault information in the embodiments of this application can refer to the terminal's fault perception module reporting fault information to the terminal's processor or call application. In other words, the call control method in the embodiments of this application is mainly executed by the internal functional modules of the terminal, such as the call application, processor, and fault perception module. For ease of understanding, the embodiments of this application mainly use the terminal as the execution subject to explain the possible implementation schemes of the embodiments of this application.

[0103] The call control method provided in this embodiment mainly targets one or more specific types of call functions for call control. For ease of description, the applicable call type is referred to as the target type. Specifically, the target type can be VoNR call, LTE call, etc. VoNR call function is a widely used call function. This embodiment mainly uses the target type call function as an example of VoNR call function, but it is not intended to limit other possible implementation methods.

[0104] Specifically, if a terminal experiences a call failure during a call of the target type, it will determine whether the current call failure meets the conditions for establishing an electronic fence. These conditions are used to determine whether to establish an electronic fence.

[0105] In some cases, the terminal can immediately perform the above-mentioned judgment action when a call failure occurs. In other cases, the terminal can also perform the above-mentioned judgment action when the current call that caused the failure ends or terminates.

[0106] For example, if a call fails due to a dropped call, a failed caller, or a failed call recipient, the call usually ends immediately upon the occurrence of the failure, and the time of the failure and the call's end are very close or even the same. In this case, the terminal can perform a judgment action immediately upon the occurrence of the failure. As another example, if a call experiences a voice call failure, the call may not end immediately upon the failure; the terminal can perform a judgment action after the call has ended.

[0107] An electronic fence is a security system built using electronic technology, primarily used to monitor and restrict the entry or exit of terminals from a specific area. Electronic fences are mainly divided into physical electronic fences and virtual electronic fences. A physical electronic fence refers to an electronic fence composed of a physical host, a detection fence, and a controller. A virtual electronic fence is a virtual boundary built based on positioning technology or wireless signal technology. The electronic fence involved in this application embodiment is a virtual electronic fence.

[0108] In this embodiment, establishing an electronic fence by the terminal means that the terminal determines a designated area and forms an electronic fence. Entering the designated area constitutes entering the electronic fence. Leaving the designated area constitutes leaving the electronic fence.

[0109] In one example, the terminal can designate one or more adjacent cells as a specified area, forming an electronic fence.

[0110] In another example, the terminal can also delineate a certain geographical area as a designated area to form an electronic fence.

[0111] In the two examples above, the terminal can obtain the specified area in several ways. For example, the terminal can use a cell it has accessed or a geographical area it has been located in as the specified area. Alternatively, the terminal can respond to user input and use the cell or geographical area indicated by the user's input as the specified area.

[0112] In this embodiment of the application, there are multiple ways for the terminal to obtain the establishment conditions.

[0113] In one example, the terminal can obtain the establishment conditions in real time from the server or other devices when a call failure occurs.

[0114] In this case, the establishment conditions described above can be applicable to multiple terminals. Alternatively, the establishment conditions described above can also be establishment conditions that are matched to the terminal based on some call settings of the terminal.

[0115] In another example, the terminal can pre-store setup conditions. When a call failure occurs, the terminal can directly use these pre-stored setup conditions to perform a judgment action.

[0116] For example, the terminal obtains the setup conditions from the server or core network in advance and stores them in local memory.

[0117] For example, a terminal can also respond to user input, determine the establishment conditions that match the terminal, and store them in local memory, without limitation.

[0118] In some embodiments, the above establishment conditions may include one or more of the following conditions:

[0119] Condition 1: Within the first time period, the first data of the same type of call failure occurring in the same cell by the terminal reaches the first threshold; where condition 1 can be called the individual counting fence generation threshold.

[0120] Condition 2: During the second time period, the second data of multiple types of call failures occurring in the same cell by the terminal reaches the second threshold; where condition 2 can be called the hybrid counting fence generation threshold.

[0121] Condition 3: The type of call failure occurring at the terminal belongs to the type set; the type set is pre-configured or pre-determined.

[0122] Condition 4: The time when the terminal experiences a call failure does not fall within the target time period.

[0123] Regarding condition 1 above.

[0124] The first time period can include the moment the call failure occurs and the preceding time period, and the duration of this first time period is denoted as the first duration. The first duration can be a fixed value, such as 1 hour or 48 hours. The first duration can be a preset duration agreed upon by the communication protocol, or a custom duration determined by the terminal in response to user operation; there are no limitations.

[0125] A call failure occurring within a cell can refer to a call failure that occurs while the terminal is accessing that cell and maintaining that access. Alternatively, a call failure occurring within a cell can also refer to a call established by the terminal in another cell, where the terminal switches to that cell during a call hold and maintains access to that cell.

[0126] The type of call failure that occurs in a cell can refer to the type of call failure indicated by the fault information obtained by the terminal, or it can refer to the type of call failure automatically detected by the terminal.

[0127] There are several ways for a terminal to obtain the type of call failure that has occurred in a cell.

[0128] In one example, the terminal obtains fault information reported by the fault perception module, and the fault information directly indicates the type of call fault.

[0129] For example, fault information can directly indicate the type of call fault currently occurring, such as calling failure, called failure, dropped call, or call voice fault.

[0130] In another example, the terminal obtains fault information reported by the fault perception module. The fault information includes the cause value of the call failure, and there is a mapping relationship between the cause value and the type of call failure.

[0131] For example, the fault information may include cause values ​​such as 400323, 40038, or other cause values. Among them, 40023 corresponds to a call drop failure caused by a packet data network (PDN) disconnection, and 40038 corresponds to a call drop failure caused by a real-time transport protocol (RTP) timeout.

[0132] In this embodiment, when a terminal experiences a call failure, the cell it accesses is designated as the first cell, and the current call type is designated as the target call type. That is, after accessing the first cell, the terminal experiences a call failure while conducting a call of the target type. The first cell can be any cell. Furthermore, the type of the currently occurring call failure is designated as the first type, which can be any type of call failure.

[0133] In this embodiment, a conditional association is established for call faults of the same type. This same type of call fault can be any type of call fault occurring within any cell, or it can be a call fault currently occurring at the terminal.

[0134] For example, when a terminal experiences a first type of call failure in the first cell, the condition 1 used by the terminal can be specifically whether the first data of the first type of call failure occurring in the first cell within the first time period reaches a first threshold.

[0135] The first data can be the number of occurrences and / or the failure rate. The corresponding first threshold can be a number of occurrences threshold and / or a failure rate threshold.

[0136] Taking the number of times as the first data point as an example, if the terminal accumulates a certain number of first-type call failures within the first cell, then condition 1 above is satisfied.

[0137] For example, let's set the first threshold to 3 times, with the first type being call failure. If, at the first moment, a terminal experiences a call failure of this type in the first cell, and within the first time period prior to that moment (i.e., the first time interval), the terminal makes 20 calls, of which 10 are call failures, and 3 of these failures are call failures. Therefore, the terminal has experienced 3 call failures of this type in the first cell, reaching the threshold and satisfying condition 1 above.

[0138] Furthermore, let's take the first data point as an example of the failure rate. If the cumulative failure rate of the terminal experiencing first-type call failures within the first cell reaches the failure rate threshold, then condition 1 above is satisfied.

[0139] For example, the first threshold is set to 20%. Continuing with the example above, the failure rate of the terminal experiencing call failures (calling failures) in the first cell is 15%, which does not reach the failure rate threshold and does not meet the above establishment conditions.

[0140] Taking the first data point as an example, if the terminal accumulates a certain number of first-type call failures within the first cell, reaching the number threshold, and the failure rate reaches the failure rate threshold, then condition 1 above is satisfied.

[0141] For example, the threshold for the number of calls to fail is set to 3, and the failure rate threshold is set to 20%. Continuing with the example above, the terminal experienced 3 call failures (calling failures) within the first cell, reaching the number of failures threshold. The failure rate for these call failures is 15%, which does not reach the failure rate threshold. Based on this, the terminal determines that condition 1 is not met.

[0142] The call control method provided in this embodiment establishes an electronic fence based on first data indicating that the same type of call fault occurs within the same cell. This allows the terminal to promptly detect abnormal situations where a certain type of call fault occurs frequently within the same cell.

[0143] Regarding condition 2 above, the explanation for condition 2 is similar to that of condition 1, except that it establishes a condition association for various types of call failures.

[0144] In this embodiment, conditions are established to associate multiple types of call faults occurring within the same cell. Continuing with the previous example, the type of call fault currently occurring at the terminal is the first type, and this call fault occurred at the terminal in the first cell. Therefore, the multiple types of call faults can include the first type of call fault and the second type of call fault. The second type of call fault can be one or more other types of call faults different from the first type. For example, the first type and the second type can be at least two different types of call faults, including calling failure, called failure, dropped call, and voice call failure.

[0145] The explanation for the second time period can refer to the explanation for the first time period mentioned above, and will not be repeated here. It should be understood that the second time period and the first time period are only used to distinguish the instructions, and the duration of these two time periods can be the same or different, without limitation.

[0146] The second data for multiple types of call failures can refer to the sum of data for multiple types of call failures. The second data may include the number of failures and / or the failure rate, and the corresponding second threshold may be a number of failures threshold and / or a failure rate threshold.

[0147] Taking the second data point as an example, the second data point, which refers to the number of times a terminal experiences multiple types of call failures within the same cell, can refer to the total number of times the terminal experiences two or more types of call failures within the cell. When the number of times a terminal experiences multiple types of call failures within the same cell reaches a threshold, condition 2 is satisfied.

[0148] For example, let's set the second threshold to 5 times, with the first type being call failure. If, at a second moment, the terminal experiences a call failure of this type in the first cell, and within the second time period preceding that moment (i.e., the second time slot), the terminal makes 20 calls, of which 10 experience call failures. Three of these failures are call failures, and two are dropped calls. Therefore, the total number of call failures (call failures and dropped calls) occurring within the first cell is 5, reaching the threshold and satisfying condition 2 above.

[0149] In the call control method provided in this embodiment, the conditions for the terminal to establish an electronic fence are related to second data showing multiple types of call failures occurring within the same cell. This allows the terminal to promptly detect abnormal situations where multiple types of call failures frequently occur within the same cell.

[0150] Regarding condition 3 above.

[0151] As described above, there are various types of call failures that can occur at a terminal. Some of these failures may be related to the current network conditions, some to the network quality of the cell, and some to the call modes currently supported by the terminal. In this embodiment, the electronic device categorizes a subset of all types of call failures into a type set. This type set may include call failures such as calling failure, called party failure, dropped calls, and voice call failures.

[0152] In some cases, the type set can be pre-configured. For example, the core network pre-configures the type set to the terminals.

[0153] In other cases, this set of types can be predetermined. For example, in response to user input, the terminal obtains the types of some call faults and determines them as a set of types. The terminal stores this set of types.

[0154] When a call failure occurs, the terminal determines whether the type of the current call failure belongs to the set of call failure types. If the type of the current call failure belongs to the set of call failure types, the terminal determines that the conditions for establishing an electronic fence are met.

[0155] In the call control method provided in this embodiment, the conditions for the terminal to establish an electronic fence are related to the type of call fault currently occurring. This allows the terminal to promptly detect certain types of call faults occurring within the cell.

[0156] Regarding condition 4 above.

[0157] The target time period may correspond to various situations where geofences need to be disabled. For example, the target time period may be late at night when call frequency is low, or daytime when call frequency is high, or a period when historical data indicates that geofences need to be disabled, etc., without limitation.

[0158] When a terminal experiences a call failure, if the time of the call failure does not fall within the target time period, the conditions for establishing an electronic fence are determined to be met.

[0159] In the call control method provided in this embodiment, the conditions for the terminal to establish an electronic fence are related to whether the time of the call failure falls within a target time period. Thus, the terminal can establish an electronic fence for call failures occurring in other time periods that do not fall within the target time period, or in other words, the terminal can avoid establishing an electronic fence for call failures occurring within the target time period.

[0160] Conditions 1 through 4 above can be used individually or in combination. Using conditions 1 through 4 in combination means that at least two of conditions 1 through 4 are used together to determine whether the conditions for establishing an electronic fence are met. For example, all of conditions 1 through 4 can be used as conditions for establishing an electronic fence.

[0161] When the terminal uses at least two of the conditions 1 to 4 above together to determine whether the conditions for establishing an electronic fence are met, the terminal can determine that the conditions for establishing an electronic fence are met if both of the conditions involved in the determination are satisfied. Furthermore, when the terminal performs the determination action for at least two conditions, the order in which the two conditions are determined is not limited. For example, the terminal can determine whether the at least two conditions are satisfied sequentially, or the terminal can determine whether the at least two conditions are satisfied simultaneously.

[0162] Taking all four conditions above as conditions for establishing an electronic fence as an example. Figure 2 The diagram shown is a partial flowchart of the call control method provided in this application embodiment. Figure 2 As shown, when a call failure occurs, the terminal is currently connected to the first cell, and the type of call failure is the first type.

[0163] The terminal first determines whether the type of the current call failure belongs to a pre-defined set of call failure types. If the type of the current call failure belongs to that set, the terminal then determines whether the time of the current call failure belongs to the target time period.

[0164] If the current call failure does not occur within the target time period, the terminal then determines whether the threshold for generating a separate counting fence is met, i.e., condition 1. Specifically, the terminal acquires the first data on the cumulative occurrence of the first type of call failure in the first cell and determines whether the first data reaches the first threshold. If the first data reaches the first threshold, the conditions for establishing an electronic fence are met, and the terminal can establish the electronic fence.

[0165] If the threshold for generating a single-count fence is not met, the terminal then determines whether the threshold for generating a mixed-count fence is met, i.e., condition 2. Specifically, the terminal acquires the second data and determines whether the second data reaches the second threshold. If the second data reaches the second threshold, the terminal establishes an electronic fence. After establishing the electronic fence, the terminal can immediately execute the first operation. The terminal will also execute the first operation when subsequently entering the electronic fence.

[0166] Figure 2 In the cases shown, if the type of call failure that occurs does not belong to the predetermined set of call failure types, or if the time when the call failure occurs belongs to the target time period, or if the terminal does not meet the mixed counting fence generation threshold, it is determined that the conditions for establishing an electronic fence are not met.

[0167] S102: The terminal establishes an electronic fence if the conditions for establishing the electronic fence are met.

[0168] Once the conditions for establishing an electronic fence are met, the terminal delineates a target area, including the cell where the call failure occurred, thus forming an electronic fence. The implementation of the terminal delineating the target area to form an electronic fence includes: the terminal storing relevant data about the target area, which is used to indicate the boundary data of the electronic fence.

[0169] In some embodiments, the electronic fence is associated with a cell, and the terminal stores the identifier of the cell within the electronic fence.

[0170] In this embodiment, when a terminal experiences a call failure, if the aforementioned establishment conditions are met, the terminal establishes an electronic fence for the cell accessed when the call failure occurred. That is, the electronic fence includes the first cell where the call failure occurred. Specifically, the terminal can establish the electronic fence by storing the identifiers of the cells within the electronic fence. The terminal can monitor whether it has entered the electronic fence by detecting whether the cell it accessed is within the electronic fence.

[0171] In one example, the electronic fence only includes the first cell where the call failure occurred.

[0172] like Figure 3 The diagram shown illustrates the inclusion relationship between the target area defined by the electronic fence and the residential community provided in this embodiment of the application. Figure 3 As shown in (1), the electronic fence S1 includes the first cell C1.

[0173] In another example, the electronic fence includes a first cell and a second cell; the second cell is a neighboring cell of the first cell, or the second cell is a cell that the terminal registered before accessing the first cell.

[0174] like Figure 3 As shown in (2), the second cell is a neighboring cell of the first cell. The neighboring cell and the first cell can be geographically adjacent or partially overlap. The electronic fence S2 includes the first cell C1, and the second cells C2 and C3.

[0175] like Figure 3 As shown in (3), the second cell is a cell that was registered before accessing the first cell. The electronic fence S3 includes the first cell C1, and the second cells C2 and C4.

[0176] In other examples, the electronic fence can also draw a circle with a certain radius, centered on the first cell, to identify cells that overlap with the area within that circle. The terminal can store the identifiers of both the first cell and the cells that overlap with the area within the circle, as the cells associated with the electronic fence.

[0177] It should be understood that after a terminal establishes an electronic fence, it can monitor whether the terminal is within the electronic fence. If a specific action is set to be automatically triggered when a terminal enters or leaves the electronic fence, then after the electronic fence is established, if a terminal is detected entering or leaving the electronic fence, the terminal will automatically execute that specific action. If no specific action is set to be automatically triggered when entering or leaving the electronic fence, then the event of entering or leaving the electronic fence will be automatically reported when a terminal is detected entering or leaving the electronic fence.

[0178] The terminal can determine whether it has entered or exited the geofence by identifying whether the identifier of the cell it is accessing is within the identifier set. In this case, the terminal can use the registered cell change event as the trigger event for determining whether it has entered or exited the geofence.

[0179] For example, when a terminal receives a registered cell change event, it triggers a detection function to check whether the terminal has entered or exited the geofence. If the identifier of the cell the terminal accesses is within the identifier set, it can be determined that the terminal has entered the geofence. Conversely, if the identifier of the cell the terminal accesses is not within the identifier set, it can be determined that the terminal has not entered the geofence. Furthermore, if the terminal is already within the geofence, but the identifier of a newly accessed cell is not within the identifier set, it can be determined that the terminal has exited the geofence.

[0180] In other embodiments, the electronic fence is associated with a geographic area, and the terminal stores the location data of the geographic area.

[0181] For example, when a call fails, if the conditions for call establishment are met, the terminal can draw a circle with a certain length as the radius, centered on the real-time location where the call failure occurred, and take the area inside the circle as the target area. The terminal stores the location data set of the target area.

[0182] The terminal can determine whether it has entered or exited the geofence by monitoring whether its real-time location data is within the location data set. In this case, the terminal can use the location update event as the trigger event to detect whether it has entered or exited the geofence.

[0183] For example, when a terminal receives a location update event, it triggers a determination to see if the terminal has entered or exited the geofence. If the terminal's real-time location data is included in the location data set, then the terminal has entered the geofence. Conversely, if the terminal's real-time location data is not included in the coordinate set, then the terminal has not entered the geofence. And if, even when the terminal is already within the geofence, the updated real-time coordinate data is not included in the coordinate set, then the terminal has exited the geofence.

[0184] In some embodiments, when a terminal performs a judgment action upon accessing a cell and experiencing a call failure, the terminal determines that the conditions for establishing an electronic fence are met and establishes the electronic fence. The terminal may use this electronic fence only for subsequent call control, and the terminal may not perform a self-healing action for this call failure. Alternatively, the terminal may perform a self-healing action for this call failure.

[0185] The self-healing actions performed by the terminal may include: turning off the VoNR calling function or the standalone (SA) networking function when the terminal is within the electronic fence, or adding the cell where the calling failure has occurred to the blacklist, etc., without limitation.

[0186] S2, The terminal uses an electronic fence.

[0187] After establishing an electronic fence, the terminal can determine whether it has entered or exited the electronic fence. The triggering events for the terminal to determine whether to enter the electronic fence can be various, such as the registered community change event, location update event, and power-on event mentioned in the previous embodiments, and are not limited to any specific event.

[0188] like Figure 1 As shown in (2), after the terminal establishes the electronic fence, the above S2 may include the following steps: S103-S105.

[0189] S103: The terminal determines whether it is within the electronic fence.

[0190] Depending on the different ways of establishing the aforementioned electronic fence, there are multiple ways for a terminal to determine whether it is located within the electronic fence.

[0191] In some examples, the terminal stores the identifiers of cells within the geofence, and the terminal can use a registered cell change event as a trigger event. When the terminal connects to a new cell, it is denoted as the third cell. The third cell can be any cell that the terminal connects to.

[0192] Terminal access to a third cell can refer to the terminal reselecting or switching from other cells to a third cell, or it can refer to the terminal changing from a state of never being connected to a cell to accessing a third cell.

[0193] When a terminal accesses a third cell, it can determine whether the third cell is located within an electronic fence by determining whether the identifier of the third cell is within the identifier set.

[0194] It should be understood that the first cell and the third cell involved in the embodiments of this application are only used to distinguish cells in different situations. In actual call control, the first cell and the third cell may be the same cell or different cells, without limitation.

[0195] S104: When the terminal is located within the electronic fence, it performs the first operation.

[0196] In this embodiment, for an electronic fence established when a call failure occurs during a call of the target type and the establishment conditions are met, a specific action that is automatically triggered when the terminal enters the electronic fence is defined as executing the first operation. That is, the terminal executes the first operation when the third cell it accesses is located within the electronic fence. The terminal can execute the first operation immediately upon determining that the first cell is within the electronic fence, or the terminal can wait for a period of time after determining that the first cell is within the electronic fence and then automatically execute the first operation.

[0197] The first operation is used to control the terminal to not support the target type of call function within the electronic fence. After the terminal executes the first operation, it will not support the target type of call function within the electronic fence.

[0198] For example, if a terminal experiences a call failure while using VoNR calling, the target type of calling function can be VoNR calling. As another example, if a terminal experiences a call failure while using VoLTE calling, the target type of calling function can be VoLTE calling. This embodiment primarily focuses on the case where the target type of calling function is VoNR calling, but it is not intended to limit other possible implementations.

[0199] In some embodiments, the first operation may include at least one of the following:

[0200] Turn off VoNR calling function;

[0201] Disable SA networking function;

[0202] Cells that have experienced call failures will be added to the blacklist.

[0203] Specifically, if the VoNR calling function is turned off, the terminal will be unable to use the VoNR calling function.

[0204] VoNR (Voice over NR) calling is a common calling function in 5G networks. Normally, when a terminal accesses a 5G cell, it supports VoNR calling and can initiate a VoNR call. In this embodiment, if the terminal accesses a cell located within an electronic fence, the terminal disables VoNR calling, preventing it from initiating a VoNR call while connected to the first cell. This avoids potential call failures that might result from initiating a VoNR call.

[0205] When VoNR calling functionality is disabled on the terminal, the terminal can initiate EPS Fallback (evolved packet system fallback). EPS Fallback is a voice call solution for 5G networks, used to fall back the terminal from the 5G network to the 4G network and initiate VoLTE calls when the 5G NR network does not support VoNR calling functionality.

[0206] When the SA networking function is disabled, the terminal cannot use the SA networking function, nor can it use the calling function under the SA networking, such as the VoNR calling function.

[0207] SA networking, also known as 5G standalone networking, refers to a networking method entirely based on the 5G New Radio (NR) network and the 5G core network (5GC). Typically, terminals in SA networking mode support VoNR calls. In this embodiment, if the first cell accessed by the terminal is located within an electronic fence, the terminal disables SA networking, thus preventing it from initiating VoNR calls. This avoids potential call failures that might result from initiating VoNR calls.

[0208] In this scenario, while the terminal cannot support 5G-based calling, it can support calling functions compatible with other network standards. For example, the terminal can initiate a VoLTE call when the current calling network is 4G, without limitation.

[0209] The terminal adds the first cell where a call failure has occurred to the blacklist, so the terminal cannot access cells on the blacklist.

[0210] It should be understood that the cell within the electronic fence can be the cell where a call failure occurred, that is, the cell that the terminal accessed when the call failure triggered the establishment of the electronic fence. For example, if a call failure occurs when the terminal accesses the first cell, and an electronic fence is established when the establishment conditions are met, then the first operation performed by the terminal after entering the electronic fence is to add the first cell to the blacklist.

[0211] The terminal adding the first cell to the blacklist can be implemented by adding the identifier of the first cell to the blacklist. The blacklist used by the terminal can be implemented in various ways, such as a blacklist of cells or a set of identifiers for cells whose access is suppressed; there is no limitation on this. The operation of adding the first cell to the blacklist can also be called a blacklist operation.

[0212] In this way, after the terminal enters the electronic fence, it can access other cells within the electronic fence except for the first cell. The terminal can suppress access to the first cell where a call failure has occurred, which can minimize the possibility of call failures that may be caused by initiating a VoNR call.

[0213] In some embodiments, the terminal establishes an electronic fence based on different call failures. Therefore, the first operation triggered by the terminal for entering different electronic fences can also be different.

[0214] In some examples, when a call failure occurs (caller failure, called party failure, or dropped call), and the terminal determines that the establishment conditions are met and establishes a first electronic fence, the first operation associated with this first electronic fence may include disabling VoNR calling functionality and / or disabling SA networking functionality. When the terminal subsequently enters this first electronic fence, the first operation performed is to disable VoNR calling functionality and / or disable SA networking functionality.

[0215] This can effectively reduce call failures that may be caused by the call functions or network standards supported by the terminal.

[0216] In other examples, if the terminal determines that the conditions for establishing an electronic fence are met when the call failure is a voice failure, it establishes a second electronic fence. The first operation associated with this second electronic fence may include adding the first cell where the call failure occurred to a blacklist. When the terminal subsequently enters the second electronic fence, the first operation performed is to add the first cell within that second electronic fence to the blacklist.

[0217] This can reduce call failures that may be caused by the cell accessed by the terminal.

[0218] In some embodiments, when the terminal executes S102, after the terminal accesses the first cell and experiences a call failure, it establishes an electronic fence and can immediately begin performing a self-healing action. This self-healing action can be the first operation involved in this embodiment. Subsequently, the terminal will also perform this first operation each time it enters the electronic fence.

[0219] In some embodiments, when the terminal executes S102, after the terminal accesses the first cell and a call failure occurs, it establishes an electronic fence and may not perform a self-healing action for this call failure. Subsequently, the terminal will perform the first operation each time it enters the electronic fence.

[0220] S105: The terminal performs a second operation when it exits the electronic fence.

[0221] The second operation is used to control the terminal to support the call function of the target type.

[0222] In this embodiment, the second operation performed by the terminal is the opposite of the first operation, and can be understood as the reverse operation of the first operation. When exiting the geofence, the terminal performs the second operation, removing the restriction that the terminal does not support call functions for the target type.

[0223] For example, the first operation is to disable VoNR calling / SA networking. Correspondingly, the second operation can be to enable VoNR calling / SA networking on the terminal. As another example, if the first operation is to add the first cell to the blacklist, the corresponding second operation could be to remove the first cell from the blacklist.

[0224] The call control method provided in this embodiment involves the terminal performing a first operation when entering an electronic fence to control the terminal to not support the target type of call function within the electronic fence. After exiting the electronic fence, the target type of call function continues to be supported. This achieves both call failure prevention within the electronic fence and ensures a good call experience outside the electronic fence. For signaling plane faults, the terminal disables VoNR call function and / or disables SA networking function. For media plane faults, the first operation performed by the terminal may include adding cells where call failures have occurred to a blacklist. Thus, the terminal implements corresponding call control schemes to prevent call failures for different types of call failures, improving the terminal's call experience.

[0225] S3, Terminal disables electronic fence.

[0226] After establishing an electronic fence, the terminal can evaluate the effectiveness of the electronic fence in preventing call failures and determine whether it is necessary to disable the electronic fence based on the effect.

[0227] In some embodiments, such as Figure 1 As shown in (3), after the terminal establishes the electronic fence, it can also perform the following steps S106-S107.

[0228] S106: The terminal determines whether the conditions for disabling the electronic fence are met.

[0229] The deactivation conditions for electronic fences are used to allow terminals to deactivate electronic fences under certain circumstances. These circumstances may include: the terminal experiencing frequent call failures within the electronic fence area; the terminal operating during specific time periods such as late at night; or the terminal deactivating the electronic fence in response to a user's action.

[0230] The terminal performs an operation to determine whether the conditions for disabling the electronic fence are met. There can be multiple triggering conditions. For example, the terminal enters the electronic fence, the terminal is powered on, the terminal experiences a call failure, or the terminal receives a user instruction to make a judgment, etc., without limitation.

[0231] Taking the trigger condition of a terminal entering a geofence as an example: After establishing a geofence, the terminal can determine whether the geofence's deactivation conditions are met each time it enters the geofence. If the terminal enters the geofence and meets the deactivation conditions, the geofence is deactivated. After the terminal deactivates the geofence, it will no longer check whether to enter the geofence again, or it will not perform the first operation after entering the geofence.

[0232] If a terminal enters a geofence but does not meet the geofence's deactivation conditions, it continuously checks whether the deactivation conditions are met until they are met, or until the terminal exits the geofence. The terminal will then begin checking whether the deactivation conditions are met again the next time it enters the geofence.

[0233] In some embodiments, the terminal acquires third data regarding call failures occurring within the geofence. This third data includes the number of failures and / or the failure rate.

[0234] Specifically, the terminal acquires data on call failures occurring within the electronic fence, which is denoted as the third data. The specific meaning of the third data can be referenced in the preceding embodiments regarding the first and second data, and is not limited thereto.

[0235] Taking the third data as an example, the third data for call failures occurring within a geofence could be the cumulative number of call failures that occurred when the terminal entered the geofence once and did not leave. Alternatively, the third data could also be the cumulative number of call failures that occurred when the terminal was within the geofence multiple times.

[0236] The fewer call failures a terminal experiences within the geofence, the better the geofence's effectiveness in preventing call failures. Conversely, the more call failures a terminal experiences after the geofence is established, the worse the geofence's effectiveness in preventing call failures.

[0237] The terminal has a pre-set third threshold, which serves as the critical value for determining whether to disable the electronic fence. After establishing the electronic fence, if the third data of a call failure occurring within the electronic fence reaches the third threshold, the electronic fence will be disabled.

[0238] In one example, the third data is the failure rate of call failures that occur cumulatively when the terminal is within an electronic fence multiple times, and the third threshold is the failure rate threshold.

[0239] For example, let's set the third threshold to 15%. After the terminal establishes an electronic fence, it makes 5 calls within the fence for the first time, with 0 calls failing. On the second entry into the fence, it makes 10 calls, with 2 failing. On the third entry, it makes 5 calls, with 1 failing. The third data point, i.e., the failure rate, is (1+2) / (5+10+5) = 15%, reaching the third threshold. The terminal can then disable the electronic fence.

[0240] In some embodiments, the terminal may also limit the time period for acquiring third data.

[0241] The time period for acquiring third-party data can be a specific period after the terminal establishes an electronic fence, such as 24 hours or 72 hours. During this specific period after the electronic fence is established, the terminal acquires third-party data to evaluate the effectiveness of preventing call failures within the electronic fence.

[0242] S107: The terminal disables the electronic fence if the conditions for disabling the electronic fence are met.

[0243] The electronic fence established by the terminal is used to prevent call disruptions that may occur within the electronic fence area. The terminal deactivates the electronic fence if it assesses, based on third-party data, that the preventative effect of the electronic fence may be poor.

[0244] Specifically, disabling the geofence on the terminal can mean that the terminal stops monitoring the process of entering or leaving the geofence, or that the terminal stops performing the first operation after entering the geofence. When the terminal disables the geofence, if the first operation has already been performed, i.e., the terminal currently does not support the target type of call function, the terminal can also perform a second operation to restore the target type of call function.

[0245] In other embodiments, when the terminal disables the electronic fence, it can also set a target time period during which the terminal does not establish a new electronic fence for any cell, or in other words, the terminal does not establish an electronic fence for any cell within the electronic fence.

[0246] If a call failure occurs during the target time period, the steps shown in S101-S102 will not be executed; and if the terminal accesses a new cell, the steps in S103-S105 will not be executed.

[0247] If a call failure occurs after the target time period ends, the terminal can continue to execute S101-S102; if the terminal connects to a new cell, it can continue to execute S103-S105.

[0248] The call control method provided in this embodiment involves the terminal calculating third data based on call failures occurring within the electronic fence after establishing it, and then determining whether to disable the electronic fence based on the third data. In this way, the terminal can both prevent call failures by establishing the electronic fence and disable it when the electronic fence's effectiveness in preventing call failures is poor, thus avoiding continuous restrictions on the terminal's call functionality.

[0249] In some embodiments, the terminal executes S106 and S107 to evaluate the preventive effect of the electronic fence on call failures. Different implementation schemes can be used for signaling plane failures and media plane failures.

[0250] In one example, the terminal targets signaling plane faults, and the third data is the failure rate of signaling plane faults occurring within the electronic fence.

[0251] like Figure 4 The diagram illustrates an evaluation scheme for signaling plane faults involved in the call control method provided in this application embodiment. The terminal notifies relevant modules to evaluate the effectiveness of the electronic fence in preventing call faults. If a call fails, it determines whether the current call fault is a signaling plane fault. If a signaling plane fault occurs, the call count is incremented by 1, and the count of call faults is also incremented by 1. The ratio of the updated count of call faults to the total number of calls is used as the third data. If no signaling plane fault occurs in the current call, only the call count is incremented by 1; the count of call faults is not updated. The sum of the count of call faults and the updated count of calls is used as the third data.

[0252] For example, the third threshold is 20%. The terminal establishes an electronic fence and disables VoNR calling or SA networking. The terminal enters the electronic fence for the first time after establishing the fence and initiates its first call (a called party call). If the called party call is successfully established, the call count is incremented by 1, and the third data is 0, continuing the evaluation. If the terminal does not exit the electronic fence or re-enters the electronic fence after exiting, and initiates a second call (a called party call), and the called party call is successfully established, the call count is incremented again by 1, and the third data is 0. Assuming the terminal continues to initiate a third and fourth call, both of which are successfully established, the call count accumulates to 4, the third data is 0, and the third threshold is not reached. If the terminal initiates a fifth call and the call fails, the call count accumulates to 5, and the third data reaches 20%, thus meeting the third threshold.

[0253] For example, the statistical period for the third data is the time from when the terminal enters the geofence to when it exits. If the terminal exits the geofence after its first entry but before the third data reaches the third threshold, the terminal does not disable the geofence. Instead, the terminal performs a second operation: enabling VoNR calling or SA networking. The terminal also stops updating the third data and call count; in other words, it resets the third data and call count to zero.

[0254] When the terminal re-enters the geofence, it performs the first operation: disabling VoNR calling or SA networking. Furthermore, the terminal starts counting the number of calls and call failures within the geofence from zero. For example, if the terminal initiates its first call after entering the geofence and the call fails, the call count is incremented by 1. The third statistic, the failure rate, becomes 100%, exceeding the third threshold of 20%, and the terminal deactivates the geofence.

[0255] In another example, for media plane failures, the third data is the failure rate corresponding to the cumulative duration of abnormal voice calls that occur within the geofence.

[0256] like Figure 5 The diagram shown illustrates an evaluation scheme for media plane faults involved in the call control method provided in this application embodiment. The terminal notifies relevant modules to evaluate the effectiveness of the electronic fence in preventing call faults. Each time a call is initiated, the terminal determines whether a media plane fault has occurred in the current call. This embodiment takes a call voice fault as an example of a media plane fault.

[0257] In some embodiments, the terminal can evaluate the effectiveness of media plane fault prevention for a single call. For a call, if no voice fault occurs, the terminal only needs to record the total cumulative call duration. If a voice fault occurs, the terminal records the abnormal voice fault duration and the total cumulative call duration, and calculates third data based on these two data points. If the third data for this call does not reach the third threshold, the geofence is not deactivated. That is, for the first call, if the third data does not reach the third threshold, the terminal can reset the third data to zero.

[0258] The terminal continues to monitor whether the third data for the next call meets the third threshold. For the next call, the terminal recalculates the cumulative duration of abnormal voice calls and the total cumulative call duration to calculate new third data.

[0259] In some embodiments, the terminal can comprehensively evaluate the prevention effectiveness of media plane faults across multiple calls. Regarding media plane faults, without exiting the geofence, the terminal can either accumulate and correlate third-party data from multiple calls, or update the third-party data after each call.

[0260] If the terminal exits the geofence after each call, it can clear the current third data. The terminal will then start calculating the third data again after re-entering the geofence and initiating a call.

[0261] Specifically, for media-side faults, the terminal calculates the ratio of the cumulative duration of abnormal voice calls that occur within the electronic fence to the total cumulative call duration, which is used as third data.

[0262] For example, this call lasted 100 minutes, from 10:00 to 11:40. The call started at 10:00 with no voice quality issues reported, and call duration was recorded. At 10:30, a voice quality issue was reported, and the duration of the issue was recorded. At 10:35, the issue ended, with a cumulative abnormal voice duration of 5 minutes. At 10:40, another voice quality issue was reported, and the duration of that issue was recorded again. At 11:20, the issue ended, and the cumulative abnormal voice duration was updated to 45 minutes. Therefore, the cumulative abnormal voice duration is 45 minutes, and the total call duration is 100 minutes. The third metric, 45% > 20%, reaches the invalidation threshold, and the electronic fence is disabled on the terminal.

[0263] It should be noted that the assessment scheme for media-side failures can also refer to the aforementioned conditions for establishing electronic fences. For example, the terminal can determine whether the fence's self-healing is effective or ineffective based on whether the number of failures occurring within a certain time period reaches a threshold, and disable the electronic fence when the threshold is reached.

[0264] It should be noted that S1, S2, and S3 above refer to the stages of establishing, using, and deactivating an electronic fence by the terminal, respectively, but are not limited to the terminal executing S2 or S3 only after executing S1. For example, the terminal can establish electronic fences for different cells, and can perform different operations for different electronic fences. For example, the terminal executes S2 for the first electronic fence corresponding to the first cell, and can also execute S3 for the second electronic fence corresponding to the second cell, and can also execute S1 for the third cell. The embodiments of this application mainly use the establishment, use, and deactivation process of an electronic fence as an example, but are not intended to limit other possible implementations.

[0265] The above mainly explains various possible embodiments of the call control method provided in this example from the perspective of the terminal. The following will explain the specific implementation process of the display control method from the perspective of the terminal's internal software architecture.

[0266] like Figure 6 The diagram shown illustrates the internal hardware and software architecture of the terminal. The following section will explain in detail the process of the terminal executing call control methods, based on its internal architecture.

[0267] Specifically, the terminal's internal architecture can be divided into four layers, from top to bottom: the application layer (APP), the framework layer (FWK), the hardware abstraction layer (HAL), and the chip layer (or driver layer). It should be noted that in addition to these main functional layers, other functional modules may also be included, without limitation. Furthermore, these functional layers may also have other names, without limitation.

[0268] The application layer can include a series of application packages, mainly divided into system applications and third-party applications, such as the call application involved in this embodiment. The call application can include a fence control module and an evaluation module. The fence control module is used to perform fence-related control operations such as determining whether the conditions for establishing an electronic fence are met, whether to enter or exit the electronic fence, and whether to deactivate the electronic fence. The evaluation module is used to evaluate the effectiveness of the electronic fence in preventing call failures.

[0269] In addition, the application layer can also include applications such as camera, calendar, map, navigation, music, and video.

[0270] The framework layer provides application programming interfaces (APIs) and programming frameworks for applications in the application layer. The application framework layer includes some predefined functions.

[0271] The framework layer includes a self-healing execution module, which is used to control the execution of the first operation or the execution of the second operation.

[0272] In addition, the framework layer may also include common services such as Windows Management System (WMS), Activity Manager Service (AMS), View Service, and Call Service, which will not be elaborated further.

[0273] The Hardware Abstraction Layer (HAL) can encapsulate the underlying drivers and provide interfaces for calls to the framework layer and local service layer, shielding the implementation details of the underlying hardware. In this embodiment, the HAL may include a call HAL. The call HAL includes call-related interface call modules used to implement interface calls between the framework layer and the underlying chip.

[0274] The chip layer includes a fault detection module, which detects potential call failures. This module can then upload detected call failures to the application layer's fence control module or evaluation module via the call HAL interface.

[0275] Understandable Figure 6 The layers in the illustrated software structure and the components contained in each layer do not constitute a specific limitation on the terminal. In other embodiments of this application, the terminal may include more or fewer layers than illustrated, and each layer may include more or fewer components; this application does not impose any limitations.

[0276] Furthermore, it is understood that the terminal, in order to implement the call control method in this embodiment, includes hardware and / or software modules that perform the respective functions. Based on the algorithm steps of the various examples described in the embodiments disclosed herein, this application can be implemented in hardware or a combination of hardware and computer software. Whether a function is executed in hardware or by computer software driving hardware depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application in conjunction with the embodiments, but such implementation should not be considered beyond the scope of this application.

[0277] like Figure 7 The diagram shown is a timing diagram of the call control method provided in an embodiment of this application. Figure 6 and Figure 7 As shown, the terminal's call control methods mainly include:

[0278] S701: The fault perception module reports a call failure to the fence control module.

[0279] When a terminal initiates a calling or receiving call, the fault detection module monitors whether a call failure has occurred. If a call failure occurs, the module reports the call failure to the fence control module.

[0280] S702: The fence control module determines whether the conditions for establishing an electronic fence are met.

[0281] The fence control module receives a call fault report from the fault detection module and determines whether the conditions for establishing an electronic fence are met. The implementation scheme for the fence control module to determine whether the conditions for establishing an electronic fence are met can be found in the aforementioned S101 and... Figure 2 The specific implementation method shown is not limited.

[0282] S703: The fence control module notifies the self-healing execution module to execute the first operation.

[0283] S704: The self-healing execution module notifies the fence control module that the first operation has been completed.

[0284] When the conditions for establishing an electronic fence are met, the fence control module notifies the self-healing execution module to perform a first operation, such as disabling the VoNR calling function or disabling the SA networking function. For details, please refer to the relevant implementation method in S104 above, which will not be elaborated further.

[0285] S705: The fence control module notifies the evaluation module to obtain third-party data.

[0286] S706: The evaluation module monitors whether the third data has reached the third threshold.

[0287] S707: The evaluation module notifies the fence control module that the third data has reached the third threshold.

[0288] The fence control module notifies the evaluation module to assess the preventative effectiveness of the electronic fence. The evaluation module can obtain call faults reported by the fault detection module, as well as the total number of calls or the total cumulative call duration reported by other call function modules, and calculate third-party data.

[0289] The evaluation module continuously acquires and updates the third data and monitors whether the third data reaches the third threshold. Reaching the third threshold indicates that the electronic fence is ineffective in preventing call failures. The evaluation module notifies the fence control module of the result that the third data has reached the third threshold. Alternatively, the evaluation module can also notify the fence control module of the effectiveness of call failure prevention, or it can directly instruct the fence control module to deactivate the electronic fence.

[0290] The scheme for the evaluation module to monitor whether the third data has reached the third threshold can be found in the specific implementation schemes of S106 and S107 mentioned above, and will not be elaborated here.

[0291] It should be noted that the third data may not reach the third threshold even after the terminal exits the geofence. In this case, after the terminal exits the geofence, the geofence control module can notify the evaluation module to stop calculating the third data, and the evaluation module will reset the calculated third data to zero.

[0292] S708, Fence Control Module: Disable Electronic Fence.

[0293] When the evaluation module receives a notification that the third data point has reached the third threshold, the fence control module deactivates the electronic fence. This way, the fence control module no longer needs to monitor whether a terminal enters or exits the electronic fence.

[0294] S709: The fence control module notifies the self-healing execution module to execute the second operation.

[0295] S710: The self-healing execution module notifies the fence control module that the second operation has been completed.

[0296] After the fence control module deactivates the electronic fence, it notifies the self-healing execution module to perform a second operation, removing the restriction that the terminal does not support the call function of the target type.

[0297] S711, The fence control module suppresses the generation of electronic fences during the target time period.

[0298] Based on the evaluation results from the assessment module, the fence control module determined that the electronic fence was ineffective in preventing call disruptions. To prevent the electronic fence from being generated again within a short period, the fence control module set a target time period to suppress the generation of electronic fences during that period.

[0299] During the above process, after establishing the electronic fence, the fence control module will continuously monitor whether the terminal enters or exits the electronic fence.

[0300] S712, Fence Control Module monitors and exits the electronic fence.

[0301] S713, The fence control module notifies the self-healing execution module to execute the second operation.

[0302] S714, The self-healing execution module notifies the fence control module that the second operation has been completed.

[0303] After establishing an electronic fence, the fence control module detects that the terminal has exited the electronic fence and then notifies the self-healing execution module to perform the second operation.

[0304] S715: The fence control module detects entry into the electronic fence and returns to execute S705 and subsequent associated steps.

[0305] If the fence control module detects that the terminal re-enters the electronic fence, it returns to execute S705, notifying the evaluation module to assess the effectiveness of the electronic fence in preventing call failures, and notifying the fence control module to deactivate the electronic fence when the third data reaches the third threshold. For details, please refer to the implementation schemes of S705-S711 mentioned above, which will not be elaborated further.

[0306] In addition, embodiments of this application also provide a terminal, including a transceiver, a memory, and a processor, wherein the transceiver and the memory are both coupled to the processor;

[0307] The memory stores instructions that the computer executes;

[0308] The processor executes computer execution instructions stored in the memory, causing the terminal to perform the display control method provided in the above embodiments. In addition to these main components, the terminal also includes components for implementing basic functions, which will be discussed below. Figure 8 Please provide a detailed explanation.

[0309] like Figure 8 The diagram shown is a structural schematic of a terminal 800 provided in an embodiment of this application. The terminal 800 may include a processor 810, a memory 820, a display 830, a SIM card module 840, antenna 1, antenna 2, a mobile communication module 850, a wireless communication module 860, an audio module 870, a speaker 870A, a receiver 870B, a microphone 870C, a headphone jack 870D, a sensor module 880, etc. The sensor module 880 may include a gyroscope sensor 880A, a proximity sensor 880B, etc.

[0310] The structure illustrated in this embodiment of the invention does not constitute a limitation on terminal 800. It 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 both.

[0311] Processor 810 may include one or more processing units. For example, processor 810 may include an application processor (AP), a modem processor, a graphics processing unit (GPU), an image signal processor (ISP), a controller, memory, a video codec, a digital signal processor (DSP), a baseband processor, and / or a neural network processing unit (NPU). Different processing units may be independent devices or integrated into one or more processors.

[0312] The aforementioned controller acts as the decision-maker, directing the various components of the terminal 800 to coordinate their operations according to instructions. It serves as the nerve center and command hub of the terminal 800. Based on the instruction opcode and timing signals, the controller generates operation control signals to control the fetching and execution of instructions.

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

[0314] In some embodiments, the processor 810 may include interfaces. These interfaces may include inter-integrated circuit (I2C) interfaces, inter-integrated circuit sound (I2S) interfaces, pulse code modulation (PCM) interfaces, universal asynchronous receiver / transmitter (UART) interfaces, mobile industry processor interfaces (MIPI), general-purpose input / output (GPIO) interfaces, SIM interfaces, and / or USB interfaces, etc.

[0315] The interface connection relationships between the modules illustrated in this embodiment of the invention are merely illustrative and do not constitute a structural limitation on the terminal 800. The terminal 800 may employ different interface connection methods or a combination of multiple interface connection methods as described in this embodiment of the invention.

[0316] The wireless communication function of terminal 800 can be implemented through antenna 1, antenna 2, mobile communication module 850, wireless communication module 860, modem, and baseband processor. That is, antenna 1, antenna 2, mobile communication module 850, wireless communication module 860, modem, and baseband processor can function as the aforementioned transceivers. For example, it can initiate calls to other terminals via a 5G cellular network or receive calls initiated by other terminals to this terminal.

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

[0318] The mobile communication module 850 can provide a communication processing module for wireless communication solutions, including 2G / 3G / 4G / 5G, applied to the terminal 800.

[0319] The wireless communication module 860 can provide a communication processing module for wireless communication solutions applied to the terminal 800, 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), infrared (IR) technology, and other wireless communication solutions.

[0320] In some embodiments, antenna 1 of terminal 800 is coupled to mobile communication module 850, and antenna 2 is coupled to wireless communication module 860, enabling terminal 800 to communicate with networks and other devices via wireless communication technology.

[0321] Terminal 800 implements display functions through a GPU, display 830, and application processor. The GPU is a microprocessor for image processing, connected to the display 830 and the application processor. The GPU is used to perform mathematical and geometric calculations and for graphics rendering. Processor 810 may include one or more GPUs, which execute program instructions to generate or modify display information.

[0322] Display 830 is used to display images, videos, etc. In some embodiments, terminal 800 may include one or N displays 830, where N is a positive integer greater than 1.

[0323] The memory 820 may include an external memory interface and internal memory. The external memory interface can be used to connect an external memory card, such as a Micro SD card, to expand the storage capacity of the terminal 800. The internal memory can be used to store executable program code, including instructions. The processor 810 executes various functional applications and data processing of the terminal 800 by running the instructions stored in the internal memory. The terminal 800 can implement audio functions, such as music playback and recording, through an audio module 870, speaker 870A, receiver 870B, microphone 870C, headphone jack 870D, and application processor.

[0324] The audio module 870 is used to convert digital audio information into analog audio signal output, and also to convert analog audio input into digital audio signal. The audio module 870 can also be used for encoding and decoding audio signals. In some embodiments, the audio module 870 may be located in the processor 810, or some functional modules of the audio module 870 may be located in the processor 810.

[0325] The SIM card module 840 is used to implement the communication function of the SIM card. The SIM card module 840 may include a SIM card interface, SIM card circuitry, and related auxiliary components. The SIM card can be inserted into or removed from the SIM card interface to make contact with and separate from the terminal 800. The terminal 800 can support one or N SIM card interfaces, where N is a positive integer greater than 1. The SIM card module 840 can support Nano SIM cards, Micro SIM cards, and other SIM cards. Multiple cards can be inserted into the same SIM card interface simultaneously. The multiple cards can be of the same or different types. The SIM card interface can also be compatible with different types of SIM cards. The SIM card interface can also be compatible with external memory cards. The terminal 800 interacts with the network through the SIM card to realize functions such as voice calls and data communication. In some embodiments, the terminal 800 uses an eSIM, i.e., an embedded SIM card. The eSIM card can be embedded in the terminal 800 and cannot be separated from the terminal 800.

[0326] The SIM card module 840 can cooperate with the processor 810, the mobile communication module 850, the wireless communication module 860, as well as the antenna 1 and the antenna 2 to perform operations such as calling, processing, and sending and receiving in the call control method provided in this embodiment.

[0327] The call control methods described in the foregoing embodiments can all be implemented in the terminal 800 having the aforementioned hardware structure.

[0328] Based on the above embodiments, this application also provides a call control device, which includes a processor for executing the call control method provided in the above embodiments.

[0329] This application also provides a computer-readable storage medium storing a computer program that, when run on a computer, causes the computer to execute the call control method provided in the above embodiments.

[0330] This application also provides a computer program product containing instructions that, when run on a computer, enable the computer to execute the call control method provided in the above embodiments.

[0331] The specific implementation methods and technical effects of the terminal, call control device, computer-readable storage medium, and computer program product containing instructions provided in this application can be found in the specific implementation process and technical effects of the call control method provided in the foregoing embodiments, which will not be repeated here.

[0332] In some embodiments, as described above, those skilled in the art will clearly understand that, for the sake of convenience and brevity, the division of the functional modules described above is merely an example. In practical applications, the functions described above 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. The specific working process of the system, device, and unit described above can be referred to the corresponding process in the foregoing method embodiments, and will not be repeated here.

[0333] In the embodiments of this application, the functional units 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.

[0334] 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 computer-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 computer software product is stored in a storage medium and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, 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 flash memory, portable hard disk, read-only memory, random access memory, magnetic disk, or optical disk.

[0335] The above description is merely a specific implementation of the embodiments of this application, but the protection scope of the embodiments of this application is not limited thereto. Any changes or substitutions within the technical scope disclosed in the embodiments of this application should be covered within the protection scope of the embodiments of this application. Therefore, the protection scope of the embodiments of this application should be determined by the protection scope of the claims.

Claims

1. A call control method, characterized in that, Applied to a terminal, the call control method includes: Determine whether the terminal is located within an electronic fence; the electronic fence includes a first cell where a call failure has occurred, the call failure occurring during the terminal's target type of call function; When the terminal is located within the electronic fence, a first operation is performed; the first operation is used to control the terminal to not support the target type of call function within the electronic fence.

2. The call control method according to claim 1, characterized in that, The call control method further includes: If a call failure occurs during the terminal's call function for the target type, determine whether the conditions for establishing the electronic fence are met. The electronic fence is established if the conditions for establishing the electronic fence are met.

3. The call control method according to claim 2, characterized in that, The establishment conditions include at least one of the following: Within a first time period, the first data point of the same type of call failure occurring in the same cell reaches a first threshold; the first data point includes the number of times and / or the failure rate. During the second time period, a second threshold is reached for the second data on different types of call failures occurring within the same cell; the second data includes the number of occurrences and / or the failure rate. The types of call failures that occurred belong to a set of types; The set of types is pre-configured or predetermined; The call failure occurred outside the target time period; The target time period is the period during which the electronic fence is disabled.

4. The call control method according to claim 2 or 3, characterized in that, After establishing the electronic fence, the call control method further includes: Determine whether the conditions for disabling the electronic fence are met; The electronic fence shall be deactivated when the deactivation conditions are met.

5. The call control method according to claim 4, characterized in that, The determination of whether the conditions for disabling the electronic fence are met includes: Acquire third data on the occurrence of the call failure within the electronic fence; the third data includes the number of times and / or the failure rate; Determine whether the third data reaches the third threshold; Specifically, if the third data reaches the third threshold, the deactivation condition is determined to be met; if the third data does not reach the third threshold, the deactivation condition is determined not to be met.

6. The call control method according to claim 4 or 5, characterized in that, If the terminal performed the first operation before disabling the electronic fence, then after disabling the electronic fence, the method further includes: The terminal performs a second operation, which controls the terminal to support the call function of the target type.

7. The call control method according to any one of claims 1 to 6, characterized in that, After performing the first operation when the terminal is located within the electronic fence, the call control method further includes: Upon exiting the electronic fence, a second operation is performed; the second operation is used to control the terminal to support the call function of the target type.

8. The call control method according to any one of claims 1 to 7, characterized in that, The electronic fence also includes a second cell; the second cell is a neighboring cell of the first cell, or the second cell is a cell that the terminal registered before accessing the first cell.

9. The call control method according to any one of claims 1 to 8, characterized in that, The first operation includes at least one of the following: Turn off VoNR calling function; Disable SA networking function; The first cell that experienced a call failure will be added to the blacklist.

10. The call control method according to claim 9, characterized in that, In the event of a call failure (caller failure, called party failure, or dropped call), the first operation includes disabling the VoNR call function and / or disabling the SA networking function. In the case of a call failure being a voice failure, the first operation includes adding the first cell that experienced the call failure to the blacklist.

11. The call control method according to any one of claims 1 to 10, characterized in that, The target type of call function includes VoNR call function.

12. The call control method according to any one of claims 1 to 11, characterized in that, The step of determining whether the terminal is located within the electronic fence includes: When the terminal accesses a cell, it determines whether the cell is located within the electronic fence.

13. A terminal, characterized in that, The terminal includes a transceiver, a memory, and a processor, wherein the transceiver and the memory are both coupled to the processor; The memory stores computer-executed instructions; The processor executes computer execution instructions stored in the memory, causing the terminal to perform the call control method as described in any one of claims 1 to 12.

14. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores a computer program that, when run on a computer, causes the computer to perform the call control method as described in any one of claims 1 to 12.

15. A computer program product, characterized in that, It includes a computer program, which, when executed by a processor, implements the call control method as described in any one of claims 1 to 12.

Images