CN110659247A - Method, device, equipment and medium for detecting continuity of call ticket file - Google Patents
Method, device, equipment and medium for detecting continuity of call ticket file Download PDFInfo
- Publication number
- CN110659247A CN110659247A CN201810608935.6A CN201810608935A CN110659247A CN 110659247 A CN110659247 A CN 110659247A CN 201810608935 A CN201810608935 A CN 201810608935A CN 110659247 A CN110659247 A CN 110659247A
- Authority
- CN
- China
- Prior art keywords
- file
- call ticket
- sub
- ticket file
- storage period
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
Images
Landscapes
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
Abstract
The embodiment of the invention relates to the technical field of communication, and provides a method, a device, equipment and a medium for detecting the continuity of a call ticket file. The invention discloses a method for detecting the continuity of a call ticket file, which comprises the following steps: collecting a charging call ticket file log containing a plurality of call ticket files, and acquiring file names of the plurality of call ticket files; respectively storing a plurality of call ticket files in corresponding sub-service databases according to the file names; determining that the call ticket file of the current storage period is completely stored in the sub-service database; and judging whether the call ticket file of the current storage period in the sub-service database which finishes the storage is continuous or not according to the file name. The method, the device, the equipment and the medium for detecting the continuity of the call ticket file can determine the continuity of the call ticket file of the current storage period by detecting the file name of the call ticket file.
Description
Technical Field
The present invention relates to the field of communications technologies, and in particular, to a method, an apparatus, a device, and a medium for detecting continuity of a ticket file.
Background
The charging ticket (including voice call, internet traffic, short message and other services) file of the mobile communication system is used as the basis for charging the user and providing detailed ticket query, and the timeliness and integrity of the ticket file in the generation, collection and processing processes must be ensured during the statistical processing. Therefore, in the process of carrying out statistical processing on the call ticket file by the charging subsystem of the mobile service support system, it is very important to ensure the timeliness and integrity of the detection and collection of the call ticket file.
The method for detecting and collecting the ticket file adopted by the existing charging subsystem is as follows:
1. the method comprises the steps that a call ticket file is collected to a temporary directory firstly, and if the collection is successful, the call ticket file is deleted from a server; if the collection is unsuccessful, the call ticket file is always kept on the server.
2. And in the collection process, the document level duplication checking can be carried out on the call ticket files, and if a plurality of call ticket files are judged to be the same file, repeated call ticket files cannot be collected.
3. And a competitive acquisition mode is supported in the acquisition process, namely two acquisition points simultaneously acquire call ticket files under the same directory of the same server.
Due to the abnormal situations such as unstable network, abnormal storage, link interruption, steep increase of telephone traffic, and problems of File Transfer Protocol (FTP) tools, etc., which may occur during the detection and collection process, the situation of backlog, abnormality or loss of the phone bill files may be caused. In addition, the call ticket file collection program itself may be abnormal or missed, and the call ticket file may be abnormal or lost. Once the call ticket file is overstocked, abnormal, lost or omitted, the normal charging of the operator is affected.
In summary, the existing method for detecting and collecting the ticket file cannot find the abnormality of the ticket file in time, and cannot effectively audit the ticket file loss and omission.
Disclosure of Invention
The embodiment of the invention provides a method, a device, equipment and a medium for detecting the continuity of a call ticket file, which can determine the continuity of the call ticket file in the current storage period by detecting the file name of the call ticket file, can find the abnormity of the call ticket file in time and effectively audit the loss and omission problems of the call ticket file.
In a first aspect, an embodiment of the present invention provides a method for detecting continuity of a ticket file, including:
collecting a charging call ticket file log containing a plurality of call ticket files, and acquiring file names of the plurality of call ticket files;
respectively storing a plurality of call ticket files in corresponding sub-service databases according to the file names;
determining that the call ticket file of the current storage period is completely stored in the sub-service database;
and judging whether the call ticket file of the current storage period in the sub-service database which finishes the storage is continuous or not according to the file name.
In a second aspect, an embodiment of the present invention provides a device for detecting continuity of a ticket file, including:
the data acquisition module is used for acquiring a charging ticket file log containing a plurality of ticket files and acquiring file names of the ticket files;
the data storage module is used for respectively storing the plurality of call ticket files into corresponding sub-service databases according to the file names;
the first processing module is used for determining that the call ticket file of the current storage period is completely stored in the sub-service database;
and the second processing module is used for judging whether the call ticket file of the current storage period in the sub-service database which is stored is continuous or not according to the file name.
The embodiment of the invention provides a call ticket file continuity detection device, which comprises: at least one processor, at least one memory, and computer program instructions stored in the memory, which when executed by the processor, implement the method of the first aspect of the embodiments described above.
In a fourth aspect, an embodiment of the present invention provides a computer-readable storage medium, on which computer program instructions are stored, which, when executed by a processor, implement the method of the first aspect in the foregoing embodiments.
The method, the device, the equipment and the medium for detecting the continuity of the ticket files provided by the embodiment of the invention can be used for timely finding the abnormity of the ticket files by acquiring the file names of a plurality of ticket files acquired by one or a plurality of network elements, detecting the file names of the ticket files, classifying the ticket files into different sub-services and determining the continuity of the ticket files of the current storage period of each sub-service, thereby effectively checking the loss and omission of the ticket files, timely triggering warning when the ticket files are discontinuous, effectively avoiding the loss of the ticket files caused by factors such as network or overstock when the ticket files generate charging tickets, reducing the loss of operators, ensuring the timeliness, integrity and safety of the charging tickets and improving the operation and maintenance efficiency of a service system.
Drawings
In order to more clearly illustrate the technical solutions of the embodiments of the present invention, the drawings required to be used in the embodiments of the present invention will be briefly described below, and for those skilled in the art, other drawings can be obtained according to the drawings without creative efforts.
Fig. 1 shows a flowchart of a method for detecting continuity of a ticket file according to an embodiment of the present invention;
fig. 2 shows a specific flowchart of the method for detecting continuity of a ticket file according to the embodiment shown in fig. 1;
fig. 3 shows a specific flowchart of a method for determining a lost ticket file according to an embodiment of the present invention;
fig. 4 shows a specific flowchart of a method for searching a lost ticket file according to another embodiment of the present invention;
FIG. 5 is a flowchart of a method for detecting continuity of a ticket file according to an embodiment of the present invention;
FIG. 6 is a detailed flowchart of a method for eliminating unreasonable files according to an embodiment of the present invention;
fig. 7 is a schematic diagram of a ticket file continuity detection apparatus according to an embodiment of the present invention;
fig. 8 is a schematic diagram of a ticket file continuity check apparatus according to another embodiment of the present invention;
fig. 9 shows a hardware structure diagram of the ticket file continuity check device according to the embodiment of the present invention.
Detailed Description
Features and exemplary embodiments of various aspects of the present invention will be described in detail below, and in order to make objects, technical solutions and advantages of the present invention more apparent, the present invention will be further described in detail below with reference to the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are merely illustrative of the invention and are not to be construed as limiting the invention. It will be apparent to one skilled in the art that the present invention may be practiced without some of these specific details. The following description of the embodiments is merely intended to provide a better understanding of the present invention by illustrating examples of the present invention.
It is noted that, herein, relational terms such as first and second, and the like may be used solely to distinguish one entity or action from another entity or action without necessarily requiring or implying any actual such relationship or order between such entities or actions. Also, the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising … …" does not exclude the presence of other identical elements in a process, method, article, or apparatus that comprises the element.
Fig. 1 shows a flowchart of a call ticket file continuity detection method according to an embodiment of the present invention.
As shown in fig. 1, an embodiment of the present invention provides a method 100 for detecting continuity of a ticket file, including:
s110, collecting a charging call ticket file log containing a plurality of call ticket files, and acquiring file names of the plurality of call ticket files;
s120, respectively storing the plurality of call ticket files in corresponding sub-service databases according to the file names;
s130, determining that the call ticket file of the current storage period is completely stored in the sub-service database;
and S140, judging whether the call ticket file of the current storage period in the sub-service database which is stored is continuous or not according to the file name.
In the embodiment of the present invention, in step S110, the file name of the ticket file acquired by the charging system may be collected in the charging ticket file log. The charging ticket file log may include ticket files of multiple users acquired by one or more network elements with a predetermined memory size acquired within a preset time period. Therefore, by acquiring the call ticket files in the charging call ticket file log, a plurality of call ticket files generated by a plurality of users in a preset time period can be acquired.
In the embodiment of the invention, the file name of the ticket file can comprise the IP of the manufacturer equipment and the prefix of the file name. The manufacturer equipment IP is used for distinguishing acquisition equipment used by different network elements for acquiring the ticket file. The file name prefix may include a sub-service code and a prefix sequence number. The sub-service codes are used for distinguishing sub-service types of the call ticket file, and the prefix numbers are used for distinguishing file numbers under the sub-services corresponding to the call ticket file.
Because there is no continuity relation between the call ticket files of different sub-services, the call ticket file continuity is judged under different sub-services, and therefore, the collected call ticket files need to be classified. And distributing the collected call ticket files to sub-service databases corresponding to different sub-services respectively.
In the embodiment of the present invention, in step S120, the method for storing a plurality of ticket files in corresponding sub-service databases according to file names may include:
s121, acquiring a sub-service code of a file name;
and S122, storing the plurality of call ticket files into corresponding sub-service databases according to the sub-service codes, namely classifying the call ticket files with the same sub-service codes into one class and storing the class into the sub-service databases corresponding to the sub-service codes.
Because the prefix sequence number of the ticket file is encoded periodically (i.e. the prefix sequence number of the file name of the ticket file usually has a starting and stopping range, e.g. 1-99), the prefix sequence numbers of the file names of the ticket files with the same sequence number in each storage period are the same, in order to avoid mutual interference of data among a plurality of storage periods, which leads to inaccurate detection results, and to improve the efficiency of continuity detection of the dialogue ticket file, it is necessary to perform periodic monitoring on the data received in the sub-service database, and perform continuity detection immediately after the ticket file in one period is stored.
In the embodiment of the present invention, in step S130, the method for determining that the storage of the ticket file of the current storage period in the sub-service database is completed may include S131 and S132.
S131, receiving the sub-service ending identification.
When the call ticket file sending equipment sends all the call ticket files of one sending period under one sub-service, a sub-service ending mark is generated to inform the receiving equipment that the call ticket files of the sending period of the sub-service are sent completely. Generally, the sub-service end identifier is sent out within two minutes after the call ticket file is sent out completely. The received sub-service end identifier can be stored in the corresponding sub-service database together with the call ticket file.
S132, determining that the call ticket file of the current storage period is completely stored in the sub-service database according to the sub-service ending identifier.
Specifically, it may be determined whether a sub-service end identifier of a transmission cycle corresponding to the current storage cycle exists in any sub-service database. If yes, determining that the call ticket file of the current storage period of the sub-service database is stored, performing continuity detection on the call ticket file, and storing the call ticket file in the next storage period when the call ticket file is continuously collected. If not, determining that the call ticket file of the current storage period of the sub-service database is not stored, reserving the current call ticket file by the sub-service database, and continuously storing the current call ticket file in the current storage period when the call ticket file is continuously acquired.
In addition, the efficient and accurate method for determining the continuity of the ticket file under different sub-services is to determine whether the prefix sequence number of the file name of the ticket file under any sub-service is continuous, so in step S140, the method for determining whether the ticket file of the current storage period in the sub-service database that has been stored is continuous according to the file name may include:
s141, acquiring a prefix serial number of the file name.
And S142, judging whether the stored call ticket file of the current storage period in the sub-service database is continuous or not according to the prefix sequence number.
And if the prefix sequence number of the file name of the ticket file of the current storage period in the sub-service database which is stored is a continuous sequence number and has no omission, determining that the ticket file of the current storage period in the sub-service database which is stored is continuous.
And if the prefix sequence number of the file name of the ticket file of the current storage period in the sub-service database which is stored is a discontinuous sequence number or the sequence number is omitted, determining that the ticket file of the current storage period in the sub-service database which is stored is discontinuous.
Fig. 2 shows a specific flowchart of the method for detecting continuity of a ticket file according to the embodiment shown in fig. 1.
As shown in fig. 2, the overall process of the method for detecting continuity of a ticket file includes:
s210, the collection equipment generates a charging ticket file log by collecting the ticket files of a plurality of network elements.
S220, collecting and sending data in the log of the charging ticket file collected by the equipment.
And S230, judging whether the transmission of the call ticket file of the current transmission period under each sub-service is finished. And if the transmission of the call ticket file in the current storage period is finished, executing S241, and then executing S242. And if the transmission of the ticket file of the current storage period is not finished, executing S242.
And S241, after the call ticket file is sent, sending a sub-service ending identifier corresponding to the sub-service.
And S242, storing the call ticket file and the sub-service ending identifier in a corresponding sub-service database.
S250, the receiving equipment judges whether the call ticket file of the current storage period in the sub-service database is stored, namely whether the sub-service ending mark is received. And if the storage is finished, executing S261 and judging the continuity of the call ticket file. If the storage is not finished, S262 is executed, and the call ticket file is kept and stored in the sub-service database. The sub-service database may be an in-memory database.
And when the continuity of the call ticket file of the current storage period is determined, displaying the call ticket file on the human-computer interaction equipment, for example, if the call ticket file of the current storage period is judged to be discontinuous, reminding the call ticket file catalog of the current storage period corresponding to the sub-service by red marking on the human-computer interaction equipment. Meanwhile, the man-machine interaction equipment can also support the inquiry of the IP and the file name prefix of manufacturer equipment of a specific discontinuous call ticket file.
The method for detecting the continuity of the call ticket file can utilize the common characteristic of the naming standards of the charging call ticket files of different network elements, namely that the file names all contain prefix serial numbers, and the prefix serial numbers all have periodicity. Therefore, the continuity of the prefix sequence number of the ticket file can be detected, and the timeliness and integrity of ticket file collection and processing can be guaranteed. As an example, the call ticket file is lost or delayed during the monitoring period, and the process can be intuitively monitored through the continuity detection of the prefix serial number.
After the determining that the call ticket file is discontinuous, in order to enable the monitoring personnel to more quickly find the missing call ticket file, in the embodiment of the present invention, after determining that the call ticket file of the current storage period in the sub-service database which has been stored is discontinuous, the method further includes:
s150, judging whether the prefix sequence number of the file name of the call ticket file is reset or not, namely judging whether the call ticket file is a cross-period file or not.
When the ticket file of the current storage period is stored in the sub-service database, the dialogue ticket file is sorted, that is, the prefix sequence numbers of the file names are arranged from small to large and then stored. At the moment, the sequence of the call ticket files subjected to continuity detection is not the arrival sequence of the call ticket files.
For example, the prefix sequence numbers of the file names of the stored call ticket files are generally stored in the order from small to large, that is, the storage sequence of the prefix sequence numbers is 1, 2, 3, 98, 99. However, the real sequence of the prefix sequence numbers may be 98, 99, 1, 2, 3, and at this time, the prefix sequence number of the file name of the ticket file is reset.
And S160, traversing the prefix sequence number corresponding to the file name of the lost ticket file according to the judgment result of the sequence number resetting.
Fig. 3 shows a specific flowchart of a method for determining a lost ticket file according to an embodiment of the present invention.
As shown in fig. 3, a specific process of the method for determining a lost ticket file according to the embodiment of the present invention may be:
s310, a ticket file of the current storage period is taken out to be used as a sequence to be detected.
S320, judging whether the sequence to be detected is empty or not. If the sequence to be detected is not empty, S330 is executed, and if the sequence to be detected is empty, the flow is ended.
S330, determining the average value of the maximum sequence number and the minimum sequence number preset in the storage period as a preset threshold value.
And S340, traversing the sequence to be detected in an increasing mode according to the step length.
And S350, respectively calculating the actual step length between the prefix sequence numbers of two adjacent call ticket files in the sequence to be detected.
And S360, judging whether the actual step length is larger than a preset threshold value or not, if so, determining that sequence number resetting occurs, and executing S371. If the actual step size is not greater than the preset threshold, S372 is performed.
And S371, respectively traversing the prefix sequence numbers of the lost ticket files at the head and the tail of the queue of the sequence to be detected.
And S372, directly traversing all discontinuous sequence numbers of the sequence to be detected as prefix sequence numbers of the lost ticket file.
For example, the prefix numbers of the sequence to be detected are 2, 3, 4, 97, and 98, respectively, and the average value of the maximum number 99 and the minimum number 1 is used as the preset threshold. If the step length between two adjacent prefix sequence numbers is larger than a preset threshold value, the queue tail is considered to arrive first, at this time, the arrival sequence of the sequence to be detected is considered to be 97, 98, 2, 3 and 4, and the sequence number is reset. At this time, the prefix sequence numbers of the lost ticket files are determined to be 1 and 99. And if the step length between two adjacent prefix serial numbers is smaller than or equal to a preset threshold value, the head of the queue is considered to arrive first, the arrival sequence of the sequence to be detected is considered to be 2, 3, 4, 97 and 98, namely the serial number is not reset, and at the moment, the prefix serial numbers of the lost ticket file are determined to be 1, 5-96 and 99.
Due to the characteristics of data transmission, the ticket files of the same sending period can be collected and stored in different storage periods. Therefore, in order to avoid that the lost ticket file is stored in the sub-service database, but the lost ticket file is not used for detecting the continuity in other storage periods, the accuracy of detecting the continuity of the ticket file is influenced. In the embodiment of the present invention, after traversing the prefix sequence number corresponding to the file name of the lost ticket file according to the determination result of the sequence number resetting, the method further includes:
s170, determining whether a lost call ticket file of the current storage period exists in the call ticket file of the previous storage period according to the prefix sequence number of the file name; if the ticket file of the previous storage period has the lost ticket file of the current storage period, the lost ticket file is supplemented into the ticket file of the current storage period; if the call ticket file of the previous storage period does not have the lost call ticket file of the current storage period, the step S180 is not executed, and the call ticket file of the current storage period is not continuous.
Similarly, whether the lost call ticket file of the previous storage period exists in the call ticket file of the current storage period can also be determined by the prefix sequence number of the file name. If the ticket file of the previous storage period has the lost ticket file of the current storage period, the lost ticket file is filled into the ticket file of the previous storage period; if the call ticket file of the previous storage period does not have the lost call ticket file of the current storage period, the step S180 is not executed, and the call ticket file of the previous storage period is not continuous.
And S180, judging whether the call ticket file of the current storage period is continuous or not.
The judgment can be performed again by adopting the methods of steps S150 and S160, and it can also be directly judged whether the supplemented lost ticket file is completely consistent with the lost ticket file of the current storage period, if so, it can be determined that the ticket file of the current storage period is continuous, and if not, for example, the number of the supplemented lost ticket files is less than that of the lost ticket file of the current storage period, it can be determined that the ticket file of the current storage period is still discontinuous. Similarly, whether the ticket file of the previous storage period is continuous or not can be judged again.
Fig. 4 shows a specific flowchart of the method for searching a lost ticket file according to the embodiment of the present invention.
As shown in fig. 4, the specific process of the method for searching for a lost ticket file may be as follows:
s410, taking out the discontinuous call ticket file with other call ticket files in the call ticket file of the previous storage period.
S420, taking out discontinuous call ticket files of the current storage period and other call ticket files.
S430, determining whether the discontinuous call ticket file is the lost call ticket file of the previous storage period and the current storage period. If so, S440 is executed, otherwise, the process ends.
And S440, supplementing the lost ticket file into the corresponding storage period.
S450, judging whether the ticket files of the previous storage period and the current storage period after rearrangement are continuous or not.
It should be noted that, if only one ticket file of the current storage period is stored in the previous storage period, and the current storage period is emptied after the last storage period is stored, so as to prevent interference of the cross-period data.
Fig. 5 shows a flowchart of a ticket file continuity detection method according to another embodiment of the present invention.
As shown in fig. 5, another embodiment of the present invention provides a method 500 for detecting continuity of a ticket file, including:
s510, collecting a charging call ticket file log containing a plurality of call ticket files, and acquiring file names of the plurality of call ticket files;
s520, respectively storing the plurality of call ticket files in corresponding sub-service databases according to the file names;
s530, determining that the call ticket file of the current storage period is completely stored in the sub-service database;
s540, eliminating unreasonable files in the call ticket files of the current storage period in the sub-service database which is stored;
and S550, judging whether the call ticket file of the current storage period in the sub-service database which is stored is continuous or not according to the file name.
Steps S510, S520, S530, and S550 are the same as the steps in the method for detecting continuity of ticket file in the foregoing embodiment, and are not described herein again.
In the embodiment of the present invention, the method for eliminating unreasonable files in the ticket file of the current storage period in the sub-service database that has been stored specifically includes:
and S241, acquiring the prefix serial number of the file name.
And S242, eliminating unreasonable files in the call ticket file of the current storage period according to the prefix serial number.
The irrational file refers to a ticket file corresponding to a prefix number which has an excessively large deviation with other prefix numbers in the current storage period and a large deviation with the prefix number in the previous storage period, and is mainly dirty data generated during start-stop or when periodic data is disordered, so that the irrational condition of the prefix number corresponding to the ticket file in the current storage period after processing occurs. Such as: the sequence of the prefix sequence numbers corresponding to the call ticket files in the current storage period is 1, 321, 322, 323, and under this condition, the call ticket file corresponding to the prefix sequence number 1 is considered to be an unreasonable file.
FIG. 6 is a flowchart illustrating an unreasonable file culling method according to an embodiment of the present invention.
As shown in fig. 6, a specific process of the method for removing unreasonable files according to the embodiment of the present invention may be as follows:
s610, reading all the call ticket files in the previous storage period and the current storage period.
And S620, eliminating unreasonable files in the previous storage period and the current storage period, and storing the unreasonable files in the sub-service database again.
S630, judging whether the call ticket file in the last storage period after the unreasonable file is removed is empty. And if the ticket file in the previous storage period is not empty, executing S642. If the ticket file in the previous storage period is empty, S641 is executed first, and then S650 is executed.
S641, clearing all the call ticket files in the previous storage period and the current storage period.
S642, whether the call ticket file in the current storage period is continuous or not is detected.
And S650, caching the call ticket file in the current storage period in the last storage period.
It should be noted that, when the call ticket file in the current storage period is cached in the previous storage period and is used for processing the call ticket file of the next storage period, the call ticket file in the current storage period is used as the cache data of the previous storage period of the call ticket file of the next storage period.
Fig. 7 shows a schematic diagram of a ticket file continuity detection apparatus according to an embodiment of the present invention.
As shown in fig. 7, an embodiment of the present invention provides a device 700 for detecting continuity of a ticket file, including:
a data acquisition module 701, configured to collect a charging ticket file log including multiple ticket files, and acquire file names of the multiple ticket files;
a data storage module 702, configured to store the multiple ticket files in corresponding sub-service databases according to the file names;
the first processing module 703 is configured to determine that the call ticket file of the current storage period has been stored in the sub-service database;
and a second processing module 704, configured to determine whether the stored ticket file in the sub-service database in the current storage period is continuous according to the file name.
The file name of the call ticket file can comprise the IP of the manufacturer equipment and the prefix of the file name. The manufacturer equipment IP is used for distinguishing acquisition equipment used by different network elements for acquiring the ticket file. The file name prefix may include a sub-service code and a prefix sequence number. The sub-service codes are used for distinguishing sub-service types of the call ticket file, and the prefix numbers are used for distinguishing file numbers under the sub-services corresponding to the call ticket file.
In this embodiment of the present invention, the data storage module 702 is further configured to obtain a sub-service code of the file name, and store the ticket file in the corresponding sub-service database according to the sub-service code.
In this embodiment of the present invention, the second processing module 704 is further configured to obtain a prefix sequence number of the file name, and determine whether the stored ticket file of the current storage period in the sub-service database is continuous according to the prefix sequence number.
When the call ticket file sending equipment sends all the call ticket files of one sending period under one sub-service, a sub-service ending mark is generated to inform the receiving equipment that the call ticket files of the sending period of the sub-service are sent completely. In this embodiment of the present invention, the first processing module 7303 is further configured to receive a sub-service end identifier, and determine that the storage of the ticket file of the current storage period in the sub-service database is completed according to the sub-service end identifier.
In this embodiment of the present invention, the present invention further includes a third processing module 705, configured to, if the stored ticket file of the current storage period in the sub-service database is not continuous, determine whether a prefix sequence number of the file name of the ticket file is subjected to sequence number resetting, and traverse the prefix sequence number corresponding to the file name of the lost ticket file according to a determination result of the sequence number resetting.
In the embodiment of the present invention, the present invention further includes a fourth processing module 706, configured to determine whether the ticket file of the previous storage period has the lost ticket file according to the prefix sequence number corresponding to the file name of the lost ticket file; and if the ticket file in the previous storage period exists, the lost ticket file is supplemented into the ticket file in the current storage period, and then whether the ticket file supplemented into the current storage period of the lost ticket file is continuous or not is judged.
Fig. 8 is a schematic diagram illustrating a ticket file continuity check apparatus according to another embodiment of the present invention.
Another embodiment of the present invention provides a device 800 for detecting continuity of a ticket file, including:
a data acquisition module 801, configured to collect a charging ticket file log including multiple ticket files, and acquire file names of the multiple ticket files;
the data storage module 802 is configured to store the plurality of ticket files in corresponding sub-service databases according to the file names;
the first processing module 803 is configured to determine that the call ticket file of the current storage period is completely stored in the sub-service database;
a fifth processing module 804, which rejects unreasonable files in the call ticket file of the current storage period;
and a second processing module 805, configured to determine whether the stored ticket file in the sub-service database in the current storage period is continuous according to the file name.
The data obtaining module 801, the data storing module 802, the first processing module 803, and the second processing module 805 are the same as those in the above embodiments, and are not described herein again.
In this embodiment of the present invention, the fifth processing module 804 is further configured to obtain a prefix sequence number of the file name, and reject unreasonable files in the ticket file of the current storage period according to the prefix sequence number.
In addition, the method for detecting the continuity of the ticket file in the embodiment of the invention described in conjunction with fig. 1-4 can be realized by a device for detecting the continuity of the ticket file. Fig. 9 shows a schematic diagram of a hardware structure of a ticket file continuity detection device according to an embodiment of the present invention.
The ticket file continuity detection device may include a processor 901 and a memory 902 having stored computer program instructions.
Fig. 9 is a block diagram illustrating an exemplary hardware architecture of a computing device capable of implementing a communication method and a network server according to an embodiment of the present invention. As shown in fig. 9, computing device 900 includes an input device 901, an input interface 902, a processor 903, a memory 904, an output interface 905, and an output device 906.
The input interface 902, the processor 903, the memory 904, and the output interface 905 are connected to each other via a bus 910, and the input device 901 and the output device 906 are connected to the bus 910 via the input interface 902 and the output interface 905, respectively, and further connected to other components of the computing device 900.
Specifically, the input device 901 receives input information from the outside and transmits the input information to the processor 903 through the input interface 902; the processor 903 processes the input information based on computer-executable instructions stored in the memory 904 to generate output information, stores the output information in the memory 904 temporarily or permanently, and then transmits the output information to the output device 906 via the output interface 905; output device 906 outputs the output information external to computing device 900 for use by a user.
The computing device 900 may perform the steps of the communication methods described herein.
The processor 903 may be one or more Central Processing Units (CPUs). In the case where the processor or processors are one CPU, the CPU may be a single-core CPU or a multi-core CPU.
The memory 904 may be, but is not limited to, one or more of Random Access Memory (RAM), Read Only Memory (ROM), Erasable Programmable Read Only Memory (EPROM), compact disc read only memory (CD-ROM), a hard disk, and the like. The memory 904 is used to store program code.
It is understood that in the embodiment of the present application, the functions of any or all of the modules provided in fig. 5 to 8 may be implemented by the processor 903 shown in fig. 9.
In the above embodiments, the implementation may be wholly or partially realized by software, hardware, firmware, or any combination thereof. When used in whole or in part, can be implemented in a computer program product that includes one or more computer instructions. When loaded or executed on a computer, cause the flow or functions according to embodiments of the invention to occur, in whole or in part. The computer may be a general purpose computer, a special purpose computer, a network of computers, or other programmable device. The computer instructions may be stored in a computer readable storage medium or transmitted from one computer readable storage medium to another, for example, the computer instructions may be transmitted from one website site, computer, server, or data center to another website site, computer, server, or data center via wire (e.g., coaxial cable, fiber optic, Digital Subscriber Line (DSL), or wireless (e.g., infrared, wireless, microwave, etc.)). The computer-readable storage medium can be any available medium that can be accessed by a computer or a data storage device, such as a server, a data center, etc., that includes one or more of the available media. The usable medium may be a magnetic medium (e.g., floppy Disk, hard Disk, magnetic tape), an optical medium (e.g., DVD), or a semiconductor medium (e.g., Solid State Disk (SSD)), among others.
All parts of the specification are described in a progressive mode, the same and similar parts of all embodiments can be referred to each other, and each embodiment is mainly introduced to be different from other embodiments. In particular, as to the apparatus and system embodiments, since they are substantially similar to the method embodiments, the description is relatively simple and reference may be made to the description of the method embodiments in relevant places.
Claims (10)
1. A method for detecting continuity of a call ticket file is characterized in that the method comprises the following steps:
collecting a charging call ticket file log containing a plurality of call ticket files, and acquiring file names of the plurality of call ticket files;
respectively storing the plurality of ticket files in corresponding sub-service databases according to the file names;
determining that the call ticket file of the current storage period is completely stored in the sub-service database;
and judging whether the call ticket file of the current storage period in the sub-service database which finishes the storage is continuous or not according to the file name.
2. The method of claim 1, wherein the storing the plurality of ticket files in corresponding sub-service databases according to the file names comprises:
acquiring a sub-service code of the file name;
and storing the plurality of call ticket files in corresponding sub-service databases according to the sub-service codes.
3. The method of claim 1, wherein the determining that the call ticket file of the current storage period is completely stored in the sub-service database comprises:
receiving a sub-service end identifier;
and determining that the call ticket file of the current storage period is completely stored in the sub-service database according to the sub-service ending identifier.
4. The method of claim 1, wherein the determining whether the call ticket file of the current storage period in the sub-service database that has been stored is continuous according to the file name comprises:
acquiring a prefix sequence number of the file name;
and judging whether the call ticket file of the current storage period in the sub-service database which finishes the storage is continuous or not according to the prefix sequence number.
5. The method according to claim 1, wherein before determining whether the call ticket file of the current storage period in the sub-service database that has been stored is continuous according to the file name, the method further comprises:
acquiring a prefix sequence number of the file name;
and eliminating unreasonable files in the call ticket file according to the prefix serial number.
6. The method of claim 1, wherein after determining whether the call ticket file of the current storage period in the sub-service database that has been stored is continuous according to the file name, the method further comprises:
the call ticket file of the current storage period in the sub-service database which is stored is not continuous;
judging whether the prefix sequence number of the file name of the call ticket file is reset or not;
and traversing the prefix sequence number corresponding to the file name of the lost call ticket file according to the judgment result of the sequence number resetting.
7. The method of claim 6, wherein after traversing the prefix sequence number corresponding to the file name of the lost ticket file according to the determination result of the sequence number resetting, the method further comprises:
determining whether the lost call ticket file exists in the call ticket file of the previous storage period according to the prefix sequence number corresponding to the file name of the lost call ticket file;
if the call ticket file of the previous storage period has the lost call ticket file, the lost call ticket file is supplemented into the call ticket file of the current storage period;
and judging whether the call ticket file of the current storage period is continuous or not.
8. A call ticket file continuity detection device is characterized in that the device comprises:
the system comprises a data acquisition module, a data processing module and a data processing module, wherein the data acquisition module is used for acquiring a charging ticket file log containing a plurality of ticket files and acquiring file names of the ticket files;
the data storage module is used for respectively storing the plurality of ticket files into corresponding sub-service databases according to the file names;
the first processing module is used for determining that the call ticket file of the current storage period is completely stored in the sub-service database;
and the second processing module is used for judging whether the call ticket file of the current storage period in the sub-service database which is stored is continuous or not according to the file name.
9. A call ticket file continuity detection device is characterized by comprising: at least one processor, at least one memory, and computer program instructions stored in the memory that, when executed by the processor, implement the method of any of claims 1-7.
10. A computer-readable storage medium having computer program instructions stored thereon, which when executed by a processor implement the method of any one of claims 1-7.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201810608935.6A CN110659247A (en) | 2018-06-13 | 2018-06-13 | Method, device, equipment and medium for detecting continuity of call ticket file |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201810608935.6A CN110659247A (en) | 2018-06-13 | 2018-06-13 | Method, device, equipment and medium for detecting continuity of call ticket file |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN110659247A true CN110659247A (en) | 2020-01-07 |
Family
ID=69026210
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201810608935.6A Pending CN110659247A (en) | 2018-06-13 | 2018-06-13 | Method, device, equipment and medium for detecting continuity of call ticket file |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN110659247A (en) |
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN112328661A (en) * | 2020-11-04 | 2021-02-05 | 北京思特奇信息技术股份有限公司 | Method and system for monitoring call ticket processing performance and electronic equipment |
| CN115129739A (en) * | 2022-08-31 | 2022-09-30 | 杭州沃趣科技股份有限公司 | Data file breakpoint continuous transmission method, device, equipment and storage medium |
Citations (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1754364A (en) * | 2003-02-28 | 2006-03-29 | 索尼株式会社 | Transmission/reception system, transmitting device and method, and receiving device and method |
| CN101925039A (en) * | 2010-08-09 | 2010-12-22 | 中兴通讯股份有限公司 | Prewarning method and device of billing ticket |
| CN105787135A (en) * | 2016-04-11 | 2016-07-20 | 久盈世纪（北京）科技有限公司 | Method and device for backing up database logs |
| CN105824824A (en) * | 2015-01-06 | 2016-08-03 | 中国移动通信集团河南有限公司 | Standby call ticket collection equipment and call ticket file collection method for same |
| CN106559739A (en) * | 2016-09-28 | 2017-04-05 | 深圳成谷科技有限公司 | It is suitable to the lightweight data transmission method of Bluetooth Low Energy wireless communication system |
| CN107135188A (en) * | 2016-02-29 | 2017-09-05 | 阿里巴巴集团控股有限公司 | The service implementation method of financial information exchange FIX agreements, apparatus and system |
| CN107491356A (en) * | 2017-08-28 | 2017-12-19 | 广州市百果园信息技术有限公司 | Message treatment method, terminal device and server based on sequence number |
| CN107613409A (en) * | 2017-09-27 | 2018-01-19 | 京信通信系统（中国）有限公司 | The processing method and processing device of multi-medium data |
-
2018
- 2018-06-13 CN CN201810608935.6A patent/CN110659247A/en active Pending
Patent Citations (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1754364A (en) * | 2003-02-28 | 2006-03-29 | 索尼株式会社 | Transmission/reception system, transmitting device and method, and receiving device and method |
| CN101925039A (en) * | 2010-08-09 | 2010-12-22 | 中兴通讯股份有限公司 | Prewarning method and device of billing ticket |
| CN105824824A (en) * | 2015-01-06 | 2016-08-03 | 中国移动通信集团河南有限公司 | Standby call ticket collection equipment and call ticket file collection method for same |
| CN107135188A (en) * | 2016-02-29 | 2017-09-05 | 阿里巴巴集团控股有限公司 | The service implementation method of financial information exchange FIX agreements, apparatus and system |
| CN105787135A (en) * | 2016-04-11 | 2016-07-20 | 久盈世纪（北京）科技有限公司 | Method and device for backing up database logs |
| CN106559739A (en) * | 2016-09-28 | 2017-04-05 | 深圳成谷科技有限公司 | It is suitable to the lightweight data transmission method of Bluetooth Low Energy wireless communication system |
| CN107491356A (en) * | 2017-08-28 | 2017-12-19 | 广州市百果园信息技术有限公司 | Message treatment method, terminal device and server based on sequence number |
| CN107613409A (en) * | 2017-09-27 | 2018-01-19 | 京信通信系统（中国）有限公司 | The processing method and processing device of multi-medium data |
Non-Patent Citations (4)
| Title |
|---|
| 刘海燕: "宁夏电信计费综合结算系统数据处理模块的设计与实现", 《中国优秀硕士学位论文全文数据库 (信息科技辑)》 * |
| 刘海燕: "宁夏电信计费综合结算系统数据处理模块的设计与实现", 《中国优秀硕士学位论文全文数据库 (信息科技辑)》, 15 March 2016 (2016-03-15) * |
| 戴乐: "湖南铁通计费系统的若干技术研究", 《中国优秀硕士学位论文全文数据库 (信息科技辑)》 * |
| 戴乐: "湖南铁通计费系统的若干技术研究", 《中国优秀硕士学位论文全文数据库 (信息科技辑)》, 15 January 2009 (2009-01-15) * |
Cited By (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN112328661A (en) * | 2020-11-04 | 2021-02-05 | 北京思特奇信息技术股份有限公司 | Method and system for monitoring call ticket processing performance and electronic equipment |
| CN112328661B (en) * | 2020-11-04 | 2024-04-02 | 北京思特奇信息技术股份有限公司 | Method, system and electronic equipment for monitoring ticket processing performance |
| CN115129739A (en) * | 2022-08-31 | 2022-09-30 | 杭州沃趣科技股份有限公司 | Data file breakpoint continuous transmission method, device, equipment and storage medium |
| CN115129739B (en) * | 2022-08-31 | 2022-11-25 | 杭州沃趣科技股份有限公司 | Data file breakpoint continuous transmission method, device, equipment and storage medium |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN111459782B (en) | Method and device for monitoring service system, cloud platform system and server | |
| CN112163728B (en) | Energy consumption data processing method and device, electronic equipment and storage medium | |
| CN110147470B (en) | Cross-machine-room data comparison system and method | |
| CN112165517B (en) | Return source detection method and device, storage medium and electronic equipment | |
| CN110659247A (en) | Method, device, equipment and medium for detecting continuity of call ticket file | |
| CN112866062A (en) | Distributed pressure test system, method, device, equipment and storage medium | |
| CN109600254B (en) | Method for generating full-link log and related system | |
| CN112148508B (en) | Information processing method and related device | |
| CN105893150B (en) | Interface calling frequency control method and device and interface calling request processing method and device | |
| CN112671602A (en) | Data processing method, device, system, equipment and storage medium of edge node | |
| CN111324583B (en) | Service log classification method and device | |
| CN116743606A (en) | Abnormal flow monitoring method, device, equipment and storage medium | |
| CN111291021A (en) | Database management method and device, electronic equipment and storage medium | |
| CN115277588B (en) | Fusing current limiting system based on middle platform system | |
| CN114039878B (en) | Network request processing method and device, electronic equipment and storage medium | |
| CN114143263B (en) | Method, equipment and medium for limiting current of user request | |
| CN114338794A (en) | Service message pushing method and device, electronic equipment and storage medium | |
| CN113839888A (en) | Current limiting method, device, equipment and readable storage medium | |
| CN112988504A (en) | Alarm strategy setting method and device, electronic equipment and storage medium | |
| CN113014456A (en) | Monitoring data transmission system, method, device, equipment and storage medium | |
| CN111507594A (en) | Data processing method and equipment | |
| CN108763291B (en) | Data management method and device and electronic equipment | |
| CN111444184A (en) | Data storage method, storage scheduling server, electronic device and storage medium | |
| JP5011174B2 (en) | Information device management method | |
| CN111104462B (en) | Task distribution method, device and system based on blockchain |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination |