Communication method and communication device
By generating detailed online and offline call records and using key records stored in memory for billing rollback, the problem of inaccurate billing caused by anomalies in the core network and online billing system was solved, thus achieving accuracy and precision in billing.
Patent Information
- Application Number
- CN202411163087.4
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2024-08-22
- Publication Date
- 2026-03-03
AI Technical Summary
In existing technologies, inaccurate billing can occur when the core network and online billing system malfunction, such as duplicate billing or under-billing.
By generating online and offline call detail records, the billing from the first moment to the second moment is rolled back based on the online call detail records, and the call from the first moment to the third moment is re-billed based on the offline call detail records. The key records stored in memory are used to improve query efficiency and billing accuracy.
It eliminates billing errors, ensures billing accuracy, and avoids issues such as duplicate or under-billing.
Smart Images
Figure CN121603899A_ABST
Abstract
Description
Technical Field
[0001] This application relates to the field of communications, and more particularly to a communication method and a communication device. Background Technology
[0002] When anomalies occur in the core network and online billing system, such as network anomalies, currently online billing sessions will be interrupted, but user call services must not be interrupted. Offline billing is required to complete call service billing.
[0003] The current offline billing method is as follows: If an anomaly occurs in the core network and / or billing system during online billing, the core network writes offline call detail records (CDRs) after it is restored. After the anomaly in the core network and billing system is resolved, the core network transmits the offline CDRs to the billing system, and the billing system performs billing based on the offline CDRs. The start time is not the actual time during which the billing system has not billed.
[0004] However, this billing method can lead to inaccurate billing, such as double billing or under-billing. Summary of the Invention
[0005] This application provides a communication method and communication device that can eliminate billing errors caused by switching from online billing to offline billing in the core network.
[0006] In a first aspect, this application provides a communication method, which includes: generating an online call detail record, wherein the online call detail record records the billing information of a first call from a first moment to a second moment; receiving an offline call detail record, wherein the offline call detail record records the call information of the first call from a first moment to a third moment; rolling back the billing from the first moment to the second moment based on the online call detail record; and billing the call between the first moment and the third moment based on the offline call detail record.
[0007] This communication method can be executed by an online charging system (OCS), or in other words, by a real-time billing system that participates in control during the communication process and provides real-time credit control, prepaid data service usage, and value-added service functions for users.
[0008] In this communication method, the online billing is accurately rolled back for the portion from the first moment to the second moment based on the online call details, and the session from the first moment to the third moment is re-charged according to the offline call details, thereby eliminating billing errors such as under-billing time before the second moment or over-billing time after the second moment.
[0009] It is understandable that the third moment occurs after the second moment.
[0010] In some designs, offline call details are received from the mobile switching center (MSC).
[0011] In some designs, this communication method also includes: storing key records in memory, the key records recording the association between online call details and the first call; and determining to roll back the billing of online call details based on the key records.
[0012] In this communication method, because key records are stored in memory and the billing rollback of online call details can be determined based on these key records, the query time for key records can be reduced and the query efficiency of key records can be improved compared to storing key records in a physical database.
[0013] It is understandable that the memory in this communication method can also be understood as a cache.
[0014] In some possible designs, online call details include an online call detail record identifier, offline call details include an identifier for the first call, and key records include both the online call detail record identifier and the first call identifier. This allows online and offline call details to be correlated through these identifiers, enabling precise rollback of online call details and re-billing based on offline call details.
[0015] In some possible designs, the user number of the initiator of the first call is recorded in the offline call details, key records, and online call details. This allows the online billing system to retrieve the offline call details, key records, and online call details based on the initiator's user number, thus enabling accurate billing.
[0016] Secondly, this application provides a communication method, which includes: generating an offline call detail record, wherein the offline call detail record records the call information of a first call from a first moment to a third moment, and the first moment is the start moment of the first call; and sending the offline call detail record.
[0017] This communication method can be executed by a mobile switching center, or in other words, by a core component in a mobile communication network that is responsible for processing and controlling communication between mobile devices and between mobile devices and fixed networks.
[0018] Thirdly, this application provides a communication device. This communication device may include modules corresponding to the methods / operations / steps / actions described in the first aspect or any possible implementation of the first aspect. These modules may be hardware circuits, software, or a combination of hardware circuits and software.
[0019] In one design, the communication device may include a processing module and a communication module. The communication module is used to perform the sending and receiving actions in the method described in the first aspect or any possible implementation thereof, while the processing module is used to perform the processing actions involved in the method described in the first aspect or any possible implementation thereof.
[0020] In one design, the communication device may be a real-time billing function system that participates in control and provides real-time credit control, prepaid data service and value-added service for users during the communication process, or it may be a device, module, circuit or chip configured in the real-time billing function system, or a device that can be matched and used with the real-time billing function system.
[0021] Fourthly, this application provides a communication device. This communication device may include modules corresponding to the methods / operations / steps / actions described in the second aspect or any possible implementation thereof.
[0022] In one design, the communication device may include a processing module and a communication module. The communication module is used to perform the sending and receiving actions in the method described in the second aspect or any possible implementation thereof, while the processing module is used to perform the processing actions involved in the method described in the second aspect or any possible implementation thereof.
[0023] In one design, the communication device may be a core component in a mobile communication network responsible for processing and controlling communication between mobile devices and between mobile devices and fixed networks, or it may be a device, module, circuit or chip configured in the core component, or a device that can be used in conjunction with the core component.
[0024] Fifthly, a communication device is provided, including a processor, wherein instructions, when executed by the processor, cause the method as described in the first aspect or any possible implementation thereof to be implemented.
[0025] Optionally, the communication device may further include a storage medium that stores the instructions executed by the processor.
[0026] A sixth aspect provides a communication device including a processor, wherein instructions, when executed by the processor, cause the method as described in the second aspect or any possible implementation thereof to be implemented.
[0027] Optionally, the communication device may further include a storage medium that stores the instructions executed by the processor.
[0028] In a seventh aspect, a chip is provided, including processing circuitry for running a program or instructions to implement a method as described in the first aspect or any possible implementation thereof.
[0029] Optionally, the chip may also include a memory for storing programs or instructions.
[0030] Optionally, the chip may also include transceiver circuitry, or input / output interfaces.
[0031] Eighthly, a chip is provided, including processing circuitry for running a program or instructions to implement the methods described in the second aspect or any possible implementation thereof.
[0032] Optionally, the chip may also include a memory for storing programs or instructions.
[0033] Optionally, the chip may also include transceiver circuitry, or input / output interfaces.
[0034] A ninth aspect provides a computer-readable storage medium including instructions that, when executed by a processor, cause a method as described in the first aspect or any possible implementation thereof to be implemented.
[0035] In a tenth aspect, a computer-readable storage medium is provided, the computer-readable storage medium including instructions that, when executed by a processor, cause the method as described in the second aspect or any possible implementation thereof to be implemented.
[0036] Eleventhly, a computer program product is provided, comprising computer program code or instructions, which, when executed, cause the method as described in the first aspect or any possible implementation thereof to be implemented.
[0037] In a twelfth aspect, a computer program product is provided, comprising computer program code or instructions that, when executed, cause the methods described in the second aspect or any possible implementation thereof to be implemented.
[0038] In a thirteenth aspect, a communication system is provided, comprising: means for performing the first aspect or any possible implementation thereof, and means for performing the second aspect or any possible implementation thereof.
[0039] It is understood that the technical effects of any of the second to thirteenth aspects of this application can be referred to the relevant content in the first aspect, and will not be repeated here. Attached Figure Description
[0040] Figure 1 This is an exemplary structural diagram of a billing process according to one embodiment of this application;
[0041] Figure 2 This is an exemplary structural diagram of a billing process according to another embodiment of this application;
[0042] Figure 3 and Figure 4 This is a flowchart illustrating the communication methods of several embodiments of this application;
[0043] Figure 5 This is a schematic diagram of key fields of a communication method according to an embodiment of this application;
[0044] Figure 6 This is a flowchart illustrating a communication method according to an embodiment of this application;
[0045] Figure 7 This is a schematic diagram of the structure of a communication device according to an embodiment of this application;
[0046] Figure 8 This is a schematic diagram of the structure of a communication device according to an embodiment of this application. Detailed Implementation
[0047] The technical solutions in the embodiments of this application will now be described with reference to the accompanying drawings.
[0048] To facilitate a clear description of the technical solutions in the embodiments of this application, the terms "first" and "second" are used in the embodiments of this application to distinguish identical or similar items with essentially the same function and effect. Those skilled in the art will understand that the terms "first" and "second" do not limit the quantity or execution order, and that "first" and "second" are not necessarily different.
[0049] It should be noted that, in the embodiments of this application, the terms "exemplary" or "for example" are used to indicate examples, illustrations, or descriptions. Any embodiment or design scheme described as "exemplary" or "for example" in this application should not be construed as being more preferred or advantageous than other embodiments or design schemes. Specifically, the use of terms such as "exemplary" or "for example" is intended to present the relevant concepts in a specific manner.
[0050] In this application embodiment, "at least one" refers to one or more, and "more than one" refers to two or more. "And / or" describes the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent: A alone, A and B simultaneously, or B alone, where A and B can be singular or plural. The character " / " generally indicates that the preceding and following related objects are in an "or" relationship. "At least one of the following" or similar expressions refer to any combination of these items, including any combination of single or plural items. For example, at least one of a, b, and / or c can represent: a, b, c, ab, ac, bc, or abc, where a, b, and c can be single or multiple.
[0051] Furthermore, the network architecture and business scenarios described in the embodiments of this application are for the purpose of more clearly illustrating the technical solutions of the embodiments of this application, and do not constitute a limitation on the technical solutions provided in the embodiments of this application. As those skilled in the art will know, with the evolution of network architecture and the emergence of new business scenarios, the technical solutions provided in the embodiments of this application are also applicable to similar technical problems.
[0052] Figure 1 This is an exemplary structural diagram of a billing process according to one embodiment of this application. The billing process is implemented by a mobile switching center and an online billing system.
[0053] The Mobile Switching Center (MSC) is the core of the global mobile communication system network. It controls the services of all base station controllers (BSCs) and provides switching functions as well as connections to other functions within the system. The MSC can directly interface with fixed networks such as the Public Switched Telephone Network (PSTN), Integrated Services Digital Network (ISDN), and Public Data Network (PDN), enabling interconnection between mobile users and between mobile users and fixed-line users.
[0054] An online billing system is a real-time billing system that participates in control during communication and provides functions such as real-time credit control for users, real-time billing for prepaid data services and value-added services. The online billing system supports unified billing based on bearer, session, and content events. Its architecture allows the billing system to fully participate in the service usage process, achieving real-time settlement. If the user's account balance is insufficient, the service will automatically stop.
[0055] like Figure 1As shown, when a user initiates a call, the mobile switching center and the online billing system establish an initial detection point (IDP) signaling interaction.
[0056] The online billing system performs authentication and authorization, and issues a request report BCSM event (RRBE) notification to the mobile switching center to monitor basic call state model (BCSM) events.
[0057] The mobile switching center performs detection point detection based on the RRBE issued by the online billing system and reports call events (event report basic call state model, ERB).
[0058] The online billing system reserves funds and issues an authorization allocation application (AC) to the mobile switching center. In this embodiment, the segmented AC time is 3 minutes as an example.
[0059] When the AC arrives at the mobile switching center, the mobile switching center connects the call, and online billing begins. In this embodiment, online call detail records (CDRs) begin to increase every 2 minutes of online call time.
[0060] After the mobile switching center connects the call and detects that the AC segment has been exhausted, it reports an application charging report (ACR) to the online billing system and continues to apply for segments.
[0061] After the online billing system deducts the fee from the previous AC, it continues to reserve funds to send the AC to the mobile switching center.
[0062] Due to a network anomaly between the mobile switching center and the online billing system, the AC message could not reach the mobile switching center. The mobile switching center waited for the AC to time out, at which point offline billing began, offline call detail records (CDRs) started being recorded, the call release rule was enabled, the user continued to call, and the call was subsequently sent to the online billing system for offline billing. The user hung up after the last CDR was recorded.
[0063] The online billing system charges users based on the 9-minute duration recorded in the online call detail record (CDR) starting from TI, and the 2-minute duration recorded in the offline call detail record (CDR) starting from T2. However, the actual combined online and offline call duration is 10 minutes. The offline call detail record from the mobile switching center includes some of the duration already charged by the online call detail record, resulting in duplicate charges in the offline billing process.
[0064] Figure 2This is an exemplary structural diagram of a billing process according to one embodiment of this application. The billing process is implemented by a mobile switching center and an online billing system.
[0065] The billing process between the mobile switching center and the online billing system, which did not experience network anomalies, can be referenced. Figure 1 The billing process will not be elaborated here.
[0066] When the Mobile Switching Center (MSC) connects a call and detects that the AC (Accounting Center) fragment is exhausted, it reports the ACR (Accounting Request) to the Online Billing System. However, a network anomaly occurs between the MSC and the Online Billing System, causing the ACR message to fail to reach the Online Billing System. The MSC's ACR reporting to the Online Billing System fails, and the Online Billing System does not receive the ACR for this fragment, resulting in a timeout for receiving the ACR.
[0067] At this point, offline billing begins, offline call detail records are started, the call can be made under the enabled rules, the user continues to make calls, and the calls are subsequently sent to the online billing system for offline billing. The user hangs up after the last call detail record is recorded.
[0068] The online billing system charges users based on the 6-minute duration recorded in the online call detail record (CDR) starting from T1, and the 2-minute duration recorded in the offline call detail record (CDR) starting from T2. However, the actual total duration of the user's online and offline calls is 10 minutes. The offline call detail record of the mobile switching center does not include all the call duration previously authorized by the online billing system, resulting in undercharging in the offline billing.
[0069] Figure 3 This is a flowchart illustrating a communication method according to an embodiment of this application. Figure 3 The communication method shown may include S310, S315, S320, S330 and S340.
[0070] S310, the online billing system generates online call details, which record the billing information of the first call from the first moment to the second moment.
[0071] Online call details refer to the detailed records of a user's calls and communication activities in the core network recorded by the online billing system. These details typically include call time, call duration, call type, call status, billing information, call location, network information, and call quality.
[0072] In some implementations, the online call detail record (CDR) can be called the charging data record (CDR).
[0073] In some implementations, the online call details also include an online call details identifier.
[0074] In some implementations, the online call details also include the user number of the caller who initiated the first call.
[0075] In some implementations, the online call details also record the identifier of the first call.
[0076] In some implementations, the identifier for the first call can be the call reference number (CRN).
[0077] In some implementations, the first moment is the start time of the first call, and the second moment is the last time when online billing has already begun.
[0078] In some implementations, online call details are generated immediately during or after a call and stored in a core network database, billing system, log server, or other dedicated storage device.
[0079] S315, the mobile switching center generates an offline call detail record, which records the call information of the first call from the first moment to the third moment.
[0080] Offline call detail record (offline CDR) is a record of detailed call information generated and saved periodically by network devices or systems. It typically includes call time, call duration, call type, call status, billing information, call location, network information, and call quality.
[0081] In some implementations, the mobile switching center immediately generates an offline call detail record after the first call ends.
[0082] If a network anomaly occurs between the mobile switching center and the online billing system, and the AC message fails to reach the mobile switching center or the ACR message fails to reach the online billing system, the online billing system will time out, and the mobile switching center will immediately generate an offline call detail record after the call ends.
[0083] In some implementations, the offline call details include an identifier for the first call.
[0084] In some implementations, the offline call details also record the user number of the caller who initiated the first call.
[0085] In some implementations, the first moment is the start time of the first call, and the third moment is the end time of the first call.
[0086] In some implementations, offline call details are stored in the local storage of network devices, core network databases, billing systems, and long-term archiving systems.
[0087] In some implementations, the information recorded in the offline call details can determine the duration from the first moment to the third moment. For example, the offline call details record the first moment and the third moment; or, the offline call details can record the duration from the first moment to the third moment; or, the offline call details can record the first moment and / or the third moment, as well as the duration from the first moment to the third moment.
[0088] S320: The mobile switching center sends offline call details. Correspondingly, the online billing system receives the offline call details.
[0089] The S330 online billing system rolls back the billing from the first moment to the second moment based on the online call details.
[0090] In some implementations, rollback refers to the process of adjusting the free call duration, main funds account, and credit limit of the user by reversing the deduction and returning the deducted amount. After the rollback, the original online billing call detail record status is marked as "rolled back".
[0091] S340, the online billing system bills for calls between the first and third moments based on offline call details.
[0092] In some implementations, after the online billing system rolls back the billing from the first moment to the second moment based on the online call details, the online billing system bills the calls from the first moment to the third moment based on the offline call details, deducting the free call duration, the amount in the main fund account, and the credit limit for the calls from the first moment to the third moment.
[0093] In this embodiment, the online billing system rolls back the billing from the first moment to the second moment based on the online call details. For example, it reverses the deduction of the amount from the user's free call duration, main fund account, and credit score by increasing the free call duration, main fund account, and credit score to replenish the deducted amount. Then, the online billing system bills the calls from the first moment to the third moment based on the offline call details. For example, it deducts the amount from the free call duration, main fund account, and credit score of the calls from the first moment to the third moment. This can solve the problem of inaccurate billing and eliminate billing errors.
[0094] Figure 4 This is a flowchart illustrating a communication method according to an embodiment of this application. Figure 4 The communication methods shown may include S410, S412, S415, S420, S430 and S440.
[0095] S410, the online billing system generates online call details, which record the billing information of the first call from the first moment to the second moment.
[0096] This step can be referred to in S310, and will not be repeated here.
[0097] S412, the online billing system stores key records in memory, which record the correlation between online call details and the first call.
[0098] In some implementations, memory can also be understood as a cache.
[0099] In some implementations, the key record includes an identifier for the online call details and an identifier for the first call.
[0100] In some implementations, the key record is the user number of the initiator of the first call.
[0101] S415, the mobile switching center generates an offline call detail record, which records the call information of the first call from the first moment to the third moment.
[0102] This step can be referred to in S315, and will not be repeated here.
[0103] S420: The mobile switching center sends offline call details. Correspondingly, the online billing system receives the offline call details.
[0104] This step can be referred to in S320, and will not be repeated here.
[0105] S430, the online billing system rolls back the billing from the first moment to the second moment based on the online call details.
[0106] S440, the online billing system bills for calls between the first and third moments based on offline call details.
[0107] In this embodiment, S430 and S440 can be referred to as S330 and S340 respectively, and will not be described again here.
[0108] In some implementations, online call details include an online call detail identifier, offline call details include an identifier for the first call, and key records include both the online call detail identifier and the identifier for the first call. In this implementation, the system queries memory to see if a key record related to the first call is stored based on the first call identifier contained in the offline call detail. For example, if a key record containing the first call identifier is stored in memory, then that key record is identified as a key record related to the first call. Based on the online call detail identifier in that key record, the online call detail related to the first call is determined. For example, the online call detail containing the online call detail identifier in the key record is identified as an online call detail related to the first call.
[0109] In this embodiment, the online billing system stores key records in memory and can determine the rollback of billing for the first to second moments of the online call details based on the key records. Then, the online billing system bills the calls between the first and third moments according to the offline call details. Compared with storing key records in the physical database, this can reduce the query time of key records, improve the query efficiency of key records, and thus achieve billing error elimination more quickly.
[0110] Figure 5 This is a schematic diagram of key fields of a communication method according to an embodiment of this application. Figure 5 The key fields shown may include key fields for offline call details, key record fields, and key fields for online call details.
[0111] In some implementations, the offline call detail record (CDR) key field includes the call reference signal, the mobile subscriber ISDN number (MSISDN), the calling start time (first moment), and the total calling duration (duration from the first moment to the third moment).
[0112] In some implementations, key record fields include the online call detail record identifier (CDR_ID), call reference signal, and the caller's number.
[0113] In some implementations, the Call Detail Record (CDR) key field includes the online call detail record identifier, the caller's number, and charge information. The charge information includes billing-related deduction information such as funds, credit score, and free resources.
[0114] In some implementations, the online billing system queries key records based on the call reference signal and the caller's number in the key fields of the offline call detail record. These key records document the association between the online call detail record's identifier and the call reference signal. The online billing system then obtains the identifier of the online call detail record associated with the call reference signal and the same caller's number from the key records. Based on this identifier and caller's number, the online billing system queries the online call detail records, finding those containing the same identifier and caller's number. From these online call detail records, the system obtains the billing details for the online call from the first moment to the second moment. After rolling back these billing details, billing is then performed on the call from the first moment to the third moment based on the offline call detail record.
[0115] Figure 6 This is a flowchart illustrating a communication method according to an embodiment of this application. Figure 6 The communication method shown may include S6010, S6020, S6030, S6040, S6050, S6060, S6070, S6080, S6090, S6100, S6110, S6120, S6131, S6132, S6141, S6142 and S6143.
[0116] S6010, the Mobile Switching Center sends IDP signaling. The IDP signaling contains the CRN. Accordingly, the Online Charging System receives the IDP signaling carrying the CRN.
[0117] In this step, when a user initiates a call, the mobile switching center sends IDP signaling containing CRN to establish interaction with the online billing system.
[0118] S6020, the online billing system sends the RRBE. Correspondingly, the mobile switching center receives the RRBE.
[0119] In this step, after receiving the IDP signaling carrying the CRN, the online billing system performs authentication and authorization, and sends an RRBE notification to the mobile switching center for BCSM event monitoring.
[0120] S6030, the mobile switching center sends the ERB. Correspondingly, the online billing system receives the ERB.
[0121] In this step, the mobile switching center performs detection point detection based on the RRBE sent by the online billing system and reports the ERB event.
[0122] S6040, the online billing system sends the AC. Correspondingly, the mobile switching center receives the AC.
[0123] In this step, the online billing system reserves call charges and sends an authorization allocation segment AC; when the AC arrives at the mobile switching center, the mobile switching center connects the call, and online billing begins.
[0124] In some implementations of this embodiment, the moment when the mobile switching center connects the call and online billing begins can be recorded as the first moment, which can be the original start time of the call.
[0125] In some implementations of this embodiment, the time for segmented AC is 3 minutes.
[0126] S6050, the mobile switching center sends the ACR. Correspondingly, the online billing system receives the ACR.
[0127] In this step, after the mobile switching center connects the call and detects that the AC fragment is exhausted, it reports the ACR to the online billing system and continues to request fragmented ACs from the online billing system.
[0128] In some implementations of this embodiment, the time for segmented AC is 3 minutes, as an example.
[0129] S6060, a network anomaly occurred between the mobile switching center and the online billing system when the online billing system was sending AC.
[0130] In this step, after the previous AC deducts the charge in the online billing system, it continues to reserve call charges and send ACs. However, due to a network anomaly between the mobile switching center and the online billing system, the AC message cannot reach the mobile switching center. At this point, offline billing begins, and offline call detail records start to be recorded. The start time of offline billing can be recorded as the second moment.
[0131] In some implementations, when the mobile switching center connects a call and detects that the AC fragments are exhausted, it reports the ACR to the online billing system. However, a network anomaly occurs between the mobile switching center and the online billing system, causing the ACR message to fail to reach the online billing system.
[0132] S6070, the mobile switching center waits for the AC timeout, activates the release rule, and the user continues to make calls.
[0133] In this step, the mobile switching center does not receive the AC message, waits for the AC timeout, activates the release rule, and the user continues to make calls. This session will not interact with the online billing system.
[0134] In some implementations, the mobile switching center fails to report the Accounting Request (ACR) to the online billing system. The online billing system does not receive the ACR for this segment. The online billing system times out receiving the ACR, activates the allow rule, and the user continues to make calls. This session will not interact with the online billing system again.
[0135] S6080: The online billing system will enter timeout processing after waiting for X minutes. Where X is a positive integer.
[0136] In some implementations, the value of X can be preset.
[0137] In this step, the online billing system waits at the second time. After the waiting time reaches X minutes, the online billing system enters the timeout processing stage.
[0138] In some implementations of this embodiment, the timeout processing stage includes steps S5090 and S5100.
[0139] S6090, the online billing system generates online call details. The online call details record the billing information for the first call from moment one to moment two.
[0140] This step can be referred to in S310, and will not be repeated here.
[0141] The S6100 online billing system stores key records in memory. These key records document the correlation between online call details and the first call.
[0142] This step can be referred to in S412, and will not be repeated here.
[0143] S6110, the mobile switching center generates offline call details. The offline call details record the call information of the first call from the first moment to the third moment.
[0144] This step can be referred to in S315, and will not be repeated here.
[0145] S6120, the mobile switching center sends offline call details. Correspondingly, the online billing system receives the offline call details.
[0146] This step can be referred to in S320, and will not be repeated here.
[0147] S6131, the online billing system queries the memory to see if there are any key records related to the first call stored based on the identifier of the first call. This first call is a session associated with the offline call details.
[0148] In some implementations, if no record is found in the query, S6132 is executed.
[0149] S6132, billing is based on offline call details.
[0150] S6141, the online billing system queries the memory to see if there are any key records related to the first call stored based on the identifier of the first call. This first call is a session associated with the offline call details.
[0151] In some implementations, if the query finds a record, then S6142 and S6143 are executed.
[0152] S6142, the online billing system obtains the billing details from the first moment to the second moment. These billing details are stored in the online call detail record, which the online billing system queries based on its identifier.
[0153] S6143, the online billing system re-bills for calls made between the first and third time points based on offline call details. Specifically, the online billing system performs precise rollback of the deduction details from the first to the second time point.
[0154] This step can be referred to in S440, and will not be repeated here.
[0155] Figure 7 This is a schematic diagram of the structure of a communication device according to an embodiment of this application. Figure 7 As shown, the communication device 700 may include a processing module 701 and a communication module 702.
[0156] As a first example, the communication device 700 can be used to implement the steps performed by the mobile switching center in any of the foregoing method embodiments. For example, the processing module 701 is used to implement the processing-related steps performed by the mobile switching center in any of the foregoing method embodiments, and the communication module 702 is used to implement the sending and / or receiving steps performed by the mobile switching center in any of the foregoing method embodiments.
[0157] As a second example, the communication device 700 can be used to implement the steps performed by the online billing system in any of the foregoing method embodiments. For example, the processing module 701 is used to implement the processing-related steps performed by the online billing system in any of the foregoing method embodiments, and the communication module 702 is used to implement the sending and / or receiving steps performed by the online billing system in any of the foregoing method embodiments.
[0158] Figure 8 This is a schematic diagram of the structure of a communication device provided in yet another embodiment of this application. (See attached diagram.) Figure 8As shown, the communication device 800 includes a processor 801 and a communication circuit 802. The processor 801 and the communication circuit 802 are coupled to each other. The communication circuit 802 can be a transceiver or an input / output interface. Optionally, the communication device 800 may also include a memory 803 for storing instructions executed by the processor 801, input data required by the processor 801 to execute instructions, or data generated after the processor 801 executes instructions. The memory 803 can be located externally to the processor 801 or internally to the processor 801.
[0159] As an example, processor 801 is used to implement the functions of the processing module 801 described above, and communication circuit 802 is used to implement the functions of the communication module 802 described above.
[0160] The communication device 800 can be a mobile switching center or a chip used in a mobile switching center.
[0161] The communication device 800 can be an online billing system or a chip used in an online billing system.
[0162] What can be addressed is that when the communication device 800 is a device, the communication circuit 802 can be a transceiver. When the communication device 800 is a chip, the communication circuit 802 can be an input / output interface.
[0163] In some embodiments of this application, a computer program product is also provided. When the computer program product runs on a processor, it can implement the method implemented by the mobile switching center in any of the above embodiments, or it can implement the method implemented by the online billing system in any of the above method embodiments.
[0164] In some embodiments of this application, a computer-readable storage medium is also provided, which contains computer instructions that, when executed on a processor, can implement the method implemented by the mobile switching center in any of the above embodiments, or the method implemented by the online billing system in any of the above method embodiments.
[0165] In some embodiments of this application, a communication system is also provided, which can implement the above-described... Figures 3 to 6 The method implemented by the mobile switching center and the online billing system in any embodiment shown in the figure.
[0166] It is understood that the processor in the embodiments of this application may be any of the following devices or all or part of the circuitry used for processing functions: a central processing unit (CPU), or other general-purpose processors, digital signal processors (DSPs), application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs), or other programmable logic devices, transistor logic devices, hardware components, or any combination thereof. A general-purpose processor may be a microprocessor or any conventional processor.
[0167] The method steps or functions in the embodiments of this application can be implemented in hardware or by a processor executing software instructions. The software instructions can consist of corresponding software modules, which can be stored in random access memory, flash memory, read-only memory, programmable read-only memory, erasable programmable read-only memory, electrically erasable programmable read-only memory, registers, hard disks, portable hard disks, CD-ROMs, or any other form of storage medium known in the art. An exemplary storage medium is coupled to a processor, enabling the processor to read information from and write information to the storage medium. Of course, the storage medium can also be a component of the processor. The processor and storage medium can reside in an ASIC. Additionally, the ASIC can reside in a network device or terminal device. Alternatively, the processor and storage medium can exist as discrete components in the network device or terminal device.
[0168] The steps or functions in the above embodiments can be implemented, in whole or in part, by software, hardware, firmware, or any combination thereof. When implemented using software, they can be implemented, in whole or in part, in the form of a computer program product. The computer program product includes one or more computer programs or instructions. When the computer program or instructions are loaded and executed on a computer, the processes or functions described in the embodiments of this application are executed, in whole or in part. The computer can be a general-purpose computer, a special-purpose computer, a computer network, a network device, a user equipment, or other programmable device. The computer program or instructions can be stored in a computer-readable storage medium or transferred from one computer-readable storage medium to another. For example, the computer program or instructions can be transferred from one website, computer, server, or data center to another website, computer, server, or data center via wired or wireless means. The computer-readable storage medium can be any available medium that a computer can access or a data storage device such as a server or data center that integrates one or more available media. The available medium can be a magnetic medium, such as a floppy disk, hard disk, or magnetic tape; it can also be an optical medium, such as a digital video optical disc; or it can be a semiconductor medium, such as a solid-state drive.
[0169] In the various embodiments of this application, unless otherwise specified or in case of logical conflict, the terms and / or descriptions between different embodiments are consistent and can be referenced by each other. The technical features in different embodiments can be combined to form new embodiments according to their inherent logical relationships.
[0170] It is understood that the various numerical designations used in the embodiments of this application are merely for descriptive convenience and are not intended to limit the scope of the embodiments of this application. The order of the process numbers described above does not imply the order of execution; the execution order of each process should be determined by its function and internal logic.
Claims
1. A communication method, characterized in that, The method includes: Generate an online call detail record, which records the billing information of the first call from the first moment to the second moment; Receive offline call details, wherein the offline call details record the call information of the first call from the first time to the third time; Based on the online call details, the billing from the first moment to the second moment is rolled back; Billing is performed on calls made between the first time point and the third time point based on the offline call details.
2. The method according to claim 1, characterized in that, The method further includes: Key records are stored in memory, and these key records record the association between the online call details and the first call. Based on the key records, it was determined that the billing for the online call details would be rolled back.
3. The method according to claim 2, characterized in that, The online call details contain the identifier of the online call details, the offline call details contain the identifier of the first call, and the key record contains both the identifier of the online call details and the identifier of the first call.
4. The method according to claim 3, characterized in that, The offline call details, the key records, and the online call details record the user number of the initiator of the first call.
5. A communication method, characterized in that, The method includes: Generate an offline call detail record, which records the call information of the first call from the first time to the third time, where the first time is the start time of the first call; Send offline call details.
6. A communication device, characterized in that, The method includes a processor configured to execute computer program instructions to implement the method as claimed in any one of claims 1 to 4, or configured to execute computer program instructions to implement the method as claimed in claim 5.
7. A chip, characterized in that, It includes processing circuitry, the processing circuitry being configured to run a program or instructions to cause the method as described in any one of claims 1 to 4 to be implemented, or to run a program or instructions to cause the method as described in claim 5 to be implemented.
8. A computer-readable storage medium, characterized in that, Includes instructions that, when run on a computer, cause the computer to perform the method as described in any one of claims 1 to 4, or cause the computer to perform the method as described in claim 5.
9. A computer program product, characterized in that, It includes computer program code or instructions that, when executed, cause the method as described in any one of claims 1 to 4 to be implemented, or cause the method as described in claim 5 to be implemented.
10. A communication system, characterized in that, Includes means for performing the method as described in any one of claims 1 to 4, and means for performing the method as described in claim 5.