CN111182485A

CN111182485A - Single ticket total traffic control system and method

Info

Publication number: CN111182485A
Application number: CN202010003396.0A
Authority: CN
Inventors: 王嘉伟
Original assignee: Lanzhou Jiawen Electronic Technology Co Ltd
Current assignee: Lanzhou Jiawen Electronic Technology Co Ltd
Priority date: 2020-01-02
Filing date: 2020-01-02
Publication date: 2020-05-19

Abstract

The invention discloses a single ticket total flow control system and a method, belonging to the technical field of ticket flow control.A Business Charging Gateway (BCG) is used for matching accumulated records according to original ticket information and carrying out combined filtering management on a dialog ticket; a charging gateway data generator (MRG) for generating said cumulative record; the combining rule management module (MRM) is used for managing the combining rule of the call tickets and caching the accumulated records into a Memory Database (MDB); a Memory Database (MDB) for storing the cumulative record; the system management module is used for BCG starting strategy planning and configuration and carrying out user level, scene level and charging element flow switching; the invention adopts the charging gateway to combine the invalid call tickets, optimizes the flow call ticket processing on the premise of keeping the logic and the flow of the existing system, and combines the fragmentary call tickets in the package.

Description

Single ticket total traffic control system and method

Technical Field

The invention relates to the technical field of call ticket flow control, in particular to a single call ticket total flow control system and a method.

Background

The existing system has low telephone charge processing efficiency and cannot effectively deal with the rapid development of flow business: the method mainly shows that the invalid call ticket accounts for a high ratio, the system resource waste is large, and the value is low: analyzing the current GPRS ticket, and finding that the broken ticket accounts for extremely high in the finally issued ticket due to lack of effective control on the total flow of the single ticket whether online charging or offline charging; the small-sized single amount (within 1M) accounts for 88.11%, the actual flow value only accounts for 6.71%, the consumption is high, the value is low, and a large amount of calculation and storage resources are wasted.

Disclosure of Invention

The invention aims to: in order to solve the problems, the invention provides a single ticket total traffic control system and a single ticket total traffic control method.

The technical scheme adopted by the invention is as follows:

a single ticket total traffic control system comprises

The Business Charging Gateway (BCG) is used for matching the accumulated records according to the original ticket information and carrying out merging, filtering and management on the conversation ticket;

a charging gateway data generator (MRG) for generating said cumulative record;

a combining rule management module (MRM) for managing the combining rule of the call tickets and caching the accumulated records into a Memory Database (MDB);

a Memory Database (MDB) for storing the cumulative record;

and the system management module is used for BCG starting strategy planning and configuration and carrying out user level, scene level and charging element flow switching.

Further, the service charging gateway (BCG) includes: the system comprises a specific element filtering module, a user level filtering module, a combined key value generating module, a combined key value comparing module, a ticket popping module, a flow accumulating module and a ticket cutting threshold module;

the specific element filtering module is used for filtering the call ticket with the specific element;

a user-level filtering module for filtering users without cumulative flow rate charge;

the combined key value generating module is used for generating the combined key value in the original call ticket;

a merged key value comparison module for matching the merged key value with the accumulated records;

the call ticket popping module is used for popping up the call ticket;

the flow accumulation module is used for accumulating the flow;

and the list cutting threshold module is used for judging whether the accumulated flow reaches a list cutting threshold.

Further, the charging gateway data generator (MRG) comprises: the system comprises a ticket element analysis module, a product filtering module, a quota calculation module and an information assembly module;

the ticket element analysis module is used for analyzing elements in the ticket;

the product filtering module is used for filtering products which are not suitable for the flow accumulation function;

the quota calculation module is used for storing a quota as a judgment basis for generating the cumulative record;

and the information assembly module is used for generating a final accumulated record.

A single ticket total traffic control method comprises the following steps:

step 1: the call ticket accesses a Business Charging Gateway (BCG), the charging gateway judges whether the current call ticket of the user can be charged cumulatively, if yes, the step 2 is skipped, otherwise, the standard charging process is skipped;

step 2: judging whether the ticket has an accumulated record, if so, skipping to the step 3, otherwise, skipping to the standard charging process;

and step 3: the Business Charging Gateway (BCG) analyzes the corresponding charging subjects according to the elements in the current call ticket, matches the charging subjects with the accumulated records, if the matching is successful, the step 4 is skipped, otherwise, the step is skipped to the standard charging process;

and 4, step 4: judging whether the available flow in the accumulated record can resist the flow of the current call bill or not, and if the available flow is insufficient, skipping to a standard charging flow; if the available flow is used up, judging whether a new cumulative record exists, if so, repeating the step 4, otherwise, skipping to the standard charging process; if the available flow is sufficient, skipping to the step 5;

and 5: accumulating the current call ticket flow to a Memory Database (MDB), judging whether the flow accumulated in the Memory Database (MDB) reaches a list cutting threshold value, if so, generating a charging call ticket, and skipping to a standard charging flow, otherwise, skipping to the step 1.

In summary, due to the adoption of the technical scheme, the invention has the beneficial effects that:

the invention adopts the charging gateway to combine the invalid call tickets, optimizes the flow call ticket processing on the premise of keeping the logic and the flow of the existing system, combines the fragmentary call tickets in the package, simplifies the analysis and the pricing flow of most GPRS call tickets, and greatly reduces the input amount of the call tickets; saving storage investment: by combining invalid call tickets, the investment of call ticket storage equipment can be saved by more than 50%.

Drawings

In order to more clearly illustrate the technical solutions of the embodiments of the present invention, the drawings needed to be used in the embodiments will be briefly described below, it should be understood that the following drawings only illustrate some embodiments of the present invention and therefore should not be considered as limiting the scope, and for those skilled in the art, other related drawings can be obtained according to the drawings without inventive efforts.

FIG. 1 is a system architecture diagram of the present invention;

FIG. 2 is a system flow diagram of the present invention;

fig. 3 is a flow chart of the service charging gateway working process of the present invention.

Detailed Description

In order to make the objects, technical solutions and advantages of the present invention more apparent, the present invention is described in further detail below with reference to the accompanying drawings and embodiments. It should be understood that the detailed description and specific examples, while indicating the preferred embodiment of the invention, are intended for purposes of illustration only and are not intended to limit the scope of the invention.

The components of embodiments of the present invention generally described and illustrated in the figures herein may be arranged and designed in a wide variety of different configurations.

Thus, the following detailed description of the embodiments of the present invention, presented in the figures, is not intended to limit the scope of the invention, as claimed, but is merely representative of selected embodiments of the invention. All other embodiments, which can be derived by a person skilled in the art from the embodiments of the present invention without making any creative effort, shall fall within the protection scope of the present invention.

It is noted that relational terms such as "first" and "second," and the like, may be used solely to distinguish one entity or action from another entity or action without necessarily requiring or implying any actual such relationship or order between such entities or actions. Also, the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising an … …" does not exclude the presence of other identical elements in a process, method, article, or apparatus that comprises the element.

The features and properties of the present invention are described in further detail below with reference to examples.

Example 1

The embodiment provides a single ticket total traffic control system, which comprises

The Business Charging Gateway (BCG) is used for matching the accumulated records according to the original ticket information and carrying out merging, filtering and management on the conversation ticket; the method specifically comprises the following steps: and matching the accumulated records in the charging gateway according to the decoded original ticket information, wherein the two dimensions comprise global accumulated analysis and user-level accumulated analysis. The global accumulative analysis is to filter specific call ticket elements in call tickets, such as a 0 flow call ticket, a VOLTE flow call ticket and the like; the user-level cumulative analysis is a process of matching the current call ticket element of the user with the cumulative record stored in the charging gateway. The Business Charging Gateway (BCG) comprises a specific element filtering module, a user level filtering module, a combined key value generating module, a combined key value comparing module, a ticket popping module, a flow accumulating module and a ticket cutting threshold value module;

the specific element filtering module is used for filtering the call ticket with the specific element; the specific element filtering rule is configured in the LUA template. After filtering the specific elements, the method can be divided into three charging strategies:

a) some specific RGs, such as VOLTE traffic tickets, content charging exemption (Internet of vehicles) tickets, and 0 traffic tickets, are directly made into E5001 wrong tickets;

b) for some services, there is greater risk control, such as international roaming, or the flow value of a single ticket per se is already higher, such as video services, a strategy of directly walking a standard charging flow can be adopted, and cumulative charging is not carried out;

c) for most other call tickets, further user filtering is needed;

the user-level filtering module is used for filtering users without the function of accumulated flow rate; the user-level filtering rules support configuration by three dimensions of numbers, number segments and cities, and when the filtering is performed in the number and number segment mode, a maximum matching principle is adopted.

The combined key value generating module is used for generating the combined key value in the original call ticket; any field with a value in the original ticket can be used as a combined key value of the merge _ key. The merging key value is composed of field elements and is configured in a system parameter mode. In this embodiment, user _ number, ggsn _ address, charging _ id, and service _ code are used as merging key values. The Usernumber needs to be numbered regularly, and 86 starts are removed; and the user number and the RG are configured forcibly, and call tickets of different users and different RGs are not allowed to be combined. The merge _ key is generated by BCG uniformly and transmitted to MRG through SDL, thus avoiding asynchronous configuration of BCG and MRG, and realizing the call bill combination of services such as one card with multiple numbers and the like.

the call ticket popping module is used for popping up the call ticket;

the flow accumulation module is used for accumulating the flow; and when the call tickets are accumulated, after the BCG generates a combination key value, matching the combination records in the MRM MDB according to the merge _ key, wherein the step comprises four steps of MDB query, MDB return information processing, MDB update and original call ticket processing.

The MDB query is: the BCG client reads in the ticket and sends key information such as duration, calling mode, timestamp and the like to the MDB.

The MDB return information processing comprises the following steps: after receiving the information, the MDB server matches the merged record stored in the MDB: if the matching is unsuccessful, returning a failure mark, and sending the call bill to service analysis processing by the BCG; if the matching is successful, judging whether the combined record in the MDB is an initial record, if the combined record in the MDB is empty, returning to the mark for the first use, and if the combined record in the MDB is combined and the current ticket flow is added, and the current ticket flow does not reach the cut-to-order valve value, returning to the combination and not popping up the mark; if the combined records in the MDB are combined and the current call ticket flow is added, the call ticket reaches the cut-to-order threshold value, the combination is returned and the mark is popped up; finally, the MDB server returns the ret _ flag to the BCG client;

the MDB is updated as: the BCG client receives a return flag ret _ flag of the MDB server, and updates the MDB according to the return flag; when the return mark is used for the first time, the information of the current call ticket of the starting time, the flow, the duration and the CDR-TEXT in the combined record needs to be updated, and the current call ticket is processed by mistake; when the return mark is closed and does not pop up, only updating the flow and duration information in the combined record, and performing the current ticket billing processing in an error way; when the return mark is closed and popped up, the SEQ, the flow + the current flow, the duration + the current duration, the starting time, the CDR _ TEXT and the ending time of the current ticket in the combined record need to be extracted, a charging-substituting ticket is popped up, meanwhile, the flow, the duration and the starting time in the combined record are updated to be in an initial state, the SEQ is updated to be a new SEQ, and the current ticket is subjected to ticket-making mistake.

And the list switching threshold module is used for judging whether the accumulated flow reaches a list switching threshold, wherein the list switching threshold comprises a flow threshold and a duration threshold, and is used for judging whether the call bill needs to be popped up when the BCG carries out call bill combination. The unit of the cut-to-order threshold and the quota threshold is M, and when the program is processed internally, the M is converted into Byte so as to keep the accumulated flow unit consistent with the original call ticket unit. The configuration table is as follows: rs _ sys _ quota _ def; the flow threshold is as follows: bcg _ merge _ slice; the duration threshold is: bcg _ merge _ time.

A charging gateway data generator (MRG) for generating said cumulative record; the MRG generates an accumulated record which can be used for analyzing and using the charging gateway through the analysis of the bill after rating, and aims to analyze the product ordering condition of the user into information which needs to be referred when the GPRS bill is rated and persist. The method has the significance that the low-frequency operation is adopted to replace the prior method that each ticket is subjected to complete data and charge analysis, so that the analysis and calculation efficiency of the total ticket is greatly improved

The billing gateway data generator (MRG) comprises a ticket element analysis module, a product filtering module, a quota calculation module and an information assembly module;

the ticket element analysis module is used for analyzing elements in the ticket; and analyzing the use _ gateway field in the SDL and extracting merge _ key information, wherein the two fields are assigned by the BCG module.

The product filtering module is used for filtering products which are not suitable for the flow accumulation function; the product filtering is to match a product filtering rule table according to an effective product list in the SDL, and the main purposes are as follows: firstly, the method is used as a control means of the charging gateway function opening range; after the charging gateway function is started, the users can be limited to start the charging gateway through the filtering rules of the product, and only the user ordering the corresponding product makes the call ticket combination judgment. Such as: unlimited package users. And secondly, complex products of the young people are removed, and the charging accuracy is ensured, namely the logic basis of the charging gateway is ensured. For example: the user ordered 2 products, a being domestic 1G traffic and B being cell 10G traffic. When user _ number, ggsn _ address, charging _ id and service _ code are used as merging key values, cell information is lost, the batch price of a B product cannot be used correctly, and users who order the B product need to be removed and call tickets are not merged aiming at the scene.

The quota calculation module is used for storing a quota as a judgment basis for generating the cumulative record; the use condition of free resources (available traffic) in the MRG analysis ticket (in this embodiment, the quota is 50M as an example); generating a merged record when 50% + 50M-100% of the interval remains; when the interval of 50% -50% +50M is left, no merged record is generated; generating a merged record when 20% + 50M-50% of the interval remains; when the interval of 20% -20% +50M is left, no merged record is generated; when the interval of 0% + 50M-20% remains, generating a merged record; and when the interval of 0% -0% +50M remains, no combined record is generated, and the combined call ticket is popped up. After the merged record is generated, the quota information itself is not updated when the call tickets are accumulated, and is not used as a threshold value of the ticket cutting, but only as a judgment basis for whether the merged record can be generated or not.

The information assembly module is used for generating a final accumulated record; the cumulative record is one or more records stored in the newly-built cumulative MDB, and no cumulative record exists at the beginning of the accounting period. After the MRG analyzes the call ticket elements, filters the products and calculates the quota, the MRG assembles the combined records to be generated and sends the combined records to the MRM MDB.

A combining rule management module (MRM) for managing the combining rule of the call tickets and caching the accumulated records into a Memory Database (MDB); and providing query updating and event notification services for the MRG and the BCG, and combining the ticket information to include dynamic recording information and static recording information.

A Memory Database (MDB) for storing the cumulative record;

the system management module is used for BCG starting strategy planning and configuration, and switching user level, scene level and charging element flow. The accumulated charging mode of whether the gateway is applicable or not can be switched through a switch at a system level; the switching on and off of the user level and the scene level is automatically controlled by the billing gateway. The user-level switch is automatically judged based on the user number, the city information and the product ordering condition; the scene level switch is automatically switched according to the use condition of free resources of users on the basis of the user level switch.

The user level switch is used for determining whether the user can accumulate or not by analyzing the user filtering rule and the product filtering rule under the condition that the charging gateway is started. When the user-level switch is turned on, the charging gateway can converse the list to use the analysis flow of accumulated charging; when the user-level switch is closed, the charging gateway can directly transfer the call ticket to the service analysis for standard charging process treatment; the user level switches are generated or updated by the MRG.

The scene level switch is automatically switched by whether to generate an accumulated record or not according to the use condition of free resources of a user on the basis of the user level switch. After the bill pricing, the MRG judges the use condition of the free resources; taking quota 50M as an example, opening when 50% + 50M-100% interval remains; closing when the interval of 50% -50% +50M remains; opening when the rest 20% + 50M-50% interval is reached; closing when the interval of 20-20% +50M remains; opening when the interval of 0% + 50M-20% remains; and closing the switch when the interval of 0% -0% +50M remains.

Example 2

The embodiment provides a method for controlling the total traffic of a single ticket based on embodiment 1, which includes the following steps:

In the embodiment, the user orders the 1G domestic flow product A and the 2G domestic flow product B, and the A is preferentially used. The quota is 100M, the singulation threshold is 20M, and the singulation time duration is 2 hours.

When the first call ticket (the size is 1M, the duration is 10MIN) is generated in the month, the BCG can not be matched with the accumulated records in the MDB, so that the business analysis and the rating can be directly carried out, and then the MRG analyzes the rating information to generate the combined record in the MRM MDB. At this time, SEQ in the merged record is 1, the start time is null, the flow and the duration are both 0, and CDR _ TEXT is a default value;

when a second ticket (the size is 2M, the duration is 5MIN) is generated, the BCG updates the flow in the MDB to be 2M, the duration to be 5MIN, the starting time to be the starting time T2 of the second ticket, and CDR _ TEXT is updated to be the information of the second ticket;

when a third ticket (the size is 10M and the duration is 5MIN) is generated, the BCG updates the flow to 12M and the duration is 10 MIN;

when the fourth ticket (the size is 10M, the duration is 10MIN), the BCG pops up the ticket because 12+10 is larger than the ticket-cutting threshold value 20. The starting time of the pop-up ticket is T2, the ending time is T4, the flow is 12+ 10-22M, the duration is 10+ 10-20 MIN, and CDR _ TEXT is the information of the second ticket. Meanwhile, SEQ ═ 2 in the merged record is updated, the start time is empty, and the flow duration is 0.

And the popped charging bill is directly sent to service analysis and rating to complete charging, the MRG acquires rating bill information, recalculates quota and confirms whether the combined record in the MDB is available. If the quota is not enough, triggering to pop up the ticket.

And circulating in sequence until the quota is insufficient, and no merging record is generated.

The product A is free of charge and resources are exhausted.

And (4) generating a new call bill, using the product batch price B, and repeating the process.

The above description is only for the purpose of illustrating the preferred embodiments of the present invention and is not to be construed as limiting the invention, and any modifications, equivalents and improvements made within the spirit and principle of the present invention are intended to be included within the scope of the present invention.

Claims

1. A single ticket total traffic control system is characterized in that: comprises that

a charging gateway data generator (MRG) for generating said cumulative record;

a Memory Database (MDB) for storing the cumulative record;

2. The system for controlling the total traffic of a single ticket according to claim 1, wherein: the service charging gateway (BCG) includes: the system comprises a specific element filtering module, a user level filtering module, a combined key value generating module, a combined key value comparing module, a ticket popping module, a flow accumulating module and a ticket cutting threshold module;

the call ticket popping module is used for popping up the call ticket;

the flow accumulation module is used for accumulating the flow;

3. The system for controlling the total traffic of a single ticket according to claim 1, wherein: the charging gateway data generator (MRG) comprises: the system comprises a ticket element analysis module, a product filtering module, a quota calculation module and an information assembly module;

4. The method for controlling the total traffic of a single ticket based on claim 1 is characterized in that: the method comprises the following steps: