Phone bill file auditing method and device and storage medium

Abstract

The invention provides a ticket file auditing method and device and a storage medium, and is applied to the field of Internet. The method comprises the following steps: acquiring a ticket file at a network element end, and determining an original auditing record based on the ticket file; obtaining a ticket file processed by the ticket processing end, and determining a target auditing record corresponding to the ticket file; and comparing the original auditing record with the target auditing record based on a first preset mode, and determining an auditing result. According to the method, the technical effect of improving the call ticket file processing service accuracy is achieved.

Description

Technical Field

[0001] This application relates to the field of the Internet, and in particular, to a method, device, and storage medium for auditing call detail record files. Background Art

[0002] With the development of Internet technology, call detail record files are one of the important files used by operators for data processing. Processing call detail record files is the basis of business analysis. In order to ensure the accuracy of call detail record file processing, it is necessary to audit call detail record files.

[0003] In the existing call detail record file auditing method, mainly the call detail record files generated by network elements are stored in a fixed directory; the call detail record files in the fixed directory of the network elements are collected, sorted, preprocessed, and labeled by a call processing system, and then distributed to multiple downstream systems; in the call processing system, the call detail record files are audited to determine the accuracy of the call detail record files obtained by the system.

[0004] In the prior art, since the method of auditing call detail record files through a call processing system lacks a file auditing method from the network element to after the call detail record file processing is completed, it is impossible to determine the problems existing in the call detail record processing process, thus affecting the accuracy of the call detail record file processing service; therefore, in the existing call detail record file auditing technology, there is a technical problem of low accuracy of the call detail record file processing service. Summary of the Invention

[0005] This application provides a method, device, and storage medium for auditing call detail record files to solve the technical problem of low accuracy of the call detail record file processing service existing in the existing call detail record file auditing technology.

[0006] In a first aspect, this application provides a method for auditing call detail record files, including:

[0007] Obtain the call detail record files at the network element end, and determine the original audit records based on the call detail record files;

[0008] Obtain the call detail record files processed by the call processing end, and determine the target audit records corresponding to the call detail record files;

[0009] Compare the original audit records and the target audit records based on a first preset method, and determine the audit result.

[0010] Optionally, comparing the original audit records and the target audit records based on a first preset method, and determining the audit result includes:

[0011] Based on a first preset time interval, determine whether the original audit records and the target audit records meet the preset conditions. If so, determine the audit failure information, and determine the audit failure information as the audit result, and store the audit failure information in the database;

[0012] Otherwise, determine that the original audit record and the target audit record are consistent, determine the audit success information, delete the original audit record and the target audit record loaded in the cache, and determine the audit result.

[0013] Optionally, the preset conditions include any one of the following:

[0014] The target audit record and / or the original audit record times out, and the target audit record does not exist or the original audit record does not exist; and / or,

[0015] The target audit record is repeated, or the original audit record is repeated; and / or,

[0016] The size of the call record file in the target audit record is inconsistent with the size of the call record file in the original audit record; and / or,

[0017] The number of call record files in the target audit record is inconsistent with the number of call record files in the original audit record.

[0018] Optionally, comparing the original audit record and the target audit record based on the first preset method and determining the audit result further includes:

[0019] Based on the first preset time interval and the original audit record, determine the original encrypted ciphertext and / or the original binary information of the call record file before call record processing, and based on the target audit record, determine the target encrypted ciphertext and / or the target binary information of the call record file after call record processing;

[0020] Determine the audit success information when the original encrypted ciphertext is consistent with the target encrypted ciphertext, and / or, the original binary information is consistent with the target binary information, determine the audit failure information when the original encrypted ciphertext is inconsistent with the target encrypted ciphertext, and / or, the original binary information is inconsistent with the target binary information, store the audit failure information in the database, and determine the audit result.

[0021] Optionally, determining the original audit record based on the call record file includes:

[0022] Based on the call record file, determine the file information of the call record file, generate the original audit file based on the second preset time interval and the file information, and store the original audit file in the preset directory; and / or,

[0023] Load the file information into the preset cache topic; and / or,

[0024] Store the file information in the preset cache middleware for storage;

[0025] Obtain the original audit record corresponding to the call record file based on the second preset method.

[0026] Optionally, obtain the original audit record corresponding to the call record file based on a second preset method, including:

[0027] Read the original audit file based on a preset directory, and parse the original audit file to obtain the original audit record; and / or,

[0028] Parse and consume a preset cache topic to obtain the original audit record corresponding to the preset cache topic; and / or,

[0029] Read file information based on a preset cache middleware and determine the original audit record, and delete the file information in the preset cache middleware.

[0030] Optionally, determine the target audit record corresponding to the call record file, including:

[0031] Generate a corresponding target audit file based on the file information of the call record file, and parse the target audit file to determine the corresponding target audit record; and / or,

[0032] Store the file information corresponding to the call record file in a preset cache middleware, and obtain the target audit record corresponding to the call record file based on the preset cache middleware.

[0033] In a second aspect, the present application provides a call record file auditing device, including:

[0034] A first acquisition module, configured to acquire a call record file at the network element side, and determine an original audit record based on the call record file;

[0035] A second acquisition module, configured to acquire the call record file processed by the call record processing end, and determine the target audit record corresponding to the call record file;

[0036] A processing module, configured to compare the original audit record and the target audit record based on a first preset method, and determine an audit result.

[0037] Optionally, the device is further configured to:

[0038] Based on a first preset time interval, determine whether the original audit record and the target audit record meet a preset condition. If so, determine audit failure information, and determine the audit failure information as the audit result, and store the audit failure information in a database;

[0039] If not, determine that the original audit record and the target audit record are consistent, determine audit success information, delete the original audit record and the target audit record loaded in the cache, and determine the audit result.

[0040] Optionally, the preset condition includes any one of the following:

[0041] The target audit record and / or the original audit record times out, and the target audit record does not exist or the original audit record does not exist; and / or,

[0042] The target audit record is duplicated, or the original audit record is duplicated; and / or,

[0043] The size of the call record file in the target audit record is inconsistent with the size of the call record file in the original audit record; and / or,

[0044] The number of call record files in the target audit record is inconsistent with the number of call record files in the original audit record.

[0045] Optionally, the device is further configured to:

[0046] Based on a first preset time interval and the original audit record, determine the original encrypted ciphertext and / or original binary information of the call record file before call record processing, and based on the target audit record, determine the target encrypted ciphertext and / or target binary information of the call record file after call record processing;

[0047] Determine the audit success information when the original encrypted ciphertext is consistent with the target encrypted ciphertext, and / or, the original binary information is consistent with the target binary information, determine the audit failure information when the original encrypted ciphertext is inconsistent with the target encrypted ciphertext, and / or, the original binary information is inconsistent with the target binary information, store the audit failure information in a database, and determine the audit result.

[0048] Optionally, the device is further configured to:

[0049] Based on the call record file, determine the file information of the call record file, generate an original audit file based on a second preset time interval and the file information, and store the original audit file in a preset directory; and / or,

[0050] Load the file information into a preset cache topic; and / or,

[0051] Store the file information in a preset cache middleware for storage;

[0052] Obtain the original audit record corresponding to the call record file based on a second preset method.

[0053] Optionally, the device is further configured to:

[0054] Read the original audit file based on a preset directory, parse the original audit file, and obtain the original audit record; and / or,

[0055] Parse and consume a preset cache topic to obtain the original audit record corresponding to the preset cache topic; and / or,

[0056] Read file information based on a preset cache middleware, determine the original audit record, and delete the file information in the preset cache middleware.

[0057] Optionally, the device is further configured to:

[0058] Generate a corresponding target audit file based on the file information of the call record file, and parse the target audit file to determine the corresponding target audit record; and / or,

[0059] Store the file information corresponding to the call record file in the preset cache middleware, and obtain the target audit record corresponding to the call record file based on the preset cache middleware.

[0060] In a third aspect of the present application, there is provided a call record file auditing device, including:

[0061] A processor and a memory;

[0062] The memory stores computer-executable instructions;

[0063] The processor executes the computer-executable instructions stored in the memory, so that the call record file auditing device executes the call record file auditing method according to any one of the first aspect.

[0064] In a fourth aspect, the present application provides a computer-readable storage medium, in which computer-executable instructions are stored, and when the computer-executable instructions are executed by a processor, they are used to implement the call record file auditing method according to any one of the first aspect.

[0065] A call record file auditing method, device and storage medium provided by the present application. The method includes: obtaining a call record file at the network element side, and determining an original audit record based on the call record file; obtaining the call record file processed by the call record processing side, and determining a target audit record corresponding to the call record file; comparing the original audit record and the target audit record based on a first preset method, and determining an audit result. By obtaining the original audit record corresponding to the call record file generated by the network element side, the file information before the call record file is processed is determined; by obtaining the target audit record corresponding to the call record file processed by the call record processing side, the file information after the call record file is processed is determined; by comparing the original audit record and the target audit record, and combining the first preset method to determine the consistency between the original audit record and the target audit record, and determining the audit result; thereby determining the problems existing in the call record file during the call record processing process, and realizing the accurate positioning of the call record file auditing; thus, the technical effect of improving the accuracy of the call record file processing service is achieved. BRIEF DESCRIPTION OF THE DRAWINGS

[0066] The accompanying drawings herein are incorporated into the specification and form a part of the specification, showing embodiments consistent with the present application, and are used together with the specification to explain the principles of the present application.

[0067] Figure 1 The process flow of the call record file auditing method provided by the embodiments of this application Figure 1 ;

[0068] Figure 2 The process flow of the call record file auditing method provided by the embodiments of this application Figure 2 ;

[0069] Figure 3 The flowchart of the call record file auditing program applied to the call record file auditing method provided by the embodiments of this application;

[0070] Figure 4 The structural schematic diagram of the call record file auditing device provided by the embodiments of this application;

[0071] Figure 5 The hardware structure diagram of the call record file auditing device provided by the embodiments of this application.

[0072] Through the above-mentioned drawings, the clear embodiments of this application have been shown, and there will be more detailed descriptions hereinafter. These drawings and text descriptions are not intended to limit the scope of the concept of this application in any way, but to illustrate the concept of this application to those skilled in the art by referring to specific embodiments. Specific embodiments

[0073] Here, the exemplary embodiments will be described in detail, and the examples are shown in the drawings. When the following description involves the drawings, unless otherwise indicated, the same numbers in different drawings represent the same or similar elements. The embodiments described in the following exemplary embodiments do not represent all embodiments consistent with this application. On the contrary, they are only examples of devices and methods consistent with some aspects of this application as detailed in the appended claims.

[0074] First, the nouns involved in this application are explained:

[0075] Kafka: It is a fast, scalable, high-throughput, fault-tolerant distributed publish-subscribe messaging system; it can process a large amount of data in real time and meet the requirements of various application scenarios.

[0076] Secure File Transfer Protocol (SFTP): It refers to a protocol used to securely transfer files on a computer network. It encrypts and authenticates through the Secure Shell (SSH) protocol to ensure the confidentiality and integrity of file transfer.

[0077] In the existing call record file auditing method, the call record files generated by network elements are mainly stored in a fixed directory; the call record processing system is used to collect, sort, preprocess, and label the call record files under the fixed directory of the network elements, and distribute them to multiple downstream systems; in the call record processing system, the call record files will be audited to judge the accuracy of the call record files obtained by the system. In the prior art, since the method of auditing call record files through the call record processing system lacks the file auditing method from the network element to after the call record file processing is completed, the problems existing in the call record processing process cannot be determined, thus affecting the accuracy of the call record file processing service; therefore, in the existing call record file auditing technology, there is a technical problem of low accuracy of the call record file processing service.

[0078] A call record file auditing method, device, and storage medium provided by this application. The method includes: obtaining the call record file at the network element end, and determining the original audit record based on the call record file; obtaining the call record file processed by the call record processing end, and determining the target audit record corresponding to the call record file; comparing the original audit record and the target audit record based on a first preset method, and determining the audit result. By obtaining the original audit record corresponding to the call record file generated at the network element end, the file information before the call record file is processed is determined; by obtaining the target audit record corresponding to the call record file processed by the call record processing end, the file information after the call record file is processed is determined; by comparing the original audit record and the target audit record, and combining the first preset method to determine the consistency of the original audit record and the target audit record, and determining the audit result; thus, the problems existing in the call record file during the call record processing process are determined, and the accurate positioning of the call record file auditing is realized; thereby, the technical effect of improving the accuracy of the call record file processing service is achieved, and the technical problem of low accuracy of the call record file processing service existing in the prior art is solved.

[0079] The technical solution of this application and how the technical solution of this application solves the above technical problems will be described in detail below with specific embodiments. These specific embodiments below can be combined with each other, and the same or similar concepts or processes may not be repeated in some embodiments. The embodiments of this application will be described below with reference to the accompanying drawings.

[0080] Figure 1 The flow of the call record file auditing method provided by the embodiment of this application Figure 1 . As Figure 1 shown, the call record file auditing method provided by the embodiment of this application includes:

[0081] S101. Obtain the call record file at the network element end, and determine the original audit record based on the call record file;

[0082] In this embodiment, the call record file at the network element side is: in a telecommunication network, a communication record file generated by a network device, which records communication activities occurring on the network device; where the communication activities can be: calls, text messages, and data transmissions; and the call record file can be applied to the operations and billing services of a telecommunication operator.

[0083] S102. Obtain the call record file processed by the call record processing end, and determine the target audit record corresponding to the call record file.

[0084] In this embodiment, the processing of the call record file by the call record processing end includes: collecting the call record file, collecting the original call record file from a network device or a network element; parsing the call record file, parsing the original call record file into a data structure that can be read and processed; processing the call record file, processing and converting the parsed call record data to facilitate subsequent querying, analysis, and execution of billing operations; and distributing the processed call record data to a downstream system.

[0085] In this embodiment, the target audit record corresponding to the call record file after processing the call record includes: the call record file and the detailed information of the call record file.

[0086] S103. Compare the original audit record and the target audit record based on a first preset method, and determine the audit result.

[0087] In this embodiment, the original audit record stores the specific file information of the call record file at the network element side, and the target audit record stores the specific file information of the call record file after being processed by the call record processing end; by comparing the original audit record and the target audit record, judge the consistency of the specific file information of the call record file before and after processing, and record the inconsistent features, so as to determine the problems existing in the processing of the call record file.

[0088] In this embodiment, the first preset method can be: comparing the consistency of the call record files in the original audit record and the target audit record; it can be achieved by encoding the call record files before and after processing and comparing the consistency of the encodings; and / or, comparing the consistency of the comparison features corresponding to the call record files in the original audit record and the target audit record.

[0089] A call record file auditing method provided by this application. The method includes: obtaining a call record file at the network element side, and determining an original audit record based on the call record file; obtaining the call record file processed by the call record processing side, and determining a target audit record corresponding to the call record file; comparing the original audit record and the target audit record based on a first preset method, and determining an audit result. By obtaining the original audit record corresponding to the call record file generated at the network element side, the file information before the call record file is processed is determined; obtaining the target audit record corresponding to the call record file processed by the call record processing side, and determining the file information after the call record file is processed; by comparing the original audit record and the target audit record, combining the first preset method to determine the consistency between the original audit record and the target audit record, and determining the audit result; thereby determining the problems existing in the call record file during the call record processing process, realizing the accurate positioning of the call record file auditing; thus, the technical effect of improving the accuracy of the call record file processing service is achieved, and the technical problem of low accuracy of the call record file processing service existing in the prior art is solved.

[0090] Figure 2 The flow of the call record file auditing method provided by the embodiments of this application Figure 2 As Figure 2 shown, the call record file auditing method provided by the embodiments of this application includes:

[0091] S201. Obtain the call record file at the network element side, determine the file information of the call record file based on the call record file, generate an original audit file based on a second preset time interval and the file information, and store the original audit file in a preset directory; and / or, load the file information into a preset cache topic; and / or, store the file information in a preset cache middleware for storage;

[0092] In this embodiment, the preset cache topic may be: a preset cache topic created based on Kafka; the original audit record corresponding to the call record file can be obtained by consuming the preset cache topic; the preset cache middleware is a software system used to improve the data access speed between data sources; the type of the preset cache middleware may be: in-memory cache middleware, distributed cache middleware, content delivery network cache middleware, and server cache middleware.

[0093] S202. Read the original audit file based on the preset directory, parse the original audit file, and obtain the original audit record; and / or, parse and consume the preset cache topic to obtain the original audit record corresponding to the preset cache topic; and / or, read the file information based on the preset cache middleware and determine the original audit record, and delete the file information in the preset cache middleware.

[0094] In this embodiment, the original audit files stored in a preset directory can be obtained through the SFTP protocol; in the first exemplary case: create a preset cache topic through the command-line tool or interface provided by Kafka, and set the attributes of the preset cache topic according to the required configuration; create a consumer instance, and specify that the topic to be consumed by the consumer instance is the preset cache topic; use the consumer instance to subscribe to the preset cache topic; obtain the information in the preset cache topic through a loop or message reception, and parse the preset cache topic to obtain the original audit records corresponding to the call record files.

[0095] In this embodiment, to obtain the information of the preset cache middleware, it is necessary to use the preset cache middleware based on the interface or command line provided by the preset cache middleware, and obtain the information stored in the preset cache middleware, so as to obtain the original audit records corresponding to the call record files.

[0096] S203. Obtain the call record file processed by the call record processing end, generate a corresponding target audit file based on the file information of the call record file, and parse the target audit file to determine the corresponding target audit record; and / or, store the file information corresponding to the call record file in the preset cache middleware, and obtain the target audit record corresponding to the call record file based on the preset cache middleware.

[0097] In this embodiment, the target audit file can be stored in a database. By loading the target audit file in the database and parsing it to obtain the target audit record; or the file information corresponding to the processed call record file can be stored in the preset cache middleware, and the corresponding information can be obtained through the interface or command line provided by the preset cache middleware, and the target audit record corresponding to the processed call record file can be determined.

[0098] S204. Based on the first preset time interval, determine whether the original audit record and the target audit record meet the preset conditions. If so, determine the audit failure information, and determine the audit failure information as the audit result, and store the audit failure information in the database.

[0099] Among them, the preset conditions include any one of the following:

[0100] The target audit record and / or the original audit record times out, and the target audit record does not exist or the original audit record does not exist; and / or,

[0101] The target audit record is repeated, or the original audit record is repeated; and / or,

[0102] The size of the call record file in the target audit record is inconsistent with the size of the call record file in the original audit record; and / or,

[0103] The number of call record files in the target audit record is inconsistent with the number of call record files in the original audit record.

[0104] In this embodiment, if the target audit record is repeated or the original audit record is repeated, it means that both the target audit record and the original audit record are determined based on the network element side or both are determined based on the call record processing side.

[0105] In the second exemplary example, if the number of call record files in the original audit record and the target audit record is inconsistent, then determine the inconsistency of the number of call record files as the audit failure information and store it in the database. The problems during the processing of the call record files can be determined by querying the records in the database.

[0106] S205: If not, then determine that the original audit record and the target audit record are consistent, determine the audit success information, delete the original audit record and the target audit record loaded in the cache, and determine the audit result;

[0107] S206: Based on the first preset time interval and the original audit record, determine the original encrypted ciphertext and / or the original binary information of the call record file before call record processing. Based on the target audit record, determine the target encrypted ciphertext and / or the target binary information of the call record file after call record processing;

[0108] In this embodiment, the ways to encrypt the call record file can be: symmetric encryption, asymmetric encryption, hash function encryption, and hybrid encryption; encrypt the call record file and form it into a unique ciphertext; judge the consistency of the call record file before and after processing by comparing the consistency of the original encrypted ciphertext and the target encrypted ciphertext.

[0109] S207: Determine the audit success information when the original encrypted ciphertext is consistent with the target encrypted ciphertext and / or the original binary information is consistent with the target binary information. Determine the audit failure information when the original encrypted ciphertext is inconsistent with the target encrypted ciphertext and / or the original binary information is inconsistent with the target binary information. Store the audit failure information in the database and determine the audit result.

[0110] In this embodiment, the binary information corresponding to the call record file can be obtained through a hash function, or the call record file can be directly converted into a binary form; thus, the comparison between the original binary information and the target binary information is realized.

[0111] By executing S201 to S207, the audit and investigation of the call record file processing process are realized by comparing the information before and after the call record file processing, thereby ensuring the accuracy in the business processing process of the call record file and achieving the technical effect of improving the accuracy of the call record file processing service.

[0112] Figure 3 It is the flowchart of the call record file audit program provided by the embodiment of the present application applied to the call record file audit method. AsFigure 3 As shown in Figure 3 , the call record file auditing program provided by the embodiment of the present application is applied to the call record file auditing method, including: obtaining the original audit record corresponding to the call record file at the network element end based on the SFTP protocol, obtaining the target audit corresponding to the call record file at the call processing end; comparing to determine the corresponding audit result, and storing the audit result in the MYSQL database. Specifically: loading the configuration for connecting the network element end and the call processing end, and connecting to the MYSQL database, Kafka system, and network element; loading the parameter configuration for data acquisition in this embodiment; starting the log metric timer, and periodically outputting log metrics for recording the log information of the program operation; starting the audit cleaning thread, and periodically cleaning the expired audit files and the corresponding databases. Loading the historical audit records from MYSQL for backing up the unprocessed historical audit records. Starting the network element file acquisition thread for obtaining the files in the network element; starting the audit result output process for implementing the output of the audit result and storing the audit result in the MYSQL database for recording; starting the network element audit file collection process for obtaining the original audit files corresponding to the call record files in the network element, periodically processing the collected files to determine the corresponding original audit records, and loading them into the memory; starting the Kafka topic collection process, and obtaining the corresponding target audit records from the preset cache topic and loading them into the memory; comparing the original audit records and the target audit records, and outputting the audit result; stopping the threads and the corresponding processes after completion. Among them, the network element file acquisition thread, the audit result output process, the network element audit file collection process, and the Kafka topic collection process are executed in parallel; the deployment of the audit program can use container deployment, and multiple instances are enabled according to the business volume, and different computing power resources are allocated to different instances.

[0113] A call record file auditing method provided by this application. The method includes: obtaining a call record file at the network element side and determining an original audit record based on the call record file; obtaining the call record file processed by the call record processing side and determining a target audit record corresponding to the call record file; comparing the original audit record and the target audit record based on a first preset method and determining an audit result. By obtaining the call record file generated at the network element side and saving the file information of the call record file when it is at the network element side, it is determined as the original audit record; the original audit record stores the file information of the call record file before being processed; after the call record file is processed by the platform or system on the call record processing side, the file information corresponding to the call record file will be determined as the target audit record; by comparing the original audit record and the target audit record, the problems generated during the processing of the call record file are determined, and the auditing of the call record file processing process is realized. Compared with the prior art, this application determines whether there are differences and specific difference items between the original audit record and the target audit record by comparing the detailed information before and after the processing of the call record file, through methods such as file encryption, file encoding, and file feature comparison; thereby auditing the processing process of the call record file, ensuring the accuracy of the call record file during various data processing; achieving the technical effect of improving the accuracy of the call record file processing service, and solving the technical problem of low accuracy of the call record file processing service existing in the prior art.

[0114] Figure 4 It is a schematic structural diagram of a call record file auditing device provided by an embodiment of this application. The device in this embodiment can be in the form of software and / or hardware. As Figure 4 shown, a call record file auditing device 400 provided by an embodiment of this application includes: a first acquisition module 401, a second acquisition module 402, and a processing module 403.

[0115] The first acquisition module 401 is used to obtain a call record file at the network element side and determine an original audit record based on the call record file.

[0116] The second acquisition module 402 is used to obtain the call record file processed by the call record processing side and determine a target audit record corresponding to the call record file.

[0117] The processing module 403 is used to compare the original audit record and the target audit record based on a first preset method and determine an audit result.

[0118] In a possible implementation manner, the device is further used for:

[0119] Based on a first preset time interval, determine whether the original audit record and the target audit record meet the preset conditions. If so, determine audit failure information, determine the audit failure information as the audit result, and store the audit failure information in the database.

[0120] Otherwise, it is determined that the original audit record is consistent with the target audit record, the audit success information is determined, the original audit record and the target audit record loaded in the cache are deleted, and the audit result is determined.

[0121] In a possible implementation, the preset conditions include any one of the following:

[0122] The target audit record and / or the original audit record times out, and the target audit record does not exist or the original audit record does not exist; and / or,

[0123] The target audit record is repeated, or the original audit record is repeated; and / or,

[0124] The size of the call record file in the target audit record is inconsistent with the size of the call record file in the original audit record; and / or,

[0125] The number of call record files in the target audit record is inconsistent with the number of call record files in the original audit record.

[0126] In a possible implementation, the device is further configured to:

[0127] Based on the first preset time interval and the original audit record, determine the original encrypted ciphertext and / or the original binary information of the call record file before call record processing, and based on the target audit record, determine the target encrypted ciphertext and / or the target binary information of the call record file after call record processing;

[0128] When the original encrypted ciphertext is consistent with the target encrypted ciphertext, and / or, the original binary information is consistent with the target binary information, determine the audit success information. When the original encrypted ciphertext is inconsistent with the target encrypted ciphertext, and / or, the original binary information is inconsistent with the target binary information, determine the audit failure information, store the audit failure information in the database, and determine the audit result.

[0129] In a possible implementation, the device is further configured to:

[0130] Based on the call record file, determine the file information of the call record file, generate an original audit file based on the second preset time interval and the file information, and store the original audit file in a preset directory; and / or,

[0131] Load the file information into a preset cache topic; and / or,

[0132] Store the file information in a preset cache middleware for storage;

[0133] Obtain the original audit record corresponding to the call record file based on the second preset method.

[0134] In a possible implementation, the device is further configured to:

[0135] Read the original audit file based on a preset directory, parse the original audit file, and obtain the original audit records; and / or,

[0136] Parse and consume a preset cache topic to obtain the original audit records corresponding to the preset cache topic; and / or,

[0137] Read file information based on a preset cache middleware, determine the original audit records, and delete the file information in the preset cache middleware.

[0138] In a possible implementation, the device is further configured to:

[0139] Generate a corresponding target audit file based on the file information of the call record file, and parse the target audit file to determine the corresponding target audit records; and / or,

[0140] Store the file information corresponding to the call record file in a preset cache middleware, and obtain the target audit records corresponding to the call record file based on the preset cache middleware.

[0141] A call record file auditing device provided by the present application. The device includes: a first acquisition module, configured to acquire the call record file at the network element side, and determine the original audit records based on the call record file; a second acquisition module, configured to acquire the call record file processed by the call record processing side, and determine the target audit records corresponding to the call record file; a processing module, configured to compare the original audit records and the target audit records based on a first preset method, and determine the audit result. By acquiring the call record file generated at the network element side, and saving the file information of the call record file when it is at the network element side, it is determined as the original audit records; the original audit records store the file information of the call record file before being processed; after the call record file is processed by the platform or system on the call record file processing side, the file information corresponding to the call record file will be determined as the target audit records; by comparing the original audit records and the target audit records, the problems generated during the processing of the call record file are determined, and the auditing of the call record file processing process is realized. Compared with the prior art, the present application determines whether there are differences and specific difference items between the original audit records and the target audit records by comparing the detailed information before and after the processing of the call record file, through methods such as file encryption, file encoding, and file feature comparison; thereby auditing the processing process of the call record file, ensuring the accuracy of the call record file during various data processing; achieving the technical effect of improving the accuracy of the call record file processing service, and solving the technical problem of low accuracy of the call record file processing service existing in the prior art.

[0142] Figure 5 This is the hardware structure diagram of the call record file auditing device provided by the embodiments of the present application. As Figure 5 shown, the call record file auditing device 500 includes:

[0143] A processor 501 and a memory 502;

[0144] The memory stores computer-executable instructions;

[0145] The processor executes the computer-executable instructions stored in the memory 502, causing the call record file auditing device to execute the call record file auditing method as described above.

[0146] It should be understood that the above-mentioned processor 501 may be a central processing unit (English: Central Processing Unit, abbreviated: CPU), or may also be other general-purpose processors, digital signal processors (English: Digital Signal Processor, abbreviated: DSP), application-specific integrated circuits (English: Application Specific Integrated Circuit, abbreviated: ASIC), etc. The general-purpose processor may be a microprocessor or the processor may also be any conventional processor, etc. The steps of the method disclosed in combination with the invention can be directly embodied as being executed and completed by a hardware processor, or can be executed and completed by a combination of hardware and software modules in the processor. The memory 502 may include high-speed random access memory (English: Random Access Memory, abbreviated: RAM), and may also include non-volatile memory (English: Non-volatile memory, abbreviated: NVM), such as at least one disk memory, and may also be a USB flash drive, a portable hard drive, a read-only memory, a magnetic disk or an optical disc, etc.

[0147] The embodiment of the present application correspondingly further provides a computer-readable storage medium, in which computer-executable instructions are stored, and when the computer-executable instructions are executed by a processor, they are used to implement the call record file auditing method.

[0148] It should be noted that for the foregoing method embodiments, for the sake of simple description, they are all expressed as a series of action combinations. However, those skilled in the art should know that the present application is not limited by the described action sequence, because according to the present application, certain steps can be performed in other sequences or simultaneously. Secondly, those skilled in the art should also know that the embodiments described in the specification are all optional embodiments, and the actions and modules involved are not necessarily essential to the present application.

[0149] It should be further noted that although the steps in the flowchart are shown sequentially according to the arrows, these steps are not necessarily executed in the order indicated by the arrows. Unless there is a clear indication in this document, there is no strict order restriction for the execution of these steps, and these steps can be executed in other orders. Moreover, at least a part of the steps in the flowchart may include multiple sub-steps or multiple stages. These sub-steps or stages are not necessarily executed at the same time, but can be executed at different times. The execution order of these sub-steps or stages is not necessarily sequential either, but can be executed alternately or in turns with at least a part of other steps or sub-steps or stages of other steps.

[0150] It should be understood that the above device embodiments are illustrative only, and the devices of the present application can also be implemented in other ways. For example, the division of units / modules in the above embodiments is only a logical function division, and there can be other division methods in actual implementation. For example, multiple units, modules or components can be combined, or can be integrated into another system, or some features can be ignored or not executed.

[0151] In addition, without special instructions, in each embodiment of the present application, each functional unit / module can be integrated in one unit / module, or each unit / module can exist physically alone, or two or more units / modules can be integrated together. The above integrated unit / module can be implemented in the form of hardware or in the form of a software program module.

[0152] When the integrated unit / module is implemented in the form of hardware, the hardware can be a digital circuit, an analog circuit, etc. The physical implementation of the hardware structure includes but is not limited to transistors, memristors, etc. Without special instructions, the processor can be any suitable hardware processor, such as CPU, GPU, FPGA, DSP, and ASIC, etc. Without special instructions, the storage unit can be any suitable magnetic storage medium or magneto-optical storage medium, such as resistive random access memory RRAM (Resistive Random Access Memory), dynamic random access memory DRAM (Dynamic Random Access Memory), static random access memory SRAM (Static Random-Access Memory), enhanced dynamic random access memory EDRAM (Enhanced Dynamic Random Access Memory), high-bandwidth memory HBM (High-Bandwidth Memory), hybrid memory cube HMC (Hybrid Memory Cube), etc.

[0153] When the integrated unit / module is implemented in the form of a software program module and sold or used as an independent product, it can be stored in a computer-readable memory. Based on this understanding, the technical solution of the present application, in essence, or the part that contributes to the prior art, or all or part of this technical solution, can be embodied in the form of a software product. This computer software product is stored in a memory and includes several instructions to enable a computer device (which can be a personal computer, a server, or a network device, etc.) to execute all or part of the steps of the methods of the various embodiments of the present application. The aforementioned memory includes: various media such as USB flash drives, read-only memories (ROM, Read-Only Memory), random access memories (RAM, Random Access Memory), mobile hard disks, magnetic disks, or optical discs that can store program codes.

[0154] In the above embodiments, the descriptions of the various embodiments each have their own focuses. For the parts not detailed in a certain embodiment, reference can be made to the relevant descriptions of other embodiments. The technical features of the above embodiments can be combined arbitrarily. For the sake of brevity of description, not all possible combinations of the technical features in the above embodiments are described. However, as long as there is no contradiction in the combination of these technical features, it should be considered as within the scope described in this specification.

[0155] Those skilled in the art will readily think of other embodiments of the present application after considering the specification and practicing the invention disclosed herein. The present application is intended to cover any variations, uses, or adaptations of the present application, which follow the general principles of the present application and include common general knowledge or conventional technical means in the technical field not disclosed in the present application. The specification and the embodiments are only regarded as exemplary, and the true scope and spirit of the present application are pointed out by the following claims.

[0156] It should be understood that the present application is not limited to the exact structure already described and shown in the drawings, and various modifications and changes can be made without departing from its scope. The scope of the present application is only limited by the appended claims.

Claims

1. A method for auditing call record files, characterized in that, it includes: Obtain the call record file at the network element side, and determine the original audit record based on the call record file; Obtain the call record file processed by the call record processing side, and determine the target audit record corresponding to the call record file; Compare the original audit record and the target audit record based on a first preset method, and determine the audit result.

2. The method according to claim 1, characterized in that, The comparing the original audit record and the target audit record based on a first preset method and determining the audit result includes: Based on a first preset time interval, determine whether the original audit record and the target audit record meet the preset conditions. If so, determine the audit failure information, and determine the audit failure information as the audit result, and store the audit failure information in the database; If not, determine that the original audit record and the target audit record are consistent, determine the audit success information, delete the original audit record and the target audit record loaded in the cache, and determine the audit result.

3. The method according to claim 2, characterized in that, The preset conditions include any one of the following: The target audit record and / or the original audit record times out, and the target audit record does not exist or the original audit record does not exist; and / or, The target audit record is repeated, or the original audit record is repeated; and / or, The size of the call record file in the target audit record is inconsistent with the size of the call record file in the original audit record; and / or, The number of call record files in the target audit record is inconsistent with the number of call record files in the original audit record.

4. The method according to claim 2, characterized in that, The comparing the original audit record and the target audit record based on a first preset method and determining the audit result further includes: Based on the first preset time interval and the original audit record, determine the original encrypted ciphertext and / or original binary information of the call record file before call record processing, and based on the target audit record, determine the target encrypted ciphertext and / or target binary information of the call record file after call record processing; Determine the audit success information when the original encrypted ciphertext and the target encrypted ciphertext are consistent, and / or, the original binary information and the target binary information are consistent. Determine the audit failure information when the original encrypted ciphertext and the target encrypted ciphertext are inconsistent, and / or, the original binary information and the target binary information are inconsistent. Store the audit failure information in the database, and determine the audit result.

5. The method according to claim 1, characterized in that, The determining the original audit record based on the call record file includes: Based on the call record file, determine the file information of the call record file, generate the original audit file based on a second preset time interval and the file information, and store the original audit file in a preset directory; and / or, Load the file information into a preset cache topic; and / or, Store the file information in a preset cache middleware for storage; Obtain the original audit record corresponding to the call record file based on a second preset method.

6. The method according to claim 5, wherein, the obtaining the original audit record corresponding to the call record file based on a second preset method includes: Reading the original audit file based on a preset directory, parsing the original audit file, and obtaining the original audit record; and / or, Parsing and consuming the preset cache topic to obtain the original audit record corresponding to the preset cache topic; and / or, Reading the file information based on the preset cache middleware, determining the original audit record, and deleting the file information in the preset cache middleware.

7. The method according to claim 1, wherein, the determining the target audit record corresponding to the call record file includes: Generating a corresponding target audit file based on the file information of the call record file, and parsing the target audit file to determine the corresponding target audit record; and / or, Storing the file information corresponding to the call record file in a preset cache middleware, and obtaining the target audit record corresponding to the call record file based on the preset cache middleware.

8. A call record file auditing device, wherein, it includes: A first obtaining module, configured to obtain a call record file at the network element side and determine an original audit record based on the call record file; A second obtaining module, configured to obtain the call record file processed by the call record processing end and determine a target audit record corresponding to the call record file; A processing module, configured to compare the original audit record and the target audit record based on a first preset method and determine an audit result.

9. A call record file auditing device, wherein, it includes: A processor and a memory communicatively connected to the processor; The memory stores computer execution instructions; The processor executes the computer execution instructions stored in the memory to implement the call record file auditing method according to any one of claims 1 to 7.

10. A computer-readable storage medium, wherein, the computer-readable storage medium stores computer execution instructions, and when the computer execution instructions are executed by a processor, they are used to implement the call record file auditing method according to any one of claims 1 to 7.

Images