A call history record data processing method based on online analytical processing and related equipment

By performing online analysis of call history records in mobile communication networks, obtaining extended detailed records, and establishing a data cube, the challenges of fault location and user complaint handling in mobile communication network operation and maintenance have been solved, achieving rapid and accurate location and efficient operation and maintenance.

CN123123970APending Publication Date: 2026-11-17CHINA TELECOM CORP LTD
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202611495681.2
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Filing Date
2026-09-23
Publication Date
2026-11-17

AI Technical Summary

Technical Problem

In the operation and maintenance of mobile communication networks, existing technologies are insufficient to accurately locate fault points, especially in the case of routine operation and maintenance faults and user complaints. The lack of flexible query and statistical methods makes fault location and handling of user complaints difficult.

Method used

The method of processing call history data based on online analytical processing is adopted. By acquiring call history records, data drilling and data cube building are performed. Combined with OLAP technology, multi-dimensional analysis is carried out to obtain extended detailed records and display them in a visual manner to assist in fault location and user complaint handling.

Benefits of technology

It improves the operation and maintenance efficiency of mobile communication networks, enables quick and accurate location of faults and handling of user complaints, and enhances the accuracy of network KPI analysis and fault location.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN123123970A_ABST
    Figure CN123123970A_ABST
Patent Text Reader

Abstract

The application discloses a kind of based on online analytical processing's call history record data processing method and related equipment, based on online analytical processing's call history record data processing method includes obtaining call history record, carries out the data drilling of call history record based on online analytical processing, obtains extended detailed record, according to extended detailed record, establishes data cube and the like steps.The application obtains extended detailed record by carrying out the data drilling of call history record based on online analytical processing, and establishes data cube according to extended detailed record, the processing result of multiple dimensions multilayer to call history record is included in data cube, can be network KPI index degradation analysis, fault location analysis and user complaint analysis, auxiliary user complaint processing and the like network operation provide data support, to improve the operation efficiency of mobile communication network core network.The application is applied to communication network technical field.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] This invention relates to the field of communication network technology, and in particular to a method and related equipment for processing call history data based on online analysis processing. Background Technology

[0002] During the operation of mobile communication networks, routine maintenance failures or customer complaints are prone to occur. It is necessary to accurately locate the fault point in the mobile communication network based on routine maintenance failures or customer complaints in order to carry out fault investigation and repair work, so as to ensure that the mobile communication network can continue to provide mobile communication services.

[0003] However, in routine maintenance and troubleshooting, as well as handling user complaints, analysis and localization are challenging and present numerous difficulties, including: 1. The handling of mobile network user complaints faces the problem of difficulty in retrospection: the network management system's performance statistics do not support detailed user records and user-granular statistics, and cannot support user-level complaint handling. 2. The means of handling mobile network user complaints and fault location are lacking and the location methods are difficult: there is a lack of professional special failure analysis methods, the personnel professional skills requirements are high, there is a lack of flexible on-demand combination query and statistical methods, and the analysis is difficult; 3. Difficulty in locating mobile network faults: After a fault occurs, it is difficult to accurately obtain the cause of the failure and the location of the failure. The signaling monitoring system has the advantage of cross-domain boundary delineation, but it is difficult to locate the failure within the equipment. Summary of the Invention

[0004] To address at least one of the aforementioned technical problems, the present invention aims to provide a method and related equipment for processing call history data based on online analytical processing.

[0005] On one hand, embodiments of the present invention include a method for processing call history data based on online analytical processing (OLAP), the method comprising: Retrieve call history; Data drill-down based on online analytics is performed on the call history to obtain extended detailed records; Based on the extended detailed records, a data cube is constructed.

[0006] Furthermore, the acquisition of call history includes: Detect target network elements in the core network of the mobile communication network; When a service failure is detected in the target network element, the call history generated by the target network element is retrieved.

[0007] Furthermore, the data drill-down based on online analytics to obtain extended detailed records from the call history includes: Determine multiple drilling start points; Based on the type of the target network element, a corresponding drilling path is determined for each of the drilling starting points; For any of the aforementioned drill start points, drill through the call history along the corresponding drill path from the drill start point to retrieve the extended sub-level detailed records corresponding to the drill start point; The extended detailed record is generated based on each of the extended sub-level detailed records.

[0008] Furthermore, determining multiple drilling start points includes: Identify multiple failure log entries in the call history; The failure log information is used to determine the corresponding drilling start point.

[0009] Further, generating the extended detailed record based on each of the extended sub-level detailed records includes: The extended detailed records are concatenated and combined to obtain the extended detailed records; or The extended detailed records are obtained by weighting and combining the detailed records of each extended sub-level.

[0010] Further, the weighted combination of each of the extended sub-level detailed records to obtain the extended detailed record includes: For any of the extended sub-level detailed records, the corresponding weight is determined in a positive correlation with the length of the drill path corresponding to the extended sub-level detailed record; Based on the weights described, the quantified data of similar items in each of the extended sub-level detailed records are weighted and summed to obtain the quantified data of similar items in the extended detailed records.

[0011] Furthermore, the step of building a data cube based on the extended detailed record includes: Determine the hierarchical relationship of each of the aforementioned drilling start points; Based on the hierarchical relationship, the extended sub-level detailed records in the extended detailed record are divided into layers; The data cube is formed by recording the parent-child relationships between the detailed records of each extended sub-level after the layering.

[0012] Furthermore, the call history data processing method based on online analytical processing also includes: Perform index analysis on the data cube; The results of the analysis of the aforementioned indicators are then visualized.

[0013] On the other hand, embodiments of the present invention also include a computer device, including a memory and a processor, the memory for storing at least one program, and the processor for loading at least one program to execute the call history data processing method based on online analysis processing in the embodiments.

[0014] On the other hand, embodiments of the present invention also include a computer-readable storage medium storing a processor-executable program, which, when executed by a processor, is used to perform the call history data processing method based on online analysis processing in the embodiments.

[0015] The beneficial effects of this invention are as follows: The call history data processing method based on online analytical processing in the embodiments obtains extended detailed records by drilling down the call history data based on online analytical processing, and establishes a data cube based on the extended detailed records. The data cube includes the multi-dimensional and multi-level processing results of the call history data, which can provide data support for network KPI indicator degradation analysis, fault location analysis, and user complaint analysis, and assist in network operation and maintenance such as handling user complaints, thereby improving the operation and maintenance efficiency of the mobile communication network core network. Attached Figure Description

[0016] Figure 1 This is a schematic diagram illustrating the steps of the call history data processing method based on online analysis processing in the embodiment; Figure 2 This is a schematic diagram illustrating the execution process of the call history data processing method based on online analysis processing in the embodiment. Figure 3 This is a schematic diagram of the drilling path in the example where the target network element is an SMF, and the EventID in the failure log information is used to determine the corresponding drilling start point. Figure 4 This is a schematic diagram of the drilling path in the example where the target network element is AMF and the EventID in the failure log information is used to determine a corresponding drilling start point. Figure 5 This is a schematic diagram of the drilling path in the example where the target network element is an SMF, and the IMSI / SUPI in the failure log information is used as the corresponding drilling start point. Figure 6 This is a schematic diagram of the drilling path in the example where the target network element is AMF and the IMSI / SUPI in the failure log information is used as the corresponding drilling start point. Figure 7 This is a schematic diagram of the drilling path in the example where the target network element is an SMF and the NFID in the failure log information is used to determine a corresponding drilling start point. Figure 8This is a schematic diagram of the drilling path in the example where the target network element is AMF and the NFID in the failure log information is used to determine a corresponding drilling start point. Figure 9 This is a schematic diagram of the drilling path in the example where the target network element is a RAT and the NFID in the failure log information is used to determine a corresponding drilling start point. Figure 10 This is a schematic diagram of the drilling path in the example where the target network element is a RAT and the NFID in the failure log information is used to determine a corresponding drilling start point. Figure 11 This is a schematic diagram of a drilling path in the embodiment, where the APN / DNN in the failure log information is used to determine a corresponding drilling start point. Figure 12 This is a schematic diagram illustrating the drilling process following the path EventID->InnerCause->IMSI_SUPI->XDR in the embodiment. Figure 13 This is a schematic diagram illustrating drilling down to InnerCause via EventID in the embodiment; Figure 14 This is a schematic diagram of drilling down to IMSI_SUPI using InnerCause in the embodiment; Figure 15 This is a schematic diagram of drilling down to the XDR call detail record via IMSI_SUPI in the embodiment; Figure 16 This is a schematic diagram illustrating the drilling process following the path IMSI_SUPI->EventID->InnerCause->XDR in the embodiment. Figure 17 This is a schematic diagram illustrating the drilling down of the EventID based on IMSI_SUPI in the embodiment; Figure 18 This is a schematic diagram illustrating drilling down to InnerCause based on EventID in the embodiment; Figure 19 This is a schematic diagram of the XDR drilled according to the InnerCause in the embodiment; Figure 20 This is a schematic diagram illustrating the drilling process in the example, following the path NFID → InnerCause, ReqAPNDNN... → IMSI-SUPI → XDR. Figure 21 This is a schematic diagram illustrating the indicator information obtained through NFID drill-down in the embodiment; Figure 22 This is a schematic diagram illustrating the drilling down to IMSI_SUPI via ReqAPNDNN in the embodiment. Figure 23This is a schematic diagram of XDR drilled through IMSI_SUPI in the embodiment; Figure 24 This is a schematic diagram illustrating the drilling process in the example, following the path RAT->TACRAC->NFID, REQAPNDNN...->XDR. Figure 25 This is a schematic diagram of TacRac being drilled using RAT in the embodiment; Figure 26 This is a schematic diagram of NFID obtained by drilling through TACRAC in the embodiment; Figure 27 This is a schematic diagram of XDR obtained by drilling through REQAPNDNN in the embodiment; Figure 28 This is a schematic diagram illustrating the drill-down process in the embodiment, following the path ReqAPNDNN—>EventID—>InnerCause—>IMSI_SUPI—>XDR; Figure 29 This is a schematic diagram illustrating the EventID obtained through drill-down using ReqAPNDNN in the embodiment. Figure 30 This is a schematic diagram illustrating drilling down to InnerCause via EventID in the embodiment; Figure 31 This is a schematic diagram of drilling down to IMSI_SUPI using InnerCause in the embodiment; Figure 32 This is a schematic diagram of XDR drilled through IMSI_SUPI in the embodiment; Figure 33 and Figure 34 This is a schematic diagram of the analysis results obtained from analyzing a specific business scenario in the embodiment. Figure 35 This is a schematic diagram of the original XDR details and processing suggestions obtained by performing step S4 in the embodiment through a combined query of mixed field multi-condition logical expressions; Figure 36 This is a schematic diagram illustrating the business failure details obtained by performing step S4 in the embodiment based on a comprehensive query of any field or combination of fields in CHR; Figure 37 This is a schematic diagram of the computer device in the embodiment; Figure 38 This is a schematic diagram of a computer-readable storage medium in an embodiment. Detailed Implementation

[0017] Terminology Explanation: CHR (CALL HISTORY RECORD): Call history records describe the entire process of service connection. The parameters recorded in CHR come from the original signaling message data. Further analysis and processing of some important parameters in the records can provide a basis for mobile service analysis.

[0018] XDR (Extended Detail Record): In communication networks, it refers to the session-level detailed record of signaling and service transmission processes generated after processing all data from the Internet.

[0019] OLAP (Online Analytical Processing) is a computing technology used for the rapid analysis of multi-dimensional data. It is primarily geared towards complex data analysis, data mining, and business intelligence (BI) scenarios, aiming to help users analyze data from multiple perspectives and levels to support decision-making.

[0020] Mobile communication networks are telecommunications networks that provide communication services to mobile users. They connect terminals to the network via radio waves (air interface) and rely on core network mechanisms such as mobility management, session management, authentication, billing, and policy control to ensure uninterrupted service when users move across cells or regions. Broadly speaking, mobile communication networks include four parts: User Equipment (UE), Radio Access Network (RAN), Core Network (CN), and Data Network (DN). UEs specifically include mobile phones, modules, Customer Premises Equipment (CPE), and IoT terminals. RANs specifically include BTS / NodeB (for 2G / 3G mobile communication networks), eNodeB (for 4G mobile communication networks), and gNB (for 5G mobile communication networks), which are responsible for air interface resource scheduling and radio link management. Data networks specifically include the Internet, IMS (voice / video), enterprise private networks, and MEC (edge ​​computing) devices.

[0021] Core network: It is the brain and hub of the mobile communication network, responsible for authentication, mobility, session, policy, accounting, and data forwarding, including various network elements with different functions such as AMF, SMF, and NWDAF.

[0022] AMF: Access and Mobility Management Function, is a network element in the core network used to perform functions such as registration management (registration, deregistration, and periodic registration updates for terminal power-on / network access), mobility management (cell handover, location update, paging, and reachability management), connection management (establishment and maintenance of NAS signaling connection (N1 interface) between UE and network), NAS security (encryption and integrity protection of NAS messages), SMF selection (selecting a suitable SMF for the terminal based on slice (S-NSSAI), DNN, etc.), authentication relay (completing terminal authentication in conjunction with AMF / UDM), and transparent transmission of session messages.

[0023] SMF: Session Management Function, is a network element in the core network used to perform functions such as PDU session management (establishment, modification, and release of sessions), UPF selection and control (selecting an optimal path for the user plane and issuing forwarding rules to the UPF through the N4 interface), IP address allocation (assigning IP addresses to UEs and acting as a DHCP server and ARP / IPv6 neighbor agent), QoS and policy enforcement (retrieving policies from the PCF, translating them into specific QoS flows, gating, and charging rules, and handing them over to the UPF for execution), and charging (collecting session-level charging data and connecting to CHF downlink data notification: when the terminal is idle, it receives data and notifies the AMF to page the terminal).

[0024] NWDAF: Network Data Analytics Function, is a network element in the core network used to perform functions such as data collection (collecting massive amounts of operational data such as network subscription events from network elements such as AMF and SMF and terminals), analysis and reasoning (outputting statistical and predictive insights based on big data and machine learning), and result output (outputting analysis results and prediction results to consumers through standard service interfaces).

[0025] This embodiment provides a method for processing call history data based on online analysis processing. (Refer to...) Figure 1 The method for processing call history data based on online analytical processing includes the following steps: S1. Retrieve call history; S2. Perform online analytical processing-based data drill-down on the call history to obtain extended detailed records; S3. Based on the extended detailed records, build a data cube.

[0026] In this embodiment, the principle of the call history data processing method based on online analytical processing (OLAP) is to analyze and process call history data using OLAP data mining technology, thereby enabling user complaint processing and rapid problem localization.

[0027] Reference Figure 2 In this embodiment, the execution process of the call history data processing method based on online analytical processing includes four processes: A, data source layer, B, data acquisition layer, C, data processing layer, and D, data presentation layer. Each process corresponds to a step in the call history data processing method based on online analytical processing.

[0028] In this embodiment, A, the data source layer, and B, the data acquisition layer, correspond to step S1 in the call history data processing method based on online analytical processing.

[0029] In this embodiment, when A, the data source layer, and B, the data acquisition layer, execute step S1, which is the step of obtaining call history, they can specifically perform the following steps: S101. Detect target network elements in the core network of the mobile communication network; S102. When a service failure is detected in the target network element, retrieve the call history generated by the target network element.

[0030] In step S101, the target network element is the network element in the core network that is being detected, specifically a particular network element in the core network. For example, in this embodiment, AMF and SMF are used as examples of target network elements for illustration.

[0031] In step S102, each target network element generates its own Call History Record (CHR) when a service failure occurs. A CHR generated by a target network element typically contains various failure log information such as EventID, IMSI / SUPI, NFID, RAT, APN / DNN, StartTime, EndTime, NSID, NSType, Result, Cause, InnerCause, IMEI, and CIID. These failure log information describe the service failure event that occurred on the target network element from corresponding perspectives.

[0032] For example, EventID (Event Identifier / Event Type) identifies which specific service process triggered the failure. Each process type has a unique number within the network element; IMSI / SUPI represents International Mobile Subscriber Identity / Subscription Permanent Identifier, where IMSI is applicable to 2G, 3G, and 4G core networks, and SUPI is applicable to 5G core networks. IMSI / SUPI indicates that the service failure occurred in the service process of a specific subscribed user, thus identifying the bearer of the failure, such as which user / number / card failed during registration, session establishment, or handover; NFID represents Network Function Instance Identifier, indicating which specific network element instance recorded or reported the service failure, or in which processing stage of the network element instance the failure occurred; RAT (Radio Access Technology) identifies the current radio standard of the terminal, indicating whether the service failure is related to a specific access standard; APN / DNN represents Access Point Name / Data Network Name. Name), where APN is applicable to 2G, 3G, 4G and other core networks, and DNN is applicable to 5G and other core networks. APN / DNN indicates that the service failure occurred when the user attempted to access a specific service network; StartTime indicates the time when the service / process was initiated (the local timestamp when the network element receives the request or begins processing); EndTime indicates the time when the process terminates, whether it returns successfully or fails; NSID (Network Slice ID) identifies the specific network slice instance to which the failed service belongs (corresponding to S-NSSAI / NSI); NSType (Network Slice Type) identifies the service type of the slice, corresponding to SST (Slice / Service). Type) value; Result indicates the final outcome of this service—success / failure, or a more specific result code; Cause is a standardized failure reason code, which is visible to external network elements; InnerCause is an internal error code defined by the equipment manufacturer, which is more detailed than the standard Cause and directly points to which specific module / link within the network element has failed.IMEI (International Mobile Equipment Identity) is a globally unique identifier (usually 15 digits) for terminal hardware, essentially the device's serial number, identifying which specific device, model, or batch of terminals caused the service failure. CIID (Cell Identifier) ​​refers to the cell identifier information where the terminal was located at the time of the failure, indicating whether the service failure was concentrated in a particular base station or cell.

[0033] In this embodiment, when B and the data acquisition layer execute step S1, which is to obtain the call history record, the message distribution unit in B and the data acquisition layer can be responsible for distributing the call history record (CHR) evenly to the data acquisition unit in B and the data acquisition layer for processing. The data acquisition unit receives the original call history record (CHR) reported by each network element of the message distribution unit and completes the cleaning, conversion and adaptation of the original data.

[0034] In this embodiment, C, the data processing layer, corresponds to step S3 in the call history data processing method based on online analysis processing.

[0035] In this embodiment, when the data processing layer (C) performs step S3, which is to drill down the call history data based on online analysis processing to obtain extended detailed records, it can specifically perform the following steps: S301. Determine multiple drilling start points; S302. Determine the corresponding drilling path for each drilling starting point according to the type of the target network element; S303. For any drilling start point, drill through the call history along the corresponding drilling path from the drilling start point to query the extended sub-level detailed records corresponding to the drilling start point; S304. Generate extended detailed records based on the detailed records of each extended sub-level.

[0036] In this embodiment, when performing step S301, which is to determine multiple drilling start points, the following steps can be performed: S30101. Identify multiple failure log messages in the call history; S30102. Use the failure log information to determine the corresponding drill-up starting point.

[0037] In step S30101, according to the principle of step S102, the call history record CHR contains various failure log information such as EventID, IMSI / SUPI, NFID, RAT, APN / DNN, StartTime, EndTime, NSID, NSType, Result, Cause, InnerCause, IMEI, and CIID.

[0038] In step S30102, each failure log message is used to determine a corresponding drill-down starting point. For example, in this embodiment, the EventID, IMSI / SUPI, NFID, RAT, and APN / DNN in the failure log messages are used as corresponding drill-down starting points, respectively, for illustration purposes.

[0039] In this embodiment, the principle of steps S302-S303 is as follows: Figures 3-11 As shown.

[0040] 1. Use the EventID from the failure log information to determine the corresponding drill-up starting point. In this embodiment, when the EventID in the failure log information is used to determine a corresponding drill-down start point, the corresponding drill-down path is as follows: Figure 3 and Figure 4 As shown.

[0041] Specifically, Figure 3 This is the drill-down path corresponding to the target network element being an SMF. (Refer to...) Figure 3 In this drill-down path, drill down from the Event ID, find the internal cause code of the event based on the failure event, then find the user whose internal cause code occurred, and finally query the extended child detailed record 1 of the specific user (which is essentially an XDR detailed record).

[0042] Specifically, Figure 4 This is the drill-down path corresponding to the target network element being AMF. (Refer to...) Figure 4 In this drilling path, drilling begins from the Event ID, the cause code of the failure is found based on the failure event, and then the internal cause code, UDM ID and SMF ID are associated. Based on these, user information is associated, and finally extended sub-level detailed record 2 (which is essentially an XDR detailed record) is found. On the other hand, at the same time, based on the internal cause code, the location TAC information and base station information can be associated, and finally extended sub-level detailed record 2 is also found.

[0043] 2. Use the IMSI / SUPI information in the failure log to determine the corresponding drill start point. In this embodiment, when the IMSI / SUPI in the failure log information is used as the corresponding drill start point, the corresponding drill path is as follows: Figure 5 and Figure 6 As shown.

[0044] Specifically, Figure 5 This is the drill-down path corresponding to the target network element being an SMF. (Refer to...) Figure 5 In this drilling path, drilling begins from IMSI / SUPI, and the failure event is linked based on user information. Finally, the specific extended sub-level detailed record 3 (which is essentially an XDR detailed record) is found.

[0045] Specifically, Figure 6 This is the drill-down path corresponding to the target network element being AMF. (Refer to...) Figure 6 In this drilling path, the drill-down starts from IMSI / SUPI, associates the failure event with the user information, and then drills down step by step to the cause code, internal cause code, location and base station information, and finally finds the specific extended sub-level detailed record 4 (which is essentially an XDR detailed record).

[0046] 3. Use the NFID in the failure log information to determine the corresponding drill-up starting point. In this embodiment, when the NFID in the failure log information is used to determine a corresponding drill-up starting point, the corresponding drill-up path is as follows: Figure 7 and Figure 8 As shown.

[0047] Specifically, Figure 7 This is the drill-down path corresponding to the target network element being an SMF. (Refer to...) Figure 7 In this drilling path, drilling starts from NFID and is associated with APN, internal cause code, location, and user information based on SMF network element information. The internal cause code and location information are further associated with user information, and finally the specific extended sub-level detailed record 5 (which is essentially an XDR detailed record) is found.

[0048] Specifically, Figure 8 This is the drill-down path corresponding to the target network element being AMF. (Refer to...) Figure 8 In this drill-down path, drilling begins from NFID, and the failure event, location, and user information are associated with the AMF network element information; the failure event is further drilled down to the cause code, internal cause code, and user information; the location information is further drilled down to the failure event, cause code, internal cause code, and base station information; the user information is further drilled down to the failure event, cause code, internal cause code, location, and base station information; finally, the specific extended sub-level detailed record 6 (essentially an XDR detailed record) is found through the base station information and user information.

[0049] 4. Use the RAT in the failure log information as the corresponding drill-in starting point. In this embodiment, when the RAT in the failure log information is used as the corresponding drill-in starting point, the corresponding drill-in path is as follows: Figure 9 and Figure 10 As shown.

[0050] Specifically, Figure 9 This is the drill-down path corresponding to the target network element being an SMF. (Refer to...) Figure 9 In this drilling path, drilling begins from the RAT, and the location information is associated with the wireless access method. Further drilling is performed to obtain network element information, APNDNN, UPF information, MME network element information, SGW and PGW network element information, which in turn are associated with user information. Finally, the specific extended sub-level detailed record 7 (which is essentially an XDR detailed record) is queried.

[0051] Specifically, Figure 10 This is the drill-down path corresponding to the target network element being AMF. (Refer to...) Figure 10 In this drilling path, drilling begins from TAC / RAC, and the failure event is associated with the location information. Further drilling is performed to obtain the cause code, internal cause code, base station and user information, and finally the specific extended sub-level detailed record 8 (which is essentially an XDR detailed record).

[0052] 5. Use the APN / DNN in the failure log information as the corresponding drill-up starting point. In this embodiment, when the APN / DNN in the failure log information is determined as a corresponding drill-up starting point, the corresponding drill-up path is as follows: Figure 11 As shown.

[0053] Specifically, Figure 11 This is the drill-down path corresponding to the target network element being an SMF or AMF. (Refer to...) Figure 11 In this drilling path, the drilling starts from the APN / DNN, and the failure event is associated with the APN / DNN. The internal cause code and user information are further drilled down, and finally the specific extended sub-level detailed record 9 (which is essentially an XDR detailed record) is found.

[0054] In this embodiment, by executing Figures 3-11 The steps S302-S303 shown can obtain the extended sub-level detailed records obtained by drilling along the corresponding drilling path from each target network element starting from each drilling start point. These extended sub-level detailed records record the detailed information of service failure from different levels and dimensions.

[0055] In this embodiment, for Figures 3-11The extended sub-level detailed records shown, such as extended sub-level detailed record 1, extended sub-level detailed record 2, extended sub-level detailed record 3, extended sub-level detailed record 4, extended sub-level detailed record 5, extended sub-level detailed record 6, extended sub-level detailed record 7, extended sub-level detailed record 8, and extended sub-level detailed record 9, can be directly concatenated and combined during step S304 to obtain the extended detailed record.

[0056] In this embodiment, for Figures 3-11 The extended sub-level detailed records shown are 1, 2, 3, 4, 5, 6, 7, 8, and 9. During step S304, corresponding weights can be assigned to each of these extended sub-level detailed records, and the quantized data of similar items in each extended sub-level detailed record can be weighted and summed to obtain the quantized data of similar items in the extended detailed records. After traversing all the quantized data of similar items, the extended detailed records are assembled.

[0057] For example, in this embodiment, weight w1 is assigned to extended sub-level detailed record 1, weight w2 to extended sub-level detailed record 2, weight w3 to extended sub-level detailed record 3, weight w4 to extended sub-level detailed record 4, weight w5 to extended sub-level detailed record 5, weight w6 to extended sub-level detailed record 6, weight w7 to extended sub-level detailed record 7, weight w8 to extended sub-level detailed record 8, and weight w9 to extended sub-level detailed record 9, such that the sum of all weights is 1, i.e., w1 + w2 + w3 + w4 + w5 + w6 + w7 + w8 + w9 = 1. In this embodiment, the weight assigned to each extended sub-level detailed record is proportional to the length of the drill path corresponding to that extended sub-level detailed record. For example, refer to... Figures 3-11 If the drilling paths corresponding to extended sub-level detailed records such as extended sub-level detailed record 1 and extended sub-level detailed record 3 are relatively short, then the weights w1 and w3 assigned to them are relatively small. If the drilling paths corresponding to extended sub-level detailed records such as extended sub-level detailed record 2 and extended sub-level detailed record 6 are relatively short, then the weights w2 and w6 assigned to them are relatively large.

[0058] In this embodiment, the extended sub-level detailed records 1-9 respectively include quantized data such as end-to-end latency, latency at each stage, number of out-of-order packets, number of retransmitted packets, number of retransmitted bytes, TCP connection establishment latency, first packet latency, window size, and RTT. The end-to-end latency included in extended sub-level detailed records 1-9 is a single-item quantized data. It can be obtained by weighting and summing the end-to-end latency in extended sub-level detailed records 1-9 according to equal weights w1-w9. The same processing is applied to other single-item quantized data to obtain the single-item quantized data in the extended detailed records.

[0059] In this embodiment, the weight of each extended sub-level detailed record is determined based on the length of the drilling path, and the extended sub-level detailed records are combined to obtain an extended detailed record. This allows the extended sub-level detailed record with a longer drilling path and richer drilling details to have a greater weight, so that the final extended detailed record contains more contributions from the details, which is conducive to the final extended detailed record being closer to the real objective situation of the mobile communication network core network.

[0060] In this embodiment, each of the extended sub-level detailed records 1-9 corresponds to a different drill-down starting point. Since these drill-down starting points correspond to different levels, each of the extended sub-level detailed records 1-9 corresponds to a different level. In this embodiment, a parent-child relationship from high to low can be established between these levels, thereby combining the extended sub-level detailed records 1-9 to obtain a data cube model. Based on the above dimensional hierarchy conditions, the data cube is queried again to obtain the corresponding detailed data. Drilling down from different dimensions such as APNDNN, events, wireless access methods, network elements, and user information can ultimately yield XDR detailed bill information.

[0061] In this embodiment, the call history data processing method based on online analysis processing further includes the following steps: S4. Perform index analysis on the data cube; S5. Visualize the results of the indicator analysis.

[0062] In this embodiment, C, the data processing layer, corresponds to step S4 in the call history data processing method based on online analysis processing.

[0063] In step S4, the extended detailed records in the form of data cubes obtained in step S3 can be used for KPI indicator analysis, specific business scenario analysis, and various statistical analyses to assist in fault location analysis and user complaint analysis.

[0064] 1. KPI Indicator Analysis In this embodiment, network anomaly KPIs are analyzed from multiple dimensions based on the extended detailed records: TOP event analysis: By statistically analyzing the signaling processes with the highest failure rate, we can identify the top N poor-quality signaling processes and their errors. TOP User Analysis: Through statistical analysis, identify the terminals and users with the highest business failure rates, and use this to discover problematic terminals and users with a large number of issues; TOP network element analysis: Through horizontal comparative analysis of similar network elements, identify the network element with the highest failure rate; TOP Wireless Analysis: By comparing and analyzing wireless access types, we identify the wireless sites with the highest failure rates. TOP APN Analysis: Through APN / DNN statistical analysis, identify the business types with the highest failure rates.

[0065] In this embodiment, when performing step S4, the EventID, IMSI, NFID, RAT, and APNDNN metrics of the entire network's TOPN are analyzed.

[0066] (1) Analysis based on EventID Reference Figure 12 Drill down according to the path EventID->InnerCause->IMSI_SUPI->XDR. For example, Figure 13 As shown, drill down to InnerCause via EventID; as... Figure 14 As shown, drilling down through InnerCause leads to IMSI_SUPI; as... Figure 15 As shown, XDR call detail records are obtained by drilling down through IMSI_SUPI.

[0067] (2) Analysis based on IMSI_SUPI Reference Figure 16 Drill down according to the path IMSI_SUPI->EventID->InnerCause->XDR. For example... Figure 17 As shown, the EventID is drilled down based on IMSI_SUPI; as... Figure 18 As shown, drill down to InnerCause based on EventID; as... Figure 19 As shown, XDR was drilled in based on InnerCause.

[0068] (3) Analysis based on NFID Reference Figure 20Drill down according to the path NFID -> InnerCause, ReqAPNDNN... -> IMSI-SUPI -> XDR. Specifically, drill down through NFID to... Figure 21 The indicator information shown; such as Figure 22 As shown, IMSI_SUPI is obtained by drilling down through ReqAPNDNN; as Figure 23 As shown, XDR is drilled down via IMSI_SUPI.

[0069] (4) Analysis based on the wireless access method RAT Reference Figure 24 Drill down according to the path RAT -> TACRAC -> NFID, REQAPNDNN... -> XDR. For example... Figure 25 As shown, TacRac was drilled using RAT; as Figure 26 As shown, NFID, REQAPNDNN... are obtained by drilling down through TACRAC. Figure 27 As shown, XDR was obtained by drilling through REQAPNDNN.

[0070] (5) Analysis based on reqAPNDNN Reference Figure 28 Drill down according to the path ReqAPNDNN->EventID->InnerCause->IMSI_SUPI->XDR. For example... Figure 29 As shown, the EventID is obtained by drilling down through ReqAPNDNN; as... Figure 30 As shown, drill down to InnerCause via EventID; as... Figure 31 As shown, drilling down through InnerCause leads to IMSI_SUPI; as... Figure 32 As shown, XDR is drilled down via IMSI_SUPI.

[0071] 2. Specific business scenario analysis In this embodiment, by analyzing the extended detailed records, we can summarize and analyze initial registration failures, paging failures, 4G and 5G network switching failures, terminal analysis, etc., and find the most frequent causes of failure during abnormal times.

[0072] For example, various statistical analyses can be performed to assist in fault location analysis: during the fault handling process, combined queries with multi-condition logical expressions of mixed fields, along with various statistical analysis methods, allow for arbitrary drill-down analysis, ultimately obtaining the original XDR detailed report and handling suggestions.

[0073] For example, user complaint analysis can be performed: using flexible query functions similar to Wireshark, a comprehensive query can be performed based on any field or combination of fields in CHR to find the corresponding business failure details, and the error code and handling suggestions can be used to assist in problem handling.

[0074] For example, when performing specific business scenario analysis in step S4, initial registration failure, paging failure, 4G and 5G network handover failure, and terminal analysis can be summarized and analyzed to obtain... Figure 33 and Figure 34 The analysis results are shown.

[0075] 3. Fault location analysis In this embodiment, when performing step S4, it can be done as follows: Figure 35 As shown, by combining multi-condition logical expressions with mixed fields and using various statistical analysis methods, drill-down analysis can be performed at will to finally obtain the original XDR detailed report and processing suggestions.

[0076] 4. User Complaint Analysis In this embodiment, when performing step S4, it can be done as follows: Figure 36 As shown, a comprehensive query is performed based on any field or combination of fields in CHR to find the corresponding business failure details, and the error code and handling suggestions are used to assist in problem handling.

[0077] In this embodiment, the data processing layer executes S1-S4, utilizing data mining, OLAP, and other technologies to flexibly aggregate, mine, and drill down into massive amounts of CHR data. This allows the layer to obtain information such as network anomaly KPIs, specific business scenarios leading to service failures, fault location in the core network, and details of user complaints. Furthermore, the layer can store CHR data, data cubes, and analysis results in a GBase columnar database cluster, thereby providing data support for troubleshooting and repair of the mobile communication network core network.

[0078] In this embodiment, D, the data presentation layer, corresponds to step S5 in the call history data processing method based on online analytical processing. Specifically, the data presentation layer presents the data in the form of tables, bar charts, line charts, pie charts, etc., and provides various specialized analysis reports. For example, when executing step S5, D, the data presentation layer, can present the analysis results as... Figures 12-34 The data is presented visually in the form shown, thereby improving its readability.

[0079] In this embodiment, the call history data processing method based on online analytical processing acquires call history data from mobile network core network elements, and based on the call history data, provides functions such as network indicator analysis, user complaint handling, and fault localization through data analysis methods such as querying, statistics, and trends, thereby solving the following problems: 1. The problem of difficult location: Since the call history comes from inside the network element, processing the call history can extract detailed location information such as the cause of the error and the precise location inside the network element. 2. Analysis of difficult problems: Based on the multi-dimensional and combined dimension analysis of call history, it is helpful to find the key factors of poor network element indicators. 3. Difficulty in tracing customer complaints: By default, all failed CHRs of mobile network users are recorded, making it easy to trace the user's failure and locate the problem in the user's complaint.

[0080] Based on the solutions to the above-mentioned technical problems, the call history data processing method based on online analytical processing in this embodiment can achieve the following effects: 1. Improve the KPI indicators of core network elements in mobile communication networks: The data cube established based on the call history data processing method of online analytical processing can perform CHR arbitrary field and logical expression combination queries; through arbitrary dimension clustering analysis and trend analysis of query conditions, the root cause of KPI indicator anomalies can be identified. 2. Rapid handling of user complaints: Utilizing centralized storage and correlation query of CHR across multiple network elements, and based on multi-dimensional statistical analysis methods of CHR, network KPI degradation analysis, fault location analysis, and user complaint analysis are conducted to assist in handling user complaints; 3. Quickly locate core network faults: Through OLAP data drilling technology, multi-level deep drilling is performed, eventually reaching the XDR call detail record. By utilizing the various fields and other information carried by the CHR when the service fails, the cause and location of the fault can be accurately obtained. This enables quick and effective fault location and handling of user complaints, thereby improving operation and maintenance efficiency.

[0081] A computer program can be written to execute the call history data processing method based on online analytical processing in this embodiment, and then written into the system. Figure 37 The computer device shown or Figure 38In the storage medium shown, when the computer program is read and run, the call history data processing method based on online analytical processing (OLAP) of this embodiment is executed, thereby achieving the same technical effect as the call history data processing method based on OLAP in the embodiment. For example, when the computer program is written to the memory in the computer device, the processor can read the computer program from the memory and execute the call history data processing method based on OLAP in this embodiment.

[0082] It should be noted that, unless otherwise specified, when a feature is referred to as "fixed" or "connected" to another feature, it can be directly fixed or connected to the other feature, or indirectly fixed or connected to the other feature. Furthermore, the descriptions of "upper," "lower," "left," and "right" used in this disclosure are only relative to the relative positional relationships of the components of this disclosure in the accompanying drawings. The singular forms "a" and "the" used in this disclosure are also intended to include the plural forms, unless the context clearly indicates otherwise. Moreover, unless otherwise defined, all technical and scientific terms used in this embodiment have the same meaning as commonly understood by one of ordinary skill in the art. The terminology used in this embodiment specification is only for describing particular embodiments and is not intended to limit the invention. The term "and / or" as used in this embodiment includes any combination of one or more of the associated listed items.

[0083] It should be understood that although the terms first, second, third, etc., may be used to describe various elements in this disclosure, these elements should not be limited to these terms. These terms are only used to distinguish elements of the same type from each other. For example, a first element may also be referred to as a second element without departing from the scope of this disclosure, and similarly, a second element may also be referred to as a first element. The use of any and all instances or exemplary language (“e.g.,” “such as,” etc.) provided in this embodiment is intended only to better illustrate embodiments of the invention and, unless otherwise required, does not impose a limitation on the scope of the invention.

[0084] It should be recognized that embodiments of the present invention can be implemented or carried out by computer hardware, a combination of hardware and software, or by computer instructions stored in a non-transitory computer-readable storage medium. The method can be implemented using standard programming techniques—including a non-transitory computer-readable storage medium configured with a computer program, wherein such a storage medium causes the computer to operate in a specific and predefined manner—according to the methods and drawings described in the specific embodiments. Each program can be implemented in a high-level procedural or object-oriented programming language to communicate with the computer system. However, if desired, the program can be implemented in assembly or machine language. In any case, the language can be a compiled or interpreted language. Furthermore, for this purpose, the program can run on a programmed application-specific integrated circuit (ASIC).

[0085] Furthermore, the procedures described in this embodiment can be performed in any suitable order unless otherwise indicated by this embodiment or clearly contradicted by the context. The procedures (or variations and / or combinations thereof) described in this embodiment can be executed under the control of one or more computer systems configured with executable instructions, and can be implemented by hardware or a combination thereof as code (e.g., executable instructions, one or more computer programs, or one or more applications) that commonly executes on one or more processors. A computer program includes multiple instructions executable by one or more processors.

[0086] Furthermore, the method can be implemented in any suitable type of computing platform, including but not limited to personal computers, minicomputers, mainframes, workstations, networked or distributed computing environments, standalone or integrated computer platforms, or in communication with charged particle tools or other imaging devices, etc. Aspects of the invention can be implemented as machine-readable code stored on a non-transitory storage medium or device, whether removable or integrated into a computing platform, such as a hard disk, optical read and / or write storage medium, RAM, ROM, etc., such that it is readable by a programmable computer, and when the storage medium or device is read by the computer, it can be used to configure and operate the computer to perform the processes described herein. Furthermore, the machine-readable code, or portions thereof, can be transmitted via wired or wireless networks. The invention of this embodiment includes these and other different types of non-transitory computer-readable storage media when such media comprises instructions or programs that implement the steps above in conjunction with a microprocessor or other data processor. When programmed according to the methods and techniques of the invention, the invention also includes the computer itself.

[0087] A computer program can be applied to input data to perform the functions of this embodiment, thereby transforming the input data to generate output data stored in non-volatile memory. The output information can also be applied to one or more output devices, such as a display. In a preferred embodiment of the invention, the transformed data represents physical and tangible objects, including specific visual depictions of physical and tangible objects generated on the display.

[0088] The above are merely preferred embodiments of the present invention. The present invention is not limited to the above-described embodiments. Any modifications, equivalent substitutions, improvements, etc., made within the spirit and principles of the present invention, as long as they achieve the technical effects of the present invention by the same means, should be included within the scope of protection of the present invention. Within the scope of protection of the present invention, the technical solutions and / or implementation methods can have various modifications and variations.

Claims

1. A method for processing call history data based on online analytical processing, characterized in that, The call history data processing method based on online analytical processing includes: Retrieve call history; Data drill-down based on online analytics is performed on the call history to obtain extended detailed records; Based on the extended detailed records, a data cube is constructed.

2. The call history data processing method based on online analytical processing according to claim 1, characterized in that, The process of obtaining call history includes: Detect target network elements in the core network of the mobile communication network; When a service failure is detected in the target network element, the call history generated by the target network element is retrieved.

3. The call history data processing method based on online analytical processing according to claim 2, characterized in that, The data drill-down based on online analytical processing of the call history to obtain extended detailed records includes: Determine multiple drilling start points; Based on the type of the target network element, a corresponding drilling path is determined for each of the drilling starting points; For any of the aforementioned drill start points, drill through the call history along the corresponding drill path from the drill start point to retrieve the extended sub-level detailed records corresponding to the drill start point; The extended detailed record is generated based on each of the extended sub-level detailed records.

4. The call history data processing method based on online analytical processing according to claim 3, characterized in that, The determination of multiple drilling start points includes: Identify multiple failure log entries in the call history; The failure log information is used to determine the corresponding drilling start point.

5. The call history data processing method based on online analytical processing according to claim 3, characterized in that, The step of generating the extended detailed record based on each of the extended sub-level detailed records includes: The extended detailed records are concatenated and combined to obtain the extended detailed records; or The extended detailed records are obtained by weighting and combining the detailed records of each extended sub-level.

6. The call history data processing method based on online analytical processing according to claim 5, characterized in that, The step of weighting and combining the detailed records of each of the extended sub-levels to obtain the extended detailed records includes: For any of the extended sub-level detailed records, the corresponding weight is determined in a positive correlation with the length of the drill path corresponding to the extended sub-level detailed record; Based on the weights described, the quantified data of similar items in each of the extended sub-level detailed records are weighted and summed to obtain the quantified data of similar items in the extended detailed records.

7. The call history data processing method based on online analytical processing according to any one of claims 3-6, characterized in that, The step of building a data cube based on the extended detailed record includes: Determine the hierarchical relationship of each of the aforementioned drilling start points; Based on the hierarchical relationship, the extended sub-level detailed records in the extended detailed record are divided into layers; The data cube is formed by recording the parent-child relationships between the detailed records of each extended sub-level after the layering.

8. The method for processing call history data based on online analytical processing according to any one of claims 1-6, characterized in that, The online analytical processing-based call history data processing method further includes: Perform index analysis on the data cube; The results of the analysis of the aforementioned indicators are then visualized.

9. A computer device, characterized in that, It includes a memory and a processor, the memory being used to store at least one program, and the processor being used to load at least one program to execute the call history data processing method based on online analytical processing as described in any one of claims 1-8.

10. A computer-readable storage medium storing a processor-executable program, characterized in that, The processor-executable program, when executed by the processor, is used to perform the call history data processing method based on online analytical processing as described in any one of claims 1-8.