Eps fallback processing method, apparatus, device, and storage medium

Abstract

The application provides an EPS fallback processing method and device, equipment and a storage medium, and relates to the technical field of communication. The method comprises the following steps: acquiring EPS fallback data when the EPS fallback success rate meets a preset condition, wherein the EPS fallback data comprises at least one of the following: user session data, network element capacity and network element configuration parameters; performing clustering analysis on the EPS fallback data to obtain a first failure factor of EPS fallback failure, wherein the clustering dimension of the clustering analysis comprises at least one of the following: user dimension, terminal type dimension, base station cell dimension or network element dimension; and obtaining a failure cause of EPS fallback failure according to the first failure factor of EPS fallback failure. In this way, targeted optimization can be performed according to the failure cause, so that the 5G user voice EPS fallback success rate is improved.

Description

Technical Field

[0001] This application relates to the field of communication technology, and in particular to an EPS fallback processing method, apparatus, device and storage medium. Background Technology

[0002] In the early stages of 5G network deployment, coverage progressed from hotspots to wider coverage, and then to even wider coverage. When a terminal moves from a 5G network coverage area to an area without 5G network coverage, such as an area covered by 4G network, the terminal can use the Evolved Packet System (EPS) fallback mechanism to switch from 5G to 4G for voice services. EPS fallback can include handover-based EPS fallback and redirection-based EPS fallback.

[0003] In some implementations, the success rate of EPS fallback can be improved by configuring accurate parameters on the radio side (also known as the base station). For example, in the handover-based EPS fallback process, the accuracy of the 4G neighbor cell parameters configured in the 5G base station can be ensured, thereby improving the fallback success rate; in the redirection-based EPS fallback, the accuracy of the 4G frequency point parameters configured in the 5G base station can be ensured, thereby improving the fallback success rate.

[0004] However, the methods described above for improving the success rate of EPS fallback by configuring accurate parameters can only solve some scenarios where EPS fallback fails. Therefore, the success rate of EPS fallback is still relatively low. Summary of the Invention

[0005] This application provides an EPS fallback processing method, apparatus, device, and storage medium to solve the problem of low success rate of existing EPS fallback methods.

[0006] In a first aspect, this application provides an EPS fallback processing method, comprising: when the EPS fallback success rate meets a preset condition, acquiring EPS fallback data, wherein the EPS fallback data includes at least one of the following: user session data, network element capacity, and network element configuration parameters;

[0007] Cluster analysis is performed based on EPS decline data to identify the first failure factor for EPS decline failure. The clustering dimensions of the cluster analysis include at least one of the following: user dimension, terminal type dimension, base station cell dimension, or network element dimension.

[0008] Based on the primary failure factor of EPS decline failure, the reasons for EPS decline failure are derived.

[0009] In one possible implementation, cluster analysis is performed based on EPS decline data to identify the primary failure factors for EPS decline failure, including:

[0010] Based on EPS fallback data, at least one of the following is obtained for the clustering dimension of clustering analysis: target users with more than one preset value of EPS fallback failures, target terminal types with more than one preset value of EPS fallback failures, target base station cells with more than one preset value of EPS fallback failures, and target network elements with more than one preset value of EPS fallback failures.

[0011] At least one of the following should be considered as the first failure factor for EPS fallback failure: target user, target terminal type, target base station cell, and target network element.

[0012] In one possible implementation, after obtaining the EPS decline data, the method further includes:

[0013] Obtain network handover success rate and tracking area update success rate;

[0014] When the network handover success rate is lower than the fifth preset value or the tracking area update success rate is lower than the sixth preset value, the second failure factor of EPS fallback failure is obtained based on the signaling in the EPS fallback data.

[0015] Based on the primary failure factor of EPS decline failure, the reasons for EPS decline failure are as follows:

[0016] Based on the first and second failure factors of EPS decline failure, the reasons for EPS decline failure are obtained.

[0017] In one possible implementation, based on the signaling in the EPS fallback data, the second failure factor for EPS fallback failure is obtained, including:

[0018] Determine whether there are process conflict signaling and / or switch cancellation signaling in the EPS fallback process based on EPS fallback data;

[0019] If there is a process conflict signaling and / or a handover cancellation signaling, the second failure factor is determined to be the base station cell or the terminal.

[0020] In one possible implementation, if the network handover success rate is lower than the fifth preset value, the method also includes:

[0021] Based on EPS drop-off data, obtain the number of successful responses, the number of failed responses, and the number of timeouts of the mobile management entity network element during the network handover process;

[0022] Based on the number of successful responses, the number of failed responses, and the number of timeouts, the third failure factor for EPS fallback failure is identified as the mobile management entity network element and the base station cell.

[0023] Based on the first and second failure factors of EPS decline failure, the reasons for EPS decline failure are as follows:

[0024] Based on the first, second, and third failure factors of EPS decline failure, the reasons for EPS decline failure are obtained.

[0025] In one possible implementation, based on the number of successful responses, the number of failed responses, and the number of timeouts, the third failure factor for EPS fallback failure is determined to be the mobility management entity network element and the base station cell, including:

[0026] The total number of responses is determined based on the number of successful responses, the number of failed responses, and the number of response timeouts.

[0027] Obtain the percentage of response failures and response timeouts in the total number of responses;

[0028] If the total percentage is greater than the seventh preset value, then the third failure factor for EPS decline failure is the mobile management entity network element and the base station cell.

[0029] In one possible implementation, when the EPS pullback success rate meets a preset condition, EPS pullback data is acquired, including:

[0030] The EPS fallback success rate is determined based on the number of successful EPS fallback processes and the number of EPS fallback process requests.

[0031] When the EPS decline success rate is lower than the eighth preset value, obtain EPS decline data.

[0032] Secondly, this application provides an EPS fallback processing device, which includes an acquisition module, an analysis module, and a determination module, wherein...

[0033] The acquisition module is used to acquire EPS fallback data when the EPS fallback success rate meets preset conditions. The EPS fallback data includes at least one of the following: user session data, network element capacity, and network element configuration parameters.

[0034] The analysis module is used to perform cluster analysis based on EPS fallback data to obtain the first failure factor of EPS fallback failure. The clustering dimensions of the cluster analysis include at least one of the following: user dimension, terminal type dimension, base station cell dimension, or network element dimension.

[0035] The determination module is used to determine the cause of EPS fallback failure based on the first failure factor.

[0036] In one possible implementation, the analysis module is specifically used for:

[0037] Based on EPS fallback data, at least one of the following is obtained for the clustering dimension of clustering analysis: target users with more than one preset value of EPS fallback failures, target terminal types with more than one preset value of EPS fallback failures, target base station cells with more than one preset value of EPS fallback failures, and target network elements with more than one preset value of EPS fallback failures.

[0038] At least one of the following should be considered as the first failure factor for EPS fallback failure: target user, target terminal type, target base station cell, and target network element.

[0039] In one possible implementation, after acquiring the EPS dropout data, the device further includes:

[0040] The first acquisition module is used to acquire network handover success rate and tracking area update success rate;

[0041] The first determination module is used to determine the second failure factor of EPS fallback failure based on the signaling in the EPS fallback data when the network handover success rate is lower than the fifth preset value or the tracking area update success rate is lower than the sixth preset value.

[0042] The module is specifically used to determine the reasons for EPS decline failure based on the first and second failure factors.

[0043] In one possible implementation, the first determining module is specifically used for:

[0044] Determine whether there are process conflict signaling and / or switch cancellation signaling in the EPS fallback process based on EPS fallback data;

[0045] If there is a process conflict signaling and / or a handover cancellation signaling, the second failure factor is determined to be the base station cell or the terminal.

[0046] In one possible implementation, if the network handover success rate is lower than a fifth preset value, the device further includes:

[0047] The second acquisition module is used to acquire the number of successful responses, the number of failed responses, and the number of timeouts of the mobility management entity network element during the network handover process, based on the EPS fallback data.

[0048] The second determining module is used to determine the third failure factor for EPS fallback failure based on the number of successful responses, the number of failed responses, and the number of timeouts. The factors are the mobility management entity network element and the base station cell.

[0049] The module is specifically used to determine the reasons for EPS decline failure based on the first, second, and third failure factors.

[0050] In one possible implementation, the second determining module is specifically used for:

[0051] The total number of responses is determined based on the number of successful responses, the number of failed responses, and the number of response timeouts.

[0052] Obtain the percentage of response failures and response timeouts in the total number of responses;

[0053] If the total percentage is greater than the seventh preset value, then the third failure factor for EPS decline failure is the mobile management entity network element and the base station cell.

[0054] In one possible implementation, the acquisition module is specifically used for:

[0055] The EPS fallback success rate is determined based on the number of successful EPS fallback processes and the number of EPS fallback process requests.

[0056] When the EPS decline success rate is lower than the eighth preset value, obtain EPS decline data.

[0057] Thirdly, this application provides an electronic device, including: a processor and a memory; the memory stores computer-executable instructions; the processor executes the computer-executable instructions stored in the memory, causing the terminal device to perform the EPS fallback processing method as described in the first aspect or any possible implementation of the first aspect.

[0058] Fourthly, this application provides a computer-readable storage medium storing computer-executable instructions that, when executed by a processor, are used to implement the EPS fallback processing method as described in the first aspect or any possible implementation thereof.

[0059] Fifthly, this application provides a computer program product, including a computer program that, when executed by a processor, can perform the EPS fallback processing method as described in the first aspect or any possible implementation of the first aspect.

[0060] In this application, when the EPS fallback success rate meets preset conditions, EPS fallback data is acquired. The EPS fallback data includes at least one of the following: user session data, network element capacity, and network element configuration parameters. Cluster analysis is performed on the EPS fallback data to determine the first failure factor for EPS fallback failure. The clustering dimensions of the cluster analysis include at least one of the following: user dimension, terminal type dimension, base station cell dimension, or network element dimension. Based on the first failure factor, the failure reason for EPS fallback failure is determined. This multi-dimensional cluster analysis of EPS fallback data identifies the first failure factor, and then the failure reason for various EPS fallback failure scenarios is determined based on the first failure factor. This allows for targeted optimization based on the failure reasons for various failure scenarios, thereby achieving the goal of improving the 5G user voice EPS fallback success rate and enhancing user experience. Attached Figure Description

[0061] To more clearly illustrate the technical solutions in the embodiments of this application or the prior art, the drawings used in the description of the embodiments or the prior art will be briefly introduced below. Obviously, the drawings described below are some embodiments of this application. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0062] Figure 1a This is a schematic diagram of an EPS decline scheme;

[0063] Figure 1b This is a schematic diagram of a VoNR scheme;

[0064] Figure 2a This is a schematic diagram of the signaling flow before and after the EPS fallback on the calling side;

[0065] Figure 2b This is a schematic diagram of the signaling flow before and after the called-side EPS falls back;

[0066] Figure 3 This is a schematic diagram of an EPS fallback process based on switching.

[0067] Figure 4 This is a schematic diagram of an EPS fallback process based on redirection;

[0068] Figure 5 A schematic flowchart of an EPS fallback processing method provided in this application embodiment;

[0069] Figure 6 A schematic flowchart of an EPS fallback processing method provided in this application embodiment is shown in Figure 2.

[0070] Figure 7aA schematic diagram of a SEQ platform interface provided for an embodiment of this application;

[0071] Figure 7b A schematic diagram of a SEQ platform interface provided for an embodiment of this application;

[0072] Figure 8a A schematic diagram of a SEQ platform interface provided for embodiments of this application. Figure 3 ;

[0073] Figure 8b A schematic diagram of a SEQ platform interface provided for embodiments of this application. Figure 4 ;

[0074] Figure 9 This is a schematic diagram of the structure of an EPS fallback processing device provided in an embodiment of this application;

[0075] Figure 10 This is a schematic diagram of the structure of an electronic device provided in an embodiment of this application. Detailed Implementation

[0076] To make the objectives, technical solutions, and advantages of this application clearer, the technical solutions in the embodiments of this application will be clearly and completely described below in conjunction with the embodiments of this application. Obviously, the described embodiments are only some embodiments of this application, not all embodiments. Based on the embodiments of this application, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of this application.

[0077] In the embodiments of this application, terms such as "first" and "second" are used to distinguish identical or similar items with essentially the same function and purpose. For example, "first chip" and "second chip" are used only to distinguish different chips and do not limit their order of execution. Those skilled in the art will understand that terms such as "first" and "second" do not limit the quantity or execution order, and that "first" and "second" do not necessarily imply that they are different.

[0078] It should be noted that, in the embodiments of this application, the terms "exemplary" or "for example" are used to indicate examples, illustrations, or descriptions. Any embodiment or design scheme described as "exemplary" or "for example" in this application should not be construed as being more preferred or advantageous than other embodiments or design schemes. Specifically, the use of terms such as "exemplary" or "for example" is intended to present the relevant concepts in a specific manner.

[0079] In this application embodiment, "at least one" refers to one or more, and "more than one" refers to two or more. "And / or" describes the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent: A alone, A and B simultaneously, or B alone, where A and B can be singular or plural. The character " / " generally indicates that the preceding and following related objects are in an "or" relationship. "At least one of the following" or similar expressions refer to any combination of these items, including any combination of single or plural items. For example, at least one of a, b, or c can represent: a, b, c, ab, a--c, bc, or abc, where a, b, and c can be single or multiple.

[0080] It should be noted that the user information (including but not limited to user device information, user personal information, etc.) and data (including but not limited to data used for analysis, data stored, data displayed, etc.) involved in this application are all information and data authorized by the user or fully authorized by all parties. Furthermore, the collection, use and processing of the relevant data must comply with the relevant laws, regulations and standards of the relevant countries and regions, and corresponding operation portals are provided for users to choose to authorize or refuse.

[0081] First, the relevant concepts or terms involved in the embodiments of this application will be explained:

[0082] User Equipment (UE): Also known as a terminal, user terminal, or terminal device. Terminal devices can be mobile phones with displays, wearable devices, tablets, computers with wireless transceiver capabilities, etc.

[0083] New Radio (NR): Also known as new wireless, it refers to the wireless network of 5G. Mobile communication technology can generally be divided into two parts: the wireless network and the core network.

[0084] Evolved Packet System (EPS): EPS can be understood as a system consisting of UE, 4G access network and evolved packet core (EPC).

[0085] IP Multimedia Subsystem (IMS) is a new form of multimedia service. It can meet the increasingly novel and diverse multimedia service needs of today's end customers. Currently, IMS is the main entity for implementing voice services in 4G and 5G mobile networks.

[0086] Voice over Long-Term Evolution (VoLTE): Based on the IMS network, it enables voice services (control and media layers) to be transmitted as data streams in the 4G data bearer network, eliminating the need to maintain and rely on the traditional circuit-switched voice network.

[0087] Voice over NR (VoNR): VoNR is very similar to VoLTE, both being voice calls based on IMS. The main difference is that VoNR's IMS is established and carried by the 5G core network, while VoLTE's IMS is established and carried by the 4G core network.

[0088] Access and Mobility Management Function (AMF): One of the core network elements of 5G, logically interconnected with 5G base stations via the N2 interface. It directly manages 5G radio access requests, possessing functions such as registration management, connection management, reachability management, and mobility management. It can be used to statistically analyze the handover success rate and redirection success rate in the embodiments of this application.

[0089] Mobility Management Entity (MME) network element: The MME network element has a similar function in the 4G network to the AMF network element in the 5G network, realizing the access and mobility management functions of 4G UE.

[0090] N26 Interface: The interface between the 5G core network element AMF and the 4G core network element MME, used for interoperability between the 4G core network and the 5G core network.

[0091] Call History Record (CHR): CHR records each call using feature extraction methods for backtracking user plane issues; every call is recorded. However, due to data volume and bandwidth requirements, it typically only records dropped or failed call setups. In the era of voice services only, CHR referred to call history. In current 4G and 5G networks, CHR broadly refers to the historical log of user communication services (including calls and internet access).

[0092] External Data Representation (XDR) call detail records (CDRs) can include Call Detail Records (CDRs) and Transaction Detailed Records (TDRs). XDRs are session-level detailed records of signaling and service transmission processes generated after processing all internet data, containing all user login information. Therefore, these CDRs have very rich data analysis and mining value.

[0093] Session Management Function (SMF) network element: responsible for tunnel maintenance, IP address allocation and management, User Plane Function (UPF) network element selection, policy enforcement and Quality of Service (QoS) control, billing data collection, roaming, etc.

[0094] Control plane data gateway (PDN gateway-control plane, PGW-C) network element: Similar to SMF function, PGW-C is a packet data network (PDN) gateway network element that performs session management functions in the 4G core network.

[0095] Access Network (AN): A network consisting of all communication devices between user terminals and the operator's metropolitan area network.

[0096] In the early stages of 5G network deployment, coverage progressed from hotspots to wider coverage, and then to even wider coverage. When a terminal moves from a 5G network coverage area to an area without 5G network coverage, such as an area covered by 4G network, it needs to be able to continue using the mobile communication network. Therefore, both the network side and the terminal side must support service continuity for users when interoperating between 4G and 5G networks, thereby achieving the goal of mobile communication networks: that is, terminals can access the mobile communication network anytime, anywhere.

[0097] Voice service is a crucial and essential service for communication networks. 5G networks can provide voice services using two solutions: one is Voice over NR (VoNR) service based on New Radio (NR) access technology in 5G standalone (SA) networks; the other is Voice over Long-Term Evolution (VoLTE) service based on the 4G voice architecture and IP Multimedia Subsystem (IMS) supported by 4G networks. Therefore, when 5G SA networks cannot execute voice services, such as when terminals cannot provide voice services based on VoNR in 5G SA networks, the EPS fallback mechanism can be used to fall back from the 5G network to the 4G LTE network, thereby providing voice services based on VoLTE provided by the 4G LTE network. This ensures voice continuity and guarantees users' call needs.

[0098] The following is a brief introduction to the EPS fallback scheme and the VoNR scheme.

[0099] For example, Figure 1a A schematic diagram of an EPS decline scheme is shown. (For example...) Figure 1a As shown, in the EPS fallback scheme, the radio side does not support NR voice. When the NR initiates an INVITE message, the 5G base station initiates a redirection to the 5GC or a handover request based on the N26 interface to fall back to the LTE network, where VoLTE handles voice and data services.

[0100] Figure 1b A schematic diagram of a VoNR scheme is shown. Figure 1b As shown, VoNR is a 5G NR voice solution based on the IMS network. It is an end-to-end voice solution built on the 5G NR network under an all-IP environment, based on the IMS server. By deploying IMS, VoNR can enable concurrent voice and data services. All services are carried through the 5G network, but voice services require IMS for service control.

[0101] In terms of deployment cycle and maximizing the utilization of the existing network, the EPS fallback solution remains the most recommended voice call evolution solution at present.

[0102] The following section describes the signaling patterns before and after EPS decline on both the calling and called sides in voice services.

[0103] For example, Figure 2a This diagram illustrates the signaling path before and after EPS fallback on the calling side. Figure 2aAs shown, before EPS fallback, that is, before the UE initiates a voice call, the signaling initiated by the UE is forwarded in 5GC, that is, sent to the AMF network element through the 5G base station (NR RAN), and then forwarded to the SMF network element. When the UE initiates a voice call, it falls back to the 4G network, and the signaling initiated by the UE (such as the INVITE message) is forwarded in EPC, that is, the signaling initiated by the UE is sent to the SGW / PGW network element through the 4G base station (E-UTRAN), and then enters the IMS domain, that is, sent to the ATS network element through the Session Border Controller / Proxy Call Session Control Function (SBC / P-CSCF) network element and the Interrogating / Serving Call Session Control Function (I / S-CSCF) network element.

[0104] Figure 2b This diagram illustrates the signaling path before and after the called party's EPS (Electronic Power Supply) falls back. (Example:) Figure 2a As shown, before EPS fallback, the signaling sent by the calling party is transmitted to the SMF network element of the 5GC via the ATS network element, I / S-CSCF network element, and SBC / P-CSCF network element in the IMS domain. The SMF network element forwards the signaling to the AMF network element, and the AMF network element sends the signaling to the called UE via the NR RAN. After EPS fallback, the signaling is transmitted to the SGW / PGW network element via the 4G core network element MME, and the SGW / PGW network element sends the signaling to the called UE via the E-UTRAN.

[0105] For detailed EPS decline procedures, please refer to [link / reference]. Figures 3 to 4 There are two scenarios for EPS fallback: one is the handover-based EPS fallback process, and the other is the redirection-based EPS fallback process. Handover is a connected state action; the target 4G base station cell has already prepared resources for the UE. The UE only needs to follow the handover command to maintain continuity of the user plane and signaling plane on the target 4G base station cell. Redirection, on the other hand, first releases the AN connection to return to the idle state, and then searches for a different system base station cell based on the content (frequency point, etc.) in the release message. Once found, it completes the bearer establishment and location update process just like other UEs.

[0106] For example, Figure 3 A schematic diagram of an EPS fallback process based on switching is shown. Figure 3 As shown, the process may include:

[0107] S301. Establishment of Quality of Service Flow (QoS Flow).

[0108] S302, Switching preparation.

[0109] The 5G base station sends a handover request to the 4G base station via the AMF to the MME, and the 4G base station prepares radio resources.

[0110] S303, Switch execution.

[0111] The AMF network element initiates a handover command to the 5G base station to switch to the 4G base station.

[0112] S304, Tracking Area Update (TAU) process.

[0113] S305, Dedicated carrier established.

[0114] Establish a dedicated voice bearer in the 4G network.

[0115] The specific signaling interaction process in the above S301 to S305 procedures is existing technology and will not be described in detail here.

[0116] For example, Figure 4 A schematic diagram of an EPS fallback process based on redirection is shown. Figure 4 As shown, the process may include:

[0117] S401, QoS Flow establishment.

[0118] S402, UE releases 5G network resources.

[0119] S403 and UE register on the 4G network.

[0120] S404. Establish a dedicated voice bearer in the 4G network.

[0121] The specific signaling interaction process in the above S401 to S404 procedures is existing technology and will not be described in detail here.

[0122] Both the EPS fallback process based on handover and the EPS fallback process based on redirection are quite complex. There are many reasons that may cause EPS fallback to fail, including issues with the UE itself, 4G base stations, 5G base stations, 4G core networks, 5G core networks, etc.

[0123] In some implementations, the success rate of EPS fallback can be improved by configuring accurate parameters on the radio side (also known as the base station). For example, in the handover-based EPS fallback process, the accuracy of the 4G neighbor cell parameters configured in the 5G base station can be ensured, thereby improving the fallback success rate; in the redirection-based EPS fallback, the accuracy of the 4G frequency point parameters configured in the 5G base station can be ensured, thereby improving the fallback success rate.

[0124] However, the methods described above for improving EPS fallback success rate by configuring accurate parameters can only address some scenarios where EPS fallback fails. EPS fallback from 5G to 4G networks involves IMS, 5GC, EPC, and other areas, resulting in a long process, high latency, numerous influencing factors, and susceptibility to degradation. Multiple factors can lead to EPS fallback failure. Therefore, the EPS fallback success rate remains relatively low.

[0125] In view of this, this application provides an EPS fallback processing method. This method monitors the EPS fallback success rate. When the EPS fallback success rate is low, it performs cluster analysis on the EPS fallback data to locate the reasons for EPS fallback failure. Then, it can perform targeted optimization based on the located reasons. After targeted optimization based on the located reasons, the probability of EPS fallback failing again due to these reasons can be reduced, thereby effectively improving the EPS fallback success rate.

[0126] The technical solution of this application and how the technical solution of this application solves the above-mentioned technical problems are described in detail below with specific embodiments. These specific embodiments can be combined with each other, and the same or similar concepts or processes may not be described again in some embodiments. The embodiments of this application will now be described with reference to the accompanying drawings.

[0127] For example, Figure 5 A schematic flowchart of an EPS fallback processing method according to an embodiment of this application is shown. The executing entity of this embodiment is an EPS fallback processing device, which is located in an electronic device. Figure 5 As shown, the method may include:

[0128] S501. When the EPS fallback success rate meets the preset conditions, obtain EPS fallback data. The EPS fallback data includes at least one of the following: user session data, network element capacity, and network element configuration parameters.

[0129] EPS fallback data is used to locate the cause of EPS fallback failure. EPS fallback data can include user session data, network element capacity, network element configuration parameters and alarm logs, etc. User session data can include CHR logs and XDR call detail records, etc.

[0130] In a possible implementation, the EPS fallback success rate is monitored in real time. When the EPS fallback success rate meets the preset conditions, EPS fallback data is obtained from the SMF network element.

[0131] S502. Perform cluster analysis based on EPS fallback data to obtain the first failure factor for EPS fallback failure. The clustering dimension of the cluster analysis includes at least one of the following: user dimension, terminal type dimension, base station cell dimension, or network element dimension.

[0132] The first failure factor can be the execution entity that causes the EPS drop-down failure. For example, the first failure factor can include base stations, network elements, terminals, and users.

[0133] In a possible implementation, cluster analysis is performed on EPS fallback data from dimensions such as user, terminal type, base station cell, and network element to locate the reasons for EPS fallback failure in each dimension, so as to optimize the subsequent analysis based on the identified reasons.

[0134] S503. Based on the first failure factor of EPS decline failure, the reasons for EPS decline failure are obtained.

[0135] Since there are many factors that can cause EPS decline failure in the EPS decline process, we can first determine the main body that caused the EPS decline failure based on the analysis of EPS decline data, which is the first failure factor. Then, we can further analyze the first failure factor to determine the cause of EPS decline failure.

[0136] For example, the reasons for EPS fallback failure obtained based on the first failure factor can include base station cell parameter configuration errors, poor terminal performance, abnormal user behavior, core network element failures, etc.

[0137] In this embodiment, when the EPS fallback success rate meets preset conditions, EPS fallback data is acquired. The EPS fallback data includes at least one of the following: user session data, network element capacity, and network element configuration parameters. Cluster analysis is performed on the EPS fallback data to obtain the first failure factor for EPS fallback failure. The clustering dimensions of the cluster analysis include at least one of the following: user dimension, terminal type dimension, base station cell dimension, or network element dimension. Based on the first failure factor, the failure reason for EPS fallback failure is obtained. This multi-dimensional cluster analysis of EPS fallback data determines the first failure factor, and then the failure reason for various EPS fallback failure scenarios is determined based on the first failure factor. This allows for targeted optimization based on the failure reasons for various failure scenarios, thereby achieving the goal of improving the 5G user voice EPS fallback success rate and enhancing user experience.

[0138] Based on the above embodiments, in order to more clearly describe the technical solution of this application, please refer to the exemplary embodiments. Figure 6 , Figure 6 A second schematic flowchart illustrates an EPS fallback processing method provided in an embodiment of this application. The executing entity in this embodiment is an EPS fallback processing device, which is located within an electronic device. For example... Figure 6 As shown, the method may include:

[0139] S601. Determine the EPS fallback success rate based on the number of successful EPS fallback processes and the number of EPS fallback process requests; when the EPS fallback success rate is lower than the eighth preset value, obtain EPS fallback data.

[0140] Among them, the EPS rollback success rate is the percentage of the number of successful EPS rollback processes out of the total number of EPS rollback process requests.

[0141] The metric of the number of successful EPS fallback processes can be obtained by the converged network element SMF / PGW-C within a specified measurement period. For example, when the converged network element SMF / PGW-C is in the EPS fallback process, and the PGW-C network element receives the Modify BearerRequest message and successfully sends the Modify Bearer Response message, the metric is incremented by 1.

[0142] The metric of the number of EPS fallback requests can be obtained by the converged network element SMF / PGW-C within a specified measurement period. For example, when the converged network element SMF / PGW-C receives an HTTP POST Modify request from the AMF network element, which carries the PDU Session Resource Modify Unsuccessful Transfer information element, and the Cause in the PDU Session Resource Modify Unsuccessful Transfer is "IMS voice EPS fallback or RAT fallback triggered", the metric is incremented by 1.

[0143] In a possible implementation, the EPS fallback success rate is monitored in real time. When the EPS fallback success rate is lower than the eighth preset value, for example, when the EPS fallback success rate is lower than 99%, the EPS fallback data is acquired and stored, so that subsequent boundary analysis can be performed based on the EPS fallback data.

[0144] Step S601 is a specific implementation of step S501 above.

[0145] S602. Based on the EPS fallback data, for the clustering dimension of the clustering analysis, obtain at least one of the following: target users whose EPS fallback failure count is greater than a first preset value, target terminal types whose EPS fallback failure count is greater than a second preset value, target base station cells whose EPS fallback failure count is greater than a third preset value, and target network elements whose EPS fallback failure count is greater than a fourth preset value; take at least one of the target users, target terminal types, target base station cells, and target network elements as the first failure factor for EPS fallback failure.

[0146] In a possible implementation, cluster analysis is performed on EPS fallback data from multiple clustering dimensions to obtain one or more targets with the most EPS fallback failures in different clustering dimensions, and the targets obtained from one or more clustering dimensions are taken as the first failure factor for EPS fallback failure.

[0147] For example, CHR logs and XDR call detail records are analyzed to statistically analyze the total number of EPS fallback failures across the network from a user perspective, identifying target users whose EPS fallback failure count exceeds a first preset value. There can be one or more target users. For instance, assuming the first preset value is 100 failures and the total number of EPS fallback failures across the network is 20,000, then users with more than 100 EPS fallback failures are considered target users. The identified target users can be used for subsequent analysis to determine if abnormal behavior corresponding to these target users is causing the EPS fallback failures, in order to avoid such abnormal behavior, reduce the number of EPS fallback failures, and thus improve the EPS fallback success rate.

[0148] This analysis statistically examines the total number of EPS fallback failures across the entire network from the perspective of terminal type, identifying target terminal types with a failure rate exceeding a second preset value. There can be one or more target terminal types. For example, assuming the second preset value is 1000 failures and the total number of EPS fallback failures across the network is 20,000, then terminal types with more than 1000 failures are considered target terminal types. The obtained target terminal types can be transmitted to relevant companies to facilitate rectification of terminals corresponding to these target terminal types, reducing EPS fallback failures caused by these target terminal types and thus improving the EPS fallback success rate.

[0149] This analysis, based on base station cell data, counts the number of EPS fallback failures across the entire network to identify target base station cells with a failure count exceeding a third preset value. There can be one or more target base station cells. For example, assuming the third preset value is 1000 failures and the total number of EPS fallback failures across the network is 20,000, then base station cells with more than 1000 failures are considered target base station cells. The obtained target base station cell information can be transmitted to the base station side, facilitating further analysis and optimization by maintenance personnel to reduce EPS fallback failures caused by target base station cells, thereby improving the EPS fallback success rate.

[0150] This analysis statistically examines the total number of EPS fallback failures across the entire network at the network element level, identifying target network elements whose EPS fallback failure count exceeds a fourth preset value. These network elements can be various core network elements such as AMF, SMF, and MME. There can be one or more target network elements. For example, assuming the fourth preset value is 1000 failures and the total number of EPS fallback failures across the network is 20,000, then the network element causing more than 1000 EPS fallback failures is considered the target network element. The obtained target network element information can be transmitted to the optimization department, facilitating further analysis and optimization by maintenance personnel to reduce EPS fallback failures caused by these target network elements, thereby improving the EPS fallback success rate.

[0151] In this embodiment, the EPS fallback data is clustered from multiple clustering dimensions to obtain the target user, target terminal type, target base station cell, and / or target network element. At least one of these factors is used as the first failure factor for EPS fallback failure. This facilitates further identification of the cause of EPS fallback failure based on the first failure factor.

[0152] In one possible implementation, the following steps may also be included after step S601:

[0153] S603. Obtain the network handover success rate and the tracking area update success rate, and determine whether the network handover success rate is lower than the fifth preset value or the tracking area update success rate is lower than the sixth preset value.

[0154] Among them, the network handover success rate is the percentage of successful network handovers in the EPS fallback process based on handover, and the tracking area update success rate is the percentage of successful redirections in the EPS fallback process based on redirection.

[0155] S604. When the network handover success rate is lower than the fifth preset value or the tracking area update success rate is lower than the sixth preset value, the second failure factor of EPS fallback failure is obtained based on the signaling in the EPS fallback data.

[0156] Since the EPS fallback process of the terminal involves a handover or redirection process from the 5G network to the 4G network, if the EPS fallback success rate is lower than the eighth preset value, it is also necessary to determine whether the handover success rate or redirection success rate from the 5G network to the 4G network is normal. Therefore, when the EPS fallback success rate is lower than the eighth preset value, the handover success rate or redirection success rate is obtained from the AMF network element. If the handover success rate or redirection success rate is abnormal, that is, the network handover success rate is lower than the fifth preset value or the tracking area update success rate is lower than the sixth preset value, the signaling in the EPS fallback data is analyzed to determine the second failure factor of the EPS fallback failure.

[0157] Furthermore, when obtaining the second failure factor for EPS decline failure, the above step S503 may include: obtaining the failure reason for EPS decline failure based on the first failure factor and the second failure factor for EPS decline failure.

[0158] In this embodiment of the application, when the EPS falls below an eighth preset value, cluster analysis can be performed on the acquired EPS fall data to determine the first failure factor. Simultaneously, based on the analysis of signaling in the EPS fall data, a second failure factor can be determined. Thus, the cause of the EPS fall failure is determined based on further analysis of the first and / or second failure factors.

[0159] For example, the reasons for EPS fallback failure determined based on the first failure factor and / or the second failure factor may include incorrect base station cell parameter configuration, poor terminal performance, abnormal user behavior, core network element failure, weak coverage or interference in the base station cell, etc.

[0160] In one possible implementation, the second failure factor for EPS fallback failure, derived from the signaling in the EPS fallback data, may include:

[0161] Based on the EPS fallback data, determine whether there are process conflict signaling and / or handover cancellation signaling in the EPS fallback process; if there are process conflict signaling and / or handover cancellation signaling, then determine that the second failure factor is the base station cell or terminal.

[0162] In this embodiment of the application, process conflict signaling can be understood as signaling that interrupts the signaling process. For example, if another signaling process is initiated before the previous signaling process is completed, causing the previous signaling process to be interrupted, then the other signaling is process conflict signaling.

[0163] For example, when the UE initiates the first signaling request, and before the UE receives a response to the first signaling request, the UE initiates a second signaling request, causing the process of the first signaling request to be interrupted. At this time, the UE can be identified as the second failure factor for EPS fallback failure, so that maintenance personnel can check the performance of the UE.

[0164] For example, if the handover fails after the base station sends a handover command to the terminal, and the terminal initiates reconstruction or reconstruction for other reasons, the base station sends a handover cancellation signaling to the core network. Therefore, when a handover cancellation signaling is present in the EPS fallback data, it means that the base station has issued a handover cancellation signaling. At this time, the second failure factor is determined to be the base station cell or the terminal, so that subsequent maintenance personnel can check the configuration of the base station cell and the performance of the terminal.

[0165] In one possible implementation, the following steps may also be included after step S603:

[0166] S605. Based on the EPS fallback data, obtain the number of successful responses, the number of failed responses, and the number of timeouts of the mobile management entity network element during the network handover process; based on the number of successful responses, the number of failed responses, and the number of timeouts, determine that the third failure factor for EPS fallback failure is the mobile management entity network element and the base station cell.

[0167] In a possible implementation, when the network handover success rate is lower than the fifth preset value or the tracking area update success rate is lower than the sixth preset value, the number of successful responses, failed responses, and timeouts of the mobility management entity (MME) during the network handover process can be statistically analyzed from the EPS fallback data. Furthermore, if a preset relationship is satisfied between the number of successful responses, failed responses, and timeouts of the MME during the network handover process, the third failure factor for EPS fallback failure is determined to be the MME and the base station cell.

[0168] Furthermore, based on the first and second failure factors of EPS decline failure, the reasons for EPS decline failure can include:

[0169] Based on the first, second, and third failure factors of EPS decline failure, the reasons for EPS decline failure are obtained.

[0170] In this embodiment of the application, when the EPS falls below an eighth preset value, cluster analysis can be performed on the acquired EPS fallback data to determine the first failure factor. At the same time, based on the analysis of signaling in the EPS fallback data, the second failure factor of EPS fallback failure can be determined, and based on the number of successful responses, the number of failed responses, and the number of response timeouts of the mobility management entity network element during network handover, the third failure factor of EPS fallback failure can be determined. Thus, the cause of EPS fallback failure can be determined based on further analysis of the first failure factor, the second failure factor, and / or the third failure factor.

[0171] For example, the reasons for EPS fallback failure determined based on the first failure factor, the second failure factor, and / or the third failure factor may include base station cell parameter configuration errors, poor terminal performance, abnormal user behavior, core network element failure, weak coverage or interference in the base station cell, data configuration errors of the N26 interface of the MME element, and intermittent disconnections of the S1 link between the 4G base station and the MME element.

[0172] In one possible implementation, the third failure factor for EPS fallback failure, derived from the above based on the number of successful responses, the number of failed responses, and the number of timeouts, is the mobility management entity network element and the base station cell, which may include:

[0173] The total number of responses is determined based on the number of successful responses, the number of failed responses, and the number of timeout responses; the total percentage of failed responses and timeout responses in the total number of responses is obtained; if the total percentage is greater than the seventh preset value, then the third failure factor for EPS fallback failure is the mobile management entity network element and the base station cell.

[0174] In addition to process conflicts and handover cancellation signaling during EPS fallback, abnormal handover success rates or redirection success rates from 5G to 4G networks can also be caused by an excessively high percentage of handover response failures and response timeouts in mobile management entity network elements.

[0175] Therefore, when the network handover success rate is lower than the fifth preset value or the tracking area update success rate is lower than the sixth preset value, that is, when the handover success rate from 5G network to 4G network or the redirection success rate is abnormal, the total number of responses is determined based on the number of successful responses, the number of failed responses, and the number of timeout responses in the EPS fallback data. Then, the total percentage of the number of failed responses and the number of timeout responses in the total number of responses is determined. If the total percentage is greater than the seventh preset value, which can be, for example, 10%, then the third failure factor for EPS fallback failure is determined to be the mobile management entity network element and the base station cell.

[0176] In this embodiment, by real-time monitoring of the EPS fallback success rate indicator, when the EPS fallback success rate is abnormal, the first failure factor, the second failure factor, and / or the third failure factor are obtained through boundary analysis of EPS fallback data such as CHR logs and XDR call detail records. Then, the cause of EPS fallback failure is located based on the first failure factor, the second failure factor, and / or the third failure factor, so that targeted optimization can be carried out according to the cause of failure in various failure scenarios, thereby improving the 5G user voice EPS fallback success rate.

[0177] Based on the above embodiments, in order to more clearly describe the technical solution of the embodiments of this application, for example, taking the Customer Experience Management Enablement (Service & Experience Quality Analyst, SEQ) platform as the execution subject, the EPS fallback processing method provided by the embodiments of this application is described based on two scenarios: EPS fallback during switching and EPS fallback during redirection.

[0178] The SEQ platform can be understood as a data analysis and storage platform that associates end-to-end data from the operator's network, including wireless, transmission, core network, and applications, and can be used to analyze data such as XDR call detail records. In this embodiment, the SEQ platform is used to provide analysis, evaluation, delimitation, location, and optimization guidance for typical problems in the EPS fallback process.

[0179] It is understood that the SEQ platform is illustrative and other implementations may use other devices or equipment to implement the EPS fallback processing method provided in this application embodiment. This application embodiment does not specifically limit this.

[0180] The method provided in the embodiments of this application will be described below based on the EPS fallback scenario during switching.

[0181] S10, EPS pullback mode selection switch.

[0182] For example, Figure 7a This illustration shows a schematic diagram of the SEQ platform interface provided in an embodiment of this application. Under the "Topic Analysis" menu of the SEQ platform tools, select EPS decline, as shown... Figure 7a As shown, you can view the EPS decline success rate index for Province A, and select an appropriate evaluation interval by time range, time granularity, and regional scope. For example... Figure 7a The interface displays the change curve of the handover-based fallback success rate indicator from May 26, 2022 to June 1, 2022. This interface can also display report details, which may include fallback success rate, fallback duration, initial call fallback success rate, initial call fallback duration, final call fallback success rate, final call fallback duration, and fallback handover success rate for each time granularity.

[0183] S11. In response to the user's drill-down operation at a specific time point, query the distribution of EPS fallback failure reasons based on the switch during that time period.

[0184] For example, Figure 7b This illustration shows a second schematic diagram of a SEQ platform interface provided in an embodiment of this application. In such... Figure 7a As shown on the interface, the success rate of the pullback during the period from May 31, 2022 to June 1, 2022 was low. In response to user drill-down operations during this period, the SEQ platform, based on its analysis of EPS pullback data, displays the following... Figure 7b The interface shown is as follows: Figure 7b As shown, based on the analysis of EPS fallback data acquired and stored by the SEQ platform, the reasons for EPS fallback failures during this period were attributed to the radio side (86.7%) and the core network side (13.3%). Among the failure reasons identified, the main causes were "successful handover but the 4G base station did not receive the TAU request sent by the UE" and "the MME network element did not receive the handover notification message sent by the 4G base station," with the former accounting for 57.75% and the latter for 27.51%. The interface also displays a list of failure reasons, which can include the failure pie chart attribution, failure scenario, transaction protocol, first fallback transaction, failure type, fallback reason, and number of failures for the period from May 31, 2022 to June 1, 2022.

[0185] S12. Investigate failure scenarios where EPS drop-off and disconnection due to SEQ switching account for a high proportion.

[0186] The reason for disconnection, "successful handover but the 4G base station did not receive the TAU request sent by the UE", accounted for 63% of the external reasons for failure. The first disconnection transaction corresponding to this reason is the TAU request, and the failure is attributed to the base station. The reason for disconnection, "the MME network element did not receive the handover notification message sent by the 4G base station", accounted for 28% of the external reasons for failure. The first disconnection transaction corresponding to this reason is the handover request, and the failure is attributed to the base station.

[0187] S13, Scenario Analysis.

[0188] The typical scenario corresponding to the disconnection reason "MME network element did not receive the handover notification message sent by the 4G base station" is during the 5G to 4G network handover process. Specifically, in step S303 above, the MME network element has replied to the 5G base station with the handover command, but the MME network element did not receive the handover notification message reported by the 4G base station, and the handover process failed. The typical scenario corresponding to the disconnection reason "Handover successful but the 4G base station did not receive the TAU request sent by the UE" is after the 5G to 4G network handover process is completed and the TAU process is about to begin. Specifically, in step S304 above, the MME network element did not receive the TAU request reported by the 4G base station, and the TAU process did not start. The reasons for the disconnection reasons "Handover successful but the 4G base station did not receive the TAU request sent by the UE" and "Handover successful but the 4G base station did not receive the TAU request sent by the UE" could be due to the UE falling back to the 4G network and becoming disconnected from the network. It is recommended to check the base station coverage.

[0189] S14. Extract the list of base stations with more than a preset value in the above two failure scenarios and the number of failures for each base station from the SEQ platform, so as to investigate coverage-related problems on the base station side.

[0190] The method provided in the embodiments of this application will be described below based on the EPS fallback scenario of redirection.

[0191] S20, EPS pullback method: select redirection.

[0192] For example, Figure 8a This application provides a schematic diagram of a SEQ platform interface according to an embodiment. Figure 3 In the SEQ platform tools main menu, under "Special Topic Analysis," select "EPS Decline," as shown below. Figure 8a As shown, you can view the EPS decline success rate index for Province A, and select an appropriate evaluation interval by time range, time granularity, and regional scope. For example... Figure 8a The display shows the change curve of the fallback success rate indicator based on redirection from May 26, 2022 to June 1, 2022. This interface can also display report details, which may include fallback success rate, fallback duration, initial call fallback success rate, initial call fallback duration, final call fallback success rate, final call fallback duration, and fallback handover success rate for each time granularity.

[0193] S21. In response to the user's drill-down operation at a specific time point, query the distribution of EPS drop-off failure reasons based on redirection during that time period.

[0194] For example, Figure 8b This illustration shows a schematic diagram of a SEQ platform interface provided in an embodiment of this application. Figure 4 In such Figure 8aOn the interface shown, in response to the user's operation of drilling down to the period from May 30, 2022 to May 31, 2022, the SEQ platform displays the following based on the analysis of EPS decline data: Figure 8b The interface shown is as follows: Figure 8b As shown, based on the analysis of EPS fallback data acquired and stored by the SEQ platform, the reasons for EPS fallback failures during this period were attributed to the radio side (93.5%), the core network side (6.3%), and the user or terminal side (0.2%). Among the failure reasons identified, the main causes were "Temporary Reject Registration Ongoing" and "AN Release Complete but TAU ​​Request Not Received" (5G base station connection release completed but MME did not receive the TAU request reported by the 4G base station). A smaller portion of the failures were due to "4G base station not initiating TAU procedure." Specifically, "Temporary Reject Registration Ongoing" and "AN Release Complete but TAU ​​Request Not Received" accounted for 63.02% and 26.66% of the failures, respectively, while other failure reasons totaled 10.32%. The interface can also display a list of failure reasons, which can include the cause of failure, failure scenario, transaction protocol, first disconnected transaction, failure type, disconnection reason, and number of failures for the period from May 30, 2022 to May 31, 2022.

[0195] S22. Investigate failure scenarios where EPS pullback due to SEQ redirection accounts for a high percentage of the failures.

[0196] The reason for disconnection, "temporary refusal to register," accounted for 65% of the external reasons for failure. The first disconnection transaction corresponding to this reason was "AMF network element transmitting N1N2 message (Namf_Communication_N1N2MessageTransfer)," and the failure was attributed to the base station. The reason for disconnection, "5G base station connection release completed but MME did not receive the TAU request reported by 4G base station," accounted for 28% of the external reasons for failure. The first disconnection transaction corresponding to this reason was TAU request, and the failure was attributed to the base station.

[0197] S23, Scenario Analysis.

[0198] The typical scenario corresponding to the disconnection reason "temporary registration refusal" is that the 5G network to 4G network redirection process is interrupted by other processes. Specifically, in step S402 above, the process of the 5G base station sending a request to the AMF network element to release the UE-related NG interface logical connection is interrupted by other processes. These other processes could be, for example, the mobility registration process or the service request process. This disconnection reason could occur because the AMF or MME network element prioritizes processing other mobility processes, causing the EPS fallback process to be interrupted, generally due to base station-side coverage issues. The typical scenario corresponding to the disconnection reason "5G base station connection release completed but MME did not receive the TAU request reported by the 4G base station" is the 5G network to 4G network redirection process. After AN Release, the TAU process is prepared, but the MME network element does not receive the TAU request reported by the base station, and the TAU process does not start. The typical scenario corresponding to the disconnection reason "4G base station did not initiate the TAU process" is the 5G network to 4G network redirection process. After AN Release, the TAU process is prepared, but the 4G base station does not initiate the TAU request. The reasons for disconnection, such as "5G base station connection release completed but MME did not receive TAU request reported by 4G base station" and "4G base station did not initiate TAU procedure", may be due to the UE falling back to the 4G network and becoming disconnected. It is recommended to check the coverage of the base station.

[0199] S24. Extract the list of base stations with more than a preset value in the above three failure scenarios and the corresponding number of failures for each base station from the SEQ platform, so as to investigate coverage-related problems on the base station side.

[0200] In one possible implementation, after optimization, the SEQ platform can be used to check whether the proportion of failure reasons that accounted for a high percentage before optimization has decreased after optimization, and whether the EPS fallback success rate has improved, to ensure that the optimization implementation has an improvement effect.

[0201] In this embodiment of the application, through daily analysis of the EPS fallback process, it was determined that the failure scenarios are mainly concentrated in two categories: process conflicts and failures caused by the base station side.

[0202] In this embodiment, the trend of EPS fallback success rate is monitored through network management indicators. If abnormal fluctuations occur in the indicators, the failure factors with higher proportions and their corresponding failure scenarios are obtained through analysis of EPS fallback data such as CHR logs and XDR call detail records, thus completing the initial delineation. Targeted optimizations are then performed based on the failure scenarios and analysis results: base station optimization, core network element problem investigation, typical user problem investigation and handling, UE problem investigation, etc., thereby reducing the number of EPS fallback failures and improving the EPS fallback success rate.

[0203] Figure 9This is a schematic diagram of an EPS fallback processing device provided in an embodiment of this application. Figure 9 As shown, the EPS fallback processing device 90 includes an acquisition module 901, an analysis module 902, and a determination module 903, wherein,

[0204] The acquisition module 901 is used to acquire EPS fallback data when the EPS fallback success rate meets the preset conditions. The EPS fallback data includes at least one of the following: user session data, network element capacity, and network element configuration parameters.

[0205] The analysis module 902 is used to perform cluster analysis based on EPS fallback data to obtain the first failure factor of EPS fallback failure. The clustering dimension of the cluster analysis includes at least one of the following: user dimension, terminal type dimension, base station cell dimension, or network element dimension.

[0206] The determination module 903 is used to determine the failure reason for EPS fallback failure based on the first failure factor.

[0207] In one possible implementation, the analysis module 902 is specifically used for:

[0208] Based on EPS fallback data, at least one of the following is obtained for the clustering dimension of clustering analysis: target users with more than one preset value of EPS fallback failures, target terminal types with more than one preset value of EPS fallback failures, target base station cells with more than one preset value of EPS fallback failures, and target network elements with more than one preset value of EPS fallback failures.

[0209] At least one of the following should be considered as the first failure factor for EPS fallback failure: target user, target terminal type, target base station cell, and target network element.

[0210] In one possible implementation, after acquiring the EPS fallback data, the EPS fallback processing device 90 further includes:

[0211] The first acquisition module is used to acquire network handover success rate and tracking area update success rate;

[0212] The first determination module is used to determine the second failure factor of EPS fallback failure based on the signaling in the EPS fallback data when the network handover success rate is lower than the fifth preset value or the tracking area update success rate is lower than the sixth preset value.

[0213] The determination module 903 is specifically used to: determine the failure reason for EPS decline failure based on the first failure factor and the second failure factor.

[0214] In one possible implementation, the first determining module is specifically used for:

[0215] Determine whether there are process conflict signaling and / or switch cancellation signaling in the EPS fallback process based on EPS fallback data;

[0216] If there is a process conflict signaling and / or a handover cancellation signaling, the second failure factor is determined to be the base station cell or the terminal.

[0217] In one possible implementation, if the network handover success rate is lower than a fifth preset value, the EPS fallback processing device 90 further includes:

[0218] The second acquisition module is used to acquire the number of successful responses, the number of failed responses, and the number of timeouts of the mobility management entity network element during the network handover process, based on the EPS fallback data.

[0219] The second determining module is used to determine the third failure factor for EPS fallback failure based on the number of successful responses, the number of failed responses, and the number of timeouts. The factors are the mobility management entity network element and the base station cell.

[0220] The determination module 903 is specifically used to: determine the failure reason for EPS decline failure based on the first failure factor, the second failure factor, and the third failure factor.

[0221] In one possible implementation, the second determining module is specifically used for:

[0222] The total number of responses is determined based on the number of successful responses, the number of failed responses, and the number of response timeouts.

[0223] Obtain the percentage of response failures and response timeouts in the total number of responses;

[0224] If the total percentage is greater than the seventh preset value, then the third failure factor for EPS decline failure is the mobile management entity network element and the base station cell.

[0225] In one possible implementation, module 901 is specifically used for:

[0226] The EPS fallback success rate is determined based on the number of successful EPS fallback processes and the number of EPS fallback process requests.

[0227] When the EPS decline success rate is lower than the eighth preset value, obtain EPS decline data.

[0228] The EPS fallback processing device 90 provided in this application embodiment can execute the technical solution shown in the above-described EPS fallback processing method embodiment. Its implementation principle and beneficial effects are similar, and will not be described again here.

[0229] Figure 10 This is a schematic diagram of the structure of an electronic device provided in an embodiment of this application. Please refer to... Figure 10 The electronic device 100 includes a memory 1001, a processor 1002, a communication component 1003, and a bus 1004. The memory 1001, the processor 1002, and the communication component 1003 are interconnected via the bus 1004.

[0230] Memory 1001 stores computer-executed instructions;

[0231] The processor 1002 executes the computer execution instructions stored in the memory 1001, causing the processor 1002 to perform the above-mentioned EPS fallback processing method.

[0232] The communication component 1003 can be applied to, but is not limited to, transceiver devices such as transceivers, to enable communication between the electronic device 100 and other devices or communication networks.

[0233] Bus 1004 may include a pathway for transmitting information between various components of electronic device 100 (e.g., memory 1001, processor 1002, communication component 1003).

[0234] Figure 10 The electronic device shown in the embodiment can execute the technical solution shown in the above EPS fallback processing method embodiment. Its implementation principle and beneficial effects are similar, and will not be described again here.

[0235] This application also provides a computer-readable storage medium storing computer-executable instructions, which are used to implement the above-described EPS fallback processing method when executed by a processor.

[0236] This application also provides a computer program product, including a computer program that, when executed by a processor, can implement the above-described EPS fallback processing method.

[0237] Other embodiments of this application will readily occur to those skilled in the art upon consideration of the specification and practice of the invention disclosed herein. This application is intended to cover any variations, uses, or adaptations of this application that follow the general principles of this application and include common knowledge or customary techniques in the art not disclosed herein. The specification and examples are to be considered exemplary only, and the true scope and spirit of this application are indicated by the appended claims.

[0238] It should be understood that this application is not limited to the precise structure described above and shown in the accompanying drawings, and various modifications and changes can be made without departing from its scope. The scope of this application is limited only by the appended claims.

Claims

1. An EPS fallback processing method, characterized by, The method comprises: According to the number of successful EPS fallback processes and the number of EPS fallback process requests, an EPS fallback success rate is determined; when the EPS fallback success rate is lower than an eighth preset value, EPS fallback data is obtained, the EPS fallback data comprising at least one of the following: user session data, network element capacity, network element configuration parameters; According to the EPS fallback data, clustering analysis is performed, and at least one of the following is obtained according to the clustering dimension of the clustering analysis: a target user with an EPS fallback failure number greater than a first preset value, a target terminal type with an EPS fallback failure number greater than a second preset value, a target base station cell with an EPS fallback failure number greater than a third preset value, and a target network element with an EPS fallback failure number greater than a fourth preset value, wherein the clustering dimension of the clustering analysis comprises at least one of a user dimension, a terminal type dimension, a base station cell dimension, or a network element dimension; at least one of the target user, the target terminal type, the target base station cell, and the target network element is taken as a first failure factor of EPS fallback failure; The network switching success rate and the tracking area update success rate are obtained, and it is determined whether the network switching success rate is lower than a fifth preset value or the tracking area update success rate is lower than a sixth preset value; when the network switching success rate is lower than the fifth preset value or the tracking area update success rate is lower than the sixth preset value, it is determined whether there is process conflict signaling and / or switching cancellation signaling in the EPS fallback process according to the signaling in the EPS fallback data, and if there is process conflict signaling and / or switching cancellation signaling, a second failure factor of EPS fallback failure is determined to be a base station cell or a terminal; According to the EPS fallback data, the number of successful responses, the number of failed responses, and the number of response timeouts of a mobile management entity network element in a network switching process are obtained; according to the number of successful responses, the number of failed responses, and the number of response timeouts, the total number of responses is determined, and the total proportion of the number of failed responses and the number of response timeouts in the total number of responses is obtained; if the total proportion is greater than a seventh preset value, a third failure factor of EPS fallback failure is obtained, which is a mobile management entity network element and a base station cell; According to the first failure factor, the second failure factor, and the third failure factor of the EPS fallback failure, the failure cause of the EPS fallback failure is obtained.

2. The method of claim 1, wherein, According to the EPS fallback data, the number of successful responses, the number of failed responses, and the number of response timeouts of a mobile management entity network element in a network switching process are obtained, comprising: If the network switching success rate is lower than a fifth preset value, according to the EPS fallback data, the number of successful responses, the number of failed responses, and the number of response timeouts of a mobile management entity network element in a network switching process are obtained.

3. An EPS fallback processing apparatus characterized by comprising: The method comprises an obtaining module, an analysis module, and a determination module, wherein: The obtaining module is configured to determine an EPS fallback success rate according to the number of successful EPS fallback processes and the number of EPS fallback process requests; when the EPS fallback success rate is lower than an eighth preset value, EPS fallback data is obtained, the EPS fallback data comprising at least one of the following: user session data, network element capacity, network element configuration parameters; The analysis module is configured to perform clustering analysis according to the EPS fallback data, obtain at least one of the following from a clustering dimension of the clustering analysis: a target user with a number of EPS fallback failures greater than a first preset value, a target terminal type with a number of EPS fallback failures greater than a second preset value, a target base station cell with a number of EPS fallback failures greater than a third preset value, and a target network element with a number of EPS fallback failures greater than a fourth preset value, wherein the clustering dimension of the clustering analysis includes at least one of a user dimension, a terminal type dimension, a base station cell dimension, or a network element dimension; take at least one of the target user, the target terminal type, the target base station cell, and the target network element as a first failure factor of the EPS fallback failure; obtain a network switching success rate and a tracking area update success rate, and determine whether the network switching success rate is lower than a fifth preset value or the tracking area update success rate is lower than a sixth preset value; when the network switching success rate is lower than the fifth preset value or the tracking area update success rate is lower than the sixth preset value, determine whether there is process conflict signaling and / or switching cancellation signaling in the EPS fallback process according to signaling in the EPS fallback data, and if there is process conflict signaling and / or switching cancellation signaling, determine that a base station cell or a terminal is a second failure factor of the EPS fallback failure; obtain, according to the EPS fallback data, a number of successful responses, a number of failed responses, and a number of timeout responses of a mobile management entity network element in a network switching process; determine a total number of responses according to the number of successful responses, the number of failed responses, and the number of timeout responses, obtain a total proportion of the number of failed responses and the number of timeout responses in the total number of responses; and if the total proportion is greater than a seventh preset value, determine that a mobile management entity network element and a base station cell are a third failure factor of the EPS fallback failure. The determination module is configured to obtain a failure cause of the EPS fallback failure according to the first failure factor, the second failure factor, and the third failure factor of the EPS fallback failure.

4. An electronic device, comprising: Comprise: a processor, a memory; The memory stores computer execution instructions; the processor executes the computer execution instructions stored in the memory, so that the processor executes the method of any one of claims 1-2.

5. A computer readable storage medium, characterized in that, The computer readable storage medium stores computer execution instructions, and when the computer execution instructions are executed by the processor, the computer execution instructions are used to implement the method of any one of claims 1-2.

Images