Call detail record auditing method, device, apparatus, medium and product

Abstract

This application provides a call detail record (CDR) auditing method and apparatus, relating to the field of communication technology. The CDR auditing method includes: obtaining the rate switching time point of billing data for a user session; segmenting the offline and online CDRs of the user session based on the rate switching time point; and performing CDR auditing on the segmented offline and online CDRs. The method based on this application provides a unified interface for offline and online CDRs, facilitating CDR auditing.

Description

Technical Field

[0001] This application relates to the field of communication technology, and in particular to a call detail record (CDR) auditing method, apparatus, equipment, medium, and product. Background Technology

[0002] To ensure the correct processing of online billing in the billing system, it is necessary to audit and check the traffic generated by online billing for online call detail records (CDRs) and the traffic generated by the core network for offline CDRs. In related technologies, due to the differences in the mechanisms by which the core network system generates CDRs and the billing system—the former generating CDRs at the session level, while the latter generates CDRs based on online messages—it is difficult to align the online and offline CDRs in terms of time when auditing them, resulting in poor accuracy in CDR auditing. Summary of the Invention

[0003] This application provides a call detail record (CDR) auditing method and device to improve the accuracy of CDR auditing.

[0004] In a first aspect, embodiments of this application provide a call detail record (CDR) auditing method, the method comprising: The rate switching time point for obtaining billing data from user sessions; After the rate switching time point is reached, the segmented offline call detail records (CDRs) and the segmented online CDRs are obtained; the segmented offline CDRs and the segmented online CDRs are segmented based on the rate switching time point. Perform call detail record (CDR) audits on the segmented offline CDRs and the segmented online CDRs.

[0005] Secondly, embodiments of this application provide a call detail record (CDR) auditing method, the method comprising: The rate switching time point for obtaining billing data from user sessions; The offline call detail records (CDRs) of a user session are segmented based on the rate switching time point to obtain segmented offline CDRs. The segmented offline CDRs are used for CDR auditing with the segmented online CDRs, which are segmented based on the rate switching time point.

[0006] Thirdly, embodiments of this application provide a call detail record (CDR) auditing method, the method comprising: The rate switching time point for obtaining billing data from user sessions; The online call detail records (CDRs) of a user session are segmented based on the rate switching time point to obtain segmented online CDRs. The segmented online CDRs are used for CDR auditing with the segmented offline CDRs, which are segmented based on the rate switching time point.

[0007] Fourthly, embodiments of this application provide a call detail record (CDR) auditing device, the device comprising: The time point acquisition module is used to obtain the rate switching time point of the billing data for user sessions; The call detail record (CDR) acquisition module is used to acquire the segmented offline CDRs and the segmented online CDRs after the rate switching time point is reached; the segmented offline CDRs and the segmented online CDRs are segmented based on the rate switching time point; The audit module is used to audit the segmented offline call detail records (CDRs) and the segmented online CDRs.

[0008] Fifthly, embodiments of this application provide a call detail record (CDR) auditing device, the device comprising: The time point acquisition module is used to obtain the rate switching time point of the billing data for user sessions; The segmentation module is used to segment the offline call detail records (CDRs) of a user session based on the rate switching time point to obtain segmented offline CDRs; the segmented offline CDRs are used for CDR auditing with the segmented online CDRs, and the segmented online CDRs are segmented based on the rate switching time point.

[0009] Sixthly, embodiments of this application provide a call detail record (CDR) auditing device, the device comprising: The time point acquisition module is used to obtain the rate switching time point of the billing data for user sessions; The segmentation module is used to segment the online call detail records (CDRs) of a user session based on the rate switching time point to obtain segmented online CDRs; the segmented online CDRs are used for CDR auditing with the segmented offline CDRs, and the segmented offline CDRs are segmented based on the rate switching time point.

[0010] In a seventh aspect, embodiments of this application provide an electronic device, including: A memory on which computer programs are stored; A processor for executing the computer program to implement the call detail record (CDR) auditing method described above in the first, second, or third aspect.

[0011] Eighthly, embodiments of this application provide a readable storage medium having a computer program stored thereon, the computer program being executable by a processor to implement the call detail record (CDR) auditing method described in the first, second, or third aspects above.

[0012] Ninthly, embodiments of this application provide a computer program product, including a computer program that can be executed by a processor to implement the call detail record (CDR) auditing method described in the first, second, or third aspects above.

[0013] In the above-mentioned technical solution provided in this application embodiment, by obtaining the rate switching time point of the billing data of the user session, the offline call detail records (CDRs) and online call detail records (CDRs) of the user session are segmented based on the rate switching time point, and the segmented offline and online CDRs are audited. The rate switching time point can be used as the unified segmentation time point for online and offline CDRs. When the rate switching time point is reached, offline and online CDRs are segmented simultaneously, unifying the CDR segmentation of offline and online CDRs, improving the accuracy of CDR auditing and the timeliness of audit result output. Attached Figure Description

[0014] Figure 1 This is a flowchart illustrating a call detail record (CDR) auditing method according to an embodiment of this application. Figure 2 This is a schematic diagram of the interaction flow of a call detail record (CDR) auditing method according to an embodiment of this application; Figure 3 This is an application example of a call detail record (CDR) auditing method according to an embodiment of this application; Figure 4 This is a schematic diagram of the audit process of a call detail record (CDR) auditing method according to an embodiment of this application; Figure 5 This is a schematic diagram of the audit process of a call detail record (CDR) auditing method according to an embodiment of this application. Detailed Implementation

[0015] To make the objectives, technical solutions, and advantages of this application clearer, the technical solutions of this application will be clearly and completely described below in conjunction with specific embodiments and corresponding drawings. Obviously, the described embodiments are only a part of the embodiments of this application, and not all of them. Based on the embodiments in this application, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of this application.

[0016] As will be known to those skilled in the art, with the development of technology and the emergence of new scenarios, the technical solutions provided in the embodiments of this application are also applicable to similar technical problems.

[0017] The terms "first," "second," etc., used in the specification, claims, and accompanying drawings of this application are used to distinguish similar objects and are not necessarily used to describe a specific order or sequence. It should be understood that such terms are interchangeable where appropriate; this is merely a way of distinguishing objects with the same attributes in the description of embodiments of this application. Furthermore, the terms "comprising" and "having," and any variations thereof, are intended to cover non-exclusive inclusion, so that a process, method, system, product, or apparatus that comprises a series of elements is not necessarily limited to those elements but may include other elements not explicitly listed or inherent to those processes, methods, products, or apparatuses.

[0018] Please refer to Figure 1 This is a flowchart illustrating a call detail record (CDR) auditing method according to an embodiment of this application. Figure 1 As shown, a call detail record (CDR) auditing method according to an embodiment of this application includes the following steps: S102, Obtain the rate switching time point of the billing data for the user session.

[0019] The rate switching time point refers to the moment when the rate is adjusted. In one implementation, the rate switching time point may include: a first rate switching time point and a second rate switching time point. The first rate switching time point can be the time when the rate switches from off-peak to peak hours, such as 23:00 every day. The second rate switching time point can be the time when the rate switches from peak hours to off-peak hours, such as 7:00 every day.

[0020] S104, based on the rate switching time point, splits the offline and online call detail records (CDRs) of a user session.

[0021] In this embodiment, the rate switching time point is used as the unified segmentation time point for offline and online call detail records (CDRs) to facilitate CDR auditing. In implementation, a single user session may span one or more rate switching time points. Each time a rate switching time point is reached, the offline CDRs are segmented, storing the traffic usage of the user session before and after the rate switching time point in different offline CDRs. Similarly, the online CDRs are segmented, storing the traffic usage of the user session before and after the rate switching time point in different online CDRs. This uses the rate switching time point as the data flow entry point for offline and online CDRs, facilitating time-based alignment of traffic usage during subsequent CDR auditing.

[0022] In one implementation, the above-mentioned segmentation of offline and online call detail records (CDRs) of a user session based on the rate switching time point may include: If the rate switching time point is reached, the first offline call detail record (CDR) for the user session is generated based on the traffic usage of the user session in the first offline CDR period, and the first online CDR for the user session is generated based on the traffic usage of the user session in the first online CDR period.

[0023] The first offline call detail record (CDR) period is the time period from the last offline CDR splitting time to the current rate switching time. The first online CDR period is the time period from the last online CDR splitting time to the current rate switching time.

[0024] In one implementation, the call detail record (CDR) auditing method of this application embodiment may further include: If the user session has been released, a second offline call detail record (CDR) for the user session is generated based on the traffic usage of the user session in the second offline CDR period, and a second online CDR for the user session is generated based on the traffic usage of the user session in the second online CDR period.

[0025] The second offline call detail record (CDR) period is the time period from the last offline CDR splitting time to the user session release time, and the second online CDR period is the time period from the last online CDR splitting time to the user session release time.

[0026] In the above implementation, the offline call detail record (CDR) segmentation time points can include: the user session establishment time point and the rate switching time point. The first offline CDR period is the offline CDR period ending at the rate switching time point. The first offline CDR is generated upon reaching the rate switching point and can record the traffic usage of the user session during that period. The second offline CDR period is the offline CDR period ending at the user session release time point. The second offline CDR is generated upon the release of the user session and can record the traffic usage of the user session during that period.

[0027] In implementation, if a user session does not span the rate switching time point, a first offline call detail record (CDR) may not be generated. Instead, a second offline CDR for the user session is generated based on the traffic usage of the user session within the second offline CDR period. In this case, the second offline CDR period can be the time interval from the user session establishment time to the user session release time, and the second offline CDR can record the traffic usage of the user session within this period.

[0028] If a user session spans a rate changeover period, a first offline call detail record (CDR) and a second offline CDR can be generated. The first offline CDR period can be the time interval from the user session establishment time to the rate changeover time, and it records the traffic usage of the user session during that period. The second offline CDR period can be the time interval from the rate changeover time to the user session release time, and it also records the traffic usage of the user session during that period.

[0029] If a user session spans multiple rate changeover times, multiple first offline call detail records (CDRs) and one second offline CDR can be generated. The first offline CDR period can be the time interval from the last offline CDR splitting time to the current rate changeover time. The last offline CDR splitting time could be the user session establishment time or the previous rate changeover time. The first offline CDR can record the traffic usage of the user session during this period. The second offline CDR period can be the time interval from the last offline CDR splitting time to the current user session release time. The last offline CDR splitting time could be the last rate changeover time during the user session. The second offline CDR can record the traffic usage of the user session during this period.

[0030] In the above implementation, the online call detail record (CDR) segmentation time points can include: the user session establishment time point, the authorized traffic quota exhaustion time point, and the rate switching time point. The first online CDR period is the period ending at the rate switching time point. This first online CDR is generated upon reaching the rate switching time point and records the traffic usage of the user session during that period. The second online CDR period is the period ending at the user session release time point. This second online CDR is generated upon the release of the user session and records the traffic usage of the user session during that period.

[0031] During a user session, one or more traffic authorizations can be granted, potentially resulting in one or more traffic quota exhaustion events. In addition to the first and second online call detail records (CDRs) mentioned above, a third online CDR can be generated based on the traffic usage of the user session within a third online CDR period. The third online CDR period can be the time interval from the last online CDR segmentation point to the current traffic quota exhaustion point; that is, the time interval ending at the traffic quota exhaustion point. The third online CDR is generated due to the exhaustion of authorized traffic quotas, and it records the traffic usage within that period. The last online CDR segmentation point could be the user session establishment point, the authorized traffic quota exhaustion point, or the rate switching point.

[0032] In implementation, if a user session does not span the rate switching time point, a first online call detail record (CDR) may not be generated. Instead, a second online CDR for the user session will be generated based on the traffic usage of the user session within the second online CDR period. The second online CDR period can be the time interval from the last online CDR splitting time point to the user session release time point. The second online CDR can record the traffic usage of the user session within this period. Specifically, if no traffic quota authorization is granted during the user session, the last online CDR splitting time point can be the user session establishment time point. If one or more traffic quota authorizations are granted during the user session, the last online CDR splitting time point can be the time point when the last traffic quota was exhausted before the user session is released. If one or more traffic quota authorizations are granted during the user session, a third online CDR for the user session can also be generated based on the user session's traffic usage within the third online CDR period each time the authorized traffic quota is exhausted. The third online call detail record (CDR) period is the time period from the last online CDR splitting time to the current traffic quota exhaustion time. The last online CDR splitting time may be the user session establishment time or the last authorized traffic quota exhaustion time. The third online CDR can record the traffic usage of the user session in this period.

[0033] If a user session spans one or more rate switching time points, a first online call detail record (CDR) for the user session can be generated based on the traffic usage of the user session in the first online CDR period, a second online CDR based on the traffic usage of the user session in the second online CDR period, and a third online CDR based on the traffic usage of the user session in the third CDR period. The first online CDR period can be the time interval from the last online CDR splitting time point to the current rate switching time point. The last online CDR splitting time point may be the user session establishment time point or the authorized traffic quota exhaustion time point. The second online CDR period can be the time interval from the last online CDR splitting time point to the user session release time point. The last online CDR time point may be the rate switching time point or the authorized traffic quota exhaustion time point. The third online CDR period can be the time interval from the last online CDR splitting time point to the current authorized traffic quota exhaustion time point. The last time an online call detail record (CDR) was split could be the time of rate switching or the time when the authorized traffic quota was exhausted.

[0034] S106, perform call detail record (CDR) audit on the segmented offline and online CDRs.

[0035] In practice, after each rate switching time point, the offline and online call detail records (CDRs) generated during the period from the previous rate switching time point to the current rate switching time point can be audited, and the audit results can be output without waiting for the user session to end, thereby improving the timeliness of the audit results output.

[0036] Specifically, offline and online call detail records (CDRs) can be audited according to appropriate audit dimensions. Audit dimensions include, but are not limited to, time, region, user, and session dimensions.

[0037] In one implementation, call detail records (CDRs) can be audited based on the user's assessment of offline and online CDRs for the current audit period. The aforementioned auditing of the segmented offline and online CDRs may include: The system calculates the offline call detail records (CDRs) of the target users during the current audit period, resulting in statistical offline CDR traffic for the target users during the current audit period. It also calculates the online CDRs of the target users during the current audit period, resulting in statistical online CDR traffic for the target users during the current audit period. The system then compares the offline and online CDR traffic statistics of the target users to determine if they are consistent, in order to conduct CDR audits on the target users' offline and online CDRs.

[0038] The current audit period is the time period from the last rate change date to the current rate change date. The target user can be a specified user.

[0039] In one implementation, call detail records (CDRs) can be audited based on the location of the user for the current audit period, including both offline and online CDRs. The aforementioned auditing of the segmented offline and online CDRs may include: The system calculates the traffic usage of user sessions in the target location during the current audit period to obtain the offline call detail record (CDR) statistics for the target location during the current audit period; it also calculates the online CDR statistics for the target location during the current audit period; and compares the offline CDR statistics with the online CDR statistics for the target location to perform CDR audits on the offline and online CDRs of the target location.

[0040] The current audit period is the time period from the last rate change date to the current rate change date. The target location can be the region that needs to be statistically analyzed, such as a specified province or city.

[0041] The call detail record (CDR) auditing method in this application obtains the rate switching time point, segments the offline and online CDRs of a user session based on the rate switching time point, and audits the segmented offline and online CDRs. It can use the rate switching time point as a unified segmentation time point for online and offline CDRs, and simultaneously segment offline and online CDRs when the rate switching time point is reached, unifying the CDR segmentation of offline and online CDRs, improving the accuracy of CDR auditing and the timeliness of audit result output.

[0042] Please refer to Figure 2 This is a schematic diagram of the interactive flow of a call detail record (CDR) auditing method according to an embodiment of this application. Figure 2 As shown in the embodiments of this application, the call detail record (CDR) auditing method described above can be executed collaboratively by the core network system 100, the billing system 200, and the CDR auditing system 300. The core network system 100 is communicatively connected to the billing system 200, and the CDR auditing system 300 is communicatively connected to both the core network system 100 and the billing system 200. The core network system 100 is the central system of the communication network, used for session management of user sessions and generating offline CDRs for user sessions. The billing system 200 is an online billing system, used for billing processing of user sessions and generating online CDRs for user sessions. The CDR auditing system 300 is used to audit the offline CDRs generated by the core network system 100 and the online CDRs generated by the billing system 200 to ensure the correctness of the billing processing for user sessions. Now, in conjunction with... Figure 2 The present application provides a further explanation of a call detail record (CDR) auditing method.

[0043] like Figure 2 As shown in the embodiments of this application, a call detail record (CDR) auditing method may include the following interactive process: S202, when a user session is established, the core network system 100 sends a user session billing data creation request to the billing system 200. Correspondingly, the billing system 200 receives the user session billing data creation request sent by the core network system 100.

[0044] The billing data creation request is an initial billing data request used to request billing initialization for a user session. It can carry session context information of the user session, such as the session identifier, service type, and session establishment time.

[0045] A user session is a logical connection established between a user terminal and a mobile communication network for the purpose of performing a specific service. It can be a Protocol Data Unit Session (PDU session). A user session can be established when the user's mobile terminal establishes this connection with the communication network. When the core network system 100 detects the establishment of a user session, it can generate a billing data creation request for that user session and send the request to the billing system 200.

[0046] In specific implementations, there can be one or more billing systems 200. In one implementation, there can be multiple billing systems 200, each corresponding to a home location. When a user session is established, the core network system 100 can determine the user's home location based on the user identifier of the user session and send a billing data creation request to the billing system 200 corresponding to the user's home location. The billing system 200 corresponding to the user's home location can receive the billing data creation request. For example, the billing system 200 corresponding to the user's home location is the online billing system of a certain province where the user belongs.

[0047] S204, the billing system 200 sends a billing data creation response to the core network system 100. Correspondingly, the core network system 100 receives the billing data creation response sent by the billing system 200.

[0048] Specifically, after receiving a billing data creation request for a user session, the billing system 200 can parse the billing data creation request to obtain the session context information of the user session carried in the billing data creation request. Based on the session context information of the user session, the billing system 200 performs billing initialization for the user session and then sends a billing data creation response to the core network system 100.

[0049] The billing data creation response is the response to the billing data creation request, and it can carry billing trigger event information. The billing trigger event information consists of the conditions and rules for triggering billing, which instruct the core network system 100 to send a billing data request to the billing system and report traffic usage information when a specific event occurs.

[0050] In this embodiment, the billing data creation response may carry multiple billing trigger event information, which may include: key billing trigger events. Key billing trigger events are events that simultaneously trigger the generation of online and offline call detail records (CDRs). Key billing trigger events may include: reaching the rate switching time point and user session release.

[0051] The arrival time for rate switching can be the system time at which the rate switching occurs. User session release can be the disconnection of the current connection between the user terminal and the communication network.

[0052] The rate switching time is a preset rate switching time, which may include a first rate switching time and a second rate switching time. The first rate switching time can be the time when switching from the off-peak rate period to the peak rate period, such as 7:00 a.m. every day. The second rate switching time can be the time when switching from the peak rate period to the off-peak rate period, such as 11:00 p.m. every day.

[0053] Of course, in this embodiment of the application, multiple billing trigger events may include not only key billing trigger events, but also other types of events.

[0054] In one implementation, the multiple billing trigger events may further include non-critical billing trigger events. These non-critical events can trigger online call detail record (CDR) generation but not offline CDR generation. Non-critical billing trigger events may include: exhaustion of authorized traffic quota. The authorized traffic quota is the maximum traffic allowance that a user session can use, for example, 100MB. The billing data creation response may carry authorized traffic quota information and information from various billing trigger events. These various billing trigger events may include: user session establishment, exhaustion of authorized traffic quota, arrival of rate switching time, and release of user session. Among these, arrival of rate switching time and release of user session are critical billing trigger events, while exhaustion of authorized traffic quota is a non-critical billing trigger event.

[0055] S206, if the core network system 100 detects any billing trigger event during a user session, it generates a billing data request based on the user session's traffic usage in the current online call detail record (CDR) period and sends the billing data request to the billing system 200. Correspondingly, the billing system 200 receives the billing data request sent by the core network system 100.

[0056] Specifically, upon receiving the billing data creation response, the core network system 100 can parse the response to obtain the billing trigger event information carried within it. Then, the core network system 100 can monitor user sessions and system time to detect whether a billing trigger event has occurred. If any billing trigger event is detected, the system can obtain the user session's traffic usage during the current online call detail record (CDR) period, generate a billing data request based on this usage, and send it to the billing system 200.

[0057] The billing data request is used to report the traffic usage of a user session in the current online call detail record (CDR) period, and it can carry information about the user session's traffic usage in the current online CDR period.

[0058] The current online call detail record (CDR) period is the time interval from the occurrence of the last billing trigger event to the occurrence of the current billing trigger event. The first billing trigger event is the user session establishment event. During a single user session, multiple billing trigger events may occur. The current online CDR period can change according to the occurrence of billing trigger events; it can be the first online CDR period, the second online CDR period, or the third online CDR period.

[0059] As an example, multiple billing trigger events can include: exhaustion of authorized traffic quota, arrival of rate switch time point, and release of user session. Arrival of rate switch time point and release of user session are critical billing trigger events, while exhaustion of authorized traffic quota is a non-critical billing trigger event. The rate switch time point can be 7:00 AM and 11:00 PM daily. If user session 1 is established at 10:00 PM on the first night, exhausts its authorized traffic quota at 10:30 PM on the first night, reaches the rate switch time point at 11:00 PM on the first night, and is released at 11:20 PM on the first night, then if the current billing trigger event is the exhaustion of authorized traffic quota that occurred at 10:30 PM on the first night, then the previous billing trigger event was the user session establishment event that occurred at 10:00 PM on the first night, and the current online call detail record period is the time period from 10:00 PM to 10:30 PM on the first night. If the billing trigger event that occurred this time is the arrival rate switching time point event that occurred at 23:00 on the first night, then the previous billing trigger event was the authorized traffic quota exhaustion event that occurred at 22:30 on the first night, and the current online call detail record period is the time period from 22:30 on the first night to 23:00 on the first night.

[0060] It is worth noting that in this embodiment, each billing trigger event is independent of the others. The last billing trigger event is the most recent billing trigger event in chronological order. It may be a critical billing trigger event, such as the start of a user session or the arrival of a rate switch, or it may be other types of events, such as the exhaustion of authorized traffic quota. The current billing trigger event may be a critical billing trigger event or other types of events. The current online call detail record period is the time interval between any two adjacent billing trigger events, with the occurrence time of the last billing trigger event of any type as the starting point and the occurrence time of the current billing trigger event of any type as the ending point.

[0061] S208, the billing system 200 performs billing processing on the user session according to the billing data request, generates an online call detail record (CDR) for the user session corresponding to the current online CDR period, and sends a response corresponding to the billing data request to the core network system 100. Correspondingly, the core network system 100 receives the response corresponding to the billing data request sent by the billing system.

[0062] In this embodiment, the billing data request can carry the user session's traffic usage information for the current online call detail record (CDR) period. The billing system 200 generates online CDRs using a request-driven mechanism. Upon receiving a billing data request, it can perform online billing processing such as account authentication, rating, and quota reservation control based on the user session's traffic usage information for the current online CDR period carried in the request, generating an online CDR corresponding to the current online CDR period for the user session. The online CDR corresponding to the current online CDR period can record the user session's traffic usage information for that period. Fields recording this information can include: user session identifier, trigger event type, traffic usage, and traffic usage time. The user session identifier field can be the user session's session identifier; the billing trigger event field can be the event type of the current billing trigger event; the traffic usage field can be the user session's traffic usage for the current online CDR period; and the traffic usage time field can be the current online CDR period.

[0063] Online call detail records (CDRs) are used for subsequent CDR auditing. To facilitate subsequent CDR auditing, the billing system 200 can store the online CDRs to the online CDR database after generating them for a user session. The online CDR database is the source database for CDR auditing, storing all online CDRs and serving as the data foundation for subsequent CDR audits. The online CDRs stored in this database are those to be audited. Storing the online CDRs of a user session in the online CDR database allows that CDR to be used as the online CDR to be audited.

[0064] In practical applications, the above processes S206–S208 can be executed repeatedly. The response to the billing data request can carry newly authorized traffic quota information for the user session. After receiving the response to the billing data request, the core network system 100 can generate another billing data request and send it to the billing system 200 again when it detects billing trigger events such as the exhaustion of the newly authorized traffic quota, the arrival of the rate switching time point, or the release of the user session, reporting the traffic usage information of the user session in the current online call detail record (CDR) period. The billing system 200 can then perform online billing processing on the user session again based on the billing data request, generating corresponding online CDRs. Thus, multiple online CDRs are generated for the user session.

[0065] In this embodiment of the application, there are various types of billing trigger events. The billing trigger event that occurs may be a critical billing trigger event or a non-critical billing trigger event. This embodiment of the application also includes the following processing: S210, when the billing trigger event is a critical billing trigger event, generate an offline call detail record (CDR) for the user session corresponding to the current offline CDR period based on the user session's traffic usage in the current offline CDR period.

[0066] The current offline call detail record (CDR) period is the time interval from the occurrence of the last critical billing trigger event to the occurrence of the current billing trigger event. This time interval is the time interval between adjacent critical billing trigger events, with the occurrence time of the last critical billing trigger event as the starting point and the occurrence time of the current critical billing trigger event as the ending point. The first critical billing trigger event is the user session establishment event.

[0067] During a single user session, multiple critical billing trigger events may occur. The current offline call detail record (CDR) period can change according to the occurrence of critical billing trigger events; it can be either the first offline CDR period or the second offline CDR period.

[0068] Continuing with the above example, if the current billing trigger event is the arrival rate switch event at 23:00 on the first night, this event is a critical billing trigger event. The previous critical billing trigger event was the user session establishment event at 22:00 on the first night, and the current offline call detail record (CDR) period is the time period from 22:00 to 23:00 on the first night. If the current billing trigger event is the user session 1 release event at 23:20 on the first night, this event is also a critical billing trigger event. The previous critical billing trigger event was the arrival rate switch event at 23:00 on the first night, and the current offline CDR period is the time period from 23:00 to 23:20 on the first night.

[0069] In this embodiment, the offline call detail record (CDR) corresponding to the current offline CDR period is generated based on the user session's traffic usage during the current CDR period. It can record the user session's traffic usage information during the current offline CDR period, and the recorded fields may include: user session identifier, billing trigger event type, traffic usage, and traffic usage time. The user session identifier field can be the session identifier of the user session; the billing trigger event type field can be the event type of the current billing trigger event; the traffic usage field can be the user session's traffic usage during the current offline CDR period; and the traffic usage time field can be the current offline CDR period.

[0070] Offline call detail records (CDRs) are generated based on critical billing events. Each time a critical billing event occurs, a corresponding offline CDR is generated for the user session, based on the user session's traffic usage during the period between the last critical billing event and the current critical billing event. Since multiple critical billing events can occur during a single user session, multiple offline CDRs can be generated for a single user session.

[0071] Of course, critical billing trigger events are billing trigger events. When a critical billing trigger event occurs, the core network system 100 also generates a billing data request for the user session based on the user session's traffic usage during the current online call detail record (CDR) period, and sends this billing data request to the billing system 200. The billing system 200 can then process the billing for the user session based on this billing data request, generating the corresponding online CDR. Therefore, when a critical billing trigger event occurs, both online and offline CDRs are generated. The time endpoints of the corresponding time periods for both online and offline CDRs are the occurrence time of the critical billing trigger event, allowing for temporal alignment for subsequent CDR auditing.

[0072] Using the above example, when the core network system 100 detects the arrival of the rate switching time at 23:00 on the first night, it can generate an offline call detail record (CDR) for user session 1 based on the traffic usage of user session 1 during the period from 22:00 to 23:00 on the first night. This offline CDR can record the traffic usage information of user session 1 during the period from 22:00 to 23:00 on the first night. Furthermore, the core network system 100 can generate a billing data request for user session 1 based on the period from 22:30 to 23:00 on the first night and send the billing data request to the billing system 200 so that the billing system 200 can generate an online CDR for user session 1 during the period from 22:30 to 23:00 on the first night. This online CDR can record the traffic usage information of user session 1 during the period from 22:30 to 23:00 on the first night.

[0073] When the core network system 100 detects that user session 1 has been released at 23:20 on the first night, it can generate an offline call detail record (CDR) for user session 1 based on the traffic usage of user session 1 during the period from 23:00 to 23:20 on the first night. This offline CDR can be based on the traffic usage of user session 1 during the period from 23:00 to 23:20 on the first night. Furthermore, the core network system 100 can generate a billing data request for user session 1 based on the traffic usage of user session 1 during the period from 23:00 to 23:20 on the first night, and send the billing data request to the billing system 200 so that the billing system 200 can generate an online CDR for user session 1 during the period from 23:00 to 23:00 on the first night. This online CDR can record the traffic usage of user session 1 during the period from 23:00 to 23:00 on the first night.

[0074] In the above embodiments, the arrival of the rate switchover time point and the release of the user session are considered as key billing trigger events for offline and online call detail record (CDR) generation. Upon arrival of the rate switchover time point, an online CDR is generated for the user session based on the traffic usage of the user session in the current online CDR period prior to the rate switchover time point, and an offline CDR is generated for the user session based on the traffic usage of the user session in the current offline CDR period prior to the rate switchover time point. Upon release of the user session, an online CDR is generated for the user session based on the traffic usage of the user session in the current online CDR period after the rate switchover time point and before the user session release, and an offline CDR is generated for the user session based on the traffic usage of the user session in the current offline CDR period after the rate switchover time point and before the user session release. Therefore, the traffic usage of a user session can be segmented in time by the rate switching time point, and the traffic usage before and after the rate switching time point can be split into different offline call records and different online call records. Thus, by using the rate switching time point as a unified traffic entry point for online and offline call records, it is easier to align the offline and online call records of a user session in time during call record auditing, thereby improving the accuracy of auditing.

[0075] Of course, in practical applications, a user session may last for a long time, potentially spanning multiple rate switching points. The core network system 100 can determine the occurrence of a billing trigger event at each rate switching point and when the user session is released. This billing trigger event is a critical billing trigger event. Based on the user session's traffic usage information from the time of the previous critical billing trigger event to the time of this billing trigger event, it generates corresponding offline call detail records (CDRs) for that time period. It also generates a billing trigger event based on the user session's traffic usage information from the previous billing trigger event to the time of this billing trigger event, and sends this billing trigger event to the billing system 200, so that the billing system 200 generates corresponding online CDRs for that time period for the user session.

[0076] Using the example above, if user session 1 is established at 22:00 on the first night, user session 1 exhausts its authorized traffic quota at 22:30 on the first night, reaches the rate switching time at 23:00 on the first night, ..., user session 1 exhausts its newly authorized traffic quota at 6:00 on the second morning, reaches the rate switching time at 7:00 on the second morning, ..., user session 1 exhausts its newly authorized traffic quota at 8:00 on the second morning, and user session 1 releases it at 9:00 on the second morning. The core network system can detect the arrival rate switching time point at 23:00 on the first night, and a critical billing trigger event occurs. Based on the traffic usage of user session 1 from 22:00 to 23:00 on the first night, it generates offline call detail records (CDRs) for user session 1 for that time period. Based on the traffic usage of user session 1 from 22:30 to 23:00 on the first night, it generates a billing data request and sends the billing data request to the billing system 200, so that the billing system 200 generates online CDRs for user session 1 for that time period. The core network system can detect the arrival of the rate switching time at 7:00 AM the following day, triggering a critical billing event. Based on the traffic usage of user session 1 from 11:00 PM the previous night to 7:00 AM the following day, it generates offline call detail records (CDRs) for user session 1 for that period. Based on the traffic usage of user session 1 from 6:00 AM to 7:00 AM the following day, it generates a billing data request and sends it to billing system 200, causing billing system 200 to generate online CDRs for user session 1 for that period. The core network system can detect the release of user session 1 at 9:00 AM the following day, triggering a critical billing event. Based on the traffic usage of user session 1 from 7:00 AM to 9:00 AM the following day, it generates offline CDRs for user session 1 for that period. Based on the traffic usage of user session 1 from 8:00 AM to 9:00 AM the following day, it generates a billing data request and sends it to billing system 200, causing billing system 200 to generate online CDRs for user session 1 for that period. Therefore, by switching the rate, the traffic usage of user session 1 is divided into different offline call detail records (CDRs) and different online CDRs, which makes it easier to align the traffic usage of online and offline CDRs in terms of time during CDR auditing.

[0077] In this embodiment, the online call detail records (CDRs) are used by the CDR auditing system for CDR auditing, and they are the CDRs to be audited. In one implementation, to facilitate subsequent CDR auditing, the billing system 200 can store the online CDRs in an online CDR database after generating them. The online CDR database is the source database for the CDR auditing system 300. Storing the online CDRs in the online CDR database allows them to be used as CDRs to be audited, facilitating subsequent CDR auditing.

[0078] In this embodiment, the offline call detail records (CDRs) generated by the core network system 100 and the online CDRs generated by the billing system 200 are used for CDR auditing. The CDR auditing method further includes the following processing: S212, the call detail record (CDR) auditing system 300 obtains online CDRs from the billing system 200.

[0079] S213, the call detail record (CDR) audit system 300, based on the online CDR cycle corresponding to the online CDR, divides the online CDR into the statistical group of the CDR statistical time period to which the online CDR cycle belongs.

[0080] In one implementation, after generating online call detail records (CDRs), the billing system 200 can store the online CDRs in an online CDR database. Specifically, the CDR auditing system 300 can retrieve online CDRs from the online CDR database and, based on the current online CDR period, classify the online CDRs into statistical groups for the corresponding statistical time periods.

[0081] In this embodiment of the application, the statistical group for the call detail record (CDR) statistical time period is the statistical group corresponding to the CDR statistical time period. Each CDR statistical time period can correspond one-to-one with a statistical group; one CDR statistical time period can correspond to one statistical group. The CDR statistical time period can use the rate switching time period as its time boundary, and its boundary point can be the rate switching time point.

[0082] Using the example above, the call detail record (CDR) statistics period can be from 7:00 AM to 11:00 PM on the first day and from 11:00 PM to 7:00 AM on the second day. If the current online CDR period is from 10:30 PM to 11:00 PM on the first day, it can be grouped into the statistical group for the CDR statistics period from 7:00 AM to 11:00 PM on the first day. If the current online CDR period is from 11:00 PM to 11:20 PM on the first day, it can be grouped into the statistical group for the CDR statistics period from 11:00 PM to 7:00 AM on the second day.

[0083] S214, the call detail record (CDR) auditing system 300 obtains offline CDRs from the core network system 100.

[0084] S215, the call detail record (CDR) audit system 300, based on the offline CDR period corresponding to the offline CDR, divides the offline CDR into the statistical group corresponding to the CDR statistical time period to which the offline CDR period belongs.

[0085] In one implementation, after generating offline call detail records (CDRs), the core network system 100 can store the offline CDRs in an offline CDR database. Specifically, the CDR audit system 300 can retrieve offline CDRs from the offline CDR database and, based on the current offline CDR period, classify the offline CDRs into the statistical groups corresponding to the statistical time periods of the current offline CDR period.

[0086] Using the example above, if the current offline call detail record (CDR) period is from 22:00 to 23:00 on the first day, the CDR can be assigned to the statistical group of the CDR statistical time period from 7:00 to 23:00 on the first day. If the current offline CDR period is from 23:00 to 23:20 on the first day, the CDR can be assigned to the statistical group of the CDR statistical time period from 23:00 on the first day to 7:00 on the second day.

[0087] S216, the call detail record (CDR) auditing system 300 audits online and offline CDRs within the same statistical group.

[0088] In one implementation, the call detail record (CDR) auditing system 300 can statistically analyze the traffic usage of online CDRs for the same user session within the same statistical group to obtain the first total traffic usage of the user session within that statistical group. It can also statistically analyze the traffic usage of offline CDRs for the same user session within the same statistical group to obtain the second total traffic usage of the user session within that statistical group. By comparing whether the first total traffic usage and the second total traffic usage of the user session are consistent, it can determine whether the billing system's billing processing is correct.

[0089] In application, steps S202~S216 above can be repeated. For example... Figure 3As shown, when a user session is established, the core network system 100 can continuously generate billing data requests and send them to the billing system 200 when a billing trigger event is detected. This causes the billing system to continuously generate online billing call detail records (CDRs), such as online billing CDR 1, online billing CDR 2, and online billing CDR 3. Furthermore, the core network system 100 can continuously generate offline CDRs, such as offline CDR 1, offline CDR 2, and offline CDR 3, when the billing trigger event is a critical billing trigger event. The CDR audit system 300 can continuously obtain the offline CDRs generated by the core network system 100, group them, and perform traffic statistics. It can also continuously obtain the online CDRs generated by the billing system 200, group them, and perform traffic statistics. When the user session is released, it performs traffic auditing on the statistical traffic of the online and offline CDRs, compares the two to see if they match, and outputs the traffic audit results.

[0090] In the above embodiments, since online and offline call detail records (CDRs) for a user session are generated before the user session ends, the CDR auditing system 300 can also perform advance audits on the generated online and offline CDRs one by one before the user session ends, and output the audit results, thereby improving the timeliness of the audit results output. For example, the online CDRs for the corresponding time period can be obtained and audited every time an offline CDR is generated or every time a rate switching time point is reached.

[0091] In practical applications, the core network system 100 can have multiple user sessions. For each user session, the core network system 100 can perform the processing described in the embodiments of this application to obtain the offline call detail records (CDRs) for each user session and store them in the offline CDR database. The billing system 200 can perform the processing described in the embodiments of this application to obtain the online CDRs for each user session and store them in the online CDR database. The CDR auditing system 300 can extract CDRs from the offline and online CDR databases according to the CDR auditing dimensions for auditing and output the CDR auditing results. The CDR auditing dimensions can be, for example, province or city, and can be determined according to user needs. The CDR auditing results can be output in the form of reports.

[0092] In some implementations, there may be multiple billing systems 200. The call detail record (CDR) auditing system 300 can execute steps S214-S215 above to obtain offline CDRs from the core network system 100, and can execute steps S212-S214 above to obtain online CDRs from each billing system 200, and perform CDR auditing on the online CDRs generated by each billing system 200 and the offline CDRs generated by the core network system 100. The above processes S212-S213 and S214-S215 can be executed in parallel.

[0093] In practical implementation, the call detail record (CDR) auditing system 300 can implement the above processing based on Redis technology. The CDR auditing system 300 can use Redis for CDR segmentation, traffic statistics, CDR auditing, and other processing, and periodically output audit results from Redis during the CDR audit result output process. After generating offline CDRs, the core network system 100 can store the offline CDRs in an offline CDR database. Each billing system 200 can store the online CDRs in a corresponding online CDR database after generating them. For example... Figure 4 , Figure 5 As shown, each database can correspond to one Dispatcher statistical process. The call detail record (CDR) audit system 300 can read the stored CDRs from each database through the corresponding Dispatcher statistical process. Based on the user's home location in the CDR, the CDRs are written to the corresponding statistical module in the audit Redis cluster. When the statistical time point is reached, the CDRs in the statistical module are grouped, traffic is statistically analyzed, and audited to generate audit results. When the number of audit results reaches the output batch, the audit results are output. When the number of audit results does not reach the output batch, the system continues to read the stored CDRs from the database and write them to the corresponding statistical module. One statistical module can correspond to one home location.

[0094] Based on the same inventive concept as the foregoing embodiments of this application, this application provides a call detail record (CDR) auditing method, which can be used in the aforementioned CDR auditing system. The method may include: The rate switching time point for obtaining billing data from user sessions; After the rate switching time point is reached, the segmented offline call detail records (CDRs) and the segmented online CDRs are obtained; the segmented offline CDRs and the segmented online CDRs are segmented based on the rate switching time point. Perform call detail record (CDR) audits on the segmented offline CDRs and the segmented online CDRs.

[0095] In one implementation, the auditing of the segmented offline call detail records (CDRs) and the segmented online CDRs includes: The offline call detail records (CDRs) of the target users in the current audit period are statistically analyzed to obtain the offline CDR statistics of the target users in the current audit period. The online call detail records (CDRs) of the target users in the current audit period are statistically analyzed to obtain the online CDR statistics of the target users in the current audit period. The offline call detail record (CDR) statistics of the target user are compared with the online CDR statistics of the target user to perform CDR audit on the offline and online CDRs of the target user; The current audit period is the time period from the last rate switch time to the current rate switch time.

[0096] In one implementation, the auditing of the segmented offline call detail records (CDRs) and the segmented online CDRs further includes: The traffic usage of user sessions in the target home area during the current audit period is statistically analyzed to obtain the offline call detail record traffic of the target home area during the current audit period. The traffic usage of user sessions in the target home area during the current audit period is statistically analyzed to obtain the online call detail record (CDR) traffic statistics for the target home area during the current audit period. The offline call detail record (CDR) statistics of the target location are compared with the online CDR statistics of the target location to perform CDR audit on the offline and online CDRs of the target location. The current audit period is the time period from the last rate switch time to the current rate switch time.

[0097] Based on the same inventive concept as the foregoing embodiments of this application, this application provides a call detail record (CDR) auditing method, which can be used in the aforementioned core network system. The method may include: The rate switching time point for obtaining billing data from user sessions; The offline call detail records (CDRs) of a user session are segmented based on the rate switching time point to obtain segmented offline CDRs. The segmented offline CDRs are used for CDR auditing with the segmented online CDRs, which are segmented based on the rate switching time point.

[0098] In one implementation, the step of segmenting offline call detail records (CDRs) of a user session based on the rate switching time point includes: When the rate switching time point is reached, the first offline call detail record (CDR) of the user session is generated based on the traffic usage of the user session in the first offline CDR period.

[0099] The first offline call detail record period is the time period from the last offline call detail record splitting time to the current rate switching time.

[0100] In one embodiment, the method further includes: When the user session is released, a second offline call detail record (CDR) for the user session is generated based on the traffic usage of the user session in the second offline CDR period. The second offline call detail record period is the time from the last offline call detail record splitting time to the user session release time.

[0101] In one implementation, the offline call detail record (CDR) splitting time points include: the user session establishment time point and the rate switching time point.

[0102] Based on the same inventive concept as the foregoing embodiments of this application, this application provides a call detail record (CDR) auditing method, which can be used in the aforementioned billing system. The method may include: The rate switching time point for obtaining billing data from user sessions; The online call detail records (CDRs) of a user session are segmented based on the rate switching time point to obtain segmented online CDRs. The segmented online CDRs are used for CDR auditing with the segmented offline CDRs, which are segmented based on the rate switching time point.

[0103] In one implementation, the step of segmenting the online call detail records (CDRs) of a user session based on the rate switching time point includes: When the rate switching time point is reached, the first online call detail record (CDR) of the user session is generated based on the traffic usage of the user session in the first online CDR period.

[0104] The first online call detail record (CDR) period is the time period from the last online CDR splitting time to the current rate switching time.

[0105] In one embodiment, the method further includes: When the user session is released, a second online call detail record (CDR) for the user session is generated based on the traffic usage of the user session in the second online CDR period. The second online call detail record (CDR) period is the time period from the last online CDR splitting time to the user session release time.

[0106] In one implementation, the online call detail record (CDR) splitting time points include: the user session establishment time point, the authorized traffic quota exhaustion time point, and the rate switching time point.

[0107] Based on the same inventive concept as the foregoing embodiments of this application, this application provides a call detail record (CDR) auditing device, which can be used in the aforementioned CDR auditing system. The device may include: The time point acquisition module is used to obtain the rate switching time point of the billing data for user sessions; The call detail record (CDR) acquisition module is used to acquire the segmented offline CDRs and the segmented online CDRs after the rate switching time point is reached; the segmented offline CDRs and the segmented online CDRs are segmented based on the rate switching time point; The audit module is used to audit the segmented offline call detail records (CDRs) and the segmented online CDRs.

[0108] In one implementation, the audit module is specifically used for: The offline call detail records (CDRs) of the target users in the current audit period are statistically analyzed to obtain the offline CDR statistics of the target users in the current audit period. The online call detail records (CDRs) of the target users in the current audit period are statistically analyzed to obtain the online CDR statistics of the target users in the current audit period. The offline call detail record (CDR) statistics of the target user are compared with the online CDR statistics of the target user to perform CDR audit on the offline and online CDRs of the target user; The current audit period is the time period from the last rate switch time to the current rate switch time.

[0109] In one implementation, the audit module is specifically used for: The traffic usage of user sessions in the target home area during the current audit period is statistically analyzed to obtain the offline call detail record traffic of the target home area during the current audit period. The traffic usage of user sessions in the target home area during the current audit period is statistically analyzed to obtain the online call detail record (CDR) traffic statistics for the target home area during the current audit period. The offline call detail record (CDR) statistics of the target location are compared with the online CDR statistics of the target location to perform CDR audit on the offline and online CDRs of the target location. The current audit period is the time period from the last rate switch time to the current rate switch time.

[0110] Based on the same inventive concept as the foregoing embodiments of this application, this application provides a call detail record (CDR) auditing device, which can be used in the aforementioned core network system. The device may include: The time point acquisition module is used to obtain the rate switching time point of the billing data for user sessions; The segmentation module is used to segment the offline call detail records (CDRs) of a user session based on the rate switching time point to obtain segmented offline CDRs; the segmented offline CDRs are used for CDR auditing with the segmented online CDRs, and the segmented online CDRs are segmented based on the rate switching time point.

[0111] In one embodiment, the segmentation module includes: a first offline call detail record (CDR) generation module, used for: When the rate switching time point is reached, the first offline call detail record (CDR) of the user session is generated based on the traffic usage of the user session in the first offline CDR period.

[0112] The first offline call detail record period is the time period from the last offline call detail record splitting time to the current rate switching time.

[0113] In one embodiment, the device further includes: a second offline call detail record (CDR) generation module, specifically used for: When the user session is released, a second offline call detail record (CDR) for the user session is generated based on the traffic usage of the user session in the second offline CDR period. The second offline call detail record period is the time from the last offline call detail record splitting time to the user session release time.

[0114] In one implementation, the offline call detail record (CDR) splitting time points include: the user session establishment time point and the rate switching time point.

[0115] Based on the same inventive concept as the foregoing embodiments of this application, this application provides a call detail record (CDR) auditing device, which can be used in the aforementioned billing system. The device may include: The time point acquisition module is used to obtain the rate switching time point of the billing data for user sessions; The segmentation module is used to segment the online call detail records (CDRs) of a user session based on the rate switching time point to obtain segmented online CDRs; the segmented online CDRs are used for CDR auditing with the segmented offline CDRs, and the segmented offline CDRs are segmented based on the rate switching time point.

[0116] In one embodiment, the segmentation module includes: a first online call detail record (CDR) generation module, used for: When the rate switching time point is reached, the first online call detail record (CDR) of the user session is generated based on the traffic usage of the user session in the first online CDR period.

[0117] The first online call detail record (CDR) period is the time period from the last online CDR splitting time to the current rate switching time.

[0118] In one embodiment, the apparatus further includes: a second online call detail record (CDR) generation module, used for: When the user session is released, a second online call detail record (CDR) for the user session is generated based on the traffic usage of the user session in the second online CDR period. The second online call detail record (CDR) period is the time period from the last online CDR splitting time to the user session release time.

[0119] In one implementation, the online call detail record (CDR) splitting time points include: the user session establishment time point, the authorized traffic quota exhaustion time point, and the rate switching time point.

[0120] It is understood that the call detail record (CDR) auditing device in this application embodiment can serve as the execution subject of the corresponding CDR auditing method described above, and realize all the functions of the corresponding CDR auditing method. To avoid repetition, it will not be described again here.

[0121] Based on the same inventive concept as the foregoing embodiments of this application, this application also provides an electronic device. The electronic device includes a memory and a processor.

[0122] In some embodiments, the memory may be configured to store various other data to support operation on the electronic device. Examples of such data include instructions for any application or method operating on the electronic device. The memory may be implemented by any type of volatile or non-volatile storage device or a combination thereof, such as static random access memory (SRAM), electrically erasable programmable read-only memory (EEPROM), erasable programmable read-only memory (EPROM), programmable read-only memory (PROM), read-only memory (ROM), magnetic storage, flash memory, magnetic disk, or optical disk. A processor, coupled to the memory, executes the computer program stored in the memory to implement the call detail record (CDR) auditing methods of the embodiments described above. To avoid repetition, further details are omitted here.

[0123] Furthermore, based on the same inventive concept as the foregoing embodiments of this application, this application also provides a computer-readable storage medium storing a computer program, which, when executed by a computer, can implement the call detail record (CDR) auditing methods of the above embodiments. To avoid repetition, further details are omitted here.

[0124] Accordingly, this application also provides a computer program product, which stores instructions that, when executed by a computer, cause the computer to perform the call detail record (CDR) auditing methods described in the above embodiments. To avoid repetition, further details are omitted here.

[0125] The device embodiments described above are merely illustrative. 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 modules can be selected to achieve the purpose of this embodiment according to actual needs. Those skilled in the art can understand and implement this without any creative effort.

[0126] Through the above description of the embodiments, those skilled in the art can clearly understand that each embodiment can be implemented by means of software plus necessary general-purpose hardware platforms, and of course, it can also be implemented by hardware. Based on this understanding, the above technical solutions, in essence or the part that contributes to the prior art, can be embodied in the form of a software product. This computer software product can be stored in a computer-readable storage medium, such as ROM / RAM, magnetic disk, optical disk, etc., and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute the methods described in the various embodiments or some parts of the embodiments.

[0127] 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 of the technical features. Such modifications or substitutions do not cause the essence of the corresponding technical solutions to deviate from the spirit and scope of the technical solutions of the embodiments of this application.

Claims

1. A method for auditing call detail records (CDRs), characterized in that, The method includes: The rate switching time point for obtaining billing data from user sessions; After the rate switching time point is reached, the segmented offline call detail records (CDRs) and the segmented online CDRs are obtained; the segmented offline CDRs and the segmented online CDRs are segmented based on the rate switching time point. Perform call detail record (CDR) audits on the segmented offline CDRs and the segmented online CDRs.

2. The method according to claim 1, characterized in that, The auditing of the segmented offline call detail records (CDRs) and the segmented online CDRs includes: The offline call detail records (CDRs) of the target users in the current audit period are statistically analyzed to obtain the offline CDR statistics of the target users in the current audit period. The online call detail records (CDRs) of the target users in the current audit period are statistically analyzed to obtain the online CDR statistics of the target users in the current audit period. The offline call detail record (CDR) statistics of the target user are compared with the online CDR statistics of the target user to perform CDR audit on the offline and online CDRs of the target user; The current audit period is the time period from the last rate switch time to the current rate switch time.

3. The method according to claim 1, characterized in that, The auditing of the segmented offline call detail records (CDRs) and the segmented online CDRs also includes: The traffic usage of user sessions in the target home area during the current audit period is statistically analyzed to obtain the offline call detail record traffic of the target home area during the current audit period. The traffic usage of user sessions in the target home area during the current audit period is statistically analyzed to obtain the online call detail record (CDR) traffic statistics for the target home area during the current audit period. The offline call detail record (CDR) statistics of the target location are compared with the online CDR statistics of the target location to perform CDR audit on the offline and online CDRs of the target location. The current audit period is the time period from the last rate switch time to the current rate switch time.

4. A method for auditing call detail records, characterized in that, The method includes: The rate switching time point for obtaining billing data from user sessions; The offline call detail records (CDRs) of a user session are segmented based on the rate switching time point to obtain segmented offline CDRs. The segmented offline CDRs are used for CDR auditing with the segmented online CDRs, which are segmented based on the rate switching time point.

5. The method according to claim 4, characterized in that, The step of segmenting offline call detail records (CDRs) of user sessions based on the rate switching time point includes: When the rate switching time point is reached, the first offline call detail record (CDR) of the user session is generated based on the traffic usage of the user session in the first offline CDR period. The first offline call detail record period is the time period from the last offline call detail record splitting time to the current rate switching time.

6. The method according to claim 5, characterized in that, The method further includes: When the user session is released, a second offline call detail record (CDR) for the user session is generated based on the traffic usage of the user session in the second offline CDR period. The second offline call detail record period is the time from the last offline call detail record splitting time to the user session release time.

7. The method according to claim 5 or 6, characterized in that, The offline call detail record (CDR) splitting time points include: the user session establishment time point and the rate switching time point.

8. A method for auditing call detail records, characterized in that, The method includes: The rate switching time point for obtaining billing data from user sessions; The online call detail records (CDRs) of a user session are segmented based on the rate switching time point to obtain segmented online CDRs. The segmented online CDRs are used for CDR auditing with the segmented offline CDRs, which are segmented based on the rate switching time point.

9. The method according to claim 8, characterized in that, The segmentation of online call detail records (CDRs) for user sessions based on the rate switching time point includes: When the rate switching time point is reached, the first online call detail record (CDR) of the user session is generated based on the traffic usage of the user session in the first online CDR period. The first online call detail record (CDR) period is the time period from the last online CDR splitting time to the current rate switching time.

10. The method according to claim 9, characterized in that, The method further includes: When the user session is released, a second online call detail record (CDR) for the user session is generated based on the traffic usage of the user session in the second online CDR period. The second online call detail record (CDR) period is the time period from the last online CDR splitting time to the user session release time.

11. The method according to claim 9 or 10, characterized in that, The online call detail record (CDR) splitting time points include: the user session establishment time point, the authorized traffic quota exhaustion time point, and the rate switching time point.

12. A call detail record (CDR) auditing device, characterized in that, The device includes: The time point acquisition module is used to obtain the rate switching time point of the billing data for user sessions; The call detail record (CDR) acquisition module is used to acquire the segmented offline CDRs and the segmented online CDRs after the rate switching time point is reached; the segmented offline CDRs and the segmented online CDRs are segmented based on the rate switching time point; The audit module is used to audit the segmented offline call detail records (CDRs) and the segmented online CDRs.

13. A call detail record (CDR) auditing device, characterized in that, The device includes: The time point acquisition module is used to obtain the rate switching time point of the billing data for user sessions; The segmentation module is used to segment the offline call detail records (CDRs) of a user session based on the rate switching time point to obtain segmented offline CDRs; the segmented offline CDRs are used for CDR auditing with the segmented online CDRs, and the segmented online CDRs are segmented based on the rate switching time point.

14. A call detail record (CDR) auditing device, characterized in that, The device includes: The time point acquisition module is used to obtain the rate switching time point of the billing data for user sessions; The segmentation module is used to segment the online call detail records (CDRs) of a user session based on the rate switching time point to obtain segmented online CDRs; the segmented online CDRs are used for CDR auditing with the segmented offline CDRs, and the segmented offline CDRs are segmented based on the rate switching time point.

15. An electronic device, characterized in that, include: A memory on which computer programs are stored; A processor for executing the computer program to implement the call detail record (CDR) auditing method according to any one of claims 1-11.

16. A readable storage medium, characterized in that, It stores a computer program that can be executed by a processor to implement the call detail record auditing method according to any one of claims 1-11.

17. A computer program product, characterized in that, Includes a computer program that can be executed by a processor to implement the call detail record (CDR) auditing method according to any one of claims 1-11.

Images