CN113411761A - Call bill charging method and system - Google Patents
Call bill charging method and system Download PDFInfo
- Publication number
- CN113411761A CN113411761A CN202010184828.2A CN202010184828A CN113411761A CN 113411761 A CN113411761 A CN 113411761A CN 202010184828 A CN202010184828 A CN 202010184828A CN 113411761 A CN113411761 A CN 113411761A
- Authority
- CN
- China
- Prior art keywords
- ticket
- call
- mrm
- call ticket
- current
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Granted
Links
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
- H04W4/24—Accounting or billing
Landscapes
- Business, Economics & Management (AREA)
- Accounting & Taxation (AREA)
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Telephonic Communication Services (AREA)
- Meter Arrangements (AREA)
Abstract
The embodiment of the invention relates to the technical field of communication, and discloses a method and a system for charging a call ticket, wherein the method comprises the following steps: MRM obtains the current call ticket sent by BCG; the MRM matches the current call ticket with a historical call ticket according to keywords carried by the current call ticket; if the matching is successful, the MRM combines the current call ticket into the history call ticket successfully matched to obtain a combined target call ticket, wherein the flow of the target call ticket is the sum of the flow of the current call ticket and the flow of the history call ticket successfully matched; MRM determines whether the flow of the target call ticket reaches a combination threshold value; if the combined threshold value is reached, the MRM outputs the target call ticket to the BCG; the BCG bills the target call list to charge the target call list. Through the mode, the embodiment of the invention realizes that a plurality of call tickets are combined into one call ticket for charging.
Description
Technical Field
The embodiment of the invention relates to the technical field of communication, in particular to a method and a system for charging a call ticket.
Background
With the continuous development of mobile communication services and the network characteristics of the mobile communication network "always on", the call tickets cut by the network elements to the charging system are usually very fragmented, i.e., each call ticket has a very small flow. In addition, the rapid development of the internet of things service leads to the rapid increase of the small-flow telephone bill.
In the current rating system, the processing modes of the low-flow call ticket and the high-flow call ticket are the same, namely, the call tickets are sequentially processed in series according to the generation sequence of the call tickets.
Because the small flow telephone bill is more, the bill cutting is frequent and the burden of the charging system is heavy.
Disclosure of Invention
In view of the above problems, embodiments of the present invention provide a method and a system for charging a ticket, which are used to solve the problem of heavy burden of a charging system in the prior art.
According to an aspect of the embodiments of the present invention, a method for charging a call ticket is provided, which is applied to a charging system, wherein the charging system includes an MRM and a BCG, and the method includes:
MRM obtains the current call ticket sent by BCG;
the MRM matches the current call ticket with a historical call ticket according to keywords carried by the current call ticket;
if the matching is successful, the MRM combines the current call ticket into the history call ticket successfully matched to obtain a combined target call ticket, wherein the flow of the target call ticket is the sum of the flow of the current call ticket and the flow of the history call ticket successfully matched;
MRM determines whether the flow of the target call ticket reaches a combination threshold value;
if the combined threshold value is reached, the MRM outputs the target call ticket to the BCG;
the BCG bills the target call list to charge the target call list.
In an alternative mode, the keyword comprises a user number and a service code; the MRM matches the current call ticket with a historical call ticket according to the keywords carried by the current call ticket, and the method comprises the following steps:
the MRM matches the user number and the service code of the current call ticket with the user number and the service code of the historical call ticket;
and if the history call bill has the history call bill which is the same as the user number and the service code of the current call bill, the matching is successful, otherwise, the matching is unsuccessful.
In an optional manner, if the current ticket and the historical ticket are not successfully matched, the method further includes:
the MRM stores the current call ticket and sends a first identification to the BCG, wherein the first identification is used for representing that the current call ticket is a first call ticket;
the BCG bills the current call list according to the first identification so as to charge the current call list.
In an optional manner, the charging system further includes an MRG, and after the BCG singulates the current session according to the first identifier, the method further includes:
the MRG determines the free flow surplus corresponding to the user number according to the user number;
and the MRG determines the merging threshold according to the free flow residual and sends the merging threshold to the MRM.
In an optional manner, after obtaining the combined target ticket, the method further includes:
MRM judges whether the current ticket meets the overtime ticket switching condition;
if the overtime list switching condition is met, outputting the target call ticket to the BCG;
and if the overtime ticket switching condition is not met, the MRM determines whether the flow of the target ticket reaches a combination threshold value.
In an optional manner, the current ticket includes a charging attribute, and if the current ticket is successfully matched with the historical ticket, the method further includes:
comparing the charging attribute of the current ticket with the charging attribute of the history ticket successfully matched, and if the charging attribute of the current ticket is inconsistent with the charging attribute of the history ticket successfully matched, combining the current ticket with the history ticket successfully matched by the MRM to obtain a combined target ticket;
and the MRM outputs the target call ticket to the BCG.
In an optional manner, the charging attribute includes at least one of a call ticket generation time, a cell identifier, and a network type.
In an optional manner, after obtaining the combined target call ticket, the method further includes:
MRM returns second identification to BCG, the second identification is used to represent that the current call tickets are combined;
and the BCG deletes the current call ticket according to the second identification.
In an optional manner, after the MRM outputs the target ticket to the BCG, the method further includes:
and the MRM deletes the target call ticket.
According to another aspect of the embodiments of the present invention, a ticket charging system is provided, where the system includes: BCG, MRM and MRG:
BCG and MRM are interconnected in communication, and MRM and MRG are interconnected in communication; the call ticket charging system is used for executing the call ticket charging method.
In the embodiment of the invention, the MRM combines the call tickets into the history call tickets, thereby realizing that a plurality of call tickets are combined into one call ticket, and outputting the combined call ticket to carry out charging operation when the combined call ticket reaches the combined threshold value. By the mode, the process of performing multiple bill cutting on the plurality of call bills is saved as a process of performing one-time bill cutting on the combined call bills, and the burden of a charging system is reduced.
The foregoing description is only an overview of the technical solutions of the embodiments of the present invention, and the embodiments of the present invention can be implemented according to the content of the description in order to make the technical means of the embodiments of the present invention more clearly understood, and the detailed description of the present invention is provided below in order to make the foregoing and other objects, features, and advantages of the embodiments of the present invention more clearly understandable.
Drawings
The drawings are only for purposes of illustrating embodiments and are not to be construed as limiting the invention. Also, like reference numerals are used to refer to like parts throughout the drawings. In the drawings:
fig. 1 shows a schematic flow chart of a method for charging a ticket according to a first embodiment of the present invention;
fig. 2 is a flowchart illustrating a method for charging a call ticket according to a second embodiment of the present invention;
fig. 3 shows a flowchart of a method for charging a call ticket according to a third embodiment of the present invention;
fig. 4 shows a flowchart of a method for charging a call ticket according to a fourth embodiment of the present invention;
fig. 5 shows a schematic structural diagram of a ticket charging system according to a fifth embodiment of the present invention.
Detailed Description
Exemplary embodiments of the present invention will be described in more detail below with reference to the accompanying drawings. While exemplary embodiments of the invention are shown in the drawings, it should be understood that the invention can be embodied in various forms and should not be limited to the embodiments set forth herein.
The application scenario of the embodiment of the invention is the ticket charging in a ticket charging system. After the call ticket is generated, the call ticket is distributed to the task processing server by the task distributing server, and the call ticket distributed by the task distributing server is charged by the task processing server. The call ticket of the task processor enters a Business Charging Gateway (BCG) in sequence, and the BCG is responsible for performing order switching control on the current call ticket. The current call ticket is the current received call ticket of the BCG. And the bill after the bill cutting enters the next charging processing flow. Whether the current call ticket needs to be cut is determined by processing a combined records database (MRM) call ticket. MRM realizes the combination of a plurality of call tickets, and when meeting the call ticket cutting condition, sends call ticket cutting information to BCG, and the BCG performs call ticket cutting. Compared with the method that the list is cut once for each bill, the bill combined into one bill is cut and charged, so that the charging flow is reduced, and the burden of a charging system is lightened.
Fig. 1 shows a flowchart of a ticket charging method according to a first embodiment of the present invention. The embodiment of the invention is applied to a charging system, and the charging system comprises MRM and BCG. As shown in fig. 1, the method comprises the steps of:
step 110: and the MRM acquires the current call ticket sent by the BCG.
In this step, the ticket is generated when the communication session is performed. A communication session is a process by which a terminal device communicates with an interactive system. For example, the process of a handset making a call through a call system is a session. The conversation generates a corresponding ticket, and the ticket enters a charging system for charging. After the BCG of the charging system acquires the current call ticket, the current call ticket is cached to the MRM. The ticket contains various information, such as the session time, the cell where the terminal device initiating the session is located, the user number of the terminal, the service code, and other keywords. The internet surfing time comprises the internet surfing starting time, the internet surfing ending and the internet surfing time. The service code means a code of a website or application software accessed by the user through internet. For example, the user accesses the video software a by surfing the internet, the code corresponding to the video software a is 17501, and the service code of the ticket is 17501.
Step 120: and the MRM matches the current call ticket with the historical call ticket according to the keywords carried by the current call ticket.
The historical ticket is a ticket stored before the current ticket. Only one call ticket record is available for the same service of the same user in the historical call tickets. The keywords carried by the call ticket include, but are not limited to, the subscriber number and the service code. In a specific implementation manner, the keywords carried by the ticket are: a subscriber number, a charging ID, a Gateway GPRS Support Node (GGSN), a Serving GPRS Support Node (SGSN), and a service code. In the charging service of the internet of things, keywords carried by a ticket include: subscriber number, APN, service code. And when the matching is carried out, the call bills with the same keywords carried by the call bills are the same call bill. And matching the user number and the service code of the current call ticket with the user number and the service code of each historical call ticket. If the historical call ticket matched with the user number and the service code of the current call ticket exists in the historical call ticket, the matching is successful; and if the historical call ticket does not have the historical call ticket matched with the user number and the service code of the current call ticket, indicating that the matching is unsuccessful.
Step 130: if the matching is successful, the MRM combines the current call ticket into the history call ticket successfully matched to obtain the combined target call ticket.
The successfully matched historical ticket and the current ticket only have different flow, and the rest information is the same. The flow of the combined target call ticket is the sum of the flow of the current call ticket and the flow of the history call ticket successfully matched.
Step 140: the MRM determines whether the flow of the target call ticket reaches a combination threshold, if so, the step 150 is executed, otherwise, the step 170 is executed.
Wherein the combining threshold is a combining threshold stored in the MRM. And when the flow of the target call ticket reaches a combination threshold value, performing call ticket cutting. For example, the traffic of the call ticket is 20M, the traffic of the history call ticket successfully matched is 80M, and the combining threshold is 100M, then the traffic of the combined target call ticket reaches the combining threshold.
Step 150: and the MRM outputs the target call ticket to the BCG.
And when the flow of the target call ticket reaches the combined threshold value, the MRM outputs the target call ticket to the BCG. After the MRM outputs the target call ticket, the MRM deletes the target call ticket so as to combine the new call tickets.
Step 160: the BCG bills the target call list to charge the target call list.
And after the BCG receives the target call ticket, performing call ticket cutting on the target call ticket according to the call ticket cutting identification carried in the target call ticket. The embodiment of the present invention does not limit the form of the cutting list identifier, for example, the cutting list identifier may be an arabic numeral 2. After the BCG bills the target call list, the charging system executes the charging process to the target call list.
Step 170: the MRM does not output the target call ticket to the BCG.
And if the flow of the target call ticket does not reach the combination threshold, the MRM does not output the target call ticket to the BCG. BCG continuously sends the newly received call ticket to MRM, and MRM continuously executes the operations of steps 110-150.
In the embodiment of the invention, the MRM combines the call tickets into the history call tickets, thereby realizing that a plurality of call tickets are combined into one call ticket, and outputting the combined call ticket to carry out charging operation when the combined call ticket reaches the combined threshold value. By the mode, the process of performing multiple bill cutting on the plurality of call bills is saved as a process of performing one-time bill cutting on the combined call bills, and the burden of a charging system is reduced.
In some embodiments, after the combined target call ticket is obtained, the MRM returns a second identifier to the BCG, where the second identifier is used to represent that the current call ticket is combined. And after the BCG receives the second representation, deleting the current call ticket so as to avoid billing for the current call ticket.
Fig. 2 shows a flowchart of a ticket charging method according to a second embodiment of the present invention. The embodiment of the invention is applied to a charging system, and the charging system comprises a convergence rule generator (MRG) besides a BCG and an MRM. And the MRG stores the free flow surplus of each user and the merging threshold corresponding to the free flow surplus of each section. The merging threshold is the merging threshold in step 140 of the first embodiment. The embodiment of the present invention includes the following processes as shown in fig. 2 in addition to the steps shown in fig. 1:
step 210: and the MRM acquires the current call ticket sent by the BCG.
Step 220: and the MRM matches the current call ticket with the historical call ticket according to the keywords carried by the current call ticket.
Step 230: if the matching is unsuccessful, the MRM stores the current call ticket and sends a first identification to the BCG.
In this step, if the matching between the current ticket and the historical ticket is unsuccessful, it is indicated that there is no ticket with the same keyword as the current ticket in the historical ticket, and the current ticket is the first ticket. The MRM stores the first call ticket, and if a new call ticket successfully matched with the first call ticket is received subsequently, the call tickets are combined according to the method in the first embodiment. The first mark is a mark agreed in advance by MRM and BCG, and is used for representing the current call ticket as a first call ticket. The embodiment of the present invention does not limit the specific form of the first identifier, for example, the first identifier may be represented by an arabic numeral 0.
Step 240: the BCG bills the current call list according to the first identification so as to charge the current call list.
In this step, after the current ticket is cut, the current ticket reaches the MRG through the charging process to determine the free traffic remaining corresponding to the user number generating the ticket. The user number is one of the keywords carried by the call ticket.
Step 250: and the MRG determines the free traffic surplus corresponding to the user number according to the user number.
In this step, the MRG stores the free traffic remaining corresponding to each user number. And when the MRG receives the call ticket of the speaking charging process, the difference is made between the free flow of the user number corresponding to the call ticket and the flow of the call ticket, and the free flow surplus is updated according to the difference result.
Step 260: and the MRG determines a merging threshold according to the free traffic residual and sends the merging threshold to the MRM.
The MRG also stores the corresponding relation between the free flow surplus and the merging threshold. The free traffic for one segment remains corresponding to one merged threshold. The block segment may be a specific flow value or may be a percentage of the total free flow. The more free traffic remains, the larger the merge threshold. Taking the percentage of the total free flow as an example, when the range of the free flow surplus is 40% -100%, the free flow surplus is sufficient, at this time, the combination threshold can be 50M, namely when the flow of the combined call ticket reaches 50M, the combination is not performed, and the combined call ticket is output for the order cutting. When the free traffic remaining interval is 0% -40%, the free traffic remaining is insufficient, and then the merging threshold may be 20M. When the free flow in the MRG is left to be updated, the corresponding combining threshold is sent to the MRM to update the combining threshold in the MRM.
It can be understood that when the free traffic remains 0, all tickets of the user need to be charged. At this time, the combination threshold is 0, that is, the call tickets are not combined, and each call ticket needs to be subjected to billing for cutting.
The embodiment of the invention bills the first call, thereby enabling the MRG to obtain the free flow surplus of the user number corresponding to the call ticket, further determining the combination threshold value, and facilitating the subsequent call ticket combination.
Fig. 3 shows a flowchart of a ticket charging method according to a third embodiment of the present invention. As shown in fig. 3, an embodiment of the present invention includes the following steps:
step 310: and the MRM acquires the current call ticket sent by the BCG.
Step 320: and the MRM matches the current call ticket with the historical call ticket according to the keywords carried by the current call ticket.
Step 330: if the matching is successful, the MRM combines the current call ticket into the history call ticket successfully matched to obtain the combined target call ticket.
Steps 310 to 330 are the same as steps 110 to 130 in the first embodiment, please refer to the description of steps 110 to 130 in the first embodiment, which is not repeated herein.
Step 340: and the MRM judges whether the current call ticket meets an overtime ticket switching condition, if so, the step 350 is executed, and if not, the step 370 is executed.
The overtime ticket switching condition is a time threshold, and the current ticket comprises the duration of the ticket. And if the duration of the current call ticket is greater than or equal to the time threshold, determining that the call ticket meets an overtime call ticket switching condition.
Step 350: and outputting the target call ticket to the BCG.
And if the current call ticket meets the overtime ticket switching condition, outputting the target call ticket to the BCG.
Step 360: the BCG bills the target call list to charge the target call list.
Step 370: and the MRM determines whether the flow of the target call ticket reaches a combination threshold, if so, executes step 350, otherwise, executes step 380.
Step 380: the MRM does not output the target call ticket to the BCG.
The embodiment of the invention outputs the combined target call ticket for charging when the current call ticket meets the overtime call ticket switching condition so as to charge the large-flow call ticket, thereby ensuring the working instantaneity of the charging system.
Fig. 4 shows a flowchart of a ticket charging method according to a fourth embodiment of the present invention. Compared with the first embodiment, when the matching is successful in step 120, the embodiment of the present invention, in addition to performing step 130, further includes the following steps:
step 410: and comparing the charging attribute of the current ticket with the charging attribute of the history ticket successfully matched.
In this step, the charging attribute includes at least one of a call ticket generation time, a cell identifier, and a network type. The ticket generation time can be used for identifying whether the ticket is generated in busy time or idle time. For example, more tickets are generated from nine am to 12 am, and the tickets in the time period are busy hours; the call ticket generation from 12 pm to 2 pm is less, and the call ticket in the time period is idle. The cell identifier is used for identifying the cell where the equipment for generating the call ticket is located. The network type includes, but is not limited to, any one of a 2G network, a 3G network, a 4G network, and a 5G network.
Step 420: and if the charging attribute of the current ticket is inconsistent with the charging attribute of the history ticket successfully matched, combining the current ticket into the history ticket successfully matched to obtain a combined target ticket.
In this step, if any charging attribute of the current ticket is inconsistent with the charging attribute of the history ticket successfully matched, the charging attribute of the current ticket is considered to be changed, and the current ticket and the history ticket successfully matched are combined into the target ticket.
If the charging attribute of the current ticket is consistent with the charging attribute of the history ticket successfully matched, the current ticket is combined into the history ticket successfully matched to obtain a combined target ticket, and whether the flow of the target ticket reaches a combined threshold value is further judged.
Step 430: and the MRM outputs the target call ticket to the BCG.
And if the charging attribute of the current call ticket is not consistent with the charging attribute of the history call ticket successfully matched with the current call ticket, outputting the combined target call ticket to the BCG no matter whether the flow of the combined target call ticket reaches the combined threshold value or not.
The embodiment of the invention combines the current ticket and the history ticket successfully matched with the current ticket and outputs the combined ticket when the charging attribute changes, thereby realizing the respective charging of the tickets with different charging attributes and improving the reliability of the charging system.
Fig. 5 is a schematic structural diagram of a charging system according to a fifth embodiment of the present invention, and as shown in fig. 5, the charging system includes BCG100, MRM200, and MRG 300. BCG100 and MRM200 are interconnected in communication, BCG100 is used for sending the current call ticket to MRM200, and is also used for performing order switching control according to the information returned by MRM 200. The ticket after BCG100 billing reaches MRG300 through charging processing, MRG300 determines the residual free flow of the user number according to the user number carried by the ticket, determines the combined threshold value according to the residual free flow, and sends the threshold value to MRM 200. MRM200 and MRG300 are communicatively coupled, and MRG300 transmits the combined threshold to MRM 200. The charging system is specifically configured to execute the ticket charging method according to any one of the first to fourth embodiments.
The embodiment of the invention provides a computer storage medium, wherein computer program instructions are stored in the computer storage medium and can be called by a processor to enable BCG, MRM and MRG in a telephone charge charging system to execute a telephone bill charging method in any method embodiment.
The embodiment of the invention provides a computer program product, wherein the computer program can be called by a processor to enable BCG, MRM and MRG in a call ticket charging system to execute the call ticket charging method in any method embodiment.
The algorithms or displays presented herein are not inherently related to any particular computer, virtual system, or other apparatus. Various general purpose systems may also be used with the teachings herein. The required structure for constructing such a system will be apparent from the description above. In addition, embodiments of the present invention are not directed to any particular programming language. It is appreciated that a variety of programming languages may be used to implement the teachings of the present invention as described herein, and any descriptions of specific languages are provided above to disclose the best mode of the invention.
In the description provided herein, numerous specific details are set forth. It is understood, however, that embodiments of the invention may be practiced without these specific details. In some instances, well-known methods, structures and techniques have not been shown in detail in order not to obscure an understanding of this description.
Similarly, it should be appreciated that in the foregoing description of exemplary embodiments of the invention, various features of the embodiments of the invention are sometimes grouped together in a single embodiment, figure, or description thereof for the purpose of streamlining the invention and aiding in the understanding of one or more of the various inventive aspects. However, the disclosed method should not be interpreted as reflecting an intention that: that the invention as claimed requires more features than are expressly recited in each claim. Rather, as the following claims reflect, inventive aspects lie in less than all features of a single foregoing disclosed embodiment. Thus, the claims following the detailed description are hereby expressly incorporated into this detailed description, with each claim standing on its own as a separate embodiment of this invention.
Those skilled in the art will appreciate that the modules in the device in an embodiment may be adaptively changed and disposed in one or more devices different from the embodiment. The modules or units or components of the embodiments may be combined into one module or unit or component, and furthermore they may be divided into a plurality of sub-modules or sub-units or sub-components. All of the features disclosed in this specification (including any accompanying claims, abstract and drawings), and all of the processes or elements of any method or apparatus so disclosed, may be combined in any combination, except combinations where at least some of such features and/or processes or elements are mutually exclusive. Each feature disclosed in this specification (including any accompanying claims, abstract and drawings) may be replaced by alternative features serving the same, equivalent or similar purpose, unless expressly stated otherwise.
Furthermore, those skilled in the art will appreciate that while some embodiments herein include some features included in other embodiments, rather than other features, combinations of features of different embodiments are meant to be within the scope of the invention and form different embodiments. For example, in the following claims, any of the claimed embodiments may be used in any combination.
It should be noted that the above-mentioned embodiments illustrate rather than limit the invention, and that those skilled in the art will be able to design alternative embodiments without departing from the scope of the appended claims. In the claims, any reference signs placed between parentheses shall not be construed as limiting the claim. The word "comprising" does not exclude the presence of elements or steps not listed in a claim. The word "a" or "an" preceding an element does not exclude the presence of a plurality of such elements. The invention may be implemented by means of hardware comprising several distinct elements, and by means of a suitably programmed computer. In the unit claims enumerating several means, several of these means may be embodied by one and the same item of hardware. The usage of the words first, second and third, etcetera do not indicate any ordering. These words may be interpreted as names. The steps in the above embodiments should not be construed as limiting the order of execution unless specified otherwise.
Claims (10)
1. A call ticket charging method is applied to a charging system, the charging system comprises MRM and BCG, and the method is characterized by comprising the following steps:
MRM obtains the current call ticket sent by BCG;
the MRM matches the current call ticket with a historical call ticket according to keywords carried by the current call ticket;
if the matching is successful, the MRM combines the current call ticket into the history call ticket successfully matched to obtain a combined target call ticket, wherein the flow of the target call ticket is the sum of the flow of the current call ticket and the flow of the history call ticket successfully matched;
MRM determines whether the flow of the target call ticket reaches a combination threshold value;
if the combined threshold value is reached, the MRM outputs the target call ticket to the BCG;
the BCG bills the target call list to charge the target call list.
2. The method of claim 1, wherein the keywords comprise a subscriber number and a service code; the MRM matches the current call ticket with a historical call ticket according to the keywords carried by the current call ticket, and the method comprises the following steps:
the MRM matches the user number and the service code of the current call ticket with the user number and the service code of the historical call ticket;
and if the history call bill has the history call bill which is the same as the user number and the service code of the current call bill, the matching is successful, otherwise, the matching is unsuccessful.
3. The method of claim 2, wherein if the current ticket is not successfully matched to the historical ticket, the method further comprises:
the MRM stores the current call ticket and sends a first identification to the BCG, wherein the first identification is used for representing that the current call ticket is a first call ticket;
the BCG bills the current call list according to the first identification so as to charge the current call list.
4. The method as claimed in claim 3, wherein the billing system further comprises an MRG, and after the BCG singulates the current call according to the first identity, the method further comprises:
the MRG determines the free flow surplus corresponding to the user number according to the user number;
and the MRG determines the merging threshold according to the free flow residual and sends the merging threshold to the MRM.
5. The method of claim 1, wherein after obtaining the combined target ticket, the method further comprises:
MRM judges whether the current ticket meets the overtime ticket switching condition;
if the overtime list switching condition is met, outputting the target call ticket to the BCG;
and if the overtime ticket switching condition is not met, the MRM determines whether the flow of the target ticket reaches a combination threshold value.
6. The method of claim 1, wherein the current ticket contains a charging attribute, and if the current ticket is successfully matched with the historical ticket, the method further comprises:
comparing the charging attribute of the current ticket with the charging attribute of the history ticket successfully matched, and if the charging attribute of the current ticket is inconsistent with the charging attribute of the history ticket successfully matched, combining the current ticket with the history ticket successfully matched by the MRM to obtain a combined target ticket;
and the MRM outputs the target call ticket to the BCG.
7. The method of claim 6, wherein the charging attributes comprise at least one of call ticket generation time, cell identification, and network type.
8. The method of claim 1, wherein after obtaining the combined target call ticket, the method further comprises:
MRM returns second identification to BCG, the second identification is used to represent that the current call tickets are combined;
and the BCG deletes the current call ticket according to the second identification.
9. The method according to claim 1, wherein after the MRM outputs the target call ticket to the BCG, the method further comprises:
and the MRM deletes the target call ticket.
10. A ticket billing system, the system comprising: BCG, MRM and MRG;
BCG and MRM are interconnected in communication, and MRM and MRG are interconnected in communication; the call ticket charging system is used for executing the call ticket charging method according to any one of claims 1-9.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010184828.2A CN113411761B (en) | 2020-03-17 | 2020-03-17 | Call bill charging method and system |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010184828.2A CN113411761B (en) | 2020-03-17 | 2020-03-17 | Call bill charging method and system |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN113411761A true CN113411761A (en) | 2021-09-17 |
| CN113411761B CN113411761B (en) | 2022-12-27 |
Family
ID=77677065
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202010184828.2A Active CN113411761B (en) | 2020-03-17 | 2020-03-17 | Call bill charging method and system |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN113411761B (en) |
Citations (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101217385A (en) * | 2008-01-15 | 2008-07-09 | 中兴通讯股份有限公司 | A method and system for the temporary storage and treatment of charging bill |
| US20080181378A1 (en) * | 2007-01-30 | 2008-07-31 | Lucent Technologies Inc. | Method of correlating charging data records within an offline charging system |
| CN101959168A (en) * | 2009-07-16 | 2011-01-26 | 华为技术有限公司 | Billing statistical method and device |
| CN102065192A (en) * | 2009-11-18 | 2011-05-18 | 中国移动通信集团安徽有限公司 | Call ticket de-duplication method and device |
| CN103167460A (en) * | 2011-12-12 | 2013-06-19 | 中国移动通信集团河北有限公司 | Dealing method and device of billing ticket |
| US20150044989A1 (en) * | 2012-03-21 | 2015-02-12 | Interdigital Patent Holdings, Inc. | Sponsoring of a mobile station session by another mobile station in a wireless network |
| CN105791613A (en) * | 2014-12-24 | 2016-07-20 | 中兴通讯股份有限公司 | Call bill processing method and device |
| CN110493016A (en) * | 2018-05-15 | 2019-11-22 | 中国移动通信集团浙江有限公司 | Flow charging method and device |
-
2020
- 2020-03-17 CN CN202010184828.2A patent/CN113411761B/en active Active
Patent Citations (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20080181378A1 (en) * | 2007-01-30 | 2008-07-31 | Lucent Technologies Inc. | Method of correlating charging data records within an offline charging system |
| CN101217385A (en) * | 2008-01-15 | 2008-07-09 | 中兴通讯股份有限公司 | A method and system for the temporary storage and treatment of charging bill |
| CN101959168A (en) * | 2009-07-16 | 2011-01-26 | 华为技术有限公司 | Billing statistical method and device |
| CN102065192A (en) * | 2009-11-18 | 2011-05-18 | 中国移动通信集团安徽有限公司 | Call ticket de-duplication method and device |
| CN103167460A (en) * | 2011-12-12 | 2013-06-19 | 中国移动通信集团河北有限公司 | Dealing method and device of billing ticket |
| US20150044989A1 (en) * | 2012-03-21 | 2015-02-12 | Interdigital Patent Holdings, Inc. | Sponsoring of a mobile station session by another mobile station in a wireless network |
| CN105791613A (en) * | 2014-12-24 | 2016-07-20 | 中兴通讯股份有限公司 | Call bill processing method and device |
| CN110493016A (en) * | 2018-05-15 | 2019-11-22 | 中国移动通信集团浙江有限公司 | Flow charging method and device |
Non-Patent Citations (1)
| Title |
|---|
| HUAWEI: "S5-193074 "Rel-16 CR 32.255 Add the quota management for interworking"", 《3GPP TSG_SA\WG5_TM》 * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN113411761B (en) | 2022-12-27 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN111124917B (en) | Method, device, equipment and storage medium for managing and controlling public test cases | |
| CN102438205B (en) | Method and system for pushing service based on action of mobile user | |
| CN106375358A (en) | Method, device and system for distributing service requirements | |
| EP3591894B1 (en) | Tariff data determination method and device | |
| CN101316391A (en) | Charge querying method and device | |
| CN112328760A (en) | Service providing method, device and system | |
| CN111242754B (en) | Account data updating method and device and electronic equipment | |
| WO2024082772A1 (en) | Method and apparatus for determining advertisement placement strategy, computer device, and storage medium | |
| CN111343348A (en) | Application method, system, device and storage medium of interactive voice response menu | |
| WO2021169110A1 (en) | Transportation route generation method, apparatus, computer device, and storage medium | |
| CN113411761B (en) | Call bill charging method and system | |
| CN115879889A (en) | Service processing method and device based on block chain and computer equipment | |
| CN113556430B (en) | Outbound system and outbound method | |
| EP2713550A1 (en) | Centralized online charging method and equipment | |
| CN111369281A (en) | Online message processing method, device, equipment and readable storage medium | |
| CN108964932B (en) | Charging method, device and computer readable storage medium | |
| CN115510366A (en) | Business message pushing method and device, computer equipment and storage medium | |
| CN110333949B (en) | Search engine processing method, device, terminal and storage medium | |
| CN113869576A (en) | Order processing method, device, equipment and storage medium | |
| WO2022038455A1 (en) | System and method for network usage product provisioning | |
| CN110099179B (en) | Number updating method and device | |
| CN111724788B (en) | Service processing method, device and equipment | |
| CN112862495A (en) | Transaction data risk control method and device, computer equipment and storage medium | |
| CN117689428B (en) | Advertisement waterfall stream price inquiry strategy generation method and device, electronic equipment and medium | |
| CN110196895B (en) | User data information self-service query method and device, computer equipment and storage medium |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |