Data processing method and device, electronic equipment and computer readable storage medium

Abstract

The application provides a data processing method and device, electronic equipment and computer readable storage medium. The data processing method comprises: receiving a user's to-be-charged bill; obtaining the user's package data; the package data is used to represent the user's current consumption behavior; determining whether the user is a charging abnormal user according to the user's package data and a preset user charging portrait; the user charging portrait is used to represent the predicted user's consumption behavior; if the user is a charging abnormal user, the user's charging information is corrected to obtain the corrected charging information; and performing charging operation on the user according to the corrected charging information and the to-be-charged bill. The application can improve the efficiency of charging abnormal correction.

Description

Technical Field

[0001] This application relates to the field of computer technology, and in particular to a data processing method, apparatus, electronic device, and computer-readable storage medium. Background Technology

[0002] After obtaining a user's call detail records (CDRs), the telecommunications industry's billing system combines the user's billing information, package details, and package usage to calculate the call detail record's cost data and then bill the user accordingly. However, during information transmission, errors may occur in the user's billing information, which could lead to incorrect call detail record costs.

[0003] Currently, the correction method for billing anomalies in user billing data is as follows: After the aforementioned billing system completes the calculation of user call detail records (CDRs) and corresponding billing, the CDR billing data auditing system compares the user billing data represented by the CDR with the user billing data stored in the billing system. When the CDR billing data auditing system finds a discrepancy between the two, maintenance personnel will further verify the correct user billing data offline. When the correct user data differs from the user billing data stored in the billing system, the maintenance personnel manually re-enter the correct user billing data into the billing system so that the billing system can recalculate the billing data and perform billing operations for that CDR.

[0004] However, the above-mentioned methods for correcting billing anomalies have problems such as low efficiency and poor timeliness. Summary of the Invention

[0005] This application provides a data processing method, apparatus, electronic device, and computer-readable storage medium to improve the efficiency of billing anomaly correction.

[0006] In a first aspect, this application provides a data processing method, the method comprising:

[0007] Receive users' pending billing call details;

[0008] Obtain the user's service plan data; the service plan data is used to characterize the user's current consumption behavior.

[0009] Based on the user's package data and a preset user billing profile, it is determined whether the user is a user with abnormal billing; the user billing profile is used to characterize the predicted consumption behavior of the user.

[0010] If the user is a user with billing irregularities, the user's billing data will be corrected to obtain corrected billing data.

[0011] Billing operations are performed on the user based on the revised billing data and the call detail records to be billed.

[0012] Optionally, the package data includes: the user's billing information, the user's package information, and the user's package usage; the user billing profile is used to represent the relationship between the billing information, package information, and package usage.

[0013] The step of determining whether a user is a user with abnormal billing based on the user's package data and a preset user billing profile includes:

[0014] Compare the user's package data with the user's billing profile;

[0015] If the user's package data satisfies the correlation represented by the user billing profile, then the user is determined to be a non-billing abnormal user.

[0016] If the user's package data does not meet the correlation represented by the user billing profile, then the user is determined to be a billing anomaly user.

[0017] Optionally, before determining whether a user is a user with abnormal billing based on the user's package data and a preset user billing profile, the method further includes:

[0018] Obtain sample data, which includes historical data of at least one sample user;

[0019] Based on the sample data, the user billing profile is obtained.

[0020] Optionally, the step of correcting the user's billing data to obtain corrected billing data includes:

[0021] Based on the user's package data, the user's billing information is corrected to obtain the initial corrected billing information;

[0022] Output the initially corrected billing data;

[0023] If a confirmation instruction is received for the initially revised billing data, the initially revised billing data will be used as the revised billing data.

[0024] Optionally, the step of performing billing operations on the user based on the revised billing data and the call detail record to be billed includes:

[0025] Using the initially corrected billing data and the call detail records to be billed, a billing operation is performed on the user to obtain the user's temporary billing result;

[0026] After using the initially revised billing data as the revised billing data, the initial billing result is changed to the user's actual billing result.

[0027] Optionally, changing the initial billing result to the user's actual billing result includes:

[0028] Based on the revised billing data and the call detail records to be billed, it is re-determined whether the user is a user with billing irregularities;

[0029] If it is determined that the user is not a user with billing irregularities, then the initial billing result will be changed to the user's actual billing result.

[0030] Optionally, the method further includes:

[0031] If a modification instruction is received for the initially revised billing data, the initially revised billing data is modified based on the modification instruction to obtain the revised billing data.

[0032] Optionally, the step of performing billing operations on the user based on the revised billing data and the call detail record to be billed includes:

[0033] Based on the revised billing data and the call detail records to be billed, it is re-determined whether the user is a user with billing irregularities;

[0034] If it is determined that the user is not a user with billing abnormality, then the pre-stored billing information of the user and the call detail record to be billed are used to perform billing operations on the user to obtain the actual billing result of the user.

[0035] Optionally, after determining whether the user is a user with abnormal billing based on the user's package data and a preset user billing profile, the method further includes:

[0036] If the user is not a user with billing irregularities, then billing operations will be performed on the user based on the user's billing information and the call detail records to be billed.

[0037] Secondly, this application provides a data processing apparatus, the apparatus comprising:

[0038] The receiving module is used to receive users' pending billing call details;

[0039] The first acquisition module is used to acquire the user's package data; the package data is used to characterize the user's current consumption behavior.

[0040] The determination module is used to determine whether the user is a user with abnormal billing based on the user's package data and a preset user billing profile; the user billing profile is used to characterize the predicted consumption behavior of the user.

[0041] The correction module is used to correct the billing data of the user when the user is a user with billing abnormality, so as to obtain the corrected billing data.

[0042] The billing module is used to perform billing operations on the user based on the revised billing data and the call detail records to be billed.

[0043] Thirdly, this application provides an electronic device, the electronic device comprising: at least one processor and a memory;

[0044] The memory stores computer-executed instructions;

[0045] The at least one processor executes computer execution instructions stored in the memory, causing the electronic device to perform the method described in any one of the first aspects.

[0046] Fourthly, this application provides a computer-readable storage medium storing computer-executable instructions, which, when executed by a processor, are used to implement the method described in any one of the first aspects.

[0047] The data processing method, apparatus, electronic device, and computer-readable storage medium provided in this application can determine whether a user's current consumption behavior matches the predicted consumption behavior by acquiring user package data and a preset user billing profile. This allows for the determination of whether the user is a billing anomaly user. When a user is determined to be a billing anomaly user, the user's billing information is promptly corrected, and the user is re-billed using the corrected billing information. This reduces the lag in user billing information confirmation and correction, thereby improving the efficiency of billing anomaly correction. Attached Figure Description

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

[0049] Figure 1 This is a schematic diagram of the communication architecture of a data processing method provided in an embodiment of this application;

[0050] Figure 2 This is a schematic diagram of the communication architecture for another data processing method provided in this application embodiment;

[0051] Figure 3This is a flowchart illustrating a data processing method provided in an embodiment of this application;

[0052] Figure 4 This is a schematic diagram of the structure of a data processing device provided in an embodiment of this application;

[0053] Figure 5 This is a schematic diagram of the structure of an electronic device provided in an embodiment of this application.

[0054] The accompanying drawings illustrate specific embodiments of this application, which will be described in more detail below. These drawings and descriptions are not intended to limit the scope of the concept in any way, but rather to illustrate the concept of this application to those skilled in the art through reference to particular embodiments. Detailed Implementation

[0055] Exemplary embodiments will now be described in detail, examples of which are illustrated in the accompanying drawings. When the following description relates to the drawings, unless otherwise indicated, the same numbers in different drawings denote the same or similar elements. The embodiments described in the following exemplary embodiments do not represent all embodiments consistent with this application. Rather, they are merely examples of apparatuses and methods consistent with some aspects of this application as detailed in the appended claims.

[0056] First, let me explain the terms used in this application:

[0057] Call detail record (CDR): Also known as a detailed record, it refers to the user's original communication records.

[0058] Taking a landline telephone as an example, the call detail record (CDR) mainly includes call records, which may include: serial number, user identifier, caller ID, called number, start time, end time, call duration, call type (whether it is a roaming call), rate, discount, etc.

[0059] Taking mobile phones as an example, in addition to call records as described above, call detail records typically include Short Message Service (SMS) usage records, Wireless Application Protocol (WAP) usage records, and General Packet Radio Service (GPRS) usage records. The content of these records is similar to that of call records. For example, GPRS usage records may include: serial number, user identifier, start time, end time, GPRS usage duration, GPRS type (whether it's out-of-plan data), rate, discount, etc.

[0060] User billing information: User information used to identify users and calculate their call detail records (CDRs).

[0061] For example, user billing information may include: user identifier, user location, user's package type, whether it is a family shared account, etc.

[0062] Package: A product formed by operators integrating various communication service products they provide.

[0063] The billing rules for each communication service product within a package usually differ from the billing rules when those services are sold individually. Furthermore, the billing rules for the same communication service product within different packages offered by the same operator often vary.

[0064] For example, a user's package information may include: the service types included in the user's package and the available quantity of each service, as well as the billing rules for call details for different service types. For instance, User A's package type is Package 1, which includes 100 minutes of call time per month (calendar month). Call details exceeding this limit are billed at 1 yuan per minute. In this case, if User A's total call time in a calendar month is less than or equal to 100 minutes, User A only needs to pay for Package 1 in that month, without paying additional call detail charges. Conversely, if User A's total call time in a calendar month exceeds 100 minutes, User A will need to pay for both Package 1 and the additional call detail charges at 1 yuan per minute.

[0065] Package usage: The number of times a user uses each service included in the package during a package usage period, and the relationship between the number of times each service is used and the number of times the corresponding service is available.

[0066] If the user billing data stored in the operator's billing system is not updated in a timely manner or is entered incorrectly, the call detail record (CDR) cost data calculated based on that billing data may also be incorrect.

[0067] Unlike existing solutions, this application provides a data processing method, apparatus, electronic device, and computer-readable storage medium that can correct user billing data in advance using the pending billing call detail record (CDR) before billing is completed, thereby improving the efficiency of billing anomaly handling.

[0068] The following is combined Figure 1 and Figure 2 This paper introduces the application scenarios of this application.

[0069] Figure 1This is a schematic diagram of the communication architecture of a data processing method provided in an embodiment of this application, such as... Figure 1 As shown, the communication architecture includes a call detail record (CDR) system and a billing system. The CDR system is used to collect and generate user call detail records (CDRs) and provide them to the billing system. The billing system is used to perform billing operations on users based on the CDRs provided by the CDR system and the user's service plan data.

[0070] Figure 2 This is a schematic diagram of the communication architecture for another data processing method provided in this application embodiment, such as... Figure 2 As shown, the communication architecture includes a billing system. This billing system comprises a call detail record (CDR) subsystem and a billing subsystem. That is, in this communication architecture, the billing system is used both for CDR statistics and generation, and for billing operations.

[0071] The following examples use Figure 1 The communication architecture shown is used as an example for detailed explanation. The execution subject of the data processing method provided in this application can be either an electronic device in the billing system or a component with processing capabilities (e.g., a chip) within that electronic device; this application does not impose any limitations on this. The following embodiments are exemplary descriptions using an electronic device as the execution subject.

[0072] It should be understood that the electronic devices mentioned here may be, for example, devices used in a billing system to perform billing operations, such as servers.

[0073] The technical solution of this application and how the technical solution of this application solves the above-mentioned technical problems are described in detail below with specific embodiments. These specific embodiments can be combined with each other, and the same or similar concepts or processes may not be described again in some embodiments. The embodiments of this application will now be described with reference to the accompanying drawings.

[0074] Figure 3 This is a flowchart illustrating a data processing method provided in an embodiment of this application. Figure 3 As shown, the method of this application may include:

[0075] S101 receives the user's pending billing call details.

[0076] For example, the call detail record (CDR) system can send the pending CDR for a communication activity to the electronic device after the user completes a communication activity through a first terminal. Alternatively, the CDR system can send the user's pending CDR to the electronic device based on a preset period. Or, the CDR system can send the user's pending CDR to the electronic device based on the statistical or reporting method corresponding to the user's billing data.

[0077] S102, obtain the user's package data.

[0078] Among them, package data is used to characterize the user's current consumption behavior.

[0079] For example, an electronic device can retrieve a user's package data from multiple user data stored in the electronic device by using the user identifier in the pending billing record. Alternatively, the user's package data can also be sent to the electronic device by a device in another system that stores such data.

[0080] The package data may include, for example, the user's billing information, the user's package information, and the user's package usage data.

[0081] S103. Based on the user's package data and the preset user billing profile, determine whether the user is a billing anomaly user. If yes, proceed to S104; otherwise, proceed to S106.

[0082] Among them, the user billing profile is used to characterize the predicted user's consumption behavior.

[0083] For example, a user billing profile can be calculated by an electronic device based on the user's historical consumption behavior, representing the probability of the user engaging in various consumption behaviors. In this case, the higher the probability of a user engaging in a certain consumption behavior in the user billing profile, the more likely the electronic device is to predict that consumption behavior will occur.

[0084] Alternatively, a user billing profile can also be a chain of tags that represents the relationship between billing data, package information, and package usage.

[0085] As one possible implementation, the electronic device can obtain a preset user billing profile based on the user's historical package data. For example, the electronic device can retrieve the user's historical package data for the previous N (N is an integer greater than or equal to 1) billing cycles based on the user identifier, calculate the average historical package usage of the user within a billing cycle, and then extract the user's billing information, package information, and historical package usage average tags respectively. Finally, a mapping relationship is established between these three tags to obtain a tag chain containing the three tags.

[0086] As another possible implementation, the electronic device can also select a user billing profile matching the user from a pre-established user billing profile library based on the user's billing data, package information, and package usage, and use this profile as the preset user billing profile. For example, the electronic device can first obtain the historical package data of at least one sample user as sample data, and then use the sample data to construct the user billing profile library. For instance, the electronic device can retrieve the historical package data of M users for the first N (N is an integer greater than or equal to 1) billing cycles, calculate the average historical package usage of the M users in one billing cycle, then extract the labels for each sample user's billing data, package information, and average historical package usage, and finally establish a mapping relationship between these three labels for each sample user to obtain M label chains containing the three labels, thereby obtaining the user billing profile library.

[0087] For example, when a user's package data meets the correlation represented by the user billing profile, the electronic device can determine that the user is a billing anomaly user.

[0088] Correspondingly, when a user's package data does not meet the correlation represented by the user billing profile, the electronic device can determine that the user is a billing anomaly user.

[0089] It should be understood that the aforementioned generation of user billing profiles can also be generated by other devices based on the historical package data of sample users and then provided to the electronic device for use; this application does not limit this.

[0090] S104, correct the user's billing data to obtain the corrected billing data.

[0091] For example, the electronic device can feed back the user's billing information to the maintenance personnel's client, whereby the maintenance personnel can verify the user's billing information based on the client and feed back the correct billing information to the electronic device through the client.

[0092] Alternatively, the electronic device can modify the user's billing information based on the user's package data. For example, it can replace the user's billing information stored in the electronic device with the user's billing information carried in the package data to obtain the initially modified billing information.

[0093] In this implementation, as one possible approach, the electronic device can directly use the initially modified billing data as the modified billing data.

[0094] As another possible implementation, the electronic device can also output the initially revised billing information. For example, it can output this information to the client of the maintenance personnel, notifying them to reconfirm the accuracy of the initially revised billing information and use the confirmed billing information as the revised billing information.

[0095] In this implementation, for example, after receiving a confirmation instruction for the initially revised billing data, the electronic device can use the initially revised billing data as the revised billing data. Alternatively, when the electronic device receives a modification instruction for the initially revised billing data, the electronic device can modify the initially revised billing data according to the relevant instructions in the modification instruction to obtain the revised billing data.

[0096] S105 performs billing operations on the user based on the revised billing data and the call detail records to be billed.

[0097] For example, the electronic device can determine the correct billing rules based on the correct billing data, calculate the cost data of the user's pending call detail records according to the correct billing rules, and then deduct the calculated call detail record cost data from the user's account.

[0098] Taking the aforementioned electronic device correcting the user's billing information based on the acquired user's package data as an example:

[0099] For example, after receiving the initially revised billing data, the electronic device can use the initially revised billing data and the call detail records (CDRs) to be billed to calculate the temporary cost data of the user's CDRs, and perform billing operations on the user to obtain the user's temporary billing result. For instance, a billing rule can be determined based on the initially revised billing data, and the cost data of the user's CDRs to be billed can be calculated according to the billing rule to obtain the temporary cost data.

[0100] Electronic devices can directly change the initial billing result to the user's actual billing result after using the initially revised billing data as the revised billing data.

[0101] Alternatively, after obtaining the corrected billing data, the electronic device can use the user's billing profile again, based on the corrected billing data and the call detail records to be billed, to determine whether the user is a user with abnormal billing. In this case, the following two situations may occur.

[0102] Scenario 1: The electronic device determines that the user is not a user with billing abnormality at this time.

[0103] For example, in this case, the electronic device can directly change the user's initial billing result to the actual billing result.

[0104] Alternatively, the electronic device can recalculate and bill the user's billing data based on the revised billing information and the billing details to be billed, thus obtaining the user's actual billing result.

[0105] Scenario 2: The electronic device determines that the user is still a user with abnormal billing at this time.

[0106] In this scenario, for example, the electronic device can output alarm information to the maintenance personnel's client, indicating that the above situation has occurred, and wait for instructions from the maintenance personnel.

[0107] S106. Using the pre-stored user billing information and the call detail record to be billed, perform billing operations on the user.

[0108] For example, an electronic device can determine the billing rules based on the user's billing data stored in its own memory, calculate the cost data of the user's pending call detail records according to the billing rules, and then deduct the calculated call detail record cost data from the user's account.

[0109] The data method provided in this application can determine whether a user's current consumption behavior matches the predicted consumption behavior by obtaining user package data and preset user billing profiles, thereby determining whether the user is a billing anomaly user. When a user is determined to be a billing anomaly user, the user's billing information is corrected in a timely manner, and the user is re-billed using the corrected billing information, thereby improving the efficiency of billing anomaly correction.

[0110] Figure 4 This is a schematic diagram of the structure of a data processing device provided in an embodiment of this application. Figure 4 As shown, the device includes: a receiving module 21, a first acquisition module 22, a determining module 23, a correcting module 24, and a billing module 25. Exemplarily, the data processing device may further include: a second acquisition module 26. Wherein:

[0111] Receiver module 21 is used to receive the user's pending billing call details;

[0112] The first acquisition module 22 is used to acquire the user's package data; the package data is used to characterize the user's current consumption behavior.

[0113] The determination module 23 is used to determine whether a user is a user with abnormal billing based on the user's package data and a preset user billing profile; the user billing profile is used to characterize the predicted user's consumption behavior.

[0114] The correction module 24 is used to correct the user's billing data when the user is a user with billing abnormality, and obtain the corrected billing data.

[0115] The billing module 25 is used to perform billing operations on users based on the revised billing data and the call details to be billed.

[0116] Optionally, the package data includes: user billing information, user package information, and user package usage; the user billing profile is used to represent the relationship between billing information, package information, and package usage; for example, the determining module 23 is specifically used to: compare the user's package data with the user billing profile; when the user's package data satisfies the relationship represented by the user billing profile, determine that the user is not a billing anomaly user; when the user's package data does not satisfy the relationship represented by the user billing profile, determine that the user is a billing anomaly user.

[0117] Optionally, the data processing device further includes: a second acquisition module 26, configured to acquire sample data before the determination module 23 determines whether a user is a user with abnormal billing based on the user's package data and a preset user billing profile; and to acquire a user billing profile based on the sample data, wherein the sample data includes historical package data of at least one sample user.

[0118] Optionally, the correction module 24 is specifically used to correct the user's billing information based on the user's package data to obtain the initially corrected billing information; output the initially corrected billing information; and, upon receiving a confirmation instruction for the initially corrected billing information, use the initially corrected billing information as the corrected billing information.

[0119] In one possible implementation, the billing module 25 is specifically used to perform billing operations on the user using the initially revised billing data and the call detail records (CDRs) to be billed, thereby obtaining a temporary billing result for the user; after using the initially revised billing data as the revised billing data, the initial billing result is changed to the user's actual billing result. For example, the billing module 25 is specifically used to re-determine whether the user is a billing anomaly user based on the revised billing data and the CDRs to be billed; if the user is determined not to be a billing anomaly user, the initial billing result is changed to the user's actual billing result.

[0120] In another possible implementation, the correction module 24 is also used to modify the initially corrected billing data based on the modification instruction when it receives the modification instruction for the initially corrected billing data, so as to obtain the corrected billing data.

[0121] In this implementation, for example, the determination module 23 is specifically used to re-determine whether a user is a billing abnormal user based on the corrected billing data and the call detail records to be billed; the billing module 25 is specifically used to perform billing operations on the user using the pre-stored billing data of the user and the call detail records to be billed when it is determined that the user is not a billing abnormal user, so as to obtain the user's actual billing result.

[0122] Optionally, the billing module 25 is also used to perform billing operations on the user based on the user's billing information and the call detail records to be billed when the user is not an abnormal billing user, after the determination module 23 determines whether the user is an abnormal billing user based on the user's package data and the preset user billing profile.

[0123] The data processing apparatus provided in this application is used to execute the aforementioned data processing method embodiments. Its implementation principle and technical effect are similar, and will not be described in detail here.

[0124] Figure 5 This is a schematic diagram of the structure of an electronic device provided in an embodiment of this application. For example... Figure 5 As shown, the electronic device 400 may include at least one processor 401 and a memory 402.

[0125] The memory 402 is used to store programs. Specifically, the program may include program code, which includes computer operation instructions.

[0126] The memory 402 may include high-speed random access memory (RAM) and may also include non-volatile memory, such as at least one disk storage device.

[0127] The processor 401 is used to execute computer execution instructions stored in the memory 402 to implement the data processing method described in the foregoing method embodiments. Exemplarily, the electronic device may be, for example, the electronic device in the foregoing method embodiments. The processor 401 may be a central processing unit (CPU), an application-specific integrated circuit (ASIC), or one or more integrated circuits configured to implement the embodiments of this application.

[0128] Optionally, the electronic device 400 may also include a communication interface 403. In specific implementations, if the communication interface 403, memory 402, and processor 401 are implemented independently, they can be interconnected via a bus to complete communication. The bus can be an Industry Standard Architecture (ISA) bus, a Peripheral Component Interconnect (PCI) bus, or an Extended Industry Standard Architecture (EISA) bus, etc. Buses can be categorized as address buses, data buses, control buses, etc., but this does not imply that there is only one bus or one type of bus.

[0129] Optionally, in a specific implementation, if the communication interface 403, memory 402 and processor 401 are integrated on a single chip, then the communication interface 403, memory 402 and processor 401 can communicate through an internal interface.

[0130] This application also provides a computer-readable storage medium, which may include various media capable of storing program code, such as a USB flash drive, a portable hard drive, a read-only memory (ROM), a RAM memory, a magnetic disk, or an optical disk. Specifically, the computer-readable storage medium stores program instructions, which are used in the methods described in the above embodiments.

[0131] This application also provides a program product including executable instructions stored in a readable storage medium. At least one processor of an electronic device can read the executable instructions from the readable storage medium, and the at least one processor executes the executable instructions to cause the electronic device to perform the data processing methods provided in the various embodiments described above.

[0132] Finally, it should be noted that the above embodiments are only used to illustrate the technical solutions of this application, and are not intended to limit them. Although this application has been described in detail with reference to the foregoing embodiments, those skilled in the art should understand that modifications can still be made to the technical solutions described in the foregoing embodiments, or equivalent substitutions can be made to some or all of the technical features therein. Such modifications or substitutions do not cause the essence of the corresponding technical solutions to deviate from the scope of the technical solutions of the embodiments of this application.

Claims

1. A data processing method, characterized in that, The method includes: Receive users' pending billing call details; Obtain the user's service plan data; the service plan data is used to characterize the user's current consumption behavior. Based on the user's package data and a preset user billing profile, it is determined whether the user is a user with abnormal billing; the user billing profile is used to characterize the predicted consumption behavior of the user. If the user is a user with billing irregularities, the user's billing data will be corrected to obtain corrected billing data. Billing operations are performed on the user based on the revised billing data and the call details to be billed; The package data includes: the user's billing data, the user's package information, and the user's package usage; the user billing profile is used to represent the relationship between the billing data, package information, and package usage. The step of determining whether a user is a user with abnormal billing based on the user's package data and a preset user billing profile includes: Compare the user's package data with the user's billing profile; If the user's package data satisfies the correlation represented by the user billing profile, then the user is determined to be a non-billing abnormal user. If the user's package data does not meet the correlation represented by the user billing profile, then the user is determined to be a billing anomaly user.

2. The method according to claim 1, characterized in that, Before determining whether a user is a user with abnormal billing based on the user's package data and a preset user billing profile, the method further includes: Obtain sample data, which includes historical data of at least one sample user; Based on the sample data, the user billing profile is obtained.

3. The method according to claim 1 or 2, characterized in that, The step of correcting the user's billing data to obtain corrected billing data includes: Based on the user's package data, the user's billing information is corrected to obtain the initial corrected billing information; Output the initially corrected billing data; If a confirmation instruction is received for the initially revised billing data, the initially revised billing data will be used as the revised billing data.

4. The method according to claim 3, characterized in that, The step of performing billing operations on the user based on the revised billing data and the call detail records to be billed includes: Using the initially corrected billing data and the call detail records to be billed, a billing operation is performed on the user to obtain the user's temporary billing result; After using the initially revised billing data as the revised billing data, the initial billing result is changed to the user's actual billing result.

5. The method according to claim 4, characterized in that, Changing the initial billing result to the user's actual billing result includes: Based on the revised billing data and the call detail records to be billed, it is re-determined whether the user is a user with billing irregularities; If it is determined that the user is not a user with billing irregularities, then the initial billing result will be changed to the user's actual billing result.

6. The method according to claim 3, characterized in that, The method further includes: If a modification instruction is received for the initially revised billing data, the initially revised billing data is modified based on the modification instruction to obtain the revised billing data.

7. The method according to claim 6, characterized in that, The step of performing billing operations on the user based on the revised billing data and the call detail records to be billed includes: Based on the revised billing data and the call detail records to be billed, it is re-determined whether the user is a user with billing irregularities; If it is determined that the user is not a user with billing abnormality, then billing operations are performed on the user based on the corrected billing data and the call detail record to be billed, so as to obtain the actual billing result of the user.

8. The method according to claim 1 or 2, characterized in that, After determining whether the user is a user with abnormal billing based on the user's package data and a preset user billing profile, the process further includes: If the user is not a user with billing irregularities, then the pre-stored billing information of the user and the call detail record to be billed are used to perform the billing operation on the user.

9. A data processing apparatus, characterized in that, The device includes: The receiving module is used to receive users' pending billing call details; The first acquisition module is used to acquire the user's package data; the package data is used to characterize the user's current consumption behavior; the package data includes: the user's billing information, the user's package information, and the user's package usage status; The determination module is used to determine whether the user is a user with abnormal billing based on the user's package data and a preset user billing profile; the user billing profile is used to characterize the correlation between the predicted user's consumption behavior and billing data, package information, and package usage. The correction module is used to correct the billing data of the user when the user is a user with billing abnormality, so as to obtain the corrected billing data. The billing module is used to perform billing operations on the user based on the revised billing data and the call detail record to be billed; The determining module is specifically used to compare the user's package data with the user's billing profile; If the user's package data satisfies the correlation represented by the user billing profile, then the user is determined to be a non-abnormal billing user; if the user's package data does not satisfy the correlation represented by the user billing profile, then the user is determined to be an abnormal billing user.

10. An electronic device, characterized in that, The electronic device includes: at least one processor and a memory; The memory stores computer-executed instructions; The at least one processor executes computer execution instructions stored in the memory, causing the electronic device to perform the method of any one of claims 1-8.

11. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores computer-executable instructions, which, when executed by a processor, are used to implement the method of any one of claims 1-8.

Images