A user-perceived fault location method based on CDR and DPI data association

Abstract

The present invention relates to the field of communication technology, and discloses a user-perceived fault location method based on the association of CDR and DPI data, comprising: obtaining CDR and DPI data, and performing call record identification, call record filtering and association synthesis on the CDR and DPI data to obtain a synthetic call record of CDR+DPI; performing abnormal call record identification, root cause judgment and delimitation experience database according to the synthetic call record of CDR+DPI, and outputting fault solution suggestions and troubleshooting ideas. The user-perceived fault location method based on the association of CDR and DPI data provided by the present invention utilizes the CDR and DPI data of the network, and automatically outputs the user fault delimitation\location results after automatic association synthesis, root cause location, and fault analysis, so as to realize fast and accurate user-perceived fault location, achieve the effect of efficient, fast and low-cost user-perceived fault location, reduce network operation and maintenance, analysis costs, and improve user perception.

Description

Technical Field

[0001] The present invention relates to the field of communication technology, and in particular to a user-perceived fault locating method based on CDR and DPI data association. Background Art

[0002] When traditional network operation and maintenance personnel deal with user perception analysis, there is a problem of isolation between wireless and core. Wireless operation and maintenance personnel can obtain the user's occupied cell and wireless event status through DPI data, and roughly judge the user's perception status based on the cell performance, but cannot obtain the user's specific service perception status; core operation and maintenance personnel can use XDR data to judge the user's event details on the signaling plane and the perceived performance on the user plane, but cannot obtain pure wireless information. The user-level wireless / core full-domain and full-process association has not been achieved, resulting in low analysis efficiency. Summary of the invention

[0003] The present invention provides a user-perceived fault locating method based on the association of CDR and DPI data. The method utilizes the CDR and DPI data of the network, automatically correlates and synthesizes, locates the root cause, and analyzes the fault before automatically outputting the user fault delimitation\location result, thereby realizing fast and accurate user-perceived fault locating, achieving the effect of efficient, fast, and low-cost user-perceived fault locating, reducing network operation and maintenance and analysis costs, and improving user perception.

[0004] The present invention provides a user-perceived fault location method based on CDR and DPI data association, comprising:

[0005] Acquire CDR and DPI data, and perform call record identification, call record filtering and correlation synthesis on the CDR and DPI data to obtain a synthetic call record of CDR+DPI;

[0006] After abnormal call records are identified, root causes are determined and an experience database is defined based on the synthetic call records of CDR+DPI, fault resolution suggestions and troubleshooting ideas are output.

[0007] Furthermore, the step of obtaining CDR and DPI data, and performing call record identification, call record filtering and correlation synthesis on the CDR and DPI data to obtain a synthetic call record of CDR+DPI includes:

[0008] The CDR call record is identified according to the preset first field definition, and the DPI call record is identified according to the preset second field definition to obtain the CDR call record related to the service;

[0009] According to the preset function description and business process definition, the interfaces and process contents involved are filtered according to the business process to obtain single-interface call records involved in different scenarios;

[0010] Based on the key cause call record established by RRC, a synthetic call record of CDR+DPI is constructed.

[0011] Furthermore, the step of filtering the interfaces and process contents involved in the business process according to the preset function description and the definition of the business process to obtain single-interface call records involved in different scenarios includes:

[0012] Determine the process of users who need to be associated;

[0013] According to the process, multiple interfaces involved in the process are determined, and single-interface XDR call records corresponding to the multiple interfaces are filtered and screened to obtain single-interface call records involved in different scenarios.

[0014] Furthermore, the step of constructing a synthetic call record of CDR+DPI based on the key cause call record established by RRC includes:

[0015] Obtain the key fields of the CDR bill and the key fields of each interface bill; wherein the key fields of the CDR bill include user number, CDR type, RRC establishment reason, RRC failure reason, and serving cell receiving interference power, and the key fields of each interface bill include user number, process type, process status, start time, end time, failure reason, and network element IP;

[0016] The key reason call record is established based on RRC, and is associated and synthesized with the business process to obtain the synthetic call record of CDR+DPI.

[0017] Furthermore, after identifying abnormal call records, determining root causes and defining an experience base based on the CDR+DPI composite call record, the step of outputting fault resolution suggestions and troubleshooting ideas includes:

[0018] Based on the synthetic call bill of the CDR+DPI, an abnormal call bill is defined by identification failure and being inferior to an indicator threshold; wherein the synthetic call bill of the CDR+DPI includes a signaling synthetic call bill and a perception synthetic call bill, the signaling synthetic call bill defines an abnormal call bill by identification failure, and the perception synthetic call bill defines an abnormal call bill by being inferior to an indicator threshold;

[0019] Performing root cause determination on the signaling synthesized call record and the perception synthesized call record;

[0020] Taking the process types of different interfaces and the failure reasons of different protocols as input conditions, according to the preset specifications and combined with network analysis examples, it outputs the problem demarcation and solution suggestion experience library with process and failure code as the dimensions;

[0021] The root cause is located using the synthetic call record of CDR+DPI and the logic judgment method, and the fault delimitation or positioning experience library is automatically matched to output fault solution suggestions and troubleshooting ideas.

[0022] Furthermore, the step of determining the root cause of the signaling synthesized call record and the perception synthesized call record includes:

[0023] Output the failure root cause process and failure reason code for the signaling abnormal call sheet according to the preset rules combined with the process status and failure reason code of the synthetic call sheet; wherein the preset rules include that different business processes involve different interface processes, there are logical relationships such as before and after, including between each process, and the preset function description and definition of the business process;

[0024] For the perception-type abnormal call records, the degradation causes and suspected problem nodes are output according to preset standards and degradation indicator definitions.

[0025] Furthermore, the step of obtaining CDR and DPI data, and performing call record identification, call record filtering and correlation synthesis on the CDR and DPI data to obtain a synthetic call record of CDR+DPI includes:

[0026] The CDR call record is identified according to the preset first field definition, and the DPI call record is identified according to the preset second field definition to obtain the CDR call record related to the service;

[0027] The user, start time and end time of the CDR call record related to the business are used as conditions to associate and obtain the full DPI call record of users within the time range to obtain a composite call record of CDR+DPI.

[0028] The present invention also provides a user-perceived fault location device based on CDR and DPI data association, comprising:

[0029] The correlation synthesis module is used to obtain CDR and DPI data, and perform call record identification, call record filtering and correlation synthesis on the CDR and DPI data to obtain a synthetic call record of CDR+DPI;

[0030] The fault analysis module is used to identify abnormal call records, determine the root causes and define the experience base based on the synthetic call records of the CDR+DPI, and then output fault solution suggestions and troubleshooting ideas.

[0031] The present invention also provides a computer device, comprising a memory and a processor, wherein the memory stores a computer program, and the processor implements the steps of the above method when executing the computer program.

[0032] The present invention also provides a computer-readable storage medium on which a computer program is stored, and the computer program implements the steps of the above method when executed by a processor.

[0033] The beneficial effects of the present invention are:

[0034] Based on the association of CDR and DPI data, user-perceived fault location is performed. Based on the CDR data type and combined with the business process, a cross-domain and cross-interface associated synthetic call record is constructed to effectively improve the efficiency and accuracy of user-perceived analysis. The delimited experience library is based on the business process, in-depth analysis of the reasons for failure of each interface, and integration of actual cases. It effectively improves the accuracy of problem analysis and reduces the skill requirements of optimization personnel. BRIEF DESCRIPTION OF THE DRAWINGS

[0035] Figure 1 The present invention is a flowchart of a user-perceived fault location method based on CDR and DPI data association.

[0036] Figure 2 This is a schematic diagram of call record identification in the present invention.

[0037] Figure 3 This is a schematic diagram of call record filtering in the present invention.

[0038] Figure 4 This is a schematic diagram of an example of associated synthesis speech in the present invention.

[0039] Figure 5 This is a schematic diagram of abnormal call record identification in the present invention.

[0040] Figure 6 It is a schematic diagram of root cause determination in the present invention.

[0041] Figure 7 This is a schematic diagram of an example of a delimited experience library in the present invention.

[0042] Figure 8 Schematic diagram of input and output of the fault location device in the present invention.

[0043] Fig. 9 The figure is a schematic diagram of the internal structure of a computer device according to an embodiment of the present invention.

[0044] The realization of the purpose, functional features and advantages of the present invention will be further explained in conjunction with embodiments and with reference to the accompanying drawings. DETAILED DESCRIPTION

[0045] It should be understood that the specific embodiments described herein are only used to explain the present invention, and are not used to limit the present invention.

[0046] Currently, operators perform optical splitting and DPI (Deep Packet Inspection) processing on core network data, and produce XDR (X Detailed Record) according to enterprise standards. XDR refers to a detailed record of signaling and services generated for network fault analysis systems, signaling monitoring / analysis platforms, and signaling applications after processing based on the full amount of data. A detailed record of the signaling process generated based on the collected control plane signaling. A single call record can only provide key information about user request / response signaling on a single interface.

[0047] Wireless network data mainly includes MR (Measurement Report), PM (Performance Management) data and CDR (Call Detail Records). MR data mainly comes from the physical layer and RLC layer of UE and eNodeB and the measurement reports calculated in the process of wireless resource management; PM data is collected regularly according to the counter defined by the equipment manufacturer, and the cell performance data is generated through unified calculation rules; CDR data is mainly used to record the key historical information of a call, including the terminal feature information of the call, call establishment feature information, QoS related information, call process behavior information, call release related information, etc.

[0048] SEQ (Service & Experience Quality Analyst) is Huawei's customer experience management enabling platform. It relies on XDR data collected by DPI probes to evaluate and analyze network performance and user perception to achieve fault demarcation and location. Due to its high professionalism, it is suitable for professional analysts to analyze and handle difficult network faults and complaints. However, the system cannot automatically output the perception fault location results and troubleshooting ideas of a single user.

[0049] The user perception deep detection method based on MR and XDR forms the service quality KQI index from the two dimensions of control plane and service plane, establishes the scoring model of user perception MOS index, and calculates the user perception MOS value based on the scoring model and service quality KQI index. The user perception MOS value is used to replace the wireless performance KPI index in MR data to diagnose the user's network perception. This method can evaluate the user's excellent network perception, but cannot effectively locate the user perception fault.

[0050] The existing user-perceived fault location methods still have the following deficiencies in the data acquisition stage and fault analysis and location stage:

[0051] Data acquisition stage: When operators deal with user perception issues, there is a problem of isolated wireless and core network data and no effective integration. As a result, the analysis of a single user needs to be transferred back and forth between the wireless and core departments, which increases processing time, affects analysis efficiency, and reduces the accuracy of fault location.

[0052] Fault analysis and location phase: In the root cause location phase of network fault analysis, current operators mainly rely on single-interface or user-level comprehensive XDR data and wireless performance data, and analysts rely on experience to analyze through clustering, trends, process status, and failure codes. The entire analysis process is heavily dependent on the experience and level of analysts, which can easily affect customer perception.

[0053] In order to solve the problems of existing user-perceived fault location methods in data acquisition and fault analysis and location, the present invention proposes a user-perceived fault location method based on the association of CDR and DPI data. It uses the network's CDR and DPI data to automatically output user fault delimitation and location results after automatic association synthesis, root cause location, and fault analysis, so as to achieve fast and accurate user-perceived fault location, achieve efficient, fast, and low-cost user-perceived fault location, reduce network operation and maintenance, and analysis costs, and improve user perception. The results include fault resolution suggestions, troubleshooting ideas, and other information, which can be configured according to needs.

[0054] like Figure 1 As shown in FIG. 1 , a user-aware fault location method based on the association of CDR and DPI data is used, and Hive database is used to perform processing using Spark and MapReduce, specifically including:

[0055] S1. Obtain CDR and DPI data, and perform call record identification, call record filtering and correlation synthesis on the CDR and DPI data to obtain a synthetic call record of CDR+DPI, wherein CDR data is key historical information of recorded calls, and DPI data is detailed records of signaling and services.

[0056] Step S1 specifically includes:

[0057] S1-1. CDR call records are identified according to the preset first field definition, and DPI call records are identified according to the preset second field definition to obtain CDR call records related to the service.

[0058] As described above, the preset first field definition refers to the cdr.type and ac.rrcestablishmentcause field definitions in the "LTE Network CDR and MR Field Requirements" enterprise standard, and the preset second field definition refers to the interface and Procedure_Type field definitions in the "Mobile Internet Data Standards and Interfaces" enterprise standard.

[0059] For example, refer to Figure 2 , for the CDR data source, the types A and B of the cdr.type field and the values ​​A, B, C, D, E, and F of the ac.rrcestablishmentcause field are used to identify the data, and the data with cdr.type of A and ac.rrcestablishmentcause of B, D, and F are identified to obtain the key call records AB, AD, and AF of different RRC establishment reasons.

[0060] S1-2. According to the preset function description and the definition of the business process, the interfaces and process contents involved are filtered according to the business process to obtain single-interface call records involved in different scenarios.

[0061] Step S1-2 specifically includes:

[0062] S1-2-1. Determine the process of users who need to be associated;

[0063] S1-2-2. Determine multiple interfaces involved in the process according to the process, and filter and screen the single-interface XDR call records corresponding to the multiple interfaces to obtain single-interface call records involved in different scenarios.

[0064] As described above, the definition of the preset functional description and service flow refers to the definition of functional description and service flow in 3GPP 23401 specification.

[0065] 3GPP (3rd Generation Partnership Project)

[0066] 23401 (Technical Specification Group Services and System Aspects; General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access)

[0067] For example, refer to Figure 3At present, it is determined that the attachment process of userA needs to be associated. After checking the 23401 specification, it is determined that the business process involves the call sheet of process No. 1 of interface A, the call sheet of process No. 3 of interface B, and the call sheet of process No. 5 of interface D. Therefore, it is necessary to filter and select the single-interface XDR call sheets corresponding to interfaces A, B, and D. See the call sheets corresponding to the solid lines in the figure below for filtering.

[0068] S1-3. Based on the key cause call record established by RRC, a synthetic call record of CDR+DPI is constructed.

[0069] Step S1-3 specifically includes:

[0070] S1-3-1. Obtain the key fields of the CDR bill and the key fields of each interface bill; wherein the key fields of the CDR bill include the user number, CDR type, RRC establishment reason, RRC failure reason, and serving cell receiving interference power; the key fields of each interface bill include the user number, process type, process status, start time, end time, failure reason, and network element IP;

[0071] S1-3-2. Based on the key reason call record established by RRC, it is associated and synthesized with the business process to obtain the synthetic call record of CDR+DPI.

[0072] As described above, the CDRs related to the service are obtained through the call record identification of S1-1, and the single-interface call records involved in different scenarios are obtained through the call record filtering of S1-2.

[0073] To obtain the key fields of the CDR, refer to the enterprise standard "LTE network CDR and MR field requirements" to obtain the key fields of the CDR, including user number, CDR type, RRC establishment reason, RRC failure reason, service cell receiving interference power, etc.

[0074] To obtain the key fields of each interface call record, refer to the "Mobile Internet Data Standards and Interfaces" enterprise standard to obtain the key fields of each interface call record, including user number, process type, process status, start time, end time, failure reason, network element IP, etc.

[0075] Based on the key cause call record established by RRC, it is associated and synthesized with the business process obtained by S1-2 to build a synthetic call record of CDR+DPI. The structure of the synthetic call record is as follows: Figure 4 shown.

[0076] In one embodiment, step S1 may also be:

[0077] S1-11. Identify the CDR according to the preset first field definition, and identify the DPI according to the preset second field definition to obtain a CDR related to the service;

[0078] S1-12. Use the user, start time and end time of the CDR bill related to the service as conditions to associate and obtain all DPI bills of users within the time range to obtain a composite bill of CDR+DPI.

[0079] As mentioned above, steps S1-2 and S1-3 can be integrated, and the call record identification of S1-1 can be used to obtain CDR call records related to the business. Based on the user, start time, and end time in the CDR call record, the full DPI call records of users within the time range are associated to achieve call record association synthesis. This implementation method can reduce the difficulty of program implementation.

[0080] S2. After abnormal call records are identified, root causes are determined, and an experience database is defined based on the CDR+DPI composite call record, fault resolution suggestions and troubleshooting ideas are output.

[0081] Step S2 specifically includes:

[0082] S2-1. Based on the composite call bill of CDR+DPI, abnormal call bills are defined by identification failure and being inferior to an indicator threshold; wherein the composite call bill of CDR+DPI includes a signaling composite call bill and a perception composite call bill, the signaling composite call bill defines an abnormal call bill by identification failure, and the perception composite call bill defines an abnormal call bill by being inferior to an indicator threshold.

[0083] As mentioned above, the synthetic call bill based on CDR+DPI is divided into signaling synthetic call bill and perception synthetic call bill. For signaling synthetic call bill, abnormal call bill is defined by identifying failed steps, and for perception synthetic call bill, abnormal call bill is defined by being inferior to the indicator threshold.

[0084] For example, refer to Figure 5 , the RRC establishment reason is "MO.data" (calling data) perception signaling call record. Judgment is made through perception indicators such as DNS resolution delay (ms), uplink rate (MB / S), downlink rate (MB / S), uplink RTT average delay (MS), and downlink RTT average delay (MS).

[0085] S2-2. Root cause determination is performed on the signaling synthesized call record and the perception synthesized call record.

[0086] Step S2-2 specifically includes:

[0087] S2-2-1. Output the failure root cause process and failure reason code for the signaling abnormal call sheet according to the preset rules combined with the process status and failure reason code of the synthetic call sheet; wherein the preset rules include that different business processes involve different interface processes, there are logical relationships such as before and after, including each process, and the preset function description and definition of the business process;

[0088] S2-2-2. For the perception-type abnormal call records, output the degradation causes and suspected problem nodes according to the preset standards and the degradation indicator definition.

[0089] As mentioned above, the preset function description and business process definition are the function description and business process definition in the 3GPP and 23401 specifications. The preset standard refers to the "Internet access information parsing bill format requirements" in the "Mobile Internet Data Standards and Interfaces" enterprise standard.

[0090] For abnormal signaling call records, different business processes involve different interface processes, and there are logical relationships such as before, after, and inclusion between each process. The function description and business process definition in the 3GPP and 23401 specifications are combined with the process status and failure reason code of the synthetic call record to output the failure root cause process and failure reason code. For abnormal perception call records, refer to the "Internet access information parsing call record format requirements" in the "Mobile Internet Data Standards and Interfaces" enterprise standard, and combine the degradation indicator definition to output the degradation cause and suspected problem nodes.

[0091] For example, in the analysis of perception-type abnormal call records, the cause of the abnormality is that the DNS resolution delay (ms) is greater than the threshold. According to the definition of DNS resolution delay, from initiating DNS resolution to receiving the DNS resolution result, two nodes, NE 1 and NE 2, are passed through. The problem boundary points are the CN / SP side and the wireless side, such as Figure 6 shown.

[0092] S2-3. Taking the process types of different interfaces and the failure reasons of different protocols as input conditions, according to the preset specifications and combined with network analysis examples, output the problem demarcation and solution suggestion experience library with process and failure code as dimensions.

[0093] As mentioned above, the preset specifications refer to 3GPP,23401 specifications, 3GPP,36413 specifications.

[0094] 36431 (Technical Specification Group Radio Access Network; Evolved Universal Terrestrial Radio Access Network (E-UTRAN); S1 Application Protocol (S1AP)).

[0095] Taking the process types of different interfaces and the failure reasons of different protocols as input conditions, referring to the 3GPP 23401 specification and 3GPP 36413 specification, combined with network analysis examples, the system outputs the problem demarcation and solution suggestion experience library with process and failure code as the dimensions. Among them, the experience library has the function of updating, and the experience library is improved by continuously collecting cases. Figure 7 shown.

[0096] S2-4. Utilize the synthetic call record of CDR+DPI and the logic judgment method to locate the root cause, automatically match the fault delimitation or location experience library, and output fault solution suggestions and troubleshooting ideas.

[0097] As mentioned above, the root cause is located by using the synthetic call record and the logical judgment method. After the root cause is located, the fault delimitation and location experience database is automatically matched to output fault solution suggestions and troubleshooting ideas, so as to achieve fast and batch user-perceived fault location, effectively improving the problem solving efficiency and reducing the skill requirements of optimization personnel.

[0098] Based on MR and XDR user perception deep detection, service quality KQI indicators are formed from the two dimensions of control plane and service plane, and a scoring model for user perception MOS indicators is established. The user perception MOS value is calculated based on the scoring model and service quality KQI indicators. The user perception MOS value replaces the wireless performance KPI indicators in MR data to diagnose the user's network perception.

[0099] Based on the data of domain B (business domain), domain O (operation domain), and domain M (management domain), multi-domain fusion analysis is carried out to realize user profiling. The machine learning classification algorithm is used to iterate repeatedly to obtain a reliable and stable decision-making model, thereby realizing the intelligent delimitation and positioning of user perception.

[0100] like Figure 8 As shown, the present invention also provides a user-perceived fault location device based on the association of CDR and DPI data. The device inputs CDR and DPI data, and through the processing of the device, it can output the root cause of the user fault, solution suggestions and troubleshooting ideas. The device uses the CDR and DPI data of the network, and automatically outputs the user fault delimitation\location results after processing and matching through the built-in association synthesis module and fault analysis module of the device, so as to realize fast and accurate user-perceived fault location, and achieve the effect of efficient, fast and low-cost user-perceived fault location, reduce network operation and maintenance, analysis costs, and improve user perception. The results include information such as fault solution suggestions and troubleshooting ideas, which can be configured according to needs. The device uses Hive database to use Spark and MapReduce for processing.

[0101] The device includes:

[0102] The correlation synthesis module is used to obtain CDR and DPI data, and perform call record identification, call record filtering and correlation synthesis on the CDR and DPI data to obtain a synthetic call record of CDR+DPI;

[0103] The fault analysis module is used to identify abnormal call records, determine the root causes and define the experience base based on the synthetic call records of the CDR+DPI, and then output fault solution suggestions and troubleshooting ideas.

[0104] In one embodiment, the association synthesis module includes:

[0105] A call record identification unit, used to identify the CDR call record according to a preset first field definition, and to identify the DPI call record according to a preset second field definition, so as to obtain a CDR call record related to the service;

[0106] The call record filtering unit is used to filter the interfaces and process contents involved in the business process according to the preset function description and the definition of the business process, and obtain the single-interface call records involved in different scenarios;

[0107] The associated synthesis unit is used to construct a synthetic call record of CDR+DPI based on the key cause call record established by RRC.

[0108] In one embodiment, the call record filtering unit includes:

[0109] Determine the subunit, which is used to determine the process of the user that needs to be associated;

[0110] The filtering subunit is used to determine multiple interfaces involved in the process according to the process, and filter and screen the single-interface XDR call records corresponding to the multiple interfaces to obtain single-interface call records involved in different scenarios.

[0111] In one embodiment, the association synthesis unit includes:

[0112] The acquisition subunit is used to acquire the key fields of the CDR bill and the key fields of each interface bill; wherein the key fields of the CDR bill include the user number, CDR type, RRC establishment reason, RRC failure reason, and serving cell receiving interference power, and the key fields of each interface bill include the user number, process type, process status, start time, end time, failure reason, and network element IP;

[0113] The synthesis subunit is used to establish a key reason call record based on RRC, and to associate and synthesize it with the business process to obtain the synthesized call record of CDR+DPI.

[0114] In one embodiment, the fault analysis module includes:

[0115] An abnormal call record identification unit is used to define an abnormal call record based on the CDR+DPI synthetic call record by identification failure and being inferior to an indicator threshold; wherein the CDR+DPI synthetic call record includes a signaling synthetic call record and a perception synthetic call record, the signaling synthetic call record defines an abnormal call record by identification failure, and the perception synthetic call record defines an abnormal call record by being inferior to an indicator threshold;

[0116] A root cause determination unit, configured to determine the root cause of the signaling synthesized call record and the perception synthesized call record;

[0117] The delimited experience library unit is used to take the process types of different interfaces and the failure reasons of different protocols as input conditions, and output the problem delimitation and solution suggestion experience library based on the process and failure code as the dimensions according to the preset specifications and network analysis examples;

[0118] The output unit is used to locate the root cause by using the synthetic call record of CDR+DPI and the logic judgment method, and automatically match the fault delimitation or positioning experience library to output fault solution suggestions and troubleshooting ideas.

[0119] In one embodiment, the root cause determination unit includes:

[0120] The failure cause output subunit is used to output the failure root cause process and the failure cause code for the signaling abnormal call sheet according to the preset rules combined with the process status and failure cause code of the synthetic call sheet; wherein the preset rules include that different business processes involve different interface processes, there are logical relationships such as before and after, including each process, and the preset function description and definition of the business process;

[0121] The degradation cause output unit is used to output the degradation cause and suspected problem nodes for the perception-type abnormal call record according to preset standards and degradation indicator definitions.

[0122] In one embodiment, the association synthesis module includes:

[0123] An identification unit, used to identify the CDR bill according to a preset first field definition, and to identify the DPI bill according to a preset second field definition, to obtain a CDR bill related to the service;

[0124] The association unit is used to associate the full DPI call records of users within the time range with the user, start time and end time of the CDR call record related to the service as conditions to obtain a composite call record of CDR+DPI.

[0125] The above modules, units and sub-units are used to execute the steps in the above user-perceived fault location method based on CDR and DPI data association. The specific implementation method is described in the above method embodiment and will not be repeated here.

[0126] like Fig. 9 As shown, the present invention also provides a computer device, which can be a server, and its internal structure can be as shown in Fig. 9 As shown. The computer device includes a processor, a memory, a network interface and a database connected through a system bus. Among them, the processor designed by the computer is used to provide computing and control capabilities. The memory of the computer device includes a non-volatile storage medium and an internal memory. The non-volatile storage medium stores an operating system, a computer program and a database. The memory provides an environment for the operation of the operating system and the computer program in the non-volatile storage medium. The database of the computer device is used to store all data required for the process of the user-perceived fault location method based on the association of CDR and DPI data. The network interface of the computer device is used to communicate with an external terminal through a network connection. When the computer program is executed by the processor, the user-perceived fault location method based on the association of CDR and DPI data is implemented.

[0127] Those skilled in the art will understand that Fig. 9 The structure shown in is merely a block diagram of a portion of the structure related to the present application solution and does not constitute a limitation on the computer device to which the present application solution is applied.

[0128] An embodiment of the present application further provides a computer-readable storage medium having a computer program stored thereon. When the computer program is executed by a processor, any one of the above-mentioned user-perceived fault location methods based on the association of CDR and DPI data is implemented.

[0129] Those of ordinary skill in the art can understand that all or part of the processes in the above-mentioned embodiment methods can be completed by instructing related hardware through a computer program, and the computer program can be stored in a non-volatile computer-readable storage medium. When the computer program is executed, it can include the processes of the embodiments of the above-mentioned methods. Among them, any reference to memory, storage, database or other media provided in this application and used in the embodiments may include non-volatile and / or volatile memory. Non-volatile memory may include read-only memory (ROM), programmable ROM (PROM), electrically programmable ROM (EPROM), electrically erasable programmable ROM (EEPROM) or flash memory. Volatile memory may include random access memory (RAM) or external cache memory. By way of illustration and not limitation, RAM is available in a variety of forms, such as static RAM (SRAM), dynamic RAM (DRAM), synchronous DRAM (SDRAM), double data rate SDRAM (SSRSDRAM), enhanced SDRAM (ESDRAM), synchronous link (Synchlink) DRAM (SLDRAM), memory bus (Rambus) direct RAM (RDRAM), direct memory bus dynamic RAM (DRDRAM), and memory bus dynamic RAM (RDRAM), etc.

[0130] It should be noted that, in this article, the terms "include", "comprises" or any other variations thereof are intended to cover non-exclusive inclusion, so that a process, device, article or method including a series of elements includes not only those elements, but also includes other elements not explicitly listed, or also includes elements inherent to such process, device, article or method. In the absence of further restrictions, an element defined by the sentence "includes a ..." does not exclude the presence of other identical elements in the process, device, article or method including the element.

[0131] The above description is only a preferred embodiment of the present invention, and does not limit the patent scope of the present invention. Any equivalent structure or equivalent process transformation made by using the contents of the present invention specification and drawings, or directly or indirectly applied in other related technical fields, are also included in the patent protection scope of the present invention.

Claims

1. A user-perceived fault location method based on CDR and DPI data association, characterized in that: include: Acquire CDR and DPI data, and perform call record identification, call record filtering and correlation synthesis on the CDR and DPI data to obtain a synthetic call record of CDR+DPI; After abnormal call records are identified, root causes are determined, and an experience database is defined based on the synthetic call records of CDR+DPI, fault resolution suggestions and troubleshooting ideas are output; The step of obtaining CDR and DPI data, and performing call record identification, call record filtering and correlation synthesis on the CDR and DPI data to obtain a synthetic call record of CDR+DPI includes: The CDR call record is identified according to the preset first field definition, and the DPI call record is identified according to the preset second field definition to obtain the CDR call record related to the service; According to the preset function description and business process definition, the interfaces and process contents involved are filtered according to the business process to obtain single-interface call records involved in different scenarios; Based on the key cause call record established by RRC, a synthetic call record of CDR+DPI is constructed; The step of filtering the interfaces and process contents involved according to the business process according to the preset function description and the definition of the business process to obtain single-interface call records involved in different scenarios includes: Determine the process of users who need to be associated; Determine multiple interfaces involved in the process according to the process, and filter and select single-interface XDR call records corresponding to the multiple interfaces to obtain single-interface call records involved in different scenarios; The step of constructing a CDR+DPI composite call record based on the key cause call record established by RRC includes: Obtain the key fields of the CDR bill and the key fields of each interface bill; wherein the key fields of the CDR bill include user number, CDR type, RRC establishment reason, RRC failure reason, and serving cell receiving interference power, and the key fields of each interface bill include user number, process type, process status, start time, end time, failure reason, and network element IP; Based on the key reason call record established by RRC, the call record is associated and synthesized with the business process to obtain the synthetic call record of CDR+DPI; After abnormal call records are identified, root causes are determined, and an experience database is defined based on the CDR+DPI composite call record, the steps of outputting fault resolution suggestions and troubleshooting ideas include: Based on the synthetic call bill of the CDR+DPI, an abnormal call bill is defined by identification failure and being inferior to an indicator threshold; wherein the synthetic call bill of the CDR+DPI includes a signaling synthetic call bill and a perception synthetic call bill, the signaling synthetic call bill defines an abnormal call bill by identification failure, and the perception synthetic call bill defines an abnormal call bill by being inferior to an indicator threshold; Performing root cause determination on the signaling synthesized call record and the perception synthesized call record; Taking the process types of different interfaces and the failure reasons of different protocols as input conditions, according to the preset specifications and combined with network analysis examples, it outputs the problem demarcation and solution suggestion experience library with process and failure code as the dimensions; The root cause is located using the synthetic call record of CDR+DPI and the logic judgment method, and the fault delimitation or positioning experience library is automatically matched to output fault solution suggestions and troubleshooting ideas.

2. The user-perceived fault location method based on CDR and DPI data association according to claim 1 is characterized in that: The step of determining the root cause of the signaling synthesized call record and the perception synthesized call record comprises: For signaling abnormal call records, the system outputs the failure root cause process and failure cause code according to preset rules combined with the process status and failure cause code of the perceived synthetic call record; among which, the preset rules include that different business processes involve different interface processes, there are logical relationships between each process, preset functional descriptions and business process definitions; For perception-type abnormal call records, the degradation causes and suspected problem nodes are output based on the preset standards and degradation indicator definitions.

3. The user-perceived fault location method based on CDR and DPI data association according to claim 1 is characterized in that: The step of obtaining CDR and DPI data, and performing call record identification, call record filtering and correlation synthesis on the CDR and DPI data to obtain a synthetic call record of CDR+DPI includes: The CDR call record is identified according to the preset first field definition, and the DPI call record is identified according to the preset second field definition to obtain the CDR call record related to the service; The user, start time and end time of the CDR call record related to the business are used as conditions to associate and obtain the full DPI call record of users within the time range to obtain a composite call record of CDR+DPI.

4. A user-perceived fault location device based on CDR and DPI data association, characterized in that: For implementing the method according to any one of claims 1 to 3, It includes: an association synthesis module, which is used to obtain CDR and DPI data, and perform call record identification, call record filtering and association synthesis on the CDR and DPI data to obtain a synthetic call record of CDR+DPI; The fault analysis module is used to identify abnormal call records, determine the root causes and define the experience base based on the synthetic call records of the CDR+DPI, and then output fault solution suggestions and troubleshooting ideas.

5. A computer device comprising a memory and a processor, wherein the memory stores a computer program, wherein: When the processor executes the computer program, the steps of the method according to any one of claims 1 to 3 are implemented.

6. A computer-readable storage medium having a computer program stored thereon, characterized in that: When the computer program is executed by a processor, the steps of the method according to any one of claims 1 to 3 are implemented.

Images