Network exception fallback identification method and device, storage medium and electronic equipment

Abstract

The application discloses a network abnormality fallback identification method and device, a storage medium and electronic equipment. The method comprises the following steps: determining a first signaling flow based on a context request record included in an N26 interface log, a tracking area update record in an S1-MME interface log, and a user terminal context release record in an N1 / N2 interface log; determining a second signaling flow based on a relocation request record included in the N26 interface log and an N2 interface switching-out flow record in the N1 / N2 interface log; and obtaining a network abnormality fallback identification result of a target user according to the first signaling flow and the second signaling flow. The application solves the technical problem of low network abnormality fallback identification accuracy caused by the fact that the 5G network cannot be excluded from falling back to the 4G network due to the evolved packet system fallback (EPS Fallback) mode when the network abnormality fallback is performed in the related art.

Description

TECHNICAL FIELD

[0001] The present application relates to the field of wireless communication and terminal, in particular to a network abnormal fallback identification method and device, a storage medium and an electronic equipment. BACKGROUND

[0002] 5G user use process sometimes falls back to 4G phenomenon, the cause of falling back mainly has two kinds: one kind is that user terminal UE or base station does not support the voice VONR service running under 5G frequency band, for guaranteeing can continue to use voice service, the normal generation 5G falls back to 4G phenomenon of using evolved packet system fallback EPS Fallback mode realization;The second kind is due to the poor quality of 5G wireless network coverage or improper configuration causes the abnormal phenomenon of 5G falls back to 4G, this phenomenon affects user perception.But in the related art, when 5G network abnormal fallback to 4G network is carried out, the network abnormal fallback identification cannot distinguish the network fallback caused by evolved packet system fallback EPS Fallback mode from the network abnormal fallback, resulting in low network abnormal fallback identification accuracy, affecting user experience.

[0003] For the above problems, no effective solution has been proposed so far. SUMMARY

[0004] The embodiments of the present application provide a network abnormal fallback identification method, device, storage medium and electronic equipment, to at least solve the technical problem of low network abnormal fallback identification accuracy caused by the fact that in the related art, when network abnormal fallback is carried out, the 5G network fallback to 4G network caused by evolved packet system fallback EPS Fallback mode cannot be excluded.

[0005] According to an aspect of the embodiments of the present application, a network abnormal fallback identification method is provided, comprising: obtaining predetermined interface call records in application detailed record XDR data of a target user, wherein the predetermined interface call records at least include: N1 / N2 interface call records corresponding to a 5G network, N26 interface call records, and S1-MME interface call records corresponding to a 4G network; determining a first signaling flow based on context request records included in the N26 interface call records, tracking area update records in the S1-MME interface call records, and user terminal context release records in the N1 / N2 interface call records, wherein the first signaling flow is used to indicate a signaling flow of switching from the 5G network to the 4G network corresponding to non-evolved packet system fallback in a network idle state; determining a second signaling flow based on relocation request records included in the N26 interface call records and N2 interface handover out flow records in the N1 / N2 interface call records, wherein the second signaling flow is used to indicate a signaling flow of switching from the 5G network to the 4G network corresponding to non-evolved packet system fallback in a network connection state; and obtaining a network abnormal fallback identification result of the target user according to the first signaling flow and the second signaling flow.

[0006] According to another aspect of the embodiments of the present application, a network abnormal fallback identification device is also provided, comprising: a first obtaining module, configured to obtain predetermined interface call records in application detailed record XDR data of a target user, wherein the predetermined interface call records at least include: N1 / N2 interface call records corresponding to a 5G network, N26 interface call records, and S1-MME interface call records corresponding to a 4G network; a first determining module, configured to determine a first signaling flow based on context request records included in the N26 interface call records, tracking area update records in the S1-MME interface call records, and user terminal context release records in the N1 / N2 interface call records, wherein the first signaling flow is used to indicate a signaling flow of switching from the 5G network to the 4G network corresponding to non-evolved packet system fallback in a network idle state; a second determining module, configured to determine a second signaling flow based on relocation request records included in the N26 interface call records and N2 interface handover out flow records in the N1 / N2 interface call records, wherein the second signaling flow is used to indicate a signaling flow of switching from the 5G network to the 4G network corresponding to non-evolved packet system fallback in a network connection state; and a second obtaining module, configured to obtain a network abnormal fallback identification result of the target user according to the first signaling flow and the second signaling flow.

[0007] According to another aspect of the embodiments of the present application, a non-volatile storage medium is also provided, the non-volatile storage medium stores a plurality of instructions, and the instructions are suitable for being loaded and executed by a processor to perform any one of the network abnormal fallback identification methods.

[0008] According to another aspect of the embodiments of the present application, an electronic device is also provided, which includes one or more processors and a memory for storing one or more programs, wherein the one or more programs, when executed by the one or more processors, cause the one or more processors to implement any one of the network abnormal fallback identification methods.

[0009] In the embodiments of the present application, the predetermined interface call records in the application detailed record XDR data of the target user are acquired, wherein the predetermined interface call records at least include: N1 / N2 interface call records corresponding to the 5G network, N26 interface call records, and S1-MME interface call records corresponding to the 4G network; based on the context request records included in the N26 interface call records, the tracking area update records in the S1-MME interface call records, and the user terminal context release records in the N1 / N2 interface call records, the first signaling flow is determined, wherein the first signaling flow is used to indicate the signaling flow of switching from the 5G network to the 4G network corresponding to the non-evolved packet system fallback in the network idle state; based on the relocation request records included in the N26 interface call records, and the N2 interface handover out flow records in the N1 / N2 interface call records, the second signaling flow is determined, wherein the second signaling flow is used to indicate the signaling flow of switching from the 5G network to the 4G network corresponding to the non-evolved packet system fallback in the network connection state; according to the first signaling flow and the second signaling flow, the network abnormal fallback identification result of the target user is obtained, which achieves the purpose of accurately identifying the network abnormal fallback caused by the evolved packet system fallback EPS Fallback mode to switch from the 5G network to the 4G network, thereby realizing the technical effects of improving the network abnormal fallback identification accuracy and accurately tracing the 5G network quality problem, and further solving the technical problem of low network abnormal fallback identification accuracy caused by the fact that the evolved packet system fallback EPS Fallback mode cannot be excluded when the network abnormal fallback is performed in the related art. BRIEF DESCRIPTION OF DRAWINGS

[0010] The accompanying drawings, which are included to provide a further understanding of the application and are incorporated in and constitute a part of this application, illustrate embodiments of the application and together with the description serve to explain the application. In the drawings:

[0011] Figure 1 is a schematic diagram of a network abnormal fallback identification method according to an embodiment of the present application;

[0012] Figure 2 is a schematic diagram of an optional network abnormal fallback identification method according to an embodiment of the present application;

[0013] Figure 3 is a comparison diagram of optional S1-MME interface message and original signaling according to an embodiment of the present application;

[0014] Figure 4 is a comparison diagram of optional context request record and original signaling according to an embodiment of the present application;

[0015] Figure 5 is a comparison diagram of optional user terminal context release record and original signaling according to an embodiment of the present application;

[0016] Figure 6 is a comparison diagram of optional N2 interface handover out flow and original signaling according to an embodiment of the present application;

[0017] Figure 7 is a schematic diagram of a network abnormality fallback identification device according to an embodiment of the present application. DETAILED DESCRIPTION

[0018] In order to make the personnel in the art better understand the present application scheme, the technical scheme in the embodiments of the present application will be described clearly and completely below in conjunction with the drawings in the embodiments of the present application. Obviously, the described embodiments are only a part of the embodiments of the present application, not all the embodiments. Based on the embodiments in the present application, all other embodiments obtained by those skilled in the art without creative labor should belong to the scope of protection of the present application.

[0019] It should be noted that the terms "first", "second", etc. in the specification and claims of the present application and the above-mentioned drawings are used to distinguish similar objects, and do not necessarily describe a specific order or sequence. It should be understood that the data thus used can be interchanged under appropriate circumstances, so that the embodiments of the present application described herein can be implemented in an order other than those illustrated or described herein. In addition, the terms "include" and "have" and any variations thereof are intended to cover non-exclusive inclusion, for example, a process, method, system, product or device including a series of steps or units does not necessarily have to be limited to those steps or units clearly listed, but can include other steps or units not clearly listed or inherent to these processes, methods, products or devices.

[0020] First, for the convenience of understanding the embodiments of the present application, the following will explain some terms or nouns involved in the present application:

[0021] 5GC (5G Core Network), 5G core network; 5G, fifth generation mobile communication network; 4G, fourth generation mobile communication network.

[0022] EPS Fallback (Evolved Packet System Fallback), evolved packet system fallback. 5G initial NR does not provide voice service, when gNodeB (Next Generation NodeB) establishes IMS (IP Multimedia Subsystem) voice channel on NR (New Radio), it will trigger handover. At this time, gNodeB initiates redirection or inter-RAT handover request to 5G Core, falls back to LTE (Long Term Evolution) network, and provides voice by VoLTE (Voice over LTE).

[0023] N26, interface between AMF (Access and Mobility Management Function) and MME (Mobility Management Entity). Provides signaling message tunneling between AMF and MME, used to assist the completion of interoperation between 5G network and LTE (Long Term Evolution) network.

[0024] S1-MME, interface between MME (Mobility Management Entity) and eNodeB, applied to 4G network.

[0025] N1, interface between UE and AMF (Access and Mobility Management Function). Used for transmission of NAS (non-Access Stratum) signaling messages between UE and AMF. The interface protocol is NAS-MM (non-Access Stratum Mobility Management), an application layer protocol between UE and AMF.

[0026] N2, interface between NG-RAN (NG Radio Access Network) and AMF (Access and Mobility Management Function). The signaling connection function of N2 interface provides reliable transmission for wireless network signaling.

[0027] UE Context Release, a message sent by the NG-RAN node to request release of the UE-related NG interface logical connection.

[0028] Context Request, the MME on the target side sends this message to the AMF on the source side over the N26 interface in the EPS and 5GS reselection procedure, for obtaining the MM and EPS bearer context of the UE. The Context Request message can also be sent by the AMF on the target side to the MME on the source side over the N26 interface in the EPS and 5GS reselection procedure.

[0029] TAU, Tracking Area Update procedure; N2 HO OUT, N2 interface handover out procedure.

[0030] Forward Relocation Request, the MME on the source side sends this message to the AMF on the target side over the N26 interface in the EPS and 5GS handover procedure, as part of the relocation procedure in the handover procedure. The Forward Relocation Request message can also be sent by the AMF on the source side to the MME on the target side over the N26 interface.

[0031] According to an embodiment of the present application, a network exception fallback identification method embodiment is provided. It should be noted that the steps shown in the flowchart of the accompanying drawings can be executed in a computer system such as a set of computer executable instructions, and although a logical order is shown in the flowchart, in some cases, the steps shown or described herein can be executed in an order different from that shown herein.

[0032] Figure 1 is a flowchart of a network exception fallback identification method according to an embodiment of the present application, as shown in Figure 1 , the method comprises the following steps:

[0033] Step S102, obtaining the predetermined interface call record in the application detailed record XDR data of the target user, wherein the predetermined interface call record at least includes: N1 / N2 interface call record corresponding to 5G network, N26 interface call record, and S1-MME interface call record corresponding to 4G network.

[0034] Optionally, the application detailed record XDR data in the problem time period can be collected according to the user permanent identifier SUPI or the mobile user international number MSISDN, specifically including the signaling XDR call record (N1 / N2, N26 interface call record) of 5G independent network group (i.e. 5G dedicated network mode, 5G SA, 5G Standalone) and the signaling XDR call record (S1-MME interface call record) of 4G.

[0035] Step S104, based on the context request record included in the N26 interface log, the tracking area update record in the S1-MME interface log, and the user terminal context release record in the N1 / N2 interface log, determine the first signaling flow, wherein the first signaling flow is used to indicate the signaling flow of switching from 5G network to 4G network corresponding to non-evolved packet system fallback in network idle state.

[0036] It should be noted that in the scenario of deploying N26 interface by 5G core network, each 4G / 5G interoperation will form an N26 interface log record, and the user falling back from 5G to 4G belongs to 4G / 5G interoperation, which corresponds to an N26 interface log record. The fall back from 5G to 4G includes 5G moving to 4G in network idle state and 5G moving to 4G in network connection state. The 5G moving to 4G in network idle state generates a context request record Context Request record of an N26 interface log. Therefore, based on the context request record Context Request record, combined with the N1 / N2 interface log and the S1-MME interface log, the 4G / 5G interoperation is further distinguished, and thus the signaling flow of switching from 5G network to 4G network corresponding to non-evolved packet system fallback in network idle state (i.e. the first signaling flow) is accurately obtained.

[0037] In an optional embodiment, the determination of the first signaling flow based on the context request record included in the N26 interface log, the tracking area update record in the S1-MME interface log, and the user terminal context release record in the N1 / N2 interface log comprises: determining a third signaling flow based on the context request record included in the N26 interface log and the tracking area update record in the S1-MME interface log, wherein the third signaling flow is used to indicate the signaling flow of switching from 5G network to 4G network in network idle state; determining the first signaling flow from the third signaling flow based on the user terminal context release record in the N1 / N2 interface log.

[0038] By the above method, the signaling flow of 5G moving to 4G in the network idle state caused by non-evolved packet system fallback EPS Fallback is identified in the context request record of the N26 interface bill mentioned above. The context request record of the N26 interface bill corresponds to three signaling flows: evolved packet system fallback EPS Fallback, 5G moving to 4G in the network idle state caused by non-evolved packet system fallback EPS Fallback, and 4G moving to 5G in the network idle state, which need to be identified. First, the tracking area update record TAU record is found in the S1-MME interface bill mentioned above. According to the tracking area update record TAU record, the corresponding signaling flow is determined to be the third signaling flow of 5G moving to 4G in the network idle state from the context request record included in the N26 interface bill. It can be understood that the third signaling flow obtained at this time includes the case of 5G moving to 4G caused by network idle state evolved packet system fallback EPS Fallback. Therefore, it is necessary to further combine the user terminal context release record UE Context Release record in the N1 / N2 interface bill to exclude the case of 5G moving to 4G caused by network idle state evolved packet system fallback EPS Fallback from the third signaling flow, and finally obtain the signaling flow corresponding to non-evolved packet system fallback EPS Fallback from 5G network to 4G network in the network idle state (i.e. the first signaling flow).

[0039] In an optional embodiment, determining the third signaling flow based on the context request record included in the N26 interface bill and the tracking area update record in the S1-MME interface bill includes: determining whether there is a first context request record in the context request record included in the N26 interface bill and the tracking area update record. The record time difference is less than a preset first difference threshold; in the case that the first context request record exists in the context request record included in the N26 interface bill, and the recording start time of the tracking area update record is earlier than the recording start time of the tracking area update record, and the recording end time of the tracking area update record is later than the recording end time of the first context request record, the signaling flow corresponding to the first context request record is taken as the third signaling flow.

[0040] Optionally, first, the tracking area update (TAU) record is found in the S1-MME interface message, and a first context request record is selected from the context request records included in the N26 interface message, wherein the first context request record is the context request record included in the N26 interface message that is closest in time to the TAU record, has a later start time and an earlier end time. Then, it is determined that the signaling procedure corresponding to the first context request record is the 5G mobile to 4G in the network idle state (i.e., the third signaling procedure), and the above operation is equivalent to eliminating the signaling procedure of 4G mobile to 5G in the network idle state from the context request records.

[0041] In an optional embodiment, the first signaling procedure is determined from the third signaling procedure based on the user terminal context release record in the N1 / N2 interface message, including: obtaining the request reason type and the request reason value corresponding to the user terminal context release record; and determining the first signaling procedure from the third signaling procedure based on the user terminal context release record in the N1 / N2 interface message, the request reason type, and the request reason value.

[0042] It can be understood that, by searching for the user terminal context release record (UE Context Release record) in the N1 / N2 interface message and according to the request reason type and the request reason value corresponding to the user terminal context release record (UE Context Release record), the signaling procedure corresponding to the evolved packet system fall back (EPS Fallack) part can be determined from the signaling procedure of 5G mobile to 4G in the network idle state (i.e., the third signaling procedure), and the signaling procedure corresponding to the evolved packet system fall back (EPS Fallack) part existing in the third signaling procedure is eliminated, thereby obtaining the first signaling procedure corresponding to the non-evolved packet system fall back (EPS Fallack) part.

[0043] In an optional embodiment, the first signaling flow is determined from the third signaling flow based on the user terminal context release record, the request cause type, and the request cause value in the N1 / N2 interface message, including: determining whether there is a second context request record in the context request record corresponding to the third signaling flow, which has a record time difference with the user terminal context release record less than a preset second difference threshold; in the case that the second context request record exists in the context request record corresponding to the third signaling flow, and the record start time of the user terminal context release record is earlier than the start record time of the second context request record, the request cause type is a radio network cause, and the request cause value is a preset value, the signaling flow corresponding to the second context request record is taken as a fourth signaling flow, wherein the fourth signaling flow is used to indicate a signaling flow corresponding to the 5G network switching to the 4G network by the evolved packet system fall back in the network idle state; and the fourth signaling flow in the third signaling flow is removed to obtain the first signaling flow.

[0044] In the above manner, after obtaining the signaling flow (i.e., the third signaling flow) of switching from the 5G network to the 4G network in the network idle state, the signaling flow (i.e., the fourth signaling flow) corresponding to the evolved packet system fall back part needs to be further determined. The fourth signaling flow satisfies the following conditions: (1) the record time of the corresponding user terminal context request Context Request record (i.e., the second context request record) is the closest to the record time of the user terminal context release UE Context Release record, and the start record time of the user terminal context release UE Context Release record is earlier than the start record time of the second context request record. (2) The field Request Cause Type of the user terminal context release UE Context Release record is 1 (the request cause type is “Radio Network Layer, Radio Network Layer”), and the field Request Cause is 36 (i.e., the request cause value is “ims-voice-eps-fallback-or-rat-fallback-triggered”). The signaling flow corresponding to the evolved packet system fall back part in the third signaling flow is removed, i.e., the first signaling flow corresponding to the non-evolved packet system fall back part in the network idle state is obtained.

[0045] In step S106, the second signaling procedure is determined based on the relocation request record included in the N26 interface log and the N2 interface switching-out procedure record in the N1 / N2 interface log. The second signaling procedure is used to indicate the signaling procedure of switching from the 5G network to the 4G network corresponding to the non-EPS fallback in the network connection state.

[0046] It should be noted that in the scenario of deploying the N26 interface by the 5G core network, each 4G / 5G interoperation will form an N26 interface log record. The user falling back from the 5G network to the 4G network belongs to the 4G / 5G interoperation, and corresponds to an N26 interface log record. The user falling back from the 5G network to the 4G network includes the 5G moving to the 4G in the network idle state and the 5G moving to the 4G in the network connection state. The 5G moving to the 4G in the network connection state generates a Forward Relocation Request record of the N26 interface log. Therefore, based on the Forward Relocation Request record, in combination with the N1 / N2 interface log, the 4G / 5G interoperation is further distinguished, and the signaling procedure of switching from the 5G network to the 4G network corresponding to the non-EPS fallback in the network connection state (i.e., the second signaling procedure) is accurately obtained.

[0047] In an optional embodiment, the second signaling procedure is determined based on the relocation request record included in the N26 interface log and the N2 interface switching-out procedure record in the N1 / N2 interface log, including: determining a network switching type corresponding to the N2 interface switching-out procedure record; and determining the second signaling procedure based on the relocation request record included in the N26 interface log, the N2 interface switching-out procedure record in the N1 / N2 interface log, and the network switching type.

[0048] By the above manner, the network switching type corresponding to the N2 HO OUT record of the N2 interface handover-out procedure is recorded in the N26 interface call record, and the second signaling procedure (i.e., the second signaling procedure) of the 5G mobile to 4G in the network connection state is identified in the Forward Relocation Request record of the N26 interface call record. In an optional embodiment, the second signaling procedure is determined based on the Forward Relocation Request record included in the N26 interface call record, the N2 interface handover-out procedure in the N1 / N2 interface call record, and the network switching type, including: determining whether there is a first relocation request record with a record time difference between the Forward Relocation Request record included in the N26 interface call record and the N2 interface handover-out procedure less than a preset third difference threshold; when the first relocation request record exists in the Forward Relocation Request record included in the N26 interface call record, and the record start time of the N2 interface handover-out procedure is earlier than the record start time of the first relocation request record, the network switching type is 5G network switching to 4G network, and the signaling procedure corresponding to the first relocation request record is taken as the second signaling procedure.

[0049] By the above manner, the network switching type corresponding to the N2 HO OUT record of the N2 interface handover-out procedure is recorded in the N26 interface call record, and the second signaling procedure (i.e., the second signaling procedure) of the 5G mobile to 4G in the network connection state is identified in the Forward Relocation Request record of the N26 interface call record. In an optional embodiment, the second signaling procedure is determined based on the Forward Relocation Request record included in the N26 interface call record, the N2 interface handover-out procedure in the N1 / N2 interface call record, and the network switching type, including: determining whether there is a first relocation request record with a record time difference between the Forward Relocation Request record included in the N26 interface call record and the N2 interface handover-out procedure less than a preset third difference threshold; when the first relocation request record exists in the Forward Relocation Request record included in the N26 interface call record, and the record start time of the N2 interface handover-out procedure is earlier than the record start time of the first relocation request record, the network switching type is 5G network switching to 4G network, and the signaling procedure corresponding to the first relocation request record is taken as the second signaling procedure.

[0050] In step S108, the network abnormal fallback identification result of the target user is obtained according to the first signaling procedure and the second signaling procedure.

[0051] Based on the acquired first signaling flow corresponding to non-evolved packet system fall back EPS Fallback in a network idle state and the second signaling flow corresponding to 5G network switching to 4G network in a network connection state, all possible abnormal events of 4G fall back related to 5G wireless network quality are screened out, and a network abnormal fall back identification result is obtained. The time, cell and other field information of the relevant key bill record corresponding to the above network abnormal fall back identification result can be used as the basis for problem tracing.

[0052] It should be noted that the embodiments of the present application are aimed at the scenario of 5G core network 5GC side based on N26 interface and wireless side configured for blind redirection to implement evolved packet system fall back EPS Fallback, and abnormal phenomena of 5G fall back 4G caused by poor coverage quality or improper configuration of 5G wireless network are identified by using application detailed record XDR data, and the factors of 5G fall back 4G caused by normal implementation of evolved packet system fall back EPS Fallback are excluded, so as to accurately trace the 5G wireless quality problem.

[0053] Through the above steps S102 to S108, the purpose of effectively excluding the case of 5G network fall back to 4G network caused by evolved packet system fall back EPS Fallback mode and accurately identifying network abnormal fall back can be achieved, so as to realize the technical effects of improving the accuracy of network abnormal fall back identification and accurately tracing the 5G network quality problem, and further solve the technical problem of low accuracy of network abnormal fall back identification caused by the fact that the 5G network fall back to 4G network caused by evolved packet system fall back EPS Fallback mode cannot be excluded when the network abnormal fall back is performed in the related art.

[0054] Based on the above embodiments and optional embodiments, the present application proposes an optional implementation, Figure 2 is a flow chart of an optional network abnormal fall back identification method according to an embodiment of the present application, as shown in the figure, the method comprises: Figure 2

[0055] ​Step S1, collect the 5G standalone network group (i.e. 5G dedicated network mode, 5G SA, 5G Standalone) signaling XDR bill (N1 / N2, N26 interface bill) and 4G signaling XDR bill (S1-MME interface bill) in the problem time period according to the user permanent identifier SUPI or the mobile user international number MSISDN. First, filter the context request record Context Request record and the forward relocation request record Forward Relocation Request record of the N26 interface bill, that is, filter all 4G / 5G interoperation history records. Then, in combination with the N1 / N2 interface bill and the S1-MME interface bill, further distinguish these 4G / 5G interoperations. The distinguishing methods are described below according to two cases of 5G moving to 4G in the network idle state and 5G moving to 4G in the network connection state.

[0056] Step S2, distinguish the signaling flow of 5G moving to 4G in the network idle state caused by the non-evolved packet system fallback EPS Fallback (i.e. the first signaling flow) in the context request record Context Request record of the N26 interface bill. The signaling flow corresponding to the Context Request record of the N26 interface bill has three types: evolved packet system fallback EPS Fallack, 5G moving to 4G in the network idle state caused by the non-evolved packet system fallback EPS Fallback, and 4G moving to 5G in the network idle state, which need to be distinguished into the following sub-steps:

[0057] Step S21, exclude the signaling flow of 4G moving to 5G in the network idle state to obtain the third signaling flow of 5G moving to 4G in the network idle state. In the above S1-MME interface bill, find the tracking area update record TAU record, which meets the condition that it is closest in time to the context request Context Request record of the above N26 interface bill, starts earlier and ends later, and then it is determined that the signaling flow corresponding to the context request Context Request record is the third signaling flow of 5G moving to 4G in the network idle state. It can be understood that the third signaling flow obtained at this time includes the case of 5G moving to 4G in the network idle state caused by the evolved packet system fallback EPS Fallback, so it is necessary to further combine the user terminal context release record UE Context Release record in the N1 / N2 interface bill.

[0058] Step S22, the fourth signaling flow corresponding to the evolved packet system fall back (EPS Fallack) is excluded, and the first signaling flow of 5G moving to 4G in the network idle state caused by the evolved packet system fall back (EPS Fallack) is obtained. In the above-mentioned N1 / N2 interface log, the user terminal context release record (UE Context Release) is searched, and if the following two conditions are met, the signaling flow corresponding to the context request record (Context Request) determined in step S21 is the evolved packet system fall back (EPS Fallack) (i.e. the fourth signaling flow). (1) The user terminal context release record (UE Context Release) is closest in recording time and starts earlier than the user terminal context request record (Context Request) determined in step S21 as 5G idle state moving to 4G (i.e. the third signaling flow). (2) The field Request Cause Type of the user terminal context release record (UE Context Release) is 1 (the request cause type is "Radio Network Layer, Radio Network Layer"), and the field Request Cause is 36 (i.e. the request cause value is "ims-voice-eps-fallback-or-rat-fallback-triggered").

[0059] Step S23, after step S21 and step S22, the signaling flow of 4G moving to 5G in the network idle state and the fourth signaling flow corresponding to the evolved packet system fall back (EPS Fallack) are excluded from the context request record (Context Request) in the N26 interface log in turn, and the signaling flow corresponding to the remaining context request record (Context Request) is the signaling flow of 5G moving to 4G in the network idle state caused by the evolved packet system fall back (EPS Fallack) (i.e. the first signaling flow).

[0060] Step S3, in the above-mentioned relocation request record (Forward Relocation Request) of the N26 interface log, the signaling flow of 5G moving to 4G in the network connection state (i.e. the second signaling flow) is identified.

[0061] In the N1 / N2 interface session in the above, the N2 interface handover out flow N2 HO OUT record is searched, and if the following two conditions are met simultaneously, it is determined that the signaling flow corresponding to the relocation request record Forward Relocation Request record is the second signaling flow of 5G moving to 4G in the network connection state: 1. The N2 interface handover out flow N2 HO OUT record is closest in recording time and starts recording earlier relative to the relocation request record Forward Relocation Request record of the N26 interface session. 2. The field Keyword of the N2 interface handover out flow N2 HO OUT record is 2 (indicating that the handover type is 5GStoEPS, that is, 5G network is switched to 4G network).

[0062] In step S4, based on the first signaling flow corresponding to the evolved packet system fallback EPS Fallack part in the network idle state and the second signaling flow corresponding to the evolved packet system fallback EPS Fallack in the network connection state, all abnormal events of falling back to 4G related to the quality of the 5G wireless network are screened out, and a network abnormal fallback identification result is obtained. The time, cell and other field information of the related key session record corresponding to the network abnormal fallback identification result can be used as the basis for problem tracing.

[0063] It should be noted that the embodiments of the present application are aimed at abnormal events of 5G falling back to 4G (the specific application scenario is: 5GC side based on N26 interface and wireless side configured for blind redirection to realize EPS Fallback service), and through comprehensive analysis of the signaling XDR session (N1 / N2 interface session, N26 interface session) of 5G SA and the signaling XDR session (S1-MME interface session) of 4G, abnormal events of falling back to 4G related to wireless network quality are identified, and single user detailed session data is obtained. In addition, the present application specially distinguishes the signaling flow of evolved packet system fallback EPS Fallack in the XDR session, and distinguishes the abnormal events of falling back to 4G related to wireless network quality caused by the evolved packet system fallback EPS Fallack (not caused by non-wireless network quality problems) and the abnormal events of falling back to 4G related to wireless network quality, so that the maintenance and optimization personnel can first exclude the factors of evolved packet system fallback EPS Fallack and focus on the wireless network quality related problems causing 5G falling back to 4G.

[0064] As an optional embodiment, Figure 3 is a schematic diagram of an S1-MME interface session and an S1-MME interface original signaling according to an embodiment of the present application, as shown in Figure 3As shown, the tracking area update record TAU record at 11:53:33 in the S1-MME interface log corresponds to the original signaling INITIAL UE MESSAGE, Tracking area update accept, and Tracking area update complete.

[0065] Figure 4 is a kind of optional context request record Context Request record according to the embodiment of the present application and original signaling, as shown in Figure 4 As shown, after the tracking area update record TAU record, the context request record Context Request record appears, which corresponds to the original signaling context request record Context Request (the field RAT Type is EUTRAN, i.e., the context request record Context Request initiated by the S1-MME interface log of 4G). Moreover, the end time of the tracking area update record TAU record is 11:53:33.344, which is greater than the time 11:53:33.210 of the context request record Context Request record.

[0066] Figure 5 is a kind of optional user terminal context release record UE Context Release according to the embodiment of the present application and original signaling, as shown in Figure 5 As shown, in order to distinguish whether the 5G idle state moves to 4G caused by the evolved packet system fallback EPSFallback, it is necessary to further check the UE Context Release record before and closest in time to the context request record Context Request record. The user terminal context release record UE Context Release record (the field Request Cause Type=1, Request Cause=36) corresponds to the original signaling UE CONTEXT RELEASE REQUEST (the request cause value is IMS voice EPSfallback or RAT fallback Triggered).

[0067] Figure 6 is a kind of optional N2 interface handover out process N2 HO OUT according to the embodiment of the present application and original signaling, as shown in Figure 6As shown, the N2 interface handover out flow N2 HOOut record (the field Keyword = 2, indicating that the handover type is 5GstoEPS, that is, 5G network is handed over to 4G network) of 16:34:17 in the N1 / N2 interface call record corresponds to the original signaling HandoverRequired (the field HandoverType is fivegs-to-eps).

[0068] It should be noted that the embodiments of the present application are applied to the application scenario of evolved packet system fallback EPS Fallback based on N26 interface and wireless side configured as blind redirection, and utilize the signaling XDR call record (N1 / N2 interface call record, N26 interface call record) of 5G SA and the signaling XDR call record (S1-MME interface call record) of 4G to analyze and identify the abnormal event of 5G fallback 4G from the single user dimension detailed level. The 4 / 5G interoperation event is preliminarily screened through the N26 interface call record; the 5G idle state moving to 4G is identified in combination with the N26 and S1-MME interface call records; the evolved packet system fallback EPS Fallback and 5G moving to 4G in the network connection state are identified in combination with the N26 interface call record and the N1 / N2 interface call record, the factors of EPS Fallback are excluded, the abnormal event of single user 5G fallback 4G related to wireless network quality problem (5G moving to 4G in the network idle state and 5G moving to 4G in the network connection state) is screened out, and a method capable of historical backtracking is provided for positioning the 5G wireless network problem causing the fallback 4G.

[0069] In the embodiment, a network abnormal fallback identification device is also provided, which is used for implementing the above-mentioned embodiments and preferred embodiments, and details are not repeated. As used below, the term "module" "device" can be a combination of software and / or hardware that implements a predetermined function. Although the device described in the following embodiments is preferably implemented in software, hardware, or a combination of software and hardware is also possible and is contemplated.

[0070] According to the embodiments of the present application, a device embodiment for implementing the above-mentioned network abnormal fallback identification method is also provided, Figure 7 is a structural schematic diagram of a network abnormal fallback identification device according to the embodiments of the present application, as Figure 7 As shown, the network abnormal fallback identification device comprises a first acquisition module 700, a first determination module 702, a second determination module 704, and a second acquisition module 706.

[0071] The first obtaining module 700 is configured to obtain a predetermined interface call record in application detailed record (XDR) data of a target user, wherein the predetermined interface call record at least includes: an N1 / N2 interface call record corresponding to a 5G network, an N26 interface call record, and an S1-MME interface call record corresponding to a 4G network;

[0072] The first determining module 702 is connected to the first obtaining module 700 and is configured to determine a first signaling flow based on a context request record included in the N26 interface call record, a tracking area update record in the S1-MME interface call record, and a user terminal context release record in the N1 / N2 interface call record, wherein the first signaling flow is used to indicate a signaling flow corresponding to a 5G network to 4G network handover in a network idle state and a non evolved packet system (non- EPS) fallback.

[0073] The second determining module 704 is connected to the first determining module 702 and is configured to determine a second signaling flow based on a relocation request record included in the N26 interface call record and an N2 interface handover out flow record in the N1 / N2 interface call record, wherein the second signaling flow is used to indicate a signaling flow corresponding to a 5G network to 4G network handover in a network connection state and a non evolved packet system (non- EPS) fallback.

[0074] The second obtaining module 706 is connected to the second determining module 704 and is configured to obtain a network abnormal fallback identification result of the target user according to the first signaling flow and the second signaling flow.

[0075] In the embodiment of the present application, by setting the first obtaining module 700, the predetermined interface call record in the application detailed record XDR data of the target user is obtained, wherein the predetermined interface call record at least includes: N1 / N2 interface call record corresponding to the 5G network, N26 interface call record, and S1-MME interface call record corresponding to the 4G network; the first determining module 702 connected to the first obtaining module 700 is used to determine the first signaling process based on the context request record included in the N26 interface call record, the tracking area update record in the S1-MME interface call record, and the user terminal context release record in the N1 / N2 interface call record, wherein the first signaling process is used to indicate the signaling process of switching from the 5G network to the 4G network corresponding to the non-evolved packet system fallback in the network idle state; the second determining module 704 connected to the first determining module 702 is used to determine the second signaling process based on the relocation request record included in the N26 interface call record and the N2 interface handover out process record in the N1 / N2 interface call record, wherein the second signaling process is used to indicate the signaling process of switching from the 5G network to the 4G network corresponding to the non-evolved packet system fallback in the network connection state; the second obtaining module 706 connected to the second determining module 704 is used to obtain the network abnormal fallback identification result of the target user according to the first signaling process and the second signaling process, so as to effectively exclude the case of 5G network fallback to 4G network caused by evolved packet system fallback EPS Fallback mode, accurately identify the network abnormal fallback, and achieve the technical effects of improving the network abnormal fallback identification accuracy and accurately tracing the 5G network quality problem, thereby solving the technical problem of low network abnormal fallback identification accuracy caused by the case of 5G network fallback to 4G network caused by evolved packet system fallback EPS Fallback mode when the network abnormal fallback is performed in the related art.

[0076] It should be noted that each of the above modules can be implemented by software or hardware. For example, for the latter, the modules can be located in the same processor or in different processors in any combination.

[0077] It should be noted that the first obtaining module 700, the first determining module 702, the second determining module 704, and the second obtaining module 706 correspond to steps S102 to S108 in the embodiment, and the modules have the same instances and application scenarios as the corresponding steps, but are not limited to the disclosed content in the above embodiment. It should be noted that the modules as part of the device can run in a computer terminal.

[0078] It should be noted that the optional or preferred embodiments of the present embodiment can refer to the related description in the embodiments, which will not be repeated here.

[0079] The network anomaly fallback identification apparatus described above can further include a processor and a memory, and the first obtaining module 700, the first determining module 702, the second determining module 704, the second obtaining module 706, etc. are stored in the memory as program modules, and the processor executes the program modules stored in the memory to realize the corresponding functions.

[0080] The processor includes a core, and the core retrieves the corresponding program modules from the memory. The core can be one or more. The memory can include a non-persistent memory in a computer readable medium, a random access memory (RAM) and / or a non-volatile memory such as a read-only memory (ROM) or a flash memory (flash RAM), and the memory includes at least one memory chip.

[0081] According to the embodiments of the present application, an embodiment of a non-volatile storage medium is also provided. Optionally, in the present embodiment, the non-volatile storage medium includes a stored program, wherein the program controls the device where the non-volatile storage medium is located to execute any of the network anomaly fallback identification methods when the program is running.

[0082] Optionally, in the present embodiment, the non-volatile storage medium can be located in any one of the computer terminals in the computer terminal group in the computer network, or in any one of the mobile terminals in the mobile terminal group, and the non-volatile storage medium includes a stored program.

[0083] Optionally, the program running time controls the device where the nonvolatile storage medium is located to perform the following functions: obtaining predetermined interface call records in the application detailed record (XDR) data of the target user, wherein the predetermined interface call records at least include: N1 / N2 interface call records corresponding to the 5G network, N26 interface call records, and S1-MME interface call records corresponding to the 4G network; determining a first signaling flow based on the context request record included in the N26 interface call records, the tracking area update record in the S1-MME interface call records, and the user terminal context release record in the N1 / N2 interface call records, wherein the first signaling flow is used to indicate a signaling flow of switching from the 5G network to the 4G network corresponding to the non-evolved packet system fallback in the network idle state; determining a second signaling flow based on the relocation request record included in the N26 interface call records and the N2 interface handover out flow record in the N1 / N2 interface call records, wherein the second signaling flow is used to indicate a signaling flow of switching from the 5G network to the 4G network corresponding to the non-evolved packet system fallback in the network connection state; and obtaining the network abnormal fallback identification result of the target user according to the first signaling flow and the second signaling flow.

[0084] According to the embodiments of the present application, an embodiment of a processor is also provided. Optionally, in the embodiment, the processor is used to run a program, wherein the program performs any of the network abnormal fallback identification methods when running.

[0085] According to the embodiments of the present application, an embodiment of a computer program product is also provided, which is adapted to execute the program initialized with the steps of any of the network abnormal fallback identification methods when executed on a data processing device.

[0086] Optionally, the computer program product described above, when executed on a data processing device, is adapted to execute the program steps of: obtaining predetermined interface call records in application detailed record XDR data of a target user, wherein the predetermined interface call records at least include: N1 / N2 interface call records corresponding to a 5G network, N26 interface call records, and S1-MME interface call records corresponding to a 4G network; determining a first signaling flow based on context request records included in the N26 interface call records, tracking area update records in the S1-MME interface call records, and user terminal context release records in the N1 / N2 interface call records, wherein the first signaling flow is used to indicate a signaling flow corresponding to switching from the 5G network to the 4G network in a network idle state under non-evolved packet system fallback; determining a second signaling flow based on relocation request records included in the N26 interface call records and N2 interface handover out flow records in the N1 / N2 interface call records, wherein the second signaling flow is used to indicate a signaling flow corresponding to switching from the 5G network to the 4G network in a network connection state under non-evolved packet system fallback; and obtaining a network abnormal fallback identification result of the target user according to the first signaling flow and the second signaling flow.

[0087] An electronic device is provided, which includes a processor, a memory, and a program stored in the memory and executable on the processor. When the processor executes the program, the following steps are implemented: obtaining predetermined interface call records in application detailed record XDR data of a target user, wherein the predetermined interface call records at least include: N1 / N2 interface call records corresponding to a 5G network, N26 interface call records, and S1-MME interface call records corresponding to a 4G network; determining a first signaling flow based on context request records included in the N26 interface call records, tracking area update records in the S1-MME interface call records, and user terminal context release records in the N1 / N2 interface call records, wherein the first signaling flow is used to indicate a signaling flow corresponding to switching from the 5G network to the 4G network in a network idle state under non-evolved packet system fallback; determining a second signaling flow based on relocation request records included in the N26 interface call records and N2 interface handover out flow records in the N1 / N2 interface call records, wherein the second signaling flow is used to indicate a signaling flow corresponding to switching from the 5G network to the 4G network in a network connection state under non-evolved packet system fallback; and obtaining a network abnormal fallback identification result of the target user according to the first signaling flow and the second signaling flow.

[0088] The above sequence numbers of embodiments of the present application are only for description, and do not represent advantages or disadvantages of the embodiments.

[0089] In the above-mentioned embodiments of the present application, the description of each embodiment focuses on different aspects, and the parts not described in detail in a certain embodiment can be referred to the relevant description of other embodiments.

[0090] In several embodiments provided in the present application, it should be understood that the disclosed technology can be implemented in other ways. Among them, the above-mentioned device embodiments are only schematic, for example, the division of the above-mentioned modules can be a logical function division, and actual implementation can have another division mode, for example, a plurality of modules or components can be combined or integrated into another system, or some features can be ignored or not executed. In addition, the coupling or direct coupling or communication connection between the displayed or discussed each other can be through some interface, indirect coupling or communication connection between modules or modules, which can be electrical or other forms.

[0091] The above-mentioned modules described as separate components can be or can not be physically separated, and the components displayed as modules can be or can not be physical modules, that is, they can be located in one place, or they can be distributed to a plurality of modules. Part or all of the modules can be selected according to actual needs to achieve the purpose of the present embodiment scheme.

[0092] In addition, the functional modules in each embodiment of the present application can be integrated in a processing module, or each module can exist physically, or two or more modules can be integrated in one module. The above-mentioned integrated module can be realized in the form of hardware or in the form of software functional module.

[0093] The above-mentioned integrated module, if realized in the form of software functional module and sold or used as an independent product, can be stored in a computer readable non-volatile storage medium. Based on this understanding, the technical scheme of the present application or the part of the present application which essentially contributes to the prior art or the whole or part of the technical scheme can be embodied in the form of software product, which is stored in a non-volatile storage medium, including a plurality of instructions for making a computer device (which can be a personal computer, a server or a network device, etc.) execute all or part of the steps of the method of each embodiment of the present application. The above-mentioned non-volatile storage medium includes: U disk, read-only memory (ROM, Read-Only Memory), random access memory (RAM, Random Access Memory), mobile hard disk, magnetic disk or optical disk and various program code storage media.

[0094] The above merely is the preferred embodiment of the present application, it should be pointed out that, for ordinary skilled in the art, without departing from the principles of the present application, can also make a number of improvements and refinements, these improvements and refinements should also be considered as the protection scope of the present application.

Claims

1. A network anomaly fallback identification method, characterized in that, The method comprises the following steps: acquire a predetermined interface call record in application detailed record (XDR) data of a target user, wherein the predetermined interface call record at least comprises: N1 / N2 interface call record corresponding to a 5G network, N26 interface call record, and S1-MME interface call record corresponding to a 4G network; determine a first signaling flow based on a context request record included in the N26 interface call record, a tracking area update record in the S1-MME interface call record, and a user terminal context release record in the N1 / N2 interface call record, wherein the first signaling flow is used to indicate a signaling flow of switching from the 5G network to the 4G network corresponding to non-evolved packet system fallback in a network idle state; determine a second signaling flow based on a relocation request record included in the N26 interface call record and an N2 interface handover out flow record in the N1 / N2 interface call record, wherein the second signaling flow is used to indicate a signaling flow of switching from the 5G network to the 4G network corresponding to non-evolved packet system fallback in a network connection state; obtain a network abnormal fallback identification result of the target user according to the first signaling flow and the second signaling flow.

2. The method of claim 1, wherein, The method of determining the first signaling flow based on the context request record included in the N26 interface call record, the tracking area update record in the S1-MME interface call record, and the user terminal context release record in the N1 / N2 interface call record comprises the following steps: determine a third signaling flow based on the context request record included in the N26 interface call record and the tracking area update record in the S1-MME interface call record, wherein the third signaling flow is used to indicate a signaling flow of switching from the 5G network to the 4G network in a network idle state; determine the first signaling flow from the third signaling flow based on the user terminal context release record in the N1 / N2 interface call record.

3. The method of claim 2, wherein, The method of determining the third signaling flow based on the context request record included in the N26 interface call record and the tracking area update record in the S1-MME interface call record comprises the following steps: determine whether there is a first context request record with a record time difference between the context request record included in the N26 interface call record and the tracking area update record less than a preset first difference threshold value; in the case that the first context request record exists in the context request record included in the N26 interface call record, and a record start time of the tracking area update record is earlier than a record start time of the first context request record and a record end time of the tracking area update record is later than a record end time of the first context request record, the signaling flow corresponding to the first context request record is taken as the third signaling flow.

4. The method of claim 2, wherein, The method of determining the first signaling flow from the third signaling flow based on the user terminal context release record in the N1 / N2 interface call record comprises the following steps: acquire a request cause type and a request cause value corresponding to the user terminal context release record; Determine the first signaling procedure from the third signaling procedure based on the user terminal context release record in the N1 / N2 interface log, the request cause type, and the request cause value.

5. The method of claim 4, wherein, The determining the first signaling procedure from the third signaling procedure based on the user terminal context release record in the N1 / N2 interface log, the request cause type, and the request cause value comprises: determining whether there is a second context request record with a record time difference between the user terminal context release record and the second context request record less than a preset second difference threshold in the context request record corresponding to the third signaling procedure; in a case where the second context request record exists in the context request record corresponding to the third signaling procedure, the record start time of the user terminal context release record is earlier than the start record time of the second context request record, the request cause type is a radio network cause, and the request cause value is a preset value, regarding a signaling procedure corresponding to the second context request record as a fourth signaling procedure, wherein the fourth signaling procedure is used to indicate a signaling procedure corresponding to an evolved packet system fall back from a 5G network to a 4G network in a network idle state; and removing the fourth signaling procedure in the third signaling procedure to obtain the first signaling procedure.

6. The method of claim 1, wherein, The determining the second signaling procedure based on the relocation request record included in the N26 interface log and the N2 interface switching out procedure record in the N1 / N2 interface log comprises: determining a network switching type corresponding to the N2 interface switching out procedure record; The determining the second signaling procedure based on the relocation request record included in the N26 interface log, the N2 interface switching out procedure record in the N1 / N2 interface log, and the network switching type.

7. The method of claim 6, wherein, The determining the second signaling procedure based on the relocation request record included in the N26 interface log, the N2 interface switching out procedure record in the N1 / N2 interface log, and the network switching type comprises: determining whether there is a first relocation request record with a record time difference between the N2 interface switching out procedure and the first relocation request record less than a preset third difference threshold in the relocation request record included in the N26 interface log; in a case where the first relocation request record exists in the relocation request record included in the N26 interface log, the record start time of the N2 interface switching out procedure is earlier than the record start time of the first relocation request record, and the network switching type is a 5G network switching to a 4G network, regarding a signaling procedure corresponding to the first relocation request record as the second signaling procedure.

8. A network anomaly fallback identification apparatus, characterized by, comprise: a first acquisition module configured to acquire predetermined interface logs in application detailed record (XDR) data of a target user, wherein the predetermined interface logs at least comprise: an N1 / N2 interface log corresponding to a 5G network, an N26 interface log, and an S1-MME interface log corresponding to a 4G network; The first determining module is configured to determine a first signaling procedure based on a context request record included in the N26 interface log, a tracking area update record in the S1-MME interface log, and a user terminal context release record in the N1 / N2 interface log, wherein the first signaling procedure is used to indicate a signaling procedure corresponding to non-evolved packet system fallback from the 5G network to the 4G network in a network idle state. The second determining module is configured to determine a second signaling procedure based on a relocation request record included in the N26 interface log and an N2 interface handover out procedure record in the N1 / N2 interface log, wherein the second signaling procedure is used to indicate a signaling procedure corresponding to non-evolved packet system fallback from the 5G network to the 4G network in a network connection state. The second obtaining module is configured to obtain a network abnormal fallback identification result of the target user according to the first signaling procedure and the second signaling procedure.

9. A non-volatile storage medium, comprising: The non-volatile storage medium stores a plurality of instructions, and the instructions are adapted to be loaded and executed by the processor to implement the network abnormal fallback identification method in any one of claims 1 to 7.

10. An electronic device, comprising: The apparatus includes one or more processors and a memory configured to store one or more programs, wherein the one or more programs, when executed by the one or more processors, cause the one or more processors to implement the network abnormal fallback identification method in any one of claims 1 to 7.

Images