Recording processing method and device, equipment, medium and product
By acquiring call record sets from multiple interfaces in call scenarios such as 5G new calls, generating a master call record set and associating them, the problem of missing call synthesis record sets is solved, and the quality of the record set and the accuracy of abnormal event location are improved.
Patent Information
- Application Number
- CN202511694309.X
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2025-11-18
- Publication Date
- 2026-02-06
AI Technical Summary
Existing technologies often result in omissions of call records when establishing call synthesis record sets for call scenarios such as 5G new calls, VoLTE, EPSFB, and VoNR, leading to poor record set quality and affecting the accuracy of abnormal event location and delimitation.
By acquiring call record sets from multiple target interfaces, especially the Gm and Mw interfaces, a call master record set is generated. Records belonging to the same call as the call master record are then filtered from the record sets of other interfaces and associated with them to generate a call composite record set, thus avoiding the problem of missing records from a single interface.
It improves the quality of the call synthesis record set, ensures the accuracy of abnormal event location and delimitation, avoids the problem of record omission, and enhances the integrity and accuracy of the call process.
Smart Images
Figure CN121486497A_ABST
Abstract
Description
TECHNICAL FIELD
[0001] The present application relates to the technical field of communication, and in particular to a record processing method and device, equipment, medium and storage medium. BACKGROUND
[0002] In related technologies, in order to locate and delimit abnormal events of calls in 5G new call, VoLTE, EPSFB, VoNR and other call scenarios, and analyze call abnormalities in these scenarios, it is necessary to establish a call synthesis record set of calls in these scenarios. At present, when establishing a call record set of calls in these scenarios, the call record is often missed, so that the quality of the established call synthesis record set is poor. Based on the call synthesis record set, the abnormal event positioning and delimitation of the calls in these scenarios will be inaccurate. Therefore, a solution is needed to improve the quality of the call synthesis record set of 5G new call and other call scenarios. SUMMARY
[0003] The purpose of the embodiments of the present application is to provide a record processing method to improve the quality of the call record set of 5G new call and other call scenarios.
[0004] In a first aspect, the embodiments of the present application provide a record processing method, which comprises: obtaining a call record set of each target interface in a plurality of target interfaces; wherein the plurality of target interfaces are interfaces involved in a call process of a target call scenario, and the plurality of target interfaces comprise a Gm interface and a Mw interface; generating a call main record set based on the call record set of the first interface; wherein the first interface comprises the Gm interface and the Mw interface; and a call main record in the call main record set is obtained by associating records belonging to the same call in the call record set of the Gm interface and the call record set of the Mw interface; In the call record set of the second interface, filtering records belonging to the same call as the call main record in the call main record set, and associating the filtered records with the call main record to generate a call synthesis record corresponding to the call main record; wherein the second interface comprises interfaces other than the Gm interface and the Mw interface in the plurality of target interfaces; generating a call synthesis record set based on the call synthesis record corresponding to each call main record in the call main record set.
[0005] In a second aspect, the embodiments of the present application provide a record processing device, which comprises: The acquisition module is configured to acquire a call record set of each target interface in a plurality of target interfaces; wherein the plurality of target interfaces are interfaces involved in a call flow of a target call scenario, and the plurality of target interfaces include a Gm interface and an Mw interface; The main record generation module is configured to generate a call main record set based on the call record set of the first interface; wherein the first interface includes the Gm interface and the Mw interface; and a call main record in the call main record set is obtained by associating records belonging to a same call in a union set of the call record set of the Gm interface and the call record set of the Mw interface; The synthetic record generation module is configured to filter, in a call record set of a second interface, records belonging to a same call as a call main record in the call main record set, associate the filtered records with the call main record, and generate a call synthetic record corresponding to the call main record; wherein the second interface includes an interface other than the Gm interface and the Mw interface in the plurality of target interfaces. The record set generation module is configured to generate a call synthetic record set based on the call synthetic record corresponding to each call main record in the call main record set.
[0006] In a third aspect, an embodiment of the present application provides a record processing device, which includes: A memory having a computer program stored thereon; A processor configured to execute the computer program to implement the steps of the record processing method.
[0007] In a fourth aspect, an embodiment of the present application provides a computer readable storage medium having a computer program stored thereon, wherein the computer program, when executed by a processor, implements the steps of the record processing method.
[0008] In a fifth aspect, an embodiment of the present application provides a computer program product including a computer program, wherein the computer program, when executed by a processor, implements the steps of the record processing method.
[0009] The above technical solution provided by the embodiments of the present application can acquire a call record set of each target interface in a plurality of target interfaces, generate a call main record set based on the call record set of the Gm interface and the Mw interface in the plurality of target interfaces, filter, in a call record set of each interface other than the Gm interface and the Mw interface in the plurality of target interfaces, records belonging to a same call as a call main record in the call main record set, associate the filtered records with the call main record, generate a call synthetic record corresponding to the call main record, and generate a call synthetic record set based on the call synthetic record corresponding to each call main record in the call main record set, thereby avoiding the problem of record omission caused by taking a call record of a single interface as a call main record and improving the quality of the call synthetic record set. Attached Figure Description
[0010] To more clearly illustrate the technical solutions in the embodiments of this application or the prior art, the drawings used in the description of the embodiments or the prior art will be briefly introduced below. Obviously, the drawings described below are only some embodiments recorded in this application. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.
[0011] Figure 1 This is a flowchart illustrating the recording processing method of some embodiments of this application; Figure 2 This is a schematic diagram of the call record set acquisition process according to some embodiments of this application; Figure 3 This is a schematic diagram illustrating the call master record set generation process of some embodiments of this application; Figure 4 This is a schematic diagram of the record filtering process in some embodiments of this application; Figure 5 This is a schematic diagram illustrating the process of determining the target time amount in some embodiments of this application; Figure 6 This is a schematic diagram illustrating the process of generating call synthesis record sets according to some embodiments of this application; Figure 7 These are modified examples of call synthesis records in some embodiments of this application; Figure 8 These are examples of modifications to call logs in some embodiments of this application; Figure 9 These are examples of label adding processes in some embodiments of this application; Figure 10 This is a schematic diagram of a recording processing apparatus according to some embodiments of this application. Detailed Implementation
[0012] This application provides a recording processing method, apparatus, device, medium, and product.
[0013] To enable those skilled in the art to better understand the technical solutions in this application, the technical solutions in the embodiments of this application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of this application, and not all embodiments. Based on the embodiments of this application, all other embodiments obtained by those skilled in the art without creative effort should fall within the scope of protection of this application.
[0014] In the related art, in order to locate and delimit abnormal events of calls in 5G new call, VoLTE, EPSFB, VoNR and other call scenarios, and analyze call abnormalities of these scenarios, it is necessary to establish a call synthesis record set of these scenarios. Currently, when establishing the call synthesis record of these scenarios, the call record is often missed, resulting in poor quality of the established call synthesis record set. Based on the call synthesis record set, the call in these scenarios is located and delimited, and the problem of inaccurate abnormal positioning and delimitation may occur.
[0015] The inventor of the present application found in the process of implementing the present application that the current poor quality of the call synthesis record set is caused by taking the call record of a single interface as the call main record when establishing the call record set.
[0016] Specifically, for 5G new call, VoLTE, EPSFB, VoNR and other call scenarios, the call process involves multiple interfaces of multiple domains, including Gm interface, Mw interface and Rx interface of IMS domain, N1 / N2 interface, N4 interface, N7 interface, N11 interface and N26 interface of 5GC domain, S1MME interface of EPC domain, and DC-1 interface, DC-3 interface, DC-5 interface, DC-7 interface and DC-9 interface of 5G new call domain.
[0017] In the related art, a DPI collection device can be set for these interfaces to collect XDR records through the DPI collection device, and a call record set of each interface can be obtained based on the XDR record set of each interface. According to the roaming strategy of the existing network, for a local user without roaming out, when a call occurs, the Gm interface and the Mw interface will have corresponding call signaling, and accordingly, the call record set of the Gm interface and the Mw interface will have corresponding records. For a local user roaming out, when a call occurs, the Gm interface has no corresponding call signaling, but the Mw interface has corresponding call signaling, and accordingly, the call record set of the Gm interface has no corresponding record, and the call record set of the Mw interface has corresponding records. For a foreign roaming user, when a call occurs, the Gm interface has corresponding call signaling, but the Mw interface has no corresponding call signaling, and accordingly, the call record set of the Gm interface has corresponding records, and the call record set of the Mw interface has no corresponding call record. In addition, for call scenarios such as 5G new call, VoLTE call, VoNR call, etc., if the dedicated bearer establishment fails, the call message of the Gm interface will not be forwarded to the Mw interface, the Gm interface has corresponding call signaling, and the Mw interface has no corresponding call signaling, and accordingly, the call record set of the Gm interface has corresponding records, and the call record set of the Mw interface has no corresponding call record. If the record of the call record set of the Gm interface is used as the main record of the synthetic call record, the call process of the local user roaming out will be discarded. If the record of the call record set of the Mw interface is used as the main record of the synthetic call record, the call process of the Gm interface failure will be discarded.
[0018] To this end, an embodiment of the present application provides a record processing method. In the record processing method, a call record set of each target interface in a plurality of target interfaces is obtained, a call main record set is generated based on the call record sets of the Gm interface and the Mw interface in the plurality of target interfaces, and then, in the call record set of each interface other than the Gm interface and the Mw interface in the plurality of target interfaces, records belonging to the same call as the call main record in the call main record set are screened out, the screened-out records are associated with the call main record, a call synthetic record corresponding to the call main record is generated, and then, based on the call synthetic record corresponding to each call main record in the call main record set, a call synthetic record set is generated. Thus, the record omission problem caused by taking the call record of a single interface as the call main record can be avoided, and the quality of the call synthetic record set can be improved.
[0019] Please refer to Figure 1 , which is a flowchart of the record processing method of some embodiments of the present application. As shown in Figure 1 , in some embodiments of the present application, the record processing method can include the following steps: S102, a call record set of each target interface in a plurality of target interfaces is obtained.
[0020] The multiple target interfaces are interfaces involved in a call flow of the target call scenario.
[0021] Exemplarily, the target call scenario can include a 5G new talk call scenario, a VoLTE call scenario, an EPSFB call scenario, and a VoNR call scenario. The multiple target interfaces can include a Gm interface, a Mw interface, and a Rx interface of an IMS domain, an N1 / N2 interface, an N4 interface, an N7 interface, an N11 interface, and an N26 interface of a 5G core (5GC) domain, an S1MME interface of an evolved packet core (EPC) domain, and a DC-1 interface, a DC-3 interface, a DC-5 interface, a DC-7 interface, and a DC-9 interface of a 5G new talk domain. The first interface can be the Gm interface and the Mw interface, and the second interface can be the Rx interface, the N1 / N2 interface, the N4 interface, the N7 interface, the N11 interface, the N26 interface, the S1MME interface, and the DC-1 interface, the DC-3 interface, and the DC-5 interface.
[0022] The call record set can be an extended data record (XDR) record set of the call flow, which can include multiple XDR records of the call flow, i.e., multiple call records. The call record set of one target interface is a set of XDR records of the XDR record set of the interface.
[0023] S104, generating a call master record set based on the call record set of the first interface.
[0024] The first interface has multiple interfaces, which can include the Gm interface and the Mw interface in the multiple target interfaces.
[0025] The call master record set is a set of call master records, which can include multiple call master records. Each call master record can be obtained by associating records belonging to the same call in the union of the call record set of the Gm interface and the call record set of the Mw interface. One call master record corresponds to one call.
[0026] S106, in the call record set of the second interface, filtering records belonging to the same call as the call master records in the call master record set, and associating the filtered records with the call master records to generate call synthesis records corresponding to the call master records.
[0027] The second interface can be multiple, which can include each interface of the multiple target interfaces except the Gm interface and the Mw interface, such as the Rx interface, the N1 / N2 interface, the N4 interface, the N7 interface, the N11 interface, the N26 interface, the S1MME interface, the DC-1 interface, the DC-3 interface, and the DC-5 interface. The records belonging to the same call as the call main record can be screened in the call record set of each second interface, the screened records are associated with the call main record, and the call synthesis record corresponding to the call main record is generated.
[0028] For each call main record in the call main record set, the records belonging to the same call as the call main record can be screened in the call record set of each second interface, the screened records are associated with the call main record, and the call synthesis record corresponding to the call main record is generated. Thus, the call synthesis record corresponding to each call main record in the call main record set is generated.
[0029] In S108, the call synthesis record set is generated based on the call synthesis record corresponding to each call main record in the call main record set.
[0030] The call synthesis record set can be a collection of the call synthesis record corresponding to each call main record in the call main record set.
[0031] In the above embodiments, the call main record set is generated based on the call record set of the Gm interface and the Mw interface in the multiple target interfaces, the records belonging to the same call as the call main record in the call main record set are screened in the call record set of the interface other than the Gm interface and the Mw interface in the multiple target interfaces, the screened records are associated with the call main record, and the call synthesis record is generated, which can avoid the record omission problem caused by taking the call XDR record of a single interface as the call main record, and improve the quality of the call synthesis record set.
[0032] Please refer to Figure 2 The flowchart of the call record set acquisition process of some embodiments of the present application is shown. As Figure 2 In some embodiments, the above step S102 of acquiring the call record set of each target interface in the multiple target interfaces can specifically include the following steps: In S202, the target interface is determined based on the target call scenario.
[0033] Exemplarily, the target call scenarios can include a 5G new call scenario, a VoLTE call scenario, an EPSFB call scenario and a VoNR call scenario. The call flows of the target call scenarios involve interfaces including Gm interface, Mw interface and Rx interface of IMS domain, N1 / N2 interface, N4 interface, N7 interface, N11 interface and N26 interface of 5GC domain, S1MME interface of EPC domain and DC-1 interface, DC-3 interface, DC-5 interface, DC-7 interface and DC-9 interface of 5G new call domain. Each interface of each domain involved in the target call scenarios can be determined as a target interface.
[0034] S204, acquire an XDR record set of the target interface.
[0035] The XDR record set of the target interface is a single-interface XDR record set of the interface, which can include a plurality of XDR records, and one XDR record can be a transaction detailed record of the interface. A DPI collection device can be deployed at each target interface, and the XDR records of each target interface can be collected through the DPI collection device of each target interface, so as to obtain the XDR record set of each interface.
[0036] S206, in the XDR record set of the target interface, filter the XDR records of the call flow, and generate a call record set of the target interface based on the filtered records.
[0037] The XDR record set of the target interface is a collection of XDR records of all flows through the interface, which can include XDR records of the call flow, and can also include XDR records of non-call flows, such as XDR records of IMS registration flow. The XDR records of the call flow can be filtered out from the XDR record set of the target interface, and the call record set of the target interface can be generated based on the filtered XDR records of the call flow. Each record in the record set is an XDR record of a call flow, that is, a call record.
[0038] In the above embodiment, the call record set of the target interface is generated by filtering the XDR records of the call flow from the XDR record set of the target interface, which can filter out records irrelevant to the call, reduce the data amount for subsequent processing, and improve the efficiency of subsequent processing.
[0039] Further, for subsequent processing, the filtered records can be normalized when the call record set is generated based on the filtered records, and the call record set can be generated based on the normalized records.
[0040] The normalization processing is configured to convert the filtered records into a specified uniform format. For example, the value format of a specified field in the filtered records is converted into the specified uniform format. The specified uniform format can be determined according to the format specification of the XDR record.
[0041] Referring to Figure 3 is a schematic diagram of a process of generating a call master record set according to some embodiments of the present application. As shown in Figure 3 In some embodiments, the step S104 of generating the call master record set based on the call record set of the first interface can include the following steps: S302, dividing the records belonging to the same call in the call record set of the Gm interface and the call record set of the Mw into the same record subset to obtain a plurality of record subsets.
[0042] Each record subset corresponds to a call, and the records in the same record subset belong to the same call.
[0043] In implementation, for the call record set of the Gm interface, the records belonging to the same call in the call record set can be divided into the same record subset to obtain a plurality of first record subsets. For the call record set of the Mw interface, the records belonging to the same call in the call record set can be divided into the same record subset to obtain a plurality of second record subsets. The record subsets belonging to the same call in the plurality of first record subsets and the plurality of second record subsets can be matched, and the matched first record subset and the second record subset can be associated to generate a record subset. For each first record subset that has not matched the second record subset, it can be taken as a record subset. For each second record subset that has not matched the first record subset, it can be taken as a record subset. In this way, a plurality of record subsets can be obtained, and each record subset corresponds to a call.
[0044] The determination of whether the records belong to the same call can be based on the field values of the key fields in the records.
[0045] For example, for any two records in the call record set of the Gm interface, it can be judged whether the field values of the key fields such as CALL_SIDE, CALLID, MSISDN, CALLING_NUMBER, CALLED_NUMBER, Service_type in the two records are the same. If the same, it can be determined that the two records belong to the same call, and the two records are divided into the same first record subset. If not, it can be determined that the two records do not belong to the same call, and the two records are divided into different first record subsets. For any two records in the call record set of the Mw interface, it can be judged whether the field values of the key fields such as CALL_SIDE, MSISDN, ICID, Service_type in the two records are the same. If the same, it can be determined that the two records belong to the same call, and the two records are divided into the same second record subset. For any first record subset and any second record subset, based on the association between the field values of the key fields such as CALLID, CALLING_NUMBER, CALLED_NUMBER in the two record subsets and the signaling flow, it can be determined whether the two record subsets belong to the same call. If yes, the two record subsets are associated to generate a record subset.
[0046] Of course, in addition to the above manner, other manners can also be used to obtain the multiple record subsets.
[0047] For example, the call record set of the Gm interface and the call record set of the Mw can be associated to obtain the union set of the call record set of the Gm interface and the call record set of the Mw. The call records belonging to the same call in the union set are divided into the same record subset to obtain the multiple record subsets.
[0048] S304, the records in the record subset are associated to generate a call main record corresponding to the record subset.
[0049] For each record subset, the operation of the above step S304 can be performed, so that the call main record corresponding to each record subset can be obtained.
[0050] S306, based on the call main record corresponding to each record subset in the multiple record subsets, a call main record set is generated.
[0051] The call main record can be a collection of the call main records corresponding to each record subset in the multiple record subsets.
[0052] In the above embodiment, by dividing the records belonging to the same call in the call record set of the Gm interface and the call record set of the Mw into the same record subset, obtaining a plurality of record subsets, associating the records in each record subset, generating the call main record corresponding to each record subset, and generating the call main record set based on the call main record corresponding to each record subset, the record omission problem of generating the call main record set based on the call record set of a single interface can be avoided, and the integrity of the call main record set can be improved.
[0053] To improve the association accuracy, in some embodiments of the present application, the records belonging to the same call as the call main record can be screened in the call record set of the second interface through a time ambiguity association algorithm. Please refer to Figure 4 The schematic diagram of the record screening process of some embodiments of the present application is shown in FIG. 6. As shown in FIG. 6, the step S106 of screening the records belonging to the same call as the call main record in the call record set of the second interface can specifically include the following steps: Figure 4 S402, determining the first process start time and the first process end time based on the call main record.
[0054] The first process start time is the start time of the process recorded by the call main record, and the first process end time is the end time of the process recorded by the call main record.
[0055] S404, advancing the first process start time by a target time amount to obtain the advanced first process start time.
[0056] The target time amount can be a predetermined time amount, and the offset start time is the first process start time.
[0057] S406, screening the associated records of the call main record in the call record set of the second interface.
[0058] The associated records of the call main record are the records associated with the same user as the call main record. In implementation, the associated records of the call main record can be screened in each call record set of the second interface based on the field value of the target field.
[0059] For example, the target field can be the MSISD field. For any record in the call record set of the second interface, if the field value of the MSISD field of the record is the same as that of the call main record, the record can be determined as the associated record of the call main record.
[0060] S408, determining the second process start time based on the associated record.
[0061] The second process start time is the start time of the process recorded by the associated record.
[0062] S410, if the second flow start time is not earlier than the first flow start time and not later than the first flow end time, determining that the association record and the call main record belong to the same call.
[0063] Exemplarily, the first flow start time can be T11, the first flow end time can be T12, the target time amount can be 2000ms, the second flow start time can be T21, the offset start time can be T11-2000ms, if T21 is located in the time period from T11-2000ms to T12, it can be determined that the association record and the call main record belong to the same call.
[0064] After determining that the association record and the call main record belong to the same call, the association record can be screened out and associated with the call main record.
[0065] In the above embodiment, by advancing the flow start time of the call main record by the target time amount, judging whether the flow start time of the association record is located between the flow start time and the flow end time of the call main record after being advanced, the association record and the call main record can be time fuzzy associated, and the misjudgment caused by the time asynchronization between the flow of the record of the second interface and the flow of the call main record can be avoided.
[0066] The target time amount can be a proper time amount set in advance, which is, for example, 2000ms.
[0067] In order to make the target time amount more accurate, in some embodiments, the target time amount can be dynamically updated. Please refer to Figure 5 The determination process of the target time amount of some embodiments of the present application is shown in the following figure. Figure 5 As shown in the figure, in some embodiments of the present application, the record processing method can further include the following determination process of the target time amount: S502, if the association record and the call main record belong to the same call, determining whether the flow recorded by the association record and the flow recorded by the call main record are in time synchronization state.
[0068] S504, if not, determining the time asynchronization amount between the flow recorded by the association record and the flow recorded by the call main record, taking the time asynchronization amount as a asynchronization amount sample and adding it to the asynchronization amount sample set.
[0069] S506, if the number of asynchronization amount samples in the asynchronization amount sample set reaches the number threshold, updating the target time amount based on the asynchronization amount sample set.
[0070] The quantity threshold can be a pre-set value, for example, 500.
[0071] If the number of out-of-sync samples in the out-of-sync sample set reaches the quantity threshold, a new target time quantity can be recalculated based on the mean and variance of the out-of-sync samples in the out-of-sync sample set, and the original target time quantity is updated using the new target time quantity. For example, the new target time quantity can be calculated based on the following formula:
[0072] wherein, is the target time quantity, is the mean of the out-of-sync samples in the out-of-sync sample set, is the standard deviation of the out-of-sync samples in the out-of-sync sample set, is a set coefficient, for example, 2 or 3.
[0073] If the number of out-of-sync samples in the out-of-sync sample set does not reach the quantity threshold, the steps S502 to S504 can be repeatedly executed to continue collecting out-of-sync samples.
[0074] S508, resetting the out-of-sync sample set to the initial state.
[0075] The out-of-sync sample set is used to collect out-of-sync samples, and the initial state is an empty set.
[0076] In implementation, the steps S502 to S508 can be iteratively executed to dynamically update the target time quantity, so that the target time quantity is kept at an appropriate size, avoiding false association caused by too large target time quantity, and avoiding failure to associate caused by too small target time quantity.
[0077] For example, assuming that the quantity threshold is 500, the initial value of the target time quantity is 2000 ms, and the initial state of the out-of-sync sample set is an empty set. In each iteration, the out-of-sync samples can be continuously stored in the out-of-sync sample set, and the out-of-sync samples are collected. If the collected out-of-sync samples reach 500, a new target time quantity can be calculated based on the mean and variance of the 500 out-of-sync samples, and the current target time quantity is replaced by the new target time quantity, so as to update the current target time quantity. After the update, the out-of-sync sample set can be reset to the initial state, and the next iteration is performed. In this way, the target time quantity can be dynamically updated based on the 500 out-of-sync samples each time the out-of-sync samples reach 500.
[0078] In the above embodiments, by dynamically collecting different synchronization amount samples, when each collected different synchronization amount sample reaches a quantity threshold, a new target time quantity is calculated based on the collected different synchronization amount samples, and the target time quantity is updated, which can keep the target time quantity at an appropriate size, avoiding problems caused by too large or too small target time quantity.
[0079] To further improve the quality of the call synthesis record set, when generating the call synthesis record set, the error data in the call synthesis record can be corrected. Please refer to Figure 6 The generation process of the call synthesis record set of some embodiments of the present application is shown in the figure. As Figure 6 shown, in some embodiments of the present application, the above step S108 generates the call synthesis record set based on the call synthesis record corresponding to each call main record in the call main record set, which can specifically include the following steps: S602, determine the call scenario corresponding to the call synthesis record.
[0080] Among them, the call scenario is, for example, an EPSFB call scenario, a VoNR call scenario, a VoTTE call scenario or a 5G new call call scenario. The call scenario corresponding to the call synthesis record can be the call scenario to which the call synthesis record belongs.
[0081] In implementation, it can be judged whether the flow and field value in the call synthesis record conforms to the judgment rule of the corresponding call scenario, and the call scenario to which the call synthesis record belongs is judged. In order to facilitate subsequent use, the call synthesis record can be added with the label of the call scenario to which it belongs.
[0082] Further, the failure event to which the call synthesis record belongs can be judged, and the failure event label is added to the call synthesis record according to the failure event to which the call synthesis record belongs.
[0083] S604, based on the signaling causality rule and the signaling transmission rule corresponding to the call scenario, correct the error data in the call synthesis record.
[0084] As an example, if the call scenario of the call synthesis record is a 5G new call call scenario, the target signaling message in abnormal state can be determined based on the call synthesis record, and whether the downstream signaling message of the target signaling message is abnormal can be determined based on the transmission rule of the target signaling message in the 5G new call call scenario. If not, it is determined that the abnormal state of the target signaling message is wrong, and the abnormal state of the target signaling message is corrected. For example, as Figure 7 shown, if there is no 180 message in interface D in the call synthesis record, but there is a 180 message in interface C. Based on the transmission rule of the 180 message, it can be determined that there should be a 180 message in interface D, and the abnormal 180 message in interface D can be corrected.
[0085] As another example, if the call scenario of the call synthesis record is a 5G new call call scenario, the target signaling flow in which the abnormal state occurs can be determined based on the call synthesis record, whether the subsequent flow of the target signaling flow fails can be determined according to the causal relationship between the target signaling flow and other signaling flows in the 5G new call call scenario, and if not, the abnormal state of the target signaling flow is corrected. For example, as shown in Figure 8 If there are A flow and B flow on the same interface, A flow is the prerequisite flow of B flow, and B flow is the subsequent flow of A flow, if A flow is in a timeout state and no response A of A flow is received in the call synthesis record, but B flow is in a normal state, based on the causal relationship between A flow and B flow in the 5G new call call scenario, it can be determined that A flow should be in a normal state, and the timeout state of A flow in the call synthesis record can be corrected.
[0086] S606, generating a call synthesis record set based on the corrected call synthesis record.
[0087] Among them, the call synthesis record set can be generated based on the corrected call synthesis record corresponding to each call main record in the call main record set.
[0088] In the above embodiments, by correcting the error data in the call synthesis record based on the signaling transmission rule and the signaling causality rule, and generating the call synthesis record set based on the corrected call synthesis record, the negative impact of the error data on the subsequent first disconnection point dotting and other abnormal positioning and delimitation can be avoided, and the accuracy of the subsequent first disconnection point dotting and other abnormal positioning and delimitation can be improved.
[0089] Further, for subsequent use, in some embodiments, when generating the call synthesis record set based on the corrected call synthesis record, the corrected call synthesis record can be further positioned and delimited, a positioning and delimitation tag is added to the call synthesis record, and the call synthesis record is generated based on the call synthesis record after adding the tag.
[0090] Exemplarily, as shown in Figure 9 The first disconnection point in the call synthesis record can be dotted based on the first disconnection principle of the failure event to generate the dotting information of the record, and then the abnormal positioning and delimitation tag of the call synthesis record can be determined based on the dotting information and the abnormal positioning and delimitation rule of the call synthesis record belonging to the call scenario in the positioning and delimitation rule library, and the positioning and delimitation tag is added to the call synthesis record.
[0091] In applications, after generating a call synthesis record set, target call synthesis records can be selected from the set and output according to user needs for analysis. For example, call synthesis records with call delays within a specified range can be selected from the set for output based on the user's specified call delay range.
[0092] Specifically, when outputting the target call synthesis record, a full call flow view can be generated and output based on the target call synthesis record, and information such as the basic information field, the first disconnection point information field, and tags of the call synthesis record can be output to facilitate user analysis.
[0093] The basic information fields may include MSISDN, call start time, call end time, call origin / end, voice / video, etc., and the tags may include call scenario (VoLTE / EPSFB / VoNR / whether it is a new call) tags, failure event tags, location delimitation tags, etc.
[0094] Of course, the call records for each interface in the target call synthesis record can also be output according to user needs. Among them, if there are multiple call records for the same interface in the target call synthesis record, the call record with the earliest failure or the call record with the earliest process time can be output according to user needs.
[0095] The above describes the recording processing method provided in the embodiments of this application. Based on the same idea, the embodiments of this application also provide a recording processing apparatus. Please refer to... Figure 10 This is a schematic diagram of the modules of a recording processing apparatus according to some embodiments of this application. Figure 10 As shown, in some embodiments of this application, the recording processing apparatus 1000 includes: The acquisition module 1010 is used to acquire the call record set of each of the multiple target interfaces; wherein, the multiple target interfaces are the interfaces involved in the call flow of the target call scenario, and the multiple target interfaces include: Gm interface and Mw interface; the call record set is the XDR record set of the call flow; The master record generation module 1020 is used to generate a call master record set based on the call record set of the first interface; wherein, the first interface includes: the Gm interface and the Mw interface; the call master records in the call master record set are obtained by associating records belonging to the same call in the union of the call record set of the Gm interface and the call record set of the Mw interface; The synthetic record generation module 1030 is configured to: in the call record set of the second interface, filter records belonging to the same call as the call main record in the call main record set, associate the filtered records with the call main record, and generate a call synthetic record corresponding to the call main record; wherein the second interface includes interfaces other than the Gm interface and the Mw interface in the plurality of target interfaces. The record set generation module 1040 is configured to generate a call synthetic record set based on the call synthetic record corresponding to each call main record in the call main record set.
[0096] In some embodiments of the present application, the acquisition module 1010 is specifically configured to: determine a target interface based on a target call scenario; acquire an XDR record set of the target interface; filter XDR records of a call flow in the XDR record set of the target interface, and generate a call record set of the target interface based on the filtered records.
[0097] In some embodiments of the present application, the main record generation module 1020 is specifically configured to: divide records belonging to the same call in the call record set of the Gm interface and the call record set of the Mw interface into the same record subset, to obtain a plurality of record subsets; associate records in the record subset to generate a call main record corresponding to the record subset; generate a call main record set based on the call main record corresponding to each record subset in the plurality of record subsets.
[0098] In some embodiments of the present application, the synthetic record generation module 1030 is specifically configured to: determine a first flow start time and a first flow end time based on the call main record; wherein the first flow start time is a start time of a flow recorded by the call main record, and the first flow end time is an end time of the flow recorded by the call main record; advance the first flow start time by a target time amount to obtain an advanced first flow start time; filter associated records of the call main record in the call record set of the second interface; wherein the associated records are records associated with the call main record to the same user; determine a second flow start time based on the associated records; wherein the second flow start time is a start time of a flow recorded by the associated records; If the second flow start time is not earlier than the first flow start time after the time adjustment and not later than the first flow end time, it is determined that the association record and the call main record belong to the same call.
[0099] In some embodiments of the present application, the apparatus further comprises: a target time quantity updating module, configured to: If the association record and the call main record belong to the same call, it is determined whether the flow recorded by the association record and the flow recorded by the call main record are in a time synchronization state; If not, a time desynchronization quantity between the flow recorded by the association record and the flow recorded by the call main record is determined, the time desynchronization quantity is determined as a desynchronization quantity sample and added to a desynchronization quantity sample set; If the number of desynchronization quantity samples in the desynchronization quantity sample set reaches a number threshold, the target time quantity is updated based on the desynchronization quantity sample set; The desynchronization quantity sample set is reset to an initial state.
[0100] In some embodiments of the present application, the record set generating module 1040 is specifically configured to: determine a call scenario corresponding to the call synthesis record; correct error data in the call synthesis record based on signaling causality rules and signaling transitivity rules corresponding to the call scenario; generate the call synthesis record set based on the corrected call synthesis record.
[0101] The record processing apparatus provided in the embodiments of the present application implements each process of the method embodiments and can achieve the same technical effects. To avoid repetition, details are not described herein.
[0102] In addition, based on the same idea, the embodiments of the present application further provide a record processing device, which comprises a processor and a memory. The memory stores a computer program capable of running on the processor. When the computer program is executed by the processor, each process of the above method embodiments is implemented, and the same technical effects can be achieved. To avoid repetition, details are not described herein.
[0103] The embodiments of the present application further provide a computer program product, which comprises a computer program. When the computer program is executed by a processor, each process of the above method embodiments is implemented, and the same technical effects can be achieved. To avoid repetition, details are not described herein.
[0104] The embodiment of the present application further provides a computer readable storage medium, and the computer readable storage medium stores a computer program. The computer program is executed by a processor to realize each process of the method embodiment and achieve the same technical effects. To avoid repetition, details are not described herein. The computer readable storage medium is, for example, a read-only memory (ROM), a random access memory (RAM), a magnetic disk or an optical disk.
[0105] Those skilled in the art should understand that the embodiments of the present application can be provided as a method, a system or a computer program product. Therefore, the present application can take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects. In addition, the present application can take the form of a computer program product implemented on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, etc.) containing computer-usable program code.
[0106] The present application is described with reference to flowcharts and / or block diagrams of the method, device (system) and computer program product according to the embodiments of the present application. It should be understood that each flow and / or block in the flowcharts and / or block diagrams, and the combination of the flows and / or blocks in the flowcharts and / or block diagrams can be implemented by computer program instructions. These computer program instructions can be provided to a general-purpose computer, a special-purpose computer, an embedded processor or other programmable data processing devices to produce a machine, so that the instructions executed by the computer or other programmable data processing devices produce a device implemented in the flowcharts and / or block diagrams. Figure 1 one or more flows and / or blocks Figure 1 an apparatus that performs the functions specified in the flow(s) or block(s).
[0107] These computer program instructions can also be stored in a computer readable memory that can direct the computer or other programmable data processing devices to work in a specific manner, so that the instructions stored in the computer readable memory produce a manufactured product including instruction apparatus, which realizes the flowcharts and / or block diagrams. Figure 1 one or more flows and / or blocks Figure 1 an apparatus that performs the functions specified in the flow(s) or block(s).
[0108] These computer program instructions can also be loaded into a computer or other programmable data processing device to make a series of operation steps executed on the computer or other programmable data processing device to produce a computer implemented process, so that the instructions executed on the computer or other programmable data processing device provide a process for realizing the flowcharts and / or block diagrams. Figure 1 one or more flows and / or blocks Figure 1steps of a function specified in one or more blocks.
[0109] In one typical arrangement, the computing device includes one or more processors (CPUs), input / output interfaces, network interfaces, and memory.
[0110] The memory can include non-persistent memory and / or volatile memory, such as random access memory (RAM) being used by the computer system to store data and program code. The memory can also include non-volatile memory, such as read only memory (ROM), electrically programmable read only memory (EPROM), electrically erasable programmable read only memory (EEPROM), flash memory, or non-volatile random access memory (NVRAM). The memory can also in some cases be considered to be a computer-readable medium, a machine-readable medium, or a computer program product.
[0111] Computer readable media includes permanent and non-permanent, removable and non-removable media implemented in any method or technology for the storage of information. The information can be computer readable instructions, data structures, program modules or other data. Examples of computer storage media include, but are not limited to, phase change memory (PRAM), static random access memory (SRAM), dynamic random access memory (DRAM), other types of random access memory (RAM), read only memory (ROM), electrically programmable read only memory (EEPROM), flash memory or other memory technology, compact disc read only memory (CD-ROM), digital versatile disc (DVD), or other optical storage, magnetic cassette, magnetic tape, magnetic disk storage or other magnetic storage devices, or any other non-transmission medium that can be used to store information accessible to a computing device. According to the definition in this paper, computer readable media does not include transitory media, such as modulated data signals and carriers.
[0112] It should also be noted that the terms "comprising", "containing", or any other variant thereof are intended to cover a non-exclusive inclusion, such that a process, method, article or apparatus that comprises a list of elements does not only include those elements, but can also include other elements not expressly listed or inherent to such process, method, article or apparatus. Without more limitations, the element defined by the statement "comprising a" does not exclude the presence of additional identical elements in the process, method, article or apparatus that includes the element.
[0113] The above description is only an embodiment of the present application and is not intended to limit the present application. For those skilled in the art, the present application can have various modifications and changes. Any modification, equivalent replacement, improvement, etc. within the spirit and principle of the present application shall be included in the scope of claims of the present application.
Claims
1. A recording and processing method, characterized in that, The method includes: Obtain the call record set for each of the multiple target interfaces; wherein, the multiple target interfaces are the interfaces involved in the call flow of the target call scenario, and the multiple target interfaces include: Gm interface and Mw interface; A call master record set is generated based on the call record set of the first interface; wherein, the first interface includes: the Gm interface and the Mw interface; the call master record in the call master record set is obtained by associating records belonging to the same call in the union of the call record set of the Gm interface and the call record set of the Mw interface; In the call record set of the second interface, records belonging to the same call as the call master record in the call master record set are filtered out, and the filtered records are associated with the call master record to generate a call synthesis record corresponding to the call master record; wherein, the second interface includes: interfaces other than the Gm interface and the Mw interface among the plurality of target interfaces; A call synthesis record set is generated based on the call synthesis record corresponding to each call master record in the call master record set.
2. The method according to claim 1, characterized in that, The step of obtaining the call record set for each of the multiple target interfaces includes: Based on the target call scenario, determine the target interface; Obtain the XDR record set of the target interface; In the XDR record set of the target interface, XDR records of the call flow are filtered, and a call record set of the target interface is generated based on the filtered records.
3. The method according to claim 1, characterized in that, The call record set based on the first interface generates a call master record set, including: Records belonging to the same call in the call record set of the Gm interface and the call record set of the Mw interface are divided into the same record subset, resulting in multiple record subsets; Associate the records in the subset of records to generate the call master record corresponding to the subset of records; A call master record set is generated based on the call master record corresponding to each of the multiple record subsets.
4. The method according to claim 1, characterized in that, In the call record set of the second interface, filtering call records that belong to the same call as the call master record in the call master record set includes: Based on the call master record, the start time of the first process and the end time of the first process are determined; wherein, the start time of the first process is the start time of the process recorded in the call master record, and the end time of the first process is the end time of the process recorded in the call master record. The start time of the first process is advanced by the target time amount to obtain the advanced start time of the first process. In the call record set of the second interface, filter the associated records of the call master record; wherein, the associated records are records that are associated with the call master record to the same user; Based on the associated records, the start time of the second process is determined; wherein, the start time of the second process is the start time of the process recorded in the associated records; If the start time of the second process is not earlier than the start time of the first process after the earlier start time and not later than the end time of the first process, it is determined that the associated record and the call master record belong to the same call.
5. The method according to claim 4, characterized in that, The method further includes: If the associated record and the call master record belong to the same call, determine whether the process recorded in the associated record and the process recorded in the call master record are in a time-synchronized state; If not, determine the time asynchrony between the process recorded in the associated record and the process recorded in the call master record, identify the time asynchrony as an asynchrony sample, and add it to the asynchrony sample set. If the number of asynchronous quantity samples in the asynchronous quantity sample set reaches the quantity threshold, the target time quantity is updated based on the asynchronous quantity sample set; Reset the different time sample sets to their initial state.
6. The method according to claim 1, characterized in that, Based on the call synthesis record corresponding to each call master record in the call master record set, a call synthesis record set is generated, including: Determine the call scenario corresponding to the call synthesis record; Based on the signaling causality rules and signaling transitivity rules corresponding to the call scenario, the erroneous data in the call synthesis record is corrected; The call synthesis record set is generated based on the corrected call synthesis record.
7. A recording and processing apparatus, characterized in that, The device includes: The acquisition module is used to acquire the call record set of each of the multiple target interfaces; wherein, the multiple target interfaces are the interfaces involved in the call flow of the target call scenario, and the multiple target interfaces include: Gm interface and Mw interface; A master record generation module is used to generate a call master record set based on the call record set of a first interface; wherein, the first interface includes: the Gm interface and the Mw interface; the call master records in the call master record set are obtained by associating records belonging to the same call in the union of the call record set of the Gm interface and the call record set of the Mw interface; The composite record generation module is used to filter records belonging to the same call as the call master record in the call master record set of the second interface, associate the filtered records with the call master record, and generate a composite call record corresponding to the call master record; wherein, the second interface includes: interfaces other than the Gm interface and the Mw interface among the plurality of target interfaces; The record set generation module is used to generate a call synthesis record set based on the call synthesis record corresponding to each call master record in the call master record set.
8. A recording and processing device, characterized in that, include: A memory on which computer programs are stored; A processor for executing the computer program to implement the steps of the method as described in any one of claims 1 to 6.
9. A computer-readable storage medium, characterized in that, A computer program is stored on the computer-readable storage medium, which, when executed by a processor, implements the steps of the method as described in any one of claims 1 to 6.
10. A computer program product, characterized in that, Includes a computer program that, when executed by a processor, implements the steps of the method according to any one of claims 1 to 6.