Method, device, equipment, medium and product for charging call detail record

Abstract

The application discloses a method, device, equipment, medium and product for call charging, and the method comprises the following steps: receiving first information sent by a first core network device corresponding to a first user equipment, wherein the first information is response information sent by the first user equipment to the first core network device based on the second user equipment sending a call request; in the case that second information sent by a second core network device corresponding to a second user equipment is not received within a first preset time period, sending indication information to a business operation system, wherein the indication information carries third information, and the third information is used for notifying the business operation system to determine call bills generated by a first charging gateway device corresponding to the first user equipment and call bills generated by a second charging gateway device corresponding to the second user equipment. The embodiment of the application can improve the consistency of the calling and called call bills.

Description

Technical Field

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

[0002] In the telecommunications industry, call detail record (CDR) revenue is a crucial aspect of industry development, and the accuracy of CDR billing is paramount. Currently, when user A initiates a call request from the calling device to user B's called device, if user B has a subscription to a third-party platform, upon the called device responding to the call request, the core network device B corresponding to the called device sends a response message to the third-party platform. Simultaneously, the billing gateway device corresponding to the called device begins billing. If the calling device cancels the call the instant the called device connects, the core network device A corresponding to the calling device sends a call cancellation message to the core network device B. The core network device B then forwards the call cancellation message to the third-party platform. Since the third-party platform receives both the response and cancellation messages simultaneously, a data collision occurs. According to the protocol, the third-party platform sends a call termination message to the core network device B. However, according to the protocol, if the core network device B receives the response message first, it will not process the call termination message, and the billing gateway device corresponding to the called device will continue billing.

[0003] Since the calling device and the called device did not communicate within the preset time period, the base station of the called device sent a call termination message to the core network device B according to the protocol information, and the billing gateway device corresponding to the called device stopped billing.

[0004] In the above situation, the calling device does not generate call detail records (CDRs), but the called device does, resulting in a discrepancy between the CDRs of the calling and called devices. This causes user B to be charged extra for CDRs, leading to a poor user experience and affecting the accuracy of the operator's CDR billing. Summary of the Invention

[0005] This application provides a method, apparatus, device, medium, and product for call detail record (CDR) billing, which can avoid inconsistencies between the caller's and called devices' CDRs and improve CDR consistency.

[0006] In a first aspect, embodiments of this application provide a method for call detail record (CDR) billing, including:

[0007] Receive first information sent by the first core network device corresponding to the first user equipment, wherein the first information is response information sent by the first user equipment to the first core network device when the first user equipment sends a call request based on the second user equipment;

[0008] If no second information is received from the second core network device corresponding to the second user equipment within a first preset time period, an instruction message is sent to the service operation system. This instruction message carries third information, which is used to notify the service operation system to determine the call detail records (CDRs) generated by the first billing gateway device corresponding to the first user equipment and the CDRs generated by the second billing gateway device corresponding to the second user equipment. Secondly, embodiments of this application provide a call detail record (CDR) billing apparatus, comprising:

[0009] The receiving module is used to receive first information sent by the first core network device corresponding to the first user equipment. The first information is response information sent by the first user equipment to the first core network device when the first user equipment sends a call request based on the second user equipment.

[0010] A sending module is configured to send an indication message to the service operation system if no second information is received from the second core network device corresponding to the second user equipment within a first preset time period. The indication message carries third information, which is used to notify the service operation system to determine the call detail records (CDRs) generated by the first billing gateway device corresponding to the first user equipment and the CDRs generated by the second billing gateway device corresponding to the second user equipment. In a third aspect, embodiments of this application provide an electronic device, the device comprising:

[0011] Processor and memory storing computer program instructions;

[0012] The method for call detail record (CDR) billing described in the first aspect above is used by the processor when executing computer program instructions.

[0013] Fourthly, embodiments of this application provide a computer storage medium storing computer program instructions, which, when executed by a processor, implement the call detail record (CDR) billing method described in the first aspect.

[0014] Fifthly, embodiments of this application provide a computer program product, including a computer program that, when processed by a processor, implements the call detail record (CDR) billing method described in the first aspect.

[0015] This application provides a method, apparatus, device, medium, and product for call detail record (CDR) billing. By receiving first information sent by a first core network device (the first information being a response message sent by the first user equipment to the first core network device when the first user equipment sends a call request based on a call request from a second user equipment), and by determining that no second information sent by the second core network device is received within a first preset time period, the above process is explained as follows: when the second user equipment sends a call request to the first user equipment, the second user equipment cancels the call simultaneously with the first user equipment responding to the request.

[0016] Instructions carrying third-party information can be sent to the business operation system to identify the call detail records (CDRs) generated by the first billing gateway device corresponding to the first user equipment and the CDRs generated by the second billing gateway device corresponding to the second user equipment. This enables the business operation system to promptly determine the consistency between the first and second CDRs, thereby improving the consistency between the CDRs of the first and second user equipment. Attached Figure Description

[0017] To more clearly illustrate the technical solutions of the embodiments of this application, the accompanying drawings used in the embodiments of this application will be briefly introduced below. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0018] Figure 1 This is a flowchart illustrating a method for billing call details (CDRs) according to an embodiment of this application.

[0019] Figure 2 This is a flowchart illustrating another method for billing call details provided in one embodiment of this application.

[0020] Figure 3 This is a schematic diagram of a call detail record (CDR) billing system provided in one embodiment of this application.

[0021] Figure 4 This is one of the flowcharts illustrating an exemplary call detail record (CDR) billing method provided in one embodiment of this application.

[0022] Figure 5 This is a second schematic flowchart illustrating an exemplary call detail record (CDR) billing method provided in one embodiment of this application.

[0023] Figure 6 This is a third flowchart illustrating an exemplary call detail record (CDR) billing method provided in one embodiment of this application.

[0024] Figure 7 This is the fourth flowchart illustrating an exemplary call detail record (CDR) billing method provided in one embodiment of this application.

[0025] Figure 8 This is the fifth flowchart illustrating an exemplary call detail record (CDR) billing method provided in one embodiment of this application.

[0026] Figure 9 This is a schematic diagram of a call detail record (CDR) billing device provided in one embodiment of this application.

[0027] Figure 10 This is a schematic diagram of the hardware structure of an electronic device provided in an embodiment of this application. Detailed Implementation

[0028] The features and exemplary embodiments of various aspects of this application will be described in detail below. To make the objectives, technical solutions, and advantages of this application clearer, the application will be further described in detail below with reference to the accompanying drawings and specific embodiments. It should be understood that the specific embodiments described herein are only intended to explain this application and not to limit it. For those skilled in the art, this application can be implemented without some of these specific details. The following description of the embodiments is merely to provide a better understanding of this application by illustrating examples.

[0029] It should be noted that, in this document, relational terms such as "first" and "second" are used merely to distinguish one entity or operation from another, and do not necessarily require or imply any such actual relationship or order between these entities or operations. Furthermore, the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or apparatus. Without further limitations, an element defined by the phrase "comprising..." does not exclude the presence of additional identical elements in the process, method, article, or apparatus that includes the element.

[0030] like Figure 1 As shown, the process for generating VoLTE-based offline call detail records (CDRs) often involves the following steps:

[0031] S110: The calling device sends a call request (e.g., INVITE request information) to the called device.

[0032] S120: The called device generates response information based on the call request and sends the response information to the first core network device corresponding to the called device.

[0033] S130: The first core network device forwards the response information to the first service network device corresponding to the called device and the second core network device corresponding to the calling device.

[0034] S140: After receiving the response information, the first service network device sends a billing request to the first billing gateway device corresponding to the called device, and the first billing gateway device starts billing based on the billing request.

[0035] S150: The second core network device sends a response message to the second service network device.

[0036] S160: The second service network device sends a billing request to the second billing gateway device corresponding to the calling device based on the response information, and the second billing gateway device starts billing.

[0037] Here, during communication between the calling and called devices, the second service network device corresponding to the calling device will send a request to the second billing gateway device to generate a call detail record (CDR) based on the communication termination request sent by either the calling or called device. The first service network device will then send a request to the first billing gateway device to generate a CDR based on the communication termination request sent by either the calling or called device.

[0038] In the above scenario, if the called device has a subscription to a third-party platform, and when the calling device sends a call request to the called device, and the called device answers while the calling device actively hangs up to cancel the call, the following process will occur, specifically, as follows: Figure 2 As shown:

[0039] S200: The calling device sends a call request to the called device.

[0040] S210: The called device sends a response message based on the call request to the first core network device.

[0041] S220: The first core network device sends response information to the first service network device and the third-party platform.

[0042] S230: The first service network device sends a response message to the first billing gateway device, and the first billing gateway device starts billing based on the response message.

[0043] S240: The calling device sends a call cancellation message to the second core network device based on the user's operation.

[0044] S250: The second core network device corresponding to the calling device sends a call cancellation message to the first core network device of the called device.

[0045] S260: The first core network device forwards the call cancellation information to a third-party platform.

[0046] S270: The third-party platform sends call termination information to the first core network device according to the protocol, based on the first received response information and the second received call cancellation information.

[0047] S280: When the first core network device receives the response information first and then the call termination information, it does not process the call termination information, and the first billing gateway device continues to bill.

[0048] S290: Since the calling device and the called device have not communicated within the preset time period, the base station of the called device sends a call termination message to the first core network device according to the protocol information.

[0049] S300: The first core network device sends a call termination message to the first service network device.

[0050] S310: The first service network device sends a cutoff message to the first billing gateway.

[0051] S320: The first billing gateway device stops billing and generates call detail records.

[0052] In the above scenario, the calling device does not generate call detail records (CDRs), while the called device does, resulting in inconsistencies between the CDRs of the calling and called devices and a poor user experience.

[0053] Based on this, embodiments of this application provide a method, apparatus, device, medium, and product for call detail record (CDR) billing, which can solve the above-mentioned problems. The following is a detailed description of a CDR billing method provided by embodiments of this application.

[0054] like Figure 3 As shown in the figure, this application provides a call detail record (CDR) consistency detection system. The CDR consistency detection system is connected to the Serving-Call Session Control Function (SCSCF), Mobile Switching Center (MSC), Interconnection Border Control Function (IBCF), and Business Operation Support System (BOSS). It can perform signaling interaction between the above-mentioned systems to realize the functions of billing detection and CDR synchronization.

[0055] In some examples, the call detail record (CDR) consistency detection system can periodically detect the consistency of CDRs from different billing systems based on the call signaling of the same communication, thereby improving the accuracy of CDRs.

[0056] like Figure 4 As shown in the embodiment of this application, a method for call detail record (CDR) billing is provided, the method including:

[0057] S410: The second user equipment sends a call request to the corresponding second core network equipment based on the user's operation.

[0058] Here, the first user equipment is the called device, and the second user equipment is the calling device. The second user equipment can send a call request to the corresponding second core network device based on user operations.

[0059] S420: The second core network device sends the call request to the first core network device corresponding to the first user equipment.

[0060] S430: The first core network device sends a call request to the first user equipment.

[0061] The second core network device sends the call request to the first core network device corresponding to the first user equipment, which is the called device, so that the first core network device forwards the call request to the first user equipment.

[0062] S440: The first user equipment sends a response message to the first core network equipment based on the user's operation.

[0063] Based on user operations, the first user equipment can send response information to the first core network equipment based on a call request. The response information indicates that the first user equipment agrees to answer the call.

[0064] S450: The call detail record consistency detection system receives the first information sent by the first core network device corresponding to the first user equipment.

[0065] Upon receiving the response information, the first core network device will send the first information to the call detail record consistency detection system.

[0066] like Figure 4 As shown, when the first user equipment and the second user equipment are communicating normally, after step S450, the method further includes:

[0067] S460: The first core network device sends a response message to the second core network device.

[0068] The first core network device will send the response information to the second core network device, and the response information indicates that the first user device agrees to answer the call.

[0069] S470: When the call detail record consistency detection system receives the second information sent by the second core network device within the first preset time period, it sends billing information to the first billing gateway device corresponding to the first user equipment and the second billing gateway device corresponding to the second user equipment, respectively. The billing information instructs the first billing gateway device and the second billing gateway device to start billing. The second information is the response information sent by the first core network device to the second core network device, representing the call request sent by the first user equipment based on the second user equipment.

[0070] When the call detail record consistency detection system receives the first information and starts the timing system, and receives the second information sent by the second core network device within the first preset time period, it can send billing information to the first billing gateway device and the second billing gateway device. The billing information instructs the first billing gateway device and the second billing gateway device to start billing. Here, the second information is the response information sent by the first core network device to the second core network device, representing the first user equipment's call request based on the second user equipment.

[0071] In some examples, the call detail record (CDR) consistency detection system can first send billing information to the first core network device, so that the first core network device can send billing information to the first service network device, and then the first service network device can forward the billing information to the first billing gateway device. Similarly, the CDR consistency detection system can send billing information to the second core network device, so that the second core network device can send billing information to the second service network device, and then the second service network device can forward the billing information to the second billing gateway device.

[0072] The call detail record (CDR) consistency detection system provided in this application embodiment, when a first user equipment (User Equipment) and a second user equipment are in normal communication, determines that if a second message sent by a second core network device is received within a second preset time period, it sends billing information to a first billing gateway device and a second billing gateway device, causing the first and second billing gateway devices to start billing. This system can synchronize the billing time of the first and second user equipment billing gateway devices while the first and second user equipment are communicating normally, thereby improving the CDR consistency between the first and second user equipment.

[0073] In some embodiments, such as Figure 4 As shown, in step S470: after receiving the second information sent by the second core network device within the first preset time period, and after sending billing information to the first billing gateway device corresponding to the first user equipment and the second billing gateway device corresponding to the second user equipment, the method further includes:

[0074] S480: During the communication between the first user equipment and the second user equipment, the first user equipment responds to the user operation and sends the fourth information to the first core network equipment. The fourth information indicates that the first user equipment has ended the communication.

[0075] When the first user equipment and the second user equipment are communicating normally, the first user equipment can respond to user operations and send fourth information to the first core network equipment. The fourth information indicates that the first user equipment has ended communication.

[0076] S490: The call detail record consistency detection system receives the fourth information sent by the first core network device.

[0077] During the communication process between the first user equipment and the second user equipment, there may be a situation where the first user equipment generates a fourth message indicating the end of communication based on user operations and sends it to the first core network equipment. When the first core network equipment receives the fourth message, it will send the fourth message to the call detail record consistency detection system.

[0078] S500: The first core network device sends the fourth information to the second core network device.

[0079] After the first core network device receives the fourth information sent by the first core network device, such as Figure 4 As shown, the first core network device will send the fourth information to the second core network device.

[0080] S510: If the call detail record consistency detection system does not receive the fifth information sent by the second core network device within the second preset time period, it sends a request information to the service operation system. The request information is used to instruct the service operation system to synchronize the billing end time of the first billing gateway device and the second billing gateway device.

[0081] Here, when the call detail record consistency detection system receives the fourth message, it will start a countdown system. If the fifth message sent by the second core network device is not received within the second preset time period, a request message will be sent to the business operation system. The request message is used to instruct the business operation system to synchronize the billing end time of the first billing gateway device and the second billing gateway device.

[0082] Here, the business operation system is the management system for the first and second billing gateway devices. The business operation system can synchronize the billing end time of the first and second billing gateway devices based on request information.

[0083] In some examples, if the first user equipment (User Equipment) and the second user equipment (User Equipment) are communicating normally, when the call detail record (CDR) consistency detection system receives the fourth sub-information sent by the second core network device (the fourth sub-information being a message sent by the second user equipment to the second core network device in response to a user operation during the communication process), a countdown system will be started. If the fifth sub-information is not received from the first core network device within a second preset time period, a request message will be sent to the service operation system. This request message instructs the service operation system to synchronize the billing end time of the first and second billing gateway devices. Further details will not be elaborated here.

[0084] In this embodiment, when the call detail record (CDR) consistency detection system receives the fourth information from the first core network device and does not receive the fifth information from the second core network device within a second preset time period, it sends a request to the service operation system to synchronize the billing end time of the first and second billing gateway devices. This enables the synchronization of the billing end time of the first and second billing gateway devices when the first user equipment and the second user equipment are communicating normally and then end their communication, thereby improving the CDR consistency between the first and second user equipment.

[0085] In some embodiments, such as Figure 5As shown, after the first core network device sends the fourth information to the second core network device in step S500, the method further includes:

[0086] S520: When the call detail record consistency detection system receives the fifth information sent by the second core network device within the second preset time period, it sends generation instructions to the first billing gateway device and the second billing gateway device respectively. The generation instructions are used to instruct the first billing gateway device and the second billing gateway device to generate the third call detail record and the fourth call detail record respectively.

[0087] Here, when the second core network device receives the fourth information, it will send the fifth information to the call detail record consistency detection system. The fifth information is used to indicate that the second user equipment and the first user equipment have ended communication. When the call detail record consistency detection system receives the fifth information sent by the second core network device within the second preset time period, it can send generation instructions to the first billing gateway device and the second billing gateway device respectively. The generation instructions are used to instruct the first billing gateway device and the second billing gateway device to generate the third and fourth call detail records respectively.

[0088] In some examples, the call detail record (CDR) consistency detection system can first send generation instructions to the first core network device and the second core network device respectively, so that the first core network device sends generation instructions to the first service network device, and the second core network device sends generation instructions to the second service network device, so that the first service network device sends generation instructions to the first billing gateway device, and the second service network device sends generation instructions to the second billing gateway.

[0089] The call detail record (CDR) consistency detection system provided in this application sends generation instructions to the first and second billing gateway devices respectively when it receives the fifth information sent by the second core network device within a second preset time period. The generation instructions are used to instruct the first and second billing gateway devices to generate the first and second CDRs respectively. This system can generate CDRs in a timely manner after the first user equipment and the second user equipment end their communication, thereby improving the user experience.

[0090] In some embodiments, such as Figure 6 As shown, when the first user device subscribes to a third-party platform and simultaneously agrees to answer the call, and the second user device cancels the call in response to the user's action, the method further includes the following after step S450:

[0091] S610: The first core network device sends the first information to the third-party platform and the first billing gateway device so that the first billing gateway device can start billing.

[0092] When the first core network device receives the response information, it sends the first information to the call detail record consistency detection system, the third-party platform, and the first billing gateway device, so that the first billing gateway device can start billing.

[0093] S620: When the second user equipment responds to the user's operation to cancel the call, the second user equipment sends a call cancellation message to the second core network equipment.

[0094] As the calling device, the second user equipment responds to user operations while the first user equipment is answering the call. It can generate a call cancellation message and send the call cancellation message to the second core network device.

[0095] S630: The second core network device sends a call cancellation message to the first core network device.

[0096] The second core network device will send the call cancellation information to the first core network device.

[0097] S640: The first core network device will send the call cancellation information to a third-party platform.

[0098] S650: The third-party platform sends call termination information to the first core network equipment.

[0099] Here, if the first core network device receives the response information first and then the call termination information, the call termination information will not be processed according to the protocol.

[0100] S660: If the call detail record consistency detection system does not receive the second information sent by the second core network device corresponding to the second user equipment within the first preset time period, it sends an indication message to the business operation system, and the indication message carries the third information.

[0101] S670: The service operation system determines the call detail records (CDRs) generated by the first billing gateway device corresponding to the first user equipment and the CDRs generated by the second billing gateway device corresponding to the second user equipment based on third information. Here, if the second user equipment cancels the call in response to the user operation while the first user equipment agrees to answer, the second core network device will send a call cancellation message to the CDR consistency detection system. That is to say, the second core network device will not receive the first information sent by the first core network device, nor will it send the second information to the CDR consistency detection system based on the first information. The second information can be the aforementioned response information, and the second core network device will not send the response information to the second billing gateway device. The second billing gateway device will not start billing, and the second user equipment will not generate CDRs.

[0102] like Figure 6As shown, if the call detail record (CDR) consistency detection system does not receive the second information from the second core network device within the first preset time period, it can send an indication message to the service operation system. This indication message carries third information, which is used to notify the service operation system to determine the CDRs generated by the first billing gateway device corresponding to the first user equipment and the CDRs generated by the second billing gateway device corresponding to the second user equipment. Here, the first preset time period can be manually set, for example, to 2 seconds.

[0103] The call detail record (CDR) consistency detection system provided in this application receives first information sent by a first core network device. The first information is the response information sent by the first user equipment (User Equipment) to the first core network device when the User Equipment sends a call request based on the second user equipment. If it is determined that no second information is received from the second core network device within a first preset time period, the system can send an indication information carrying third information to the service operation system. The third information is used to notify the service operation system to determine the CDRs generated by the first billing gateway device corresponding to the first user equipment and the CDRs generated by the second billing gateway device corresponding to the second user equipment, which helps to improve the CDR consistency between the first user equipment and the second user equipment.

[0104] In some examples, after the business operations system determines the call detail records (CDRs) generated by the first billing gateway device corresponding to the first user equipment and the CDRs generated by the second billing gateway device corresponding to the second user equipment, it sends feedback information to the CDR consistency detection system. This feedback information includes two scenarios: first, the first billing gateway device generated a CDR, but the second billing gateway device did not; second, the first billing gateway device generated the first CDR, and the second billing gateway device generated the second CDR. The CDR consistency detection system will execute different steps based on these different feedback scenarios.

[0105] In some embodiments, such as Figure 6 As shown, after step S670 above, the method further includes:

[0106] S680: When the first billing gateway device generates a call detail record (CDR) but the second billing gateway device corresponding to the second user equipment does not generate a CDR, a deletion command is sent to the service operation system. The deletion command instructs the service operation system to delete the CDR generated by the first billing gateway device. When the first billing gateway device generates a CDR (i.e., the called device generates a CDR), and the second user equipment's corresponding second billing gateway device does not generate a CDR based on the same identifier information, the deletion command can be included in the third information. This allows the service operation system to promptly delete the CDR generated by the first billing gateway device based on the deletion command, improving the consistency of CDRs generated by the first and second user equipment. This solves the technical problem in the prior art where the first user equipment generates a response information based on a call request while the second user equipment cancels the call, resulting in a poor user experience due to the first billing gateway device generating a CDR while the second billing gateway device does not.

[0107] In some embodiments, such as Figure 7 As shown, after step S670 above, the method further includes:

[0108] S690: When the first billing gateway device generates the first call detail record (CDR) and the second billing gateway device generates the second CDR, a request message is sent to the business operation system. The request message is used to instruct the business operation system to synchronize the billing start time of the first CDR and the second CDR.

[0109] When the first billing gateway generates the first call detail record (CDR) and the second billing gateway generates the second CDR, the second user equipment may cause a discrepancy in the billing start time of the first CDR and the second CDR because the second user equipment fails to send the second information to the CDR consistency detection system within the first preset time period. In this case, a request message can be sent to the business operation system to instruct the business operation system to synchronize the billing start time of the first CDR and the second CDR.

[0110] This application embodiment, when a first billing gateway generates a first call detail record (CDR) and a second billing gateway generates a second CDR, sends a request message to the service operation system. This request message instructs the service operation system to synchronize the billing start times of the first and second CDRs, thereby improving CDR consistency. In some embodiments, such as... Figure 8 As shown, when the first user equipment receives a call request from the second device and transfers the call request to the third user equipment, after step S420—where the second core network device sends the call request to the first core network device corresponding to the first user equipment—the method further includes:

[0111] S810: The first core network device sends a call request to the third core network device.

[0112] The first core network device will send the call request to the third core network device to achieve call forwarding.

[0113] S820: The third core network device sends a call request to the third user equipment.

[0114] like Figure 7 As shown, when the second user device cancels the call while the third user device has signed up with a third-party platform and agrees to answer, the methods include:

[0115] S830: The third user equipment responds to the user's operation by sending a response message to the third core network equipment. The response message indicates that the third user equipment agrees to answer the call.

[0116] S840: The third core network device sends the first sub-information to the third-party platform, sends the first sub-information to the call detail record consistency detection system, and simultaneously sends the first sub-information to the third billing gateway device.

[0117] When the third core network device receives the response information, it sends the third sub-information to the third-party platform, the call detail record consistency detection system, and the third billing gateway device, so that the third billing gateway device can start billing based on the first sub-information.

[0118] S850: The second user equipment responds to the user's operation and sends a call cancellation message to the second core network equipment.

[0119] The second user equipment can respond to user actions and send a call cancellation message to the second core network equipment.

[0120] S860: The second core network device sends a call cancellation message to the first core network device.

[0121] S870: The first core network device sends a call cancellation message to the third core network device.

[0122] S880: The third core network device sends a call cancellation message to a third-party platform.

[0123] S890: The third-party platform sends call termination information to the third core network equipment according to the protocol.

[0124] S900: If the call detail record consistency detection system does not receive the second information sent by the second core network device corresponding to the second user equipment within the first preset time period, it sends an indication information to the service operation system. The indication information carries third information, which is used to notify the service operation system to determine the call detail records generated by the second billing gateway device corresponding to the second user equipment and the call detail records generated by the third billing gateway device corresponding to the third user equipment.

[0125] Here, if the third billing gateway device generates a call detail record (CDR) while the second billing gateway device does not, a deletion command can be sent to the business operation system, causing the business operation system to delete the CDR generated by the third billing gateway.

[0126] When the second billing gateway device generates the first call detail record (CDR) and the third billing gateway device generates the second CDR, a request message is sent to the business operation system. The request message is used to instruct the business operation system to synchronize the billing start time of the first and second CDRs.

[0127] The call detail record (CDR) consistency detection system provided in this application, when a first user equipment receives a call request from a second user equipment, transfers the call request to a third user equipment. If the third user equipment has signed up with a third-party platform and agrees to answer the call, and the second user equipment cancels the call, the system sends an instruction message to the business operation system. The instruction message carries third information, which is used to notify the business operation system to determine the CDRs generated by the second billing gateway device corresponding to the second user equipment and the CDRs generated by the third billing gateway device corresponding to the third user equipment, thereby improving the CDR consistency between the second user equipment and the third user equipment.

[0128] In some embodiments, the first core network device includes a service call session control function device or an interconnection boundary control function device.

[0129] Here, the first core network device can be either a Serving-Call Session Control Function (S-CSCF) device or an Interconnection Border Control Function (IBCF) device.

[0130] This application embodiment improves the consistency of call detail records (CDRs) in various communication scenarios by setting the first core network equipment to include a service call session control function device or an interconnection boundary control function device.

[0131] In some embodiments, the deletion instruction includes identification information, which corresponds to call detail records (CDRs).

[0132] If the first billing gateway device generates a call detail record (CDR), but the second billing gateway device corresponding to the second user equipment does not generate a CDR, the CDR consistency detection system sends a deletion command to the service operation system, including:

[0133] When the first billing gateway device generates a call detail record (CDR) but the second billing gateway device corresponding to the second user equipment does not generate a CDR, the CDR consistency detection system sends identification information to the business operation system. The identification information is used to instruct the business operation system to delete the CDR corresponding to the identification information based on the identification information.

[0134] Based on the same communication, the first, second, third, fourth, and fifth messages carry identification information. The aforementioned call detail record (CDR) consistency detection system can determine the time difference between different messages received in the same communication based on this identification information. Simultaneously, the CDR consistency detection system can send a deletion command to the service operation system. This deletion command includes the identification information, and the service operation system can delete the CDR uniquely corresponding to that identification information.

[0135] In some instances, when the call detail record (CDR) consistency detection system sends a request to the business operations system, the request includes identification information, enabling the business operations system to synchronize the billing end time of the first billing gateway device and the second billing gateway device based on the identification information.

[0136] This application embodiment includes identification information in the deletion instruction. The identification information indicates unique communication. When the first billing gateway device generates a call detail record (CDR) but the second billing gateway device corresponding to the second user equipment does not generate a CDR, the CDR consistency detection system can send a deletion instruction carrying the identification information to the service operation system. This allows the service operation system to delete the CDR that uniquely corresponds to the identification information based on the identification information, thereby improving the consistency of the calling and called CDRs.

[0137] In some embodiments, such as Figure 9 As shown in the figure, this application provides a call detail record (CDR) billing apparatus, comprising:

[0138] The receiving module 901 is used to receive first information sent by the first core network device corresponding to the first user equipment. The first information is response information sent by the first user equipment to the first core network device when the first user equipment sends a call request based on the second user equipment.

[0139] The sending module 902 is used to send an indication message to the service operation system if it does not receive the second information sent by the second core network device corresponding to the second user equipment within a first preset time period. The indication message carries third information, which is used to notify the service operation system to determine the call detail records (CDRs) generated by the first billing gateway device corresponding to the first user equipment and the CDRs generated by the second billing gateway device corresponding to the second user equipment.

[0140] In some embodiments, the sending module can specifically be used for:

[0141] If the first billing gateway device generates a call detail record (CDR) but the second billing gateway device does not, a deletion command is sent to the business operations system. The deletion command instructs the business operations system to delete the CDR generated by the first billing gateway device.

[0142] In some embodiments, the sending module can specifically be used for:

[0143] When the first billing gateway device generates the first call detail record (CDR) and the second billing gateway device generates the second CDR, a request message is sent to the business operation system. The request message is used to instruct the business operation system to synchronize the billing start time of the first and second CDRs.

[0144] In some embodiments, the sending module can also be used for:

[0145] If the second information is received from the second core network device within the first preset time period, billing information is sent to the first billing gateway device corresponding to the first user equipment and the second billing gateway device corresponding to the second user equipment, respectively. The billing information instructs the first billing gateway device and the second billing gateway device to start billing. The second information is a response information sent by the first core network device to the second core network device, representing the call request sent by the first user equipment based on the second user equipment.

[0146] In some embodiments,

[0147] The receiving module can also be used to receive fourth information sent by the first core network device. The fourth information is information sent by the first user equipment to the first core network device in response to user operation during the communication process between the first user equipment and the second user equipment, indicating the end of communication.

[0148] The sending module can also be used to send a request message to the business operation system if it does not receive the fifth message sent by the second core network device within the second preset time period. The request message is used to instruct the business operation system to synchronize the billing end time of the first billing gateway device and the second billing gateway device.

[0149] In some embodiments, the apparatus further includes a generation module for:

[0150] Upon receiving the fifth message from the second core network device within the second preset time period, generation instructions are sent to the first and second billing gateway devices respectively. The generation instructions are used to instruct the first and second billing gateway devices to generate the third and fourth call detail records (CDRs) respectively.

[0151] In some embodiments, the first information includes first sub-information sent by the third core network device corresponding to the third user equipment to the first core network device. The first sub-information is response information sent by the third user equipment to the third core network device when the third user equipment sends a call request based on the second user equipment.

[0152] In some embodiments, the first core network device includes a service call session control function device or an interconnection boundary control function device.

[0153] In some embodiments, the deletion instruction includes identification information, which corresponds to call detail records (CDRs).

[0154] When the first billing gateway device generates a call detail record (CDR), it sends a deletion command to the service operation system. The deletion command instructs the service operation system to delete the CDR, including:

[0155] When the first billing gateway device generates a call detail record (CDR), it sends identification information to the business operation system. The identification information is used to instruct the business operation system to delete the CDR corresponding to the identification information.

[0156] The apparatus described above is used to implement the corresponding call detail record (CDR) billing method in any of the foregoing embodiments, and has the beneficial effects of the corresponding method embodiments, which will not be repeated here.

[0157] Figure 10 A schematic diagram of the hardware structure of an electronic device is provided in the application embodiment.

[0158] The electronic device 1000 may include a processor 1001 and a memory 1002 storing computer program instructions.

[0159] Specifically, the processor 1001 may include a central processing unit (CPU), an application-specific integrated circuit (ASIC), or one or more integrated circuits that can be configured to implement the embodiments of this application.

[0160] Memory 1002 may include mass storage for data or instructions. For example, and not limitingly, memory 1002 may include a hard disk drive (HDD), floppy disk drive, flash memory, optical disk, magneto-optical disk, magnetic tape, or Universal Serial Bus (USB) drive, or a combination of two or more of these. Where appropriate, memory 1002 may include removable or non-removable (or fixed) media. Where appropriate, memory 1002 may be internal or external to the integrated gateway disaster recovery device. In a particular embodiment, memory 1002 is non-volatile solid-state memory.

[0161] In a particular embodiment, memory 1002 includes read-only memory (ROM). Where appropriate, the ROM may be a mask-programmed ROM, a programmable ROM (PROM), an erasable PROM (EPROM), an electrically erasable PROM (EEPROM), an electrically rewritable ROM (EAROM), or flash memory, or a combination of two or more of these.

[0162] Memory may include read-only memory (ROM), random access memory (RAM), disk storage media devices, optical storage media devices, flash memory devices, and electrical, optical, or other physical / tangible memory storage devices. Therefore, typically, memory includes one or more tangible (non-transitory) computer-readable storage media (e.g., memory devices) encoded with software including computer-executable instructions, and when the software is executed (e.g., by one or more processors), it is operable to perform the operations described with reference to the method according to the first aspect of this application.

[0163] The processor 1001 reads and executes computer program instructions stored in the memory 1002 to implement any of the call detail record (CDR) billing methods described in the above embodiments.

[0164] In one example, the electronic device may also include a communication interface 1003 and a bus 1004. Wherein, for example... Figure 10 The processor 1001, memory 1002, and communication interface 1003 are connected through bus 1004 and complete communication with each other.

[0165] The communication interface 1003 is mainly used to realize communication between various modules, devices, units and / or equipment in the embodiments of this application.

[0166] Bus 1004 includes hardware, software, or both, that couples components of an online data traffic metering device together. For example, and not limitingly, the bus may include an Accelerated Graphics Port (AGP) or other graphics bus, an Enhanced Industry Standard Architecture (EISA) bus, a Front Side Bus (FSB), HyperTransport (HT) interconnect, an Industry Standard Architecture (ISA) bus, an Infinite Bandwidth Interconnect, a Low Pin Count (LPC) bus, a memory bus, a Microchannel Architecture (MCA) bus, a Peripheral Component Interconnect (PCI) bus, a PCI-Express (PCI-X) bus, a Serial Advanced Technology Attachment (SATA) bus, a Video Electronics Standards Association Local (VLB) bus, or other suitable buses, or combinations of two or more of these. Where appropriate, bus 1004 may include one or more buses. Although specific buses are described and illustrated in embodiments of this application, any suitable bus or interconnect is contemplated herein.

[0167] The electronic devices described above are used to implement the corresponding call detail record (CDR) billing methods in any of the foregoing embodiments, and have the beneficial effects of the corresponding method embodiments, which will not be repeated here.

[0168] Furthermore, in conjunction with the call detail record (CDR) billing methods described in the above embodiments, this application embodiment can provide a computer storage medium for implementation. This computer storage medium stores computer program instructions; when these computer program instructions are executed by a processor, they implement any of the CDR billing methods described in the above embodiments.

[0169] Furthermore, in conjunction with the call detail record (CDR) billing methods described in the above embodiments, this application can provide a computer program product for implementation. When the instructions of this computer program product are executed by the processor of an electronic device, they implement any of the CDR billing methods described in the above embodiments.

[0170] Those skilled in the art should understand that the discussion of any of the above embodiments is merely exemplary and is not intended to imply that the scope of this application (including the claims) is limited to these examples; within the framework of this application, the technical features of the above embodiments or different embodiments can also be combined, the steps can be implemented in any order, and there are many other variations of different aspects of the embodiments of this application as described above, which are not provided in the details for the sake of brevity.

[0171] The functional blocks shown in the above-described structural diagram can be implemented as hardware, software, firmware, or a combination thereof. When implemented in hardware, they can be, for example, electronic circuits, application-specific integrated circuits (ASICs), appropriate firmware, plug-ins, function cards, etc. When implemented in software, the elements of this application are programs or code segments used to perform the required tasks. Programs or code segments can be stored on a machine-readable medium or transmitted over a transmission medium or communication link via data signals carried on a carrier wave. "Machine-readable medium" can include any medium capable of storing or transmitting information. Examples of machine-readable media include electronic circuits, semiconductor memory devices, ROM, flash memory, erasable ROM (EROM), floppy disks, CD-ROMs, optical disks, hard disks, fiber optic media, radio frequency (RF) links, etc. Code segments can be downloaded via computer networks such as the Internet, intranets, etc.

[0172] It should also be noted that the exemplary embodiments mentioned in this application describe methods or apparatuses based on a series of steps or devices. However, this application is not limited to the order of the above steps; that is, the steps can be performed in the order mentioned in the embodiments, or in a different order, or several steps can be performed simultaneously.

[0173] The aspects of this application have been described above with reference to flowchart illustrations and / or block diagrams of methods, apparatus (devices), and computer program products according to embodiments of this application. It should be understood that each block in the flowchart illustrations and / or block diagrams, and combinations of blocks in the flowchart illustrations and / or block diagrams, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, or other programmable data processing apparatus to produce a machine such that these instructions, executable via the processor of the computer or other programmable data processing apparatus, enable the implementation of the functions / actions specified in one or more blocks of the flowchart illustrations and / or block diagrams. Such a processor can be, but is not limited to, a general-purpose processor, a special-purpose processor, a special application processor, or a field-programmable logic circuit. It is also understood that each block in the block diagrams and / or flowcharts, and combinations of blocks in the block diagrams and / or flowcharts, can also be implemented by dedicated hardware performing the specified functions or actions, or can be implemented by a combination of dedicated hardware and computer instructions.

[0174] The above description is merely a specific embodiment of this application. Those skilled in the art will clearly understand that, for the sake of convenience and brevity, the specific working processes of the devices, modules, and units described above can be referred to the corresponding processes in the foregoing method embodiments, and will not be repeated here. It should be understood that the protection scope of this application is not limited thereto. Any person skilled in the art can easily conceive of various equivalent modifications or substitutions within the technical scope disclosed in this application, and these modifications or substitutions should all be covered within the protection scope of this application.

Claims

1. A method of call billing, characterized by, Comprising receiving first information sent by a first core network device corresponding to a first user equipment, the first information being response information sent by the first user equipment to the first core network device based on a situation that a second user equipment sends a call request; in a case that second information sent by a second core network device corresponding to the second user equipment is not received within a first preset time period, sending indication information to a business operation system, the indication information carrying third information used for notifying the business operation system to determine a bill generated by a first charging gateway device corresponding to the first user equipment and a bill generated by a second charging gateway device corresponding to the second user equipment; after the case that the second information sent by the second core network device corresponding to the second user equipment is not received within the first preset time period, the method further comprises: in a case that the bill generated by the first charging gateway device and the bill generated by the second charging gateway device are not generated, sending a deletion instruction to the business operation system, the deletion instruction being used for instructing the business operation system to delete the bill generated by the first charging gateway device.

2. The method of call accounting according to claim 1, wherein, after the case that the second information sent by the second core network device corresponding to the second user equipment is not received within the first preset time period, the method further comprises: in a case that the first bill generated by the first charging gateway device and the second bill generated by the second charging gateway device are generated, sending request information to the business operation system, the request information being used for instructing the business operation system to synchronize a charging start time of the first bill and the second bill.

3. The method of call accounting according to claim 1, wherein, after the first information sent by the first core network device is received, the method further comprises: in a case that second information sent by the second core network device is received within a first preset time period, sending charging information to a first charging gateway device corresponding to the first user equipment and a second charging gateway device corresponding to the second user equipment respectively, the charging information being used for instructing the first charging gateway device and the second charging gateway device to start charging, the second information being response information sent by the first core network device to the second core network device and representing that the first user equipment is based on a call request sent by the second user equipment.

4. The method of call accounting according to claim 3, wherein, after the case that the second information sent by the second core network device is received within the first preset time period, the method further comprises: receiving fourth information sent by a first core network device, the fourth information being information sent by a first user equipment to the first core network device and representing ending communication in a process that the first user equipment communicates with a second user equipment and responds to a user operation; In a case where the fifth information sent by the second core network device is not received within a second preset time period, sending request information to the service operation system, the request information being used for instructing the service operation system to synchronize the charging end time of the first charging gateway device and the second charging gateway device.

5. The method of call accounting according to claim 4, wherein, After receiving the fourth information sent by the first core network device, the method further comprises: In a case where the fifth information sent by the second core network device is received within a second preset time period, sending generation instructions to the first charging gateway device and the second charging gateway device respectively, the generation instructions being used for instructing the first charging gateway device and the second charging gateway device to generate third call records and fourth call records respectively.

6. The method of call accounting according to claim 1, wherein, The first information comprises first sub-information sent by a third core network device corresponding to a third user equipment to the first core network device, the first sub-information being response information sent by the third user equipment to the third core network device based on a case where a second user equipment sends a call request.

7. The method of call accounting according to claim 1, wherein, The first core network device comprises a serving call session control function device or an interconnection border control function device.

8. The method of call accounting according to claim 1, wherein, The deletion instruction comprises identification information, the identification information having a corresponding relationship with a call record, In a case where the first charging gateway device generates a call record and a second charging gateway device corresponding to a second user equipment does not generate a call record, sending a deletion instruction to a service operation system, the deletion instruction being used for instructing the service operation system to delete the call record generated by the first charging gateway device, comprising: In a case where the first charging gateway device generates a call record and a second charging gateway device corresponding to a second user equipment does not generate a call record, sending the identification information to a service operation system, the identification information being used for instructing the service operation system to delete the call record corresponding to the identification information based on the identification information.

9. A device for charging of a call slip, characterized in that comprising The receiving module is configured to receive first information sent by a first core network device corresponding to a first user equipment, the first information being response information sent by the first user equipment to the first core network device based on a case where a second user equipment sends a call request; The sending module is configured to, in a case where second information sent by a second core network device corresponding to the second user equipment is not received within a first preset time period, send indication information to a service operation system, the indication information carrying third information, the third information being used for notifying the service operation system to determine a call record generated by a first charging gateway device corresponding to the first user equipment and a call record generated by a second charging gateway device corresponding to the second user equipment. After the indication information is sent to the service operation system in the case where the second information sent by the second core network device corresponding to the second user equipment is not received within the first preset time period, the method further comprises: In a case where the first charging gateway device generates a call record and the second charging gateway device does not generate a call record, sending a deletion instruction to the service operation system, the deletion instruction being used for instructing the service operation system to delete the call record generated by the first charging gateway device.

10. An electronic device, comprising: The device comprises a processor and a memory storing computer program instructions; The processor reads and executes the computer program instructions to implement the method for charging a message as claimed in any one of claims 1 to 8.

11. A readable storage medium, characterized by, The computer program instructions are stored on the readable storage medium and are executed by the processor to implement the method for charging a message as claimed in any one of claims 1 to 8.

12. A computer program product comprising a computer program, characterized in that, The computer program is processed by the processor to implement the method for charging a message as claimed in any one of claims 1 to 8.

Images