CN109428732B

CN109428732B - Call bill processing method and device

Info

Publication number: CN109428732B
Application number: CN201710752620.4A
Authority: CN
Inventors: 张春雨; 包贤德
Original assignee: Huawei Technologies Co Ltd
Current assignee: Huawei Technologies Co Ltd
Priority date: 2017-08-28
Filing date: 2017-08-28
Publication date: 2020-09-04
Anticipated expiration: 2037-08-28
Also published as: CN109428732A

Abstract

The embodiment of the application provides a call ticket processing method and device, relates to the technical field of charging, and can save the storage space of call tickets and ensure the consistency of call ticket audit. The specific scheme is as follows: the method comprises the steps that a data adaptation network element obtains m first ticket files from a convergence charging point, wherein m is a positive integer, each first ticket file comprises at least one ticket, the data adaptation network element combines a plurality of tickets meeting preset conditions in the m first ticket files into a combined ticket to generate n combined ticket files, n is a positive integer, the combined ticket files correspond to the combined ticket one by one, the data adaptation network element generates n audit files according to the m first ticket files and the n combined ticket files, the audit files are used for bill audit by an accounting processing network element, the data adaptation network element sends ticket information to the accounting processing network element, and the bill information comprises the n combined ticket files and the n audit files. The embodiment of the application is used for processing the call ticket.

Description

Call bill processing method and device

Technical Field

The embodiment of the application relates to the technical field of communication, in particular to a method and equipment for processing a call ticket.

Background

The converged charging system (CBS) is a comprehensive online and offline charging platform, can provide flexible pricing and real-time charging functions for services such as voice, data and the like, and can support various prepaid and postpaid services, voice, data and multimedia services, wired, wireless and Internet services and the like.

In practical applications, the CBS system usually generates a large amount of low-value tickets, such as zero-cost tickets, which occupy a large amount of storage space and have a great influence on the charging and billing performance of the CBS system. For example, when a user uses data services at a national boundary or across networks, there are frequent roaming handovers, which generate a large number of roaming zero-cost tickets in a short time. Besides data services, zero-cost telephone bills can be generated in many other scenes, such as frequent network disconnection, network access and the like. The zero-cost call ticket has a huge amount, for example, in a certain region of europe, a user can generate at most 40 ten thousand data service zero-cost call tickets per month, and the zero-cost call tickets not only occupy a large amount of storage space, but also greatly affect the performance of call ticket warehousing, account accumulation and account discharge.

In the prior art, referring to fig. 1, a data adaptation network element in a CBS system directly filters out collected telephone bills with low value, and then distributes the filtered telephone bills to an accounting processing network element for warehousing, accumulating accounts, going out accounts and other operations, so that the storage space of the telephone bills can be saved. However, some call tickets are filtered, so that call tickets processed by different stages of the CBS system are inconsistent, roaming data auditing between different mobile network operators is inconsistent, call ticket consistency auditing is failed, and charging reliability of the CBS system is affected.

Disclosure of Invention

The embodiment of the application provides a method and equipment for processing call tickets, which can save the storage space of the call tickets and ensure the consistency of the audit of the call tickets.

In order to achieve the above purpose, the embodiment of the present application adopts the following technical solutions:

in a first aspect, an embodiment of the present application provides a method for processing a ticket, including: the data adaptation network element obtains m first ticket files from the fusion charging point, wherein m is a positive integer, and each first ticket file comprises at least one ticket. And then, the data adaptation network element combines a plurality of call tickets meeting preset conditions in the m first call ticket files into a combined call ticket so as to generate n combined call ticket files, wherein n is a positive integer, and the combined call ticket files correspond to the combined call tickets one by one. And the data adaptation network element generates n audit files according to the m first call ticket files and the n combined call ticket files, wherein the audit files are used for the accounting processing network element to audit call tickets. And then, the data adaptation network element sends the ticket information to an accounting processing network element, wherein the ticket information comprises n ticket combination files and n audit files.

Therefore, the data adaptation unit combines a plurality of call tickets in the first call ticket file into a combined call ticket and sends the combined call ticket file to the accounting processing network element, so that the accounting processing network element can put the combined call tickets in the combined call ticket file into a warehouse and accumulate accounts, instead of putting each call ticket in the first call ticket file into the warehouse and accumulating accounts, the number of the call tickets put into the warehouse and accumulated accounts can be reduced, the storage space occupied by the call tickets can be reduced, the storage cost is reduced, the warehousing, accumulation and output performance of the system is improved, and the operation and maintenance efficiency is improved.

With reference to the first aspect, in a possible implementation manner, the preset condition includes: the user identification information corresponds to the same user, or corresponds to a plurality of users, and the plurality of users are associated users.

Therefore, the call bills corresponding to the same user or the corresponding associated users are combined into one combined call bill, so that the call bill charging and management can be facilitated.

With reference to the first aspect and the foregoing possible implementation manners, in another possible implementation manner, the preset condition further includes at least one of the following conditions: the corresponding service type is a preset service type, the corresponding rates are the same, the corresponding service starting time is within a preset time period, and the corresponding service ending time is within a preset time period.

In this way, the specific content of the preset condition can be set according to actual needs.

With reference to the first aspect and the foregoing possible implementation manners, in another possible implementation manner, the preset condition further includes that the corresponding cost is 0, or the corresponding cost is less than or equal to a preset value.

Thus, the zero-cost call tickets can be combined, or the small-amount call tickets can be combined.

In another possible implementation manner, the combined ticket includes a service start time, a service end time and a cost, and the service start time corresponding to the combined ticket is a minimum value of a plurality of service start times corresponding to a plurality of tickets meeting a preset condition; the service ending time corresponding to the combined call ticket is the maximum value of a plurality of service ending times corresponding to a plurality of call tickets meeting the preset condition; the sum of the fees corresponding to the combined call tickets is the sum of the fees corresponding to the call tickets meeting the preset condition.

Therefore, the combined call ticket has a corresponding relation with the plurality of call tickets before combination.

With reference to the first aspect and the possible implementation manners described above, in another possible implementation manner, at least one of the first ticket files that is not merged into the merged ticket forms a second ticket file, at least one of the m first ticket files that is not merged generates p second ticket files, p is a positive integer and p is less than or equal to m, and the ticket information further includes the p second ticket files.

In this way, the data adaptation network element may further send the non-combined ticket to the accounting processing network element in the form of the second ticket file, so that the accounting processing network element performs warehousing and accounting.

With reference to the first aspect and the possible implementation manners described above, in another possible implementation manner, a first association exists between the file name of the second ticket file and the file name of the corresponding first ticket file.

Therefore, the file name of the first ticket file corresponding to the second ticket file can be determined according to the first association relation and the file name of the second ticket file.

With reference to the first aspect and the foregoing possible implementation manners, in another possible implementation manner, the file name includes a file main name and a suffix, and the file name of the second ticket file and the file name of the corresponding first ticket file have a first association relationship, including: and the file name of the second ticket file is obtained by adding preset characters at the front end or the rear end of the file name of the corresponding first ticket file.

Therefore, the file name of the first ticket file corresponding to the second ticket file can be quickly determined according to the file main name and the suffix.

In another possible implementation manner, the audit file corresponds to the combined call ticket file and the combined call tickets one to one, and the audit file includes a corresponding relationship between a file name of each first call ticket file corresponding to the corresponding combined call ticket and the audit amount.

That is, the audit file can be used to represent the combination relationship between the combined call ticket file and the call ticket in the first call ticket file.

With reference to the first aspect and the possible implementation manners described above, in another possible implementation manner, a second association relationship exists between the file name of the audit file and the file name of the corresponding ticket-closing file.

Therefore, the file name of the audit file can be determined according to the second association relation and the file name of the ticket file.

With reference to the first aspect and the possible implementation manners, in another possible implementation manner, the determining that the file name of the audit file and the file name of the corresponding ticket-closing file have the second association relationship includes: the main file names of the audit file and the corresponding file names of the combined ticket files are the same, and suffixes in the file names of the audit file are preset suffixes and are different from the suffixes in the file names of the corresponding combined ticket files.

Therefore, the file name of the audit file corresponding to the combined ticket file can be quickly determined according to the main file name and the suffix.

With reference to the first aspect and the possible implementation manners described above, in another possible implementation manner, the ticket information further includes first audit information, where the first audit information includes a correspondence between a file name of each of the m first ticket files and an audit amount, and before the data adaptation network element sends the ticket information to the accounting processing network element, the method further includes: the data adaptation network element acquires the first audit information from the convergence charging point.

In this way, the data adaptation network element may send the first audit information acquired from the converged charging point to the accounting processing network element, so that the accounting processing network element performs ticket audit according to the first audit information.

With reference to the first aspect and the possible implementation manners described above, in another possible implementation manner, the audit quantity includes at least one of a number of call ticket records and a cost.

Therefore, when the ticket audit is carried out, the consistency of the number of the recorded tickets and/or the fee can be audited.

In a second aspect, an embodiment of the present application provides a method for processing a ticket, including: and the accounting processing network element receives the ticket information sent by the data adaptation network element. The method comprises the steps that the ticket information comprises n pieces of combined ticket files and n pieces of audit files, wherein n is a positive integer, the combined ticket files comprise combined tickets, the combined tickets are tickets formed by combining a plurality of tickets meeting preset conditions in m pieces of first ticket files, and the n pieces of audit files are obtained according to the m pieces of first ticket files and the n pieces of combined ticket files. And then, the accounting processing network element stores the ticket files in a warehouse and accumulates accounts, wherein the ticket files comprise n combined ticket files in the ticket information. And then, the accounting processing network element conducts ticket auditing according to the n combined ticket files and the n auditing files.

Therefore, the accounting processing network element puts the combined call bills after combining the multiple call bills in the first call bill file into a warehouse and accumulates the account, but not puts each call bill in the first call bill file into a warehouse and accumulates the account, so that the number of the call bills which are put into the warehouse and accumulated the account can be reduced, the storage space occupied by the call bills can be reduced, the storage cost is reduced, the input and output operations of the call bills and the number of times of interaction with a network are reduced, the warehousing, account accumulation and account output performance of the system are improved, and the operation and maintenance efficiency is improved.

Moreover, the accounting processing network element can also audit the call bills in the first call bill file acquired by the merging charging point and the call bills in the warehousing call bill of the accounting processing network element and the data adapting unit according to the audit file for representing the combination relation of the call bills in the first call bill file and the merging call bill file, so that the consistency of call bill audit can be ensured.

In combination with the second aspect, in a possible implementation manner, the ticket information and ticket file further includes p second ticket files, a ticket included in each second ticket file is a ticket that is not merged in the merged ticket in the first ticket file, and after the accounting processing network element receives the ticket information sent by the data adaptation network element, the method further includes: and the accounting processing network element generates second audit information according to the p second bill files.

Therefore, the accounting processing network element can audit the call ticket according to the second audit information.

With reference to the second aspect and the foregoing possible implementation manners, in another possible implementation manner, a first association exists between a file name of a second ticket file and a file name of a corresponding first ticket file, and the generating, by the accounting processing network element, second audit information according to p second ticket files includes: and for any second bill file in the p second bill files, the accounting processing network element determines the file name of the first bill file corresponding to the second bill file according to the file name of any second bill file and the first association relation. And the file name of the first call ticket file corresponding to any second call ticket file and the auditing amount in any second call ticket file form sub-second auditing information. And forming second audit information by the p pieces of sub-second audit information corresponding to the p pieces of second dialog documents.

In this way, the accounting processing network element may generate the second audit information according to the first association relationship and the p second phone bill files.

With reference to the second aspect and the possible implementation manners described above, in another possible implementation manner, the ticket information further includes first audit information, where the first audit information includes a correspondence between a file name of each of the m first ticket files and the audit amount.

Therefore, the accounting processing network element can audit the call ticket according to the first audit information.

With reference to the second aspect and the possible implementation manners described above, in another possible implementation manner, the performing, by the accounting processing network element, ticket audit according to the n combined ticket files and the n audit files includes: and the accounting processing network element generates third audit information according to the n combined call list files and the n audit files. And the accounting processing network element combines the second audit information and the third audit information into fourth audit information. And the accounting processing network element conducts ticket auditing according to the fourth auditing information and the first auditing information.

Therefore, the accounting processing network element can audit the call ticket by comparing the consistency of the fourth audit information and the first audit information.

In another possible implementation manner, in combination with the second aspect and the possible implementation manners, a second association relationship exists between the file name of the audit file and the file name of the corresponding combined ticket file, the audit file corresponds to the combined ticket file and the combined ticket one to one, and the audit file includes a corresponding relationship between the file name of each first ticket file corresponding to the corresponding combined ticket and the audit amount. The step of generating third audit information by the accounting processing network element according to the n combined call ticket files and the n audit files comprises the following steps: and for any combination ticket file in the n combination ticket files, the accounting processing network element determines the file name of the audit file corresponding to the any combination ticket file according to the file name of the any combination ticket file and the second association relation. And forming sub-third audit information according to the corresponding relation between the file name of each first ticket file and the audit amount in the audit file corresponding to any combined ticket file. And forming third audit information by the n pieces of sub third audit information corresponding to the n pieces of combined ticket files.

In this way, the accounting processing network element may generate the third audit information according to the second association relationship, the n combined ticket files and the n audit files.

With reference to the second aspect and the foregoing possible implementation manners, in another possible implementation manner, the audit quantity includes at least one of a call ticket record number and a charge.

With reference to the second aspect and the foregoing possible implementation manners, in another possible implementation manner, the preset condition includes: the user identification information corresponds to the same user, or corresponds to a plurality of users, and the plurality of users are associated users.

With reference to the second aspect and the foregoing possible implementation manners, in another possible implementation manner, the preset condition further includes at least one of the following conditions: the corresponding service type is a preset service type, the corresponding rates are the same, the corresponding service starting time is within a preset time period, and the corresponding service ending time is within a preset time period.

With reference to the second aspect and the foregoing possible implementation manners, in another possible implementation manner, the preset condition further includes that the corresponding cost is 0, or the corresponding cost is less than or equal to a preset value.

In a third aspect, an embodiment of the present application provides a data adaptation network element, including: the device comprises an acquisition unit and a processing unit, wherein the acquisition unit is used for acquiring m first ticket files from a fusion charging point, m is a positive integer, and each first ticket file comprises at least one ticket. And the combining unit is used for combining a plurality of call bills meeting the preset conditions in the m first call bill files into one combined call bill so as to generate n combined call bill files, wherein n is a positive integer, and the combined call bill files correspond to the combined call bills one to one. And the generating unit is used for generating n auditing files according to the m first call ticket files and the n combined call ticket files, and the auditing files are used for the accounting processing network element to audit call tickets. And the sending unit is used for sending the ticket information to the accounting processing network element, wherein the ticket information comprises n combined ticket files and n audit files.

With reference to the third aspect, in a possible implementation manner, at least one of the un-merged tickets in each first ticket file to the merged tickets forms a second ticket file, at least one of the un-merged tickets in the m first ticket files generates p second ticket files, p is a positive integer and p is less than or equal to m, and the ticket information further includes the p second ticket files.

With reference to the third aspect and the possible implementation manners described above, in another possible implementation manner, the ticket information further includes first audit information, the first audit information includes a correspondence between a file name of each of the m first ticket files and the audit amount, and the obtaining unit is further configured to: before the sending unit sends the ticket information to the accounting processing network element, first audit information is obtained from the fusion charging point.

With reference to the third aspect and the possible implementation manners described above, in another possible implementation manner, a first association relationship exists between the file name of the second ticket file and the file name of the corresponding first ticket file.

With reference to the third aspect and the possible implementation manners described above, in another possible implementation manner, a second association relationship exists between the file name of the audit file and the file name of the corresponding ticket-closing file.

With reference to the third aspect and the foregoing possible implementation manners, in another possible implementation manner, the audit quantity includes at least one of a call ticket record number and a charge.

With reference to the third aspect and the foregoing possible implementation manners, in another possible implementation manner, the preset condition includes: the user identification information corresponds to the same user, or corresponds to a plurality of users, and the plurality of users are associated users.

With reference to the third aspect and the foregoing possible implementation manners, in another possible implementation manner, the preset condition further includes at least one of the following conditions: the corresponding service type is a preset service type, the corresponding rates are the same, the corresponding service starting time is within a preset time period, and the corresponding service ending time is within a preset time period.

With reference to the third aspect and the foregoing possible implementation manners, in another possible implementation manner, the preset condition further includes that the corresponding cost is 0, or the corresponding cost is less than or equal to a preset value.

In a fourth aspect, an embodiment of the present application provides an accounting processing network element, including: and the receiving unit is used for receiving the ticket information sent by the data adaptation network element. The method comprises the steps that the ticket information comprises n pieces of combined ticket files and n pieces of audit files, wherein n is a positive integer, the combined ticket files comprise combined tickets, the combined tickets are tickets formed by combining a plurality of tickets meeting preset conditions in m pieces of first ticket files, and the n pieces of audit files are obtained according to the m pieces of first ticket files and the n pieces of combined ticket files. And the processing unit is used for warehousing and accumulating the ticket files, and the ticket files comprise n combined ticket files in the ticket information. And the auditing unit is used for auditing the call bills according to the n combined call bill files and the n auditing files.

With reference to the fourth aspect, in a possible implementation manner, the audit file corresponds to the combined ticket file and the combined ticket one to one, and the audit file includes a corresponding relationship between a file name of each first ticket file corresponding to the corresponding combined ticket and the audit amount.

In another possible implementation manner, in combination with the fourth aspect and the above possible implementation manner, the ticket information and ticket file further includes p second ticket files, a ticket included in each second ticket file is a ticket that is not merged in the first ticket file into the merged ticket, and the auditing unit is further configured to: and generating second audit information according to the p second dialog documents.

With reference to the fourth aspect and the possible implementation manners described above, in another possible implementation manner, the ticket information further includes first audit information, where the first audit information includes a correspondence between a file name of each of the m first ticket files and the audit amount.

With reference to the fourth aspect and the foregoing possible implementation manners, in another possible implementation manner, the auditing unit is specifically configured to: and generating third audit information according to the n combined call ticket files and the n audit files. And merging the second audit information and the third audit information into fourth audit information. And performing ticket auditing according to the fourth auditing information and the first auditing information.

With reference to the fourth aspect and the foregoing possible implementation manners, in another possible implementation manner, a first association exists between a file name of a second ticket file and a file name of a corresponding first ticket file, and the processing unit is specifically configured to: and for any second bill file in the p second bill files, the accounting processing network element determines the file name of the first bill file corresponding to the any second bill file according to the file name of the any second bill file and the first association relation. And the file name of the first call ticket file corresponding to any second call ticket file and the auditing amount in any second call ticket file form sub-second auditing information. And forming second audit information by the p pieces of sub-second audit information corresponding to the p pieces of second dialog documents.

In another possible implementation manner, in combination with the fourth aspect and the possible implementation manners, a second association relationship exists between a file name of the audit file and a file name of a corresponding combined ticket file, the audit file corresponds to the combined ticket file and the combined ticket one to one, and the audit file includes a corresponding relationship between a file name of each first ticket file corresponding to the corresponding combined ticket and the audit amount. The auditing unit is specifically used for: and for any combination ticket file in the n combination ticket files, the accounting processing network element determines the file name of the audit file corresponding to the any combination ticket file according to the file name of the any combination ticket file and the second association relation. And forming sub-third audit information according to the corresponding relation between the file name of each first ticket file and the audit amount in the audit file corresponding to any combined ticket file. And forming third audit information by the n pieces of sub third audit information corresponding to the n pieces of combined ticket files.

With reference to the fourth aspect and the foregoing possible implementation manners, in another possible implementation manner, the audit quantity includes at least one of a call ticket record number and a charge.

With reference to the fourth aspect and the foregoing possible implementation manners, in another possible implementation manner, the preset condition includes: the user identification information corresponds to the same user, or corresponds to a plurality of users, and the plurality of users are associated users.

With reference to the fourth aspect and the foregoing possible implementation manners, in another possible implementation manner, the preset condition further includes at least one of the following conditions: the corresponding service type is a preset service type, the corresponding rates are the same, the corresponding service starting time is within a preset time period, and the corresponding service ending time is within a preset time period.

With reference to the fourth aspect and the foregoing possible implementation manners, in another possible implementation manner, the preset condition further includes that the corresponding cost is 0, or the corresponding cost is less than or equal to a preset value.

With reference to the fourth aspect and the possible implementation manners described above, in another possible implementation manner, the combined ticket includes a service start time, a service end time, and a cost, and the service start time corresponding to the combined ticket is a minimum value of a plurality of service start times corresponding to a plurality of tickets meeting a preset condition; the service ending time corresponding to the combined call ticket is the maximum value of a plurality of service ending times corresponding to a plurality of call tickets meeting the preset condition; the sum of the fees corresponding to the combined call tickets is the sum of the fees corresponding to the call tickets meeting the preset condition.

In a fifth aspect, an embodiment of the present application provides a data adaptation network element, which includes at least one processor, a memory, a communication interface, and a bus, where the at least one processor and the memory are connected by the bus. The communication interface is used for data interaction. The memory is to store instructions. The processor is configured to invoke an instruction stored in the memory to implement the ticket processing method in any one of the first aspect and the first aspect.

In a sixth aspect, an embodiment of the present application provides an accounting processing network element, which includes at least one processor, a memory, a communication interface, and a bus, where the at least one processor and the memory are connected by the bus. The communication interface is used for data interaction. The memory is to store instructions. The processor is configured to invoke the instructions stored in the memory to implement the ticket processing method provided by any one of the above-mentioned second aspect and possible implementation manners of the second aspect.

In a seventh aspect, an embodiment of the present application provides a computer-readable storage medium, which includes instructions, and when the computer-readable storage medium is run on a data adaptation network element, the data adaptation network element executes the ticket processing method in any one of the first aspect and the first aspect.

In an eighth aspect, an embodiment of the present application provides a computer-readable storage medium, which includes instructions that, when executed on an accounting processing network element, cause the accounting processing network element to execute the ticket processing method according to any one of the second aspect and the second aspect.

In a ninth aspect, an embodiment of the present application provides a computer program product containing instructions, which when run on a data adaptation network element, causes the data adaptation network element to execute the method for processing a ticket as in any one of the first aspect and the first aspect.

In a tenth aspect, an embodiment of the present application provides a computer program product including instructions, which, when run on an accounting processing network element, causes the accounting processing network element to execute the ticket processing method in any one of the second aspect and the second aspect.

In an eleventh aspect, an embodiment of the present application provides a system, where the system includes a data adaptation network element and an accounting processing network element. The data adaptation network element is configured to execute the ticket processing method provided by any one of the possible implementation manners of the first aspect and the first aspect, and the account processing network element is configured to execute the ticket processing method provided by any one of the possible implementation manners of the second aspect and the second aspect.

For the beneficial effects of the third to eleventh aspects, reference may be made to the description of the first and second aspects, and details are not repeated here.

Drawings

Fig. 1 is a flow chart of a call ticket processing method provided in the prior art;

fig. 2 is a diagram of a billing system architecture according to an embodiment of the present application;

fig. 3 is a schematic structural diagram of a data adaptation network element and an accounting processing network element according to an embodiment of the present application;

fig. 4 is a flowchart of a call ticket processing method provided in the embodiment of the present application;

fig. 5 is a flowchart of another call ticket processing method provided in the embodiment of the present application;

fig. 6 is a flowchart of another call ticket processing method provided in the embodiment of the present application;

fig. 7 is a schematic structural diagram of a data adaptation network element according to an embodiment of the present application;

fig. 8 is a schematic structural diagram of another data adapting network element provided in an embodiment of the present application;

fig. 9 is a schematic structural diagram of an accounting processing network element according to an embodiment of the present application;

fig. 10 is a schematic structural diagram of another accounting processing network element according to an embodiment of the present application.

Detailed Description

For ease of understanding, examples are given in part to illustrate concepts related to embodiments of the present application. As follows:

a ticket: refers to the original communication record information, which may also be referred to as a Call Detail Record (CDR).

Rate: the rate of payment is referred to.

Accounting: the process of accumulating the cost in the call ticket according to a certain mode.

And (4) expenditure presentation: refers to a process of forming billing data for a charged fee within a time range (e.g., month) through a certain business process.

The technical solutions in the embodiments of the present application will be described below with reference to the drawings in the embodiments of the present application. In the description of the embodiments herein, "/" means "or" unless otherwise specified, for example, a/B may mean a or B; "and/or" herein is merely an association describing an associated object, and means that there may be three relationships, e.g., a and/or B, which may mean: a exists alone, A and B exist simultaneously, and B exists alone. In addition, in the description of the embodiments of the present application, "a plurality" means two or more than two.

An architecture diagram of the converged billing system 10 according to an embodiment of the present application can be seen in fig. 2. As shown in fig. 2, the converged charging system 10 may include a converged charging point (CBP) 11, a data adaptation network element mediation12, an accounting processing network element billing 13, and an accounting receivable network element (AR) 14. The integrated charging point 11 is mainly used for rating and entering account for the service to be charged, and writing the deduction details into a ticket file, where the ticket file includes multiple tickets, and each ticket corresponds to a ticket record. The data adaptation network element 12 may also be referred to as an intermediary network element or a data acquisition network element, and is mainly used to acquire a generated ticket file from the convergence charging point 11 and distribute the acquired ticket file to a specified directory of the accounting processing network element. The accounting processing network element 13 is mainly configured to scan a ticket file in a specified directory, store and accumulate tickets in the ticket file, and audit whether the stored ticket of the accounting processing network element 13 is consistent with the ticket generated by the fusion charging point 11. The accounting processing network element 13 may further be configured to perform an account-out based on the warehousing and accounting data, and synchronize an account-out result to the accounting and receival network element 14. The accounting receivable network element 14 is mainly configured to perform operations such as canceling accounts according to the accounting result provided by the accounting processing network element 13. The accounting processing network element 13 may include a memory database and a call ticket database, and the entering of the call ticket by the accounting processing network element means that the accounting processing network element 13 stores the call ticket into the call ticket database; the in-memory database may be used to store charge-up data and charge-out data. The accounting receivable network element 14 may be configured to perform an operation such as canceling the account of the billing result.

In the architecture shown in fig. 2, a schematic diagram of a data adaptation network element may be shown in fig. 3, and as shown in fig. 3, the data adaptation network element may include at least one processor 21, a memory 22, a communication interface 23, and a bus 24. The following will specifically describe each constituent component of the data adaptation network element with reference to fig. 3:

the processor 21 is a control center of the data adaptation network element, and may be a processor or a collective term for multiple processing elements. For example, the processor 21 is a Central Processing Unit (CPU), and may be an Application Specific Integrated Circuit (ASIC), or one or more integrated circuits configured to implement the embodiments of the present application, such as: one or more microprocessors (DSPs), or one or more Field Programmable Gate Arrays (FPGAs).

The processor 21 may perform various functions of the data adaptation network element by running or executing software programs stored in the memory 22 and calling up data stored in the memory 22.

In particular implementations, processor 21 may include one or more CPUs such as CPU0 and CPU1 shown in fig. 3 as one example.

In a specific implementation, the data adaptation network element may include a plurality of processors, as an example. Each of these processors may be a single-Core Processor (CPU) or a multi-Core Processor (CPU). A processor herein may refer to one or more devices, circuits, and/or processing cores for processing data (e.g., computer program instructions).

The memory 22 may be, but is not limited to, a read-only memory (ROM) or other type of static storage device that can store static information and instructions, a Random Access Memory (RAM) or other type of dynamic storage device that can store information and instructions, an electrically erasable programmable read-only memory (EEPROM), a compact disc read-only memory (CD-ROM) or other optical disc storage, optical disc storage (including compact disc, laser disc, optical disc, digital versatile disc, blu-ray disc, etc.), magnetic disk storage media or other magnetic storage devices, or any other medium that can be used to carry or store desired program code in the form of instructions or data structures and that can be accessed by a computer. The memory 22 may be self-contained and coupled to the processor 21 via a bus 24. The memory 22 may also be integrated with the processor 21.

The memory 22 is used for storing software programs for executing the scheme of the application, and is controlled by the processor 21 to execute.

The communication interface 23 is any device, such as a transceiver, for communicating with other devices or communication networks, such as ethernet, Radio Access Network (RAN), Wireless Local Area Networks (WLAN), etc. The communication interface 23 may include a receiving unit implementing a receiving function and a transmitting unit implementing a transmitting function.

The bus 24 may be an Industry Standard Architecture (ISA) bus, a Peripheral Component Interconnect (PCI) bus, an extended ISA (enhanced industry standard architecture) bus, or the like. The bus may be divided into an address bus, a data bus, a control bus, etc. For ease of illustration, only one thick line is shown in FIG. 3, but this does not mean only one bus or one type of bus.

The device structure shown in fig. 3 does not constitute a definition of a data adaptation network element and may comprise more or less components than those shown, or some components may be combined, or a different arrangement of components.

In addition, the accounting processing network element in the architecture shown in fig. 2 may have a similar structure to the data adapting network element shown in fig. 3, and is not described herein again.

Based on the framework shown in fig. 2, for a large amount of generated bills with low values, such as zero cost, in the prior art shown in fig. 1, the data adaptation network element directly filters the bills with low values to save the bill storage space, but the bills with low values are not distributed to the accounting processing network element, so that the bills put into storage by the accounting processing network element in the CBS system are inconsistent with the bills acquired by the data adaptation network element, and further the bill auditing is failed. The method and the device have the main scheme that the data adaptation network element combines the telephone bills with low value into a combined telephone bill so as to save the storage space of the telephone bills, and simultaneously generates the auditing file corresponding to the combined telephone bill so as to be used for the accounting processing network element to audit the telephone bills according to the auditing file, thereby ensuring the consistency of the telephone bill auditing. The following will be described in detail by way of specific examples.

Referring to fig. 4, an embodiment of the present application provides a method for processing a ticket, where the method may include:

201. the data adaptation network element obtains m first ticket files from the fusion charging point, wherein m is a positive integer, and each first ticket file comprises at least one ticket.

The first ticket file is used for storing tickets, each first ticket file can comprise one or more tickets, and each ticket corresponds to a ticket record number. The m first ticket files are ticket files acquired by the data adaptation network element from the convergence charging point, and can be called original ticket files. The call ticket in the first call ticket file may be referred to as an original call ticket. In the following embodiments of the present application, the first ticket file and the original ticket file represent the same meaning and can be used in common.

In a specific implementation manner, the data adaptation network element may periodically obtain the first ticket file from the convergence charging point.

202. The data adaptation network element combines a plurality of call bills meeting preset conditions in the m first call bill files into a combined call bill so as to generate n combined call bill files, wherein n is a positive integer, and the combined call bill files correspond to the combined call bills one to one.

The combined ticket file is used for storing combined tickets, and each combined ticket file can store one combined ticket. Here, the ticket satisfying the preset condition may be a ticket with a low value, such as a zero-cost ticket.

In this step 202, the data adaptation network element combines a plurality of tickets meeting the preset condition in the m first ticket files into one combined ticket, thereby generating n combined ticket files, that is, the m first ticket files can be converted into n combined ticket files. The data adaptation network element can reduce the number of the call tickets by combining a plurality of call tickets meeting the preset condition into one call ticket.

203. And the data adaptation network element generates n audit files according to the m first call ticket files and the n combined call ticket files, and the audit files are used for the accounting processing network element to audit call tickets.

The audit file corresponds to the combined call ticket file and the combined call tickets in the combined call ticket file one by one. The audit file is generated according to the corresponding relation between the m first ticket files and the n combined ticket files, namely according to the combined relation between the tickets in the m first ticket files and the combined tickets in the n combined ticket files. That is, the audit file may be used to represent a combination relationship between the first ticket file and the tickets in the combined ticket file.

204. And the data adaptation network element sends the ticket information to the accounting processing network element, wherein the ticket information comprises n combined ticket files and n audit files.

In a specific implementation manner, the data adaptation network element may periodically send the ticket information to the accounting processing network element.

The period here may be the same as or different from the period in step 201, the size of the period may be set according to actual situations, and for example, the period in step 201 may be 5 minutes, and the period in step 204 may be 2 hours.

205. After receiving the ticket information sent by the data adaptation network element, the accounting processing network element stores the ticket files in a warehouse and accumulates accounts, wherein the ticket files comprise n combined ticket files in the ticket information.

The ticket information here corresponds to the ticket information sent by the data adaptation network element in step 204, and may include n pieces of combined ticket files and n pieces of audit files, where the combined ticket file includes a combined ticket, the combined ticket is a ticket formed by combining a plurality of tickets meeting a preset condition in m pieces of first ticket files, and the n pieces of audit files are obtained according to the m pieces of first ticket files and the n pieces of combined ticket files.

After receiving the ticket information sent by the data adaptation network element, the accounting processing network element can put n combined ticket files in the ticket information and accumulate accounts. Wherein, the warehousing means storing in a call ticket database.

The combined bill file is stored and accumulated in the bill database, and the storage space of the bill database occupied by the bills can be saved, and the storage and accumulation performance of the system can be improved.

206. And the accounting processing network element conducts ticket auditing according to the n combined ticket files and the n auditing files.

The ticket auditing refers to auditing whether the condition of the ticket put into the financial processing network element is consistent with the condition of the original ticket acquired by the data adapting unit from the fusion charging point. The ticket file stored by the audit accounting processing network element is the ticket file converted from the original ticket file.

Since the n pieces of synthesized ticket files are ticket files of the warehousing of the accounting processing network element, and the audit file is generated in step 203 according to the corresponding relationship between the m pieces of first ticket files and the n pieces of synthesized ticket files, and can be used for representing the combined relationship between the first ticket files and the tickets in the synthesized ticket files, according to the n pieces of synthesized ticket files and the n pieces of audit file, the accounting processing network element can acquire the original ticket condition before conversion corresponding to the tickets warehoused by the accounting processing network element according to the ticket condition of the warehousing of the accounting processing network element, and perform consistency audit with the original ticket condition acquired by the data adaptation network element, thereby ensuring the consistency of ticket audit.

In the embodiment of the application, the data adaptation unit combines a plurality of tickets in the first ticket file into a combined ticket and sends the combined ticket to the accounting processing network element in the form of the combined ticket file, the accounting processing network element puts the combined tickets in storage and accumulates the accounts instead of putting each ticket in storage and accumulating the accounts in the first ticket file, so that the number of the tickets put in storage and accumulated accounts can be reduced, the storage space occupied by the tickets can be reduced, the storage cost is reduced, the input and output operations of the tickets and the number of times of interaction with a network are reduced, the warehousing, accumulated accounts and output performances of a system are improved, and the operation and maintenance efficiency is improved.

And moreover, the number of the phone bills for warehousing and accumulated account is reduced, the efficiency of operation and maintenance personnel for operating the phone bill database can be improved, and the daily maintenance (such as index reconstruction, statistical update and data relocation) cost of the phone bill database is reduced.

In addition, the accounting processing network element can also audit the call bills in the storage of the accounting processing network element and the call bills in the first call bill file acquired by the data adapting unit from the fusion charging point according to the audit file for representing the combination relation of the first call bill file and the call bills in the combination call bill file, so that the consistency of call bill audit can be ensured.

In addition, it is noted that in the embodiment of the present application, the audit file is generated while the call tickets are combined to save the storage space of the call ticket database, but the audit file is used for auditing the call tickets and cannot be stored in the call ticket database, so that the storage space of the call ticket database cannot be occupied.

And, under normal circumstances, the size of each ticket in the first ticket file is about 1kB (byte), and the size of each audit file is only about 0.1kB, and the number of tickets in the first ticket file obtained by the data adaptation network element from the fusion charging point is usually very large, and accordingly, the number of tickets meeting the preset condition and having low value to be combined is also very large (usually not on an order of magnitude with the ordinary tickets not meeting the preset condition), so that the number of combined tickets after combination is usually much smaller than the number of tickets having low value before combination, and the number of combined tickets can be on the same order of magnitude with the ordinary tickets, or can be lower than the corresponding order of magnitude of the ordinary tickets.

For example, data services have become the main income of various operators in europe, and the frequency of data services is high, so that call tickets need to be generated in real time. European countries and operators have the following characteristics: the European countries are numerous, and many countries are the Shen Guo, so that users can conveniently go out of each country; a large number of european high-end operators, and a Mobile Virtual Network Operator (MVNO) is widely applied; roaming settlement of data services between countries and operators is frequent. Therefore, when a user uses data services at national boundaries or across networks, frequent roaming handovers exist, which can generate a large number of low-value bills, such as roaming zero-cost bills, in a short time. Assuming that each user in a certain region in Europe generates 40 ten thousand zero-cost call tickets each month, the size of the 40 ten thousand zero-cost call tickets is about 0.4GB approximately, if the call tickets can be combined into 1000 combined call tickets and 1000 audit files are generated correspondingly, the size of the 1000 combined call tickets is about 1000kB, the size of the 1000 audit files is about 100k, the size of the 1000 combined call tickets and the size of the 1000 audit files are about 1100kB in total and are far less than 0.4GB, and thus, a large amount of call ticket storage space can be saved.

The preset condition in step 203 may be set according to actual needs. For example, the preset condition may specifically include that the preset condition corresponds to the same user, or that the preset condition corresponds to multiple users, where the multiple users are associated users. That is, the data adaptation network element may combine the tickets corresponding to the same user in the m first ticket files into one combined ticket. Or, the data adaptation network element may combine the tickets corresponding to different users in the m first ticket files, where the tickets of the different users are associated users, into a combined ticket.

Further, the preset condition may further include at least one of the following conditions: the corresponding service type is a preset service type, the corresponding rates are the same, the corresponding service starting time is within a preset time period, and the corresponding service ending time is within a preset time period. The service type is used to indicate the category to which the service belongs, and may include, for example, a data service, a voice service, a short message service, or a multimedia message service.

Illustratively, the preset condition specifically includes: corresponding to the same user, and the corresponding service type is data service. As another example, the preset condition may specifically include: corresponding to the same user, the corresponding service type is data service, the charge rate is the same, the corresponding service starting time is after 12:00, and the corresponding service ending time is before 14: 00. That is, the data adaptation network element may combine at least one of the m first ticket files, which correspond to the same user and correspond to the data service of the service type, with the same charge rate and the service start time and the service end time within the range of 12:00 to 14:00, into one combined ticket.

Further, the preset condition may further include that the cost is 0 or the cost is less than or equal to a preset value. For example, the preset condition may specifically include that the corresponding service type corresponds to the same user, the corresponding service type is a data service, the corresponding service start time is after 12:00, the corresponding service end time is before 14:00, and the cost is 0. As another example, the preset condition may specifically include that the corresponding service type corresponds to the same user, the corresponding service type is a data service, the charging rate is the same, the corresponding service start time is after 12:00, the corresponding service end time is before 14:00, and the charge is less than or equal to the preset value of 1 yuan. That is, the accounting processing network element may combine at least one call ticket, which corresponds to the same user, has the corresponding service type of data service and the same charge rate, has the service start time and the service end time within the range of 12:00-14:00, and has the charge less than or equal to 1 yuan corresponding to the call ticket, into one combined call ticket.

Specifically, the field content included in the ticket in the first ticket file may be set according to actual needs, and the field content included in the combined ticket obtained in step 203 may also be set according to actual needs. For example, in one implementation, the tickets and the combined tickets in the first ticket file may include service start time, service end time and cost. The service starting time corresponding to the combined call ticket can be the minimum value of a plurality of service starting times corresponding to a plurality of call tickets meeting preset conditions; the service ending time corresponding to the combined call ticket can be the maximum value of a plurality of service ending times corresponding to a plurality of call tickets meeting the preset condition; the sum of the fees corresponding to the combined call tickets is the sum of the fees corresponding to the call tickets meeting the preset condition.

In another implementation manner, the tickets and the combined tickets in the first ticket file may further include a ticket identifier and a charging object identifier. In another implementation manner, referring to table 1, the tickets and the combined tickets in the first ticket file may further include other fields such as a ticket sub identifier, a service sub type, a rate, and the like. The call ticket sub-identifier is used to identify a call ticket in cooperation with the call ticket identifier, for example, when the duration of a certain service spans 00:00, the service may correspond to two call tickets, the call ticket identifiers of the two call tickets may be the same, but the call ticket sub-identifiers may be different. The call ticket mark and the call ticket sub mark can form a main key of the call ticket. The service subclass is used for matching with the service type to mark the classification to which the service belongs.

TABLE 1

Field(s)	Field description
		CDR_ID	Ticket identification
CDR_SUB_ID	Ticket identifier
		OBJ_ID	Charging object identification, typically subscriber identification
START_DATE	Service start time
		END_DATE	Service end time
AMOUNT	Cost of
		SERVICE_CATEGORY	Type of service
USAGE_SERVICE_TYPE	Business subclass
		…	Other fields

For example, if the preset condition is preset condition 1, the corresponding service type is data service, and the cost is 0; if the m first ticket FILEs acquired by the data adaptation network element from the convergence charging point include 2 ticket FILEs, namely the ticket FILE CBP _ CDR _ FILE _00001.dat and the ticket FILE CBP _ CDR _ FILE _00002. dat; referring to table 2 below, the ticket FILE CBP _ CDR _ FILE _00001.dat may include 3 tickets, corresponding to 3 ticket records, where each ticket record represents a ticket; referring to table 3 below, the ticket FILE CBP _ CDR _ FILE _00002.dat may include 2 tickets, corresponding to 2 ticket records, where each ticket record represents a ticket; then the call ticket combination meeting the preset condition in the 2 first call ticket files can obtain a combined call ticket and a combined call ticket file, and the combined call ticket file can be called as

Table 4 below can be seen for details of CBP _ CDR _ FILE _00001_ aggregated.

TABLE 2

TABLE 3

Name of field	Telephone bill record 1	Telephone bill record 2
			CDR_ID	1011	1012
CDR_SUB_ID	1	1
			OBJ_ID	200002	200002
START_DATE	20170302 13:01:07	20170302 13:01:08
			END_DATE	20170302 13:01:07	20170302 13:01:08
AMOUNT	0	0
			SERVUCE_CATEGIRT	data	data
USAGE_SERVICE_TYPE	—	—

TABLE 4

Name of field	Telephone bill record 1
		CDR_ID	1000000001
CDR_SUB_ID	1
		OBJ_ID	200002
START_DATE	20170302 13:01:05
		END_DATE	20170302 13:01:08
AMOUNT	0
		SERVUCE_CATEGIRT	data
USAGE_SERVICE_TYPE	—

Wherein "-" in tables 2 to 4 indicates that the field is empty, voice indicates a voice service, and data indicates a data service. As can be seen from table 2, table 3, and table 4, table 4 includes a combined ticket 1000000001, which is obtained by combining a ticket 1002 corresponding to the ticket record 2 and a ticket 1003 corresponding to the ticket record 3 in the ticket FILE CBP _ CDR _ FILE _00001.dat shown in table 2, and a ticket 1011 corresponding to the ticket record 1 and a ticket 1012 corresponding to the ticket record 2 in the ticket FILE CBP _ CDR _ FILE _00002.dat shown in table 3.

The payment object corresponding to the combined ticket 1000000001 is 200002, and is the same as the payment objects corresponding to the ticket 1002, the ticket 1003, the ticket 1011 and the ticket 1012, that is, the combined ticket 1000000001 corresponds to the same user as the ticket 1002, the ticket 1003, the ticket 1011 and the ticket 1012.

The service starting time corresponding to the combined ticket 1000000001 is 2017030213: 01:05, the service starting time corresponding to the ticket 1002, the ticket 1003, the ticket 1011 and the ticket 1012 is 2017030213: 01:05, 2017030213: 01:06,

2017030213: 01:07 and 2017030213: 01:08, namely the service start time corresponding to the combined ticket 1000000001 is the minimum value of the service start time corresponding to the tickets 1002, 1003, 1011 and 1012 respectively.

The service ending time corresponding to the combined ticket 1000000001 is 2017030213: 01:08, the service ending time corresponding to the ticket 1002, the ticket 1003, the ticket 1011 and the ticket 1012 is 2017030213: 01:05, 2017030213: 01:06,

2017030213: 01:07 and 2017030213: 01:08, namely the service ending time corresponding to the combined ticket 1000000001 is the maximum value of the service ending time corresponding to the ticket 1002, the ticket 1003, the ticket 1011 and the ticket 1012 respectively.

In addition, the service types corresponding to the call ticket 1002, the call ticket 1003, the call ticket 1011 and the call ticket 1012 are data service data when the call ticket 1000000001 is combined, and the charges corresponding to the call ticket 1002, the call ticket 1003, the call ticket 1011 and the call ticket 1012 are 0 when the call ticket 1000000001 is combined.

In addition, in the step 202, the preset condition may not include a preset time period, and the data adaptation network element may also periodically combine the tickets meeting the preset condition in the m first ticket files into one combined ticket according to a preset combining period, for example, the combining period here may be 2 hours, that is, the data adaptation network element may combine the tickets every 2 hours.

In addition, it should be noted that, the above only describes how to combine the corresponding service start time, service end time, and cost, and when the ticket further includes other fields, for any field, for example, the field 1 in the ticket may be set to a preset value or a null value, or the field 1 in the ticket may be a value of any field 1 in a plurality of fields 1 to be combined into a plurality of tickets in the ticket. For example, when the call ticket 1 and the call ticket 2 are combined into the combined call ticket 1, if the service type in the call ticket 1 is a data service and the service type in the call ticket 2 is a voice service, the service type in the combined call ticket 1 may be a null value, or the service type in the combined call ticket 1 may be a preset value data service, or one of the service types in the call ticket 1 and the call ticket 2 may be randomly selected.

Besides, the ticket processing method provided by the embodiment of the invention can be used for carrying out ticket processing in other application scenes such as the Internet of things and the Internet of vehicles besides a mobile communication scene. For example, in a specific embodiment, the charging mode is a per-time charging (for example, 0.1 yuan per time), each time a corresponding ticket is used, when the ticket amount is large, the tickets in each hour can be combined, and the charges in the combined tickets are accumulated.

It should be noted that, in practical application, call ticket merging in the embodiment of the present application may be specifically implemented in multiple ways, and the specific way of call ticket merging shown above is merely an exemplary description and is not taken as a limitation to the way of call ticket merging provided in the embodiment of the present application.

In this embodiment of the present application, after n combined ticket files are generated in step 202, at least one ticket in each first ticket file that is not combined into a combined ticket forms a second ticket file, at least one ticket that is not combined in m first ticket files generates p second ticket files, p is a positive integer and p is less than or equal to m, so that tickets in m first ticket files can be converted into combined tickets in n combined ticket files and tickets in p second ticket files. The second ticket file can be understood as a ticket file formed by remaining tickets after the tickets meeting the preset conditions are split out in the first ticket file. That is, the m first ticket files can be converted into n combined ticket files, and can also be converted into p second ticket files. After the p second phone bill files are generated, the phone bill information can also comprise the p second phone bill files.

Also taking the first ticket file and the preset condition 1 shown in the above tables 2 and 3 as examples, the ticket file shown in table 2

In CBP _ CDR _ FILE _00001.dat, the ticket not merged into the merged ticket is the ticket corresponding to the ticket record 1

1001 and thus the ticket 1001 forms a second ticket file. The ticket file shown in Table 3

In CBP _ CDR _ FILE _00002.dat, all the tickets are combined into a combined ticket, so that

There is no un-merged ticket in CBP _ CDR _ FILE _00002.dat, so a second ticket FILE is not generated in CBP _ CDR _ FILE _00002. dat. That is, the p second phone FILEs generated here are 1 second phone FILE, which may be referred to as a second phone FILE CBP _ CDR _ FILE _00001_ split

The CBP _ CDR _ FILE _00001_ divided.dat can be seen in table 5 below.

TABLE 5

As can be seen from table 5, the call tickets in the second call ticket FILE CBP _ CDR _ FILE _00001_ split.dat are the call tickets 1001 in the call ticket FILE CBP _ CDR _ FILE _00001.dat shown in table 2 that are not merged.

In addition, as can be seen from comparing table 2, table 3, table 4 and table 5, the call tickets in the first call ticket file shown in table 2 and table 3 are converted into the call tickets in the call ticket file shown in table 4 and the call tickets in the second call ticket file shown in table 5.

On the basis of generating p second bill files, the bill information sent by the data adaptation network element to the accounting processing network element in step 204 may further include the p second bill files, and the bill files put into storage and accumulated by the accounting processing network element may further include the second bill files. That is to say, the ticket information received by the accounting processing network element and sent by the data adaptation network element may include n closed ticket files, n audit files, and p second ticket files, and the accounting processing network element may put in and accumulate tickets in the n closed ticket files and the p second ticket files, which are converted from tickets in m first ticket files in the ticket information, that is, the ticket files put in and accumulated by the accounting processing network element include n closed ticket files and p second ticket files.

Further, referring to fig. 5, after the receiving, by the accounting processing network element, the ticket information sent by the data adapting network element in step 204, the method may further include:

207. and the accounting processing network element generates second audit information according to the p second bill files.

The second audit information can be used for auditing the consistency of the bill by the accounting processing network element.

In the embodiment of the application, the ticket auditing performed by the accounting processing network element may specifically be to audit whether a corresponding relationship between an original ticket file before conversion and an auditing amount corresponding to a ticket put into storage by the accounting processing network element is consistent with a corresponding relationship between an original ticket file acquired by the data adaptation network element from the fusion charging point and the auditing amount. The audit quantity may be used to describe characteristics of the call ticket, and may include at least one of a corresponding call ticket record number and a corresponding call ticket cost, and/or other characteristics, which are not specifically limited herein. The following embodiments of the present application will be described with the example that the audit quantity includes the number of records and the cost of the call ticket.

The second audit information can be used to describe a corresponding relationship between the original ticket file (the first ticket file) before conversion and the audit amount corresponding to the second ticket file stored in the accounting processing network element.

Specifically, the file name of the second ticket file and the file name of the corresponding first ticket file may have a first association relationship. On this basis, step 207 may specifically include: and for any second bill file in the p second bill files, the accounting processing network element determines the file name of the first bill file corresponding to the second bill file according to the file name of any second bill file and the first association relation. And the file name of the first call ticket file corresponding to any second call ticket file and the auditing amount in any second call ticket file form sub-second auditing information. And forming second audit information by the p pieces of sub-second audit information corresponding to the p pieces of second dialog documents.

And if the call ticket included in the second call ticket file 1 is a call ticket which is not merged into a merged call ticket in the first call ticket file 1, the second call ticket file 1 corresponds to the first call ticket file 1. When the file name of the second ticket file and the file name of the corresponding first ticket file can have a first association relationship, the accounting processing network element can determine the file name of the first ticket file corresponding to the second ticket file according to the file name of the second ticket file and the first association relationship.

The first association relationship may be set according to actual needs. For example, the file name of the second ticket file may be obtained by adding a preset character to the front end or the rear end of the file name of the corresponding first ticket file. For example, the FILE name may mainly include a FILE main name and a suffix, the second ticket FILE shown in table 5 corresponds to the first ticket FILE in table 2, the FILE name of the second ticket FILE shown in table 5 is CBP _ CDR _ FILE _00001_ split.dat, the FILE name of the first ticket FILE shown in table 2 is CBP _ CDR _ FILE _00001.dat, and the FILE name of the second ticket FILE is obtained by adding a preset character "_ split" to the rear end of the FILE main name of the corresponding first ticket FILE. Thus, the accounting processing element may determine, according to the second ticket FILE with the FILE name CBP _ CDR _ FILE _00001_ divided.dat, that the first ticket FILE with the FILE name CBP _ CDR _ FILE _00001.dat corresponds to the second ticket FILE CBP _ CDR _ FILE _00001_ divided.dat.

The FILE name CBP _ CDR _ FILE _00001_ divided.dat of the first ticket FILE corresponding to the second ticket FILE CBP _ CDR _ FILE _00001_ divided.dat, and the audit volume in the second ticket FILE CBP _ CDR _ FILE _00001_ divided.dat form sub-second audit information. The audit volume includes the number of records and the cost of the second ticket FILE CBP _ CDR _ FILE _00001_ split. As can be seen from table 5, the second ticket FILE CBP _ CDR _ FILE _00001_ divided.dat only includes 1 ticket, which corresponds to a ticket record number and the fee is 100, so that the auditing amount of the second ticket FILE CBP _ CDR _ FILE _00001_ divided.dat is the ticket record number 1 and the fee is 100. The sub-second audit information can be seen in table 6 below.

TABLE 6

Filename of first ticket file	Number of telephone bill records	Cost of
			CBP_CDR_FILE_00001.dat	1	100

In table 6, the file name of the first ticket file is the file name of the original ticket file corresponding to the second ticket file stored by the accounting processing network element.

Further, referring to table 7 below, the sub-second audit information may further include a file name of a corresponding second ticket file on the basis of the corresponding relationship between the file name of the first ticket file and the audit amount.

TABLE 7

Filename of second-order file	Filename of first ticket file	Number of telephone bill records	Cost of
				CBP_CDR_FILE_00001_splited.dat	CBP_CDR_FILE_00001.dat	1	100

It should be noted that, in the example of the embodiment of the present application, only one second dialog document is generated, and therefore, only one piece of sub-second audit information corresponds to, and the second audit information only includes one piece of sub-second audit information shown in table 6 or table 7; when there are multiple second dialog documents, each second dialog document may correspond to one sub-second audit information, and all the sub-second audit information may form second audit information, which is not described herein again.

Further, the ticket information in step 204 may further include first audit information, where the first audit information includes a corresponding relationship between a file name of each of the m first ticket files and the audit amount. Prior to step 204, the method may further comprise:

208. the data adaptation network element acquires the first audit information from the convergence charging point.

The first audit information can be used to describe the corresponding relationship between the original call ticket file and the audit amount, which is obtained by the data adaptation network element from the fusion charging point. For example, the first audit information can be seen in table 8 below.

TABLE 8

Filename of first ticket file	Number of telephone bill records	Cost of
			CBP_CDR_FILE_00001.dat	3	100
CBP_CDR_FILE_00002.dat	2	0

In table 8, the file name of the first ticket file is the file name of the first ticket file acquired by the data adaptation network element from the convergence charging point. As can be seen from table 8, the data adaptation network element obtains 2 first ticket files, that is, ticket files, from the convergence charging point

CBP _ CDR _ FILE _00001.dat and a ticket FILE CBP _ CDR _ FILE _00002.dat, wherein the ticket FILE

The CBP _ CDR _ FILE _00001.dat comprises 3 call tickets, the number of records of the 3 call tickets is corresponded, and the total cost of the 3 call tickets is 0; the ticket FILE CBP _ CDR _ FILE _00002.dat comprises 2 tickets, which corresponds to the record number of the 2 tickets, and the total cost of the 2 tickets is 0.

On the basis of obtaining the second audit information and the first audit information, the performing, by the accounting processing network element, the ticket audit according to the n combined ticket files and the n audit files in the step 206 may include:

2061. and the accounting processing network element generates third audit information according to the n combined call list files and the n audit files.

2062. And the accounting processing network element combines the second audit information and the third audit information into fourth audit information.

2063. And the accounting processing network element conducts ticket auditing according to the fourth auditing information and the first auditing information.

The third audit information is used to describe a corresponding relationship between the original ticket file (the first ticket file) before conversion and the audit amount corresponding to the closed ticket file put into the database by the accounting processing network element. And because the second audit information is used for describing the corresponding relation between the original ticket file (the first ticket file) before conversion and the audit amount corresponding to the second ticket file stored in the accounting processing network element. Therefore, the fourth audit information obtained by combining the second audit information and the third audit information can be used for describing the corresponding relationship between the original ticket file (the first ticket file) before conversion and the audit amount corresponding to the ticket file stored in the accounting processing network element, and the first audit information is used for describing the corresponding relationship between the original ticket file and the audit amount obtained by the data adaptation network element from the fusion charging point. Therefore, the accounting processing network element can ensure the consistency of the ticket audit by auditing the fourth audit information and the first audit information, thereby improving the reliability of the charging system.

Specifically, the audit file corresponds to the combined call ticket file and the combined call ticket one to one, and the audit file can be used for describing the combination relationship of the call tickets in the first call ticket file and the combined call ticket file. Therefore, according to the audit file, the accounting processing network element can obtain the corresponding relationship between the original ticket file (the first ticket file) before conversion and the audit amount corresponding to the combined ticket file put into the account processing network element, that is, the third audit information. In a specific implementation manner, the audit file may include a corresponding relationship between a file name of each first ticket file corresponding to the corresponding combined ticket and the audit amount. For an exemplary audit FILE corresponding to the synthesized ticket FILE CBP _ CDR _ FILE _00001_ aggregated.dat shown in table 4 above, see table 9 below.

TABLE 9

Name of field	Merging records 1	Merge record 2
			MRG_CDR_ID	1000000001	1000000001
MGR_CDR_SUB_ID	1	1
			SRC_FILE_NAME	CBP_CDR_FILE_00001.dat	CBP_CDR_FILE_00002.dat
SRC_CDR_CNT	2	2
			TOTAL_AMT	0	0

As can be seen from table 9, the audit file includes two combined records, each combined record corresponds to a first ticket file, and each combined record is used to describe a corresponding relationship between a combined ticket corresponding to the audit file and a first ticket, and the number of ticket records or the cost of the ticket combined to the combined ticket in the first ticket file. For example, the combined record 1 may indicate that the combined ticket corresponding to the audit FILE is a combined ticket 1000000001, the combined ticket 1000000001 corresponds to a first ticket FILE CBP _ CDR _ FILE _00001.dat, the number of ticket records of the ticket combined into the combined ticket in the first ticket FILE CBP _ CDR _ FILE _00001.dat is 2, and the sum of the fees of the tickets combined into the combined ticket in the first ticket FILE CBP _ CDR _ FILE _00001.dat is 0. That is, the merged record 1 records: 2 call tickets in the first call ticket FILE CBP _ CDR _ FILE _00001.dat are merged into a combined call ticket 1000000001, and the total cost of the 2 call tickets is 0. Similarly, merge record 2 records: 2 call tickets in the first call ticket FILE CBP _ CDR _ FILE _00002.dat are merged into a combined call ticket 1000000001, and the total cost of the 2 call tickets is 0.

In a specific embodiment, if the preset condition includes that the fee is 0, the fees of the tickets combined into the combined tickets are all 0, so that the field of the fee may not be included in the combined tickets and the audit file, and the default fee is 0.

In the embodiment of the application, the file name of the audit file and the file name of the corresponding ticket-closing file can have a second association relationship. On this basis, the step 2061 of generating the third audit information by the accounting processing network element according to the n ticket files and the n audit files may include: and for any combination ticket file in the n combination ticket files, the accounting processing network element determines the file name of the audit file corresponding to the any combination ticket file according to the file name of the any combination ticket file and the second association relation. And forming sub-third audit information according to the corresponding relation between the file name of each first ticket file and the audit amount in the audit file corresponding to any combined ticket file. And forming third audit information by the n pieces of sub third audit information corresponding to the n pieces of combined ticket files.

The second association relationship here can be set according to actual needs. For example, in a specific implementation manner, the main file name of the audit file is the same as the main file name of the corresponding closed ticket file, and the suffix in the file name of the audit file is a preset suffix and is different from the suffix in the file name of the corresponding closed ticket file. Illustratively, the FILE name of the audit FILE shown in table 9 above is CBP _ CDR _ FILE _00001_ aggregated.chk, and the suffix is ". chk"; the corresponding contract ticket FILE in table 3 has a FILE name CBP _ CDR _ FILE _00001_ merged.dat and a suffix ". dat". Thus, the accounting processing element can determine that the audit FILE with the FILE name of CBP _ CDR _ FILE _00001_ aggregated.chk corresponds to the combined ticket FILE of CBP _ CDR _ FILE _00001_ aggregated.dat according to the combined ticket FILE with the FILE name of CBP _ CDR _ FILE _00001_ aggregated.dat. In another specific implementation manner, a preset character is added at the rear end of the file main name of the audit file, which is the corresponding combination ticket file, and a suffix in the file name of the audit file is a preset suffix which is different from the suffix in the file name of the corresponding combination ticket file.

Referring to table 9, the audit FILE CBP _ CDR _ FILE _00001_ staged.dat corresponding to the combined ticket FILE CBP _ CDR _ FILE _00001_ staged.chk includes the FILE name CBP _ CDR _ FILE _00001.dat and CBP _ CDR _ FILE _00002.dat of the first ticket FILE, and the audit amount in the audit FILE CBP _ CDR _ FILE _00001_ staged.chk forms a sub-third audit information. The audit volume comprises the number of call ticket records and the cost in the audit FILE CBP _ CDR _ FILE _00001_ aggregated. As can be seen from table 9, the audit FILE CBP _ CDR _ FILE _00001_ aggregated.chk includes the FILE names of the two first ticket FILEs, i.e., CBP _ CDR _ FILE _00001.dat and CBP _ CDR _ FILE _00002.dat, and also includes the ticket record number 2 and the fee 0 corresponding to the first ticket FILE CBP _ CDR _ FILE _00001.dat, and also includes the ticket record number 2 and the fee 0 corresponding to the second ticket FILE CBP _ CDR _ FILE _00002. dat. Thus, the sub-third audit information can be seen in table 10 below.

Watch 10

First call ticket file name	Number of telephone bill records	Cost of
			CBP_CDR_FILE_00001.dat	2	0
CBP_CDR_FILE_00002.dat	2	0

In table 10, the file name of the first ticket file is the file name of the original ticket file corresponding to (or including) the audit file, and the audit file corresponds to the closed ticket file stored in the accounting processing network element.

Further, referring to table 11 below, the sub-third audit information may further include a file name of a closed ticket file stored by the accounting processing network element corresponding to the audit file, on the basis of the corresponding relationship between the file name of the first ticket file and the audit amount.

TABLE 11

It should be noted that, in the example of the embodiment of the present application, only one combined ticket file and one audit file are generated, so that only one piece of sub-third audit information corresponds to, and the third audit information only includes one piece of sub-third audit information shown in table 10 or table 11; when there are multiple combined call ticket files and multiple audit files, each audit file may correspond to one piece of sub-third audit information, and all the sub-third audit information may form third audit information, which is not described herein again.

After the second audit information and the third audit information are obtained, the accounting processing network element may combine the second audit information and the third audit information into fourth audit information. For example, the fourth audit information obtained by combining the second audit information corresponding to table 6 and the third audit information corresponding to table 10 can be referred to as the following table 12.

TABLE 12

Comparing the fourth audit information in the table 12 with the first audit information in the table 8, it can be known that the fourth audit information and the first audit information include the same number and file names of the first call ticket files, and the audit amount, i.e., the number of call ticket records and the cost, corresponding to the file name of each first call ticket file are also the same.

The fourth audit information in table 12 can be used to describe the corresponding relationship between the original ticket file (first ticket file) before conversion and the audit volume corresponding to the ticket file put into the database of the accounting processing network element, while the first audit information in table 8 can be used to describe the corresponding relationship between the original ticket file and the audit volume obtained from the fusion charging point by the data adaptation network element. Therefore, it can be shown that the table 12 is the same as the table 8 that the correspondence between the original ticket file (first ticket file) before conversion and the audit amount corresponding to the ticket file stored in the accounting processing network element is the same as the correspondence between the original ticket file and the audit amount acquired by the data adapting network element from the fusion charging point, and the ticket consistency audit is passed. Therefore, the call ticket processing method provided by the embodiment of the application can ensure the consistency of the call ticket audit, thereby improving the reliability of the charging system.

Further, the call ticket processing method provided by the embodiment of the present application may further include:

209. and the accounting processing network element performs charge-off according to the data which is put in storage and accumulated in the account.

210. And the accounting processing network element sends the accounting data to the accounting receivable network element.

In addition, another flowchart of the ticket processing method provided by the above embodiment of the present application may also refer to fig. 6.

The above-mentioned scheme provided by the embodiment of the present application is introduced mainly from the perspective of interaction between network elements. It is to be understood that the data adaptation network element and the accounting processing network element comprise corresponding hardware structures and/or software modules for performing the respective functions in order to realize the functions. Those of skill in the art would readily appreciate that the various illustrative elements and algorithm steps described in connection with the embodiments disclosed herein may be implemented as hardware or combinations of hardware and computer software. Whether a function is performed as hardware or computer software drives hardware depends upon the particular application and design constraints imposed on the solution. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present application.

In the embodiment of the present application, according to the above method example, functional units or modules may be divided for the data adaptation network element and the accounting processing network element, for example, each functional unit or module may be divided corresponding to each function, or two or more functions may be integrated into one processing unit or module. The integrated module can be realized in a form of hardware, and can also be realized in a form of a software functional unit or module. It should be noted that, in the embodiment of the present application, the division of the unit or the module is schematic, and is only a logic function division, and there may be another division manner in actual implementation.

For example, in the case of dividing each functional unit by corresponding functions, fig. 7 shows a possible structural diagram of the data adaptation network element 70 involved in the above embodiment. The data adaptation network element 70 comprises an obtaining unit 701, a combining unit 702, a generating unit 703 and a sending unit 704. The obtaining unit 701 is configured to obtain m first ticket files from a convergence charging point, where m is a positive integer, each first ticket file includes at least one ticket, and may also be configured to execute step 208 in fig. 5. A combining unit 702, configured to combine multiple tickets meeting a preset condition in the m first ticket files into one combined ticket to generate n combined ticket files, where n is a positive integer, and the combined ticket files correspond to the combined tickets one to one. The generating unit 703 is configured to generate n audit files according to the m first ticket files and the n combined ticket files, where the audit files are used by the accounting processing network element to perform ticket audit. The sending unit 704 is configured to send the ticket information to the accounting processing network element, where the ticket information includes n combined ticket files and n audit files.

All relevant contents of each step related to the above method embodiment may be referred to the functional description of the corresponding functional unit or module, which is not described herein again.

In the case of dividing the functional modules in an integrated manner, fig. 8 shows a schematic structural diagram of a data adaptation network element 80 involved in the foregoing embodiment, where the data adaptation network element 80 includes: a processing module 801 and a communication module 802. The processing module 801 may be configured to execute operations that can be executed by the merging unit 702 and the generating unit 703 in fig. 7, and the communication module 802 may be configured to execute operations that can be executed by the obtaining unit 701 and the sending unit 704 in fig. 7, which may specifically refer to the embodiment shown in fig. 7, and this embodiment of the present application is not described herein again.

In this embodiment, the data adaptation network element is presented in a form of dividing each functional unit or module corresponding to each function, or the data adaptation network element is presented in a form of dividing each functional unit or module in an integrated manner. As used herein, a "unit, module" may refer to an application specific integrated circuit, a processor and memory that execute one or more software or firmware programs, an integrated logic circuit, and/or other devices that may provide the described functionality. In a simple embodiment, it is conceivable for a person skilled in the art that the data adaptation network element 70 or the data adaptation network element 80 may take the form shown in fig. 3. For example, the obtaining unit 701, the merging unit 702, the generating unit 703 and the sending unit 704 in fig. 7 may be executed by the processor 21 calling the application program code stored in the memory 22, which is not limited in this embodiment of the present application. Alternatively, for example, the processing module 801 and the communication module 802 in fig. 8 may be executed by the processor 21 calling the application program code stored in the memory 22, which is not limited in this embodiment of the present application.

Since the data adaptation network element provided in the embodiment of the present application can be used to execute the above-mentioned ticket processing method, the technical effect that can be obtained by the data adaptation network element can refer to the above-mentioned method embodiment, and is not described herein again.

For example, in the case of dividing each functional unit according to each function, fig. 9 shows a schematic diagram of a possible structure of the accounting processing network element related in the foregoing embodiment, where the accounting processing network element 90 includes: a receiving unit 901, a processing unit 902, an auditing unit 903 and a sending unit 904. The receiving unit 901 is configured to receive ticket information sent by a data adaptation network element, where the ticket information includes n ticket files and n audit files, and n is a positive integer. The combined call ticket file comprises combined call tickets, wherein the combined call tickets are formed by combining a plurality of call tickets meeting preset conditions in m first call ticket files, and n audit files are obtained according to the m first call ticket files and the n combined call ticket files. And the processing unit 902 is configured to store and accumulate the ticket files, where the ticket files include n combined ticket files in the ticket information. The auditing unit 903 is used for auditing the call tickets according to the n combined call ticket files and the n auditing files.

The processing unit 902 may also be configured to support the accounting processing network element 90 to perform step 209 in fig. 5. The auditing unit 903 may also be used to support the accounting processing network element 90 to perform steps 2061-2063 and 207 in fig. 5. The sending unit 904 may be configured to support the accounting processing network element 90 to perform step 210 in fig. 5.

In the case that the functional modules are divided in an integrated manner, fig. 10 shows a schematic diagram of a possible structure of the accounting processing network element 100 related in the foregoing embodiment, where the accounting processing network element 100 includes: a processing module 1001 and a communication module 1002. The processing module 1001 may be configured to execute operations that can be executed by the processing unit 902 and the auditing unit 903 in fig. 9, and the communication module 1002 may be configured to execute operations that can be executed by the receiving unit 901 and the sending unit 904 in fig. 9, which may specifically refer to the embodiment shown in fig. 9, and this embodiment is not described herein again.

All relevant contents of each step related to the above method embodiment may be referred to the functional description of the corresponding functional module, and are not described herein again.

In this embodiment, the accounting processing network element is presented in a form of dividing each functional module corresponding to each function, or in a form of dividing each functional module in an integrated manner. As used herein, a "module" may refer to an application specific integrated circuit, a processor and memory that execute one or more software or firmware programs, an integrated logic circuit, and/or other devices that may provide the described functionality. In a simple embodiment, it is conceivable for the skilled person that the accounting processing network element 90 or the accounting processing network element 100 may take the form shown in fig. 3. For example, the receiving unit 901, the processing unit 902, the auditing unit 903 and the sending unit 904 in fig. 9 may be executed by the processor 21 calling the application program code stored in the memory 22, which is not limited in this embodiment of the present application. Alternatively, for example, the processing module 1002 and the communication module 1001 in fig. 10 may be executed by the processor 21 calling an application program code stored in the memory 22, which is not limited in this embodiment.

Since the accounting processing network element provided in the embodiment of the present application may be configured to execute the above ticket processing method, the technical effect obtained by the accounting processing network element may refer to the above method embodiment, and is not described herein again.

The embodiment of the present application further provides a computer storage medium, configured to store a computer software instruction used by the data adaptation network element, and when the computer software instruction runs on the data adaptation network element, enable the data adaptation network element to execute the ticket processing method in the foregoing embodiment.

The embodiment of the present application further provides a computer storage medium, configured to store a computer software instruction used by the accounting processing network element, and when the computer software instruction runs on the accounting processing network element, the accounting processing network element may execute the ticket processing method in the foregoing embodiment.

The embodiment of the present application further provides a computer program product containing instructions, which, when running on the data adaptation network element, enables the data adaptation network element to execute the ticket processing method in the foregoing embodiment.

The embodiment of the present application further provides a computer program product containing instructions, which, when running on the accounting processing network element, enables the accounting processing network element to execute the ticket processing method in the foregoing embodiment.

The embodiment of the application also provides a system, which can comprise a data adaptation network element and an accounting processing network element. Further, the system may further include a converged charging point and accounting receivable network element. The schematic structure of the system can be seen in fig. 2. The data adaptation network element and the accounting processing network element in the system can execute the ticket processing method provided by the embodiment of the application.

In the above embodiments, the implementation may be wholly or partially realized by software, hardware, firmware, or any combination thereof. When implemented using a software program, may be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions. The procedures or functions according to the embodiments of the present application are all or partially generated when the computer program instructions are loaded and executed on a computer. The computer may be a general purpose computer, a special purpose computer, a network of computers, or other programmable device. The computer instructions may be stored on a computer readable storage medium or transmitted from one computer readable storage medium to another computer readable storage medium, for example, the computer instructions may be transmitted from one website, computer, server, or data center to another website, computer, server, or data center via wire (e.g., coaxial cable, fiber optic, Digital Subscriber Line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.). Computer-readable storage media can be any available media that can be accessed by a computer or can comprise one or more data storage devices, such as servers, data centers, and the like, that can be integrated with the media. The usable medium may be a magnetic medium (e.g., floppy disk, hard disk, magnetic tape), an optical medium (e.g., DVD), or a semiconductor medium (e.g., Solid State Disk (SSD)), among others.

While the present application has been described in connection with various embodiments, other variations to the disclosed embodiments can be understood and effected by those skilled in the art in practicing the claimed application, from a review of the drawings, the disclosure, and the appended claims. In the claims, the word "comprising" does not exclude other elements or steps, and the word "a" or "an" does not exclude a plurality. A single processor or other unit may fulfill the functions of several items recited in the claims. The mere fact that certain measures are recited in mutually different dependent claims does not indicate that a combination of these measures cannot be used to advantage.

The above description is only an embodiment of the present application, but the scope of the present application is not limited thereto, and any changes or substitutions within the technical scope of the present disclosure should be covered by the scope of the present application. Therefore, the protection scope of the present application shall be subject to the protection scope of the claims.

Claims

1. A method for processing call tickets, comprising:

the method comprises the steps that a data adaptation network element obtains m first ticket files from a fusion charging point, wherein m is a positive integer, and each first ticket file comprises at least one ticket;

the data adaptation network element takes all the telephone bills in the m first telephone bill files as a combination basis, combines a plurality of telephone bills meeting preset conditions into a combined telephone bill so as to generate n combined telephone bill files, wherein n is a positive integer, and the combined telephone bill files correspond to the combined telephone bills one by one;

the data adaptation network element generates n auditing files according to the m first call ticket files and the n combined call ticket files, and the auditing files are used for the accounting processing network element to audit call tickets;

and the data adaptation network element sends call ticket information to the accounting processing network element, wherein the call ticket information comprises the n combined call ticket files and the n audit files.

2. The method according to claim 1, wherein the preset condition comprises: the method corresponds to the same user, or corresponds to a plurality of users, and the users are associated users.

3. The method according to claim 2, wherein the preset conditions further comprise at least one of the following conditions: the corresponding service type is a preset service type, the corresponding rates are the same, the corresponding service starting time is within a preset time period, and the corresponding service ending time is within a preset time period.

4. The method according to claim 2 or 3, wherein the predetermined condition further comprises that the corresponding cost is 0, or that the corresponding cost is less than or equal to a predetermined value.

5. The method of claim 1, wherein the combined ticket comprises a service start time, a service end time and a cost, and the service start time corresponding to the combined ticket is a minimum value of a plurality of service start times corresponding to the plurality of tickets meeting a preset condition; the service ending time corresponding to the combined call ticket is the maximum value of a plurality of service ending times corresponding to the plurality of call tickets meeting the preset condition; and the cost corresponding to the combined call ticket is the sum of a plurality of costs corresponding to the plurality of call tickets meeting the preset condition.

6. The method of claim 1, wherein at least one of the first ticket files that is not merged into the merged ticket forms a second ticket file, wherein at least one of the m first ticket files that is not merged generates p second ticket files, p is a positive integer and p is less than or equal to m, and the ticket information further includes the p second ticket files.

7. The method of claim 6, wherein a first association exists between the file name of the second ticket file and the corresponding file name of the first ticket file.

8. The method of claim 1, wherein the audit file corresponds to the combined ticket file and the combined ticket one to one, and the audit file comprises a corresponding relationship between a file name of each first ticket file corresponding to the corresponding combined ticket and an audit amount.

9. The method of claim 8, wherein the filename of the audit file has a second association relationship with the filename of the corresponding ticket file.

10. The method of claim 1, wherein the ticket information further includes first audit information, the first audit information includes a correspondence between a filename of each of the m first ticket files and an audit amount, and before the data adaptation network element sends the ticket information to the accounting processing network element, the method further includes:

and the data adaptation network element acquires the first audit information from the fusion charging point.

11. The method of any one of claims 8-10, wherein the audit volume comprises at least one of a number of call ticket records and a cost.

12. A method for processing call tickets, comprising:

the accounting processing network element receives ticket information sent by a data adaptation network element, wherein the ticket information comprises n combined ticket files and n audit files, n is a positive integer, the combined ticket files comprise combined tickets, the combined tickets are tickets formed by combining a plurality of tickets meeting preset conditions in m first ticket files by taking all the tickets as a combination basis, and the n audit files are obtained according to the m first ticket files and the n combined ticket files;

the accounting processing network element puts the ticket files in storage and accumulates accounts, wherein the ticket files comprise the n combined ticket files in the ticket information;

and the accounting processing network element conducts ticket auditing according to the n combined ticket files and the n auditing files.

13. The method of claim 12, wherein the ticket information and the ticket file further include p second ticket files, each of the second ticket files includes a ticket that is not merged in the merged ticket in the first ticket file, and after the accounting processing element receives the ticket information sent by the data adaptation element, the method further includes:

and the accounting processing network element generates second audit information according to the p second bill files.

14. The method of claim 13, wherein a first association exists between the file name of the second ticket file and the corresponding file name of the first ticket file, and wherein the generating, by the accounting processing element, second audit information according to the p second ticket files comprises:

for any second bill file in the p second bill files, the accounting processing network element determines the file name of the first bill file corresponding to the any second bill file according to the file name of the any second bill file and the first association relation;

the file name of the first call ticket file corresponding to any second call ticket file and the auditing amount in any second call ticket file form sub-second auditing information;

and the p pieces of sub-second audit information corresponding to the p pieces of second dialog documents form the second audit information.

15. The method of claim 13, wherein the ticket information further comprises first audit information, and the first audit information comprises a correspondence between a filename of each of the m first ticket files and an audit volume.

16. The method of claim 15, wherein the performing the ticket audit by the accounting processing element according to the n combined ticket files and the n audit files comprises:

the accounting processing network element generates third audit information according to the n combined call ticket files and the n audit files;

the accounting processing network element merges the second audit information and the third audit information into fourth audit information;

and the accounting processing network element conducts ticket auditing according to the fourth auditing information and the first auditing information.

17. The method of claim 16, wherein a second association relationship exists between a file name of the audit file and a file name of the corresponding combined ticket file, the audit file corresponds to the combined ticket file and the combined ticket one by one, the audit file comprises a corresponding relationship between a file name of each first ticket file corresponding to the corresponding combined ticket and an audit amount, and the generating, by the accounting processing network element, third audit information according to the n combined ticket files and the n audit files comprises:

for any combined call ticket file in the n combined call ticket files, the accounting processing network element determines the file name of the audit file corresponding to the any combined call ticket file according to the file name of the any combined call ticket file and the second association relation;

the corresponding relation between the file name of each first call ticket file and the auditing amount in the auditing file corresponding to any combined call ticket file forms sub-third auditing information;

and the n pieces of sub-third audit information corresponding to the n pieces of combined ticket files form the third audit information.

18. The method of any one of claims 15-17, wherein the audit volume comprises at least one of a number of call ticket records and a cost.

19. A data adaptation network element, comprising:

the device comprises an acquisition unit, a processing unit and a processing unit, wherein the acquisition unit is used for acquiring m first ticket files from a fusion charging point, m is a positive integer, and each first ticket file comprises at least one ticket;

a combining unit, configured to combine all tickets in the m first ticket files into a combined ticket by using the tickets as a combining basis, so as to generate n combined ticket files, where n is a positive integer, and the combined ticket files correspond to the combined tickets one by one;

a generating unit, configured to generate n audit files according to the m first ticket files and the n combined ticket files, where the audit files are used by an accounting processing network element to perform ticket audit;

and the sending unit is used for sending the ticket information to the accounting processing network element, wherein the ticket information comprises the n combined ticket files and the n audit files.

20. The network element of claim 19, wherein at least one of the first ticket files that is not merged into the merged ticket forms a second ticket file, wherein at least one of the m first ticket files that is not merged generates p second ticket files, p is a positive integer and p is less than or equal to m, and the ticket information further includes the p second ticket files.

21. The network element of claim 19, wherein the ticket information further includes first auditing information, the first auditing information includes a correspondence between a filename of each of the m first ticket files and an auditing amount, and the obtaining unit is further configured to:

and before the sending unit sends the ticket information to the accounting processing network element, acquiring the first audit information from the converged charging point.

22. The network element of claim 21, wherein the audit file corresponds to the combined ticket file and the combined ticket one to one, and the audit file comprises a correspondence between a file name of each first ticket file corresponding to the corresponding combined ticket and an audit amount.

23. The network element of claim 21 or 22, wherein the audit volume comprises at least one of a number of call ticket records and a cost.

24. An accounting processing network element, comprising:

the device comprises a receiving unit, a processing unit and a processing unit, wherein the receiving unit is used for receiving ticket information sent by a data adaptation network element, the ticket information comprises n combined ticket files and n audit files, n is a positive integer, the combined ticket files comprise combined tickets, the combined tickets are tickets formed by combining a plurality of tickets meeting preset conditions in m first ticket files by taking all the tickets as a combination basis, and the n audit files are obtained according to the m first ticket files and the n combined ticket files;

the processing unit is used for warehousing and accumulating the ticket files, wherein the ticket files comprise the n combined ticket files in the ticket information;

and the auditing unit is used for auditing the call bills according to the n combined call bill files and the n auditing files.

25. The network element of claim 24, wherein the audit file corresponds to the combined ticket file and the combined ticket one to one, and the audit file comprises a correspondence between a file name of each first ticket file corresponding to the corresponding combined ticket and an audit amount.

26. The network element of claim 24 or 25, wherein the ticket information and the ticket file further include p second ticket files, each of the second ticket files includes a ticket that is not merged in the first ticket file into the merged ticket, and the auditing unit is further configured to:

and generating second audit information according to the p second dialog documents.

27. The network element of claim 26, wherein the ticket information further comprises first audit information, and the first audit information comprises a correspondence between a filename of each of the m first ticket files and an audit volume.

28. The network element of claim 27, wherein the auditing unit is specifically configured to:

generating third audit information according to the n combined call ticket files and the n audit files;

merging the second audit information and the third audit information into fourth audit information;

and performing ticket auditing according to the fourth auditing information and the first auditing information.