Latency segment monitoring method and apparatus, electronic device, and computer program product

Abstract

The application relates to the technical field of mobile communication, and provides a time delay segmentation monitoring method and device, electronic equipment and computer program product. The method comprises the following steps: determining whether a 5G call service flow is a service behavior of a same call flow of a same user based on an interface signaling code stream; if yes, performing association on service flow data corresponding to a service interface of the 5G call service flow, associating a formed calling bill record and a called bill record, and obtaining a comprehensive bill record; performing time delay segmentation delimitation on an end-to-end 5G voice call flow and a call fallback flow respectively; determining the occupation time of each sub-stage time delay segment respectively, and backfilling the occupation time into the comprehensive bill record respectively. The time delay segmentation monitoring method provided in the application embodiment can solve the technical problem of dividing time delay segments according to the phase characteristics of signaling interaction, monitor network problems of each time delay segment, and improve network operation efficiency.

Description

Technical Field

[0001] This application relates to the field of mobile communication technology, specifically to a delay segmentation monitoring method, device, electronic device, and computer program product. Background Technology

[0002] Currently, the numerous network elements in 5G networks result in a complex 5G network topology. There are two main methods for implementing voice calls in 5G standalone networks: EPSFB and VoNR. EPSFB involves falling back from 5G to 4G during a voice call, using 4G VoLTE to complete the call, and then resuming 5G after the call ends. VoNR, on the other hand, uses the 5G standalone network to carry the voice call service. However, both methods face challenges due to the large number and types of network elements involved, leading to complex service triggering, numerous signaling interactions, complex service processes, and a significant impact on call setup latency. Therefore, latency monitoring is necessary. Currently, the common method for statistical analysis and monitoring latency metrics is to provide user-level call setup latency and dependent network element latency through call detail records (CDRs). However, this only provides a total latency and cannot pinpoint the location of latency delays. Dependent network element latency analysis only tracks the latency of the network element itself and cannot cover the entire end-to-end latency setup process. Furthermore, some network elements handle both voice and internet services simultaneously, making it difficult to accurately distinguish between voice call latency statistics, which has certain limitations.

[0003] In the prior art, a method for processing call delay information is proposed, which determines the delay information of each signaling interface corresponding to the same call, and generates the total delay information corresponding to the call using the delay information of each signaling interface corresponding to the same call.

[0004] The aforementioned prior art has the following disadvantages:

[0005] This scheme calculates the total latency based on the latency information of each signaling interface, but it cannot divide the latency into segments according to the phased characteristics of signaling interaction, which is not conducive to monitoring network problems in each latency segment. Summary of the Invention

[0006] This application provides a latency segmentation monitoring method to solve the technical problem of dividing latency into segments according to the phased characteristics of signaling interaction and monitoring network problems in each latency segment, thereby improving network operation and maintenance efficiency.

[0007] In a first aspect, embodiments of this application provide a delay segmentation monitoring method, including:

[0008] Obtain the interface signaling code stream in the 5G call service process, and determine whether the 5G call service process is the same call process of the same user based on the interface signaling code stream. If so, associate the service process data corresponding to the service interface of the 5G call service process to form the calling call detail record and the called call detail record.

[0009] The calling party's call detail record (CDR) and the called party's call detail record (CDR) are associated and combined to obtain a comprehensive CDR for the 5G call service process.

[0010] The 5G call service process includes an end-to-end 5G voice call process and a call fallback process. The end-to-end 5G voice call process and the call fallback process are segmented and delimited to obtain several sub-stage delay segments.

[0011] The time occupied by each sub-stage delay segment is determined, and the occupied time is filled back into the delay record position corresponding to each sub-stage delay segment in the integrated call detail record.

[0012] In one embodiment, the interface signaling stream includes the N2 interface signaling stream, the N26 interface signaling stream, the S1 interface signaling stream, and the IMS SIP message signaling stream;

[0013] Determining whether a 5G call service process is the same call process of the same user based on the interface signaling code stream includes:

[0014] If the values ​​of AMF UE NGAP ID and RAN UE NGAP ID are the same in the N2 interface signaling stream, and the source TEID, destination TEID, source IP address, destination IP address, source port, and destination port are all unique in the N26 interface signaling stream, and the values ​​of MME UE S1AP ID and eNB UE S1AP ID are the same in the S1 interface signaling stream, and the Call ID is unique in the IMS SIP message signaling stream, then it is determined that the 5G call service process is the same call process of the same user.

[0015] In one embodiment, associating the service process data corresponding to the service interface of the 5G call service process includes:

[0016] In the mobility registration process of the 5G call service process, obtain SUPI and 5G-GUTI, obtain GPSI number of the 5G call service process according to the tuple binding relationship of SUPI and 5G-GUTI, and fill the GPSI number back into each service process of N2 interface and N26 interface.

[0017] In the LTE attach process of the 5G call service process, the IMSI and 4G-GUTI are obtained. The MSISDN number of the 5G call service process is determined according to the tuple binding relationship between the IMSI and 4G-GUTI. The MSISDN number is then filled back into the S1 interface and various service processes in the IMS domain.

[0018] On both the calling and called sides, the business process data corresponding to the business interfaces that have the same interface signaling code stream generation time, the same mobile user number, the same user identification code, and the same ICID information are associated. The ICID information is extracted from the SIP message.

[0019] In one embodiment, associating and combining the calling party's call detail record (CDR) and the called party's CDR includes:

[0020] The calling and called call detail records (CDRs) with the same interface signaling code stream generation time, mobile user number, user identification code, and ICID information are associated and merged.

[0021] In one embodiment, latency segmentation and delimitation are performed on the end-to-end 5G voice call process and the call fallback process, respectively. The latency segmentation and delimitation of the end-to-end 5G voice call process includes:

[0022] Based on the phase characteristics of SIP message interaction and the responsibility division rules between the core network and the radio, the end-to-end 5G voice call process is divided into 12 sub-phase delay segments. The 12 sub-phase delay segments are as follows: calling bearer establishment phase, calling call control phase, IMS addressing phase, called call control phase, called radio establishment phase, called bearer establishment phase, 183 forwarding phase, calling radio establishment phase, calling update phase, update forwarding phase, called update phase, and Ring forwarding phase.

[0023] The start time of the calling bearer establishment phase is the time when the calling SBC receives the INVITE message sent by the calling UE through the Gm interface, and the end time of the calling bearer establishment phase is the first time point, which is the time when the calling S-CSCF receives the first INVITE message sent by the calling SBC through the Mw interface.

[0024] The start time of the calling party's call control phase is the first time point, and the end time of the calling party's call control phase is the second time point. The second time point is the time when the calling party's S-CSCF receives the INVITE message sent by the last TAS from the calling party's side.

[0025] The start time of the IMS addressing phase is the second time point, and the end time of the IMS addressing phase is the third time point. The third time point is the time when the called S-CSCF sends the INVITE message to the first TAS on the called side.

[0026] The start time of the called party's call control phase is the third time point, and the end time of the called party's call control phase is the fourth time point. The fourth time point is the time when the called party's SBC sends the INVITE message to the called party's UE through the Gm interface.

[0027] The start time of the called party's radio establishment phase is the fourth time point, and the end time of the called party's radio establishment phase is the fifth time point. The fifth time point is the time when the called party's SBC receives the 183 message sent by the called party's UE through the Gm interface.

[0028] The start time of the called bearer establishment phase is the fifth time point, and the end time of the called bearer establishment phase is the sixth time point. The sixth time point is the time when the called S-CSCF receives the first 183 message sent by the called SBC through the Mw interface.

[0029] The 183 forwarding phase begins at the sixth time point and ends at the seventh time point. The seventh time point is the time when the calling SBC sends the 183 message to the calling UE through the Mw interface.

[0030] The start time of the calling radio setup phase is the seventh time point, and the end time of the calling radio setup phase is the eighth time point. The eighth time point is the time when the calling SBC receives the PRACK message sent by the calling UE through the Mw interface.

[0031] The start time of the calling party's Update phase is the eighth time point, and the end time of the calling party's Update phase is the ninth time point. The ninth time point is the time when the calling party's SBC receives the UPDATE message sent by the calling party's UE through the Mw interface.

[0032] The start time of the Update forwarding phase is the ninth time point, and the end time of the Update forwarding phase is the tenth time point. The tenth time point is the time when the called SBC sends the UPDATE message to the called UE through the Mw interface.

[0033] The start time of the called party's Update phase is the tenth time point, and the end time of the called party's Update phase is the eleventh time point. The eleventh time point is the time when the called party's SBC receives the 180Ring message sent by the called party's UE through the Mw interface.

[0034] The Ring forwarding phase begins at the eleventh time point and ends at the time when the calling SBC sends a 180 Ring message to the calling UE via the Mw interface.

[0035] In one embodiment, delay segmentation and delimitation are performed on the end-to-end 5G voice call process and the call fallback process, respectively. The delay segmentation and delimitation of the call fallback process includes:

[0036] Based on the phase characteristics of signaling interaction in the call fallback process and the responsibility division rules between the core network and radio, the call fallback process is divided into 11 sub-phase delay segments. The 11 sub-phase delay segments are, in order: dedicated loadout establishment initiation phase, fallback triggering phase, fallback initiation phase, fallback execution phase, fallback completion phase, 4G location update initiation phase, 4G location update completion phase, 4G-GUTI allocation completion phase, 4G dedicated loadout establishment initiation phase, 4G dedicated loadout establishment completion phase, and location reporting phase.

[0037] The start time of the dedicated load facilitator establishment phase on the calling side is the time when the calling SBC receives the initial INVITE message from the calling UE through the Gm interface. The start time on the called side is the time when the called SBC receives the 183 message from the called UE through the Gm interface. The end time of the dedicated load facilitator establishment phase is the time when the N2 interface receives the first PDU SessionResource Modify Request message carrying fiveQI=1.

[0038] The fallback trigger phase starts when the N2 interface receives the PDU Session Modify Request message, and ends at the first moment when the N2 interface receives the PDU SessionModify Response message.

[0039] When the fallback process uses a handover fallback method, the start time of the fallback initiation phase is the first moment, and the end time is the second moment, which is the time when the N2 interface receives the Handover Required message; the start time of the fallback execution phase is the second moment, and the end time is the third moment, which is the time when the N2 interface receives the Handover Command message; the start time of the fallback completion phase is the third moment, and the end time is the fourth moment, which is the time when the S1 interface receives the Handover Notify message or the Relocation Complete Ack message; the start time of the 4G location update initiation phase is the fourth moment, and the end time is the fifth moment, which is the time when the S1 interface receives the TAU Request message;

[0040] When the fallback process uses redirection fallback, the start time of the fallback initiation phase is the first moment, and the end time of the fallback initiation phase is the sixth moment, which is the time when the N2 interface receives the UE Context release request message; the start time of the fallback execution phase is the sixth moment, and the end time of the fallback execution phase is the seventh moment, which is the time when the N2 interface receives the UE Context release command message; the start time of the fallback completion phase is the seventh moment, and the end time of the fallback completion phase is the fifth moment.

[0041] The 4G location update completion phase begins at the fifth hour and ends at the eighth hour, which is the time when the S1 interface receives the TAU Accepted message.

[0042] The 4G-GUTI allocation completion phase starts at time eight and ends at time nine. Time nine is the time when the S1 interface receives the TAU complete message.

[0043] The start time of the 4G dedicated network establishment initiation phase is the ninth moment, and the end time of the 4G dedicated network establishment initiation phase is the tenth moment. The tenth moment is the time when the S1 interface receives the E-RAB Setup Request message carrying QCI=1.

[0044] The start time of the 4G dedicated bearer establishment completion phase is the tenth time, and the end time of the 4G dedicated bearer establishment completion phase is the eleventh time. At the eleventh time, the S1 interface receives a NAS layer message carrying QCI=1. The NAS layer message is Activate dedicated EPS bearer context Accept.

[0045] The location reporting phase begins at time 11. The cutoff time for the calling side of the location reporting phase is the time when the calling SBC receives the initial INVITE message through the Mw interface. The cutoff time for the called side of the location reporting phase is the time when the called SBC receives the first RAR message through the Rx interface or the time when the PCRF sends the first RAR message.

[0046] In one embodiment, the duration of each sub-stage delay segment is determined, including:

[0047] Extract the signaling timestamp from the MAC address block of the interface signaling stream;

[0048] Based on the signaling timestamp and the start and end times of each sub-stage delay segment, the duration of each sub-stage delay segment is determined.

[0049] In one embodiment, after filling the occupied time back into the delay record positions corresponding to the delay segments of each sub-stage in the integrated call detail record, the process includes:

[0050] The data statistics equipment summarizes the comprehensive call detail records and generates latency statistics according to the dimension type and time granularity. The dimension types include provincial dimension, city dimension and network element dimension.

[0051] Secondly, embodiments of this application provide a time delay segmentation monitoring device, including:

[0052] The interface data association module is used to obtain the interface signaling code stream in the 5G call service process. Based on the interface signaling code stream, it determines whether the 5G call service process is the same call process of the same user. If so, it associates the service process data corresponding to the service interface of the 5G call service process to form the calling call detail record and the called call detail record.

[0053] The call detail record association module is used to associate and synthesize the call detail records of the calling party and the called party to obtain a comprehensive call detail record of the 5G call service process.

[0054] The delay segmentation and delimitation module is used to segment and delimit the delay of the end-to-end 5G voice call process and the call fallback process respectively, resulting in several sub-stage delay segments.

[0055] The time occupancy determination module is used to determine the occupancy time of each sub-stage delay segment and fill the occupancy time back into the delay record position corresponding to each sub-stage delay segment in the integrated call detail record.

[0056] Thirdly, embodiments of this application provide an electronic device, including a processor and a memory storing a computer program, wherein the processor executes the program to implement the steps of the delay segmentation monitoring method described in the first aspect.

[0057] Fourthly, embodiments of this application provide a computer program product, including a computer program that, when executed by a processor, implements the steps of the delay segmentation monitoring method described in the first aspect.

[0058] The latency segmentation monitoring method, apparatus, electronic device, and computer program product provided in this application obtain the interface signaling code stream in the 5G call service process. Based on the interface signaling code stream, it determines whether the 5G call service process is the same call process of the same user. If so, it associates the service process data corresponding to the service interface of the 5G call service process to form a calling party call detail record (CDR) and a called party call detail record (CDR). The calling party CDR and the called party CDR are then associated and synthesized to obtain a comprehensive CDR of the 5G call service process. This summarizes and associates the service process data corresponding to the service interfaces in the same call process of the same user. Let's reconstruct the complete 5G call service process. This process includes an end-to-end 5G voice call process and a call fallback process. We then segment and demarcate the latency of both processes to obtain several sub-stage latency segments. We determine the duration of each sub-stage latency segment and fill it back into the corresponding latency record position in the integrated call detail record. This clearly reflects the duration of each sub-stage latency segment, effectively improving the monitoring efficiency of network issues related to each sub-stage latency segment, increasing operational efficiency, and enhancing network quality. Attached Figure Description

[0059] To more clearly illustrate the technical solutions in 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.

[0060] Figure 1 This is one of the flowcharts illustrating the delay segmentation monitoring method provided in the embodiments of this application;

[0061] Figure 2 This is the second flowchart illustrating the delay segmentation monitoring method provided in the embodiments of this application;

[0062] Figure 3 This is the third flowchart illustrating the delay segmentation monitoring method provided in the embodiments of this application;

[0063] Figure 4 This is the fourth flowchart of the delay segmentation monitoring method provided in the embodiments of this application;

[0064] Figure 5 This is a schematic diagram of the time delay segmentation monitoring device provided in the embodiments of this application;

[0065] Figure 6 This is a schematic diagram of the structure of the electronic device provided in the embodiments of this application. Detailed Implementation

[0066] To make the objectives, technical solutions, and advantages of this application clearer, the technical solutions of this application will be clearly and completely described below with reference to the accompanying drawings of the embodiments. 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.

[0067] Figure 1 This is one of the flowcharts illustrating the delay segmentation monitoring method provided in this application. (Refer to...) Figure 1 This application provides a delay segmentation monitoring method, which may include:

[0068] Step 101: Obtain the interface signaling code stream in the 5G call service process, and determine whether the 5G call service process is the same call process of the same user based on the interface signaling code stream.

[0069] In this embodiment of the application, the 5G call service process refers to the complete voice call service process of a 5G standalone network. In the entire service process, various signaling code streams interact in various data interfaces of the service process to form interface signaling code streams. Based on these signaling code streams, it can be determined whether the current 5G call service process is the same call process of the same user. The same user refers to the same calling user and the same called user. The same call process refers to the process in which the current user is talking.

[0070] Step 102: If the current 5G call service process is the same call process of the same user, then associate the service process data corresponding to the service interface of the 5G call service process to form the calling party call detail record and the called party call detail record.

[0071] The business process data corresponding to the calling side's business interface and the business process data corresponding to the called side's business interface are associated according to the agreed call flow, forming the calling call detail record corresponding to the calling side's business process and the called call detail record corresponding to the called side's business process.

[0072] Step 103: Associate and synthesize the calling party's call detail record (CDR) and the called party's call detail record (CDR) to obtain the comprehensive CDR of the 5G call service process.

[0073] The calling and called records are further correlated and synthesized to restore the complete 5G call service process and form a comprehensive call record that matches the 5G call service process.

[0074] Step 104: Determine the latency segmentation of the end-to-end 5G voice call process and the call fallback process respectively to obtain several sub-stage latency segments.

[0075] In this embodiment, the 5G call service process includes an end-to-end 5G voice call process and a call fallback process. The end-to-end 5G voice call process can be an end-to-end 5G voice call process based on IMS signaling, while the call fallback process is the EPSFB call fallback process. Since the 4G network already has excellent coverage, it is necessary to use the 4G network to compensate for the insufficient coverage of the 5G network in its early stages, so as to ensure the quality of voice calls when using the 5G network. Generally, the voice call service of 5G standalone network will adopt the form of EPSFB voice call. EPSFB means that during a voice call, the call falls back from 5G to 4G and uses 4G VoLTE to complete the call. After the call ends, the voice service of the 5G network is restored.

[0076] Latency segmentation and delimitation are performed separately for the end-to-end 5G voice call process and the call fallback process. This involves breaking down the end-to-end 5G voice call process into multiple sub-stages, and defining the latency segments of the call path based on each sub-stage, thus obtaining multiple sub-stage latency segments corresponding to the number of sub-stages in the multiple call processes. Similarly, the call fallback process is broken down into multiple fallback process sub-stages, and the fallback process latency segments are defined based on each sub-stage, resulting in multiple sub-stage latency segments corresponding to the number of sub-stages in the multiple fallback processes. Finally, the sub-stage latency segments of the multiple call processes and the multiple sub-stage latency segments of the multiple fallback processes are aggregated to obtain several sub-stage latency segments.

[0077] Step 105: Determine the time occupied by each sub-stage delay segment.

[0078] By determining the time occupied by each sub-stage delay segment, we can obtain the corresponding delay information for each sub-stage delay segment.

[0079] Step 106: Fill the occupied time back into the delay record position corresponding to each sub-stage delay segment in the integrated call detail record.

[0080] Understandably, when the 5G call service process is broken down into several sub-stage delay segments, the corresponding comprehensive call detail records (CDRs) are also broken down simultaneously. For example, if the 5G call service process is broken down into a first sub-stage delay segment, a second sub-stage delay segment, and a third sub-stage delay segment, then the comprehensive CDR will also be broken down into a first delay record, a second delay record, and a third delay record corresponding to the first, second, and third sub-stage delay segments, respectively. Accordingly, the first, second, and third delay records have corresponding recording positions, so that each occupied time can be filled back into each recording position, realizing the recording and monitoring of the delay situation corresponding to each sub-stage delay segment, which is beneficial for the immediate discovery and tracking of network problems.

[0081] The following beneficial effects can be seen from the above embodiments:

[0082] By acquiring the interface signaling code stream in the 5G call service process, it is determined whether the 5G call service process belongs to the same user and the same call process. If so, the service process data corresponding to the service interface of the 5G call service process is associated to form the calling party's call detail record (CDR) and the called party's CDR. The calling party's CDR and the called party's CDR are then associated and synthesized to obtain the comprehensive CDR of the 5G call service process. This allows the service process data corresponding to the service interfaces in the same call process of the same user to be summarized and associated, thus reconstructing the complete 5G call service process. In this context, the 5G call service process includes an end-to-end 5G voice call process and a call fallback process. The latency of both processes is segmented and delimited to obtain several sub-stage latency segments. The duration of each sub-stage latency segment is determined and then filled back into the corresponding latency record position in the integrated call detail record. This clearly reflects the duration of each sub-stage latency segment, effectively improving the monitoring efficiency of network issues related to each sub-stage latency segment, increasing operational efficiency, and enhancing network quality.

[0083] To facilitate understanding, an embodiment of the latency segmentation monitoring method is provided below. In practical applications, the 5G single-interface signaling stream, 4G single-interface signaling stream, and IMS SIP message signaling stream in the interface signaling stream are judged to determine whether the 5G call service process is the same call process of the same user, and then to determine whether to associate the service process data corresponding to the service interface of the 5G call service process.

[0084] Figure 2This is the second flowchart illustrating the delay segmentation monitoring method provided in this application. (Refer to...) Figure 2 This application provides a delay segmentation monitoring method, which may include:

[0085] Step 201: Determine whether the 5G call service process is the same call process of the same user based on the interface signaling code stream.

[0086] In this embodiment, the interface signaling stream includes the N2 interface signaling stream, the N26 interface signaling stream, the S1 interface signaling stream, and the IMS SIP message signaling stream. The N2 interface is a type of 5G single interface. In practical applications, since the N1 and N2 interfaces are combined, with the N1 interface using the NAS protocol and the N2 interface using the NGAP protocol, and the N1 interface carried on top of the N2 interface, the N2 interface is essentially the N1 / N2 interface. The N26 interface is also a type of 5G single interface, using the GTPv2 protocol. The S1 interface is a type of 4G single interface, using the S1AP protocol. The IMS SIP message can be understood as the SIP message in the IMS-based call flow. Before making a judgment, the interface signaling stream can be parsed and encoded / decoded.

[0087] If the values ​​of AMF UE NGAP ID and RAN UE NGAP ID are the same in the N2 interface signaling stream, and the source TEID, destination TEID, source IP address, destination IP address, source port, and destination port are all unique in the N26 interface signaling stream, and the values ​​of MME UE S1AP ID and eNB UE S1AP ID are the same in the S1 interface signaling stream, and the Call ID is unique in the IMS SIP message signaling stream, then it is determined that the 5G call service process is the same call process of the same user. Specifically, the values ​​of the AMF UE NGAP ID field and the RAN UE NGAP ID field in the N2 interface signaling stream are used to determine whether they are the same user on the 5G side. The source TEID, destination TEID, source IP address, destination IP address, source port, and destination port in the N26 interface signaling stream are used to determine whether they are the same call process on the 5G side. The values ​​of the MME UE S1AP ID field and the eNB UE S1AP ID field in the S1 interface signaling stream are used to determine whether they are the same user on the 4G side. The Call ID in the IMS SIP message signaling stream is used to determine whether they are the same call process on the 4G side.

[0088] Step 202: Associate the business process data corresponding to the business interface of the 5G call service process.

[0089] In the mobility registration process of the 5G call service, the SUPI and 5G-GUTI are obtained. Based on the tuple binding relationship between the SUPI and 5G-GUTI, the GPSI number of the 5G call service is obtained. The GPSI number is then filled into various service processes on the N2 and N26 interfaces. The SUPI can also be filled in simultaneously. In the LTE attach process of the 5G call service, the IMSI and 4G-GUTI are obtained. Based on the tuple binding relationship between the IMSI and 4G-GUTI, the MSISDN number of the 5G call service is determined. The MSISDN number is then filled into various service processes on the S1 interface and IMS domain. The IMSI can also be filled in simultaneously. The mobility registration process refers to a registration process that allows users from any location to access one or more communication networks for communication. The LTE attach process is a fundamental process of the 4G network, used to describe the setup of an LTE session.

[0090] On both the calling and called sides, service process data corresponding to service interfaces with the same interface signaling stream generation time, the same mobile subscriber number, the same subscriber identification code, and the same ICID information are associated. The ICID information is extracted from the SIP message. It can be understood that on the 5G side, the mobile subscriber number is the GPSI number, and the subscriber identification code is the SUPI; on the 4G side, the mobile subscriber number is the MSISDN number, and the subscriber identification code is the IMSI. The interface signaling stream generation time can be determined by extracting the timestamp from the MAC address block of the interface signaling stream.

[0091] It is also understandable that each service interface, including but not limited to the N2 interface, N26 interface, S1 interface, and IMS domain interface, has a unique identifier after the number is filled in. Therefore, it is possible to associate the service process data corresponding to service interfaces with the same interface signaling code stream generation time, the same mobile user number, the same user identification code, and the same ICID information, and restore the complete calling side service process and the called side service process respectively, thus forming the calling call detail record and the called call detail record.

[0092] The calling and called records retain fields such as interface signaling code stream generation time, 5G and 4G cell location information, mobile user number, user identification code, network element IP address, fallback type, service result, and terminal type, while removing temporary fields such as flow identifier and user-transparent data such as QoS information and terminal capabilities.

[0093] Step 203: Associate and synthesize the calling party's call detail record (CDR) and the called party's CDR.

[0094] By associating and merging calling and called call detail records (CDRs) with the same interface signaling code stream generation time, mobile user number, user identification code, and ICID information, a complete 5G call service process can be reconstructed.

[0095] The following beneficial effects can be seen from the above embodiments:

[0096] By determining whether a 5G call service process is the same call process of the same user based on the interface signaling code stream, if so, the service process data corresponding to the service interface of the 5G call service process is associated, and the calling party's call detail record (CDR) and the called party's CDR are associated and synthesized to form a comprehensive CDR record of the 5G call service process. This summarizes and associates the service process data corresponding to the service interfaces in the same call process of the same user, and restores the complete 5G call service process. This is beneficial for subsequent delay segmentation and demarcation according to the stage characteristics of message interaction and the division of responsibilities between the core network and radio, to clearly identify the location of network problems in the entire 5G call service process, and to optimize and solve the network problems in a targeted manner, thereby improving network operation and maintenance efficiency and enhancing network quality.

[0097] For ease of understanding, an embodiment of the latency segmentation monitoring method is provided below. In practical applications, latency segmentation and delimitation will be performed on the end-to-end 5G voice call process and the call fallback process respectively.

[0098] Figure 3 This is the third flowchart illustrating the delay segmentation monitoring method provided in this application. (Refer to...) Figure 3 This application provides a delay segmentation monitoring method, which may include:

[0099] Step 301: Determine the time delay segmentation boundary for the end-to-end 5G voice call process.

[0100] Based on the phase characteristics of SIP message interaction and the responsibility division rules between the core network and the radio, the end-to-end 5G voice call process is divided into 12 sub-phase latency segments. The phase characteristics of SIP message interaction refer to the characteristics of each stage of the 5G voice call process, from call initiation to resource reservation, to calling service triggering, to called addressing, to called service triggering, to paging, to resource negotiation, to ringing. The responsibility division rules between the core network and the radio are based on the respective functions of the core network and the radio.

[0101] The 12 sub-stage delay segments are, in order: calling bearer establishment stage, calling call control stage, IMS addressing stage, called call control stage, called radio establishment stage, called bearer establishment stage, 183 forwarding stage, calling radio establishment stage, calling update stage, update forwarding stage, called update stage, and Ring forwarding stage.

[0102] The start time of the calling bearer establishment phase is the time when the calling SBC receives the INVITE message sent by the calling UE through the Gm interface, and the end time of the calling bearer establishment phase is the first time point, which is the time when the calling S-CSCF receives the first INVITE message sent by the calling SBC through the Mw interface. The calling bearer establishment phase mainly involves the calling party's resource reservation and bearer establishment, and the network issues it addresses mainly come from EPC, i.e., the all-IP packet core network.

[0103] The start time of the calling party's call control phase is the first time point, and the end time of the calling party's call control phase is the second time point. The second time point is the time when the calling party's S-CSCF receives the INVITE message sent by the last TAS on the calling party's side. The calling party's call control phase is mainly for the calling party to complete call-related work. The network problems it addresses mainly come from IMS, i.e., IP Multimedia System.

[0104] The IMS addressing phase begins at the second time point and ends at the third time point. The third time point is when the called party's S-CSCF sends the INVITE message to the first TAS on the called party's side. The IMS addressing phase mainly completes the routing work for the called party's user. The network problems it addresses mainly come from DNS or HSS. DNS is the Domain Name System, and HSS is the Home Subscriber Server.

[0105] The call control phase begins at the third time point and ends at the fourth time point. The fourth time point is when the called SBC sends the INVITE message to the called UE through the Gm interface. The call control phase is mainly for the called party to complete call-related work, and the network issues it addresses mainly come from IMS.

[0106] The start time of the called party's radio establishment phase is the fourth time point, and the end time of the called party's radio establishment phase is the fifth time point. The fifth time point is the time when the called party's SBC receives the 183 message sent by the called party's UE through the Gm interface. The called party's radio establishment phase is mainly caused by the called party's UE and the called party's radio environment. The network problems it addresses mainly come from the radio.

[0107] The start time of the called party bearer establishment phase is the fifth time point, and the end time of the called party bearer establishment phase is the sixth time point. The sixth time point is the time when the called party S-CSCF receives the first 183 message sent by the called party SBC through the Mw interface. The called party bearer establishment phase mainly involves the called party's resource reservation and bearer establishment, and the network issues it addresses mainly come from EPC.

[0108] The 183 forwarding phase is the phase in which SIP 183 messages are forwarded, informing the calling party that the call is in progress. Its start time is the sixth time point, and the end time of the 183 forwarding phase is the seventh time point. The seventh time point is when the calling SBC sends the 183 message to the calling UE through the Mw interface. The main reason for the delay in the 183 forwarding phase is the forwarding delay of 183 messages by the IMS network. The network problem it addresses mainly comes from IMS.

[0109] The caller radio establishment phase begins at time point seven and ends at time point eight. Time point eight is the time when the caller SBC receives the PRACK message sent by the caller UE through the Mw interface. The caller radio establishment phase is mainly caused by the caller UE and the caller's radio environment, and the network problems it addresses mainly come from the radio.

[0110] The caller update phase begins at the eighth time point and ends at the ninth time point. The ninth time point is the time when the caller SBC receives the UPDATE message sent by the caller UE through the Mw interface. The caller update phase is mainly caused by the caller UE and the caller's wireless environment, and the network problems it addresses mainly come from the wireless.

[0111] The Update forwarding phase begins at the ninth time point and ends at the tenth time point. The tenth time point is when the called SBC sends the UPDATE message to the called UE through the Mw interface. The Update forwarding phase mainly involves the IMS network forwarding the UPDATE message, and the network issues it addresses mainly come from the IMS.

[0112] The called party update phase starts at the tenth time point and ends at the eleventh time point. The eleventh time point is when the called party SBC receives the 180Ring message sent by the called party UE through the Mw interface. The called party update phase is mainly caused by the called party UE and the called party's wireless environment, and the network problems it addresses mainly come from the wireless.

[0113] The Ring forwarding phase begins at the eleventh time point and ends at the time when the calling SBC sends a 180 Ring message to the calling UE via the Mw interface. The Ring forwarding phase mainly involves the IMS network forwarding the 180 Ring message, and the network issues it addresses primarily come from the IMS.

[0114] Step 302: Determine the time delay segmentation boundary for the call fallback process.

[0115] Based on the phase characteristics of signaling interaction in the call fallback process and the responsibility division rules between the core network and radio, the call fallback process is divided into 11 sub-phase delay segments. The 11 sub-phase delay segments are, in order: dedicated loadout establishment initiation phase, fallback triggering phase, fallback initiation phase, fallback execution phase, fallback completion phase, 4G location update initiation phase, 4G location update completion phase, 4G-GUTI allocation completion phase, 4G dedicated loadout establishment initiation phase, 4G dedicated loadout establishment completion phase, and location reporting phase.

[0116] The fallback process is triggered during the 5G dedicated network setup phase. The 5G dedicated network setup is triggered by the SBC receiving a SIP message carrying media information from the terminal. Therefore, for calls with resource reservation, the start time of the dedicated network setup initiation phase for the calling side is the time when the calling SBC receives the initial INVITE message from the calling UE through the Gm interface, and the start time for the called side is the time when the called SBC receives the 183 message from the called UE through the Gm interface. The end time of the dedicated network setup initiation phase is the time when the N2 interface receives the first PDU Session Resource Modify Request message carrying fiveQI=1. These two messages are the first messages carrying media information for the calling side and the called side, respectively. After receiving them, the SBC will request the PCF to authorize the 5GC to establish the 5G dedicated network through the Rx interface to trigger the fallback. The PCF is a device with packet control function in the radio domain and packet domain interface, and the 5GC is the 5G core network.

[0117] The dedicated carrier establishment initiation phase mainly involves querying the PCF hostname and triggering resource reservation. The network issues it addresses primarily originate from PCC and 5GC. PCC is an architecture that maps the QoS requirements of application-level session service data streams to IP-CAN, and uses the QoS requirements of the access transmission network bearer-level services to ensure data transmission.

[0118] During the fallback trigger phase, the AMF receives a response message from the 5G base station indicating a failure to establish the 5G dedicated bearer. This response message, carrying an NGAP reason value, is feedback information to the PDU Session Resource Modify Request message, i.e., a PDU Session Modify Response message. This indicates that the 5G base station has decided to use EPSFB for this call. An NGAP reason value could be, for example, ims-voice-eps-fallback-or-rat-fallback-triggered or redirection. Therefore, the fallback trigger phase begins when the N2 interface receives the PDU Session Modify Request message, and ends at the first instant, which is the time the N2 interface receives the PDU Session Modify Response message. The fallback trigger phase primarily focuses on establishing radio resources, addressing network issues mainly originating from the radio.

[0119] Furthermore, the 5G base station will determine the fallback method of the call fallback process based on the terminal's wireless capabilities and the base station configuration decision. This fallback method includes, but is not limited to, the 5G-4G handover fallback method based on the N26 interface and the redirect fallback method.

[0120] When the fallback process uses a switching fallback method, the fallback initiation phase starts at the first moment and ends at the second moment, which is the time when the N2 interface receives the Handover Required message. The fallback execution phase starts at the second moment and ends at the third moment, which is the time when the N2 interface receives the Handover Command message. The fallback completion phase starts at the third moment and ends at the fourth moment, which is the time when the S1 interface receives the Handover Notify message or Relocation Complete Ack message, indicating that the terminal has successfully accessed the 4G network. After further changing the downlink channel, data transmission in the data domain can be achieved. The 4G location update initiation phase starts at the fourth moment and ends at the fifth moment, which is the time when the S1 interface receives the TAU Request message.

[0121] When the fallback process uses redirected fallback, the start time of the fallback initiation phase is the first moment, and the end time is the sixth moment, which is the time when the N2 interface receives the UE Context release request message; the start time of the fallback execution phase is the sixth moment, and the end time is the seventh moment, which is the time when the N2 interface receives the UE Context release command message; the start time of the fallback completion phase is the seventh moment, and the end time is the fifth moment. It can be understood that the work of the 4G location update initiation phase has already been completed in the fallback completion phase, and a deadline has been generated, so there is no need to execute the 4G location update initiation phase again.

[0122] The fallback initiation phase mainly involves terminal measurements and gNodeB handover decisions, addressing network issues primarily originating from radio. The fallback execution phase mainly involves 4G-side handover preparation and core network bearer establishment, addressing network issues primarily originating from radio and EPC. The fallback completion phase mainly involves completing the handover operation based on the S1 interface, addressing network issues primarily originating from radio. The 4G location update initiation phase mainly involves the 4G location update initiation process, addressing network issues primarily originating from radio.

[0123] The 4G location update completion phase starts at the fifth hour and ends at the eighth hour. The eighth hour is when the S1 interface receives the TAU Accepted message. The 4G location update completion phase mainly completes the 4G location update, and the network issues it addresses mainly come from EPC.

[0124] The 4G-GUTI allocation completion phase begins at time eight and ends at time nine. Time nine is the time when the S1 interface receives the TAU complete message. The 4G-GUTI allocation completion phase is mainly caused by the wireless environment, and the network problems it addresses mainly originate from the wireless.

[0125] The start time of the 4G dedicated bearer establishment initiation phase is the ninth hour, and the end time of the 4G dedicated bearer establishment initiation phase is the tenth hour. The tenth hour is the time when the S1 interface receives the E-RAB Setup Request message carrying QCI=1. The 4G dedicated bearer establishment initiation phase mainly initiates the dedicated bearer establishment process, and the network problems it addresses mainly come from EPC.

[0126] The start time of the 4G dedicated bearer establishment completion phase is the tenth hour, and the end time of the 4G dedicated bearer establishment completion phase is the eleventh hour. At the eleventh hour, the S1 interface receives a NAS layer message carrying QCI=1. The NAS layer message is Activate dedicated EPS bearer context Accept. The 4G dedicated bearer establishment completion phase mainly involves reserving radio resources and the RRC reconfiguration process. RRC is Radio Resource Control, and the network problems it addresses mainly come from the radio.

[0127] The location reporting phase begins at time 11. The cutoff time for the calling side of the location reporting phase is when the calling SBC receives the initial INVITE message through the Mw interface. The cutoff time for the called side of the location reporting phase is when the called SBC receives the first RAR message through the Rx interface or when the PCRF sends the first RAR message. The location reporting phase mainly consists of reporting user location information and establishing a continued call. The network issues it addresses mainly come from EPC and PCC.

[0128] The following beneficial effects can be seen from the above embodiments:

[0129] By segmenting and delimiting the latency of the end-to-end 5G voice call process and the call fallback process, we can develop targeted optimization methods for network problems corresponding to each sub-stage latency segment. This will guide us in resolving issues such as extended call setup and fallback times, improve network operation and maintenance efficiency, promptly identify network vulnerabilities, and enhance network quality.

[0130] To facilitate understanding, the following is an example of a delay segmentation monitoring method. In practical applications, the signaling timestamp is extracted from the interface signaling code stream. Combined with the start and end times of each sub-stage delay segment, the occupied time of each sub-stage delay segment is determined. The occupied time is then filled back into the delay record position corresponding to each sub-stage delay segment in the integrated call detail record. Statistical data is then generated to meet the analysis needs of different application scenarios.

[0131] Figure 4 This is the fourth flowchart illustrating the delay segmentation monitoring method provided in this application. (Refer to...) Figure 4 This application provides a delay segmentation monitoring method, which may include:

[0132] Step 401: Determine the time occupied by each sub-stage delay segment.

[0133] The signaling timestamp is extracted from the MAC address block of the interface signaling code stream, with a time precision of nanoseconds. The MAC address block contains a 6-byte source MAC address and a 6-byte destination MAC address. These 6-byte source and destination MAC addresses correspond to 4 bytes of data source information, 4 bytes of timestamp in seconds, and 4 bytes of timestamp in nanoseconds.

[0134] Based on the signaling timestamps and the start and end times of each sub-stage delay segment, the duration of each sub-stage delay segment is determined. Since the calling and called party call detail records (CDRs) are associated and synthesized, and based on the call flow's interaction from the calling side to the called side's response, this embodiment uses a dual-series stack approach for both the calling and called party flows to record the timestamps of each signaling message. Combined with the start and end times of each sub-stage delay segment, the duration of each sub-stage delay segment can be calculated. It is understood that in practical applications, the methods for recording the timestamps of each signaling message are diverse, and a suitable recording method must be determined based on the specific application; no single method is limited here.

[0135] Step 402: Fill the occupied time back into the delay record position corresponding to each sub-stage delay segment in the integrated call detail record.

[0136] In this embodiment, the content of step 402 is similar to that of step 106 in the above embodiment, and will not be repeated here.

[0137] Step 403: Summarize the comprehensive call detail records using data statistics equipment, and generate latency statistics data according to dimension type and time granularity.

[0138] By aggregating comprehensive call detail records through data statistics equipment, latency statistics are generated according to dimension type and time granularity. Dimension types include provincial, municipal, and network element dimensions, etc. Time granularity refers to minutes, hours, days, weeks, and months, etc. In practical applications, the appropriate dimension type and time granularity should be selected according to the actual analysis needs to generate latency statistics. There is no single limitation here, so that the latency statistics can be applied to application scenarios such as user complaint handling, indicator optimization, network performance monitoring, daily network problem analysis, and network fault location.

[0139] In this embodiment of the application, each sub-stage latency segment can be further divided into latency intervals related to quality levels. The quality levels include excellent, good, medium, and poor. For example, in the calling party control stage, if the calling party control latency is less than 80 microseconds, the latency of the calling party control stage is determined to be excellent. If the calling party control latency is greater than or equal to 80 microseconds and less than or equal to 200 microseconds, the latency of the calling party control stage is determined to be good. If the calling party control latency is greater than 200 microseconds and less than or equal to 400 microseconds, the latency of the calling party control stage is determined to be only medium, and attention needs to be paid to it. If the calling party control latency is greater than 400 microseconds, the latency of the calling party control stage is determined to be poor, and network problems caused by the calling party control stage need to be addressed to avoid affecting user experience.

[0140] It is understood that the above description of the time delay interval division of quality levels is only illustrative. In actual applications, the division should be based on the specific application situation, and no single limitation is made here.

[0141] The following beneficial effects can be seen from the above embodiments:

[0142] By determining the duration of each sub-stage latency segment and backfilling the duration into the corresponding latency record position in the integrated call detail record (CDR), and then aggregating the CDR records using data statistics equipment to generate latency statistics data according to dimension type and time granularity, statistical monitoring of latency in each sub-stage latency segment is achieved. This eliminates the need for manual analysis, saves manpower, improves network operation and maintenance efficiency, accurately and effectively identifies the fault point where latency issues occur, facilitates subsequent fault dispatch and problem tracking, improves network quality, and enhances user satisfaction.

[0143] The delay segmentation monitoring device provided in the embodiments of this application is described below. The delay segmentation monitoring device described below and the delay segmentation monitoring method described above can be referred to in correspondence.

[0144] Figure 5 A schematic diagram of the delay segmentation monitoring device provided in an embodiment of this application. (Refer to...) Figure 5 This application provides a time delay segmentation monitoring device, which may include:

[0145] The interface data association module 510 is used to obtain the interface signaling code stream in the 5G call service process, and determine whether the 5G call service process is the same call process of the same user based on the interface signaling code stream. If so, the business process data corresponding to the business interface of the 5G call service process is associated to form the calling call detail record and the called call detail record.

[0146] The call detail record association module 520 is used to associate and synthesize the calling call detail record and the called call detail record to obtain the comprehensive call detail record of the 5G call service process.

[0147] The delay segmentation and delimitation module 530 is used to perform delay segmentation and delimitation on the end-to-end 5G voice call process and the call fallback process respectively, in order to obtain several sub-stage delay segments.

[0148] The occupancy time determination module 540 is used to determine the occupancy time of each sub-stage delay segment and fill the occupancy time back into the delay record position corresponding to each sub-stage delay segment in the integrated call detail record.

[0149] The latency segmentation monitoring device provided in this application embodiment acquires the interface signaling code stream in the 5G call service process, determines whether the 5G call service process is the same call process of the same user based on the interface signaling code stream, and if so, associates the service process data corresponding to the service interface of the 5G call service process to form the calling party call detail record and the called party call detail record, and associates and synthesizes the calling party call detail record and the called party call detail record to obtain the comprehensive call detail record of the 5G call service process, thereby summarizing and associating the service process data corresponding to the service interface in the same call process of the same user, and restoring the complete 5G call detail record. The 5G call service process includes an end-to-end 5G voice call process and a call fallback process. The end-to-end 5G voice call process and the call fallback process are then segmented and delimited for latency, resulting in several sub-stage latency segments. The duration of each sub-stage latency segment is determined and then filled back into the corresponding latency record position in the integrated call detail record. This clearly reflects the duration of each sub-stage latency segment, effectively improving the monitoring efficiency of network issues corresponding to each sub-stage latency segment, increasing operational efficiency, and enhancing network quality.

[0150] In one embodiment, the interface signaling stream includes the N2 interface signaling stream, the N26 interface signaling stream, the S1 interface signaling stream, and the IMS SIP message signaling stream;

[0151] Determining whether a 5G call service process is the same call process of the same user based on the interface signaling code stream includes:

[0152] If the values ​​of AMF UE NGAP ID and RAN UE NGAP ID are the same in the N2 interface signaling stream, and the source TEID, destination TEID, source IP address, destination IP address, source port, and destination port are all unique in the N26 interface signaling stream, and the values ​​of MME UE S1AP ID and eNB UE S1AP ID are the same in the S1 interface signaling stream, and the Call ID is unique in the IMS SIP message signaling stream, then it is determined that the 5G call service process is the same call process of the same user.

[0153] In one embodiment, associating business process data corresponding to the business interface of a 5G call service process includes:

[0154] In the mobility registration process of the 5G call service process, obtain SUPI and 5G-GUTI, obtain GPSI number of the 5G call service process according to the tuple binding relationship of SUPI and 5G-GUTI, and fill the GPSI number back into each service process of N2 interface and N26 interface.

[0155] In the LTE attach process of the 5G call service process, the IMSI and 4G-GUTI are obtained. The MSISDN number of the 5G call service process is determined according to the tuple binding relationship between the IMSI and 4G-GUTI. The MSISDN number is then filled back into the S1 interface and various service processes in the IMS domain.

[0156] On both the calling and called sides, the business process data corresponding to the business interfaces that have the same interface signaling code stream generation time, the same mobile user number, the same user identification code, and the same ICID information are associated. The ICID information is extracted from the SIP message.

[0157] In one embodiment, associating and combining the calling party's call detail record (CDR) and the called party's CDR includes:

[0158] The calling and called call detail records (CDRs) with the same interface signaling code stream generation time, mobile user number, user identification code, and ICID information are associated and merged.

[0159] In one embodiment, latency segmentation and delimitation are performed on the end-to-end 5G voice call process and the call fallback process, respectively. The latency segmentation and delimitation of the end-to-end 5G voice call process includes:

[0160] Based on the phase characteristics of SIP message interaction and the responsibility division rules between the core network and the radio, the end-to-end 5G voice call process is divided into 12 sub-phase delay segments. The 12 sub-phase delay segments are as follows: calling bearer establishment phase, calling call control phase, IMS addressing phase, called call control phase, called radio establishment phase, called bearer establishment phase, 183 forwarding phase, calling radio establishment phase, calling update phase, update forwarding phase, called update phase, and Ring forwarding phase.

[0161] The start time of the calling bearer establishment phase is the time when the calling SBC receives the INVITE message sent by the calling UE through the Gm interface, and the end time of the calling bearer establishment phase is the first time point, which is the time when the calling S-CSCF receives the first INVITE message sent by the calling SBC through the Mw interface.

[0162] The start time of the calling party's call control phase is the first time point, and the end time of the calling party's call control phase is the second time point. The second time point is the time when the calling party's S-CSCF receives the INVITE message sent by the last TAS from the calling party's side.

[0163] The start time of the IMS addressing phase is the second time point, and the end time of the IMS addressing phase is the third time point. The third time point is the time when the called S-CSCF sends the INVITE message to the first TAS on the called side.

[0164] The start time of the called party's call control phase is the third time point, and the end time of the called party's call control phase is the fourth time point. The fourth time point is the time when the called party's SBC sends the INVITE message to the called party's UE through the Gm interface.

[0165] The start time of the called party's radio establishment phase is the fourth time point, and the end time of the called party's radio establishment phase is the fifth time point. The fifth time point is the time when the called party's SBC receives the 183 message sent by the called party's UE through the Gm interface.

[0166] The start time of the called bearer establishment phase is the fifth time point, and the end time of the called bearer establishment phase is the sixth time point. The sixth time point is the time when the called S-CSCF receives the first 183 message sent by the called SBC through the Mw interface.

[0167] The start time of the 183 forwarding phase is the sixth time point, and the end time of the 183 forwarding phase is the seventh time point. The seventh time point is the time when the calling SBC sends the 183 message to the calling UE through the Mw interface.

[0168] The start time of the calling radio setup phase is the seventh time point, and the end time of the calling radio setup phase is the eighth time point. The eighth time point is the time when the calling SBC receives the PRACK message sent by the calling UE through the Mw interface.

[0169] The start time of the calling party's Update phase is the eighth time point, and the end time of the calling party's Update phase is the ninth time point. The ninth time point is the time when the calling party's SBC receives the UPDATE message sent by the calling party's UE through the Mw interface.

[0170] The start time of the Update forwarding phase is the ninth time point, and the end time of the Update forwarding phase is the tenth time point. The tenth time point is the time when the called SBC sends the UPDATE message to the called UE through the Mw interface.

[0171] The start time of the called party's Update phase is the tenth time point, and the end time of the called party's Update phase is the eleventh time point. The eleventh time point is the time when the called party's SBC receives the 180Ring message sent by the called party's UE through the Mw interface.

[0172] The Ring forwarding phase begins at the eleventh time point and ends at the time when the calling SBC sends a 180 Ring message to the calling UE via the Mw interface.

[0173] In one embodiment, delay segmentation and delimitation are performed on the end-to-end 5G voice call process and the call fallback process, respectively. The delay segmentation and delimitation of the call fallback process includes:

[0174] Based on the phase characteristics of signaling interaction in the call fallback process and the responsibility division rules between the core network and radio, the call fallback process is divided into 11 sub-phase delay segments. The 11 sub-phase delay segments are, in order: dedicated loadout establishment initiation phase, fallback triggering phase, fallback initiation phase, fallback execution phase, fallback completion phase, 4G location update initiation phase, 4G location update completion phase, 4G-GUTI allocation completion phase, 4G dedicated loadout establishment initiation phase, 4G dedicated loadout establishment completion phase, and location reporting phase.

[0175] The start time of the dedicated load facilitator establishment phase on the calling side is the time when the calling SBC receives the initial INVITE message from the calling UE through the Gm interface. The start time on the called side is the time when the called SBC receives the 183 message from the called UE through the Gm interface. The end time of the dedicated load facilitator establishment phase is the time when the N2 interface receives the first PDU SessionResource Modify Request message carrying fiveQI=1.

[0176] The fallback trigger phase starts when the N2 interface receives the PDU Session Modify Request message, and ends at the first moment when the N2 interface receives the PDU SessionModify Response message.

[0177] When the fallback process uses a handover fallback method, the start time of the fallback initiation phase is the first moment, and the end time is the second moment, which is the time when the N2 interface receives the Handover Required message; the start time of the fallback execution phase is the second moment, and the end time is the third moment, which is the time when the N2 interface receives the Handover Command message; the start time of the fallback completion phase is the third moment, and the end time is the fourth moment, which is the time when the S1 interface receives the Handover Notify message or the Relocation Complete Ack message; the start time of the 4G location update initiation phase is the fourth moment, and the end time is the fifth moment, which is the time when the S1 interface receives the TAU Request message;

[0178] When the fallback process uses redirection fallback, the start time of the fallback initiation phase is the first moment, and the end time of the fallback initiation phase is the sixth moment, which is the time when the N2 interface receives the UE Context release request message; the start time of the fallback execution phase is the sixth moment, and the end time of the fallback execution phase is the seventh moment, which is the time when the N2 interface receives the UE Context release command message; the start time of the fallback completion phase is the seventh moment, and the end time of the fallback completion phase is the fifth moment.

[0179] The 4G location update completion phase begins at the fifth hour and ends at the eighth hour, which is the time when the S1 interface receives the TAU Accepted message.

[0180] The 4G-GUTI allocation completion phase begins at time eight and ends at time nine. Time nine is the time when the S1 interface receives the TAU complete message.

[0181] The start time of the 4G dedicated network establishment initiation phase is the ninth moment, and the end time of the 4G dedicated network establishment initiation phase is the tenth moment. The tenth moment is the time when the S1 interface receives the E-RAB Setup Request message carrying QCI=1.

[0182] The start time of the 4G dedicated bearer establishment completion phase is the tenth time, and the end time of the 4G dedicated bearer establishment completion phase is the eleventh time. At the eleventh time, the S1 interface receives a NAS layer message carrying QCI=1. The NAS layer message is Activate dedicated EPS bearer context Accept.

[0183] The location reporting phase begins at time 11. The cutoff time for the calling side of the location reporting phase is the time when the calling SBC receives the initial INVITE message through the Mw interface. The cutoff time for the called side of the location reporting phase is the time when the called SBC receives the first RAR message through the Rx interface or the time when the PCRF sends the first RAR message.

[0184] In one embodiment, the duration of each sub-stage delay segment is determined, including:

[0185] Extract the signaling timestamp from the MAC address block of the interface signaling stream;

[0186] Based on the signaling timestamp and the start and end times of each sub-stage delay segment, the duration of each sub-stage delay segment is determined.

[0187] In one embodiment, after filling the occupied time back into the delay record positions corresponding to the delay segments of each sub-stage in the integrated call detail record, the process includes:

[0188] The data statistics equipment summarizes the comprehensive call detail records and generates latency statistics according to the dimension type and time granularity. The dimension types include provincial dimension, city dimension and network element dimension.

[0189] Figure 6 An example is a schematic diagram of the physical structure of an electronic device, such as... Figure 6 As shown, the electronic device may include: a processor 610, a communication interface 620, a memory 630, and a communication bus 640, wherein the processor 610, the communication interface 620, and the memory 630 communicate with each other via the communication bus 640. The processor 610 can call a computer program in the memory 630 to execute the steps of the time delay segmentation monitoring method, such as including:

[0190] Obtain the interface signaling code stream in the 5G call service process, and determine whether the 5G call service process is the same call process of the same user based on the interface signaling code stream. If so, associate the service process data corresponding to the service interface of the 5G call service process to form the calling call detail record and the called call detail record.

[0191] The calling party's call detail record (CDR) and the called party's call detail record (CDR) are associated and combined to obtain a comprehensive CDR for the 5G call service process.

[0192] The 5G call service process includes an end-to-end 5G voice call process and a call fallback process. The end-to-end 5G voice call process and the call fallback process are segmented and delimited to obtain several sub-stage delay segments.

[0193] The time occupied by each sub-stage delay segment is determined, and the occupied time is filled back into the delay record position corresponding to each sub-stage delay segment in the integrated call detail record.

[0194] Furthermore, the logical instructions in the aforementioned memory 630 can be implemented as software functional units and, when sold or used as independent products, can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the prior art, or a part of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute all or part of the steps of the methods described in the various embodiments of this application. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, portable hard drives, read-only memory (ROM), random access memory (RAM), magnetic disks, or optical disks.

[0195] On the other hand, this application also provides a computer program product, which includes a computer program that can be stored on a non-transitory computer-readable storage medium. When the computer program is executed by a processor, the computer can perform the steps of the latency segmentation monitoring method provided in the above embodiments, such as including:

[0196] Obtain the interface signaling code stream in the 5G call service process, and determine whether the 5G call service process is the same call process of the same user based on the interface signaling code stream. If so, associate the service process data corresponding to the service interface of the 5G call service process to form the calling call detail record and the called call detail record.

[0197] The calling party's call detail record (CDR) and the called party's call detail record (CDR) are associated and combined to obtain a comprehensive CDR for the 5G call service process.

[0198] The 5G call service process includes an end-to-end 5G voice call process and a call fallback process. The end-to-end 5G voice call process and the call fallback process are segmented and delimited to obtain several sub-stage delay segments.

[0199] The time occupied by each sub-stage delay segment is determined, and the occupied time is filled back into the delay record position corresponding to each sub-stage delay segment in the integrated call detail record.

[0200] On the other hand, embodiments of this application also provide a processor-readable storage medium storing a computer program for causing a processor to perform the steps of the methods provided in the above embodiments, such as including:

[0201] Obtain the interface signaling code stream in the 5G call service process, and determine whether the 5G call service process is the same call process of the same user based on the interface signaling code stream. If so, associate the service process data corresponding to the service interface of the 5G call service process to form the calling call detail record and the called call detail record.

[0202] The calling party's call detail record (CDR) and the called party's call detail record (CDR) are associated and combined to obtain a comprehensive CDR for the 5G call service process.

[0203] The 5G call service process includes an end-to-end 5G voice call process and a call fallback process. The end-to-end 5G voice call process and the call fallback process are segmented and delimited to obtain several sub-stage delay segments.

[0204] The time occupied by each sub-stage delay segment is determined, and the occupied time is filled back into the delay record position corresponding to each sub-stage delay segment in the integrated call detail record.

[0205] The processor-readable storage medium can be any available medium or data storage device that the processor can access, including but not limited to magnetic memory (e.g., floppy disk, hard disk, magnetic tape, magneto-optical disk (MO)), optical memory (e.g., CD, DVD, BD, HVD), and semiconductor memory (e.g., ROM, EPROM, EEPROM, non-volatile memory (NAND FLASH), solid-state drive (SSD)).

[0206] The device embodiments described above are merely illustrative. The units described as separate components may or may not be physically separate. The components shown as units may or may not be physical units; that is, they may be located in one place or distributed across multiple network units. Some or all of the modules can be selected to achieve the purpose of this embodiment according to actual needs. Those skilled in the art can understand and implement this without any creative effort.

[0207] Through the above description of the embodiments, those skilled in the art can clearly understand that each embodiment can be implemented by means of software plus necessary general-purpose hardware platforms, and of course, it can also be implemented by hardware. Based on this understanding, the above technical solutions, in essence or the part that contributes to the prior art, can be embodied in the form of a software product. This computer software product can be stored in a computer-readable storage medium, such as ROM / RAM, magnetic disk, optical disk, etc., and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute the methods described in the various embodiments or some parts of the embodiments.

[0208] Finally, it should be noted that the above embodiments are only used to illustrate the technical solutions of this application, and are not intended to limit them. Although this application has been described in detail with reference to the foregoing embodiments, those skilled in the art should understand that modifications can still be made to the technical solutions described in the foregoing embodiments, or equivalent substitutions can be made to some of the technical features. Such modifications or substitutions do not cause the essence of the corresponding technical solutions to deviate from the spirit and scope of the technical solutions of the embodiments of this application.

Claims

1. A time delay segmentation monitoring method, characterized in that, include: The interface signaling code stream in the 5G call service process is obtained. Based on the interface signaling code stream, it is determined whether the 5G call service process is the same call process of the same user. If so, the service process data corresponding to the service interface of the 5G call service process is associated to form the calling call detail record and the called call detail record. The calling party's call detail record (CDR) and the called party's call detail record (CDR) are associated and synthesized to obtain the comprehensive CDR of the 5G call service process. The 5G call service process includes an end-to-end 5G voice call process and a call fallback process. The end-to-end 5G voice call process and the call fallback process are respectively divided into delay segments and delimited to obtain several sub-stage delay segments. The time occupied by each sub-stage delay segment is determined, and the occupied time is filled back into the delay record position corresponding to each sub-stage delay segment in the integrated call detail record; The interface signaling stream includes the N2 interface signaling stream, the N26 interface signaling stream, the S1 interface signaling stream, and the IMSSIP message signaling stream; The process of determining whether the 5G call service flow is the same call flow of the same user based on the interface signaling code stream includes: If the values ​​of AMF UE NGAP ID and RAN UE NGAP ID are the same in the N2 interface signaling stream, and the source TEID, destination TEID, source IP address, destination IP address, source port, and destination port in the N26 interface signaling stream are all unique, and the values ​​of MME UE S1AP ID and eNB UE S1AP ID are the same in the S1 interface signaling stream, and the Call ID in the IMSSIP message signaling stream is unique, then it is determined that the 5G call service process is the same call process of the same user. The association of business process data corresponding to the business interface of the 5G call service process includes: In the mobility registration process of the 5G call service process, SUPI and 5G-GUTI are obtained. The GPSI number of the 5G call service process is obtained according to the tuple binding relationship between SUPI and 5G-GUTI. The GPSI number is then filled back into each service process of the N2 interface and N26 interface. In the LTE attach process of the 5G call service process, the IMSI and 4G-GUTI are obtained. The MSISDN number of the 5G call service process is determined according to the tuple binding relationship between the IMSI and the 4G-GUTI. The MSISDN number is then filled back into each service process of the S1 interface and the IMS domain. On the calling and called sides, the business process data corresponding to the service interfaces with the same interface signaling code stream generation time, the same mobile user number, the same user identification code, and the same ICID information are associated respectively. The ICID information is information extracted from SIP messages. The step of associating and synthesizing the calling party's call detail record and the called party's call detail record includes: The calling call detail records and called call detail records that have the same interface signaling code stream generation time, the same mobile user number, the same user identification code, and the same ICID information are associated and merged. The step of performing delay segmentation and delimitation on the end-to-end 5G voice call process and the call fallback process, respectively, wherein performing delay segmentation and delimitation on the end-to-end 5G voice call process includes: Based on the phase characteristics of SIP message interaction and the responsibility division rules between the core network and the radio, the end-to-end 5G voice call process is divided into 12 sub-phase delay segments. The 12 sub-phase delay segments are, in order, the calling bearer establishment phase, the calling call control phase, the IMS addressing phase, the called call control phase, the called radio establishment phase, the called bearer establishment phase, the 183 forwarding phase, the calling radio establishment phase, the calling update phase, the update forwarding phase, the called update phase, and the Ring forwarding phase. The start time of the calling bearer establishment phase is the time when the calling SBC receives the INVITE message sent by the calling UE through the Gm interface, and the end time of the calling bearer establishment phase is the first time point, which is the time when the calling S-CSCF receives the first INVITE message sent by the calling SBC through the Mw interface. The start time of the calling party's call control phase is the first time point, and the end time of the calling party's call control phase is the second time point, which is the time when the calling party's S-CSCF receives the INVITE message sent by the last TAS on the calling party's side. The start time of the IMS addressing phase is the second time point, and the end time of the IMS addressing phase is the third time point, which is the time when the called S-CSCF sends the INVITE message to the first TAS on the called side. The start time of the called party call control phase is the third time point, and the end time of the called party call control phase is the fourth time point. The fourth time point is the time when the called party SBC sends the INVITE message to the called party UE through the Gm interface. The start time of the called radio establishment phase is the fourth time point, and the end time of the called radio establishment phase is the fifth time point. The fifth time point is the time when the called SBC receives the 183 message sent by the called UE through the Gm interface. The start time of the called bearer establishment phase is the fifth time point, and the end time of the called bearer establishment phase is the sixth time point. The sixth time point is the time when the called S-CSCF receives the first 183 message sent by the called SBC through the Mw interface. The start time of the 183 forwarding phase is the sixth time point, and the end time of the 183 forwarding phase is the seventh time point. The seventh time point is the time when the calling SBC sends the 183 message to the calling UE through the Mw interface. The start time of the calling radio establishment phase is the seventh time point, and the end time of the calling radio establishment phase is the eighth time point. The eighth time point is the time when the calling SBC receives the PRACK message sent by the calling UE through the Mw interface. The start time of the calling party's Update phase is the eighth time point, and the end time of the calling party's Update phase is the ninth time point. The ninth time point is the time when the calling party's SBC receives the UPDATE message sent by the calling party's UE through the Mw interface. The start time of the Update forwarding phase is the ninth time point, and the end time of the Update forwarding phase is the tenth time point. The tenth time point is the time when the called SBC sends the UPDATE message to the called UE through the Mw interface. The start time of the called party Update phase is the tenth time point, and the end time of the called party Update phase is the eleventh time point. The eleventh time point is the time when the called party SBC receives the 180Ring message sent by the called party UE through the Mw interface. The start time of the Ring forwarding phase is the eleventh time point, and the end time of the Ring forwarding phase is the time when the calling SBC sends the 180 Ring message to the calling UE through the Mw interface. The step of performing delay segmentation and delimitation on the end-to-end 5G voice call process and the call fallback process, respectively, wherein performing delay segmentation and delimitation on the call fallback process includes: Based on the phase characteristics of the signaling interaction in the call fallback process and the responsibility division rules between the core network and the radio, the call fallback process is divided into 11 sub-phase delay segments. The 11 sub-phase delay segments are, in order: dedicated loadout establishment initiation phase, fallback triggering phase, fallback initiation phase, fallback execution phase, fallback completion phase, 4G location update initiation phase, 4G location update completion phase, 4G-GUTI allocation completion phase, 4G dedicated loadout establishment initiation phase, 4G dedicated loadout establishment completion phase, and location reporting phase. The starting time of the dedicated loadout establishment phase on the calling side is the time when the calling SBC receives the initial INVITE message from the calling UE through the Gm interface, and the starting time on the called side is the time when the called SBC receives the 183 message from the called UE through the Gm interface. The ending time of the dedicated loadout establishment phase is the time when the N2 interface receives the first PDU Session Resource Modify Request message carrying fiveQI=1. The start time of the fallback triggering phase is the time when the N2 interface receives the PDU Session Modify Request message, and the end time of the fallback triggering phase is the first moment, which is the time when the N2 interface receives the PDU Session Modify Response message. When the fallback process uses a switching fallback method, the start time of the fallback initiation phase is the first moment, and the end time is the second moment, which is the time when the N2 interface receives the Handover Required message; the start time of the fallback execution phase is the second moment, and the end time is the third moment, which is the time when the N2 interface receives the HandoverCommand message; the start time of the fallback completion phase is the third moment, and the end time is the fourth moment, which is the time when the S1 interface receives the Handover Notify message or the Relocation Complete Ack message; the start time of the 4G location update initiation phase is the fourth moment, and the end time is the fifth moment, which is the time when the S1 interface receives the TAU Request message; When the fallback process uses a redirected fallback method, the start time of the fallback initiation phase is the first moment, and the end time of the fallback initiation phase is the sixth moment, which is the time when the N2 interface receives the UE Context release request message; the start time of the fallback execution phase is the sixth moment, and the end time of the fallback execution phase is the seventh moment, which is the time when the N2 interface receives the UE Context release command message; the start time of the fallback completion phase is the seventh moment, and the end time of the fallback completion phase is the fifth moment. The start time of the 4G location update completion phase is the fifth moment, and the end time of the 4G location update completion phase is the eighth moment, which is the time when the S1 interface receives the TAU Accepted message. The start time of the 4G-GUTI allocation completion phase is the eighth time, and the end time of the 4G-GUTI allocation completion phase is the ninth time, which is the time when the S1 interface receives the TAU complete message. The start time of the 4G dedicated network establishment initiation phase is the ninth moment, and the end time of the 4G dedicated network establishment initiation phase is the tenth moment. The tenth moment is the time when the S1 interface receives the E-RAB SetupRequest message carrying QCI=1. The start time of the 4G dedicated bearer establishment completion phase is the tenth moment, and the end time of the 4G dedicated bearer establishment completion phase is the eleventh moment. The eleventh moment is when the S1 interface receives a NAS layer message carrying QCI=1. The NAS layer message is Activate dedicated EPS bearer context Accept. The start time of the location reporting phase is the eleventh moment. The cutoff time of the calling side of the location reporting phase is the time when the calling SBC receives the initial INVITE message through the Mw interface. The cutoff time of the called side of the location reporting phase is the time when the called SBC receives the first RAR message through the Rx interface or the time when the PCRF sends the first RAR message.

2. The time delay segmentation monitoring method according to claim 1, characterized in that, The determination of the time occupied by each sub-stage delay segment includes: Extract the signaling timestamp from the MAC address block of the interface signaling code stream; Based on the signaling timestamp and the start and end times of each sub-stage delay segment, the duration of each sub-stage delay segment is determined.

3. The time delay segmentation monitoring method according to claim 1, characterized in that, After filling the occupied time back into the delay record positions corresponding to the delay segments of each sub-stage in the integrated call detail record, the process includes: The comprehensive call detail records are aggregated by data statistics equipment, and latency statistics are generated according to dimension type and time granularity. The dimension types include provincial dimension, prefecture-level city dimension and network element dimension.

4. A time delay segmentation monitoring device, characterized in that, The application of the delay segmentation monitoring method as described in claim 1 includes: The interface data association module is used to obtain the interface signaling code stream in the 5G call service process, and determine whether the 5G call service process is the same call process of the same user based on the interface signaling code stream. If so, the service process data corresponding to the service interface of the 5G call service process is associated to form the calling call detail record and the called call detail record. The call detail record association module is used to associate and synthesize the calling call detail record and the called call detail record to obtain the comprehensive call detail record of the 5G call service process. The delay segmentation and delimitation module is used to perform delay segmentation and delimitation on the end-to-end 5G voice call process and the call fallback process respectively, to obtain several sub-stage delay segments. The time occupancy determination module is used to determine the time occupancy of each sub-stage delay segment and fill the occupancy time back into the delay record position corresponding to each sub-stage delay segment in the integrated call detail record.

5. An electronic device comprising a processor and a memory storing a computer program, characterized in that, When the processor executes the computer program, it implements the steps of the delay segmentation monitoring method according to any one of claims 1 to 3.

6. A computer program product, comprising a computer program, characterized in that, When the computer program is executed by the processor, it implements the steps of the delay segmentation monitoring method according to any one of claims 1 to 3.

Images