CN105050068A

CN105050068A - Billing bill recording, detection, and correction method, apparatus, and bill processing system

Info

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

Abstract

The invention relates to a billing bill recording, detection, and correction method. The method includes four steps: acquiring billing bill files, establishing a correction reference user information database, generating bill billing conversation sequences, and detecting abnormal fields in bill records. The invention also relates to a billing bill recording, detection, and correction apparatus and a bill processing system. According to the method, the apparatus, and the system, problems of abnormal fields in the bill records, missing and incomplete bill, and repeated bills in the bill records are solved, the repeated bill records can be removed, the bill billing conversation sequences and the correction reference user information database are established according to the billing correlation relation between the bill records in the billing conversation process, the detection and the correction of the bill integrity and abnormal fields in the bill records are developed and finished aiming to the bill billing conversation sequences, the accuracy and the effectiveness of billing bill data of mobile Internet are improved, the accuracy and the reliability of the calculation of the user Internet cost are improved, and the benefits of operators and users are guaranteed.

Description

A kind of charging bill record detects bearing calibration, device and ticket treatment system

Technical field

The present invention relates to communication technical field, specifically a kind of charging bill record detects bearing calibration, device and ticket treatment system.

Background technology

Along with mobile communication network technology development, the mobile data network of high speed Internet access business can be provided to obtain widespread deployment and application.CDMA2000 network, as the 3G mobile communication technology of main flow, can provide the mobile Internet access business of 1X/EV-DO two kinds of patterns for user, meet the business demand of people's mobile Internet access.The framework of CDMA2000 network and charge system as shown in Figure 1, when user initiates business of networking, by the RAN1 (Radioaccessnetwork of CDMA2000, Radio Access Network) be linked into packet core network and comprise: data gateway equipment 3 and AAA equipment 2, complete after by user authentication authentication at core network, core network device sets up user PPP session, and be user's distributing IP address, the upper network process of AAA equipment 2 couples of users carries out charging, use in the process of business of networking user, AAA equipment 2 can according to user's charging property and session status, prepaid user is realized to the function of online charging, offline charging function is realized to postpaid service user.AAA equipment 2 is mutual with BOSS system server 4, common completing user charging.

AAA equipment produces user and to surf the Net complete ticket writing, and ticket writing comprises pre-payment ticket writing and rear paying ticket writing, outputs to charging bill file.Ticket writing is made up of multiple territory (record field), mainly comprises user's business of networking information, the network information and traffic carrying capacity and uses information (data on flows, time long data).AAA equipment, according to user's charging property, adopts two kinds of business processing flows to realize customer billing function: prepayment service flow process, post payment service flow process.Prepayment service processing procedure is: for prepaid user in upper network process, AAA equipment is by online charging agreement and Online Charging System real-time, interactive user Internet data, the online charging module of Online Charging System to conversate management to user, the operations such as charging control, and according to operating result and AAA equipment mutual, control user's business of networking to use, AAA equipment can produce pre-payment online ticket writing and be written to CDR file on user in network process.Offline charging business procession is: on postpaid service user in network process, and AAA equipment produces to pay ticket writing after user and writes CDR file, and BOSS system acquisition AAA CDR file carries out charging process.The ticket writing that AAA equipment generates adopts the detailed single form of identical ticket, distinguishes according to the charge type field value in pre-payment and rear paying ticket writing.

According to CDMA2000 mobile network charging specification, ticketing terminates ticket and to surf the Net the basis that rates ground and expense calculate as user.The accuracy of ticket writing charging bill data, Usefulness Pair are in guaranteeing that operator's mobile data services business revenue is significant.According to previously described two kinds of call charge service processing procedures:

For mobile Internet access online charging business, AAA equipment and Online Charging System real-time, interactive, Online Charging System completes the processing procedures such as wholesale price, traffic carrying capacity inverse, management of balance, generate online keep cost order record to comprise: business information, traffic information, cost information, simultaneously the AAA equipment online charging ticket writing that can produce.

For offline charging business, AAA equipment generates offline charging CDR file, and BOSS system acquisition AAA equipment generates charging bill file, completes charging handling process, generate user's billing invoice, complete the business revenue of mobile data services according to end ticket writing.

For online charging business, existing charging bill auditing method has: check the online charging inventory record and user's ticket writing that are generated by Online Charging System, otherness between the statistics of comparison above-mentioned " online charging inventory record " and " user's ticket writing ", thus the error that may occur in discovery charging, mark error log, generate and check report data.For the online charging process of duration based accounting, there is the process surf time to overlap the method for charging bill, reject the part of time-interleaving, merge generation new ticket.

For offline charging business, existing method is that the transmitting procedure of the CDR file that the AAA equipment original to BOSS system acquisition generates checks correction, ensures the correctness that CDR file collection transmits and verification property.Check code is increased to CDR file, after each file collection transmits, carry out automatic Verification according to the check code of file to this file to check, system checks the CDR file and collection log information that collect, check following content by CDR file: collection point, file name, file size, daily or the time period check quantity of documents, file total bytes etc.System is progressively formed based on collection statistical data analysis according to the file gathered and daily record, and principal statistical key element comprises: collection point, switch, collection period, collection file number, collection file size.Simultaneously this information gathered just is carried out contrast with history Information Monitoring and is verified by acquisition system per a period of time, formation variance analysis, and can think acquisition abnormity for the image data exceeding certain value, formation form, for confirmation.

From analyzing above, the charging bill data that AAA equipment generates are as the data foundation of mobile data services user charging, the Original CDR that existing metering data handling process and auditing method generate using network billing equipment, as basis and the foundation of checking process, can not remove the field and the numerical value that change and revise the call bill data self generated.Along with the development of development of Mobile Internet technology and terminal technology, the kind of business of networking, application scenarios and user's internet behavior all become more and more various, and wireless network overlay environment (as covering scene such as high ferro, track traffic, tunnel, bridges) also becomes and becomes increasingly complex simultaneously.The interaction of the factors such as network, user, business can produce material impact to network quality and performance, the further quality affecting network data and generate, the factors such as abnormal in operation flow, signaling message is lost, counter data is abnormal, timer is extremely overtime, magnetic disc i/o is abnormal talk with unirecord integrality, validity has an impact, and following abnormal conditions appear in the call bill data causing AAA equipment to generate:

1. ticket writing is imperfect, lacks ticket writing, loses the ticket writing that should generate in part online chargeable session process, as started ticket, interim UDR or terminating ticket.

2. occur many and repeat identical ticket writing, in CDR file, occur the ticket writing that many ticket field contents are identical.

3. the one or more field values in ticket writing occur abnormal, and as field value does not meet equipment specification requirement, 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, can have influence on the validity of call bill data, accuracy and reliability, and then affect accuracy and the validity of charging result, cause the business revenue of mobile data services to be protected.

Summary of the invention

The object of the present invention is to provide a kind of charging bill record to detect bearing calibration, device and ticket treatment system, it is for solving the problem of field exception in ticket writing.

Technical scheme of the present invention is as follows:

A kind of charging bill record detects bearing calibration, and it comprises the steps:

Step a: obtain charging bill file from counting equipment or charging gateway or BOSS system, described charging bill file is the user's metering data generated in the process that terminates to chargeable session from chargeable session in upper network process of user.

Step b: set up calibration reference user information database, the user's ticket writing not comprising exception field that the data in described calibration reference user information database are user record in provider customer's information bank and/or get.

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

Steps d: detect each ticket writing in described ticketing session sequence and whether contain exception field; ticket writing containing exception field is outputted in an original anomaly CDR file; according to the service logic rule in ticketing session sequence between ticket writing and the exception field by the Data correction ticket writing in comparison calibration reference user information database, the ticketing session sequence after correcting is outputted in an abnormal correction ticket writing file.

Further, also step c1 is comprised after described step c: abnormal call ticket code field is increased to every bar ticket writing and composes initial value; The process of the unirecord exception field of described steps d lieutenant colonel means comprises: according to the exception field classification of type assignment exception code field of ticket writing, identify different exception field types by different exception codes.

Further, in described steps d, the exception field type of ticket writing comprises end ticket integrality exception, Subscriber Number field exception, user IMSI field exception, charge type field exception, chargeable session duration field exception, exception of network traffic, activation duration field extremely.

Further, the initial assignment of the exception code field of described ticket writing is numerical value 0, the detection correction of the ticket writing in ticketing session sequence is sequentially followed successively by the correction of end ticket integrity detection, Subscriber Number field detection correction, user 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, and the exception code field that the Exception Type of this order is corresponding is followed successively by numerical value 1 to 7.

Further; terminating ticket integrity detection trimming process is: detect the charging mode field being in the ticket writing of last sequential in ticketing session sequence; if the value of charging mode field is abnormal; the abnormal call ticket code then arranging this ticket writing is numerical value 1; this ticket writing is outputted in original anomaly CDR file, the value of the charging mode field of this ticket writing is corrected to the numerical value representing that ticket terminates.

Further, Subscriber Number field detects trimming process: the number format and the digit that detect Subscriber Number field, if Subscriber Number field is abnormal, under the exception code field of ticket writing is the prerequisite of numerical value 0, then arranging abnormal call ticket code value is numerical value 2, and this ticket writing is written in original anomaly CDR file, to represent the IMSI field of international mobile subscriber identity in ticket writing for critical field, search the user record in calibration reference user information database, if there is the record that IMSI field value is identical, Subscriber Number field value then in use calibration reference user information database record corrects the Subscriber Number field in this ticket writing.

Further, user IMSI field detects trimming process: the number format and the digit that detect international mobile subscriber identity field, if international mobile subscriber identity field is abnormal, under the exception code field of ticket writing is the prerequisite of numerical value 0, then arranging abnormal call ticket code value is numerical value 3, and this ticket writing is written in original anomaly CDR file, with the Subscriber Number field value in ticket writing for critical field, search the user record in calibration reference user information database, if there is the record that Subscriber Number field value is identical, international mobile subscriber identity value then in use calibration reference user information database corrects the international mobile subscriber identity field in this ticket writing.

Further, charge type field detects trimming process: the number format and the span that detect charge type field, if charge type field value is abnormal, under the exception code field of ticket writing is the prerequisite of numerical value 0, then arranging abnormal call ticket code value is numerical value 4, and this ticket writing is written in original anomaly CDR file, with the Subscriber Number field value in this ticket writing for critical field, search the user record in calibration reference user information database, if there is the record that Subscriber Number field value is identical, charge type field value then in use calibration reference user information database corrects the charge type field value in this ticket writing.

Further, chargeable session duration field detects trimming process: the number format and the span that detect chargeable session duration field value, if chargeable session duration field value is abnormal, under the exception code field of ticket writing is the prerequisite of numerical value 0, then arranging abnormal call ticket code value is numerical value 5, this ticket writing is written in abnormal correction ticket writing file, and chargeable session duration field value is corrected to the dialog events time difference, the described dialog events time difference is the dialog events time of current ticket writing and the difference of dialog events time being in sequential ticket writing foremost in ticketing session sequence.

Further, network traffics detect trimming process: detect the byte number sending to user in ticket writing, Client-initiated byte number, the number format of uplink traffic upset number of times and downlink traffic upset number of times four fields, and the upstream data flow to calculate based on these four field values and downlink data flow, if detect Client-initiated byte number field format, an exception is had at least in uplink traffic upset time field form and upstream data flow three, under the exception code field of ticket writing is the prerequisite of numerical value 0, then arranging abnormal call ticket code value is 6, and by this ticket writing write original anomaly CDR file, the value of Client-initiated byte number field and uplink traffic upset time field is corrected to respective value in the ticket writing of previous moment in ticketing session sequence, if detect send to user byte number field format, downlink traffic upset time field form and downlink data flow three at least one exception, under the exception code field of ticket writing is the prerequisite of numerical value 0, then arranging abnormal call ticket code value is 6, and by this ticket writing write original anomaly CDR file, the value sending to the byte number field of user, downlink traffic to overturn time field is corrected to the respective value in the ticket writing of previous moment in ticketing session sequence.

Further, activating duration field detection trimming process is: the number format of the interim UDR record in detection ticketing session sequence and the activation duration field value of end ticket writing, span and service logic rule, if it is abnormal to activate duration field value, under the exception code field of ticket writing is the prerequisite of numerical value 0, then abnormal call ticket code value is set to numerical value 7, this ticket writing is written in original anomaly CDR file, if in ticketing session sequence previous moment ticket writing in activation duration be 0, so using the corrected value of duration as current activation duration of eating dishes without rice or wine in the user radio ticket of equipment for radio access network record corresponding for this online, or using the corrected value of the chargeable session duration in ticket writing as the activation duration of current ticket writing, otherwise using the corrected value of the activation duration in the ticket writing of previous moment in ticketing session sequence as the activation duration of current ticket writing.

Further, also comprise steps d after step e: detect correct statistical report form according to original anomaly CDR file and the abnormal ticket writing file generated ticket that corrects.

A kind of charging bill record detects means for correcting, it comprises acquiring unit, calibration reference unit, pretreatment unit and correction processing unit, calibration reference unit and correction processing unit data interaction, acquiring unit exports and connects pretreatment unit, pretreatment unit exports and connects correction processing unit, wherein: acquiring unit is used for periodically obtaining or receiving charging bill file, is the charging bill file in counting equipment, charging gateway or BOSS system in described charging bill file, calibration reference unit is used for setting up calibration reference user information database, and the data in calibration reference user information database are the user record in provider customer's information bank or the user's ticket writing not comprising exception field for getting, pretreatment unit is used for the ticket writing in duplicate removal process charging bill file, by with the ticket writing in a chargeable session chronologically and charging state relation relation generate the ticketing session sequence that take ticket writing as element, the each ticket writing of correction processing unit to ticket chargeable session sequence sets up exception code field, detect the ticket writing with exception field, the ticket writing with exception field is saved in original anomaly CDR file, according in ticketing session sequence between ticket writing service logic rule and correct the exception field of ticket writing with the calibration reference user information database data interaction in calibration reference unit, all ticket writings in ticketing session sequence after correction are saved in abnormal correction ticket writing file, and correct statistical report form by original anomaly CDR file and the abnormal data genaration ticket detection corrected in ticket writing file.

Further, described correction processing unit corrects the detection that each ticket writing carries out terminating ticket integrality, Subscriber Number field, user IMSI field, charge type field, chargeable session duration field, network traffics and activation duration field seven Exception Types, the initial assignment that correction processing unit arranges exception code field is numerical value 0, and according to the exception field classification of type assignment exception code field of ticket writing, the exception code field that described seven Exception Types are corresponding is followed successively by numerical value 1 to 7.

Further; terminating ticket integrity detection trimming process is: detect the charging mode field being in the ticket writing of last sequential in ticketing session sequence; if the value of charging mode field is abnormal; under the exception code field of ticket writing is the prerequisite of numerical value 0; the abnormal call ticket code then arranging this ticket writing is numerical value 1; this ticket writing is outputted in original anomaly CDR file, the value of the charging mode field of this ticket writing is corrected to the numerical value representing that ticket terminates.

Subscriber Number field detects trimming process: the number format and the digit that detect Subscriber Number field, if Subscriber Number field is abnormal, under the exception code field of ticket writing is the prerequisite of numerical value 0, then arranging abnormal call ticket code value is numerical value 2, and this ticket writing is written in original anomaly CDR file, to represent the IMSI field of international mobile subscriber identity in ticket writing for critical field, search the user record in calibration reference user information database, if there is the record that IMSI field value is identical, Subscriber Number field value then in use calibration reference user information database record corrects the Subscriber Number field in this ticket writing.

User IMSI field detects trimming process: the number format and the digit that detect international mobile subscriber identity field, if international mobile subscriber identity field is abnormal, under the exception code field of ticket writing is the prerequisite of numerical value 0, then arranging abnormal call ticket code value is numerical value 3, and this ticket writing is written in original anomaly CDR file, with the Subscriber Number field value in ticket writing for critical field, search the user record in calibration reference user information database, if there is the record that Subscriber Number field value is identical, international mobile subscriber identity value then in use calibration reference user information database corrects the international mobile subscriber identity field in this ticket writing.

Charge type field detects trimming process: the number format and the span that detect charge type field, if charge type field value is abnormal, under the exception code field of ticket writing is the prerequisite of numerical value 0, then arranging abnormal call ticket code value is numerical value 4, and this ticket writing is written in original anomaly CDR file, with the Subscriber Number field value in this ticket writing for critical field, search the user record in calibration reference user information database, if there is the record that Subscriber Number field value is identical, then use in calibration reference user information database charge type field value correct charge type field value in this ticket writing.

Chargeable session duration field detects trimming process: the number format and the span that detect chargeable session duration field value, if chargeable session duration field value is abnormal, under the exception code field of ticket writing is the prerequisite of numerical value 0, then arranging abnormal call ticket code value is numerical value 5, this ticket writing is written in abnormal correction ticket writing file, and chargeable session duration field value is corrected to the dialog events time difference, the described dialog events time difference is the dialog events time of current ticket writing and the difference of dialog events time being in sequential ticket writing foremost in ticketing session sequence.

Network traffics detect trimming process: detect the byte number sending to user in ticket writing, Client-initiated byte number, the number format of uplink traffic upset number of times and downlink traffic upset number of times four fields, and the upstream data flow to calculate based on these four field values and downlink data flow, if detect Client-initiated byte number field format, an exception is had at least in uplink traffic upset time field form and upstream data flow three, under the exception code field of ticket writing is the prerequisite of numerical value 0, then arranging abnormal call ticket code value is 6, and by this ticket writing write original anomaly CDR file, the value of Client-initiated byte number field and uplink traffic upset time field is corrected to respective value in the ticket writing of previous moment in ticketing session sequence, if detect send to user byte number field format, downlink traffic upset time field form and downlink data flow three at least one exception, under the exception code field of ticket writing is the prerequisite of numerical value 0, then arranging abnormal call ticket code value is 6, and by this ticket writing write original anomaly CDR file, the value sending to the byte number field of user, downlink traffic to overturn time field is corrected to the respective value in the ticket writing of previous moment in ticketing session sequence.

Activating duration field detection trimming process is: the number format of the interim UDR record in detection ticketing session sequence and the activation duration field value of end ticket writing, span and service logic rule, if it is abnormal to activate duration field value, under the exception code field of ticket writing is the prerequisite of numerical value 0, then abnormal call ticket code value is set to numerical value 7, this ticket writing is written in original anomaly CDR file, if in ticketing session sequence previous moment ticket writing in activation duration be 0, so using the corrected value of duration as current activation duration of eating dishes without rice or wine in the user radio ticket of equipment for radio access network record corresponding for this online, or using the corrected value of the chargeable session duration in ticket writing as the activation duration of current ticket writing, otherwise using the corrected value of the activation duration in the ticket writing of previous moment in ticketing session sequence as the activation duration of current ticket writing.

A kind of ticket treatment system, it comprises data gateway equipment, AAA equipment, BOSS system server, operator CRM/ODS system server, AAA equipment is connected with data gateway devices communicating, BOSS system server is connected with AAA devices communicating, it also comprises charging bill record and detects means for correcting, and described charging bill record detects means for correcting and communicates to connect with AAA equipment, BOSS system server, operator CRM/ODS system server respectively.

A kind of charging bill record provided by the invention detects bearing calibration, device and ticket treatment system, abnormal for the ticket writing field existed in ticket writing, ticket lacks problem that is imperfect and ticket repetition, can duplicate removal ticket writing, according to the charge associated relation in chargeable session process between ticket writing, build ticketing session sequence, for ticketing session sequence, carry out and terminate ticket integrality and ticket writing field abnormality detection and correction, improve accuracy and the validity of mobile Internet access charging bill data, improve accuracy and the reliability of the calculating of user's expenses of surfing Internet simultaneously, also the interests of operator and user have been ensured.

Accompanying drawing explanation

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

A kind of ticket writing that Fig. 2 provides for the embodiment of the present invention detects bearing calibration schematic flow sheet;

The schematic diagram of the calibration reference user information database that Fig. 3 provides for the embodiment of the present invention;

The schematic diagram of the ticketing session sequential structure that Fig. 4 provides for the embodiment of the present invention;

The detection correcting process precedence diagram of a kind of ticket writing that Fig. 5 provides for the embodiment of the present invention;

The system construction drawing of a kind of station message recording detection means for correcting that Fig. 6 provides for the embodiment of the present invention;

The system construction drawing of a kind of ticket treatment system that Fig. 7 provides for the embodiment of the present invention.

Embodiment

Below in conjunction with drawings and Examples, the invention will be further described.

User once goes up in network process, AAA equipment can set up the chargeable session process collection user metering data of user, AAA equipment is that the chargeable session of each user distributes a unique identification by CorrelationID (association identification), AccountSessionID (chargeable session mark) two field combination, primary charging session may generate many ticket writings, and these station message recordings may export in different charging bill files.There is service logic relevance with many ticket writings generated in a chargeable session process in user, these service logic relevances are the important analysis bases for estimation as ticket writing loss, ticket field exception in record generation time, ticketing state, network traffics, activation duration, chargeable session duration etc.

Under above-mentioned foundation, present solution provides a kind of charging bill record and detect bearing calibration, as shown in Figure 2, it comprises the steps:

Step a: obtain charging bill file from counting equipment, charging gateway or BOSS system, described charging bill file is the user's metering data generated in the process that terminates to chargeable session from chargeable session in upper network process of user.

Step b: gather the user record in provider customer information bank and/or do not comprise user's ticket writing of exception field, set up calibration reference user information database.

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

In step a, ticket writing periodically outputs in charging bill file and preserves, charging bill file includes the ticket writing of pre-charge type and rear charge type, and the primary data content of ticket writing has: the data contents such as subscriber directory number, IMSI number, base station information, AAA address information, charge type, roaming type, business type selecting, uplink traffic, downlink traffic, charging duration, activation duration.The mode obtaining charging bill file can be from AAA equipment or charging gateway or BOSS system equipment active obtaining, also can be passive reception from the charging bill file of AAA equipment or charging gateway, can also be indirectly obtain from the other system that can obtain charging bill file, as ticket storage server.

Data in calibration reference user information database in step b, for correcting the part exception field part in ticket writing, the record field in calibration reference user information database should be corresponding with the field needing in ticket writing to correct.Calibration reference user information database can be updated periodically according to the update time of configuration, preferably upgrades in units of sky, guarantees consistency and the integrality of source of reference data.The method setting up calibration reference user information database can shown in reference diagram 3, can active obtaining or accept from the user data in the external user databases such as operator CRM/ODS system.When setting up or upgrade user's calibration reference information bank, need to judge user profile whether Already in storehouse, using Subscriber Number as keyword, scanning calibration reference user information database, if the user record having a same subscriber number is Already in storehouse, then upgrade user record in storehouse, otherwise the user record of a newly-built Subscriber Number.

In embodiments of the present invention, calibration reference user information database can be set up, the user data that stored reference corrects by usage data storehouse table.

Being that preliminary treatment is carried out to all ticket writings got in calibration cycle in step c, identifying the heavy list in ticket writing, after duplicate removal process, retain a ticket writing, guaranteeing in the call bill data of subsequent treatment without repeating ticket writing.Whether whether heavy single identification can be identical as heavy single foundation by comparing the whole field value of ticket writing, also can be identical as heavy single foundation according to the combination of Partial key field.User is once surfed the Net charging process, can according to the Subscriber Number in ticket writing, IMSI, CorrelationID, the charging identifier combined fields such as AccountSessionID identify heavy single, for user with the ticket writing generated in a chargeable session process, the sequential relationship in same chargeable session process between ticket writing is identified according to the EventTime (Event Timestamp) in ticket writing, Acct-Status-Type (charging state) two associations of field combination on time and charging state.The all ticket writings of same chargeable session after duplicate removal process generate a ticketing session sequence, as shown in Figure 4, complete ticketing session sequence is by starting ticket writing (starting CDR), several interim UDR record (middle CDR) and terminate ticket (terminating CDR) to record and form.

In steps d, following ticket writing is carried out to ticket chargeable session sequence and detects correction process: integrity detection and correction are carried out to the end ticket writing in chargeable session sequence, carries out the field abnormality detection correction process of every bar ticket writing further.The mainly field format detection of ticket writing field abnormality detection content, span detection and service logic relation detect, can correct according to the data of above-mentioned calibration reference user information database the exception field detected, or correct according to the service logic relation in ticket session sequence between ticket writing.

Trailer field mark such as the ticket writing of last sequential is not a field value representing conversation end, and so this field is considered as exception, and be corrected to the field value representing that chargeable session terminates, this corrects according to service logic relation.The and for example user of certain online set meal type, up-downgoing transfer of data is had in business of networking process, AAA equipment is surfed the Net in whole process user, by a series of ticket writings produced, namely the last item ticket produced for online finish time terminates ticket writing, in ticket writing, the business rule record network traffics of flux cumulating are adopted according to AAA equipment, if the up or downlink network flow that the ticket writing that in the up or downlink network flow-rate ratio chargeable session sequence that end ticket writing calculates, last charging point generates calculates is little, then be considered as exception of network traffic, need the flow field value relevant to this exception of network traffic types corrective detected, now, can from current ticketing session sequence, find up or that downlink network flow is maximum ticket writing, such as terminating ticket writing uplink traffic is 10MB, but the uplink traffic of the ticket writing of previous moment is 12MB in ticketing session sequence, the byte number so sent with the user in previous moment ticket writing and uplink traffic upset time field go to correct the corresponding field terminated in ticket writing, guarantee the uplink network flow terminating ticket writing, meet uplink network flow in primary charging conversation procedure and carry out record by the service logic rule of bulk billing system.The field value of similar this dynamic change in charging process, as flow, time long type field value occur abnormal, because factual data cannot reduce, the numerical value establishing factual data optimum based on the service logic rule in ticketing session sequence between ticket writing can only be passed through, with factual data of trying one's best to reach correction object.And for example detect in certain ticket writing that user IMSI field figure place is abnormal, so can search the identical user record of a Subscriber Number field by the Subscriber Number field in ticket writing from calibration reference user information database, correct the IMSI field of ticket by the IMSI field in this record.Thisly once going up the static types field value that can not change in network process, can by correcting according to the user record in calibration reference database.Therefore, the user record in calibration reference user information database upgrades more timely, more accurate according to the result that the data in calibration reference user information database correct.

After exception field detection correction process is carried out to the ticket writing in ticket chargeable session sequence; output calibration audit files, corrects audit files and should comprise following file: abnormal ticket writing file, original anomaly CDR file and the ticket of correcting detects correction statistical report form.

Be basic detect correction data unit with the ticketing session sequence of above-mentioned foundation; field abnormality detection and correction process are carried out to the ticket writing in ticket chargeable session sequence; to the abnormal ticket writing detected according to the different abnormal conditions detected; adopt the mode Classification and Identification that different exception codes is set; newly-increased exception code field; be convenient to specific aim correct and data statistics, and to compose initial value be that 0 expression is without exception.According to the value of exception code field, the exception for the type corrects, and the ticketing session sequence after correction outputs to abnormal correction in ticket writing file.Timing, the value of such as abnormal call ticket code field is numerical value 6, represents exception of network traffic, and timing has then directly pointed to the field representing network traffics in ticket writing, and which need not investigate one by one is exception field.According to the difference of Exception Type, part exception field needs to use the data in above-mentioned calibration reference user information database to correct, and part exception field corrects according to chargeable session service logic rule.Ticket writing before correcting is outputted in original anomaly CDR file, all ticket writings corrected in what happened latter list chargeable session sequence are outputted to abnormal correction ticket writing file.According to the data in original anomaly CDR file and the abnormal data corrected in ticket writing file, generate ticket detection and correct statistical report form, for operator's back-end data analysis.

The exception field type of usual ticket writing comprises end ticket integrality exception, Subscriber Number field exception, user IMSI field exception, charge type field exception, chargeable session duration field exception, exception of network traffic, activation duration field extremely.The detection correction order of ticket writing can be as shown in Figure 5, by logical order, carry out the correction of end ticket integrity detection, Subscriber Number field detection correction, user 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 successively to every bar ticket writing one by one, the exception code field that the Exception Type of this order is corresponding is set as numerical value 1 to 7 successively.Said sequence also can reset, and also can carry out separately field to wherein certain exception field type and detect and correct.The detection trimming process of each abnormal field type is as follows:

Terminate ticket integrity detection to correct: the integrality first detecting ticketing session sequence, check the charging mode field being in the ticket writing of last sequential in ticketing session sequence, detect this field value whether to identify this chargeable session and terminate, CDMA2000 network Acct-Status-Type field represents charging state, and its value is that numeral 2 represents conversation end.If Acct-Status-Type field value is 2, ticket writing is then without exception, enters subsequent detection aligning step.If the numerical value of Acct-Status-Type field is not 2; then ticketing session sequence is imperfect; lack end ticket writing; need to carry out correction process to the Acct-Status-Type field value of the last item ticket writing in ticket chargeable session sequence; the abnormal call ticket code arranging the last item ticket writing is numerical value 1; be written in original anomaly CDR file by the ticket writing before correcting, the value of the Acct-Status-Type field of amendment the last item ticket writing is numeral 2.

Subscriber Number field detects and corrects: detect the MDN Field Count word format of representative of consumer telephone number and digit and correct.MDN field value form should be decimal number word format; MDN field value digit rule is pre-configured; domestic consumer MDN field figure place is generally 13 (86+ subscriber directory number (11)) in the cdma 2000 network; MDN field value is detected according to number format and figure place configuration rule; for the ticket writing detecting MDN field exception; if abnormal call ticket code is numerical value 0; then arranging abnormal call ticket code value is numerical value 2, and is written in original anomaly CDR file by ticket writing.Further to represent MSID (user IMSI) field of international mobile subscriber identity in ticket writing for critical field, search the user record in calibration reference user information database, if there is the record that IMSI field value is identical, MDN field value then in use calibration reference user information database record corrects the MDN field in this ticket writing, enters subsequent detection aligning step; If do not find the user record of identical IMSI field, then directly enter subsequent detection aligning step.

User IMSI field detects and corrects: carry out number format and digit detection to the MSID field representing international mobile subscriber identity; the form of MSID field should be the decimal number word format of 15; MSID field is not met to the ticket writing of number format and digit; if abnormal call ticket code is numerical value 0; then arranging abnormal call ticket code value is numerical value 3, and is written in original anomaly CDR file by this ticket writing.Further with the MDN field value in ticket writing for critical field; search the user record in calibration reference user information database; if there is the record that MDN field value is identical; then use the MSID number in the abnormal ticket writing of MSID value correction in this ticket writing; enter subsequent detection aligning step; if do not find the user record of identical MDN field, then directly enter subsequent detection aligning step.

Charge type field detects and corrects: to representing that the PaidType field value of charge type carries out the detection of number format and span, PaidType field value form should be decimal number word format, the scope of PaidType field value generally should be [0 in the cdma 2000 network, 4], for the PaidType field value of exception, if abnormal call ticket code is numerical value 0, then needing to arrange abnormal call ticket code value is numerical value 4, and this ticket writing is written in original anomaly CDR file, further with the MDN field value in this ticket writing for critical field, search the user record in calibration reference user information database, if there is the ticket writing that MDN field value is identical, then use the PaidType field value in the abnormal ticket writing of PaidType value correction in this record, enter follow-up detection aligning step, if do not find the user record of identical MDN field, then directly enter subsequent detection aligning step.

Chargeable session duration field detects and corrects: the ticket writing to Acct-Status-Type field being numerical value 2 or 3, carries out the detection of chargeable session duration field value number format and span.Chargeable session duration field value form should be non-negative decimal number word format, introduce intermediate variable chargeable session event time difference (default value is 0), identify the EventTime field value of the ticket foremost of sequential in ticketing session sequence with variable Min_Event_Time, the computing formula of intermediate variable chargeable session event time difference is: chargeable session event time difference=EventTime-Min_Event_Time.If detect that Acct_Session_Time field format exception or Acct_Session_Time value equal numerical value 0 and intermediate variable chargeable session event time difference is one of abnormal conditions of positive number; if abnormal call ticket code is numerical value 0; then arranging abnormal call ticket code value is numerical value 5; ticket writing is written in original anomaly CDR file; and it is poor Acct_Session_Time value to be corrected to intermediate variable chargeable session event time, enter follow-up detection aligning step.

Network traffics detect and correct: the number format detecting DataOctetCount (Origination) in ticket writing (byte number that user sends), DataOctetCount (Termination) (sending to the byte number of user), Acct-Output-Gigawords (uplink traffic upset number of times), Acct-Input-Gigawords (downlink traffic upset number of times) four field values, and the uplink network flow calculated based on above-mentioned four field values and downlink network flow.In ticket writing, the form of DataOctetCount (Origination), DataOctetCount (Termination), Acct-Output-Gigawords and Acct-Input-Gigawords tetra-field values should be the ten's digit of non-negative; Uplink network flow rate calculation formula: DataOctetCount (Origination)+Acct-Output-Gigawords × 4 × 1024 × 1024 × 1024, downlink network flow rate calculation formula: DataOctetCount (Termination)+Acct-Input-Gigawords × 4 × 1024 × 1024 × 1024.According to CDMA2000 call charge service specification, the ticket writing that same chargeable session process produces, counting equipment adopts the mode of flux cumulating to be recorded in ticket writing, the uplink network flow of the posterior ticket writing of sequential should be more than or equal to the uplink network flow of the preceding ticket writing of sequential, and the downlink network flow of the posterior ticket writing of sequential should be more than or equal to the downlink network flow of the preceding ticket writing of sequential.

If detect at least one exception in DataOctetCount (Origination) field format, Acct-Output-Gigawords field format or uplink network flow three; if abnormal call ticket code is numerical value 0; then needing to arrange abnormal call ticket code value is 6; and write by ticket writing in original anomaly CDR file, the value of the byte number send user and uplink traffic upset number of times is corrected to the corresponding field value in ticket sequence in previous moment ticket writing.

If detect and occur at least one exception in DataOctetCount (Termination) field format, Acct-Input-Gigawords field format and downlink network flow three; if abnormal call ticket code is numerical value 0; then needing to arrange abnormal call ticket code value is 6; and ticket writing is write in original anomaly CDR file; the value sending to the byte number of user, downlink traffic to overturn number of times is corrected to the corresponding field value in the ticket writing of previous moment in ticket sequence, enters follow-up detection aligning step.

Activate duration field to detect and correct: be the ticket writing of 2 or 3 for Acct-Status-Type field value in ticketing session sequence, detect the number format and span that activate duration ActiveTime field value, ActiveTime field value form is non-negative decimal number word format in the cdma 2000 network.Introduce intermediate variable and correct activation duration (default value is 0), preferably intermediate variable correction activation duration is set to the duration of eating dishes without rice or wine in the wireless talking unirecord of wireless access network equipment generation corresponding to this internet records, also preferably can be greater than the ticket of 0 for network traffics, high-ranking officers are just activating duration and are being set to Acct_Session_Time field value.If detect that ActiveTime field value form is abnormal, meet Acct_Session_Time field value and equal 0 and intermediate variable corrects that to activate duration be positive number and activate duration and be less than one in three kinds of abnormal sights of the activation duration in chargeable session sequence previous moment ticket, if abnormal call ticket code is numerical value 0, then abnormal call ticket code value is set to numerical value 7, ticket writing is written in original anomaly CDR file, if in ticketing session sequence previous moment ticket writing in activation duration be 0, so ActiveTime field is corrected to intermediate variable and corrects activation duration, otherwise using the corrected value of the activation duration in the ticket writing of previous moment in ticketing session sequence as current activation duration.

The ticket writing completing whole ticketing session sequence by above-mentioned steps detects and corrects, and for detecting exception and ticket sequence after correcting, whole for whole sequence ticket writing need be outputted to abnormal correction in ticket writing file.

Carry out in above-mentioned all types of detection trimming process chronologically successively; for ensureing to detect comprehensively and correct without omitting; when detecting that ticket writing has the exception of certain type; after abnormal call ticket code value is set; except abnormal ticket writing is outputted in original anomaly CDR file, the abnormal ticket writing of current type is corrected.The abnormality detection of other types and correction are proceeded until finish to the ticket writing after correcting, complete detection and the correction of all records in whole ticketing session sequence, the whole records finally corrected in the ticketing session sequence that obtains are outputted to abnormal correction in ticket writing file.

Based on same thinking, present invention also offers a kind of charging bill record and detect means for correcting, it above-mentioned ticket writing can be adopted to detect bearing calibration carry out ticket writing detecting the entity device corrected, as shown in Figure 6, acquiring unit 601, calibration reference unit 602, pretreatment unit 603 and correction processing unit 604 4 parts are comprised.Its acquiring unit 601 periodically obtains the data in charging bill file from counting equipment or charging gateway or BOSS system, and obtain manner is active or passive.The data about ticket writing obtained are sent to pretreatment unit 603 and carry out duplicate removal preliminary treatment by acquiring unit 601, set up ticketing session sequence.Its pretreatment unit 603 carries out duplicate removal process to the ticket writing got, repeat ticket writing identification to determine according to the combination of different ticket field, according to the relevance in chargeable session process between ticket writing, charging identifier combined field (the MDN of ticket writing, IMSI, CorrelationID, and sequential relationship combined field (EventTime AccountSessionID), Acct-Status-Type) ticketing session sequence is set up, travel through all ticket writings, formed from ticket writing, interim UDR record, terminate the ticketing session sequential structure that ticket is formed, the ticketing session sequence generated is supplied to correction processing unit 604.

Its calibration reference unit 602 is for setting up user base reference information storehouse, above-mentioned user information database have recorded the reference data for correcting abnormal ticket writing field, calibration reference unit 602 and correction processing unit 604 data interaction, calibration reference data are supplied in trimming process, the Data Source in above-mentioned reference information storehouse can preferably adopt external data interface acquisition as the user data of operator ODS/CRM system (operator data warehousing and storage system/CRM system), or effective word segment value in ticket writing can be adopted as data source.

Its correction processing unit 604 contains the program detecting and correct, this program is write by detection bearing calibration above, every bar ticket writing is set up to exception code field, detects exception field, identifies exception code field, corrected ticket writing, the ticket writing of exception field and the ticket writing after correcting will be had to export preservation respectively, and generate ticket detection correction statistical report form according to this.Correction processing unit 604 corrects the detection that each ticket writing carries out terminating ticket integrality, Subscriber Number field, user IMSI field, charge type field, chargeable session duration field, network traffics and activation duration field seven Exception Types, the initial assignment that correction processing unit arranges exception code field is numerical value 0, and according to the exception field classification of type assignment exception code field of ticket writing, the exception code field that described seven Exception Types are corresponding is followed successively by numerical value 1 to 7.The concrete detection trimming process of each Exception Type can be undertaken by the embodiment of above-mentioned charging bill record detection bearing calibration, repeats no more here.

This charging bill record detects means for correcting can be arranged on AAA equipment or billing gateway device as embedded processor part, or in BOSS system, also independently can arrange individualism.When it embeds in AAA equipment, carrying out every bar ticket writing detecting on the basis corrected, the ticket writing after BOSS system acquisition corrects and do not detect abnormal ticket writing, and carrying out charging process according to charging regulation.

When it embeds in BOSS system, carrying out every bar ticket writing detecting on the basis of correction, BOSS system application charging regulation is to the ticket writing after correction and do not detect that abnormal ticket writing carries out charging process.Charging bill file detects after correction process through this device and obtains charging bill, by checking the charging bill after the online charging inventory of OCS online charging CMOS macro cell and this detection correction process, can generate and check file, realize the monitoring to Mobile data online online charging handling process, according to what export, relevant staff can check that file Timeliness coverage leaks the problem such as meter, wrong meter.

On the basis of above-mentioned detection bearing calibration and device, a kind of ticket treatment system can be set up, except the charging bill record of this case detects means for correcting 6, this ticket treatment system also comprises existing data gateway equipment 3, AAA equipment 2, BOSS system server 4, operator CRM/ODS system server 5, as shown in Figure 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 detect means for correcting 6 respectively with AAA equipment 2, BOSS system server 4, operator CRM/ODS system server 5 communicates to connect.

AAA equipment 2 generates charging bill record data in network process on user; BOSS system server 4 and charging bill record detect the charging bill record data that means for correcting 6 obtains AAA equipment 2; charging bill record detects means for correcting 6 and sets up calibration reference user information database with operator's ODS/CRM DSN; build ticketing session sequence; carry out abnormality detection and correction process to the ticket writing in ticket chargeable session sequence, output abnormality corrects ticket writing file, original anomaly CDR file and ticket and detects correction statistical report form.BOSS system server 4 acquisition abnormity corrects the charging bill record data of ticket writing file and AAA equipment 2 generation, and application charging regulation is to the ticket writing after correction and do not detect that abnormal ticket writing carries out pool charging process.

Claims

1. charging bill record detects a bearing calibration, it is characterized in that: comprise the steps:

Step a: obtain charging bill file from counting equipment, charging gateway or BOSS system, described charging bill file is the user's metering data generated in the process that terminates to chargeable session from chargeable session in upper network process of user;

Step b: set up calibration reference user information database, the user's ticket writing not comprising exception field that the data in described calibration reference user information database are user record in provider customer's information bank and/or get;

Step c: the ticket writing in duplicate removal charging bill file, with the ticket writing in user's chargeable session process chronologically and charging state relation relation generate a ticketing session sequence;

2. a kind of charging bill record according to claim 1 detects bearing calibration, it is characterized in that:

Also step c1 is comprised: abnormal call ticket code field is increased to every bar ticket writing and composes initial value after described step c;

The process of the unirecord exception field of described steps d lieutenant colonel means comprises: according to the exception field classification of type assignment exception code field of ticket writing, identify different exception field types by different exception codes.

3. a kind of charging bill record according to claim 2 detects bearing calibration, it is characterized in that: in described steps d, the exception field type of ticket writing comprises end ticket integrality exception, Subscriber Number field exception, user IMSI field exception, charge type field exception, chargeable session duration field exception, exception of network traffic, activation duration field extremely.

4. a kind of charging bill record according to claim 3 detects bearing calibration, it is characterized in that: the initial assignment of the exception code field of described ticket writing is numerical value 0, the detection correction order of the ticket writing in ticketing session sequence is followed successively by and terminates the correction of ticket integrity detection, Subscriber Number field detects and corrects, user IMSI field detects and corrects, charge type field detects and corrects, chargeable session duration field detects and corrects, exception of network traffic detects and corrects and activate duration field detection correction, the exception code field that the Exception Type of this order is corresponding is followed successively by numerical value 1 to 7.

5. a kind of charging bill record according to claim 4 detects bearing calibration, it is characterized in that:

Terminating ticket integrity detection trimming process is: detect the charging mode field being in the ticket writing of last sequential in ticketing session sequence, if the value of charging mode field is abnormal, the abnormal call ticket code then arranging this ticket writing is numerical value 1, this ticket writing is outputted in original anomaly CDR file, the value of the charging mode field of this ticket writing is corrected to the numerical value representing that ticket terminates;

Subscriber Number field detects trimming process: the number format and the digit that detect Subscriber Number field, if Subscriber Number field is abnormal, under the exception code field of ticket writing is the prerequisite of numerical value 0, then arranging abnormal call ticket code value is numerical value 2, and this ticket writing is written in original anomaly CDR file, to represent the IMSI field of international mobile subscriber identity in ticket writing for critical field, search the user record in calibration reference user information database, if there is the record that IMSI field value is identical, Subscriber Number field value then in use calibration reference user information database record corrects the Subscriber Number field in this ticket writing,

User IMSI field detects trimming process: the number format and the digit that detect international mobile subscriber identity field, if international mobile subscriber identity field is abnormal, under the exception code field of ticket writing is the prerequisite of numerical value 0, then arranging abnormal call ticket code value is numerical value 3, and this ticket writing is written in original anomaly CDR file, with the Subscriber Number field value in ticket writing for critical field, search the user record in calibration reference user information database, if there is the record that Subscriber Number field value is identical, international mobile subscriber identity value then in use calibration reference user information database corrects the international mobile subscriber identity field in this ticket writing,

Charge type field detects trimming process: the number format and the span that detect charge type field, if charge type field value is abnormal, under the exception code field of ticket writing is the prerequisite of numerical value 0, then arranging abnormal call ticket code value is numerical value 4, and this ticket writing is written in original anomaly CDR file, with the Subscriber Number field value in this ticket writing for critical field, search the user record in calibration reference user information database, if there is the record that Subscriber Number field value is identical, then use in calibration reference user information database charge type field value correct charge type field value in this ticket writing,

Chargeable session duration field detects trimming process: the number format and the span that detect chargeable session duration field value, if chargeable session duration field value is abnormal, under the exception code field of ticket writing is the prerequisite of numerical value 0, then arranging abnormal call ticket code value is numerical value 5, this ticket writing is written in abnormal correction ticket writing file, and chargeable session duration field value is corrected to the dialog events time difference, the described dialog events time difference is the dialog events time of current ticket writing and the difference of dialog events time being in sequential ticket writing foremost in ticketing session sequence,

Network traffics detect trimming process: detect the byte number sending to user in ticket writing, Client-initiated byte number, the number format of uplink traffic upset number of times and downlink traffic upset number of times four fields, and the upstream data flow to calculate based on these four field values and downlink data flow, if detect Client-initiated byte number field format, an exception is had at least in uplink traffic upset time field form and upstream data flow three, under the exception code field of ticket writing is the prerequisite of numerical value 0, then arranging abnormal call ticket code value is 6, and by this ticket writing write original anomaly CDR file, the value of Client-initiated byte number field and uplink traffic upset time field is corrected to respective value in the ticket writing of previous moment in ticketing session sequence, if detect send to user byte number field format, downlink traffic upset time field form and downlink data flow three at least one exception, under the exception code field of ticket writing is the prerequisite of numerical value 0, then arranging abnormal call ticket code value is 6, and by this ticket writing write original anomaly CDR file, the value sending to the byte number field of user, downlink traffic to overturn time field is corrected to the respective value in the ticket writing of previous moment in ticketing session sequence,

6. a kind of charging bill record according to any one of claim 1 to 5 detects bearing calibration, it is characterized in that: the step e after also comprising steps d: detect according to original anomaly CDR file and abnormal correction ticket writing file generated ticket and correct statistical report form.

7. a charging bill record detects means for correcting, it is characterized in that: comprise acquiring unit, calibration reference unit, pretreatment unit and correction processing unit, calibration reference unit and correction processing unit data interaction, acquiring unit exports and connects pretreatment unit, pretreatment unit exports and connects correction processing unit, wherein:

Acquiring unit is used for periodically obtaining or receiving charging bill file, is the charging bill file in counting equipment, charging gateway or BOSS system in described charging bill file;

Calibration reference unit is used for setting up calibration reference user information database, and the data in calibration reference user information database are the user record in provider customer's information bank or the user's ticket writing not comprising exception field for getting;

Pretreatment unit is used for the ticket writing in duplicate removal process charging bill file, by with the ticket writing in a chargeable session chronologically and charging state relation relation generate the ticketing session sequence that take ticket writing as element;

The each ticket writing of correction processing unit to ticket chargeable session sequence sets up exception code field, detect the ticket writing with exception field, the ticket writing with exception field is saved in original anomaly CDR file, according in ticketing session sequence between ticket writing service logic rule and correct the exception field of ticket writing with the calibration reference user information database data interaction in calibration reference unit, all ticket writings in ticketing session sequence after correction are saved in abnormal correction ticket writing file, and correct statistical report form by original anomaly CDR file and the abnormal data genaration ticket detection corrected in ticket writing file.

8. a kind of charging bill record detects means for correcting according to claim 7, it is characterized in that: described correction processing unit carries out end ticket integrality to each ticket writing, Subscriber Number field, user IMSI field, charge type field, chargeable session duration field, the detection of network traffics and activation duration field seven Exception Types corrects, the initial assignment that correction processing unit arranges exception code field is numerical value 0, and according to the exception field classification of type assignment exception code field of ticket writing, the exception code field that described seven Exception Types are corresponding is followed successively by numerical value 1 to 7.

9. a kind of charging bill record detects means for correcting according to claim 8, it is characterized in that:

Terminating ticket integrity detection trimming process is: detect the charging mode field being in the ticket writing of last sequential in ticketing session sequence, if the value of charging mode field is abnormal, under the exception code field of ticket writing is the prerequisite of numerical value 0, the abnormal call ticket code then arranging this ticket writing is numerical value 1, this ticket writing is outputted in original anomaly CDR file, the value of the charging mode field of this ticket writing is corrected to the numerical value representing that ticket terminates;

10. a ticket treatment system, comprise data gateway equipment, AAA equipment, BOSS system server, operator CRM/ODS system server, AAA equipment is connected with data gateway devices communicating, BOSS system server is connected with AAA devices communicating, it is characterized in that: also comprise charging bill record as claimed in claim 7 and detect means for correcting, described charging bill record detects means for correcting and communicates to connect with AAA equipment, BOSS system server, operator CRM/ODS system server respectively.