A method and apparatus for processing a call record
By obtaining user packages and determining call detail record (CDR) costs based on package type and historical consumption patterns, the problem of low CDR processing efficiency is solved, and storage resources are saved while the processing flow is simplified.
Patent Information
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- CHINA UNITED NETWORK COMM GRP CO LTD
- Filing Date
- 2022-12-20
- Publication Date
- 2026-05-12
AI Technical Summary
Call detail record (CDR) processing consumes a lot of storage resources and is inefficient. Existing technologies require complex processes such as format conversion, standard tariff pricing, package tariff pricing, and deduplication.
By obtaining the target user's data plan, if it is an unlimited data plan, the plan fee is directly used as the call detail record (CDR) fee; if it is a limited data plan, the CDR fee is determined based on the relationship between the historical total consumption and the total plan amount, combined with numerical values and thresholds, thus avoiding a complicated processing procedure.
It improved the efficiency of call detail record (CDR) processing, reduced storage resource consumption, and simplified the processing flow.
Smart Images
Figure CN116260910B_ABST
Abstract
Description
Technical Field
[0001] This application relates to the field of telecommunications, and more particularly to a method and apparatus for processing call detail records (CDRs). Background Technology
[0002] The telecommunications industry uses call detail records (CDRs) as the billing standard, with a daily CDR processing volume of over 200 billion records. As society develops, the scale of CDRs continues to rise.
[0003] Currently, all call detail record (CDR) processing generally requires a series of processes such as format conversion, standard tariff approval, package tariff approval, and deduplication. Therefore, it not only consumes a lot of storage resources, but also leads to a decrease in CDR processing efficiency. Summary of the Invention
[0004] This application provides a call detail record (CDR) processing method and apparatus, which can improve the efficiency of CDR processing.
[0005] To achieve the above objectives, this application adopts the following technical solution:
[0006] Firstly, this application provides a call detail record (CDR) processing method, which includes:
[0007] Obtain the target user's monthly subscription plan.
[0008] If the user's plan is an unlimited data plan, then the plan fee will be used as the target user's monthly call charge.
[0009] Based on the above technical solution, the call detail record (CDR) processing method provided in this application can obtain the target user's monthly data plan. If the user's data plan is an unlimited data plan, the plan fee is used as the target user's monthly CDR fee. This method directly uses the plan fee of an unlimited data plan as the target user's monthly CDR fee, without requiring all CDRs to undergo a series of complex processes such as format conversion, standard tariff approval, data plan tariff approval, and deduplication. Therefore, it can effectively improve the efficiency of CDR processing.
[0010] Optionally, the method further includes:
[0011] If the user's data plan is determined to be a limited data plan, the monthly call charge for the target user is determined based on the relationship between the target user's total historical data consumption and the total data included in the historical user plans over the past period, and the preset first condition. Total historical data consumption refers to the target user's total data consumption in all months prior to the current month; historical user plans refer to the user plans corresponding to the target user in all months prior to the current month.
[0012] Optionally, the first condition is that the target user's total historical consumption is less than the total amount included in the user's historical data plan. Based on the relationship between the target user's total historical consumption and the total amount included in the user's historical data plan within a historical time period, and the preset first condition, the target user's monthly call charge is determined, including:
[0013] If the relationship between the target user's historical total consumption and the total amount of data included in the historical user's data plan within a historical time period meets the first condition, then the target user's monthly call charge is determined based on the first value and the first threshold; the first value is an approximate figure of the target user's monthly total consumption.
[0014] Optionally, based on the first value and the first threshold, determine the target user's monthly call charge, including:
[0015] If the first value is less than the first threshold, the user's package fee will be used as the target user's monthly call charge.
[0016] If the first value is greater than or equal to the first threshold, then the monthly call charge of the target user is determined based on the second value; the second value is the total monthly consumption of the target user.
[0017] Optionally, the method further includes:
[0018] If the relationship between the target user's historical total consumption and the total amount included in the historical user's package does not meet the first condition within the historical time period, then the target user's monthly call charge will be determined based on the second value; the second value is the target user's monthly total consumption.
[0019] Secondly, this application provides a call detail record (CDR) processing apparatus, the apparatus comprising:
[0020] The acquisition unit is used to acquire the target user's monthly subscription plan.
[0021] The unit is defined so that if the user's plan is an unlimited data plan, the plan fee of the user's plan will be used as the target user's monthly call bill fee.
[0022] Optionally, the determining unit is also used for:
[0023] If the user's data plan is determined to be a limited data plan, the monthly call charge for the target user is determined based on the relationship between the target user's total historical data consumption and the total data included in the historical user plans over the past period, and the preset first condition. Total historical data consumption refers to the target user's total data consumption in all months prior to the current month; historical user plans refer to the user plans corresponding to the target user in all months prior to the current month.
[0024] Optionally, the first condition is that the target user's total historical consumption is less than the total amount included in the historical user's data plan; this determining unit is specifically used for:
[0025] If the relationship between the target user's historical total consumption and the total amount of data included in the historical user's data plan within a historical time period meets the first condition, then the target user's monthly call charge is determined based on the first value and the first threshold; the first value is an approximate figure of the target user's monthly total consumption.
[0026] Optionally, the determining unit is specifically used for:
[0027] If the first value is less than the first threshold, the user's package fee will be used as the target user's monthly call charge.
[0028] If the first value is greater than or equal to the first threshold, then the monthly call charge of the target user is determined based on the second value; the second value is the total monthly consumption of the target user.
[0029] Optionally, the determining unit is also used for:
[0030] If the relationship between the target user's historical total consumption and the total amount included in the historical user's package does not meet the first condition within the historical time period, then the target user's monthly call charge will be determined based on the second value; the second value is the target user's monthly total consumption.
[0031] Thirdly, this application provides a call detail record (CDR) processing apparatus, which includes: a processor and a communication interface; the communication interface and the processor are coupled, and the processor is used to run computer programs or instructions to implement the CDR processing method as described in the first aspect and any possible implementation thereof.
[0032] Fourthly, this application provides a computer-readable storage medium storing instructions that, when executed on a terminal, cause the terminal to perform the call detail record (CDR) processing method as described in the first aspect and any possible implementation thereof.
[0033] Fifthly, embodiments of this application provide a computer program product containing instructions that, when run on a call detail record (CDR) processing device, cause the CDR processing device to perform the CDR processing method as described in the first aspect and any possible implementation thereof.
[0034] In a sixth aspect, embodiments of this application provide a chip including a processor and a communication interface, the communication interface being coupled to the processor, the processor being used to run computer programs or instructions to implement the call detail record (CDR) processing method as described in the first aspect and any possible implementation thereof.
[0035] Specifically, the chip provided in this application embodiment also includes a memory for storing computer programs or instructions. Attached Figure Description
[0036] Figure 1 This application scenario diagram illustrates a call detail record (CDR) processing method provided in an embodiment of this application.
[0037] Figure 2 A flowchart illustrating a call detail record (CDR) processing method provided in this application embodiment;
[0038] Figure 3 A flowchart illustrating another call detail record (CDR) processing method provided in this application embodiment;
[0039] Figure 4 This is a schematic diagram of the structure of a call detail record (CDR) processing device provided in an embodiment of this application;
[0040] Figure 5 This is a schematic diagram of another call detail record (CDR) processing device provided in an embodiment of this application. Detailed Implementation
[0041] The following is a detailed description of a call detail record (CDR) processing method and apparatus provided in the embodiments of this application, with reference to the accompanying drawings.
[0042] In this article, the term "and / or" is merely a description of the relationship between related objects, indicating that there can be three relationships. For example, A and / or B can represent three situations: A exists alone, A and B exist simultaneously, and B exists alone.
[0043] The terms "first" and "second," etc., used in the specification and drawings of this application are used to distinguish different objects or to distinguish different treatments of the same object, rather than to describe a specific order of objects.
[0044] Furthermore, the terms "comprising" and "having," and any variations thereof, used in the description of this application are intended to cover non-exclusive inclusion. For example, a process, method, system, product, or apparatus that includes a series of steps or units is not limited to the steps or units listed, but may optionally include other steps or units not listed, or may optionally include other steps or units inherent to such process, method, product, or apparatus.
[0045] It should be noted that in the embodiments of this application, the words "exemplary" or "for example" are used to indicate examples, illustrations, or explanations. Any embodiment or design scheme described as "exemplary" or "for example" in the embodiments of this application should not be construed as being more preferred or advantageous than other embodiments or design schemes. Specifically, the use of the words "exemplary" or "for example" is intended to present the relevant concepts in a specific manner.
[0046] Figure 1 This application scenario diagram illustrates a call detail record (CDR) processing method provided in an embodiment of this application. Figure 1 As shown in the diagram, this application scenario may include a terminal device 101, a network 102, and a server 103. The network 102 provides a communication link between the terminal device 101 and the server 103. The network 102 may include various connection types, such as wired or wireless communication links, or fiber optic cables, etc.
[0047] In this application, the terminal device 101 is a terminal device capable of installing a SIM card (Subscriber Identity Module), also referred to as a terminal, mobile station (MS), mobile terminal (MT), etc. It is a device that provides voice and / or data connectivity to users. For example, terminal device 101 can be a handheld device or in-vehicle device with wireless connectivity. Specifically, it can be a smartphone, pocket personal computer (PPC), handheld computer, personal digital assistant (PDA), laptop computer, tablet computer, wearable device, or in-vehicle device, etc. This application does not limit the specific technology, quantity, or form of the terminal device 101.
[0048] It should be noted that, Figure 1 This is just an example framework diagram. Figure 1 The names of the various devices included are unrestricted, and except for Figure 1 In addition to the functional nodes shown, other nodes may also be included, but this application embodiment does not limit this.
[0049] The telecommunications industry uses call detail records (CDRs) as its billing standard, processing over 200 billion CDRs daily, and this number continues to rise with societal development. Currently, all CDR processing generally involves a series of processes, including format conversion, standard tariff approval, package tariff approval, and deduplication. Therefore, this not only consumes significant storage resources but also reduces CDR processing efficiency.
[0050] To address the aforementioned technical problems, this application provides a call detail record (CDR) processing method and apparatus. This method can obtain the target user's monthly user package and then determine the target user's monthly CDR cost based on the user package. This approach allows for the determination of the target user's monthly CDR cost based on the user package, eliminating the need for a series of complex processes such as format conversion, standard tariff pricing, package tariff pricing, and deduplication for all CDRs. Therefore, it effectively improves the efficiency of CDR processing.
[0051] Figure 2 A flowchart of a call detail record (CDR) processing method provided in an embodiment of this application is shown below. Figure 2 As shown, the method includes the following steps:
[0052] Step S201: Obtain the target user's monthly user package.
[0053] Specifically, the user plan subscribed to by the target user in the current month can be obtained based on the target user's user identifier. The target user's user identifier can be the target user's SIM number, name, etc., and this application does not limit this.
[0054] Step S202: If the user's plan is an unlimited plan, then the plan fee of the user's plan will be used as the target user's monthly call charge.
[0055] After obtaining the target user's monthly data plan through step S201, if the user plan is an unlimited data plan, the plan fee can be used as the target user's monthly call charge.
[0056] Using the above method, the cost of unlimited data plans can be directly used as the monthly call detail record (CDR) cost for the target user, without having to go through a series of complex processes such as format conversion, standard tariff pricing, plan tariff pricing, and deduplication for all users' CDRs. Therefore, it can effectively improve the efficiency of CDR processing.
[0057] Figure 3 A flowchart of another call detail record (CDR) processing method provided in the embodiments of this application is shown below. Figure 3 As shown, the method includes:
[0058] Step S301: Obtain the target user's monthly user package.
[0059] Step S302: Is the target user's monthly data plan an unlimited data plan? If yes, proceed to step S303; otherwise, proceed to step S304.
[0060] Unlimited data plans may include unlimited call minutes, unlimited cellular data, and unlimited SMS messages, etc. This application does not limit them.
[0061] Step S303: Use the user's package fee as the target user's monthly call detail record fee.
[0062] For example, suppose there are two user plans, Plan A and Plan B, where Plan A is an unlimited plan and Plan B is a limited plan. The intention is to collect the call charges for each user in November.
[0063] In one embodiment, assuming the target user is user A, step S201 determines that user A's user package for November is package A. Since package A is an unlimited data package, the package fee corresponding to user A's user package for November can be directly used as user A's call detail record fee for November.
[0064] Step S304: Within the historical time period, does the total historical consumption of the target user and the total amount of packages included in the historical user packages meet the preset first condition? If yes, proceed to step S305; if no, proceed to step S306.
[0065] Among them, the total historical consumption refers to the total consumption of the target user in all months before the current month; the historical user package refers to the user package corresponding to the target user in all months before the current month.
[0066] Specifically, in one optional implementation, the first preset condition can be that the target user's total historical consumption is less than the total amount of data included in the historical user's data plan.
[0067] For example, assuming the current month is November, in one embodiment, the target user's historical total consumption can be the total call duration and / or total cellular data traffic consumed by the target user in October, and the historical user plan can be the user plan subscribed by the target user in October. A preset first condition can be that the target user's historical total consumption in October is less than the target user's total plan subscription amount in October.
[0068] In another embodiment, the target user's historical total consumption can be the total call duration and / or total cellular data traffic consumed by the target user in October and September, respectively, and the historical user plan can be the user plan subscribed by the target user in October and September, respectively. A preset first condition can be that the target user's historical total consumption in October is less than the target user's total plan subscription in October, and the target user's historical total consumption in September is less than the target user's total plan subscription in September.
[0069] Step S305: Determine the monthly call detail record (CDR) cost for the target user based on the first value and the first threshold.
[0070] The first value is an approximate estimate of the target user's total consumption for the month. For example, assuming the current month is November, the target user's call duration for each day in November (in minutes) is as follows: 10, 11, 0, 0, 0, 0, 0, 12, 13, 15, 0, 0, 5, 6, 25, 0, 0, 0, 0, 2, 10, 0, 9, 0, 36, 0, 25, 0, 13, 17. Then, the target user's call duration for each day in November can be recorded as: 10, 10, 0, 0, 0, 0, 0, 10, 10, 20, 0, 0, 10, 10, 30, 0, 0, 0, 0, 0, 10, 0, 10, 0, 40, 0, 30, 0, 10, 20. The first value is the sum of the above approximate values.
[0071] In this application embodiment, the first threshold can be determined based on the user's historical total consumption or based on the user's subscribed package; this application does not limit this.
[0072] Specifically, in one optional implementation, in the process of determining the monthly call charge of the target user based on the first value and the first threshold, if the first value is less than the first threshold, the monthly user package fee of the target user can be directly used as the monthly call charge of the target user; if the first value is greater than or equal to the first threshold, the monthly call charge of the target user can be determined based on the second value, wherein the second value is the total monthly consumption of the target user.
[0073] For example, assuming the current month is November, the call duration of the target user on each day in November is as follows (in minutes): 10, 11, 0, 0, 0, 0, 0, 12, 13, 15, 0, 0, 5, 6, 25, 0, 0, 0, 0, 2, 10, 0, 9, 0, 36, 0, 25, 0, 13, 17. Then the second value is the sum of the above data.
[0074] In this embodiment of the application, in the process of determining the monthly call detail record (CDR) cost of the target user based on the second value, the monthly CDR cost of the target user can be determined through a series of processes such as format conversion, standard tariff pricing, package tariff pricing, and deduplication.
[0075] Step S306: Determine the monthly call detail record (CDR) cost for the target user based on the second value.
[0076] Specifically, in step S306, the process of determining the target user's monthly call charge based on the second value is similar to the process of determining the target user's monthly call charge based on the second value in step S305 above, and will not be repeated here.
[0077] In this embodiment of the application, during the processing of the call details of the target user for the current month, the data can also be stored at the user level, for example, by storing the target user's name as the identifier, so that the various call details of the target user for the current month can be extracted more quickly in the subsequent processing.
[0078] For example, before determining the monthly call detail record (CDR) cost of the target user based on the second value, the CDR cost of the target user for the current month can be stored at the user level. This allows for the rapid extraction of each CDR for the target user in the current month when determining the monthly CDR cost based on the second value, thereby effectively improving the efficiency of CDR processing.
[0079] Using the above method, when the target user's user plan is an unlimited plan, or when the target user's historical total consumption and the total amount of data included in the historical user plan meet the preset first condition, the monthly call detail record (CDR) cost of the target user can be determined based on the target user's current monthly user plan. This eliminates the need for a series of complex processes such as format conversion, standard tariff pricing, plan tariff pricing, and deduplication for all users' CDRs. Therefore, it can effectively improve the efficiency of CDR processing.
[0080] Figure 4 This is a schematic diagram of the structure of a call detail record (CDR) processing device provided in an embodiment of this application, as shown below. Figure 4 As shown, the device includes:
[0081] Acquisition unit 401 is used to acquire the target user's monthly user package;
[0082] Unit 402 is used to determine the monthly call charge of the target user if the user's plan is an unlimited plan.
[0083] Optionally, the determining unit 402 is also used for:
[0084] If the user's plan is determined to be a limited plan, the monthly call charge for the target user is determined based on the relationship between the target user's total historical consumption and the total amount of data included in the historical user plan within the historical time period and the preset first condition. The total historical consumption refers to the target user's total consumption in all months prior to the current month; the historical user plan refers to the user plan corresponding to the target user in all months prior to the current month.
[0085] Optionally, the first condition is that the target user's total historical consumption is less than the total amount included in the historical user's data plan; the determining unit 402 is specifically used for:
[0086] If, within a historical time period, the relationship between the target user's total historical consumption and the total amount included in the historical user's package satisfies the first condition, then the target user's monthly call charge is determined based on the first value and the first threshold; the first value is an approximate figure for the target user's total monthly consumption.
[0087] Optionally, the determining unit 402 is specifically used for:
[0088] If the first value is less than the first threshold, the user's package fee will be used as the target user's monthly call charge.
[0089] If the first value is greater than or equal to the first threshold, then the monthly call charge of the target user is determined based on the second value; the second value is the total monthly consumption of the target user.
[0090] Optionally, the determining unit 402 is also used for:
[0091] If the relationship between the target user's historical total consumption and the total amount included in the historical user's package does not meet the first condition within the historical time period, then the target user's monthly call charge will be determined based on the second value; the second value is the target user's monthly total consumption.
[0092] Figure 5 This diagram illustrates another possible structural design of the call detail record (CDR) processing device described in the above embodiments. The CDR processing device includes a processor 501 and a communication interface 502. The processor 501 controls and manages the operation of the CDR processing device, and the communication interface 502 supports communication between the CDR processing device and other network entities. The CDR processing device may also include a memory 503 and a bus 504. The memory 503 stores the program code and data of the CDR processing device.
[0093] The memory 503 may be a memory in a call detail record (CDR) processing device, and may include volatile memory, such as random access memory; the memory may also include non-volatile memory, such as read-only memory, flash memory, hard disk or solid-state drive; the memory may also include a combination of the above types of memory.
[0094] The processor 501 described above can implement or execute various exemplary logic blocks, modules, and circuits described in conjunction with the disclosure of this application. The processor can be a central processing unit, a general-purpose processor, a digital signal processor, an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA), or other programmable logic devices, transistor logic devices, hardware components, or any combination thereof. It can implement or execute various exemplary logic blocks, modules, and circuits described in conjunction with the disclosure of this application. The processor can also be a combination that implements computing functions, such as including one or more microprocessor combinations, a combination of a DSP and a microprocessor, etc.
[0095] Bus 504 can be an Extended Industry Standard Architecture (EISA) bus, etc. Bus 504 can be divided into address bus, data bus, control bus, etc. For ease of representation, Figure 5 The bus is represented by a single thick line, but this does not mean that there is only one bus or one type of bus.
[0096] Through the above description of the embodiments, those skilled in the art will clearly understand that, for the sake of convenience and brevity, only the division of the above functional modules is used as an example. In practical applications, the above functions can be assigned to different functional modules as needed, that is, the internal structure of the device can be divided into different functional modules to complete all or part of the functions described above. The specific working process of the system, device, and unit described above can be referred to the corresponding process in the foregoing method embodiments, and will not be repeated here.
[0097] This application provides a computer program product containing instructions that, when run on a computer, causes the computer to execute the call detail record (CDR) processing method described in the above method embodiments.
[0098] This application also provides a computer-readable storage medium storing instructions that, when executed on a computer, cause the computer to perform the call detail record (CDR) processing method in the method flow shown in the above method embodiments.
[0099] The computer-readable storage medium may be, for example, but not limited to, an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any combination thereof. More specific examples (a non-exhaustive list) of computer-readable storage media include: electrical connections having one or more wires; portable computer disks; hard disks; random access memory (RAM); read-only memory (ROM); erasable programmable read-only memory (EPROM); registers; hard disks; optical fibers; portable compact disc read-only memory (CD-ROM); optical storage devices; magnetic storage devices; or any suitable combination thereof; or any other form of computer-readable storage medium known in the art. An exemplary storage medium is coupled to a processor, enabling the processor to read information from and write information to the storage medium. Of course, the storage medium may also be a component of the processor. The processor and the storage medium may reside in an application-specific integrated circuit (ASIC). In the embodiments of this application, the computer-readable storage medium can be any tangible medium that contains or stores a program that can be used by or in conjunction with an instruction execution system, apparatus, or device.
[0100] Embodiments of the present invention provide a computer program product containing instructions that, when executed on a computer, cause the computer to perform the call detail record (CDR) processing method described in the embodiments of this application.
[0101] Since the call detail record processing device, computer-readable storage medium, and computer program product in the embodiments of the present invention can be applied to the above-described method, the technical effects obtained can also be referred to the above-described method embodiments. The embodiments of the present invention will not be described again here.
[0102] In the several embodiments provided in this application, it should be understood that the disclosed systems, devices, and methods can be implemented in other ways. For example, the device embodiments described above are merely illustrative; for instance, the division of units is only a logical functional division, and in actual implementation, there may be other division methods. For example, multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed. Furthermore, the mutual coupling or direct coupling or communication connection shown or discussed may be through some interfaces; the indirect coupling or communication connection between devices or units may be electrical, mechanical, or other forms.
[0103] The units described as separate components may or may not be physically separate. The components shown as units may or may not be physical units; that is, they may be located in one place or distributed across multiple network units. Some or all of the units can be selected to achieve the purpose of this embodiment according to actual needs.
[0104] In addition, the functional units in the various embodiments of this application can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit.
[0105] The above are merely specific embodiments of this application, but the scope of protection of this application is not limited thereto. Any variations or substitutions within the technical scope disclosed in this application should be included within the scope of protection of this application. Therefore, the scope of protection of this application should be determined by the scope of the claims.
Claims
1. A call detail record (CDR) processing method, characterized in that, The method includes: Obtain the target user's monthly subscription plan; If the user package is an unlimited data plan, then the package fee of the user package will be used as the monthly call charge for the target user. If the user package is a limited-time package, and the relationship between the target user's historical total consumption and the total amount of data included in the historical user package within a historical period satisfies a first condition, then if the first value is less than a first threshold, the package fee of the user package will be used as the target user's monthly call charge; the first value is an approximate figure of the target user's total monthly consumption; the historical total consumption refers to the target user's total consumption in all months prior to the current month; the historical user package refers to the user package corresponding to the target user in all months prior to the current month, and the first condition includes that the target user's historical total consumption in each month is less than the target user's total package amount in the corresponding month; If the first value is greater than or equal to the first threshold, the monthly call details of the target user are stored at the user level, and the standard tariff approval and package tariff approval processing flow is executed according to the second value to determine the monthly call details of the target user; the second value is the total monthly consumption of the target user. If the relationship between the target user's historical total consumption and the total amount of packages included in the historical user's packages does not meet the first condition within the historical time period, then the target user's monthly call details are stored at the user level, and the standard tariff approval and package tariff approval processing flow is executed according to the second value to determine the target user's monthly call details; the second value is the target user's monthly total consumption.
2. A call detail record (CDR) processing device, characterized in that, The device includes: The acquisition unit is used to acquire the target user's monthly subscription plan. The determining unit is used to determine the monthly call charge of the target user if the user package is an unlimited data package. The determining unit is further configured to, when determining that the user package is a limited-use package, and when the relationship between the target user's historical total consumption and the total package amount included in the historical user package within a historical time period satisfies a first condition, if the first value is less than a first threshold, then use the package fee of the user package as the target user's monthly call charge; the first value is an approximate figure of the target user's monthly total consumption; the historical total consumption refers to the target user's total consumption in each month prior to the current month; the historical user package refers to the user package corresponding to the target user in each month prior to the current month, and the first condition includes that the target user's historical total consumption in each month is less than the target user's package amount in the corresponding month; If the first value is greater than or equal to the first threshold, the monthly call details of the target user are stored at the user level, and the standard tariff approval and package tariff approval processing flow is executed according to the second value to determine the monthly call details of the target user; the second value is the total monthly consumption of the target user. The determining unit is further configured to, if the relationship between the total historical consumption of the target user and the total amount of packages included in the historical user packages does not meet the first condition during the historical time period, store the target user's monthly call details at the user level, and execute the standard tariff approval and package tariff approval processing flow according to the second value to determine the target user's monthly call details; the second value is the target user's total monthly consumption.
3. A call detail record (CDR) processing device, characterized in that, include: A processor and a communication interface; the communication interface is coupled to the processor, the processor being used to run computer programs or instructions to implement the call detail record (CDR) processing method as described in claim 1.
4. A computer-readable storage medium storing instructions, characterized in that, When the computer executes the instruction, the computer performs the call detail record (CDR) processing method as described in claim 1.