CN105050068B

CN105050068B - A kind of charging bill record detection bearing calibration, device and ticket processing system

Info

Publication number: CN105050068B
Application number: CN201510332379.0A
Authority: CN
Inventors: 岳锐
Original assignee: Chongqing Yue Zhi Technology Co Ltd
Current assignee: Chongqing Yue Zhi Technology Co., Ltd.
Priority date: 2015-06-16
Filing date: 2015-06-16
Publication date: 2018-12-11
Anticipated expiration: 2035-06-16
Also published as: CN105050068A

Abstract

It is recorded the present invention relates to a kind of charging bill and detects bearing calibration, it includes obtain charging bill file, establish correction with reference to the exception field in user information database, generation ticketing session sequence and detection ticket record and correct four steps.The invention further relates to a kind of charging bills to record detection means for correcting and a kind of ticket processing system.The present invention is abnormal for ticket writing field present in ticket writing, the problem of ticket missing is imperfect and ticket repeats, it being capable of duplicate removal ticket writing, according to the charge associated relationship between ticket writing during chargeable session, ticketing session sequence and correction are constructed with reference to user information database, for ticketing session sequence, carrying out terminates ticket integrality and ticket writing field abnormality detection and correction, improve the accuracy and validity of mobile Internet access charging bill data, the accuracy and reliability of user's expenses of surfing Internet calculating is improved simultaneously, also operator and the interests of user have been ensured.

Description

A kind of charging bill record detection bearing calibration, device and ticket processing system

Technical field

The present invention relates to field of communication technology, specifically a kind of charging bill record detection bearing calibration, device and ticket Processing system.

Background technique

As mobile communication network technology develops, the mobile data network for being capable of providing high speed Internet access business obtains extensive portion Administration and application.3G mobile communication technology of the CDMA2000 network as mainstream, can provide 1X/EV-DO both of which for user Mobile Internet access business, meet the business demand of people's mobile Internet access.CDMA2000 network and the framework of charge system such as Fig. 1 institute Show, when user initiates internet business, is connect by the RAN1 (Radio access network, Radio Access Network) of CDMA2000 Entering to packet core network includes: data gateway equipment 3 and AAA equipment 2, completes to authenticate by user authentication in core network Afterwards, core network device establishes user's PPP session, and distributes IP address for user, AAA equipment 2 to the upper network process of user into Row charging, during user uses internet business, AAA equipment 2 can be according to user's charging property and session status, to prepayment The function of online charging is realized at expense family, realizes offline charging function to postpaid service user.AAA equipment 2 and BOSS system service The interaction of device 4, it is common to complete user's charging.

AAA equipment generates the complete ticket writing of user's online, and ticket writing includes pre-payment ticket writing and post-paid Ticket writing is output to charging bill file.Ticket writing is made of multiple domains (record field), mainly includes user's online industry Business information, the network information and portfolio use information (data on flows, duration data).AAA equipment is adopted according to user's charging property Customer billing function: prepayment service process, post payment service process is realized with two kinds of business processing flows.At prepayment service Reason process is: for prepaid user during online, AAA equipment is real-time by online charging agreement and online charging system Interactive user Internet data, the online charging module of online charging system conversate management to user, the operation such as charging control, And interacted according to operating result with AAA equipment, control user's internet business uses, and AAA equipment can produce during user surfs the Internet Raw pre-payment online ticket writing is simultaneously written to CDR file.Offline charging business procession is: surfing the Internet in postpaid service user In the process, AAA equipment generates user's post-paid ticket writing and is written CDR file, BOSS system acquisition AAA CDR file into Row charging processing.The ticket writing that AAA equipment generates uses the detailed single lattice formula of identical ticket, according to pre-payment and post-paid ticket Charge type field value in record distinguishes.

According to CDMA2000 mobile network's charging specification, ticketing terminates ticket as user's online rates ground and expense With the basis of calculating.The accuracys of ticket writing charging bill data, Usefulness Pair are in ensuring that operator's mobile data services seek Receipts are of great significance.According to previously described two kinds of call charge service treatment processes:

For mobile Internet access online charging business, AAA equipment and online charging system real-time, interactive, online charging system are complete At treatment processes such as wholesale price, portfolio inverse, management of balance, generating online charging inventory record includes: business information, portfolio Information, cost information, while the online charging ticket writing that AAA equipment can generate.

For offline charging business, AAA equipment generates offline charging CDR file, and BOSS system acquisition AAA equipment generates Charging bill file completes charging process flow according to ticket writing is terminated, generates user's billing invoice, complete mobile data industry The business revenue of business.

For online charging business, existing charging bill auditing method has: check by online charging system generate Line keep cost order record and user bill record, compare the statistics of above-mentioned " online charging inventory record " and " user bill record " Otherness between data marks error log to find the error being likely to occur in charging, and report data is checked in generation. For the online charging process of duration based accounting, there is the processing surf time to overlap the method for charging bill, reject time-interleaving Part merges and generates a new ticket.

For offline charging business, existing method is the CDR file that the AAA equipment original to BOSS system acquisition generates Transmission process check correction, guarantee the correctness and verification property of CDR file acquisition transmission.School is increased to CDR file Code is tested, after the acquisition transmission of each file, automatic Verification is carried out to this document according to the check code of file and checks that system, which is checked, adopts The CDR file and acquisition log information collected, checks the following contents by CDR file: collection point, file name, file size, Daily or the period checks quantity of documents, file total bytes etc..System is to according to the file of acquisition and log gradually shape At based on acquisition statistical data analysis, principal statistical element include: collection point, interchanger, collection period, acquisition file number, Acquire file size.The information of this acquisition and history acquisition information are just compared school by acquisition system per a period of time simultaneously It tests, forms variance analysis, for being more than that the acquisition data of certain value can consider acquisition abnormity, report is formed, for confirmation.

By being analyzed above it is found that number of the charging bill data as mobile data services user's charging that AAA equipment generates According to foundation, existing metering data process flow and auditing method are using the Original CDR that network billing equipment generates as auditing department The basis of reason and foundation will not go the field and numerical value that change and revise the call bill data itself generated.With mobile mutual The development of networking technology and terminal technology, the type of internet business, application scenarios and user's internet behavior all become increasingly Multiplicity, while wireless network overlay environment (such as high-speed rail, rail traffic, tunnel, bridge covering scene) also becomes more and more multiple It is miscellaneous.The interaction of the factors such as network, user, business can have an important influence on network quality and performance, further influence net The quality that network data generate, as operation flow is abnormal, signaling message is lost, counter data is abnormal, timer is extremely overtime, magnetic The factors such as disk I/O exception have an impact integrality, the validity of ticket writing, and the call bill data for causing AAA equipment to generate goes out Existing following abnormal conditions:

1. ticket writing is imperfect, lack ticket writing, loses what part online chargeable session should generate in the process Ticket writing such as starts ticket, interim UDR or terminates ticket.

2. there is the identical ticket writing of a plurality of repetition, occur in CDR file a plurality of ticket field contents it is identical if Unirecord.

3. exception occur in one or more field values in ticket writing, wanted as field value does not meet equipment specification It asks or numerical value does not meet the abnormal conditions such as bill services logic.

The abnormal conditions that the ticket writing that AAA equipment generates occurs, influence whether the validity of call bill data, accuracy and Reliability, and then the accuracy and validity of charging processing result are influenced, cause the business revenue of mobile data services to be unable to get guarantor Barrier.

Summary of the invention

The purpose of the present invention is to provide a kind of charging bills to record detection bearing calibration, device and ticket processing system, It is used to solve the problems, such as in ticket writing that field to be abnormal.

Technical scheme is as follows:

A kind of charging bill record detection bearing calibration comprising following steps:

Step a: charging bill file, the charging words are obtained from counting equipment or charging gateway or BOSS system User's charging number that monofile is user to be generated during terminating since chargeable session to chargeable session during online According to.

Step b: it establishes correction and refers to user information database, the correction is that operation is commercial with reference to the data in user information database User record in the information bank of family and/or the user bill record not comprising exception field got.

Step c: the ticket writing in duplicate removal charging bill file, with the ticket writing during user's chargeable session Chronologically and charging state relation relationship generates a ticketing session sequence.

Step d: detecting whether each ticket writing in the ticketing session sequence contains exception field, will contain different The ticket writing of normal field is output in an original anomaly CDR file, according between ticket writing in ticketing session sequence Service logic rule and the exception field that the Data correction ticket writing in user information database is referred to by comparing correction, high-ranking officers Ticket chargeable session sequence after just is output in an abnormal correction ticket writing file.

Further, further include step c1 after the step c: abnormal call ticket code field being increased to every ticket writing and is assigned Initial value；The process of the exception field of the positive ticket writing of step d lieutenant colonel includes: the exception field type according to ticket writing Classification assignment exception code field, different exception field types is identified with different exception codes.

Further, the exception field type of ticket writing includes terminating the complete sexual abnormality of ticket, user in the step d Number field is abnormal, user IMSI field is abnormal, charge type field is abnormal, chargeable session duration field is abnormal, network flow Abnormal, activation duration field exception.

Further, the initial assignment of the abnormal code field of the ticket writing is numerical value 0, in ticketing session sequence The detection correction sequence of ticket writing be followed successively by and terminate the correction of ticket integrity detection, Subscriber Number field detection correction, use Family IMSI field detection correction, charge type field detection correction, chargeable session duration field detection correction, exception of network traffic Detection correction and activation duration field detection correction, the corresponding abnormal code field of the Exception Type of the sequence be followed successively by numerical value 1 to 7。

Further, terminate ticket integrity detection correction course are as follows: in last in detection ticket chargeable session sequence The charging mode field of the ticket writing of timing, if the value of charging mode field is abnormal, the ticket that the ticket writing is arranged is different Normal code is numerical value 1, which is output in original anomaly CDR file, by the charging mode field of the ticket writing Value is corrected to the numerical value for indicating that ticket terminates.

Further, Subscriber Number field detects correction course are as follows: the number format and number of detection Subscriber Number field If Subscriber Number field is abnormal under the premise of the abnormal code field of ticket writing is numerical value 0, then abnormal call ticket is arranged in digit Code value is numerical value 2, and the ticket writing is written in original anomaly CDR file, to represent international mobile use in ticket writing The IMSI field of family identification code is critical field, searches correction with reference to the user record in user information database, if there is IMSI The identical record of field value then corrects this ticket writing with reference to the Subscriber Number field value in user information database record using correction In Subscriber Number field.

Further, user IMSI field detects correction course are as follows: the number of detection international mobile subscriber identity field Format and digit, if international mobile subscriber identity field is abnormal, before the abnormal code field of ticket writing is numerical value 0 It puts, then it is numerical value 3 that abnormal call ticket code value, which is arranged, and the ticket writing is written in original anomaly CDR file, with ticket Subscriber Number field value in record is critical field, searches the user record corrected with reference in user information database, if there is The identical record of Subscriber Number field value is then corrected using correction with reference to the international mobile subscriber identity value in user information database International mobile subscriber identity field in the ticket writing.

Further, charge type field detects correction course are as follows: the number format and value of detection charge type field If charge type field value is abnormal under the premise of the abnormal code field of ticket writing is numerical value 0, then it is different that ticket is arranged in range Normal code value is numerical value 4, and the ticket writing is written in original anomaly CDR file, with the user number in the ticket writing Code word segment value is critical field, searches correction with reference to the user record in user information database, if there is Subscriber Number field value Identical record then corrects the charging class in the ticket writing with reference to the charge type field value in user information database using correction Type-word segment value.

Further, chargeable session duration field detects correction course are as follows: the number of detection chargeable session duration field value Format and value range, if chargeable session duration field value is abnormal, in the premise that the abnormal code field of ticket writing is numerical value 0 Under, then it is numerical value 5 that abnormal call ticket code value, which is arranged, which is written in abnormal correction ticket writing file, and will Chargeable session duration field value is corrected to the dialog events time difference, and the dialog events time difference is the session of current ticket writing Event time and the difference in the dialog events time of the ticket writing of timing front end in ticketing session sequence.

Further, network flow detects correction course are as follows: byte number, the user of user are sent in detection ticket record Byte number, uplink traffic overturning number and the downlink traffic of initiation overturn the number format of four fields of number, and are based on this The calculated upstream data flow of four field values and downlink data flow, if detecting Client-initiated byte digital section lattice An at least exception in formula, uplink traffic overturning time field format and upstream data flow three, in the different of ticket writing Under the premise of normal code field is numerical value 0, then it is 6 that abnormal call ticket code value, which is arranged, and ticket writing write-in original anomaly is talked about In monofile, the value of Client-initiated byte digital section and uplink traffic overturning time field is corrected to ticketing session sequence Respective value in column in the ticket writing of previous moment；If detecting the byte number field format, the downstream that are sent to user Amount overturning at least one of time field format and downlink data flow three is abnormal, is number in the abnormal code field of ticket writing Under the premise of value 0, then it is 6 that abnormal call ticket code value, which is arranged, and the ticket writing is written in original anomaly CDR file, will be sent out The value of the byte digital section, downlink traffic overturning time field of giving user is corrected to previous moment in ticketing session sequence Ticket writing in respective value.

Further, activation duration field detects correction course are as follows: the interim UDR in detection ticket chargeable session sequence Record and the number format for activating duration field value, value range and the service logic rule for terminating ticket writing, if when activation Duration field value is abnormal, under the premise of the abnormal code field of ticket writing is numerical value 0, then sets numerical value for abnormal call ticket code value 7, which is written in original anomaly CDR file, if the ticket of previous moment is remembered in ticketing session sequence A length of 0 when activation in record, then in the user radio ticket for corresponding equipment for radio access network record that this is surfed the Internet Corrected value of the duration of eating dishes without rice or wine as the currently active duration, or the chargeable session duration in ticket writing is remembered as current ticket Otherwise the corrected value of the activation duration of record is made the activation duration in ticketing session sequence in the ticket writing of previous moment For the corrected value of the activation duration of current ticket writing.

Further, further include step e after step d: according to original anomaly CDR file and abnormal correction ticket note Record file generated ticket detection correction statistical report form.

A kind of charging bill record detection means for correcting comprising acquiring unit, correction reference unit, pretreatment unit and Correction processing unit, correction reference unit and correction processing unit data interaction, acquiring unit output connection pretreatment unit, in advance Processing unit output connection correction processing unit, in which: acquiring unit is for periodically acquiring or receiving charging bill file, institute It states in charging bill file as the charging bill file in counting equipment, charging gateway or BOSS system；Correct reference unit User information database is referred to for establishing correction, correction is with reference to the use that the data in user information database are in provider customer's information bank Family record records for the user bill not comprising exception field got；Pretreatment unit is talked about for duplicate removal processing charging Ticket writing in monofile, by with the ticket writing in chargeable session chronologically and charging state relation relationship generates one It is a using ticket writing as the ticket chargeable session sequence of element；Each ticket of the correction processing unit to ticket chargeable session sequence Record adds abnormal code field, detects the ticket writing with exception field, the ticket writing with exception field is saved in In original anomaly CDR file, join according to the service logic rule between ticket writing in ticketing session sequence and with correction The correction in unit is examined with reference to the exception field of user information database data interaction correction ticket writing, by the ticketing after correction All ticket writings in session sequence are saved in abnormal correction ticket writing file, and by original anomaly CDR file and Data in abnormal correction ticket writing file generate ticket detection correction statistical report form.

Further, the correction processing unit carries out each ticket writing to terminate ticket integrality, user number code word Section, user IMSI field, charge type field, chargeable session duration field, network flow and activation seven exceptions of duration field The detection of type corrects, and the initial assignment that abnormal code field is arranged in correction processing unit is numerical value 0, and according to the different of ticket writing Normal field type classification assignment exception code field, the corresponding abnormal code field of seven Exception Types are followed successively by numerical value 1 to 7.

Further, terminate ticket integrity detection correction course are as follows: in last in detection ticket chargeable session sequence The charging mode field of the ticket writing of timing, if the value exception of charging mode field, is in the abnormal code field of ticket writing Under the premise of numerical value 0, then the ticket exception code that the ticket writing is arranged is numerical value 1, which is output to original anomaly In CDR file, the value of the charging mode field of the ticket writing is corrected to the numerical value for indicating that ticket terminates.

Subscriber Number field detects correction course are as follows: the number format and digit of detection Subscriber Number field, if with Family number field is abnormal, and under the premise of the abnormal code field of ticket writing is numerical value 0, then it is numerical value that abnormal call ticket code value, which is arranged, 2, and the ticket writing is written in original anomaly CDR file, to represent international mobile subscriber identity in ticket writing IMSI field is critical field, searches the user record corrected with reference in user information database, identical if there is IMSI field value Record, then using correction with reference to user information database record in Subscriber Number field value correct the user number in this ticket writing Code field.

User's IMSI field detects correction course are as follows: the number format and number of detection international mobile subscriber identity field Digit under the premise of the abnormal code field of ticket writing is numerical value 0, is then set if international mobile subscriber identity field is abnormal Setting abnormal call ticket code value is numerical value 3, and the ticket writing is written in original anomaly CDR file, with the use in ticket writing Family Number character segment value is critical field, searches correction with reference to the user record in user information database, if there is user number code word The identical record of segment value then corrects the ticket writing with reference to the international mobile subscriber identity value in user information database using correction In international mobile subscriber identity field.

Charge type field detects correction course are as follows: the number format and value range of detection charge type field, if meter Take type field value exception, under the premise of the abnormal code field of ticket writing is numerical value 0, then abnormal call ticket code value is set for number Value 4, and the ticket writing is written in original anomaly CDR file, it is with the Subscriber Number field value in the ticket writing Critical field, searches correction with reference to the user record in user information database, if there is the identical record of Subscriber Number field value, Then the charge type field value in the ticket writing is corrected with reference to the charge type field value in user information database using correction.

Chargeable session duration field detects correction course are as follows: the number format and value of detection chargeable session duration field value If chargeable session duration field value is abnormal under the premise of the abnormal code field of ticket writing is numerical value 0, then words are arranged in range Single exception code value is numerical value 5, which is written in abnormal correction ticket writing file, and by chargeable session duration Field value is corrected to the dialog events time difference, and the dialog events time difference is dialog events time and the place of current ticket writing The difference of the dialog events time of the ticket writing of timing front end in ticketing session sequence.

Network flow detects correction course are as follows: byte number, the Client-initiated word of user are sent in detection ticket record The number format of joint number, uplink traffic overturning number and downlink traffic overturning four fields of number, and it is based on this four fields It is worth calculated upstream data flow and downlink data flow, if detecting Client-initiated byte number field format, uplink Flow overturns an at least exception in time field format and upstream data flow three, in the abnormal code field of ticket writing Under the premise of for numerical value 0, then it is 6 that abnormal call ticket code value, which is arranged, and the ticket writing is written in original anomaly CDR file, The value of Client-initiated byte digital section and uplink traffic overturning time field is corrected to previous in ticketing session sequence Respective value in the ticket writing at moment；If detecting the byte number field format, the downlink traffic overturning time that are sent to user At least one of digital paragraph format and downlink data flow three are abnormal, before the abnormal code field of ticket writing is numerical value 0 It puts, then it is 6 that abnormal call ticket code value, which is arranged, and the ticket writing is written in original anomaly CDR file, will be sent to use The byte digital section at family, the value of downlink traffic overturning time field are corrected to the ticket of previous moment in ticketing session sequence Respective value in record.

Duration field is activated to detect correction course are as follows: interim UDR record and end in detection ticket chargeable session sequence Number format, value range and the service logic rule of the activation duration field value of ticket writing, if activation duration field value is different Often, under the premise of the abnormal code field of ticket writing is numerical value 0, then numerical value 7 is set by abnormal call ticket code value, by the ticket Record is written in original anomaly CDR file, if the activation in ticketing session sequence in the ticket writing of previous moment Shi Changwei 0, then the duration of eating dishes without rice or wine in the user radio ticket for corresponding equipment for radio access network record that this is surfed the Internet is made For the corrected value of the currently active duration, or using the chargeable session duration in ticket writing as when the activation of current ticket writing Long corrected value, otherwise using the activation duration in ticketing session sequence in the ticket writing of previous moment as current ticket The corrected value of the activation duration of record.

A kind of ticket processing system comprising data gateway equipment, AAA equipment, BOSS system server, operator CRM/ ODS system server, AAA equipment and data gateway equipment communicate to connect, and BOSS system server and AAA equipment communicate to connect, It further includes charging bill record detection means for correcting, charging bill record detection means for correcting respectively with AAA equipment, BOSS system server, the communication connection of operator's CRM/ODS system server.

A kind of charging bill record detection bearing calibration, device and ticket processing system provided by the invention, for ticket The problem of ticket writing field present in record is abnormal, ticket missing is imperfect and ticket repeats, being capable of duplicate removal ticket note Record constructs ticketing session sequence, for ticket meter according to the charge associated relationship between ticket writing during chargeable session Take session sequence, carrying out terminates ticket integrality and ticket writing field abnormality detection and correction, improves mobile Internet access charging The accuracy and validity of call bill data, while the accuracy and reliability of user's expenses of surfing Internet calculating is improved, also ensure The interests of operator and user.

Detailed description of the invention

Fig. 1 is mobile grouping field charge system network architecture schematic diagram in the prior art；

Fig. 2 is that a kind of ticket writing provided in an embodiment of the present invention detects bearing calibration flow diagram；

Fig. 3 is the schematic diagram that correction provided in an embodiment of the present invention refers to user information database；

Fig. 4 is the schematic diagram of ticketing session sequential structure provided in an embodiment of the present invention；

Fig. 5 is a kind of detection correcting process precedence diagram of ticket writing provided in an embodiment of the present invention；

Fig. 6 is the system construction drawing for a kind of station message recording provided in an embodiment of the present invention detecting means for correcting；

Fig. 7 is a kind of system construction drawing of ticket processing system provided in an embodiment of the present invention.

Specific embodiment

The invention will be further described with reference to the accompanying drawings and examples.

During user once surfs the Internet, AAA equipment can establish chargeable session process collection user's metering data of user, AAA equipment is that the chargeable session of each user distributes one by Correlation ID (association identification), Account Session The unique identification of ID (chargeable session mark) two field combinations, primary charging session may generate a plurality of ticket writing, and These station message recordings may export in different charging bill files.User is more with generating during a chargeable session Ticket writing is deposited in terms of recording generation time, ticketing state, network flow, activation duration, chargeable session In service logic relevance, these service logic relevances are as ticket writing loss, the important analysis of ticket field exception Judgment basis.

Under above-mentioned foundation, present solution provides a kind of charging bills to record detection bearing calibration, as shown in Fig. 2, it is wrapped Include following steps:

Step a: charging bill file, the charging bill are obtained from counting equipment, charging gateway or BOSS system User's metering data that file is user to be generated during terminating since chargeable session to chargeable session during online.

Step b: the user record in acquisition provider customer's information bank and/or the user bill note not comprising exception field Record establishes correction and refers to user information database.

Step c: duplicate removal pretreatment is carried out to the ticket writing in charging bill file, with user's chargeable session process In ticket writing chronologically and charging state relation relationship generate a ticketing session sequence.

In step a, ticket writing is periodically output in charging bill file and saves, and charging bill file includes The primary data content of the ticket writing of pre- charge type and post-billing type, ticket writing has: user's phone number, IMSI number When code, base station information, AAA address information, charge type, roaming type, business type selecting, uplink traffic, downlink traffic, charging The data contents such as long, activation duration.The mode for obtaining charging bill file can be from AAA equipment or charging gateway or BOSS system equipment actively obtains, and is also possible to passively receive the charging bill file from AAA equipment or charging gateway, also It can be and obtained from the other systems that can obtain charging bill file indirectly, such as ticket storage server.

Correction in step b is with reference to the data in user information database, for correcting the part exception field in ticket writing Part, correction should be corresponding with the field for needing to correct in ticket writing with reference to the record field in user information database.Correction ginseng Examining user information database can be updated periodically according to the renewal time of configuration, be preferably updated as unit of day, it is ensured that The consistency and integrality of source of reference data.Establishing correction can be refering to what is shown in Fig. 3, can be actively with reference to the method for user information database Obtain or receive the user data in the external user databases such as operator's CRM/ODS system.It is establishing or is updating When user corrects reference information library, need to judge whether user information is already present in library, using Subscriber Number as keyword, Scanning correction then updates in library with reference to user information database if there is the user record of same subscriber number is already present in library Otherwise user record creates the user record of a Subscriber Number.

In embodiments of the present invention, database table can be used to establish correction with reference to user information database, storage refers to school Positive user data.

It is that all ticket writings got in calibration cycle are pre-processed in step c, identifies in ticket writing Weight it is single, a ticket writing is retained after duplicate removal processing, it is ensured that without repeating ticket writing in the call bill data of subsequent processing.Weight is single Whether identification can identical as the single foundation of weight by comparing ticket writing whole field value, can also be according to Partial key field Combination it is whether identical as the single foundation of weight.It once surfs the Internet charging process for user, it can be according to the user number in ticket writing Code, IMSI, the charging identifier combined field such as Correlation ID, Account Session ID is single to identify weight, for Family is with the ticket writing generated during chargeable session, according to the Event Time (Event Timestamp) in ticket writing, Association of two field combinations of Acct-Status-Type (charging state) on time and charging state identifies same charging Sequential relationship in conversation procedure between ticket writing.All ticket writings of the same chargeable session after duplicate removal processing generate One ticketing session sequence, as shown in figure 4, complete ticketing session sequence ticket writing by (starts CDR), several interim UDR records (intermediate CDR) and end ticket (terminating CDR) record are constituted.

In step d, following ticket writing is carried out to ticket chargeable session sequence and detects correction process: to chargeable session sequence In end ticket writing carry out integrity detection and correction, further carry out the field abnormality detection correction of every ticket writing Processing.Ticket writing field abnormality detection content is mainly field format detection, the inspection of value range detection and service logic relationship It surveys, the exception field detected can be corrected according to above-mentioned correction with reference to the data of user information database, or according to words Service logic relationship in single session sequence between ticket writing is corrected.

Trailer field mark for example as the ticket writing of last timing is not the field value for representing conversation end, So the field is considered as exception, and being corrected to indicates the field value that terminates of chargeable session, this be according to service logic relationship into Row correction.The for another example user of some online set meal type, there is the transmission of uplink and downlink data during internet business, and AAA equipment exists User surfs the Internet in whole process, by a series of ticket writings of generation, the last item ticket generated for online finish time Terminate ticket writing, network flow is recorded using the business rule of flux cumulating in ticket writing according to AAA equipment, if Terminate in the calculated uplink of ticket writing or downlink network flow-rate ratio chargeable session sequence if previous charging point generation The calculated uplink of unirecord or downlink network flow are small, then are considered as exception of network traffic, need to the network detected The relevant flow field value of Traffic Anomaly types corrective, at this point it is possible to find uplink from current ticketing session sequence Or the ticket writing of downlink network maximum flow, such as terminating ticket writing uplink traffic is 10MB, however ticketing meeting The uplink traffic for talking about the ticket writing of previous moment in sequence is 12MB, then being sent with the user in previous moment ticket writing Byte number and uplink traffic overturning time field go correction terminate ticket writing in corresponding field, it is ensured that terminate ticket writing Uplink network flow, meet uplink network flow in primary charging conversation procedure and carried out by the service logic rule of bulk billing system Record.The field value of the similar this dynamic change in charging process, as flow, when long type field value occur it is abnormal, by It can not be restored in factual data, it can only be by being established based on the service logic rule between ticket writing in ticketing session sequence Factual data optimal numerical value, to reach correction purpose close to factual data as far as possible.For another example detected in certain ticket writing User's IMSI field digit is abnormal, then can be referred in user information database with the Subscriber Number field in ticket writing from correction The identical user record of a Subscriber Number field is searched, with the IMSI field of the IMSI field correction ticket in the record.This Kind during primary online will not changed static types field value, can be by according in correction reference database User record is corrected.Therefore, correction updates more timely with reference to the user record in user information database, is used according to correction reference Data in the information bank of family are more accurate come the result corrected.

After carrying out exception field detection correction process to the ticket writing in ticket chargeable session sequence, output calibration is verified File, correction audit files should include following file: abnormal correction ticket writing file, original anomaly CDR file and ticket inspection Survey correction statistical report form.

It is basic detection correction data unit with the ticket chargeable session sequence of above-mentioned foundation, to ticket chargeable session sequence In ticket writing carry out field abnormality detection and correction process, to the abnormal ticket writing detected according to the difference detected Abnormal conditions, the Classification and Identification by the way of different exception codes is arranged increase exception code field newly, correct sum number convenient for specific aim According to statistics, and assign initial value be 0 indicate it is without exception.According to the value of abnormal code field, it is corrected for the exception of the type, school Ticket chargeable session sequence after just is output in abnormal correction ticket writing file.Timing, such as abnormal call ticket code field Value be numerical value 6, represent exception of network traffic, timing has then been pointing directly in ticket writing the field for indicating network flow, It is exception field which need not be checked one by one.According to the difference of Exception Type, part exception field needs to join using above-mentioned correction The data examined in user information database are corrected, and part exception field is corrected according to chargeable session service logic rule.It will Ticket writing before correction is output in original anomaly CDR file, will correct all tickets in what happened latter list chargeable session sequence Record is output to abnormal correction ticket writing file.According to the data and exception correction ticket writing in original anomaly CDR file Data in file generate ticket detection correction statistical report form, analyze for operator's back-end data.

The exception field type of usual ticket writing includes terminating the complete sexual abnormality of ticket, Subscriber Number field exception, using Long word when family IMSI field exception, charge type field exception, chargeable session duration field exception, exception of network traffic, activation Duan Yichang.The detection correction sequence of ticket writing can be as shown in figure 5, press logical order, one by one successively to every ticket writing It carries out terminating the correction of ticket integrity detection, Subscriber Number field detection correction, user's IMSI field detection correction, charge type Field detection correction, chargeable session duration field detection correction, exception of network traffic detection correction and activation duration field detection Correction, the corresponding abnormal code field of the Exception Type of the sequence are successively set as numerical value 1 to 7.Said sequence can also be set again It is fixed, it can also individually carry out field detection correction to wherein some exception field type.The detection correction of each exception field type Process is as follows:

Terminate the correction of ticket integrity detection: the integrality of detection ticket chargeable session sequence first checks ticketing The charging mode field of ticket writing in session sequence in last timing, detects whether the field value identifies this charging meeting Words terminate, and CDMA2000 network indicates that charging state, value are that number 2 then represents session knot with Acct-Status-Type field Beam.If Acct-Status-Type field value is 2, ticket writing is without exception, into subsequent detection aligning step.If Acct- The numerical value of Status-Type field is not 2, then ticketing session sequence is imperfect, lacks end ticket writing, needs to talk with The Acct-Status-Type field value of the last item ticket writing is corrected processing in single chargeable session sequence, and setting is last The ticket exception code of one ticket writing is numerical value 1, and the ticket writing before correction is written in original anomaly CDR file, is repaired Change the value of the Acct-Status-Type field of the last item ticket writing as number 2.

The detection correction of Subscriber Number field: to represent the MDN field number format sum number word bit number of user's phone number into Row detection and correction.MDN field value format should be decimal number word format, and MDN field value digit rule is to be pre-configured with, Ordinary user MDN field digit is generally 13 (86+ user's phone number (11)) in the cdma 2000 network, according to number Format and digit configuration rule detect MDN field value, for detecting the ticket writing of MDN field exception, if abnormal call ticket Code is numerical value 0, then it is numerical value 2 that abnormal call ticket code value, which is arranged, and ticket writing is written in original anomaly CDR file.Into One step searches correction using MSID (user IMSI) field for representing international mobile subscriber identity in ticket writing as critical field With reference to the user record in user information database, if there is the identical record of IMSI field value, then believed using correction with reference to user MDN field value in the record of breath library corrects the MDN field in this ticket writing, into subsequent detection aligning step；If do not looked for To the user record of identical IMSI field, then subsequent detection aligning step is directly entered.

User's IMSI field detection correction: to represent international mobile subscriber identity MSID field carry out number format and Digit detection, the format of MSID field should be 15 decimal number word formats, be unsatisfactory for digital lattice for MSID field Unirecord if formula and digit, if abnormal call ticket code is numerical value 0, it is numerical value 3 that abnormal call ticket code value, which is arranged, and will The ticket writing is written in original anomaly CDR file.Further using the MDN field value in ticket writing as critical field, look into It looks for correction with reference to the user record in user information database, if there is the identical record of MDN field value, then uses the ticket writing In MSID value correct the MSID number in abnormal ticket writing, into subsequent detection aligning step, if not finding identical MDN The user record of field is then directly entered subsequent detection aligning step.

The detection correction of charge type field: number format and value are carried out to the PaidType field value for indicating charge type The detection of range, PaidType field value format should be decimal number word format, in the cdma 2000 network PaidType field The range of value generally should be [0,4], and abnormal PaidType field value is needed to set if abnormal call ticket code is numerical value 0 Setting abnormal call ticket code value is numerical value 4, and the ticket writing is written in original anomaly CDR file, further with the ticket MDN field value in record is critical field, searches correction with reference to the user record in user information database, if there is MDN word The identical ticket writing of segment value then corrects the PaidType field in abnormal ticket writing using the PaidType value in the record Value, into subsequent detection aligning step, if not finding the user record of identical MDN field, is directly entered subsequent detection Aligning step.

The detection correction of chargeable session duration field: being the ticket writing of numerical value 2 or 3 to Acct-Status-Type field, Carry out the detection of chargeable session duration field value number format and value range.Chargeable session duration field value format should be non-negative Decimal number word format, introducing intermediate variable chargeable session event time is poor (default value 0), with variable Min_Event_Time The Event Time field value for identifying timing front end ticket in ticketing session sequence, when intermediate variable chargeable session event Between poor calculation formula are as follows: chargeable session event time difference=Event Time-Min_Event_Time.If detected Acct_Session_Time field format exception or Acct_Session_Time value are equal to numerical value 0 and intermediate variable chargeable session Event time difference is one of the abnormal conditions of positive number, if abnormal call ticket code is numerical value 0, it is numerical value that abnormal call ticket code value, which is arranged, 5, ticket writing is written in original anomaly CDR file, and Acct_Session_Time value is corrected to intermediate variable Chargeable session event time is poor, into subsequent detection aligning step.

Network flow detection correction: (user sends Data Octet Count (Origination) in detection ticket record Byte number), Data Octet Count (Termination) (byte number for being sent to user), Acct-Output- Four Gigawords (uplink traffic overturning number), Acct-Input-Gigawords (downlink traffic overturning number) field values Number format, and be based on the calculated uplink network flow of aforementioned four field value and downlink network flow.Ticket writing Middle Data Octet Count (Origination), Data Octet Count (Termination), Acct-Output- The format of tetra- field values of Gigawords and Acct-Input-Gigawords should be non-negative ten's digit；Uplink network Flow rate calculation formula :+Acct-Output-Gigawords × 4 × 1024 Data Octet Count (Origination) × 1024 × 1024, downlink network flow rate calculation formula: Data Octet Count (Termination)+Acct-Input- Gigawords×4×1024×1024×1024.According to CDMA2000 call charge service specification, same chargeable session process is generated Ticket writing, counting equipment is recorded in ticket writing by the way of flux cumulating, the posterior ticket writing of timing it is upper Row network flow should be greater than or equal to the preceding ticket writing of timing uplink network flow, under the posterior ticket writing of timing Row network flow should be greater than or equal to the preceding ticket writing of timing downlink network flow.

If detecting Data Octet Count (Origination) field format, Acct-Output-Gigawords At least one of field format or uplink network flow three are abnormal, if abnormal call ticket code is numerical value 0, need to be arranged words Single exception code value is 6, and ticket writing is written in original anomaly CDR file, the byte number and upstream that user is sent The value of amount overturning number is corrected to the corresponding field value in ticket sequence in previous moment ticket writing.

If there is Data Octet Count (Termination) field format, Acct-Input- in detection At least one of Gigawords field format and downlink network flow three are abnormal, if abnormal call ticket code is numerical value 0, need It is 6 that abnormal call ticket code value, which is arranged, and ticket writing is written in original anomaly CDR file, will be sent to the byte of user The value that number, downlink traffic overturn number is corrected to the corresponding field value in ticket sequence in the ticket writing of previous moment, enters Subsequent detection aligning step.

It activates duration field detection correction: being 2 for Acct-Status-Type field value in ticketing session sequence Or 3 ticket writing, detection activation duration Active Time field value number format and value range, in CDMA2000 net Active Time field value format is non-negative decimal number word format in network.Introduce intermediate variable correction activation duration (default value 0), intermediate variable preferably to be corrected activation duration and is set to the nothing that the corresponding wireless access network equipment of this internet records generates Duration of eating dishes without rice or wine in line ticket writing, can also be greater than 0 ticket preferably to network flow, and high-ranking officers' positive actuation duration is set to Acct_Session_Time field value.If detecting that Active Time field value format is abnormal, meeting Acct_Session_ Time field value is equal to 0 and intermediate variable correction activates duration to be less than chargeable session sequence previous moment for positive number and activation duration One of abnormal scene of three kinds of activation duration in ticket, if abnormal call ticket code is numerical value 0, by abnormal call ticket code value It is set as numerical value 7, ticket writing is written in original anomaly CDR file, if previous moment in ticketing session sequence Ticket writing in activation when a length of 0, then by Active Time field be corrected to intermediate variable correction activation duration, it is no Then using the activation duration in ticketing session sequence in the ticket writing of previous moment as the corrected value of the currently active duration.

The ticket writing detection correction that entire ticketing session sequence is completed by above-mentioned steps, for detecting exception simultaneously Entire sequence whole ticket writing need to be output in abnormal correction ticket writing file by simple sequence after being corrected.

It chronologically successively carries out in above-mentioned all types of detection correction course, to guarantee that detection is comprehensive and correcting exhaustive, When detecting that ticket writing has the exception of some type, after abnormal call ticket code value is arranged, except abnormal ticket writing is defeated Out into original anomaly CDR file, the abnormal ticket writing of current type is corrected.To the ticket writing after correction after It is continuous to carry out other kinds of abnormality detection and correction until finishing, complete the inspection of all records in entire ticketing session sequence It surveys and corrects, it is literary that the whole records finally corrected in obtained ticket chargeable session sequence are output to abnormal correction ticket writing In part.

Based on same thinking, the present invention also provides a kind of charging bills to record detection means for correcting, is that can use Above-mentioned ticket writing detection bearing calibration carries out the entity device of detection correction to ticket writing, as shown in fig. 6, including obtaining list Member 601, correction 604 4 reference unit 602, pretreatment unit 603 and correction processing unit parts.Its acquiring unit 601 weeks Phase property from the data obtained in counting equipment or charging gateway or BOSS system in charging bill file, acquisition modes are Actively or passively.The data transmission about ticket writing that acquiring unit 601 will acquire to pretreatment unit 603 is gone It pre-processes again, establishes ticketing session sequence.Its pretreatment unit 603 carries out duplicate removal processing to the ticket writing got, Repeating ticket writing identification can determine according to the combination of different ticket fields, according to the pass between ticket writing during chargeable session Connection property, ticket writing charging identifier combined field (MDN, IMSI, Correlation ID, Account Session ID) with And sequential relationship combined field (Event Time, Acct-Status-Type) establishes ticketing session sequence, traversal is all Ticket writing is formed from the ticket chargeable session sequential structure for starting ticket writing, interim UDR, which records, terminates ticket is constituted, The ticket chargeable session sequence of generation is supplied to correction processing unit 604.

It corrects reference unit 602 for establishing user base reference information library, and above-mentioned user information database, which has recorded, to be used for The reference data of abnormal ticket writing field, correction reference unit 602 and 604 data interaction of correction processing unit are corrected, in school It is supplied to correction reference data during just, the data source in above-mentioned reference information library can preferably use external data interface The user data such as operator ODS/CRM system (operator data warehousing and storage system/CRM system) is obtained, or Person can be using the effective word segment value in ticket writing as data source.

Its correction processing unit 604 contains the program of detection correction, which is compiled by detection bearing calibration above It writes, abnormal code field, detection exception field is added to every ticket writing, identify abnormal code field, correction ticket writing, will be had The ticket writing of exception field and the ticket writing after correction export preservation respectively, and generate ticket detection correction statistics report according to this Table.Correction processing unit 604 to each ticket writing carry out terminate ticket integrality, Subscriber Number field, user IMSI field, Charge type field, chargeable session duration field, network flow and the detection correction for activating seven Exception Types of duration field, school The initial assignment that abnormal code field is arranged in positive processing unit is numerical value 0, and is assigned according to the exception field classification of type of ticket writing It is worth abnormal code field, the corresponding abnormal code field of seven Exception Types is followed successively by numerical value 1 to 7.The tool of each Exception Type Correction course is surveyed in physical examination can be recorded the embodiment progress of detection bearing calibration by above-mentioned charging bill, and which is not described herein again.

This charging bill record detection means for correcting can be used as insertion processing apparatus and be arranged in AAA equipment or billing network It closes in equipment or BOSS system, individualism can also be independently arranged.When it is embedded in AAA equipment, to every ticket note Record carry out detection correction on the basis of, BOSS system acquisition correction after ticket writing and do not detect abnormal ticket writing, And charging processing is carried out according to charging regulation.

When it is embedded in BOSS system, on the basis of carrying out detection correction to every ticket writing, BOSS system application Charging regulation is to the ticket writing after correction and does not detect that abnormal ticket writing carries out charging processing.Charging bill file warp Charging bill is obtained after present apparatus detection correction process, by the online charging inventory generated to OCS online charging module and is somebody's turn to do Charging bill after detection correction process is checked, is produced and is checked file, is realized to mobile data online online charging processing The monitoring of process, relevant staff can check that file finds leakage meter, wrong the problems such as counting in time according to output.

On the basis of above-mentioned detection bearing calibration and device, a kind of ticket processing system can be established, except the charging of this case Ticket writing detects means for correcting 6, which further includes existing data gateway equipment 3, AAA equipment 2, BOSS system System server 4, operator's CRM/ODS system server 5, as shown in fig. 7, AAA equipment 2 and data gateway equipment 3 communicate to connect, BOSS system server 4 and AAA equipment 2 communicate to connect, charging bill record detection means for correcting 6 respectively with AAA equipment 2, BOSS system server 4, operator's CRM/ODS system server 5 communicate to connect.

AAA equipment 2, which is used to generate charging bill during user's online, records data, BOSS system server 4 and meter Nonsense unirecord detects the charging bill record data that means for correcting 6 obtains AAA equipment 2, charging bill record detection correction dress It sets 6 and correction is established with reference to user information database with operator's ODS/CRM system data source, construct ticketing session sequence, dialogue Ticket writing in single chargeable session sequence carries out abnormality detection and correction process, and output abnormality corrects ticket writing file, original Begin abnormal CDR file and ticket detection correction statistical report form.4 acquisition abnormity of BOSS system server corrects ticket writing file Data are recorded with the charging bill that AAA equipment 2 generates, do not detect to the ticket writing after correction and exception using charging regulation Ticket writing carry out plan as a whole charging processing.

Claims

1. a kind of charging bill record detection bearing calibration, characterized by the following steps:

Step a: charging bill file, the charging bill file are obtained from counting equipment, charging gateway or BOSS system User's metering data that be user generate during terminating since chargeable session to chargeable session during online；

Step b: it establishes correction and refers to user information database, the correction is provider customer's letter with reference to the data in user information database The user bill record not comprising exception field for ceasing the user record in library and/or getting；

Step c: the ticket writing in duplicate removal charging bill file, on time with the ticket writing during user's chargeable session Sequence and charging state relation relationship generate a ticketing session sequence；

Step d: detecting whether each ticket writing in the ticketing session sequence contains exception field, will contain abnormal word The ticket writing of section is output in an original anomaly CDR file, according to the business between ticket writing in ticketing session sequence Logic rules and the exception field that the Data correction ticket writing in user information database is referred to by comparing correction, after correction Ticket chargeable session sequence be output in an abnormal correction ticket writing file；

Further include step c1 after the step c: abnormal call ticket code field being increased to every ticket writing and assigns initial value；

The process of the exception field of the positive ticket writing of step d lieutenant colonel includes: according to the exception field type of ticket writing point Class assignment exception code field, different exception field types is identified with different exception codes；

The initial assignment of the abnormal code field of the ticket writing is numerical value 0, the ticket writing in ticketing session sequence Detection correction sequence, which is followed successively by, terminates the correction of ticket integrity detection, Subscriber Number field detection correction, the inspection of user's IMSI field It surveys correction, charge type field detection correction, chargeable session duration field detection correction, exception of network traffic detection correction and swashs Duration field detection correction living, the corresponding abnormal code field of the Exception Type of the sequence are followed successively by numerical value 1 to 7；

Terminate ticket integrity detection correction course are as follows: the ticket writing of last timing is in detection ticket chargeable session sequence Charging mode field, if the value of charging mode field is abnormal, the ticket exception code that the ticket writing is arranged is numerical value 1, will The ticket writing is output in original anomaly CDR file, and the value of the charging mode field of the ticket writing is corrected to expression words The numerical value of unijunction beam；

Subscriber Number field detects correction course are as follows: the number format and digit of detection Subscriber Number field, if user number Code field is abnormal, and under the premise of the abnormal code field of ticket writing is numerical value 0, then it is numerical value 2 that abnormal call ticket code value, which is arranged, and The ticket writing is written in original anomaly CDR file, to represent the IMSI of international mobile subscriber identity in ticket writing Field is critical field, searches correction with reference to the user record in user information database, if there is the identical note of IMSI field value Record then corrects the user number code word in this ticket writing with reference to the Subscriber Number field value in user information database record using correction Section；

User's IMSI field detects correction course are as follows: the number format and digit order number of detection international mobile subscriber identity field Number under the premise of the abnormal code field of ticket writing is numerical value 0, is then arranged if international mobile subscriber identity field is abnormal Abnormal call ticket code value is numerical value 3, and the ticket writing is written in original anomaly CDR file, with the user in ticket writing Number character segment value is critical field, searches correction with reference to the user record in user information database, if there is Subscriber Number field It is worth identical record, then is corrected in the ticket writing using correction with reference to the international mobile subscriber identity value in user information database International mobile subscriber identity field；

Charge type field detects correction course are as follows: the number format and value range of detection charge type field, if charging class Type-word segment value is abnormal, and under the premise of the abnormal code field of ticket writing is numerical value 0, then it is numerical value 4 that abnormal call ticket code value, which is arranged, And the ticket writing is written in original anomaly CDR file, is key with the Subscriber Number field value in the ticket writing Field, searching correction then makes with reference to the user record in user information database if there is the identical record of Subscriber Number field value The charge type field value in the ticket writing is corrected with reference to the charge type field value in user information database with correction；

Chargeable session duration field detects correction course are as follows: the number format and value model of detection chargeable session duration field value It encloses, if chargeable session duration field value is abnormal, under the premise of the abnormal code field of ticket writing is numerical value 0, then ticket is set Abnormal code value is numerical value 5, which is written in abnormal correction ticket writing file, and by long word when chargeable session Segment value is corrected to the dialog events time difference, the dialog events time difference be current ticket writing the dialog events time be in The difference of the dialog events time of the ticket writing of timing front end in ticketing session sequence；

Network flow detects correction course are as follows: be sent in detection ticket record the byte number of user, Client-initiated byte number, Uplink traffic overturns the number format of number and downlink traffic overturning four fields of number, and is calculated based on this four field values Upstream data flow and downlink data flow out, if detecting that Client-initiated byte number field format, uplink traffic turn over Turn an at least exception in time field format and upstream data flow three, is numerical value in the abnormal code field of ticket writing Under the premise of 0, then it is 6 that abnormal call ticket code value, which is arranged, and the ticket writing is written in original anomaly CDR file, by user The value of byte digital section and uplink traffic the overturning time field of initiation is corrected to previous moment in ticketing session sequence Respective value in ticket writing；If detecting the byte number field format, the downlink traffic overturning time field that are sent to user At least one of format and downlink data flow three are abnormal, under the premise of the abnormal code field of ticket writing is numerical value 0, then It is 6 that abnormal call ticket code value, which is arranged, and the ticket writing is written in original anomaly CDR file, will be sent to the byte of user The value that digital section, downlink traffic overturn time field is corrected in ticketing session sequence in the ticket writing of previous moment Respective value；

Duration field is activated to detect correction course are as follows: interim UDR record and end ticket in detection ticket chargeable session sequence Number format, value range and the service logic rule of the activation duration field value of record, if activation duration field value is abnormal, Under the premise of the abnormal code field of ticket writing is numerical value 0, then numerical value 7 is set by abnormal call ticket code value, by the ticket writing It is written in original anomaly CDR file, if the activation duration in ticketing session sequence in the ticket writing of previous moment It is 0, then the duration of eating dishes without rice or wine in the user radio ticket for corresponding equipment for radio access network record that this is surfed the Internet is as working as The corrected value of preceding activation duration, or using the chargeable session duration in ticket writing as the activation duration of current ticket writing Corrected value, otherwise using the activation duration in ticketing session sequence in the ticket writing of previous moment as current ticket writing Activation duration corrected value.

2. a kind of charging bill record detection bearing calibration according to claim 1, it is characterised in that: in the step d The exception field type of ticket writing includes the complete sexual abnormality of end ticket, Subscriber Number field is abnormal, user's IMSI field is different Often, charge type field exception, chargeable session duration field exception, exception of network traffic, activation duration field are abnormal.

3. a kind of charging bill record detection bearing calibration according to claim 1 or 2, it is characterised in that: further include step Step e after rapid d: according to original anomaly CDR file and abnormal correction ticket writing file generated ticket detection correction statistics Report.

4. a kind of charging bill record detection means for correcting, it is characterised in that: including acquiring unit, correction reference unit, pre- place Manage unit and correction processing unit, correction reference unit and correction processing unit data interaction, the pre- place of acquiring unit output connection Manage unit, pretreatment unit output connection correction processing unit, in which:

Acquiring unit is counting equipment, meter in the charging bill file for periodically acquiring or receiving charging bill file Take the charging bill file in gateway or BOSS system；

It corrects reference unit and refers to user information database for establishing correction, correction is operator with reference to the data in user information database User record in user information database or the user bill record not comprising exception field to get；

Pretreatment unit will be remembered for the ticket writing in duplicate removal processing charging bill file with the ticket in a chargeable session Record is chronologically and charging state relation relationship generates one using ticket writing as the ticket chargeable session sequence of element；

Correction processing unit adds abnormal code field to each ticket writing of ticket chargeable session sequence, and detection has abnormal word The ticket writing of section, the ticket writing with exception field is saved in original anomaly CDR file, according to ticketing meeting It talks about the service logic rule in sequence between ticket writing and refers to user information database data with the correction in correction reference unit The exception field of interaction correction ticket writing, all ticket writings in the ticket chargeable session sequence after correction is saved in different Often in correction ticket writing file, and generated by the data in original anomaly CDR file and abnormal correction ticket writing file Ticket detection correction statistical report form；

The correction processing unit carries out each ticket writing to terminate ticket integrality, Subscriber Number field, user's IMSI word Section, charge type field, chargeable session duration field, network flow and the detection school for activating seven Exception Types of duration field Just, it is numerical value 0 that the initial assignment of abnormal code field, which is arranged, in correction processing unit, and according to the exception field type of ticket writing point Class assignment exception code field, the corresponding abnormal code field of seven Exception Types are followed successively by numerical value 1 to 7；

Terminate ticket integrity detection correction course are as follows: the ticket writing of last timing is in detection ticket chargeable session sequence Charging mode field, if the value of charging mode field is abnormal, under the premise of the abnormal code field of ticket writing is numerical value 0, The ticket exception code that the ticket writing is then arranged is numerical value 1, which is output in original anomaly CDR file, by this The value of the charging mode field of ticket writing is corrected to the numerical value for indicating that ticket terminates；

5. a kind of ticket processing system, including data gateway equipment, AAA equipment, BOSS system server, operator CRM/ODS System server, AAA equipment and data gateway equipment communicate to connect, and BOSS system server and AAA equipment communicate to connect, special Sign is: further including charging bill record detection means for correcting as claimed in claim 4, the charging bill record detection school Equipment is communicated to connect with AAA equipment, BOSS system server, operator's CRM/ODS system server respectively.