Call record file early warning method and device and storage medium

Abstract

This application provides a call detail record (CDR) file early warning method, apparatus, and storage medium, relating to the field of communication technology, and capable of being used for CDR file early warning. The method includes: acquiring first CDR file information; the first CDR file information includes at least one of the following: the number of first CDR files and the size of the first CDR files; determining, based on the first CDR file information, an early warning threshold range and a preset number of detections for the first CDR files within multiple preset time periods; determining whether the number of first CDR files exceeds or falls below the early warning threshold range within the preset number of detections; if so, determining abnormal indicator information for the first CDR files; and generating CDR early warning information based on the abnormal indicator information. This application is used for call detail record (CDR) file early warning.

Description

TECHNICAL FIELD

[0001] The present application relates to the technical field of communication, and in particular to a bill file early warning method and device and a storage medium. BACKGROUND

[0002] At present, a bill file early warning detection device adopts a unified early warning scheme to realize detection of abnormal bills by setting a unified early warning threshold. However, the unified early warning scheme cannot monitor the differentiated indexes of bill files, and lacks flexibility and accuracy of bill file monitoring. Therefore, how to flexibly monitor and early warn bill abnormalities becomes a technical problem to be solved. SUMMARY

[0003] The present application provides a bill file early warning method, device and storage medium, which can perform bill file early warning.

[0004] To achieve the above-mentioned purpose, the present application adopts the following technical scheme:

[0005] In a first aspect, the present application provides a bill file early warning method, which comprises: obtaining first bill file information; the first bill file information comprises at least one of the following: the number of first bill files and the size of first bill files; determining the early warning threshold range and the preset detection number of the first bill files in a plurality of preset time periods according to the first bill file information; determining whether the number of the first bill files exceeds or is lower than the early warning threshold range within the preset detection number; if so, determining abnormal index information of the first bill files; and generating bill early warning information according to the abnormal index information.

[0006] In combination with the first aspect, in a possible implementation manner, the determination of the early warning threshold range and the preset detection number of the first bill files in a plurality of preset time periods according to the first bill file information comprises: determining a first change trend of the number of the first bill files; determining the early warning threshold range of the first bill files in a plurality of preset time periods according to the first change trend; and determining the preset detection number of the first bill files in a plurality of preset time periods according to the number of the first bill files and the size of the first bill files.

[0007] In combination with the first aspect, in a possible implementation manner, the determination of the abnormal index information of the first bill files comprises: obtaining core network index information; marking an abnormal point of the number of the first bill files exceeding or being lower than the preset early warning range; and determining abnormal information of the abnormal point according to the core network index information.

[0008] In a possible implementation manner of the first aspect, before the first bill file information is acquired, the method further includes: acquiring a second bill file; dividing the second bill file into a plurality of sub-bill files; combining the plurality of sub-bill files according to a preset order to generate the first bill file; and determining first bill information of the first bill file according to the first bill file.

[0009] In a possible implementation manner of the first aspect, before the first bill file information is acquired, the method further includes: acquiring a second bill file; dividing the second bill file into a plurality of sub-bill files; combining the plurality of sub-bill files according to a preset order to generate the first bill file; and determining first bill information of the first bill file according to the first bill file.

[0010] In a possible implementation manner of the second aspect, the processing unit is specifically configured to: determine a first change trend of the number of the first bill files; determine the pre-warning threshold range of the first bill files in the plurality of preset time periods according to the first change trend; and determine the preset detection times of the first bill files in the plurality of preset time periods according to the number of the first bill files and the size of the first bill files.

[0011] In a possible implementation manner of the second aspect, the processing unit is specifically configured to: determine a first change trend of the number of the first bill files; determine the pre-warning threshold range of the first bill files in the plurality of preset time periods according to the first change trend; and determine the preset detection times of the first bill files in the plurality of preset time periods according to the number of the first bill files and the size of the first bill files.

[0012] In a possible implementation manner of the second aspect, the processing unit is further specifically configured to: acquire core network index information; mark an abnormal point at which the number of the first bill files exceeds or is lower than the preset pre-warning range; and determine abnormal information of the abnormal point according to the core network index information.

[0013] In a possible implementation manner of the second aspect, the processing unit is further configured to: determine a second change trend of the first bill file quantity according to the core network index information; if the first bill file quantity of the abnormal point matches the second change trend, determine that the core network index information is abnormal information; if the first bill file quantity of the abnormal point does not match the second change trend, determine that the target information of the abnormal point is abnormal information; and the target information at least includes one of the first file quantity at the abnormal point and change trend information of the first file quantity at the abnormal point.

[0014] In a possible implementation manner of the second aspect, the processing unit is further configured to: obtain a second bill file; divide the second bill file into a plurality of sub-bill files; combine the plurality of sub-bill files in a preset order to generate a first bill file; and determine first bill information of the first bill file according to the first bill file.

[0015] In a third aspect, the present application provides a bill file early warning device, which comprises a processor and a memory; wherein the memory is configured to store computer execution instructions; when the bill file early warning device is running, the processor executes the computer execution instructions stored in the memory, so that the bill file early warning device executes the bill file early warning method described in the first aspect and any possible implementation manner of the first aspect.

[0016] In a fourth aspect, the present application provides a computer readable storage medium, and the computer readable storage medium stores instructions; when the instructions in the computer readable storage medium are executed by the processor of the bill file early warning device, the bill file early warning device can execute the bill file early warning method described in the first aspect and any possible implementation manner of the first aspect.

[0017] In a fifth aspect, the present application provides a computer program product comprising instructions; when the computer program product is running on the bill file early warning device, the bill file early warning device executes the bill file early warning method described in the first aspect and any possible implementation manner of the first aspect.

[0018] In a sixth aspect, the present application provides a chip, which comprises a processor and a communication interface; the communication interface and the processor are coupled; the processor is configured to run a computer program or instructions, so as to realize the bill file early warning method described in the first aspect and any possible implementation manner of the first aspect.

[0019] Specifically, the chip provided in the embodiments of the present application further comprises a memory configured to store the computer program or instructions.

[0020] In the present application, the name of the above-mentioned bill file early warning device does not constitute a limitation on the device or functional module itself, and in actual implementation, these devices or functional modules can appear with other names. As long as the functions of each device or functional module are similar to those of the present application, they belong to the scope of the claims of the present application and their equivalents.

[0021] These aspects or other aspects of the present application will be more apparent in the following description.

[0022] The technical solutions provided by the present application at least have the following beneficial effects: The bill file early warning device obtains bill information such as the number and size of the first bill file. The bill file early warning device determines the early warning threshold range of the first bill file in multiple different time periods and the preset detection number of times when the early warning value range is exceeded based on the obtained first bill file information. The bill file early warning device determines whether the first bill file has a case where the number of the first bill file exceeds or is lower than the early warning threshold range within the preset detection number of times. If so, the bill file early warning device determines abnormal index information of the first bill file. The bill file early warning device generates bill early warning information according to the obtained abnormal index information. In this way, the bill file early warning device sets different bill early warning threshold ranges in different time periods and preset detection numbers of times when bill abnormalities occur by obtaining information such as the number and size of the bill file. Moreover, the bill file early warning device generates bill early warning information from bill abnormal index information, which facilitates subsequent arrangement and maintenance of bill files. The flexibility and accuracy of bill detection and early warning are improved. BRIEF DESCRIPTION OF DRAWINGS

[0023] Figure 1 A bill file early warning system structure schematic diagram provided by an embodiment of the present application;

[0024] Figure 2 A hardware structure schematic diagram of a bill file early warning device provided by an embodiment of the present application;

[0025] Figure 3 A flowchart of a bill file early warning method provided by an embodiment of the present application;

[0026] Figure 4 Another flowchart of a bill file early warning method provided by an embodiment of the present application;

[0027] Figure 5 Another flowchart of a bill file early warning method provided by an embodiment of the present application;

[0028] Figure 6 Another flowchart of a bill file early warning method provided by an embodiment of the present application;

[0029] Figure 7This is a schematic diagram of a call detail record (CDR) file early warning device provided in an embodiment of this application. Detailed Implementation

[0030] The following description, in conjunction with the accompanying drawings, details the call detail record (CDR) file early warning method, apparatus, and storage medium provided in this application embodiment.

[0031] In this article, the term "and / or" is merely a description of the relationship between related objects, indicating that there can be three relationships. For example, A and / or B can represent three situations: A exists alone, A and B exist simultaneously, and B exists alone.

[0032] The terms "first" and "second," etc., used in the specification and drawings of this application are used to distinguish different objects or to distinguish different treatments of the same object, rather than to describe a specific order of objects.

[0033] Furthermore, the terms "comprising" and "having," and any variations thereof, used in the description of this application are intended to cover non-exclusive inclusion. For example, a process, method, system, product, or apparatus that includes a series of steps or units is not limited to the steps or units listed, but may optionally include other steps or units not listed, or may optionally include other steps or units inherent to such process, method, product, or apparatus.

[0034] It should be noted that in the embodiments of this application, the words "exemplary" or "for example" are used to indicate examples, illustrations, or explanations. Any embodiment or design scheme described as "exemplary" or "for example" in the embodiments of this application should not be construed as being more preferred or advantageous than other embodiments or design schemes. Specifically, the use of the words "exemplary" or "for example" is intended to present the relevant concepts in a specific manner.

[0035] In related technologies, call detail record (CDR) file early warning detection devices employ a unified early warning scheme, detecting abnormal CDRs by setting uniform early warning thresholds. However, this unified scheme cannot monitor based on the differentiated indicators of CDR files, lacking the flexibility and accuracy of CDR file monitoring. Therefore, how to flexibly monitor and issue early warnings for abnormal CDRs has become an urgent technical problem to be solved.

[0036] To address the aforementioned technical problems, this application provides a call detail record (CDR) file early warning method. The CDR file early warning device acquires CDR information such as the quantity and size of a first CDR file. Based on the acquired information, the CDR file early warning device determines the early warning threshold range for the first CDR file within multiple different time periods and a preset number of detections when the threshold is exceeded. Within the preset number of detections, the CDR file early warning device determines whether the quantity of the first CDR file exceeds or falls below the early warning threshold range. If so, the CDR file early warning device identifies abnormal indicator information for the first CDR file. Based on the acquired abnormal indicator information, the CDR file early warning device generates CDR early warning information. In this way, the CDR file early warning device, by acquiring information such as the quantity and size of CDR files, sets different CDR early warning threshold ranges for different time periods and a preset number of detections when CDR anomalies occur. Furthermore, the CDR file early warning device generates CDR early warning information from abnormal indicator information, facilitating subsequent CDR file organization and maintenance. This improves the flexibility and accuracy of CDR detection and early warning.

[0037] This application provides a call detail record (CDR) file early warning method, which can be applied to, for example... Figure 1 The document early warning system 10 shown includes: a data acquisition unit 101, a preprocessing unit 102, an analysis unit 103, a judgment module 104, an anomaly indicator judgment and processing module 105, and a monitoring data presentation and notification module 106. The data acquisition unit is used to acquire files from a specified target directory; the preprocessing unit is used to preprocess the acquired target files according to a prescribed format; the analysis unit is used to analyze the file indicators of the target files; the judgment module is used to determine whether the indicators of the target files are within the threshold range; the anomaly indicator judgment and processing module is used to mark and process anomalies; and the monitoring data presentation and notification module is used to present and notify the monitoring quantity trend and anomalies of the target files.

[0038] Figure 2 This application provides a schematic diagram of the structure of a call detail record (CDR) file early warning device, which can be applied to, for example... Figure 1 The call detail record (CDR) file early warning system 10 shown includes a CDR file early warning device 200 comprising at least one processor 201, a communication line 202, and at least one communication interface 204, and may also include a memory 203. The processor 201, memory 203, and communication interface 204 are connected via the communication line 202.

[0039] The processor 201 may be a central processing unit (CPU), an application-specific integrated circuit (ASIC), or one or more integrated circuits configured to implement the embodiments of this application, such as one or more digital signal processors (DSPs), or one or more field-programmable gate arrays (FPGAs).

[0040] Communication line 202 may include a path for transmitting information between the aforementioned components.

[0041] The communication interface 204 is used to communicate with other devices or communication networks. It can use any transceiver-like device, such as Ethernet, radio access network (RAN), wireless local area network (WLAN), etc.

[0042] The memory 203 may be a read-only memory (ROM) or other type of static storage device capable of storing static information and instructions, random access memory (RAM) or other type of dynamic storage device capable of storing information and instructions, or electrically erasable programmable read-only memory (EEPROM), compact disc read-only memory (CD-ROM) or other optical disc storage, optical disc storage (including compressed optical discs, laser discs, optical discs, digital universal optical discs, Blu-ray discs, etc.), magnetic disk storage media or other magnetic storage devices, or any other medium capable of including or storing desired program code having the form of instructions or data structures and accessible by a computer, but not limited thereto.

[0043] In one possible design, the memory 203 can exist independently of the processor 201, meaning the memory 203 can be an external memory of the processor 201. In this case, the memory 203 can be connected to the processor 201 via the communication line 202 to store execution instructions or application code, and its execution is controlled by the processor 201 to implement the space measurement determination method provided in the following embodiments of this application. In another possible design, the memory 203 can also be integrated with the processor 201, meaning the memory 203 can be an internal memory of the processor 201. For example, the memory 203 can be a cache, which can be used to temporarily store some data and instruction information.

[0044] As one possible implementation, processor 201 may include one or more CPUs, for example Figure 1 CPU0 and CPU1 in the example. Alternatively, the call detail record (CDR) file warning device 200 may include multiple processors, such as... Figure 1 The processors 201 and 207 are included. Alternatively, the call detail record (CDR) file warning device 200 may also include an output device 205 and an input device 206.

[0045] Through the above description of the implementation methods, those skilled in the art will clearly understand that, for the sake of convenience and brevity, only the division of the above functional modules is used as an example. In practical applications, the above functions can be assigned to different functional modules as needed, that is, the internal structure of the network node can be divided into different functional modules to complete all or part of the functions described above. The specific working process of the system, modules, and network nodes described above can be referred to the corresponding process in the foregoing method embodiments, and will not be repeated here.

[0046] Figure 3 The call detail record (CDR) file early warning method provided in this application embodiment, such as Figure 3 As shown, the call detail record (CDR) file early warning method provided in this application embodiment can be implemented through the following steps 301 to 305.

[0047] Step 301: The call detail record (CDR) file early warning device acquires the first CDR file information.

[0048] The information in the first episode file includes at least one of the following: the number of first episode files and the size of the first episode file.

[0049] In one possible implementation, the call detail record (CDR) file early warning device acquires information about the first CDR file, including the number of first CDR files, the size of the first CDR file, and the duration of the first CDR file.

[0050] In one example, the call detail record (CDR) file early warning device collects all CDR files related to mobile network users from the billing gateway on the core network side. The CDR file early warning device performs call detail record (CDR) splitting and reassembly processing on the collected CDR files to obtain a first CDR file. Based on this first CDR file, the CDR file early warning device obtains information about the first CDR file.

[0051] Step 302: The call detail record (CDR) file early warning device determines the early warning threshold range and preset detection count of the first CDR file within multiple preset time periods based on the information in the first CDR file.

[0052] In one possible implementation, the call detail record (CDR) file early warning device determines the changing trend of the first CDR file information over different time periods based on information such as the number, size, and duration of the first CDR file. Based on the changing trend of the first CDR file information over multiple time periods, the CDR file early warning device determines the early warning threshold range and preset detection count for the first CDR file within those multiple time periods.

[0053] Step 303: The call detail record (CDR) file early warning device determines whether the number of CDR files exceeds or falls below the early warning threshold within a preset number of detections.

[0054] In one possible implementation, the call detail record (CDR) file early warning device detects the quantity of the first CDR file at different time periods. If the quantity of the first CDR file suddenly increases or decreases, the CDR file early warning device continuously detects the first CDR file, and the number of continuous detections is the preset number of detections determined in step 302. Within the preset number of detections, the CDR file early warning device checks whether the quantity of the first CDR file exceeds or falls below the early warning threshold range. If it does, the CDR file early warning device determines that the first CDR file is abnormal. If it does not, the CDR file early warning device determines that the first CDR file is not abnormal.

[0055] In one example, the preset number of checks for call detail records (CDRs) is N. If, in N checks, the number of first CDRs is outside the warning threshold range once or more, the CDR warning device determines that the first CDR is abnormal. If, in N checks, the number of first CDRs is within the warning threshold range for all of them, the CDR warning device determines that the first CDR is not abnormal.

[0056] Step 304: If it exists, the call detail record (CDR) file early warning device determines the abnormal indicator information of the first CDR file.

[0057] In one possible implementation, if the number of first call detail records (CDRs) exceeds or falls below the warning threshold at least once within a preset number of detections, the CDR warning device locates and obtains the abnormal indicator information of the first CDRs.

[0058] Step 305: The call detail record (CDR) file early warning device generates CDR early warning information based on abnormal indicator information.

[0059] In one possible implementation, the call detail record (CDR) file early warning device records and saves the acquired abnormal information, and generates CDR early warning information based on the recorded and saved abnormal information.

[0060] In one example, the call detail record (CDR) file early warning device saves and visualizes the acquired abnormal indicator information. Simultaneously, the device summarizes this abnormal indicator information, generates CDR early warning information, and notifies relevant maintenance personnel of this information via SMS.

[0061] The above solution offers at least the following benefits: The call detail record (CDR) file early warning device acquires CDR information such as the quantity and size of the first CDR file. Based on this information, the device determines the early warning threshold range for the first CDR file across multiple time periods and the preset number of checks required when the threshold is exceeded. Within the preset number of checks, the device determines whether the quantity of the first CDR file exceeds or falls below the early warning threshold. If so, the device identifies abnormal indicators for the first CDR file. Based on this abnormal indicator information, the device generates a CDR early warning message. In this way, by acquiring information such as the quantity and size of the CDR files, the device sets different early warning threshold ranges for different time periods and preset checks for abnormal CDR occurrences. Furthermore, the generation of early warning messages from abnormal indicator information facilitates the subsequent organization and maintenance of CDR files, improving the flexibility and accuracy of CDR detection and early warning.

[0062] Combination Figure 3 ,like Figure 4 As shown, step 302 above, namely, the call detail record (CDR) file early warning device determining the early warning threshold range and preset detection count of the first CDR file within multiple preset time periods based on the first CDR file information, can be specifically implemented through the following steps 401-403:

[0063] Step 401: The call detail record (CDR) file early warning device determines the first trend of change in the number of the first CDR file.

[0064] In one possible implementation, the call detail record (CDR) file early warning device acquires the trend of the number of first CDR files over a historical period.

[0065] In one example, the call detail record (CDR) file early warning device acquires the number of CDR files in the first CDR file over the past week. Based on the trend of the number of CDR files in the first CDR file over the past week, the CDR file early warning device determines the service volume of the CDR files, the real-time processing capability of the CDR files, and any problems existing in the CDR files.

[0066] Step 402: The call detail record (CDR) file early warning device determines the early warning threshold range of the first CDR file within multiple preset time periods based on the first change trend.

[0067] In one possible implementation, the call detail record (CDR) file early warning device predicts the change trend of the number of CDR files in different time periods based on the change trend of the first CDR file within a historical time period. Based on the change trend of the number of CDR files, the CDR file early warning device determines the early warning threshold range of the first CDR file within multiple different preset time periods.

[0068] In one example, within a preset time period from 0:00 to 6:00, the call detail record (CDR) file early warning device determines the early warning threshold range for the first CDR file within that time period based on the changing trend of the number of user CDRs generated during that time period. The threshold range is: the number of CDR files does not exceed 150,000, the size of the CDR file does not exceed 15MB, and the duration of the CDR file does not exceed 900 seconds.

[0069] Step 403: The call detail record (CDR) file early warning device determines the preset number of times to detect the first CDR file within multiple preset time periods based on the number and size of the first CDR file.

[0070] In one possible implementation, the call detail record (CDR) early warning device sets a preset number of detections for the first CDR file in different time periods based on the number and size of the first CDR file, as well as information such as the trend of the number of the first CDR file based on historical time periods.

[0071] In one example, within a preset time period from 0:00 to 6:00, the call detail record (CDR) file early warning device determines the preset number of checks within that time period based on the quantity and size of the CDR files. For example, the preset number of checks within that preset time period is determined to be N.

[0072] The above solution offers at least the following benefits: The call detail record (CDR) file early warning device determines the first trend of change within a historical time period of the first CDR file. Based on the acquired first trend of change, the CDR file early warning device determines the early warning threshold range for the first CDR file within multiple preset time periods. Based on the early warning threshold range of the CDR file, the CDR file early warning device determines the preset number of times to detect the first CDR file within multiple preset time periods, based on the number and size of the first CDR file. In this way, the CDR file early warning device determines the early warning threshold range and the preset number of detections for the CDR file in different time periods by detecting the historical trend of changes in the number of CDR files, as well as information such as the number and size of the CDR files. This improves the accuracy of CDR file monitoring and ensures the efficiency and accuracy of the CDR file early warning device in handling abnormal situations when CDR files are abnormal in different time periods and application scenarios.

[0073] Combination Figure 3 ,like Figure 5 As shown, in step 304 above, if an anomaly exists, the call detail record (CDR) file early warning device determines the abnormal indicator information of the first CDR file. This can be specifically achieved through the following steps 501-503:

[0074] Step 501: The call detail record (CDR) file early warning device acquires core network indicator information.

[0075] In one possible implementation, the call detail record (CDR) file early warning device obtains core network indicator information from the core network side.

[0076] In one example, the call detail record (CDR) file early warning device establishes a connection mechanism with the core network. Based on this connection mechanism, the CDR file early warning device obtains core network indicator information that affects the number of first CDR files. For example, if the core network performs an upgrade or maintenance operation, this operation will cause the number of first CDR files collected by the core network to suddenly decrease; if the core network performs a CDR temporary storage operation, this operation will cause the number of first CDR files collected by the core network to suddenly increase.

[0077] Step 502: The call detail record (CDR) file early warning device marks abnormal points where the number of the first CDR file exceeds or falls below the preset early warning range.

[0078] In one possible implementation, the call detail record (CDR) file early warning device marks the situation where the number of the first CDR files exceeds or falls below a preset threshold, and the marked point is the abnormal point of the first CDR file.

[0079] In one example, the preset warning threshold range for the call detail record (CDR) file early warning device at "12:00" is 100-1000. If the CDR file early warning device detects a real-time count of 2500 for the first CDR file at "12:00", then the count of the first CDR file at "12:00" is marked as an anomaly.

[0080] Step 503: The call detail record (CDR) file early warning device determines the abnormal information of the abnormal point based on the core network indicator information.

[0081] In one possible implementation, the call detail record (CDR) file early warning device predicts a second trend in the number of first CDR files based on core network indicator information. The CDR file early warning device compares the anomalies in the first CDR files with the second trend to determine the anomaly information of the anomalies.

[0082] In one example, if an anomaly in the first call detail record (CDR) file matches a second trend, the CDR file early warning device marks the anomaly information as a change in the number of the first CDR files caused by core network operations. If the anomaly in the first CDR file does not match the second trend, the CDR file early warning device determines that the number of the first CDR files is abnormal, and uses the number of the first CDR files at the anomaly point, as well as information on any sudden increase or decrease in the number of first CDR files, as the anomaly information for that point.

[0083] Furthermore, the call detail record (CDR) file early warning device generates CDR early warning information based on the abnormal information at the anomaly points and notifies the relevant maintenance personnel.

[0084] The above solution offers at least the following benefits: The call detail record (CDR) file early warning device acquires core network indicator information. Based on this information, the CDR file early warning device compares the anomalies in the first CDR file with the core network indicator information to determine the anomalies. In this way, by marking the anomalies in the CDR files and comparing them with core network indicator information, the CDR file early warning device can pinpoint the causes of some CDR anomalies, improving the accuracy of anomaly location and the efficiency of subsequent CDR anomaly processing.

[0085] Combination Figure 3 ,like Figure 6 As shown, before the call detail record (CDR) file early warning device obtains the first CDR file information, step 601 above also includes the following steps 601-604:

[0086] Step 601: The call detail record (CDR) file early warning device acquires the second CDR file;

[0087] In one possible implementation, the call detail record (CDR) file early warning device obtains all CDR-related files of mobile users in a designated directory of the core network through the core network billing gateway.

[0088] In one example, the call detail record (CDR) file early warning device sends an instruction to the billing gateway via the core network to retrieve the CDR file. The billing gateway then stores the second CDR file in a designated directory within the core network. The CDR file early warning device then retrieves the second CDR file from the designated directory within the core network.

[0089] It should be noted that the aforementioned billing gateway is located between the core network and the billing system, and is responsible for call detail record (CDR) recording, conversion, and billing message adaptation.

[0090] Step 602: The call detail record (CDR) file early warning device divides the second CDR file into multiple sub-CDR files.

[0091] In one possible implementation, the call detail record (CDR) file early warning device performs call splitting processing on the acquired second CDR file. The CDR file early warning device acquires multiple sub-CDR files through the call splitting operation.

[0092] In one example, the call detail record (CDR) file early warning device performs call splitting processing on the second CDR file through the billing gateway CDF module.

[0093] Step 603: The call detail record (CDR) file early warning device combines multiple sub-CDR files in a preset order to generate the first CDR file.

[0094] In one possible implementation, the call detail record (CDR) file early warning device combines multiple sub-CDR files according to time sequence to generate a complete first CDR file.

[0095] Step 604: The call detail record (CDR) file early warning device determines the first call detail record information in the first CDR file based on the first CDR file.

[0096] In one possible implementation, the call detail record (CDR) file early warning device obtains relevant parameters and other information from the first CDR file. Further, based on the obtained relevant parameter information, the CDR file early warning device generates the first CDR file information.

[0097] In one example, the relevant parameter information of the first call detail record (CDR) file includes, but is not limited to, user registration information, CDR duration information, CDR quantity information, CDR file size, and CDR file service type.

[0098] The above scheme brings at least the following beneficial effects: The call detail record (CDR) file early warning device acquires the second CDR file. The CDR file early warning device divides the second CDR file into multiple sub-CDR files and combines the sub-CDR files according to a preset order to generate the first CDR file. The CDR file early warning device determines the first CDR information in the first CDR file based on the first CDR file. In this way, the CDR file early warning device, by segmenting CDR files and combining them according to a preset order, facilitates accurate extraction and analysis of relevant information from the CDR files, improving the accuracy of CDR file monitoring.

[0099] The above provides a detailed description of the call detail record (CDR) file early warning device and the functions of each device involved in the embodiments of this application, as well as the interactions between the devices.

[0100] As can be seen, the above mainly describes the technical solutions provided by the embodiments of this application from a methodological perspective. To achieve the above functions, it includes corresponding hardware structures and / or software modules for executing each function. Those skilled in the art should readily recognize that, in conjunction with the modules and algorithm steps of the various examples described in the embodiments disclosed herein, the embodiments of this application can be implemented in hardware or a combination of hardware and computer software. Whether a function is executed in hardware or by computer software driving hardware depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this application.

[0101] This application embodiment can divide the functional modules according to the above-described example dialog single-file early warning device. For example, each function can be divided into its own functional module, or two or more functions can be integrated into one processing module. The integrated module can be implemented in hardware or as a software functional module. Optionally, the module division in this application embodiment is illustrative and only represents one logical functional division; other division methods may be used in actual implementation.

[0102] This application provides a call detail record (CDR) file early warning device for executing the method required by any device in the aforementioned CDR file early warning system. This CDR file early warning device may be the CDR file early warning device described in this application, or a module within a CDR file early warning device; it may also be a chip within a CDR file early warning device, or other devices used to execute the CDR file early warning method; this application does not limit the specific device used.

[0103] like Figure 7 The diagram shown is a structural schematic of a call detail record (CDR) file early warning device provided in an embodiment of this application. The CDR file early warning device includes a processing unit 701 and a communication unit 702.

[0104] Processing unit 701 is used to acquire first call detail record (CDR) file information; the first CDR file information includes at least one of the following: the number of first CDR files and the size of the first CDR files; processing unit 701 is also used to determine, based on the first CDR file information, the warning threshold range and the preset number of detections for the first CDR file within multiple preset time periods; processing unit 701 is also used to determine whether the number of first CDR files exceeds or falls below the warning threshold range within the preset number of detections; processing unit 701 is also used to determine, if so, the abnormal indicator information of the first CDR file; processing unit 701 is also used to generate CDR warning information based on the abnormal indicator information.

[0105] Optionally, the processing unit 701 is specifically used to: determine a first trend in the number of first call detail records (CDRs); determine a range of warning thresholds for the first CDRs within multiple preset time periods based on the first trend; and determine a preset number of detections for the first CDRs within multiple preset time periods based on the number of CDRs and the size of the first CDRs.

[0106] Optionally, the processing unit 701 is also specifically used for: acquiring core network indicator information; marking abnormal points where the number of first call single files exceeds or falls below the preset warning range; and determining the abnormal information of the abnormal points based on the core network indicator information.

[0107] Optionally, the processing unit 701 is further specifically used to: determine the second trend of change in the number of first call detail records (CDRs) based on the core network indicator information; if the number of first CDRs at the anomaly point matches the second trend, then the core network indicator information is determined to be anomaly information; if the number of first CDRs at the anomaly point does not match the second trend, then the target information at the anomaly point is determined to be anomaly information; the target information includes at least one of the following: the number of first CDRs at the anomaly point, and the trend information of change in the number of first CDRs at the anomaly point.

[0108] Optionally, the processing unit 701 is further configured to: acquire a second call detail record (CDR) file; divide the second CDR file into multiple sub-CDR files; combine the multiple sub-CDR files in a preset order to generate a first CDR file; and determine the first CDR information of the first CDR file based on the first CDR file.

[0109] This application provides a call detail record (CDR) file early warning device for executing the method required by any device in the aforementioned CDR file early warning system. This CDR file early warning device may be the CDR file early warning device described in this application, or a module within a CDR file early warning device; it may also be a chip within a CDR file early warning device, or other devices used to execute the CDR file early warning method; this application does not limit the specific device used.

[0110] This application also provides a computer-readable storage medium storing instructions. When a computer executes these instructions, the computer performs each step of the method flow shown in the above-described method embodiments.

[0111] Embodiments of this application provide a computer program product containing instructions that, when executed on a computer, cause the computer to perform the call detail record (CDR) file warning method described in the above method embodiments.

[0112] Embodiments of this application provide a chip, which includes a processor and a communication interface. The communication interface and the processor are coupled. The processor is used to run computer programs or instructions to implement the call detail record (CDR) file early warning method as described in the above method embodiments.

[0113] The computer-readable storage medium may be, for example, but not limited to, an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any combination thereof. More specific examples of computer-readable storage media (a non-exhaustive list) include: an electrical connection having one or more wires, a portable computer disk, a hard disk, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM), registers, hard disks, optical fibers, compact disc read-only memory (CD-ROM), optical storage devices, magnetic storage devices, or any suitable combination of the foregoing, or any other form of computer-readable storage medium in the art. An exemplary storage medium is coupled to a processor, enabling the processor to read information from and write information to the storage medium. Of course, the storage medium may also be a component of the processor. The processor and the storage medium may reside in an application-specific integrated circuit (ASIC). In the embodiments of this application, the computer-readable storage medium can be any tangible medium that contains or stores a program that can be used by or in conjunction with an instruction execution system, apparatus, or device.

[0114] Since the apparatus, device, computer-readable storage medium, and computer program product in the embodiments of this application can be applied to the above methods, the technical effects that can be obtained can also be referred to the above method embodiments. The embodiments of this application will not be repeated here.

[0115] The above description is merely a specific embodiment of this application, but the scope of protection of this application is not limited thereto. Any changes or substitutions within the technical scope disclosed in this application should be included within the scope of protection of this application. Therefore, the scope of protection of this application should be determined by the scope of the claims.

Claims

1. A method for early warning of call detail records (CDRs), characterized in that, The method includes: Obtain information about the first call detail record (CDR) file; the information about the first CDR file includes at least one of the following: the number of first CDR files and the size of the first CDR file; Determine the first trend of change in the number of first call detail records (CDRs); based on the first trend of change, determine the warning threshold range of the first CDRs within multiple preset time periods; based on the number of the first CDRs and the size of the first CDRs, determine the preset number of times to detect the first CDRs within the multiple preset time periods. Determine whether, within the preset number of detections, the number of the first call detail record (CDR) files exceeds or falls below the warning threshold range; If it exists, obtain the core network indicator information; mark the abnormal points where the number of the first call detail record (CDR) files exceeds or falls below the warning threshold range; determine the second trend of change in the number of the first CDR files based on the core network indicator information; if the number of the first CDR files at the abnormal point matches the second trend of change, then determine the core network indicator information as abnormal indicator information. If the number of the first call detail records (CDRs) at the anomaly point does not match the second trend, then the target information of the anomaly point is determined to be the anomaly indicator information; the target information includes at least one of the following: the number of the first CDRs at the anomaly point, and the trend information of the number of the first CDRs at the anomaly point. Based on the abnormal indicator information, a call detail record (CDR) warning is generated.

2. The method according to claim 1, characterized in that, Before obtaining the first call detail record file information, the process also includes: Obtain the second episode file; The second call detail record (CDR) file is divided into multiple sub-CDR files; The multiple sub-call detail records (CDRs) are combined in a preset order to generate the first CDR file; Based on the first call detail record (CDR) file, determine the first CDR information in the first CDR file.

3. A call detail record (CDR) file early warning device, characterized in that, The device includes: a processing unit; The processing unit is used to: acquire first call detail record (CDR) file information; the first CDR file information includes at least one of the following: the number of first CDR files, the size of the first CDR file; Determine the first trend of change in the number of first call detail records (CDRs); based on the first trend of change, determine the warning threshold range of the first CDRs within multiple preset time periods; based on the number of the first CDRs and the size of the first CDRs, determine the preset number of times to detect the first CDRs within the multiple preset time periods. Determine whether, within the preset number of detections, the number of the first call detail record (CDR) files exceeds or falls below the warning threshold range; If it exists, obtain the core network indicator information; mark the abnormal points where the number of the first call detail record (CDR) files exceeds or falls below the warning threshold range; determine the second trend of change in the number of the first CDR files based on the core network indicator information; if the number of the first CDR files at the abnormal point matches the second trend, determine the core network indicator information as abnormal indicator information; if the number of the first CDR files at the abnormal point does not match the second trend, determine the target information of the abnormal point as the abnormal indicator information; the target information includes at least one of the following: the number of the first CDR files at the abnormal point, and the trend information of the number of the first CDR files at the abnormal point. Based on the abnormal indicator information, a call detail record (CDR) warning is generated.

4. The apparatus according to claim 3, characterized in that, The processing unit is further configured to: Obtain the second episode file; The second call detail record (CDR) file is divided into multiple sub-CDR files; The multiple sub-call detail records (CDRs) are combined in a preset order to generate the first CDR file; Based on the first call detail record (CDR) file, determine the first CDR information in the first CDR file.

5. A call detail record (CDR) file early warning device, characterized in that, include: A processor and a communication interface; the communication interface is coupled to the processor, the processor being used to run computer programs or instructions to implement the call detail record (CDR) file early warning method as described in any one of claims 1-2.

6. A computer-readable storage medium storing instructions, characterized in that, When the computer executes the instruction, the computer performs the call detail record (CDR) file early warning method as described in any one of claims 1-2.

Images