Call record triggering control method, device and electronic equipment

Abstract

The present application discloses a call bill trigger control method, device and electronic device. The method includes: obtaining the current call bill record of the target object; extracting target information from the call bill record, wherein the target information includes: the service flow usage information and the busyness of the service flow corresponding to the call bill record; determining the target call bill trigger rule of the target object based on the target information, and sending the target call bill trigger rule to the billing trigger function entity, wherein the target call bill trigger rule is used to adjust the next trigger condition of the billing trigger function entity and the service flow usage information in the target call bill. The present application solves the business problem that the prior art is prone to generate large-volume and long-duration call bills when reducing fragmented call bills, which cause user complaints, and there is a technical problem that the timeliness of signal control is poor.

Description

Technical Field

[0001] The present application relates to the field of billing management, and more specifically, to a call bill triggering control method, device and electronic equipment. Background Art

[0002] With the development of telecommunications mobile traffic services and the application of deep message analysis technology, different business flows can be identified for differentiated billing, resulting in a surge in call bills, which has a continuous increase trend with the evolution of deep message analysis functions, causing the billing system to spend a lot of resources to process small-flow fragmented call bills. Such call bills are of low value and account for more than half of the total, so technical means are needed to suppress the generation of such call bills. The related technology has the business problem of easily generating large-flow and long-duration call bills when reducing fragmented call bills, which causes user complaints, and there is also a technical problem of poor timeliness of signal control. In response to the above problems, no effective solution has been proposed so far. Summary of the invention

[0003] The embodiments of the present application provide a call bill trigger control method, device and electronic device to at least solve the technical problem that the existing call bill trigger control technology is unable to reduce the triggering of fragmented call bills while avoiding suppressing the excessive generation of large call bills that lead to user complaints.

[0004] According to one aspect of an embodiment of the present application, a call bill trigger control method is provided, including: obtaining a current call bill record of a target object; extracting target information from the call bill record, wherein the target information includes: service flow usage information and the busyness of the service flow corresponding to the call bill record; determining a target call bill trigger rule for the target object based on the target information, and sending the target call bill trigger rule to a billing trigger function entity, wherein the target call bill trigger rule is used to adjust the next trigger condition of the billing trigger function entity and the service flow usage information in the target call bill.

[0005] Optionally, determining the target call bill triggering rules of the target object based on the target information includes: determining the type of idle-busy degree of the business flow, wherein the types include: idle-time triggering type and busy-time triggering type; determining the target call bill triggering rules based on the type of idle-busy degree of the business flow and the business flow usage information.

[0006] Optionally, the target call record triggering rule is determined based on the type of the service flow's busy or idle degree and the service flow usage information, including: when the type of the service flow's busy or idle degree is an idle-time trigger type, the target call record triggering rule is determined to increase the service flow's duration usage threshold and reduce the service flow threshold of the target call record; when the type of the service flow's busy or idle degree is a busy-time trigger type, the target call record triggering rule is determined to reduce the service flow's duration usage threshold and increase the service flow threshold of the target call record.

[0007] Optionally, the off-peak trigger type includes: the duration usage of the service flow corresponding to the call record is greater than or equal to a first reference value, and the traffic usage corresponding to the call record is less than a second reference value; the busy trigger type includes: the duration usage of the service flow corresponding to the call record is less than a third reference value, and the traffic usage corresponding to the call record is greater than or equal to a fourth reference value.

[0008] Optionally, the service flow usage information corresponding to the call bill record includes at least one of the following: duration usage and traffic usage of the service flow.

[0009] Optionally, sending the target call record trigger rule to the billing trigger function entity includes: determining the field information corresponding to the target call record trigger rule, wherein the field information is the field in the context information; replacing the content in the field information with the target call record trigger rule, and sending the replaced context information to the billing trigger function entity.

[0010] Optionally, the field information includes: result table fields in the context information.

[0011] According to another aspect of an embodiment of the present application, a call bill trigger control device is also provided, including: an acquisition module, used to obtain the current call bill record of the target object; an extraction module, used to extract target information from the call bill record, wherein the target information includes: the service flow usage information and the busyness of the service flow corresponding to the call bill record; a determination module, used to determine the target call bill trigger rule of the target object based on the target information; a sending module, used to send the target call bill trigger rule to the billing trigger function entity, wherein the target call bill trigger rule is used to adjust the next trigger condition of the billing trigger function entity and the service flow usage information in the target call bill.

[0012] According to another aspect of an embodiment of the present application, a non-volatile storage medium is also provided, which includes a stored program, wherein when the program is running, the device where the non-volatile storage medium is located is controlled to execute the above-mentioned call record triggering control method.

[0013] According to another aspect of an embodiment of the present application, there is also provided an electronic device, comprising: a processor; a memory for storing processor executable instructions; wherein the processor is configured to execute instructions to implement the above-mentioned call record triggering control method.

[0014] In an embodiment of the present application, by obtaining the current call record of the target object; extracting target information from the call record, wherein the target information includes: the service flow usage information and the busyness of the service flow corresponding to the call record; determining the target call record trigger rule of the target object based on the target information, and sending the target call record trigger rule to the billing trigger function entity, the purpose of adjusting the next trigger condition of the billing trigger function entity and the service flow usage information in the target call record according to the target call record trigger rule is achieved, thereby achieving the technical effect of reducing the triggering of fragmented call records, and further solving the technical problems that the prior art is prone to generate large-volume and long-duration call records when reducing fragmented call records, causing user disputes, and has poor timeliness of signal control. BRIEF DESCRIPTION OF THE DRAWINGS

[0015] The drawings described herein are used to provide a further understanding of the present application and constitute a part of the present application. The illustrative embodiments of the present application and their descriptions are used to explain the present application and do not constitute an improper limitation on the present application. In the drawings:

[0016] Figure 1 It is a hardware structure block diagram of a computer terminal (or electronic device) for implementing a call bill trigger control method according to an embodiment of the present application;

[0017] Figure 2 is a flow chart of a call record triggering control method according to an embodiment of the present application;

[0018] Figure 3 It is a flow chart of determining a target trigger rule according to the type of trigger reason and service flow usage information according to an embodiment of the present application;

[0019] Figure 4 It is a flow chart of sending a target call list trigger rule to a charging trigger function entity according to an embodiment of the present application;

[0020] Figure 5 is a billing request flow chart according to an embodiment of the present application;

[0021] Figure 6 It is a structural diagram of a call record triggering control device according to an embodiment of the present application. DETAILED DESCRIPTION

[0022] In order to enable those skilled in the art to better understand the solution of the present application, the technical solution in the embodiments of the present application will be clearly and completely described below in conjunction with the drawings in the embodiments of the present application. Obviously, the described embodiments are only part of the embodiments of the present application, not all of the embodiments. Based on the embodiments in the present application, all other embodiments obtained by ordinary technicians in this field without creative work should fall within the scope of protection of the present application.

[0023] It should be noted that the terms "first", "second", etc. in the specification and claims of the present application and the above-mentioned drawings are used to distinguish similar objects, and are not necessarily used to describe a specific order or sequence. It should be understood that the data used in this way can be interchangeable where appropriate, so that the embodiments of the present application described herein can be implemented in an order other than those illustrated or described herein. In addition, the terms "including" and "having" and any of their variations are intended to cover non-exclusive inclusions, for example, a process, method, system, product or device comprising a series of steps or units is not necessarily limited to those steps or units clearly listed, but may include other steps or units that are not clearly listed or inherent to these processes, methods, products or devices.

[0024] First, some nouns or terms that appear in the description of the embodiments of the present application are subject to the following explanations:

[0025] 5GC: 5G core, namely 5G core network.

[0026] Billing Domain: The area responsible for fee calculation, user accounts, traffic settlement and other business processing.

[0027] CHF: Charging Function, deployed at the boundary between 5GC and the charging domain, integrates online charging (OCS) and offline charging (OFCS) functions through the N40 interface, and provides interactive implementations such as trigger rule issuance, authorization quantity issuance, re-authorization triggering, and triggering service termination. CHF is responsible for generating accountable user call records for the charging domain.

[0028] CGF: Changing Gateway Function, that is, the charging gateway function, interacts with each network element in the core network through GTP protocol messages, and encodes the call record message content into a file and sends it to the charging domain. For the charging area, this type of call record file is an offline file, which is usually used for fault recovery, omission completion, traffic auditing, etc., and does not directly participate in user accounts, which is different from the billable call record generated by CHF.

[0029] SMF: Session Management Function, which is responsible for the lifecycle management of 5G user sessions, IP address allocation, data routing selection, business continuity management, policy rule matching, and traffic billing processing.

[0030] CTF: Charging Triggering Function, which is the client function of user usage reporting and authorization application implemented in each network element. CTF generates charging signaling messages according to the preset or trigger conditions issued by CCF, and reports the reasons for triggering the reporting. For the 5GC scenario, CTF is implemented as a submodule on SMF and interacts with CHF through the N40 interface.

[0031] CCF: Charging Control Funcation, that is, charging control function. The charging network element server function issues trigger rules and authorization amounts to CTF according to business needs, controls the trigger frequency of CTF and the conditions for reporting usage. For 5GC scenarios, CCF is a submodule on CHF to interact with SMF through the N40 interface.

[0032] GU: Granted Unit, i.e., authorized quantity. In the strict accounting online billing scenario, CCF sends it to CTF, indicating the usage quantity that the user cannot exceed before the next time CTF interacts with CCF for authorization quantity application.

[0033] UU: UsedUnit, i.e. usage, the amount of business incurred in the user's call log.

[0034] MU: measure unit, which is a unit used to measure the amount of user business. Common measurements in the billing domain are duration, traffic, and number of times. Standard measurement units in billing messages and call records include seconds, bytes, and times.

[0035] FBC: flow-based charging, that is, charging based on business flows. CTF identifies and tags (rating-group, service-id and other information elements are used to mark and identify business flows) different business flows on user sessions, distinguishes business flow usage reporting and performs authorization quantity control. CCF can issue separate trigger conditions for different business flows. Only when the usage of a business flow meets the conditions described by the trigger will CTF trigger the billing request message of this business flow to CCF.

[0036] SBC: session-based charging, that is, based on session charging, CTF does not distinguish between various service flows on the user device, and reports the amount of the entire session network session (there is only one default service flow). The trigger conditions issued by CCF are effective for the entire CTF billing session.

[0037] There are two technical solutions in the related art that can reduce call bills:

[0038] The first is the reverse calculation of charges. Prepaid users use online billing to query user static information and balance acceptance status, calculate the allowed authorization range, and then distinguish the rate groups according to a certain weight ratio and issue different authorization amounts to PGW / SMF network elements. This type of method is only applicable to online billing users (prepaid users). For offline billing (postpaid) and converged billing users, the actual use range of production is limited because the backend signal control implementation interface is not necessarily based on online messages. This type of method is mainly applicable to linear continuous function tariff packages for voice services. For traffic multi-dimensional multi-session conditional discontinuous function packages, the reverse calculated authorization amount may not be reasonable, which is easy to cause signal control problems and user complaints. The production system implementation has certain parameter adjustment and protection processing logic. The prepaid system based on reverse calculation of charges is complex to implement, and the online failure rate and complaint risk are higher than those of the traditional postpaid system, so the actual use range is relatively narrow.

[0039] The second is dynamic step size. After the converged billing CHF, there is a dynamic step size method, which uses big data to predict the user's usage and package situation to set the user's authorization amount and the step size parameters in the traffic duration trigger. This type of method requires the implementation of a real-time data warehouse and recommendation system to calculate the fee, and transmit it back to CHF through a certain mechanism, resulting in a lengthy call chain, low cost performance, high coupling between systems, strong fault propagation, and easy to cause conflicts between departments and management problems. Therefore, the actual implementation effect is generally to update the prediction results once a day and set a unique step size and authorization value for each user. This low-rate update cannot cope with the occasional situation of users, resulting in excessively high charges and the risk of complaints.

[0040] The actual effects of the above two technologies are often not as good as directly increasing the step parameters of the duration trigger or the fixed default parameters of the duration authorization amount and quota validity period. However, the adjustment range of the fixed default values ​​is limited, and each adjustment requires notifying the business department to explain the caliber for complaint prevention.

[0041] In order to simplify the control process of call record triggering frequency, eliminate the dependence on user information (package charges, balance credit, etc.) in the processing process, reduce the coupling between systems, and balance the contradiction between call record triggering conditions and signal control accuracy, suppress the triggering of fragmented call records, and provide a passive protection mechanism to avoid excessive suppression and lead to complaints from signal control sensitive users, the embodiment of the present application provides a corresponding solution, which is described in detail below.

[0042] The call bill trigger control method embodiment provided in the embodiment of the present application can be executed in a mobile terminal, a computer terminal or a similar computing device. Figure 1 The hardware structure block diagram of a computer terminal (or electronic device) for implementing a call bill trigger control method is shown. Figure 1As shown, the computer terminal 10 (or electronic device 10) may include one or more (102a, 102b, ..., 102n are used to illustrate) processors (the processor may include but is not limited to a processing device such as a microprocessor MCU or a programmable logic device FPGA), a memory 104 for storing data, and a transmission module 106 for communication functions. In addition, it may also include: a display, an input / output interface (I / O interface), a universal serial bus (USB) port (which may be included as one of the ports of the I / O interface), a network interface, a power supply and / or a camera. It can be understood by those skilled in the art that Figure 1 The structure shown is only for illustration and does not limit the structure of the above electronic device. Figure 1 More or fewer components as shown, or with Figure 1 Different configurations shown.

[0043] It should be noted that the one or more processors and / or other data processing circuits described above may generally be referred to herein as "data processing circuits". The data processing circuits may be embodied in whole or in part as software, hardware, firmware, or any other combination thereof. In addition, the data processing circuit may be a single independent processing module, or may be incorporated in whole or in part into any of the other components in the computer terminal 10 (or electronic device). As described in the embodiments of the present application, the data processing circuit acts as a processor control (e.g., selection of a variable resistor terminal path connected to an interface).

[0044] The memory 104 can be used to store software programs and modules of application software, such as the program instructions / data storage device corresponding to the call slip trigger control method in the embodiment of the present application. The processor executes various functional applications and data processing by running the software programs and modules stored in the memory 104, that is, the above-mentioned call slip trigger control method is realized. The memory 104 may include a high-speed random access memory, and may also include a non-volatile memory, such as one or more magnetic storage devices, flash memory, or other non-volatile solid-state memory. In some instances, the memory 104 may further include a memory remotely arranged relative to the processor, and these remote memories may be connected to the computer terminal 10 via a network. Examples of the above-mentioned network include, but are not limited to, the Internet, an intranet, a local area network, a mobile communication network, and combinations thereof.

[0045] The transmission module 106 is used to receive or send data via a network. The specific example of the above network may include a wireless network provided by a communication provider of the computer terminal 10. In one example, the transmission device 106 includes a network adapter (Network Interface Controller, NIC), which can be connected to other network devices through a base station so as to communicate with the Internet. In one example, the transmission device 106 can be a radio frequency (RF) module, which is used to communicate with the Internet wirelessly.

[0046] The display may be, for example, a touch screen liquid crystal display (LCD) that enables a user to interact with a user interface of the computer terminal 10 (or electronic device).

[0047] It should be noted that, in some optional embodiments, the above Figure 1 The computer device (or electronic device) shown may include hardware elements (including circuits), software elements (including computer code stored on a computer-readable medium), or a combination of hardware elements and software elements. It should be noted that Figure 1 This is merely one example of a particular embodiment and is intended to illustrate the types of components that may be present in the above-described computer device (or electronic device).

[0048] In the above-mentioned operating environment, an embodiment of the present application provides an embodiment of a call record triggering control method. It should be noted that the steps shown in the flowchart in the accompanying drawings can be executed in a computer system such as a set of computer executable instructions, and although the logical order is shown in the flowchart, in some cases, the steps shown or described can be executed in an order different from that shown here.

[0049] Figure 2 is a flow chart of a call record triggering control method according to an embodiment of the present application, such as Figure 2 As shown, the method comprises the following steps:

[0050] Step S202, obtaining the current call record of the target object;

[0051] Step S204, extracting target information from the call record, wherein the target information includes: service flow usage information and the idleness or busyness of the service flow corresponding to the call record;

[0052] Step S206, determine the target call record triggering rule of the target object based on the target information, and send the target call record triggering rule to the billing triggering function entity, wherein the target call record triggering rule is used to adjust the next triggering condition of the billing triggering function entity and the service flow usage information in the target call record.

[0053] Specifically, in the above steps S202 to S206, the call record triggering control method includes the following steps: S1: distinguish the rate group to obtain the call record in the current billing session message or file; S2: infer the usage of the service flow corresponding to each rate group according to the information element or field content in the call record; S2-1: the content of the call record in S2 should include the call record triggering reason and usage, and the triggering reason can refer to the idleness and busyness of the service flow; S2-2: the inference process in S2 can be implemented by a heuristic strategy, inputting the call record content and outputting the service flow usage; S3: according to the service flow usage output by S2, sending a trigger combination with an inhibitory protection effect to the CTF Update the trigger conditions of the corresponding business flow to achieve call record trigger frequency control; S3-1: The trigger combination with suppression protection in S3 needs to include at least one call record suppression trigger rule that can reduce the call record trigger frequency of the business flow when S2 infers a hit, and also needs to include a trigger rule with promotion effect that can increase the trigger frequency when S2 infers an error, and play a protective role in other trigger dimensions to avoid excessive suppression. A control loop is formed through two or more positive and negative feedbacks. The higher the hit rate of the heuristic strategy inference in S2-1, the more accurate the call record trigger frequency control, the more the call record cutting effect can reflect the actual usage status of the user's equipment, and reduce fragmented call records.

[0054] In step S206 of the above-mentioned call record triggering control method, the target call record triggering rule of the target object is determined according to the target information, such as Figure 3 The flowchart shown specifically includes the following steps:

[0055] Step S302, determining the type of the idle-busy degree of the service flow, wherein the type includes: an idle-time trigger type and a busy-time trigger type;

[0056] Step S304, determining a target call list triggering rule according to the type of the service flow's busy or idle degree and service flow usage information.

[0057] In the above step S304, the target call bill triggering rule is determined based on the type of the busyness of the business flow and the business flow usage information, which specifically includes the following steps: when the type of the busyness of the business flow is an idle time trigger type, the target call bill triggering rule is determined to increase the duration usage threshold of the business flow and reduce the business traffic threshold of the target call bill; when the type of the busyness of the business flow is a busy time trigger type, the target call bill triggering rule is determined to reduce the duration usage threshold of the business flow and increase the business traffic threshold of the target call bill.

[0058] By making the size of the service traffic and duration quota negatively correlated, combined with the feedback of the busyness of the service flow: when it is triggered during idle time, the quota is issued with increased duration and reduced traffic; when it is triggered during busy time, the quota is issued with increased traffic and reduced duration, so as to achieve the purpose of cutting call records in accordance with the user's usage behavior and reduce unnecessary performance resource overhead.

[0059] In the above-mentioned call record trigger control method, the off-peak trigger type includes: the duration usage of the service flow corresponding to the call record is greater than or equal to the first reference value, and the traffic usage corresponding to the call record is less than the second reference value; the busy trigger type includes: the duration usage of the service flow corresponding to the call record is less than the third reference value, and the traffic usage corresponding to the call record is greater than the fourth reference value.

[0060] Specifically, in the call record information of input service flow A, the duration usage T is greater than or equal to the duration usage upper limit delimiter value T high , the T high The first reference value is the traffic usage V, which is less than the lower limit of traffic usage V. low , the V low That is the second reference value. The heuristic strategy determines that the service flow A is in an idle state and outputs the inference result. The inference result is to send a trigger combination that has a suppressive protection effect on the service flow to CTF, update the trigger conditions of the corresponding service flow, and realize the call trigger frequency control. The inference result generates a trigger combination (R1, R2), and the duration step corresponding to R1 is set to K (K>1) times the default value T0, and the flow trigger step corresponding to R2 is set to 1 / K times the flow default value V0. If business flow A remains relatively idle within the next T0*K period (the generated traffic is less than V0 / K), CTF triggers the next call bill reporting of business flow A according to R1. This situation is regarded as a heuristic strategy speculation hit. Since the issued time step is greater than the fixed default value T0, the frequency of periodic fragmented call bills is reduced. If business flow A is relatively busy in the subsequent use and the traffic usage soon exceeds V0 / K, CTF will trigger the next call bill reporting of business flow A according to R2. This situation is regarded as a heuristic strategy speculation error. Since the triggered traffic step is less than the fixed default value V0, the suppression effect of R1 will not generate call bills with excessive traffic, affecting the accuracy of signal control and reducing the risk of user complaints.

[0061] When the duration usage T in the call record information of service flow B is less than the lower limit of duration usage T low , the T low The third reference value is the traffic usage V greater than or equal to the traffic usage upper limit delimiter V high , the V highThat is the fourth reference value. The heuristic strategy determines that business flow A is in a busy state and outputs the inference result. The inference result generates a trigger combination (R3, R4, R5). The duration step corresponding to R3 is set to 1 / K (K>1) times the default value T0, and the traffic trigger step corresponding to R4 is set to K times the default traffic value V0. R5 is a location change trigger. R4 increases the step size of the traffic trigger to reduce the frequency of triggering call bill reporting when business flow B is used at high speed, which has an inhibitory effect. At the same time, R3 and R5 set protection boundaries in the time dimension and space dimension respectively. If the geographical location of the device remains unchanged, because the duration step size set by R3 is less than the default value T0, R3 can increase the trigger frequency in the time dimension to increase the sensitivity of credit. When the location of the device changes when it is busy, R5 triggers the call bill reporting, which improves the accuracy of call bill cutting in the spatial dimension and avoids tariff disputes.

[0062] Optionally, when the service flow C call record information, duration usage T, traffic usage V, is entered, under the condition NOT (T> = T high AND V <V low O R T <T low AND V>=V high ) is satisfied, the heuristic strategy determines that the service flow C is in the intermediate state of not busy and not limited, and outputs the inference result. The inference result generates a trigger combination (R6, R7), R6 corresponding to the flow trigger step is set to the flow default value V0, R7 corresponding to the duration step is set to the default value T0, at this time, it is equivalent to neither inhibition nor protection, so that the control loop formed by CTF and CCF is restored to the initial state.

[0063] It should be noted that in the embodiment of the present application, "step size" in the 3GPP protocol refers to volumeLimit and timeLimit in the postpaid mode (offline charging), and refers to GrantedUnit.time and GrantedUnit.totalVolume in the prepaid mode (online charging).

[0064] In the above-mentioned call record triggering control method, the service flow usage information corresponding to the call record includes at least one of the following: the duration usage and traffic usage of the service flow.

[0065] In step S206 of the above-mentioned call bill triggering control method, the target call bill triggering rule is sent to the charging triggering function entity, such as Figure 4 The flowchart shown specifically includes the following steps:

[0066] Step S402, determining the field information corresponding to the target call record triggering rule, wherein the field information is the field in the context information;

[0067] Step S404: replace the content in the field information with the target call record trigger rule, and send the replaced context information to the charging trigger function entity.

[0068] In the above-mentioned call record triggering control method, the field information includes: the result table field in the context information.

[0069] The call bill trigger control method provided in the embodiment of the present application can be applied to a billing signaling suppression application framework, which has a built-in default strategy: the traffic sent by CCF to CTF is negatively correlated with the duration quota (authorized quantity), thereby preventing CTF from generating overly large or fragmented call bills while maintaining the accuracy and economy of call bill cutting.

[0070] The call slip trigger control method provided in the embodiment of the present application can also be applied to a heuristic strategy execution framework, which executes the default strategy (the default strategy must be the first one to be executed and output) plus 0 or more heuristic strategies in sequence in a pipeline manner. The output results of the strategies executed later overwrite the output results of the previous strategies until the last one is executed as the final output, which is used for new strategy effect evaluation, data sampling, grayscale release, compatibility with old system transformation, and DevOps-related live network tuning scenarios to avoid network shock after going online due to excessive differences in the effects of new and old strategies.

[0071] like Figure 5 As shown in the billing request flow chart, CTF initiates a billing request to CCF, and CCF forwards the billing request and the triggering reason of the request to the heuristic signaling suppression policy application framework, which analyzes and deduces according to the built-in heuristic policy, and sends the parameters of the new round of triggers to CCF. After receiving the parameters, CCF sends the billing response message containing the new trigger to CTF. After updating the trigger parameters, if CTF receives a new trigger condition, it initiates a billing request to CCF again, and CCF sends the second billing request and the triggering reason to the heuristic signaling suppression policy application framework for analysis and deduction.

[0072] The design idea of ​​the call bill trigger control method provided in the embodiment of the present application is as follows: In practice, operators mainly use traffic billing and rarely use duration as a billing dimension, so controlling the size of reported traffic has a more important impact on the accuracy of signal control and reminders. If the user uses the traffic quickly, the time interval between triggering is short. If the user is stationary and dormant, the triggered traffic is very small, resulting in fragmented call bills. The user's current usage can be guessed based on the information reported by CTF. If a certain business flow is triggered by TIME_LIMIT or TimeQuotaThreshold, it is considered that the business flow is very idle, and the corresponding suppression trigger is issued to increase the reporting interval of the business flow while reducing the trigger traffic of the call bill, so as to achieve the effect of trigger fitting user behavior and reduce the call bill without affecting the accuracy of signal control.

[0073] The call record trigger control method provided in the embodiment of the present application can solve the long-standing problem of fragmented call records in the billing domain, fully consider practical factors such as the compatibility of the peer system behavior and the cost of transforming the old system, and provide a set of default policy implementation standards and parameter adjustment suggestions that have been tested in the existing network practice, so as to achieve the purpose of saving system capacity while ensuring the accuracy of billing signal control, and minimize the risk of cutover and online launch.

[0074] The call bill trigger control method provided in the embodiment of the present application is that "speculation + protection" produces a chemical reaction. In the presence of a trigger combination with a protective effect, the accuracy requirements of the speculation method can be greatly reduced. Due to the existence of the protection mechanism, the original complaint risk of unreasonable call bill cutting caused by a few prediction errors is transferred to the difference in the global call bill suppression effect. The higher the hit rate of the speculation result, the better the suppression effect. Even if the impact caused by inaccurate speculation is that the suppression effect is not good, it will not lead to the risk of complaints about unreasonable call bill cutting. The internal principle is similar to spread spectrum communication to avoid interference signals in a single frequency band. Therefore, the implementation process of this invention is very safe and not easy to cause user complaints. In the case of reduced requirements for the accuracy of the speculation method, in a complex and variable current network environment, the speculation algorithm can be easily and flexibly adjusted. A very simple heuristic strategy can be used for speculation implementation to achieve a good suppression effect while being compatible with different network element CTFs.

[0075] The call slip trigger control method provided in the embodiment of the present application requires the output of the judgment of the idle and busy status in the speculation, and sends trigger combination rules of different dimensions according to the idle and busy conditions, so that CTF and CCF (collectively referred to as CDF / CDF / CHF) form an adaptive control loop with negative feedback suppression and positive feedback protection, which is similar to an automatic transmission of a car that automatically changes gears according to driving conditions.

[0076] The call record trigger control method provided in the embodiment of the present application has the following advantages: 1. The development and operation are simple and the implementation process is relatively safe. The characteristics of the call record cutting results are obvious and highly interpretable, and it is not easy to cause users to dispute the list query results; 2. The suppression effect is controllable. Under the trigger combination with suppression protection, the requirements for the accuracy of the inference algorithm are greatly reduced. The inference algorithm can be flexibly adjusted according to the actual situation of the existing network, which is convenient for compatibility with different network element products (CTF), especially for the common network elements with non-standard implementation, incomplete functions, and incorrect configuration, which greatly improves the scope of application and practicality of this method.

[0077] Figure 6 is a structural diagram of a call bill triggering control device according to an embodiment of the present application, such as Figure 6 As shown, the device comprises:

[0078] The acquisition module 602 is used to acquire the current call record of the target object;

[0079] Extraction module 604, used to extract target information from the call record, wherein the target information includes: service flow usage information and service flow busyness corresponding to the call record;

[0080] A determination module 606, configured to determine a target call list triggering rule of a target object according to the target information;

[0081] The sending module 608 is used to send the target call bill trigger rule to the charging trigger function entity, wherein the target call bill trigger rule is used to adjust the next trigger condition and service flow usage information of the charging trigger function entity.

[0082] In the determination module in the above-mentioned call record trigger control device, the determination module is used to determine the type of idle or busy degree of the business flow, wherein the types include: idle time trigger type and busy time trigger type; and determine the target call record trigger rule based on the type of idle or busy degree of the business flow and the business flow usage information.

[0083] In the determination module in the above-mentioned call record trigger control device, the target call record trigger rule is determined based on the type of the busyness of the business flow and the business flow usage information, which specifically includes the following processes: when the type of the busyness of the business flow is an idle time trigger type, the target call record trigger rule is determined to increase the duration usage threshold of the business flow and reduce the business traffic threshold of the target call record; when the type of the busyness of the business flow is a busy time trigger type, the target call record trigger rule is determined to reduce the duration usage threshold of the business flow and increase the business traffic threshold of the target call record.

[0084] In the above-mentioned call record trigger control device, the off-peak trigger type includes: the duration usage of the service flow corresponding to the call record is greater than or equal to the first reference value, and the traffic usage corresponding to the call record is less than the second reference value; the busy trigger type includes: the duration usage of the service flow corresponding to the call record is less than the third reference value, and the traffic usage corresponding to the call record is greater than the fourth reference value.

[0085] In the above-mentioned call bill triggering control device, the service flow usage information corresponding to the call bill record includes at least one of the following: the duration usage and traffic usage of the service flow.

[0086] In the sending module in the above-mentioned call record trigger control device, the target call record trigger rule is sent to the billing trigger function entity, which specifically includes the following process: determining the field information corresponding to the target call record trigger rule, wherein the field information is the field in the context information; replacing the content in the field information with the target call record trigger rule, and sending the replaced context information to the billing trigger function entity.

[0087] In the above-mentioned call record triggering control device, the field information includes: the result table field in the context information.

[0088] It should be noted that Figure 6 The call slip trigger control device shown is used to execute Figure 2 The call record trigger control method shown, therefore the relevant explanations in the above call record trigger control method are also applicable to the call record trigger control device, and will not be repeated here.

[0089] An embodiment of the present application also provides a non-volatile storage medium, which includes a stored program, wherein when the program is running, the device where the non-volatile storage medium is located is controlled to execute the following call bill trigger control method: obtain the current call bill record of the target object; extract target information from the call bill record, wherein the target information includes: the service flow usage information and the busyness of the service flow corresponding to the call bill record; determine the target call bill trigger rule of the target object based on the target information, and send the target call bill trigger rule to the billing trigger function entity, wherein the target call bill trigger rule is used to adjust the next trigger condition of the billing trigger function entity and the service flow usage information in the target call bill.

[0090] The serial numbers of the above-mentioned embodiments of the present application are for description only and do not represent the advantages or disadvantages of the embodiments.

[0091] In the above embodiments of the present application, the description of each embodiment has its own emphasis. For parts that are not described in detail in a certain embodiment, please refer to the relevant description of other embodiments.

[0092] In the several embodiments provided in this application, it should be understood that the disclosed technical content can be implemented in other ways. Among them, the device embodiments described above are only schematic. For example, the division of the units can be a logical function division. There may be other division methods in actual implementation. For example, multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be through some interfaces, indirect coupling or communication connection of units or modules, which can be electrical or other forms.

[0093] The units described as separate components may or may not be physically separated, and the components shown as units may or may not be physical units, that is, they may be located in one place or distributed on multiple units. Some or all of the units may be selected according to actual needs to achieve the purpose of the present embodiment.

[0094] In addition, each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit. The above-mentioned integrated unit may be implemented in the form of hardware or in the form of software functional units.

[0095] If the integrated unit is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present application, in essence, or the part that contributes to the prior art or all or part of the technical solution can be embodied in the form of a software product, and the computer software product is stored in a storage medium, including a number of instructions to enable a computer device (which can be a personal computer, a server or a network device, etc.) to perform all or part of the steps of the method described in each embodiment of the present application. The aforementioned storage medium includes: U disk, read-only memory (ROM, Read-Only Memory), random access memory (RAM, Random Access Memory), mobile hard disk, disk or optical disk and other media that can store program codes.

[0096] The above is only a preferred implementation of the present application. It should be pointed out that for ordinary technicians in this technical field, several improvements and modifications can be made without departing from the principles of the present application. These improvements and modifications should also be regarded as the scope of protection of the present application.

Claims

1. A call record trigger control method, characterized in that: include: Get the current call record of the target object; Extracting target information from the call record, wherein the target information includes: service flow usage information and service flow busyness corresponding to the call record; Determine a target call list trigger rule of the target object according to the target information, and send the target call list trigger rule to the billing trigger function entity, wherein the target call list trigger rule is used to adjust the next trigger condition of the billing trigger function entity and the service flow usage information in the target call list; The target call bill triggering rule is determined based on the type of the idle-busy degree of the business flow and the business flow usage information, including: when the type of the idle-busy degree of the business flow is an idle-time trigger type, the target call bill triggering rule is determined to increase the duration usage threshold of the business flow and reduce the business traffic threshold of the target call bill; when the type of the idle-busy degree of the business flow is a busy-time trigger type, the target call bill triggering rule is determined to reduce the duration usage threshold of the business flow and increase the business traffic threshold of the target call bill.

2. The method according to claim 1, characterized in that Determining a target call record triggering rule of the target object according to the target information includes: Determine the type of the idle-busy degree of the service flow, wherein the type includes: an idle-time trigger type and a busy-time trigger type; The target call list triggering rule is determined according to the type of the busyness or idleness of the service flow and the service flow usage information.

3. The method according to claim 1, characterized in that The off-peak trigger type includes: the duration usage of the service flow corresponding to the call record is greater than or equal to the first reference value, and the traffic usage corresponding to the call record is less than the second reference value; the busy trigger type includes: the duration usage of the service flow corresponding to the call record is less than the third reference value, and the traffic usage corresponding to the call record is greater than or equal to the fourth reference value.

4. The method according to claim 3, characterized in that The service flow usage information corresponding to the call bill record includes at least one of the following: the duration usage of the service flow and the traffic usage.

5. The method according to claim 1, characterized in that Sending the target call record trigger rule to the charging trigger function entity includes: Determine the field information corresponding to the target call record trigger rule, wherein the field information is a field in the context information; The content in the field information is replaced with the target call record trigger rule, and the replaced context information is sent to the charging trigger function entity.

6. The method according to claim 5, characterized in that The field information includes: the result table fields in the context information.

7. A call record trigger control device, characterized in that: include: The acquisition module is used to obtain the current call record of the target object; An extraction module, used to extract target information from the call record, wherein the target information includes: service flow usage information and service flow idleness and busyness corresponding to the call record; A determination module, used to determine a target call list triggering rule of the target object according to the target information; A sending module, used for sending the target call list triggering rule to the charging triggering function entity, wherein the target call list triggering rule is used to adjust the triggering condition of the charging triggering function entity and the service flow usage information in the target call list; The determination module is also used to determine the target call bill triggering rule based on the type of the idle-busy degree of the business flow and the business flow usage information, including: when the type of the idle-busy degree of the business flow is an idle-time trigger type, determining the target call bill triggering rule to increase the duration usage threshold of the business flow and reduce the business traffic threshold of the target call bill; when the type of the idle-busy degree of the business flow is a busy-time trigger type, determining the target call bill triggering rule to reduce the duration usage threshold of the business flow and increase the business traffic threshold of the target call bill.

8. A non-volatile storage medium, characterized in that: The storage medium includes a stored program, wherein when the program is running, the device where the storage medium is located is controlled to execute the call record trigger control method described in any one of claims 1 to 6.

9. An electronic device, characterized in that: include: processor; a memory for storing instructions executable by the processor; Wherein, the processor is configured to execute the instructions to implement the call record triggering control method as described in any one of claims 1 to 6.

Images