Call bill distribution method and device, server and storage medium

Abstract

The invention provides a ticket distribution method and device, a server and a storage medium. The method comprises the following steps: receiving multiple pieces of call ticket data sent by operator network equipment; according to the attribute information of each piece of call ticket data, sending the plurality of pieces of call ticket data to a Kafka cluster, so that a plurality of themes in the Kafka cluster store the plurality of pieces of call ticket data; multiple pieces of call ticket data sent by the Kafka cluster are received, and demand information of multiple back-end systems is acquired; classifying the plurality of call ticket data according to the demand information, and storing the call ticket data of the plurality of demand types to a plurality of call ticket temporary files; caching all the call ticket temporary files meeting a caching condition in the plurality of call ticket temporary files to an object storage system, so that the object storage system stores the plurality of call ticket cache files; and receiving the plurality of call ticket cache files sent by the object storage system, and sending the plurality of call ticket cache files to the plurality of back-end systems. According to the method, occupation of computer resources is reduced.

Description

Technical Field

[0001] The present application relates to the field of computer technology, and in particular to a call record distribution method, device, server and storage medium. Background Art

[0002] In the billing system of the telecommunications industry, the call bill management center, as the source of call bill data collection, not only provides billing call bill data for billing, but also provides call bill data for other systems. However, different systems require different call bill data.

[0003] At present, in the prior art, the call record data is mainly copied and marked by computers according to the needs of different systems, and the same call record data is copied into multiple copies and distributed to different systems.

[0004] However, this method in the prior art will occupy a lot of computer resources. Summary of the invention

[0005] The present application provides a call bill distribution method, device, server and storage medium to solve the technical problem of occupying a large amount of computer resources.

[0006] In a first aspect, the present application provides a call record distribution method, which is applied to a server and includes:

[0007] Receive multiple call record data sent by the operator's network equipment;

[0008] According to the attribute information of each call record data, the multiple call record data are sent to the Kafka cluster, so that the multiple topics in the Kafka cluster save the multiple call record data;

[0009] Receive the multiple call sheet data sent by the Kafka cluster, and obtain demand information of multiple backend systems; classify the multiple call sheet data according to the demand information to obtain call sheet data of multiple demand types;

[0010] Saving the call sheet data of the multiple demand types into multiple call sheet temporary files;

[0011] Determine all temporary call record files that meet the cache condition among the multiple temporary call record files as multiple call record cache files;

[0012] Cache the multiple call record cache files to an object storage system so that the object storage system saves the multiple call record cache files;

[0013] The multiple call record cache files sent by the object storage system are received, and the multiple call record cache files are sent to multiple backend systems.

[0014] Optionally, the method as described above, sending the multiple call record data to the Kafka cluster according to the attribute information of each call record data, so that multiple topics in the Kafka cluster save the multiple call record data, including: classifying the multiple call record data according to the attribute information of each call record data to obtain multiple types of call record data; sending the multiple types of call record data to the Kafka cluster, so that multiple topics in the Kafka cluster save the multiple call record data.

[0015] Optionally, the method as described above, after receiving the multiple call record cache files sent by the object storage system and sending the multiple call record cache files to multiple back-end systems, also includes: if there is a newly added back-end system, determining whether there is newly added demand information in the demand information; if it is determined that the newly added demand information exists in the demand information, receiving at least one call record cache file corresponding to the newly added demand information sent by the object storage system, and sending the at least one call record cache file to the newly added back-end system.

[0016] Optionally, in the method as described above, if there is a newly added backend system, then after determining whether there is newly added demand information in the demand information, it also includes: if it is determined that the newly added demand information does not exist in the demand information, receiving at least one call record data corresponding to the newly added demand information sent by the Kafka cluster, wherein the at least one call record data is obtained according to the old offset for multiple topics in the Kafka cluster; saving the at least one call record data to at least one call record temporary file; determining all call record temporary files in the at least one call record temporary file that meet the caching condition as the at least one call record cache file; caching the at least one call record cache file to the object storage system, so that the object storage system saves the at least one call record cache file; receiving the at least one call record cache file sent by the object storage system, and sending the at least one call record cache file to the newly added backend system.

[0017] Optionally, in the method described above, the caching condition is: the time difference between the creation time of each temporary call record file and the current time exceeds a preset time threshold; or, the size of each temporary call record file exceeds a preset file size threshold.

[0018] In a second aspect, the present application provides a call record distribution device, applied to a server, comprising:

[0019] A first receiving module, used to receive a plurality of call record data sent by an operator network device;

[0020] A first sending module, configured to send the plurality of call record data to a Kafka cluster according to attribute information of each call record data, so that the plurality of call record data are saved by the plurality of topics in the Kafka cluster;

[0021] A second receiving module is used to receive the multiple call list data sent by the Kafka cluster and obtain demand information of multiple backend systems; classify the multiple call list data according to the demand information to obtain call list data of multiple demand types;

[0022] A saving module, used for saving the call sheet data of the multiple demand types into multiple call sheet temporary files;

[0023] A determination module, configured to determine all temporary call bill files that meet the cache condition among the multiple temporary call bill files as multiple call bill cache files;

[0024] A cache module, used for caching the plurality of call record cache files to an object storage system, so that the object storage system saves the plurality of call record cache files;

[0025] The second sending module is used to receive the multiple call record cache files sent by the object storage system, and send the multiple call record cache files to multiple backend systems.

[0026] In a third aspect, the present application provides a server, comprising: at least one processor and a memory;

[0027] The memory stores computer-executable instructions;

[0028] The at least one processor executes the computer-executable instructions stored in the memory, so that the at least one processor executes the call record distribution method as described in the first aspect and various possible designs of the first aspect.

[0029] In a fourth aspect, the present application provides a computer storage medium, in which computer execution instructions are stored. When a processor executes the computer execution instructions, the call record distribution method described in the first aspect and various possible designs of the first aspect is implemented.

[0030] The call record distribution method, device, server and storage medium provided in the present application classify multiple call record data according to the demand information of multiple back-end systems to obtain call record data of multiple demand types, so as to distribute the call record data of each demand type to the corresponding back-end system; avoid copying multiple call record data and sending the copied results to multiple back-end systems, thereby reducing the occupation of computer resources. BRIEF DESCRIPTION OF THE DRAWINGS

[0031] The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the present application and, together with the description, serve to explain the principles of the present application.

[0032] Figure 1 A schematic diagram of a scenario of a call bill distribution system provided in an embodiment of the present application;

[0033] Figure 2 A flowchart of a method for distributing call receipts provided in one embodiment of the present application;

[0034] Figure 3 A flowchart of a method for distributing call receipts provided in another embodiment of the present application;

[0035] Figure 4 A schematic diagram of the structure of a bill distribution device provided in an embodiment of the present application;

[0036] Figure 5 A schematic diagram of the hardware structure of the server provided in an embodiment of the present application.

[0037] The above drawings have shown clear embodiments of the present application, which will be described in more detail later. These drawings and text descriptions are not intended to limit the scope of the present application in any way, but to illustrate the concept of the present application to those skilled in the art by referring to specific embodiments. DETAILED DESCRIPTION

[0038] Exemplary embodiments will be described in detail herein, examples of which are shown in the accompanying drawings. When the following description refers to the drawings, the same numbers in different drawings represent the same or similar elements unless otherwise indicated. The implementations described in the following exemplary embodiments do not represent all implementations consistent with the present application. Instead, they are merely examples of devices and methods consistent with some aspects of the present application as detailed in the appended claims.

[0039] It should be noted that the user information (including but not limited to user device information, user personal information, etc.) and data (including but not limited to data used for analysis, stored data, displayed data, etc.) involved in this application are all information and data authorized by the user or fully authorized by all parties, and the collection, use and processing of relevant data must comply with relevant laws, regulations and standards, and provide corresponding operation entrances for users to choose to authorize or refuse.

[0040] In the billing system of the telecommunications industry, the bill management center, as the source of bill data collection, not only provides billing bill data for billing, but also provides bill data for other systems. However, different systems require different bill data. At present, in the prior art, computers are mainly used to copy and mark bill data according to the needs of different systems, and the same bill data is copied into multiple copies and distributed to different systems. However, this method of the prior art will occupy a lot of computer resources.

[0041] In order to solve the above technical problems, the embodiments of the present application propose the following technical ideas: Considering that copying the same call record data into multiple copies and distributing them to different systems will occupy a large amount of computer resources, the inventor thought of classifying multiple call record data according to the demand information of multiple back-end systems, and sending call record data of multiple demand types to multiple back-end systems respectively, thereby reducing the occupation of computer resources.

[0042] The call record distribution method provided in this application is intended to solve the above technical problems in the prior art.

[0043] The technical solution of the present application and how the technical solution of the present application solves the above-mentioned technical problems are described in detail below with specific embodiments. The following specific embodiments can be combined with each other, and the same or similar concepts or processes may not be repeated in some embodiments. The embodiments of the present application will be described below in conjunction with the accompanying drawings.

[0044] Figure 1 Schematic diagram of application scenarios of the call bill distribution system provided in the embodiment of the present application. Figure 1 As shown, the application scenario includes: operator network equipment 101, server 102, Kafka cluster 103, object storage system 104 and multiple backend systems 105.

[0045] Among them, the operator network equipment 101 obtains multiple call record data and sends the multiple call record data to the server 102; the server 102 sends the multiple call record data to the Kafka cluster 103 according to the attribute information of each call record data; the Kafka cluster 103 saves the multiple call record data to multiple topics in the Kafka cluster, and sends the multiple call record data to the server 102; the server 102 performs a series of processing on the multiple call record data to obtain multiple call record cache files, and sends the multiple call record cache files to the object storage system 104; the object storage system 104 caches the multiple call record cache files; the server 102 receives the multiple call record cache files sent by the object storage system 104, and sends the multiple call record cache files to multiple back-end systems 105.

[0046] Figure 2This is a flow chart of a method for distributing a call receipt provided by an embodiment of the present application. The execution subject of this embodiment may be Figure 1 The server 102 in the embodiment may also be other servers with similar functions, and this embodiment does not impose any special restrictions here. Figure 2 As shown, the method includes:

[0047] S201: Receive multiple call record data sent by the operator's network equipment.

[0048] Among them, the call record data is the original communication record information, which is mainly used to record the original communication status of the communication equipment.

[0049] Specifically, multiple call record data sent by the operator network device can be received through wireless communication, and multiple call record data sent by the operator network device can also be received through wired communication.

[0050] S202: Send the multiple call record data to the Kafka cluster according to the attribute information of each call record data, so that the multiple topics in the Kafka cluster save the multiple call record data.

[0051] Specifically, according to the attribute information of each call bill data, multiple call bill data are classified to obtain multiple types of call bill data; the multiple types of call bill data are sent to the Kafka cluster, so that multiple topics in the Kafka cluster save the multiple call bill data.

[0052] The attribute information includes: the region to which the call record belongs, the call record type and the province code. There are multiple topics in the Kafka cluster. The topic is used as a logical container to classify multiple call record data.

[0053] In this embodiment, a plurality of call record data are classified according to the region to which each call record data belongs, the call record type and the province code.

[0054] Exemplarily, the multiple types of call bill data are: voice call bill data of Province A, traffic call bill data of Province A, traffic call bill data of Province B, and SMS call bill data of Province C, etc.

[0055] S203: receiving multiple call record data sent by the Kafka cluster, and obtaining demand information of multiple backend systems; classifying the multiple call record data according to the demand information to obtain call record data of various demand types.

[0056] Optionally, the multiple backend systems may be a backend system of Province A, a backend system of Province B, a backend system of Province C, and the like.

[0057] For example, the demand information of the backend system of Province A may be the voice bill data of Province A and the traffic bill data of Province A; the demand information of the backend system of Province B may be the traffic bill data of Province B and the SMS bill data of Province B; the demand information of the backend system of Province C may be the SMS bill data of Province C;

[0058] S204: Save the call record data of various demand types into multiple call record temporary files.

[0059] S205: All temporary call bill files that meet the cache condition among the multiple temporary call bill files are determined as multiple call bill cache files.

[0060] The cache condition is that the time difference between the creation time of each temporary call record file and the current time exceeds a preset time threshold; or the size of each temporary call record file exceeds a preset file size threshold.

[0061] In this embodiment, the preset time threshold and the preset file size threshold are preset.

[0062] Optionally, if the local disk capacity is large enough, or the access speed requirement for stored data is high, a relatively large file size threshold and time threshold are pre-set; if the local storage space is tight or the call record cache files need to be frequently cached to the object storage system, a relatively small file size threshold and time threshold are pre-set.

[0063] S206: Cache the multiple call record cache files to the object storage system, so that the object storage system saves the multiple call record cache files.

[0064] Optionally, the object storage system can be MinIO.

[0065] S207: receiving multiple call record cache files sent by the object storage system, and sending the multiple call record cache files to multiple backend systems.

[0066] In this embodiment, after multiple call record cache files are successfully sent to multiple backend systems, the object storage system deletes the multiple call record cache files.

[0067] It can be seen from the above embodiments that by classifying multiple call record data according to the demand information of multiple back-end systems, call record data of multiple demand types are obtained, so as to distribute the call record data of each demand type to the corresponding back-end system; this avoids copying multiple call record data and sending the copied results to multiple back-end systems, thereby reducing the occupancy of computer resources.

[0068] Figure 3 This is a flow chart of a method for distributing a call receipt provided by another embodiment of the present application. The execution subject of this embodiment may be Figure 1The server 102 in the embodiment may also be other servers with similar functions. This embodiment is not particularly limited here. This embodiment focuses on how to process multiple call list data when a new backend system appears, and send the call list data corresponding to the new backend system to the new backend system, such as Figure 3 As shown, the method includes:

[0069] S301: If there is a newly added backend system, determine whether there is any newly added demand information in the demand information.

[0070] S302: If it is determined that there is no new demand information in the demand information, at least one call bill data corresponding to the new demand information sent by the Kafka cluster is received, wherein the at least one call bill data is obtained from multiple topics in the Kafka cluster according to old offsets.

[0071] In a Kafka cluster, the old offset refers to the position of the consumer when it consumes the topic. When the consumer is restarted or rebalanced, it records the offset of the next message to be read, which is the old offset.

[0072] In this embodiment, if there is no newly added demand information in the demand information, at least one call record data corresponding to the newly added demand information obtained from multiple topics in the Kafka cluster according to the old offset is received.

[0073] S303: Save at least one call record data to at least one call record temporary file.

[0074] S304: Determine all temporary call bill files that meet the cache condition in at least one temporary call bill file as at least one call bill cache file.

[0075] In this embodiment, the cache conditions are consistent with the cache conditions in the previous embodiment and will not be repeated here.

[0076] S305: Cache at least one call record cache file to the object storage system, so that the object storage system saves the at least one call record cache file.

[0077] S306: Receive at least one call record cache file sent by the object storage system, and send the at least one call record cache file to the newly added backend system.

[0078] In this embodiment, if it is determined that there is new demand information in the demand information, at least one call record cache file corresponding to the new demand information sent by the object storage system is received, and the at least one call record cache file is sent to the newly added backend system.

[0079] It can be seen from the above embodiments that if there is new demand information in the demand information, at least one call bill cache file sent by the object storage system is received, and at least one call bill cache file is sent to the newly added backend system; if there is no new demand information in the demand information, at least one call bill data corresponding to the new demand information obtained according to the old offset from multiple topics in the Kafka cluster is received, thereby realizing rapid support for changes in the backend system, thereby reducing the workload and difficulty of multiple links such as demand, operation and maintenance, implementation, research and development, and testing, and further improving the efficiency of call bill distribution.

[0080] Figure 4 This is a schematic diagram of the structure of the bill distribution device provided in the embodiment of the present application. Figure 4 As shown, the call bill distribution device includes: a first receiving module 401, a first sending module 402, a second receiving module 403, a saving module 404, a determining module 405, a caching module 406 and a second sending module 407.

[0081] The first receiving module 401 is used to receive a plurality of call record data sent by the operator network equipment.

[0082] The first sending module 402 is used to send the multiple call record data to the Kafka cluster according to the attribute information of each call record data, so that the multiple topics in the Kafka cluster save the multiple call record data.

[0083] The second receiving module 403 is used to receive the multiple call record data sent by the Kafka cluster and obtain demand information of multiple backend systems; classify the multiple call record data according to the demand information to obtain call record data of multiple demand types.

[0084] The saving module 404 is used to save the call record data of the multiple demand types into multiple call record temporary files.

[0085] The determination module 405 is used to determine all temporary call record files that meet the cache condition among the multiple temporary call record files as multiple call record cache files.

[0086] The cache module 406 is used to cache the multiple call record cache files to the object storage system, so that the object storage system saves the multiple call record cache files.

[0087] The second sending module 407 is used to receive the multiple call record cache files sent by the object storage system, and send the multiple call record cache files to multiple backend systems.

[0088] Optionally, in the method as described above, the first sending module 402 is specifically used to: classify the multiple call record data according to the attribute information of each call record data to obtain multiple types of call record data; send the multiple types of call record data to the Kafka cluster, so that multiple topics in the Kafka cluster save the multiple call record data.

[0089] Optionally, in the method described above, the call record distribution device also includes: a determination module 408, which is used to determine whether there is new demand information in the demand information if there is a new back-end system; if it is determined that the new demand information exists in the demand information, receiving at least one call record cache file corresponding to the new demand information sent by the object storage system, and sending the at least one call record cache file to the new back-end system.

[0090] Optionally, in the method as described above, the determination module 408 is also used to: if it is determined that the newly added demand information does not exist in the demand information, then receive at least one call record data corresponding to the newly added demand information sent by the Kafka cluster, wherein the at least one call record data is obtained according to the old offset for multiple topics in the Kafka cluster; save the at least one call record data to at least one call record temporary file; determine all call record temporary files in the at least one call record temporary file that meet the caching condition as the at least one call record cache file; cache the at least one call record cache file to the object storage system, so that the object storage system saves the at least one call record cache file; receive the at least one call record cache file sent by the object storage system, and send the at least one call record cache file to the newly added back-end system.

[0091] Optionally, as described above, the call record distribution device further includes: a cache condition setting module 409, used to set the cache condition: the time difference between the creation time of each call record temporary file and the current time exceeds a preset time threshold; or, the size of each call record temporary file exceeds a preset file size threshold.

[0092] Figure 5 The hardware structure diagram of the server provided in the embodiment of the present application is shown in FIG. Figure 5 As shown, the server of this embodiment includes: at least one processor 501 and a memory 502; the memory stores computer execution instructions; at least one processor executes the computer execution instructions stored in the memory, so that at least one processor executes the above call record distribution method.

[0093] Optionally, the memory 502 may be independent or integrated with the processor 501 .

[0094] When the memory 502 is independently provided, the server further includes a bus 503 for connecting the memory 502 and the processor 501 .

[0095] An embodiment of the present application also provides a computer-readable storage medium, in which computer-executable instructions are stored. When a processor executes the computer-executable instructions, the call record distribution method as described above is implemented.

[0096] An embodiment of the present application also provides a computer program product, including a computer program, which is stored in a computer storage medium. At least one processor can read the computer program from the computer storage medium, and when at least one processor executes the computer program, the above-mentioned call record distribution method can be implemented.

[0097] It should be noted that, for the aforementioned method embodiments, for the sake of simplicity, they are all expressed as a series of action combinations, but those skilled in the art should be aware that the present application is not limited by the described order of actions, because according to the present application, certain steps can be performed in other orders or simultaneously. Secondly, those skilled in the art should also be aware that the embodiments described in the specification are all optional embodiments, and the actions and modules involved are not necessarily required by the present application.

[0098] It should be further noted that, although the various steps in the flowchart are displayed in sequence according to the indication of the arrows, these steps are not necessarily executed in sequence in the order indicated by the arrows. Unless there is a clear description in this article, the execution of these steps is not strictly limited in order, and these steps can be executed in other orders. Moreover, at least a portion of the steps in the flowchart may include multiple sub-steps or multiple stages, and these sub-steps or stages are not necessarily executed at the same time, but can be executed at different times, and the execution order of these sub-steps or stages is not necessarily to be carried out in sequence, but can be executed in turn or alternately with other steps or at least a portion of the sub-steps or stages of other steps.

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

[0100] In addition, unless otherwise specified, each functional unit / module in each embodiment of the present application may be integrated into one unit / module, each unit / module may exist physically separately, or two or more units / modules may be integrated together. The above-mentioned integrated unit / module may be implemented in the form of hardware or in the form of a software program module.

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

[0102] If the integrated unit / module is implemented in the form of a software program module and sold or used as an independent product, it can be stored in a computer-readable memory. Based on this understanding, the technical solution of the present application, or the part that contributes to the prior art or all or part of the technical solution, can be embodied in the form of a software product, which is stored in a memory and includes several instructions for a computer device (which can be a personal computer, a server or a network device, etc.) to perform all or part of the steps of the various embodiments of the present application. The aforementioned memory includes: U disk, read-only memory (ROM, Read-Only Memory), random access memory (RAM, Random Access Memory), mobile hard disk, disk or optical disk and other media that can store program codes.

[0103] In the above embodiments, the description of each embodiment has its own emphasis. For the part not described in detail in a certain embodiment, please refer to the relevant description of other embodiments. The technical features of the above embodiments can be combined arbitrarily. In order to make the description concise, all possible combinations of the technical features in the above embodiments are not described. However, as long as there is no contradiction in the combination of these technical features, they should be considered to be within the scope of this specification.

[0104] Those skilled in the art will readily appreciate other embodiments of the present application after considering the specification and practicing the invention disclosed herein. The present application is intended to cover any modification, use or adaptation of the present application, which follows the general principles of the present application and includes common knowledge or customary techniques in the art that are not disclosed in the present application. The specification and examples are intended to be exemplary only, and the true scope and spirit of the present application are indicated by the following claims.

[0105] It should be understood that the present application is not limited to the precise structures that have been described above and shown in the drawings, and that various modifications and changes may be made without departing from the scope thereof. The scope of the present application is limited only by the appended claims.

Claims

1. A method for distributing call records, characterized in that: Applicable to servers, including: Receive multiple call record data sent by the operator's network equipment; According to the attribute information of each call record data, the multiple call record data are sent to the Kafka cluster, so that the multiple topics in the Kafka cluster save the multiple call record data; Receive the multiple call sheet data sent by the Kafka cluster, and obtain demand information of multiple backend systems; classify the multiple call sheet data according to the demand information to obtain call sheet data of multiple demand types; Saving the call sheet data of the multiple demand types into multiple call sheet temporary files; Determine all temporary call record files that meet the cache condition among the multiple temporary call record files as multiple call record cache files; Cache the multiple call record cache files to an object storage system so that the object storage system saves the multiple call record cache files; The multiple call record cache files sent by the object storage system are received, and the multiple call record cache files are sent to multiple backend systems.

2. The method according to claim 1, characterized in that The sending the plurality of call record data to the Kafka cluster according to the attribute information of each call record data, so that the plurality of topics in the Kafka cluster save the plurality of call record data, includes: Classifying the plurality of call record data according to the attribute information of each call record data to obtain multiple types of call record data; The multiple types of call record data are sent to the Kafka cluster, so that the multiple topics in the Kafka cluster save the multiple call record data.

3. The method according to any one of claims 1 or 2, characterized in that: After receiving the plurality of call record cache files sent by the object storage system and sending the plurality of call record cache files to a plurality of backend systems, the method further includes: If there is a newly added backend system, determining whether there is newly added demand information in the demand information; If it is determined that the newly added demand information exists in the demand information, at least one call record cache file corresponding to the newly added demand information sent by the object storage system is received, and the at least one call record cache file is sent to the newly added backend system.

4. The method according to claim 3, characterized in that If there is a newly added backend system, after determining whether there is newly added demand information in the demand information, the method further includes: If it is determined that the newly added demand information does not exist in the demand information, receiving at least one call list data corresponding to the newly added demand information sent by the Kafka cluster, wherein the at least one call list data is obtained according to the old offset for multiple topics in the Kafka cluster; Saving the at least one call record data to at least one call record temporary file; Determine all temporary bill files that meet the cache condition in the at least one temporary bill file as the at least one temporary bill file; Cache the at least one call record cache file to the object storage system so that the object storage system saves the at least one call record cache file; Receive the at least one call record cache file sent by the object storage system, and send the at least one call record cache file to the newly added backend system.

5. The method according to claim 1, characterized in that The cache conditions are: The time difference between the creation time of each temporary call record file and the current time exceeds the preset time threshold; or The size of each temporary CDR file exceeds the preset file size threshold.

6. A call bill distribution device, characterized in that: Applicable to servers, including: A first receiving module, used to receive a plurality of call record data sent by an operator network device; A first sending module, configured to send the plurality of call record data to a Kafka cluster according to attribute information of each call record data, so that the plurality of call record data are saved by the plurality of topics in the Kafka cluster; A second receiving module is used to receive the multiple call list data sent by the Kafka cluster and obtain demand information of multiple backend systems; classify the multiple call list data according to the demand information to obtain call list data of multiple demand types; A saving module, used for saving the call sheet data of the plurality of demand types into a plurality of call sheet temporary files; A determination module, configured to determine all temporary call bill files that meet the cache condition among the multiple temporary call bill files as multiple call bill cache files; A cache module, used for caching the plurality of call record cache files to an object storage system, so that the object storage system saves the plurality of call record cache files; The second sending module is used to receive the multiple call record cache files sent by the object storage system, and send the multiple call record cache files to multiple backend systems.

7. The device according to claim 6, characterized in that The first sending module is specifically used to: classify the multiple call record data according to the attribute information of each call record data to obtain multiple types of call record data; send the multiple types of call record data to the Kafka cluster respectively, so that the multiple topics in the Kafka cluster can save the multiple call record data.

8. The device according to claim 6, characterized in that The device also includes a determination module, which is specifically used to: if there is a newly added backend system, determine whether there is newly added demand information in the demand information; if it is determined that the newly added demand information exists in the demand information, receive at least one call record cache file corresponding to the newly added demand information sent by the object storage system, and send the at least one call record cache file to the newly added backend system.

9. A server, characterized in that: It comprises at least one processor and a memory; the memory stores computer-executable instructions; the at least one processor executes the computer-executable instructions stored in the memory, so that the at least one processor executes the call record distribution method as described in any one of claims 1-5.

10. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores computer-executable instructions. When the processor executes the computer-executable instructions, the call record distribution method as described in any one of claims 1 to 5 is implemented.

Images